| Asset ID: |
1-71-2205420.1 |
| Update Date: | 2017-02-01 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2205420.1
:
Diameter Signaling Router (DSR) Why Connections Went Unavailable After "network" Service Restart on MP servers
| Related Items |
- Oracle Communications Diameter Signaling Router (DSR)
|
| Related Categories |
- PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec DSR
|
In this Document
Created from <SR 3-13546477631>
Applies to:
Oracle Communications Diameter Signaling Router (DSR) - Version DSR 3.0 and later
Information in this document applies to any platform.
Goal
Why after a "service network restart" on MP servers, most of diameter links/connections went unavailable? And How to fix this?
Solution
When a “service network restart” is performed, it takes down all the interfaces including the loopback interfaces. There is one loopback interface per TSA. Messages are routed to this IP address and per the TSA they are sent to MP’s, the MP’s use the loopback to route the responses back to the peers. The loopback interface is added/configured on DA-MP servers at the time of TSA configuration if the software is running or when the DSR software is started. When executing the “service network restart” command, all loopback interfaces added for TSA will be deleted. IPFE floating connections will not be able to come up.
Therefore, the restart of the DSR process needs to be restarted after a network service restart.
Attachments
This solution has no attachment
