Oracle Communications EAGLE (Hardware)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec EMS
 

In this Document

Goal

Solution

Created from <SR 3-9854046331>

Applies to:

Goal

Statistics collection accidentally stopped on E5MS since the primary server was brought down for troubleshooting and secondary server was made active.

Solution

At the Eagle side; the priority1 for meas file transfer is Primary Server.
As the Primary Server is out of service but ping is accessible; so STP is considering it as active and not sending data to secondary server.

Reason for below mentioned changes:
EMS-02 is currently active server but as EMS-01 is still pingable from Eagle; so the measurement data is being sent there.
The data should be sent to EMS-02 which is priority 2.
So need is to:
EMS-02  >>>>> Priority 1
EMS-01  >>>>> Priority 2


This is for the time when EMS-01 comes back to service. Once EMS-01 is back to service; the priorities will need to be set to:
EMS-02  >>>>> Priority 2
EMS-01  >>>>> Priority 1

Please perform following steps on STP end:
  
1. Login to STP
2. Enter following commands:
3. chg-ftp-serv:app=meas:ipaddr=<Ip of primary>:prio=3
4. chg-ftp-serv:app=meas:ipaddr=<Ip of secondary>:prio=1
5. chg-ftp-serv:app=meas:ipaddr=<IP of primary>:prio=2
6. rtrv-ftp-serv to make sure priorities are now changed

<IP of Secondary> needs to be changed to priority 1. But for that; first you need to change <IP of Primary> to some other priority.

  
Whether this action will be required every time; this depends upon issue.
  
For example:
1. If Primary Server goes down and is no more pingable; the measurement will be sent automatically to second priority
2. If Primary server goes down but it is still pingable; the measurement data will still be transferred to first priority
  
Once the EMS01 is set back to primary; you will need to run following commands on Eagle:
  
1. Login to STP
2. Enter following commands:
3. chg-ftp-serv:app=meas:ipaddr=<IP of secondary>:prio=3
4. chg-ftp-serv:app=meas:ipaddr=<IP of Primary>:prio=1
5. chg-ftp-serv:app=meas:ipaddr=<IP of secondary>:prio=2
6. rtrv-ftp-serv to make sure priorities are now changed
  

Whenever the EMS service is down but the server itself is up; these manual changes will be required.

This is the measurement data flow:
1. csv from Eagle comes to /root/E5-MS/measurement/csvinput
2. Data is parsed to E5MS DB
3. csv is transferred to /var/E5-MS/measurement/csvoutput
Step 2 is done when E5MS application is running. Which is not running on the E5-MS01. That is why the data is not being transferred to output directory.
If processing is required; then this data needs to be sent to E5-MS02 input directory either directly from Eagle or from E5-MS01 input directory to E5-MS02 input directory.
 

This solution has no attachment