Sunteți pe pagina 1din 93

118 - R5.

3 alarms Page 1 sur 93

7302/7330/7356/7360/7367/7363 ISAM Operations and Maintenance Using the 5520 AMS Release 9.4 > Alarms

118 - R5.3 alarms


118.1 Alarm classes
118.2 EMS local alarms
118.3 NE alarms

118.1 Alarm classes


Table 118-1 lists the NE alarms classes.

Table 118-1 NE alarms classes


NE alarms classes
AIPLATFORM alarms ONT VDSL2 far-end service alarms
ATM alarms ONT video ANI service alarms
Authentication alarms ONT video service alarms
Board alarms ONT VoIP service alarms
Bonding alarms ONT-Board alarms
CHANNEL-PAIR alarms ONT Ethernet alarms
Derived alarms ONT MDU alarms
E1-DS1 alarms ONT SFU alarms
EPON alarms ONT-SNMP alarms
EPONONT alarms ONT SOHO alarms
EPONONT-ETHPORT alarms ONT IP host alarms
EPONONT-POTSPORT alarms ONT VEIP configuration alarms
Ethernet alarms PON alarms
FTP alarms PORT alarms
HUB alarms PPPCCEngine alarms
IMA group alarms QoS alarms
IMA link alarms Rack alarms
IP routing alarms SFP alarms
LLU alarms SHDSL pair alarms
Logical link alarms SHDSL Unit alarms
MEP alarms SHub alarms
MGC configuration alarms SIP alarms
Multicast alarms SIP configuration alarms
NE alarms SIP termination alarms
NGPON2-ONT alarms Slot alarms
ONT alarms Subrack alarms
ONT CES DS1 service alarms TR-069 alarms
ONT CES E1 service alarms VLAN port alarms
ONT CES PWE service alarms Voice server alarms
ONT HPNA service alarms VoIP alarms
ONT LAN service alarms VOIP configuration alarms
ONT MoCA service alarms xDSL alarms
ONT POTS service alarms xDSL far-end alarms
ONT VDSL2 service alarms xDSL near-end alarms

Table 118-2 provides a legend of the alarm categories that are displayed in the alarm tables.

Table 118-2 Category legend


Category Description

Comm Communications

Env Environmental

Eqt Equipment

Proc Processing Error

Qos Quality of Service

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 2 sur 93

118.2 EMS local alarms


Table 118-3 describes the NE alarms.

Table 118-3 NE alarms


Default
Category /
Probable cause / severity /
Specific problem Service Repair action
Mnemonic Default
affecting
reporting

Alarm Synchronization
Alarm Not Known By Major Eqt Contact your Alcatel-Lucent technical support
Problem
EMS On No representative.
ALRM

118.3 NE alarms
Table 118-4 describes the AIPLATFORM alarms.

Table 118-4 AIPLATFORM alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

Application Not Read more information about the


Installation Major Comm
Installed AIINSTALLFAIL 201 / 2 failure in the AI Platform-Application
Failure On No
ANI table.

Platform Not
Platform Major Eqt Check if the board plugged in the slot
Available AIPLATFFAIL 201 / 1
Failure On No is operational.
PNA

Table 118-5 describes the ATM alarms.

Table 118-5 ATM alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Congestion Cells Discarded Minor Qos No local repair action. Sender


CELLDSCUP 8/2
CONG Upstream Off Yes must have a lower shaping rate.

Congestion Cells Discarded Minor Qos No local repair action. Sender


CELLDSCDN 8/3
CONG Downstream Off Yes must have a lower shaping rate.

Table 118-6 describes the authentication alarms.

Table 118-6 Authentication alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

1. Check the configuration


Configuration Or VLAN Major Proc of the system.
Customization Error Assignment VLANASGFAIL 55 / 2
Failure On Yes 2. Check the configuration
CFG
of the RADIUS server.

Table 118-7 describes the board alarms.

Table 118-7 Board alarms


Probable cause / Specific problem TL1 condition Default Alarm Category / Repair action
Mnemonic severity / ID Service
Default affecting
reporting

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 3 sur 93

Configuration Or 1. Check the configuration.


Customization Waiting For Major Eqt 2. Download the software.
Error PROGVER 3/4
Software On No 3. Wait for the SW download from
CFG the server to be completed.

Configuration Or 1. Download the required CDE file


Customization Major Proc again.
Error CDE File Missing MISSCDE 29 / 6
On No 2. Activate the downloaded CDE
CFG file.

Configuration Or
Customization Major Proc Download and active a new CDE
Error CDE File Hash Error CDEHASHERR 29 / 8
On Yes profile with valid hash key.
CFG

Synchronization
Loss Of Network Major Eqt Check the status of the NT-A
Source Mismatch NTRALOS 84 / 6
Timing Reference A On Yes network timing reference.
CLK

Synchronization
Loss Of Network Major Eqt Check the status of NT-B network
Source Mismatch NTRBLOS 84 / 7
Timing Reference B On Yes timing reference.
CLK

Communications
DHCP Server Critical Comm Check the link between ISAM and
Subsystem Failure DHCPUNRCH 99 / 3
Unreachable On Yes the DHCP server.
COM

Equipment Force a cold reset of the board. If


Board Initialization Major Eqt
Malfunction BDINIT 3 / 16 the board fails again, repair the
Failure On Yes
EQP board.

Check the cabling if the alarm is


Equipment persistent. If alarm toggles
Board Reset Or Major Eqt
Malfunction frequently, the board goes into the
Communication BDRESETCF 3 / 30
On Yes board reset protection mode
EQP Failure
(board reset threshold exceeded
alarm) and powers down.

No Free MAC No special repair action. This


Minor 84 / Eqt alarm is a notification that there
Entry - NOFREEMAC
On 12 No are no more free MAC entries in
MAC the MAC table on the LT board.

Power Problem Power To External Critical Eqt


SEM-PWR- Check the power to the external
Power Source 3 / 28
PWR FAIL On Yes power supply.
Failure

Power Problem External Power Critical Eqt


SEM-UPS-FAIL 3 / 29 Check the external power supply.
PWR Failure On Yes

Temperature Check fans and restart the board.


Temperature Major Eqt
Unacceptable HITEMP 3/8 In remote boxes, check the fan
Threshold Exceeded On No
TEMP dust filter as well.

1. Check the ambient


Temperature Temperature temperature.
Threshold Far Major Eqt
Unacceptable SHUTDOWN 3 / 12 2. Check the operation of the
Exceeded (Power On Yes
TEMP fans.
Shutdown)
3. Check the board.

Table 118-8 describes the bonding alarms.

Table 118-8 Bonding alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

1. Check the
Configuration Or Upstream Major Comm configuration data.
Customization Error Configuration Not BELOWCONFRATE 54 / 3
Feasible On Yes 2. Check the physical
CFG
line.

Configuration Or Downstream BELOWCONFRATE Major 54 / 6 Comm 1. Check the


Customization Error Configuration Not On Yes configuration data.
Feasible

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 4 sur 93

CFG 2. Check the physical


line.

Communications 1. Check the modem.


No Bonding CPE Minor Comm
Subsystem Failure NOBONDCPE 54 / 8 2. Check the physical
Modem Connected On Yes
COM line.

Communications Bonding Group 1. Check the DSL


Major Comm
Subsystem Failure Connected To BGMORECPE 54 / 9 wiring configuration.
Multiple CPE On No
COM 2. Check the CPE.

Communications
Major Comm
Subsystem Failure CPE Register Failure REGFAIL 54 / 10 Check the CPE.
On No
COM

Communications 1. Check the DSL


Bonding Group Minor Comm
Subsystem Failure BGINCOMPL 54 / 11 wiring configuration.
Incomplete On No
COM 2. Check the CPE.

Threshold Crossed Upstream Planned Minor Comm Decrease the group


Bitrate Threshold BELOWPLANRATE 54 / 1 upstream planned bit
TCA Alarm On Yes rate.

Upstream Minimum 1.Check the physical


Threshold Crossed Minor Comm
Bitrate Threshold BELOWMINRATE 54 / 2 line.
TCA Alarm On Yes
2. Check the line state.

Threshold Crossed Downstream Planned Minor Comm Decrease the group


Bitrate Threshold BELOWPLANRATE 54 / 4 downstream planned
TCA Alarm On Yes bit rate.

Downstream 1. Check the physical


Threshold Crossed Minor Comm
Minimum Bitrate BELOWMINRATE 54 / 5 line.
TCA Threshold Alarm On Yes
2. Check the line state.

Table 118-9 describes the CHANNEL-PAIR alarms.

Table 118-9 CHANNEL-PAIR alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

Configuration
Or No repair necessary,indication to
New ONT Minor 226 / Eqt
Customization CPNEWONT operator that further provisioning
Error Discovered On 3 No should commence.
CFG

Configuration
Or Channel Pair Provisioned attributes failed to be
Major 226 / Eqt
Customization Provisioning CPMEA provisioned for Channel Pair.
Error On 4 Yes
Failure Reprovision the Channel Pair.
CFG

Equipment Channel Pair Critical 226 / Eqt


Malfunction Communication CPCOMMFAIL Restart the Channel Pair.
On 1 Yes
EQP Failure

Local Node
Transmission Critical 226 / Eqt
Error - CPTXFAIL Check OLT laser.
On 2 Yes
LCL

Loss Of Signal Major 226 / Comm Check receive Channel Pair Fiber
- CPLOS
LOS On 5 Yes input at OLT.

This alarm indicates that there is a


mismatch between the channel
pair provisioned SFP laser
SFP Problem Major Eqt characteristics and actual SFP
User SFP 226 /
CPSFPMISMATCH laser transceive that is plugged in.
SFP Mismatch On 10 Yes Either re-provision the channel-
pair to match the SFP or plug in a
new SFP that matches the
provisioning or do both.

T-TXMCUTILHI Warning Qos

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 5 sur 93

Threshold Downstream 227 / 1/ None. Just a warning that


Crossed Multicast On 1 No traffic has exceeded a set
TCA Utilization High bandwidth threshold.
Threshold Alarm

Downstream
Threshold Multicast 1/ None. Just a warning that
Warning 227 / Qos
Crossed Utilization T-TXMCUTILMD traffic has exceeded a set
On 2 No
TCA Medium bandwidth threshold.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. Just a warning that
Crossed Multicast 227 /
T-TXMCUTILLO traffic has exceeded a set
Utilization Low On 3 No
TCA bandwidth threshold.
Threshold Alarm

Threshold Downstream Total 1/ None. Just a warning that


Warning 227 / Qos
Crossed Utilization High T-TXTOTUTILHI traffic has exceeded a set
On 4 No
TCA Threshold Alarm bandwidth threshold.

Threshold Downstream Total


Warning Qos 1/ None. Just a warning that
Crossed Utilization 227 /
T-TXTOTUTILMD traffic has exceeded a set
Medium On 5 No
TCA bandwidth threshold.
Threshold Alarm

Threshold Downstream Total 1/ None. Just a warning that


Warning 227 / Qos
Crossed Utilization Low T-TXTOTUTILLO traffic has exceeded a set
On 6 No
TCA Threshold Alarm bandwidth threshold.

Threshold Upstream Total 1/ None. Just a warning that


Warning 227 / Qos
Crossed Utilization High T-RXTOTUTILHI traffic has exceeded a set
On 7 No
TCA Threshold Alarm bandwidth threshold.

Threshold Upstream Total


Warning Qos 1/ None. Just a warning that
Crossed Utilization 227 /
T-RXTOTUTILMD traffic has exceeded a set
Medium On 8 No
TCA bandwidth threshold.
Threshold Alarm

Threshold Upstream Total 1/ None. Just a warning that


Warning 227 / Qos
Crossed Utilization Low T-RXTOTUTILLO traffic has exceeded a set
On 9 No
TCA Threshold Alarm bandwidth threshold.

Threshold DBA Congestion 1/ None. Just a warning that


T- Warning 227 / Qos
Crossed High Threshold traffic has exceeded a set
DBACONGPERIODHI On 10 No
TCA Alarm bandwidth threshold.

Threshold DBA Congestion 1/ None. Just a warning that


T- Warning 227 / Qos
Crossed Medium traffic has exceeded a set
DBACONGPERIODMD On 11 No
TCA Threshold Alarm bandwidth threshold.

Threshold DBA Congestion 1/ None. Just a warning that


T- Warning 227 / Qos
Crossed Low Threshold traffic has exceeded a set
DBACONGPERIODLO On 12 No
TCA Alarm bandwidth threshold.

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Unicast Dropped 227 /
T-TXUCDROPFRMHI unacceptable, determine why
Frames High On 13 No
TCA frames are being dropped.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Unicast Dropped 227 /
T-TXUCDROPFRMMD unacceptable, determine why
Frames Medium On 14 No
TCA frames are being dropped.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Unicast Dropped 227 /
T-TXUCDROPFRMLO unacceptable, determine why
Frames Low On 15 No
TCA frames are being dropped.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Multicast Dropped 227 /
T-TXMCDROPFRMHI unacceptable, determine why
Frames High On 16 No
TCA frames are being dropped.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Multicast Dropped 227 /
T-TXMCDROPFRMMD unacceptable, determine why
Frames Medium On 17 No
TCA frames are being dropped.
Threshold Alarm

Threshold Downstream T-TXMCDROPFRMLO Warning 227 / Qos 1/ None. A warning. If situation


Crossed Multicast Dropped On 18 No unacceptable, determine why
frames are being dropped.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 6 sur 93

TCA Frames Low


Threshold Alarm

Downstream
Threshold Broadcast 1/ None. A warning. If situation
Warning 227 / Qos
Crossed Dropped Frames T-TXBCDROPFRMHI unacceptable, determine why
On 19 No
TCA High Threshold frames are being dropped.
Alarm

Downstream
Threshold Broadcast 1/ None. A warning. If situation
Warning 227 / Qos
Crossed Dropped Frames T-TXBCDROPFRMMD unacceptable, determine why
On 20 No
TCA Medium frames are being dropped.
Threshold Alarm

Downstream
Threshold Broadcast 1/ None. A warning. If situation
Warning 227 / Qos
Crossed Dropped Frames T-TXBCDROPFRMLO unacceptable, determine why
On 21 No
TCA Low Threshold frames are being dropped.
Alarm

Threshold Upstream Total


Warning Qos 1/ None. A warning. If situation
Crossed Dropped Frames 227 /
T-RXTOTDROPFRMHI unacceptable, determine why
High Threshold On 22 No
TCA frames are being dropped.
Alarm

Threshold Upstream Total


Warning Qos 1/ None. A warning. If situation
Crossed Dropped Frames T- 227 /
unacceptable, determine why
Medium RXTOTDROPFRMMD On 23 No
TCA frames are being dropped.
Threshold Alarm

Threshold Upstream Total


Warning Qos 1/ None. A warning. If situation
Crossed Dropped Frames T- 227 /
unacceptable, determine why
Low Threshold RXTOTDROPFRMLO On 24 No
TCA frames are being dropped.
Alarm

1. Check Receive Channel Pair


signal at OLT.
2. Check Transmit Channel Pair
Errored Lost GEM signal at ONT.
Threshold
Fragments Minor 229 / Qos 3. Check ONT for ONT TC
Crossed T-CPERRFRAGS
Received At OLT On 1 No ERRFRAGS and isolate at ONT
TCA Near End level if ONT counts exist.
4. Reset LT 5/Replace
associated LT at OLT if PM
counts persist.

Threshold Channel Pair


Major Comm None. A warning. If situation
Crossed Upstream 229 /
T-CPBWTCA unacceptable, determine why
Bandwidth At On 2 Yes
TCA Upstream BW is high.
OLT

Threshold Channel Pair


Major Comm None. A warning. If situation
Crossed Downstream 229 /
T-BWTCA unacceptable, determine why
Bandwidth At On 3 Yes
TCA Downstream BW is high.
OLT

Table 118-10 describes the derived alarms.

Table 118-10 Derived alarms


Default
Category /
Probable cause / Specific TL1 severity / Alarm
Service Repair action
Mnemonic problem condition Default ID
affecting
reporting

<From basic
<From basic alarm> Temporal
- - 34 / 1 alarm> -
- Filter 1
No

<From basic
<From basic alarm> Temporal
- - 34 / 2 alarm> -
- Filter 2
No

<From basic
<From basic alarm> Temporal
- - 34 / 3 alarm> -
- Filter 3
No

<From basic alarm> Temporal - - 34 / 4 <From basic -


- Filter 4 alarm>

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 7 sur 93

No

<From basic
<From basic alarm> Temporal
- - 34 / 5 alarm> -
- Filter 5
No

<From basic
<From basic alarm> Temporal
- - 34 / 6 alarm> -
- Filter 6
No

<From basic
<From basic alarm> Temporal
- - 34 / 7 alarm> -
- Filter 7
No

<From basic
<From basic alarm> Temporal
- - 34 / 8 alarm> -
- Filter 8
No

<From basic
<From basic alarm> Temporal
- - 34 / 9 alarm> -
- Filter 9
No

<From basic
<From basic alarm> Temporal
- - 34 / 10 alarm> -
- Filter 10
No

<From basic
<From basic alarm> Temporal
- - 34 / 11 alarm> -
- Filter 11
No

<From basic
<From basic alarm> Temporal
- - 34 / 12 alarm> -
- Filter 12
No

<From basic
<From basic alarm> Temporal
- - 34 / 13 alarm> -
- Filter 13
No

<From basic
<From basic alarm> Temporal
- - 34 / 14 alarm> -
- Filter 14
No

<From basic
<From basic alarm> Temporal
- - 34 / 15 alarm> -
- Filter 15
No

<From basic
<From basic alarm> Temporal
- - 34 / 16 alarm> -
- Filter 16
No

<From basic
<From basic alarm> Temporal
- - 34 / 17 alarm> -
- Filter 17
No

<From basic
<From basic alarm> Temporal
- - 34 / 18 alarm> -
- Filter 18
No

<From basic
<From basic alarm> Temporal
- - 34 / 19 alarm> -
- Filter 19
No

<From basic
<From basic alarm> Temporal
- - 34 / 20 alarm> -
- Filter 20
No

<From basic
<From basic alarm> Temporal
- - 34 / 21 alarm> -
- Filter 21
No

<From basic
<From basic alarm> Temporal
- - 34 / 22 alarm> -
- Filter 22
No

<From basic
<From basic alarm> Temporal
- - 34 / 23 alarm> -
- Filter 23
No

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 8 sur 93

<From basic alarm> Temporal - - 34 / 24 <From basic -


- Filter 24 alarm>
No

<From basic
<From basic alarm> Temporal
- - 34 / 25 alarm> -
- Filter 25
No

<From basic
<From basic alarm> Temporal
- - 34 / 26 alarm> -
- Filter 26
No

<From basic
<From basic alarm> Temporal
- - 34 / 27 alarm> -
- Filter 27
No

<From basic
<From basic alarm> Temporal
- - 34 / 28 alarm> -
- Filter 28
No

<From basic
<From basic alarm> Temporal
- - 34 / 29 alarm> -
- Filter 29
No

<From basic
<From basic alarm> Temporal
- - 34 / 30 alarm> -
- Filter 30
No

<From basic
<From basic alarm> Temporal
- - 34 / 31 alarm> -
- Filter 31
No

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 1 alarm>
SPF1 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 10 alarm>
SPF10 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 11 alarm>
SPF11 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 12 alarm>
SPF12 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 13 alarm>
SPF13 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 14 alarm>
SPF14 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 15 alarm>
SPF15 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 16 alarm>
SPF16 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 17 alarm>
SPF17 On 2. Check the setting of the
No
related filter.

<From basic alarm> - SF Indeterminate 35 / 18 <From basic 1. Check the cause of the
SPF18 On alarm> related basic alarm.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 9 sur 93

No 2. Check the setting of the


related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 19 alarm>
SPF19 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 2 alarm>
SPF2 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 20 alarm>
SPF20 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 21 alarm>
SPF21 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 22 alarm>
SPF22 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 23 alarm>
SPF23 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 24 alarm>
SPF24 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 25 alarm>
SPF25 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 26 alarm>
SPF26 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 27 alarm>
SPF27 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 28 alarm>
SPF28 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 29 alarm>
SPF29 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 3 alarm>
SPF3 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 30 alarm>
SPF30 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 31 alarm>
SPF31 On 2. Check the setting of the
No
related filter.

<From basic alarm> - SF Indeterminate 35 / 4 <From basic 1. Check the cause of the
SPF4 On alarm> related basic alarm.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 10 sur 93

No 2. Check the setting of the


related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 5 alarm>
SPF5 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 6 alarm>
SPF6 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 7 alarm>
SPF7 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 8 alarm>
SPF8 On 2. Check the setting of the
No
related filter.

1. Check the cause of the


<From basic
<From basic alarm> Indeterminate related basic alarm.
- SF 35 / 9 alarm>
SPF9 On 2. Check the setting of the
No
related filter.

Table 118-11 describes the E1-DS1 alarms.

Table 118-11 E1-DS1 alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

SERDES 1. Check clock source configuration,


Alarm Failure Major 210 / Comm
Clock Alarm DS1E1_SERDES_FAIL 2. Verify if SERDES clock is traceable
AF On 1 Yes
Failure to a reliable clock (PRC)

Alarm Failure Tributary 1 Major Comm


210 /
Clock Not DS1E1_TRIB1_FAIL Check Clock Source configurations
AF On 2 Yes
Present

Alarm Failure Tributary 2 Major Comm


210 /
Clock Not DS1E1_TRIB2_FAIL Check Clock Source configurations
AF On 3 Yes
Present

1. Determine whether problem is due


to E1/DS1 network/equipment problem
or misprovisioning. AIS represents a
failure upstream in the network where
Alarm Indication Alarm AIS is inserted downstream toward the
Indication Major 209 / Comm
Signal DS1E1_AIS_LIU downstream equipment to indicate that
Signal At On 6 Yes a failure exists upstream.
AIS LIU
2. If no E1/DS1 network/equipment
problem, check E1/DS1 provisioning
on the far-end for valid traffic path
configuration.

1. Determine whether problem is due


to E1/DS1 network/equipment problem
or misprovisioning. AIS represents a
failure upstream in the network where
Alarm Indication Alarm AIS is inserted downstream toward the
Indication Major 209 / Comm
Signal DS1E1_AIS_IWF downstream equipment to indicate that
Signal At On 15 Yes a failure exists upstream.
AIS IWF
2. If no E1/DS1 network/equipment
problem, check E1/DS1 provisioning
on the far-end for valid traffic path
configuration.

1. Determine whether problem is due


to physical interface cabling or due to
Alarm
actual failure of signal from far end
Synchronization Loss Of Major 210 / Comm
DS1E1_LOS_FAIL DS1 equipment.
Problem Signal On 4 Yes
2. If no physical cabling problem
ALRM
exists, check far-end DS1/E1 transmit
capabilities.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 11 sur 93

1. Determine whether problem is due


to E1/DS1 network/equipment
problem or misprovisioning. AIS
represents a failure upstream in the
Alarm Alarm network where AIS is inserted
Synchronization Indication Major 210 / Comm downstream toward the downstream
Problem DS1E1_AIS_SYNC equipment to indicate that a failure
Signal On On 5 Yes
ALRM Tributary exists upstream.
2. If no E1/DS1 network/equipment
problem, check E1/DS1 provisioning
on the far-end for valid traffic path
configuration.

1. Determine whether problem is due


to physical interface cabling,
misprovisioning, or signal from far
Alarm
end E1/DS1 equipment.
Synchronization Loss Of Major 210 / Comm
Problem DS1E1_LOF_SYNC 2. If no physical cabling problem
Frame On 6 Yes
exists, check for misprovisioning of
ALRM
framing format between equipment.
Also check far-end E1/DS1 transmit
capabilities.

1. Determine whether problem is due


to physical interface cabling or due to
Alarm actual failure of signal from far end
Synchronization Loss Of Major Comm E1/DS1 equipment.
210 /
Problem Signal At DS1E1_LOS_SYNC
On 7 Yes 2. If no physical cabling problem
Tributary
ALRM exists, check far-end E1/DS1 transmit
capabilities or verify the far-end
equipment is not out-of-service.

1. Determine whether there are


Cyclic
CRC 6 problems in the network that could
Redundancy Minor 209 / Comm
Alarm From DS1E1_CRC6_LIU cause bit-errors.
Check On 3 No
LIU 2. Verify if the far-end DS1 equipment
CRC
is using CRC-6 in the frame.

1. Determine whether there are


Cyclic
CRC 4 problems in the network (E1-side)
Redundancy Minor 209 / Comm
Alarm From DS1E1_CRC4_LIU that could cause bit-errors.
Check On 4 No
LIU 2. Verify if the far-end E1 equipment
CRC
is using CRC-4 in the frame.

1. Determine whether there are


Cyclic CRC 4 problems in the network (E1-side)
Redundancy Threshold Minor 209 / Comm
DS1E1_CRC4_TLIU that could cause bit-errors.
Check Alarm From On 5 No
LIU 2. Verify if the far-end E1 equipment
CRC
is using CRC-4 in the frame.

1. Determine whether there are


Cyclic
CRC 6 problems in the network (EMAN) that
Redundancy Minor 209 / Comm
Alarm From DS1E1_CRC6_IWF could cause bit-errors.
Check On 12 No
IWF 2. Verify if the far-end equipment is
CRC
using CRC-6in the frame.

1. Determine whether there are


Cyclic
CRC 4 problems in the network (EMAN) that
Redundancy Minor 209 / Comm
Alarm From DS1E1_CRC4_IWF could cause bit-errors.
Check On 13 No
IWF 2. Verify if the far-end equipment is
CRC
using CRC-4 in the frame.

1. Determine whether there are


Cyclic CRC 4 problems in the network (EMAN) that
Redundancy Threshold Minor 209 / Comm
DS1E1_CRC4_TIWF could cause bit-errors.
Check Alarm From On 14 No
IWF 2. Verify if the far-end equipment is
CRC
using CRC-4 in the frame.

1. Determine whether problem is due


to physical interface cabling,
misprovisioning, or signal from far
Loss Of end E1/DS1 equipment.
Loss Of Frame Major 209 / Comm
Frame At DS1E1_LOF_LIU 2. If no physical cabling problem
LOF On 8 Yes
LIU exists, check for misprovisioning of
framing format between equipment.
Also check far-end E1/DS1 transmit
capabilities.

Loss Of Frame Loss Of DS1E1_LOMF_LIU Major 209 / Comm 1. Determine whether problem is due
LOF Multi Frame On 9 Yes to physical interface cabling,
LIU misprovisioning, or signal from far
end E1/DS1 equipment.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 12 sur 93

2. If no physical cabling problem


exists, check for misprovisioning of
framing format between equipment.
Also check far-end E1/DS1 transmit
capabilities.

1. Determine the reason for packet-


loss on the CES pseudowire. Has
Loss Of there been an outage of a network
Loss Of Frame Major 209 / Comm
Frame At DS1E1_LOF_IWF element ?
LOF On 17 Yes
IWF 2. Verify if the far-end device (EMAN
side) is still operational and sending
CES frames.

1. Determine whether problem is due


to physical interface cabling,
misprovisioning, or signal from far
end E1/DS1 equipment (EMAN
Loss Of Frame Loss Of Major Comm side).
209 /
Multi Frame DS1E1_LOMF_IWF
LOF On 18 Yes 2. If no physical cabling problem
IWF
exists, check for misprovisioning of
framing format between equipment.
Also check far-end E1/DS1 transmit
capabilities.

1. Determine whether problem is due


to physical interface cabling or due
to actual failure of signal from far end
Loss Of Signal Loss Of Major Comm E1/DS1 equipment.
209 /
Signal At DS1E1_LOS_LIU
LOS On 7 Yes 2. If no physical cabling problem
LIU
exists, check far-end E1/DS1
transmit capabilities or verify the far-
end equipment is not out-of-service.

1. Determine whether problem is due


to physical interface cabling,
misprovisioning, or signal from far
Loss Of end DS1 equipment.
Loss Of Signal Major 209 / Comm
Signal At DS1E1_LOS_IWF 2. If no physical cabling problem
LOS On 16 Yes
IWF exists, check for misprovisioning of
framing format between equipment.
Also check far-end DS1 transmit
capabilities.

1. Determine whether problem is due


to physical interface cabling. REI is
the result of the far end E1/DS1
Remote Alarm Remote equipment detecting a problem with
Alarm Major 209 / Comm
Indication DS1E1_REI_LIU its receive signal and indicating a
Indication On 1 Yes remote alarm indication back.
RAI LIU
2. If no physical cabling problem
exists, check far-end E1/DS1
equipment for alarms and resolve.

1. Determine whether problem is due


to physical interface cabling. REI is
the result of the far end E1/DS1
Remote equipment (EMAN side) detecting a
Remote Alarm
Alarm Major 209 / Comm problem with its receive signal and
Indication DS1E1_REI_IWF
Indication On 10 Yes indicating a remote alarm indication
RAI IWF back.
2. If no physical cabling problem
exists, check far-end E1/DS1
equipment for alarms and resolve.

1. Determine whether problem is due


to physical interface cabling. RDI is
Remote the result of the far end E1/DS1
Remote Defect
Defect Major 209 / Comm equipment detecting a problem with
Indication DS1E1_RDI_LIU
Indication On 2 Yes its receive signal and indicating a
RDI LIU remote alarm indication back.
2. If no physical cabling problem
exists, check far

1. Determine whether problem is due


to physical interface cabling. RDI is
the result of the far end E1/DS1
Remote equipment (EMAN side) detecting a
Remote Defect
Defect Major 209 / Comm problem with its receive signal and
Indication DS1E1_RDI_IWF
Indication On 11 Yes indicating a remote alarm indication
RDI IWF back.
2. If no physical cabling problem
exists, check far-end E1/DS1
equipment for alarms and resolve.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 13 sur 93

Degraded Signal Degraded DS1E1_DEG_FAIL Major 210 / Comm 1. Check clock source configuration
SIGN Signal On 8 Yes and determine whether problem is
due to physical interface cabling or
due to actual failure of signal from
far end DS1/E1 equipment or due to
a failure in the signal from a PRC
traceable clock.

Table 118-12 describes the EPON alarms.

Table 118-12 EPON alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

Bias Problem Transmit Bias Too Major 195 / Eqt Check the transmitted bias
TXBIASHIALM
BIPR High Alarm On 3 Yes and decrease Bias

Bias Problem Transmit Bias Too Major 195 / Eqt Check the transmitted bias
TXBIASLOALM
BIPR Low Alarm On 4 Yes and increase Bias

