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-1950618.1
Update Date:2017-02-15
Keywords:

Solution Type  Technical Instruction Sure

Solution  1950618.1 :   Starting EMS Services on Secondary Server After Primary Goes Down  


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-9918001561>

Applies to:

Oracle Communications EAGLE (Software) - Version EMS 43.x to EMS 44.x [Release EMS 43.0 to EMS 44.0]
Tekelec

Goal

Support required for netboss EMS-02 to make active with application after hardware fault diagnose at EMS01
 

Solution

Secondary EMS takes status of primary automatically.

No action is needed.

However; need to do a basic health check like

1. disk space check:

df -hk

Clean any old log files if there is a space constraint

2. DB status check

NBInfo.sh

3. Status of EMS applications:

sudo /etc/init,d/netboss checkall

Start any services manually that are not started.

4. Open a vncserver port for remote access to EMS GUI:

vncserver :44


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