[c-nsp] Troubleshooting OC3

[Paul Stewart]

I got an offlist message from a helpful guy who stated the errors are
actually nothing to worry about.... The errors are generated because of
the subscriber's dsl connections going across these links and that any
errors they incurred would showup on the ATM side ... Makes sense...;)

So I guess I can safely ignore these errors.... The DSLAM folks on our
side are looking into it further between remote DSLAMS where they are
seeing a lot of errors before they hit the Cisco...

Thanks to everyone for the replies...

Paul
 

-----Original Message-----
From: surfer at mauigateway.com [mailto:surfer at mauigateway.com] 
Sent: Monday, January 16, 2006 4:53 PM
To: Paul Stewart; surfer at mauigateway.com; cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] Troubleshooting OC3


What I'm looking for are BIP-8 errors (B1, B2 and B3 (section, line and
path) errors).  Not having used cisco for a few years (I'm a Juniper
junkie as of late) I don't know the exact command to get that info.
It's not ATM stats, it's SONET stats that're needed.  You were close on
the bottom of the output to James, but I saw no numbers on the
counters:

   Facility statistics: current interval elapsed 855 seconds
             sbip      lbip      lfebe      pbip     pfebe  
 hcse
     
------------------------------------------------------------


CRC errors say that the ones and zeros received don't match what was
sent.  In my experience, many times this indicates a problem on the
line.

scott