Bias Problem Transmit Bias Too Warning 195 / Eqt Check the transmitted bias
TXBIASHIWARN
BIPR High Warning On 11 No and decrease Bias

Bias Problem Transmit Bias Too Warning 195 / Eqt Check the transmitted bias
TXBIASLOWARN
BIPR Low Warning On 12 No and increase Bias

Bias Problem XFP Transmit Bias Major 195 / Eqt Check 10G XFP transmitted
EXTTXBIASHIALM
BIPR Too High Alarm On 19 Yes bias and decrease Bias

Bias Problem XFP Transmit Bias Major 195 / Eqt Check 10G XFP transmitted
EXTTXBIASLOALM
BIPR Too Low Alarm On 20 Yes bias and increase Bias

Bias Problem XFP Transmit Bias Warning 195 / Eqt Check 10G XFP transmitted
EXTTXBIASHIWARN
BIPR Too High Warning On 23 No bias and decrease Bias

Bias Problem XFP Transmit Bias Warning 195 / Eqt Check 10G XFP transmitted
EXTTXBIASLOWARN
BIPR Too Low Warning On 24 No bias and increase Bias

Configuration Or No repair necessary.


Customization Minor Eqt Indication to operator that
New ONT 158 /
Error NEWEONT further provisioning should
Discovered On 1 No commence. Newly installed
CFG ONT MDU on PON.

Configuration Or
Customization Optical Module Major 158 / Eqt Check the actual optical
Error OPMODULEMISMACH
Mismatch On 8 Yes module
CFG

Communications
Rogue ONT Major 158 / Comm Check if rogue ONU exist or
Subsystem Failure ROGUEONT
Disabled On 7 Yes not
COM

Error Bit Rate High Major 158 / Comm Check the fiber or PON
Error Bit Rate High ERRBITRATEHI
EBRH On 3 Yes interface.

1. Check the receive PON


Loss Of Signal PON Loss Of Major 158 / Comm fiber input at the OLT.
EPONLOS
LOS Signal On 2 Yes 2. Check if the ONT power
is on or off.

Power Problem Idle Power Too Major 158 / Comm Check the idle power of the
IDLERXPWHI
PWR High On 5 Yes PON

Transmitted
Power Problem Major Comm Check the transmitted
Optical Signal 195 /
TXPWHIALM power and decrease signal
PWR Above Alarm On 1 Yes level
Threshold

Transmitted
Power Problem Major Comm Check the transmitted
Optical Signal 195 /
TXPWLOALM power and increase signal
PWR Below Alarm On 2 Yes level
Threshold

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 14 sur 93

Power Problem Transmitted TXPWHIWARN Warning 195 / Comm Check the transmitted
PWR Optical Signal On 9 No power and decrease signal
Above Warning level
Threshold

Transmitted
Power Problem Warning Comm Check the transmitted
Optical Signal 195 /
TXPWLOWARN power and increase signal
PWR Below Warning On 10 No level
Threshold

Power Problem XFP Transmit Major Comm Check 10G XFP


195 /
Optical Signal Too EXTTXPWHIALM transmitted power and
PWR On 17 Yes
High Alarm decrease signal level

Power Problem XFP Transmit Major Comm Check 10G XFP


195 /
Optical Signal Too EXTTXPWLOALM transmitted power and
PWR On 18 Yes
Low Alarm increase signal level

Power Problem XFP Transmit Warning Comm Check 10G XFP


195 /
Optical Signal Too EXTTXPWHIWARN transmitted power and
PWR On 21 No
High Warning decrease signal level

Power Problem XFP Transmit Warning Comm Check 10G XFP


195 /
Optical Signal Too EXTTXPWLOWARN transmitted power and
PWR On 22 No
Low Warning increase signal level

Temperature
Temperature Too Major 195 / Eqt Check temperature and
Unacceptable TEMPEHIALM
High Alarm On 7 Yes decrease temperature
TEMP

Temperature
Temperature Too Major 195 / Eqt Check temperature and
Unacceptable TEMPELOALM
Low Alarm On 8 Yes increase temperature
TEMP

Temperature
Temperature Too Warning 195 / Eqt Check temperature and
Unacceptable TEMPEHIWARN
High Warning On 15 No decrease temperature
TEMP

Temperature
Temperature Too Warning 195 / Eqt Check temperature and
Unacceptable TEMPELOWARN
Low Warning On 16 No increase temperature
TEMP

Test Problem Rogue Test Major 158 / Eqt Check if rogue ONU test
PONROGUETEST
TEST Ongoing On 6 Yes ongoing

Voltage Problem Voltage Too High Major 195 / Eqt Check voltage and
VOLHIALM
VTP Alarm On 5 Yes decrease voltage

Voltage Problem Voltage Too Low Major 195 / Eqt Check voltage and increase
VOLLOALM
VTP Alarm On 6 Yes voltage

Voltage Problem Voltage Too High Warning 195 / Eqt Check voltage and
VOLHIWARN
VTP Warning On 13 No decrease voltage

Voltage Problem Voltage Too Low Warning 195 / Eqt Check voltage and increase
VOLLOWARN
VTP Warning On 14 No voltage

Table 118-13 describes the EPONONT alarms.

Table 118-13 EPONONT alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

Critical Event Receive Critical Major 156 / Comm


Indication Event Indication CREVT Check the ONT.
On 3 Yes
CEI From ONT

Configuration Or
Customization Minor Eqt Determine why the ONU
ONU Provisioning 184 /
Error PROVFAIL rejected the provisioning
Failure On 15 Yes request.
CFG

Configuration Or Capability Mismatch LLIDCAPMISMATCH Minor 184 / Eqt Check ONT capability and
Customization On 16 Yes whether support multiple LLID.
Error

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 15 sur 93

CFG

Configuration Or
Customization Minor Eqt Determine why the pre-
Software Version 185 /
Error SWVERMM configured ONU software type
Mismatch On 1 No does not match the actual ONU.
CFG

Determine why the configured


Configuration Or software download mode does
Customization Minor Eqt not match the actual ONU
Software Download 185 /
Error SWDLMM supported download mode, for
Mode Mismatch On 2 No example: operator configures
CFG CTC 2.1 mode to a CTC 2.0
ONU.

Configuration Or
Customization Minor Eqt Determine why no matched
Software Version 185 /
Error SWVERNF version is found in the ONU
Not Found On 3 No software mapping table.
CFG

Configuration Or The software version


Customization Software Download Minor 185 / Eqt downloading to the ONU is in
Error SWDLIP
In Progress On 5 No progress. This message is for
CFG information purposes only.

Configuration Or
Customization Minor Eqt Determine why there is a failure
Software Download 185 /
Error SWDLFAIL to download a software version
Failure On 6 No to the ONU.
CFG

Dying Gasp Received Dying Restore power to the ONT. The


Minor 156 / Comm
Indication Gasp Indication EDG dying gasp indication is due to
On 2 Yes
DGI From ONT loss of power input to the ONT.

Loss Of Link Major 156 / Comm


Link Fault At ONT LINKFAULT Check the link.
LOL On 1 Yes

Loss Of Power Minor 184 / Eqt Determine why the ONU power
ONU Power Broken POWERBROKEN
LOPW On 5 Yes is broken.

Loss Of Power ONU Power Too Minor 184 / Eqt Determine why the ONU power
POWERHIGH
LOPW High On 6 Yes is too high.

Loss Of Power ONU Power Too Minor 184 / Eqt Determine why the ONU power
POWERLOW
LOPW Low On 7 Yes is too low.

OAM Failure Loss Of Major 156 / Comm Check the OAM version for the
OAMFAIL
OAMFL Communications On 4 Yes OLT and ONT.

ONU Equipment
Minor 184 / Eqt Determine why the ONU reset
Alarm Reset Failure RESETFAIL
On 1 Yes failed.
OEA

ONU Self Test Minor 184 / Eqt Determine why the ONU switch
ONU Switch Failure SWITCHFAIL
OST On 2 Yes selftest failed.

ONU Self Test ONU VoIP HW Minor 184 / Eqt Determine why the ONU VoIP
VOIPHWFAIL
OST Failure On 3 Yes hardware selftest failed.

ONU Self Test Minor 184 / Eqt Determine why the ONU E1
ONU E1 HW Failure E1HWFAIL
OST On 4 Yes hardware selftest failed.

Determine why the ONU


PON IF Switch ONU Switch PON Minor 184 / Eqt detected a PON link failure, or
PONIFSW
PIS Interface On 14 No received an Active PON_IF
Adminstate message.

Physical
Detection Such As Warning 184 / Eqt Check if the ONT door or box is
Intrusion INTRUDER
Door Or Box Open On 11 No open.
PSI

Power Problem Received Optical Major Comm Check the received optical
157 /
Signal Above Alarm RXPWHI signal and decrease the signal
PWR On 1 Yes
Threshold level.

Power Problem Received Optical Major Comm Check the received optical
157 /
Signal Below Alarm RXPWLO signal and increase the signal
PWR On 2 Yes
Threshold level.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 16 sur 93

Power Problem Transmitted Optical TXPWHI Major 157 / Comm Check the transmitted power
PWR Signal Above Alarm On 3 Yes and decrease the signal level.
Threshold

Power Problem Transmitted Optical Major Comm


157 / Check the transmitted power
Signal Below Alarm TXPWLO
PWR On 4 Yes and increase the signal level.
Threshold

Power Problem Received Optical Warning Comm


157 / Check the received power and
Signal Above RXPWHIWARN
PWR On 11 No decrease the power.
Warning Threshold

Power Problem Received Optical Warning Comm


157 / Check the received power and
Signal Below RXPWLOWARN
PWR On 12 No decrease the power.
Warning Threshold

Power Problem Transmitted Optical Warning Comm


157 / Check the transmitted power
Signal Above TXPWHIWARN
PWR On 13 No and decrease the power.
Warning Threshold

Power Problem Transmitted Optical Warning Comm


157 / Check the transmitted power
Signal Below TXPWLOWARN
PWR On 14 No and increase the power.
Warning Threshold

Power Problem Minor Eqt Determine why the ONU


184 /
Battery Missing BATTMISS battery is provisioned but
PWR On 8 No missing.

Power Problem Minor Eqt Determine why the ONU


184 /
Battery Failure BATTFAIL battery is provisioned and
PWR On 9 No present but cannot recharge.

Determine why the ONU


Power Problem Minor 184 / Eqt battery is provisioned and
Battery Low BATTLOW
PWR On 10 No present but its voltage is too
low.

Software
Download Minor Eqt Determine why the system
Software Download 185 /
Failure SWDLFM cannot find the software
File Missing On 4 No version file the NT flush.
SWDL

Software Determine why there is a


Download Software Download Minor 185 / Eqt failure to active a software
Failure SWACTFAIL
Active Failure On 7 Yes version that has been
SWDL downloaded to the ONU.

Software Determine why there is a


Download Software Download Minor 185 / Eqt failure to commit a software
Failure SWCMTFAIL
Commit Failure On 8 Yes version that has been
SWDL downloaded to the ONU.

Temperature
Temperature Too Major 157 / Eqt Check and decrease the
Unacceptable TEMPEHI
High Alarm On 9 Yes temperature.
TEMP

Temperature
Temperature Too Major 157 / Eqt Check and increase the
Unacceptable TEMPLO
Low Alarm On 10 Yes temperature.
TEMP

Temperature
Temperature Too Warning 157 / Eqt Check and decrease the
Unacceptable TEMPEHIWARN
High Warning On 19 No temperature.
TEMP

Temperature
Temperature Too Warning 157 / Eqt Check and increase the
Unacceptable TEMPELOWARN
Low Warning On 20 No temperature.
TEMP

Temperature Determine why the ONU


ONU High Minor Eqt
Unacceptable 184 / internal temperature exceeds
Temperature HITEMPWARN
On 12 No the high temperature alarm
TEMP Warning
warning.

Temperature Determine why the ONU


ONU Low Minor Eqt
Unacceptable 184 / internal temperature is below
Temperature LOTEMPWARN
On 13 No the low temperature alarm
TEMP Warning
warning.

Transmission Transmit Bias Too TXBIASHI Major 157 / Eqt Check and decrease the
Problem High Alarm On 5 Yes transmit bias.
TMP

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 17 sur 93

Transmission
Transmit Bias Too Major 157 / Eqt Check and increase the
Problem TXBIASLO
Low Alarm On 6 Yes transmit bias.
TMP

Transmission
Transmit Bias Too Warning 157 / Eqt Check and decrease the
Problem TXBIASHIWARN
High Warning On 15 No transmit bias.
TMP

Transmission
Transmit Bias Too Warning 157 / Eqt Check and increase the
Problem TXBIASLOWARN
Low Warning On 16 No transmit bias.
TMP

Voltage
Voltage Too High Major 157 / Eqt
Problem VOLHI Check and decrease voltage.
Alarm On 7 Yes
VTP

Voltage
Voltage Too Low Major 157 / Eqt
Problem VOLLO Check and increase voltage.
Alarm On 8 Yes
VTP

Voltage
Voltage Too High Warning 157 / Eqt
Problem VOLHIWARN Check and decrease voltage.
Warning On 17 No
VTP

Voltage
Voltage Too Low Warning 157 / Eqt
Problem VOLLOWARN Check and increase voltage.
Warning On 18 No
VTP

Voice Problem Voice Gateway Minor Comm Determine why


182 /
Communication VGATEWAYCOMM communication with the
VX On 1 Yes
Failure softswitch has failed.

Voice Problem Voice DHCP Server Minor 182 / Comm Check why the AG cannot get
VDHCPERR
VX Error On 2 Yes IP address from DHCP server.

Table 118-14 describes the EPONONT-ETHPORT alarms.

Table 118-14 EPONONT-ETHPORT alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

Auto Determine why the port auto negotiation


Negotiation Auto Major Eqt failed at uniport at ONT side, for example:
Failure Negotiation PORTNEGFAIL 159 / 2
On Yes ONT support port mode mismatch with
Failure
ANF peer side.

Congestion Port Major Eqt Determine why there is port congestion at


PORTCONG 159 / 5
CONG Congestion On Yes uniport at the ONT side.

Loss Of Signal Minor Eqt Determine why there is port loss of signal
Loss Of Signal PORTLOS 159 / 3 at uniport at ONT side, for example:
LOS On Yes Ethernet cable is not connected.

Port Failure Major Eqt Determine why there is a port failure at


Port Failure PORTFAIL 159 / 4 uniport at ONT side, for example:
PF On Yes hardware failure for special port.

Port Loop Major Eqt Determine why there is a port loop at


Port Loop PORTLOOP 159 / 1
PL On Yes uniport at ONT side.

Table 118-15 describes the EPONONT-POTSPORT alarms.

Table 118-15 EPONONT-POTSPORT alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

Port Failure Over Temperature PORTOVERTEMP Minor 183 / 1 Eqt Determine why the ONU POTS
PF On Yes port temperature too high.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 18 sur 93

Port Failure Minor Eqt Determine why there is over


Over Current PORTOVERCUR 183 / 2
PF On Yes current on the ONU POTS port.

Port Failure Minor Eqt Determine why the ONU POTS


Grounded PORTGROUNDED 183 / 3
PF On Yes port is grounded.

Unknown
Megaco Minor Comm Determine why the subscriber
Unknown Megaco
Subscriber UNKMEGASUB 183 / 4 has not been configured on the
Subscriber On Yes softswitch.
UMS

Table 118-16 describes the Ethernet alarms.

Table 118-16 Ethernet alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

Address No special repair action. The


MAC Address Minor Comm
Conflict BRGMACCONFLICT 109 / 1 conflicted port can be manually
Conflict On No
ADDR closed or opened, if needed.

Threshold Excessive LOS Minor Qos 1. Check the physical line.


Crossed Errors In 15 ETHLOS15 107 / 1
Minutes Interval On No 2. Check the modem equipment.
TCA

Threshold Excessive FCS Minor Qos 1. Check the physical line.


Crossed Errors In 15 ETHFCS15 107 / 2
Minutes Interval On No 2. Check the modem equipment.
TCA

Threshold Excessive LOS Minor Qos 1. Check the physical line.


Crossed Errors In 1 Day ETHLOSDAY 107 / 3
Interval On No 2. Check the modem equipment.
TCA

Threshold Excessive FCS Minor Qos 1. Check the physical line.


Crossed Errors In 1 Day ETHFCSDAY 107 / 4
Interval On No 2. Check the modem equipment.
TCA

Threshold Excessive Received Minor Qos


Crossed Octets In 15 ETHRXB15 107 / 5 Add extra lines in the LAG.
Minutes Interval On No
TCA

Threshold Excessive
Transmitted Octets Minor Qos
Crossed ETHTXB15 107 / 6 Add extra lines in the LAG.
In 15 Minutes On No
TCA Interval

Threshold Excessive Received Minor Qos


Crossed Octets In 1 Day ETHRXBDAY 107 / 7 Add extra lines in the LAG.
Interval On No
TCA

Threshold Excessive Minor Qos


Crossed Transmitted Octets ETHTXBDAY 107 / 8 Add extra lines in the LAG.
In 1 Day Interval On No
TCA

Virtual MAC Disable the vmac-translation


Allocation Virtual MAC Minor Comm functions for the l2 forwarder id
Failed BRGVMACFULL 109 / 2
Address Full On No which is attached to the vlanport
VMACF on top of this bridge port.

Table 118-17 describes the FTP alarms.

Table 118-17 FTP alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

File Transfer File Server FTPSRVUNAVAIL Major 105 / 1 Comm 1. Determine whether the file
Problem Unreachable On No transfer server has been correctly
FTP configured.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 19 sur 93

2. Check the network to the file


transfer server.

Table 118-18 describes the HUB alarms.

Table 118-18 HUB alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

Disable the responsible user-


side ports involved in the
Duplicate MAC alarm.
Use IACM Forwarding Data
Base to identify responsible
Address Conflict MAC Address Minor 146 / Comm
VPLSDUPADDR user-side ports.
ADDR Conflict On 2 Yes
Re-enable port when alarm is
cleared after a timeout.
Try to identify the source of
DOS attack, and remove from
the network.

Disable the responsible user-


side ports involved in the
Duplicate MAC alarm in this
network element or in the
surrounding network elements.
Use IACM Forwarding Data
Address Conflict Self MAC Minor Comm
146 / Base of these network
Address DUPADDRSELFSAP
ADDR On 4 Yes elements to identify
Conflict
responsible user-side ports.
Re-enable port when alarm is
cleared after a timeout. Try to
identify the source of DOS
attack, and remove from the
network.

Disable responsible user-side


ports involved in the Duplicate
MAC alarm in this network
element or in the surrounding
network elements.
SDP Binding Use IACM Forwarding Data
Address Conflict Self MAC Minor 146 / Comm Base of these network
DUPADDRSELFSDP elements to identify
ADDR Address On 5 Yes
Conflict responsible user-side ports.
Re-enable port when alarm is
cleared after a timeout.
Try to identify the source of
DOS attack, and remove from
the network.

In case the duplicate IPv6


address alarm occurs for:
- the LL address: shutdown
the interface in order to trigger
Address Conflict IPv6 Local Major Comm the System to initiate the DAD
178 /
Address IPv6DADOWN procedure once more [and
ADDR On 1 Yes
Conflict hope for successful outcome].
- a configured IPv6 address:
operator can choose a
different IPv6 address for the
interface.

Address Conflict IPv6 Address IPv6DAD Minor 178 / Comm In case the duplicate IPv6
ADDR Conflict On 2 No address alarm occurs for:
- If duplicate address is a link
local address and also a
duplicate MAC alarm is raised:
same MAC is used at 2 ends.
- If the duplicate address is a
global address assigned using
a DHCP address, verify the
configuration at the DHCP
server.
1. If the duplicate address is
an address configured by
operator and announced to
the user via router
advertisement, verify the

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 20 sur 93

configuration of the
addresses for node and
user.\2. If the duplicate
address is an address that is
already allocated to another
user (case of local proxy ND),
the operator should verify the
configuration of the
addresses for the users.

Check for MEPS in MA the


Ethernet CFM CCIEnabled flag.
RDI CCM Minor 212 / Comm
CCM Defect ETHCFM_DEFRDICCM Check operational status of
Defect On 1 Yes
CCM links needed for the CCM
transmission towards peer.

Ethernet CFM Remote MEP found in


MAC Status Minor 212 / Comm dot1agCfmMepDbTable,
CCM Defect ETHCFM_DEFMACSTATUS
CCM Defect On 2 Yes check operational status of
CCM physical links on that MEP.

Restore CCM
misconfigurations (peer MEP
Ethernet CFM
Remote CCM Major 212 / Comm list), device failures, link
CCM Defect ETHCFM_DEFREMOTECCM
Defect On 3 Yes failures.
CCM
Check for admin status of the
CCM from peer MEP.

Check MA configuration: peer


Ethernet CFM MEP list, MEPIDs, CCM
Error CCM Major 212 / Comm
CCM Defect ETHCFM_DEFERRORCCM interval etc to see if there is
Defect On 4 Yes
CCM any mis-configuration or mis-
match between MEP peers.

Ethernet CFM
xCon CCM Major 212 / Comm Check MAID configuration.
CCM Defect ETHCFM_DEFXCONCCM
Defect On 5 Yes Check service configuration.
CCM

Indicates SFP or SFP+ type


does not match the planned
speed and/or auto-
negotiation for the port.
Configuration Or Either reconfigure the
Customization Configuration Major 150 / Comm planned speed and/or the
Error PORTCONFMM
Mismatch On 3 Yes auto-negotiation to match the
CFG current speed and auto-
negotiation, or reconfigure
external device to match
current configured speed and
auto-negotiation.

Check if the port or lag on


which the path is configured
is operational down or if the
corresponding path-mep has
Communications
encountered a ccm-failure.
Subsystem Ethernet Path Minor 222 / Comm
Failure ETHRINGPATHBLOCK If the port / lag is oper-up and
Is Blocked On 1 No
there is no ccm failure for the
COM
path-mep,then the Eth-Ring-
Path is blocked due to normal
protocol functionality,in this
case no action is required.

Check for possible network,


equipment, and facility alarms
SHUB / IHUB and clear.
CPU Minor 151 / Eqt
Malfunction IHUBPROCROVLD
Overload On 9 No If problem persists, reset NT
HUB card.
Replace NT card.

Try reset of NT to clean up


SHUB / IHUB memory depletion.
Out Of Critical 151 / Eqt
Malfunction IHUBOUTOFMEM If fault persists, contact your
Memory Error On 10 Yes
HUB Alcatel-Lucent technical
support representative.

Link Aggregation Port LAGPORTADDFAIL Minor 150 / Comm Retrieve the additional info of
Failure Aggregation On 2 Yes the alarm to see the failure
LAG Failure reason string and correct.
Possible reasons are:
1. Administrative key
mismatch.
2. System ID mismatch.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 21 sur 93

3. LACP passive both ends.


4. Link down - Check the
links.
5. Unknown - contact your
Alcatel-Lucent technical
support representative.

LI Malfunction Traffic LI Minor 179 / Comm


LITRAFDISABLED Enable traffic interception.
LI Disabled On 1 Yes

Loss Of Link Ethernet Link Critical 150 / Comm Check the physical Ethernet
LINKDOWN
LOL Down On 1 Yes link.

Check the physical Ethernet


Loss Of Link Ethernet LAG Major 152 / Comm links associated for LAG
LAGDOWN
LOL Down On 1 Yes negotiation or timeout
problems.

The alarm can be raised as


a result of a recent
configuration change.
If this is the case, check the
most recent new
configuration for:
a) IP Interface
If there is no shutdown but
the interface is operationally
down, check for an
underlying failure.
If none, set the interface to
down, clear the alarm, then
set the interface to up.
Check the alarm again. If the
alarm is present:
i) Set the interface to down
and try back later.
ii) Remove static MAC
addresses.
Out Of Resource Major Comm iii) Reduce the number of
Switch Out Of 153 /
SWITCHOOR subnets.
OOR Resource On 2 No
iv) Clear IPv6 neighbor
cache entries.
b) Static-MAC
i) Remove Static-MAC.
ii) Manually clear the alarm.
iii) Add Static-MAC back.\iv)
nCheck for the alarm again.
If present, remove other
static MACs.
c) Static IP multicast group
i) Remove the static group.
ii) Manually clear the alarm.
iii) Add the static group back.
iv) Check for the alarm
again.
If present, reduce the size of
various subnets.
If no recent configuration
change was done, check the
current network topology.

System is almost used


above capacity, it cannot
Maximum
store that many DHCP
Out Of Resource Number Of Major Comm
153 / sessions in the system.
DHCP Relay DHCPSESSIONOOR
OOR On 4 Yes Consider reducing DHCP
Sessions
lease time or reducing the
Reached
allowed DHCP sessions for
that ISAM in DHCP server.

Out Of Resource LI Out Of LIOOR Major 179 / Comm Lower the number of targets
OOR Resource On 3 Yes to be intercepted
Decrement the number of
used resources by
-removing or simplifying
filters attached to a target
-making the target key more
specific (for example, use
circuit-id , specify VRF) so
fewer DHCP sessions (IP

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 22 sur 93

addresses ) to be
intercepted.

BFD 1. Delete a BFD session.


Out Of Resource Maximum Major 197 / Comm 2. Increase the
BFDMAXRESOURCE
OOR Resource On 2 Yes receive/transmit interval in
Reached interface BFD configuration.

1. When the operator


succeeds in configuring the
BFD Session by deleting
few BFD Sessions or by
manipulating transmitting /
Out Of Resource BFD Session Major 197 / Comm
BFDSTALEENTRY receiving rates and then
OOR Stale Entry On 3 Yes recreating the failed
session.
2.Removing the session
configuration for which this
alarm is raised.

Check the administrative


state of all IS-IS
components, for example,
interfaces and instance
should be unlocked.
Check operational state of
Routing Failure IS-IS Minor Comm any interfaces needed for
141 /
Adjacency ADJACENCYDOWN peer connections.
ROUT On 1 No
Down If administrative and
operational states are up,
check the IS-IS
configuration, for example,
verify that the autonomous
system IDs of peers are
correct.

Routing Failure IS-IS Minor Comm


141 / Check the IS-IS level-
Adjacency ADJACENCYREJECT
ROUT On 2 No capability configuration.
Rejected

Routing Failure IS-IS Critical Comm


141 / Check the IS-IS
Instance ISISDOWN
ROUT On 3 Yes configuration.
Down

Check the status of peer


nodes, if they belong to the
same operator domain.
Routing Failure OSPF Minor Comm
144 / Then take corrective
Neighbor NEIGHBORDOWN
ROUT On 3 No actions on peer node.
Down
Change the network
topology if the peer nodes
cannot be corrected.

Routing Failure OSPF Critical Comm


144 / Check the OSPF
Instance OSPFDOWN
ROUT On 4 Yes configuration.
Down

Check the status of peer


nodes, if they belong to
same operator domain.
Then take corrective
actions on the peer node.
Routing Failure OSPFv3 Minor Comm Change the network
144 /
Neighbor V3NEIGHBORDOWN topology if the peer nodes
ROUT On 7 No
Down cannot be corrected.
Check OSPFv3
configurations to see if
there is any mismatch (for
example, a type, id, link
type, or timer intervals).

Routing Failure OSPFv3 Critical Comm


144 / Check the OSPFv3
Instance V3OSPFDOWN
ROUT On 8 Yes configuration.
Down

Routing Failure RIP Instance RIPDOWN Critical 145 / Comm 1. Verify the RIP interface
ROUT Down On 1 Yes configurations.
2. Check the memory
consumed by the RIP
protocol.
3. Check the number of
routes learned through RIP.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 23 sur 93

Note: The RIP protocol


instance attempts to restart
within 30 seconds.

Routing Failure Critical Comm Verify the LDP status for


LDP Instance 170 /
LDPDOWN base router and restart
ROUT Down On 1 Yes LDP.

Verify peer router up.


Verify that the correct far-
end IP address is
configured.
Routing Failure LDP Session Critical 170 / Comm Verify that the LDP
LDPSESSIONDOWN
ROUT Down On 2 Yes interfaces are up.
Verify that the system IP is
configured.
Verify the configured
authentication parameters.

Routing Failure MPLS Critical Comm Verify MPLS status for


171 /
Instance MPLSDOWN base router and restart
ROUT On 1 Yes
Down MPLS.

Routing Failure Critical 171 / Comm Verify next-hop IP address


LSP Down LSPDOWN
ROUT On 2 Yes by pinging it.

Check if the corresponding


