7570 Alarms Dictionary 3bl77057acbarkzza 04 en

Alcatel-Lucent 7570 Media Gateway
7570 ALARMS DICTIONARY
3BL 77057 ACBA RKZZA Ed.04
Status Mnemonic
RELEASED ALAOPG
25/04/2008
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent.
2 / 245
7570 Alarms Dictionary
CONTENTS
PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 1 ALARM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1.1 About alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1.2 MG alarm trigger mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1.2.1 ATCA line card extracted, locked or powered off . . . . . . . . . . . . . . . . . . . . 13 1.2.2 ATCA line card inserted, powered on or unlocked . . . . . . . . . . . . . . . . . . . 16 1.2.3 ATCA line card reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 1.2.4 Overheated event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 HARDWARE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 INFRASTRUCTURE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 SOFTWARE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 LINE AND PORT ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 SIGNALING ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 RESOURCE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 MGC10 SYNTHESIS ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
2 3 4 5 6 7 8
ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241 INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245
3 / 245
4 / 245
PREFACE
This dictionary dedicated to the Alcatel-Lucent 7570 Media Gateway (MG) describes all the alarms raised by the 7570. This guide applies to second Generation (2G) and third Generation (3G) networks. Information presented in this document applies to 7570 releases beginning with G3.1. You will find this guide helpful if you are involved in the 7570 alarm management. The 7570 alarm dictionary is organized in the following manner: Chapter 1 introduces the 7570 alarms displayed in the Alarm Management Graphical User Interface (GUI), and describes the alarm trigger mechanisms for the ATCA line cards. describes all alarms raised by the 7570 related to the hardware. You will find troubleshooting actions for each of these alarms. describes all alarms raised by the 7570 related to the infrastructure. You will find troubleshooting actions for each of these alarms. describes all alarms raised by the 7570 related to the software. You will find troubleshooting actions for each of these alarms. describes all alarms raised by the 7570 related to line and port. You will find troubleshooting actions for each of these alarms. describes all alarms raised by the 7570 signaling. You will find troubleshooting actions for each of these alarms. describes all alarms raised by the 7570 resources. You will find troubleshooting actions for each of these alarms. describes MGC10 synthesis alarms. You will find troubleshooting actions for each of these synthesis alarms. List of all abbreviations used in this document.
Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Abbreviations
Related documents Documents related to this dictionary include: - Alcatel-Lucent ATCA-based Platform, Alarm Management, Operator Guide, ALAMGT, - Alcatel-Lucent 7570 Media Gateway, 7570 Maintenance guide, BACKOPG, - Alcatel-Lucent 7570 Media Gateway, Hardware Management, 7570HWOPG, - Alcatel-Lucent 5020 MGC10, Operate alarms Operation and maintenance sheet, ALEXPL, - Alcatel-Lucent 5020 MGC10, Alarms Dictionary, ALA283.
5 / 245
Typographical conventions This guide uses the following typopgraphical conventions: - text in italics: document titles, - text in bold: important information.
Terminological conventions - Global System for Mobile communications (GSM), - General Packet Radio Service (GPRS), This guide uses acronyms developed from the English extended form when available. acronyms may be French-based when no English extended form exists. This guide uses: - 2G network (second-generation network) to indicate GSM networks, - BSS (Base Station Subsystem) to indicate the radio network subsystem that provides UE (User Equipment) with access to the PLMN in 2G networks, - 3G network (third-generation network) to indicate UMTS networks, - UTRAN (UMTS Terrestrial Radio Access Network) to indicate the terrestrial radio network that provides UE (User Equipment) with access to the PLMN in 3G networks, - UE (User Equipment) to indicate the subscriber terminal, regardless of whether the subscriber is in a 2G or a 3G network. Certain
6 / 245
1 ALARM OVERVIEW
This chapter introduces alarm basics and defines the types of information this guide provides to describe 7570 alarms.
7 / 245
1.1 About alarms

There are two basic alarm states: - raised alarms, which are notifications of a fault, - cleared alarms, which are notifications for which the problem that raised the alarm is no longer present.
Note:
Alarm Management enables you only to consult the list of raised alarms. The cause of the raised alarm must be corrected before the alarm is cleared automatically.
Once the cleared alarm notification has been generated, the raised alarm is deleted from the Current Alarms List. It is still available for consultation in the Historical Alarm List. This Alarm Dictionary describes each alarm according to the following scheme: - Alarm identification Managed Object Class (MOC), Alarm type, Probable cause, Specific problem, Severity, Additional text, Additional info, Threshold info. - Description Probable cause(s), Probable effects on system, Probable effects on service, Related alarms. - Corrective actions, On-site intervention required? Actions. Alarm Management enables you to display and work with alarm lists and subsets of the main alarm information, called sublists. Alarm records are stored in alarm lists and displayed according to the severity of the alarm condition. The alarm details are displayed in columns. Much of the information in the alarms corresponds to the International Telecommunication Union - Telecommunication standardization sector (ITU-T) X.733 Recommendation standard information elements. Table 1 gives a description of the fields used in the present guide as well as the correspondence between the Alarm Management GUI, this dictionary and the ITU-T X.733 Recommendation.
8 / 245
Table 1: Alarm dictionary information element Alarm Management GUI parameter
Alarm information elements Corresponding ITU-T X.733 alarm reporting parameter
Description
Alarm identification Managed Object None Class (MOC) Managed object Contains the alarm source identifier (NE type/Friendly Name) Identifies the type of alarm: - Quality of Service - Communications - Processing Error - Equipment - Environmental Probable cause Probable (Id) Cause Probable cause Indicates the probable cause of the alarm based on ITU-T Recommendation X.733. Identifies further refinements to the probable cause of the alarm Specific problems Specific Problems Specific problems Qualifies the chosen Probable Cause and may be used by the managed object class definer to specify a set of identifiers for use in managed object classes
Alarm type
Event Type
Event type
9 / 245
Alarm dictionary information element
Alarm Management GUI parameter
Corresponding ITU-T X.733 alarm reporting parameter
Description
Defines severity levels The levels defined for use with this mandatory parameter in the Alarm management GUI are: - Indeterminate: indicates that the severity level cannot be determined - Critical: indicates that a service affecting condition has occurred and an immediate corrective action is required - Major: indicates that a service affecting condition has developed and an urgent corrective action is required - Minor: indicates a non-service affecting fault condition and that corrective action is required to prevent a more serious (for example, service affecting) fault - Warning: indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action to further diagnose or correct the problem is required to prevent a more serious fault Additional text Alarm Description Additional text A free form text description of the alarm
Severity
Severity
Perceived severity
Additional info
Additional mation
Infor- Additional mation
A set of additional information in the event report. It consists of a series of data structures each of which infor- contains 3 items of information: - an identifier - a significance indicator - problem information
10 / 245
Corresponding ITU-T X.733 alarm reporting parameter
Description
Threshold info
Threshold Info
Threshold informa- triggered threshold tion - threshold level - observed value - arm time
This parameter is present when the alarm is a result of crossing a threshold. It consists of four subparameters:
None None None
Event Time Source Instance Source Type
Event time Source Source class Description
Contains the date and time at which the alarm was raised Contains the alarm source identifier Contains the alarm source type
Probable cause(s)
Probable (Name)
Cause
n.a.
Provides further information on the probable cause of the alarm Provides a description of any probable effects on operation of the system Provides a description of any probable effects on the quality of service provided by the telecommunication network Provides information about other alarms that may have been raised as a result of the raising of this alarm. Defines one or mores attributes of the managed object and the corresponding values at the time of the alarm
Probable effects on None system
n.a.
Probable effects on None service
n.a.
Related alarms
None
n.a.
None
Monitored tributes
At- Monitored tributes
at- Managed object definers may specify the set of attributes which are of interest, if any. This allows, for example, the timely reporting of changing conditions prevalent at the time of the alarm
Corrective actions
11 / 245
Corresponding ITU-T X.733 alarm reporting parameter n.a. n.a.
Description
On-site intervenNone tion required? Actions None
Contains an indication on whether on-site intervention is required to rectify the problem Contains a list of corrective actions
For more information about alarm management for: - Alcatel-Lucent ATCA-based Platform, refer to Alarm Management Operator guide, ALAMGT, - Alcatel-Lucent 5020 MGC10, refer to the Operate alarms Operation and maintenance sheet, ALEXPL.
12 / 245
1.2 MG alarm trigger mechanisms

