Académique Documents
Professionnel Documents
Culture Documents
323-1233-543
SDH TRANSMISSION
The copyright of this document is the property of Nortel Networks. Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL: The information contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein
confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information
contained herein.
So far as Nortel Networks is aware the contents of this document are correct. However, such contents have been obtained from a
variety of sources and Nortel Networks can give no warranty or undertaking and make no representation as to their accuracy. In
particular, Nortel Networks hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of
data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein
or any third party arising out of the contents of this document.
*NORTEL NETWORKS, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks.
Publication history
April 2004
Release 4.1 Standard introduces the following features:
• General robustness improvements
• Connection restriction removal
• Port Alarm Monitoring improvements
November 2002
Release 4 Standard introduces the following features:
• Single fibre working using STM-16o long haul aggregates NTEU25DG
and NTEU25DO
• Ultra long haul STM-16o aggregate cards NTEU25GN and NTEU25GO
• STM-1o long haul tributary card NTEU10AB
• STM-4o long haul tributary card NTEU15AB
• Amplified spans on STM-16 aggregate card NTEU25DO
• Amplified spans on STM-1o and STM-4o long haul tributary cards
NTEU10AB and NTEU15AB
• Intermediate path performance monitoring (IPPM)
May 2002
Release 3.5 Preliminary introduces the following features:
• STM-1e only tributary card NTEU16AA
• Port Alarm Monitoring available on a per port basis, allows all alarms to
be masked or suppressed
• Accomodates up to eight 10/100 Mbit/s Ethernet OPTera Packet Edge
100 (OPE100) cards. Each card gas eight Ethernet ports and two WAN
(POS) ports.
• The OPE100 card provides Ethernet bridging capability to the OM4200
SDH network
March 2002
Release 3.1 Standard introduces the following features:
• Quad STM-1o tributary card, short haul 1310 nm
February 2001
Release 2 Standard introduces the following OM4200 features:
• STM-4o tributary card, short haul 1310 nm
• Multiplexer Section Protection for STM-4o tributary cards
• Aggregate and Trib to Trib connection
• Intermediate System to Intermediate System Level 2 routing
October 2000
Release 1 Standard introduces the following OM4200 features:
• STM-16o aggregate card, long haul 1539 nm and short haul 1310 nm
• STM-1o tributary card, short haul 1310 nm with two STM-1 ports
• STM-1e/140Mbit/s, single channel, tributary card
• Three channel, 34/45Mbit/s PDH electrical tributary card
• 32 channel, 2Mbit/s PDH electrical tributary cards (75 ohm and 120 ohm)
• Multiplex section protection for STM-1 tributary cards and STM-16
aggregate cards
• 1+1 protection for 34/45Mbit/s and STM-1e/140Mbit/s tributaries
• Performance monitoring to G.826
• SETS (synchronisation function) and SEMF (Shelf Controller function)
redundancy
• VC-4, VC-3 and VC-12 connections with path protection
Contents
About this document xxix
Introduction 1-1
Card LEDs 1-3
Rack alarm unit (RAU) indications on the subrack 1-3
Card alarm correlation 1-4
Traffic and BER alarms correlation 1-5
Alarm severity states 1-7
RAU categories 1-7
Port Alarm Monitoring 1-8
Instance/Unit 2-25
Impact 2-25
Consequent Action 2-25
Possible causes 2-25
Corrective actions 2-26
RS-Loopback On 2-27
Significance 2-27
Instance/Unit 2-27
Impact 2-27
Consequent Action 2-27
Possible causes 2-27
Corrective actions 2-27
Significance 2-36
Instance/Unit 2-36
Impact 2-36
Consequent Action 2-36
Possible causes 2-36
Corrective actions 2-37
Impact 2-77
Consequent Action 2-77
Possible causes 2-77
Corrective actions 2-78
Instance/Unit 2-88
Impact 2-88
Consequent Action 2-88
Possible causes 2-88
Corrective actions 2-88
Significance 2-100
Instance/Unit 2-100
Impact 2-100
Consequent Action 2-100
Possible causes 2-100
Corrective actions 2-101
Impact 2-130
Consequent Action 2-130
Possible causes 2-130
Corrective actions 2-130
PPI-Loopback On 2-132
Significance 2-132
Instance/Unit 2-132
Impact 2-132
Consequent Action 2-132
Possible causes 2-132
Corrective actions 2-132
INT-NE-HBEAT_Missing 2-162
Significance 2-162
Instance/Unit 2-162
Impact 2-162
Consequent Action 2-162
Possible causes 2-162
Corrective actions 2-162
Equip_Fail 2-180
Significance 2-180
Instance/Unit 2-180
Impact 2-180
Consequent Action 2-180
Possible causes 2-180
Corrective actions 2-180
Equip_Out 2-181
Significance 2-181
Instance/Unit 2-181
Impact 2-181
Consequent Action 2-181
Possible causes 2-181
Corrective actions 2-181
Unexpected_Equip 2-182
Significance 2-182
Instance/Unit 2-182
Impact 2-182
Consequent Action 2-182
Possible causes 2-182
Corrective actions 2-182
Cable_Error 2-183
Significance 2-183
Instance/Unit 2-183
Impact 2-183
Consequent Action 2-183
Possible causes 2-183
Corrective actions 2-183
Wrong_Equip 2-184
Significance 2-184
Instance/Unit 2-184
Impact 2-184
Consequent Action 2-184
Possible causes 2-184
Corrective actions 2-184
FOP_PAM 2-185
Significance 2-185
Instance/Unit 2-185
Impact 2-185
Consequent Action 2-185
Possible causes 2-185
Corrective actions 2-185
FOP_SCM 2-186
Significance 2-186
Instance/Unit 2-186
Impact 2-186
Consequent Action 2-186
Possible causes 2-186
Corrective actions 2-186
FOP_INV 2-187
Significance 2-187
Instance/Unit 2-187
Impact 2-187
Consequent Action 2-187
Possible causes 2-187
Corrective actions 2-187
FOP_TMOUT 2-188
Significance 2-188
Instance/Unit 2-188
Impact 2-188
Consequent Action 2-188
Possible causes 2-188
Corrective actions 2-188
NE_Config_Bp_Mismatch 2-189
Significance 2-189
Instance/Unit 2-189
Impact 2-189
Consequent Action 2-189
Possible causes 2-189
Corrective actions 2-189
NE_Cfg_Corrupt_Bank 2-190
Significance 2-190
Instance/Unit 2-190
Impact 2-190
Consequent Action 2-190
Possible causes 2-190
Corrective actions 2-190
NE_Cfg_All_Banks_Corrupt 2-191
Significance 2-191
Instance/Unit 2-191
Impact 2-191
Consequent Action 2-191
Possible causes 2-191
Corrective actions 2-191
NE_Cfg_Validation_Err 2-192
Significance 2-192
Instance/Unit 2-192
Impact 2-192
Consequent Action 2-192
Possible causes 2-192
Corrective actions 2-192
NE_Cfg_SW_Mismatch 2-193
Significance 2-193
Instance/Unit 2-193
Impact 2-193
Consequent Action 2-193
Possible causes 2-193
Corrective actions 2-193
VC-EDD 2-194
Significance 2-194
Instance/Unit 2-194
Impact 2-194
Consequent Action 2-194
Possible causes 2-194
Corrective actions 2-194
HP-SIM 2-195
Significance 2-195
Instance/Unit 2-195
Impact 2-195
Consequent Action 2-195
Possible causes 2-195
Corrective actions 2-195
INT-NE-IP_Subnet_Unknown 2-196
Significance 2-196
Instance/Unit 2-196
Impact 2-196
Consequent Action 2-196
Possible causes 2-196
Corrective actions 2-196
2-197
Amplifier alarm conditions 2-197
Corrective action 2-197
Index 3-1
Figures
Figure 1-1 RAU indicators on the Upper EOS card 1-4
Figure 1-2 Card Alarm Correlation hierarchy 1-5
Figure 1-3 Traffic and BER alarm correlation hierarchy 1-6
Figure 1-4 Hierarchy of alarm correlation for PDH traffic 1-7
Tables
Table 2-1 Possible alarm instances 2-11
Table 2-2 Optical amplifier alarms 2-197
Procedures
Procedure 2-1 Es-cmi-violation alarm clearing 2-16
Procedure 2-2 ES_TF alarm clearing 2-17
Procedure 2-3 Es_cv_qosv_15M alarm clearing 2-18
Procedure 2-4 ES-CV-QOSV-24H alarm clearing 2-19
Procedure 2-5 Rs-los alarm clearing 2-22
Procedure 2-6 Rs_lof alarm clearing 2-24
Procedure 2-7 Rs-tim alarm clearing 2-26
Procedure 2-8 Rs_qosv_15M alarm clearing 2-28
Procedure 2-9 Rs_qosv_24H alarm clearing 2-29
Procedure 2-10 MS-AIS alarm clearing 2-31
Procedure 2-11 MS-RDI alarm clearing 2-33
Procedure 2-12 MS-REI alarm clearing 2-35
Procedure 2-13 MS-EXC alarm clearing 2-37
Audience
Associated documents
The following documents are referred to in this document:
• Documentation Overview and Safety, 323-1233-090
• System Description, 323-1233-100
• Software and Hardware Description, 323-1233-101
• Installation Procedures, 323-1233-201
• Provisioning and Operations Procedures, 323-1233-310
• Network Surveillance Procedures, 323-1233-510
• Maintenance Procedures, 323-1233-547
• EC-1 User Procedures, 323-1091-402
IONNTPS@nortelnetworks.com
Nortel Networks provides a full technical support service for its customers.
The Nortel Networks Service Desk can be called at any time on the following
numbers:
As an option, you can contact technical support through the Nortel Networks
web site:
www.nortelnetworks.com
EMC/Safety conformance
This product/product family complies with the essential protection re-
quirements of the EMC Directive 89/336/EEC as amended by 92/31/
EEC, when it is properly installed and maintained and when it is used
for the purposes for which it is intended.
Declaration of Conformity
Suppliers Name & Address: Nortel Networks, of Doagh Road, Newtownabbey,
County Antrim, Northern Ireland, BT36 6XA
We hereby declare that the products identified in Section 1 comply with the standards listed in
Section 2 and fulfil our obligations under the EU Directives listed in Section 3.
Section 1 - Products Covered
Signed:
Date:
The instructions for installation, use and maintenance form part of the product compliance and
must be observed.
This declaration has been made in accordance with ISO/IEC Guide 22, General criteria for suppliers' declaration of conformity
1
1-1
Introduction 1-
Maintenance philosophy
This section describes the maintenance method for locating and clearing
alarm indications.
Procedures to locate faults use all the indications and techniques provided by
the NE and the Element Controller (EC-1) or CAT. The NE has failure
indicator lamps on the hardware and also has alarm or action log reports on
the user interface.
Alarm clearing
To locate and clear a fault in a NE continue as follows:
1. Use the EC to open the Alarm Monitor tool. View the active alarm
summaries in the EC’s span of control (see Element Controller, User
Procedures, 323-1091-402). From the active alarm list, identify the NE on
which the highest severity alarm has occurred.
2. Log in to the NE and clear the alarms one channel and one direction at a
time, starting with the highest-severity alarm. If required, send a person to
the NE site to do maintenance procedures and card replacement.
3. Refer to Chapter 2 for detailed step-by-step procedures for clearing alarms.
WARNING
Safety guidelines
Refer to safety information in Documentation Overview and
Safety, 323-1233-090.
CAUTION
Risk of traffic interruption
The Network Element is a high capacity system. Be careful
not to interrupt traffic or perform any task without a valid
reason. Where possible reroute the traffic through another
path before replacing any traffic-carrying circuit pack.
CAUTION
Risk of optical overload and damage to equipment
For STM-16 Long Haul and Short Haul aggregate cards
external loopback connections, ensure that the received
optical power does not exceed the optical overload level, by
installing a 15dB optical attenuator between the transmit
output and receive input.
When one connection is established before the other, the first connection
raises a temporary alarm. The alarm clears once the second connection is
established and carrying clean traffic.
The nature of alarms being raised depends upon the connections and card
types used during set-up.
Card LEDs
All cards have several light-emitting diodes (LEDs) on the faceplates as an
aid to fault finding. Card LED descriptions are in the Software and Hardware
Description, 323-1233-101.
Figure 1-1
RAU indicators on the Upper EOS card
FAIL
ACK ALARM
REC ATT
NPUT
Also, if a defect occurs, the multiplexer can report a low severity alarm before
a higher severity alarm. To make sure operators view only higher severity
alarm reports, the software applies a fault masking check period before
reporting the alarm.
Figure 1-2
Card Alarm Correlation hierarchy
1
Equipment Alarms Card Alarms
The operator can change the RAU category for all alarms except OS-Optical_
Power_High and PS-Power Fail. If the operator changes the RAU category
for an alarm the alarm severity also changes automatically.
Figure 1-3
Traffic and BER alarm correlation hierarchy
ES CMI
RS LOF
MS AIS
MS REI
MS EXC
AU AIS
HPOM EXC
TU AIS
LP EXC
LP-REI
Figure 1-4
Hierarchy of alarm correlation for PDH traffic
1
PPI LOS PPI UNEXP SGNL
PPI EXC
PPI LOF
PPI LOM
RAU categories
Each alarm severity (except warning) matches a rack alarm unit category:
• Prompt maintenance alarm (Critical alarm) - an alarm that requires
immediate action at all times. Generally, this alarm passes to a
maintenance/control point when the station is without an operator.
• Deferred maintenance alarm (Major alarm) - an alarm that does not
require immediate action outside normal hours. Generally, this alarm
passes to a maintenance/control point when the station is without an
operator.
• In Station maintenance alarm (Minor alarm) - an alarm that does not
require action outside normal hours.
Note: The RS-Loss of Signal (LOS) alarm can be masked using the Port
Alarm Monitoring feature. For details on this feature refer to Chapter 7 of
the Provisioning and Operations Procedures, 323-1233-310 handbook.
Multiplexer section alarms
Synchronization alarms
Miscellaneous alarms
Card alarms
Configuration alarms
LED LCD
Alarm instances
The following table details the alarm instances that are valid for each card
type in a NE.
Table 2-1
Possible alarm instances
2
Card <Slot-no> <Port> J<VC-4> <KLM>
STM-1e/140 Mbit/s 1 to 4, 11 to 14 1 - -
tributary (140 Mbit/s mode)
2 Mbit/s tributary 1 to 4, 11 to 14 1 to 32 - -
STM-1e tributary 1 to 4, 11 to 14 1 - -
UEOS 15A 1 - -
OS
OS-Optical Power High
Significance
The laser or its related control loop has failed. The optical power output has
exceeded the nominal limit by +4dB or greater (i.e. Optical Power High).
Instance/Unit
This alarm is reported against an optical port instance as
S <slot-no> - <port-no>
Impact
Critical alarm
Loss of traffic output. If far end has ALS,received traffic will also be lost.
Protection switch on protected paths.
Consequent Action
The laser is shutdown. This is a safety feature, although the laser output is still
within the standard safe range.
Note: The laser shutdown is latched, the laser will remain off until the
card is reseated or a cold restart is performed.
Resulting alarms
This alarm also provides a hardwired Metallic Alarm signal to the RAU. The
alarm does not respond to the Receive Attention button on the UEOS card.
Possible causes
Faulty STM-N optical aggregate or optical tributary card.
Corrective actions
Re-seat the indicated card.
If the alarm is still present replace the card. Refer to the Maintenance
Procedures, 323-1233-547.
OS
OS-Disabled Laser Shutdown
Significance 2
The automatic laser shutdown (ALS) function is disabled on all ports of
indicated PIU.
Instance/Unit
This alarm is reported against an optical port instance as
S <slot-no> - <port-no>
Impact
This alarm is reported against an optical port; however, the ALS function is
enabled or disabled on a card basis.
Minor alarm.
Consequent Action
Automatic laser shutdown will not operate on the indicated port.
Possible causes
The automatic laser shutdown (ALS) function has been disabled.
Corrective actions
This alarm is only cleared when ALS is enabled. ALS is enabled by removing
a plug-in link on the appropriate card. Refer to the Software and Hardware
Description, 323-1233-101 for the position of the links on the cards.
OS
OS-Laser Shutdown
Significance
This alarm is reported when the laser on the specified optical port has been
shutdown by the automatic laser shutdown (ALS) circuit.
Instance/Unit
This alarm is reported against an optical port instance, as
S <slot-no> - <port-no>
Impact
Critical alarm
Consequent Action
None.
Possible causes
Possible causes for the OS-Laser shutdown alarm are:
• RS_LOS alarm.
• Faulty STM-N optical aggregate or optical tributary.
Corrective actions
If the RS_LOS alarm is present, perform the alarm clearing procedures for
that alarm.
If the RS_LOS alarm is not present, replace the indicated STM-N optical
aggregate or optical tributary card. Refer to the Maintenance Procedures,
323-1233-547.
ES
ES-Coded mark inversion violation
Significance 2
The Es_cmi_violation alarm is reported when CMI violations exceed the
threshold in an STM-1e signal.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Critical alarm
Consequent Action
If this port is the synchronization source for the multiplexer then a
synchronization switch occurs. If the port is in the synchronization source
hierarchy list, then the port is marked not available for synchronization.
PM event
Possible causes
Possible causes for the Es_cmi_violation alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty STM-1e tributary card.
Corrective actions
Procedure 2-1
Es-cmi-violation alarm clearing
Step Action
—end—
ES
ES-Transmit Fail (TF)
Significance 2
The STM-1e tributary output signal has fallen below a pre-defined threshold.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Consequent Action
None.
Possible causes
Possible causes for the ES-TF alarm are:
• Cable fault.
• Faulty STM-1e tributary card.
Corrective actions
Procedure 2-2
ES_TF alarm clearing
Step Action
—end—
ES
ES-Code violation quality of service violation
(15 minute)
Significance
The Es_cv_qosv_15M alarm is reported to indicate that any BBE, ES, SES,
UAS active performance monitoring threshold has been broken within a 15
minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The Es_cv_qosv_15M alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty electrical tributary card.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-3
Es_cv_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs-los alarm. Identify and remove the cause of
this alarm.
2 Check for the presence of the Es_cmi_violation alarm. Identify and remove
the cause of this alarm.
3 The Es_cv_qosv_15M alarm clears after the next 15 minute monitoring
period.
—end—
ES
ES-Code violation quality of service violation
(24 hour)
2
Significance
The Es_cv_qosv_24H alarm is reported to indicate that any BBE, ES, SES,
UAS active performance monitoring threshold has been broken within a 24
hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Consequent Action
None.
Possible causes
Possible causes for the Es_cv_qosv_24H alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty electrical tributary card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period. The following procedure describes how to detect the cause of the
alarm.
Procedure 2-4
ES-CV-QOSV-24H alarm clearing
Step Action
1 Check for the presence of the Rs_los alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of the Es_cmi_violation alarm. Identify and remove
the cause of this alarm.
3 The Es_cv_qosv_24H alarm clears after the current 24 hour monitoring
period.
—end—
RS
RS-Unexpected signal
Significance
Indicates that an optical signal is present at a specified port, but the port has
not been configured for a connection.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Incorrect fibre or cable connection.
Corrective actions
Configure the STM-1 port as detailed in Provisioning and Operations
Procedures, 323-1233-310.
RS
RS-Loss of Signal (LOS)
Significance 2
The indicated card detects the loss of the received signal.
Note: The RS-Loss of Signal (LOS) alarm can be masked using the Port
Alarm Monitoring feature. For details on this feature refer to the
Provisioning & Operations (323-1233-310) handbook.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Critical alarm
Consequent Action
AIS is injected downstream.
On optical cards, the laser is shut down by the ALS circuit (if ALS is
enabled).
Resulting alarm
OS_laser_shutdown, Ms_ais alarms.
Possible causes
Possible causes for the Rs-los alarm are:
• Faulty optical fibre, cable or connectors.
• Faulty local STM-N optical aggregate, optical tributary or SDH elecrical
tributary.
• Faulty far end STM-N optical aggregate, optical tributary or SDH elecrical
tributary.
Corrective actions
Procedure 2-5
Rs-los alarm clearing
Step Action
—end—
RS
RS-Loss of Frame (LOF)
Significance 2
The frame alignment algorithm has detected loss of frame alignment.
Instance/Unit
This alarm is reeported against a port instance as
S <slot-no> - <port-no>
Impact
Critical alarm
Consequent Action
AIS is injected downstream.
PM event.
Possible causes
Possible causes for the Rs_lof alarm are:
• Faulty optical fibre or cable.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end local STM-N optical aggregate, optical tributary or SDH
electrical tributary card.
Corrective actions
Procedure 2-6
Rs_lof alarm clearing
Step Action
—end—
RS
RS-Trace Identifier Mismatch (TIM)
Significance 2
This alarm indicates that the received STM path trace string in the J0 byte of
the RS overhead does not match the expected string. The alarm is not reported
until four successive occurrences of the string mismatch.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
AIS is injected downstream
Possible causes
Possible causes for the Rs-tim alarm are:
• Incorrect fibre or cable connection setup.
• Path trace settings incorrect (i.e. receive string or far end transmit string).
• Cyclic redundancy check (CRC) settings incorrect.
• Faulty STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• If intermittent or transient events, the cause could be errors in signal.
• Faulty single fibre working span.
Corrective actions
Procedure 2-7
Rs-tim alarm clearing
Step Action
—end—
RS
RS-Loopback On
Significance 2
This alarm indicates that an internal local or remote loopback is present at the
indicated port.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor alarm.
Possible TIM.
Consequent Action
None.
Possible causes
The operator has applied a local or remote loopback at the indicated port.
Corrective actions
If required, remove the loopback as detailed in Network Surveillance
Procedures, 323-1233-510.
RS
RS-Quality of service violation (15 minute)
Significance
The Rs_qosv_15M alarm is reported to indicate that an active BBE, ES, SES
or UAS performance monitoring point threshold has been exceeded within a
15 minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Rs_qosv_15M alarm are:
• Excessive attenuation in cable or optical fibre.
• Faulty traffic card.
• RS_LOS, RS_LOF or ES_CMI alarm.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-8
Rs_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs_los or Rs_lof alarm. Identify and remove the
cause of this alarm.
2 Check for the presence of B1 bit errors. Identify and remove the cause of
these errors.
3 The Rs_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—
RS
RS-Quality of service violation (24 hour)
Significance 2
The Rs_qosv_24H alarm is reported to indicate that an active BBE, ES, SES
or UAS performance monitoring point threshold has been exceeded within a
24 hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Rs_qosv_24H alarm are:
• Excessive attenuation in cable.
• Faulty traffic card.
• RS_LOS, RS_LOF or ES_CMI alarm.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period. The following procedure describes how to detect the cause of the
alarm.
Procedure 2-9
Rs_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Rs_los or Rs_lof alarm. Identify and remove the
cause of this alarm.
2 Check for the presence of B1 bit errors. Identify and remove the cause of
these errors.
3 The Rs_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—
MS
MS-Alarm Indication Signal (AIS)
Significance
An AIS is detected in the K2 byte in the multiplex section overhead which
indicates a failure at the far multiplexer. The alarm is reported when there are
three successive occurrences of AIS.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor alarm.
Consequent Action
AIS is inserted downstream.
Resulting alarm
MS-RDI alarm is reported at the remote (source) multiplexer if RDI is “on”
for reporting (default is “off”).
Possible causes
MS-AIS alarm is generated at the source multiplexer or by a regenerator in
between.
Corrective actions
Procedure 2-10
MS-AIS alarm clearing
Step Action 2
1 Check the far multiplexer and any intermediate regenerators for the cause of
the AIS.
If the cause of the AIS is found, perform the appropriate alarm clearing
procedure.
If the cause of the alarm is not found, go to step 3.
2 If the ‘Local’ port provides the current synchronization source, a switch occurs
to an alternative source.
3 Set RS-TIM “off” then perform loopback
4 Perform a ‘Local’ loopback on the local card (see Network Surveillance
Procedures, 323-1233-510).
If the alarm is still present, remove the ‘Local’ loopback and go to step 5.
If the alarm clears, remove the ‘Local’ loopback and go to step 6.
5 Replace the local card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
6 Replace the far end card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
MS
MS-Remote Defect Indicator (RDI)
Significance
An MS Remote Defect Indicator has been detected in the K2 bytes of the MS
overhead. This indicates that the far multiplexer has detected a fault in its
incoming signal. The alarm is reported when there are five successive
occurrences of RDI and cleared when there are three successive absences of
RDI.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the MS-RDI alarm are:
• RS-LOS, RS-LOF, RS-TIM or MS-EXC at the far multiplexer resulting in
an MS-AIS.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-11
MS-RDI alarm clearing
Step Action 2
1 Check the far multiplexer for the cause of the MS-AIS alarm.
If the cause of the alarm is found, perform the appropriate alarm clearing
procedure.
If the cause of the alarm is not found, go to step 2.
2 Check local multiplexer for local receive errors.
If local receive errors are found, investigate cause of errors.
If the alarm is still present, go to step 3.
3 Replace the local card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, go to step 4.
4 Replace the far end card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
MS
MS-Remote Error Indicator (REI)
Significance
An MS Remote Error Indication (the M1 byte of the section overhead)
indicates that the bit errors received at the far end multiplexer exceed the
configured threshold.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the MS-REI alarm are:
• MS-DEG or MS-EXC alarms at the far multiplexer.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-12
MS-REI alarm clearing
Step Action 2
1 Check the far multiplexer for the cause of the MS-DEG or MS-EXC alarms.
If the cause of the alarm is found, perform the appropriate alarm clearing
procedure.
2 Check local multiplexer for local receive errors.
If local receive errors are found, investigate cause of errors.
3 Replace the local card Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
4 Replace the far end card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
MS
MS-Excessive errors (EXC)
Significance
An MS Excessive Bit Error alarm is reported when the BER of the BIP-24N
error check on a received signal exceeds the configured threshold.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Critical alarm
If this port is entered in the synchronization source priority list this alarm
causes it to be marked unavailable for synchronization.
Consequent Action
AIS is injected on the AU-4 payload of the transmitted path
(the consequent action is configurable - the default is off).
Possible causes
Possible causes for the MS-EXC alarm are:
• Faulty optical fibre, cable or connections.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-13
MS-EXC alarm clearing
Step Action 2
1 Perform a ‘Local’ loopback on the local card (see Network Surveillance
Procedures, 323-1233-510).
If the alarm is still present, remove the ‘Local’ loopback and go to step 2.
If the alarm clears, remove the ‘Local’ loopback and go to step 4.
2 Replace the local card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
3 If the far end port provides the current synchronization source, switch to an
alternative source.
4 Perform a ‘Local’ loopback on the appropriate far end card (see Network
Surveillance Procedures, 323-1233-510).
If a MS-EXC alarm is present at the far multiplexer, remove the ‘Local’
loopback and go to step 5.
If a MS-EXC alarm is not present at the far multiplexer, remove the ‘Local’
loopback and go to step 6.
5 Replace the far end card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
6 On optical cards, clean the receive optical connections at the local aggregate
or optical tributary, refer to Maintenance Procedures, 323-1233-547. Verify
that the received optical power is in the correct range.
If the received optical power is within range, go to step 7.
If the received optical power is not within range, clean the receive optical
connections at the local STM-N optical aggregate or optical tributary.
7 On optical cards, clean the transmit optical connections at the far STM-N
optical aggregate or optical tributary, refer to Maintenance Procedures,
323-1233-547. Verify that the transmit optical power at the far STM-N optical
aggregate oroptical tributary is in the correct range.
If the transmit optical power is not within range, go to step 5.
If the transmit optical power is within range, the fault is associated with the
optical fibre. Use appropriate methods to isolate and repair fibre fault.
—end—
MS
MS-Signal Degrade (DEG)
Significance
The MS Signal Degrade alarm is reported when the BER of the BIP-24N
error check exceeds the configured threshold.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Resulting alarm
Possible HP-REI or LP-REI alarms reported at an HP source.
Possible causes
Possible causes for the MS-DEG alarm are:
• Faulty optical fibre, cable or connections.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-14
MS_DEG alarm clearing
Step Action 2
1 Perform a ‘Local’ loopback on the local card (see Network Surveillance
Procedures, 323-1233-510).
If the alarm is still present, remove the ‘Local’ loopback and go to step 2.
If the alarm clears, remove the ‘Local’ loopback and go to step 3.
2 Replace the local card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
3 If the far end port provides the current synchronization source, switch to an
alternative source.
4 Set RS-TIM “off” then perform loopback
5 Perform a ‘Local’ loopback on the appropriate far end card (see Network
Surveillance Procedures, 323-1233-510).
If a MS_DEG alarm is present at the far multiplexer, remove the ‘Local’
loopback and go to step 6.
If a MS-DEG alarm is not present at the far multiplexer, remove the ‘Local’
loopback and go to step 7.
6 Replace the far end card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
7 On optical cards, clean the receive optical connections at the local aggregate
or optical tributary, refer to Maintenance Procedures, 323-1233-547. Verify
that the received optical power is in the correct range.
If the received optical power is within range, go to step 8.
If the received optical power is not within range, clean the receive optical
connections at the local STM-N optical aggregate or optical tributary.
8 On optical cards, clean the transmit optical connections at the far STM-N
optical aggregate or optical tributary, refer to Maintenance Procedures,
323-1233-547. Verify that the transmit optical power at the far STM-N optical
aggregate or optical tributary is in the correct range.
If the transmit optical power is not within range, go to step 5.
If the transmit optical power is within range, the fault is associated with the
optical fibre. Use appropriate methods to isolate and repair fibre fault.
—end—
MS
MS-Quality of service violation (15 minute)
Significance
The Ms_qosv_15M alarm is reported to indicate that an active BBE, ES, SES
or UAS performance monitoring point threshold has been exceeded within a
15 minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Ms_qosv_15M alarm are:
• Excessive attenuation in cable or optical fibre.
• Faulty traffic card.
• RS_LOS, RS_LOF, ES_CMI, MS-AIS, MS-EXC or MS-DEG alarm.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-15
Ms_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs_los, Rs_lof alarm, Ms-ais, Ms-exc, Ms-deg
or Es-cmi. Identify and remove the cause of this alarm.
2 Check for the presence of B2 bit errors. Identify and remove the cause of
these errors.
3 The Ms_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—
MS
MS-Quality of service violation (24 hour)
Significance 2
The Ms_qosv_24M alarm is reported to indicate that an active BBE, ES, SES
or UAS performance monitoring point threshold has been exceeded within a
24 hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Ms_qosv_24H alarm are:
• Excessive attenuation in cable.
• Faulty traffic card.
• RS_LOS, RS_LOF, ES_CMI, MS-AIS, MS-EXC or MS-DEG alarm.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period. The following procedure describes how to detect the cause of the
alarm.
Procedure 2-16
Ms_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Rs_los, Rs_lof alarm, Ms-ais or Ms-exc,
Ms-deg or Es-cmi. Identify and remove the cause of this alarm.
2 Check for the presence of B2 bit errors. Identify and remove the cause of
these errors.
3 The Ms_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—
MS
MS-Far end quality of service violation (15 minute)
Significance
The Ms_qosv_15M alarm is reported to indicate that an active BBE, ES, SES
or UAS performance monitoring point threshold has been exceeded within a
15 minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Consequent Action
None.
Possible causes
Possible causes for the Ms_fe_qosv_15M alarm are:
• RDI or REI received from the far multiplexer.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-17
Ms_fe_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Ms_rdi, Ms_rei alarm. Identify and remove the
cause of this alarm.
2 Check for the presence of B2 bit errors at the far mux. Identify and remove the
cause of these errors.
3 The Ms_qosv_15M alarm clears after the next 15 minute monitoring period.
—end—
MS
MS-Far end quality of service violation (24 hour)
Significance 2
The Ms_fe_qosv_24H alarm is reported to indicate that any BBE, ES, SES,
UAS active performance monitoring threshold has been broken within a 24
hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Consequent Action
None.
Possible causes
Possible causes for the Ms_fe_qosv_24H alarm are:
• MS-RDI or MS-REI received from the far multiplexer.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period. The following procedure describes how to detect the cause of the
alarm.
Procedure 2-18
Ms_fe_qosv_24H alarm clearing
Step Action
1 Check for the presence of the Ms_rdi, Ms_rei alarm. Identify and remove the
cause of this alarm.
2 Check for the presence of B2 bit errors at the far mux. Identify and remove the
cause of these errors.
3 The Ms_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—
AU
AU-Alarm Indication Signal (AIS)
Significance
An AIS has been detected in the H1 and H2 bytes indicating a failure in the
upstream path.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Minor alarm.
Consequent Action
AIS is injected downstream.
Possible causes
Possible causes for the AU-AIS alarm are:
• Upstream alarms which inject AIS.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-19
AU-AIS alarm clearing
Step Action 2
1 If the indicated port provides the current synchronization source, switch to an
alternative synchronization source.
2 Check the remote multiplexer and any intermediate regenerators for the
cause of AIS.
If the cause of AIS found, perform the appropriate alarm clearing procedure.
If the cause of AIS not found, go to step 3.
3 Perform a ‘Local’ loopback on the card (see Network Surveillance
Procedures, 323-1233-510).
Note: This loops back the STM-N data.
If the alarm is still present remove the ‘Local’ loopback and go to step 4.
If the alarm clears, the fault is at the far multiplexer. Remove the ‘Local’
loopback and go to step 5.
4 Replace the indicated card. Refer to Maintenance Procedures,
323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
5 Replace the far end card. Refer to Maintenance Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
AU
AU-Loss of Pointer (LOP)
Significance
The pointer value in the H1 and H2 bytes is invalid for three consecutive
frames.
Instance/Unit
This alarm is reported against a high order path instance, reported as
S <slot-no> - <port-no> - J<AU-4>
Impact
Critical alarm.
Consequent Action
AIS is injected downstream.
Procedure 2-20
AU-LOP alarm clearing
Step Action
—end—
HP
HP-Excessive errors (EXC)
Significance 2
When a VC-4 signal is created, a BIP-8 parity checksum is generated and
transmitted with the signal in the B3 byte. The B3 byte is examined and the
Bit error rate (BER) calculated when the VC-4 signal is received and
terminated.
When the BER value exceeds the operator configured threshold, the HP-EXC
alarm is reported.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Critical alarm.
Consequent Action
AIS is injected downstream.
PM event.
Resulting alarms
RDI is transmitted in the return path (if the consequent action is on).
Possible causes
Possible causes for the HP-EXC alarm are:
• Possible line errors.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-21
HP-EXC alarm clearing
Step Action
—end—
HP
HP-Signal Degrade (DEG)
Significance 2
Signal degrade is an intermediate alarm which informs the operator that
signal quality has declined. The B3 byte is examined and the Bit error rate
(BER) calculated when the VC-4 signal is received and terminated. When the
BER value exceeds the operator configured threshold, the HP-DEG alarm is
reported.
Instance/Unit
This alarm is reported against a high order path instance, reported as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
None
Possible causes
Possible causes for the HP-DEG alarm are:
• Possible line errors.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-22
HP-DEG alarm clearing
Step Action
—end—
HP
HP-Trace Identifier Mismatch (TIM)
Significance 2
The VC-4 path trace feature allows the operator to specify a trace identifier at
the start of the SDH path and an expected identifier at the end of the SDH
path. In the event the expected trace identifier not matching the transmitted
identifier, the HP-TIM alarm is reported.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
AIS is injected downstream.
PM event.
Possible causes
Possible causes for the HP-TIM alarm are:
• Incorrect connection.
• Path trace settings incorrect (i.e. expected receive string or far end transmit
string).
• If intermittent or transient events, the cause could be errors in signal.
Corrective actions
Procedure 2-23
HP-TIM alarm clearing
Step Action
—end—
HP
HP-Remote Defect Indicator (RDI)
Significance 2
The VC-4 path remote defect indication (RDI) bit in the VC-4 path status byte
(G1) is set. This indicates that the far end multiplexer has detected a fault in
the incoming VC-4.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the HP-RDI alarm are:
• AU_AIS, AU_LOP, HP_LOM, HP_EXC, HP_TIM, HP_PLM or
HP_UNEQ alarm at far multiplexer.
• Faulty far end or near end aggregate, Quad STM-1o, STM-1o, STM-4o
tributary or SDH electrical tributary card.
Corrective actions
Procedure 2-24
HP-RDI alarm clearing
Step Action
—end—
HP
HP-Loss of Multiframe (LOM)
Significance 2
When the VC-4 contains multiframe TU-12 payloads. The H4 byte indicates
that the frame within the multiframe carried is the current VC-4. Loss of
multiframe alignment is indicated if three consecutive out of sequence H4
bytes are received. Alignment is regained if two consecutive in sequence H4
bytes are received.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
AIS is injected downstream.
Possible causes
Possible causes for the HP_LOM alarm are:
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-25
HP-LOM alarm clearing
Step Action
—end—
HP
HP-Remote Error Indicator (REI)
Significance 2
The BER derived from the remote error indication (REI) bits in the VC-4 path
status byte (G1) exceeds the configured threshold. This indicates that the far
end multiplexer has detected bit errors in the VC-4 path.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the HP-REI alarm are:
• Bit errors on transmission path from the NE.
• Faulty remote STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-26
HP-REI alarm clearing
Step Action
—end—
HP
HP-Payload Label Mismatch (PLM)
Significance 2
The value of the VC-4 signal label code in the C2 byte does not correspond
with the expected value.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
AIS is injected downstream.
PM event.
Possible causes
Possible causes for the HP-PLM alarm are:
• Incorrect connection setup.
• Settings incorrectly set during configuration (i.e. expected receive string or
far end transmit string).
• If intermittent or transient events, errors in the signal.
Corrective actions
Procedure 2-27
HP-PLM alarm clearing
Step Action
—end—
HP
HP-Unequipped (UNEQ)
Significance 2
The value of the VC-4 path signal label code in the C2 byte indicates
unequipped (when unequipped was not the expected C2 byte. This alarm is
reported when five successive string mismatches occur.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
AIS is injected downstream.
PM event.
Possible causes
Possible causes for the HP-UNEQ alarm are:
• Incorrect connection setup.
• Signal label incorrect (i.e. receive string or far end transmit string).
Corrective actions
Procedure 2-28
HP-UNEQ alarm clearing
Step Action
—end—
HP
HP-Signal Fail (SF)
Significance 2
The HP Signal Fail alarm is reported if both paths of a VC-4 protected
connection fail.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Critical alarm.
Traffic is affected.
Consequent Action
None.
Possible causes
Possible causes for the HP-SF alarm are:
• Incorrect connections.
• Faulty far end card.
• Any permutation of HPOM-TIM, HPOM-EXC, HPOM-UNEQ,
HPOM-PLM or AU-AIS on both paths.
Corrective actions
Procedure 2-29
HP-SF alarm clearing
Step Action
—end—
HP
INT-HP-Input Buffer Overflow
Significance 2
The INT-HP-IP-BUFFER is reported if the input buffer for the high order
(VC-4) PDH mapper overflows.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm
Consequent Action
The VC-4 payload of the ongoing path is filled with ‘all ones’
Possible causes
Possible causes for the INT-HP-IP-BUFFER alarm are:
• Incoming 140 Mbit/s signal bit-rate out-of-limits.
• Faulty 140 Mbit/s tributary card.
• Synchronization problem in the network (e.g. timing loop).
Corrective actions
Procedure 2-30
INT-HP-IP-BUFFER alarm clearing
Step Action
—end—
HP
INT HP-Output Buffer Overflow
Significance 2
The INT-HP-OP-BUFFER is reported if the output buffer for the 140M bit/s
desynchronizer overflows.
Instance/Unit
This alarm is reported against a high order port instance as
S <slot-no> - <port-no> - J<AU-4>.
Impact
Major alarm
Consequent Action
The ongoing payload is filled with ‘all ones’.
Possible causes
Possible causes for the INT-HP-OP-BUFFER alarm are:
• Transient changes in the payload bit rate.
• Faulty 140 Mbit/s tributary card.
• Synchronization problem in the network (e.g. timing loop).
Corrective actions
Procedure 2-31
INT-HP-OP-BUFFER alarm clearing
Step Action
—end—
HP
HP-Quality of service violation (15 minute)
Significance
The Hp_qosv_15M alarm is reported to indicate that an active BBE, ES, SES
2
or UAS performanance monitoring threshold has been exceeded within a 15
minute monitoring period.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
For details of valid arguments see Table 2-1 on page 2-11
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Hp_qosv_15M alarm are:
• Excessive attenuation in cable or optical fibre.
• RS_LOS, RS_LOF, ES_CMI, MS_AIS, MS_EXC, MS_DEG,
INT_AU_AIS, INT_AU_LOP, HP_LOM, HP_TIM, HP_PLM or
HP_EXC alarm.
• Faulty traffic card.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-32
Hp_qosv_15M alarm clearing
Step Action
—end—
HP
HP-Quality of service violation (24 hour)
Significance
The Hp_qosv_24H alarm is reported to indicate that any BBE, ES, SES or
UAS performanance monitoring point threshold has been exceeded within a
24 hour monitoring period.
Instance/Unit
This alarm is reported against a high order path instanced as
S <slot-no> - <port-no> - J<AU-4>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Hp_qosv_24H alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty traffic card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period. The following procedure describes how to detect the cause of the
alarm.
Procedure 2-33
Hp_qosv_24H alarm clearing
Step Action
—end—
HP
HP-Far end quality of service violation (15 minute)
Significance 2
The Hp_fe_qosv_15M alarm is reported to indicate that any BBE, ES, SES or
UAS performanance monitoring point threshold has been exceeded within a
15 minute monitoring period.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Possible causes
Possible causes for the Hp_fe_qosv_15M alarm are:
• HP-RDI or HP-REI alarm from the far multiplexer.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-34
Hp_fe_qosv_15M alarm clearing
Step Action
1 Check for the presence of the Rs_los, Rs_lof alarm, Ms-ais or Ms-exc,
Ms-deg or Es-cmi. Identify and remove the cause of this alarm.
2 Check for the presence of B2 bit errors. Identify and remove the cause of
these errors.
3 The Ms_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—
HP
HP-Far end quality of service violation (24 hour)
Significance
The HP_fe_qosv_24H alarm is reported to indicate that any BBE, ES, SES,
UAS active performanance monitoring threshold has been broken within a 24
hour monitoring period.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Step Action
1 Check for the presence of the HP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of errored blocks from HP-REI. Identify and remove
the cause of these errors.
3 The Hp_fe_qosv_24H alarm clears after the current 24 hour monitoring
period.
—end—
HPOM
HPOM quality of service violation
(15 minute)
2
Significance
The HPOM_QOSV_15M alarm is reported to indicate that any BBE, ES,
SES, UAS active performance monitoring threshold has been broken within a
15 minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The HPOM_QOSV_15M alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty tributary card.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-36
HPOM_QOSV_15M alarm clearing
Step Action
1 Check for the presence of the RS-LOS alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of the HPOM_Violation alarm. Identify and remove
the cause of this alarm.
3 The HPOM_QOSV_15M alarm clears after the next 15 minute monitoring
period.
—end—
HPOM
HPOM quality of service violation
(24 hour)
Significance
The HPOM_QOSV_24H alarm is reported to indicate that any BBE, ES,
SES, UAS active performance monitoring threshold has been broken within a
24 hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The HPOM_QOSV_24H alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty tributary card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-37
HPOM_QOSV_24H alarm clearing
Step Action
1 Check for the presence of the RS-LOS alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of the HPOM_Violation alarm. Identify and remove
the cause of this alarm.
3 The HPOM_QOSV_24H alarm clears after the next 24 hour monitoring
period.
—end—
HPOM
HPOM-far end quality of service violation (15 minute)
Significance 2
The HPOM-FE_QOSV_15M alarm is reported to indicate that any BBE, ES,
SES, UAS active performance monitoring threshold has been broken within a
15 minute monitoring period.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Step Action
1 Check for the presence of the HP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of errored blocks from HP-REI. Identify and remove
the cause of these errors.
3 The HPOM-FE_QOSV_15M alarm clears after the current 15 minute
monitoring period.
—end—
HPOM
HPOM-far end quality of service violation
(24 hour)
Significance
The HPOM_FE_QOSV_24H alarm is reported to indicate that any BBE, ES,
SES, UAS active performance monitoring threshold has been broken within a
24 hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The HPOM_FE_QOSV_24H alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty tributary card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-39
HPOM_FE_QOSV_24H alarm clearing
Step Action
1 Check for the presence of the RS-LOS alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of the HPOM_FE_Violation alarm. Identify and
remove the cause of this alarm.
3 The HPOM_FE_QOSV_24H alarm clears after the next 24 hour monitoring
period.
—end—
HPOM
HPOM-Excessive errors (EXC)
Significance 2
When a VC-4 signal is created, a BIP-8 parity checksum is generated and
transmitted with the signal in the B3 byte. When he BER value exceeds the
operator configured threshold, the HPOM-EXC alarm is reported.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Critical alarm.
Consequent Action
Protection switch on protected paths.
Possible causes
Possible causes for the HPOM-EXC alarm are:
• Possible line errors.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-40
HPOM-EXC alarm clearing
Step Action
—end—
HPOM
HPOM-Trace Identifier Mismatch (TIM)
Significance 2
The VC-4 path trace feature allows the operator to specify a trace identifier at
the transmitting multiplexer and an expected identifier at the terminating
multiplexer. In the event of the expected trace identifier not matching the
transmitted identifier, the HP-TIM alarm is reported.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
Protection switch on protected paths.
Possible causes
Possible causes for the HPOM-TIM alarm are:
• Incorrect connection setup.
• Path trace settings incorrect (i.e. receive string or far end transmit string).
• If intermittent or transient events, the cause could be errors in signal.
Corrective actions
Procedure 2-41
HPOM-TIM alarm clearing
Step Action
—end—
HPOM
HPOM-Payload Label Mismatch (PLM)
Significance 2
The value of the VC-4 signal label code in the C2 byte does not correspond
with the expected value.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
Protection switch, if configured “on”.
Possible causes
Possible causes for the HPOM-PLM alarm are:
• Incorrect connection setup.
• Settings incorrectly set during configuration (i.e. receive string or far end
transmit string).
• If intermittent or transient events, errors in the signal.
Corrective actions
Procedure 2-42
HPOM-PLM alarm clearing
Step Action
—end—
HPOM
HPOM-Unequipped (UNEQ)
Significance 2
The value of the VC-4 path signal label code in the C2 byte indicates
unequipped (when unequipped was not the expected C2 byte. This alarm is
reported when five successive string mismatches occur.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Impact
Major alarm.
Consequent Action
Protection switch, if configured “on”.
Possible causes
Possible causes for the HPOM-UNEQ alarm are:
• Incorrect connection setup.
• Signal label incorrect (i.e. receive string or far end transmit string).
Corrective actions
Procedure 2-43
HPOM-UNEQ alarm clearing
Step Action
—end—
TU
Instance/Unit
This alarm is reported against a low order path instance as
S <slot-no> - <port-no> - J<AU-4> - K<klm>
Impact
Minor alarm
Consequent Action
AIS is injected downstream.
Possible causes
AIS being generated by another multiplexer on the network.
Corrective actions
Procedure 2-44
TU-AIS alarm clearing
Step Action
1 Investigate network (LP path source and intermediate locations) for cause of
AIS (e.g., alarms that cause pass-through TU-AIS injection).
If the cause of AIS is found, perform the appropriate alarm clearing
procedures.
If cause of alarm not found, escalate problem.
—end—
TU
TU-Loss of Pointer (LOP)
Significance
The pointer value has been invalid for three consecutive frames.
Instance/Unit
This alarm is reported against a low order path instance as
S <slot-no> - <port-no> - J<VC-4> - K<klm>
Impact
Critical alarm
Consequent Action
AIS is injected downstream.
Possible causes
Faulty aggregate or tributary card.
Corrective actions
Procedure 2-45
TU-LOP alarm clearing
Step Action
1 Check that the correct network settings have been made. Refer to
Provisioning and Operations Procedures, 323-1233-310.
If network connection settings are incorrect, correct as necessary.
If network connection settings are correct, go to step 2.
2 At the far multiplexer, replace the appropriate card. Refer to Maintenance
Procedures, 323-1233-547.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
TU
INT-TU-Alarm Indication Signal (AIS)
Significance 2
INT-TU-AIS is reported where the AIS has been detected in the pointer bytes
of the TU overhead. This alarm is monitored later in the demultiplexer path
than the observation of TU-AIS, therefore an occurrence of INT-TU-AIS in
the absence of TU-AIS indicates an internal problem in the NE.
Instance/Unit
This alarm is reported against a PDH port instance as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
AIS is injected downstream to the PDH port output.
Possible causes
Faulty upstream traffic source.
Faulty tributary.
Corrective actions
Procedure 2-46
INT-TU-AIS alarm clearing
Step Action
1 If INT_TU_AIS and TU-AIS are both present, Investigate network (LP path
source and intermediate locations) for cause of AIS (e.g., alarms that cause
pass-through TU-AIS injection).
If the cause of AIS is found, perform the appropriate alarm clearing
procedures.
2 If INT_TU_AIS is present and TU-AIS is not present, replace the aggregate
or tributary Unit. Refer to Maintenance Procedures, 323-1233-547.
If cause of alarm not found, escalate problem.
—end—
TU
INT-TU-Loss of Pointer (LOP)
Significance
INT-TU-LOP is reported where the pointer value in the pointer bytes of the
TU overhead are invalid for three consecutive frames. This alarm is
monitored later in the demultiplexer path than the observation of TU-LOP,
therefore an occurrence of INT-TU-LOP in the absence of TU-LOP indicates
an internal problem in the NE.
Instance/Unit
This alarm is reported against a PDH port instance, reported as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
AIS is injected downstream to the PDH port output.
Possible causes
Faulty upstream traffic source.
Faulty tributary.
Corrective actions
Procedure 2-47
INT-TU-LOP alarm clearing
Step Action
1 If INT_TU_LOP and TU-LOP are both present, Investigate network (LP path
source and intermediate locations) for cause of AIS (e.g., alarms that cause
pass-through TU-AIS injection).
If the cause of AIS is found, perform the appropriate alarm clearing
procedures.
2 If INT_TU_LOP is present and TU-LOP is not present, replace the aggregate
or tributary Unit. Refer to Maintenance Procedures, 323-1233-547.
If cause of alarm not found, escalate problem.
—end—
LP
LP-Excessive errors (EXC)
Significance 2
The BER of the VC-12 path status byte (V5) has exceeded the configured
threshold. This alarm is observed at the termination of the Low order
container.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Critical alarm
Consequent Action
AIS is injected.
Possible causes
Possible causes for the LP-EXC alarm are:
• Line errors.
• Faulty 2 Mbit/s tributary or 34/45 M/bit/s tributary.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-48
LP-EXC alarm clearing
Step Action
1 Check upstream for Lpom alarms (it may be necessary to set reporting to
“monitor”. If Lpom alarms present, fault lies upstream. If no Lpom alarms are
present, fault is local.
2 Check network for possible bit errors.
3 Replace the indicated 2 Mbit/s tributary card. Refer Maintenance Procedures,
323-1233-547.
4 Restore to the old configuration.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
LP
LP-Signal Degrade (DEG)
Significance 2
The LP-DEG alarm is reported when the BER of the VC-12 path status byte
(V5) has exceeded the configured threshold.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the LP-DEG alarm are:
• Errors on network (Traffic source containing errors).
• Faulty tributary.
• Faulty backplane interface.
Corrective actions
Procedure 2-49
LP-DEG alarm clearing
Step Action
—end—
LP
LP-Payload Label Mismatch (PLM)
Significance 2
The value of the VC-3/VC-12 signal label does not correspond with the
expected value. This alarm is reported at a path termination point, subsequent
to a protection switch.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
If configured on:
• AIS is injected downstream.
• RDI is injected upstream.
• PM event.
Possible causes
Possible causes for the LP-PLM alarm are:
• Incorrect overhead configuration at near or far end.
• Incorrect path connection.
• Faulty tributary.
Corrective actions
Procedure 2-50
LP-PLM alarm clearing
Step Action
1 Ensure that the system path configuration at both ends is correct as follows:
- if no traffic expected, both ends should be configured to send a
value of ‘0’.
- if traffic is expected, both ends should be configured to send a
value of ‘1’ or ‘2’.
Refer to Provisioning and Operations Procedures, 323-1233-310 for the
procedure to view and change connections.
If the connections are incorrect, reconfigure as necessary.
If the settings are correct, go to step 2.
2 Verify that the path is correctly connected at all intermediate multiplexers and
that no LP errors are present on the network.
If the path is incorrectly connected and/or LP errors are present, re-connect
as necessary and/or investigate network errors.
If the path is correctly connected and there are no LP errors in the network,
go to step 3.
3 Replace the local 2 Mbit/s tributary card. Refer to the Equipment
Maintenance Procedures, 323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 4.
4 Replace the far 2 Mbit/s card. Refer to the Equipment Maintenance
Procedures, 323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LP
LP-Remote Defect Indicator (RDI)
Significance 2
The RDI bit (bit 8 in the V5 byte) is set. This indicates that the far end
multiplexer has detected a fault in the incoming VC-12.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the LP-RDI alarm are:
• If alarm reported for all tributaries, RS-LOS, RS-LOF, MS-AIS, MS-EXC,
AU-AIS, INT-AU-AIS, INT-AU-LOP, HP-TIM, HP-PLM or HP-LOM
alarm at the far multiplexer.
• If alarm reported for one tributary only, TU-AIS, TU-LOP, INT-TU-AIS,
INT-TU-LOP, LP-PLM, LP-EXC, LP-UNEQ or LP-TIM alarm present at
far path termination.
Corrective actions
Procedure 2-51
LP-RDI alarm clearing
Step Action
1 Investigate far multiplexer/path termination for cause of alarm and carry out
fault finding procedures for appropriate alarm.
If cause of alarm found, perform the appropriate alarm clearing procedure.
If cause of alarm not found, go to step 2.
2 Verify that no LP errors are present on the network.
If there are no LP errors in the network, go to step 3.
3 Replace the local tributary card. Refer to the Equipment Maintenance
Procedures, 323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 4.
4 Replace the far end tributary card. Refer to the Equipment Maintenance
Procedures, 323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LP
LP-Remote Error Indication (REI)
Significance 2
The REI bit (bit 3 in the V5 byte) is set. This indicates that the far end
multiplexer has detected bit errors in the VC-12. The BER calculated from an
accumulation of the values in REI is above the configured threshold
indicating that the far end has had bit errors in its received signal.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Procedure 2-52
LP-REI alarm clearing
Step Action
1 Investigate far path termination for cause of errors and carry out fault finding
procedures for appropriate alarm (e.g. LP-DEG alarm).
If cause of alarm found, perform the appropriate alarm clearing procedure.
If cause of alarm not found, go to step 2.
2 Replace the local tributary card. Refer to the Equipment Maintenance
Procedures, 323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 3.
3 Replace the far end tributary card. Refer to the Equipment Maintenance
Procedures, 323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LP
INT-LP-Input Buffer Overflow
Significance
The INT-LP-IP-BUFFER is reported if the input buffer for the low order
(VC-12, VC-3) PDH mapper overflows.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
AIS is injected downstream.
Possible causes
Possible causes for the INT-LP-IP-BUFFER alarm are:
• Incoming signal bit-rate out-of-limits.
• Faulty tributary card.
• Synchronization problem in the network (e.g. timing loop).
Corrective actions
Procedure 2-53
INT-LP-IP-BUFFER alarm clearing
Step Action 2
1 Check for timing loops in the synchronization for the network.
a. Check that synchronization is set up according to the network
synchronization plan.
b. Check if a synchronization source switch has caused a timing loop.
If the alarm is still present go to step 3.
2 Check if the INT-LP-IP_Buffer alarm is present on more than one 2 Mbit/s
tributary port.
If the INT-LP-IP_Buffer alarm is only present on one tributary port, go to
step 3.
If the INT-LP-IP_Buffer alarm is present on all the tributary ports on more than
one 2 Mbit/s cards, go to step 3.
If the INT-LP-IP_Buffer alarm is present on more than one tributary port on a
single 2 Mbit/s card, go to step 4
3 Check if the tributary input signal is within limits.
If the tributary input signal is not within limits, investigate preceding 2 Mbit/s
equipment.
If the tributary signal is within limits, go to step 4.
4 Replace the indicated 2 Mbit/s tributary card. Refer to the Maintenance
Procedures, 323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LP
INT LP-Output Buffer Overflow
Significance
The INT-LP-OP-BUFF is reported if the output buffer for the low order
(VC-12, VC-3) desynchronizer overflows.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
AIS injected downstream.
Possible causes
Possible causes for the INT-LP-OP-BUFF alarm are:
• Transient changes in the received payload bit rate.
• Faulty tributary card.
• Synchronization problem in the network (e.g. timing loop).
Corrective actions
Procedure 2-54
INT-LP-OP-BUFFER alarm clearing
Step Action
2
1 Check for timing loops in the synchronization for the network.
a. Check that synchronization is set up according to the network
synchronization plan.
b. Check if a synchronization source switch has caused a timing loop.
If the alarm is still present go to step 3.
2 Check if the INT-LP-OP_BUFFER alarm is present on more than one of the 2
Mbit/s tributary ports.
If the INT-LP-OP_BUFFER alarm is only present on one tributary port, go to
step 3.
If the INT-LP-OP_BUFFER alarm is present on more than one tributary port
on a single 2 Mbit/s card, go to step 4
If the INT-LP-OP_BUFFER alarm is present on all the tributary ports on more
than one 2Mbit/s cards, go to step 3.
3 Check if the tributary received signal is stable and within limits.
If the tributary input signal is not within limits, investigate preceding 2 Mbit/s
equipment.
If the tributary signal is within limits, go to step 4.
4 Replace the indicated 2 Mbit/s tributary card. Refer to the Maintenance
Procedures, 323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LP
LP-Signal Fail (SF)
Significance
The LP Signal Fail alarm is reported if both paths in a protected VC-12 or
VC-3 connection fail.
Instance/Unit
This alarm is reported against a port instanced as
S <slot-no> - <port-no>
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Upstream fault in both traffic paths.
Corrective actions
Procedure 2-55
LP-SF alarm clearing
Step Action
—end—
LP
LP-Trail Identifier Mismatch (TIM)
Significance
2
The VC-12 and VC-3 path trace feature allows the operator to specify a trace
identifier in the J2 byte at the transmitting multiplexer and an expected
identifier at the terminating multiplexer. In the event of the expected trace
identifier not matching the transmitted identifier, the LP-TIM alarm is
reported. This alarm is detected at a path termination.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
AIS is injected downstream.
PM event.
Possible causes
Possible causes for the LP-TIM alarm are:
• Incorrect configuration of far end or near end path string.
• Incorrect path connection.
• Faulty tributary.
Corrective actions
Procedure 2-56
LP-TIM alarm clearing
Step Action
1 Ensure that the operator entered string has been entered correctly at both
ends:
If the settings are incorrect, correct as necessary
If the settings are correct, go to step 2.
2 Verify that the path is correctly connected at all local and intermediate
multiplexers and that no LP errors are present on the network.
If the path is incorrectly connected and/or LP errors are present, re-connect
as necessary and/or investigate network errors.
If the path is correctly connected and there are no LP errors in the network,
go to step 3.
3 Replace the local tributary card. Refer to the Maintenance Procedures,
323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 4.
4 Replace the far end card. Refer to the Maintenance Procedures,
323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LP
LP-Label Unequipped
Significance
2
The LP-UNEQ value of the VC-12 or VC-3 payload signal label indicates
unequipped (no traffic in payload) when unequipped is not the expected
payload label.
Instance/Unit
This alarm is reported against a port instanceas
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
If configured on:
• AIS is injected downstream.
• RDI is injected upstream.
• PM event.
PM event.
Possible causes
Possible causes for the LP-UNEQ alarm are:
• Incorrect overhead configuration at near or far end.
• Incorrect path connection.
• Faulty tributary.
Corrective actions
Procedure 2-57
LP-UNEQ alarm clearing
Step Action
1 Ensure that the system path configuration at both ends is correct as follows:
- if no traffic expected, both ends should be configured to send a
value of ‘0’.
- if traffic is expected, both ends should be configured to send a
value of ‘1’ or ‘2’.
If the settings are incorrect, correct as necessary
If the settings are correct, go to step 2.
2 Verify that the path is correctly connected at all intermediate multiplexers and
that no LP errors are present on the network.
If the path is incorrectly connected and/or LP errors are present, re-connect
as necessary and/or investigate network errors.
If the path is correctly connected and there are no LP errors in the network,
go to step 3.
3 Replace the local tributary card. Refer to the Maintenance Procedures,
323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 4.
4 Replace the far end card. Refer to the Maintenance Procedures,
323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LP
LP-Quality of service violation (15 minute)
Significance
The Lp_qosv_15M alarm is reported to indicate that an active BBE, ES, SES
2
or UAS performanance monitoring point threshold has been exceeded within
a 15 minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Lp_qosv_15M alarm are:
• Excessive attenuation in cable or optical fibre.
• Faulty traffic card.
• RS_LOS, RS_LOF, ES_CMI, TU_AIS, TU-LOP, LP_TIM, LP_EXC,
LP_UNEQ, LP_DEG or INT_LO_BUFFER_OVERFLOW alarms.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-58
Lp_qosv_15M alarm clearing
Step Action
—end—
LP
LP-Quality of service violation (24 hour)
Significance
The Lp_qosv_24H alarm is reported to indicate that an active BBE, ES, SES
or UAS performanance point monitoring threshold has been exceeded within
a 24 hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Consequent Action
None.
Possible causes
Possible causes for the Lp_qosv_24H alarm are:
• Excessive attenuation in cable.
• Errored input signal.
• Faulty traffic card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-59
Lp_qosv_24H alarm clearing
Step Action
—end—
LP
LP-Far end quality of service violation (15 minute)
Significance 2
The Lp_fe_qosv_15M alarm is reported to indicate that an active BBE, ES,
SES or UAS performance monitoring point threshold has been exceeded at
the far end within a 15 minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the Lp_fe_qosv_15M alarm are:
• RDI or REI received from the far multiplexer.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary, or SDH
electrical tributary card.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-60
Hp_fe_qosv_15M alarm clearing
Step Action
1 Check for the presence of the LP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of B3 bit errors (for VC-3) or V5 bit errors (for VC-12).
Identify and remove the cause of these errors.
3 The Lp_fe_qosv_15M alarm clears after the next 15 minute monitoring
period.
—end—
LP
LP-Far end quality of service violation (24 hour)
Significance 2
The LP_fe_qosv_24H alarm is reported to indicate that an active BBE, ES,
SES or UAS performanance monitoring point threshold has been exceeded at
the far end within a 24 hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the LP_fe_qosv_24H alarm are:
• LP-RDI alarm from the far multiplexer.
• Faulty local tributary.
• Faulty far end tributary.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-61
Lp_fe_qosv_24H alarm clearing
Step Action
1 Check for the presence of the LP-RDI alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of errored blocks from LP-REI. Identify and remove
the cause of these errors.
3 The Lp_qosv_24H alarm clears after the current 24 hour monitoring period.
—end—
LPOM
LPOM - quality of service violation
(15 minute)
Significance
The LPOM_QOSV_15M alarm is reported to indicate that any BBE, ES,
SES, UAS active performance monitoring threshold has been broken within a
15 minute monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The LPOM_QOSV_15M alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty tributary card.
Corrective actions
This alarm automatically clears upon completion of a 15 minute monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-62
LPOM_QOSV_15M alarm clearing
Step Action
1 Check for the presence of the RS-LOS alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of the LPOM_Violation alarm. Identify and remove the
cause of this alarm.
3 The LPOM_QOSV_15M alarm clears after the next 15 minute monitoring
period.
—end—
LPOM
LPOM - quality of service violation
(24 hour)
2
Significance
The LPOM_QOSV_24H alarm is reported to indicate that any BBE, ES, SES,
UAS active performance monitoring threshold has been broken within a 24
hour monitoring period.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the The LPOM_QOSV_24H alarm are:
• Excessive attenuation in cable.
• Errored input signal
• Faulty tributary card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-63
LPOM_QOSV_24H alarm clearing
Step Action
1 Check for the presence of the RS-LOS alarm. Identify and remove the cause
of this alarm.
2 Check for the presence of the LPOM_Violation alarm. Identify and remove the
cause of this alarm.
3 The LPOM_QOSV_24H alarm clears after the next 24 hour monitoring
period.
—end—
LPOM
LPOM-Excessive Errors (EXC)
Significance
The LPOM-EXC is reported when the BER of the VC-12 path status byte
(V5) or VC-3 (B3) has exceeded the configured threshold.
Instance/Unit
This alarm is reported against a low order path instance as
S <slot-no> - <port-no>
Impact
Critical alarm
Consequent Action
A traffic protection switch occurs.
Possible causes
Possible causes for the LPOM-EXC alarm are:
• Errors on network.
• Faulty STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-64
LPOM-EXC alarm clearing
Step Action 2
1 Check if there are any MS or HP bit error alarms in the network, upstream.
If there are MS or HP alarms in the network, perform the recommended
actions to clear alarms.
If there are no MS or HP alarms in the network, go to step 2.
2 Replace the indicated card. Refer to Maintenance Procedures,
323-1233-547. Restore to the old configuration.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
LPOM
LPOM-Trail Identifier Mismatch (TIM)
Significance
The VC-12 or VC-3 path trace feature allows the operator to specify a trace
identifier in the J2 byte at the transmitting multiplexer and an expected
identifier at the terminating multiplexer. In the event of the expected trace
identifier not matching the transmitted identifier, the LPOM-TIM alarm is
reported.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
None.
Possible causes
Possible causes for the LPOM-TIM alarm are:
• Incorrect configuration of far end or near end path string.
• Incorrect path connection.
• Faulty 2 Mbit/s tributary.
• Faulty 34/45 Mbit/s tributary.
Corrective actions
Procedure 2-65
LPOM-TIM alarm clearing
Step Action 2
1 Ensure that the operator entered string has been entered correctly at both
ends:
If the settings are incorrect, correct as necessary
If the settings are correct, go to step 2.
2 Verify that the path is correctly connected at all local and intermediate
multiplexers and that no LP errors are present on the network.
If the path is incorrectly connected and/or LP errors are present, re-connect
as necessary and/or investigate network errors.
If the path is correctly connected and there are no LP errors in the network,
go to step 3.
3 Replace the local 2 Mbit/s (or 34/45 Mbit/s) tributary card. Refer to the
Maintenance Procedures, 323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 4.
4 Replace the far 2 Mbit/s (or 34/45 Mbit/s) card. Refer to the Maintenance
Procedures, 323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LPOM
LPOM-Payload Label Mismatch (PLM)
Significance
The value of the VC-12/VC-3 signal label code, or VC-3 C2 byte, does not
correspond with the expected value. This alarm is reported at a path
termination point, subsequent to a protection switch.
Impact
Major alarm
Consequent Action
Protection switch.
Possible causes
Possible causes for the LPOM-PLM alarm are:
• Incorrect overhead configuration at near or far end.
• Incorrect path connection.
• Faulty 2 Mbit/s tributary.
Corrective actions
Procedure 2-66
LPOM-PLM alarm clearing
Step Action 2
1 Ensure that the system path configuration at both ends is correct as follows:
- if no traffic expected, both ends should be configured to send a
value of ‘0’.
- if traffic is expected, both ends should be configured to send a
value of ‘1’ or ‘2’.
Refer to Provisioning and Operations Procedures, 323-1233-310 for the
procedure to view and change connections.
If the connections are incorrect, reconfigure as necessary.
If the settings are correct, go to step 2.
2 Verify that the path is correctly connected at all intermediate multiplexers and
that no LP errors are present on the network.
If the path is incorrectly connected and/or LP errors are present, re-connect
as necessary and/or investigate network errors.
If the path is correctly connected and there are no LP errors in the network,
go to step 3.
3 Replace the local 2 Mbit/s tributary card. Refer to the Maintenance
Procedures, 323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 4.
4 Replace the far 2 Mbit/s card. Refer to the Maintenance Procedures,
323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
LPOM
LPOM-Label Unequipped (UNEQ)
Significance
The LP-UNEQ value of the VC-12 payload signal label indicates unequipped
(no traffic in payload) when unequipped is not the expected payoad label.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Major alarm
Consequent Action
Protection switch on protected paths.
Possible causes
Possible causes for the LPOM-UNEQ alarm are:
• Incorrect overhead configuration at near or far end.
• Incorrect path connection.
• Faulty 2 Mbit/s tributary.
• Faulty 34/45 Mbit/s tributary.
Corrective actions
Procedure 2-67
LPOM-UNEQ alarm clearing
Step Action 2
1 Ensure that the system path configuration at both ends is correct as follows:
- if no traffic expected, both ends should be configured to send a
value of ‘0’.
- if traffic is expected, both ends should be configured to send a
value of ‘1’ or ‘2’.
If the settings are incorrect, correct as necessary
If the settings are correct, go to step 2.
2 Verify that the path is correctly connected at all intermediate multiplexers and
that no LP or LPOM errors are present on the network.
If the path is incorrectly connected and/or LP errors are present, re-connect
as necessary and/or investigate network errors.
If the path is correctly connected and there are no LP errors in the network,
go to step 3.
3 Replace the local 2 Mbit/s tributary card. Refer to the Maintenance
Procedures, 323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedures are complete.
If the alarm is still present, go to step 4.
4 Replace the far 2 Mbit/s card. Refer to the Maintenance Procedures,
323-1233-547 for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
PPI
PPI-Transmit Fail (TF)
Significance
The tributary output signal has fallen below a predefined threshold.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Critical Alarm
Consequent Action
None.
Possible causes
Possible causes for the PPI-TF alarm are:
• Cable fault.
• Faulty tributary card.
Corrective actions
Procedure 2-68
PPI-TF alarm clearing
Step Action 2
1 Ensure that the traffic output cable is properly terminated. Re-terminate the
connector if required.
If the alarm clears, the alarm clearing procedure is complete.If the alarm is
still present, go to step 2.
2 Check the far end equipment for a short circuit.
If the alarm clears, the alarm clearing procedure is complete. If the alarm is
still present, go to step 3.
3 Replace the indicated tributary card. Refer to the Maintenance Procedures,
323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
PPI
PPI-Loss Of Signal (LOS)
Significance
The PPI-LOS is reported where the loss of a PDH input signal is detected.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Critical alarm.
Consequent Action
All-ones(AIS) are transmitted in the traffic payload.
Possible causes
Possible causes for the PPI-LOS alarm are:
• Preceding equipment failure.
• Input connector not properly connected.
• Faulty tributary card.
Corrective actions
Procedure 2-69
PPI-LOS alarm clearing
Step Action 2
1 Ensure that the associated input connector is properly connected.
If connector is not properly connected, re-insert connector.
If connector is properly connected, go to step 2.
2 Verify that a valid tributary signal is present at distribution frame.
If a valid signal is not present, check the tributary source equipment.
If a valid signal is present, go to step 4.
3 Verify that a valid tributary signal is present at the cable headshell.
Note: Removal of a 2 Mbit/s cable headshell causes a traffic loss on all 16
ports.
If a spare unused traffic port is available, the PDH signal can be verified by
connecting the cable to the spare port. If a signal is present, a
‘PPI-Unexp_Signal’ alarm will be reported for the spare port.
If a valid signal is not present, a cable fault is suspected.
If a valid signal is present, go to step 4.
4 Replace the indicated tributary card, Refer to the Maintenance Procedures,
323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
PPI
PPI-Alarm Indication Signal (AIS)
Significance
The PPI-AIS alarm is reported when the PDH interface detects an AIS
condition on the PDH input traffic.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Minor alarm.
Consequent Action
All-ones(AIS) are transmitted in the traffic payload.
Possible causes
AIS being generated by preceding equipment.
Corrective actions
Investigate preceding equipment for the cause of AIS.
PPI
PPI-Excessive errors (EXC)
Significance 2
The PPI-EXC alarm is reported when HDB3 or B3ZS code violations exceed
the threshold in a PDH signal.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Critical alarm.
Consequent Action
AIS is injected downtream.
Possible causes
Possible causes for the PPI-EXC alarm are:
• Excessive attenuation in cable.
• Errored input signal.
• Faulty tributary card.
Corrective actions
Procedure 2-70
PPI-EXC alarm clearing
Step Action
—end—
PPI
PPI-Signal Degrade (DEG)
Significance
The PPI-DEG alarm is reported when HDB3 or B3ZS code violations exceed
the threshold in a PDH signal.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Traffic is affected.
Consequent Action
None.
Possible causes
Possible causes for the PPI-DEG alarm are:
• Errored input signals.
• Faulty tributary card.
Corrective actions
Procedure 2-71
PPI-DEG alarm clearing
Step Action
—end—
PPI
PPI-Unexpected Signal
Significance 2
The PPI-UNEXP_SIGNAL alarm is reported where a signal is connected to a
2 Mbit/s, 34/45 Mbit/s or 140 Mbit/s port for which a traffic connection is not
configured.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
For details of valid arguments see Table 2-1 on page 2-11
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the PPI-UNEXP_SIGNAL alarm are:
• Incorrect cable connection.
• Incorrect traffic connection configuration.
• Faulty 2 Mbit/s, 34/45 Mbit/s or 140 Mbit/s tributary card.
Corrective actions
Procedure 2-72
PPI-UNEXP_SIGNAL alarm clearing
Step Action
—end—
PPI
PPI-Loss of Frame (LOF)
Significance
The PPI-LOF alarm is reported when a PDH port indicates that signal
framing information cannot be recovered in the receive path. This alarm will
ony be reported if the input port is configured to framed or multi-framed.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Major alarm.
Loss of traffic.
Consequent Action
None.
Possible causes
Possible causes for the PPI-LOF alarm are:
• Faulty tributary card.
• Errored input signal.
Corrective actions
Procedure 2-73
PPI-LOF alarm clearing
Step Action
—end—
PPI
PPI-Loss of Multiframe (LOM)
Significance 2
The PPI-LOM alarm is reported where a 2 Mbit/s PDH port reports that
signal multiframing information cannot be recovered in the recieve path. The
input port must be configured to multi-framed.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the PPI-LOM alarm are:
• Faulty 2 Mbit/s tributary card.
• Errored input signal.
Corrective actions
Procedure 2-74
PPI-LOM alarm clearing
Step Action
—end—
PPI
PPI-Loopback On
Significance
This alarm indicates that an internal local or remote loopback is present at the
indicated port.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Minor alarm.
Consequent Action
None.
Possible causes
The operator has applied a local or remote loopback at the indicated port.
Corrective actions
If required, remove the loopback as detailed in Network Surveillance
Procedures, 323-1233-510.
PPI
PPI- Transmit-Loss of Frame (T-LOF)
Significance 2
The PPI-LOF-T alarm is reported where a 140 Mbit/s PDH port reports that
signal framing information cannot be recovered in the transmit path. This
alarm will ony be reported if the input port is configured to framed or
multi-framed.
Instance/Unit
This alarm is reported against a port instance, reported as
S <slot-no> - <port-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the PPI-LOF-T alarm are:
• Faulty 140 Mbit/s tributary card.
• Output cable fault.
Corrective actions
Procedure 2-75
PPI-T-LOF alarm clearing
Step Action
1 Investigate preceding 140 Mbit/s equipment and cables for cause of errors.
If errors are intermittent, most likely cause is cabling and the connectors.
If no errors from preceding equipment, go to step 2.
2 Replace the indicated tributary card. Refer to the Maintenance Procedures,
323-1233-547, for replacement procedures.
If the alarm clears, the alarm clearing procedure is complete.
If the alarm is still present, escalate the problem.
—end—
PPI
PPI-Code violation Quality of service violation
(15 minute)
Significance
The PPI_CV_qosv_15M alarm is reported to indicate that any BBE, ES, SES,
UAS active performance monitoring threshold has been broken within a 15
minute monitoring period.
Instance/Unit
This alarm is reported as
S <slot-no> - <port-no>
Step Action
1 Check for the presence of code violation defects, PPI-LOF, PPI-AIS. Identify
and remove the cause of these alarms.
2 Check for the presence of errored frames. Identify and remove the cause of
these errors.
3 The PPI_CV_qosv_15M alarm clears after the next 15 minute monitoring
period.
—end—
PPI
PPI-Code violation-Quality of service violation
(24 hour)
2
Significance
The PPI_CV_qosv_24H alarm is reported to indicate that any BBE, ES, SES,
UAS active performanance monitoring threshold has been broken within a 24
hour monitoring period.
Instance/Unit
This alarm is reported against a port instance, as
S <slot-no> - <port-no>
Impact
Minor Alarm
Consequent Action
None.
Possible causes
Possible causes for the PPI_CV_qosv_24H alarm are:
• Excessive attenuation in cable.
• Errored input signal.
• Faulty traffic card.
Corrective actions
This alarm automatically clears upon completion of a 24 hour monitoring
period in which no QOSV thresholds have been exceeded. The following
procedure describes how to detect the cause of the alarm.
Procedure 2-77
PPI_CV_qosv_24H alarm clearing
Step Action
1 Check for the presence of code violation defects, PPI-LOF, PPI-AIS. Identify
and remove the cause of these alarms.
2 Check for the presence of errored frames. Identify and remove the cause of
these errors.
3 The PPI_CV_qosv_24H alarm clears after the current 24 hour monitoring
period.
—end—
SYNC
Sync-SETG Fail
Significance
This alarm indicates that a serious problem has occurred in the
synchronization source selection circuit on the indicated aggregate card.
Instance/Unit
This alarm is reported against an aggregate card instance as
S <slot-no>
Impact
Critical alarm
Consequent Action
None.
Possible causes
Failure of the synchronization circuit on the indicated aggregate card.
Corrective actions
Procedure 2-78
SYNC-SETG_Fail alarm clearing
Step Action
—end—
SYNC
Sync-Unexpected signal
Significance 2
The external synchronization input (ESI) port is receiving a synchronization
signal but the port is not in the hierarchy list.
Instance/Unit
This alarm is reported against an external synchronization port instance as
S <slot-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
The ESI port is not in the SETG or ESO hierarchy list.
Corrective actions
Add the ESI port to the hierarchy list or remove external synchronisation
signal.
SYNC
Sync-ESO Source Not Primary
Significance
The source currently selected to provide synchronization is not the primary
source as defined in the ESO hierarchy list.
• If synchronization source messaging (SSM) is active this alarm is not
reported.
• Selecting a synchronization source using a Forced or Manual override does
not raise this alarm.
Instance/Unit
None.
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Failure of primary source.
Corrective actions
Investigate primary source for possible faults or synchronization source
switching actions.
SYNC
Sync-SETG Holdover
Significance 2
This alarm is reported when the NE is operating in holdover mode. This mode
is entered when all external synchronization input sources are rejected and the
internal clock is running off historical values (or has just started).
Instance/Unit
This alarm is reported against the NE.
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Possible causes for the SYNC_SETG_HOLDOVER alarm are:
• Forced switch to a faulty synchronization source.
• All sources on the hierarchy list are faulty and the NE is using the internal
oscillator for synchronization.
Corrective actions
If a forced switch or manual overide is active, check the status of the
synchronization source.
SYNC
Sync-Source Not Primary
Significance
The source currently selected to provide synchronization is not the primary
source as defined in the SETG hierarchy list.
• If synchronization source messaging (SSM) is active this alarm will not be
reported.
• If the current synchronization source was selected by a Forced or Manual
override, this alarm is not reported.
Instance/Unit
None.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Failure of primary source.
Corrective actions
Investigate primary source for possible faults or synchronization source
switching actions.
SYNC
Sync-External Sync Loss Of Signal
Significance 2
The signal from the external synchronization input (ESI) on an End of Shelf
(EOS) card has failed.
Impact
Critical alarm
Consequent Action
None.
Possible causes
Possible causes for the SYNC-External Loss of Signal alarm are:
• Input connector not properly terminated.
• External synchronization source failure.
• Faulty End of Shelf card.
Corrective actions
Procedure 2-79
SYNC-Ext_Sync_LOS alarm clearing
Step Action
—end—
SYNC
Sync-Source out of limits
Significance 2
A port which can be used as a frequency source has a gross frequency offset.
Instance/Unit
This alarm is reported against an input port which is in either of the SETG or
ESO selector Synchronization Source Hierarchies.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Faulty synchronization source or SETS in the aggregate card.
Corrective actions
Note: Allow 5 minutes to elapse before attempting to clear the alarm.
Procedure 2-80
SYNC-SOURCE-OUT-OF-LIMITS alarm clearing
Step Action
—end—
Misc
Qecc Comms Fail
Significance
The NE cannot communicate over any specific link with the neighbouring NE
via the Embedded Control Channel (ECC).
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Critical alarm.
Non-traffic affecting.
Consequent Action
None.
Possible causes
Possible causes for the Qecc Comms Fail alarm are:
• Loopback present.
• The card carrying the ECC has been unequipped.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-81
Qecc_Comms_Fail alarm clearing
Step Action 2
1 Check if a loopback is present. Refer to Network Surveillance Procedures,
323-1233-510.
If a loopback is present, disable the loopback. If the alarm is still present, go
to step 2.
If the alarm has cleared, the alarm clearing procedure is complete.
2 Check if any of the cards in the ECC path have been unequipped.
If the card is unequipped, re-equip it using the CAT. refer to Provisioning and
Operations Procedures, 323-1233-310.
3 Examine the current Lapd mode.Refer to Provisioning and Operations
Procedures, 323-1233-310.
If the failed link is in then
Rs mode goto step 4
Ms mode goto step 5
Both goto step 6
Auto goto step 7
—continued—
Procedure 2-81
Qecc_Comms_Fail alarm clearing (continued)
Step Action
—end—
Misc
INT NE-Spi Comms Fail
Significance 2
A fault has been detected on the internal SPI communications function.
Instance/Unit
This alarm is reported against a port instance as
S <slot-no> - <port-no>
Impact
Critical alarm.
Non-traffic affecting.
Consequent Action
None.
Possible causes
Possible causes for the INT NE-Spi-Comms-Fail alarm are:
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Procedure 2-82
Spi-Comms_Fail alarm clearing
Step Action
—end—
Misc
EA-Ext inp <1-8>
Significance
A alarm has been received on one of the external alarm inputs.
Instance/Unit
This alarm is reported against an external alarm input instance.
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Dependant on the alarm source.
Corrective actions
Investigate the alarm source for the cause of the alarm.
Misc
EA-Ext out <1-5>
Significance 2
An alarm has been received on one of the external alarm outputs.
Note: More than one alarm type can map to activate an external alarm
signal; however a single alarm type cannot.
Instance/Unit
This alarm is reported against an external alarm output instance.
Impact
Depends on the alarm type and mapping.
Consequent Action
None.
Possible causes
Dependant on the alarm source.
Corrective actions
Investigate the alarm source for the cause of the alarm.
Misc
INT NE-Configuration Corrupt
Significance
The configuration data held in the configuration bank is corrupt and the NE
enters detached mode.
This alarm is reported only when one of the following configuration alarms is
reported:
• INT NE-config_all_banks_corrupt
• INT NE-config_available_bank_corrupt
• INT NE-config_validation_error
• INT NE-config_audit_mismatch
• INT NE-config_bp_mismatch
Instance/Unit
This alarm is reported against the NE.
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Configuration data corrupt.
Corrective actions
Check which of the associated configuration alarms are also present. Perform
the alarm clearing procedures for the associated alarm.
Misc
NE-Lan Alarm
Significance 2
A fault has been detected on the LAN sub-network.
Impact
Critical alarm.
Loss of communication to the EC and to any NEs connected via the local
LAN sub-network.
Consequent Action
None.
Possible causes
Possible causes for the NE-Lan alarm are:
• LAN connector not properly terminated.
• Problem on LAN sub-network.
Corrective actions
Check that the LAN connector is properly terminated. If the LAN connector
is properly terminated, investigate the local LAN sub-network.
Misc
NE-Unexpected LAN
Significance
Indicates a LAN is present but the LAN service state is set to Standby
(indicating that a LAN is not expected).
Instance/Unit
None.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the Unexpected LAN alarm are:
• LAN is incorrectly connected.
• System is incorrectly configured.
Corrective actions
If a LAN is expected, reconfigure the system as required (see Provisioning
and Operations Procedures, 323-1233-310).
Misc
INT NE-Config bp mismatch
Significance 2
The serial number of the master aggregate card does not match the serial
number stored in the backplane SIM card. This check occurs during a warm
or cold restart of the master aggregate. The NE enters detached mode.
Instance/Unit
This alarm is reported against the NE.
Impact
Critical Alarm
Critical alarm.
Consequent Action
If alarm is raised against the Master SEMF the Network Element enters
detached mode.
Possible causes
The aggregate has been replaced or there is a mismatch in the configuration
data.
Corrective actions
Perform the following procedures (refer to System and Data Administration
Procedures, 323-1233-302):
• Check the configuration and change if necessary.
• Impose the stored configuration. This will:
—write the serial number of the aggregate cards into the SIM card
—take the NE out of detached mode
—remove the alarm
Misc
Ps-power fail
Significance
The power supply to either the Upper or Lower end of shelf cards has failed.
Instance/Unit
This alarm is reported against an EOS card instance as
S <slot-no>
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Power supply fail.
Corrective actions
Check the power connection to the indicated card.
Misc
NE-Date time unknown
Significance 2
This alarm is reported when the real time clock in the NE has no knowledge
of the date and time.
Instance/Unit
None.
Impact
Major alarm.
Consequent Action
None.
Possible causes
A loss of power to the NE will cause the contents of the RTC to be lost.
Corrective actions
Set the real time clock. Refer to System and Data Administration Procedures,
323-1233-302.
Misc
Unexpected SW version
Significance
The software version on a tributary or aggregate card does not match the
version number in the configuration store.
Instance/Unit
None.
Impact
Minor alarm.
Consequent Action
None.
Possible causes
Card installed with incorrect software load.
Card type may not have been previously installed in the shelf.
Corrective actions
Perform a software upgrade on the indicated card as detailed in System and
Data Administration Procedures, 323-1233-302 or set expected software
version.
Misc
Internal 1 second clock loss of signal
Significance 2
A card with a missing 1-second input clock will raise this alarm.
Instance/Unit
This alarm is reported against a card instance as
S <slot-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for this alarm are:
• aggregate failure.
• tributary failure.
• Backplane failure.
Corrective actions
Perform a SEMF protection switch. If the alarm persists, replace aggregate or
tributary card (see Provisioning and Operations Procedures, 323-1233-310).
Card
NE-Card Out
Significance
Indicates that the indicated card has been removed from the shelf without
unequipping the slot.
Impact
Critical alarm
Consequent Action
None.
Possible causes
Possible causes for the Card Out alarm are:
• Card removed.
• System incorrectly configured.
• Faulty aggregate card.
Corrective actions
Procedure 2-83
NE-Card_Out alarm clearing
Step Action 2
1 Check if the card is expected in the indicated slot.
If the card is not expected, go to step 2.
If the card is expected in the indicated slot, check that the card is correctly
installed in the NE. If the alarm still present, go to step 3.
2 Configure the equipment to unequip the indicated slot, see Provisioning and
Operations Procedures, 323-1233-310.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, go to step 3.
3 Peform a warm restart on the master aggregate card, see System and Data
Administration Procedures, 323-1233-302.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, go to step 4.
4 Peform a manual SEMF protection switch on the master aggregate card, see
Provisioning and Operations Procedures, 323-1233-310.
If the alarm has cleared, go to step 5
If the alarm is still present escalate the problem.
5 Replace the aggregate card. Refer to Maintenance Procedures,
323-1233-547.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, replace original aggregate card and escalate
problem.
—end—
Card
NE-Unexpected Card
Significance
Indicates that a card is present in a slot which is configured as ‘Unequipped’.
This alarm is reported approximately 30 seconds after the card is inserted.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the Unexpected Card alarm are:
• Card inserted into wrong slot.
• System incorrectly configured.
• Faulty aggregate card.
Corrective actions
Procedure 2-84
NE-Unexpected_Card alarm clearing
Step Action 2
1 Check if the card is expected in indicated slot.
If the card is expected, go to step 2.
If the card is not expected, remove the card from the indicated slot. If alarm
still present, go to step 3
2 Configure the equipment to equip the slot with the correct card type (see
Provisioning and Operations Procedures, 323-1233-310).
If the alarm clears, the alarm clearing procedure is complete.
If the alarm still present, go to step 3.
3 Peform a warm restart on the master aggregate card, see System and Data
Administration Procedures, 323-1233-302.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, go to step 4.
4 Peform a manual SEMF protection switch on the master aggregate card, see
Provisioning and Operations Procedures, 323-1233-310.
If the alarm has cleared, go to step 5
If the alarm is still present escalate the problem.
5 Replace the aggregate card. Refer to Maintenance Procedures,
323-1233-547.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, replace original aggregate card and escalate
problem.
—end—
Card
INT-NE-HBEAT_Missing
Significance
The aggregate card detects a fault on the indicated card or fails to
communicate with the indicated card.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Possible cause for the INT-NE-HBEAT_Missing alarm is a faulty indicated
card.
Corrective actions
Procedure 2-85
INT-NE-HBEAT_Missing alarm clearing
Step Action
—end—
Card
NE-Card Fault
Significance 2
Self-diagnosis indicates the card has a fault.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Faulty indicated card.
Corrective actions
If the alarm is repeated or persistent, replace indicated card. Refer to the
Maintenance Procedures, 323-1233-547.
Card
NE-Wrong Card
Significance
A card has been inserted into a slot designated for another type of card (slot
wrong or card wrong).
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Consequent Action
None.
Possible causes
Possible causes for the Wrong Card alarm are:
• Wrong card fitted in a slot.
• Card fitted in wrong slot.
• System incorrectly configured.
Corrective actions
Procedure 2-86
NE-Wrong_Card alarm clearing
Step Action
—end—
Card
NE-Invt Write Jumper Fitted
Significance 2
This alarm indicates that a link is present on a card which enables access to
the non-volatile RAM.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Link is present on the card.
Corrective actions
Contact Nortel Networks technical support.
Card
NE-Minor card mismatch
Significance
This alarm occurs when the operator configures a slot for a card type and
sub release but inserts a card with a lower sub release.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Minor alarm.
Consequent Action
None.
Possible causes
Wrong sub release of card in slot.
Corrective actions
Replace the card or re-equip the slot for the correct sub-release (see
Provisioning and Operations Procedures, 323-1233-310).
Config
INT NE-Configuration Corrupt Bank
Significance 2
The configuration data held in the active non volatile configuration bank is
corrupt.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the Configuration Corrupt bank alarm are:
• Non volatile store corruption on the aggregate card.
• Continual cyclic reboots.
Corrective actions
Procedure 2-87
INT-NE_Config_Corrupt_Bank
Step Action
1 Carry out a restore of the configuration bank as detailed in System and Data
Administration Procedures, 323-1233-302.
2 If the alarm is still present, replace the aggregate card. Refer to Maintenance
Procedures, 323-1233-547.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
Config
Significance
The configuration data held in both the active and standby non-volatile
configuration banks is corrupt.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
The NE enters detached mode.
The following operations are not allowed until the alarm is cleared:
• software upgrade
• configuration changes
• consolidation of the configuration banks
• traffic card provisioning
Possible causes
Possible causes for the Configuration All Banks Corrupt alarm are:
• Non-volatile store corruption on the aggregate card.
• Continual cyclic reboots.
Corrective actions
Procedure 2-88
INT-NE_Config_All_Banks_Corrupt
Step Action
1 Carry out a restore of the configuration banks as detailed in System and Data
Administration Procedures, 323-1233-302.
2 If the alarm is still present, replace the aggregate card. Refer to Maintenance
Procedures, 323-1233-547.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
Config
INT NE-Configuration Available Bank Corrupt
Significance 2
This alarm is reported if the data held in the configuration bank is corrupted
during a software upgrade or configuration restore procedure.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
The NE enters detached mode.
The following procedures are not allowed until the alarm is cleared:
• software upgrade
• configuration changes
• consolidation of the configuration banks
• a restore of the configuration banks
• traffic card provisioning
Possible causes
Possible causes for the Configuration Available Bank Corrupt alarm are:
• Non-volatile store corruption on the aggregate card.
• Continual cyclic reboots.
Corrective actions
Procedure 2-89
INT NE-Config_Avail_Bank_Corrupt
Step Action
Cnfg_tbl ↵ c↵
View ↵ v↵
A confirmation is required.
4 Execute the backout command by entering
Backout ↵ b↵
—end—
Config
INT NE-Configuration Software Mismatch
Significance 2
The version of software loaded on a card and the version referenced in the
configuration bank are different.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
None.
Possible causes
New card inserted with incorrect software or configuration version.
Corrective actions
Procedure 2-90
INT NE-Cfg_sw_mismatch
Step Action
1 Display the software and configuration table status. Access the ‘Admin/
cnfg_tbl’ submenu by entering
Admin ↵ a↵
Cnfg_tbl ↵ c↵
2 If the software version is correct carry out step 3. If the software version is
incorrect carry out step 4.
—continued—
Procedure 2-90
INT NE-Cfg_sw_mismatch (continued)
Step Action
Admin ↵ a↵
Cnfg_tbl ↵ c↵
Consolidate ↵ c↵
No confirmation is required.
4 If the alarm is still present, carry out a software download as detailed in
System and Data Administration Procedures, 323-1233-302.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
Config
INT NE-Configuration Audit Mismatch
Significance 2
A configuration audit indicates that the configuration data in the RAM is
different to the configuration settings on the traffic cards.
Impact
Major alarm.
Consequent Action
The NE enters detached mode.
Possible causes
Audit mismatch.
Corrective actions
Procedure 2-91
INT NE-Cfg_Audit_Mismatch
Step Action
Cnfg_tbl ↵ c↵
Impose_config ↵ ic ↵
A confirmation is required.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
Config
INT NE-Configuration Validation Error
Significance 2
During a restart, a value read from the configuration store is invalid.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
If alarm is raised against the Master SEMF the Network Element enters
detached mode.
Possible causes
Incorrect software or configuration version.
Corrective actions
Procedure 2-92
INT NE-Cfg_validation_error
Step Action
1 Carry out a restore of the configuration banks as detailed in System and Data
Administration Procedures, 323-1233-302.
2 If the alarm is still present, replace the aggregate card. Refer to Maintenance
Procedures, 323-1233-547.
If the alarm has cleared, the alarm clearing procedure is complete.
If the alarm is still present, escalate problem.
—end—
Config
INT NE-Standby Configuration Software Unstable
Significance
This alarm indicates a problem with the standby software.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Software or configuration problem.
Corrective actions
Perform a backup of the active configuration store to the standby as detailed
in System and Data Administration Procedures, 323-1233-302.
Config
INT NE-Standby Configuration Flash Corrupt
Significance 2
This alarm indicates a problem with the standby flash memory.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Corruption of the standby non-volatile configuration banks.
Corrective actions
Perform a backup of the active configuration store to the standby as detailed
in System and Data Administration Procedures, 323-1233-302.
Config
INT NE-Standby Configuration audit mismatch
Significance
The configuration data held in the standby aggregate active non-volatile
configuration bank is corrupt (it does not match the configuration data held in
the master aggregate active non-volatile configuration bank).
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the alarm are:
• Non-volatile store corruption on the aggregate card.
• Continual cyclic reboots.
Corrective actions
Perform a backup of the active configuration store to the standby as detailed
in System and Data Administration Procedures, 323-1233-302.
Config
INT NE-Standby Configuration fail
Significance 2
The configuration bank on the stand-by aggregate has failed.
Instance/Unit
This alarm is reported against the NE.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Stand-by flash memory is corrupt or the stand-by configuration state is
misaligned with the master aggregate.
Corrective actions
Perform a backup of the active configuration store to the standby as detailed
in System and Data Administration Procedures, 323-1233-302.
Prot
Equip_Fail
Significance
Reported when a 1+1 protection I/O card fails.
Instance/Unit
This alarm is reported against the working tributary card.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Hardware failure on 1+1 protection I/O card.
Corrective actions
Replace the 1+1 protection I/O card. Refer to the Maintenance Procedures,
323-1233-547.
Prot
Equip_Out
Significance 2
Reported when both the 1+1 working and protection tributary cards detect no
connection to the 1+1 protection I/O card.
Instance/Unit
This alarm is reported against the working tributary card.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Interface cable between the 1+1 protection I/O card and the tributaries is not
present or is incorrectly connected.
Corrective actions
Check interface cable between the 1+1 protection I/O card and the tributaries.
Prot
Unexpected_Equip
Significance
Reported where the 1+1 I/O card is connected to a tributary card in a
protection slot, but that slot is not in a 1+1 card association.
Instance/Unit
This alarm is reported against a protection tributary card.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Card association not made by operator.
Corrective actions
Create card association for 1+1 card protection (see Provisioning and
Operations Procedures, 323-1233-310).
Prot
Cable_Error
Significance 2
Reported to indicate that a cable fault exists between a tributary slot and a 1+1
protection I/O card.
Instance/Unit
This alarm is reported against the working or protection card slot.
Impact
Major alarm.
Consequent Action
Protection switch to the other slot in the association.
Possible causes
Fault in the cable between the 1+1 protection I/O card and the tributaries.
The cable from the working or protection card is connected to the wrong port
on the 1+1 protection I/O card.
Corrective actions
Replace the interface cable between the 1+1 protection I/O card and the
tributaries.
Prot
Wrong_Equip
Significance
Reported to indicate a mismatch between a tributary card and a 1+1
protection
I/O card.
Instance/Unit
This alarm is reported against the working or protection card slot.
Impact
Major alarm.
Consequent Action
None.
Possible causes
1+1 protection I/O card and the tributaries are not compatible.
Corrective actions
Replace either the 1+1 protection I/O card or the tributaries.
MSP
FOP_PAM
Significance 2
The Failure Of Protocol-Protection Architecture Mismatch alarm raises when
the multiplexing equipments at either end of transmission path are using
different protection architectures. For example, the local multiplexer is
operating 1+1 MSP and the remote end is operating 1:N protection.
Instance/Unit
The alarm is reported against bidirectional SDH protection ports.
Impact
Major alarm.
Consequent Action
None.
Possible causes
Multiplexing equipment at either end of transmission path are using different
protection architectures.
Corrective actions
Reconfigure equipment to a common protection architecture.
MSP
FOP_SCM
Significance
The Failure Of Protocol-Selector Channel Mismatch alarm is reported to
indicate that a difference exists in the transmitted channel of the K1 byte and
the received channel K2 byte.
Instance/Unit
The alarm is reported against bidirectional SDH protection ports.
Impact
Major alarm.
Consequent Action
Causes an MSP protection switch.
Possible causes
Possible causes for the FOP_SCM alarm are:
• Indicates a protocol failure.
• Incorrect optical fibre connection between protection and working cards
across the transmission path.
Corrective actions
Ensure optical fibre connections between protection and working cards across
the transmission path are correct.
MSP
FOP_INV
Significance 2
The Failure Of Protocol-Invalid alarm is reported to indicate that the received
K1 byte is invalid.
Instance/Unit
The alarm is reported against bidirectional SDH protection ports.
Impact
Major alarm.
Consequent Action
This is an signal fail condition so it causes a MSP protection switch.
Possible causes
Possible causes for the FOP_INV alarm are:
• Optical hygiene problem.
• Faulty local STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
• Faulty far end STM-N optical aggregate, optical tributary or SDH electrical
tributary card.
Corrective actions
Examine fibre-optic path for hygiene problems and replace local or far end
cards as necessary.
MSP
FOP_TMOUT
Significance
The Failure of protocol-Timeout alarm indicates that the K1 byte has not been
received within the specified 50 ms.
Instance/Unit
The alarm is reported against bidirectional SDH protection ports.
Impact
Major Alarm
Consequent Action
This is an signal fail condition so it causes a MSP protection switch.
Possible causes
Possible causes for the FOP_TMOUT alarm are:
• Multiplexing equipment at either end of transmission path are using
different protection architectures.
• Incorrect optical fibre connection between protection and working cards
across the transmission path.
Corrective actions
Reconfigure equipment to a common protection architecture or ensure optical
fibre connections between protection and working cards across the
transmission path are correct
OPE100 Card
NE_Config_Bp_Mismatch
Significance 2
Existing SDH connections have been affected by the card being inserted into
either the wrong slot, or wrong shelf.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Critical alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Config_Bp_Mismatch alarm are:
• The MAC address of the shelf recorded in the last successful boot does
not match the current shelf MAC address.
• The slot number of the last successful boot does not match the current slot
number.
Corrective actions
To correct the MAC address/slot number mismatch alarm, you must either:
• put the card in to the last booted shelf, or
• login within reduced mode and type the "proceed" command.
Refer to the OPTera Packet Edge 100 DCLI Command Specification
document for details on how to perform the "proceed" command..
Access is limited to rwa users as they have the greatest access rights to
diagnose card faults.
OPE100 Card
NE_Cfg_Corrupt_Bank
Significance
Configuration of card could not be obtained during start-up.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Major, deferred alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_Corrupt_Bank alarm are:
• The config.cfg file is corrupt.
• The config.cfg file is absent, and the $temp$.cfg file is corrupt.
Corrective actions
As access is denied, use the reduced mode password to access the system and
repair the config.cfg file.
OPE100 Card
NE_Cfg_All_Banks_Corrupt
Significance 2
During boot-up of card, configuration could not be read.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Major, deferred alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_All_Banks_Corrupt alarm are:
• The config.cfg file is corrupt or absent.
• The $temp$.cfg file is corrupt or absent.
Corrective actions
As access is denied, use the reduced mode password to access the system and
repair the config.cfg file.
OPE100 Card
NE_Cfg_Validation_Err
Significance
An invalid parameter exists on the config.cfg or $temp$.cfg file.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Major alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_Validation_Err alarm are:
• The config.cfg file contains invalid parameters.
• The $temp$.cfg file contains invalid parameters.
Corrective actions
As access is denied, use the reduced mode password to access the system and
repair the config.cfg file.
OPE100 Card
NE_Cfg_SW_Mismatch
Significance 2
An invalid command exists on the config.cfg or $temp$.cfg file.
Instance/Unit
This alarm is reported against an NE card instance as
S <slot-no>
Impact
Major, deferred alarm.
Consequent Action
None.
Possible causes
Possible causes for the NE_Cfg_SW_Mismatch alarm are:
• The config.cfg file contains invalid commands, or is absent.
• The $temp$.cfg file contains invalid commands, or is absent.
Corrective actions
As access is denied, use the reduced mode password to access the system and
repair the config.cfg file.
OPE100 Card
VC-EDD
Significance
An occurence of this alarm will mean that all traffic has stopped.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4> - k<VC-3>
k<VC-12>
Consequent Action
None.
Possible causes
Possible cause for the VC-EDD (Excessive Differential Delay) alarm is a very
long delay in one of the containers arriving.
If there are only 2 VCs concatenated then all traffic will be lost. However, if
there are more than 2 VCs concatenated then the card will grey-out the
delayed VC. This results in traffic flowing with lower bandwidth.
Corrective actions
Investigate cause of delay.
OPE100 Card
HP-SIM
Significance 2
An occurence of this alarm will mean that all traffic has stopped. It cannot be
protected against by protection switching or grey-out and is therefore
extremely serious.
Instance/Unit
This alarm is reported against a high order path instance as
S <slot-no> - <port-no> - J<AU-4>
Consequent Action
None
Possible causes
Possible causes for the HP-SIM (Sequence Identifier Mismatch) alarm are:
• One of the VCs could contain incorrect information, therefore all other
VCs are invalid.
• The bit sequence may have been altered by 3rd party vendor
• If there are more than 2 VCs concatenated, then the alarm will be raised
against the High Order Path Instance (J#). The card will grey-out the VC
that is out of sequence and traffic will flow, with lower bandwidth.
Corrective actions
This transient alarm should be corrected after the protection mechanism,
possibly from another alarm, is initiated.
OPE100 Card
INT-NE-IP_Subnet_Unknown
Significance
This alarm is only relevant when there are OPE100 cards present. This alarm
will not stop IP traffic on the OPE100 card, or SDH traffic.
Instance/Unit
This alarm is NE wide and so it does not relate to a given port. It is only raised
if there is an OPE100 card in the shelf.
Impact
Minor alarm
Consequent Action
None.
Possible causes
The OPE100 card’s IP subnet information has not been provisioned. The IP
subnet address, configured via the ~c o ip s command, must be forwarded to
all OPE100 cards in the shelf.
Corrective actions
This alarm is cleared when a valid subnet and mask for the shelf has been
configured. The occurrence of this alarm means that the OPE100 cards can
not be managed over the OSI network, but can still be managed over any
existing TCP/IP network.
Corrective action
Technical assistance must be obtained from Nortel Networks for any optical
amplifier alarm.
Index 3- 3
A action log 1-2
action
log H
fault clearing 1-2 HP-Excessive errors (EXC) alarm 2-47
alarm HP-Loss_of_Multiframe (LOM) alarm 2-55
clearing 1-1 HPOM_FE_QOSV_15M 2-76
consequent action 1-8 HPOM_QOSV_15M 2-73, 2-74
correlation 1-4 HPOM-Excessive errors (EXC) alarm 2-77
indications 1-3 HPOM-FE_QOSV_24H alarm 2-75
RAU category 1-5 HP-Path_Label_Mismatch (PLM)
severity 1-5 alarm 2-59, 2-81
alarms HP-Remote_Defect_Indicator (RDI)
port alarm monitoring 1-8, 2-2, 2-21 alarm 2-53
AU-Alarm_Indication_Signal (AIS) HP-Remote_Error_Indicator (REI)
alarm 2-44 alarm 2-57
AU-Loss_of_Pointer (LOP) alarm 2-46 HP-Signal Degrade (DEG) alarm 2-49
HP-Signal_Fail (SF) alarm 2-63
C HP-SIM
OPE100 card 2-195
Cable_Error alarm 2-183
clearing HP-Trace Identifier Mismatch (TIM) 2-51,
faultst 2-79
action log 1-2 HP-Unequipped alarm 2-61, 2-83
consequent action
alarm 1-8 I
Critical (alarm severity) 1-7 In station (RAU category) 1-7
INT LP-Input Buffer Overflow alarm 2-65,
D 2-98
INT LP-Output Buffer Overflow alarm 2-67,
Deferred (RAU category) 1-7
2-100
INT NE-Config_All_Banks_Corrupt
E alarm 2-168
EA-Ext_inp alarm 2-148 INT NE-Config_Audit_Mismatch
EA-Ext_out alarm 2-149 alarm 2-173
Equip_Fail alarm 2-180 INT NE-Config_Available_Bank_Corrupt
Equip_Out alarm 2-181 alarm 2-169
INT NE-Config_Bp_Mismatch alarm 2-153
F INT NE-Config_Corrup_Bank alarm 2-167
faults INT NE-Config_Corrupt alarm 2-150
clearing faults
Q
Qecc_Comms_Fail alarm 2-144
R
Rack alarm unit (RAU) 3
alarm category 1-5
rack alarm unit (RAU)
alarm indications 1-3
RS-Loopback_On alarm 2-27
RS-Loss_of_Signal (LOS) alarm 2-21
RS-Trace_Identifier_Mismatch (TIM)
alarm 2-25
RS-Unexpected_Signal alarm 2-20
S
Sync-ESO_Source_Not_Primary
alarm 2-138
SYNC-External_Sync_LOS alarm 2-141
Sync-Holdover alarm 2-139
Sync-SETG_Fail alarm 2-136
Sync-Source_Not_Primary alarm 2-140
Sync-Unexpected_Signal alarm 2-137
T
TU-Alarm_Indication_Signal alarm 2-85
TU-Loss_of_Pointer (LOP) alarm 2-86
U
Unexpected_Equip alarm 2-182
Unexpected_SW_Version alarm 2-156
V
VC-EDD
OPE100 card 2-194
W
Warning (alarm severity) 1-7
Wrong_Equip alarm 2-184
Nortel Networks
Optical Metro 4200
Alarm Clearing Procedures
Copyright © 2004, Nortel Networks, All Rights Reserved.
The copyright of this document is the property of Nortel Networks.
Without the written consent of Nortel Networks, given by contract
or otherwise, this document must not be copied, reprinted or
reproduced in any material form, either wholly or in part, and the
contents of this document, or any methods or techniques
available therefrom, must not be disclosed to any other person
whatsoever.
NORTEL NETWORKS CONFIDENTIAL:The information
contained herein is the property of Nortel Networks and is strictly
confidential. Except as expressly authorized in writing by Nortel
Networks, the holder shall keep all information contained herein
confidential, shall disclose it only to its employees with a need to
know, and shall protect it, in whole or in part, from disclosure and
dissemination to third parties with the same degree of care it uses
to protect its own confidential information, but with no less than
reasonable care. Except as expressly authorized in writing by
Nortel Networks, the holder is granted no rights to use the
information contained herein.
Document Number: 323-1233-543
Product Release Number: Release 4.1
Status: Standard
Date: April 2004
Printed in England