FOX515T AlarmEvent 1KHW001699R0001 PDF

ABB
FOX from ABB, covers all your communication requirements in one system.
FOX515T
Alarms and Events
FOX515T
Alarms and Events
Copyright: © ABB Switzerland Ltd - All rights reserved.
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. ABB shall have no liability for any error or damage of any kind
resulting from the use of this document.
Document Number: 1KHW001699R0001
ABB Switzerland Ltd

Power Systems
Bruggerstrasse 72
CH-5400 Baden
Switzerland © June 2006 by ABB Ltd
ALARMS AND EVENTS ABB
Clearable Alarm Notifications

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: A textual id of the notification. There is a 1-1 relationship between notification id and the probable cause.
ProbableCauseQualifier: A full textual description of the probable cause.
Severity: The default severity for the notification for a given Managed object. The severity can be configured on the network element.
ManagedObject: The managed objects that can be the source of the notification.
AlarmCategory: Alarm category used to categories alarm notifications for different suppression.
Description: This field will contain a description of this alarm and why it has been reported.
Troubleshooting This entry is a trouble shooting guide to the operator.
Notific Probable Cause Probable Cause Severity ManagedObject AlarmCategory Description Troubleshooting
ation Qualifier
Id
100 mid Management interface critical ManagementPortInterface NONE This alarm is reported when the Management port
down interface has lost IP connectivity.
100 mid Management interface critical ManagementDCC NONE This alarm is reported when the Management DCC
down used in IP mode has lost IP connectivity.
100 mid Management interface critical OsiTunnel NONE This alarm is reported when the OSI tunnel has lost IP
down connectivity.
100 mid Management interface critical ManagementVlan NONE This alarm is reported when the Management VLAN
down has lost IP connectivity.
100 mid Management interface critical L1CC NONE This alarm is reported when the Ethernet L1
down communication channel (L1CC) has lost IP
connectivity.
101 los Loss of signal critical PDHE1Port HIGH_ORDER_ Alarm reported when there is no PDH signal received
LEVEL on the E1 port.
1KHW001699R0001 Alarms and Events FOX515T Page3/51

ation Qualifier
Id
101 los Loss of signal critical PDHE3Port HIGH_ORDER_ Alarm reported when there is no PDH signal received
LEVEL on the E3 port.
101 los Loss of signal critical SDHPort HIGH_ORDER_ Alarm reported when there is no PDH signal received
LEVEL on the SDH port.
101 los Loss of signal critical AuxPort HIGH_ORDER_ Alarm reported when there is no signal received on
LEVEL the Aux port.
101 los Loss of signal critical SyncInOutPort HIGH_ORDER_ 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.
has been detected.
has been detected.

ation Qualifier
Id
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 TU12 LOW_ORDER_ When a NE detects a defect on the TU-12 level or any If AIS is reported for an TU-12,
LEVEL level above TU-12, the TU-12 payload is invalid. The verify alarm conditions on sections
NE 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 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_ORDER_ 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.
103 csf DCC termination failure minor MS HIGH_ORDER_ This alarm may be reported for a DCC-m (D4-D12) Verify that equal DCC settings are
103 csf DCC termination failure minor RS HIGH_ORDER_ This alarm may be reported for a DCC-r (D1-D3) Verify that equal DCC settings are

ation Qualifier
Id
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 has short detection-time, 1E-9 has
long detection 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

ation Qualifier
Id

