ons alarms events

7/31/2019 Ons Alarms Events

1/29

Common Alarms and Events Supported by ONS15305 and ONS 15302

Document ID: 64208

ContentsIntroduction

Prerequisites

Requirements

Components Used

Conventions

Alarms and Events

Related Information

Introduction

This document explains the most common alarms that ONS 15305 supports. Many of these alarms are alsoapplicable to ONS 15302, except for some differences in default severity for some of the alarms, because the

products serve different roles in a network.

For an overview of the default alarm suppression list and persistency for each type of network element (NE),

refer to the respective user guides.

Note: Ensure that you enable alarm reporting for modules and ports that are in use, because these parameters

are disabled by default.

Note: Most alarm IDs with higher severity than Warning, which is an event, are onoff alarms (which are

raised and cleared).

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

Cisco ONS 15305 and 15302

Components UsedThe information in this document is based on the Cisco ONS 15305 and 15302.

The information in this document was created from the devices in a specific lab environment. All of the

devices used in this document started with a cleared (default) configuration. If your network is live, make sure

that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.


2/29

Alarms and Events

This table describes the alarms and events on Cisco ONS 15305 and 15302:

Reference

NumberObject

Default

Severity

Alarm Id

(ProbCause)

Description

(ProbCauseQ)Detailed Description

1aiPort Warning alarmInp

Alarm condition

on alarmin

port

The NEs provide four auxiliary alarm

inputs (dry contact alarms) for associat

equipment. For example, power modul

failure, battery condition, and open cab

door. The operator can set the alarm to

triggered on either open or closed cont

2au4 Minor ais

Alarm

Indication

Signal (AIS)

When an NE detects a defect in the

regenerator section (RS) or the multipl

section (MS) of an incoming link, the

payload of that link is invalid. The NE

replaces the payload with an AIS in th

forwarding direction.

All subsequent NEs detect AU4 AIS.

Note: By default, the alarm is suppres

3au4 Critical lop Loss Of Pointer

AU4 Loss of Pointer (LOP) occurs w

an NE is unable to interpret the AU4

pointer. This alarm normally indicates

the NE receives concatenated AU4s w

the NE actually expects nonconcaten

AU4s.

4au4 Major epj

Excessive Ptr

Justification

This alarm appears if the number of Pojustification events (PJEs) over a

15minute period is greater than a

threshold that you can configure, or th

