7570 Alarms Dictionary 3bl77057acbarkzza 04 en[1]

Alcatel-Lucent7570 MediaGateway

7570 ALARMS DICTIONARY

3BL 77057 ACBA RKZZA Ed.04

Status RELEASED 25/04/2008

Mnemonic ALAOPG

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.

2 / 245 3BL 77057 ACBA RKZZA Ed.04

7570 Alarms Dictionary

CONTENTS

PREFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 ALARM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 About alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.2 MG alarm trigger mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.2.1 ATCA line card extracted, locked or powered off . . . . . . . . . . . . . . . . . . . . 131.2.2 ATCA line card inserted, powered on or unlocked . . . . . . . . . . . . . . . . . . . 161.2.3 ATCA line card reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.2.4 Overheated event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

2 HARDWARE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 INFRASTRUCTURE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4 SOFTWARE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

5 LINE AND PORT ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

6 SIGNALING ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

7 RESOURCE ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

8 MGC10 SYNTHESIS ALARMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

ABBREVIATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

3BL 77057 ACBA RKZZA Ed.04 3 / 245

4 / 245 3BL 77057 ACBA RKZZA Ed.04


PREFACEThis dictionary dedicated to the Alcatel-Lucent 7570 Media Gateway (MG) describes all the alarmsraised 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 GraphicalUser Interface (GUI), and describes the alarm trigger mechanisms for theATCA line cards.

Chapter 2 describes all alarms raised by the 7570 related to the hardware. You willfind troubleshooting actions for each of these alarms.

Chapter 3 describes all alarms raised by the 7570 related to the infrastructure. You willfind troubleshooting actions for each of these alarms.

Chapter 4 describes all alarms raised by the 7570 related to the software. You will findtroubleshooting actions for each of these alarms.

Chapter 5 describes all alarms raised by the 7570 related to line and port. You willfind troubleshooting actions for each of these alarms.

Chapter 6 describes all alarms raised by the 7570 signaling. You will find troubleshoot-ing actions for each of these alarms.

Chapter 7 describes all alarms raised by the 7570 resources. You will find troubleshoot-ing actions for each of these alarms.

Chapter 8 describes MGC10 synthesis alarms. You will find troubleshooting actions foreach of these synthesis alarms.

Abbreviations List of all abbreviations used in this document.

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.

3BL 77057 ACBA RKZZA Ed.04 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. Certainacronyms 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 Equip-ment) 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 pro-vides 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 ina 2G or a 3G network.

6 / 245 3BL 77057 ACBA RKZZA Ed.04


1 ALARM OVERVIEWThis chapter introduces alarm basics and defines the types of information this guide provides to de-scribe 7570 alarms.

3BL 77057 ACBA RKZZA Ed.04 7 / 245


1.1 About alarmsThere 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 longerpresent.

Note: Alarm Management enables you only to consult the list of raised alarms. The cause ofthe 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 CurrentAlarms 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 alarminformation, 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 tothe International Telecommunication Union - Telecommunication standardization sector (ITU-T) X.733Recommendation standard information elements. Table 1 gives a description of the fields used in thepresent guide as well as the correspondence between the Alarm Management GUI, this dictionary andthe ITU-T X.733 Recommendation.

8 / 245 3BL 77057 ACBA RKZZA Ed.04


Table 1: Alarm information elements

Alarmdictionaryinformationelement

AlarmManagementGUI parameter

CorrespondingITU-T X.733

alarm reportingparameter

Description

Alarm identification

Managed ObjectClass (MOC)

None Managed objectContains the alarm source identifier(NE type/Friendly Name)

Alarm type Event Type Event type

Identifies the type of alarm:

- Quality of Service

- Communications

- Processing Error

- Equipment

- Environmental

Probable causeProbable Cause(Id)

Probable causeIndicates the probable cause of thealarm based on ITU-T Recommen-dation X.733.

Specific problems Specific Problems Specific problems

Identifies further refinements to theprobable cause of the alarm

Qualifies the chosen ProbableCause and may be used by themanaged object class definer tospecify a set of identifiers for use inmanaged object classes

3BL 77057 ACBA RKZZA Ed.04 9 / 245






Description

Severity Severity Perceived severity

Defines severity levels

The levels defined for use with thismandatory parameter in the Alarmmanagement GUI are:

- Indeterminate: indicates thatthe severity level cannot be de-termined

- Critical: indicates that a serviceaffecting condition has occurredand an immediate corrective ac-tion is required

- Major: indicates that a ser-vice affecting condition has de-veloped and an urgent correc-tive action is required

- Minor: indicates a non-serviceaffecting fault condition and thatcorrective action is required toprevent a more serious (for ex-ample, service affecting) fault

- Warning: indicates the detec-tion of a potential or impend-ing service affecting fault, be-fore any significant effects havebeen felt. Action to further diag-nose or correct the problem is re-quired to prevent a more seriousfault

Additional text Alarm Description Additional textA free form text description of thealarm

Additional infoAdditional Infor-mation

Additional infor-mation

A set of additional information inthe event report. It consists of a se-ries of data structures each of whichcontains 3 items of information:

- an identifier

- a significance indicator

- problem information

10 / 245 3BL 77057 ACBA RKZZA Ed.04






Description

Threshold info Threshold InfoThreshold informa-tion

This parameter is present whenthe alarm is a result of crossing athreshold. It consists of four subpa-rameters:

- triggered threshold

- threshold level

- observed value

- arm time

None Event Time Event time Contains the date and time at whichthe alarm was raised

None Source Instance Source Contains the alarm source identifier

None Source Type Source class Contains the alarm source type

Description

Probable cause(s)Probable Cause(Name)

n.a. Provides further information on theprobable cause of the alarm

Probable effects onsystem

None n.a.Provides a description of any prob-able effects on operation of the sys-tem

Probable effects onservice

None n.a.

Provides a description of any prob-able effects on the quality of serviceprovided by the telecommunicationnetwork

Related alarms None n.a.

Provides information about otheralarms that may have been raisedas a result of the raising of thisalarm.

None Monitored At-tributes

Monitored at-tributes

Defines one or mores attributes ofthe managed object and the corre-sponding values at the time of thealarm

Managed object definers may spec-ify the set of attributes which areof interest, if any. This allows, forexample, the timely reporting ofchanging conditions prevalent atthe time of the alarm

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 11 / 245






Description

On-site interven-tion required?

None n.a.Contains an indication on whetheron-site intervention is required torectify the problem

Actions None n.a. 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, AL-EXPL.

12 / 245 3BL 77057 ACBA RKZZA Ed.04


1.2 MG alarm trigger mechanismsThe 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.

3BL 77057 ACBA RKZZA Ed.04 13 / 245


If the line card is of type... then... and if...

TDMX or ATMX

with the protection role: protec-tion

actions depend on previous op-erational state and protectionstate of protection card

the previous state(s) is:

- disabled

No action (alarm MG#20"EPS protection lost" is al-ready raised)

- enabled-standby

Minor alarm MG#20 "EPSprotection lost" is raised

- enabled-protecting

1) Protection mode ofprotection card be-comes "standby"

2) Minor alarm MG#20"EPS protection lost" israised

3) Protection mode of re-lated working card be-comes "active". Ac-cording to the previousoperational state of re-lated working card:

• working card enabled:EPS forces a switchback (protection cardfunctions switch overto working card)

• working card dis-abled: critical alarmMG#21 "Card activitylost" is raised referenc-ing the working card

14 / 245 3BL 77057 ACBA RKZZA Ed.04



TDMX or ATMX

working card belonging to aprotection group

- major alarm MG#1 "Pro-tected line card out of ser-vice" is raised

- actions depend on previousoperational state and pro-tection state of working card

the previous state is:

- enabled-active

If EPS activation is possible:

1) EPS forces a switchover(working card func-tions switch over toprotection card)

2) Minor alarm MG#20"EPS protection lost" israised

3) Protection state ofworking card becomes"spared"

4) Protection state of re-lated protection cardbecomes "protecting"

If EPS activation is not possi-ble:

1) Critical alarm MG#21"Card activity lost" israised

- enabled-spared

If protection group has type1:1 EPS/APS coupled, theminor alarm MG#20 "EPSprotection lost" is raised(switch back not requiredfor card protection group1:1 EPS/APS coupled)

- other state values

No action

3BL 77057 ACBA RKZZA Ed.04 15 / 245



TDMX or ATMX

and the working card does notbelong to a card protectiongroup

critical alarm MG#2 "Unpro-tected line card out of service"is raised

VPP or IPGE card

Note: VPP and IPGE cards areimplictly in load sharing mode

actions depend on number ofports in an operational state"disabled"

number of ports is:

- equal to 1

1) Major alarm“Loss of extra (1)VPP/IP resource"(MG#160/MG#161)is raised

- greater than 1

1) major alarm “Lossof extra VPP/IP re-source" is cleared(MG#160/MG#161)

2) critical alarm “Loss ofextra 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 3BL 77057 ACBA RKZZA Ed.04



TDMX or ATMX

with the protection role: protec-tion

major alarm MG#1 "Protectedline card out of service" iscleared

- a working card of this pro-tection group (1:N or 1:1EPS/APS coupled) is "dis-abled" (if more than onecard is "disabled” alarm in-dicates card on lowest shelf):

1) EPS forces a switchover(related working cardfunctions switch over toprotection card)

2) Critical alarm MG#21"Card activity lost" re-lated to working cardis cleared

3) Protection state ofworking card becomes"spared"

4) Protection role of pro-tection card becomes"protecting"

- a working card of this protec-tion group is "enabled":

1) Minor alarm MG#20"EPS protection lost" iscleared

2) Protection mode ofProtection card be-comes stand-by

TDMX or ATMX

working card belonging to acard protection group

major alarm MG#1 "Protectedline card out of service" iscleared

- protection mode of workingcard is "active"

- critical alarm MG#21 "Cardactivity lost" is cleared

- protection group has type1:1 EPS/APS coupled, andif protection card is en-abled, the minor alarmMG#20 "EPS protection lost"is cleared (switch back notrequired for card protectiongroup 1:1 EPS/APS coupled)

3BL 77057 ACBA RKZZA Ed.04 17 / 245



TDMX or ATMX

and the working card does notbelong to a card protectiongroup

critical alarm MG#2 "Unpro-tected line card out of service"is cleared

VPP or IPGE card actions depend on number ofports in an operational state"disabled"

number of ports is:

- equal to 0

1) Major alarm“Loss of extra (1)VPP/IP resource"(MG#160/MG#161)is cleared

- equal to 1

1) critical alarm “Lossof extra VPP/IP re-source" is cleared(MG#160/MG#161)

2) major alarm “Loss ofextra 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... then...

no more overheating

minor overheating

MG#3 minor alarm "Minor line card failure" iscleared (if necessary)

major overheating MG#3 minor alarm "Minor line card failure" israised

critical overheating the line card is powered off by system defense(see section 1.2.1)

18 / 245 3BL 77057 ACBA RKZZA Ed.04


2 HARDWARE ALARMSThis section provides all information related to the hardware alarms.

3BL 77057 ACBA RKZZA Ed.04 19 / 245


GHM#500 - Check Configuration error



System

Alarm type Processing error

Probable cause Configuration or customization error

Specific problem None

Severity Warning

Additional Text Check Configuration error

Additional Info None

Threshold Info 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 acard’s flash memory), the card is redundant or presents an incorrect ID, oran incorrect MIB version

Probable effectson system

Equipment services are unavailable

Probable effectson service

Yes

Related alarms - GHM#518 - Card failure

Corrective actions


Yes

Actions Perform the following actions in the given order. Continue to the next actiononly if the system does not clear the alarm

1. Check that the MIB version number is the same as the version num-ber specified on the software delivery certificate.

2. Check that the chassis’ card configuration corresponds to the chas-sis’ equipment list.

3. Replace the faulty element according to replacement procedures.

Contact Alcatel-Lucent TASC before any hardware replacement

20 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#501 - Temperature crosses warning threshold



Card

Alarm type Equipment

Probable cause Temperature unacceptable


Severity Warning

Additional Text Temperature crosses warning threshold

Additional Info 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 Hard-ware Management GUI.


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


Cards can be damaged very quickly if the chassis temperature is not con-trolled


No

Related alarms - GHM#504 - Failure of a chassis fan

- GHM#505 - Failure of all chassis fans

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 21 / 245


GHM#501 - Temperature crosses warning threshold


Yes


Contact Alcatel-Lucent TASC before any hardware replacement

1. Check if there are other alarms that could explain the rise in tem-perature, 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 3BL 77057 ACBA RKZZA Ed.04


GHM#502 - Temperature crosses minor threshold



Card




Severity Minor

Additional Text Temperature crosses minor threshold





Description

Probable cause(s) Hardware or environmental non-fatal alarm. The unit temperature is overthe “minor” threshold. The station is still running



Cards can be damaged very quickly if the chassis temperature is not con-trolled


Yes



Corrective actions