LSP is up.
If yes, check how the path
is associated to the lsp. i.e
primary path /secondary
path in standby/secondary
path in non-standby.
Routing Failure LSP Path Minor 171 / Comm ((It is expected that the
LSPPATHDOWN path configured as
ROUT Down On 3 Yes
secondary in non-standby
mode to have oper down
(while lsp is up), until lsp
switches to that secondary
path).
Check if the HOPs in the
path are reachable (via
ping).

Verify what the reason is to


be operational down, use
the given index to read
sdpBindOperStatus of
SDPbind table
- TLPD parameters
mismatch: VC-TYPE ,
Routing Failure Critical 172 / Comm MTU ?
SDP Down SDPDOWN
ROUT On 1 Yes - Associated service
operational down ?
- Associated SDP
operational down
No configuration at the
peer for this VC-id, so no
egress label received.

Verify whether the


configured far-end router is
alive by pinging the
configured-far end IP
address.
Routing Failure SDP Binding Critical 172 / Comm Verify own status of LDP
SDPBINDDOWN and MPLS.
ROUT Down On 2 Yes
Verify the LDP session and
adjacency status.
Verify the path towards the
far end is IP accessible
using the network ports.

1. Verify the status of the


attached SAP and the SDP
Routing Failure Critical 173 / Comm binding.
EPIPE Down EPIPEDOWN
ROUT On 1 Yes 2. Verify that the remote
peer has been correctly
configured or is still up.

Routing Failure PIM NEIGHBORDOWN Minor 176 / Comm Check status of peer
ROUT Adjacency On 1 No nodes, if belonging to
Down same operator domain.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 24 sur 93

Then do corrective
actions on peer node.
Change network topology
if peer nodes cannot be
corrected. Check PIM
configurations to see if
there is any mismatch.

Check the admin status of


all BGP components, for
example, interfaces,
group, and neighbor
should have a 'no
shutdown' status.
Check the operational
status of any interfaces
needed for peer
connections.
Routing Failure BGP Peer Critical 177 / Comm If admin and operational
PEERDOWN
ROUT Down On 1 Yes states are up, check the
BGP for misconfiguration,
for example, verify that
the autonomous system
IDs of peers are correct.
Check the BGP prefix
limit if memory resources
are available. If memory
is not available, modify
policies to reduce BGP
route importation.

1. Bring the BFD session


UP.
2. Delete the BFD session
by disabling 'bfd-enable'
on the routing protocol(s).
3. Remove the session by
disabling BFD on the
interface using 'no bfd'.
Routing Failure BFD Session Major 197 / Comm 4. Shutdown the interface
BFDSESSIONDOWN
ROUT Down On 1 Yes on which BFD is enabled.
5. Remove all the
associated protocols on
which BFD is enabled
corresponding to that
interface.
6. Shutdown the protocol
(s) for which BFD is
enabled.

Check the peer


configuration &
Routing Failure RSVP Minor Comm operational status.
216 /
Neighbor NEIGHBORDOWN
ROUT On 1 No Check if the peer is part
Down
of lsp path (which is
active)

Check MPLS admin


status.
Routing Failure RSVP Critical Comm
216 / Check RSVP/MPLS
Instance RSVPDOWN
ROUT On 2 Yes configuration.
Down
Check memory usage for
RSVP/MPLS

Redimensioning of the
Storage network is required. In
Capacity Max Number Major Comm
143 / case of wholesale,
Problem Of Routes MAXIPROUTES
On 1 Yes administrative actions
Reached
SCP with the customer of the
VPRN is required.

Redimensioning of the
Storage Maximum network is required. In
Capacity Number Of Major 143 / Comm case of wholesale,
Problem MAXIPv6ROUTES
IPv6 Routes On 2 Yes administrative actions
SCP Reached with the customer of the
VPRN is required.

Storage Maximum MAXDHCPV6LEASES Major 143 / Comm The operator can reduce
Capacity Number Of On 3 Yes the filling of the lease
Problem DHCPv6 database in either way:
SCP Leases - trigger clearing (specific
Reached entries or all) of the lease

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 25 sur 93

database for this


interface,
- disable dhcpv6 on the
interface
- disable Ipv6 on the
interface.
Alternatively, increases
the max number of
leases such that the
filling level drops below
the fixed threshold.
Note: shutting down the
VPRN service or the IP
interface leaves the
lease database
untouched.

The operator can reduce


the filling of the lease
database in either way:
- trigger clearing (specific
entries or all) of the lease
Storage Maximum database for this
Capacity Number Of Major Comm interface,
143 /
Problem DHCPv4 MAXDHCPV4LEASES
On 4 Yes - disable dhcpv4 on the
Leases
SCP Reached interface
Note: shutting down the
VPRN/IES service or the
IP interface does leave
the lease database
untouched.

Storage
Capacity OSPF Major Comm
144 / Redimensioning of the
Problem Overflow On MAXLIMLSDB
On 1 Yes network is required.
LSDB
SCP

Storage OSPF
Capacity Approaching Minor 144 / Comm Redimensioning of the
Problem MIDLIMLSDB
Overflow On On 2 No network is required.
SCP LSDB

Storage
Capacity OSPFv3 Major Comm
144 / Redimensioning of the
Problem Overflow On V3MAXLIMLSDB
On 5 Yes network is required.
LSDB
SCP

Storage OSPFv3
Capacity Approaching Minor 144 / Comm Redimensioning of the
Problem V3MIDLIMLSDB
Overflow On On 6 No network is required.
SCP LSDB

Redimensioning of the
Storage Multicast node required. In case of
Capacity Forwarding Minor 146 / Comm wholesale, administrative
Problem MAXLIMFIBTABLE
Database On 1 No actions with the
SCP Full customer of the VPLS
required.

Storage MAC MAXLIMFWDMAC Major 146 / Comm A condition meaning the


Capacity Address On 3 Yes number of MAC
Problem Forwarding addresses being learned
SCP Database for a vVPLS service
Full instance is nearing or
has exceeded a
configured table size
limit.
Possible reason for the
alarm:
Too many subscriber
MACs for the configured
service.
Possible solutions:
a) Increase the v-VPLS
FDB Table size.
b) Check the gateway of
the subscriber to see if it
is in bridge mode when it
should be in router
mode.
c) Check the port of the
subscriber to see if too
many MACs are being

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 26 sur 93

learned, and if so put


learning limit on that
subscriber port (if
feature supported).
d) Check the
aggregation network
that connects multiple
access nodes together
is operating in split
horizon L2 forwarding. If
not, the access node
may also be learning
subscriber MACs from
another access node.
e) If subtending off of a
hub access node, make
sure the port of the hub
node that is connected
to the subtended access
node is configured as
residential. If not, the
subtended access node
may also be learning
subscriber MACs from
the hub access node.

The number of ARP


entries in the ARP
cache of the system has
exceeded its resource
limits.
Possible reason for the
alarm:
Too many subscriber
host devices are using
L3 services on the NT.
Possible solutions:
a) Check and reduce
Storage the number of directly
Capacity ARP Table Major 153 / Comm attached hosts to local
Problem MAXARPUPTH subnets in the instance.
Full On 1 No
SCP b) Check the residential
gateway of the
subscriber to see if it is
in bridge mode when it
should be in router
mode.
c) Check the port of the
subscriber to see if too
many MACs are being
learned, and if so put
learning limit on that
subscriber port and
enable anti-spoofing (if
it is supported).

The number of NC
entries (IPv6) in the
system neighbor cache
is about to exceed its
resource limits.
- Possible reasons:
1) Too many subscriber
host devices are using
L3 services on the NT.
- Possible solutions:
1) Check and reduce
the number of directly
Storage attached hosts to local
Capacity IPv6 Major Comm
153 / subnets in the instance.
Problem Neighbor IPV6NEIGHCACHEUPTH
On 3 No
Cache Full 2) Check the subscriber
SCP residential gateway to
see if it is in bridge
mode when it should be
in router mode.
3) Check the subscriber
port to see if too many
MACs are being
learned, and if so put
learning limit on that
subscriber port and
enable anti-spoofing (if
the feature is
supported).

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 27 sur 93

Storage L2 FDB MACLIMNODE Major 153 / Comm The alarm informs about
Capacity Table Full On 5 No the fact that the amount
Problem of MAC addresses
SCP being learned for all
layer 2 services is
nearing the node limit.
- Possible Solutions:
1) Check the subscriber
gateway to see if it is in
bridge mode when it
should be in router
mode,
2) Check the subscriber
port to see if too many
MACs are being
learned, and if so, put a
learning limit on that
subscriber port (if the
feature is supported),
3) Check that the
aggregation network
that connects multiple
access nodes together
is operating in split
horizon L2 forwarding. If
not, the access node
may also be learning
subscriber MACs from
another Access Node,
4) If subtending off of a
hub access node, make
sure the hub node port
that is connected to the
subtended access node
is configured as
residential. If not, the
subtended access node
may also be learning
subscriber MACs from
the hub access node.

Condition occurs when


number of of internal
MAC entries used by
IHUB has reached 20%
of the hardware MAC
table size. Internal MAC
entries are used by L3
Storage interfaces, interfaces in
Capacity Internal MAC Major Comm a true VPLS and CFM
153 /
Problem Threshold IHUBINTMACTHRESHREACH end points. Higher the
On 6 No
Reached level of a MEP more is
SCP
the number of internal
MACs used
Possible Reasons:
1) Too many CFM
MEPs have been
configured. Reduce the
number of MEPs

Check the number of


(S,G),(*,G) joins
received from the
network and user side.
Consider creating at
network side a join
policy to restrict
accepted joins.
PIM Consider to restrict the
Storage Maximum allowed groups from the
Capacity Number Of Major 176 / Comm
MAXMCROUTES user.
Problem Multicast On 2 Yes
Routes Increase the number of
SCP
Reached maximum routes, but
take into account that
replication resources
are limited to 4K and
shared with next L2
services: one per VPLS
for flooding and one per
(S,G)/(*,G) for VPLS/v-
VPLS IGMP snooping.

Storage BGP MIDLIMPEEROUTES Major 177 / Comm Increase prefix limit if


Capacity Approaching On 2 No memory resources are
Problem Max Number available.
SCP Of Learned
Routes

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 28 sur 93

If memory is not
available, modify
policies to reduce BGP
route importation.

Lower the number of


targets to be
intercepted.
Decrement the number
of sessions, traffic to be
Storage Maximum intercepted by
Capacity Intercepted Major 179 / Comm -Attaching a filter to the
Problem LIBANDWIDTH
Traffic Flows On 2 Yes target.
SCP Reached -specifying a more
specific target key (for
example, use circuit-id
instead of remote-id ,
specify the VRF, and so
on).

1. Check the number of


physical links that are
up in the LAG subgroup
to which switchover
failed.
Switchover Subgroup Major 152 / Comm 2. It should be made
Failure Switchover SUBGRPSWITCHFAIL
On 3 Yes greater than the
SOF Failed
configured threshold
value for the subgroup.
3. After it is done, the
switchover occurs and
the alarm is cleared.

A condition detected by
STP on a port.
Possible reasons:
- Detection of a topology
STP Failure Major Comm loop.
STP 142 /
STPEXCEPTION Possible solutions:
STP Exception On 1 Yes
- Check the STP peer to
see if it is misconfigured
to flood BPDUs, and its
Ethernet ports are
cabled together.

The system has


detected a STP root-
guard violation.
When root guard is
enabled for the access
interface, this condition
can occur when a port
that has STP enabled is
attempting to become
root (has a better STP
priority vector).
Possible reason:
STP Failure STP Root Minor Comm
142 / STP peers are
Guard STPROOTGUARDV
STP On 2 Yes indicating they have
Violation
higher bridge address or
priority.
Possible solutions:
a) Configure STP peers
to have a lower bridge
priority.
b) Check for possible
spoofing by equipment
that is not trusted and is
attempting to become
root through the
alarmed port.

Synchronization NTP Servers Check if the NTP


Major 151 / Eqt
Problem Not NTPCOMM servers are operational
On 11 No
SYNC Responding and reachable.

Threshold Subgroup SUBGRPTHRESHREACHED Major 152 / Comm 1. Check the number of


Crossed Threshold On 2 Yes physical links that are
TCA Reached up in the LAG subgroup
for which the alarm has
occurred.
2. It should be made
greater than the

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 29 sur 93

configured threshold
value for the subgroup.

Threshold Used Output Major 218 / Comm Check the port's


Crossed Bandwidth TCA_OUTPUTBW
On 1 No bandwidth usage
TCA Threshold

Threshold Used Input Major 218 / Comm Check the port's


Crossed Bandwidth TCA_INPUTBW
On 2 No bandwidth usage
TCA Threshold

Threshold Receive
CRC Align Major 218 / Comm Check the port's
Crossed TCA_RXCRCALIGN
Errors On 3 No physical connections
TCA Threshold

Threshold Transmit
CRC Align Major 218 / Comm Check the port's
Crossed TCA_TXCRCALIGN
Errors On 4 No physical connections
TCA Threshold

Threshold Transmit Major 218 / Comm Check the port's


Crossed Collision TCA_TXCOLLISION
On 5 No physical connections
TCA Threshold

Table 118-19 describes the IMA group alarms.

Table 118-19 IMA group alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Configuration Or
Far End Failed Minor Comm Check the configuration at
Customization Error CFGABORT 13 / 2
Configuration On Yes the near end and far end.
CFG

Configuration Or
Near End Failed Minor Comm Check the configuration at
Customization Error CFGABORT 13 / 3
Configuration On Yes the near end and far end.
CFG

Communications
Minor Comm Check the far-end IMA
Protocol Error Starting Up At Far End STARTUP 13 / 1
On Yes group configuration.
PRTCL

Communications
Insufficient Number Of Minor Comm Check the status of links at
Protocol Error INSUFLNKS 13 / 4
Links At Far End On Yes the far end.
PRTCL

Communications
Insufficient Number Of Minor Comm Check the status of links at
Protocol Error INSUFLNKS 13 / 5
Links At Near End On Yes the near end.
PRTCL

Communications
Minor Comm Check the status of the far
Protocol Error Blocked At Far End BLOCKED 13 / 6
On Yes -end IMA group.
PRTCL

Table 118-20 describes the IMA link alarms.

Table 118-20 IMA link alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Communications Check the clock


Link Out Of Delay Minor Comm
Subsystem Failure LODS 14 / 3 configuration for the
Synchronization On Yes
COM associated group.

Communications
Minor Comm Check the link
Subsystem Failure Link Misconnected MISCONN 14 / 4
On Yes configuration at the far end.
COM

Fault In Link Facility FAULT-IMA Minor 14 / 6 Comm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 30 sur 93

Communications On Yes Check for problems with


Subsystem Failure the associated facility.
COM

Loss Of Frame Minor Comm Verify that the clock that is


- LIF 14 / 2
LOF On Yes associated with this link.

Communications Check the link


Transmit Blocked Due UNUSABLE- Minor Comm
Protocol Error 14 / 7 configuration at the far
To Far End IMA On Yes
PRTCL end.

Communications Check the link


Receive Blocked Due UNUSABLE- Minor Comm
Protocol Error 14 / 8 configuration at the far
To Far End IMA On Yes
PRTCL end.

Remote Node
Link Remote Failure Minor Comm Check the state of the
Transmission Error RFI-IMA 14 / 5
Indication On Yes associated facility.
RTE

Table 118-21 describes the IP routing alarms.

Table 118-21 IP routing alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

1. Check the authentication


type and password configured
Authentication OSPF Minor Comm on the OSPF area and OSPF
Failed Authentication OSPF_AUTH 69 / 2
On No interface.
AUTH Failure
2. Check the authentication
time range.

1. Check the authentication


type and password
Authentication
RIP Authentication Minor Comm configuration of the RIP
Failed RIP_AUTH 70 / 2
Failure On No interface.
AUTH
2. Check the authentication
time range.

1. Check the configuration of


OSPF and the OSPF interface.
Configuration Or
Customization OSPF Interface Minor Comm 2. Check the configuration of
Error Configuration OSPF_CFG 69 / 1 the IP interface.
Error On No
CFG 3. Check the OSPF hello
packets received on the OSPF
interface.

1. Check the configuration of


RIP send and receive version.
Configuration Or
Customization RIP Interface Minor Comm 2. Check the configuration of
Error Configuration RIP_CONFIG 70 / 1 the IP interface.
Error On No
CFG 3. Check the RIP request and
update packets received on the
interface.

Communications
Bad OSPF Packet Critical Comm Check for connectivity between
Protocol Error OSPF_PKT 69 / 3
Received On Yes the RIP interface and the cable.
PRTCL

Communications
Bad RIP Packet Minor Comm Check for connectivity between
Protocol Error RIP_PKT 70 / 3
Received On No the RIP interface and the cable.
PRTCL

Check the OSPF neighbor table


to get more detailed
information. If the neighbor is
Routing Failure OSPF Neighbor Minor Comm correctly established, no action
OSPF_NSTATE 69 / 6
ROUT State Change On Yes is required. If the neighbor is
unexpectedly down, check the
OSPF process status and
interface related parameters.

Routing Failure OSPF Interface OSPF_IFSTATE Minor 69 / 7 Comm There is no need to repair. If
ROUT State Change On Yes wanted, check and modify the
OSPF interface parameters to

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 31 sur 93

change the OSPF interface


status.

1. Start the OSPF instance


again (do not wait for OSPF
restart after timeout).
2. Check the network L3 and
Routing Failure Critical Comm OSPF routing protocol
OSPF Instance
OSPF_INSTDWN 69 / 9 configuration and the number
ROUT Down On Yes of routes configured in all
instances for ISAM and all
other routers within the AS.
3. Check route redistribution to
OSPF configuration.

1. Start the RIP instance again


(do not wait for RIP restart
after timeout).
2. Check the network L3 and
RIP routing protocol
Routing Failure Critical Comm configuration (split horizon,
RIP Instance
RIP_INSTDWN 70 / 5 poison reverse) and the
ROUT Down On Yes number of routes configured in
the instance for ISAM and all
other routers within the AS.
3. Check the route
redistribution to RIP
configuration.

1. Remove some external


routes configured in the OSPF
Storage Capacity domain.
OSPF Overflow Major Comm
Problem OSPF_LSDBOVFL 69 / 5 2. Configure the OSPF area as
On LSDB On No
SCP stub area ,if possible.
3. Only configure the external
major network routes.

1. Check route redistribution to


Storage Capacity OSPF Link State OSPF configuration in ISAM.
Major Comm
Problem Advertisement OSPF_EXTLSATHR 69 / 8 2. Check AS Border router L3
Table Full On No
SCP configuration (including route
aggregation configuration).

1. Check the network L3 and


RIP routing protocol
configuration (split horizon,
poison reverse) and the
Storage Capacity
RIP Route Table Major Comm number of routes configured in
Problem RIP_ROUTTHR 70 / 4
Full On No the instance both for ISAM and
SCP all other routers within the AS.
2. Check the route
redistribution to RIP
configuration.

1. Check the number of routes


Storage Capacity Route Table in routing table.
Major Comm
Problem Threshold L3FWD_ROUTTHR 71 / 2 2. If the number is too high,
Reached On Yes
SCP decrease the routes
accordingly.

1. Check the AS border router


L3 configuration (including
route aggregation
configuration).
2. Check the network L3 and
OSPF routing protocol
configuration (route
Storage Capacity
OSPF Global Major 122 / Comm aggregation) and the number
Problem OSPFGLRTTHR
Route Table Full On 1 No of routes configured in all
SCP instances both for ISAM and all
other routers within the AS.
3. Check the route
redistribution configuration in
ISAM.
4. Check the route aggregation
configuration in ISAM.

Storage Capacity OSPF Global Link OSPFGLRTLSATHR Major 122 / Comm 1. Check the route
Problem State On 2 No redistribution (from other RP)
SCP Advertisement configuration.
Table Full 2. Check the AS border router
L3 configuration (including
route aggregation
configuration).

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 32 sur 93

3. Check the network L3 and


OSPF routing protocol
configuration (route
aggregation) and the number
of routes configured in all
instances both for ISAM and
all other routers within the AS.
3. Create more OSPF areas.

1. Check for a problem in


neighbor OSPF routers.
Storage Capacity OSPF Global Major 122 / Comm 2. Check the link overload
Problem Retransmission OSPFGLRTRETRTHR
On 3 No causing excessive packet
SCP Table Full
loss, including the loss of
multiple OSPF packets.

1. Check the number of


Storage Capacity OSPF Global Self redistributed routes to OSPF.
Generated LSA Major 122 / Comm
Problem OSPFGLRTLSAOFL 2. Reduce the number of
Threshold On 4 No
SCP Reached redistributed routes as much
as possible.

OSPF Global 1. Check the area topology


Storage Capacity
Area Topology Major 122 / Comm and try to reduce the number
Problem OSPFGLRTARTOP
Threshold On 5 No of interfaces in that area.
SCP Reached 2. Reduce the neighbor.

1. Check the network L3 and


RIP routing protocol
configuration (split horizon,
poison reverse) and the
Storage Capacity number of routes configured
RIP Global Route Major 124 / Comm
Problem RIPGLRTUPTHR in all instances both for ISAM
Table Full On 1 No and all other routers within the
SCP
AS.
2. Check the route
redistribution to RIP
configuration.

1. Check the network L3


configuration and the number
of routes configured within the
AS (all instances).
2. Check the route
Storage Capacity aggregation configuration in
Global Forwarding Major 125 / Comm
Problem FWDGLFWDTHR ISAM and all other routers in
Table Full On 2 No the AS.
SCP
3. Reduce the number of
enabled routing protocols.
4. Check the routemaps
configuration in other routers
in the AS.

Table 118-22 describes the LLU alarms.

Table 118-22 LLU alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Configuration Or Check the compatibility to


Applique Unsuitable For Major Comm
Customization Error APPLIQ 78 / 1 LLU relay of the applique
Local Loop Unbundling On Yes
CFG inserted.

Table 118-23 describes the ogical link alarms.

Table 118-23 Logical link alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

Communications Report Time Out REPORTTIMEOUT Critical 154 / 4 Comm 1. Check whether the
Subsystem Failure Detecting On Yes ONT receive gate or
COM not.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 33 sur 93

2. Check whether ONT


sends a report or not.

Errored Event TLV Errored Symbol Warning Qos Check the physical
Period Event SYMBOLIERRPR 155 / 1
EET On No line.
TLV

Errored Event TLV Errored Frame Warning Qos Check the physical
FRAMEERR 155 / 2
EET Event TLV On No line.

Errored Event TLV Errored Frame Warning Qos Check the physical
Period Event FRAMEERRPR 155 / 3
EET On No line.
TLV

Errored Frame
Errored Event TLV Seconds Warning Qos Check the physical
FRAMEERRSEC 155 / 4
EET Summary Event On No line.
TLV

1. Verify that the ONT


Key Exchange Failure During receives key exchange
Major Comm
Failure One Churning KEYFAIL1CHTIME 154 / 1 requests.
Time On Yes
KEF 2. Verify that the ONT
sends key responses.

1. Verify that the ONT


Key Exchange Failure During receives key exchange
Major Comm
Failure Three Churning KEYFAIL3CHTIME 154 / 2 requests.
Time On Yes
KEF 2. Verify that the ONT
sends key responses.

Check the OAM


OAM Failure Extend OAM Critical Comm extension supported
EXOAMFAL 154 / 3
OAMFL Discovery On Yes version between OLT
and ONT.

Check whether ONU is


Threshold Crossed Total Protocol Major Comm in attack or has virus.
TOTALPACKETEXDTHD 154 / 5
TCA Packets On Yes Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed Minor Comm in attack or has virus.
ARP Packets ARPPACKETEXDTHD 154 / 6
TCA On No Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed Minor Comm in attack or has virus.
DHCP Packets DHCPPACKETEXDTHD 154 / 7
TCA On No Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed Minor Comm in attack or has virus.
IGMP Packets IGMPPACKETEXDTHD 154 / 8
TCA On No Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed Minor Comm in attack or has virus.
PPPoE Packets PPPOEPACKETEXDTHD 154 / 9
TCA On No Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed Minor 154 / Comm in attack or has virus.
ND Packets NDPACKETEXDTHD
TCA On 10 No Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed Minor 154 / Comm in attack or has virus.
ICMPv6 Packets ICMPV6PACKETEXDTHD
TCA On 11 No Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed Minor 154 / Comm in attack or has virus.
MLD Packets MLDPACKETEXDTHD
TCA On 12 No Check whether the
threshold set too small.

Check whether ONU is


Threshold Crossed DHCPv6 Minor 154 / Comm in attack or has virus.
DHCPV6PACKETEXDTHD
TCA Packets On 13 No Check whether the
threshold set too small.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 34 sur 93

Threshold Crossed CFM Packets CFMPACKETEXDTHD Minor 154 / Comm Check whether ONU
TCA On 14 No is in attack or has
virus.
Check whether the
threshold set too
small.

Table 118-24 describes the MEP alarms.

Table 118-24 MEP alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

Last CCM
Ethernet CFM Check for MEPs in MA with the
Received From Minor Comm
CCM Defect 202 / CCIEnabled flag.Check operational
Remote MEP DEFRDICCM
On 1 Yes status of links needed for the CCM
CCM Contained the RDI
transmission towards peer
Bit

MAC Reports
Ethernet CFM Error via Port Minor 202 / Comm Check for failed bridge or aggregated
CCM Defect Status TLV/ DEFMACSTATUS
On 2 Yes ports in the remote MEPs in the MA
CCM Interface Status
TLV

Ethernet CFM Check MA configuration: peer MEP


Invalid CCMs Major 202 / Comm
CCM Defect DEFERRORCCM list,MEPIDs,CCM transmission
Received On 4 Yes
CCM periods

Ethernet CFM Receiving CCMs


of Other MA. Major 202 / Comm Check MAID configuration.Check
CCM Defect DEFXCONCCM
Mismerge On 5 Yes service configuration
CCM Condition

Missing Not Receiving


CCMs from CCMs From Major 202 / Comm Check CCM misconfigurations(peer
MEP DEFREMOTECCM
Remote MEPs. On 3 Yes MEP list),device failures,link failures
CCM Loss of Continuity

Table 118-25 describes the MGC configuration alarms.

Table 118-25 MGC configuration alarms


Default
Category /
Probable cause / Specific TL1 severity / Alarm
Service Repair action
Mnemonic problem condition Default ID
affecting
reporting

The LT or ONT did not accept the


configuration requests for the
provisioned MGC. Possible reasons are:
Configuration Or 1. The interface is not supported by the
ONT MGC Minor Comm
Customization Error MGCMIS 187 / 1 ONT.
Mismatch On Yes
CFG 2. LT configuration or setup problem.
Possible solutions are to restart ONT,
restart LT, or to deprovision the MGC,
since it is not supported.

The association with the MGC timed


out. Possible solutions are:
Configuration Or 1. Check the MGC configuration at both
ONT MGC Major Comm
Customization Error MGCTMOUT 187 / 2 the MGC and ONT (such as IP address
Timeout On Yes and message ID)
CFG
2. Verify the MGC server configuration.
3. Check the network alarms.

Table 118-26 describes the multicast alarms.

Table 118-26 Multicast alarms


Probable cause / Specific TL1 Default Alarm Category / Repair action
Mnemonic problem condition severity / ID

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 35 sur 93

Default Service
reporting affecting

1. Check the receive signal at the NT.


2. If there is an alarm at NT
PONMCSRC, verify the network
configuration and connectivity to the
Communications video source.
Video Loss Major Comm
Subsystem Failure MCASTLOSS 120 / 1 3. If there is an alarm at LT PON
Of Signal On Yes
COM multicast source, verify the provisioning
and operational state of the OLT
equipment.
4. If a multicast source is no longer in
use, deprovision the multicast service.

Table 118-27 describes the NE alarms.

Table 118-27 NE alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

Configuration Or The system starts up with the


Customization Major Eqt default back panel type.
Invalid Back
Error BCKPNLINV 1 / 25 Check the back panel type
Panel Type On No configuration when SYS is
CFG running.

Configuration Or Check the HUB configuration


Customization SHUB / IHUB Critical Eqt with respect to the database.
Error Configuration HUBCONFLOSS 1 / 28
On Yes The last database changes
Loss
CFG may be lost.

Check the peer equipment


and link between peer
equipment and the ISAM for
all the timing references that
Synchronization correspond to the preferred
Preferred Timing Major Comm
Source Mismatch PREFREFFAIL 1/5 timing mode.
Mode Not Used On Yes
CLK If the BITS mode is E1 or
DS1, check that there is no
Alarm Indication Signal (AIS)
on the BITS inputs to the
system.

Check peer equipment and


link between the peer
equipment and the ISAM for
all timing references.
Synchronization System In If BITS is used as external
Holdover Mode Critical Comm source for network timing
Source Mismatch ALLREFFAIL 1/6
Or In Free Run On Yes reference, check that the
CLK Mode signals at the BITS inputs to
the system are within
specification and that there is
no Alarm Indication Signal
(AIS) on these inputs.

Check the admin status of all


ANCP Adjacency
components, for example:
ANCP Session interfaces, virtual router, and
ANCP Adjacency Major Comm
Terminated ANCPADJACENCYLOST 58 / 1 VLAN. Check compatibility of
Lost On No
COM own and peer ANCP
capabilities, partition id, TCP
Port number, BRAS IP
address.

A download is in progress to
one or more ONTs. The
system clears the alarm when
Download In ONT SW no further download or
Automatic Minor 121 / Eqt
Progress AUTOONTSWDLIP activations are pending.
Download In On 14 No
DLIP Progress Contact your Alcatel-Lucent
technical support
representative if the alarm
fails to clear.

Equipment Environment Box LOSSENVMON Critical 104 / Eqt Check for the existence of the
Malfunction Unreachable On 1 No environment box.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 36 sur 93

EQP

1. Check network
connectivity to the system
File Transfer
System Log File Minor 121 / Comm log server.
Problem ULFAILED
Upload Failure On 7 No 2. Check the system log
FTP
server configuration and
provisioning.

SHUB / IHUB Loss Of 1. Check the external HUB.


Communication Communication Critical Eqt
Lost HUBOOS 1/8 2. The HUB has reset, wait
With SHUB / On Yes
IHUB until it has restarted.
HLOC

1. Remove the corrupted


OSWP (ABORT operation).
OSWP Activation
Implicit Software Major Proc 2. Download the required
Failure SWROLLBK 29 / 1
Rollback On Yes OSWP again.
OSWP
3. Activate the downloaded
OSWP.

OSWP Activation
Implicit Database Major Proc Download the required
Failure DBROLLBK 29 / 2
Rollback On Yes database again.
OSWP

1. Check the transmit fiber.


2. Check the default gateway
Ping Check configuration.
Major Eqt
Failure - PINGFAIL 20 / 3 3. Check that the configured
On No
PNG IP address is correct using
the ping connectivity check
command.

1. Check the link on the


Standby NT.
NT Protection
Switch Over Major Eqt 2. Check the Standby
Failure SWCAP 20 / 1
Capability Lost On No Extenders.
PROT
3. Wait for the Quench
TimeOut.

Remote Node
Transmission SNTP Major Eqt
Error Communication SNTPCOMM 1/2 Check the SNTP server.
Lost On No
RTE

Storage Capacity
Disk Full 95 Major Eqt
Problem DISKSPACE 1/4 Clean up disk space.
Percent On No
SCP

Storage Capacity Change the alarm severity to


Alarm Table Critical 217 / Comm
Problem ALRMTBLOVERFLOW 'ignore' for alarms of no
Overflow On 1 No
SCP interest.

Successful Generated due to successful


Management Successful Major Comm login attempt via
192 /
Login Management SECUMGTACCESS Management Access.
On 1 No
Access
SML Check for security measures.

Software
Program
Persistent Data Critical Eqt
Abnormally INIT 1/1 Reconfigure the NE.
Terminated Loss On Yes
SW

Generated due to too many


Threshold Invalid Major 192 / Comm invalid attempts to login via
Crossed Management SECUMGTACCESSTCA
On 2 No Management Access.
TCA Access Attempt
Check for security measures.

Table 118-28 describes the NGPON2-ONT alarms.

Table 118-28 NGPON2-ONT alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 37 sur 93

Configuration Or Wavelength Tuning TUNEFAIL Major 129 / Comm Check OLT and/or ONT
Customization Error Failure On 21 Yes to see why it failed to
CFG tune.

