New Routes Stuck In Configured State In NOAM GUI but Event 10051 Reports Different Route Failure

Asset ID:	1-72-2350800.1
Update Date:	2018-02-07
Keywords:

Solution Type Problem Resolution Sure

Solution 2350800.1 : New Routes Stuck In Configured State In NOAM GUI but Event 10051 Reports Different Route Failure

Applies to:

Oracle Communications Diameter Signaling Router (DSR) - Version DSR 5.0 and later
Information in this document applies to any platform.

Symptoms

Attempts to add new routes on recently replaced servers was successful in the GUI but fails to transition to 'Deployed' status (remained 'Configured') and is not inserted into the route table on the server kernel. On the GUI, 10051 EventID MN alarm exists, but for a different route on this same server.

Changes

Servers were replaced with newer generation hardware. [This man not be the only possible trigger for this problem].

Cause

The reason for this condition is not the route being added, but the presence of the 10051 Event. This version of DSR--release 5.0--contains an audit mechanism to process new routes and deploy them to the server. This audit will stop at the first failure encountered. Hence, routes added when a 10051 Event alarm already exists will never be processed by the audit.
The cause is a condition of the audit mechanism introduced in DSR 5.0. The expectation is that route issues that result in this alarm will be addressed before new routes are added.

Solution

The cause of the 10051 Events for the route stated in the Event text needs to be addressed before the audit can successfully process the new route.

Addressing causes of 10051 is documented in MOS Knowledge articles 2192089.1 and 1925835.1 (latter may require TAC assistance).

Typical causes of 10051 include (not comprehensive):

Alarm indicates failure on insert
- duplicate routes exist
- route is to same network that server's interface IP resides within
Alarm indicates failure on the delete
- route is already deleted

Once the reason for the existing 10051 alarm is resolved, the audit will proceed to the next resource to be audited/processed. Note that other routes not yet in alarm may be encountered in this process; address each as encountered until new route gets processed and deployed. Note also that an asserted 10051 may not get cleared; reference Knowledge article 1967988.1 (contact TAC if document unavailable).

References

<NOTE:2192089.1> - Event ID 10051 Route Deployment Failed Is Raised After Adding Host Route

Attachments

This solution has no attachment