Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Meaning of Alarms

Hi ,

please anyone tell me the meanings of these alrams which are coming in my MGX 8850

M8850_SF.10.MPSM155[FR].a > dsplnalmcnt 1.1

Line Number: 1.1

Elapsed Time(in sec): 397

Num of LOS : 0

Num of OOF : 0

Num of RAI : 0

Near End Far End

CurrentCCVs : 0 CurrentCCVs : 0 <--------- This

CurrentCESs : 0 CurrentCESs : 0 <--------- This

CurrentCSESs : 0 CurrentCSESs : 0 <-------- This

CurrentUASs : 6 CurrentUASs : 6 <-------- This

CurrentLCV : 0 <------------

CurrentLES : 0 <----------

CurrentLSES : 0

CurrentPCV : 0

CurrentPES : 0

CurrentPSES : 0

Current24HrLCV : 0

Current24HrLES : 0

Current24HrLSES: 0

Current24HrPCV : 0

Current24HrPES : 0

and due to which error do we get this alarms

regards

2 REPLIES

Re: Meaning of Alarms

Hello,

Num of LOS : 0

Number of "Loss Of Signals"

Num of OOF : 0

Number of "Out Of Frame" conditions

Num of RAI : 0

Number of "Remote Alarm Indicator" occurences

Near End Far End

Current "NE/FE alarm conditions"

CurrentCCVs : 0 CurrentCCVs : 0 <--------- This

Current "Channel Code Violations"

CurrentCESs : 0 CurrentCESs : 0 <--------- This

Current "Channel Errored Seconds"

CurrentCSESs : 0 CurrentCSESs : 0 <-------- This

Current "Channel Severely Errorred Seconds"

CurrentUASs : 6 CurrentUASs : 6 <-------- This

Current "UnAvailable Seconds"

CurrentLCV : 0 <------------

Current "Line Code Violations"

CurrentLES : 0 <----------

Current "Line Errored Seconds"

CurrentLSES : 0

Current "Line Serverely Errored Seconds"

CurrentPCV : 0

Current "Path Code Violations"

CurrentPES : 0

Current "Path Errored Seconds"

CurrentPSES : 0

Current "Path Severely Errored Seconds"

Current24HrLCV : 0

"Last 24 hour Line Code Violations"

Current24HrLES : 0

"Last 24 hours Line Errored Seconds"

Current24HrLSES: 0

"Last 24 hours Line Severely Errored Seconds"

Current24HrPCV : 0

"Last 24 hours Path Code Violations"

Current24HrPES : 0

"Last 24 hours Path Errored Seconds"

The generally have to do with your line format - STM1 and the multiplexer stuff behind. You can define the error/alarm counters and conditions with xcnfalmcnt and you find an description at

http://www.cisco.com/en/US/products/hw/switches/ps1938/products_configuration_guide_chapter09186a0080203fe6.html#wp1700762

Hope this helps! Please rate all posts.

Regards, Martin

Silver

Re: Meaning of Alarms

To elaborate further on the errors:

Num of LOS : 0

Number of "Loss Of Signals" These are the loss of input signal to your interface. Caused by many reasons(no cable)

Num of OOF : 0

Number of "Out Of Frame" conditions This is the loss of framing to your interface. This is where you have a signal but no framing. Can be caused by the carrier not configured correctly.

Num of RAI : 0

Number of "Remote Alarm Indicator" occurences . This is an indication that the remote end is seeing an alarm from you. Maybe they lost signal from you or your xmit is bad. They will send this alarm to you.

Near End Far End

Current "NE/FE alarm conditions" This is another alarm that is similar to the previous.

CurrentCCVs : 0 CurrentCCVs : 0 <--------- This

Current "Channel Code Violations" This is in reference to the line code (B8ZS, AMI). This can be caused by a mismatch of line coding from you to the carrier.

CurrentCESs : 0 CurrentCESs : 0 <--------- This

Current "Channel Errored Seconds" This is a count of errored seconds from a time reference (counters cleared). You need to look at this error along with the following ones to determine how bad your problem is.

CurrentCSESs : 0 CurrentCSESs : 0 <-------- This

Current "Channel Severely Errorred Seconds" This is a counter on severly errored seconds. The previous error was just errored seconds, this counter shows you long and continuous errors on the line. Again, you can determine and figure out you problem by looking at these errors.

CurrentUASs : 6 CurrentUASs : 6 <-------- This

Current "UnAvailable Seconds" This shows you the current unavailable seconds. This means you have a loss of signel now on the line.

CurrentLCV : 0 <------------

Current "Line Code Violations" Shows current line code violations. This is real time not like the one above which showed you the errors that happened.

CurrentLES : 0 <----------

Current "Line Errored Seconds" This is the line errored seconds where the counter shows you the framing errors of the line. The error above is for clocking this is for framing.

CurrentLSES : 0

Current "Line Serverely Errored Seconds" The same for framing to show you severly errored seconds on the line.

CurrentPCV : 0

Current "Path Code Violations" This shows you the total path (point a to z) and if you had any path code violations.

CurrentPES : 0

Current "Path Errored Seconds" Same for the path to show you path errored seconds.

CurrentPSES : 0

Current "Path Severely Errored Seconds" Sam as above...

Current24HrLCV : 0 These remaining errors are accumulations throughout the past 24 hours...

"Last 24 hour Line Code Violations"

Current24HrLES : 0

"Last 24 hours Line Errored Seconds"

Current24HrLSES: 0

"Last 24 hours Line Severely Errored Seconds"

Current24HrPCV : 0

"Last 24 hours Path Code Violations"

Current24HrPES : 0

"Last 24 hours Path Errored Seconds"

Hope I clarified these errors for you.....

289
Views
9
Helpful
2
Replies
CreatePlease to create content