Re: POS Issues

Oh, one last thing:

it happened before, about three or four times, the routers received B3
errors on both sides of this circuit and then the protocol went down (line
up/protocol down). APS did not act, so the protection circuit stayed also
down. The provider always siad their line was fine and that they could not
see any issues. The circuit would not recover unless we did a loopback (hard
or logical) towards the line.

Is that normal? How can I avoid this?

On Thu, Aug 11, 2011 at 1:52 PM, Persio Pucci <persio_at_gmail.com> wrote:

> Thanks, yeah I've reached that article after your email... thank you again
> :)
>
>
> On Thu, Aug 11, 2011 at 1:30 PM, Christian Hunter <stasis416_at_gmail.com>wrote:
>
>> Yes, PSE = positive stuff events, NSE = negative
>>
>> Consider reading:
>> http://www.cisco.com/application/pdf/paws/18932/nsepse_18932.pdf
>>
>>
>>
>>
>> On Thu, Aug 11, 2011 at 11:08 AM, Persio Pucci <persio_at_gmail.com> wrote:
>>
>>> Christian,
>>>
>>> can't thank you enough on this. Last question: on the other side, I have
>>> PSE increasing. Same thing?
>>>
>>>
>>> On Thu, Aug 11, 2011 at 11:23 AM, Christian Hunter <stasis416_at_gmail.com>wrote:
>>>
>>>>
>>>>
>>>> You have a lot of NSE there. This is typically due to synchronization
>>>> problems (timing) on a link due to incorrect clock or degraded signal.
>>>> (Might want to check light levels on either end, and db pad if needed, could
>>>> be lack of attenuation). Have your provider check clocking, etc. The rate of
>>>> NSE should not increase with load. Fiber might need cleaning.
>>>>
>>>> Cisco interfaces only report NSE based on what they see, the interface
>>>> itself does not generate this.
>>>>
>>>> There is an acceptable level of NSE's per day but this depends on your
>>>> clock stratum. Your provider can explain this to you.
>>>>
>>>> BIP3 errors are path level. The B3 byte carries the path parity. So are
>>>> NSE errors, PATH.
>>>>
>>>> Tell your telco provider your seeing BIP(B3) and NSE from your router
>>>> that holds POS4/1/0
>>>> and that your clock source is LINE - give them the circuit ID your
>>>> seeing those errors from.
>>>>
>>>> Good luck!
>>>> Christian Hunter
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Thu, Aug 11, 2011 at 9:57 AM, Persio Pucci <persio_at_gmail.com> wrote:
>>>>
>>>>> Sure, but I have cleared the counters after the last event, so I
>>>>> believe that may not show any current issues... (hostname and IPs were
>>>>> changed to protect the innocent)
>>>>>
>>>>> ROUTER#sh controllers pos 4/1/0
>>>>> POS4/1/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
>>>>> PLM = 0 UNEQ = 0 TIM = 0 TIU = 0
>>>>> LOP = 0 NEWPTR = 0 PSE = 0 NSE =
>>>>> 32246
>>>>>
>>>>> Active Defects: None
>>>>> Active Alarms: None
>>>>> Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA
>>>>>
>>>>> Framing: SDH
>>>>> APS
>>>>> working (active)
>>>>> COAPS = 0 PSBF = 0
>>>>> State: PSBF_state = False
>>>>> Rx(K1/K2): 00/00 Tx(K1/K2): 00/00
>>>>> Rx Synchronization Status S1 = 0B
>>>>> S1S0 = 02, C2 = 16
>>>>> Remote aps status (none); Reflected local aps status (none)
>>>>> CLOCK RECOVERY
>>>>> RDOOL = 0
>>>>> State: RDOOL_state = False
>>>>> PATH TRACE BUFFER: STABLE
>>>>> Remote hostname : REMOTE
>>>>> Remote interface: POS2/2/0
>>>>> Remote IP addr : X.X.X.X
>>>>> Remote Rx(K1/K2): 00/00 Tx(K1/K2): 00/00
>>>>>
>>>>> BER thresholds: SF = 10e-3 SD = 10e-6
>>>>> TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6
>>>>>
>>>>> Clock source: line
>>>>>
>>>>> ROUTER#
>>>>>
>>>>> On Thu, Aug 11, 2011 at 10:46 AM, Christian Hunter <
>>>>> stasis416_at_gmail.com> wrote:
>>>>>
>>>>>> Can you post a sh controller pos x/x/x
>>>>>> for both of the interfaces on either side?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Aug 11, 2011 at 9:36 AM, Persio Pucci <persio_at_gmail.com>wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> anybody with good experience with POS/SDH and some spare time? :)
>>>>>>>
>>>>>>> I am getting some B3 errors on a OC12 circuit I have. The (not) funny
>>>>>>> thing
>>>>>>> is that when I get the B3 errors, I have input errors and CRC errors
>>>>>>> incremented ON BOTH SIDES of the circuit.
>>>>>>>
>>>>>>> Is this an issue on the SDH transport? Cause I've been researching
>>>>>>> about it
>>>>>>> and Cisco literature says B3 are path-level errors and most likely to
>>>>>>> be
>>>>>>> caused by some router interface. If it is a router issue, what can I
>>>>>>> do to
>>>>>>> resolve it?
>>>>>>>
>>>>>>> Any thoughts?
>>>>>>>
>>>>>>>
>>>>>>> Blogs and organic groups at http://www.ccie.net
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________________________________
>>>>>>> Subscription information may be found at:
>>>>>>> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Thu Aug 11 2011 - 13:56:45 ART