Major Alarm ''AS Unvailable'' Is Raised For All MPE And Then Auto Clears

Asset ID:	1-71-2180177.1
Update Date:	2017-10-12
Keywords:

Solution Type Technical Instruction Sure

Solution 2180177.1 : Major Alarm ''AS Unvailable'' Is Raised For All MPE And Then Auto Clears

Applies to:

Oracle Communications User Data Repository - Version UDR 10.0 and later
Information in this document applies to any platform.

Goal

Explain why are we receiving the alarm, "AS unavailable" on the Active NOAM during our OCUDR Migration.

Solution

These alarms are due to the fact that the DR site had not yet been fully configured for DIAMETER traffic.

Explanation:

As soon as the DR site is added to the NOAM, the OCUDR will attempt to deliver PNRs through the MPs on that site, regardless of if the connections between the MPEs and the MPs on the DR site have been configured, enabled, or if traffic is flowing or not.

When attempting to deliver PNRs, the UDR application running on the active NO will use a round-robin approach to send the PNR via one of the MPs. If a delivery attempt is made via an MP on a site that does not have a direct Diameter connection to the MPE, but another MP on the same site does, then the PNR delivery will be "hopped" across to an MP instance (on that site) that does have a Diameter connection. If no MP on the site has a connection, the delivery attempt will fail (potentially eventually causing an "AS Unavailable" scenario).

Every MPE must be connected to at least one (preferably two MP instances, running on different physical servers) MP per site.

The delivery attempt was made through an MP on the DR site, and neither that MP instance or another MP instance had a connection which caused the failure and generated the Alarm.

Once the DIAMETER connections are properly configured and activated the alarms should clear along with any possible Notification Table alarms.

Attachments

This solution has no attachment