3BL 77057 ACBA RKZZA Ed.04 23 / 245


GHM#502 - Temperature crosses minor threshold


Yes





4. Check that the fan units of the suspect chassis are operating correctly.If they are not, replace the fan units according to the replacementprocedure.

5. If fans are operating properly and if there is no other alarm, replacefaulty FRU according to the appropriate replacement procedure.


7. End.

24 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#503 - Temperature crosses major threshold



Card




Severity Major

Additional Text Temperature crosses major threshold





Description

Probable cause(s) Hardware or environmental fatal alarm. Temperature of the unit is over the“major” threshold. The card is powered off



The station has stopped. High Availability functionality is reduced


Yes



Corrective actions

3BL 77057 ACBA RKZZA Ed.04 25 / 245


GHM#503 - Temperature crosses major threshold


Yes





4. Check that the fan units of the suspect chassis are operating correctly.If they are not, replace the fan units according to the replacementprocedure.

5. If fans are operating properly and if there is no other alarm, replacefaulty FRU according to the appropriate replacement procedure.


7. End.

26 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#504 - One Chassis fan failure



Fan


Probable cause Heating/ventilation/cooling


Severity Minor

Additional Text One Chassis fan failure





Description

Probable cause(s) One of the chassis’ fan units has failed. The platform is still running


Cards can be damaged very quickly if the chassis temperature isnot controlled

Warning: Corrective action must be taken to avoid damage to system com-ponents. Cards can be damaged if ventilation is stopped for more than oneminute


Yes

Related alarms None

Corrective actions


Yes

Actions Replace the faulty fan unit according to the appropriate replacement pro-cedure.

3BL 77057 ACBA RKZZA Ed.04 27 / 245


GHM#505 - All Chassis fans failure



Chassis


Probable cause Heating/ventilation/cooling


Severity Critical

Additional Text All Chassis fans failure





Description

Probable cause(s) All fans in a chassis have failed. The chassis has been powered off


The chassis is powered off and all applications on the chassis are stopped


Yes


Corrective actions


Yes

Actions Replace the fan units according to the appropriate replacement procedurebefore powering on the station.

28 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#506 - One Chassis Power Unit failure



Card


Probable cause Power problem


Severity Minor

Additional Text One Chassis Power Unit failure





Description

Probable cause(s) One of the two redundant power units or one of the two power distributionunits has failed


None. The chassis is still running


No

Related alarms - GHM#507 - Failure of all power entries of a chassis

Corrective actions


Yes

Actions Perform each of the following actions in the given order.. Continue to thenext action only if the system does not clear the alarm

1. Check the top rack power distribution unit’s LED and circuit breakers.(see your rack documentation).

2. Replace the faulty power supply according to the appropriate re-placement procedure.


4. End.

3BL 77057 ACBA RKZZA Ed.04 29 / 245


GHM#507 - All Chassis Power Units failure



Chassis




Severity Critical

Additional Text All Chassis Power Units failure





Description

Probable cause(s) All power units in the chassis have failed


The chassis is powered off. All applications on the chassis are stopped


Yes

Related alarms - GHM#506 - Failure of a chassis power entry module

Corrective actions


Yes

Actions Perform each of the following actions in the given order.. Continue to thenext action only if the system does not clear the alarm

1. Check the top rack power distribution unit’s LED and circuit breakers.(see your rack documentation).

2. Replace the faulty power supply according to the appropriate re-placement procedure.


4. End.

30 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#508 - Board voltage out of range



Card




Severity Critical

Additional Text Board voltage out of range





Description

Probable cause(s) Card voltage is out of range (5V, 3.3V, 12V). It may be the CPU voltage orcard voltage

The card itself or its power supply unit can be the cause of the alarm.


The station is powered off. All applications running on the faulty station arestopped


Yes

Related alarms - GHM#506 - Failure of a chassis power entry module

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 31 / 245


GHM#508 - Board voltage out of range


Yes


1. Check if all the cards in the chassis have sent the same alarm. Ifthis is the case, replace the power supply unit(s) according to theappropriate replacement procedure.

2. Replace the faulty card according to the appropriate replacementprocedure.

3. Replace the IU (Interface Unit), located behind the faulty card, ac-cording to the appropriate replacement procedure.


5. End.

32 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#509 - ShMC Access Problem



Card


Probable cause Communications subsystem failure


Severity Major

Additional Text ShMC Access Problem





Description

Probable cause(s) Access to equipment via the Shelf Management Controller is not possible


None. The chassis is still running. Nevertheless the availability is down-graded


No


Corrective actions

3BL 77057 ACBA RKZZA Ed.04 33 / 245


GHM#509 - ShMC Access Problem


Yes


1. If the alarm originates from only one card: that card is defective.Replace the faulty card according to the appropriate replacementprocedure.

2. If the alarm originates from all cards in the chassis except one: thatcard is defective. Replace the faulty card according to the appropri-ate replacement procedure.

3. If the alarm originates from all cards in the chassis, apply the fol-lowing 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. Replacethe 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.


6. End.

34 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#510 - Station unreachable through LSN



Station

Alarm type Communication

Probable cause LAN error


Severity Major

Additional Text Station unreachable through LSN





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.


Station services are unavailable


Yes


- GHM#524 - Minor LSN access problem

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 35 / 245


GHM#510 - Station unreachable through LSN


Yes

Actions Perform each of the following actions in the given order.. Continue to thenext action only if the system does not clear the alarm. If there is no otheralarm on the station (or switch) and if the station does not initialize, performthe following actions:

1. If in a multi-rack configuration, check cables and plug connectionsalong the Ethernet path to the station. If necessary, replace faultycables.

2. Verify that the suspected card works properly. If necessary, replacethe card according to the appropriate replacement procedure.

3. Check the corresponding IU.

4. Check the Ethernet switch. If necessary, replace the switch accordingto the appropriate replacement procedure.


6. End.

36 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#511 - Loss of contact



Station


Probable cause Sofware program abnormally terminated


Severity Major

Additional Text Loss of contact





Description

Probable cause(s) Contact with a remote station has been lost. This can happen if the stationhas been reset by a defense action taken by the control station software, orthe software on the station causes the reset, or the station has failed


There is no contact with the station. Station applications are unavailable


Yes

Related alarms - GHM#519 - Fatal ethernet switch error

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 37 / 245


GHM#511 - Loss of contact


Yes


1. Allow 10 to 15 minutes for the station to restart automaticaly

2. Replace the faulty station card according to the appropriate replace-ment 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.


6. End.

38 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#512 - SW Version not compatible with MIB



Station


Probable cause Version mismatch


Severity Critical

Additional Text SW Version not compatible with MIB





Description

Probable cause(s) Initialization error. The software version is incompatible with information inthe MIB (Management Information Base)

As a result of a system installation, upgrade, or power shortage, a card isredundant or presents an incorrect ID, or has an incorrect MIB version




Yes


Corrective actions

3BL 77057 ACBA RKZZA Ed.04 39 / 245


GHM#512 - SW Version not compatible with MIB


Yes


1. Check that the MIB version is the same as the version number on thesoftware 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.


5. End.

40 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#513 - Unrecoverable software error



Station


Probable cause Sofware error


Severity Critical

Additional Text Unrecoverable software error





Description

Probable cause(s) The software has crashed




Yes


Corrective actions


No


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 replacementprocedure.


5. End.

3BL 77057 ACBA RKZZA Ed.04 41 / 245


GHM#514 - Local Disk I/O device error



Card


Probable cause I/O device error


Severity Major

Additional Text Local Disk I/O device error





Description

Probable cause(s) Fatal hardware error. Local I/O error

Internal disk error in the control station.


Control station services are unavailable for this station. A switchover hasoccurred if it was the active station. If it is the standby station, the switchoveris impossible. System redundancy is reduced


Yes


Corrective actions


Yes

Actions Replace the suspect control station (without the Interface Unit) according tothe appropriate replacement procedure

42 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#515 - MSM Disk I/O device error



Card


Probable cause I/O device error


Severity Major

Additional Text MSM Disk I/O device error





Description

Probable cause(s) MSM (Mass Storage Module) disk error

Device disk error or linkage error (SCSI, Fiber channel, etc).


The related control station managing the faulty MSM switched automaticallyto stop standby mode. Control station services are unavailable for this sta-tion. A switchover has occurred if it was the active station. If it is the standbystation, the switchover is impossible. System redundancy is reduced


Yes


Corrective actions

3BL 77057 ACBA RKZZA Ed.04 43 / 245


GHM#515 - MSM Disk I/O device error


Yes


1. Replace the faulty MSM card according to the appropriate devicereplacement procedure.

2. Replace the control station card Interface cable according to theappropriate replacement procedure.

3. If the alarm condition is still present, replace the chassis.


5. End.

44 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#516 - Hardware Fatal Error



Card


Probable cause Equipment malfunction


Severity Critical

Additional Text Hardware Fatal Error





Description

Probable cause(s) Hardware Fatal Error


Card applications are stopped


Yes



Corrective actions


Yes


1. Check if there are other current alarms. Troubleshoot these alarms.

2. If necessary, replace the faulty card according to the appropriatereplacement procedure.


4. End.

3BL 77057 ACBA RKZZA Ed.04 45 / 245


GHM#517 - PMC Access Failure



Card


Probable cause Adapter error


Severity Major

Additional Text PMC Access Failure





Description

Probable cause(s) Hardware error on a PMC (PCI Mezzanine Card)


Card services are unavailable


Yes


Corrective actions


Yes


1. Check if there are other current alarms ( SS7 Alarms). Troubleshootthese alarms.

2. If necessary, replace defective card according to the appropriatereplacement procedure.


4. End.

46 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#518 - Card failure



Card




Severity Major

Additional Text Card failure





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 inthe same chassis, or identical geographical addresses across differentchassis)

i) IPMB communication error (card Baseboard Management Controller,backplane, IPMC on FRU).


Card services are unavailable


Yes

Related alarms None

3BL 77057 ACBA RKZZA Ed.04 47 / 245


GHM#518 - Card failure

Corrective actions


Yes


1. In case of a geographical address error, check the micro switchsettings on the configuration and alarm card.

2. If the alarm condition continues, replace the card that does notanswer to the Hardware Management GUI according to the appro-priate replacement procedure.

3. If there is no other current alarm on the same chassis, replacethe suspected card according to the appropriate replacement pro-cedure.

4. Check each of the possible causes with the Hardware ManagementGUI. Replace the suspected card according to the appropriate re-placement procedure.


6. End.

48 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#519 - Ethernet switch fatal error



LAN




Severity Major

Additional Text Ethernet switch fatal error





Description

Probable cause(s) The Ethernet switch is not accessible

The Ethernet switch is disconnected or out of service


Network operation is affected


Yes


Corrective actions


Yes


1. In a multi-rack configuration, check the switch cables and powersupply.

2. Reset the switch.

3. Replace the switch according to the appropriate procedure.


5. End.

3BL 77057 ACBA RKZZA Ed.04 49 / 245


GHM#520 - Router communication failure



Router




Severity Major

Additional Text Router communication failure





Description

Probable cause(s) Remote equipment is unreachable

The router is disconnected or out of service




Yes


Corrective actions

50 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#520 - Router communication failure


Yes


1. If there are other related alarms, troubleshoot these alarms beforeproceeding.

2. Check router cables and power supply.

3. Reset the router.

4. Replace the router according to the appropriate procedure.

5. Reset the router.



8. End.

3BL 77057 ACBA RKZZA Ed.04 51 / 245


GHM#521 - Minor Router Path failure



Router




Severity Minor

Additional Text Minor Router Path failure





Description

Probable cause(s) One of the router’s two Ethernet links is down

The switch or router is disconnected, off or out of service




Yes

Related alarms - GHM#520 - Router communication failure

Corrective actions


Yes


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 pro-cedure.


6. End.

52 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#522 - Major Router Path failure



Router




Severity Major

Additional Text Major Router Path failure





Description

Probable cause(s) The Ethernet links are down on both routers

The router or switch is disconnected, off or out of service




Yes

Related alarms - GHM#520 - Router communication failure

Corrective actions


Yes


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 proce-dure(s).


6. End.

3BL 77057 ACBA RKZZA Ed.04 53 / 245


GHM#523 - Both ShMC Access Problem



Card




Severity Critical

Additional Text Both ShMC Access Problem





Description

Probable cause(s) Access to equipment via the Shelf Management Controller is not possible

Both Shelf Management cards are unreachable through Ethernet


No hardware management action is possible on the chassis


Yes


Corrective actions

54 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#523 - Both ShMC Access Problem


Yes


1. If the alarm originates from only one card: that card is defective.Replace the faulty card according to the appropriate replacementprocedure.

2. If the alarm originates from all cards in the chassis except one: thatcard is defective. Replace the faulty card according to the appropri-ate replacement procedure.

3. If the alarm originates from all cards in the chassis, apply the fol-lowing 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. Replacethe 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.


6. End.

