[c-nsp] Troubleshooting OC3

[Scott Weeks]

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


----- Original Message Follows -----
From: "Paul Stewart" <pstewart at nexicomgroup.net>
To: <surfer at mauigateway.com>, <cisco-nsp at puck.nether.net>
Subject: RE: [c-nsp] Troubleshooting OC3
Date: Mon, 16 Jan 2006 16:36:12 -0500

> I just talked to another tech who has access to the DSLAM
> and he said that the errors they see are "out of bounds"
> errors??
> 
> Sorry, as some of you may have realized.. My ATM knowledge
> is very minimal on a good day...;) 
> 
> -----Original Message-----
> From: surfer at mauigateway.com
> [mailto:surfer at mauigateway.com]  Sent: Monday, January 16,
> 2006 4:32 PM To: Paul Stewart; cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] Troubleshooting OC3
> 
> 
> 
> On the surface it looks like a physical layer problem:
> 
>    20966 input errors, 20966 CRC
> 
> But the counters haven't been cleared for over 4 days:
> 
>    Last clearing of "show interface" counters 4d06h
> 
> What're your SONET counters showing?
> 
> scott
> 
> 
> 
> ----- Original Message Follows -----
> From: "Paul Stewart" <pstewart at nexicomgroup.net>
> To: <cisco-nsp at puck.nether.net>
> Subject: [c-nsp] Troubleshooting OC3
> Date: Mon, 16 Jan 2006 16:09:15 -0500
> 
> > We have a pair of OC3's coming into a 7206VXR currently
> > from an AFC  DSLAM shelf.... Getting fair amount of
> > errors and just wondering how  to troubleshoot it.... If
> > anyone has any input please feel free..;)