The TCP connections between the
Diameter proxy (Diamproxy) and the configured peers for different endpoints can
either be in Open or Closed state. The state of these TCP connections for every
peer (or endpoints) is maintained at the Diamproxy and the clients
(sessmgrs/aaamgrs), for enabling communication with these peers through the
Diamproxy. If the connection status of sessmgrs/aaamgrs is IDLE and the
Diamproxy is in OPEN state, then the Diameter messaging failures, resulting in
call failures, can be seen. This is the primary reason an audit mechanism and
auto-correction is required and useful.
Due to network conditions, the connection state can change randomly.
If this change is not communicated appropriately, it can result in
discrepancies regarding connection state at the clients. Similarly, when a new
peer is configured, the clients initiates PIN Peer messages to Diamproxy to
notify the new peer configuration. Due to the throttling done at the Diamproxy,
some of the PIN Peer messages get dropped. This can also result in
discrepancies in connection state at the clients.
This feature helps in auto-detecting, and correcting these
discrepancies by Peer Connection Status Audit mechanism between the Diamproxy
and Diabase clients. The Diamproxy periodically publishes current connection
status of Diameter peers across all endpoints to the registered Diabase clients
(sessmgr/aaamgr tasks). The Diabase client audits the current connection status
and takes corrective action if there is any discrepancy in connection status.
How It Works
Following is a brief
overview of how this feature works:
initiates endpoint peer connection status audit process with sessmgr and
If there is any
discrepancy in peer connection status, then the sessmgr and aaamgr initiate an
in peer connection status between Diamproxy and sessmgr/aaamgr gets corrected
within pre-defined time interval.
After any type
of recovery event and peer connection status audit process, there is no race
condition between peer connection status reconciliation during startup.
The Audit is delayed
by 3 minutes for connection stabilization when any of the following events
-> Chassis state moves from Standby to Active.
migration -> Start AUDIT 3 minutes from migration end time.
migration -> Same as Diamproxy task restart.
Diamproxy Peer Connection Status Audit
This section provides information
about CLI commands available in support of the feature.