ation Qualifier
Id
104 deg Degraded signal defect minor MS HIGH_ORDER_ This alarm is raised when the Bit Error Rate is greater Investigate whether there are bit
LEVEL than configured threshold. The threshold for this alarm errors reported for RS sections on
to be reported is configurable from 1E-6 to 1E-9. E.g. the path. E.g. a radio hop. To
if set to 1E-7 (default), an alarm is raised when BER clear, the BER level must be
exceeds this threshold. The detection time depends improved by a factor 10.
on the threshold. (1E-6 has short detection-time, 1E-9
has long detection time).
104 deg Degraded signal defect minor RS HIGH_ORDER_ This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
LEVEL than configured threshold. The threshold for this alarm improved by a factor 10.
to be reported is configurable from 1E-6 to 1E-9. E.g.
if set to 1E-7 (default), an alarm is raised when BER
exceeds this threshold. The detection time depends
on the threshold. (1E-6 has short detection-time, 1E-9
104 deg Degraded signal defect minor VC12 LOW_ORDER_ This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be
LEVEL than configured threshold. The threshold for this alarm improved by a factor 10.Investigate
to be reported is configurable from 1E-6 to 1E-9. E.g. whether there are bit errors
if set to 1E-7 (default), an alarm is raised when BER reported for other sections in the
exceeds this threshold. The detection time depends network between intermediate
on the threshold. (1E-6 has short detection-time, 1E-9 nodes.

ation Qualifier
Id
104 deg Degraded signal defect minor WANVC12Channel LOW_ORDER_ This alarm is raised when the Bit Error Rate is greater To clear, the BER level must be

ation Qualifier
Id
105 epj Excessive pointer major AU4 NONE Excessive Pointer justification (EPJ) alarm is raised if The alarm indicates
justification 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
justifications, are counted and measured over a reported per AU-4 object. The
24hour interval. Both current and past 24hour interval alarm is cleared when the number
counters are available. of received pointer events is lower
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
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
available. than the set threshold within a full
15 minutes interval. NOTE! This
than 30 minutes.

ation Qualifier
Id
the default configuration. PJE, both positive and in ”free running” cause this alarm
negative justifications, are counted and measured reported per AU-4-4c object. The
over a 24hour interval. Both current and past 24hour alarm is cleared when the number
interval counters are available. of received pointer events is lower
than the set threshold within a full
15 minutes interval. NOTE! This
than 30 minutes.
PJE, both positive and negative justifications, are reported per AU-4-8c object. The
15 minutes interval. Note! This
than 30 minutes.

ation Qualifier
Id
105 epj Excessive pointer major AU4_16c NONE Excessive Pointer justification (EPJ) alarm is raised if
The alarm indicates
justification the number of Pointer justification events (PJE's) over
synchronisation problems in 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
16c from 1 to 1024 events. 100 events per interval is
interconnected devices operating
PJE, both positive and negative justifications, arereported per AU-4-16c object. The
15 minutes interval.NOTE! This
than 30 minutes.
106 exc Excessive error defect major VC4NIM LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater Investigate whether there are bit
LEVEL than 1E-5 for a DCB-value that is structured as AU-4 errors reported for other sections in
and has a non-intrusive monitor active. the network between intermediate
nodes.
106 exc Excessive error defect major VC4_2cNIM NONE This alarm is reported if the Bit Error Rate is greater Investigate whether there are bit
than 1E-5 for a DC-value that is structured as AU- errors reported for other sections in
4_2c and has a non-intrusive monitor active. the network between intermediate
nodes.
106 exc Excessive error defect major VC4_4cNIM LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater Investigate whether there are bit
LEVEL than 1E-5 for a DC-value that is structured as AU-4- errors reported for other sections in
4C and has a non-intrusive monitor active. the network between intermediate
nodes.
than 1E-5 for a DC-value that is structured as AU- errors reported for other sections in
4_8c and has a non-intrusive monitor active. the network between intermediate
nodes.
than 1E-5 for a DC-value that is structured as AU-16 errors reported for other sections in
nodes.

ation Qualifier
Id
LEVEL than 1E-5 for a K-value that is structured as TU-3 and errors reported for other sections in
has a non-intrusive monitor active. the network between intermediate
nodes.
LEVEL than 1E-5 for a KLM-value that is structured as TU-12 errors reported for other sections in
nodes.
106 exc Excessive error defect major MS HIGH_ORDER_ This alarm is reported if the Bit Error Rate is greater Investigate whether there are bit
LEVEL than 1E-5. errors reported for RS sections on
the path. E.g. a radio hop.
106 exc Excessive error defect major RS HIGH_ORDER_ This alarm is reported if the Bit Error Rate is greater Investigate whether there are bit
LEVEL than 1E-5. errors reported for other sections in
the network between intermediate
nodes.
106 exc Excessive error defect major VC12 LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater Investigate whether there are bit
nodes.
106 exc Excessive error defect major VC3 LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater
LEVEL than 1E-5.
106 exc Excessive error defect major VC4 LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater
LEVEL than 1E-5.
106 exc Excessive error defect major WANVC12Channel LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater Investigate whether there are bit
nodes.
106 exc Excessive error defect major WANVC3Channel LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater
LEVEL than 1E-5.
106 exc Excessive error defect major WANVC4Channel LOW_ORDER_ This alarm is reported if the Bit Error Rate is greater
LEVEL than 1E-5.
107 lof Loss of frame alignment critical RS HIGH_ORDER_ The loss of frame (LOF) alarm is reported when the See OOF.
LEVEL frame sync can not be recognised and the out of
frame (OOF) alarm has been persistent for @ 3ms.

ation Qualifier
Id
107 lof Loss of frame alignment critical AuxPort HIGH_ORDER_ The loss of frame (LOF) alarm is reported when the See OOF.
107 lof Loss of frame alignment critical SyncInOutPort HIGH_ORDER_ The loss of frame (LOF) alarm is reported when the See OOF.
108 lom Loss of multiframe critical VC4 UNFILTERED A VC-4 carrying TU-12’s has a multiframe indication Check configuration in other end.
in the H4 byte. If this multiframe indication is missing,
Loss Of Multiframe is reported.
108 lom VCAT loss of multiframe critical WANVC12Channel UNFILTERED All VCAT VC-n’s carry a multiframe indication which is Check configuration in other end
used to re-align all members of a VCAT group in the and cross-connections.
sink end. If the sink end is unable to interpret the
multiframe indication, VCAT Loss Of Multiframe is
reported.
reported.
reported.
109 lop Loss of pointer critical AU4 UNFILTERED AU-4 Loss of Pointer is reported when a network Verify that connected STM-n ports
element is unable to interpret the AU-4 pointer. This maintain the same structure on
normally indicates that the NE receives concatenated both ends.
AU-4’s when un-concatenated AU-4’s are expected.
109 lop Loss of pointer critical AU4_2c NONE Loss of Pointer (LOP) is reported when a network Verify that connected STM-n ports
element is unable to interpret the AU-4-2c pointer. maintain the same structure on
This normally indicates that the NE receives un- both ends.
concatenated AU-4’s when concatenated AU-4-2c’s
are expected.

ation Qualifier
Id
109 lop Loss of pointer critical AU4_4c UNFILTERED Loss of Pointer (LOP) is reported when a network Verify that connected STM-n ports
are expected.
are expected.
are expected.
109 lop Loss of pointer critical TU3 UNFILTERED Loss of Pointer is reported when a network element is Verify that connected STM-n ports
unable to interpret the TU-3 pointer. This normally maintain the same structure on
indicates that the NE receives TU-12’s when TU-3’s both ends.
are expected.
109 lop Loss of pointer critical TU12 UNFILTERED Loss of Pointer is reported when a network element is Verify that connected STM-n ports
unable to interpret the TU-12 pointer. This normally maintain the same structure on
indicates that the NE receives TU-3’s when TU-12’s both ends.
are expected.
110 loa Loss of alignment for major VCGroup NONE Alarm is raised when the channel cannot be aligned,
channels with traffic due to differential delay between channels. Ensure
lowest possible VCAT differential delay (LCAS max.
62 ms)
111 eosMultiple LCAS two or more major VCGroup NONE Two or more received channels have End of Look for other alarms in both ends.
channels have EOS Sequence (EoS). One and only one channel shall
have EOS. See sqnc alarm.
112 eosMissing LCAS one channel has major VCGroup NONE None of the received channels have End of Sequence Look for other alarms in both ends.
EOS (EoS). One and only one channel shall have EOS.
See sqnc alarm.
113 sqNonCont LCAS missing SQ major VCGroup NONE Sequence number missing. See sqnc alarm. Configuration mismatch or other
detected in set of alarms.
channels

ation Qualifier
Id
114 sqMultiple LCAS equal SQ for two major VCGroup NONE Two or more channels have the same sequence Configuration mismatch or other
or more channels number. See sqnc alarm. alarms.
115 sqOor LCAS SQ outside of major VCGroup NONE Received sequence number outside of valid range Check configuration in other end
range (VC-4: 0-6, VC-3: 0-20, VC-12: 0-62). See sqnc and other alarms.
alarm.
116 lcasCrc LCAS CRC error major WANVC12Channel NONE The Cyclic Redundancy check failed. Check configuration in other end
detected and other alarms.
117 nonLcas Non-LCAS source major VCGroup NONE The NE in the other end is not in LCAS mode. Check configuration.
detected
118 mnd LCAS member not de- major VCGroup NONE
skewable
119 gidErr Group Id different for major VCGroup NONE Active channels within the same VCGroup receive Check configuration.
active channels different Group ID.
N/A
121 plc Partial loss of capacity major VCGroup NONE This alarm is reported when the operational status for
bandwidth for an EoS mapper is less than what is
administratively set. Only reported for ports with
bidirectional capacity (ABB proprietary mapping.)
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.

ation Qualifier
Id
125 plct Partial loss of capacity major VCGroup NONE Alarm is reported when the traffic capacity is less than Check operational capacity. Check
transmit provisioned in the transmit direction on this port due to for configuration parameters at this
SDH alarms. side, cross-connect status, and
alarm status on the opposing port.
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.
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.

ation Qualifier
Id
132 rdi Remote defect indication minor MS HIGH_ORDER_ If a RS alarm (LOS, LOF, TIM, AIS) or MS-AIS is Verify alarm conditions on
LEVEL detected on a STM-n port, MS-RDI is sent out on that regenerator sections on the path
port. e.g. a radio hop and configuration
on opposing port.
132 rdi Remote defect indication minor VC12 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).
132 rdi Remote defect indication minor WANVC12Channel LOW_ORDER_ This alarm indicates that at the point where the VC-12
133 ssf Server signal failure minor VC12 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.

ation Qualifier
Id
133 ssf Server signal failure minor WANVC12Channel LOW_ORDER_ This alarm indicates that there is an alarm present in
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

ation Qualifier
Id
will be triggered if the received
value is different from the
transmitted value.
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.

ation Qualifier
Id
transmitted value.
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

ation Qualifier
Id
transmitted value.
enabled and the “received string” is different from the VC-4-8c level you should verify the

ation Qualifier
Id
transmitted value.
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 Trace

ation Qualifier
Id
transmitted value.
“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

ation Qualifier
Id
transmitted value.
“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

ation Qualifier
Id
transmitted value.
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
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

ation Qualifier
Id
transmitted value.
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

ation Qualifier
Id
transmitted value.

ation Qualifier
Id
transmitted value.
as AIS is inserted downstream instead of the original the VC-4 terminations. You do not

ation Qualifier
Id
transmitted value.
134 tim Trace identifier mismatch critical WANVC12Channel LOW_ORDER_ Trace Identifier Mismatch is raised when path trace is When the TIM alarm is present on

ation Qualifier
Id
transmitted value.

ation Qualifier
Id
transmitted value.
as AIS is inserted downstream instead of the original the VC-4 terminations. You do not

ation Qualifier
Id
transmitted value.
135 uneq Unequipped critical VC4NIM LOW_ORDER_ This alarm indicates that an STM-n port does not
LEVEL contain a VC-4 for a CB-value that is structured as
AU-4 and has a non-intrusive monitor active.
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

ation Qualifier
Id
LEVEL contain a VC-3 for a K-value that is structured as TU-
3 and has a non-intrusive monitor active
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.
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 VC3 LOW_ORDER_ This alarm reported indicates loss of connectivity for
LEVEL configured payload. E.g. if enabling a 34Mbit (E3)
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
LEVEL normally indicates loss of connectivity for configured cross-connects.
payload.
135 uneq Unequipped critical WANVC12Channel LOW_ORDER_ This alarm means that the VC-12 has no payload.
LEVEL This normally indicates loss of connectivity for
configured 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, 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

ation Qualifier
Id
138 lofRx Loss of frame alignment major PDHE1Port HIGH_ORDER_ Alarm reported on E1 in PRA mode, when the signal
on network side LEVEL received from the network is not formatted as
expected.
139 lofTx Loss of frame alignment major PDHE1Port HIGH_ORDER_ Alarm reported on E1 in PRA mode, when the signal
on customer side LEVEL received on the PDH port is not formatted as
expected.
140 oof Out of frame major RS HIGH_ORDER_ The out of frame (OOF) alarm is reported when the Check to see if the framing format
LEVEL frame sync can not be recognised. OOF condition will configured on the port matches the
result in a loss of frame (LOF) alarm, if persistent in framing format on the line. Try the
@ 3ms. other framing format and see if the
alarm clears. Open the statistics
report (RS) for the port and look for
evidence of a bad line. Bit errors
may indicate a timing problem. If
there is evidence of a bad line,
isolate the problem by physical
looping ports with a cable in each
end of the connection.
141 linkDown Link down critical LANXPort NONE This alarm is reported when the Ethernet port is being
disconnected.
141 linkDown Link down critical WANXPort NONE
142 alarmInp Alarm condition on major AlarmInPort HIGH_ORDER_ ABB devices provide up to 16 alarm inputs (dry
alarm-in port LEVEL contact alarms) for associated equipment, e.g. power
module failure, battery condition, open cabinet door
etc. Operator can set alarm to be triggered on either
open or closed contact. The severity of the alarm
input can be individually configured.
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 Restart module, if persistent the
condition: module needs to be replaced.
- Unable to read module inventory
- Unable to access I2C devices on module
- Module reports power fail (CM-FE-8xRj45 only)

ation Qualifier
Id
144 modFail Module failure critical TributaryModule NONE Module Failed. The following faults results in this Restart module, if persistent the
- Unable to access I2C devices
- FPGAs failure
- Unable to access Flash memory
- Unable to activate correct mode
- Hot-insert of switches failed (FE modules only)
- Other problems detected
144 modFail Module failure critical AggregateModule NONE Module Failed. The following faults results in this Restart module, if persistent the
- 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_ 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 carrying. The payload label mismatch (PLM) and cross-connects.

ation Qualifier
Id
147 plm Payload mismatch major WANVC12Channel 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.
147 plm Payload mismatch major WANVC3Channel LOW_ORDER_ The signal label indicates what type of payload the
LEVEL VC-3 is carrying. The payload label mismatch (PLM)
147 plm Payload mismatch major WANVC4Channel LOW_ORDER_ The signal label indicates what type of payload the Check configuration in other end
LEVEL VC-4 is carrying. The payload label mismatch (PLM) and cross-connects.
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

ation Qualifier
Id
153 seqFail Wrong channel critical VCGroup NONE This alarm is reported when there is incorrect order of Verify order of VC's carrying
sequence numbering VC’s. This alarm is similar to sqm, but reported only Ethernet traffic between two WAN-
P2P for Wan-ports with ABB proprietary mapping. ports.
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

ation Qualifier
Id
history.
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
163 pwrHigh Power high critical Power NONE 48V/60V Power high reported by power port power port
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

ation Qualifier
Id
166 ifmodMismatch Interface module critical LANXPort NONE Indicates that there is a mismatch between the
mismatch provisioned and the installed interface module
167 ifmodRemoved Interface module critical SDHPort NONE Indicates that an equipped interface module has been
removed removed.
167 ifmodRemoved Interface module critical LANXPort NONE Indicates that an equipped interface module has been
removed removed.
168 ifmodNotProv Interface module not critical SDHPort NONE Indicates that an interface module has not been
provisioned provisioned for a port, despite the port state being In
Service
168 ifmodNotProv Interface module not critical LANXPort NONE Indicates that an interface module has not been
provisioned provisioned for a port, despite the port state being In
Service
169 ifmodNotAppr Interface module not major SDHPort NONE Indicates that the detected interface module is not Traffic might not be impacted, but
approved recognised as an approved interface module. ABB does not guaranty that the
equipment functions according to
specifications, nor performs any
support related to problems with
unapproved interface modules.
169 ifmodNotAppr Interface module not major LANXPort NONE Indicates that the detected interface module is not Traffic might not be impacted, but
approved recognised as an approved interface module. ABB does not guaranty that the
equipment functions according to
specifications, nor performs any
support related to problems with
unapproved interface modules.
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..
Files on disk should be checked

Indicates that the disk with configuration data and any unnecessary files
172 cdbDiskNearFull CDB disk over 90% full major AggregateModule NONE has less than 20 Mb free. removed.
Intercontroller
173 icccComError communication errror warning Device NONE There is no communication between the controllers.

ation Qualifier
Id
174 exm Extension header minor VCGroup NONE Alarm is raised when the received Extension Header The opposing side port is sending
mismatch Identifier (EXI) is different from the expected EXI. Null unsupported EXI.
Extension Header is the supported EXI in this release.
Alarm based on detection of EXI field value in ITU-T
G.7041
175 pfm Payload FCS Mismatch minor VCGroup NONE Alarm is raised when the received Payload FCS
Indication (PFI) is different from the expected
PFI.Alarm based on detection of PFI field value in
ITU-T G.7041.
176 tmpDiskNearFull Tmp disk is nearly full warning AggregateModule NONE Indicates that the /tmp disk is more than 80 % full.
177 varLogDiskNearFull Var disk is nearly full warning AggregateModule NONE Indicates that the /var/log disk is more than 80 % full.
If the alarm is persistent, it may
indicate a hardware error on the
module in the slot indicated by the
two digits in the probable cause of
the alarm.
The error could also be caused by
a hardware error on the module
which the alarm is reported on. If it
is intermittent it is probably caused
LOF is detected on the incoming SERDES link by a switch of synch. sources,
nternal TDM SERDES from the slot indicated by the two digits in the where the two sources deviate by
178 intTDMLinkFailSlot01 link failed from slot 01 warning AggregateModule NONE probable cause of the alarm more than 2 ppm.

the alarm.
180 intTDMLinkFailSlot03 nternal TDM SERDES warning AggregateModule NONE LOF is detected on the incoming SERDES link If the alarm is persistent, it may

ation Qualifier
Id
link failed from slot 03 from the slot indicated by the two digits in the indicate a hardware error on the
probable cause of the alarm module in the slot indicated by the
the alarm.
by a switch of synch. sources,
where the two sources deviate by
more than 2 ppm.
the alarm.
the alarm.
LOF is detected on the incoming SERDES link If the alarm is persistent, it may
nternal TDM SERDES from the slot indicated by the two digits in the indicate a hardware error on the
182 intTDMLinkFailSlot05 link failed from slot 05 warning TributaryModule NONE probable cause of the alarm module in the slot indicated by the

ation Qualifier
Id
the alarm.
more than 2 ppm.
the alarm.
the alarm.
183 intTDMLinkFailSlot06 link failed from slot 06 warning TributaryModule NONE probable cause of the alarm more than 2 ppm.
LOF is detected on the incoming SERDES link module in the slot indicated by the
nternal TDM SERDES from the slot indicated by the two digits in the two digits in the probable cause of
184 intTDMLinkFailSlot07 link failed from slot 07 warning AggregateModule NONE probable cause of the alarm the alarm.

ation Qualifier
Id
more than 2 ppm.
the alarm.
the alarm.
LOF is detected on the incoming SERDES link the alarm.
nternal TDM SERDES from the slot indicated by the two digits in the The error could also be caused by
187 intTDMLinkFailSlot10 link failed from slot 10 warning AggregateModule NONE probable cause of the alarm a hardware error on the module

ation Qualifier
Id
more than 2 ppm.

Non-clearable Alarm Notifications
Notificati Probable Probable Cause Qualifier Severity ManagedObject AlarmCategory Description Troubleshooting
on Id Cause
203 rsAckTime Lcas RS-ack timeout major VCGroup NONE Event indicating that a RS-sequence Look for other alarms in both
out Acknowledge has timed out. When a LCAS ends.
source performs a re-sequencing of it’s
VC-n channels, it expects the opposite end
to acknowledge the re-sequencing by
ending an RS-ACK.If RS-ACK is not
received within a reasonable amount of
time, a timeout is declared.
204 swdlAborte Software download aborted major Device NONE
d
206 fmRestarte Fault management server major Device NONE The fault management server has restarted
d restarted on NE due to system boot/reboot, switch over, or
some software problem. All notification logs
are cleared and alarm reporting will start
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 Management software major Device NONE Non-clearable alarm reported when a
Fail download failed management software download 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-
EEPROM

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-
EEPROM

Notificati Probable Probable Cause Qualifier Severity ManagedObject AlarmCategory Description Troubleshooting
on Id Cause
211 swdlRollba SWDL rollback failed major Device NONE The rollback to previous installed Network Download the previous Network
ckFail Release failed.Systemis still running Release (the target release for
current Network Release. the rollback.)
212 standbyS SW upgrade on standy major Device NONE Upgrade of the SW on the standby
WDLFail AGG failed aggregate module to match SW on active
aggregate maodule failed.
213 haLogRes HA-log has been reset warning Device NONE Indicates that the HA-log was reset during
et 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 Traffic interruptions may minor Device NONE One or both aggregate modules could not Contact technical support
SwitchOve have occurred obtain proper synchronization lock within
r the required time period and traffic
interruptions may have occurred

Event Notifications
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: A textual id of the notification. There is a 1-1 relationship between notification id and the event cause.
EventType: The event notification belongs to one of two types: warning or info
ManagedObject: The managed objects that can be the source of the notification.
Description: This field will contain a description of this event and why it has been reported.
Troubleshooting This entry is a trouble shooting guide to the operator.
NotificationId EventCause EventType ManagedObject Description 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.


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
reported on the management interface object.
58 rstpNewRoot warning Switch The bridge has been assigned as the new
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
counter) has crossed its pre-defined rising
threshold.
61 rmonFallingThreshold warning LANXPort This event indicates that an RMON
counter) has crossed its pre-defined falling
threshold.
61 rmonFallingThreshold warning WANXPort This event indicates that an 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


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,
timeout, host unreachable...)
63 modIns information Slot This event is reported when the inserted
module in slot goes into service
70 modOos information Slot This event is reported when the inserted
module in slot goes out of service.
71 modOosMaint information Slot This event is reported when a module goes
out of service caused by an operator initiated
action
72 moduleRestart information Slot This event is reported when the inserted
module in slot is restarted
73 moduleShutdown information Slot This event is reported when the inserted
module in slot is shut down
74 slotUnequipped information Slot This event is reported when a slot is
unequipped
75 emergencyPassword warning Device "This event indicates that the emergency
password has been used on FOXCLI to gain
system administrator access rights.
76 aggAvailable information Device The active agggregate module is ready for This event may or may not indicate that an
management commands error has occured. It will be sent when an
active aggregate module has restarted, and
when the new active module has started after
a switch-over.

