RE: SONET-4-ALARM everyday

From: Martin, Christian (cmartin@gnilink.net)
Date: Wed Sep 20 2000 - 19:02:07 EDT


Then it would appear that RTRA may have bad transmit, or the transmit
through the carrier (NEON?) is bad. Recall that if the transit through the
carrier was bad, the carrier would be seeing Line errors at some point in
their network. Since this is less likely than there being a bad transmit
from RTRA, have the carrier check the Rx port on their LTE. They are likely
seeing errors.

regards,
.chris

-----Original Message-----
From: tishi@ziplink.net [mailto:tishi@ziplink.net]
Sent: Wednesday, September 20, 2000 3:33 PM
To: cisco-nsp@puck.nether.net
Subject: Re: SONET-4-ALARM everyday

thank you all who responded to my email.
to clarify my configuration. I have

RTA ----- NEON ---- RTB

RTA logs SONET-4-ALARM everyday. MIB shows.
sonetFarEndPathCurrentESs.5 = Gauge: 122
sonetFarEndPathCurrentSESs.5 = Gauge: 0
sonetFarEndPathCurrentCVs.5 = Gauge: 122
sonetFarEndPathCurrentUASs.5 = Gauge: 0

RTB does not log SONET-4-ALARM at all, MIB shows.
sonetPathCurrentESs.2 = Gauge: 122
sonetPathCurrentSESs.2 = Gauge: 0
sonetPathCurrentCVs.2 = Gauge: 122
sonetPathCurrentUASs.2 = Gauge: 0
sonetFarEndPathCurrentESs.2 = Gauge: 1
sonetFarEndPathCurrentSESs.2 = Gauge: 1
sonetFarEndPathCurrentCVs.2 = Gauge: 81
sonetFarEndPathCurrentUASs.2 = Gauge: 0

I do not see any errors on sonetSectionCurrent.., sonetLineCurrent.. and
sonetFarEndLineCurrent.. .

any idea?

-tishi

On Tue, 19 Sep 2000 tishi@ziplink.net wrote:

> Hi all,
>
> I am getting syslog entries listed below everyday.
> I had a TAC case but all I got from CISCO was "it's a dirty fiber".
> If that is the case, how a dirty fiber affects us everyday
> almost at the same time? I contacted a SONET provider,
> they told me that "we do not see any hit". I also see lots of
> PATH errors.
>
> any suggestions?
>
> -tishi
>
> >>>>
> Sep 14 04:44:55 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER exceeds threshold,
TC alarm declared
> Sep 14 04:46:44 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER below threshold,
TC alarm cleared
> Sep 15 04:44:56 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER exceeds threshold,
TC alarm declared
> Sep 15 04:46:45 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER below threshold,
TC alarm cleared
> Sep 16 04:44:57 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER exceeds threshold,
TC alarm declared
> Sep 16 04:46:46 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER below threshold,
TC alarm cleared
> Sep 17 04:44:59 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER exceeds threshold,
TC alarm declared
> Sep 17 04:46:48 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER below threshold,
TC alarm cleared
> Sep 18 04:44:59 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER exceeds threshold,
TC alarm declared
> Sep 18 04:46:48 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER below threshold,
TC alarm cleared
> Sep 19 04:45:00 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER exceeds threshold,
TC alarm declared
> Sep 19 04:46:49 EDT: %SONET-4-ALARM: POS5/0/0: B3 BER below threshold,
TC alarm cleared
> <<<<
>
>
>



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:17 EDT