PJEL (Pointer Justification Event Limi

You can configure the PJEL individua

for each AU4 from 1 to 1024 events.

default configuration is 100 events per

interval.

PJE, both positive and negativejustifications, are counted and measure

over a 24hour interval. Both current a

past 24hour interval counters are

available.

5 au4 Warning switchWork


3/29

SNCP switched

to working

This event occurs if the traffic switche

from protectingto working.

Switching criteria depend on SNCP ty

other words, the criteria depend on wh

SNCP is SNC/i or SNC/n. The main

difference between the two is that in

addition to a switch on AIS/LOP alarm

SNC/n also switches on (nonintrusive

UNEQ/TIM/DEG/EXC alarms.

6au4 Warning switchProt

SNCP switched

to protecting


from workingto protecting.

Switching criteria depend on SNCP ty

other words, switching depends on wh

SNCP is SNC/i or SNC/n. The main

difference between the two is that in

addition to switch on AIS/LOP alarms



7au44c Minor ais

Alarm

Indication

Signal

When an NE detects a defect in the

regenerator section (RS) or the multipl

section (MS) of an incoming link, the

payload of that link is invalid. The NE

replaces the payload with an AIS in th

forwarding direction.

All subsequent NEs detect AU44c A

Note: By default, the alarm is suppres

8au44c Critical lop Loss Of Pointer

AU44c Loss of Pointer (LOP) occur

when an NE is unable to interpret the

AU44c pointer. This normally indic

that the NE receives nonconcatenated

AU4s when the NE expects concaten

AU44cs.

9 au44c Major epj Excessive Ptr

Justification

Excessive Pointer justification (EPJ) a

appears if the number of Pointer

justification events (PJEs) over a

15minute period is greater than a

threshold that you can configure, or th

PJEL (Pointer Justification Event Limi

You can configure the PJEL individua

for each AU44c from 1 to 1024 eve

100 events per interval is the default

configuration.

PJE, both positive and negative

justifications, are counted and measure

over a 24hour interval. Both current a

past 24hour interval counters are


4/29

available.

10au44c Warning switchWork

SNCP switched

to working



Switching criteria depend on the SNCP

type. In other words, switching depend

whether SNCP is SNC/i or SNC/n. Th

main difference between the two is tha




11 au44c Warning switchProt SNCP switchedto protecting



Switching criteria depend on the SNCP

type. In other words, switching dependwhether SNCP is SNC/i or SNC/n. Th

main difference between the two is tha




12auxIf Major lofTx Loss Of Frame

This alarm appears when an unsupport

signal type arrives.

13auxIf Major los Loss Of Signal

This alarm appears when the AUX inte

has no signal.

14device Critical ufail

Device main

unit failure

This alarm appears if you encounterproblems when you try to load FPGA,

SPI/Eeprom, Power input, DXC inlet o

XBAR on Main card.

15 device Major temp High

temperature

alarm

This alarm appears if the temperature

exceeds 450. For ONS 15305, both pa

Fans spin.


5/29

16device Major t0HoldOver

T0 in holdover

mode

This alarm appears if none of the T0

synchronization candidates is available

17device Critical t0Defect T0 SETG defect

This alarm appears for defective hardw

that impacts the internal T0 clock.

18device Warning t0SyncSwitch

T0 sync

switchover

This event occurs when automatic, ma

or forced switchover occurs.

19device Warning t0QlFailed

T0 sync

candidate in fail

This alarm applies to T1/T2/T3 source

member of the T0 synchronization tab

20device Warning t0QlDnu

T0 sync

candidate rec.

DNU

This alarm appears when T0

synchronization candidate receives the"DoNotUse" message.

21device Critical t4Squelch

T4 output

squelched

This alarm appears when no T4

synchronization candidate has QL equ

or above QLmin

22device Critical inletFail

DXC inlet

failure

When you power cycle (turn the powe

or off at different temperatures) a devi

the main card can fail to recover opera

after the power on or off, and can rema

an alarm state. In such a state, the devi

does not carry traffic, and the card repo

the "DXC inlet failure alarm."

23device Critical inletBitError

DXC inlet bit

error

The DXC inlet bit error alarm appears

the device level to indicate a failure

between the two DXC devices on the

mainboard. The system detects no fai

in nominal conditions.

24device Warning unknownFlashType

Unknown

FLASHdevice

detected

This alarm appears when the Flashpr

discovers an unknown flash type on th

mainboard.

25device Warning errorNewBank

ERROR in

newest bank

This error indicates that the mainboar

does not start up with the latest downlo

firmware.

26device Warning alarmStormStart

Alarm storm

start detected

This alarm indicates number of alarm

changes is too high for the device to re

all alarms as traps.

27 device Warning alarmStormEnd Alarm storm

end detected

This alarm appears when the number o

alarm status changes reduces to a level

where all alarms show up as traps agai


6/29

28device Warning

rxOverflow

HWFault

RX buffer

overflow

This alarm indicates an overflow of the

receive buffers on the LAN interface.

29device Warning

txOverflow

HWFault

Interport queue

overflow

This alarm indicates an interport queue

overflow on the LAN interface.

30device Warning routeTable Overflow

Routing table

overflow

This event occurs when the routing tab

exceeds 2048 entries.

31device Warning endTftp

TFTP session

completed

This event occurs on successful compl

of a TFTP session.

32device Warning abortTftp

TFTP session

aborted

This event occurs when the completion

TFTP session is unsuccessful.

33device Warning startTftp

TFTP session

initiated

This event occurs when a download

operation starts from the manager towa

the NE. For example, a software upgra

configuration file restore operation.


7/29

34device Warning

forwardingTab

Overflow

Layer II

Forward Table

overflow

This event indicates that the Unicast G

Forwarding table has reached the maxi

limit on the number of MAC addresses

new addresses are learned until old on

removed (which can happen through a

or when a link goes down, or when the

operator removes them).

35device Warning vlanDynPortAdded

DynamicVLAN port

added

This event shows that the GVRP proto

dynamically adds a port to a VLAN.

36device Warning

vlanDynPort

Removed

Dynamic

VLAN port

removed

This event shows that the GVRP proto

dynamically removes a port from a VL

37device Warning rsPingCompletion

Ping sequence

completed

This event signifies the completion of

sequence of ICMP echos (Pings) initia

from the device.

38device Warning

rlIgmpTable

Overflow

IGMP table

overflow

This alarm indicates that the maximum

allowed entries in the IGMP table has reached.

39device Warning rlIpFftStnOverflow

IP SFFT

overflow

This alarm shows that the table that ho

an individual IP address to forward da

full.

40e1Port Major lofRx

Loss Of Frame

downlink

This alarm appears on E1 in PRA mod

when E1 receives the signal from the

network in a format that E1 does not

expect.

41 e1Port Major lofTx Loss Of Frameuplink


when E1 receives the signal on the PDport in a format that E1 does not expec

42e1Port Minor aisRx

AIS received

downlink


when the network sends a signal with A

to E1. This event indicates an alarm

elsewhere in the network.

43e1Port Critical los Loss Of Signal

This alarm appears when the E1 port d

not receive a PDH signal.

44e1Port Warning loopClosed Loop closed

This event occurs when you set a test

on an E1port.

45e1Port Warning loopOpened Loop opened

This event occurs when a testloop cle

on an E1port.

46e3T3Port Minor aisRx

AIS received

downlinkNot supported.

47e3T3Port Critical los Loss Of Signal

This alarm appears when the E3 port d

not receive a PDH signal.

48e3T3Port Warning loopClosed Loop closed

This event occurs when you set a test

on an E3port.

49 e3T3Port Warning loopOpened loop opened This event occurs when a testloop cle


8/29

on an E3port.

50eth Warning

rldot1dStpPort

StateForwarding

Bridge port

learning to

forwarding state

transition

This message means that the STP port

for the given port has moved from Lea

state to Forwarding state. The port now

forwards traffic.

51

eth Warning

rldot1dStpPort

StateNotForwarding

Bridge port

forwarding to

blocking statetransition

This message means that the STP port

for the given port has moved from theForwarding state to the Blocking state

port no longer forwards traffic.

52fan Major fan Fan failure

This alarm appears on the maincard w

temperature rises above 850C. The ala

specific for each fan. The maincard

processes and presents this alarm as Fa

Failure Alarm.

53fan Critical diagFail

Diagnostic

failure

This alarm implies incorrect module

identification.

54fan Major inventoryFail

Inventory

failure

This alarm indicates that inventory

retrieved from the fan module does no

match with expected inventory.

55gfp Minor plm

GFP payload

mismatch

This alarm appears due to a mismatch

between expected and received PTI va

the GFP PTI field.

Refer to ITUT G.7041 for details.

56gfp Minor upm

GFP user payl.

type mismatch

This alarm appears when the received Payload Identifier (UPI) is different fro

the expected UPI. This release support

FrameMapped Ethernet UPI.

Refer to alarm based on detection of U

field value in ITUT G.7041.

57gfp Minor lfd

GFP loss of

frame delin.

This alarm appears when the delineatio

process is not in SYNC state.

58 gfp Minor exm GFP exheader

ident. mismatch

This alarm appears when the received

Extension Header Identifier (EXI) is


9/29

different from the expected EXI. This

release supports the Null Extension He

EXI.

Refer to alarm based on detection of E


59gfp Minor pfm

GFP payloadFCS ident.

mismatch


Payload FCS Indication (PFI) is differfrom the expected PFI.

Refer to alarm based on detection of P


60lanx Warning lanOn Link Up

This event occurs as you try to connec

Ethernet LANport.

61lanx Warning lanOff Link Down

This event occurs as you try to disconn

the Ethernet LANport.

62lcas Warning acMstTimeout

Ack Mst

Timeout

This event indicates a Member Status

Signal (MST) timeout. When you add VCn to the upstream capacity, MST=

for this VCn is expected to be receive

from the opposite end. If the source do

not receive an MST=OK within a

reasonable amount of time, the source

declares a timeout.

63 lcas Warning rsAckTimeout RS ACKTimeout

This event indicates that an RSsequen

Acknowledge has timed out. When an

LCAS source resequences the VCn

channels, the LCAS source expects the

opposite end to acknowledge this operthrough an RSACK. If the source doe

receive an RSACK within a reasonab

amount of time, the source declares a

timeout.

64lcas Minor eosMultiple

Two or more

chan. have EoS

This event occurs when two or more

received channels have End of Sequen

(EoS). One and only one channel must

EOS. See sqnc alarm.

65lcas Minor eosMissing

No channel has

EoS

None of the received channels has End

Sequence (EoS). One and only one chamust have EOS. See sqnc alarm.

66lcas Minor sqNonCont

Missing SQ

detected

This alarm appears when a sequence

number is missing. See sqnc alarm.

67lcas Minor sqMultiple

Equal SQ for

two or more

chan

This message appears when two or mo

channels have the same sequence num

See sqnc alarm.

68 lcas Major sqOor


10/29

SQ outside of

range

This alarm occurs when the received

sequence number is outside of the vali

range (VC4: 06, VC3: 020, VC

062). See sqnc alarm.

69 lcas Major sqnc sequence nbrnot consistent

This alarm appears when one or more

these alarms occur: eosMultiple,eosMissing, sqNonCont, sqOor and

sqMultiple.

70lcas Major gidErr

GID different

for active chan

This alarm appears when active chann

within the same VCGroup receive diff

Group ID.

71 lcas Major ctrlOor CTRL wordundefined

This alarm indicates the receipt of an ior undefined CTRL word value.

72lcas Major lcasCrc

CRC error

detected

This alarm appears when the Cyclic

Redundancy Check (CRC) fails.

73lcas Minor nonLcas

NonLCAS

source detected

This alarm implies that the NE at the o

end is not in LCAS mode.

74lcas Major plcr

Partial loss

capacity rx


capacity is less than expected.

75lcas Critical tlcr

Total loss

capacity rx

This message indicates that the port

receives no traffic.

76lcas major plct

Partial loss

capacity tx

This alarm appears when the send capa

is less than expected.

77 lcas Critical tlct Total loss

capacity tx

This message indicates that no traffic i

sent.


11/29

78module Critical modFail Module failure

This alarm indicates a module failure

(power loss on the module).

79module Critical diagFail

Diagnostic

failure

This alarm appears when you encounte

problems when you try to load FPGA,

SPI/Eeprom, Power input, DXC inlet o

Ethernet switch on service modules.

80module Major inventoryFail

Inventory

failure

Inventory failure occurs when module

identification is not correct.

81module Critical inletFail

DXC inlet

failure

When you power cycle (power on/off

different temperatures) a service modu

the card can fail to recover operation a

the power on/off, and can remain in analarm state. In sych a state the card doe

carry traffic. When the card indicates t

"DXC inlet failure alarm", the LED of

card is also red. The card recovers norm

operation after software reset. This issu

occurs in approximately one out of eve

power cycles.

82module Critical inletBitError

DXC inlet bit

error

Cards with EoS mappers can experienc

packet losses. For example, LAN traff

mapped to EoS ports on 8xSTM1+map

module, and "DXC inlet bit error alarmconditions can occur when you expose

8xSTM1+map cards to extreme tempe

cycles (5 to 50C with 2 hours dwell

each extreme temperature, and 1C/mi

gradients). The packet losses and cond

can occur on the 8xSTM1+map card. T

only occurs under temperature stress. T

frequency with which the issue occurs

average of 10 packets lost, and less tha

100 alarms recorded in a 12 hours cycl

Nominal conditions record no failures.

83 module Critical cardIsolated Card isolated The 'card isolated' error can occur in th

conditions:

A card anomaly occurs while t

module is inservice:

Module removed (extr

from the chassis).

a.

Module failed (power

on the module).

b.

1.


12/29

Dxc inlet failure (inter

between maincard an

module).

Note: If a) or b) or c)