3BL 77057 ACBA RKZZA Ed.04 55 / 245


GHM#524 - One LSN access of the station is out of service



Station




Severity Minor

Additional Text One LSN access of the station is out of service





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


Station services are degraded


No


Corrective actions

56 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#524 - One LSN access of the station is out of service


Yes

Actions Perform each of the following actions in the given order. Continue to thenext 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 doesnot initialize, perform the following actions:

1. In a multi-rack configuration, check cables and plug connectionsalong the Ethernet path to the station. If necessary, replace faultycables.



4. Check the Ethernet switch. If necessary, replace the switch accordingto the appropriate replacement procedure.


6. End.

3BL 77057 ACBA RKZZA Ed.04 57 / 245


GHM#528 - Initializing error



Station




Severity Warning

Additional Text Initializing error

Additional Info The station did not succeed to boot during platform restart.


Description

Probable cause(s) Board error


Station services are unavailable.


Yes


Corrective actions


Yes

Actions Perform the following actions in the given order. Continue to the next actiononly 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 stationinto service.

4. If necessary, replace the faulty unit according to the appropriatereplacement procedure.


6. End.

58 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#529 - One LANIO access of the station is out of service



Station




Severity Minor

Additional Text One LANIO access of the station is out of service





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.




No

Related alarms - GHM#530 - Major LANIO access problem

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 59 / 245


GHM#529 - One LANIO access of the station is out of service


Yes


If there is no other alarm on the station, perform the following actions:

1. Check cables and plug connections along the Ethernet path to thestation. If necessary, replace faulty cables.




5. End.

60 / 245 3BL 77057 ACBA RKZZA Ed.04


GHM#530 - All configured LANIO access of the station are out of service



Station




Severity Major

Additional Text All configured LANIO access of the station are out of service





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.




No

Related alarms - GHM#529 - Minor LANIO access problem

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 61 / 245


GHM#530 - All configured LANIO access of the station are out of service


Yes


If there is no other alarm on the station, perform the following actions:

1. Check cables and plug connections along the Ethernet path to thestation. If necessary, replace faulty cables.




5. End.

62 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#1 - Protected line card out of service



ATCA_card




Severity Major

Additional Text Protected line card out of service