The alarm trigger mechanisms for the ATCA line cards vary according to the following cases: - ATCA line card extracted or locked by the operator or powered off by the system, - ATCA line card inserted, powered on or unlocked, - ATCA line card reset, - overheated event. 1.2.1 ATCA line card extracted, locked or powered off When an ATCA line card is extracted or locked by the operator or powered off by the system defense, the operational state of the line card becomes "disabled" with reason "not present" or "locked" or "fault / powered off". The alarm trigger mechanisms depend on line card type.
13 / 245
If the line card is of type... TDMX or ATMX
then...
and if...
actions depend on previous op- the previous state(s) is: with the protection role: protec- erational state and protection - disabled state of protection card tion No action (alarm MG#20 "EPS protection lost" is already raised) - enabled-standby Minor alarm MG#20 "EPS protection lost" is raised - enabled-protecting 1) Protection mode of protection card becomes "standby" 2) Minor alarm MG#20 "EPS protection lost" is raised 3) Protection mode of related working card becomes "active". According to the previous operational state of related working card: working card enabled: EPS forces a switch back (protection card functions switch over to working card) working card disabled: critical alarm MG#21 "Card activity lost" is raised referencing the working card
14 / 245
then...
and if...
- major alarm MG#1 "Pro- the previous state is: tected line card out of serworking card belonging to a - enabled-active vice" is raised protection group If EPS activation is possible: - actions depend on previous 1) EPS forces a switchover operational state and pro(working card functection state of working card tions switch over to protection card) 2) Minor alarm MG#20 "EPS protection lost" is raised 3) Protection state of working card becomes "spared" 4) Protection state of related protection card becomes "protecting" If EPS activation is not possible: 1) Critical alarm MG#21 "Card activity lost" is raised - enabled-spared If protection group has type 1:1 EPS/APS coupled, the minor alarm MG#20 "EPS protection lost" is raised (switch back not required for card protection group 1:1 EPS/APS coupled) - other state values No action
15 / 245
then...
and if...
critical alarm MG#2 "Unproand the working card does not tected line card out of service" belong to a card protection is raised group VPP or IPGE card actions depend on number of number of ports is: ports in an operational state Note: VPP and IPGE cards are - equal to 1 "disabled" implictly in load sharing mode 1) Major alarm Loss of extra (1) VPP/IP resource" (MG#160/MG#161) is raised - greater than 1 1) major alarm Loss of extra VPP/IP resource" is cleared (MG#160/MG#161) 2) critical alarm Loss of extra VPP/IP resources" (MG#160/MG#161) is raised 1.2.2 ATCA line card inserted, powered on or unlocked When an ATCA line card is inserted, powered on or unlocked, its operational state becomes "enabled". The alarm trigger mechanisms depend on line card type.
16 / 245
then...
and if...
major alarm MG#1 "Protected - a working card of this protection group (1:N or 1:1 with the protection role: protec- line card out of service" is EPS/APS coupled) is "discleared tion abled" (if more than one card is "disabled alarm indicates card on lowest shelf): 1) EPS forces a switchover (related working card functions switch over to protection card) 2) Critical alarm MG#21 "Card activity lost" related to working card is cleared 3) Protection state of working card becomes "spared" 4) Protection role of protection card becomes "protecting" - a working card of this protection group is "enabled": 1) Minor alarm MG#20 "EPS protection lost" is cleared 2) Protection mode of Protection card becomes stand-by TDMX or ATMX major alarm MG#1 "Protected - protection mode of working card is "active" working card belonging to a line card out of service" is cleared card protection group - critical alarm MG#21 "Card activity lost" is cleared - protection group has type 1:1 EPS/APS coupled, and if protection card is enabled, the minor alarm MG#20 "EPS protection lost" is cleared (switch back not required for card protection group 1:1 EPS/APS coupled)
17 / 245
then...
and if...
critical alarm MG#2 "Unproand the working card does not tected line card out of service" belong to a card protection is cleared group VPP or IPGE card actions depend on number of number of ports is: ports in an operational state - equal to 0 "disabled" 1) Major alarm Loss of extra (1) VPP/IP resource" (MG#160/MG#161) is cleared - equal to 1 1) critical alarm Loss of extra VPP/IP resource" is cleared (MG#160/MG#161) 2) major alarm Loss of extra VPP/IP resources" (MG#160/MG#161) is raised - greater than 1 No action 1.2.3 ATCA line card reset When an ATCA line card is reset, no alarm is raised or cleared 1.2.4 Overheated event When an overheated event occurs, the actions depend on the notified event. If the notified overheated event is... no more overheating minor overheating major overheating then... MG#3 minor alarm "Minor line card failure" is cleared (if necessary) MG#3 minor alarm "Minor line card failure" is raised the line card is powered off by system defense (see section 1.2.1)
critical overheating
18 / 245
2 HARDWARE ALARMS
This section provides all information related to the hardware alarms.
19 / 245
GHM#500 - Check Configuration error Alarm identification Managed Object System Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Processing error Configuration or customization error None Warning Check Configuration error None Not applicable Description Probable cause(s) The hardware configuration data is in conflict with the data After a system installation, upgrade or a power shortage (that damaged a cards flash memory), the card is redundant or presents an incorrect ID, or an incorrect MIB version Probable on system Probable on service effects Equipment services are unavailable effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Check that the MIB version number is the same as the version number specified on the software delivery certificate. 2. Check that the chassis card configuration corresponds to the chassis equipment list. 3. Replace the faulty element according to replacement procedures. Contact Alcatel-Lucent TASC before any hardware replacement
20 / 245
GHM#501 - Temperature crosses warning threshold Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Temperature unacceptable None Warning Temperature crosses warning threshold The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Hardware or environmental warning. The temperature is over the warning threshold for one of the following units: a) card CPU b) card Rear Transition Module c) card d) hard disk drive e) Mass Storage Module f) disk drive g) power unit h) Fan The room or chassis air conditioning unit is defective, or the unit overheats Probable on system Probable on service effects Cards can be damaged very quickly if the chassis temperature is not controlled effects No - GHM#504 - Failure of a chassis fan - GHM#505 - Failure of all chassis fans Corrective actions
Related alarms
21 / 245
GHM#501 - Temperature crosses warning threshold On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm Contact Alcatel-Lucent TASC before any hardware replacement 1. Check if there are other alarms that could explain the rise in temperature, especially fan alarms. 2. If there are, troubleshoot these alarms first. 3. Check that the room air conditioning system is operating properly. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
22 / 245
GHM#502 - Temperature crosses minor threshold Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Temperature unacceptable None Minor Temperature crosses minor threshold The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Hardware or environmental non-fatal alarm. The unit temperature is over the minor threshold. The station is still running The room or chassis air conditioning unit is defective, or the unit overheats Probable on system Probable on service effects Cards can be damaged very quickly if the chassis temperature is not controlled effects Yes - GHM#504 - Failure of a chassis fan - GHM#505 - Failure of all chassis fans Corrective actions
Related alarms
23 / 245
GHM#502 - Temperature crosses minor threshold On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Check if there are other alarms that could explain the rise in temperature, especially fan alarms. 2. If there are, troubleshoot these alarms first. 3. Check that the room air conditioning system is operating properly. 4. Check that the fan units of the suspect chassis are operating correctly. If they are not, replace the fan units according to the replacement procedure. 5. If fans are operating properly and if there is no other alarm, replace faulty FRU according to the appropriate replacement procedure. 6. If the problem persists, contact Alcatel-Lucent TASC. 7. End.
24 / 245
GHM#503 - Temperature crosses major threshold Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Temperature unacceptable None Major Temperature crosses major threshold The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Hardware or environmental fatal alarm. Temperature of the unit is over the major threshold. The card is powered off The room or chassis air conditioning unit is defective, or the unit overheats Probable on system Probable on service effects The station has stopped. High Availability functionality is reduced effects Yes - GHM#504 - Failure of a chassis fan - GHM#505 - Failure of all chassis fans Corrective actions
Related alarms
25 / 245
GHM#503 - Temperature crosses major threshold On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Check if there are other alarms that could explain the rise in temperature, especially fan alarms. 2. If there are, troubleshoot these alarms first. 3. Check that the room air conditioning system is operating properly. 4. Check that the fan units of the suspect chassis are operating correctly. If they are not, replace the fan units according to the replacement procedure. 5. If fans are operating properly and if there is no other alarm, replace faulty FRU according to the appropriate replacement procedure. 6. If the problem persists, contact Alcatel-Lucent TASC. 7. End.
26 / 245
GHM#504 - One Chassis fan failure Alarm identification Managed Object Fan Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Heating/ventilation/cooling None Minor One Chassis fan failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system One of the chassis fan units has failed. The platform is still running
effects Cards can be damaged very quickly if the chassis temperature is not controlled Warning: Corrective action must be taken to avoid damage to system components. Cards can be damaged if ventilation is stopped for more than one minute
Probable on service
effects Yes None Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Replace the faulty fan unit according to the appropriate replacement procedure.
27 / 245
GHM#505 - All Chassis fans failure Alarm identification Managed Object Chassis Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Heating/ventilation/cooling None Critical All Chassis fans failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service All fans in a chassis have failed. The chassis has been powered off
effects The chassis is powered off and all applications on the chassis are stopped effects Yes - GHM#504 - Failure of a chassis fan Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Replace the fan units according to the appropriate replacement procedure before powering on the station.
28 / 245
GHM#506 - One Chassis Power Unit failure Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Power problem None Minor One Chassis Power Unit failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service One of the two redundant power units or one of the two power distribution units has failed
effects None. The chassis is still running effects No - GHM#507 - Failure of all power entries of a chassis Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform each of the following actions in the given order.. Continue to the next action only if the system does not clear the alarm 1. Check the top rack power distribution units LED and circuit breakers. (see your rack documentation). 2. Replace the faulty power supply according to the appropriate replacement procedure. 3. If the problem persists, contact Alcatel-Lucent TASC. 4. End.
29 / 245
GHM#507 - All Chassis Power Units failure Alarm identification Managed Object Chassis Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Power problem None Critical All Chassis Power Units failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service All power units in the chassis have failed
effects The chassis is powered off. All applications on the chassis are stopped effects Yes - GHM#506 - Failure of a chassis power entry module Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform each of the following actions in the given order.. Continue to the next action only if the system does not clear the alarm 1. Check the top rack power distribution units LED and circuit breakers. (see your rack documentation). 2. Replace the faulty power supply according to the appropriate replacement procedure. 3. If the problem persists, contact Alcatel-Lucent TASC. 4. End.
30 / 245
GHM#508 - Board voltage out of range Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Power problem None Critical Board voltage out of range The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Card voltage is out of range (5V, 3.3V, 12V). It may be the CPU voltage or card voltage The card itself or its power supply unit can be the cause of the alarm. Probable on system Probable on service effects The station is powered off. All applications running on the faulty station are stopped effects Yes - GHM#506 - Failure of a chassis power entry module Corrective actions
Related alarms
31 / 245
GHM#508 - Board voltage out of range On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Check if all the cards in the chassis have sent the same alarm. If this is the case, replace the power supply unit(s) according to the appropriate replacement procedure. 2. Replace the faulty card according to the appropriate replacement procedure. 3. Replace the IU (Interface Unit), located behind the faulty card, according to the appropriate replacement procedure. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
32 / 245
GHM#509 - ShMC Access Problem Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Communications subsystem failure None Major ShMC Access Problem The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service Access to equipment via the Shelf Management Controller is not possible
effects None. The chassis is still running. Nevertheless the availability is downgraded effects No - GHM#518 - Card failure Corrective actions
Related alarms
33 / 245
GHM#509 - ShMC Access Problem On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. If the alarm originates from only one card: that card is defective. Replace the faulty card according to the appropriate replacement procedure. 2. If the alarm originates from all cards in the chassis except one: that card is defective. Replace the faulty card according to the appropriate replacement procedure. 3. If the alarm originates from all cards in the chassis, apply the following procedure to each card in the chassis in the following order: fans, SHMC cards, COAL cards, CPU cards, PEM. 4. a) Remove the card from the chassis, b) If the alarm disappears within 1 minute, that card is defective. Replace the faulty card according to the appropriate remplacement procedure. The procedure is now terminated. c) If the alarm does not disappear, re-insert the card removed in step a, and repeat step a with the next card. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
34 / 245
GHM#510 - Station unreachable through LSN Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication LAN error None Major Station unreachable through LSN The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Access to the station through both Ethernet switches and local subnetwork (LSN) is not possible Any element in the Ethernet path to the station can be the cause. Probable on system Probable on service effects Station services are unavailable effects Yes - GHM#518 - Card failure - GHM#524 - Minor LSN access problem Corrective actions
Related alarms
35 / 245
GHM#510 - Station unreachable through LSN On-site interven- Yes tion required? Actions Perform each of the following actions in the given order.. Continue to the next action only if the system does not clear the alarm. If there is no other alarm on the station (or switch) and if the station does not initialize, perform the following actions: 1. If in a multi-rack configuration, check cables and plug connections along the Ethernet path to the station. If necessary, replace faulty cables. 2. Verify that the suspected card works properly. If necessary, replace the card according to the appropriate replacement procedure. 3. Check the corresponding IU. 4. Check the Ethernet switch. If necessary, replace the switch according to the appropriate replacement procedure. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
36 / 245
GHM#511 - Loss of contact Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Sofware program abnormally terminated None Major Loss of contact The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Contact with a remote station has been lost. This can happen if the station has been reset by a defense action taken by the control station software, or the software on the station causes the reset, or the station has failed
Probable on system Probable on service
effects There is no contact with the station. Station applications are unavailable effects Yes - GHM#519 - Fatal ethernet switch error Corrective actions
Related alarms
37 / 245
GHM#511 - Loss of contact On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Allow 10 to 15 minutes for the station to restart automaticaly 2. Replace the faulty station card according to the appropriate replacement procedure. 3. Allow 10 to 15 minutes for the station to restart automatically. 4. If there is still an alarm, replace the station card Interface Unit. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
38 / 245
GHM#512 - SW Version not compatible with MIB Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Processing error Version mismatch None Critical SW Version not compatible with MIB The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Initialization error. The software version is incompatible with information in the MIB (Management Information Base) As a result of a system installation, upgrade, or power shortage, a card is redundant or presents an incorrect ID, or has an incorrect MIB version Probable on system Probable on service effects Station services are unavailable effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
39 / 245
GHM#512 - SW Version not compatible with MIB On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Check that the MIB version is the same as the version number on the software delivery certificate. 2. Verify that the chassis card configuration corresponds to the chassis shipping list. 3. Replace the faulty element according to the replacement procedure. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
40 / 245
GHM#513 - Unrecoverable software error Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Processing error Sofware error None Critical Unrecoverable software error The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service The software has crashed
effects Station services are unavailable effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
On-site interven- No tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Wait about 15 minutes for an automatic reinitialization. 2. Re-initialize the faulty unit (this may take up to 15 minutes). 3. Replace the faulty unit according to the appropriate replacement procedure. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
41 / 245
GHM#514 - Local Disk I/O device error Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment I/O device error None Major Local Disk I/O device error The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Fatal hardware error. Local I/O error Internal disk error in the control station. Probable on system Probable on service effects Control station services are unavailable for this station. A switchover has occurred if it was the active station. If it is the standby station, the switchover is impossible. System redundancy is reduced effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Replace the suspect control station (without the Interface Unit) according to the appropriate replacement procedure
42 / 245
GHM#515 - MSM Disk I/O device error Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment I/O device error None Major MSM Disk I/O device error The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) MSM (Mass Storage Module) disk error Device disk error or linkage error (SCSI, Fiber channel, etc). Probable on system effects The related control station managing the faulty MSM switched automatically to stop standby mode. Control station services are unavailable for this station. A switchover has occurred if it was the active station. If it is the standby station, the switchover is impossible. System redundancy is reduced effects Yes - GHM#518 - Card failure Corrective actions
Probable on service
Related alarms
43 / 245
GHM#515 - MSM Disk I/O device error On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Replace the faulty MSM card according to the appropriate device replacement procedure. 2. Replace the control station card Interface cable according to the appropriate replacement procedure. 3. If the alarm condition is still present, replace the chassis. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
44 / 245
GHM#516 - Hardware Fatal Error Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Critical Hardware Fatal Error The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service Hardware Fatal Error
effects Card applications are stopped effects Yes - GHM#504 - Failure of a chassis fan - GHM#505 - Failure of all chassis fans Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Check if there are other current alarms. Troubleshoot these alarms. 2. If necessary, replace the faulty card according to the appropriate replacement procedure. 3. If the problem persists, contact Alcatel-Lucent TASC. 4. End.
45 / 245
GHM#517 - PMC Access Failure Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Adapter error None Major PMC Access Failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service Hardware error on a PMC (PCI Mezzanine Card)
effects Card services are unavailable effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. Check if there are other current alarms ( SS7 Alarms). Troubleshoot these alarms. 2. If necessary, replace defective card according to the appropriate replacement procedure. 3. If the problem persists, contact Alcatel-Lucent TASC. 4. End.
46 / 245
GHM#518 - Card failure Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Major Card failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) The chassis has detected a defect on a card Possible cause(s) include: a) BIOS startup test error b) Test Program error c) Physical sensor error d) card memory error (ECC non recoverable, scrubbing error, etc.) e) card watchdog f) MSM sensor error g) Power unit Status error h) Incoherent geographical addresses (different geographical addresses in the same chassis, or identical geographical addresses across different chassis) i) IPMB communication error (card Baseboard Management Controller, backplane, IPMC on FRU). Probable on system Probable on service effects Card services are unavailable effects Yes None
Related alarms
47 / 245
GHM#518 - Card failure Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. In case of a geographical address error, check the micro switch settings on the configuration and alarm card. 2. If the alarm condition continues, replace the card that does not answer to the Hardware Management GUI according to the appropriate replacement procedure. 3. If there is no other current alarm on the same chassis, replace the suspected card according to the appropriate replacement procedure. 4. Check each of the possible causes with the Hardware Management GUI. Replace the suspected card according to the appropriate replacement procedure. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
48 / 245
GHM#519 - Ethernet switch fatal error Alarm identification Managed Object LAN Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment LAN error None Major Ethernet switch fatal error The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) The Ethernet switch is not accessible The Ethernet switch is disconnected or out of service Probable on system Probable on service effects Network operation is affected effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. In a multi-rack configuration, check the switch cables and power supply. 2. Reset the switch. 3. Replace the switch according to the appropriate procedure. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
49 / 245
GHM#520 - Router communication failure Alarm identification Managed Object Router Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Communications subsystem failure None Major Router communication failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Remote equipment is unreachable The router is disconnected or out of service Probable on system Probable on service effects Network operation is affected effects Yes - GHM#519 - Fatal ethernet switch error Corrective actions
Related alarms
50 / 245
GHM#520 - Router communication failure On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. If there are other related alarms, troubleshoot these alarms before proceeding. 2. Check router cables and power supply. 3. Reset the router. 4. Replace the router according to the appropriate procedure. 5. Reset the router. 6. Replace the switch according to the appropriate procedure. 7. If the problem persists, contact Alcatel-Lucent TASC. 8. End.
51 / 245
GHM#521 - Minor Router Path failure Alarm identification Managed Object Router Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Equipment malfunction None Minor Minor Router Path failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) One of the routers two Ethernet links is down The switch or router is disconnected, off or out of service Probable on system Probable on service effects Network operation is affected effects Yes - GHM#520 - Router communication failure Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. If there are other current alarms, troubleshoot these first. 2. Check router and switch cables and power supply. 3. Reset the router or the switch 4. Replace the router or the switch according to the appropriate procedure. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
52 / 245
GHM#522 - Major Router Path failure Alarm identification Managed Object Router Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Equipment malfunction None Major Major Router Path failure The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) The Ethernet links are down on both routers The router or switch is disconnected, off or out of service Probable on system Probable on service effects Network operation is affected effects Yes - GHM#520 - Router communication failure Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. If there are current related alarms, troubleshoot these first. 2. Check router and switch cables and power supply. 3. Reset the router(s) or the switch. 4. Replace the router(s) or switch according to the appropriate procedure(s). 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
53 / 245
GHM#523 - Both ShMC Access Problem Alarm identification Managed Object Card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Communications subsystem failure None Critical Both ShMC Access Problem The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Access to equipment via the Shelf Management Controller is not possible Both Shelf Management cards are unreachable through Ethernet Probable on system Probable on service effects No hardware management action is possible on the chassis effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
54 / 245
GHM#523 - Both ShMC Access Problem On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm 1. If the alarm originates from only one card: that card is defective. Replace the faulty card according to the appropriate replacement procedure. 2. If the alarm originates from all cards in the chassis except one: that card is defective. Replace the faulty card according to the appropriate replacement procedure. 3. If the alarm originates from all cards in the chassis, apply the following procedure to each card in the chassis in the following order: fans, SHMC cards, COAL cards, CPU cards, PEM. 4. a) Remove the card from the chassis, b) If the alarm disappears within 1 minute, that card is defective. Replace the faulty card according to the appropriate remplacement procedure. The procedure is now terminated. c) If the alarm does not disappear, re-insert the card removed in step a, and repeat step a with the next card. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
55 / 245
GHM#524 - One LSN access of the station is out of service Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication LAN error None Minor One LSN access of the station is out of service The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Access to the station through one Ethernet switch and LSN is not possible Any element on the Ethernet path to the station can be the cause Probable on system Probable on service effects Station services are degraded effects No - GHM#518 - Card failure Corrective actions
Related alarms
56 / 245
GHM#524 - One LSN access of the station is out of service On-site interven- Yes tion required? Actions Perform each of the following actions in the given order. Continue to the next action only if the system does not clear the alarm If there is no other alarm on the station (or switch) and if the station does not initialize, perform the following actions: 1. In a multi-rack configuration, check cables and plug connections along the Ethernet path to the station. If necessary, replace faulty cables. 2. Verify that the suspected card works properly. If necessary, replace the card according to the appropriate replacement procedure. 3. Check the corresponding IU. 4. Check the Ethernet switch. If necessary, replace the switch according to the appropriate replacement procedure. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
57 / 245
GHM#528 - Initializing error Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Processing error Equipment malfunction None Warning Initializing error The station did not succeed to boot during platform restart. Not applicable Description Probable cause(s) Probable on system Probable on service Board error
effects Station services are unavailable. effects Yes - GHM#518 - Card failure Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm: 1. Wait about 15 minutes for an automatic reinitialization. 2. Re-initialize the faulty unit (this may take up to 15 minutes). 3. Depending on the application, restart the platform to put the station into service. 4. If necessary, replace the faulty unit according to the appropriate replacement procedure. 5. If the problem persists, contact Alcatel-Lucent TASC. 6. End.
58 / 245
GHM#529 - One LANIO access of the station is out of service Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication LAN error None Minor One LANIO access of the station is out of service The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Access to the station through one Ethernet switch and external subnetwork (LANIO) is not possible Any element on the Ethernet path to the station can be the cause. Probable on system Probable on service effects Station services are degraded effects No - GHM#530 - Major LANIO access problem Corrective actions
Related alarms
59 / 245
GHM#529 - One LANIO access of the station is out of service On-site interven- Yes tion required? Actions Perform each of the following actions in the given order. Continue to the next action only if the system does not clear the alarm If there is no other alarm on the station, perform the following actions: 1. Check cables and plug connections along the Ethernet path to the station. If necessary, replace faulty cables. 2. Verify that the suspected card works properly. If necessary, replace the card according to the appropriate replacement procedure. 3. Check the corresponding IU. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
60 / 245
GHM#530 - All configured LANIO access of the station are out of service Alarm identification Managed Object Station Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication LAN error None Major All configured LANIO access of the station are out of service The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use this information to retrieve the object by its name in the Hardware Management GUI. Threshold Info Not applicable Description Probable cause(s) Access to the station through one Ethernet switch and external subnetwork (LANIO) is not possible Any element in the Ethernet path to the station can be the cause. Probable on system Probable on service effects Station services are degraded effects No - GHM#529 - Minor LANIO access problem Corrective actions
Related alarms
61 / 245
GHM#530 - All configured LANIO access of the station are out of service On-site interven- Yes tion required? Actions Perform each of the following actions in the given order. Continue to the next action only if the system does not clear the alarm If there is no other alarm on the station, perform the following actions: 1. Check cables and plug connections along the Ethernet path to the station. If necessary, replace faulty cables. 2. Verify that the suspected card works properly. If necessary, replace the card according to the appropriate replacement procedure. 3. Check the corresponding IU. 4. If the problem persists, contact Alcatel-Lucent TASC. 5. End.
62 / 245
MG#1 - Protected line card out of service Alarm identification Managed Object ATCA_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Major Protected line card out of service [ Location of the faulty ATCA card (Shelf/Slot) ] [ Cause of outage ]: 1 = Background DIAG 2 = Directed DIAG 3 = Startup DIAG 4 = Boot 5 = Firmware 6 = Fabric ethernet link 7 = Base ethernet link 8 = NE1oE supervision 9 = Card unreachable 10 = RTM failure DIAG 11 = RTM mismatch DIAG 12 = RTM not present DIAG 13 = Wrong card type 14 = Major overheated DIAG 16 = Critical overheated DIAG 17 = TCP socket failure 18 = Card locked 0 = Other Threshold Info Not applicable Description
63 / 245
MG#1 - Protected line card out of service Probable cause(s) This alarm is raised when a line card which belongs to a card protection group becomes out of service: the card was either locked or extracted by the operator or detected in failure by the system The cause of outage is indicated in section additional info When alarm is raised with cause of outage "Card locked", that means that no failure is detected by system: you only need to unlock the card to clear this alarm Probable on system effects In case of card failure, a "power-off" is automatically generated for the line card In all cases (failure, extract, lock), card services become unavailable (all associated established calls are lost) All alarms associated with elements (ports, lines, etc.) of the line card are automatically cleared Automatic actions then depend on the card protection mode: * Protection mode 1:1 active/standby coupled APS: If conditions required for EPS are satisfied, card services are automatically reconfigured on associated card. An alarm is raised if EPS is not possible. * Protection mode 1:N active/standby: If conditions required for EPS are satisfied, card services are automatically reconfigured on associated card. An alarm is raised if EPS is not possible. An alarm is raised if EPS protection is lost. * Protection mode 1+N load sharing (case of VPP and IPGE line cards): New traffic is shared on operational cards. An alarm is raised to inform operator that resource(s) of associated function are lost. Probable on service effects Yes - MG#20 - EPS protection lost - MG#21 - Card activity lost - MG#160 - Loss of extra (1) VPP resources - MG#161 - Loss of extra (1) IP resources - MG#162 - Loss of several VPP resources - MG#163 - Loss of several IP resources Corrective actions
Related alarms
64 / 245
MG#1 - Protected line card out of service On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If necessary, replace or insert the card according to the appropriate procedure. 2. If necessary, unlock the card. Card operational states must become "enabled". 3. Check if related alarms (if they are still present) are justified. 4. If protection state of card is "spared", activate a "manual switch" command. Protection state of card must become "active". 5. If necessary, send the faulty card to the repair service. 6. End.
65 / 245
MG#2 - Unprotected line card out of service Alarm identification Managed Object ATCA_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Critical Unprotected line card out of service [ Location of the faulty ATCA card (Shelf/Slot) ] [ Cause of outage ]: 1 = Background DIAG 2 = Directed DIAG 3 = Startup DIAG 4 = Boot 5 = Firmware 6 = Fabric ethernet link 7 = Base ethernet link 8 = NE1oE supervision 9 = Card unreachable 10 = RTM failure DIAG 11 = RTM mismatch DIAG 12 = RTM not present DIAG 13 = Wrong card type 14 = Major overheated DIAG 16 = Critical overheated DIAG 17 = TCP socket failure 18 = Card locked 0 = Other Threshold Info Not applicable Description
66 / 245
MG#2 - Unprotected line card out of service Probable cause(s) This alarm is raised when a line card which doesnt belong to a card protection group becomes out of service: the card was either locked or extracted by the operator or detected in failure by the system The cause of outage is indicated in section additional info When alarm is raised with cause of outage "Card locked", that means that no failure is detected by system: you only need to unlock the card to clear this alarm Probable on system effects In case of card failure, a "power-off" is automatically generated for the line card In all cases (failure, extract, lock), card services become unavailable (all associated established calls are lost) All alarms associated with elements (ports, lines, etc.) of the line card are automatically cleared Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If necessary, replace or insert the card according to the appropriate procedure. 2. If necessary, unlock the card. Card operational states must become "enabled". 3. Check if related alarms (if they are still present) are justified. 4. If necessary, send the faulty card to the repair service. 5. End.
Related alarms
67 / 245
MG#3 - Minor line card failure Alarm identification Managed Object ATCA_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Minor Minor line card failure [ Location of the faulty ATCA card (Shelf/Slot) ] [ Cause of outage ]: 1 = Background DIAG 2 = Directed DIAG 3 = Startup DIAG 15 = Minor overheated DIAG 0 = Other Threshold Info The value of counter has crossed the % lower threshold . The alarm will disappear if the value of counter crosses the % upper threshold . Description Probable cause(s) This alarm is raised when a minor failure probably due to hardware is detected on a line card Types of failure are indicated in section additional info Probable on system Probable on service effects No effect because card remains operational effects No None Corrective actions
Related alarms
68 / 245
MG#3 - Minor line card failure On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If protection state of card is "active", activate a "manual switch" command. Protection state of card must become "spared". 2. Lock the card. The system must clear the alarm. 3. Replace the card according to the appropriate procedure. 4. Unlock the card. Card operational states must become "enabled". 5. If protection state of card is "spared", activate a "manual switch" command. Protection state of card must become "active". 6. Send the faulty card to the repair service. 7. End.
69 / 245
MG#10 - LIU shelf activity lost Alarm identification Managed Object LIU_shelf Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Communications subsystem failure None Critical LIU shelf activity lost [ LIU shelf number (Shelf) ] [ Cause of outage MUX A ] Possible causes by decreasing priority of display are: 1 - MUX card locked 2 - MUX card unreachable 3 - Wrong card type 4 - Synchronization failure 5 - Traffic not operational on first Ge link 6 - Traffic not operational on second Ge link 7 - First Ge link connected to a wrong ATCA switch card 8 - Second Ge link not connected or connected to a wrong ATCA switch card [ Cause of outage MUX B ] same possible causes as above Threshold Info Not applicable Description Probable cause(s) This alarm is raised when operational state of the two MUX cards is disabled This alarm is cleared when operational state of at least one MUX card is enabled Probable on system Probable on service effects LIU services become unavailable effects Yes None Corrective actions
Related alarms
70 / 245
MG#10 - LIU shelf activity lost On-site interven- Yes tion required? Actions Perform the following actions in the given order and continue to the next action if the system doesnt clear the alarm: 1. Check if MUX cards are correctly inserted into this LIU shelf. 2. Check if Ethernet links related to MUX cards are correctly linked to MUX and ATCA switch cards. 3. Lock and unlock MUX cards and verify if alarm is cleared. 4. Replace one MUX card according to the appropriate procedure and verify if alarm is cleared when this MUX card is unlocked. If the alarm is cleared, replace the other MUX card, unlock it and send the faulty cards to the repair service. 5. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center (failure is perhaps due to LIU shelf). 6. End.
71 / 245
MG#11 - LIU shelf number configuration error Alarm identification Managed Object LIU_shelf Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Processing error Configuration or customization error None Critical LIU shelf number configuration error [ LIU shelf number (Shelf) ] Not applicable Description Probable cause(s) This alarm is raised if MUX cards are detected with the same identity (same slot and same LIU number) This alarm is cleared if no MUX cards are detected with the same identity (same slot and same LIU number) Probable on system effects Services related to the first MUX cards detected on this LIU remain available Services related to the other MUX cards detected on wrong numbered LIU are unavailable effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Modify the LIU number (micro-switch) of the faulty LIU shelf and reinitialize this LIU shelf. 2. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 3. End.
Probable on service
Related alarms
72 / 245
MG#12 - LIU shelf number unknown Alarm identification Managed Object LIU_shelf Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Processing error Configuration or customization error None Minor LIU shelf number unknown [ LIU shelf number (Shelf) ] Not applicable Description Probable cause(s) This alarm is raised if a MUX card related to this LIU shelf not created is detected This alarm is cleared if no MUX card related to this LIU shelf not created is detected Probable on system Probable on service effects LIU services of this wrong numbered LIU shelf are unavailable effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If LIU shelf is not created, create it. 2. If LIU shelf is wrong numbered, modify its LIU number (micro-switch) and reinitialize it. 3. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 4. End.
Related alarms
73 / 245
MG#13 - MUX card out of service Alarm identification Managed Object LIU_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Major MUX card out of service [ Location of the faulty MUX card (Shelf/Slot) ] [ Cause of outage ] Possible causes by decreasing priority of display are: 1 - MUX card locked 2 - MUX card unreachable 3 - Wrong card type 4 - Synchronization failure 5 - Traffic not operational on first Ge link 6 - Traffic not operational on second Ge link 7 - First Ge link connected to a wrong switch card 8 - Second Ge link not connected or connected to a wrong switch card Threshold Info Not applicable Description Probable cause(s) This alarm is raised if operational state of the MUX card is disabled This alarm is cleared if operational state of the MUX card is enabled Probable on system effects No effect on system because the redundant MUX card is necessarily enabled When all MUX cards on an LIU shelf are disabled, alarm GW#10 is raised and alarm GW#13 is cleared effects Yes None Corrective actions
Probable on service
Related alarms
74 / 245
MG#13 - MUX card out of service On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If the MUX card is locked, unlock it. 2. If the MUX card is failed, replace it according to the appropriate procedure. 3. If the MUX card is incorrectly connected, check if associated Ethernet link(s) is (are) correctly linked to the MUX and to ATCA switch cards 4. Verify that operational state of this MUX card becomes "enabled". 5. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 6. End.
75 / 245
MG#14 - LIU card out of service Alarm identification Managed Object LIU_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Major LIU card out of service [ Location of the faulty LIU card (Shelf/Slot) ] [ Cause of outage ] Possible causes by decreasing priority of display are: 1 - Card locked 2 - Shelf unreachable 3 - Card not present 4 - Card unreachable 5 - Wrong card type 6 - Wrong card variant Threshold Info Not applicable Description Probable cause(s) This alarm is raised if operational state of the LIU card is disabled This alarm is cleared if operational state of the LIU card is enabled Probable on system effects If the type of LIU card is E1/T1, the activity related to these E1/T1 is lost If the type of LIU card is STM-1 TDM/ATM, the activity related to this STM-1 card is lost (see alarm MG#22) or taken over by the related APS LIU card effects Yes None Corrective actions
Probable on service
Related alarms
76 / 245
MG#14 - LIU card out of service On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If the card is locked, unlock it. 2. If the card is failed, replace it according to the appropriate procedure. 3. Card operational state must become "enabled". 4. End.
77 / 245
MG#15 - PEM card out of service Alarm identification Managed Object LIU_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Major PEM card out of service [ Location of the faulty PEM card (Shelf/Slot) ] [ Cause of outage ] Possible causes by decreasing priority of display are: 1 - Card not present 2 - Wrong card type 3 - Tertiary voltage failure 4 - Card overheating Threshold Info Not applicable Description Probable cause(s) This alarm is raised if the system detects a PEM failure This alarm is cleared if the system no longer detects any PEM failure Probable on system Probable on service effects No effect due to PEM cards redundancy effects No None Corrective actions On-site interven- Yes tion required? Actions Replace the PEM card according to the appropriate procedure.
Related alarms
78 / 245
MG#16 - LIU shelf 48V redundancy failure Alarm identification Managed Object LIU_shelf Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Major LIU shelf 48V redundancy failure [ LIU shelf number (Shelf) ] Not applicable Description Probable cause(s) This alarm is raised if the system detects an LIU shelf 48V redundancy failure This alarm is raised if the system no longer detects any LIU shelf 48V redundancy failure Probable on system Probable on service effects No effect due to 48V redundancy effects No None Corrective actions On-site interven- Yes tion required? Actions Locate the failure and repair faulty element(s).
Related alarms
79 / 245
MG#17 - Firmware upgrade required Alarm identification Managed Object LIU_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Configuration or customization error None Major Firmware upgrade required Shelf and slot number of the faulty LIU card Not applicable Description Probable cause(s) Probable on system The current version available on the flash memory is different from the one available in the 7570 Vn set, on the disk of the Control station
effects The faulty LIU card is working with a firmware version different from the reference firmware on the disk of the Control station Quality of service may be affected
Probable on service
Related alarms
80 / 245
MG#17 - Firmware upgrade required On-site interven- No tion required? Actions If the faulty LIU card is a GMUX: 1. Place the GMUX board in standby mode (force a switchover if necessary). 2. Check there is no incidence on traffic. 3. From the Hardware management GUI, upgrade the firmware of the card: a) Display the caracteristics of the card. b) Click the "SW/FW Version" tab. c) Click the "Upgrade" button. A pop-up window indicates "OK" after 8 mn. d) Click "YES_reset". 4. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. If the faulty LIU card is a JBSS1 without APS protection: 1. From the Hardware management GUI, upgrade the firmware of the card: a) Display the caracteristics of the card. b) Click the "SW/FW Version" tab. c) Click the "Upgrade" button. A pop-up window indicate "OK" after 40 seconds. d) Click "YES_reset". e) Verify that operational state of this JBSS1 card becomes "active" after upgrade. f) If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. If the faulty LIU card is a JBSS1 with APS protection: 1. Place the STM-1 line of the faulty JBSS1 card in standby mode by locking the STM-1 line. 2. From the Hardware management GUI, upgrade the firmware of the card: a) Display the caracteristics of the card. b) Click the "SW/FW Version" tab. c) Click the "Upgrade" button. A pop-up window indicate "OK" after 40 seconds. d) Click "YES_reset". 3. unlock the STM-1 line. 4. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center.
81 / 245
MG#20 - EPS protection lost Alarm identification Managed Object EPS_group Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Minor EPS protection lost [ Protection reference group (EPS_ref) ] Not applicable Description Probable cause(s) Probable on system This alarm is raised when operational state of a protection card becomes "disabled"
effects EPS protection is lost for line cards belonging to this card protection group No effect on system as long as the line cards belonging to this card protection group remain operational effects No - MG#1 - Protected line card out of service Corrective actions
Probable on service
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Retrieve protection card references from EPS reference. 2. Retrieve protection card state. 3. If protection card state is disabled for reason "locked", unlock protection card. 4. If protection card state is disabled for reason "failure", see the troubleshooting of related alarm. 5. End.
82 / 245
MG#21 - Card activity lost Alarm identification Managed Object ATCA_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Critical Card activity lost [ Location of the faulty ATCA card (Shelf/Slot) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes - MG#1 - Protected line card out of service Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the actions described in related alarm.
83 / 245
MG#30 - Ethernet plane unavailable Alarm identification Managed Object ATCA_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Major Ethernet plane unavailable [ Location of the ATCA switch card (Shelf/Slot) ] [ Type of failure ]: 1=base ethernet 2=fabric ethernet 3=base ethernet uplink 4=fabric ethernet uplink 5=switch card processor Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects Fabric ethernet traffic is automatically switched over the redundant ethernet plane effects No None Corrective actions
Related alarms
84 / 245
MG#30 - Ethernet plane unavailable On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If the gatewy is made of 2 ATCA shelves, check that second switch card is present and not in reset state 2. If type of failure is equal to 1 (base ethernet) or 2 (fabric ethernet) or 5 (switch card processor), then insert or replace the switch card according to the appropriate procedure and, if necessary, send it to the repair service. 3. If type of failure is equal to 3 (base ethernet uplink), then plug or replace the related ethernet uplink. 4. If type of failure is equal to 4 (fabric ethernet uplink), plug or replace the related ethernet uplink, then extract and insert the related switch card.
85 / 245
MG#40 - Loss of all synchro references Alarm identification Managed Object Synchro Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Critical Loss of all synchro references None Not applicable Description Probable cause(s) Probable on system Synchronization reference is no longer available
effects The system clock module of the switch cards switches automatically in "free run" mode (signal generation from local clock) Voice quality disturbance Data flow disturbance (major)
Probable on service
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check synchronizing lines (state and link). 2. If necessary, repair. 3. Check if synchronization function is available. 4. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 5. End.
86 / 245
MG#41 - Loss of synchro reference (line timing mode) Alarm identification Managed Object Synchro_line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Minor Loss of synchro reference (line timing mode) [ Location of the synchronizing line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system Probable on service Synchronizing line failure
effects No effect because an other line is automatically used as synchronization source reference effects No None Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check synchronizing lines (state and link). If necessary, repair or replace of synchronization source reference. 2. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 3. End.
87 / 245
MG#43 - Loss of synchro reference (external timing mode) Alarm identification Managed Object ATCA_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Minor Loss of synchro reference (external timing mode) [ Location of the switch card on which the external line is linked (Shelf/Slot) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects No effect because an other external reference is automatically used as synchronization source reference effects No None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check synchronizing external reference (state and link). If necessary, repair or replace of synchronization source reference. 2. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 3. End.
Related alarms
88 / 245
MG#44 - System clock module failure Alarm identification Managed Object ATCA_card Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Major System clock module failure [ Location of the ATCA switch card (Shelf/Slot) ] [ Type of failure ]: 1=invalid status 2=watchdog 3=boot failure 4=configuration failure 5=SNMP error (processor failure) Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service HW failure of related switch card
effects Synchronization function is provided by the other switch card All user traffic is provided by the other switch card effects No - GHM#516 - Fatal hardware error Corrective actions
Related alarms
On-site interven- Yes tion required? Actions replace the switch card according to the appropriate procedure (see related alarm).
89 / 245
PDUA#1 - RAP Unreachable Alarm identification Managed Object PDUA Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Equipment malfunction None Critical RAP Unreachable The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use the Hardware Management GUI to locate the name of the object displayed in the Name field Threshold Info Not applicable Description Probable cause(s) Remote equipment is unreachable. The Alarm PDU is disconnected or out of service. Probable on system Probable on service effects Alarm synthesis is unreliable. effects Yes - GHM#519 - Fatal ethernet switch error Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm: 1. If there are other related alarms troubleshoot these alarms before proceeding. 2. Check the Alarm PDU cables and power supply. 3. Reset the Alarm PDU. 4. Replace the switch according to the appropriate procedure. 5. If the problem persists, contact Alcatel TASC. 6. End.
90 / 245
PDUA#2 - Default on infrastucture loops supervision Alarm identification Managed Object PDUA Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Equipment malfunction None Critical Default on infrastucture loops supervision The location of the faulty unit is indicated in this field Format: "location: <location of the faulty unit>" You can use the Hardware Management GUI to locate the name of the object displayed in the Name field Threshold Info Not applicable Description Probable cause(s) Remote equipment is unreachable. The Alarm PDU is disconnected or out of service. Probable on system Probable on service effects Alarm synthesis is unreliable. effects No - PDUA#1 - RAP Unreachable Corrective actions
Related alarms
91 / 245
PDUA#2 - Default on infrastucture loops supervision On-site interven- Yes tion required? Actions Perform the following actions in the given order. Continue to the next action only if the system does not clear the alarm: Contact Alcatel TASC before any hardware replacement. 1. If there are other related alarms troubleshoot these alarms before proceeding. 2. Check the Alarm PDU Loops sensors. 3. Check the Alarm PDU cables and power supply. 4. Reset the the Alarm PDU. 5. If the problem persists, contact Alcatel TASC. 6. End.
92 / 245
3 INFRASTRUCTURE ALARMS
This section describes the infrastructure alarms that can be sent by the alarm loops on a 7570 equipped with the Rack Alarm Panel.
93 / 245
INFR#1 - Default on infrastucture loop #1 Alarm identification Managed Object PDUA Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Input device error None Indeterminate Default on infrastucture loop #1 The location of RAP managing the loop is given here. Not applicable Description Probable cause(s) This alarm can be customized on site. The probable cause, type, severity displayed on the Alarm GUI can differ from the present dictionary. Probable on system Probable on service effects Depends on sensor supervized. effects No None Corrective actions On-site interven- Yes tion required? Actions Depends on sensor supervized.
Related alarms
94 / 245
INFR#2 - Default on infrastucture loop #2 Alarm identification Managed Object PDUA Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Input device error None Indeterminate Default on infrastucture loop #2 The location of RAP managing the loop is given here. Not applicable Description Probable cause(s) This alarm can be customized on site. The probable cause, type, severity displayed on the Alarm GUI can differ from the present dictionary. Probable on system Probable on service effects Depends on sensor supervized. effects No None Corrective actions On-site interven- Yes tion required? Actions Depends on sensor supervized.
Related alarms
95 / 245
4 SOFTWARE ALARMS
This section provides all information related to the software alarms.
96 / 245
MG#230 - Control management initialization in progress Alarm identification Managed Object Platform_MG Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Warning Control management initialization in progress None Not applicable Description Probable cause(s) This alarm is raised when initialization of the active control station starts It is cleared when control station initialization ends Probable on system effects During the initialization phase, 7570 management is unavailable As long as this alarm or related alarm is raised, GUI notifies you that 7570 management is unavailable effects Yes - MG#231 - Board configuration initialization in progress Corrective actions
Probable on service
Related alarms
On-site interven- No tion required? Actions Wait for end of 7570 control station initialization phase.
97 / 245
MG#231 - Board configuration initialization in progress Alarm identification Managed Object Platform_MG Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Warning Board configuration initialization in progress None Not applicable Description Probable cause(s) This alarm is raised when initialization of the active control station starts It is cleared when control station initialization ends Probable on system effects During the initialization phase, 7570 management is unavailable As long as this alarm or related alarm is raised, GUI notifies you that 7570 management is unavailable effects Yes - MG#230 - Control management initialization in progress Corrective actions
Probable on service
Related alarms
On-site interven- No tion required? Actions Wait for end of 7570 control station initialization phase.
98 / 245
MG#240 - Database Migration failed Alarm identification Managed Object SW_management Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Processing error Corrupt data None Critical Database Migration failed [ Release of the 7570 software that did not succeed to start ] Not applicable Description Probable cause(s) This alarm is raised when a software upgrade embeddding a database migration has failed A database corruption is detected after migration Probable on system effects The 7570 fails to start the requested hardware Standard software upgrade is performed by standby hardware only: a) The 7570 standby equipment does not start on the requested release b) The 7570 active equipment continue to manage the 7570 c) The 7570 standby equipment or the full 7570 restarts with the previous valid software version The Alarm is raised as soon as the database corruption is detected on a release This alarm is cleared when the control station successfuly restarts on the previous valid software release Probable on service effects No None Corrective actions On-site interven- No tion required? Actions Contact your Alcatel-Lucent Technical Support Center.
Related alarms
99 / 245
MG#241 - Database Corruption detected Alarm identification Managed Object SW_management Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Processing error Corrupt data None Major Database Corruption detected OAM database corruption detected. Not applicable Description Probable cause(s) An OAM database corruption is detected A database corruption is detected by audit tools Probable on system Probable on service effects This alarm is cleared when the control station successfuly restarts on the previous database effects No None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Save the current database and send it to your Alcatel-Lucent Technical Support Center support center for analysis. 2. Replace the current database with the reference one (i.e., the saved database). 3. Wait for both control cards to be synchronized 4. Force the switchover of the control stations 5. If the problem persists, contact your Alcatel-Lucent Technical Support Center 6. End.
Related alarms
100 / 245
5 LINE AND PORT ALARMS

This section provides all the information related to the line and port alarms.
101 / 245
MG#22 - Port activity lost Alarm identification Managed Object SDH_port Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Equipment malfunction None Major Port activity lost [ Location of the SDH port (Shelf/Slot/Port) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions This alarm is raised when an SDH port, belonging to an unlocked ATCA line card, no longer has operational SDH line and has at least one unlocked line
Related alarms
102 / 245
MG#50 - Threshold crossing: TCA Register Section 15 minutes Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA Register Section 15 minutes [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
103 / 245
MG#51 - Threshold crossing: TCA Mux Section 15 minutes Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA Mux Section 15 minutes [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
104 / 245
MG#52 - Threshold crossing: TCA path 15 minutes Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA path 15 minutes [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
105 / 245
MG#53 - Threshold crossing: TCA Register Section 24 hours Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA Register Section 24 hours [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
106 / 245
MG#54 - Threshold crossing: TCA Mux Section 24 hours Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA Mux Section 24 hours [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
107 / 245
MG#55 - Threshold crossing: TCA path 24 hours Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA path 24 hours [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
108 / 245
MG#56 - Threshold crossing: TCA Mux Section - Far End 15 minutes Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA Mux Section - Far End 15 minutes [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
109 / 245
MG#57 - Threshold crossing: TCA path - Far End 15 minutes Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA path - Far End 15 minutes [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
110 / 245
MG#58 - Threshold crossing: TCA Mux Section - Far End 24 hours Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA Mux Section - Far End 24 hours [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
111 / 245
MG#59 - Threshold crossing: TCA path - Far End 24 hours Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor Threshold crossing: TCA path - Far End 24 hours [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
112 / 245
MG#60 - Threshold crossing: TCA Egress Cell Data Error Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Threshold crossed None Minor Threshold crossing: TCA Egress Cell Data Error [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
113 / 245
MG#61 - SDH loss of clock Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Timing problem None Minor SDH loss of clock [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Power is received but received clock frequency cannot be recognized or is out of authorized bounds The connected line is probably not an STM-1 Probable on system effects The line is disabled All other SDH_Line and SDH_Path alarms are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects No None Corrective actions
Related alarms
114 / 245
MG#61 - SDH loss of clock On-site interven- Yes tion required? Actions Perform the following verifications in the given order: 1. Check, using the GUI alarm management, that synchronization equipment is not under critical alarm. 2. Check that the SDH configuration of the connected line is appropriate on both ends of the line. 3. Check line cabling. 4. Check operational state of external optical/electrical line and its SDH framing in receive direction using external test equipment. 5. Perform a line loopback to check the operational state of optical/electrical line and its SDH framing, using external test equipment. 6. End.
115 / 245
MG#62 - SDH loss of signal Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Loss of signal None Minor SDH loss of signal [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) No power is received from the line: a) The cable may be not connected b) The line may be locked or may have failed on the remote equipment side Probable on system effects The line is disabled Lower priority SDH_Line and SDH_Path alarms are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects No None Corrective actions
Related alarms
116 / 245
MG#62 - SDH loss of signal On-site interven- Yes tion required? Actions Perform the following verification in the given order: 1. Check that the SDH configuration of the connected line is appropriate on both ends of the line, and that the line is "unlocked". 2. Check line cabling 3. Check operational state of external optical/electrical line and its SDH framing in receive direction using external test equipment. 4. Perform a line loopback to check the operational state of optical/electrical line and its SDH framing, using external test equipment. 5. End.
117 / 245
MG#63 - SDH loss of frame Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Loss of frame None Minor SDH loss of frame [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) No SDH framing is detected from the line The line may be misconfigured on the remote equipment Probable on system effects The line is disabled Lower priority SDH_Line and SDH_Path alarms are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects No None Corrective actions
Related alarms
118 / 245
MG#63 - SDH loss of frame On-site interven- Yes tion required? Actions Perform the following verification in the given order: 1. Check that the SDH configuration of the connected line is appropriate on both ends of the line (in particular, ends should be either both ETSI or both ANSI), and that the line is "unlocked". 2. Check line cabling 3. Check operational state of external optical/electrical line and its SDH framing in receive direction using external test equipment. 4. Perform a line loopback to check the operational state of optical/electrical line and its SDH framing, using external test equipment.
119 / 245
MG#64 - SDH line/Mux section AIS Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor SDH line/Mux section AIS [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) SDH framing is received but the line/Mux section layer delivers an AIS indicating a defect detected upstream The remote end of the SDH line or another remote equipment may be misconfigured Probable on system effects The line is disabled Lower priority SDH_Line and SDH_Path alarms are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects No None Corrective actions On-site interven- No tion required? Actions Repair remote equipment defect.
Related alarms
120 / 245
MG#65 - SDH path AIS Alarm identification Managed Object SDH_Path Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Remote node transmission error None Minor SDH path AIS [ Location of the SDH path (Shelf/Slot/Line_position/hop/mop/lop) ] hop/mop/lop identifies the path in failure This path is evidently not related to a TDM in case of ATM SDH Threshold Info Not applicable Description Probable cause(s) SDH path layer delivers an AIS indicating a path defect detected upstream: a) A remote equipment may be misconfigured b) In case of TDM SDH, a path may not be configured and this alarm is for information only Probable on system effects Lower priority SDH_Line and SDH_Path alarms related to the same path are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects No None Corrective actions On-site interven- No tion required? Actions Check if the alarm indicates a defect and, if necessary, reconfigure or repair remote equipment.
Related alarms
121 / 245
MG#66 - SDH loss of pointer Alarm identification Managed Object SDH_Path Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Framing error None Minor SDH loss of pointer [ Location of the SDH path (Shelf/Slot/Line_position/hop/mop/lop) ] hop/mop/lop identifies the path in failure This path is evidently not related to a TDM in case of ATM SDH Threshold Info Not applicable Description Probable cause(s) An SDH path container is not accessible The local or remote equipment may be misconfigured or failed Probable on system effects Lower priority SDH_Line and SDH_Path alarms related to the same path are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects No None Corrective actions On-site interven- No tion required? Actions Check configuration on line and path ends
Related alarms
122 / 245
MG#67 - Section trace mismatch (J0) Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Communications subsystem failure None Minor Section trace mismatch (J0) [ Location of the SDH line (Shelf/Slot/Line_position) ] [ Received section trace value ] Threshold Info Not applicable Description Probable cause(s) Unexpected SDH line name in payload (trace name) The local or remote equipment is misconfigured Probable on system effects The line is disabled Lower priority SDH_Line and SDH_Path alarms are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following verifications in the given order: 1. Retrieve line information from the GUI and check if the section trace check must really be enabled, and verify the section trace string. 2. Check the received string and line cabling. 3. End.
Related alarms
123 / 245
MG#68 - Path trace mismatch (J1, J2) Alarm identification Managed Object SDH_Path Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Communications subsystem failure None Minor Path trace mismatch (J1, J2) [ Location of the SDH path (Shelf/Slot/Line_position/hop/mop/lop) ] hop/mop/lop identifies the path in failure This path is evidently not related to a TDM in case of ATM SDH [ Received path trace value ] Threshold Info Not applicable Description Probable cause(s) Unexpected SDH path name in payload (trace name) The local or remote equipment is misconfigured Probable on system effects Traffic expected in this container cannot be processed Lower priority SDH_Line alarms and SDH_Path alarms related to the same path are cleared This alarm is associated with each SDH line regardless of APS configuration If the associated port has no operational line, a "port activity lost" alarm is raised Current alarm is cleared when the card or the line is locked Probable on service effects Yes None Corrective actions
Related alarms
124 / 245
MG#68 - Path trace mismatch (J1, J2) On-site interven- No tion required? Actions Perform the following verifications in the given order: 1. Retrieve line information from the GUI and check if the path trace check must really be enabled, and verify the path trace string. 2. Check the received string and the remote equipment. 3. End.
125 / 245
MG#69 - SDH Signal fail (SF) Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Threshold crossed None Minor SDH Signal fail (SF) [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system The line has reached an error threshold indicating the lowest limit of acceptable reception quality
effects No system reaction Poor transmission with risk of Cs frames loss that affects traffic quality and is perceptible by end users Risk of local or remote hardware anomaly along the line
Probable on service
Related alarms
126 / 245
MG#69 - SDH Signal fail (SF) On-site interven- Yes tion required? Actions Perform the following verification in the given order: 1. From the GUI, activate - if not yet started - performance monitoring on the faulty line (and on the possible other line in APS) to get more details about errors types. 2. If APS is available, force an APS switch to the best line among the two to improve quality. 3. Activate performance monitoring of other nodes or lines on the link and locate the faulty element. 4. Repair faulty element. 5. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 6. End.
127 / 245
MG#70 - SDH Signal degrade (SD) Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Threshold crossed None Minor SDH Signal degrade (SD) [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system The line has reached an error threshold that indicates a poor reception quality
effects No immediate system reaction Degraded transmission with probable loss of Cs traffic frames Possible local or remote hardware anomaly along the line
Probable on service
Related alarms
128 / 245
MG#70 - SDH Signal degrade (SD) On-site interven- Yes tion required? Actions Perform the following verification in the given order: 1. From the GUI, activate - if not yet started - performance monitoring on the faulty line (and on the possible other line in APS) to get more details about errors types. 2. If APS is available, force an APS switch to the best line among the two to improve quality. 3. Activate performance monitoring of other nodes or lines on the link and locate the faulty element. 4. Repair faulty element. 5. If the alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 6. End.
129 / 245
MG#71 - SDH Signal label: Protocol mismatch Alarm identification Managed Object SDH_Path Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Configuration or customization error None Minor SDH Signal label: Protocol mismatch [ Location of the SDH path (Shelf/Slot/Line_position/hop/mop/lop) ] hop/mop/lop identifies the path in failure This path is evidently not related to a TDM in case of ATM SDH [ Received path trace value ] Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service The received SDH container is designed to transport an unexpected protocol
effects This particular virtual container is unusable for traffic Valid traffic was probably expected effects Yes None Corrective actions
Related alarms
130 / 245
MG#71 - SDH Signal label: Protocol mismatch On-site interven- Yes tion required? Actions Perform the following verifications depending on the case: 1. If all other containers on the same TDMX or ATMX card are also wrong, the LIU shelf is not the expected one: check LIU shelf cabling to the ATCA rack. 2. If all other containers on the same line are also wrong, the line is not the expected one: check the line cabling. 3. If several containers on the same line are also wrong, check if the container is expected to be used by the 7570. If it is, check the other NEs. If it is not, no action is required from the 7570 and the alarm is informative only, although you are still advised to check the other NEs. 4. End.
131 / 245
MG#72 - SDH Signal label: VC unequipped Alarm identification Managed Object SDH_Path Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Configuration or customization error None Minor SDH Signal label: VC unequipped [ Location of the SDH path (Shelf/Slot/Line_position/hop/mop/lop) ] hop/mop/lop identifies the path in failure This path is evidently not related to a TDM in case of ATM SDH [ Received path trace value ] Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service The received SDH container is not designed to transport data
effects This particular virtual container is unusable for traffic effects No None Corrective actions
Related alarms
On-site interven- No tion required? Actions Perform the following verification: 1. Check if the container is expected to be used by the 7570. If it is, check the other NEs. If it is not, no action is required from the 7570 and the alarm is informative only. 2. End.
132 / 245
MG#73 - SDH line/Mux section RDI Alarm identification Managed Object SDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor SDH line/Mux section RDI [ Location of the SDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system An SDH line AIS from the 7570 has been detected by the peer end point
effects No traffic is received from the line Lower priority SDH_Line alarms and SDH_Path alarms are cleared This alarm is associated with each SDH line regardless of APS configuration Current alarm is cleared when the card or the line is locked
Probable on service
Related alarms
On-site interven- No tion required? Actions Perform the following verification: 1. Check if the 7570 line is looped or in manual maintenance. If not, check the other NEs. If it is, the alarm is informative only and will be cleared when maintenance ends. 2. End.
133 / 245
MG#74 - SDH path RDI Alarm identification Managed Object SDH_Path Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Communication Remote node transmission error None Minor SDH path RDI [ Location of the SDH path (Shelf/Slot/Line_position/hop/mop/lop) ] hop/mop/lop identifies the path in failure This path is evidently not related to a TDM in case of ATM SDH Threshold Info Not applicable Description Probable cause(s) An SDH path AIS from the 7570 is detected by peer end point: a) In case of TDM SDH, a path may not be configured and this alarm is for information only b) A remote equipment may be misconfigured Probable on system effects No traffic is received for this path Lower priority SDH_Line alarms and SDH_Path alarms are cleared This alarm is associated with each SDH path. Current alarm is cleared when the card or the line is locked Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following verification: 1. Check if the 7570 path is configured for traffic. If it is, check the other NEs, especially the receive and transmit fibers. If it is not, the alarm is informative only
Related alarms
134 / 245
MG#75 - PDH payload loss of frame Alarm identification Managed Object SDH_T1E1 Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Loss of frame None Minor PDH payload loss of frame [ Location of the T1/E1 (Shelf/Slot/Line_position/hop/mop/lop) ] Not applicable Description Probable cause(s) No E1 or DS1 framing is detected from the line The line may be misconfigured on the remote equipment Probable on system Probable on service effects E1 or DS1 is disabled Lower priority SDH_T1E1 alarms are cleared effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following verifications: 1. Check that the configuration of the PDH payload is appropriate on both ends of the line: in particular, ends should be either both ETSI or both ANSI. 2. Check the end to end container cross connection. 3. End.
Related alarms
135 / 245
MG#76 - PDH payload line AIS Alarm identification Managed Object SDH_T1E1 Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor PDH payload line AIS [ Location of the T1/E1 (Shelf/Slot/Line_position/hop/mop/lop) ] Not applicable Description Probable cause(s) Bit pattern is received from PDH payload but it is "all 1s" (AIS), which indicates that a defect was detected upstream The remote end of PDH payload or another remote equipment may be misconfigured Probable on system Probable on service effects E1 or DS1 is disabled Lower priority SDH_T1E1 alarms are cleared effects Yes None Corrective actions On-site interven- No tion required? Actions Reconfigure remote equipment
Related alarms
136 / 245
MG#77 - PDH payload line RDI Alarm identification Managed Object SDH_T1E1 Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor PDH payload line RDI [ Location of the T1/E1 (Shelf/Slot/Line_position/hop/mop/lop) ] Not applicable Description Probable cause(s) Probable on system Probable on service A PDH payload AIS from the 7570 has been detected by the peer end point
effects No E1 or DS1 traffic is received from the line Lower priority SDH_T1E1 alarms are cleared effects Yes None Corrective actions
Related alarms
On-site interven- No tion required? Actions Perform the following verification: 1. Check if the 7570 is in manual maintenance. If it is check the other NEs. If it is not, the alarm is informative only and will be cleared when maintenance ends. 2. End.
137 / 245
MG#79 - Loss of CRC4 multiframe Alarm identification Managed Object SDH_T1E1 Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Loss of frame None Minor Loss of CRC4 multiframe [ Location of the T1/E1 (Shelf/Slot/Line_position/hop/mop/lop) ] Not applicable Description Probable cause(s) Loss of CRC4 multiframe The PDH payload may be misconfigured on the remote equipment Probable on system Probable on service effects No E1 or DS1 traffic is received Lower priority SDH_T1E1 alarms are cleared effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following verifications: 1. Check that the configuration of E1 or DS1 is appropriate on both ends of the line: in particular, they must be either both CRC4 configured, or both CRC4 not configured. 2. End.
Related alarms
138 / 245
MG#80 - Signal fail (SF) Alarm identification Managed Object SDH_T1E1 Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Threshold crossed None Minor Signal fail (SF) [ Location of the T1/E1 (Shelf/Slot/Line_position/hop/mop/lop) ] Not applicable Description Probable cause(s) Probable on system The SDH_T1E1 has reached an error threshold that indicates the lowest limit of acceptable reception quality
effects No system reaction Poor transmission with probably a loss of Cs frames affecting traffic quality and perceptible by end users Possible local or remote hardware anomaly on the end to end connection
Probable on service
Related alarms
On-site interven- No tion required? Actions Perform the following verifications in the given order: 1. Verify presence of threshold crossing alert. 2. Activate performance monitoring of other nodes or lines on the link and locate the faulty element. 3. Repair faulty elements. 4. End.
139 / 245
MG#81 - Signal degraded (SD) Alarm identification Managed Object SDH_T1E1 Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Threshold crossed None Minor Signal degraded (SD) [ Location of the T1/E1 (Shelf/Slot/Line_position/hop/mop/lop) ] Not applicable Description Probable cause(s) Probable on system The SDH_T1E1 has reached an error threshold that indicates a poor reception quality
effects No immediate system reaction Degraded transmission with probable loss of Cs traffic frames Possible local or remote hardware anomaly on the end to end connection
Probable on service
Related alarms
On-site interven- No tion required? Actions Perform the following verifications: 1. Verify presence of threshold crossing alert. 2. Activate performance monitoring of other nodes or lines on the link and locate the faulty element. 3. Repair faulty elements. 4. End.
140 / 245
MG#90 - Loss of signal Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Loss of signal None Minor Loss of signal [ Location of the PDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) No power is received from the line a) The cable may be not connected b) The line may be locked or may have failed on the remote equipment side Probable on system effects The line is disabled Lower priority PDH_Line alarms are cleared This line failure prevents port activity and also raises the associated alarm "port activity lost" Current alarm is cleared when the card or the line is locked Probable on service effects Yes None Corrective actions
Related alarms
141 / 245
MG#90 - Loss of signal On-site interven- No tion required? Actions Perform the following verifications in the given order: 1. Check that the PDH configuration of the line is appropriate on both ends, and is "unlocked". 2. Check line cabling. 3. Check external electrical line and its framing in receive direction using external test equipment. 4. Perform a line loopback to check the operational state of electrical line and its PDH framing, using external test equipment. 5. End.
142 / 245
MG#91 - Loss of frame Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Loss of frame None Minor Loss of frame [ Location of the PDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) No E1 or DS1 framing is detected from the line The line may be misconfigured on the remote equipment Probable on system effects The line is disabled Lower priority PDH_Line alarms are cleared This line failure prevents port activity and also raises the associated alarm "port activity lost" Current alarm is cleared when card or line is locked Probable on service effects Yes None Corrective actions
Related alarms
143 / 245
MG#91 - Loss of frame On-site interven- No tion required? Actions Perform the following verifications in the given order: 1. Check that the E1 or DS1 configuration of the connected line is appropriate on both ends: in particular, ends should be either both ETSI or both ANSI, and is "unlocked". 2. Check line cabling. 3. Check external electrical line and its framing in receive direction using external test equipment. 4. Perform a line loopback to check the operational state of electrical line and its PDH framing, using external test equipment. 5. End.
144 / 245
MG#92 - PDH line AIS Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor PDH line AIS [ Location of the PDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Power is received from the PDH line but the bit pattern is "all 1s" (AIS), which indicates that a defect was detected upstream The remote end of the PDH line or another remote equipment may be misconfigured Probable on system Probable on service effects The line is disabled Lower priority SDH_Line alarms and SDH_Path alarms are cleared effects Yes None Corrective actions On-site interven- No tion required? Actions Repair remote equipment defect
Related alarms
145 / 245
MG#93 - Signal Failure (SF) Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Threshold crossed None Minor Signal Failure (SF) [ Location of the PDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system The line has reached an error threshold that indicates the lowest limit of acceptable reception quality
effects No system reaction Poor transmission with possible loss of Cs frames that affects traffic quality and is perceptible by end users Possible local or remote hardware anomaly along the line
Probable on service
Related alarms
On-site interven- No tion required? Actions Perform the following verifications in the given order: 1. From the GUI, activate - if not yet started - performance monitoring on the faulty line to get more details about errors types. 2. Activate performance monitoring of other nodes or lines on the link and locate the faulty elements. 3. Repair faulty elements. 4. End.
146 / 245
MG#94 - Signal Degraded (SD) Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Threshold crossed None Minor Signal Degraded (SD) [ Location of the PDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system The line has reached an error threshold that indicates a poor reception quality
effects No immediate system reaction Degraded transmission with possible loss of Cs frames that affects traffic quality and is perceptible by end users Possible local or remote hardware anomaly along the line
Probable on service
Related alarms
On-site interven- No tion required? Actions Perform the following verifications in the given order: 1. From the GUI, activate performance monitoring on the line to get more details about errors types. 2. Activate performance monitoring of elements along the link, including a local loop on the 7570, and locate the faulty elements. 3. Repair faulty elements. 4. End.
147 / 245
MG#95 - PDH line RDI Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor PDH line RDI [ Location of the PDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system A PDH line AIS from the 7570 has been detected by the peer end point
effects No traffic is received from the line Lower priority PDH_Line alarms are cleared Current alarm is cleared when the card or the line is locked
Probable on service
Related alarms
On-site interven- No tion required? Actions Perform the following verification: 1. Check if the 7570 line is looped or in manual maintenance. If it is not, check the other NEs. If it is, the alarm is informative only and will be cleared when maintenance ends. 2. End.
148 / 245
MG#96 - TCA crossing 15 minutes Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor TCA crossing 15 minutes [ Location of the PDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
149 / 245
MG#97 - TCA crossing 24 hours Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service Threshold crossed None Minor TCA crossing 24 hours [ Location of the PDH line (Shelf/Slot/Line_position) ] [ Error type related to TCA ]: 1=code violation 2=errored seconds 3=severely errored seconds 4=severely errored frame seconds 5=unavailable seconds Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions
Related alarms
150 / 245
MG#98 - Loss of CRC4 multiframe Alarm identification Managed Object PDH_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Loss of frame None Minor Loss of CRC4 multiframe [ Location of the PDH line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Loss of CRC4 multiframe The line may be misconfigured on the remote equipment Probable on system effects The line is disabled Lower priority PDH_Line alarms are cleared This line failure prevents port activity and also raises the associated alarm "port activity lost" Current alarm is cleared when the card or the line is locked Probable on service effects Yes None Corrective actions On-site interven- No tion required? Actions Perform the following verifications in the given order: 1. Check that E1 or DS1 configuration of the connected line is appropriate on both ends: in particular, ends should either be both CRC4 configured, or both CRC4 not configured. 2. End.
Related alarms
151 / 245
MG#111 - Loss of cell delineation Alarm identification Managed Object ATM_Port Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Major Loss of cell delineation [ Location of the ATM port (Shelf/Slot/Port) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects All cross connections and all AAL2 paths are out of service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check if the line is really intended for ATM usage. 2. Lock the line (APS case: the other line is used). 3. Perform a line loopback type 4 to check the operational state of the 7570 hardware. 4. If the hardware is faulty, lock the ATM card: the ATM card in EPS takes over. 5. Replace the ATM card, and repeat loopback test. 6. End.
Related alarms
152 / 245
MG#113 - OAM too many AIS detected Alarm identification Managed Object ATM_Port Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Critical OAM too many AIS detected [ Location of the ATM port (Shelf/Slot/Port) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- No tion required? Actions Perform the following actions in the given order: 1. Check the OFRT profile characteristics. 2. Check ATM network outage (ATM NE(s) and ATM SDH lines). 3. End. The number of end points in AIS state has exceeded the configured AIS threshold
Related alarms
153 / 245
MG#114 - OAM too many LOC Alarm identification Managed Object ATM_Port Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Critical OAM too many LOC [ Location of the ATM port (Shelf/Slot/Port) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check the OFRT profile characteristics. 2. Check that CC source points has been configured. 3. Check ATM network outage (ATM NE(s) and ATM SDH lines). 4. Check for a Switch card problem (Fabric switch). 5. Check for a backplane problem. 6. End. The number of end points in LOC state has exceeded the configured LOC threshold
Related alarms
154 / 245
MG#115 - OAM too many RDI detected Alarm identification Managed Object ATM_Port Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Critical OAM too many RDI detected [ Location of the ATM port (Shelf/Slot/Port) ] Not applicable Description Probable cause(s) Probable on system Probable on service effects effects Yes None Corrective actions On-site interven- No tion required? Actions Perform the following actions in the given order: 1. Check the OFRT profile characteristics. 2. Check ATM network outage (ATM NE(s) and ATM SDH lines). 3. End. The number of end points in RDI state has exceeded the configured RDI threshold
Related alarms
155 / 245
MG#116 - OAM VC-RDI detected Alarm identification Managed Object ATM_VC Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM VC-RDI detected [ Location of the ATM VC Not applicable Description Probable cause(s) This alarm is raised when an OAM VC RDI cell is received: a) If the ATM endpoint configuration is end-to-end, OAM RDI b) If the ATM endpoint configuration is segment, OAM RDI c) VC RDI cell has been received for 3.5 seconds Probable on system Probable on service effects Interruption of cell transfer at VC level in the forward direction effects Yes None Corrective actions On-site interven- No tion required? Actions Check for an ATM card failure or ATM SDH lines outage on the VCC path. Note: For a Segment RDI, perform the above check only inside the segment boundaries, at ATM endpoints that are configured as segment-intermediate.
Related alarms
156 / 245
MG#117 - OAM VP-RDI detected Alarm identification Managed Object ATM_VP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM VP-RDI detected [ Location of the ATM VP Not applicable Description Probable cause(s) This alarm is raised when an OAM VP RDI cell is received: a) If the ATM endpoint configuration is end-to-end, OAM RDI b) If the ATM endpoint configuration is segment, OAM RDI c) VP RDI cell has been received for 3,5 seconds Probable on system Probable on service effects Interruption of cell transfer at VP level in the forward direction effects Yes None Corrective actions On-site interven- No tion required? Actions Check for an ATM card failure or ATM SDH lines outage in the VPC path. Note: For a Segment RDI, perform the above check only inside the segment boundaries, at ATM endpoints that are configured as segment-intermediate.
Related alarms
157 / 245
MG#118 - OAM VC-AIS detected Alarm identification Managed Object ATM_VC Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM VC-AIS detected [ Location of the ATM VC Not applicable Description Probable cause(s) This alarm is raised when an OAM VC AIS cell is received: a) If the ATM OAM AIS cell type is End-to-end b) If the ATM OAM AIS cell type is Segment c) VC RDI VC d) The alarm clears when no VC AIS cell has been received for 3.5 seconds or on reception of a valid user cell or a valid end-to-end CC cell Probable on system Probable on service effects Interruption of cell transfer at VC level in the forward direction effects Yes None Corrective actions On-site interven- No tion required? Actions Check for an ATM card failure or ATM SDH lines outage on the VPC path. Note: For a Segment AIS, perform the above check only inside the segment boundaries, at ATM endpoints that are configured as segment-intermediate.
Related alarms
158 / 245
MG#119 - OAM VP-AIS detected Alarm identification Managed Object ATM_VP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM VP-AIS detected [ Location of the ATM port (Shelf/Slot/PortVP) ] Not applicable Description Probable cause(s) This alarm is raised when an OAM VP AIS cell is received: a) If the ATM OAM AIS cell type is End-to-end b) If the ATM OAM AIS cell type is Segment c) VP RDI VP d) The alarm clears when no VP AIS cell has been received for 3.5 seconds or on reception of a valid user cell or end-to-end CC cell Probable on system Probable on service effects Interruption of cell transfer at VP level in the forward direction effects Yes None Corrective actions On-site interven- No tion required? Actions Check for an ATM card failure or ATM SDH lines outage on the VPC path. Note: For a Segment AIS, perform the above check only inside the segment boundaries, at ATM endpoints that are configured as segment-intermediate.
Related alarms
159 / 245
MG#120 - OAM LNK E2E VC-LOC Alarm identification Managed Object ATM_VC Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM LNK E2E VC-LOC One information item is provided with this alarm: Location of the ATM VC Not applicable Description Probable cause(s) This alarm is raised on an OAM VC sink point on an UNI ATM port when no OAM VC CC cell nor user cell is received for 3.5 seconds from the link VC AIS cells are sent in the forward direction VC CC cell or user cell from the link Probable on system Probable on service effects No cell received from the link on this VC terminating point, or No cell received from the link on this VC cross-connection effects Yes None Corrective actions On-site interven- No tion required? Actions Perform the following actions in the given order: 1. OAM CC source is already configured. 2. Check for an ATM card failure or ATM SDH lines outage on the VCC path. 3. End.
Related alarms
160 / 245
MG#121 - OAM LNK E2E VP-LOC Alarm identification Managed Object ATM_VP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM LNK E2E VP-LOC [ Location of the ATM VP Not applicable Description Probable cause(s) This alarm is raised on an OAM VP sink point on an UNI ATM port when no OAM VP CC cell nor user cell is received for 3.5 seconds from the link VP AIS cells are sent in the forward direction VP CC cell or user cell from the link Probable on system Probable on service effects No cell received from the link on this VP cross-connection effects Yes None Corrective actions On-site interven- No tion required? Actions Perform the following actions in the given order: 1. OAM CC source is already configured. 2. Check for an ATM card failure or ATM SDH lines outage on the VPC path. 3. End.
Related alarms
161 / 245
MG#122 - OAM LNK SEG VC-LOC Alarm identification Managed Object ATM_VC Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM LNK SEG VC-LOC [ Location of the ATM VC Not applicable Description Probable cause(s) This alarm is raised on an OAM VC segment sink point on an ATM port when no OAM VC CC cell nor user cell is received for 3.5 seconds from the link VC AIS cells are sent in the forward direction VC CC cell or user cell from the link Probable on system Probable on service effects No cell received from the link on this VC cross-connection effects Yes None Corrective actions On-site interven- No tion required? Actions Perform the following actions in the given order: 1. OAM CC source is already configured. 2. Check for an ATM card failure or ATM SDH lines outage on the VCC segment path 3. End.
Related alarms
162 / 245
MG#123 - OAM LNK SEG VP-LOC Alarm identification Managed Object ATM_VP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM LNK SEG VP-LOC [ Location of the ATM VP Not applicable Description Probable cause(s) This alarm is raised on an OAM VP segment sink point on an ATM port when no OAM VP CC cell nor user cell is received for 3.5 seconds from the link VP AIS cells are sent in the forward direction VP CC cell or user cell from the link Probable on system Probable on service effects No cell received from the link on this VP cross-connection effects Yes None Corrective actions On-site interven- No tion required? Actions Perform the following actions in the given order: 1. OAM CC source is already configured before. 2. Check for an ATM card failure or ATM SDH lines outage on the VPC segment path. 3. End.
Related alarms
163 / 245
MG#124 - OAM MATX E2E VC-LOC Alarm identification Managed Object ATM_VC Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM MATX E2E VC-LOC [ Location of the ATM VC Not applicable Description Probable cause(s) This alarm is raised on an OAM VC sink point on an UNI ATM port when no OAM VC CC cell nor user cell is received for 3.5 seconds from the fabric switch VC AIS cells are sent in the forward direction VC CC cell or user cell from the fabric switch Probable on system Probable on service effects No cell received from the matrix on this VC cross connection effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. OAM CC source is already configured. 2. Check for an ATM card failure or ATM SDH lines outage on the VCC path. 3. Check for a Switch card problem (Fabric switch). 4. Check for a backplane problem. 5. End.
Related alarms
164 / 245
MG#125 - OAM MATX E2E VP-LOC Alarm identification Managed Object ATM_VP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor OAM MATX E2E VP-LOC [ Location of the ATM VP Not applicable Description Probable cause(s) This alarm is raised on an OAM VP sink point on an UNI ATM port when no OAM VP CC cell nor user cell is received for 3.5 seconds from the fabric switch VP AIS cells are sent in the forward direction VP CC cell or user cell from the fabric switch Probable on system Probable on service effects No cell received from the fabric switch on this VP cross-connection effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. OAM CC source is already configured. 2. Check for an ATM card failure or ATM SDH lines outage on the VPC path. 3. Check for a Switch card problem (Fabric switch). 4. Check for a backplane problem. 5. End.
Related alarms
165 / 245
MG#126 - Internal OAM MATX SEG VC-LOC Alarm identification Managed Object ATM_VC Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor Internal OAM MATX SEG VC-LOC One information item is provided with this alarm: Location of the ATM VC Not applicable Description Probable cause(s) Information : An internal OAM Segment is used to monitor the ATM crossconnection This alarm is raised on an OAM VC sink point on a ATM port when neither OAM VC CC cells nor user cells are received for 3.5 seconds from the fabric switch VC AIS cells are sent in the forward direction VC CC cell or a user cell from the fabric switch Probable on system Probable on service effects No cell received from the fabric switch on this VC cross-connection effects Yes None Corrective actions
Related alarms
166 / 245
MG#126 - Internal OAM MATX SEG VC-LOC On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check for any ATM card failure or ATM SDH lines outage on the VCC segment path. 2. Check for any Switch card problem (Fabric switch). 3. Check for any backplane problem. 4. If the problem persists, contact your Alcatel-Lucent Technical Support Center 5. End.
167 / 245
MG#127 - Internal OAM MATX SEG VP-LOC Alarm identification Managed Object ATM_VP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Minor Internal OAM MATX SEG VP-LOC [ Location of the ATM VP Not applicable Description Probable cause(s) Information : An internal OAM Segment is used to monitor the ATM crossconnection This alarm is raised on an OAM VP segment sink point on an ATM port when neither OAM VP CC cells nor user cells are received for 3.5 seconds from the fabric switch VP AIS cells are sent in the forward direction VP CC cell or a user cell from the fabric switch Probable on system Probable on service effects No cell received from the matrix on this VP cross-connection effects Yes None Corrective actions
Related alarms
168 / 245
MG#127 - Internal OAM MATX SEG VP-LOC On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check for any ATM card failure or ATM SDH lines outage in the VPC segment path. 2. Check for any Switch card problem (Fabric switch). 3. Check for any backplane problem. 4. If the problem persists, contact your Alcatel-Lucent Technical Support Center 5. End.
169 / 245
MG#150 - IP line degraded Alarm identification Managed Object IP_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Degraded signal None Warning IP line degraded [ Location of the IP line (Shelf/Slot/Line_position) ] Not applicable Description Probable cause(s) Probable on system The line has reached an FCS error threshold indicating poor reception quality
effects No immediate system reaction Degraded transmission with Cs traffic frames loss Possible local or remote hardware anomaly along the line
Probable on service
Related alarms
170 / 245
MG#150 - IP line degraded On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. From the GUI, activate performance monitoring on the line - or the two lines of the port - for more details about errors types. 2. If both lines are configured and enabled, force a switchover to the best line among the two, by locking / unlocking the worst line to improve user Cs quality. 3. Activate performance monitoring of elements on the link and locate the faulty element. 4. Repair faulty element. 5. If needed, activate a line loopback on the 7570 faulty line, and connect an external tool to make measurements. 6. End.
171 / 245
MG#151 - IP line failure Alarm identification Managed Object IP_Line Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Equipment Communications subsystem failure None Minor IP line failure [ Location of the IP line (Shelf/Slot/Line_position) ] [ Failure cause ]: 1 = laser 2 = loss of signal 4 = edge router unreachable 8 = hold reset 16 = no PING response 32 = excessive FCS rate Threshold Info Not applicable Description Probable cause(s) This alarm is raised when an IP line has failed for one of the following causes: a) Transmission Laser failure b) LOS c) Edge Router (Next hop router) unreachable d) No response to Ping e) Excessive FCS errors rate Probable on system effects line is disabled If the associated port has no more operational line, an "IP port activity lost" alarm is raised If raised, the "IP line degraded" alarm is cleared The alarm is cleared when the card or the line is locked Probable on service effects No
172 / 245
MG#151 - IP line failure Related alarms None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If cause is "transmission laser failure", lock the IP line, replace the laser module and unlock the IP line. 2. Check that the configuration of the connected IP line is appropriate on both ends (layer 1) and is "unlocked". 3. If cause is "router unreacheable", check the L2-L3 router state and configuration on the interface to the 7570. 4. Check line cabling. 5. In case of excessive FCS error rate, check the operational state of the external optical line and FCS error rate in the receive direction using external test equipment. 6. Perform a 7570 line loopback to check the operational state of the optical line and FCS error rate of the 7570 line, using external test equipment. 7. Check response to ping. 8. End.
173 / 245
MG#152 - IP port activity lost Alarm identification Managed Object IP_Port Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Equipment Communications subsystem failure None Major IP port activity lost [ Location of the IP port (Shelf/Slot/Port) ] Not applicable Description Probable cause(s) Probable on system Probable on service This alarm is raised when both IP lines of the port of an unlocked card are disabled
effects This IP port does not transport traffic The alarm is cleared when card or both lines are locked effects Yes - MG#151 - IP line failure Corrective actions
Related alarms
On-site interven- No tion required? Actions The port repair is linked to its line repair.
174 / 245
6 SIGNALING ALARMS
This section provides all information related to the signaling alarms.
175 / 245
GSS7#1000 - Platform SS7 destination DPC unreachable Alarm identification Managed Object Routeset Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical Platform SS7 destination DPC unreachable None Not applicable Description Probable cause(s) The Destination Point cannot be reached by any route. The Destination Point or the path to the Destination Point may be down (remote cause) or there are no routes available (local cause) or the corresponding link set is in alarm state. Note: The name of the concerned RouteSet is given in the "Object Name". Destination and logical network are displayed in the object.s Name field as follows: Destination%logical_network. Probable on system Probable on service effects Destination Point applications are not available. effects Yes - GSS7#1001 - Link set out of service Corrective actions
Related alarms
176 / 245
GSS7#1000 - Platform SS7 destination DPC unreachable On-site interven- Yes tion required? Actions Signaling traffic should be routed to a backup node or application Perform each troubleshooting step in the order shown. If the system does not clear the alarm continue to the next step. Troubleshooting procedure: 1. Check if there are alarms on the link sets or individual links that compose link sets in the faulty route set. If there are troubleshoot thesealarms. 2. Call the operator in charge of the Destination Point to find out if there are any problems on that side and how long they expect the failure to continue. 3. If the Destination Point is expected to be unreachable for an undetermined period of time check your network configuration to make sure there are no other problems that could blockthe connection. 4. Else re-insert the card removed in step 1, and continue with the next card. 5. If the problem persists, contact Alcatel TASC. 6. End.
177 / 245
GSS7#1001 - Platform SS7 Link set out of service Alarm identification Managed Object Linkset Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Major Platform SS7 Link set out of service None Not applicable Description Probable cause(s) There are no active links in the link set. The link set is disabled. All links (16 links max.) in the set are locked, initializing,or not operational. Note: The name of the concerned LinkSet is given in the "Object Name". Link set name and logical network are displayed in the object.s Name field as follows:link_set%logical_network. Probable on system Probable on service effects A link set failure can mean that routes and destinations are unavailable.The redundancy of the SS7 network is in danger. effects Yes - GSS7#1002 - Signaling link out of service Corrective actions
Related alarms
On-site interven- Yes tion required? Actions You should re-enable at least one link in a link set in order to re-enable the link set. Use the SS7 management GUI to determine which links within the link set are currently unavailable, initializing, or locked. If there are locked links verify the cause. Note: To prevent hardware problems from endangering an entire link set, spread the links in the link set over several PCM or ATM connections.
178 / 245
GSS7#1002 - Platform SS7 Signaling link out of service Alarm identification Managed Object Link Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Minor Platform SS7 Signaling link out of service None Not applicable Description Probable cause(s) The link is initializing (trying to realign and resynchronizewith the end point), or is not operational. Alignment process can take several minutes, depending on thenumber of links. If the alignment process fails, the cause might be a hardware problem. Note: The name of the concerned LinkSet is given in the "Object Name". The link name is displayed in the objects Name field as follows: link_set%logical_network%SLC where SLC = Signaling Link Code. Probable on system Probable on service effects A link failure can mean that link sets and routes are unavailable. The redundancy of the SS7 network is in danger. effects Yes - GSS7#1005 - PCM link alarm - GSS7#1006 - ATM link alarm Corrective actions
Related alarms
179 / 245
GSS7#1002 - Platform SS7 Signaling link out of service On-site interven- Yes tion required? Actions Follow the steps below to restore a signaling link. After troubleshooting related alarms perform each troubleshooting step in the order shown. If the system does not clear the alarm continue tothe next step. 1. Check the path between the originating station and the Adjacent Point to determine that the equipment is working properly. 2. Contact the external link providers (telecom operator) if you cannot locate the faulty element within your network. 3. If the problem persists, contact Alcatel TASC. 4. End. Note: If you determine the signaling link will be down for a long period of time, check your SS7 configuration to ensure redundancy andavailability.
180 / 245
GSS7#1005 - Platform SS7 PCM link alarm Alarm identification Managed Object PCM_Link Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure PCM alarm (can be an SIA alarm, PVST alarm, CRC4 alarm, IA alarm, TE alarm, or a PVT alarm) Major Platform SS7 PCM link alarm None Not applicable Description Probable cause(s) An alarm signal has appeared on a PCM link (narrowband). The cause can be any element in the PCM path that hosts the PCM link: a) station hardware failure b) cable or bad connection The cause could also be related to a link problem (synchronization)associated with one of the following alarms: a) LIS alarm (Loss of Incoming Signal) b) AIS alarm (Alarm Indication Signal) c) LFA alarm (Loss of Frame Alignment) d) LCA alarm (Loss of CRC4 sub-multiframe Alignment) e) RJA (Remote Junction Alarm) f) NRJA (Non-urgent Remote Junction Alarm) It could also be related to telecom company problem outsidethe platform, or a remote end problem. Probable on system Probable on service effects Some SS7 routes, link sets and applications that use your node may be unavailable. SS7 network redundancy is reduced. effects Yes
181 / 245
GSS7#1005 - Platform SS7 PCM link alarm Related alarms - GHM#510 - Station unreachable through LSN - GHM#511 - Loss of contact - GHM#513 - Fatal software error - GHM#516 - Fatal hardware error - GHM#518 - Card failure Corrective actions On-site interven- Yes tion required? Actions Perform each troubleshooting step in the order shown. If the system does not clear the alarm continue to the next step. If there are related alarms troubleshoot these first. 1. Determine alarm origin:Display the faulty PCM object using the SS7 management GUI to find out which event caused the alarm. Depending on the event, perform the following steps: a) LIS alarm (Loss of Incoming Signal): check station cables and connections b) AIS alarm (Alarm Indication Signal): go to step2 c) LFA alarm (Loss of Frame Alignment): go to step 2 d) LCA alarm (Loss of CRC4 sub-multiframe Alignment): go to step 2 e) RJA (Remote Junction Alarm): go to step 3 f) NRJA (Non-urgent Remote Junction Alarm): go to step 3 2. Replace signaling application Interface Unit. 3. Replace signaling application card. 4. Check the other end of the PCM link 5. Contact the operator in charge of the other end of the PCM link to find out if there are any problems on that side and to determine how long the failure might last 6. Check network integrity: 7. if you determine the PCM link will be down for a long period of time 8. check your SS7 configuration to ensure redundancy and availability. a) Check the path between the originating station and the Adjacent Point to determine that the equipment is working properly. b) Contact the external link providers (telecom operator) if you cannot locate the faulty element within your network.
182 / 245
GSS7#1006 - Platform SS7 ATM link alarm Alarm identification Managed Object ATM_Link Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Major Platform SS7 ATM link alarm None Not applicable Description Probable cause(s) An alarm signal has appeared on an ATM link resulting an unavailable AAL5 connection. The ATM interface is not connected or has powered off or the link is down. The name of the ATM link is in the objects Name. Probable on system effects Some SS7 routes, link sets and applications that use your node may be unavailable. SS7 network redundancy is reduced. Probable on service effects Yes - GHM#510 - Station unreachable through LSN - GHM#511 - Loss of contact - GHM#513 - Fatal software error - GHM#516 - Fatal hardware error - GHM#518 - Card failure Corrective actions
Related alarms
183 / 245
GSS7#1006 - Platform SS7 ATM link alarm On-site interven- Yes tion required? Actions After troubleshooting related alarms perform each troubleshooting step in the order shown. If the system does not clear the alarm continue to the next step. 1. Display the faulty link using the SS7 management GUI to find out which event caused the alarm. 2. Check the other end of the link. Contact the operator in charge of the other end of the link to find out if there are any problems on that side and to determine how long the failure might last 3. Check the path between the originating stationand the Adjacent Point to determine that the equipment is working properly. 4. Contact the external link providers (telecom operator) if you cannot locate the faulty element within your network. 5. if you determine that the link will be down for a long period of time, check your SS7 configuration to ensure redundancy and availability. 6. If the problem persists, contact Alcatel TASC. 7. End.
184 / 245
GSS7#1100 - Platform SS7 Signaling gateway overload Alarm identification Managed Object Gateway Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Major Platform SS7 Signaling gateway overload None Not applicable Description Probable cause(s) The signaling gateway application station is overloaded(too much traffic). The alarm may be due to traffic bursts or a permanently highlevel of traffic on the gateway. Probable on system Probable on service effects Traffic may be lost. effects Yes None Corrective actions On-site interven- No tion required? Actions If station overload is: 1. transient: (or due to an exceptional event), use the SS7 management GUI to distribute load balancing among signaling gateways. 2. permanent : but repetitive verify network elements (such as RNCs).
Related alarms
185 / 245
G3UA#1200 - Platform SIGTRAN Association out of service Alarm identification Managed Object Association Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Minor Platform SIGTRAN Association out of service None Not applicable Description Probable cause(s) No SCTP path is available toward the remote ASP . Several causes may happen: a) All the ethernet interfaces are down. b) The cables are unplugged. c) All the stations carrying the ethernet interfaces are down. d) The routers carrying the paths are wrongly configured e) The routers carrying the paths are down. f) The ethernet switches carrying the paths are wrongly configured g) The ethernet switches carrying the paths are down. Probable on system Probable on service effects An association failure can mean that AS or SG are unavailable. The redundancy of the Sigtran network is in danger. effects Yes
186 / 245
G3UA#1200 - Platform SIGTRAN Association out of service Related alarms - GHM#510 - Station unreachable through LSN - GHM#511 - Loss of contact - GHM#513 - Fatal software error - GHM#516 - Fatal hardware error - GHM#518 - Card failure - GHM#519 - Fatal ethernet switch error - GHM#520 - Router communication failure - GHM#521 - Non-fatal router path failure - GHM#522 - Fatal router path failure Corrective actions On-site interven- Yes tion required? Actions Check the connectivity with the remote node. Troubleshooting procedure: 1. Try a ping to the remote node. 2. Check the related alarms. 3. Check the ethernet interfaces. 4. Check the cables. 5. If the problem persists, contact Alcatel TASC. 6. End.
187 / 245
G3UA#1201 - Platform SIGTRAN unreachable Application Server Alarm identification Managed Object AS Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical Platform SIGTRAN unreachable Application Server None Not applicable Description Probable cause(s) Probable on system Probable on service The local AS is down because there is no more association available to any remote AS.
effects Local applications are not available from remote AS. effects Yes - G3UA#1200 - Association out of service Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Try to have at least one association available. Troubleshooting procedure: 1. Fix the related alarms 2. Add an extra SGP or ASP to the local AS 3. If the problem persists, contact Alcatel TASC. 4. End.
188 / 245
G3UA#1202 - Platform SIGTRAN unreachable Application Server Alarm identification Managed Object AS Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical Platform SIGTRAN unreachable Application Server None Not applicable Description Probable cause(s) Probable on system Probable on service The remote AS is down because there is no more association available to any remote AS.
effects Destination Point applications are not available. effects Yes - G3UA#1200 - Association out of service Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Try to have at least one association available. Troubleshooting procedure: 1. Fix the related alarms 2. Add an extra SGP or ASP to the local AS 3. If the problem persists, contact Alcatel TASC. 4. End.
189 / 245
G3UA#1203 - Platform SIGTRAN unreachable Destination PC Node Alarm identification Managed Object PC Node Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical Platform SIGTRAN unreachable Destination PC Node None Not applicable Description Probable cause(s) The remote PC Node is down because there is no more SG available toward this PC. There is a MTP3 alarm on the node carrying the remote SG. Probable on system Probable on service effects Destination Point applications are not available. effects Yes - G3UA#1200 - Association out of service Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Ask the remote operator if there is currently a MTP3 alarm on his site. Try to have at least one SG available. Troubleshooting procedure: 1. Fix the related alarms 2. Add an extra SG to the PC Node 3. If the problem persists, contact Alcatel TASC. 4. End.
190 / 245
MG#260 - 7570 SCTP Association Not Established Alarm identification Managed Object Association Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical 7570 SCTP Association Not Established None Not applicable Description Probable cause(s) No SCTP path is available toward the remote ASP with following potential causes: a) The SCTP configuration data are erroneous b) The Switch Cards Ethernet ports are down c) The Ethernet cables are unplugged. d) The routers carrying the paths are wrongly configured e) The routers carrying the paths are down. f) The remote Application Server (AS) is down. Probable on system Probable on service effects An association failure can mean that AS or SG are unavailable. The redundancy of the Sigtran network is in danger. effects Yes - MG#261 - Application Server (AS) not active - MG#262 - 7570 SCTP Association Not active - MG#263 - 7570 SS7 Signaling link out of service Corrective actions
Related alarms
191 / 245
MG#260 - 7570 SCTP Association Not Established On-site interven- Yes tion required? Actions Check the connectivity with the remote node. Troubleshooting procedure: 1. Try a ping to the remote node 2. Check the related alarms 3. Check the ethernet interfaces 4. Check the cables 5. If the problem persists, contact Alcatel-Lucent Technical Support Center 6. End
192 / 245
MG#261 - Application Server (AS) not active Alarm identification Managed Object Association Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical Application Server (AS) not active None Not applicable Description Probable cause(s) This alarm is raised if the local Signalling Gateway is not in AS_ACTIVE state a) The Switch Cards Ethernet ports are down b) The Ethernet cables are unplugged. c) The routers carrying the paths are wrongly configured d) The routers carrying the paths are down. e) The remote Application Server (AS) is down. Probable on system Probable on service effects An association failure can mean that AS is unavailable. The redundancy of the Sigtran network is in danger. effects Yes - MG#260 - 7570 SCTP Association Not Established - MG#262 - 7570 SCTP Association Not active - MG#263 - 7570 SS7 Signaling link out of service Corrective actions
Related alarms
193 / 245
MG#261 - Application Server (AS) not active On-site interven- Yes tion required? Actions Check the connectivity with the remote node. Troubleshooting procedure: 1. Try a ping to the remote node 2. Check the related alarms 3. Check the ethernet interfaces 4. Check the cables 5. If the problem persists, contact Alcatel-Lucent Technical Support Center 6. End
194 / 245
MG#262 - 7570 SCTP Association Not active Alarm identification Managed Object Association Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical 7570 SCTP Association Not active None Not applicable Description Probable cause(s) This alarm is raised if the local Signalling Gateway is not in ASP_ACTIVE state a) The Switch Cards Ethernet ports are down b) The Ethernet cables are unplugged. c) The routers carrying the paths are wrongly configured d) The routers carrying the paths are down. e) The remote Application Server Processor (ASP) is down. f) The remote Application Server (AS) is down. Probable on system Probable on service effects An association failure can mean that AS is unavailable. The redundancy of the Sigtran network is in danger. effects Yes - MG#260 - 7570 SCTP Association Not Established - MG#261 - Application Server (AS) not active - MG#263 - 7570 SS7 Signaling link out of service Corrective actions
Related alarms
195 / 245
MG#262 - 7570 SCTP Association Not active On-site interven- Yes tion required? Actions Check the connectivity with the remote node. Troubleshooting procedure: 1. Try a ping to the remote node 2. Check the related alarms 3. Check the ethernet interfaces 4. Check the cables 5. If the problem persists, contact Alcatel-Lucent Technical Support Center 6. End
196 / 245
MG#263 - 7570 SS7 Signaling link out of service Alarm identification Managed Object Association Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical 7570 SS7 Signaling link out of service None Not applicable Description Probable cause(s) The link is initializing (trying to realign and resynchronize with the end point), or is not operational. Alignment process can take several minutes, depending on thenumber of links. If the alignment process fails, the cause might be a hardware problem. You may also check your configuration data Note: The link name is displayed in the object Name field as follows: Shelf/Slot/line number or H-M-P/TS. Probable on system Probable on service effects A link failure can mean that link sets and routes are unavailable. The redundancy of the SS7 network is in danger. effects Yes - MG#260 - 7570 SCTP Association Not Established - MG#261 - Application Server (AS) not active - MG#262 - 7570 SCTP Association Not active Corrective actions
Related alarms
197 / 245
MG#263 - 7570 SS7 Signaling link out of service On-site interven- Yes tion required? Actions Follow the steps below to restore a signaling link. After troubleshooting related alarms perform each troubleshooting step in the order shown. If the system does not clear the alarm continue to the next step. 1. Check the path between the originating station and the Adjacent Point to determine that the equipment is working properly. 2. Contact the external link providers (telecom operator) if you cannot locate the faulty element within your network. 3. If the problem persists, contact Alcatel-Lucent Technical Support Center. 4. End. Note: If you determine the signaling link will be down for a long period of time, check your SS7 configuration to ensure redundancy andavailability.
198 / 245
7 RESOURCE ALARMS
This section provides all information related to the resource alarms.
199 / 245
MG#160 - Loss of extra (1) VPP resources Alarm identification Managed Object VPP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Major Loss of extra (1) VPP resources [ Function ] = VPP Not applicable Description Probable cause(s) 7570 is configured with N+1 VPP cards One VPP card is disabled Probable on system effects No effect on system because subscriber traffic is allocated normally to remaining enabled VPP cards, but there is no more spare VPP resources in the system Alarm MG#162 is cleared Probable on service effects No None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Identify VPP card disabled. 2. If disabled reason is "locked", unlock the card. 3. If disabled reason is "not present", insert the card. 4. If disabled reason is "failed", replace the card and send the faulty card to the repair service. 5. End.
Related alarms
200 / 245
MG#161 - Loss of extra (1) IP resources Alarm identification Managed Object IP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Major Loss of extra (1) IP resources [ Function ] = IP Not applicable Description Probable cause(s) Probable on system Number of disabled IP ports of 7570 becomes equal to 1
effects No effect on system because subscriber traffic is allocated normally to remaining enabled IP ports, but there is no more spare IP bandwidth in the system Alarm MG#163 is cleared
Probable on service
effects No - MG#152 - IP port activity lost Corrective actions
Related alarms
On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Identify IP port disabled. 2. If disabled reason is "card locked", unlock the card. 3. If disabled reason is "card not present", insert the card. 4. If disabled reason is "card failed", replace the card and send the faulty card to the repair service. 5. If disabled reason is "IP line(s) locked", unlock the IP line(s). 6. If disabled reason is "IP line(s) failed", repair the IP line(s) - see related alarm. 7. End.
201 / 245
MG#162 - Loss of several VPP resources Alarm identification Managed Object VPP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Critical Loss of several VPP resources [ Function ] = VPP Not applicable Description Probable cause(s) 7570 is configured with N+1 VPP cards More than one VPP card are disabled Probable on system effects Subscriber traffic is distributed to remaining enabled VPP cards on a per call basis, and part of the calls are rejected due to lack of VPP resources in the system Alarm MG#160 is cleared Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Identify VPP cards disabled. 2. For each disabled card: 3. If disabled reason is "locked", unlock the card. 4. If disabled reason is "not present", insert the card. 5. If disabled reason is "failed", replace the card and send the faulty card to the repair service. 6. End.
Related alarms
202 / 245
MG#163 - Loss of several IP resources Alarm identification Managed Object IP Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Critical Loss of several IP resources [ Function ] = IP Not applicable Description Probable cause(s) 7570 is configured with N+1 IP ports More than one IP port are disabled Probable on system effects Subscriber traffic is distributed to remaining enabled IP ports on a per call basis, and part of the calls are rejected due to lack of IP bandwidth in the system Alarm MG#161 is cleared Probable on service effects Yes - MG#152 - IP port activity lost - MG#161 - Loss of extra (1) IP resources Corrective actions
Related alarms
203 / 245
MG#163 - Loss of several IP resources On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Identify IP ports disabled. 2. For each IP port disabled: 3. If disabled reason is "card locked", unlock the card. 4. If disabled reason is "card not present", insert the card. 5. If disabled reason is "card failed", replace the card and send the faulty card to the repair service. 6. If disabled reason is "IP line(s) locked", unlock the IP line(s). 7. If disabled reason is "IP line(s) failed", repair the IP line(s) - see related alarm. 8. End.
204 / 245
MG#170 - Remote NE is isolated Alarm identification Managed Object AAL2_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Major Remote NE is isolated [ Remote_NE ] Not applicable Description Probable cause(s) This alarm is raised when a remote NE is isolated. The system provides the reason: a) SS7 PC inaccessible b) no more AAL2 path available Probable on system Probable on service effects No more call can be established with this RNC or this remote NE effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following verifications in the given order: 1. Check the point code of the remote NE and the configured one. 2. Check the availibility of the SS links. 3. Check the availibility of the remote NE. 4. End.
Related alarms
205 / 245
MG#180 - Handoff erroneous referenced for secondary MGC Alarm identification Managed Object MGC_address Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Major Handoff erroneous referenced for secondary MGC [ MGC_address ] Not applicable Description Probable cause(s) This alarm is raised when the 7570 tries to perform a handoff on an IP address which is not configured in the MGC list Types of failure are: a) 7570 configuration error b) Potential security threat c) Error in the call server Probable on system effects This Alarm is raised as soon as such a message appears This alarm is cleared when no message appears for 5 minutes The handoff is not accepted The 7570 tries to continue to work with the current MGC If the communication is lost, the 7570 tries the other MGC of the configured MGC list Probable on service effects Yes None Corrective actions
Related alarms
206 / 245
MG#180 - Handoff erroneous referenced for secondary MGC On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Configure the MGC list in the 7570 if it is a configuration mistake. 2. Check the configuration in the MGC and modify this configuration if needed. 3. Increase the IP security for the H.248 protocol. 4. End.
207 / 245
MG#181 - Connection to MGC is impossible Alarm identification Managed Object Platform_MG Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Remote node transmission error None Critical Connection to MGC is impossible None Not applicable Description Probable cause(s) Connection to MGC is impossible Types of failure are: a) 7570 configuration error b) The MGC is down c) Error in the IP network Probable on system effects Connection to MGC is impossible No traffic can be established The Alarm is raised as soon as the global list of the MGC has been used unsuccessfully for dialog initialization This alarm is cleared when the communication is established again When this alarm is present, 7570 operational state is "disabled" with reason "connection to MGC is impossible" Probable on service effects Yes None Corrective actions
Related alarms
208 / 245
MG#181 - Connection to MGC is impossible On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check if the MGC and the possible redundant MGC are available (trace route may be used). if not, repair the MGC. 2. Check if the IP network is available by a trace route, for example. If not repair it. 3. Check the Configured MGC list (IP address and other MGC data) and modify it, if necessary. 4. End.
209 / 245
MG#182 - First state of regulation Alarm identification Managed Object Resource_control Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service CPU cycles limit exceeded None Minor First state of regulation [ Traffic (in Call Attempts Per Second) ] [ Overload origin ]: 1=Megacop 2=Media Adaptation 3=Megacop traffic acceptable 4=Trillium stack 5=Lowest priority task Threshold Info Not applicable Description Probable cause(s) This alarm is raised when the capacity of the 7570 is reached Possible types of failure are: a) Too much traffic is coming into the 7570 b) The traffic has too many bursts and there are too many calls to the 7570 at the same time c) The H.248.10 package is not used in the call server Probable on system effects The call server is required to reduce the number of calls: a) The 7570 requires the MGC to reduce the H.248 traffic with the help of H.248.10 package (if used by the MGC) b) The 7570 notifies the MGC (with the chp/mgcon event) to reduce the traffic by a factor of R from 0 to 100%. It represents the percentage of load that the MGC is requested to block This alarm is raised as soon as the overload appears This alarm is cleared when a higher overload appears or when there is no overload for 5 minutes Probable on service effects Yes
210 / 245
MG#182 - First state of regulation Related alarms None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Reduce the traffic in the 7570 by removing 2G, 3G or UMA access. 2. Activate the H.248.10 package in the call server. 3. Contact your Alcatel-Lucent Technical Support Center to request a CPU extension. 4. End.
211 / 245
MG#183 - Second state of regulation Alarm identification Managed Object Resource_control Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service CPU cycles limit exceeded None Major Second state of regulation [ Traffic (in Call Attempts Per Second) ] [ Overload origin ]: 1=Megacop 2=Media Adaptation 3=Megacop traffic acceptable 4=Trillium stack 5=Lowest priority task Threshold Info Not applicable Description Probable cause(s) This alarm is raised when the capacity of the 7570 is reached Possible types of failure are: a) Too much traffic is coming into the 7570 b) The traffic has too many bursts and there are too many calls to the 7570 at the same time c) The MGC does not reduce the traffic enough, or it does not reduce it quickly enough
212 / 245
MG#183 - Second state of regulation Probable on system effects The call server is required to reduce the number of calls a) The 7570 requires the MGC to reduce the H.248 traffic with the help of H.248.10 package b) The 7570 notifies the MGC (with the chp/mgcon event) to reduce the traffic by a factor of R from 0 to 100%. It represents the percentage of load that the MGC is requested to block c) In addition, the 7570 refuses any traffic relative to new H.248 contexts (if the H.248 priority is higher than 8 or if an emergency call indicator is set up, the new contexts are accepted) This alarm may be changed to a minor alarm if the MGC does not use the H.248.10 "Overload package" This alarm is raised as soon as the overload appears This alarm is cleared when a higher overload appears or when no overload occurs for at least 5 minutes Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Reduce the traffic of the 7570 by removing 2G, 3G or UMA Access. 2. Activate the H.248.10 package in the call server. 3. Contact your Alcatel-Lucent Technical Support Center to request a CPU extension. 4. End.
Related alarms
213 / 245
MG#184 - Higher state of regulation before 7570 crash Alarm identification Managed Object Resource_control Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Quality of service CPU cycles limit exceeded None Critical Higher state of regulation before 7570 crash [ Traffic (in Call Attempts Per Second) ] [ Overload origin ]: 1=Megacop 2=Media Adaptation 3=Megacop traffic acceptable 4=Trillium stack 5=Lowest priority task Threshold Info Not applicable Description Probable cause(s) This alarm is raised when the capacity of the 7570 is reached Possible types of failure are: a) Too much traffic is coming into the 7570 b) The traffic has too many bursts, and there are too many calls to the 7570 at the same time c) The MGC does not reduce the traffic enough, or does not reduce it quickly enough
214 / 245
MG#184 - Higher state of regulation before 7570 crash Probable on system effects Calls are no longer processed; only subtracts are made The call server is required to reduce the number of calls a) The 7570 requires the MGC to reduce the H.248 traffic with the help of H.248.10 package b) The 7570 notifies the MGC (with the chp/mgcon event) to reduce the traffic by a factor of R from 0 to 100%. It represents the percentage of load that the MGC is requested to block c) In addition, the 7570 accepts subtract commands and only in a proportion of 20% of the acceptable H.248 command. Commands for new context are rejected with error xxx This Alarm is raised as soon as the overload appears This alarm is cleared when a higher overload appears or when no overload occurs for at least 5 minutes Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Megacop overload, MA overload, Megacop traffic acceptable, trillium stack overload, lowest priority task overload
Related alarms
215 / 245
MG#185 - Profile negotiation failed with MGC Alarm identification Managed Object MGC_address Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Communication Communications subsystem failure None Critical Profile negotiation failed with MGC [ Profile sent by MGC to 7570 ] Not applicable Description Probable cause(s) This alarm is raised when a profile negotiation between MGC and 7570 failed Possible type of failure is: a) 7570 profile list not compliant with MGC supported profiles Probable on system effects 7570 is not registered by MGC This alarm is raised as soon as a profile given by MGC is unknown by 7570 This alarm is cleared when 7570 is registered with MGC Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Match 7570 and MGC profile lists. 2. End.
Related alarms
216 / 245
MG#200 - Loss of IP Bandwidth Alarm identification Managed Object Common_Media_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Not applicable Description Probable cause(s) This alarm is raised when the available bandwidth is insufficient to establish an IP bearer for a call Possible types of failure are: a) More than one IPGE is in failure b) Loss of IPGE c) Loss of bandwidth on IPGE Probable on system effects Call will not be established This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions Quality of service Resource at or nearing capacity None Minor Loss of IP Bandwidth
Related alarms
217 / 245
MG#200 - Loss of IP Bandwidth On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check the availability of the IP Port. If it is not available, restore its availability. 2. If the AAL2 path is available, add AAL2 path or increase the bandwidth of AAL2 path if the maximum bandwidth is not reached. 3. End.
218 / 245
MG#201 - Loss of ATM bandwidth Alarm identification Managed Object AAL2_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Loss of ATM bandwidth [ Remote NE ] Not applicable Description Probable cause(s) This alarm is raised when the available bandwidth is not enough to establish an AAL2 bearer for a call Possible types of failure are: a) A call initialized by the remote side is incompatible with the allowed bandwidth b) Call initialized by the local side: Loss of bandwidth on an AAL2 path c) Call initialized by the local side: One ATMx card is in failure without redudant card d) Call initialized by the local side: Lack of AAL2 path Probable on system effects Call will not be established This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions
Related alarms
219 / 245
MG#201 - Loss of ATM bandwidth On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check the availability of the AAL2 path toward this remote NE. 2. It it is not available, restore the availability of these AAL2 paths. 3. If it is available, add the AAL2 path. 4. End.
220 / 245
MG#202 - Lack of codec Alarm identification Managed Object Codec_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of codec [ Codec_type ] Not applicable Description Probable cause(s) This alarm is raised in case of lack of codec type Possible types of failure are: a) More one than one VPP has failed b) Lack of VPP c) Bad package configuration Probable on system effects Call will not be established This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions
Related alarms
221 / 245
MG#202 - Lack of codec On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check the availability of the VPP cards (one can stay out of service). If it is not available, restore the availability of the VPP cards. 2. Check the codec and IWF pakage measurement. If all codec packages and IWF packages are in overload, you must add a VPP or choose (at MGC level) a codec that requires less DSP processing like G711. If some codec packages are in overload, and others are not, the configuration of the DSP must be changed. 3. End.
222 / 245
MG#203 - Lack of echo canceling Alarm identification Managed Object Line_card_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of echo canceling [TDM/X address (Shelf/Slot) ] Not applicable Description Probable cause(s) This alarm is raised in case of lack of echo cancelling Possible types of failure are: a) The does not have enough echo cancelling b) A wrong port is attached to the TDMX (PSTN port instead of PLMN port for example) c) Too many ports are attached to this TDMX Probable on system effects Call will be established without EC This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions
Related alarms
223 / 245
MG#203 - Lack of echo canceling On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Change the TDMX variant to increase the percentage of EC or VQE. 2. Move some ports that need EC or VQE to another TDMX. 3. Add TDMX and balance TDMX loads (in terms of E1 or STM1 port). 4. End.
224 / 245
MG#204 - Lack of Voice quality enhancement processing Alarm identification Managed Object Line_card_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of Voice quality enhancement processing [TDM/X address (Shelf/Slot) ] Not applicable Description Probable cause(s) This alarm is raised in case of lack of Voice Quality Enhancement (VQE) Possible types of failure are: a) The TDMX does not have enough Voice Quality Enhancement process b) A wrong port is attached to the TDMX (PSTN port instead of PLMN port for example) c) Too many ports are attached to this TDMX Probable on system effects Call will be established without VQE processing This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions
Related alarms
225 / 245
MG#204 - Lack of Voice quality enhancement processing On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Change the TDMX variant to increase the percentage of EC or VQE. 2. Move some ports that need EC or VQE to another TDMX. 3. Add TDMX and balance TDMX loads (in terms of E1 or STM1 port). 4. End.
226 / 245
MG#205 - Lack of MF generator Alarm identification Managed Object Line_card_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of MF generator [ Line card address (Shelf/Slot) ] Not applicable Description Probable cause(s) This alarm is raised in case of a lack of MF generators The number of DTMF generators is reached due to excessive use of DTMF Probable on system effects DTMF is not transmitted This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If a TDMX is concerned, balance 2G//PLMN or PSTN port on the card to reduce the load of the card. 2. If a VPP is concerned, add a VPP card. 3. End.
Related alarms
227 / 245
MG#206 - Lack of MF receiver Alarm identification Managed Object Line_card_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of MF receiver [ Line card address (Shelf/Slot) ] Not applicable Description Probable cause(s) This alarm is raised in case of a lack of MF receiver The number of DTMF receiver is reached due to excessive use of DTMF Probable on system effects DTMF is not transmitted This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If a TDMX is concerned, balance 2G//PLMN or PSTN port on the card to reduce the load of the card. 2. If a VPP is concerned, add a VPP card. 3. End.
Related alarms
228 / 245
MG#208 - Lack of announcement generator Alarm identification Managed Object Line_card_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of announcement generator [ Line card address (Shelf/Slot) ] Not applicable Description Probable cause(s) This alarm is raised in case of a lack of special tones generator The number of announcement generator is reached due to excessive use of announcements Probable on system effects Announcement is not sent This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. If a TDMX is concerned, balance 2G//PLMN or PSTN port on the card to reduce the load of the card. 2. If a VPP is concerned, add a VPP card. 3. Reduce the number of cases where an announcement is sent. 4. End. Warning: if the cause is a big crash in the network the alarm will disappear when the crash will end so the action is to repair the crash
Related alarms
229 / 245
MG#209 - Lack of conference bridge Alarm identification Managed Object Common_Media_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of conference bridge none Not applicable Description Probable cause(s) This alarm is raised in case of a lack of conference bridge The number of conference bridges is reached due to: a) More one than one VPP is in failure b) Lack of VPP c) IP address for conference not configured Note : For each TDMX with an operational state "enabled" and a protection state "active" or "none", related conference bridge resources are lost. Because need of these resources may be considered related to TDMX traffic, it is rational to think that changes of TDMX states dont generate a lack of conference bridge. Probable on system effects The conference cannot be established This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions
Related alarms
230 / 245
MG#209 - Lack of conference bridge On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. The conference bridges of VPP and TDMX are in pool. So first check the availability of the N VPP if any (one can stay out of service), and if it is not available restore the availability of these VPP . 2. Check if the IP address for conference is configured, and if it is not, configure an IP address for conference not used in the IP network. 3. Add a VPP card. 4. End.
231 / 245
MG#210 - Lack of continuity check resources Alarm identification Managed Object Line_card_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of continuity check resources [ TDMX address (Shelf/Slot) ] Not applicable Description Probable cause(s) This alarm is raised in case of lack of continuity check resource The number of continuity check resource is reached due to excessive use of continuity check Probable on system effects The continuity check will fail All TS will be unaivailable as long as no continuity check is successfull This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Mix BSC and ISUP terminations on this TDMX to reduce the need of ISUP terminations on this TDMX. 2. Require continuity check only on demand or with cyclic maintenance. 3. End.
Related alarms
232 / 245
MG#211 - Lack of IWF Alarm identification Managed Object IWF_resources Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Quality of service Resource at or nearing capacity None Minor Lack of IWF [ IWF_type ] Not applicable Description Probable cause(s) This alarm is raised in case of lack of IWF type Possible types of failure are: a) More one than one VPP has failed b) Lack of VPP c) Bad package configuration Probable on system effects Call will not be established This alarm is raised as soon as 15 lack of resource events occur within 15 minutes This alarm is cleared when no lack of resource event occurs within a period of 15 to 30 minutes Probable on service effects Yes None Corrective actions
Related alarms
233 / 245
MG#211 - Lack of IWF On-site interven- Yes tion required? Actions Perform the following actions in the given order: 1. Check the availability of the N VPP (one can stay out of service). If it is not available, restore the availability of the VPP . 2. Check the codec and IWF pakage measurement. If all codec and IWF packages are in overload, you must add a VPP If some IWF . packages are in overload, and others are not, change the configuration of the DSP . 3. End.
234 / 245
8 MGC10 SYNTHESIS ALARMS

This section is applicable only when the 7570 MG platform supports the Alcatel-Lucent 5020 Media Gateway Controller-10 (MGC10) product. It provides all information related to the MGC10 synthesis alarms. In the following alarm definitions, E10 refers to the MGC10. For more information about MGC10 alarms description, see the Alcatel-Lucent 5020 MGC10 Alarms Dictionary, ALA283.
235 / 245
E10#1 - Total MGC Failure Alarm identification Managed Object E10_supervision Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service This alarm is raised when MGC10 becomes out of service or runs in non connected mode Equipment Equipment malfunction None Critical Total MGC Failure
effects a) The MGC10 may be out of service. b) Operation of the MGC10 may be unavailable. effects Yes None Corrective actions
Related alarms
On-site interven- No tion required? Actions Perform the following actions in the given order: 1. Restart the MGC10 (see the MGC10 maintenance information). 2. If this alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 3. End.
236 / 245
E10#2 - MGC Call Server synthesis - IM Alarm identification Managed Object E10_supervision Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service This alarm is raised when at least one critical alarm is present on the MGC10 subsystem. Quality of service Performance degraded None Critical MGC Call Server synthesis - IM
effects Dependent on the alarm raised at the MGC10. effects Yes None Corrective actions
Related alarms
On-site interven- No tion required? Actions See the MGC10 Alarm Management GUI to perform the actions for each alarm.
237 / 245
E10#3 - MGC Call Server synthesis - ID Alarm identification Managed Object E10_supervision Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service This alarm is raised when at least one major alarm is present on the MGC10 subsystem. Quality of service Performance degraded None Major MGC Call Server synthesis - ID
Related alarms
238 / 245
E10#4 - MGC Call Server synthesis - SI Alarm identification Managed Object E10_supervision Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service This alarm is raised when at least one minor alarm is present on the MGC10 subsystem. Quality of service Performance degraded None Minor MGC Call Server synthesis - SI
Related alarms
239 / 245
E10#5 - MGC Internal System Backup Missing Alarm identification Managed Object E10_supervision Class (MOC) Alarm type Probable cause Specific problem Severity Additional Text Additional Info Threshold Info Not applicable Description Probable cause(s) Probable on system Probable on service This alarm is raised when the internal MGC10 system backup is missing or faulty. Processing error Sofware error None Minor MGC Internal System Backup Missing
effects As long as this alarm is present, you cannot launch an MGC10 application backup. effects No None Corrective actions
Related alarms
On-site interven- No tion required? Actions Perform the following actions in the given order: 1. Open a telnet windows with OAM IP address of the platform. 2. Launch the internal MGC10 system backup using the following Linux command: touch /e10/pivot/e10proxy/syst_backup.flag 3. If this alarm is still not cleared, contact your Alcatel-Lucent Technical Support Center. 4. End.
240 / 245
ABBREVIATIONS
2G 2G 3G 3G second Generation Second Generation third Generation Third Generation
A
AAL2 AAL5 AIS ATM ATM Adaptation Layer type 2 ATM Adaptation Layer type 5 Alarm Indication Signal Asynchronous Transfer Mode
B
BIOS BSS Basic Input Output System Base Station Subsystem
C
CC COAL CPU Continuity Check Configuration and Alarms Central Processing Unit
E
ECC EPS Error Correction Code Equipment Protection Switch
F
FCS FRU Frame Check Sequence Field Replaceable Unit
G
GPRS GSM GUI General Packet Radio Service Global System for Mobile communications Graphical User Interface
H
HW HardWare
I
I/O ID IM IPGE Input/Output deferred action IMmediate action Internet Protocol packet processing over Gigabit Ethernet
241 / 245
IP IPMB IPMC ITU-T sector IU IWF
Internet Protocol Intelligent Platform Management Bus Intelligent Platform Management Controller International Telecommunication Union - Telecommunication standardization Interface Unit InterWorking Function
L
LANIO LCA LFA LIS LIU LOC LSN Local Area Network Input/Output Loss of CRC4 sub-multiframe Alignment Loss of Frame Alignment Loss of Incoming Signal Line Interface Unit Loss Of Continuity Local Secured Network
M
MGC MG MIB MOC MSM Media Gateway Controller Media Gateway Management Information Base Managed Object Class Multiple Storage Module
N
NE NRJA Network Element Non-urgent Remote Junction Alarm
O
OAM Operation, Administration and Maintenance
P
PCM PDH PDU PEM PMC Pulse Code Modulation Plesiochronous Digital Hierarchy Power Distribution Unit Power Entry Module PCI Mezzanine Card
R
RAP RDI RJA RNC Rack Alarm Panel Remote Defect Indication Remote Junction Alarm Radio Network Controller
242 / 245
S
SDH SHMC SI SS7 SS7 Synchronous Digital Hierarchy Shelf Management Controller without action Signaling System Nº7 Signaling System N7
T
TASC TDM Technical Assistance and Support Center Time Division Multiplexing
U
UE UMA UTRAN User Equipment Unlicensed Mobile Access UMTS Terrestrial Radio Access Network
V
VCC VC VPC VPP VP Virtual Channel Connection Virtual Channel Virtual Path Connection Voice Packet Processing Virtual Path
243 / 245
244 / 245
INDEX
A
Alarm description overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
H
Hardware alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
I
Infrastructure alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
L
Line and port alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
M
MGC10 alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
R
Resource alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
S
Signaling alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Software alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
245 / 245

