[c-nsp] Help with old POSIP card

[Michael K. Smith - Adhost]

Hello Bill:

> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of Bill Wichers
> Sent: Wednesday, January 17, 2007 9:21 PM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] Help with old POSIP card
> 
> I have an old POSIP-OC3-50-SM blade giving some wierd errors... Can
> anyone
> help me to interpret the output (I'm afraid the blade might be dead):
> 
> ---- snip 8< ----
> POS5/0/0
> SECTION
>   LOF = 0          LOS = 0                            BIP(B1) = 1866
> LINE
>   AIS = 0          RDI = 0          FEBE = 72         BIP(B2) = 669
> PATH
>   AIS = 0          RDI = 0          FEBE = 33218      BIP(B3) = 23955
>   PLM = 0          UNEQ = 0
>   LOP = 0          NEWPTR = 10765      PSE = 15585       NSE = 0
> 
> Active Defects: B3-TCA
> Active Alarms:  B3-TCA
> Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
> 
> APS
>   COAPS = 1          PSBF = 0
>   State: PSBF_state = False
>   Rx(K1/K2): 00/00  Tx(K1/K2): 00/00
>   S1S0 = 00, C2 = CF
> CLOCK RECOVERY
>   RDOOL = 0
>   State: RDOOL_state = False
> PATH TRACE BUFFER: STABLE
>   Remote hostname : troy-319-router1
>   Remote interface: POS0/0/0
>   Remote IP addr  : 216.29.182.94
>   Remote Rx(K1/K2): 00/00  Tx(K1/K2): 00/00
> 
> 
> 4285F3D0:     7472 6F792D33 31392D72 6F757465    troy-319-route
> 4285F3E0: 72310000 00000000 0000504F 53302F30  r1........POS0/0
> 4285F3F0: 2F300000 00000000 3231362E 32392E31  /0......216.29.1
> 4285F400: 38322E39 34000000 30303030 30303030  82.94...00000000
> 4285F410: 0D0A                                 ..
> BER thresholds:  SF = 10e-3  SD = 10e-6
> TCA thresholds:  B1 = 10e-6  B2 = 10e-6  B3 = 10e-6
> 
>   Clock source:  internal
> ---- snip 8< ----
> 
>     -Bill
> 
> 
Here's a pretty good Cisco link for troubleshooting SONET.
http://www.cisco.com/warp/public/127/biterrorrate_16149.html

I would check the physical layer (connections, fiber and terminations)
and also confirm clock source.  It appears you are using clock-source
internal.  Have you tried switching to clock-source line if that's
available?

Regards,

Mike