Additional Info [ 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


Description

3BL 77057 ACBA RKZZA Ed.04 63 / 245



Probable cause(s) This alarm is raised when a line card which belongs to a card protectiongroup becomes out of service: the card was either locked or extracted bythe 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 thatno failure is detected by system: you only need to unlock the card to clearthis alarm


In case of card failure, a "power-off" is automatically generated for the linecard

In all cases (failure, extract, lock), card services become unavailable (allassociated established calls are lost)

All alarms associated with elements (ports, lines, etc.) of the line card areautomatically cleared

Automatic actions then depend on the card protection mode:

* Protection mode 1:1 active/standby coupled APS: If conditions required forEPS are satisfied, card services are automatically reconfigured on associatedcard. An alarm is raised if EPS is not possible.

* Protection mode 1:N active/standby: If conditions required for EPS aresatisfied, card services are automatically reconfigured on associated card.An alarm is raised if EPS is not possible. An alarm is raised if EPS protectionis 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 informoperator that resource(s) of associated function are lost.


Yes

Related alarms - 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

64 / 245 3BL 77057 ACBA RKZZA Ed.04




Yes

Actions Perform the following actions in the given order:

1. If necessary, replace or insert the card according to the appropriateprocedure.

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.

3BL 77057 ACBA RKZZA Ed.04 65 / 245


MG#2 - Unprotected line card out of service



ATCA_card




Severity Critical

Additional Text Unprotected line card out of service



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


Description

66 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#2 - Unprotected line card out of service

Probable cause(s) This alarm is raised when a line card which doesn’t belong to a card protec-tion group becomes out of service: the card was either locked or extractedby 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 thatno failure is detected by system: you only need to unlock the card to clearthis alarm


In case of card failure, a "power-off" is automatically generated for the linecard

In all cases (failure, extract, lock), card services become unavailable (allassociated established calls are lost)

All alarms associated with elements (ports, lines, etc.) of the line card areautomatically cleared


Yes

Related alarms None

Corrective actions


Yes


1. If necessary, replace or insert the card according to the appropriateprocedure.

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.

3BL 77057 ACBA RKZZA Ed.04 67 / 245


MG#3 - Minor line card failure



ATCA_card




Severity Minor

Additional Text Minor line card failure



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 thresh-old .

Description

Probable cause(s) This alarm is raised when a minor failure probably due to hardware is de-tected on a line card

Types of failure are indicated in section additional info


No effect because card remains operational


No

Related alarms None

Corrective actions

68 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#3 - Minor line card failure


Yes


1. If protection state of card is "active", activate a "manual switch" com-mand. 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.

3BL 77057 ACBA RKZZA Ed.04 69 / 245


MG#10 - LIU shelf activity lost



LIU_shelf




Severity Critical

Additional Text LIU shelf activity lost

Additional Info [ 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


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 isenabled


LIU services become unavailable


Yes

Related alarms None

Corrective actions

70 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#10 - LIU shelf activity lost


Yes

Actions Perform the following actions in the given order and continue to the nextaction if the system doesn’t 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 toMUX 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 andverify if alarm is cleared when this MUX card is unlocked. If the alarmis cleared, replace the other MUX card, unlock it and send the faultycards to the repair service.

5. If the alarm is still not cleared, contact your Alcatel-Lucent TechnicalSupport Center (failure is perhaps due to LIU shelf).

6. End.

3BL 77057 ACBA RKZZA Ed.04 71 / 245


MG#11 - LIU shelf number configuration error



LIU_shelf




Severity Critical

Additional Text LIU shelf number configuration error



Description

Probable cause(s) This alarm is raised if MUX cards are detected with the same identity (sameslot and same LIU number)

This alarm is cleared if no MUX cards are detected with the same identity(same slot and same LIU number)


Services related to the first MUX cards detected on this LIU remain available

Services related to the other MUX cards detected on wrong numbered LIUare unavailable


Yes

Related alarms None

Corrective actions


Yes


1. Modify the LIU number (micro-switch) of the faulty LIU shelf andreinitialize this LIU shelf.

2. If the alarm is still not cleared, contact your Alcatel-Lucent TechnicalSupport Center.

3. End.

72 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#12 - LIU shelf number unknown



LIU_shelf




Severity Minor

Additional Text LIU shelf number unknown



Description

Probable cause(s) This alarm is raised if a MUX card related to this LIU shelf not created isdetected

This alarm is cleared if no MUX card related to this LIU shelf not created isdetected


LIU services of this wrong numbered LIU shelf are unavailable


Yes

Related alarms None

Corrective actions


Yes


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.


4. End.

3BL 77057 ACBA RKZZA Ed.04 73 / 245


MG#13 - MUX card out of service



LIU_card




Severity Major

Additional Text MUX card out of service

Additional Info [ Location of the faulty MUX card (Shelf/Slot) ]

[ Cause of outage ]


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


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


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 raisedand alarm GW#13 is cleared


Yes

Related alarms None

Corrective actions

74 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#13 - MUX card out of service


Yes


1. If the MUX card is locked, unlock it.

2. If the MUX card is failed, replace it according to the appropriateprocedure.

3. If the MUX card is incorrectly connected, check if associated Ethernetlink(s) is (are) correctly linked to the MUX and to ATCA switch cards

4. Verify that operational state of this MUX card becomes "enabled".


6. End.

3BL 77057 ACBA RKZZA Ed.04 75 / 245


MG#14 - LIU card out of service



LIU_card




Severity Major

Additional Text LIU card out of service

Additional Info [ Location of the faulty LIU card (Shelf/Slot) ]

[ Cause of outage ]


1 - Card locked

2 - Shelf unreachable

3 - Card not present

4 - Card unreachable

5 - Wrong card type

6 - Wrong card variant


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


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-1card is lost (see alarm MG#22) or taken over by the related APS LIU card


Yes

Related alarms None

Corrective actions

76 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#14 - LIU card out of service


Yes


1. If the card is locked, unlock it.

2. If the card is failed, replace it according to the appropriate proce-dure.

3. Card operational state must become "enabled".

4. End.

3BL 77057 ACBA RKZZA Ed.04 77 / 245


MG#15 - PEM card out of service



LIU_card




Severity Major

Additional Text PEM card out of service

Additional Info [ Location of the faulty PEM card (Shelf/Slot) ]

[ Cause of outage ]


1 - Card not present

2 - Wrong card type

3 - Tertiary voltage failure

4 - Card overheating


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


No effect due to PEM cards redundancy


No

Related alarms None

Corrective actions


Yes

Actions Replace the PEM card according to the appropriate procedure.

78 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#16 - LIU shelf 48V redundancy failure



LIU_shelf




Severity Major

Additional Text LIU shelf 48V redundancy failure



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 redun-dancy failure


No effect due to 48V redundancy


No

Related alarms None

Corrective actions


Yes

Actions Locate the failure and repair faulty element(s).

3BL 77057 ACBA RKZZA Ed.04 79 / 245


MG#17 - Firmware upgrade required



LIU_card




Severity Major

Additional Text Firmware upgrade required

Additional Info Shelf and slot number of the faulty LIU card


Description

Probable cause(s) The current version available on the flash memory is different from the oneavailable in the 7570 Vn set, on the disk of the Control station


The faulty LIU card is working with a firmware version different from thereference firmware on the disk of the Control station

Quality of service may be affected


Yes

Related alarms None

Corrective actions

80 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#17 - Firmware upgrade required


No

Actions If the faulty LIU card is a GMUX:

1. Place the GMUX board in standby mode (force a switchover if nec-essary).

2. Check there is no incidence on traffic.

3. From the Hardware management GUI, upgrade the firmware of thecard:

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".


If the faulty LIU card is a JBSS1 without APS protection:





• A pop-up window indicate "OK" after 40 seconds.


e) Verify that operational state of this JBSS1 card becomes "active" afterupgrade.

f) If the alarm is still not cleared, contact your Alcatel-Lucent Technical Sup-port 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 bylocking the STM-1 line.





• A pop-up window indicate "OK" after 40 seconds.


3. unlock the STM-1 line.


3BL 77057 ACBA RKZZA Ed.04 81 / 245


MG#20 - EPS protection lost



EPS_group




Severity Minor

Additional Text EPS protection lost

Additional Info [ Protection reference group (EPS_ref) ]


Description

Probable cause(s) This alarm is raised when operational state of a protection card becomes"disabled"


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 protec-tion group remain operational


No

Related alarms - MG#1 - Protected line card out of service

Corrective actions


Yes


1. Retrieve protection card references from EPS reference.

2. Retrieve protection card state.

3. If protection card state is disabled for reason "locked", unlock pro-tection card.

4. If protection card state is disabled for reason "failure", see the trou-bleshooting of related alarm.

5. End.

82 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#21 - Card activity lost



ATCA_card




Severity Critical

Additional Text Card activity lost



Description

Probable cause(s)



Yes

Related alarms - MG#1 - Protected line card out of service

Corrective actions


Yes

Actions Perform the actions described in related alarm.

3BL 77057 ACBA RKZZA Ed.04 83 / 245


MG#30 - Ethernet plane unavailable



ATCA_card




Severity Major

Additional Text Ethernet plane unavailable

Additional Info [ 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


Description

Probable cause(s)


Fabric ethernet traffic is automatically switched over the redundant ethernetplane


No

Related alarms None

Corrective actions

84 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#30 - Ethernet plane unavailable


Yes


1. If the gatewy is made of 2 ATCA shelves, check that second switchcard 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 cardaccording to the appropriate procedure and, if necessary, send it tothe repair service.

3. If type of failure is equal to 3 (base ethernet uplink), then plug orreplace the related ethernet uplink.

4. If type of failure is equal to 4 (fabric ethernet uplink), plug or replacethe related ethernet uplink, then extract and insert the related switchcard.

3BL 77057 ACBA RKZZA Ed.04 85 / 245


MG#40 - Loss of all synchro references



Synchro




Severity Critical

Additional Text Loss of all synchro references



Description

Probable cause(s) Synchronization reference is no longer available


The system clock module of the switch cards switches automatically in "freerun" mode (signal generation from local clock)

Voice quality disturbance

Data flow disturbance (major)


Yes

Related alarms None

Corrective actions


Yes


1. Check synchronizing lines (state and link).

2. If necessary, repair.

3. Check if synchronization function is available.


5. End.

86 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#41 - Loss of synchro reference (line timing mode)



Synchro_line




Severity Minor

Additional Text Loss of synchro reference (line timing mode)

Additional Info [ Location of the synchronizing line (Shelf/Slot/Line_position) ]


Description

Probable cause(s) Synchronizing line failure


No effect because an other line is automatically used as synchronizationsource reference


No

Related alarms None

Corrective actions


Yes


1. Check synchronizing lines (state and link). If necessary, repair orreplace of synchronization source reference.


3. End.

3BL 77057 ACBA RKZZA Ed.04 87 / 245


MG#43 - Loss of synchro reference (external timing mode)



ATCA_card




Severity Minor

Additional Text Loss of synchro reference (external timing mode)

Additional Info [ Location of the switch card on which the external line is linked (Shelf/Slot) ]


Description

Probable cause(s)


No effect because an other external reference is automatically used as syn-chronization source reference


No

Related alarms None

Corrective actions


Yes


1. Check synchronizing external reference (state and link). If necessary,repair or replace of synchronization source reference.


3. End.

88 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#44 - System clock module failure



ATCA_card




Severity Major

Additional Text System clock module failure

Additional Info [ 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)


Description

Probable cause(s) HW failure of related switch card


Synchronization function is provided by the other switch card

All user traffic is provided by the other switch card


No

Related alarms - GHM#516 - Fatal hardware error

Corrective actions


Yes

Actions replace the switch card according to the appropriate procedure (see relatedalarm).

3BL 77057 ACBA RKZZA Ed.04 89 / 245


PDUA#1 - RAP Unreachable



PDUA




Severity Critical

Additional Text RAP Unreachable



You can use the Hardware Management GUI to locate the name of theobject displayed in the Name field


Description

Probable cause(s) Remote equipment is unreachable.

The Alarm PDU is disconnected or out of service.


Alarm synthesis is unreliable.


Yes


Corrective actions


Yes


1. If there are other related alarms troubleshoot these alarms beforeproceeding.

2. Check the Alarm PDU cables and power supply.

3. Reset the Alarm PDU.


5. If the problem persists, contact Alcatel TASC.

6. End.

90 / 245 3BL 77057 ACBA RKZZA Ed.04


PDUA#2 - Default on infrastucture loops supervision



PDUA




Severity Critical

Additional Text Default on infrastucture loops supervision



You can use the Hardware Management GUI to locate the name of theobject displayed in the Name field


Description

Probable cause(s) Remote equipment is unreachable.

The Alarm PDU is disconnected or out of service.


Alarm synthesis is unreliable.


No

Related alarms - PDUA#1 - RAP Unreachable

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 91 / 245


PDUA#2 - Default on infrastucture loops supervision


Yes


Contact Alcatel TASC before any hardware replacement.

1. If there are other related alarms troubleshoot these alarms beforeproceeding.

2. Check the Alarm PDU Loops sensors.

3. Check the Alarm PDU cables and power supply.

4. Reset the the Alarm PDU.


6. End.

92 / 245 3BL 77057 ACBA RKZZA Ed.04


3 INFRASTRUCTURE ALARMSThis section describes the infrastructure alarms that can be sent by the alarm loops on a 7570 equippedwith the Rack Alarm Panel.

3BL 77057 ACBA RKZZA Ed.04 93 / 245


INFR#1 - Default on infrastucture loop #1



PDUA


Probable cause Input device error


Severity Indeterminate

Additional Text Default on infrastucture loop #1

Additional Info The location of RAP managing the loop is given here.


Description

Probable cause(s) This alarm can be customized on site.

The probable cause, type, severity displayed on the Alarm GUI can differfrom the present dictionary.


Depends on sensor supervized.


No

Related alarms None

Corrective actions


Yes

Actions Depends on sensor supervized.

94 / 245 3BL 77057 ACBA RKZZA Ed.04


INFR#2 - Default on infrastucture loop #2



PDUA


Probable cause Input device error


Severity Indeterminate

Additional Text Default on infrastucture loop #2

Additional Info The location of RAP managing the loop is given here.


Description

Probable cause(s) This alarm can be customized on site.

The probable cause, type, severity displayed on the Alarm GUI can differfrom the present dictionary.


Depends on sensor supervized.


No

Related alarms None

Corrective actions


Yes

Actions Depends on sensor supervized.

3BL 77057 ACBA RKZZA Ed.04 95 / 245


4 SOFTWARE ALARMSThis section provides all information related to the software alarms.

96 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#230 - Control management initialization in progress



Platform_MG




Severity Warning

Additional Text Control management initialization in progress



Description

Probable cause(s) This alarm is raised when initialization of the active control station starts

It is cleared when control station initialization ends


During the initialization phase, 7570 management is unavailable

As long as this alarm or related alarm is raised, GUI notifies you that 7570management is unavailable


Yes

Related alarms - MG#231 - Board configuration initialization in progress

Corrective actions


No

Actions Wait for end of 7570 control station initialization phase.

3BL 77057 ACBA RKZZA Ed.04 97 / 245


MG#231 - Board configuration initialization in progress



Platform_MG




Severity Warning

Additional Text Board configuration initialization in progress



Description

Probable cause(s) This alarm is raised when initialization of the active control station starts

It is cleared when control station initialization ends


During the initialization phase, 7570 management is unavailable

As long as this alarm or related alarm is raised, GUI notifies you that 7570management is unavailable


Yes

Related alarms - MG#230 - Control management initialization in progress

Corrective actions


No

Actions Wait for end of 7570 control station initialization phase.

98 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#240 - Database Migration failed



SW_management


Probable cause Corrupt data


Severity Critical

Additional Text Database Migration failed

Additional Info [ Release of the 7570 software that did not succeed to start ]


Description

Probable cause(s) This alarm is raised when a software upgrade embeddding a database mi-gration has failed

A database corruption is detected after migration


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 previousvalid software version

The Alarm is raised as soon as the database corruption is detected on arelease

This alarm is cleared when the control station successfuly restarts on theprevious valid software release


No

Related alarms None

Corrective actions


No

Actions Contact your Alcatel-Lucent Technical Support Center.

3BL 77057 ACBA RKZZA Ed.04 99 / 245


MG#241 - Database Corruption detected



SW_management


Probable cause Corrupt data


Severity Major

Additional Text Database Corruption detected

Additional Info OAM database corruption detected.


Description

Probable cause(s) An OAM database corruption is detected

A database corruption is detected by audit tools


This alarm is cleared when the control station successfuly restarts on theprevious database


No

Related alarms None

Corrective actions


Yes


1. Save the current database and send it to your Alcatel-Lucent Techni-cal Support Center support center for analysis.

2. Replace the current database with the reference one (i.e., the saveddatabase).

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 SupportCenter

6. End.

100 / 245 3BL 77057 ACBA RKZZA Ed.04


5 LINE AND PORT ALARMSThis section provides all the information related to the line and port alarms.

3BL 77057 ACBA RKZZA Ed.04 101 / 245


MG#22 - Port activity lost



SDH_port




Severity Major

Additional Text Port activity lost

Additional Info [ Location of the SDH port (Shelf/Slot/Port) ]


Description

Probable cause(s) This alarm is raised when an SDH port, belonging to an unlocked ATCA linecard, no longer has operational SDH line and has at least one unlocked line



Yes

Related alarms None

Corrective actions


Yes

Actions

102 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#50 - Threshold crossing: TCA Register Section 15 minutes



SDH_Line

Alarm type Quality of service

Probable cause Threshold crossed


Severity Minor

Additional Text Threshold crossing: TCA Register Section 15 minutes

Additional Info [ 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


Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

3BL 77057 ACBA RKZZA Ed.04 103 / 245


MG#51 - Threshold crossing: TCA Mux Section 15 minutes



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA Mux Section 15 minutes



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

104 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#52 - Threshold crossing: TCA path 15 minutes



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA path 15 minutes



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

3BL 77057 ACBA RKZZA Ed.04 105 / 245


MG#53 - Threshold crossing: TCA Register Section 24 hours



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA Register Section 24 hours



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

106 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#54 - Threshold crossing: TCA Mux Section 24 hours



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA Mux Section 24 hours



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

3BL 77057 ACBA RKZZA Ed.04 107 / 245


MG#55 - Threshold crossing: TCA path 24 hours



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA path 24 hours



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

108 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#56 - Threshold crossing: TCA Mux Section - Far End 15 minutes



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA Mux Section - Far End 15 minutes



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

3BL 77057 ACBA RKZZA Ed.04 109 / 245


MG#57 - Threshold crossing: TCA path - Far End 15 minutes



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA path - Far End 15 minutes



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

110 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#58 - Threshold crossing: TCA Mux Section - Far End 24 hours



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA Mux Section - Far End 24 hours



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

3BL 77057 ACBA RKZZA Ed.04 111 / 245


MG#59 - Threshold crossing: TCA path - Far End 24 hours



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA path - Far End 24 hours



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

112 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#60 - Threshold crossing: TCA Egress Cell Data Error



SDH_Line




Severity Minor

Additional Text Threshold crossing: TCA Egress Cell Data Error



Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

3BL 77057 ACBA RKZZA Ed.04 113 / 245


MG#61 - SDH loss of clock



SDH_Line


Probable cause Timing problem


Severity Minor

Additional Text SDH loss of clock



Description

Probable cause(s) Power is received but received clock frequency cannot be recognized or isout of authorized bounds

The connected line is probably not an STM-1


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 israised

Current alarm is cleared when the card or the line is locked


No

Related alarms None

Corrective actions

114 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#61 - SDH loss of clock


Yes

Actions Perform the following verifications in the given order:

1. Check, using the GUI alarm management, that synchronizationequipment is not under critical alarm.

2. Check that the SDH configuration of the connected line is appropri-ate on both ends of the line.

3. Check line cabling.

4. Check operational state of external optical/electrical line and its SDHframing in receive direction using external test equipment.

5. Perform a line loopback to check the operational state of opti-cal/electrical line and its SDH framing, using external test equipment.

6. End.

3BL 77057 ACBA RKZZA Ed.04 115 / 245


MG#62 - SDH loss of signal



SDH_Line


Probable cause Loss of signal


Severity Minor

Additional Text SDH loss of signal



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



Lower priority SDH_Line and SDH_Path alarms are cleared





No

Related alarms None

Corrective actions

116 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#62 - SDH loss of signal


Yes

Actions Perform the following verification in the given order:

1. Check that the SDH configuration of the connected line is appropri-ate on both ends of the line, and that the line is "unlocked".

2. Check line cabling



5. End.

3BL 77057 ACBA RKZZA Ed.04 117 / 245


MG#63 - SDH loss of frame



SDH_Line


Probable cause Loss of frame


Severity Minor

Additional Text SDH loss of frame



Description

Probable cause(s) No SDH framing is detected from the line

The line may be misconfigured on the remote equipment








No

Related alarms None

Corrective actions

118 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#63 - SDH loss of frame


Yes


1. Check that the SDH configuration of the connected line is appropri-ate on both ends of the line (in particular, ends should be either bothETSI or both ANSI), and that the line is "unlocked".

2. Check line cabling



3BL 77057 ACBA RKZZA Ed.04 119 / 245


MG#64 - SDH line/Mux section AIS



SDH_Line


Probable cause Remote node transmission error


Severity Minor

Additional Text SDH line/Mux section AIS



Description

Probable cause(s) SDH framing is received but the line/Mux section layer delivers an AIS indi-cating a defect detected upstream

The remote end of the SDH line or another remote equipment may be mis-configured








No

Related alarms None

Corrective actions


No

Actions Repair remote equipment defect.

120 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#65 - SDH path AIS



SDH_Path




Severity Minor

Additional Text SDH path AIS

Additional Info [ 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


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 forinformation only


Lower priority SDH_Line and SDH_Path alarms related to the same path arecleared





No

Related alarms None

Corrective actions


No

Actions Check if the alarm indicates a defect and, if necessary, reconfigure or repairremote equipment.

3BL 77057 ACBA RKZZA Ed.04 121 / 245


MG#66 - SDH loss of pointer



SDH_Path


Probable cause Framing error


Severity Minor

Additional Text SDH loss of pointer





Description

Probable cause(s) An SDH path container is not accessible

The local or remote equipment may be misconfigured or failed


Lower priority SDH_Line and SDH_Path alarms related to the same path arecleared





No

Related alarms None

Corrective actions


No

Actions Check configuration on line and path ends

122 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#67 - Section trace mismatch (J0)



SDH_Line




Severity Minor

Additional Text Section trace mismatch (J0)


[ Received section trace value ]


Description

Probable cause(s) Unexpected SDH line name in payload (trace name)

The local or remote equipment is misconfigured








Yes

Related alarms None

Corrective actions


Yes


1. Retrieve line information from the GUI and check if the section tracecheck must really be enabled, and verify the section trace string.

2. Check the received string and line cabling.

3. End.

3BL 77057 ACBA RKZZA Ed.04 123 / 245


MG#68 - Path trace mismatch (J1, J2)



SDH_Path




Severity Minor

Additional Text Path trace mismatch (J1, J2)




[ Received path trace value ]


Description

Probable cause(s) Unexpected SDH path name in payload (trace name)

The local or remote equipment is misconfigured


Traffic expected in this container cannot be processed

Lower priority SDH_Line alarms and SDH_Path alarms related to the samepath are cleared





Yes

Related alarms None

Corrective actions

124 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#68 - Path trace mismatch (J1, J2)


No


1. Retrieve line information from the GUI and check if the path tracecheck must really be enabled, and verify the path trace string.

2. Check the received string and the remote equipment.

3. End.

3BL 77057 ACBA RKZZA Ed.04 125 / 245


MG#69 - SDH Signal fail (SF)



SDH_Line




Severity Minor

Additional Text SDH Signal fail (SF)



Description

Probable cause(s) The line has reached an error threshold indicating the lowest limit of accept-able reception quality


No system reaction

Poor transmission with risk of Cs frames loss that affects traffic quality andis perceptible by end users

Risk of local or remote hardware anomaly along the line


Yes

Related alarms None

Corrective actions

126 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#69 - SDH Signal fail (SF)


Yes


1. From the GUI, activate - if not yet started - performance monitoringon the faulty line (and on the possible other line in APS) to get moredetails about errors types.

2. If APS is available, force an APS switch to the best line among thetwo to improve quality.

3. Activate performance monitoring of other nodes or lines on the linkand locate the faulty element.

4. Repair faulty element.


6. End.

3BL 77057 ACBA RKZZA Ed.04 127 / 245


MG#70 - SDH Signal degrade (SD)



SDH_Line




Severity Minor

Additional Text SDH Signal degrade (SD)



Description

Probable cause(s) The line has reached an error threshold that indicates a poor reception qual-ity


No immediate system reaction

Degraded transmission with probable loss of Cs traffic frames

Possible local or remote hardware anomaly along the line


Yes

Related alarms None

Corrective actions

128 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#70 - SDH Signal degrade (SD)


Yes


1. From the GUI, activate - if not yet started - performance monitoringon the faulty line (and on the possible other line in APS) to get moredetails about errors types.

2. If APS is available, force an APS switch to the best line among thetwo to improve quality.




6. End.

3BL 77057 ACBA RKZZA Ed.04 129 / 245


MG#71 - SDH Signal label: Protocol mismatch



SDH_Path




Severity Minor

Additional Text SDH Signal label: Protocol mismatch






Description

Probable cause(s) The received SDH container is designed to transport an unexpected protocol


This particular virtual container is unusable for traffic

Valid traffic was probably expected


Yes

Related alarms None

Corrective actions

130 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#71 - SDH Signal label: Protocol mismatch


Yes

Actions Perform the following verifications depending on the case:

1. If all other containers on the same TDMX or ATMX card are alsowrong, the LIU shelf is not the expected one: check LIU shelf cablingto the ATCA rack.

2. If all other containers on the same line are also wrong, the line isnot the expected one: check the line cabling.

3. If several containers on the same line are also wrong, check if thecontainer is expected to be used by the 7570. If it is, check the otherNEs. If it is not, no action is required from the 7570 and the alarmis informative only, although you are still advised to check the otherNEs.

4. End.

3BL 77057 ACBA RKZZA Ed.04 131 / 245


MG#72 - SDH Signal label: VC unequipped



SDH_Path




Severity Minor

Additional Text SDH Signal label: VC unequipped






Description

Probable cause(s) The received SDH container is not designed to transport data


This particular virtual container is unusable for traffic


No

Related alarms None

Corrective actions


No

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 7570and the alarm is informative only.

2. End.

132 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#73 - SDH line/Mux section RDI



SDH_Line




Severity Minor

Additional Text SDH line/Mux section RDI



Description

Probable cause(s) An SDH line AIS from the 7570 has been detected by the peer end point


No traffic is received from the line

Lower priority SDH_Line alarms and SDH_Path alarms are cleared




Yes

Related alarms None

Corrective actions


No


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 becleared when maintenance ends.

2. End.

3BL 77057 ACBA RKZZA Ed.04 133 / 245


MG#74 - SDH path RDI



SDH_Path




Severity Minor

Additional Text SDH path RDI





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 forinformation only

b) A remote equipment may be misconfigured


No traffic is received for this path


This alarm is associated with each SDH path.



Yes

Related alarms None

Corrective actions


Yes


1. Check if the 7570 path is configured for traffic. If it is, check theother NEs, especially the receive and transmit fibers. If it is not, thealarm is informative only

134 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#75 - PDH payload loss of frame



SDH_T1E1




Severity Minor

Additional Text PDH payload loss of frame

Additional Info [ Location of the T1/E1 (Shelf/Slot/Line_position/hop/mop/lop) ]


Description

Probable cause(s) No E1 or DS1 framing is detected from the line



E1 or DS1 is disabled

Lower priority SDH_T1E1 alarms are cleared


Yes

Related alarms None

Corrective actions


Yes

Actions Perform the following verifications:

1. Check that the configuration of the PDH payload is appropriate onboth ends of the line: in particular, ends should be either both ETSIor both ANSI.

2. Check the end to end container cross connection.

3. End.

3BL 77057 ACBA RKZZA Ed.04 135 / 245


MG#76 - PDH payload line AIS



SDH_T1E1




Severity Minor

Additional Text PDH payload line AIS



Description

Probable cause(s) Bit pattern is received from PDH payload but it is "all 1s" (AIS), which indicatesthat a defect was detected upstream

The remote end of PDH payload or another remote equipment may be mis-configured


E1 or DS1 is disabled



Yes

Related alarms None

Corrective actions


No

Actions Reconfigure remote equipment

136 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#77 - PDH payload line RDI



SDH_T1E1




Severity Minor

Additional Text PDH payload line RDI



Description

Probable cause(s) A PDH payload AIS from the 7570 has been detected by the peer end point


No E1 or DS1 traffic is received from the line



Yes

Related alarms None

Corrective actions


No


1. Check if the 7570 is in manual maintenance. If it is check the otherNEs. If it is not, the alarm is informative only and will be clearedwhen maintenance ends.

2. End.

3BL 77057 ACBA RKZZA Ed.04 137 / 245


MG#79 - Loss of CRC4 multiframe



SDH_T1E1




Severity Minor

Additional Text Loss of CRC4 multiframe



Description

Probable cause(s) Loss of CRC4 multiframe

The PDH payload may be misconfigured on the remote equipment


No E1 or DS1 traffic is received



Yes

Related alarms None

Corrective actions


Yes


1. Check that the configuration of E1 or DS1 is appropriate on bothends of the line: in particular, they must be either both CRC4 con-figured, or both CRC4 not configured.

2. End.

138 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#80 - Signal fail (SF)



SDH_T1E1




Severity Minor

Additional Text Signal fail (SF)



Description

Probable cause(s) The SDH_T1E1 has reached an error threshold that indicates the lowest limitof acceptable reception quality


No system reaction

Poor transmission with probably a loss of Cs frames affecting traffic qualityand perceptible by end users

Possible local or remote hardware anomaly on the end to end connection


Yes

Related alarms None

Corrective actions


No


1. Verify presence of threshold crossing alert.


3. Repair faulty elements.

4. End.

3BL 77057 ACBA RKZZA Ed.04 139 / 245


MG#81 - Signal degraded (SD)



SDH_T1E1




Severity Minor

Additional Text Signal degraded (SD)



Description

Probable cause(s) The SDH_T1E1 has reached an error threshold that indicates a poor recep-tion quality



Degraded transmission with probable loss of Cs traffic frames

Possible local or remote hardware anomaly on the end to end connection


Yes

Related alarms None

Corrective actions


No


1. Verify presence of threshold crossing alert.



4. End.

140 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#90 - Loss of signal



PDH_Line


Probable cause Loss of signal


Severity Minor

Additional Text Loss of signal

Additional Info [ Location of the PDH line (Shelf/Slot/Line_position) ]


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



Lower priority PDH_Line alarms are cleared

This line failure prevents port activity and also raises the associated alarm"port activity lost"



Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 141 / 245


MG#90 - Loss of signal


No


1. Check that the PDH configuration of the line is appropriate on bothends, and is "unlocked".


3. Check external electrical line and its framing in receive directionusing external test equipment.

4. Perform a line loopback to check the operational state of electricalline and its PDH framing, using external test equipment.

5. End.

142 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#91 - Loss of frame



PDH_Line




Severity Minor

Additional Text Loss of frame



Description

Probable cause(s) No E1 or DS1 framing is detected from the line






Current alarm is cleared when card or line is locked


Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 143 / 245


MG#91 - Loss of frame


No


1. Check that the E1 or DS1 configuration of the connected line isappropriate on both ends: in particular, ends should be either bothETSI or both ANSI, and is "unlocked".


3. Check external electrical line and its framing in receive directionusing external test equipment.

4. Perform a line loopback to check the operational state of electricalline and its PDH framing, using external test equipment.

5. End.

144 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#92 - PDH line AIS



PDH_Line




Severity Minor

Additional Text PDH line AIS



Description

Probable cause(s) Power is received from the PDH line but the bit pattern is "all 1s" (AIS), whichindicates that a defect was detected upstream

The remote end of the PDH line or another remote equipment may be mis-configured





Yes

Related alarms None

Corrective actions


No

Actions Repair remote equipment defect

3BL 77057 ACBA RKZZA Ed.04 145 / 245


MG#93 - Signal Failure (SF)



PDH_Line




Severity Minor

Additional Text Signal Failure (SF)



Description

Probable cause(s) The line has reached an error threshold that indicates the lowest limit ofacceptable reception quality


No system reaction

Poor transmission with possible loss of Cs frames that affects traffic qualityand is perceptible by end users



Yes

Related alarms None

Corrective actions


No


1. From the GUI, activate - if not yet started - performance monitoringon the faulty line to get more details about errors types.

2. Activate performance monitoring of other nodes or lines on the linkand locate the faulty elements.


4. End.

146 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#94 - Signal Degraded (SD)



PDH_Line




Severity Minor

Additional Text Signal Degraded (SD)



Description

Probable cause(s) The line has reached an error threshold that indicates a poor reception qual-ity



Degraded transmission with possible loss of Cs frames that affects trafficquality and is perceptible by end users



Yes

Related alarms None

Corrective actions


No


1. From the GUI, activate performance monitoring on the line to getmore details about errors types.

2. Activate performance monitoring of elements along the link, includ-ing a local loop on the 7570, and locate the faulty elements.


4. End.

3BL 77057 ACBA RKZZA Ed.04 147 / 245


MG#95 - PDH line RDI



PDH_Line




Severity Minor

Additional Text PDH line RDI



Description

Probable cause(s) A PDH line AIS from the 7570 has been detected by the peer end point


No traffic is received from the line




Yes

Related alarms None

Corrective actions


No


1. Check if the 7570 line is looped or in manual maintenance. If it isnot, check the other NEs. If it is, the alarm is informative only andwill be cleared when maintenance ends.

2. End.

148 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#96 - TCA crossing 15 minutes



PDH_Line




Severity Minor

Additional Text TCA crossing 15 minutes



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

3BL 77057 ACBA RKZZA Ed.04 149 / 245


MG#97 - TCA crossing 24 hours



PDH_Line




Severity Minor

Additional Text TCA crossing 24 hours



1=code violation

2=errored seconds





Description

Probable cause(s)



Yes

Related alarms None

Corrective actions


Yes

Actions

150 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#98 - Loss of CRC4 multiframe



PDH_Line




Severity Minor

Additional Text Loss of CRC4 multiframe



Description

Probable cause(s) Loss of CRC4 multiframe








Yes

Related alarms None

Corrective actions


No


1. Check that E1 or DS1 configuration of the connected line is appro-priate on both ends: in particular, ends should either be both CRC4configured, or both CRC4 not configured.

2. End.

3BL 77057 ACBA RKZZA Ed.04 151 / 245


MG#111 - Loss of cell delineation



ATM_Port




Severity Major

Additional Text Loss of cell delineation

Additional Info [ Location of the ATM port (Shelf/Slot/Port) ]


Description

Probable cause(s)


All cross connections and all AAL2 paths are out of service


Yes

Related alarms None

Corrective actions


Yes


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 the7570 hardware.

4. If the hardware is faulty, lock the ATM card: the ATM card in EPStakes over.

5. Replace the ATM card, and repeat loopback test.

6. End.

152 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#113 - OAM too many AIS detected



ATM_Port




Severity Critical

Additional Text OAM too many AIS detected



Description

Probable cause(s) The number of end points in AIS state has exceeded the configured AISthreshold



Yes

Related alarms None

Corrective actions


No


1. Check the OFRT profile characteristics.

2. Check ATM network outage (ATM NE(s) and ATM SDH lines).

3. End.

3BL 77057 ACBA RKZZA Ed.04 153 / 245


MG#114 - OAM too many LOC



ATM_Port




Severity Critical

Additional Text OAM too many LOC



Description

Probable cause(s) The number of end points in LOC state has exceeded the configured LOCthreshold



Yes

Related alarms None

Corrective actions


Yes



2. Check that CC source points has been configured.


4. Check for a Switch card problem (Fabric switch).

5. Check for a backplane problem.

6. End.

154 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#115 - OAM too many RDI detected



ATM_Port




Severity Critical

Additional Text OAM too many RDI detected



Description

Probable cause(s) The number of end points in RDI state has exceeded the configured RDIthreshold



Yes

Related alarms None

Corrective actions


No




3. End.

3BL 77057 ACBA RKZZA Ed.04 155 / 245


MG#116 - OAM VC-RDI detected



ATM_VC




Severity Minor

Additional Text OAM VC-RDI detected

Additional Info [ Location of the ATM VC


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


Interruption of cell transfer at VC level in the forward direction


Yes

Related alarms None

Corrective actions


No

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 segmentboundaries, at ATM endpoints that are configured as segment-intermediate.

156 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#117 - OAM VP-RDI detected



ATM_VP




Severity Minor

Additional Text OAM VP-RDI detected

Additional Info [ Location of the ATM VP


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


Interruption of cell transfer at VP level in the forward direction


Yes

Related alarms None

Corrective actions


No

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 segmentboundaries, at ATM endpoints that are configured as segment-intermediate.

3BL 77057 ACBA RKZZA Ed.04 157 / 245


MG#118 - OAM VC-AIS detected



ATM_VC




Severity Minor

Additional Text OAM VC-AIS detected



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 secondsor on reception of a valid user cell or a valid end-to-end CC cell


Interruption of cell transfer at VC level in the forward direction


Yes

Related alarms None

Corrective actions


No

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 segmentboundaries, at ATM endpoints that are configured as segment-intermediate.

158 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#119 - OAM VP-AIS detected



ATM_VP




Severity Minor

Additional Text OAM VP-AIS detected

Additional Info [ Location of the ATM port (Shelf/Slot/PortVP) ]


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 secondsor on reception of a valid user cell or end-to-end CC cell


Interruption of cell transfer at VP level in the forward direction


Yes

Related alarms None

Corrective actions


No

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 segmentboundaries, at ATM endpoints that are configured as segment-intermediate.

3BL 77057 ACBA RKZZA Ed.04 159 / 245


MG#120 - OAM LNK E2E VC-LOC



ATM_VC




Severity Minor

Additional Text OAM LNK E2E VC-LOC

Additional Info One information item is provided with this alarm: Location of the ATM VC


Description

Probable cause(s) This alarm is raised on an OAM VC sink point on an UNI ATM port whenno 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


No cell received from the link on this VC terminating point, or

No cell received from the link on this VC cross-connection


Yes

Related alarms None

Corrective actions


No


1. OAM CC source is already configured.

2. Check for an ATM card failure or ATM SDH lines outage on the VCCpath.

3. End.

160 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#121 - OAM LNK E2E VP-LOC



ATM_VP




Severity Minor

Additional Text OAM LNK E2E VP-LOC



Description

Probable cause(s) This alarm is raised on an OAM VP sink point on an UNI ATM port when noOAM 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


No cell received from the link on this VP cross-connection


Yes

Related alarms None

Corrective actions


No



2. Check for an ATM card failure or ATM SDH lines outage on the VPCpath.

3. End.

3BL 77057 ACBA RKZZA Ed.04 161 / 245


MG#122 - OAM LNK SEG VC-LOC



ATM_VC




Severity Minor

Additional Text OAM LNK SEG VC-LOC



Description

Probable cause(s) This alarm is raised on an OAM VC segment sink point on an ATM portwhen no OAM VC CC cell nor user cell is received for 3.5 seconds from thelink


VC CC cell or user cell from the link


No cell received from the link on this VC cross-connection


Yes

Related alarms None

Corrective actions


No



2. Check for an ATM card failure or ATM SDH lines outage on the VCCsegment path

3. End.

162 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#123 - OAM LNK SEG VP-LOC



ATM_VP




Severity Minor

Additional Text OAM LNK SEG VP-LOC



Description

Probable cause(s) This alarm is raised on an OAM VP segment sink point on an ATM port whenno OAM VP CC cell nor user cell is received for 3.5 seconds from the link


VP CC cell or user cell from the link


No cell received from the link on this VP cross-connection


Yes

Related alarms None

Corrective actions


No


1. OAM CC source is already configured before.

2. Check for an ATM card failure or ATM SDH lines outage on the VPCsegment path.

3. End.

3BL 77057 ACBA RKZZA Ed.04 163 / 245


MG#124 - OAM MATX E2E VC-LOC



ATM_VC




Severity Minor

Additional Text OAM MATX E2E VC-LOC



Description

Probable cause(s) This alarm is raised on an OAM VC sink point on an UNI ATM port whenno OAM VC CC cell nor user cell is received for 3.5 seconds from the fabricswitch


VC CC cell or user cell from the fabric switch


No cell received from the matrix on this VC cross connection


Yes

Related alarms None

Corrective actions


Yes



2. Check for an ATM card failure or ATM SDH lines outage on the VCCpath.



5. End.

164 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#125 - OAM MATX E2E VP-LOC



ATM_VP




Severity Minor

Additional Text OAM MATX E2E VP-LOC



Description

Probable cause(s) This alarm is raised on an OAM VP sink point on an UNI ATM port whenno OAM VP CC cell nor user cell is received for 3.5 seconds from the fabricswitch


VP CC cell or user cell from the fabric switch


No cell received from the fabric switch on this VP cross-connection


Yes

Related alarms None

Corrective actions


Yes



2. Check for an ATM card failure or ATM SDH lines outage on the VPCpath.



5. End.

3BL 77057 ACBA RKZZA Ed.04 165 / 245


MG#126 - Internal OAM MATX SEG VC-LOC



ATM_VC




Severity Minor

Additional Text Internal OAM MATX SEG VC-LOC

Additional Info One information item is provided with this alarm: Location of the ATM VC


Description

Probable cause(s) Information : An internal OAM Segment is used to monitor the ATM cross-connection

This alarm is raised on an OAM VC sink point on a ATM port when neitherOAM VC CC cells nor user cells are received for 3.5 seconds from the fabricswitch


VC CC cell or a user cell from the fabric switch


No cell received from the fabric switch on this VC cross-connection


Yes

Related alarms None

Corrective actions

166 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#126 - Internal OAM MATX SEG VC-LOC


Yes


1. Check for any ATM card failure or ATM SDH lines outage on theVCC segment path.

2. Check for any Switch card problem (Fabric switch).

3. Check for any backplane problem.


5. End.

3BL 77057 ACBA RKZZA Ed.04 167 / 245


MG#127 - Internal OAM MATX SEG VP-LOC



ATM_VP




Severity Minor

Additional Text Internal OAM MATX SEG VP-LOC



Description

Probable cause(s) Information : An internal OAM Segment is used to monitor the ATM cross-connection

This alarm is raised on an OAM VP segment sink point on an ATM port whenneither OAM VP CC cells nor user cells are received for 3.5 seconds fromthe fabric switch


VP CC cell or a user cell from the fabric switch


No cell received from the matrix on this VP cross-connection


Yes

Related alarms None

Corrective actions

168 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#127 - Internal OAM MATX SEG VP-LOC


Yes


1. Check for any ATM card failure or ATM SDH lines outage in the VPCsegment path.

2. Check for any Switch card problem (Fabric switch).

3. Check for any backplane problem.


5. End.

3BL 77057 ACBA RKZZA Ed.04 169 / 245


MG#150 - IP line degraded



IP_Line


Probable cause Degraded signal


Severity Warning

Additional Text IP line degraded

Additional Info [ Location of the IP line (Shelf/Slot/Line_position) ]


Description

Probable cause(s) The line has reached an FCS error threshold indicating poor reception qual-ity



Degraded transmission with Cs traffic frames loss



Yes

Related alarms None

Corrective actions

170 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#150 - IP line degraded


Yes


1. From the GUI, activate performance monitoring on the line - or thetwo lines of the port - for more details about errors types.

2. If both lines are configured and enabled, force a switchover to thebest line among the two, by locking / unlocking the worst line toimprove user Cs quality.

3. Activate performance monitoring of elements on the link and locatethe faulty element.


5. If needed, activate a line loopback on the 7570 faulty line, andconnect an external tool to make measurements.

6. End.

3BL 77057 ACBA RKZZA Ed.04 171 / 245


MG#151 - IP line failure



IP_Line




Severity Minor

Additional Text IP line failure

Additional Info [ 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


Description

Probable cause(s) This alarm is raised when an IP line has failed for one of the followingcauses:

a) Transmission Laser failure

b) LOS

c) Edge Router (Next hop router) unreachable

d) No response to Ping

e) Excessive FCS errors rate


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


No

172 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#151 - IP line failure

Related alarms None

Corrective actions


Yes


1. If cause is "transmission laser failure", lock the IP line, replace thelaser module and unlock the IP line.

2. Check that the configuration of the connected IP line is appropriateon both ends (layer 1) and is "unlocked".

3. If cause is "router unreacheable", check the L2-L3 router state andconfiguration on the interface to the 7570.


5. In case of excessive FCS error rate, check the operational state ofthe external optical line and FCS error rate in the receive directionusing external test equipment.

6. Perform a 7570 line loopback to check the operational state of theoptical line and FCS error rate of the 7570 line, using external testequipment.

7. Check response to ping.

8. End.

3BL 77057 ACBA RKZZA Ed.04 173 / 245


MG#152 - IP port activity lost



IP_Port




Severity Major

Additional Text IP port activity lost

Additional Info [ Location of the IP port (Shelf/Slot/Port) ]


Description

Probable cause(s) This alarm is raised when both IP lines of the port of an unlocked card aredisabled


This IP port does not transport traffic

The alarm is cleared when card or both lines are locked


Yes

Related alarms - MG#151 - IP line failure

Corrective actions


No

Actions The port repair is linked to its line repair.

174 / 245 3BL 77057 ACBA RKZZA Ed.04


6 SIGNALING ALARMSThis section provides all information related to the signaling alarms.

3BL 77057 ACBA RKZZA Ed.04 175 / 245


GSS7#1000 - Platform SS7 destination DPC unreachable



Routeset




Severity Critical

Additional Text Platform SS7 destination DPC unreachable



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 corre-sponding link set is in alarm state.

Note:

The name of the concerned RouteSet is given in the "Object Name". Destina-tion and logical network are displayed in the object.s Name field as follows:Destination%logical_network.


Destination Point applications are not available.


Yes

Related alarms - GSS7#1001 - Link set out of service

Corrective actions

176 / 245 3BL 77057 ACBA RKZZA Ed.04


GSS7#1000 - Platform SS7 destination DPC unreachable


Yes

Actions Signaling traffic should be routed to a backup node or application

Perform each troubleshooting step in the order shown. If the system doesnot clear the alarm continue to the next step.

Troubleshooting procedure:

1. Check if there are alarms on the link sets or individual links thatcompose link sets in the faulty route set. If there are troubleshootthesealarms.

2. Call the operator in charge of the Destination Point to find out ifthere are any problems on that side and how long they expect thefailure to continue.

3. If the Destination Point is expected to be unreachable for an unde-termined period of time check your network configuration to makesure there are no other problems that could blockthe connection.

4. Else re-insert the card removed in step 1, and continue with the nextcard.


6. End.

3BL 77057 ACBA RKZZA Ed.04 177 / 245


GSS7#1001 - Platform SS7 Link set out of service



Linkset




Severity Major

Additional Text Platform SS7 Link set out of service



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". Linkset name and logical network are displayed in the object.s Name field asfollows:link_set%logical_network.


A link set failure can mean that routes and destinations are unavailable.Theredundancy of the SS7 network is in danger.


Yes

Related alarms - GSS7#1002 - Signaling link out of service

Corrective actions


Yes

Actions You should re-enable at least one link in a link set in order to re-enable thelink set. Use the SS7 management GUI to determine which links within thelink set are currently unavailable, initializing, or locked. If there are lockedlinks verify the cause.

Note:

To prevent hardware problems from endangering an entire link set, spreadthe links in the link set over several PCM or ATM connections.

178 / 245 3BL 77057 ACBA RKZZA Ed.04


GSS7#1002 - Platform SS7 Signaling link out of service



Link




Severity Minor

Additional Text Platform SS7 Signaling link out of service



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 oflinks. 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". Thelink name is displayed in the object’s Name field as follows: link_set%logi-cal_network%SLC where SLC = Signaling Link Code.


A link failure can mean that link sets and routes are unavailable. The re-dundancy of the SS7 network is in danger.


Yes

Related alarms - GSS7#1005 - PCM link alarm

- GSS7#1006 - ATM link alarm

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 179 / 245


GSS7#1002 - Platform SS7 Signaling link out of service


Yes

Actions Follow the steps below to restore a signaling link.

After troubleshooting related alarms perform each troubleshooting step inthe order shown. If the system does not clear the alarm continue tothe nextstep.

1. Check the path between the originating station and the AdjacentPoint to determine that the equipment is working properly.

2. Contact the external link providers (telecom operator) if you cannotlocate the faulty element within your network.


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 3BL 77057 ACBA RKZZA Ed.04


GSS7#1005 - Platform SS7 PCM link alarm



PCM_Link



Specific problem PCM alarm (can be an SIA alarm, PVST alarm, CRC4 alarm, IA alarm, TEalarm, or a PVT alarm)

Severity Major

Additional Text Platform SS7 PCM link alarm



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)associ-ated 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.