FOX515T AlarmEvent 1KHW001699R0001 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FOX515T AlarmEvent 1KHW001699R0001 PDF

Uploaded by

Copyright:

Available Formats

ABB

Alarms and Events

Copyright: © ABB Switzerland Ltd - All rights reserved.

Document Number: 1KHW001699R0001

ABB Switzerland Ltd

Clearable Alarm Notifications

ProbableCauseQualifier: A full textual description of the probable cause.

Troubleshooting This entry is a trouble shooting guide to the operator.

1KHW001699R0001 Alarms and Events FOX515T Page3/51

1KHW001699R0001 Alarms and Events FOX515T Page4/51

1KHW001699R0001 Alarms and Events FOX515T Page5/51

1KHW001699R0001 Alarms and Events FOX515T Page6/51

1KHW001699R0001 Alarms and Events FOX515T Page7/51

1KHW001699R0001 Alarms and Events FOX515T Page8/51

1KHW001699R0001 Alarms and Events FOX515T Page9/51

1KHW001699R0001 Alarms and Events FOX515T Page10/51

1KHW001699R0001 Alarms and Events FOX515T Page11/51

1KHW001699R0001 Alarms and Events FOX515T Page12/51

1KHW001699R0001 Alarms and Events FOX515T Page13/51

1KHW001699R0001 Alarms and Events FOX515T Page14/51