Configuration Or Check OLT and/or ONT


Wavelength Tuning TUNEFAIL- Major 164 / Comm
Customization Error to see why it failed to
Failure SFU SFU On 21 Yes
CFG tune.

Configuration Or Check OLT and/or ONT


Wavelength Tuning TUNEFAIL- Major 166 / Comm
Customization Error to see why it failed to
Failure SOHO SOHO On 21 Yes
CFG tune.

Configuration Or Check OLT and/or ONT


Wavelength Tuning TUNEFAIL- Major 168 / Comm
Customization Error to see why it failed to
Failure MDU MDU On 21 Yes
CFG tune.

Table 118-29 describes the ONT alarms.

Table 118-29 ONT alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

Bias Problem Bias Too High Minor 129 / Eqt 1. Check board problem
BIASH
BIPR Alarm On 14 No 2. Check sfp module.

Bias Problem Bias Too High Minor 219 / Eqt 1. Check board problem
BIASH-SFU
BIPR Alarm SFU On 14 No 2. Check sfp module.

Bias Problem Bias Too High Minor 220 / Eqt 1. Check board problem
BIASH-SOHO
BIPR Alarm SOHO On 14 No 2. Check sfp module.

Bias Problem Bias Too High Minor 221 / Eqt 1. Check board problem
BIASH-MDU
BIPR Alarm MDU On 14 No 2. Check sfp module.

1. Try another activation


(change the planned version
to be the currently passive
Configuration Or version).
Customization Software Major Eqt 2. Manually clear the alarm
Error SWACTFAIL 41 / 9
Activation Failure On Yes (change the planned version
CFG to the wildcard).
3. Contact your Alcatel-
Lucent technical support
representative.

Configuration Or
Customization Software Minor Eqt This is a transient alarm that
41 /
Error Download In SWDLIP clears after the download is
On 11 No
Progress finished.
CFG

Either change the provisioned


Configuration Or version ID to match the
Customization Major Eqt reported version ID, or
Equipment 41 /
Error EQVERMIS change the physical ONT so
Version Mismatch On 12 Yes that the reported version ID to
CFG match the provisioned
version ID.

Either make the active


software version equal to the
Configuration Or planned version through a
Customization Software Version Minor 41 / Eqt successful activation, or
Error SWVER
Mismatch On 16 No make the planned software
CFG version equal to the active
version using an operator
update.

Configuration Or Provisioned parameters failed


Customization ONT Provisioning Major 41 / Eqt to be provisioned in the ONT.
Error ONTMEA
Failure On 23 Yes Delete the ONT and provision
CFG it again.

Configuration Or Configuration ONTNSAMEA Minor 41 / Eqt Non-service-affecting


Customization Mismatch On 31 No provisioned parameters failed
Error to be provisioned in the ONT.
CFG Check the supported

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 38 sur 93

capabilities of the ONT and


deprovision unsupported
features.

No ONT software match was


found in ONT SW version
control table.
Note: This alarm is only valid
when either the planned
software or downloaded
software on the ONT is
provisioned as AUTO.
Possible solutions:
a) If the planned software
parameter on the ONT is
AUTO, check if there is a
matching entry in the ONT
SW version control table.
Configuration Or
Customization Minor Eqt b) If the downloaded software
ONT SW Version 129 /
Error SWVERCTLERR parameter on the ONT is
Control Error On 7 No AUTO, verify that there is a
CFG matching entry in the ONT
SW version control table. If
no match exists in ONT SW
version control table, either
update the planned variant
on the ONT, and/or add a
new entry to the ONT SW
version control table in a
manner that causes the
AUTO setting to have a
match. Otherwise disable the
feature by changing the
planned software and
downloaded software
parameters to not be AUTO.

Configuration Or
Customization Critical Eqt Adjust the feeding of each
PoE Feeding 129 /
Error POEOVERLOAD ethernet port to fit the ONT
Exceed Maximum On 8 No output.
CFG

Configuration Or
Customization ONT RSSI Minor Eqt Check ONT capability and
129 /
Error Configuration PRFMIS whether it supports this
On 10 No
Mismatch function or parameter.
CFG

Configuration Or ONT Loop


Customization Minor Eqt Check ONT capability and
Detection 129 /
Error ONTLOOPMISMATCH whether support loop
Configuration On 15 No detection
CFG Mismatch

Configuration Or
Customization Configuration Of Minor Eqt ONT did not accept the
129 /
Error HGU TR069 HGUTR069MEA configuration for HGU TR069
On 22 No
Failed parameters.
CFG

Configuration Or ONT SW Version SWVERCTLERR-SFU Minor 219 / Eqt No ONT software match was
Customization Control Error SFU On 7 No found in ONT SW version
Error control table.
CFG Note: This alarm is only valid
when either the planned
software or downloaded
software on the ONT is
provisioned as AUTO.
Possible solutions:
a) If the planned software
parameter on the ONT is
AUTO, check if there is a
matching entry in the ONT
SW version control table.
b) If the downloaded software
parameter on the ONT is
AUTO, verify that there is a
matching entry in the ONT
SW version control table. If
no match exists in ONT SW
version control table, either
update the planned variant
on the ONT, and/or add a
new entry to the ONT SW
version control table in a
manner that causes the
AUTO setting to have a
match. Otherwise disable the

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 39 sur 93

feature by changing the


planned software and
downloaded software
parameters to not be AUTO.

Configuration Or
Customization PoE Feeding Critical Eqt Adjust the feeding of each
219 /
Error Exceed Maximum POEOVERLOAD-SFU ethernet port to fit the ONT
On 8 No
SFU output.
CFG

Configuration Or
Customization ONT RSSI Minor Eqt Check ONT capability and
219 /
Error Configuration PRFMIS-SFU whether it supports this
On 10 No
Mismatch SFU function or parameter.
CFG

Configuration Or
Customization Minor Eqt Check ONT capability and
ONT Loop ONTLOOPMISMATCH 219 /
Error whether support loop
Mismatch SFU -SFU On 15 No detection
CFG

No ONT software match was


found in ONT SW version
control table.
Note: This alarm is only valid
when either the planned
software or downloaded
software on the ONT is
provisioned as AUTO.
Possible solutions:
a) If the planned software
parameter on the ONT is
AUTO, check if there is a
matching entry in the ONT
SW version control table.
Configuration Or
Customization ONT SW Version Minor Eqt b) If the downloaded software
SWVERCTLERR- 220 / parameter on the ONT is
Error Control Error
SOHO On 7 No AUTO, verify that there is a
SOHO
CFG matching entry in the ONT
SW version control table. If
no match exists in ONT SW
version control table, either
update the planned variant
on the ONT, and/or add a
new entry to the ONT SW
version control table in a
manner that causes the
AUTO setting to have a
match. Otherwise disable the
feature by changing the
planned software and
downloaded software
parameters to not be AUTO.

Configuration Or
Customization PoE Feeding Critical Eqt Adjust the feeding of each
POEOVERLOAD- 220 /
Error Exceed Maximum ethernet port to fit the ONT
SOHO On 8 No
SOHO output.
CFG

Configuration Or
Customization ONT RSSI Minor Eqt Check ONT capability and
220 /
Error Configuration PRFMIS-SOHO whether it supports this
On 10 No
Mismatch SOHO function or parameter.
CFG

Configuration Or
Customization Minor Eqt Check ONT capability and
ONT Loop ONTLOOPMISMATCH 220 /
Error whether support loop
Mismatch SOHO -SOHO On 15 No detection
CFG

Configuration Or ONT SW Version SWVERCTLERR- Minor 221 / Eqt No ONT software match was
Customization Control Error MDU On 7 No found in ONT SW version
Error MDU control table.
CFG Note: This alarm is only valid
when either the planned
software or downloaded
software on the ONT is
provisioned as AUTO.
Possible solutions:
a) If the planned software
parameter on the ONT is
AUTO, check if there is a
matching entry in the ONT
SW version control table.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 40 sur 93

b) If the downloaded software


parameter on the ONT is
AUTO, verify that there is a
matching entry in the ONT
SW version control table. If
no match exists in ONT SW
version control table, either
update the planned variant
on the ONT, and/or add a
new entry to the ONT SW
version control table in a
manner that causes the
AUTO setting to have a
match. Otherwise disable the
feature by changing the
planned software and
downloaded software
parameters to not be AUTO.

Configuration Or
Customization PoE Feeding Critical Eqt Adjust the feeding of each
POEOVERLOAD- 221 /
Error Exceed Maximum ethernet port to fit the ONT
MDU On 8 No
MDU output.
CFG

Configuration Or
Customization ONT RSSI Minor Eqt Check ONT capability and
221 /
Error Configuration PRFMIS-MDU whether it supports this
On 10 No
Mismatch MDU function or parameter.
CFG

Configuration Or
Customization Minor Eqt Check ONT capability and
ONT Loop ONTLOOPMISMATCH 221 /
Error whether support loop
Mismatch MDU -MDU On 15 No detection
CFG

1. Make the Active version


Configuration Or equal Planned version via
Customization Configuration File Minor 228 / Eqt successful activation or
Error CFGVER
Version Mismatch On 4 No 2. Make the Planned version
CFG equal Active version via
operator update.

1. Ensure that Planned


Config File version is
physically present on the
Configuration Or OLT.
Customization Configuration File Minor 228 / Eqt
CFGDLFILE 2. Retry the download again.
Error Error On 5 No
3. Reload the config file on
CFG
the OLT.
4. Call Alcatel-Lucent
customer service.

Configuration Or Configuration File CFGVERCTLERR Minor 228 / Eqt A condition meaning no


Customization Version Control On 6 No Config File match found in
Error Error ONT SW version control
CFG table.
Note: Only valid when either
ENT-ONT PLANVER or
DLVER is provisioned as
'AUTO'.
Possible reasons for alarm
are:
1. If PLANVER attribute on
ONT is 'AUTO', check
ACTHWVER/PLANSWVAR
for match of provisioned
AUTOHWVER/AUTOSWVAR
values in the ONT SW
version control table.
2. If DLVER attribute on ONT
is 'AUTO', check
ACTHWVER/PLANSWVAR
for match of provisioned
AUTOHWVER/AUTOSWVAR
values in the ONT SW
version control table.
3. If no match exists in ONT
SW version control table,
either update PLANSWVAR
and/or add a new entry to the
ONT SW version control
table in a manner that causes
the 'AUTO' setting to have a
match.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 41 sur 93

4. Otherwise disable feature


by changing PLANVER and
DLVER to not be AUTO.

1. Set PLNDCFGFILE and


Configuration Or DLCFGFILE attribute to
Customization Configuration File Minor Eqt DISABLED, or change with
228 /
Error Download Not CFGDLNSUPP an ONT that supports the
On 7 No
Supported config file download function.
CFG
2. Call ALU customer service

The ONT has never been


able to reach and get the
time from an NTP server. A
30-minute alarm declaration
interval is started when the
NTP and VoIP clients are
both enabled, and ends as
soon as the ONT syncs with
Synchronization the NTP server. Note: if the
Network Timing Minor 41 / Comm ONT successfully gets the
Source Mismatch NTPERR
Protocol Error On 28 No time from an NTP server, and
CLK
then loses contact with it, the
alarm is not raised. To
troubleshoot:
1. Check the NTP server
accessibility and ONT
provisioning configuration.
2. Restart the ONT to see if
the alarm returns.

1. Check the status of both


Synchronization ONT and PON.
Major 129 / Eqt
Source Mismatch ToD Out Of Sync TODOUTSYNC 2. Perform an ONT reset or
On 20 Yes
CLK replace the ONT if the failure
persists.

1. Check the receive signal at


Communications the ONT.
Subsystem Major 40 / Comm
Failure Loss Of PLOAM LOAM 2. Reset the ONT.
On 20 Yes
COM 3. If the Loss of PLOAM
persists, replace the ONT.

Check the quality of the line


Communications from the ONT if the condition
Subsystem Major 40 / Comm persists. The OLT received a
Failure Drift Of Window DOW
On 21 Yes transmission from the ONT at
COM an unexpected place within
the upstream virtual frame.

1. Check the connectivity


between the OLT and ONT
that is resulting in a loss of
Communications
key exchange PLOAM
Subsystem Loss Of Key Major 40 / Comm
LOKS message between the OLT
Failure Synchronization On 24 Yes and ONT.
COM
2. Reset the ONT. If the
condition persists, replace
the ONT.

Reset ONT by
Communications administratively putting it
Subsystem Rogue ONT Major 40 / Comm OOS and then IS.
Failure ROGUEONTDIS
Disabled On 26 Yes If the alarm occurs again, the
COM ONT must likely be physically
repaired or swapped.

ONT has been deactivated


Communications because its location on the
Subsystem Differential Reach Major 40 / Comm PON has exceeded its
Failure DIFREACH differential reach capability.
Exceeded On 27 No
COM Alarm is cleared when ONT
is disconnected from PON.

1/ Power Cycle the ONT unit.


2/ If problem persists after a
Communications power cycle of the ONT unit,
Subsystem Major Comm re-program registration ID
Loss Of OMCI 40 /
Failure LOOC into ONT unit.
Channel On 28 Yes
COM 3/ If problem persists after
registration ID re-
programming, replace the
ONT unit.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 42 sur 93

Communications OMCI Failure OMCICOMM Major 41 / 1 Comm Attempt to restart the ONT.
Subsystem On Yes
Failure
COM

An emergency phone call is


active. Wait for the call to
terminate.
Communications
Subsystem Emergency Call Minor 129 / Comm Note: During an emergency
Failure ECALLACT call, no upgrade or
Active On 5 No
modification to the system
COM
should be performed, which
could cause a call
termination.

1/Ensure the voice


configuration file is physically
present on the OLT. If not,
Communications ensure the voice
Subsystem Voice Major Comm configuration file is on the
129 /
Failure Configuration File ONTCFGDLDFAIL FTP server and the FTP
On 9 Yes
Download Failed server is available.
COM
2/Ensure the OMCI between
OLT and ONT is ok.
3/Retry the download again.

1/ Power Cycle the ONT unit.


2/ If problem persists after a
Communications power cycle of the ONT unit,
Subsystem Major Comm re-program registration ID
Loss Of OMCI 163 /
Failure LOOC-SFU into ONT unit.
Channel SFU On 28 Yes
COM 3/ If problem persists after
registration ID re-
programming, replace the
ONT unit.

1/ Power Cycle the ONT unit.


2/ If problem persists after a
Communications power cycle of the ONT unit,
Subsystem Major Comm re-program registration ID
Loss Of OMCI 165 /
Failure LOOC-SOHO into ONT unit.
Channel SOHO On 28 Yes
COM 3/ If problem persists after
registration ID re-
programming, replace the
ONT unit.

1/ Power Cycle the ONT unit.


2/ If problem persists after a
Communications power cycle of the ONT unit,
Subsystem Major Comm re-program registration ID
Loss Of OMCI 167 /
Failure LOOC-MDU into ONT unit.
Channel MDU On 28 Yes
COM 3/ If problem persists after
registration ID re-
programming, replace the
ONT unit.

An emergency phone call is


active. Wait for the call to
terminate.
Communications
Subsystem Emergency Call Minor 219 / Comm Note: During an emergency
Failure ECALLACT-SFU call, no upgrade or
Active SFU On 5 No
modification to the system
COM
should be performed, which
could cause a call
termination.

1/Ensure the voice


configuration file is physically
present on the OLT. If not,
Communications Voice ensure the voice
Subsystem Configuration File ONTCFGDLDFAIL- Major 219 / Comm configuration file is on the
Failure Download Failed SFU On 9 Yes FTP server and the FTP
COM SFU server is available.
2/Ensure the OMCI between
OLT and ONT is ok.
3/Retry the download again.

Communications Emergency Call ECALLACT-SOHO Minor 220 / Comm An emergency phone call is
Subsystem Active SOHO On 5 No active. Wait for the call to
Failure terminate.
COM Note: During an emergency
call, no upgrade or
modification to the system

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 43 sur 93

should be performed, which


could cause a call
termination.

1/Ensure the voice


configuration file is physically
present on the OLT. If not,
Communications Voice ensure the voice
Subsystem Configuration File ONTCFGDLDFAIL- Major 220 / Comm configuration file is on the
Failure Download Failed SOHO On 9 Yes FTP server and the FTP
COM SOHO server is available.
2/Ensure the OMCI between
OLT and ONT is ok.
3/Retry the download again.

An emergency phone call is


active. Wait for the call to
terminate.
Communications
Subsystem Emergency Call Minor 221 / Comm Note: During an emergency
Failure ECALLACT-MDU call, no upgrade or
Active MDU On 5 No
modification to the system
COM
should be performed, which
could cause a call
termination.

1/Ensure the voice


configuration file is physically
present on the OLT. If not,
Communications Voice ensure the voice
Subsystem Configuration File ONTCFGDLDFAIL- Major 221 / Comm configuration file is on the
Failure Download Failed MDU On 9 Yes FTP server and the FTP
COM MDU server is available.
2/Ensure the OMCI between
OLT and ONT is ok.
3/Retry the download again.

1. Retry the download again.


Communications
Subsystem Minor Eqt 2. Give up and manually
Configuration File 228 /
Failure CFGDLFAIL clear the alarm.
Download Failure On 1 No
COM 3. Call Alcatel-Lucent
customer service.

1. Retry another activation.


Communications
Subsystem Major Eqt 2. Give up and manually
Configuration File 228 /
Failure CFGACTFAIL clear the alarm.
Activation Failure On 2 Yes
COM 3. Call Alcatel-Lucent
customer service.

Not a problem.
Download In Configuration File Minor 228 / Eqt This is a transient condition
Progress Download In CFGDLIP
On 3 No that self clears once
DLIP Progress
download activity ceases.

Enclosure Door Investigate the ONT for


Enclosure Door Major Comm
Open INTRUDER 41 / 7 possible illegal physical
Open On No
DOOR access to ONT (MDU).

MDU
Environmental MDU Indeterminate Env Verify that the external
41 /
Alarm 1 Environmental ENV1 equipment is connected to
On 24 No
Alarm 1 MDU Alarm Input 1.
ENV-1

MDU
Environmental MDU Indeterminate Env Verify that the external
41 /
Alarm 2 Environmental ENV2 equipment is connected to
On 25 No
Alarm 2 MDU Alarm Input 2.
ENV-2

MDU
Environmental MDU Indeterminate Env Verify that the external
41 /
Alarm 3 Environmental ENV3 equipment is connected to
On 26 No
Alarm 3 MDU Alarm Input 3.
ENV-3

Equipment
Physical Major Comm
Malfunction PEE 40 / 6 Perform loopback tests.
Equipment Error On Yes
EQP

Equipment Defense Action ONTDISABLED Major 40 / Comm Reset the ONT by


Malfunction On 12 Yes administratively putting it
EQP OOS and then IS. If the alarm
occurs again, the ONT most
likely needs to be physically
repaired or replaced.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 44 sur 93

Equipment
Major 40 / Comm The ONT needs to be ranged
Malfunction Device Not Active INACT
On 15 Yes (made active).
EQP

Equipment Check the quality of the line


Major 40 / Comm
Malfunction Signal Failure SF from the ONT. Signal Fail
On 17 Yes
EQP BER exceeded.

Equipment Restore power to the ONT.


Major 40 / Comm The dying gasp indication is
Malfunction Dying Gasp DG
On 18 Yes due to a loss of power input
EQP to the ONT.

Equipment 1. Reset the ONT.


Deactivation Major 40 / Comm
Malfunction DF 2. Replace the ONT if the
Failure On 19 Yes
EQP Deactivation Failure persists.

Equipment Command another ONT self-


Major Eqt
Malfunction Self Test Failed EQPT 41 / 2 test. If it fails, implement
On Yes creative diagnostics.
EQP

Equipment Check the fan.


Major 129 / Eqt
Malfunction Fan Failure FANALM 2. Check the ambient
On 2 No
EQP temperature.

Equipment Check the fan.


Major 219 / Eqt
Malfunction Fan Failure SFU FANALM-SFU 2. Check the ambient
On 2 No
EQP temperature.

Equipment Check the fan.


Fan Failure Major 220 / Eqt
Malfunction FANALM-SOHO 2. Check the ambient
SOHO On 2 No
EQP temperature.

Equipment Check the fan.


Major 221 / Eqt
Malfunction Fan Failure MDU FANALM-MDU 2. Check the ambient
On 2 No
EQP temperature.

Loss Of Cell Or
Packet Loss Of Cell Or Major Comm Check the quality of the line
Delineation Packet LCD 40 / 4
On Yes from the ONT.
Delineation
LCD

Loop Detection Major Eqt Check ONT LAN link and


Loop Detection on 213 /
ONTLOOPDETECT figure out which ports are
LD ONT LAN Ports On 1 Yes looped.

Loss Of See if the specific ONT is


Loss Of Major Comm
Acknowledgement LOA 40 / 2 isolated. If it is not, this is
Acknowledgement On Yes
LOA likely a software error.

Loss Of Signal Major Comm Check the received signal at


Loss Of Signal LOS 40 / 1
LOS On Yes the ONT.

Message Error See if the specific ONT is


Message Error Major 40 / Comm
Message MEM isolated. If it is not, this is
Message On 13 Yes
MEM likely a software error.

Extraneous power bursts


have been detected for this
ONT. This alarm clears
automatically after 15
Power Problem ONT Power Up Minor 40 / Comm minutes.
ONTPWRERR
PWR Error On 25 No 1. Replace the ONT.
2. Change the power burst
detection mode at the system
level to normal soak mode.

Power Problem External Power Minor Env Wait for power to return to
ACFAIL 41 / 3
PWR Failure On No the ONT.

Power Problem Minor Eqt Change the provisioning, or


Battery Missing BATTMISS 41 / 4 determine why the battery is
PWR On No missing.

Power Problem Minor Eqt If power is present, determine


Battery Low BATTLOW 41 / 5 why the battery does not
PWR On No charge, or why it is low.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 45 sur 93

Power Problem Battery Failure BATTFAIL Minor 41 / 6 Eqt The customer needs to
PWR On No replace the battery.

Transmitted Check why is too low.


Power Problem Optical Signal Minor 129 / Eqt 1. Check optical attenuator or
TXPWL
PWR Below Alarm On 11 No the line problem
Threshold 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Major 129 / Comm
Too Low At OLT OLTRXPWLO the line problem
PWR On 16 Yes
Side (GPON) 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Major 129 / Comm
Too High At OLT OLTRXPWHI the line problem
PWR On 17 Yes
Side (GPON) 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too Low Warning Warning 129 / Comm
OLTRXPWLOWARN the line problem
PWR At OLT Side On 18 No
(GPON) 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too High Warning Warning 129 / Comm
OLTRXPWHIWARN the line problem
PWR At OLT Side On 19 No
(GPON) 2. Check sfp module

Power Problem Receive Power Major Comm Determine why received


160 /
Too Low At OLT OLTRXPWLO power from ONT at OLT side
PWR On 1 Yes
Side is low.

Power Problem Receive Power Major Comm Determine why received


160 /
Too High At OLT OLTRXPWHI power from ONT at OLT side
PWR On 2 Yes
Side is high.

Power Problem Receive Power Warning Comm


160 / Check the received power
Too Low Warning OLTRXPWLOWARN
PWR On 3 No from ONT at OLT side
At OLT Side

Power Problem Receive Power Warning Comm


160 / Check the received power
Too High Warning OLTRXPWHIWARN
PWR On 4 No from ONT at OLT side
At OLT Side

Check why is too low.


Power Problem Transmit Optical Minor Eqt
219 / 1. Check optical attenuator or
Signal Too Low TXPWL-SFU
PWR On 11 No the line problem
Alarm SFU
2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Major 219 / Comm
Too Low at OLT OLTRXPWLO-SFU the line problem
PWR On 16 Yes
Side GPON SFU 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Major 219 / Comm
Too High at OLT OLTRXPWHI-SFU the line problem
PWR On 17 Yes
Side GPON SFU 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too Low Warning OLTRXPWLOWARN- Warning 219 / Comm
the line problem
PWR at OLT Side SFU On 18 No
GPON SFU 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too High Warning OLTRXPWHIWARN- Warning 219 / Comm
the line problem
PWR at OLT Side SFU On 19 No
GPON SFU 2. Check sfp module

Check why is too low.


Power Problem Transmit Optical Minor Eqt
220 / 1. Check optical attenuator or
Signal Too Low TXPWL-SOHO
PWR On 11 No the line problem
Alarm SOHO
2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too Low at OLT Major 220 / Comm
OLTRXPWLO-SOHO the line problem
PWR Side GPON On 16 Yes
SOHO 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too High at OLT Major 220 / Comm
OLTRXPWHI-SOHO the line problem
PWR Side GPON On 17 Yes
SOHO 2. Check sfp module

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 46 sur 93

Power Problem Receive Power OLTRXPWLOWARN- Warning 220 / Comm 1. Check optical attenuator or
PWR Too Low Warning SOHO On 18 No the line problem
at OLT Side 2. Check sfp module
GPON SOHO

Receive Power 1. Check optical attenuator or


Power Problem Too High Warning OLTRXPWHIWARN- Warning 220 / Comm
the line problem
PWR at OLT Side SOHO On 19 No
GPON SOHO 2. Check sfp module

Check why is too low.


Power Problem Transmit Optical Minor Eqt
221 / 1. Check optical attenuator or
Signal Too Low TXPWL-MDU
PWR On 11 No the line problem
Alarm MDU
2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Major 221 / Comm
Too Low at OLT OLTRXPWLO-MDU the line problem
PWR On 16 Yes
Side GPON MDU 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Major 221 / Comm
Too High at OLT OLTRXPWHI-MDU the line problem
PWR On 17 Yes
Side GPON MDU 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too Low Warning OLTRXPWLOWARN- Warning 221 / Comm
the line problem
PWR at OLT Side MDU On 18 No
GPON MDU 2. Check sfp module

Receive Power 1. Check optical attenuator or


Power Problem Too High Warning OLTRXPWHIWARN- Warning 221 / Comm
the line problem
PWR at OLT Side MDU On 19 No
GPON MDU 2. Check sfp module

Remote Defect Check the receive signal at


Remote Defect Major 40 / Comm the ONT. The OLT
Indication RDI
Indication On 22 Yes transmission was received
RDI with errors at the ONT.

Degraded Signal Major Comm Check the quality of the line


Degraded Signal SD 40 / 9
SIGN On Yes from the ONT.

Signal Power Received Optical Check the received optical


Major 41 / Comm
Problem Signal Level Too LEVELHI signal and decrease the
On 29 Yes
SPWR High signal level.

Signal Power Received Optical Check the received optical


Major 41 / Comm
Problem Signal Level Too LEVELLO signal and increase the signal
On 30 Yes
SPWR Low level.

Startup Failure Major Comm


Startup Failure SUF 40 / 7 Re-range the ONT.
SUF On Yes

1. Ensure that the planned


ONT software version is
physically present on the
OLT.
Software 2. Retry the download again.
Software Minor Eqt
Download Failure SWDLFAIL 41 / 8 3. Manually clear the alarm
Download Failure On No
SWDL (for example, change the
planned version to the
wildcard). Contact your
Alcatel-Lucent technical
support representative.

1. Check that the planned


ONT software version is
physically present on the
Software OLT.
File Missing Or Minor 129 / Eqt
Download Failure SWDLFILE 2. Retry the download again.
File Error On 1 No
SWDL 3. Reload the ONT image on
the OLT. Contact your Alcatel
-Lucent technical support
representative.

Software File Missing Or SWDLFILE-SFU Minor 219 / Eqt 1. Check that the planned
Download Failure File Error SFU On 1 No ONT software version is
SWDL physically present on the
OLT.
2. Retry the download again.
3. Reload the ONT image on
the OLT. Contact your Alcatel

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 47 sur 93

-Lucent technical support


representative.

1. Check that the planned


ONT software version is
physically present on the
Software OLT.
File Missing Or Minor 220 / Eqt
Download Failure SWDLFILE-SOHO 2. Retry the download again.
File Error SOHO On 1 No
SWDL 3. Reload the ONT image on
the OLT. Contact your Alcatel
-Lucent technical support
representative.

1. Check that the planned


ONT software version is
physically present on the
Software OLT.
File Missing Or Minor 221 / Eqt
Download Failure SWDLFILE-MDU 2. Retry the download again.
File Error MDU On 1 No
SWDL 3. Reload the ONT image on
the OLT. Contact your Alcatel
-Lucent technical support
representative.

1. Check the receive PON


signal at the ONT.
2. Check the transmit PON
Lost GEM signal at the OLT.
Threshold
Fragments Warning Qos 3. Reset the ONT.
Crossed T-LOSTFRAGS 90 / 1
Received At ONT On No 4. Replace the ONT if the PM
TCA Near End counts persist.
5. Replace the associated LT
at OLT if the PM counts
persist.

1. Check the PON signal at


Threshold Lost GEM the ONT.
Fragments Warning Qos
Crossed T-LOSTFRAGS 90 / 2 2. Reset the ONT.
Transmitted At On No
TCA ONT Near End 3. If the PM counts persist,
replace the ONT.

1. Check the receive PON


signal at ONT.
2. Check the transmit PON
Bad GEM signal at OLT.
Threshold
Headers Warning Qos 3. Reset the ONT.
Crossed T-BADGEMHDRS 90 / 3
Received At ONT On No 4. Replace the ONT if the PM
TCA Near End counts persist.
5. Replace the associated LT
at OLT if the PM counts
persist.

1. Check the receive PON


signal at the OLT.
2. Check the transmit PON
Errored Lost GEM signal at the ONT.
Threshold
Fragments Warning Qos 3. Reset the ONT.
Crossed T-ERRFRAGSONT 95 / 1
Received At OLT On No 4. Replace the ONT if the PM
TCA Near End counts persist.
5. Replace the associated LT
at OLT if the PM counts
persist.

Temperature
High Temperature Major 129 / Eqt Check the fan. Check the
Unacceptable HITEMPWARN
Warning On 3 No ambient temperature.
TEMP

Temperature
High Temperature Major 129 / Eqt Check the fan. Check the
Unacceptable HITEMPSHUTOFF
Shutoff On 4 Yes ambient temperature.
TEMP

Temperature 1. Check fans


Temperature Too Minor 129 / Eqt
Unacceptable TMPH 2. Check environment of that
High Alarm On 12 No
TEMP eqpt, add fans

Temperature
High Temperature Major 219 / Eqt Check the fan. Check the
Unacceptable HITEMPWARN-SFU
Warning SFU On 3 No ambient temperature.
TEMP