Some SS7 routes, link sets and applications that use your node may beunavailable. SS7 network redundancy is reduced.


Yes

3BL 77057 ACBA RKZZA Ed.04 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


Yes

Actions Perform each troubleshooting step in the order shown. If the system doesnot 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 SS7management GUI to find out which event caused the alarm. De-pending 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 tofind out if there are any problems on that side and to determine howlong 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 todetermine that the equipment is working properly.

b) Contact the external link providers (telecom operator) if you cannot locatethe faulty element within your network.

182 / 245 3BL 77057 ACBA RKZZA Ed.04


GSS7#1006 - Platform SS7 ATM link alarm



ATM_Link




Severity Major

Additional Text Platform SS7 ATM link alarm



Description

Probable cause(s) An alarm signal has appeared on an ATM link resulting an unavailable AAL5connection.

The ATM interface is not connected or has powered off or the link is down.

The name of the ATM link is in the object’s Name.


Some SS7 routes, link sets and applications that use your node may beunavailable.

SS7 network redundancy is reduced.


Yes






Corrective actions

3BL 77057 ACBA RKZZA Ed.04 183 / 245


GSS7#1006 - Platform SS7 ATM link alarm


Yes

Actions After troubleshooting related alarms perform each troubleshooting step inthe order shown. If the system does not clear the alarm continue to the nextstep.

