Loss of Q2-communications
...................................................................................................................................................................................................................................
Alarm identifier MLQ2
Information Communication between the network element and the ITM-SC is lost.
Alarm category Processing error
ASAP dcn
Alarm severity
(default setting)
Information
Reporting state
(default setting)
Reported
Local indications
Cause The communication path between ITM-SC and the reporting network element
is out of order. To pinpoint the reason one has to look into how the
communication path has been or should be setup and if there are alarms
reported on intermediary network elements in the path between ITM-SC and
reporting network element. One would have to look for alarms such as
Loss of Q2-communication (MLQ2),
Q-LAN termination loopback failed (LANcTRM), transmission failures or
unit failures reported within the complete communication path between
network element and ITM-SC. If there are none then the DCC path settings
have to be checked between the network element and the first next associated
network element in the communication path.
Actions If the red fault LED on the System Controller is flashing, then the associated
alarm is
Q-LAN termination loopback failed (LANcTRM), and you
should check that alarm for cause and action.
If red fault LED on the System Controller is off:
• Check for relevant alarms on network elements in the communication path
towards the management system, and repair those first.
• If there are a few SCs reporting an MLQ2 alarm and they are all connected
to one (single) Q-LAN then pull the System Controllers out one by one
since one of them may have a LAN device failure. Pulling an SC does
(should) not break the Q-LAN.
• Connect the ITM-CIT to the reporting network element and check the
AREA (Login → Area). The nearest, in the path towards the ITM-SC,
missing network element in the area list is most probably also the network
element where the problem cause resides.
• Check the DCC settings in the communication path.
• If it is not possible to get association with the network element (after
initial installation) then the network element state may be “Isolated”. Make
local contact with the ITM-CIT to the network element involved and check
and confirm the DCN settings: Management → Overlay Comms Network
→ DCN → Edit → OK.
• It is also possible that the SEEPROM is defective, or the contents is
corrupt.
Alarm messages
...................................................................................................................................................................................................................................
365-312-803R7.2
Issue 4, May 2007
Alcatel-Lucent - Proprietary
See notice on first page
1-75
To Next Page
Loading...
