Alcatel-Lucent

WiMAX
9753 OMC Alarm Dictionary
OMC Document
Reference Guide
Release W3 from MR1
3BK 21549 AAAA TQZZA Ed.10
Status RELEASED
Short title 9753 OMC Alarm Dictionary
All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel.
BLANK PAGE BREAK
2 / 8 3BK 21549 AAAA TQZZA Ed.10
Contents
Contents
1 OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Loss of communication between NE and OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.2 NE DNS resolution failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 NE SNMP authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4 NE SSL authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3BK 21549 AAAA TQZZA Ed.10 3 / 8
Contents
4 / 8 3BK 21549 AAAA TQZZA Ed.10
1 OMC
1 OMC
3BK 21549 AAAA TQZZA Ed.10 5 / 8
1 OMC
1.1 Loss of communication between NE and OMC
Specific Problem
Description
Loss of communication between NE and OMC
Probable Cause Communication subsystem failure
Alarm Type communication
Alarm Severity critical
Repair Action 1. Open a terminal from OMC-R Server
2. Check that the TCP/IP connection to NE exists. Type:
ping <NE IP address>
<NE IP address> is alive
3. If the message received is:
<NE IP address> is alive
there is a software problem on the OMC-R Server. Contact Alcatel
Technical Assistance Center.
4. If the ping command gives an error output, there is a routing problem.
Check that the correct Default Gateway address is set on server and
NE machine.
Check that the correct routing configuration is set on all routers. Refer to
Transport Network Requirements.
1.2 NE DNS resolution failure
Specific Problem
Description
NE DNS resolution failure
Probable Cause Communication subsystem failure
Alarm Type communication
Alarm Severity critical
Repair Action 1. Check that the DNS service is running on the DNS Server for NE. refer to
DNS/DHCP for NE Description and Installation Manual
2. If the service is running check the DNS configuration files.
An example of how to configure correctly the DNS files is described in
DNS/DHCP for NE Description and Installation Manual.
6 / 8 3BK 21549 AAAA TQZZA Ed.10
1 OMC
1.3 NE SNMP authentication failure
Specific Problem
Description
NE SNMP authentication failure
Probable Cause Communication subsystem failure
Alarm Type communication
Alarm Severity critical
Repair Action None
1.4 NE SSL authentication failure
Specific Problem
Description
NE SSL authentication failure
Probable Cause Communication subsystem failure
Alarm Type communication
Alarm Severity critical
Repair Action Check the following:
Check that the user/password used are the good ones
If the key used to connect through the secure connection is spoiled, it
must be removed.
To remove the key used to connect through the secure connection:
1. Check that the /<user_home_dir>/.ssh/known_hosts file is created
(To find the user home dir type cd command with no parameters)
2. Open with vi the known_hosts file
3. Remove the line beginning with the <NE IP address> or with the <NE
hostname>
4. Save the file and exit.
3BK 21549 AAAA TQZZA Ed.10 7 / 8
1 OMC
BLANK PAGE BREAK
8 / 8 3BK 21549 AAAA TQZZA Ed.10