1. Display the faulty link using the SS7 management GUI to find outwhich event caused the alarm.

2. Check the other end of the link. Contact the operator in charge ofthe other end of the link to find out if there are any problems on thatside and to determine how long the failure might last

3. Check the path between the originating stationand the Adjacent Pointto determine that the equipment is working properly.


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.


7. End.

184 / 245 3BL 77057 ACBA RKZZA Ed.04


GSS7#1100 - Platform SS7 Signaling gateway overload



Gateway




Severity Major

Additional Text Platform SS7 Signaling gateway overload



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 trafficon the gateway.


Traffic may be lost.


Yes

Related alarms None

Corrective actions


No

Actions If station overload is:

1. transient: (or due to an exceptional event), use the SS7 managementGUI to distribute load balancing among signaling gateways.

2. permanent : but repetitive verify network elements (such as RNCs).

3BL 77057 ACBA RKZZA Ed.04 185 / 245


G3UA#1200 - Platform SIGTRAN Association out of service



Association




Severity Minor

Additional Text Platform SIGTRAN Association out of service



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.


An association failure can mean that AS or SG are unavailable. The redun-dancy of the Sigtran network is in danger.


Yes

186 / 245 3BL 77057 ACBA RKZZA Ed.04


G3UA#1200 - Platform SIGTRAN Association out of service






