PDF Fox515t Alarmevent 1khw001699r0001 - Compress
PDF Fox515t Alarmevent 1khw001699r0001 - Compress
PDF Fox515t Alarmevent 1khw001699r0001 - Compress
ABB
FOX from
FOX from ABB, covers
covers all your communication
commu nication re
r equirements
quirements in
i n one system.
FOX515T
Al
A l ar
armm s an
andd Ev
Even
entt s
FOX515T
A
Alar
lar ms and
an d Even
Ev entt s
Disclaimer: No part of this document may be reproduced in any form without the written permission of the copyright
owner. The contents of this document is subject to revision without notice due to continued progress in
methodology, design and manufacturing.
manufacturing. ABB shall have no liability for any error or damage of any kind
resulting from the use of this document.
AL ARMS A
AND
ND EVENTS ABB
Cleara
Clearable
ble Alarm Notifi cations
NotificationId : This is the unique identifier of a notification. Alarm notification that are clearable has id's in the range from 100 to 200.
ProbableCause::
ProbableCause A textual id of the notification. There is a 1-1 relationship between notification id and the probable cause.
Severity::
Severity The default severity for the notification for a given Managed object. The severity can be configured on the network element.
ManagedObject::
ManagedObject The managed objects that can be the source of the notification.
Al arm
armCateg
Categor
or y : Alarm category used to categories alarm notifications for different suppression.
Description:
Description: This field will contain a description of this alarm and why it has been reported.
Troubleshooting
Troubleshooting This entry is a trouble shooting guide to the operator.
AL ARMS A
AND
ND EVENTS ABB
ation
Id Qualifier
101 los Loss of signal critical PDHE3Port HIGH_ORDER_
HIGH_ORDER_ Alarm reported when there is no PDH
PDH signal received
LEVEL on the E3 port.
101 los Loss of signal critical SDHPort HIGH_ORD
HIGH_ORDER_
ER_ Alarm reported when there is no PDH
PDH signal received
LEVEL on the SDH port.
101 los Loss of signal critical AuxPort HIGH_ORDE
HIGH_ORDER_
R_ Alarm reported when there is no signal received on
LEVEL the Aux port.
101 los Loss of signal critical SyncInOutPort HIGH_ORD
HIGH_ORDER_
ER_ Alarm reported when there is no signal received on
LEVEL the Synch port.
102 ais Alarm indication signal minor AU4 LOW_ORDER_ When a network element detects a defect in the If AIS is reported for AU-4, verify
LEVEL regenerator section (RS) or the multiplexer section alarm conditions on sections
(MS) of an incoming link, the payload of that link is between intermediate nodes on the
invalid. The network element then replaces the path.
payload with an alarm indication signal in the
forwarding direction. All following network element will
then detect AU-4 AIS. Note! By default suppressed.
102 ais Alarm indication signal minor AU4_2c NONE An Alarm Indication Signal (AIS) is a signal sent
downstream as an indication that an upstream defect
has been detected.
102 ais Alarm indication signal minor AU4_4c LOW_ORDER_ When a network element detects a defect in the If AIS is reported for AU-4-4c,
LEVEL regenerator section (RS) or the multiplexer section verify alarm conditions on sections
(MS) of an incoming link, the payload of that link is between intermediate nodes on the
invalid. The network element then replaces the path.
payload with an alarm indication signal in the
forwarding direction. All following network element will
then detect AU-4-4c AIS. Note! By default
suppressed.
102 ais Alarm indication signal minor AU4_8c NONE An Alarm Indication Signal (AIS) is a signal sent
downstream as an indication that an upstream defect
has been detected.
102 ais Alarm indication signal minor AU4_16c NONE An Alarm Indication Signal (AIS) is a signal sent
downstream as an indication that an upstream defect
has been detected.
AL ARMS A
AND
ND EVENTS ABB
ation
Id Qualifier
102 ais Alarm indication signal minor TU3 LOW_ORDER_ When a NE detects a defect on the TU-3 level or any If AIS is reported for an TU-3,
LEVEL level above TU-3, the TU-3 payload is invalid. The NE verify alarm conditions on sections
then replaces the payload with an alarm indication between intermediate nodes on the
signal in the forwarding direction. All following NE’s path.
will then detect TU-AIS. Note! By default suppressed.
102 ais Alarm indication signal minor MS HIGH_ORDER_ MS-AIS is the alarm indication signal for the MS
HIGH_ORDER_ If AIS is reported in multiplexer
LEVEL section. Un-configured STM-n ports often transmit section (MS), verify alarm
MS-AIS, and a regenerator with no input signal will conditions on regenerator sections
transmit MS-AIS. on the path e.g. a radio hop. Verify
also configuration on opposing
port.
103 csf DCC termination failure minor DCC HIGH_ORD
HIGH_ORDER_
ER_ This alarm may be reported for a DCC-m (D4-D12) Verify that equal DCC settings are
LEVEL connection, which is activated but not properly obtained in both ends of the link.
terminated in the other end.
AL ARMS A
AND
ND EVENTS ABB
ation
Id Qualifier
104 deg Degraded signal defect minor VC4NIM NONE This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
than configured threshold for a KLM-value that is improved by a factor 10.Investigate
structured as TU-12 and has a non-intrusive monitor whether there are bit errors
active. The threshold for this alarm to be reported is reported for other sections in the
configurable from 1E-6 to 1E-9. E.g. if set to 1E-7 network between intermediate
(default), an alarm is raised when BER exceeds this nodes.
threshold. The detection time depends on the
threshold. (1E-6
long detection has short detection-time, 1E-9 has
time).
104 deg Degraded signal defect minor VC4_2cNIM NONE This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
than configured threshold for a KLM-value that is improved by a factor 10.Investigate
structured as TU-12 and has a non-intrusive monitor whether there are bit errors
active. The threshold for this alarm to be reported is reported for other sections in the
configurable from 1E-6 to 1E-9. E.g. if set to 1E-7 network between intermediate
(default), an alarm is raised when BER exceeds this nodes.
threshold. (1E-6
threshold. The detection time
has short depends on 1E-9
detection-time, the has
long detection time).
104 deg Degraded signal defect minor VC4_4cNIM NONE This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
than configured threshold for a KLM-value that is improved by a factor 10.Investigate
structured as TU-12 and has a non-intrusive monitor whether there are bit errors
active. The threshold for this alarm to be reported is reported for other sections in the
configurable from 1E-6 to 1E-9. E.g. if set to 1E-7 network between intermediate
(default), an alarm is raised when BER exceeds this nodes.
threshold. The detection time depends on the
threshold. (1E-6 has short detection-time, 1E-9 has
long detection time).
AL ARMS A
AND
ND EVENTS ABB
ation
Id Qualifier
104 deg Degraded signal defect minor VC4_8cNIM NONE This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
than configured threshold for a KLM-value that is improved by a factor 10.Investigate
structured as TU-12 and has a non-intrusive monitor whether there are bit errors
active. The threshold for this alarm to be reported is reported for other sections in the
configurable from 1E-6 to 1E-9. E.g. if set to 1E-7 network between intermediate
(default), an alarm is raised when BER exceeds this nodes.
threshold. The detection time depends on the
threshold. (1E-6
long detection has short detection-time, 1E-9 has
time).
104 deg Degraded signal defect minor VC4_16cNIM NONE This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
than configured threshold for a KLM-value that is improved by a factor 10.Investigate
structured as TU-12 and has a non-intrusive monitor whether there are bit errors
active. The threshold for this alarm to be reported is reported for other sections in the
configurable from 1E-6 to 1E-9. E.g. if set to 1E-7 network between intermediate
(default), an alarm is raised when BER exceeds this nodes.
threshold. (1E-6
threshold. The detection time
has short depends on 1E-9
detection-time, the has
long detection time).
104 deg Degraded signal defect minor VC3NIM NONE This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
than configured threshold for a KLM-value that is improved by a factor 10.Investigate
structured as TU-12 and has a non-intrusive monitor whether there are bit errors
active. The threshold for this alarm to be reported is reported for other sections in the
configurable from 1E-6 to 1E-9. E.g. if set to 1E-7 network between intermediate
(default),
threshold.an alarm
The is raised
detection when
time BER on
depends exceeds
the this nodes.
threshold. (1E-6 has short detection-time, 1E-9 has
long detection time).
AL ARMS A
AND
ND EVENTS ABB
ation
Id Qualifier
104 deg Degraded signal defect minor VC12NIM NONE This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
than configured threshold for a KLM-value that is improved by a factor 10.Investigate
structured as TU-12 and has a non-intrusive monitor whether there are bit errors
active. The threshold for this alarm to be reported is reported for other sections in the
configurable from 1E-6 to 1E-9. E.g. if set to 1E-7 network between intermediate
(default), an alarm is raised when BER exceeds this nodes.
threshold. The detection time depends on the
threshold. (1E-6
long detection has short detection-time, 1E-9 has
time).
AL ARMS A
AND
ND EVENTS ABB
ation
Id Qualifier
105 epj Excessive pointer major AU4 NONE Excessive Pointer justification (EPJ) alarm is raised if The alarm indicates
ustification the number of Pointer justification events (PJE's) over synchronisation problems in the
a 15minute period is greater than a configurable network. Likely cause is that the
threshold, PJEL (Pointer Justification Event Limit). devices operate with different
The PJEL is individually configurable for each AU-4 sync-sources. E.g. will
from 1 to 1024 events. 100 events per interval is the interconnected devices operating
default configuration.PJE, both positive and negative in ”free running” cause this alarm
ustifications,
24hour areBoth
interval. counted andand
current measured over interval
past 24hour a reported per AU-4
alarm is cleared object.
when the The
number
counters are available. of received pointer events is lower
lo wer
than the set threshold within a full
15 minutes interval.NOTE! This
alarm may be experienced after a
NE restart. If synchronisation is
maintained in the network, this
alarm should be cleared after less
than 30 minutes.
105 epj Excessive pointer major AU4_2c NONE Excessive Pointer justification (EPJ) alarm is raised if The alarm indicates
ustification the number of Pointer justification events (PJE's) over synchronisation problems in the
a 15minute period is greater than a configurable network. Likely cause is that the
threshold, PJEL (Pointer Justification Event Limit). devices operate with different
The PJEL is individually configurable for each AU-4- sync-sources. E.g. will
2c from 1 to 1024 events. 100 events per interval is interconnected devices operating
the default configuration. in ”free running” cause this alarm
PJE, both positive and negative justifications, are reported per AU-4-2c object. The
counted and measured over a 24hour interval. Both alarm is cleared when the number
current and past 24hour interval counters are of received pointer events is lower
lo wer
available. than the set threshold within a full
15 minutes interval. NOTE! This
alarm may be experienced after a
NE restart. If synchronisation is
maintained in the network, this
alarm should be cleared after less
than 30 minutes.
AL ARMS A
AND
ND EVENTS ABB
ation
Id Qualifier
105 epj Excessive pointer major AU4_4c NONE Excessive Pointer justification (EPJ) alarm is raised if The alarm indicates
ustification the number of Pointer justification events (PJE's) over synchronisation problems in the
a 15minute period is greater than a configurable network. Likely cause is that the
threshold, PJEL (Pointer Justification Event Limit). devices operate with different
The PJEL is individually configurable for each AU-4- sync-sources. E.g. will
4c from 1 to 1024 events. 100 events per interval is interconnected devices operating
the default configuration. PJE, both positive and in ”free running” cause this alarm
negative justifications,
over a 24hour interval. are
Bothcounted
currentand
andmeasured
past 24hour reported per AU-4-4c
alarm is cleared whenobject. The
the number
interval counters are available. of received pointer events is lower
lo wer
than the set threshold within a full
15 minutes interval. NOTE! This
alarm may be experienced after a
NE restart. If synchronisation is
maintained in the network, this
alarm should be cleared after less
than 30 minutes.
105 epj Excessive pointer major AU4_8c NONE Excessive Pointer justification (EPJ) alarm is raised if The alarm indicates
ustification the number of Pointer justification events (PJE's) over synchronisation problems in the
a 15minute period is greater than a configurable network. Likely cause is that the
threshold, PJEL (Pointer Justification Event Limit). devices operate with different
The PJEL is individually configurable for each AU-4- sync-sources. E.g. will
8c from 1 to 1024 events. 100 events per interval is interconnected devices operating
the default configuration. in ”free running” cause this alarm
PJE, both positive and negative justifications, are reported per AU-4-8c object. The
counted and measured over a 24hour interval. Both alarm is cleared when the number
current and past 24hour interval counters are of received pointer events is lower
lo wer
available. than the set threshold within a full
15 minutes interval. Note! This
alarm may be experienced after a
NE restart. If synchronisation is
maintained in the network, this
alarm should be cleared after less
than 30 minutes.
AL ARMS A
AND
ND EVENTS ABB
122 tlc Total loss of capacity major VCGroup NONE Alarm is reported when there is no traffic on this port
due to SDH alarms. Only reported for ports with
bidirectional capacity (ABB proprietary mapping.)
123 plcr Partial loss of capacity major VCGroup NONE Alarm is reported when the traffic capacity is less than Check operational-capacity, VC-n
receive provisioned in the receive direction on this port due to alarms, and configuration
SDH alarms. parameters on the opposing port.
124 tlcr Total loss of capacity major VCGroup NONE No traffic received. Check for VC-n alarms and
receive configuration parameters on the
opposing port.
AL ARMS A
AND
ND EVENTS ABB
126 tlct Total loss of capacity major VCGroup NONE No traffic sent. Check for configuration parameters
transmit at this side, cross-connect status,
and alarm status on the opposing
port.
127 ctrlOor LCAS undefined Ctrl- major VCGroup NONE Received illegal/undefined CTRL word value. Check configuration in both ends.
word for one or more
channels
128 sqm Sequence indicator major WANVC12Channel NONE Alarm is raised when received sequence (SQ) number
mismatch is different from expected sequence number. Only
possible in non-LCAS mode.
128 sqm Sequence indicator major WANVC4Channel NONE Alarm is raised when received sequence (SQ) number
mismatch is different from expected sequence number. Only
possible in non-LCAS mode.
129 sqnc Inconsistent SQ major VCGroup NONE Alarm is raised when we have one or more of the Channels must have unique
numbers following alarms eosMultiple, eosMissing, sqNonCont, sequence numbers. Check
sqOor and sqMultiple. received sequence numbers. May
indicate signalling problem at the
opposing port, or cross-connect
problems.
130 msp MSP signalling problem critical MSProtectionGroup NONE MSP signalling problem is typically reported if you Check MSP configuration.
have a mismatch in configuration. I.e. Uni-directional
one end and Bi-directional on the other end.
131 orxo Optical receiver overload minor SDH Port NONE Alarm reported on STM-4 and STM-16 when the Reduce optical Rx-level to make
received signal is too strong. (Optical Rx-level too sure traffic is not affected.
high.) The maximum allowed level depends on
module type and type of optical-receiver.
AL ARMS A
AND
ND EVENTS ABB
132 rdi Remote defect indication minor WANVC12Channel LOW_ORDER_ This alarm indicates that at the point where the VC-12
LEVEL is terminated at the other end, there is an incoming
alarm present (UNEQ, TIM, SSF).
AL ARMS A
AND
ND EVENTS ABB
133 ssf Server signal failure minor WANVC12Channel LOW_ORDER_ This alarm indicates that there is an alarm present in
LEVEL the device that affects the traffic on this VC-12
termination point. E.g. a LOS-alarm on an STM-n port
at the other end of a cross-connect.
133 ssf Server signal failure minor WANVC3Channel LOW_ORDER_ This alarm indicates that there is an alarm present in
LEVEL the device that affects the traffic on this VC-3
termination point. E.g. a LOS-alarm on an STM-n port
at the other end of a cross-connect.
133 ssf Server signal failure minor WANVC4Channel LOW_ORDER_ This alarm indicates that there is an alarm present in
LEVEL the device that affects the traffic on this VC-4
termination point. E.g. a LOS-alarm on an STM-n port
at the other end of a cross-connect.
134 tim Trace identifier mismatch critical VC4NIM LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different from the VC-4 level you should verify the
“expected string” for a DCB-value that is structured as configured string in both ends of
AU-4 and has a non-intrusive monitor active. This the VC-4 terminations. You do not
alarm condition does not affect traffic.NOTE! For a have to set the Path Trace
EoS mapper (Ethernet over SDH port), Path trace is a Identifier attributes, but it is a very
global setting per Group, though the received string useful tool for checking the
can be read for each individual VC. connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC4_2cNIM NONE Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
enabled and the “received string” is different from the VC-4-2c level you should verify the
“expected string” for a DC-value that is structured as configured string in both ends of
AU-4-2c and has a non-intrusive monitor active. This the VC-4-2c terminations. You do
alarm condition does not affect traffic. not have to set the Path Trace
Identifier attributes, but it is a very
useful tool for checking the
connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC4_4cNIM LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different from the VC-4-4c level you should verify the
“expected string” for a DC-value that is structured as configured string in both ends of
AU-4-4c and has a non-intrusive monitor active. This the VC-4-4c terminations. You do
alarm condition does not affect traffic. not have to set the Path Trace
Identifier attributes, but it is a very
useful tool for checking the
connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC4_8cNIM NONE Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
enabled and the “received string” is different from the VC-4-8c level you should verify the
“expected string” for a DC-value that is structured as configured string in both ends of
AU-4-8c and has a non-intrusive monitor active. This the VC-4-8c terminations. You do
alarm condition does not affect traffic. not have to set the Path Trace
Identifier attributes, but it is a very
useful tool for checking the
connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC4_16cNIM NONE Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
enabled and the “received string” is different from the VC-4-16c level you should verify
“expected string” for a DC-value that is structured as the configured string in both ends
AU-4-16c and has a non-intrusive monitor active. This of the VC-4-16c terminations. You
alarm condition does not affect traffic. do not have to set the Path TraceT race
Identifier attributes, but it is a very
useful tool for checking the
connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC3NIM LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different from the VC-3 level you should verify the
“expected string” for a K-value that is structured as configured string in both ends of
TU-3 and has a non-intrusive monitor active. This the VC-3 terminations. You do not
alarm condition does not affect traffic. NOTE! For a have to set the Path Trace
EoS mapper
global setting(Ethernet over
per Group, SDHthe
though port),
received stringis a Identifier
Path trace useful toolattributes, but itthe
for checking is a very
can be read for each individual VC. connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received
network. on the
If you other
enter side of
a value forthe
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC12NIM LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different from the VC-12 level you should verify the
“expected string” for a KLM-value that is structured as configured string in both ends of
TU-12 and has a non-intrusive monitor active. This the VC-12 terminations. You do not
alarm condition does not affect traffic. NOTE! For a have to set the Path Trace
EoS mapper (Ethernet over SDH port), Path trace is a Identifier attributes, but it is a very
global setting per Group, though the received string useful tool for checking the
can be read for each individual VC. connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical RS HIGH_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
HIGH_ORDER_
LEVEL enabled and the “received string” is different than the RS level you should verify the
“expected string." This alarm condition will stop traffic. configured string in both ends of
the physical connection. You do
not have to set the Path Trace
Identifier attributes, but it is a very
useful tool for checking the
connectivity of complex networks.
Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC12 LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different than the VC-12 level you should verify the
“expected string." This alarm condition will stop traffic configured string in both ends of
as AIS is inserted downstream instead of the original the VC-12 terminations.You do not
signal when there is a mismatch between expected have to set the Path Trace
and received Path Trace. NOTE! For a EoS mapper Identifier attributes, but it is a very
(Ethernet over SDH port), Path trace is a global useful tool for checking the
setting per Group, though the received string can be connectivity of complex networks.
read for each individual VC. Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC3 LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different than the VC-3 level you should verify the
“expected string." This alarm condition will stop traffic configured string in both ends of
as AIS is inserted downstream instead of the original the VC-3 terminations.You do not
signal when there is a mismatch between expected have to set the Path Trace
and received Path Trace. NOTE! For a EoS mapper Identifier attributes, but it is a very
(Ethernet over SDH port), Path trace is a global useful tool for checking the
setting per Group, though the received string can be connectivity of complex networks.
read for each individual VC. Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical VC4 LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different than the VC-4 level you should verify the
“expected string." This alarm condition will stop traffic configured string in both ends of
as AIS is inserted downstream instead of the original the VC-4 terminations. You do not
signal when there is a mismatch between expected have to set the Path Trace
and received Path Trace. NOTE! For a EoS mapper Identifier attributes, but it is a very
(Ethernet over SDH port), Path trace is a global useful tool for checking the
setting per Group, though the received string can be connectivity of complex networks.
read for each individual VC. Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network. If you enter a value for
the Path Trace Expected value and
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical WANVC3Channel LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different than the VC-3 level you should verify the
“expected string." This alarm condition will stop traffic configured string in both ends of
as AIS is inserted downstream instead of the original the VC-3 terminations.You do not
signal when there is a mismatch between expected have to set the Path Trace
and received Path Trace. NOTE! For a EoS mapper Identifier attributes, but it is a very
(Ethernet
setting perover SDH
Group, port), the
though Pathreceived
trace is string
a global
can be useful tool for
connectivity ofchecking
complex the
networks.
read for each individual VC. Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
network.
the If you enter
Path Trace a value
Expected forand
value
enable Path Trace, a TIM alarm
will be triggered if the received
value is different from the
AL ARMS A
AND
ND EVENTS ABB
134 tim Trace identifier mismatch critical WANVC4Channel LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on
LEVEL enabled and the “received string” is different than the VC-4 level you should verify the
“expected string." This alarm condition will stop traffic configured string in both ends of
as AIS is inserted downstream instead of the original the VC-4 terminations. You do not
signal when there is a mismatch between expected have to set the Path Trace
and received Path Trace. NOTE! For a EoS mapper Identifier attributes, but it is a very
(Ethernet
setting perover SDH
Group, port), the
though Pathreceived
trace is string
a global
can be useful tool for
connectivity ofchecking
complex the
networks.
read for each individual VC. Basically a Path Trace Identifier is
inserted at the beginning of a path
and extracted at the end of a path.
By setting Path Trace Transmitted
to a logical value, e.g. "BONN-3-
21" you can easily see if this value
is received on the other side of the
AL ARMS A
AND
ND EVENTS ABB
135 uneq Unequipped critical VC4_2cNIM NONE This alarm indicates that an STM-n port does not
contain a VC-44c for a C-value that is structured as
AU-42c and has a non-intrusive monitor active.
135 uneq Unequipped critical VC4_4cNIM LOW_ORDER_ This alarm indicates that an STM-n port does not
LEVEL contain a VC-44c for a C-value that is structured as
AU-44c and has a non-intrusive monitor active.
135 uneq Unequipped critical VC4_8cNIM NONE This alarm indicates that an STM-n port does not
contain a VC-44c for a C-value that is structured as
AU-48c and has a non-intrusive monitor active.
AL ARMS A
AND
ND EVENTS ABB
135 uneq Unequipped critical VC12NIM LOW_ORDER_ This alarm indicates that an STM-n port does not
LEVEL contain a VC-12 for a KLM-value that is structured as
TU-12 and has a non-intrusive monitor active.
135 uneq Unequipped critical VC12 LOW_ORDER_ This alarm means that the VC-12 has no payload.
LOW_ORDER_
LEVEL This normally indicates loss of connectivity for
configured payload. E.g. if enabling a 2Mbit (E1)
without cross-connecting the VC will raise this alarm.
135 uneq Unequipped critical VC4 LOW_ORDER_ This alarm means that the VC-4 has no payload. This Check configuration other and
LOW_ORDER_
LEVEL normally indicates loss of connectivity for configured cross-connects.
payload.
135 uneq Unequipped critical WANVC3Channel LOW_ORDER_ This alarm means that the VC-3 has no payload. This
LEVEL alarm reported indicates loss of connectivity for
configured payload.
135 uneq Unequipped critical WANVC4Channel LOW_ORDER_ This alarm means that the VC-4 has no payload. This Check configuration other and
LEVEL normally indicates loss of connectivity for configured cross-connects.
payload.
136 aisRx Alarm indication signal minor PDHE1Port LOW_ORDER_ Alarm reported on E1 in PRA mode,
mode, when the signal
on network side LEVEL received from the network contains AIS. Indicates
alarm elsewhere in the network.
137 aisTx Alarm indication signal minor PDHE1Port NONE Not used in FOX515X
on customer side
1KHW001699R0001 Alarms and Events FOX515T Page34/51
AL ARMS A
AND
ND EVENTS ABB
143 modMis Module mismatch critical Slot NONE A module mismatch alarm will be reported if the The alarm is cleared if the module
software configured module type is different from the is replaced or the expected module
one inserted. is changed, i.e., a match between
expected and installed.
144 modFail Module failure critical ConnectorModule NONE Module Failed. The following faults results in this
condition: Restart module,
module needs toifbe
persistent
replaced.the
- Unable to read module inventory
- Unable to access I2C devices on module
- Module reports power fail (CM-FE-8xRj45 only)
1KHW001699R0001 Alarms and Events FOX515T Page35/51
AL ARMS A
AND
ND EVENTS ABB
144 modFail Module failure critical AggregateModule NONE Module Failed. The following faults results in this Restart module, if persistent the
condition: module needs to be replaced.
- Unable to read module inventory
- Unable to access I2C devices
- FPGAs failure
- Unable to access Flash memory
- Unable to activate correct mode
- Other problems detected
145 fan Fan error minor FanModule NONE The fan module is working, but is reporting a minor The fan module reports a minor
error. error.
146 fanMa Major fan error major FanModule NONE The fan module is either defect or is reporting a major The fan module is either reporting
error. a major error, or it inaccessible
(I2C failure).
147 plm Payload mismatch major VC12 LOW_ORDER_
LOW_ORDER_ The signal label indicates what type of payload the Check configuration in both ends
LEVEL VC-12 is carrying. The payload label mismatch (PLM) of the path.
is reported if there is detected a mismatch between
expected and received signal label.
147 plm Payload mismatch major VC3 LOW_ORDER_ The payload label mismatch (PLM) is reported if there
LEVEL is detected a mismatch between expected and
received signal label.
147 plm Payload mismatch major VC4 LOW_ORDER_ The signal label indicates what type of payload the Check configuration in other end
LEVEL VC-4
is is carrying.
reported if thereThe payload a
is detected label mismatch
mismatch (PLM)
between and cross-connects.
expected and received signal label.
1KHW001699R0001 Alarms and Events FOX515T Page36/51
AL ARMS A
AND
ND EVENTS ABB
147 plm Payload type mismatch minor VCGroup NONE Alarm is raised when the received Trail Signal Label
(TSL) is different from the expected TSL. The
received TSL can be seen in Signal Label under each
VC-n channel. The apposing port is sending
unexpected TSL. Alarm based on detection of PTI
field value in ITU-T G.7041.
148 upm Client payload type minor VCGroup NONE Alarm is raised when the received User Payload
mismatch Identifier (UPI) is different from the expected UPI.
Frame-Mapped Ethernet is the supported UPI in this
release. Alarm based on detection of UPI field value
in ITU-T G.7041.
149 clos Loss of client signal minor VCGroup NONE GFP client loss of signal. (Not used in Edge).
150 lfd Frame delin. loss event warning VCGroup NONE Alarm is raised when the delineation process is not in
SYNC state.
151 loaNoTraf Loss of alignment for major VCGroup NONE Alarm is raised when the channel cannot be aligned, Ensure that the differential delay
channels w/wo traffic due to differential delay between channels. Ensure between the VCAT members is
lowest possible VCAT differential delay (LCAS max. less than the maximum tolerable
62 ms) delay.
152 wanDelay Delay between VC12's critical VCGroup NONE No traffic due to time delay between two or more
above limit channels too big to align
1KHW001699R0001 Alarms and Events FOX515T Page37/51
AL ARMS A
AND
ND EVENTS ABB
154 temp High temperature major Device NONE This alarm is raised when the temperature on the Check that the combination of
device is above high threshold. equipped modules in the chassis
maintains the limit for maximum
power consumption and verify that
proper ventilation is maintained in
the environment surrounding the
device.
155 tempCri Critical temperature critical Device NONE This alarm is raised when the temperature on the
device goes above critical threshold. The device will
be shut down if the temperature stays above this
threshold for more than 2 minutes.
156 modOut Module removed critical Slot NONE A module removed alarm will be reported if a module
is missing from an equipped slot.
157 arc Alarm reporting warning Device NONE The number of alarm status changes has become too In a situation where the alarm is
congestion high for the device to be able to report all alarms. reported on and before an off
alarm is reported, the current
alarm-list may be wrong. The list
may show alarms that are no
longer present, and there may be
active alarms that are not in the
list. Also, for some alarms, the
time-stamp may be wrong. In this
situation the alarm history may be
wrong. Some alarm conditions may
have been present and
disappeared again without
appearing in the alarm-lists. Also
the time-stamps may be wrong on
some alarms/events. After the
alarm is turned off the current-
alarm-list is correct again, and
every alarm and event from that
point in time will be present in the
1KHW001699R0001 Alarms and Events FOX515T Page38/51
AL ARMS A
AND
ND EVENTS ABB
158 t0HoldOver T0 in hold over mode major Device NONE The T0 holdover mode alarm is reported if none of the
T0 synchronisation candidates are available.
159 t4Squelch T4 output squelched critical Device NONE No T4 sync. candidate with QL equal to or above
QLmin
degCrc Degrade based on CRC minor VCGroup NONE Number of bad GFP frames received, based upon
calc. payload CRC calculation.
160
degtHec Degrade based on HEC minor VCGroup NONE Number of tHec corrected and uncorrected errors
161 calc.
Check DC voltage supplied to
162 pwrLow Power low critical Power NONE 48V/60V Power low reported by power port power port
Check DC voltage supplied to
163 pwrHigh Power high critical Power NONE 48V/60V Power high reported by power port power port
Check DC voltage supplied to
164 pwrOff Power off critical Power NONE 48V/60V Power off reported by power port power port
165 modDown Module down minor Slot NONE Module has been shut down.
166 ifmodMismatch Interface module critical SDHPort NONE Indicates that there is a mismatch between the
mismatch provisioned and the installed interface module
1KHW001699R0001 Alarms and Events FOX515T Page39/51
AL ARMS A
AND
ND EVENTS ABB
Network release The inserted standby aggregate module has different Upgrade standby aggregate
mismatch on AGG SW version than the active aggregate module. module from the NE Maintenance
170 nrMismatch modules major Device NONE System runs in duplex mode. GUI.
The NTP server is not The configured NTP server is not reachable from the Check NTP address settings.
171 ntpUnreachable reachable minor Device NONE network element. Check network configuration..
AL ARMS A
AND
ND EVENTS ABB
AL ARMS A
AND
ND EVENTS ABB
AL ARMS A
AND
ND EVENTS ABB
AL ARMS A
AND
ND EVENTS ABB
AL ARMS A
AND
ND EVENTS ABB
AL ARMS A
AND
ND EVENTS ABB
Non-clearable
Non-clearable Alarm Notif ication s
some
are software
cleared andproblem. All notification
alarm reporting will startlogs
from scratch.
207 cdbRestor CDB restore failed major Device NONE Non-clearable alarm reported when a CDB
eFail restore operation fails.
208 cdbBackup CDB backup failed major Device NONE Non-clearable alarm reported when a CDB
Fail backup operation fails.
209 fileTransfer File transfer failed major Device NONE Non-clearable alarm reported when a file
Fail transfer operation fails.
210 mgmtSwdl
Fail Management software
download failed major Device NONE Non-clearablesoftware
management alarm reported when
download a
operation
fails.
205 invFailure Inventory Failure minor Device NONE Not possible to read Device inventory from This can be caused by either an
EEPROM erroneous or an un-
programmed/corrupt inventory
EEPROM
205 invFailure Inventory Failure minor BackPlane NONE Not possible to read BackPlane inventory This can be caused by either an
from EEPROM erroneous or an un-
programmed/corrupt inventory
EEPROM
1KHW001699R0001 Alarms and Events FOX515T Page46/51
AL ARMS A
AND
ND EVENTS ABB
205 invFailure Inventory Failure minor FanModule NONE Not possible to read FanModule inventory This can be caused by either an
from EEPROM erroneous or an un-
programmed/corrupt inventory
EEPROM
1KHW001699R0001 Alarms and Events FOX515T Page47/51
AL ARMS A
AND
ND EVENTS ABB
213 haLogRes
et HA-log has been reset warning Device NONE Indicates that the HA-log was reset during
startup.
214 cdbErased CDB was automatically major Device NONE The module could not start due to errors in Contact technical support
erased the CDB The CDB has been automatically
erased.
215 nrAutoRoll Automatic rollback major AggregateModule NONE An automatic rollback to old network Contact technical support
back performed release has been performed due to
repetitive software error
216 nonHitless
SwitchOve Traffic interruptions may
have occurred minor Device NONE One
obtainorproper
both aggregate modules
synchronization could
lock not
within Contact technical support
r the required time period and traffic
interruptions may have occurred
1KHW001699R0001 Alarms and Events FOX515T Page48/51
AL ARMS A
AND
ND EVENTS ABB
Event
Event Notifications
NotificationId::
NotificationId This is the unique identifier of a notification. Alarm notification that are clearable has id's in the range from 100 to 200.
EventCause:
EventCause: A textual id of the notification. There is a 1-1 relationship between notification id and the event cause.
cause.
EventType::
EventType The event notification belongs to one of two types: warning or info
ManagedObject::
ManagedObject The managed objects that can be the source of the notification.
Description::
Description This field will contain a description of this event and why it has been reported.
Troubleshooting
Troubleshooting This entry is a trouble shooting guide to the operator.
NotificationId
NotificationId EventCause
EventCause EventType
EventType ManagedObject
ManagedObject Description
Description Troubleshooting
Troubleshooting
50 swdlOk information Device Successful software download
51 mspComTimeout warning MSProtectionGroup This event indicates that an MSP-command This event does not indicate any malfunction.
successfully entered at this end has timed It may occur as a consequence of the MSP-
out, due to no response from the other end. protocol in different combinations of alarm-
Only reported when bidirectional MSP is state or MSP-commands.
used.
52 mspComOverruled warning MSProtectionGroup This event indicates that an MSP-command
with a higher priority is entered at the other
end of the connection. The result is that the
MSP-command at this end is removed. Only
reported when bidirectional MSP is used.
53 loopOpended warning E1 This event is reported when a test-loop has
been cleared on an E1-port
53 loopOpended warning E3 This event is reported when a test-loop has
been cleared on an E3-port
54 loopClosed warning E1 This event is reported when a test-loop has
been set on an E1-port
54 loopClosed warning E3 This event is reported when a test-loop has
been set on an E3-port
55 ifmodInserted information SDHPort This event indicates that an SFP has been
inserted at a port.
55 ifmodInserted information LANXPort This event indicates that an SFP has been
inserted at a port.
1KHW001699R0001 Alarms and Events FOX515T Page49/51
AL ARMS A
AND
ND EVENTS ABB
NotificationId
NotificationId EventCause
EventCause EventType
EventType ManagedObject
ManagedObject Description
Description Troubleshooting
Troubleshooting
56 mcu warning ManagementPort Management Channel Up This event is related to the linkStatus of the
management port and is not an alarm
situation. Errors on the management port is
reported on the management interface object.
57 mcd warning ManagementPort Management Channel Down This event is related to the linkStatus of the
management port and is not an alarm
situation. Errors on the management port is
58 rstpNewRoot warning Switch The bridge has been assigned as the new reported on the management interface object.
root
59 rstpTopologyChange warning Switch A topology change has been detected
60 rmonRisingThreshold warning LANXPort This event indicates that an RMON
performance monitoring parameter (RMON
counter) has crossed its pre-defined rising
threshold.
60 rmonRisingThreshold warning WANXPort This event indicates that an RMON
performance
counter) monitoring
has crossed its parameter
pre-defined(RMON
rising
threshold.
61 rmonFallingThreshold warning LANXPort This event indicates that an RMON
performance monitoring parameter (RMON
counter) has crossed its pre-defined falling
threshold.
61 rmonFallingThreshold warning WANXPort This event indicates that an RMON
performance monitoring parameter (RMON
counter) has crossed its pre-defined falling
threshold.
64 cdbBackupOk information Device This event is reported when a CDB backup is
performed.
65 cdbRestoreOk information Device This event is reported when a CDB restore is
performed.
66 information information Device General informational event. Information to
be found in the additional text
1KHW001699R0001 Alarms and Events FOX515T Page50/51
AL ARMS A
AND
ND EVENTS ABB
NotificationId
NotificationId EventCause
EventCause EventType
EventType ManagedObject
ManagedObject Description
Description Troubleshooting
Troubleshooting
67 fileTransferStart information Device This event is reported when the NE begins a
file transfer. Reported for both downloads
and uploads.
68 fileTransferEnd information Device This event is reported when the NE has
performed a filetransfer.
62 pingCompleted information Device This event indicates that a ping operation
has completed, and presents its status (OK,