occurs on pure SDH/P

modules, an alarm app

Card_removeCard_anomaly

(B/C)

If a) occurs on module

with switch

(8xstm1_map/8xfe/2x

an alarm (card_remov

appears, BUT, in addi

the complete device

restarts, due to

recovery/cleanup

handling of the crossbswitch system. When

device is up again, the

card_removed alarm i

present.

If b) or c) occurs on

modules with switch

(8xstm1/8xfe/2xge/4x

an alarm (card_anoma

appears BUT in additi

the complete devicerestarts, due to

recovery/cleanup

handling of the crossb

switch system. When

device is up again, the

failed module is mark

"ISOLATED".

c.

On a module (with switch

8xstm1/8xfe/2xge/4xfe_map/8

the hotremoval process fails

you shut down the module. Ag

the system restarts, due to

recovery/cleanup handling of

crossbar or switch system. Wh

the device is up again, the faile

module is marked "ISOLATED

2.

84module Critical cardAnomaly Card anomaly See card Isolated.

85 module Critical hotSwapFailure Hot swap failure This alarm indicates that the module c

be reported to the processor, and Ether

services will not become operational fo

module.


13/29

86module Warning modOos

Module Out Of

Service

This event occurs when the module en

the OOS state.

87module Warning modOosMaint

Module OOS by

maintenance


the OOS by maintenance state.

88module Warning modIns

Module IN

Service


the inservice state.

89module Warning unknownFlashType

Unknown

FLASHdevice

detected

This alarm appears when the Flashpr

discovers an unknown flash type on th

module.

90module Warning errorNewBank

ERROR in

newest bank

This error appears when the module donot start up with the latest downloaded

firmware.

91module Warning moduleShutdown

Module

shutdown


the Shutdown state.

92module Warning moduleRestart Module restart


the Restart state.

93module Warning modUnEq

Module

UnEquipped

This event occurs when the module or

enters the Unequipped state.

94mst Major exc

BER excessive

error rate

This alarm appears if the Bit Error Rat

greater than 1E5.

95 mst Minor deg Signal degrade

(BER low)

This alarm appears when the Bit Error

is greater than the configured threshold

You can configure the threshold for th

alarm from 1E6 to 1E9. For exampl

set to 1E7 (default), an alarm appears

when BER exceeds this threshold.


14/29

The detection time depends on the

threshold. (1E6 has a short

detectiontime, 1E9 has longer detec

time).

96mst Minor csf

Dcc

Termination

Failure

This alarm can occur for a DCCm

(D4D12) connection, which is active

does not properly terminate at the othe

97mst Minor ais

Alarm

Indication

Signal

MSAIS is the alarm indication signal

the multiplexer section (MS). STMn

that are not configured often transmit

MSAIS, and a regenerator with no in

signal transmits MSAIS.

98mst Minor rdi

Remote Defect

Indication

If an RS alarm (LOS, LOF, TIM, AIS)

MSAIS appears on an STMn port,

MSRDI goes out on that port.

99mst Critical msp

MSP signalling

problem

This problem typically occurs if you h

mismatch in configuration. In other wo

this occurs when your configuration is

unidirectional on one end and bidirecti

on the other end.100

mst Warning switchToProtMSP switched

to protecting



101mst Warning switchToWork

MSP switched

to working



102mst Warning mspComTimeOut

MSP command

timed out,

removed

This event indicates the timeout of an

MSPcommand that you successfully

at this end. The timeout occurs due to

"no" from the other end. This alarm onappears when you use bidirectional M

103mst Warning mspComOverruled

MSP command

overruled,

removed

This event indicates that a user has ent

an MSPcommand with a higher prior

the other end of the connection. The re

is that the MSPcommand at this end i

removed. This alarm only appears whe

you use bidirectional MSP.


15/29

104power Critical pwrInA

Power failure

input AThis means power input A is absent.

105power Critical pwrInB

Power failure

input BThis means power input B is absent.

106power Critical pwrOut

Power output

failure

This indicates that 48VDC / 230VAC

power module does not provide intern

power (5V).

107power Critical pwrFail

Power module

out

This alarm appears if the power modul

administratively enabled and removed

108power Critical diagFail

Diagnostic

failure

This failure occurs due to incorrect mo

identification.

109power Major inventoryFail

Inventory

failure

This event occurs if the correct

HWinventory cannot be retrieved fro

powermodule.

110 power Critical pwrUIL 230VAC powerinput low

This alarm appears when an AC modu

receives less than 195VAC from the230VAC outlet.

111 power Critical pwrUIH 230VAC powerinput high

This alarm appears when an AC modu

receives more than 255VAC from the

230VAC outlet.

112rst Critical lof Loss Of Frame

The loss of frame (LOF) alarm appear

when the frame sync is not recognizab

and the out of frame (OOF) alarm pers

for 3ms.


16/29

113rst Major exc

BER excessive

error rate


greater than 1E5.

114rst Minor deg

Signal degrade

(BER low)










time).

115rst Critical tim

Trace Identifier

Mismatch

Trace Identifier Mismatch occurs when

have enabled path trace and the receiv

stringis different from the expected

string.

This alarm condition stops traffic.


17/29


18/29

payload with an AIS in the forwarding

direction.

All subsequent NEs detect TUAIS.

Note: This alarm is suppressed by defa

125tu12 Critical lop Loss Of Pointer

This alarm appears when an NE is una

interpret the TU12 pointer. This alarmnormally indicates that the NE receive

TU3s when the NE actually expects

TU12s.

126tu12 Warning switchWork

SNCP switched

to working



Switching criteria include the SNCP ty

namely, SNC/i or SNC/n. The main

difference between the two is that SNC

in addition to a switch on AIS/LOP ala

also switches on (nonintrusive)UNEQ/TIM/DEG/EXC alarms.

127tu12 Warning switchProt

SNCP switched

to protecting







also switches on (nonintrusive)


128tu3 Minor ais

Alarm

Indication

Signal

When an NE detects a defect on the TU

level or any level above TU3, the TU

payload is invalid. The NE then replac

payload with an AIS in the forwarding

direction. All subsequent NEs detect

TUAIS.

Note: This alarm is suppressed by defa

129tu3 Critical lop Loss Of Pointer

This alarm appears when an NE is una

interpret the TU3 pointer. This alarm

normally indicates that the NE receiveTU12s when the NE actually expects

TU3s.

130tu3 Warning switchWork

SNCP switched

to working










19/29

131tu3 Warning switchProt

SNCP switched

to protecting









132vc12 Major exc

BER excessive

error rate


greater than 1E5.

133vc12 Minor deg

Signal degrade

(BER low)


is greater than configured threshold.


alarm from 1E6 to 1E9. For examplset to 1E7 (default), an alarm appears





time).

134 vc12 Critical tim Trace Identifier

Mismatch

This alarm appears when path trace is

enabled and the received stringis

different from the expected string.

This alarm condition stops traffic beca

AIS is inserted downstream instead of

original signal when there is a mismatc

between expected and received Path T

Note: For an Ethernet over SDH (EoS

mapper, Path trace is a global setting f

each Group, though you can read the

received string for each individual VC


20/29

135vc12 Minor rdi

Remote Defect

Indication

This alarm indicates the presence of an

incoming alarm at the point where the

VC12 terminates at the other end. Th

alarm can be UNEQ, TIM, or SSF.

136vc12 Minor ssf

Server Signal

Failure

This alarm indicates that an alarm in th

device affects the traffic on this VC1

termination point. For example, a LOS

alarm on an STMn port at the other e

a crossconnect.

137vc12 Critical uneq Unequipped

This alarm means that the VC12 has

payload. This alarm normally indicate

of connectivity for the configured payl

For example, if you enable a 2Mbit (E

do not crossconnect the VC, this alar

appears.

138vc12 Critical plm

Payload

Mismatch

The signal label indicates what type of

payload the VC12 carries. The paylo

label mismatch (PLM) occurs if there i

detected a mismatch between an expec

and received signal label.

139vc12Nim Major exc

BER excessive

error rate


greater than 1E5 for a KLMvalue th

structured as TU12 and has a

nonintrusive monitor active.

140vc12Nim Minor deg

Signal degrade

(BER low)



a KLMvalue that is structured as TU

and has a nonintrusive monitor active








time).

141 vc12Nim Critical tim Trace Identifier

Mismatch




21/29

different from the expected stringfor a

KLMvalue that is structured as TU1


This alarm condition does not affect tr

Note: For an EoS mapper (Ethernet ov

SDH port), Path trace is a global settin

Group, though you can read the receiv

string for each individual VC.

142vc12Nim Critical uneq Unequipped

This alarm indicates that an STMn po

does not contain a VC12 for a

KLMvalue that is structured as TU1


143vc3 Major exc

BER excessive

error rate

This alarm is reported if the Bit Error R

is greater than 1E5.

144 vc3 Minor deg Signal degrade

(BER low)










22/29


time).

145vc3 Critical tim

Trace Identifier

Mismatch

This alarm appears when path trace isenabled and the received stringis








each Group, though you can read thereceived string for each individual VC

146vc3 Minor rdi

Remote Defect

Indication



VC3 terminates at the other end. The

alarm can be UNEQ, TIM, or SSF.

147vc3 Minor ssf

Server Signal

Failure



termination point. For example, a

LOSalarm on an STMn port at the o

end of a crossconnect.


This alarm indicates loss of connectivi

the configured payload. For example, i

enable a 34Mbit (E3) but do not

crossconnect the VC, this alarm occu

149 vc3 Critical plm Payload The payload label mismatch (PLM) oc


23/29

Mismatch if a mismatch is detected between expe

and received signal label.

150vc3Nim Major exc

BER excessive

error rate


greater than 1E5 for a Kvalue that is

structured as TU3 and has a nonintr

monitor active.

151vc3Nim Minor deg

Signal degrade

(BER low)

This alarm appears when the Bit Erroris greater than configured threshold fo

Kvalue that is structured as TU3 an

a nonintrusive monitor active.



set to 1E7 (default), an alarm is raised



threshold. (1E6 has a shortdetectiontime, 1E9 has longer detec

time).

152 vc3Nim Critical tim Trace Identifier

Mismatch




Kvalue that is structured as TU3 an

a nonintrusive monitor active.


Note: For an EoS mapper (Ethernet ovSDH port), Path trace is a global settin

Group, though you can read the receiv

string for each individual VC.


24/29

153vc3Nim Critical uneq Unequipped


does not contain a VC3 for a Kvalu

is structured as TU3 and has anonintrusive monitor active.

154vc4 Major exc

BER excessive

error rate


greater than 1E5.

155vc4 Minor deg

Signal degrade

(BER low)


is greater than configured threshold.








time).