- 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


Yes

Actions Check the connectivity with the remote node.


1. Try a ping to the remote node.

2. Check the related alarms.

3. Check the ethernet interfaces.

4. Check the cables.


6. End.

3BL 77057 ACBA RKZZA Ed.04 187 / 245


G3UA#1201 - Platform SIGTRAN unreachable Application Server



AS




Severity Critical

Additional Text Platform SIGTRAN unreachable Application Server



Description

Probable cause(s) The local AS is down because there is no more association available to anyremote AS.


Local applications are not available from remote AS.


Yes

Related alarms - G3UA#1200 - Association out of service

Corrective actions


Yes

Actions Try to have at least one association available.


1. Fix the related alarms

2. Add an extra SGP or ASP to the local AS


4. End.

188 / 245 3BL 77057 ACBA RKZZA Ed.04


G3UA#1202 - Platform SIGTRAN unreachable Application Server



AS




Severity Critical

Additional Text Platform SIGTRAN unreachable Application Server



Description

Probable cause(s) The remote AS is down because there is no more association available toany remote AS.




Yes


Corrective actions


Yes

Actions Try to have at least one association available.



2. Add an extra SGP or ASP to the local AS


4. End.

3BL 77057 ACBA RKZZA Ed.04 189 / 245


G3UA#1203 - Platform SIGTRAN unreachable Destination PC Node



PC Node




Severity Critical

Additional Text Platform SIGTRAN unreachable Destination PC Node



Description

Probable cause(s) The remote PC Node is down because there is no more SG available towardthis PC.

There is a MTP3 alarm on the node carrying the remote SG.




Yes


Corrective actions


Yes

Actions Ask the remote operator if there is currently a MTP3 alarm on his site.

Try to have at least one SG available.



2. Add an extra SG to the PC Node


4. End.

190 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#260 - 7570 SCTP Association Not Established



Association




Severity Critical

Additional Text 7570 SCTP Association Not Established



Description

Probable cause(s) No SCTP path is available toward the remote ASP with following potentialcauses:

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.


An association failure can mean that AS or SG are unavailable. The redun-dancy of the Sigtran network is in danger.


Yes

Related alarms - 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

3BL 77057 ACBA RKZZA Ed.04 191 / 245


MG#260 - 7570 SCTP Association Not Established


Yes



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 Cen-ter

6. End

192 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#261 - Application Server (AS) not active



Association




Severity Critical

Additional Text Application Server (AS) not active



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.


An association failure can mean that AS is unavailable. The redundancy ofthe Sigtran network is in danger.


Yes

Related alarms - MG#260 - 7570 SCTP Association Not Established



Corrective actions

3BL 77057 ACBA RKZZA Ed.04 193 / 245


MG#261 - Application Server (AS) not active


Yes






4. Check the cables


6. End

194 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#262 - 7570 SCTP Association Not active



Association




Severity Critical

Additional Text 7570 SCTP Association Not active



Description

Probable cause(s) This alarm is raised if the local Signalling Gateway is not in ASP_ACTIVEstate

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.


An association failure can mean that AS is unavailable. The redundancy ofthe Sigtran network is in danger.


Yes


- MG#261 - Application Server (AS) not active


Corrective actions

3BL 77057 ACBA RKZZA Ed.04 195 / 245


MG#262 - 7570 SCTP Association Not active


Yes






4. Check the cables


6. End

196 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#263 - 7570 SS7 Signaling link out of service



Association




Severity Critical

Additional Text 7570 SS7 Signaling link out of service



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 oflinks. 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.


A link failure can mean that link sets and routes are unavailable. The re-dundancy of the SS7 network is in danger.


Yes


- MG#261 - Application Server (AS) not active


Corrective actions

3BL 77057 ACBA RKZZA Ed.04 197 / 245


MG#263 - 7570 SS7 Signaling link out of service


Yes

Actions Follow the steps below to restore a signaling link.

After troubleshooting related alarms perform each troubleshooting step inthe order shown. If the system does not clear the alarm continue to the nextstep.

1. Check the path between the originating station and the AdjacentPoint to determine that the equipment is working properly.


3. If the problem persists, contact Alcatel-Lucent Technical Support Cen-ter.

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 3BL 77057 ACBA RKZZA Ed.04


7 RESOURCE ALARMSThis section provides all information related to the resource alarms.

3BL 77057 ACBA RKZZA Ed.04 199 / 245


MG#160 - Loss of extra (1) VPP resources



VPP


Probable cause Resource at or nearing capacity


Severity Major

Additional Text Loss of extra (1) VPP resources

Additional Info [ Function ] = VPP


Description

Probable cause(s) 7570 is configured with N+1 VPP cards

One VPP card is disabled


No effect on system because subscriber traffic is allocated normally to re-maining enabled VPP cards, but there is no more spare VPP resources in thesystem

Alarm MG#162 is cleared


No

Related alarms None

Corrective actions


Yes


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 faultycard to the repair service.

5. End.

200 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#161 - Loss of extra (1) IP resources



IP




Severity Major

Additional Text Loss of extra (1) IP resources

Additional Info [ Function ] = IP


Description

Probable cause(s) Number of disabled IP ports of 7570 becomes equal to 1


No effect on system because subscriber traffic is allocated normally to re-maining enabled IP ports, but there is no more spare IP bandwidth in thesystem



No

Related alarms - MG#152 - IP port activity lost

Corrective actions


Yes


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 thefaulty 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 relatedalarm.

7. End.

3BL 77057 ACBA RKZZA Ed.04 201 / 245


MG#162 - Loss of several VPP resources



VPP




Severity Critical

Additional Text Loss of several VPP resources

Additional Info [ Function ] = VPP


Description

Probable cause(s) 7570 is configured with N+1 VPP cards

More than one VPP card are disabled


Subscriber traffic is distributed to remaining enabled VPP cards on a per callbasis, and part of the calls are rejected due to lack of VPP resources in thesystem



Yes

Related alarms None

Corrective actions


Yes


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 faultycard to the repair service.

6. End.

202 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#163 - Loss of several IP resources



IP




Severity Critical

Additional Text Loss of several IP resources

Additional Info [ Function ] = IP


Description

Probable cause(s) 7570 is configured with N+1 IP ports

More than one IP port are disabled


Subscriber traffic is distributed to remaining enabled IP ports on a per callbasis, and part of the calls are rejected due to lack of IP bandwidth in thesystem



Yes

Related alarms - MG#152 - IP port activity lost

- MG#161 - Loss of extra (1) IP resources

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 203 / 245


MG#163 - Loss of several IP resources


Yes


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 thefaulty 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 relatedalarm.

8. End.

204 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#170 - Remote NE is isolated



AAL2_resources




Severity Major

Additional Text Remote NE is isolated

Additional Info [ Remote_NE ]


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


No more call can be established with this RNC or this remote NE


Yes

Related alarms None

Corrective actions


Yes


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.

3BL 77057 ACBA RKZZA Ed.04 205 / 245


MG#180 - Handoff erroneous referenced for secondary MGC



MGC_address




Severity Major

Additional Text Handoff erroneous referenced for secondary MGC

Additional Info [ MGC_address ]


Description

Probable cause(s) This alarm is raised when the 7570 tries to perform a handoff on an IPaddress 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


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 configuredMGC list


Yes

Related alarms None

Corrective actions

206 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#180 - Handoff erroneous referenced for secondary MGC


Yes


1. Configure the MGC list in the 7570 if it is a configuration mistake.

2. Check the configuration in the MGC and modify this configurationif needed.

3. Increase the IP security for the H.248 protocol.

4. End.

3BL 77057 ACBA RKZZA Ed.04 207 / 245


MG#181 - Connection to MGC is impossible



Platform_MG




Severity Critical

Additional Text Connection to MGC is impossible



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


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 usedunsuccessfully 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"


Yes

Related alarms None

Corrective actions

208 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#181 - Connection to MGC is impossible


Yes


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. Ifnot repair it.

3. Check the Configured MGC list (IP address and other MGC data)and modify it, if necessary.

4. End.

3BL 77057 ACBA RKZZA Ed.04 209 / 245


MG#182 - First state of regulation



Resource_control


Probable cause CPU cycles limit exceeded


Severity Minor

Additional Text First state of regulation

Additional Info [ Traffic (in Call Attempts Per Second) ]

[ Overload origin ]:

1=Megacop

2=Media Adaptation

3=Megacop traffic acceptable

4=Trillium stack

5=Lowest priority task


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 7570at the same time

c) The H.248.10 package is not used in the call server


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 ofH.248.10 package (if used by the MGC)

b) The 7570 notifies the MGC (with the chp/mgcon event) to reduce thetraffic by a factor of “R” from 0 to 100%. It represents the percentage ofload 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 nooverload for 5 minutes


Yes

210 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#182 - First state of regulation

Related alarms None

Corrective actions


Yes


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 aCPU extension.

4. End.

3BL 77057 ACBA RKZZA Ed.04 211 / 245


MG#183 - Second state of regulation



Resource_control




Severity Major

Additional Text Second state of regulation



1=Megacop

2=Media Adaptation


4=Trillium stack



Description




b) The traffic has too many bursts and there are too many calls to the 7570at the same time

c) The MGC does not reduce the traffic enough, or it does not reduce itquickly enough

212 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#183 - Second state of regulation


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 ofH.248.10 package


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 isset up, the new contexts are accepted)

This alarm may be changed to a minor alarm if the MGC does not use theH.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 overloadoccurs for at least 5 minutes


Yes

Related alarms None

Corrective actions


Yes


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 aCPU extension.

4. End.

3BL 77057 ACBA RKZZA Ed.04 213 / 245


MG#184 - Higher state of regulation before 7570 crash



Resource_control




Severity Critical

Additional Text Higher state of regulation before 7570 crash



1=Megacop

2=Media Adaptation


4=Trillium stack



Description




b) The traffic has too many bursts, and there are too many calls to the 7570at the same time

c) TheMGC does not reduce the traffic enough, or does not reduce it quicklyenough

214 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#184 - Higher state of regulation before 7570 crash


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 ofH.248.10 package


c) In addition, the 7570 accepts subtract commands and only in a propor-tion of 20% of the acceptable H.248 command. Commands for newcontext 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 overloadoccurs for at least 5 minutes