Temperature High Temperature HITEMPSHUTOFF- Major 219 / Eqt Check the fan. Check the
Unacceptable Shutoff SFU SFU On 4 Yes ambient temperature.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 48 sur 93

TEMP

Temperature 1. Check fans


Temperature Too Minor 219 / Eqt
Unacceptable TMPH-SFU 2. Check environment of that
High Alarm SFU On 12 No
TEMP eqpt, add fans

Temperature
High Temperature Major 220 / Eqt Check the fan. Check the
Unacceptable HITEMPWARN-SOHO
Warning SOHO On 3 No ambient temperature.
TEMP

Temperature
High Temperature HITEMPSHUTOFF- Major 220 / Eqt Check the fan. Check the
Unacceptable
Shutoff SOHO SOHO On 4 Yes ambient temperature.
TEMP

Temperature 1. Check fans


Temperature Too Minor 220 / Eqt
Unacceptable TMPH-SOHO 2. Check environment of that
High Alarm SOHO On 12 No
TEMP eqpt, add fans

Temperature
High Temperature Major 221 / Eqt Check the fan. Check the
Unacceptable HITEMPWARN-MDU
Warning MDU On 3 No ambient temperature.
TEMP

Temperature
High Temperature HITEMPSHUTOFF- Major 221 / Eqt Check the fan. Check the
Unacceptable
Shutoff MDU MDU On 4 Yes ambient temperature.
TEMP

Temperature 1. Check fans


Temperature Too Minor 221 / Eqt
Unacceptable TMPH-MDU 2. Check environment of that
High Alarm MDU On 12 No
TEMP eqpt, add fans

Voltage Problem Voltage Too High Minor 129 / Eqt 1. Check board problem
VOLTH
VTP Alarm On 13 No 2. Check sfp module.

Voltage Problem Voltage Too High Minor 219 / Eqt 1. Check board problem
VOLTH-SFU
VTP Alarm SFU On 13 No 2. Check sfp module.

Voltage Problem Voltage Too High Minor 220 / Eqt 1. Check board problem
VOLTH-SOHO
VTP Alarm SOHO On 13 No 2. Check sfp module.

Voltage Problem Voltage Too High Minor 221 / Eqt 1. Check board problem
VOLTH-MDU
VTP Alarm MDU On 13 No 2. Check sfp module.

Table 118-30 describes the ONT CES DS1 service alarms.

Table 118-30 ONT CES DS1 service alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

1. Determine whether problem is due to


DS1 network or equipment problem or
misprovisioning. AIS represents a failure
Receiving upstream in the network where AIS is
Alarm Indication Alarm inserted toward the downstream
Major Comm
Signal Indication CESDS1AISR 64 / 8 equipment to indicate a failure exists
Signal On On Yes upstream.
AIS
DS1 Interface 2. If there is no DS1 network or
equipment problem, check the DS1
provisioning on the far end for valid
traffic path configuration.

The provisioned CES DS1 service was


rejected by the ONT during OMCI
Configuration Or configuration requests.
Customization DS1 Service Minor Eqt 1. Verify the DS1 port service capability
Error CESDS1SVCMIS 64 / 1
Mismatch On Yes of the ONT.
CFG 2. Restart the ONT to see if the problem
persists or delete the unsupported DS1
service port.

Configuration Or CESDS1 line loopback enabled. To


Customization Line Loopback Major Comm
64 / remove the loopback, perform a manual
Error enabled at CESDS1LINLPBK
On 10 Yes command RLS-LPBK-ONTCESUNI to
DS1 Interface
CFG release the loopback.

CESDS1TERLPBK Major Comm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 49 sur 93

Configuration Or Terminal 64 / CESDS1 terminal loopback enabled. To


Customization Loopback On 11 Yes remove the loopback, either generate a
Error enabled at CESDS1 UNLOOP code on the
CFG DS1 Interface CESDS1 interface, or perform a manual
command RLS-LPBK-ONTCESUNI to
release the loopback.

1. Determine whether the problem is


due to physical interface cabling,
Loss Of misprovisioning, or signal from far end
Loss Of Frame Frame On Major Comm DS1 equipment.
DS1 Interface, CESDS1LOF 64 / 3
LOF Fault Code: On Yes 2. If no physical cabling problem exists,
2108 check for misprovisioning of framing
format between equipment. Also check
far-end DS1 transmit capabilities.

1. Determine whether the problem is


Loss Of due to physical interface cabling or due
Loss Of Signal Signal On Major Comm to actual failure of signal from far end
DS1 Interface, CESDS1LOS 64 / 2 DS1 equipment.
LOS Fault Code: On Yes
2107 2. If no physical cabling problem exists,
check far-end DS1 transmit capabilities.

1. Determine whether the problem is


due to physical interface cabling, or bad
Receiving ONT transmit signal. RAI is the result of
Remote Alarm
Remote Alarm Major Comm the far end DS1 equipment detecting a
Indication CESDS1RAIR 64 / 6
Indication On On Yes problem with its receive signal.
RAI DS1 Interface 2. If no physical cabling problem exists,
check far-end DS1 equipment for
alarms and resolve.

Table 118-31 describes the ONT CES E1 service alarms.

Table 118-31 ONT CES E1 service alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

1. Determine whether problem is due to E1


network or equipment problem or
Receiving misprovisioning. AIS represents a failure
Alarm Indication Alarm upstream in the network where AIS is
Major 102 / Comm
Signal Indication CESE1AISR inserted toward the downstream equipment
On 8 Yes to indicate a failure exists upstream.
AIS Signal On E1
Interface 2. If there is no E1 network or equipment
problem, check the E1 provisioning on the
far end for valid traffic path configuration.

The provisioned CES E1 service was


rejected by the ONT during OMCI
Configuration Or configuration requests.
Customization E1 Service Minor 102 / Eqt 1. Verify the E1 port service capability of
Error CESE1SVCMIS
Mismatch On 1 Yes the ONT.
CFG 2. Restart the ONT to see if the problem
persists or delete the unsupported E1
service port.

1. Determine whether the problem is due to


physical interface cabling, misprovisioning,
Loss Of Frame or signal from far end E1 equipment.
Loss Of Frame Major 102 / Comm
On E1 CESE1LOF 2. If no physical cabling problem exists,
LOF On 3 Yes
Interface check for misprovisioning of framing format
between equipment. Also check far-end E1
transmit capabilities.

1. Determine whether the problem is due to


Loss Of Signal physical interface cabling or due to actual
Loss Of Signal Major 102 / Comm
On E1 CESE1LOS failure of signal from far end E1 equipment.
LOS On 2 Yes
Interface 2. If no physical cabling problem exists,
check far-end E1 transmit capabilities.

Remote Alarm Receiving CESE1RAIR Major 102 / Comm 1. Determine whether the problem is due to
Indication Remote Alarm On 6 Yes physical interface cabling, or bad ONT
RAI Indication On transmit signal. RAI is the result of the far
E1 Interface end E1 equipment detecting a problem
with its receive signal.
2. If no physical cabling problem exists,
check far-end E1 equipment for alarms and
resolve.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 50 sur 93

Table 118-32 describes the ONT CES PWE service alarms.

Table 118-32 ONT CES PWE service alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

The provisioned pseudowire


service was rejected by the
ONT during OMCI
Configuration Or configuration requests.
Customization Pseudowire Minor 101 / Eqt 1. Verify the Pseudowire
Error PWESVCMIS
Service Mismatch On 1 Yes (CES) service capability of the
CFG ONT.
2. Restart the ONT to see if
the problem persists, or delete
the unsupported PWE service.

1. Assess whether the


problem is due to a network
Pseudowire problem or a misconfiguration.
Communications
Excessive Frame Major 101 / Comm 2. If no network path problem
Subsystem Failure PWELOSSREORDER
Reordering And On 2 Yes exists, check for
COM Loss misconfiguration of the
pseudowire service between
endpoints.

1. Assess whether the


problem is due to a network
problem or a misconfiguration.
Communications
Pseudowire Jitter Major 101 / Comm 2. If no network path problem
Subsystem Failure PWEJBOVRRUN
Buffer Overrun On 3 Yes exists, check for
COM
misconfiguration of the
pseudowire service between
endpoints.

1. Assess whether the


problem is due to a network
problem or a misconfiguration.
Communications
Pseudowire Jitter Major 101 / Comm 2. If no network path problem
Subsystem Failure PWEJBUNDRUN
Buffer Underrun On 4 Yes exists, check for
COM
misconfiguration of the
pseudowire service between
endpoints.

1. Assess whether the


problem is due to a network
Pseudowire problem or a misconfiguration.
Communications
Excessive Major 101 / Comm 2. If no network path problem
Subsystem Failure PWEMALFORM
Malformed On 5 Yes exists, check for
COM Frames Received misconfiguration of the
pseudowire service between
endpoints.

1. Assess whether the


problem is due to a network
Pseudowire problem or a misconfiguration.
Communications
Excessive Major 101 / Comm 2. If no network path problem
Subsystem Failure PWELATEFRMS
Frames Arriving On 6 Yes exists, check for
COM Late misconfiguration of the
pseudowire service between
endpoints.

1. Assess whether the


problem is due to a network
problem or a misconfiguration.
Communications
Pseudowire Loss Major 101 / Comm 2. If no network path problem
Subsystem Failure PWELINKLOSS
Of Link On 7 Yes exists, check for
COM
misconfiguration of the
pseudowire service between
endpoints.

1/Check the static IP


Communications
Pseudo-wire ARP Major 101 / Comm configuration at ONT.
Subsystem Failure PWEARPFAIL
Failure On 8 Yes 2/ check DS1 PW peer
COM
connectivity.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 51 sur 93

Table 118-33 describes the ONT HPNA service alarms.

Table 118-33 ONT HPNA service alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

The provisioned HPNA service was


rejected by the ONT during OMCI
configuration requests.
Configuration Or
Service Minor Comm Verify HPNA service capability of
Customization Error HPNASVCMIS 169 / 1
Mismatch On Yes ONT.
CFG
Restart ONT to see if problem
persists, or delete unsupported HPNA
service port.

Loss Of Signal Major Comm Determine why not signal on the


- HPNALOS 169 / 2
LOS On Yes HPNA port.

Table 118-34 describes the ONT LAN service alarms.

Table 118-34 ONT LAN service alarms


Default
Probable Category /
Specific TL1 severity / Alarm
cause / Service Repair action
problem condition Default ID
Mnemonic affecting
reporting

The provisioned LAN service was rejected by


Configuration Or the ONT during OMCI configuration requests.
Customization Service Minor Eqt Verify the LAN service capability of the ONT.
Error LANSVCMIS 63 / 1
Mismatch On Yes Restart the ONT to see if the problem
CFG persists or delete the unsupported LAN
service port.

Loss Of Signal Indeterminate Comm


- LANLOS 63 / 2 Validate the input to the Ethernet port.
LOS On Yes

Table 118-35 describes the ONT MoCA service alarms.

Table 118-35 ONT MoCA service alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

Bandwidth Determine why MoCA coaxial interface is


Threshold Limited Link Major Comm degraded. Check the coaxial interface and
Crossed MOCALIMLINK 89 / 3
Bandwidth On Yes signal. Adjust the minimum bandwidth
BW threshold if a lower threshold is acceptable.

The provisioned MoCA UNI service was


Configuration Or rejected by the ONT during OMCI
Customization Service Minor Eqt configuration requests. Verify the MoCA
Error MOCASVCMIS 89 / 1
Mismatch On Yes service capability of the ONT. Restart the
CFG ONT to see if the problem persists or
delete the unsupported MoCA port.

Loss Of Link Major Comm Determine why ONT has lost MoCA coaxial
- MOCALOL 89 / 2
LOL On Yes input signal. Check the signal.

Errored 1. Check the MoCA UNI physical interface


Threshold
Frames T- Warning Qos receive signal.
Crossed 93 / 1
Received At RXERRFRMS On No 2. Check the MoCA CPE equipment and
TCA Near End CPE signal for problems.

Table 118-36 describes the ONT POTS service alarms.

Table 118-36 ONT POTS service alarms


Probable cause / Specific TL1 condition Default Alarm Category / Repair action
Mnemonic problem severity / ID

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 52 sur 93

Service
Default affecting
reporting

The provisioned POTS service


SIP registration failed.
1. Check network connectivity
and configuration.
Application
2. Verify the domain name.
Subsystem SIP Registration Minor Comm
Failure SIPREGFAIL 62 / 6 3. Verify the security
Failure On Yes
authentication credentials.
APPL
4. Check the SIP server
configuration.
5. Deprovision the service if it is
no longer required.

The provisioned POTS service


SIP invite failed.
1. Check the network connectivity
and configuration.
2. Verify the domain name.
Application
Subsystem Minor Comm 3. Verify security authentication
Failure SIP Invite Failure SIPINVITEFAIL 62 / 7 credentials.
On Yes
APPL 4. Check SIP server configuration
(Note: 480 and 486 responses
are not considered failures for
this alarm).
5. Deprovision the service if it is
no longer required.

The provisioned POTS service


SIP subscribe failed.
1. Check network connectivity
and configuration.
Application
2. Verify the domain name.
Subsystem SIP Subscription Warning Comm
Failure SIPSUBFAIL 62 / 8 3. Verify the security
Failure On No
authentication credentials.
APPL
4. Check the SIP server
configuration.
5. Deprovision the service if it is
no longer required.

Application
Subsystem iConfig Minor Comm Domain name is resolved, or
62 /
Failure Subscription PICNFSUBDNS SIPPING address reconfigured to
On 12 Yes
DNS Problem not use a domain name.
APPL

To clear, TCP socket must open


Application iConfig successfully.
Subsystem Subscription Minor 62 / Comm
Failure PICNFSUBTCP Check network connectivity and
TCP Socket On 13 Yes configuration.
APPL Problem
Check POTS configuration.

To clear, TLS session must be


Application established successfully.
Subsystem iConfig Minor Comm
62 /
Failure Subscription TLS PICNFSUBTLS Check network connectivity and
On 14 Yes
Session Problem configuration.
APPL
Check POTS configuration.

To clear, subscription must be


Application iConfig successful or a non-401/407 error
Subsystem Subscription Minor 62 / Comm response is received.
Failure PICNFSUBAUTH
Authentication On 15 Yes Check network connectivity and
APPL Error configuration.
Check the POTS configuration.

To clear, subscribe responses


Application must be received.
Subsystem iConfig Minor Comm
62 /
Failure Subscription PICNFSUBTO Check network connectivity and
On 16 Yes
Timeout configuration.
APPL
Check POTS configuration.

To clear, subscription must be


Application successful.
Subsystem iConfig Minor Comm
62 /
Failure Subscription PICNFSUBERR Check network connectivity and
On 17 Yes
Response Error configuration.
APPL
Check POTS configuration.

iConfig Notify PICNFNOTTO Minor 62 / Comm To clear, any notify must be


Timeout On 18 Yes received for subscription.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 53 sur 93

Application Check network connectivity and


Subsystem configuration.
Failure Check the POTS configuration.
APPL

To clear, any notify must be


Application received for subscription.
Subsystem iConfig Notify Warning 62 / Comm
Failure PICNFNOTREFTO Check network connectivity and
Refresh Timeout On 19 No configuration.
APPL
Check the POTS configuration.

To clear, a valid notify must be


Application received.
Subsystem iConfig Notify Minor Comm
62 /
Failure Response PICNFNOTMAL Check network connectivity and
On 20 Yes
Malformed configuration
APPL
Check the POTS configuration.

To clear, a valid notify must be


Application received.
Subsystem iConfig Notify Minor Comm
62 /
Failure Response PICNFNOTREJ Check network connectivity and
On 21 Yes
Rejected configuration
APPL
Check the POTS configuration.

To clear, domain name must be


resolved or not used in a
Application subsequent document retrieval
Subsystem iConfig HTTP Minor 62 / Comm attempt.
Failure PICNFHTTPDNS
DNS Problem On 22 Yes Check network connectivity and
APPL configuration.
Check the POTS configuration.

To clear, a TCP socket must be


Application opened on a subsequent
Subsystem iConfig HTTP Minor Comm document retrieval attempt.
62 /
Failure TCP Socket PICNFHTTPTCP
On 23 Yes Check network connectivity and
Problem
APPL configuration.
Check the POTS configuration.

To clear, a TLS session must be


Application established on a subsequent
Subsystem iConfig HTTP Minor Comm document retrieval attempt.
62 /
Failure TLS Session PICNFHTTPTLS
On 24 Yes Check network connectivity and
Problem
APPL configuration.
Check the POTS configuration.

To clear, an authentication must


Application be successful on a subsequent
Subsystem iConfig HTTP Minor Comm document retrieval attempt.
62 /
Failure Authentication PICNFHTTPAUTH
On 25 Yes Check network connectivity and
Error
APPL configuration.
Check the POTS configuration.

To clear, a subsequent
Application document retrieval attempt must
Subsystem iConfig HTTP Minor 62 / Comm be successful.
Failure PICNFHTTPTO
Timeout On 26 Yes Check network connectivity and
APPL configuration.
Check the POTS configuration.

To clear, a aubsequent
Application document retrieval attempt must
Subsystem iConfig HTTP Minor 62 / Comm be successful.
Failure PICNFHTTPERR
Response Error On 27 Yes Check network connectivity and
APPL configuration.
Check the POTS configuration.

To clear, a subsequent
Application iConfig HTTP document retrieval attempt must
Subsystem Configuration Minor 62 / Comm
PICNFHTTPMAL be successful.
Failure Document On 28 Yes
Malformed Check the POTS configuration
APPL
document.

To clear, a subsequent
Application document retrieval which
Subsystem iConfig Minor Comm provides sufficient data must
62 /
Failure Configuration PICNFINSUFF occur.
On 29 Yes
Data Insufficient
APPL Check the POTS configuration
document.

SIPREGDNS Minor Comm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 54 sur 93

Application SIP Registration On 161 / Yes The provisioned POTS service


Subsystem DNS Problem 1 SIP registration failed because
Failure domain could not be resolved.
APPL 1. Check network connectivity
and configuration.
2. Verify the domain name.
3. Verify security authentication
credentials.
4. Check the SIP server
configuration.
5. Deprovision the service if it is
no longer required.

The provisioned POTS service


SIP registration failed because
authentication failed between
the ONT and the registration
Application server.
Subsystem SIP Registration Minor Comm
161 / 1. Verify security authentication
Failure Authentication SIPREGAUTH
On 4 Yes credentials.
Failed
APPL
2. Check the SIP server
configuration.
3. Deprovision the service if it is
no longer required.

The provisioned POTS service


SIP registration failed because
all attempted retransmissions
timed out.
1. Check network connectivity
Application and configuration.
Subsystem SIP Registration Minor 161 / Comm
SIPREGTO 2. Verify the domain name.
Failure Timeout On 5 Yes
3. Verify the security
APPL
authentication credentials.
4. Check the SIP server
configuration.
5. Deprovision the service if it is
no longer required.

The provisioned POTS service


SIP registration failed because
there was an error response
from the registration server.
1. Check network connectivity
Application and configuration.
Subsystem SIP Registration Minor 161 / Comm
SIPREGERR 2. Verify the domain name.
Failure Response Error On 6 Yes
3. Verify the security
APPL
authentication credentials.
4. Check the SIP server
configuration.
5. Deprovision the service if it is
no longer required.

The provisioned POTS service


SIP INVITE failed because
domain could not be resolved.
1. Check network connectivity
Application and configuration.
Subsystem SIP Invite DNS Minor 161 / Comm 2. Verify the domain name.
Failure SIPINVITEDNS
Problem On 7 Yes 3. Verify security authentication
APPL credentials.
4. Check the SIP server
configuration.
5. Deprovision the service if it is
no longer required.

The provisioned POTS service


SIP INVITE failed because
authentication failed between
the ONT and the registration
Application server.
Subsystem SIP Invite Minor Comm
161 / 1. Verify security authentication
Failure Authentication SIPINVITEAUTH
On 10 Yes credentials.
Failed
APPL
2. Check the SIP server
configuration.
3. Deprovision the service if it is
no longer required.

Application SIP Invite SIPINVITETO Minor 161 / Comm The provisioned POTS service
Subsystem Timeout On 11 Yes SIP INVITE failed because all
Failure

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 55 sur 93

APPL attempted retransmissions


timed out.
1. Check network connectivity
and configuration.
2. Verify the domain name.
3. Verify security authentication
credentials.
4. Check the SIP server
configuration.
5. Deprovision the service if it
is no longer required.

The provisioned POTS service


SIP INVITE failed because
there was an error response
from the registration server.
1. Check network connectivity
Application and configuration.
Subsystem SIP Invite Minor 161 / Comm
SIPINVITEERR 2. Verify the domain name.
Failure Response Error On 12 Yes
3. Verify security authentication
APPL
credentials.
4. Check the SIP server
configuration.
5. Deprovision the service if it
is no longer required.

To clear, any refresh must be


Application received for subscription.
Subsystem iConfig Warning Comm
161 /
Failure Subscription PICNFSUBREFERR Check network connectivity
On 13 No
Refresh Error and configuration.
APPL
Check POTS configuration.

To clear, a valid notify


Application response for refresh must be
Subsystem iConfig Notify Warning 161 / Comm received for subscription.
Failure PICNFNOTREFERR
Refresh Failed On 14 No Check network connectivity
APPL and configuration.
Check the POTS configuration.

To clear, an iconfig
Application configuration must complete
Subsystem iConfig Minor Comm successfully.
161 /
Failure Configuration PICNFERR
On 15 Yes Check network connectivity
Error
APPL and configuration.
Check the POTS configuration.

The provisioned POTS service


was rejected by the ONT
Configuration Or during OMCI configuration
Customization Minor Eqt requests. Verify the POTS
Service
Error POTSSVCMIS 62 / 1 service capability of the ONT.
Mismatch On Yes Restart the ONT to see if the
CFG problem persists or deprovision
the unsupported POTS service
port.

An active voice call RTCP


packets stream was lost.
Communications 1. Check connectivity with
Subsystem Loss Of RTCP Minor Comm remote POTS interface
Failure RTCPSTREAMLOSS 62 / 2
Stream On No (statistics and QoS data for a
COM call).
2. Check the network
configuration.

The provisioned POTS SIP


message timeout threshold
was crossed during a 15-
minute interval.
Threshold
SIP Message Warning Qos 1. Check network connectivity
Crossed SIPMSGTMOUTTCA 62 / 9
Timeouts On No and configuration.
TCA
2. Check the SIP server
configuration.
3. Deprovision the service if it
is no longer required.

Threshold RTP Bearer RTPPKTLOSSTCA Warning 62 / Qos The POTS service RTP Bearer
Crossed Packet Loss On 10 No packet threshold crossed.
TCA 1. Check network connectivity
and configuration.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 56 sur 93

2. Check connectivity with the


remote POTS interface.

The POTS service Jitter


threshold has been crossed.
Threshold
Warning 62 / Qos 1. Check network connectivity
Crossed RTP Jitter JITTERTCA
On 11 No and configuration.
TCA
2. Check connectivity with
remote the POTS interface.

Table 118-37 describes the ONT VDSL2 service alarms.

Table 118-37 ONT VDSL2 service alarms


Default
Probable Category /
Specific TL1 severity / Alarm
cause / Service Repair action
problem condition Default ID
Mnemonic affecting
reporting

The provisioned VDSL2 service was


Configuration Or rejected by the ONT during OMCI
Customization Service Minor 118 / Eqt configuration requests. Verify the XDSL
Error XDSLSVCMIS
Mismatch On 1 Yes service capability of the ONT. Restart the
CFG ONT to see if the problem persists or
delete the unsupported xDSL service port.

The provisioned VDSL2 service was


Configuration Or rejected by the ONT during post OMCI
Customization XDSL Minor Eqt
118 / processing. Verify the xDSL service
Error Configuration XDSLCNFG
On 9 Yes capability of the ONT, CPE modem, and
Error
CFG consistency of the provisioning
parameters.

Configuration Init Configuration Minor 118 / Comm Check the ONT/MDU xDSL receive signal
Failure Init Failure At LINEINIT
On 4 Yes and the CPE equipment for problems.
CIF Near End

Loss Of Frame Loss Of Frame Minor 118 / Comm Check the ONT/MDU xDSL receive signal
XLOF
LOF At Near End On 2 Yes and the CPE equipment for problems.

Loss Of Link Loss Of Link At Minor 118 / Comm Check the ONT/MDU xDSL receive signal
XLOL
LOL Near End On 5 Yes and the CPE equipment for problems.

Loss Of Signal Loss Of Signal Minor 118 / Comm Check the ONT/MDU xDSL receive signal
XLOS
LOS At Near End On 3 Yes and the CPE equipment for problems.

1. Check the xDSL UNI physical interface


Threshold Errored Warning 119 / Qos receive signal.
Crossed Seconds Near T-ES
On 1 No 2. Check the CPE equipment and CPE
TCA End
signal for problems.

Severely 1. Check the xDSL UNI physical interface


Threshold
Errored Warning 119 / Qos receive signal.
Crossed T-SES
Seconds Near On 2 No 2. Check the CPE equipment and CPE
TCA End signal for problems.

1. Check the xDSL UNI physical interface


Threshold Unavailable Warning 119 / Qos receive signal.
Crossed Seconds Near T-UAS
On 3 No 2. Check the CPE equipment and CPE
TCA End
signal for problems.

Table 118-38 describes the ONT VDSL2 far-end service alarms.

Table 118-38 ONT VDSL2 far-end service alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Loss Of Frame Minor Comm Check the CPE equipment and


Loss Of Frame At
XLOF 118 / 6 the CPE receive signal for
LOF Far End On Yes problems.

Loss Of Power Loss Of Power At XLOP Minor 118 / 8 Comm Check the CPE equipment and
LOPW Far End On Yes the CPE receive signal for
problems.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 57 sur 93

Loss Of Signal Minor Comm Check the CPE equipment and


Loss Of Signal At
XLOS 118 / 7 the CPE receive signal for
LOS Far End On Yes problems.

1. Check the xDSL UNI physical


Threshold
Errored Seconds Far Warning Qos interface receive signal.
Crossed T-ES 119 / 4
End On No 2. Check the CPE equipment and
TCA
CPE signal for problems.

1. Check the xDSL UNI physical


Threshold
Severely Errored Warning Qos interface receive signal.
Crossed T-SES 119 / 5
Seconds Far End On No 2. Check the CPE equipment and
TCA
CPE signal for problems.

1. Check the xDSL UNI physical


Threshold
Unavailable Warning Qos interface receive signal.
Crossed T-UAS 119 / 6
Seconds Far End On No 2. Check the CPE equipment and
TCA
CPE signal for problems.

Table 118-39 describes the ONT video ANI service alarms.

Table 118-39 ONT video ANI service alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

The provisioned video ANI service was


Configuration Or rejected by the ONT during OMCI
Customization Video ANI Minor Eqt configuration requests. Verify RF Video
Error Service VIDEOANISVCMIS 86 / 1
On Yes Overlay service capability of ONT.
Mismatch
CFG Restart ONT to see if problem persists,
or delete unsupported Video port.

Communications Determine why the ONT has lost the


Video Loss Major Comm
Subsystem Failure VIDEOLOS 86 / 2 RF video input signal. Check the video
Of Signal On Yes
COM signal.

Signal Power Video


Optical Major Comm Check the RF video signal and
Problem LEVELHIGH 86 / 3
Signal Level On Yes decrease the signal level.
SPWR Too High

Signal Power Video


Optical Major Comm Check the RF video signal and
Problem LEVELLOW 86 / 4
Signal Level On Yes increase the signal level.
SPWR Too Low

Table 118-40 describes the ONT video service alarms.

Table 118-40 ONT video service alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

Configuration Or The provisioned video service was


Customization Minor Eqt rejected by the ONT during OMCI
Service
Error VIDEOUNISVCMIS 61 / 1 configuration requests. Restart the
Mismatch On Yes ONT to see if the problem persists or
CFG delete the unsupported video service.

1. Verify whether the RF Video output


level is too high.
Signal Power RF Video 2. If level is too high, replace the failing
Output Power Major Eqt
Problem RFOUTHIGH 61 / 3 ONT.
Level Too On Yes
SPWR High 3. Else reset the ONT.
4. Replace the ONT if the failure
persists.

Signal Power RF Video RFOUTLOW Major 61 / 4 Eqt 1. Verify whether the RF Video output
Problem Output Power On Yes level is too low.
SPWR Level Too 2. If level is too low, replace the failing
Low ONT.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 58 sur 93

3. Else reset the ONT.


4. Replace the ONT if the failure
persists.

Table 118-41 describes the ONT VoIP service alarms.

Table 118-41 ONT VoIP service alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

This alarm indicates


misprovisioning, a network
Application connectivity issue, or a problem
Major Comm
Subsystem Failure DHCP Timeout VDHCPTO 67 / 8 with the server.
On Yes
APPL Check provisioning, network
connectivity, and server
configuration.

This alarm indicates


misprovisioning, a network
Application connectivity issue, or a problem
DHCP Response Major Comm
Subsystem Failure VDHCPMAL 67 / 9 with the server.
Malformed On Yes
APPL Check provisioning, network
connectivity, and server
configuration.

This alarm indicates


misprovisioning, a network
Application connectivity issue, or a problem
DHCP No IP Major 67 / Comm
Subsystem Failure VDHCPNOADD with the server.
Address On 10 Yes
APPL Check provisioning, network
connectivity, and server
configuration.

This alarm indicates


misprovisioning, a network
Application connectivity issue, or a problem
DHCP Renew Minor 67 / Comm
Subsystem Failure VDHCPLEASE with the server.
Lease Failed On 11 No
APPL Check provisioning, network
connectivity, and server
configuration.

Application iConfig Domain name is resolved, or


Major 67 / Comm
Subsystem Failure Subscription DNS VICNFSUBDNS SIPPING address reconfigured
On 12 Yes
APPL Problem to not use a domain name.

To clear, the TCP socket must


open successfully.
Application iConfig Major 67 / Comm Check network connectivity and
Subsystem Failure Subscription TCP VICNFSUBTCP
On 13 Yes configuration.
APPL Socket Problem
Check the voice client
configuration.

To clear, TLS session must be


established successfully.
Application iConfig Major 67 / Comm Check network connectivity and
Subsystem Failure Subscription TLS VICNFSUBTLS
On 14 Yes configuration.
APPL Session Problem
Check the voice client
configuration.

To clear, subscription must be