156 vc4 Critical tim Trace Identifier

Mismatch










each Group, though you can read the

received string for each individual VC


25/29

157vc4 Minor rdi

Remote Defect

Indication



VC4 terminates at the other end. The

incoming alarm can be UNEQ, TIM, o

SSF.

158vc4 Critical lom

Loss Of

Multiframe

A VC4 that carries TU12s has a

multiframe indication in the H4 byte. I

multiframe indication is absent, Loss O

Multiframe occurs.

159vc4 Minor ssf

Server Signal

Failure



termination point. For example, a

LOSalarm on an STMn port at the o

end of a crossconnect.


This alarm means that the VC4 has n

payload. This alarm normally indicate

of connectivity for configured payload

161vc4 Critical plm

Payload

Mismatch

The signal label indicates what type ofpayload the VC4 carries. The payload

label mismatch (PLM) alarm appears i

case of a mismatch between expected a

received signal label.

162vc44cNim Major exc

BER excessive

error rate


greater than 1E5 for a Cvalue that is

structured as AU44C and has a


163 vc44cNim Minor deg Signal degrade(BER low)

This alarm appears when the Bit Erroris greater than configured threshold fo

Cvalue that is structured as AU44c

has a nonintrusive monitor active.








26/29


time).

164vc44cNim Critical tim