Yes

Related alarms None

Corrective actions


Yes

Actions Megacop overload, MA overload, Megacop traffic acceptable, trillium stackoverload, lowest priority task overload

3BL 77057 ACBA RKZZA Ed.04 215 / 245


MG#185 - Profile negotiation failed with MGC



MGC_address




Severity Critical

Additional Text Profile negotiation failed with MGC

Additional Info [ Profile sent by MGC to 7570 ]


Description

Probable cause(s) This alarm is raised when a profile negotiation between MGC and 7570failed

Possible type of failure is:

a) 7570 profile list not compliant with MGC supported profiles


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


Yes

Related alarms None

Corrective actions


Yes


1. Match 7570 and MGC profile lists.

2. End.

216 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#200 - Loss of IP Bandwidth



Common_Media_resources




Severity Minor

Additional Text Loss of IP Bandwidth

Additional Info


Description

Probable cause(s) This alarm is raised when the available bandwidth is insufficient to establishan IP bearer for a call


a) More than one IPGE is in failure

b) Loss of IPGE

c) Loss of bandwidth on IPGE


Call will not be established

This alarm is raised as soon as 15 lack of resource events occur within 15minutes

This alarm is cleared when no lack of resource event occurs within a periodof 15 to 30 minutes


Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 217 / 245


MG#200 - Loss of IP Bandwidth


Yes


1. Check the availability of the IP Port. If it is not available, restore itsavailability.

2. If the AAL2 path is available, add AAL2 path or increase the band-width of AAL2 path if the maximum bandwidth is not reached.

3. End.

218 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#201 - Loss of ATM bandwidth



AAL2_resources




Severity Minor

Additional Text Loss of ATM bandwidth

Additional Info [ Remote NE ]


Description

Probable cause(s) This alarm is raised when the available bandwidth is not enough to establishan AAL2 bearer for a call


a) A call initialized by the remote side is incompatible with the allowed band-width

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 withoutredudant card

d) Call initialized by the local side: Lack of AAL2 path






Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 219 / 245


MG#201 - Loss of ATM bandwidth


Yes


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 3BL 77057 ACBA RKZZA Ed.04


MG#202 - Lack of codec



Codec_resources




Severity Minor

Additional Text Lack of codec

Additional Info [ Codec_type ]


Description

Probable cause(s) This alarm is raised in case of lack of codec type


a) More one than one VPP has failed

b) Lack of VPP

c) Bad package configuration






Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 221 / 245


MG#202 - Lack of codec


Yes


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 pack-ages and IWF packages are in overload, you must add a VPP orchoose (at MGC level) a codec that requires less DSP processing likeG711. If some codec packages are in overload, and others are not,the configuration of the DSP must be changed.

3. End.

222 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#203 - Lack of echo canceling



Line_card_resources




Severity Minor

Additional Text Lack of echo canceling

Additional Info [TDM/X address (Shelf/Slot) ]


Description

Probable cause(s) This alarm is raised in case of lack of echo cancelling


a) The does not have enough echo cancelling

b) A wrong port is attached to the TDMX (PSTN port instead of PLMN portfor example)

c) Too many ports are attached to this TDMX


Call will be established without EC




Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 223 / 245


MG#203 - Lack of echo canceling


Yes


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 3BL 77057 ACBA RKZZA Ed.04


MG#204 - Lack of Voice quality enhancement processing



Line_card_resources




Severity Minor

Additional Text Lack of Voice quality enhancement processing

Additional Info [TDM/X address (Shelf/Slot) ]


Description

Probable cause(s) This alarm is raised in case of lack of Voice Quality Enhancement (VQE)


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 portfor example)

c) Too many ports are attached to this TDMX


Call will be established without VQE processing




Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 225 / 245


MG#204 - Lack of Voice quality enhancement processing


Yes


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 3BL 77057 ACBA RKZZA Ed.04


MG#205 - Lack of MF generator



Line_card_resources




Severity Minor

Additional Text Lack of MF generator

Additional Info [ Line card address (Shelf/Slot) ]


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


DTMF is not transmitted




Yes

Related alarms None

Corrective actions


Yes


1. If a TDMX is concerned, balance 2G//PLMN or PSTN port on thecard to reduce the load of the card.

2. If a VPP is concerned, add a VPP card.

3. End.

3BL 77057 ACBA RKZZA Ed.04 227 / 245


MG#206 - Lack of MF receiver



Line_card_resources




Severity Minor

Additional Text Lack of MF receiver



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


DTMF is not transmitted




Yes

Related alarms None

Corrective actions


Yes




3. End.

228 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#208 - Lack of announcement generator



Line_card_resources




Severity Minor

Additional Text Lack of announcement generator



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 ofannouncements


Announcement is not sent




Yes

Related alarms None

Corrective actions


Yes




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 disappearwhen the crash will end so the action is to repair the crash

3BL 77057 ACBA RKZZA Ed.04 229 / 245


MG#209 - Lack of conference bridge



Common_Media_resources




Severity Minor

Additional Text Lack of conference bridge

Additional Info none


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 protectionstate "active" or "none", related conference bridge resources are lost. Be-cause need of these resources may be considered related to TDMX traffic,it is rational to think that changes of TDMX states don’t generate a lack ofconference bridge.


The conference cannot be established




Yes

Related alarms None

Corrective actions

230 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#209 - Lack of conference bridge


Yes


1. The conference bridges of VPP and TDMX are in pool. So first checkthe availability of the N VPP if any (one can stay out of service), andif 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.

3BL 77057 ACBA RKZZA Ed.04 231 / 245


MG#210 - Lack of continuity check resources



Line_card_resources




Severity Minor

Additional Text Lack of continuity check resources

Additional Info [ TDMX address (Shelf/Slot) ]


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 ofcontinuity check


The continuity check will fail

All TS will be unaivailable as long as no continuity check is successfull




Yes

Related alarms None

Corrective actions


Yes


1. Mix BSC and ISUP terminations on this TDMX to reduce the need ofISUP terminations on this TDMX.

2. Require continuity check only on demand or with cyclic maintenance.

3. End.

232 / 245 3BL 77057 ACBA RKZZA Ed.04


MG#211 - Lack of IWF



IWF_resources




Severity Minor

Additional Text Lack of IWF

Additional Info [ IWF_type ]


Description

Probable cause(s) This alarm is raised in case of lack of IWF type


a) More one than one VPP has failed

b) Lack of VPP

c) Bad package configuration






Yes

Related alarms None

Corrective actions

3BL 77057 ACBA RKZZA Ed.04 233 / 245


MG#211 - Lack of IWF


Yes


1. Check the availability of the N VPP (one can stay out of service). If itis not available, restore the availability of the VPP.

2. Check the codec and IWF pakage measurement. If all codec andIWF packages are in overload, you must add a VPP. If some IWFpackages are in overload, and others are not, change the configu-ration of the DSP.

3. End.

234 / 245 3BL 77057 ACBA RKZZA Ed.04


8 MGC10 SYNTHESIS ALARMSThis section is applicable only when the 7570 MG platform supports the Alcatel-Lucent 5020 MediaGateway Controller-10 (MGC10) product. It provides all information related to the MGC10 synthesisalarms.

In the following alarm definitions, E10 refers to the MGC10.

For more information about MGC10 alarms description, see the Alcatel-Lucent 5020 MGC10 AlarmsDictionary, ALA283.

3BL 77057 ACBA RKZZA Ed.04 235 / 245


E10#1 - Total MGC Failure



E10_supervision




Severity Critical

Additional Text Total MGC Failure

Additional Info


Description

Probable cause(s) This alarm is raised when MGC10 becomes out of service or runs in nonconnected mode


a) The MGC10 may be out of service.

b) Operation of the MGC10 may be unavailable.


Yes

Related alarms None

Corrective actions


No


1. Restart the MGC10 (see the MGC10 maintenance information).

2. If this alarm is still not cleared, contact your Alcatel-Lucent TechnicalSupport Center.

3. End.

236 / 245 3BL 77057 ACBA RKZZA Ed.04


E10#2 - MGC Call Server synthesis - IM



E10_supervision


Probable cause Performance degraded


Severity Critical

Additional Text MGC Call Server synthesis - IM

Additional Info


Description

Probable cause(s) This alarm is raised when at least one critical alarm is present on the MGC10subsystem.


Dependent on the alarm raised at the MGC10.


Yes

Related alarms None

Corrective actions


No

Actions See the MGC10 Alarm Management GUI to perform the actions for eachalarm.

3BL 77057 ACBA RKZZA Ed.04 237 / 245


E10#3 - MGC Call Server synthesis - ID



E10_supervision




Severity Major

Additional Text MGC Call Server synthesis - ID

Additional Info


Description

Probable cause(s) This alarm is raised when at least one major alarm is present on the MGC10subsystem.




Yes

Related alarms None

Corrective actions


No


238 / 245 3BL 77057 ACBA RKZZA Ed.04


E10#4 - MGC Call Server synthesis - SI



E10_supervision




Severity Minor

Additional Text MGC Call Server synthesis - SI

Additional Info


Description

Probable cause(s) This alarm is raised when at least one minor alarm is present on the MGC10subsystem.




Yes

Related alarms None

Corrective actions


No


3BL 77057 ACBA RKZZA Ed.04 239 / 245


E10#5 - MGC Internal System Backup Missing



E10_supervision


Probable cause Sofware error


Severity Minor

Additional Text MGC Internal System Backup Missing

Additional Info


Description

Probable cause(s) This alarm is raised when the internal MGC10 system backup is missing orfaulty.


As long as this alarm is present, you cannot launch an MGC10 applicationbackup.


No

Related alarms None

Corrective actions


No


1. Open a telnet windows with OAM IP address of the platform.

2. Launch the internal MGC10 system backup using the following Linuxcommand: touch /e10/pivot/e10proxy/syst_backup.flag

3. If this alarm is still not cleared, contact your Alcatel-Lucent TechnicalSupport Center.

4. End.

240 / 245 3BL 77057 ACBA RKZZA Ed.04


ABBREVIATIONS2G second Generation2G Second Generation3G third Generation3G Third Generation

A

AAL2 ATM Adaptation Layer type 2AAL5 ATM Adaptation Layer type 5AIS Alarm Indication SignalATM Asynchronous Transfer Mode

B

BIOS Basic Input Output SystemBSS Base Station Subsystem

C

CC Continuity CheckCOAL Configuration and AlarmsCPU Central Processing Unit

E

ECC Error Correction CodeEPS Equipment Protection Switch

F

FCS Frame Check SequenceFRU Field Replaceable Unit

G

GPRS General Packet Radio ServiceGSM Global System for Mobile communicationsGUI Graphical User Interface

H

HW HardWare

I

I/O Input/OutputID deferred actionIM IMmediate actionIPGE Internet Protocol packet processing over Gigabit Ethernet

3BL 77057 ACBA RKZZA Ed.04 241 / 245


IP Internet ProtocolIPMB Intelligent Platform Management BusIPMC Intelligent Platform Management ControllerITU-T International Telecommunication Union - Telecommunication standardizationsectorIU Interface UnitIWF InterWorking Function

L

LANIO Local Area Network Input/OutputLCA Loss of CRC4 sub-multiframe AlignmentLFA Loss of Frame AlignmentLIS Loss of Incoming SignalLIU Line Interface UnitLOC Loss Of ContinuityLSN Local Secured Network

M

MGC Media Gateway ControllerMG Media GatewayMIB Management Information BaseMOC Managed Object ClassMSM Multiple Storage Module

N

NE Network ElementNRJA Non-urgent Remote Junction Alarm

O

OAM Operation, Administration and Maintenance

P

PCM Pulse Code ModulationPDH Plesiochronous Digital HierarchyPDU Power Distribution UnitPEM Power Entry ModulePMC PCI Mezzanine Card

R

RAP Rack Alarm PanelRDI Remote Defect IndicationRJA Remote Junction AlarmRNC Radio Network Controller

242 / 245 3BL 77057 ACBA RKZZA Ed.04


S

SDH Synchronous Digital HierarchySHMC Shelf Management ControllerSI without actionSS7 Signaling System Nº7SS7 Signaling System N7

T

TASC Technical Assistance and Support CenterTDM Time Division Multiplexing

U

UE User EquipmentUMA Unlicensed Mobile AccessUTRAN UMTS Terrestrial Radio Access Network

V

VCC Virtual Channel ConnectionVC Virtual ChannelVPC Virtual Path ConnectionVPP Voice Packet ProcessingVP Virtual Path

3BL 77057 ACBA RKZZA Ed.04 243 / 245

244 / 245 3BL 77057 ACBA RKZZA Ed.04


INDEXA

Alarm descriptionoverview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

H

Hardwarealarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

I

Infrastructurealarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

L

Line and portalarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

M

MGC10alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

R

Resourcealarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

S

Signalingalarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Softwarealarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

3BL 77057 ACBA RKZZA Ed.04 245 / 245