9753 Alarm Dictionary
Transcript of 9753 Alarm Dictionary
-
8/11/2019 9753 Alarm Dictionary
1/8
Alcatel-LucentWiMAX
9753 OMC Alarm Dictionary
OMC Document
Reference Guide
Release W3 from MR1
3BK 21549 AAAA TQZZA Ed.10
-
8/11/2019 9753 Alarm Dictionary
2/8
Status RELEASED
Short title 9753 OMC Alarm Dictionary
All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel.
BLANK PAGE BREAK
2 / 8 3BK 21549 AAAA TQZZA Ed.10
-
8/11/2019 9753 Alarm Dictionary
3/8
Contents
Contents
1 OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1 Loss of communication between NE and OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.2 NE DNS resolution failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 NE SNMP authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 NE SSL authentication failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
3BK 21549 AAAA TQZZA Ed.10 3 / 8
-
8/11/2019 9753 Alarm Dictionary
4/8
Contents
4 / 8 3BK 21549 AAAA TQZZA Ed.10
-
8/11/2019 9753 Alarm Dictionary
5/8
1 OMC
1 OMC
3BK 21549 AAAA TQZZA Ed.10 5 / 8
-
8/11/2019 9753 Alarm Dictionary
6/8
1 OMC
1.1 Loss of communication between NE and OMC
Specific ProblemDescription
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
is alive
3. If the message received is: is alive
there is a software problem on the OMC-R Server. Contact AlcatelTechnical 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 andNE machine.
Check that the correct routing configuration is set on all routers. Refer toTransport Network Requirements.
1.2 NE DNS resolution failureSpecific ProblemDescription
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 Manual2. If the service is running check the DNS configuration files.
An example of how to configure correctly the DNS files is described inDNS/DHCP for NE Description and Installation Manual.
6 / 8 3BK 21549 AAAA TQZZA Ed.10
-
8/11/2019 9753 Alarm Dictionary
7/8
1 OMC
1.3 NE SNMP authentication failure
Specific ProblemDescription
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 ProblemDescription
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 //.ssh/known_hostsfile 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 or with the
4. Save the file and exit.
3BK 21549 AAAA TQZZA Ed.10 7 / 8
-
8/11/2019 9753 Alarm Dictionary
8/8
1 OMC
BLANK PAGE BREAK
8 / 8 3BK 21549 AAAA TQZZA Ed.10