Trace Identifier

Mismatch




Cvalue that is structured as AU44chas a nonintrusive monitor active.


165vc44cNim Critical uneq Unequipped


does not contain a VC44c for a Cva

that is structured as AU44c and has a


166vc4Nim Major exc

BER excessive

error rate


greater than 1E5 for a CBvalue that

structured as AU4 and has a nonintr

monitor active.

167 vc4Nim Minor deg Signal degrade

(BER low)


is greater than configured threshold fo


27/29

CBvalue that is structured as AU4 a




set to 1E7 (default), an alarm is raised





time).

168vc4Nim Critical tim

Trace Identifier

Mismatch




CBvalue that is structured as AU4 a





each Group, though you can read thereceived string for each individual VC

169 vc4Nim Critical uneq Unequipped This alarm indicates that an STMn po

does not contain a VC4 for a CBval

that is structured as AU4 and has a


28/29


170vcat Critical lom

Vcat Loss Of

Multiframe

All Vcat VCns carry a multiframe

indication to realign all members of a

group in the sink end. If the sink end is

unable to interpret the multiframe

indication, Vcat Loss Of Multiframe

occurs.

171vcat Major sqm

Sequenceindicator

mismatch

This alarm appears when the receivedsequence (SQ) number is different from

expected sequence number. This is

applicable only in nonLCAS mode.

172vcat Major loa

Loss of align.

traffic ch

This alarm appears when excessive

differential delay between channels

prevents channel alignment.

173wan Critical wanDelay

Delay between

VC12s above

limit

This alarm appears when the differentidelay between VC12s exceed ca. 6.5

This alarm is similar to loa, but appear

only for WAN ports with proprietary

mapping.

174wan Critical seqFail

Wrong channel

seq. numbering

P2P

This alarm appears when the order of t

VCs is incorrect. This alarm is similar

sqm, but appears only for WAN ports

proprietary mapping.

175wan Major plc

Partial loss

capacity

This alarm appears when the operation

status for bandwidth for an EoS mappe

less than what is administratively set. T

alarm appears only for ports with

bidirectional capacity (proprietary

mapping).

176wan Critical tlc

Total loss

capacity

This alarm appears in the event of abse

of traffic on a port due to SDH alarms.

alarm appears only for ports with

bidirectional capacity (proprietary

mapping).

177wan Major plcr

Partial loss

capacity rx

This alarm appears when the traffic

capacity is less than provisioned in the

receive direction on this port due to SD

alarms.

178wan Critical tlcr

Total loss

capacity rx

This alarm appears when there is no tr

in the receive direction on this port due

SDH alarms.

179 wan Warning rldot1dStpPortState

Forwarding

Bridge port

learning to

forwarding state

This alarm indicates a move in the STP

state for the given port from the "Learn

state to the "Forwarding" state. The po


29/29

transition now forwards traffic.

180wan Warning

rldot1dStpPortState

NotForwarding

Bridge port

forwarding to

blocking state

transition

This alarm indicates a move in the STP

state for the given port from the

"Forwarding" state to the "Blocking" s

The port no longer forwards traffic.

Related InformationTechnical Support & Documentation Cisco Systems

Contacts & Feedback | Help | Site Map

2009 2010 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of

Cisco Systems, Inc.

Updated: Oct 05, 2005 Document ID: 64208

ons alarms events

Documents