successful or a non-401/407
Application iConfig error response is received.
Subscription Major 67 / Comm
Subsystem Failure VICNFSUBAUTH Check network connectivity and
Authentication On 15 Yes
APPL configuration.
Error
Check the voice client
configuration.

To clear, subscribe responses


must be received.
Application iConfig Major 67 / Comm Check network connectivity and
Subsystem Failure Subscription VICNFSUBTO
On 16 Yes configuration.
APPL Timeout
Check the voice client
configuration.

Application VICNFSUBERR Major 67 / Comm To clear, subscription must be


Subsystem Failure On 17 Yes successful.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 59 sur 93

APPL iConfig Check network connectivity and


Subscription configuration.
Response Error Check the voice client
configuration.

To clear, any notify must be


received for subscription.
Application
iConfig Notify Major 67 / Comm Check network connectivity and
Subsystem Failure VICNFNOTTO
Timeout On 18 Yes configuration.
APPL
Check the voice client
configuration.

To clear, any notify must be


received for subscription.
Application
iConfig Notify Warning 67 / Comm Check network connectivity and
Subsystem Failure VICNFNOTREFTO
Refresh Timeout On 19 No configuration.
APPL
Check the voice client
configuration.

To clear, a valid notify must be


received.
Application iConfig Notify Major 67 / Comm Check network connectivity and
Subsystem Failure Response VICNFNOTMAL
On 20 Yes configuration.
APPL Malformed
Check the voice client
configuration.

To clear, a valid notify must be


received.
Application iConfig Notify Major 67 / Comm Check network connectivity and
Subsystem Failure Response VICNFNOTREJ
On 21 Yes configuration.
APPL Rejected
Check the voice client
configuration.

To clear, domain name must be


resolved or not used in a
subsequent document retrieval
Application attempt.
iConfig HTTP Major 67 / Comm
Subsystem Failure VICNFHTTPDNS
DNS Problem On 22 Yes Check network connectivity and
APPL configuration.
Check the voice client
configuration.

To clear, a TCP socket must be


opened on a subsequent
Application iConfig HTTP document retrieval attempt.
Major 67 / Comm
Subsystem Failure TCP Socket VICNFHTTPTCP Check network connectivity and
On 23 Yes
APPL Problem configuration.
Check vvoice client
configuration.

To clear, a TLS session must be


established on a subsequent
Application iConfig HTTP document retrieval attempt.
Major 67 / Comm
Subsystem Failure TLS Session VICNFHTTPTLS Check network connectivity and
On 24 Yes
APPL Problem configuration.
Check vvoice client
configuration.

To clear, an authentication must


be successful on a subsequent
Application iConfig HTTP document retrieval attempt.
Major 67 / Comm
Subsystem Failure Authentication VICNFHTTPAUTH Check network connectivity and
On 25 Yes
APPL Error configuration.
Check the voice client
configuration.

To clear, a subsequent
document retrieval attempt must
Application be successful.
iConfig HTTP Major 67 / Comm
Subsystem Failure VICNFHTTPTO Check network connectivity and
Timeout On 26 Yes
APPL configuration.
Check vvoice client
configuration.

Application iConfig HTTP VICNFHTTPERR Major 67 / Comm To clear, a subsequent


Subsystem Failure Response Error On 27 Yes document retrieval attempt must
APPL be successful.
Check network connectivity and
configuration.
Check the voice client
configuration.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 60 sur 93

To clear, a subsequent
Application iConfig HTTP document retrieval attempt
Configuration Major 67 / Comm
Subsystem Failure VICNFHTTPMAL must be successful.
Document On 28 Yes
APPL Malformed Check the voice client
configuration document.

To clear, any refresh must be


received for subscription.
Application iConfig Warning 67 / Comm Check network connectivity and
Subsystem Failure Subscription VICNFSUBREFERR
On 29 No configuration.
APPL Refresh Error
Check the voice client
configuration.

To clear, a valid notify response


for receive must be received for
Application subscription.
iConfig Notify Warning 67 / Comm
Subsystem Failure VICNFNOTREFERR Check network connectivity and
Refresh Failed On 30 No
APPL configuration.
Check the voice client
configuration.

To clear, an iconfig
configuration must complete
Application iConfig successfully.
Major 67 / Comm
Subsystem Failure Configuration VICNFERR Check network connectivity and
On 31 Yes
APPL Error configuration.
Check the voice client
configuration.

The voice provisioning file


failed to be downloaded to the
Configuration Or ONT.
Customization VoIP Major Comm
Configuration File VOIPCNFG 67 / 1 1. Check for connectivity to the
Error On Yes
Error FTP server.
CFG
2. Check the format of the file.
3. Verify the specified filename.

Either the ONT or LT did not


accept the configuration
requests for the provisioned
voice client service. Possible
reasons for the alarm:
Configuration Or a) The service is not supported
Customization Voice Client Minor Eqt by the ONT.
Error VCLIENTSVCMIS 67 / 2
Service Mismatch On Yes b) LT configuration or setup
CFG problem.
Possible solutions are to restart
the ONT, restart the LT or to
deprovision the voice client
service since it is not
supported.

The voice gateway cannot be


Communications reached by the ONT voice
Voice Gateway Major Comm
Subsystem Failure VGATEWAYCOMM 67 / 3 client software. Check the
Unreachable On Yes
COM network connectivity and
configuration.

This alarm indicates a


provisioning error, a network
Equipment Voice Network connectivity issue, or a problem
Major Comm
Malfunction Error, DHCP or VNTWKERR 67 / 4 with the server. Check
PPPoE Problem On Yes provisioning, network
EQP
connectivity, and server
configuration.

Table 118-42 describes the ONT-board alarms.

Table 118-42 ONT-Board alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

Configuration Or Missing LIMMISSING Major 60 / 1 Eqt Install the missing ONT card or
Customization Planned On Yes deprovision the ONT card and
Error Board services if they are no longer
CFG supported.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 61 sur 93

Configuration Or
Customization Invalid Board Major Eqt
Error LIMMEA 60 / 2 Install the correct type of ONT card.
Type On Yes
CFG

Configuration Or Install the missing ONT card or


Customization Board Major Eqt deprovision the ONT card and
Error LIMIMPROPRMVL 60 / 3
Removed On Yes services if they are no longer
CFG supported.

Configuration Or The provisioned card was rejected


Customization Major Eqt by the ONT during OMCI
Service
Error LIMSVCMIS 60 / 6 configuration requests. Restart the
Mismatch On Yes ONT to see if the problem persists
CFG or delete the unsupported card.

Configuration Or 1. Install an ONT card with the


Customization Physical Major Eqt correct number of ports.
Error Equipment LIMNUMPORTSMIS 60 / 7
Error On Yes 2. Re-provision the ONT card with
CFG the correct number of ports.

Equipment Board Failure Major Eqt


Malfunction Or Self Test LIMFAIL 60 / 4 Replace the failed ONT card.
Failed On Yes
EQP

Table 118-43 describes the ONT Ethernet alarms.

Table 118-43 ONT Ethernet alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

1. Check the receive PON


signal at the ONT.
2. Check the transmit PON
signal at the OLT.
Threshold
Ethernet Frames T- Warning Qos 3. Reset the ONT.
Crossed 91 / 1
Dropped Downstream DSDRPDFRMS On No 4. Replace the ONT if the PM
TCA
counts persist.
5. Replace the associated LT
at the OLT if the PM counts
persist.

1. Check the PON signal at


the ONT.
Threshold 2. Check the UNI interface
Ethernet Frames T- Warning Qos
Crossed 91 / 2 physical signal.
Dropped Upstream USDRPDFRMS On No
TCA 3. Reset the ONT.
4. If the PM counts persist,
replace the ONT.

Table 118-44 describes the ONT MDU alarms.

Table 118-44 ONT MDU alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

1. Try another activation


(change the planned version to
be the currently passive
Configuration Or version).
Customization Software Activation SWACTFAIL- Major 168 / Eqt
Error 2. Manually clear the alarm
Failure MDU MDU On 9 Yes (change the planned version to
CFG the wildcard).
3. Contact your Alcatel-Lucent
technical support representative.

Configuration Or Software Download SWDLIP-MDU Minor 168 / Eqt This is a transient alarm that
Customization In Progress MDU On 11 No clears after the download is
Error finished.
CFG

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 62 sur 93

Either change the provisioned


Configuration Or version ID to match the
Customization Equipment Version EQVERMIS- Major 168 / Eqt reported version ID, or change
Error Mismatch MDU MDU On 12 Yes the physical ONT so that the
CFG reported version ID to match
the provisioned version ID.

Either make the active software


Configuration Or version equal to the planned
Customization Minor Eqt version through a successful
Software Version 168 /
Error SWVER-MDU activation, or make the planned
Mismatch MDU On 16 No software version equal to the
CFG active version using an operator
update.

Configuration Or Provisioned parameters failed


Customization ONT Provisioning Major 168 / Eqt to be provisioned in the ONT.
Error ONTMEA-MDU
Failure MDU On 23 Yes Delete the ONT and provision it
CFG again.

Non-service-affecting
Configuration Or provisioned parameters failed
Customization Minor Eqt to be provisioned in the ONT.
Configuration ONTNSAMEA- 168 /
Error Check the supported
Mismatch MDU MDU On 31 No capabilities of the ONT and
CFG deprovision unsupported
features.

The ONT has never been able


to reach and get the time from
an NTP server. A 30-minute
alarm declaration interval is
started when the NTP and VoIP
clients are both enabled, and
ends as soon as the ONT syncs
Synchronization with the NTP server. Note: if the
Network Timing Minor 168 / Comm ONT successfully gets the time
Source Mismatch NTPERR-MDU
Protocol Error MDU On 28 No from an NTP server, and then
CLK
loses contact with it, the alarm
is not raised. To troubleshoot:
1. Check the NTP server
accessibility and ONT
provisioning configuration.
2. Restart the ONT to see if the
alarm returns.

1. Check the receive signal at


Communications the ONT.
Loss Of PLOAM Major 167 / Comm
Subsystem Failure LOAM-MDU 2. Reset the ONT.
MDU On 20 Yes
COM 3. If the Loss of PLOAM
persists, replace the ONT.

Check the quality of the line


Communications from the ONT if the condition
Drift Of Window Major 167 / Comm persists. The OLT received a
Subsystem Failure DOW-MDU
MDU On 21 Yes transmission from the ONT at
COM an unexpected place within the
upstream virtual frame.

1. Check the connectivity


between the OLT and ONT that
is resulting in a loss of key
Communications Loss Of Key Major 167 / Comm exchange PLOAM message
Subsystem Failure Synchronization LOKS-MDU
On 24 Yes between the OLT and ONT.
COM MDU
2. Reset the ONT. If the
condition persists, replace the
ONT.

Reset ONT by administratively


Communications putting it OOS and then IS.
Rogue ONT ROGUEONTDIS Major 167 / Comm
Subsystem Failure If the alarm occurs again, the
Disabled (MDU) -MDU On 26 Yes
COM ONT must likely be physically
repaired or swapped.

ONT has been deactivated


because its location on the
Communications
Differential Reach DIFREACH- Major 167 / Comm PON has exceeded its
Subsystem Failure
Exceeded (MDU) MDU On 27 No differential reach capability.
COM
Alarm is cleared when ONT is
disconnected from PON.

OMCI Failure MDU Major Comm Attempt to restart the ONT.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 63 sur 93

Communications OMCICOMM- On 168 / Yes


Subsystem Failure MDU 1
COM

Enclosure Door Investigate the ONT for


Enclosure Door INTRUDER- Major 168 / Comm
Open possible illegal physical
Open MDU MDU On 7 No
DOOR access to ONT (MDU).

MDU
Environmental MDU Indeterminate Env Verify that the external
168 /
Alarm 1 Environmental ENV1-MDU equipment is connected to
On 24 No
Alarm 1 MDU Alarm Input 1.
ENV-1

MDU
Environmental MDU Indeterminate Env Verify that the external
168 /
Alarm 2 Environmental ENV2-MDU equipment is connected to
On 25 No
Alarm 2 MDU Alarm Input 2.
ENV-2

MDU
Environmental MDU Indeterminate Env Verify that the external
168 /
Alarm 3 Environmental ENV3-MDU equipment is connected to
On 26 No
Alarm 3 MDU Alarm Input 3.
ENV-3

Equipment Physical Major 167 / Comm


Malfunction Equipment Error PEE-MDU Perform loopback tests.
On 6 Yes
EQP MDU

Reset the ONT by


Equipment administratively putting it OOS
Defense Action ONTDISABLED- Major 167 / Comm and then IS. If the alarm
Malfunction
MDU MDU On 12 Yes occurs again, the ONT most
EQP likely needs to be physically
repaired or replaced.

Equipment
Device Not Active Major 167 / Comm The ONT needs to be ranged
Malfunction INACT-MDU
MDU On 15 Yes (made active).
EQP

Equipment Check the quality of the line


Major 167 / Comm
Malfunction Signal Failure MDU SF-MDU from the ONT. Signal Fail BER
On 17 Yes
EQP exceeded.

Equipment Restore power to the ONT.


Minor 167 / Comm The dying gasp indication is
Malfunction Dying Gasp MDU DG-MDU
On 18 Yes due to a loss of power input to
EQP the ONT.

Equipment 1. Reset the ONT.


Deactivation Major 167 / Comm
Malfunction DF-MDU 2. Replace the ONT if the
Failure MDU On 19 Yes
EQP Deactivation Failure persists.

Equipment Command another ONT self-


Self Test Failed Major 168 / Eqt
Malfunction EQPT-MDU test. If it fails, implement
MDU On 2 Yes
EQP creative diagnostics.

Loss Of Cell Or Loss Of Cell Or Major 167 / Comm Check the quality of the line
Packet Delineation Packet Delineation LCD-MDU
On 4 Yes from the ONT.
LCD MDU

Loss Of Loss Of See if the specific ONT is


Major 167 / Comm
Acknowledgement Acknowledgement LOA-MDU isolated. If it is not, this is likely
On 2 Yes
LOA MDU a software error.

Loss Of Signal Loss Of Signal Major 167 / Comm Check the received signal at
LOS-MDU
LOS MDU On 1 Yes the ONT.

Message Error See if the specific ONT is


Message Error Major 167 / Comm
Message MEM-MDU isolated. If it is not, this is likely
Message MDU On 13 Yes
MEM a software error.

Extraneous power bursts have


been detected for this ONT.
This alarm clears automatically
Power Problem ONT Power Up ONTPWRERR- Minor 167 / Comm after 15 minutes.
PWR Error MDU MDU On 25 No 1. Replace the ONT.
2. Change the power burst
detection mode at the system
level to normal soak mode.

Power Problem ACFAIL-MDU Minor Env

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 64 sur 93

External Power 168 / Wait for power to return to the


PWR Failure MDU On 3 No ONT.

Power Problem Minor Eqt Change the provisioning, or


Battery Missing BATTMISS- 168 /
determine why the battery is
PWR MDU MDU On 4 No missing.

Power Problem Minor Eqt If power is present, determine


168 /
Battery Low MDU BATTLOW-MDU why the battery does not
PWR On 5 No charge, or why it is low.

Power Problem Battery Failure Minor 168 / Eqt The customer needs to
BATTFAIL-MDU
PWR MDU On 6 No replace the battery.

Remote Defect Check the receive signal at


Remote Defect Major 167 / Comm the ONT. The OLT
Indication RDI-MDU
Indication MDU On 22 Yes transmission was received
RDI with errors at the ONT.

Degraded Signal Degraded Signal Major 167 / Comm Check the quality of the line
SD-MDU
SIGN MDU On 9 Yes from the ONT.

Signal Power Received MDU Check the received optical


Major 168 / Comm
Problem Optical Signal LEVELHI-MDU signal and decrease the
On 29 Yes
SPWR Level Too High signal level.

Signal Power Received MDU Check the received optical


Major 168 / Comm
Problem Optical Signal LEVELLO-MDU signal and increase the signal
On 30 Yes
SPWR Level Too Low level.

Startup Failure Startup Failure Major 167 / Comm


SUF-MDU Re-range the ONT.
SUF MDU On 7 Yes

1. Ensure that the planned


ONT software version is
physically present on the
OLT.
Software Software 2. Retry the download again.
SWDLFAIL- Minor 168 / Eqt
Download Failure Download Failure 3. Manually clear the alarm
MDU On 8 No
SWDL MDU (for example, change the
planned version to the
wildcard). Contact your
Alcatel-Lucent technical
support representative.

Table 118-45 describes the ONT SFU alarms.

Table 118-45 ONT SFU alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

1. Try another activation (change


the planned version to be the
Configuration Or currently passive version).
Customization Software Activation SWACTFAIL- Major 164 / Eqt 2. Manually clear the alarm (change
Error Failure SFU SFU On 9 Yes the planned version to the
CFG wildcard).
3. Contact your Alcatel-Lucent
technical support representative.

Configuration Or
Customization Software Download Minor 164 / Eqt This is a transient alarm that clears
Error SWDLIP-SFU
In Progress SFU On 11 No after the download is finished.
CFG

Configuration Or Either change the provisioned


Customization Major Eqt version ID to match the reported
Equipment Version EQVERMIS- 164 /
Error version ID, or change the physical
Mismatch SFU SFU On 12 Yes ONT so that the reported version ID
CFG to match the provisioned version ID.

Configuration Or Software Version SWVER-SFU Minor 164 / Eqt Either make the active software
Customization Mismatch SFU On 16 No version equal to the planned
Error version through a successful
CFG activation, or make the planned
software version equal to the active
version using an operator update.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 65 sur 93

Configuration Or
Customization Major Eqt Provisioned parameters failed to
ONT Provisioning 164 /
Error ONTMEA-SFU be provisioned in the ONT. Delete
Failure SFU On 23 Yes the ONT and provision it again.
CFG

Non-service-affecting provisioned
Configuration Or parameters failed to be
Customization Configuration ONTNSAMEA- Minor 164 / Eqt provisioned in the ONT. Check the
Error Mismatch SFU SFU On 31 No supported capabilities of the ONT
CFG and deprovision unsupported
features.

The ONT has never been able to


reach and get the time from an
NTP server. A 30-minute alarm
declaration interval is started when
the NTP and VoIP clients are both
enabled, and ends as soon as the
ONT syncs with the NTP server.
Synchronization Note: if the ONT successfully gets
Network Timing Minor 164 / Comm the time from an NTP server, and
Source Mismatch NTPERR-SFU
Protocol Error SFU On 28 No then loses contact with it, the
CLK
alarm is not raised. To
troubleshoot:
1. Check the NTP server
accessibility and ONT provisioning
configuration.
2. Restart the ONT to see if the
alarm returns.

1. Check the receive signal at the


Communications ONT.
Loss Of PLOAM Major 163 / Comm
Subsystem Failure LOAM-SFU 2. Reset the ONT.
SFU On 20 Yes
COM 3. If the Loss of PLOAM persists,
replace the ONT.

Check the quality of the line from


Communications the ONT if the condition persists.
Drift Of Window Major 163 / Comm The OLT received a transmission
Subsystem Failure DOW-SFU
SFU On 21 Yes from the ONT at an unexpected
COM place within the upstream virtual
frame.

1. Check the connectivity between


the OLT and ONT that is resulting
Communications Loss Of Key in a loss of key exchange PLOAM
Major 163 / Comm
Subsystem Failure Synchronization LOKS-SFU message between the OLT and
On 24 Yes ONT.
COM SFU
2. Reset the ONT. If the condition
persists, replace the ONT.

Reset ONT by administratively


Communications putting it OOS and then IS.
Rogue ONT ROGUEONTDIS Major 163 / Comm
Subsystem Failure If the alarm occurs again, the ONT
Disabled (SFU) -SFU On 26 Yes
COM must likely be physically repaired
or swapped.

ONT has been deactivated


because its location on the PON
Communications
Differential Reach Major 163 / Comm has exceeded its differential reach
Subsystem Failure DIFREACH-SFU
Exceeded (SFU) On 27 No capability.
COM
Alarm is cleared when ONT is
disconnected from PON.

Communications
OMCICOMM- Major 164 / Comm
Subsystem Failure OMCI Failure SFU Attempt to restart the ONT.
SFU On 1 Yes
COM

Equipment
Physical Equipment Major 163 / Comm
Malfunction PEE-SFU Perform loopback tests.
Error SFU On 6 Yes
EQP

Reset the ONT by administratively


Equipment putting it OOS and then IS. If the
Defense Action ONTDISABLED- Major 163 / Comm
Malfunction alarm occurs again, the ONT most
SFU SFU On 12 Yes
EQP likely needs to be physically
repaired or replaced.

Equipment Device Not Active INACT-SFU Major 163 / Comm The ONT needs to be ranged
Malfunction SFU On 15 Yes (made active).
EQP

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 66 sur 93

Equipment Check the quality of the line from


Major 163 / Comm
Malfunction Signal Failure SFU SF-SFU the ONT. Signal Fail BER
On 17 Yes
EQP exceeded.

Equipment Restore power to the ONT. The


Minor 163 / Comm
Malfunction Dying Gasp SFU DG-SFU dying gasp indication is due to a
On 18 Yes
EQP loss of power input to the ONT.

Equipment 1. Reset the ONT.


Deactivation Major 163 / Comm
Malfunction DF-SFU 2. Replace the ONT if the
Failure SFU On 19 Yes
EQP Deactivation Failure persists.

Equipment Command another ONT self-test.


Self Test Failed Major 164 / Eqt
Malfunction EQPT-SFU If it fails, implement creative
SFU On 2 Yes
EQP diagnostics.

Loss Of Cell Or Loss Of Cell Or Major 163 / Comm Check the quality of the line from
Packet Delineation Packet Delineation LCD-SFU
On 4 Yes the ONT.
LCD SFU

Loss Of Loss Of See if the specific ONT is


Major 163 / Comm
Acknowledgement Acknowledgement LOA-SFU isolated. If it is not, this is likely a
On 2 Yes
LOA SFU software error.

Loss Of Signal Major 163 / Comm Check the received signal at the
Loss Of Signal SFU LOS-SFU
LOS On 1 Yes ONT.

Message Error See if the specific ONT is


Message Error Major 163 / Comm
Message MEM-SFU isolated. If it is not, this is likely a
Message SFU On 13 Yes
MEM software error.

Extraneous power bursts have


been detected for this ONT. This
alarm clears automatically after
Power Problem ONT Power Up ONTPWRERR- Minor 163 / Comm 15 minutes.
PWR Error SFU SFU On 25 No 1. Replace the ONT.
2. Change the power burst
detection mode at the system
level to normal soak mode.

Power Problem External Power Minor 164 / Env Wait for power to return to the
ACFAIL-SFU
PWR Failure SFU On 3 No ONT.

Power Problem Minor Eqt Change the provisioning, or


Battery Missing 164 /
BATTMISS-SFU determine why the battery is
PWR SFU On 4 No missing.

Power Problem Minor Eqt If power is present, determine


164 /
Battery Low SFU BATTLOW-SFU why the battery does not charge,
PWR On 5 No or why it is low.

Power Problem Minor 164 / Eqt The customer needs to replace


Battery Failure SFU BATTFAIL-SFU
PWR On 6 No the battery.

Remote Defect Check the receive signal at the


Remote Defect Major 163 / Comm
Indication RDI-SFU ONT. The OLT transmission was
Indication SFU On 22 Yes
RDI received with errors at the ONT.

Degraded Signal Degraded Signal Major 163 / Comm Check the quality of the line from
SD-SFU
SIGN SFU On 9 Yes the ONT.

Signal Power Received SFU Major 164 / Comm Check the received optical signal
Problem Optical Signal LEVELHI-SFU
On 29 Yes and decrease the signal level.
SPWR Level Too High

Signal Power Received SFU Major 164 / Comm Check the received optical signal
Problem Optical Signal LEVELLO-SFU
On 30 Yes and increase the signal level.
SPWR Level Too Low

Startup Failure Startup Failure Major 163 / Comm


SUF-SFU Re-range the ONT.
SUF SFU On 7 Yes

Software Software Download SWDLFAIL-SFU Minor 164 / Eqt 1. Ensure that the planned ONT
Download Failure Failure SFU On 8 No software version is physically
SWDL present on the OLT.
2. Retry the download again.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 67 sur 93

3. Manually clear the alarm (for


example, change the planned
version to the wildcard). Contact
your Alcatel-Lucent technical
support representative.

Table 118-46 describes the ONT-SNMP alarms.

Table 118-46 ONT-SNMP alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

A condition meaning that either the ONT


did not accept the configuration requests
for the provisioned ont snmp agent.
Configuration Or Possible reasons are:
Customization ONT SNMP Minor Comm
ONTSNMPMIS 205 / 1 1. It is not supported by the ONT.
Error Mismatch On Yes
2. Some parameters are not proper.
CFG
Possible solutions are to restart ONT,
restart LT, or to deprovision the ont snmp
agent since not supported

Table 118-47 describes the ONT SOHO alarms.

Table 118-47 ONT SOHO alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

1. Try another activation (change


the planned version to be the
Configuration Or currently passive version).
Customization Software Activation SWACTFAIL- Major 166 / Eqt 2. Manually clear the alarm (change
Error Failure SOHO SOHO On 9 Yes the planned version to the
CFG wildcard).
3. Contact your Alcatel-Lucent
technical support representative.

Configuration Or
Customization Software Download Minor 166 / Eqt This is a transient alarm that clears
Error SWDLIP-SOHO
In Progress SOHO On 11 No after the download is finished.
CFG

Either change the provisioned


Configuration Or version ID to match the reported
Customization Equipment Version EQVERMIS- Major 166 / Eqt version ID, or change the physical
Error Mismatch SOHO SOHO On 12 Yes ONT so that the reported version ID
CFG to match the provisioned version
ID.

Either make the active software


Configuration Or version equal to the planned
Customization Software Version Minor 166 / Eqt version through a successful
Error SWVER-SOHO
Mismatch SOHO On 16 No activation, or make the planned
CFG software version equal to the active
version using an operator update.

Configuration Or
Customization Major Eqt Provisioned parameters failed to be
ONT Provisioning 166 /
Error ONTMEA-SOHO provisioned in the ONT. Delete the
Failure SOHO On 23 Yes ONT and provision it again.
CFG

Configuration Or Non-service-affecting provisioned


Customization Minor Eqt parameters failed to be provisioned
Configuration ONTNSAMEA- 166 /
Error in the ONT. Check the supported
Mismatch SOHO SOHO On 31 No capabilities of the ONT and
CFG deprovision unsupported features.

Synchronization Network Timing NTPERR-SOHO Minor 166 / Comm The ONT has never been able to
Source Mismatch Protocol Error On 28 No reach and get the time from an NTP
CLK SOHO server. A 30-minute alarm
declaration interval is started when
the NTP and VoIP clients are both
enabled, and ends as soon as the

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 68 sur 93

ONT syncs with the NTP server.


Note: if the ONT successfully gets
the time from an NTP server, and
then loses contact with it, the
alarm is not raised. To
troubleshoot:
1. Check the NTP server
accessibility and ONT provisioning
configuration.
2. Restart the ONT to see if the
alarm returns.

1. Check the receive signal at the


Communications ONT.
Loss Of PLOAM Major 165 / Comm
Subsystem Failure LOAM-SOHO 2. Reset the ONT.
SOHO On 20 Yes
COM 3. If the Loss of PLOAM persists,
replace the ONT.

Check the quality of the line from


Communications the ONT if the condition persists.
Drift Of Window Major 165 / Comm The OLT received a transmission
Subsystem Failure DOW-SOHO
SOHO On 21 Yes from the ONT at an unexpected
COM place within the upstream virtual
frame.

1. Check the connectivity between


the OLT and ONT that is resulting
Communications Loss Of Key in a loss of key exchange PLOAM
Major 165 / Comm
Subsystem Failure Synchronization LOKS-SOHO message between the OLT and
On 24 Yes ONT.
COM SOHO
2. Reset the ONT. If the condition
persists, replace the ONT.

Reset ONT by administratively


Communications putting it OOS and then IS.
Rogue ONT ROGUEONTDIS Major 165 / Comm
Subsystem Failure If the alarm occurs again, the ONT
Disabled (SOHO) -SOHO On 26 Yes
COM must likely be physically repaired
or swapped.

ONT has been deactivated


because its location on the PON
Communications
Differential Reach DIFREACH- Major 165 / Comm has exceeded its differential reach
Subsystem Failure
Exceeded (SOHO) SOHO On 27 No capability.
COM
Alarm is cleared when ONT is
disconnected from PON.

Communications
OMCI Failure OMCICOMM- Major 166 / Comm
Subsystem Failure Attempt to restart the ONT.
SOHO SOHO On 1 Yes
COM

Equipment
Physical Equipment Major 165 / Comm
Malfunction PEE-SOHO Perform loopback tests.
Error SOHO On 6 Yes
EQP

Reset the ONT by administratively


Equipment putting it OOS and then IS. If the
Defense Action ONTDISABLED- Major 165 / Comm
Malfunction alarm occurs again, the ONT most
SOHO SOHO On 12 Yes
EQP likely needs to be physically
repaired or replaced.

Equipment
Device Not Active Major 165 / Comm The ONT needs to be ranged
Malfunction INACT-SOHO
SOHO On 15 Yes (made active).
EQP

Equipment Check the quality of the line from


Signal Failure Major 165 / Comm
Malfunction SF-SOHO the ONT. Signal Fail BER
SOHO On 17 Yes
EQP exceeded.

Equipment Restore power to the ONT. The


Minor 165 / Comm
Malfunction Dying Gasp SOHO DG-SOHO dying gasp indication is due to a
On 18 Yes
EQP loss of power input to the ONT.

Equipment 1. Reset the ONT.


Deactivation Failure Major 165 / Comm
Malfunction DF-SOHO 2. Replace the ONT if the
SOHO On 19 Yes
EQP Deactivation Failure persists.

Equipment Command another ONT self-test.


Self Test Failed Major 166 / Eqt
Malfunction EQPT-SOHO If it fails, implement creative
SOHO On 2 Yes
EQP diagnostics.

LCD-SOHO Major Comm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 69 sur 93

Loss Of Cell Or Loss Of Cell Or On 165 / Yes Check the quality of the line from
Packet Delineation Packet Delineation 4 the ONT.
LCD SOHO

Loss Of Loss Of See if the specific ONT is


Major 165 / Comm
Acknowledgement Acknowledgement LOA-SOHO isolated. If it is not, this is likely a
On 2 Yes
LOA SOHO software error.

