Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2259161.1
Update Date:2017-04-27
Keywords:

Solution Type  Technical Instruction Sure

Solution  2259161.1 :   Diameter Signaling Router Appears to Assign a Disabled Connection to an Unrelated DA-MP Server  


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
Goal
Solution


Created from <SR 3-14753311561>

Applies to:

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

Goal

The goal of this article is to explain why it appears that the DSR may assign an unrelated DA-MP server to some connection types when down or disabled.

Solution

Connections are configured as nailed-up (i.e. associated to a specific DA-MP IP interface via Local Node) or as IP Front End (IPFE) Responder connections associated with an IPFE Target Set Address (TSA).  In the latter case, multiple DA-MPs are configured within the Target Set and any one of them may become host to the connection when it is established.

For IPFE-based connections that are not established (e.g. administratively disabled or the connection failed), no MP has been assigned so the server currently acting as the DA-MP Leader within the DA-MP Multi-Active Cluster Server Group will report the connection status to the DSR Site OAM (SOAM) GUI under Main Menu / Diameter / Maintenance / Connections.  On the Connections screen, the 'MP Server Hostname' shown for these connections will be the DA-MP Leader.

If the DA-MP Leader is not among the DA-MPs specified for the IPFE's Target Set, then the appearance of the DA-MP Leader under the 'MP Server Hostname' column for the disabled or down IPFE Responder connection may provide the appearance that the wrong DA-MP has been assigned.  Instead, the DA-MP Leader is only reporting the status.  Upon successful transport handshake and Diameter CER/CEA exchange, the DA-MP server selected by the IPFE from among the configured Target Set will report the status and appear under the 'MP Server Hostname' column on the Diameter / Maintenance / Connections screen.

 

Another possible misconception arising from the DA-MP Leader reporting the disabled or down IPFE Responder connections is that if many are in that state, viewing the Diameter / Maintenance / Connections screen's 'MP Server Hostname' column may make it appear that one MP server -- the DA-MP Leader -- is unnaturally overloaded with connection assignments relative to other available DA-MP servers.  But again, this is only a consequence of reporting, not the actual assignment of connection host.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback