Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2285178.1
Update Date:2017-07-12
Keywords:

Solution Type  Technical Instruction Sure

Solution  2285178.1 :   Oracle Communications EAGLE Element Management System (E5-MS) Health Check Procedure  


Related Items
  • Oracle Communications EAGLE (Software)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec EMS
  •  




In this Document
Goal
Solution


Created from <SR 3-15264400111>

Applies to:

Oracle Communications EAGLE (Software) - Version E5-MS 46.2 to E5-MS 46.3 [Release E5-MS 46.0]
Information in this document applies to any platform.

Goal

The Goal of this document is specifically to determine the Health of an EAGLE Element Management System (E5-MS) server which can be executed by customer
 

Solution

Acronym Description
HC Health Check
E5-MS EAGLE Element Management System

 

 

 

 

 

 

 

 1. Verification of Server Status

 Make Sure E5-MS server Login is Successful root@<ipaddress>'s password:
Last login: Thu Sep 11 14:13:15 2014 from 172.x.x.x
[root@ e5msserver ~]#
 Display source Operating System and E5-MS release version

 #uname -a

Example:

[root@e5ms ~]# uname -a
Linux mts-e5ms 2.6.32-358.el6.x86_64 #1 SMP Fri Feb 22 00:31:26 UTC 2013

# rpm –qa E5-MS

Example:

[root@e5ms ~]# rpm -qi E5-MS
Name : E5-MS Relocations: (not relocatable)
Version : 46.3.0.0.1 Vendor: Oracle
Release : 463.15.101 Build Date: Tue 18 Apr 2017 10:00:33 PM MSK
Install Date: Fri 02 Jun 2017 12:11:20 AM MSK Build Host: diablo-7
Group : Applications/System Source RPM: E5-MS-46.3.0.0.1-463.15.

 

 Ensure no partition is filled up to more than 80%.

#df -h

Example:

[root@e5ms ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/vg_mtse5msmoscow-lv_root
50G 24G 24G 50% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
/dev/sda1 485M 38M 422M 9% /boot
/dev/mapper/vg_mtse5msmoscow-lv_home
78G 34G 40G 46% /home

 

 Run command verify system
date
 #date
 Verify all active network
interfaces have got a valid IP
address assigned
 #ifconfig -a

 Verify Java version at
$JAVA_HOME

Java version should be 1.7.x or
higher.

 # $JAVA_HOME/bin/java -version

Sample Output:

java version "1.8.0_60"
Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)

 

 Check for e5msService configured on the system  #service e5msService status
 Check for httpd service configured on the system  #service httpd status
 Check uptime of the Server

 #uptime

Sample Output

[root@e5ms ~]# uptime
14:59:50 up 73 days, 7:41, 5 users, load average: 0.00, 0.02, 0.00

 Check process and memory status

 #ps -ef

# free

Run script to identify unique
ID

#sh /Tekelec/WebNMS/bin/UniqueIDLinux.sh

Sample Output:

Your Unique Machine ID is 2abVDag3S3
Note:
Please use the Unique Machine ID shown above useful to get the License Key.

 Login to E5-MS GUI to check whether alarms are getting updated

 Go to Fault Management - Alarm view

Verify alarms are getting updated from all STP configured

 

 

 Verify SNMP Traps

 If SNMP is configured in the NBI configuration via E5-MS GUI.

Verify the NMS configuration and make sure alarms are getting forwarded to NMS.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback