RxGyRoCcrEventNoDestHostMultOcsPoolMode

Measurement Group: OC-DRA Diameter Exception

Measurement Type: Simple

Measurement Dimension: Single

Description: The number of Gy/Ro CCR-E messages received without a Destination-Host when OC-DRA is operating in Multiple OCS Pools mode.

Collection Interval: 5 min

Peg Condition: Each time a Gy/Ro Credit-Control-Request message with the CC-Request-Type AVP set to EVENT_REQUEST (CCR-E) is received without a Destination-Host when OC-DRA is operating in Multiple OCS Pools mode.

Measurement Scope: All

Recovery:

  1. This measurement represents an exception condition in which Gy/Ro CCR-E messages are being received without containing a Destination-Host when OC-DRA is operating in Multiple OCS Pools Mode for Regionalized Routing. Each Gy/Ro CCR-E Request message not containing a Destination-Host when OC-DRA is operating in Multiple OCS Pools Mode is sent without modification to the OCS.
  2. When OC-DRA is configured to operate in Multiple OCS Pools Mode for Regionalize Routing, it relies on Range Based Address Resolution (RBAR) and mechanisms like Mediation to be invoked prior to PCA OC-DRA invocation to populate a Destination-Host and/or Destination-Realm AVPs for session initiation Requests (CCR-Is). The Destination-Host is used to represent a pool of OCS servers that can serve the Request. The Request is routed via the Diameter Routing Layer where the Peer Routing Table (PRT) rules will be used to route the Request to one of the OCS servers within the pool using priorities/weights configured in the Route List selected via the Peer Routing Table (PRT).
  3. RBAR and mechanisms like Mediation should be verified to be properly configured and invoked prior to PCA invocation.
  4. Contact My Oracle Support (MOS) for assistance if needed.
Parent topic: OC-DRA Diameter Exception measurements