1KHW001699R0001 Alarms and Events FOX515T Page15/51

1KHW001699R0001 Alarms and Events FOX515T Page16/51

1KHW001699R0001 Alarms and Events FOX515T Page17/51

1KHW001699R0001 Alarms and Events FOX515T Page18/51

1KHW001699R0001 Alarms and Events FOX515T Page19/51

1KHW001699R0001 Alarms and Events FOX515T Page20/51

1KHW001699R0001 Alarms and Events FOX515T Page21/51

1KHW001699R0001 Alarms and Events FOX515T Page22/51

1KHW001699R0001 Alarms and Events FOX515T Page23/51

1KHW001699R0001 Alarms and Events FOX515T Page24/51

1KHW001699R0001 Alarms and Events FOX515T Page25/51

1KHW001699R0001 Alarms and Events FOX515T Page26/51

1KHW001699R0001 Alarms and Events FOX515T Page27/51

1KHW001699R0001 Alarms and Events FOX515T Page28/51

1KHW001699R0001 Alarms and Events FOX515T Page29/51

1KHW001699R0001 Alarms and Events FOX515T Page30/51

1KHW001699R0001 Alarms and Events FOX515T Page31/51

1KHW001699R0001 Alarms and Events FOX515T Page32/51

1KHW001699R0001 Alarms and Events FOX515T Page33/51

1KHW001699R0001 Alarms and Events FOX515T Page34/51

1KHW001699R0001 Alarms and Events FOX515T Page35/51

1KHW001699R0001 Alarms and Events FOX515T Page36/51

1KHW001699R0001 Alarms and Events FOX515T Page37/51

1KHW001699R0001 Alarms and Events FOX515T Page38/51

1KHW001699R0001 Alarms and Events FOX515T Page39/51

Files on disk should be checked

1KHW001699R0001 Alarms and Events FOX515T Page40/51

If the alarm is persistent, it may

1KHW001699R0001 Alarms and Events FOX515T Page41/51

1KHW001699R0001 Alarms and Events FOX515T Page42/51

1KHW001699R0001 Alarms and Events FOX515T Page43/51

1KHW001699R0001 Alarms and Events FOX515T Page44/51

1KHW001699R0001 Alarms and Events FOX515T Page45/51

Non-clearable Alarm Notifications

1KHW001699R0001 Alarms and Events FOX515T Page46/51

1KHW001699R0001 Alarms and Events FOX515T Page47/51

1KHW001699R0001 Alarms and Events FOX515T Page48/51

NotificationId EventCause EventType ManagedObject Description Troubleshooting

1KHW001699R0001 Alarms and Events FOX515T Page49/51

NotificationId EventCause EventType ManagedObject Description Troubleshooting

1KHW001699R0001 Alarms and Events FOX515T Page50/51

NotificationId EventCause EventType ManagedObject Description Troubleshooting

1KHW001699R0001 Alarms and Events FOX515T Page51/51