7570 Alarms Dictionary 3bl77057acbarkzza 04 en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

7570 Alarms Dictionary 3bl77057acbarkzza 04 en

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent 7570 Media Gateway

7570 ALARMS DICTIONARY

3BL 77057 ACBA RKZZA Ed.04

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

3BL 77057 ACBA RKZZA Ed.04

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

Chapter 2 Chapter 3 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Abbreviations

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

1.1 About alarms

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

Table 1: Alarm dictionary information element Alarm Management GUI parameter

Alarm information elements Corresponding ITU-T X.733 alarm reporting parameter

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

Alarm dictionary information element

Alarm Management GUI parameter

Corresponding ITU-T X.733 alarm reporting parameter

Infor- Additional mation

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

Alarm dictionary information element

Alarm Management GUI parameter

Corresponding ITU-T X.733 alarm reporting parameter

None None None

Event Time Source Instance Source Type

Event time Source Source class Description

Probable effects on None system

Probable effects on None service

At- Monitored tributes

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

Alarm dictionary information element

Alarm Management GUI parameter

Corresponding ITU-T X.733 alarm reporting parameter n.a. n.a.

On-site intervenNone tion required? Actions None

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

1.2 MG alarm trigger mechanisms

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

If the line card is of type... TDMX or ATMX

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

If the line card is of type... TDMX or ATMX

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

If the line card is of type... TDMX or ATMX

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

If the line card is of type... TDMX or ATMX

3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

If the line card is of type... TDMX or ATMX

3BL 77057 ACBA RKZZA Ed.04