[c-nsp] 7304 OC12 issue

Aaron dudepron at gmail.com
Fri Nov 2 10:44:12 EDT 2007


That looks like a bug with POS in the 12.2 code. NSE just means that the
payload has moved in the sonet frame as per design.

Aaron

On 11/2/07, Tim Murfy <timothy.murfy at gmail.com> wrote:
>
> Well, we are now able to reproduce the errors. Everytime we write mem, we
> can cause those input errors to occur.  They are only occuring on the POS
> interface.  If we are not doing with write mem, then we have no problems.
> We are running 12.2(31)SB9.
>
> Thanks,
>
> On 10/29/07, Mike Johnson <harbor235 at gmail.com> wrote:
> >
> > Tim,
> >
> > NSEs (Negative stuff events) are accumulating, this indicated a timing
> > issue as they
> > were not generated when you downed/up the circuit. Clear the counters
> and
> > see if they increment again.
> > If they continue to increment I would engage you circuit provider and
> have
> > them check their hardware.
> >
> > harbor235
> >
> > On 10/29/07, Tim Murfy <timothy.murfy at gmail.com> wrote:
> > >
> > > Here is the output:
> > >
> > > POS2/0/0
> > > SECTION
> > >   LOF = 0          LOS    = 0                            BIP(B1) = 0
> > > LINE
> > >   AIS = 0          RDI    = 0          FEBE = 0          BIP(B2) = 0
> > > PATH
> > >   AIS = 0          RDI    = 0          FEBE = 0          BIP(B3) = 0
> > >   LOP = 0          NEWPTR = 0          PSE  = 0          NSE     =
> > > 414640
> > >
> > > Active Defects: None
> > > Active Alarms:  None
> > > Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
> > >
> > > Framing: SONET
> > > APS
> > >
> > >   COAPS = 0          PSBF = 0
> > >   State: PSBF_state = False
> > >   Rx(K1/K2): 00/00  Tx(K1/K2): 00/00
> > >   S1S0 = 00, C2 = CF
> > >   Remote aps status (none); Reflected local aps status (none)
> > > CLOCK RECOVERY
> > >   RDOOL = 0
> > >   State: RDOOL_state = False
> > > PATH TRACE BUFFER: STABLE
> > >   Remote hostname : XXXXXXXXXXXXXXXXXX
> > >   Remote interface:
> > >   Remote IP addr  :
> > >   Remote Rx(K1/K2):   /    Tx(K1/K2):   /
> > >
> > > BER thresholds:  SF = 10e-3  SD = 10e-6
> > > TCA thresholds:  B1 = 10e-6  B2 = 10e-6  B3 = 10e-6
> > >
> > >   Clock source:  line
> > >
> > > On 10/29/07, Aaron <dudepron at gmail.com> wrote:
> > > >
> > > > What does the show controller pos show?
> > > >
> > > > Aaron
> > > >
> > > > On 10/29/07, Tim Murfy <timothy.murfy at gmail.com> wrote:
> > > >
> > > > >    We are experiencing a strange issues with our new 7304 and a
> new
> > > > > OC-12
> > > > > circuit. When we bring the circuit up with a full BGP table, we
> see
> > > > > ignored
> > > > > errors on the POS interface every few seconds.  The only errors we
> > > see
> > > > > are
> > > > > the ignored errors, and the match the input error number
> > > exactly.  The
> > > > > show
> > > > > controllers show nothing wrong.  This is happening when traffic
> > > patters
> > > > > are
> > > > > only around 40 Mbps/8K pps.  We have turned everything off that
> > > could be
> > > > > turned off on the interface, including service policy, ACL's,
> > > netflow.,
> > > > > and
> > > > > it still showed this symptom.  Has anyone seen anything
> > > similiar?  Its a
> > > > >
> > > > > cisco 7304 with NPE-G100 using the SPA adapter with the OC12 card.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Tim
> > > > > _______________________________________________
> > > > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > > >
> > > >
> > > >
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > >
> >
> >
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>


More information about the cisco-nsp mailing list