| Asset ID: |
1-72-2006752.1 |
| Update Date: | 2016-10-13 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
2006752.1
:
ELAP VIP Down Towards LSMS
| Related Items |
- Oracle Communications EAGLE (Software)
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec OS ELAP LSMS
|
In this Document
Created from <SR 3-10659564581>
Applies to:
Oracle Communications EAGLE (Software) - Version ELAP 9.0 and later
Information in this document applies to any platform.
Symptoms
ELAP was not associated to the LSMS and not taking updates.
Cause
User mentioned that network maintenance had been performed that would have interrupted the connection between the LSMS and ELAP. By design, when the active ELAP detects a network failure, it will initiate a switchover to the standby mate in hope that it has network access to the LSMS. During the switchover, the config database (EuiDB) hung and the data partition (drbd) experienced a split brain in which both servers assumed control of the partition.
ELAP 9 will experience a spontaneous reboot during a failover due to a bug in the drbd when the active server has been active for longer than a few days. When it reboots, the servers may require intervention to resolve conflicts and issues relative to which server is active and which is standby.
Solution
To correct the EuiDB, ELAP B was rebooted.
To correct the split brain, the resources and data were disconnected on ELAP B. The drbd on B was reconnected to ELAP A and synced to A.
References
<NOTE:1020199.1> - How to Upload Support Files to Oracle Such as Explorer and Crash Dumps
<NOTE:1312847.1> - Oracle Explorer Data Collector Resource Center
<NOTE:1019144.1> - Data Requirements reference: What data is needed in order to troubleshoot my software or hardware problem?
Attachments
This solution has no attachment