Loss Of Signal Loss Of Signal Major 165 / Comm Check the received signal at the
LOS-SOHO
LOS SOHO On 1 Yes ONT.

Message Error See if the specific ONT is


Message Error Major 165 / Comm
Message MEM-SOHO isolated. If it is not, this is likely a
Message SOHO On 13 Yes
MEM software error.

Extraneous power bursts have


been detected for this ONT. This
alarm clears automatically after
Power Problem ONT Power Up ONTPWRERR- Minor 165 / Comm 15 minutes.
PWR Error SOHO SOHO On 25 No 1. Replace the ONT.
2. Change the power burst
detection mode at the system
level to normal soak mode.

Power Problem External Power Minor 166 / Env Wait for power to return to the
ACFAIL-SOHO
PWR Failure SOHO On 3 No ONT.

Power Problem Minor Eqt Change the provisioning, or


Battery Missing BATTMISS- 166 /
determine why the battery is
PWR SOHO SOHO On 4 No missing.

Power Problem Minor Eqt If power is present, determine


BATTLOW- 166 /
Battery Low SOHO why the battery does not charge,
PWR SOHO On 5 No or why it is low.

Power Problem Battery Failure BATTFAIL- Minor 166 / Eqt The customer needs to replace
PWR SOHO SOHO On 6 No the battery.

Remote Defect Check the receive signal at the


Remote Defect Major 165 / Comm
Indication RDI-SOHO ONT. The OLT transmission was
Indication SOHO On 22 Yes
RDI received with errors at the ONT.

Degraded Signal Degraded Signal Major 165 / Comm Check the quality of the line from
SD-SOHO
SIGN SOHO On 9 Yes the ONT.

Signal Power Received SOHO Major 166 / Comm Check the received optical signal
Problem Optical Signal LEVELHI-SOHO
On 29 Yes and decrease the signal level.
SPWR Level Too High

Signal Power Received SOHO


LEVELLO- Major 166 / Comm Check the received optical signal
Problem Optical Signal
SOHO On 30 Yes and increase the signal level.
SPWR Level Too Low

Startup Failure Startup Failure Major 165 / Comm


SUF-SOHO Re-range the ONT.
SUF SOHO On 7 Yes

1. Ensure that the planned ONT


software version is physically
present on the OLT.
Software 2. Retry the download again.
Software Download SWDLFAIL- Minor 166 / Eqt
Download Failure 3. Manually clear the alarm (for
Failure SOHO SOHO On 8 No
SWDL example, change the planned
version to the wildcard). Contact
your Alcatel-Lucent technical
support representative.

Table 118-48 describes the ONT IP host alarms.

Table 118-48 ONT IP host alarms


Default
Category /
Probable cause / Specific TL1 severity / Alarm
Service Repair action
Mnemonic problem condition Default ID
affecting
reporting

Configuration Or ONT IP Host IPHOSTMIS Minor 188 / 1 Comm The LT or ONT did not accept the
Customization Error Mismatch On Yes configuration requests for the

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 70 sur 93

CFG provisioned ONT IP host. Possible


reasons are:
1. The interface is not supported by the
ONT.
2. LT configuration or setup problem.
Possible solutions are to restart the
ONT, restart the LT, or to deprovision
the IP host since it is not supported.

Table 118-49 describes the ONT VEIP configuration alarms.

Table 118-49 ONT VEIP configuration alarms


Default
Category /
Probable cause / Specific TL1 severity / Alarm
Service Repair action
Mnemonic problem condition Default ID
affecting
reporting

The ONT or LT did not accept the


configuration requests for the provisioned
VEIP. Possible reasons are:
Configuration Or 1. The interface is not supported by the
ONT VEIP Minor Comm
Customization Error VEIPMIS 186 / 1 ONT.
Mismatch On Yes
CFG 2. LT configuration or setup problem.
Possible solutions are to restart the ONT,
restart the LT, or to deprovision the VEIP
since it is not supported.

Table 118-50 describes the PON alarms.

Table 118-50 PON alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

Configuration Or
Customization Minor Eqt No repair is necessary. This
New ONT
Error NEWONT 45 / 7 alarm serves as an indication that
Discovered On No further provisioning is required.
CFG

Configuration Or
Customization PON Major Eqt Provisioned parameters failed to
Error Provisioning PONMEA 45 / 8 be provisioned for PON. Delete
Failure On Yes the PON and provision it again.
CFG

Configuration Or
Customization Minor Eqt No repair is necessary. This
45 /
Error LOID Conflict LOIDCONFLICT alarm serves as an indication that
On 13 No further provisioning is required.
CFG

Configuration Or
Customization Minor Eqt No repair is necessary. This
LOID Password 45 /
Error LOIDPWDERR alarm serves as an indication that
Error On 14 No further provisioning is required.
CFG

Indicates that there is at least one


non PON ONT exists on the PON
that interrupts the ranging or re-
Communications ranging of other ONTs.
Subsystem Alien ONT Major 45 / Eqt 1. Investigate the operating
Failure ALIENDETECTED
Detected On 17 No environment as soon as possible
COM to disconnect these Alien ONTs.
2. The alarm clears when later
test runs to find that there is no
Alien ONT existed any more.

Equipment PON Critical Eqt


Malfunction Communication PONCOMMFAIL 45 / 1 Restart the PON.
Failure On Yes
EQP

Local Node
Transmission Critical Eqt
Error - TXFAIL 45 / 2 Check the OLT laser.
On Yes
LCL

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 71 sur 93

Loss Of Signal - PONLOS Major 45 / 9 Comm Check the receive PON fiber
LOS On Yes input at the OLT.

OTDR Problem Minor Eqt Replace the SFP with an OTDR


SFP Does Not 190 /
OTDRCAPMISM capable SFP or disable OTDR
OTDR Support OTDR On 1 No on that SFP.

PON Protection Protection Not Major 208 / Eqt Check availability of protection
Failure Available On PROTNOTAVAIL
On 1 No equipment.
PONPF Protecting PON

PON Protection Protection Critical 208 / Eqt


Failure Switchover PROTSWFAIL -
On 2 Yes
PONPF Failure

Synchronization
Bulk Sync Failed Minor 207 / Eqt
Problem BSFDHCPV4 -
DHCPv4 On 1 Yes
SYNC

Synchronization
Bulk Sync Failed Minor 207 / Eqt
Problem BSFDHCPV6 -
DHCPv6 On 2 Yes
SYNC

Synchronization
Bulk Sync Failed Minor 207 / Eqt
Problem BSFPON -
PON On 3 Yes
SYNC

Synchronization Bulk Sync Failed Minor 207 / Eqt


Problem VLAN Bridge BSFVLANBM -
On 4 Yes
SYNC MGMT

Synchronization
Bulk Sync Failed Minor 207 / Eqt
Problem BSFQOS -
QoS On 5 Yes
SYNC

Synchronization
Bulk Sync Failed Minor 207 / Eqt
Problem BSFIGMP -
IGMP On 6 Yes
SYNC

1. Check the receive PON signal


at the OLT.
2. Check the transmit PON
signal at the ONT.
Threshold Errored Lost
Warning Qos 3. Check the ONT for ONT TC
Crossed GEM Fragments
T-ERRFRAGSPON 94 / 1 ERRFRAGS and isolate at the
Received At OLT On No
TCA ONT level if the ONT counts
Near End
exist.
4. Reset LT.
5. Replace the associated LT at
the OLT if the PM counts persist.

1. Check ONT upstream


Threshold PON Upstream Major Comm bandwidth configurations
Crossed Bandwidth At T-BWTCA 94 / 2
OLT On Yes 2. Reassign some subscribers to
TCA
other PON ports

PON 1. Check ONT downstream


Threshold
Downstream Major Comm bandwidth configurations
Crossed T-BWTCA 94 / 3
Bandwidth At On Yes 2. Reassign some subscribers to
TCA OLT other PON ports

Threshold Downstream
Warning Qos 1/ None. Just a warning that
Crossed Multicast 225 /
T-TXMCUTILHI traffic has exceeded a set
Utilization High On 1 No
TCA bandwidth threshold.
Threshold Alarm

Downstream
Threshold Multicast 1/ None. Just a warning that
Warning 225 / Qos
Crossed Utilization T-TXMCUTILMD traffic has exceeded a set
On 2 No
TCA Medium bandwidth threshold.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. Just a warning that
Crossed Multicast 225 /
T-TXMCUTILLO traffic has exceeded a set
Utilization Low On 3 No
TCA bandwidth threshold.
Threshold Alarm

Threshold Downstream T-TXTOTUTILHI Warning 225 / Qos 1/ None. Just a warning that
Crossed Total Utilization On 4 No traffic has exceeded a set
TCA bandwidth threshold.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 72 sur 93

High Threshold
Alarm

Threshold Downstream
Warning Qos 1/ None. Just a warning that
Crossed Total Utilization 225 /
T-TXTOTUTILMD traffic has exceeded a set
Medium On 5 No
TCA bandwidth threshold.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. Just a warning that
Crossed Total Utilization 225 /
T-TXTOTUTILLO traffic has exceeded a set
Low Threshold On 6 No
TCA bandwidth threshold.
Alarm

Threshold Upstream Total 1/ None. Just a warning that


Warning 225 / Qos
Crossed Utilization High T-RXTOTUTILHI traffic has exceeded a set
On 7 No
TCA Threshold Alarm bandwidth threshold.

Threshold Upstream Total


Warning Qos 1/ None. Just a warning that
Crossed Utilization 225 /
T-RXTOTUTILMD traffic has exceeded a set
Medium On 8 No
TCA bandwidth threshold.
Threshold Alarm

Threshold Upstream Total 1/ None. Just a warning that


Warning 225 / Qos
Crossed Utilization Low T-RXTOTUTILLO traffic has exceeded a set
On 9 No
TCA Threshold Alarm bandwidth threshold.

Threshold DBA Congestion 1/ None. Just a warning that


T- Warning 225 / Qos
Crossed High Threshold traffic has exceeded a set
DBACONGPERIODHI On 10 No
TCA Alarm bandwidth threshold.

Threshold DBA Congestion 1/ None. Just a warning that


T- Warning 225 / Qos
Crossed Medium traffic has exceeded a set
DBACONGPERIODMD On 11 No
TCA Threshold Alarm bandwidth threshold.

Threshold DBA Congestion 1/ None. Just a warning that


T- Warning 225 / Qos
Crossed Low Threshold traffic has exceeded a set
DBACONGPERIODLO On 12 No
TCA Alarm bandwidth threshold.

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Unicast Dropped 225 /
T-TXUCDROPFRMHI unacceptable, determine why
Frames High On 13 No
TCA frames are being dropped.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Unicast Dropped 225 /
T-TXUCDROPFRMMD unacceptable, determine why
Frames Medium On 14 No
TCA frames are being dropped.
Threshold Alarm

Threshold Downstream
Warning Qos 1/ None. A warning. If situation
Crossed Unicast Dropped 225 /
T-TXUCDROPFRMLO unacceptable, determine why
Frames Low On 15 No
TCA frames are being dropped.
Threshold Alarm

Downstream
Threshold Multicast 1/ None. A warning. If situation
Warning 225 / Qos
Crossed Dropped Frames T-TXMCDROPFRMHI unacceptable, determine why
On 16 No
TCA High Threshold frames are being dropped.
Alarm

Downstream
Threshold Multicast 1/ None. A warning. If situation
Warning 225 / Qos
Crossed Dropped Frames T-TXMCDROPFRMMD unacceptable, determine why
On 17 No
TCA Medium frames are being dropped.
Threshold Alarm

Downstream
Threshold Multicast 1/ None. A warning. If situation
Warning 225 / Qos
Crossed Dropped Frames T-TXMCDROPFRMLO unacceptable, determine why
On 18 No
TCA Low Threshold frames are being dropped.
Alarm

Downstream
Threshold Broadcast 1/ None. A warning. If situation
Warning 225 / Qos
Crossed Dropped Frames T-TXBCDROPFRMHI unacceptable, determine why
On 19 No
TCA High Threshold frames are being dropped.
Alarm

Downstream
Threshold Broadcast 1/ None. A warning. If situation
Warning 225 / Qos
Crossed Dropped Frames T-TXBCDROPFRMMD unacceptable, determine why
On 20 No
TCA Medium frames are being dropped.
Threshold Alarm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 73 sur 93

Downstream
Threshold Broadcast 1/ None. A warning. If situation
Warning 225 / Qos
Crossed Dropped Frames T-TXBCDROPFRMLO unacceptable, determine why
On 21 No
TCA Low Threshold frames are being dropped.
Alarm

Threshold Upstream Total


Warning Qos 1/ None. A warning. If situation
Crossed Dropped Frames 225 /
T-RXTOTDROPFRMHI unacceptable, determine why
High Threshold On 22 No
TCA frames are being dropped.
Alarm

Threshold Upstream Total


Warning Qos 1/ None. A warning. If situation
Crossed Dropped Frames T- 225 /
unacceptable, determine why
Medium RXTOTDROPFRMMD On 23 No
TCA frames are being dropped.
Threshold Alarm

Threshold Upstream Total


Warning Qos 1/ None. A warning. If situation
Crossed Dropped Frames T- 225 /
unacceptable, determine why
Low Threshold RXTOTDROPFRMLO On 24 No
TCA frames are being dropped.
Alarm

PON Rogue (Misbehaving) test


is currently active. Wait for test
Test Problem Major Eqt to complete or abort or stop
Rogue Test 45 /
PONROGUETEST current test. After the test
TEST Ongoing On 10 No completes, look for ONTs
diagnosed as misbehaving
(INACT alarm) and resolve.

Indicates that due to 'rogue


ONT testing' an 'unranged
ONT' on the PON may have
been DISABLED via OLT
broadcast 'disable laser'
command. This alarm clears
Test Problem Minor Comm automatically after 12 hours. If
Stuck Laser 45 /
STKLASERDIS such an ONT was disabled,
TEST Disabled On 15 Yes the only way to re-range it is to
plan it via direct provisioning of
its Serial Number. But prior to
doing that, the physical ONT
should be examined to
determine if it has a stuck
laser.

PON Alien (Non PON ONT)


test is currently active.
Test Problem Major Eqt 1. Wait for test to complete or
Alien ONT Test 45 /
PONALIENTEST abort/stop current test.
TEST Ongoing On 16 No
2. Once test completes, look
for ALIENDETECTED alarm to
resolve the problem.

Table 118-51 describes the PORT alarms.

Table 118-51 PORT alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

1. Check the operational


Critical Event Unspecified Critical Minor Comm
CPECREVT 203 / 3 state of the port.
CE Event On Yes
2. Restart the CPE.

Dying Gasp Unrecoverable Minor Comm CPE is failing, it should be


CPEDYINGGASP 203 / 2
DG Failure On No restarted or replaced.

Link Fault Detected Receive Minor Comm Check the operational state
EFMLNKFAULT 203 / 1
LF Fault On Yes of the port

Table 118-52 describes the PPPCCEngine alarms.

Table 118-52 PPPCCEngine alarms


Probable cause / Specific problem TL1 condition Default Alarm Category / Repair action
Mnemonic severity / ID Service
affecting

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 74 sur 93

Default
reporting

Session
Inactive Session in Minor Comm Check DSL stability
Disconnected PPPCCESESS15MIN 211 / 2
15 Minutes On Yes and BRAS reachability
SD

Session
Inactive Session in Minor Comm Check DSL stability
Disconnected PPPCCESESS1DAY 211 / 4
1 Day On Yes and BRAS reachability
SD

Session Not Transaction Minor Comm Check BRAS


Established Timeout in 15 PPPCCETRANS15MIN 211 / 1
On Yes reachability
SNE Minutes

Session Not
Transaction Minor Comm Check BRAS
Established PPPCCETRANS1DAY 211 / 3
Timeout in 1 Day On Yes reachability
SNE

Table 118-53 describes the QoS alarms.

Table 118-53 QoS alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

Threshold
QoS LT Bus Fan Out Minor Qos
Crossed FANOUT 106 / 1 Check the LT load.
Load Overflow On No
TCA

Threshold QoS Upstream Minor Qos Check the LT load in the


Crossed Aggregate Load UPOVERFLOW 106 / 2
On No upstream direction.
TCA Overflow

Threshold Check the LT load to the


QoS Upstream OBC Minor Qos
Crossed UPOBCFLOW 106 / 3 OBC in the upstream
Load Overflow On No
TCA direction.

Threshold Check the LT load to the


QoS Downstream OBC Minor Qos
Crossed DWOBCFLOW 106 / 4 OBC in the downstream
Load Overflow On No
TCA direction.

Threshold QoS Downstream Minor Qos Check the LT load in the


Crossed Aggregate Load DWOVERFLOW 106 / 5
On No downstream direction.
TCA Overflow

Threshold Excessive Drop Of Minor Qos Check the voice and video
Crossed Lower Traffic Class LPDRFLOW 106 / 6
On No load.
TCA Packets

Threshold
Excessive Drop Of Minor Qos Check the corresponding
Crossed QUEUEDRFLOW 112 / 1
Packets On No queue load.
TCA

Threshold
Minor Qos Check the corresponding
Crossed Load Overflow QUEUELD 112 / 2
On No queue load.
TCA

Table 118-54 describes the rack alarms.

Table 118-54 Rack alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Rack Customizable
Indeterminate Env
Alarm 1 - MISC 10 / 1 -
On No
ENV-1

Rack Customizable - MISC Indeterminate 10 / 21 Env -


Alarm 10 On No

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 75 sur 93

ENV-10

Rack Customizable
Indeterminate Env
Alarm 11 - MISC 10 / 22 -
On No
ENV-11

Rack Customizable
Indeterminate Env
Alarm 12 - MISC 10 / 23 -
On No
ENV-12

Rack Customizable
Indeterminate Env
Alarm 13 - MISC 10 / 24 -
On No
ENV-13

Rack Customizable
Indeterminate Env
Alarm 14 - MISC 10 / 25 -
On No
ENV-14

Rack Customizable
Indeterminate Env
Alarm 15 - MISC 10 / 26 -
On No
ENV-15

Rack Customizable
Indeterminate Env
Alarm 16 - MISC 10 / 27 -
On No
ENV-16

Rack Customizable
Indeterminate Env
Alarm 17 - MISC 10 / 28 -
On No
ENV-17

Rack Customizable
Indeterminate Env
Alarm 2 - MISC 10 / 2 -
On No
ENV-2

Rack Customizable
Indeterminate Env
Alarm 3 - MISC 10 / 3 -
On No
ENV-3

Rack Customizable
Indeterminate Env
Alarm 4 - MISC 10 / 4 -
On No
ENV-4

Rack Customizable
Indeterminate Env
Alarm 5 - MISC 10 / 5 -
On No
ENV-5

Rack Customizable
Indeterminate Env
Alarm 6 - MISC 10 / 17 -
On No
ENV-6

Rack Customizable
Indeterminate Env
Alarm 7 - MISC 10 / 18 -
On No
ENV-7

Rack Customizable
Indeterminate Env
Alarm 8 - MISC 10 / 19 -
On No
ENV-8

Rack Customizable
Indeterminate Env
Alarm 9 - MISC 10 / 20 -
On No
ENV-9

Equipment Malfunction Major Eqt


Rack Fan 1 Failure FANALM-1 2/2 Check the fan.
EQP On No

Equipment Malfunction Major Eqt


Rack Fan 2 Failure FANALM-2 2/3 Check the fan.
EQP On No

Power Problem Rack Power Fuse Minor Eqt Check the power
FA 2/1
PWR Broken On No supplies.

Table 118-55 describes the SFP alarms.

Table 118-55 SFP alarms


Specific problem TL1 condition Category / Repair action

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 76 sur 93

Probable Default Alarm Service


cause / severity / ID affecting
Mnemonic Default
reporting

Bias Problem Transmit Bias Too Major 206 / Eqt Check the transmitted bias and
TXBIASCURHI
BIPR High Alarm On 5 Yes decrease Bias

Bias Problem Transmit Bias Too Major 206 / Eqt Check the transmitted bias and
TXBIASCURLO
BIPR Low Alarm On 6 Yes increase Bias

Bias Problem Transmit Bias Too Warning 206 / Eqt Check the transmitted bias and
TXBIASCURHIWARN
BIPR High Warning On 15 No decrease Bias

Bias Problem Transmit Bias Too Warning 206 / Eqt Check the transmitted bias and
TXBIASCURLOWARN
BIPR Low Warning On 16 No increase Bias

Transmitted
Power Problem Optical Power Major 206 / Comm Check the transmitted power and
TXPWHI
PWR Above Alarm On 1 Yes decrease signal level
Threshold

Transmitted
Power Problem Optical Power Major 206 / Comm Check the transmitted power and
TXPWLO
PWR Below Alarm On 2 Yes increase signal level
Threshold

Power Problem Received Optical Major Comm Check the received Optical
206 /
Power Above RXPWHI signal power and decrease
PWR On 3 Yes
Alarm Threshold signal level

Power Problem Received Optical Major Comm Check the received Optical
206 /
Power Below RXPWLO signal power and increase signal
PWR On 4 Yes
Alarm Threshold level

Transmitted
Power Problem Optical Power Warning 206 / Comm Check the transmitted power and
TXPWHIWARN
PWR Above Warning On 11 No decrease signal level
Threshold

Transmitted
Power Problem Optical Power Warning 206 / Comm Check the transmitted power and
TXPWLOWARN
PWR Below Warning On 12 No increase signal level
Threshold

Received Optical
Power Problem Warning Comm Check the received Optical
Power Above 206 /
RXPWHIWARN signal power and decrease
PWR Warning On 13 No signal level
Threshold

Received Optical
Power Problem Warning Comm Check the received Optical
Power Below 206 /
RXPWLOWARN signal power and increase signal
PWR Warning On 14 No level
Threshold

SFP Problem Host SFP Loss Of Critical Comm


HSFPLOS 76 / 1 Check the physical line.
SFP Signal On Yes

SFP Problem Host SFP Critical Comm Check the host-side SFP
HSFPTXF 76 / 2
SFP Transmit Failure On Yes module.

SFP Problem Critical Comm Check the host-side SFP


Host SFP Missing HSFPNP 76 / 3
SFP On Yes presence.

SFP Problem Host SFP Invalid Critical Comm Check the ID of the host-side
HSFPINVID 76 / 4
SFP Module ID On Yes SFP module.

Check the host-side SFP module


SFP Problem Host SFP Control Critical Comm or I2C bus. If the control of all
HSFPCTRF 76 / 5
SFP Failure On Yes host-side SFPs fails, check the
NT applique.

Check whether the host-side


Host SFP
SFP Problem Minor Eqt SFP assignment configuration is
Unconfigured
HSFPUEPR 76 / 6 missing or whether the remote
SFP Remote LT On No LT is cabled to the wrong Host-
Detected
side SFP module.

SFP Problem Host SFP Remote HSFPRASM Major 76 / 7 Eqt


SFP LT Slot Mismatch On Yes

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 77 sur 93

Check for a cabling error or host


-side SFP assignment
configuration error.

SFP Problem Host SFP Remote Minor Eqt Check for a cabling error, shelf
LT Shelf Type HSFPINCOMPS 76 / 8 type planning error, or
SFP Mismatch On No assignment configuration error.

SFP Problem Expansion SFP Critical 76 / Comm


ESFPLOS Check the physical line.
SFP Loss Of Signal On 11 Yes

SFP Problem Expansion SFP Critical 76 / Comm Check the expansion-side SFP
ESFPTXF
SFP Transmit Failure On 12 Yes module.

SFP Problem Expansion SFP Critical 76 / Comm Check the expansion-side SFP
ESFPNP
SFP Missing On 13 Yes presence.

SFP Problem Expansion SFP Critical 76 / Comm Check the ID of the expansion-
ESFPINVID
SFP Invalid Module ID On 14 Yes side SFP module.

SFP Problem Expansion SFP Critical 76 / Comm Check the expansion-side SFP
ESFPCTRF
SFP Control Failure On 15 Yes module or I2C bus.

Check the physical line: is the


optical link from the host to the
SFP Problem Expansion SFP1 Critical 76 / Comm remote unit too highly
ESFP1LOS
SFP Loss Of Signal On 16 Yes attenuated, is SFP still OK in
the host/remote, is the optical
cable correctly connected?

Check the physical line: is the


optical link from the host to the
SFP Problem Expansion SFP2 Critical 76 / Comm remote unit too highly
ESFP2LOS
SFP Loss Of Signal On 17 Yes attenuated, is SFP still OK in
the host/remote, is the optical
cable correctly connected?

SFP Problem User SFP Loss Of Minor 108 / Comm


LTSFPLOS Check the physical line.
SFP Signal On 1 Yes

SFP Problem User SFP Minor 108 / Comm


LTSFPTXF Check the SFP module.
SFP Transmit Failure On 2 Yes

SFP Problem Minor 108 / Comm


User SFP Missing LTSFPNP Check the SFP presence.
SFP On 3 Yes

SFP Problem User SFP Invalid Minor 108 / Comm


LTSFPINVID Check the SFP module ID.
SFP Module ID On 4 Yes

SFP Problem User SFP Critical Comm


108 /
Temperature LTTEMPEXCED Check the SFP temperature.
SFP On 5 Yes
Exceeds

SFP Problem User SFP Minor 108 / Comm


LTSFPMIS Check the SFP type.
SFP Mismatch On 6 Yes

Temperature
Temperature Too Major 206 / Eqt Check temperature and
Unacceptable TEMPEHI
High Alarm On 9 Yes decrease temperature
TEMP

Temperature
Temperature Too Major 206 / Eqt Check temperature and
Unacceptable TEMPLO
Low Alarm On 10 Yes increase temperature
TEMP

Temperature
Temperature Too Warning 206 / Eqt Check temperature and
Unacceptable TEMPEHIWARN
High Warning On 19 No decrease temperature
TEMP

Temperature
Temperature Too Warning 206 / Eqt Check temperature and
Unacceptable TEMPELOWWARN
Low Warning On 20 No increase temperature
TEMP

Voltage
Voltage Too High Major 206 / Eqt Check voltage and decrease
Problem VOLHI
Alarm On 7 Yes voltage
VTP

Voltage Voltage Too Low VOLLO Major 206 / Eqt Check voltage and increase
Problem Alarm On 8 Yes voltage

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 78 sur 93

VTP

Voltage
Voltage Too High Warning 206 / Eqt Check voltage and decrease
Problem VOLHIWARN
Warning On 17 No voltage
VTP

Voltage
Voltage Too Low Warning 206 / Eqt Check voltage and increase
Problem VOLLOWARN
Warning On 18 No voltage
VTP

Table 118-56 describes the SHDSL pair alarms.

Table 118-56 SHDSL pair alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Customer Segment Activation Failure At Minor Comm Check the CO wiring of


Activation Failure Customer Segment CACTFAIL 82 / 19
On Yes the different segments.
ACTF Termination

DC Continuity Fault Minor Comm Check the network-


DC Continuity Fault At
NDCCONT 82 / 9 side equipment and
DC Network Side On Yes wiring.

DC Continuity Fault Minor Comm Check the customer-


DC Continuity Fault At
CDCCONT 82 / 10 side equipment and
DC Customer Side On Yes wiring.

Loss Of
Loss Of Synchronization Minor Comm Check the signal at the
Synchronization Word NLOSW 82 / 3
Word At Network Side On Yes network side.
LOSW

Loss Of
Loss Of Synchronization Minor Comm Check the signal at the
Synchronization Word CLOSW 82 / 4
Word At Customer Side On Yes customer side.
LOSW

Loop Attenuation
Loop Attenuation Alarm At Minor Comm Check the signal at the
Alarm NATEN 82 / 5
Network Side On Yes network side.
LPAT

Loop Attenuation
Loop Attenuation Alarm At Minor Comm Check the signal at the
Alarm CATEN 82 / 6
Customer Side On Yes customer side.
LPAT

SNR Margin Alarm SNR Margin Alarm At Minor Comm Check the signal at the
NSNR 82 / 7
SNR Network Side On Yes network side.

SNR Margin Alarm SNR Margin Alarm At Minor Comm Check the signal at the
CSNR 82 / 8
SNR Customer Side On Yes customer side.

Table 118-57 describes the SHDSL Unit alarms.

Table 118-57 SHDSL Unit alarms


Default
Category /
Probable cause / TL1 severity / Alarm
Specific problem Service Repair action
Mnemonic condition Default ID
affecting
reporting

Configuration Or Check configuration


Minor Comm
Customization Error Configuration Error CONFERR 23 / 13 parameters supported by
On Yes device.
CFG

Hardware Device
Minor Eqt
Failure - DEVFAIL 23 / 17 Check equipment.
On Yes
HW

Loss Of Cell Or Packet


Minor Comm Check the clock subsystem
Delineation - ATMLCD 23 / 14
On Yes or ATM configuration.
LCD

Loss Of Power LPR Minor 23 / 15 Comm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 79 sur 93

LOPW Loss Of Power at On Yes Check the power supply at


STU-R STU-R.

Facility In Loopback Minor Comm


- NLOOPBACK 23 / 11 Testing in progress.
LPBK On Yes

Facility In Loopback Loopback Active At Minor Comm


CLOOPBACK 23 / 12 Testing in progress.
LPBK Customer Side Off Yes

No Cell Or Packet
Minor Comm Check the clock subsystem
Delineation - ATMNCD 23 / 18
On Yes or ATM configuration.
NCD

Communications Check devices that do not


Minor Comm
Protocol Error - SECUERR 23 / 16 support disabling STU-R
On Yes access.
PRTCL

Table 118-58 describes the SHub alarms.

Table 118-58 SHub alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

No special repair action. The


Address Conflict MAC Address Minor Comm conflicted MAC address can be
SA_LANXPORTMAC1 52 / 3
ADDR Conflict On Yes manually prohibited or permitted if
needed.

Check the configuration mode of


Configuration the port and can change the
Or administrative speed based on
Operational and Minor Comm
Customization 52 / the port capability,
Administrative OPERSPD_MISM
Error On 10 No SFP/XFP/RJ45 interfaces used,
Speed Mismatch
such that operational speed
CFG matches with the administrative
speed.

Loss Of Link Ethernet Link Critical Comm


LANXPORTLINK 52 / 1 Check the physical Ethernet link.
LOL Down On Yes

Loss Of Link Major Eqt Check the service hub uplink


- UPLINKDWN 75 / 1
LOL On No group.

PCCP Group Check the SHub PCCP group


Critical Eqt ports operational status. At least
Down - - 75 / 2
On Yes one of the ports in the PCCP
PCCP group should be operational.

Restore Failure Major Eqt Check the local flash or remote


Service Hub
LANXDBASEALM 51 / 3 file system or the availability of
REST Restore Failed On Yes MIB database.

Remote Node
Transmission SNTP Major Eqt
Error Communication LANXSNTPALM 51 / 5 Check the SNTP server.
Lost On No
RTE

1. Check the network L3


configuration and the number of
routes configured for ISAM and
all other routers within the AS and
the instance.
2. Check the route aggregation
configuration in ISAM and all
Storage other routers within the AS and
Capacity Major Comm the instance.
Problem ARP Table Full L3FWD_ARPTHR 71 / 1
On No 3. Reduce the number of enabled
SCP routing protocols in the instance.
4. Check the routemaps
configuration in other routers in
the AS and the instance.
5. Check and reduce the number
of directly attached hosts to local
subnets in the instance.

FWDGLARPTHR Major Comm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 80 sur 93

Storage ARP Global Table On 125 / No 1. Check the network L3


Capacity Full 1 configuration and the number of
Problem routes configured both for ISAM
SCP and all other routers within the
AS (all instances).
2. Check the route aggregation
configuration in ISAM and all
other routers in the AS (all
instances.).
3. Reduce the number of
enabled routing protocols (all
instances).
4. Check the routemaps
configuration in other routers in
the AS.
5. Check and reduce the number
of directly-attached hosts to all
local subnets.

Table 118-59 describes the SIP alarms.

Table 118-59 SIP alarms


Default
Probable Category /
severity / Alarm
cause / Specific problem TL1 condition Service Repair action
Default ID
Mnemonic affecting
reporting

DNS Problem Critical Comm Check the configuration or


No Reply From DNS 194 /
NONEDNSSRV connection of DNS servers in
DNS Servers On 2 Yes ISAM voice.

DNS Problem No DNS servers Critical 194 / Comm Check the configuration of
NODNSSRV
DNS configured On 3 Yes DNS servers in ISAM voice.

DNS Problem Critical 196 / Comm Check the configuration of


DNS Lookup Failure DNSLKUPFAIL
DNS On 2 Yes DNS servers in ISAM-V.

SIP Bad
SIP DigitMap Critical 193 / Proc Check the configured
DigitMap BADDM
Unusable On 1 Yes digitmap.
SBDM

SIP First Hop


No reply for all SIP Critical 194 / Comm Check the configuration of
Problem NONESRV
First Hops On 4 Yes SIP servers in ISAM voice.
SIPFH

SIP First Hop


No Proxy Servers Critical 194 / Comm Check the configuration of
Problem NOSRV
configured On 5 Yes SIP servers in ISAM voice.
SIPFH

Server Check configuration of the


Resource All Register Servers Critical 194 / Comm proxy servers of ISAM-V and
Isolation SRSRVUNRCH
Unreachable On 6 Yes those allowed to SIP servers
SISO ISAM-V should connected.

Server Check configuration of the


Resource Critical Comm register servers of ISAM-V
All Proxy Servers 194 /
Isolation SPSRVUNRCH and those allowed to SIP
Unreachable On 7 Yes servers ISAM-V should
SISO connected.

Transport Check configuration of the


Transport Protocol
Protocol Critical Comm transport mode of ISAM-V
Mismatch between 196 /
Mismatch TRANSPORTMISMATCH and those allowed to SIP
ISAM-V and SIP On 1 Yes servers ISAM-V should be
TPM First Hop
connected.

Table 118-60 describes the SIP configuration alarms.

Table 118-60 SIP configuration alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

SIPAREGFAILNAME Major 180 / Comm


1

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 81 sur 93

Configuration Or SIP UA On Yes SIPUA register name - Failed to


Customization Registration resolve the registration server
Error Name Failed name. Possible reasons are:
CFG 1. Domain name of SIP server not
resolvable.
Possible solutions are:
1. Verify registration server name.
2. Check DNS server IP address.

SIPUA register reach - Cannot


reach registration server (the port
cannot be reached, ICMP errors).
Possible reasons are:
Configuration Or
Customization SIP UA Major Comm 1. Connectivity lost.
180 /
Error Register SIPAREGREACH Possible solutions are:
On 2 Yes
Reach Failed
CFG 1. Check network connectivity and
configuration.
2. Check for network alarms.
3. Ping the ONT.

SIPUA register connect - Cannot


connect to registration server (due
Configuration Or to bad credentials or other fault
Customization SIP UA Major Comm after the port responded). Possible
180 /
Error Register SIPAREGCONNECT reasons are:
On 3 Yes
Connect Failed 1. Invalid user login and password.
CFG
Possible solutions are:
1. Verify configuration.

Configuration Or SIP UA SIPUA register validate - Cannot


Customization Register Major 180 / Comm validate registration server.
Error SIPAREGVALIDATE Possible solutions are:
Validation On 4 Yes
CFG Failed 1. Verify configuration.

The LT or ONT did not accept the


configuration requests for the
provisioned SIP user agent
parameter. Possible reasons are:
Configuration Or
SIP UA 1. The service is not supported by
Customization Minor 180 / Comm
Register SIPAREGMIS the ONT.
Error On 5 Yes
Mismatch 2. Setup problem.
CFG
Possible solutions are to restart
ONT or to deprovision the SIP
user agent since it is not
supported.

Table 118-61 describes the SIP termination alarms.

Table 118-61 SIP termination alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

Configuration Or Check if the directory


Unknown SIP Major Comm
Customization Error UNKNSIPSUB 100 / 1 number, user name or URI of
Subscriber On Yes
CFG the SIP Voice Port is valid.

Call On Going Minor Comm The alarm will be cleared as


Emergency Call On 100 /
ECALLACT soon as the emergency call
CON Going On 20 No is finished.

Domain Name
SIP Registration Major Comm
Failure SIPREGDN 100 / 7 Check domain name.
Domain Name Failure On Yes
DNF

Domain Name
SIP Invite Domain Major 100 / Comm
Failure SIPINVDN Check domain name.
Name Failure On 11 Yes
DNF

Domain Name
SIP Subscribe Resolve Major 100 / Comm
Failure SIPSUBSDN Check Domain Name
Domain Name Failure On 16 Yes
DNF

JBFL Threshold PSTN Port JBFL JBFLTCA Minor 100 / 6 Qos Check JB fill level of the port.
Exceeded Threshold Exceeded On No
JBFL

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 82 sur 93

Authentication
SIP Registration Major Comm
Failure SIPREGAUTH 100 / 8 Check auth element.
Authentication Failure On Yes
SIPAF

Authentication
SIP Invite Major 100 / Comm
Failure SIPINVAUTH Check auth element.
Authentication Failure On 12 Yes
SIPAF

Authentication
SIP Subscribe Major 100 / Comm
Failure SIPSUBSAUTH Check Auth Element
Authentication Failure On 17 Yes
SIPAF

Failure Response SIP Registration Major 100 / Comm


From Server Response from SIP SIPREGFRSP Check SIP server.
On 10 Yes
SIPFR Server Failure

Failure Response SIP Invite Response Major 100 / Comm


From Server from SIP Server SIPINVFRSP Check SIP server.
On 14 Yes
SIPFR Failure

Failure Response SIP Subscribe Major 100 / Comm


From Server Response from SIP SIPSUBSFRSP Check SIP server.
On 15 Yes
SIPFR Server Failure

Message Timeout SIP Registration Major Comm


SIPREGTO 100 / 9 Check network.
SIPTO Message Timeout On Yes

Message Timeout Major 100 / Comm


SIP Invite Timeout SIPINVTO Check network.
SIPTO On 13 Yes

Message Timeout SIP Subscribe Refresh Major 100 / Comm


SIPSUBSRTTO Check Network
SIPTO Timeout On 18 Yes

Message Timeout SIP Subscribe Initial Major 100 / Comm


SIPSUBSINTO Check Network
SIPTO Request Timeout On 19 Yes

1. Check ambient
Temperature
Temperature Major Eqt temperature.
Unacceptable HITEMP 100 / 3
Threshold Exceeded On Yes 2. Check operation of fans 3.
TEMP
Check port.

Voice Problem Major Eqt Check the cabling of the


Ground Key Detection GRDKEY 100 / 2
VX On Yes port.

Table 118-62 describes the slot alarms.

Table 118-62 Slot alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

Configuration Or Check the configuration and


Customization Minor Eqt correct the configuration or replace
Error Type Mismatch MEMDIF 3/3
On No the board with a board of the
CFG correct type.

Configuration Or
Customization Major Eqt
Error Board Removed BDMISSING 3 / 14 Check the board presence.
On Yes
CFG

Configuration Or
Customization Board Not Yet Minor Eqt
Error BDNOTINST 3 / 15 Install the board.
Installed On Yes
CFG

1.Check the physical connection of


Configuration Or
Fibre the FD-REM.
Customization Major 84 / Eqt
Error Connection FIBRECONNMIS 2.Check the configuration of the
On 17 Yes
Mismatch CTRL card identification of the FD-
CFG
REM.

LINKCAPMISMATCH Major Eqt

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 83 sur 93

Configuration Or Link Speed On 84 / No 1. Check for faulty fiber link,


Customization Capability 18 NTIO, host SFP, remote SFP and
Error Mismatch CTRL board (on FD-REM).
CFG

Configuration Or
Customization Link Equipment Minor Eqt 1. Check the speed capability of
84 /
Error Capability EQPTCAPMISMATCH NTIO, host SFP, remote SFP and
On 19 No
Mismatch CTRL board (on FD-REM).
CFG

Configuration Or Software 1. Check the firmware version in


Customization Download For Major 84 / Eqt the alarm.
Error SWDNLDCCFLD
ControllerCard On 20 No 2. Restart the first LT plugged in
CFG Failed the expansion shelf.

The configuration implies that the


BITS output has been shutoff
because the overall System QL
has become worse than the
configured minimum QL for BITS
output.
QL Threshold Note that when the system clock
BITS Output Critical 134 / Eqt is in free-running (i.e. has never
Crossed BITSSHUTOFF
Shutoff On 3 Yes been locked on any external clock
CLK
source since the last reset), the
BITS output signal is shut down
and this alarm will also be raised.
To get it cleared, the system must
have been locked on a valid
external clock source, at least
once since the last system reset.

Check the peer equipment and


connection between the
Synchronization equipment and the ISAM for the
Source BITS Timing Major 134 / Eqt corresponding BITS timing
Mismatch BITSFAIL reference.
Source Failure On 1 Yes
CLK Check that there is no Alarm
Indication Signal (AIS) on the
corresponding BITS input.

Synchronization Check the peer equipment and


Source Major Eqt the connection between the
SyncE Timing 134 /
Mismatch SYNCEFAIL equipment and the ISAM for the
Source Failure On 2 Yes timing reference for the specified
CLK synchronous Ethernet port.

Synchronization Check the peer equipment and


Source IEEE1588 Major Eqt the connection between the
134 /
Mismatch Timing Source IEEE1588FAIL equipment and the ISAM for the
On 4 Yes
Failure corresponding IEEE1588 timing
CLK reference.

Synchronization Check the peer equipment and


Source Major Eqt the connection between the
GNSS Timing 134 /
Mismatch GNSSFAIL equipment and the ISAM for the
Source Failure On 5 Yes corresponding GNSS timing
CLK reference.

Slot
Customizable Major Eqt
Alarm 1 - CUSTALARM1 83 / 1 -
On No
ENV-1

Slot
Customizable Major Eqt
Alarm 2 - CUSTALARM2 83 / 2 -
On No
ENV-2

Slot
Customizable Major Eqt
Alarm 3 - CUSTALARM3 83 / 3 -
On No
ENV-3

Slot
Customizable Major Eqt
Alarm 4 - CUSTALARM4 83 / 4 -
On No
ENV-4

Slot - CUSTALARM5 Major 83 / 5 Eqt -


Customizable On No
Alarm 5
ENV-5

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 84 sur 93

Equipment
Compact Flash Critical Eqt Replace the Compact Flash
Malfunction CFERROR 1 / 10
Access Failure On Yes card.
EQP

Equipment
Fan Power Major Eqt
Malfunction FAN 84 / 1 Check the fan.
Problem On No
EQP

Equipment Check the cabling, the fuse, the


Critical Eqt convertor, the temperature and
Malfunction Dying Gasp DG 84 / 4
On Yes the on/off switch at remote and
EQP cabinet level.

Equipment
Applique Power Critical Eqt Check the power supply of the
Malfunction APSF 84 / 5
Supply Failure On Yes applique.
EQP

SHUB / IHUB Check the HUB uplink cable for


SHUB / IHUB Critical Eqt
Malfunction LANXUPBRKDWN 3 / 31 removal or for any loose
Uplink Broken On Yes
HUB contacts.

Hardware
Board Hardware Major 84 / Eqt
Problem BOARDHWISSUE Change another Board
Issue On 21 Yes
HWF

1. Undo the last applied


configurations (Bridge ports,
VLAN ports or QoS) on that
Hardware HW board.
Major 84 / Eqt
Problem Configuration HWCONFIGFAIL 2. If the alarm is not cleared
On 22 Yes
HWF Failure because of this action, a restart
of tthe board might be required
to clear the alarm and to check
that the problem is fixed.

1. Remove configuration on the


board (Bridge ports, VLAN ports
Hardware
HW Resource Major 84 / Eqt or QoS).
Problem HWLIMITSEXCEEDED
Limit Exceeded On 23 Yes 2. Check the planned internal
HWF
HW resources used by the
board.

1. Check the link on the standby


LT Protection LSM.
Switch Over Major 131 / Eqt
Failure LSMSWCAP
Capability Lost On 1 No 2. Check the standby boards.
LTPF
3. Wait for the quench time-out.

LT Protection
Data Not Major 131 / Eqt
Failure xVPSINVDATA Check the xVPS pair data.
Synchronized On 2 No
LTPF

Power Problem DC Voltage Low Major Eqt


DCA 84 / 2 Check the cabling and the fuse.
PWR A On No

Power Problem DC Voltage Low Major Eqt


DCB 84 / 3 Check the cabling and the fuse.
PWR B On No

1. Check the equipment: VP-


Vectoring Vectoring Links LSM and the cabling.
Major 191 / Eqt
Problem Mismatch or VPLTMISM 2. Check configuration expected
On 1 Yes
VECT Lost VP-LSM connectivity versus
actual VP-LSM connections.

Vectoring 1.Check QSFP ID.


QSFP Invalid ID Major 191 / Comm
Problem VPLQSFPINVID 2. Use a cable with a valid
Error On 2 Yes
VECT Alcatel-Lucent ID.

Vectoring Cable Problem Major 191 / Comm Check the equipment VP-LSM
Problem Between VP VPLTLINKFAIL
On 3 Yes cable
VECT and SLV-LT

Table 118-63 describes the subrack alarms.

Table 118-63 Subrack alarms


TL1 condition Category / Repair action

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 85 sur 93

Probable cause / Specific Default Alarm Service


Mnemonic problem severity / ID affecting
Default
reporting

Configuration Or
Customization Type Minor Eqt 1. Check the equipment.
Error MEMDIFEH 2/7
Mismatch On No 2. Check the configuration.
CFG

In case of extension through


the IQ bus.
1. Check the presence of the
extension board.
2. Check the cabling of the
extension chain.
When the
extension/expansion uses
optical fiber and SFP:
1. Check the presence of shelf
-expander unit on the host
shelf.
Configuration Or
Customization Major Eqt 2. Check cabling to the
Subrack
Error SHMISSING 2/9 expansion shelf.
Removed On Yes
CFG 3. Check the presence of the
slave expander card on the
expansion shelf.
4. Check the presence of the
line board on the expansion
shelf.
5. Check the presence of the
general facilities card on the
expansion shelf.
6. Check the fan on the
expansion shelf.
7. Check the power cable on
the expansion shelf.

Configuration Or 1. Check the presence of the


Customization Subrack Not Minor Eqt extension board.
Error SHNOTINST 2 / 10
Yet Installed On No 2. Check the cabling of the
CFG extension chain.

Enclosure Door
Minor Env
Open - DOORALM 2 / 15 Close the door.
On No
DOOR

Subrack
Customizable Indeterminate Env
Alarm 1 - MISC 10 / 11 -
On No
ENV-1

Subrack
Customizable Indeterminate Env
Alarm 2 - MISC 10 / 12 -
On No
ENV-2

Subrack
Customizable Indeterminate Env
Alarm 3 - MISC 10 / 13 -
On No
ENV-3

Subrack
Customizable Indeterminate Env
Alarm 4 - MISC 10 / 14 -
On No
ENV-4

Subrack
Customizable Indeterminate Env
Alarm 5 - MISC 10 / 15 -
On No
ENV-5

Subrack
Customizable Indeterminate Env
Alarm 6 - MISC 10 / 16 -
On No
ENV-6

Power Problem External Critical Env


Power ACALM 2 / 20 Check power installation.
PWR Failure On Yes

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 86 sur 93

Power Problem BAT-A Failed BATAFAIL Major 130 / 9 Eqt Check the power supplies.
PWR On No

Power Problem Major 130 / Eqt


BAT-B Failed BATBFAIL Check the power supplies.
PWR On 10 No

Power Problem Loss Of Major Env


NETWORKPWRLOSS 130 / Check that the RFT-V power
Network
PWR -B On 13 Yes source B is sourcing power.
Power B

Power Problem External AC Critical Eqt


130 / Check that the AC power
Power SEM-PWR-FAIL
PWR On 15 Yes source is sourcing power
Failure

External
Power Problem Power Major 130 / Eqt Check that the RFT-V power
SEM-UPS-FAIL
PWR Supply On 16 Yes source has correct voltage
Failure

Power Problem Local DC A Major Eqt


130 / Check that the DC A power
Power DCAFAIL
PWR On 17 No source, is sourcing power
Failure

Power Problem Local DC B Major Eqt


130 / Check that the DC B power
Power DCBFAIL
PWR On 18 No source, is sourcing power
Failure

Power Problem Planned Minor Eqt Adapt the planned


130 /
Power Mode PLANPWRMISM powerMode, or replace the
PWR On 19 No
Mismatch power supply

Table 118-64 describes the TR-069 alarms.

Table 118-64 TR-069 alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

A condition meaning that either the ONT


did not accept the configuration requests
for the provisioned TR069 management
Configuration Or server. Possible reasons are:
Customization TR069 Minor Comm
Server TR069SERVMIS 204 / 1 1. It is not supported by the ONT.
Error On Yes
Mismatch 2. Some parameters are not proper.
CFG
Possible solutions are to restart ONT,
restart LT, or to deprovision the TR069
management server since not supported.

Table 118-65 describes the VLAN port alarms.

Table 118-65 VLAN port alarms


Default
Category /
Probable cause / Specific severity / Alarm
TL1 condition Service Repair action
Mnemonic problem Default ID
affecting
reporting

1. A condition meaning that the ONT


Configuration Or did not accept the configuration
Service Minor Eqt
Customization Error VLANPORTSVCMIS 175 / 1 requests for the provisioned VLAN
Mismatch On Yes port.
CFG
2. Setup problem.

Table 118-66 describes the voice server alarms.

Table 118-66 Voice server alarms


Default
Category /
Probable cause / Specific TL1 severity / Alarm
Service Repair action
Mnemonic problem condition Default ID
affecting
reporting

Configuration Or xVPSINVCDE Major 29 / 5 Proc


Customization Error

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 87 sur 93

VoIP On No Download the required CDE file


CFG Configuration again. Activate the downloaded
File Error CDE file.

Configuration Or VoIP Check the xVPS configuration with


Critical Eqt
Customization Error Configuration xVPSCONFL 84 / 11 regard to the database (last
Loss On No database changes may be lost).
CFG

Database Failure VoIP Database Major Proc Download the required database
xVPSINVDB 29 / 4
DB Corrupted On No again. Restore the database.

Table 118-67 describes the VoIP alarms.

Table 118-67 VoIP alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

Configuration Or Access Termination Major Comm Check the identification


Customization Error Unknown In Call UNSUB 116 / 1
On Yes of the user port.
CFG Server

Configuration Or Check the subscriber


Major Comm
Customization Error Line Wiring Mix Up LNESHOWER 116 / 6 line for any line wiring
On Yes mix-up.
CFG

Communications Media Gateway Critical Comm


Subsystem Failure Controller MGWCLOSS 113 / 1 Check the environment.
Unreachable On Yes
COM

Equipment Malfunction Return Current To Major Eqt Check the environment


GRDKEY 116 / 2
EQP Ground On Yes and subscriber line.

System Overload Critical Eqt Restrain the rate that


Mg Overload MGOVERLOAD 117 / 5
SO On Yes MG admits calls.

Threshold Crossed QoS Packet Loss Major Qos Check the RTP packet
LQOSPKTLOSS 116 / 7
TCA Threshold On Yes loss.

Threshold Crossed Minor Qos


QoS Jitter Threshold LQOSJITTER 116 / 8 Check the RTP jitter.
TCA On Yes

Threshold Crossed Low QoS Delay Minor Qos


LQOSDELAY 116 / 9 Check the RTP delay.
TCA Threshold On Yes

Temperature
Major Eqt Check the environment
Unacceptable - HIGNTEM 116 / 3
On Yes and subscriber line.
TEMP

Table 118-68 describes the VOIP configuration alarms.

Table 118-68 VOIP configuration alarms


Default
Probable Category /
Specific severity / Alarm
cause / TL1 condition Service Repair action
problem Default ID
Mnemonic affecting
reporting

VCD config server name - Failed to


resolve the configuration server
name. Possible reasons are:
1. Domain name of FTP server not
resolvable.
Configuration Or
Possible solutions are:
Customization VCD Config Major 181 / Comm
Error VCDCFGFAILNAME 1. Verify config server name.
Name Failed On 1 Yes
CFG 2. Check the DNS server IP
address.
3. Try FTP from a different network
source, if it does not work, check
FTP server operation, configuration
and credentials.

VCDCFGREACH Major Comm

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 88 sur 93

Configuration VCD Config On 181 / Yes VCD config server reach - Cannot
Or Reach Failed 2 reach configuration server (the port
Customization cannot be reached, ICMP errors).
Error Possible reasons are:
CFG 1. Connectivity lost.
Possible solutions are:
1. Check network connectivity and
configuration.
2. Check for network alarms.
3. Perform a ping to the ONT.
4. Try FTP from a different network
source, if it does not work, check
the FTP server operation,
configuration and credentials.

VCD config server connect -


Cannot connect to configuration
server (due to bad credentials or
other fault after the port
Configuration responded). Possible reasons are:
Or 1. Invalid user login and password.
VCD Config Major 181 / Comm
Customization VCDCFGCONNECT Possible solutions are:
Error Connect Failed On 3 Yes
1. Verify config server
CFG configuration.
2. Try FTP from a different network
source, if it does not work, check
FTP server operation, configuration
and credentials.

VCD config server validate -


Cannot validate configuration
Configuration server. Possible solutions are:
Or 1. Verify config server
VCD Config Major 181 / Comm
Customization VCDCFGVALIDATE configuration.
Error Validation Failed On 4 Yes
2. Try FTP from a different network
CFG source,if it does not work, check
the FTP server operation,
configuration and credentials.

VCD config server auth - Cannot


authenticate configuration session
(for example, missing credentials)
Possible reasons are:
Configuration 1. Invalid user login and password.
Or VCD Config Major 181 / Comm Possible solutions are:
Customization Authentication VCDCFGAUTH
Error On 5 Yes 1. Verify the config server
Failed
CFG configuration.
2. Try FTP from a different network
source, if it does not work, check
FTP server operation, configuration
and credentials.

VCD config server timeout -


Timeout waiting for response from
configuration server. Possible
Configuration solutions are:
Or VCD Config 1. Verify config server
Major 181 / Comm
Customization Response VCDCFGTMOUT configuration.
Error On 6 Yes
Timeout 2. Check network alarms.
CFG 3. Try FTP from a different network
source, if it does not work, check
the FTP server operation,
configuration and credentials.

VCD config server fail - Failure


response received from
configuration server. Possible
reasons:
1. File not found.
Configuration
Possible solutions are:
Or
VCD Config Major 181 / Comm 1. Verify config server
Customization VCDCFGRESPERR
Error Response Error On 7 Yes configuration.
CFG 2. Verify that the configuration file
is present on the server.
3. Try FTP from a different network
source, if it does not work, check
FTP server operation, configuration
and credentials.

Configuration VCD Config File VCDCFGFILEERR Major 181 / Comm VCD config file error -
Or Error On 8 Yes Configuration file received has an
error. Possible reasons are:

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 89 sur 93

Customization 1. XML file received but contains


Error invalid data.
CFG Possible solutions are:
1. Replace the XML file on the
server.
2. Correct contents of XML file.

VCD subscription name - Failed to


resolve the subscription server
name. Possible reasons are:
Configuration 1. Domain name of subscription
Or VCD server not resolvable.
Major 181 / Comm
Customization Subscription VCDSUBSFAILNAME
Error On 9 Yes Possible solutions are:
Name Failed
CFG 1. Verify subscription server
name.
2. Check the DNS server IP
address.

VCD subscription reach - Cannot


reach subscription server (the port
cannot be reached, ICMP errors).
Configuration Possible reasons are:
Or VCD 1. Connectivity lost.
Major 181 / Comm
Customization Subscription VCDSUBSREACH
On 10 Yes Possible solutions are:
Error Reach Failed
1. Check network connectivity and
CFG
configuration.
2. Check for network alarms.
3. Ping the ONT.

VCD subscription connect -


Cannot connect to subscription
server (due to bad credentials or
Configuration other fault after the port
Or VCD responded). Possible reasons are:
Major 181 / Comm
Customization Subscription VCDSUBSCONNECT
On 11 Yes 1. Invalid user login and
Error Connect Failed password.
CFG
Possible solutions are:
1. Verify subscription server
configuration.

Configuration VCD subscription validate -


Or VCD Cannot validate subscription
Subscription Major 181 / Comm
Customization VCDSUBSVALIDATE server. Possible solutions are:
Error Validation On 12 Yes
Failed 1. Verify subscription server
CFG configuration.

VCD subscription auth - Cannot


authenticate subscription session
Configuration (eg missing credentials). Possible
Or VCD reasons are:
Subscription Major 181 / Comm
Customization VCDSUBSAUTH 1. Invalid user login and
Error Authentication On 13 Yes password.
Failed
CFG Possible solutions are:
1. Verify subscription server
configuration.

VCD subscription timeout -


Configuration Timeout waiting for response from
Or VCD subscription server. Possible
Subscription Major 181 / Comm solutions are:
Customization VCDSUBSTMOUT
Error Response On 14 Yes 1. Verify subscription server
Timeout
CFG configuration.
2. Check network alarms.

VCD subscription fail - Failure


Configuration response received from
Or VCD subscription server. Possible
Major 181 / Comm solutions are:
Customization Subscription VCDSUBSRESPERR
Error On 15 Yes
Response Error 1. Verify subscription server
CFG configuration.
2. Check network alarms.

VCD reboot request - A non-OMCI


Configuration management interface has
Or requested a reboot of the ONU.
VCD Reboot Major 181 / Comm Note: This alarm is used only to
Customization VCDREBOOTREQ
Error Request On 16 Yes indicate the request and not to
indicate that a reboot has actually
CFG taken place. This alarm is for
information only.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms Page 90 sur 93

Configuration VCD Mismatch VCDMIS Minor 181 / Comm The LT or ONT did not accept the
Or On 17 Yes configuration requests for the
Customization provisioned VCD (VoIP
Error Configuration Data). Possible
CFG reasons are:
1. The service is not supported
by the ONT.
2. Setup problem.
Possible solutions are to restart
the ONT or to deprovision the
VCD since it is not supported.

Table 118-69 describes the xDSL alarms.

Table 118-69 xDSL alarms


Default
Category /
Probable cause / severity / Alarm
Specific problem TL1 condition Service Repair action
Mnemonic Default ID
affecting
reporting

Excessive
Cancellation Abnormal Variation Minor Comm
189 /
Coefficient in Incoming XTCVARVIC Check the physical line.
On 1 Yes
Crosstalk
CANC

Excessive
Cancellation Abnormal Variation Minor Comm
189 /
Coefficient in Outgoing XTCVARDIST Check the physical line.
On 2 Yes
Crosstalk
CANC

Configuration Or
Customization Major Comm Check the peer modem type
38 /
Error TPS-TC Mismatch TPSTCMIS or change the TPS-TC mode
Off 25 Yes of the line.
CFG

Configuration Or Auto-Switching
Customization Between Major Comm Check for configuration data
223 /
Error ATMoADSL and AUTOSWITCHSTAT or physical line or peer
On 1 Yes
PTMoVDSL modem type
CFG Problem

1. Update profile parameters.


Configuration Init 2. Assure that the pilot tones
Configuration Init Critical Comm
Failure are not masked.
Failure At Near CFGERR 38 / 5
End On Yes 3. In case G.lite is used,
CIF
assure that the bit rates fit
within the standard.

Communications
Activation Failure Major 38 / Comm
Subsystem Failure CPEPOLICING Check the peer modem type.
CPE Policing On 24 No
COM

Vector Disorderly
Loss of Upstream Minor 38 / Comm
Leaving DLE Check the physical line.
Signal On 27 Yes
DLE

Excessive Severe
Excessive Severe Minor Comm
Errors ESE 38 / 4 Check the physical line.
Errors At Near End On Yes
ESE

Ensure that the standard


Forced RTX ARQ (ITU-T G.998.4) is
Initialization Activation Failure Major Comm
38 / supported at both ends (LT,
Failure Forced RTX FRTXINITF
On 26 Yes CPE) or modify or
Initialization Failure
FRTX unconfigure the
retransmission (RTX) profile.

Loss Of Cell Or Loss Of Cell Or Minor Comm


Packet Delineation Packet Delineation LCD 38 / 9 Check the quality of the line.
At Near End On Yes
LCD

Loss Of Frame Loss Of Frame At Minor Comm Check the modem


LOF 38 / 2
LOF Near End On Yes equipment.

Loss Of Margin Loss Of Margin At Minor Comm Check the physical line (new
LOM 38 / 3
LOM Near End On Yes disturbers).

Loss Of RMC Near End (LOR) LOS Minor Comm 1. Check the physical line.

http://127.0.0.1:60526/help/ntopic/com.alcatel.axs.gui.doc.isam52/html/7302_7330_R... 11/03/2018
118 - R5.3 alarms