3.60.1 BindCorrFailedUsingDefaultAPN

Measurement ID

11469

Measurement Group

P-DRA Diameter Exception

Measurement Type

Simple

Measurement Dimension

Single

Description

Number of times a binding correlation attempt using a non-specific subscriber binding key and default APN failed to retrieve a binding.

Collection Interval

5 min

Peg Condition

Each time a binding could not be retrieved from the SBR database using a non-specific binding key (such as IMSI or MSISDN) and the default APN configured, when the binding dependent session initiation request contains no APN. If both IMSI and MSISDN are configured in the binding key priority table, this measurement can be incremented twice for one binding dependent session initiation request.

Note:

This measurement applies when Policy DRA is working in Multi Pool Mode.

Note:

If a lower priority key results in a successful binding retrieval, the binding dependent session initiation request may be route successfully to the bound PCRF. This exception measurement does not satisfactorily indicate a Binding Not Found error condition and/or a Diameter routing failure.

Measurement Scope

Both

This measurement represents an exception condition in which the binding key priority is configured to use IMSI, MSISDN, or both, there is a Default APN configuration present that is used when the binding dependent session request has no APN value, but the binding lookup attempt results in a failure. This condition causes binding correlation to fail for the MSISDN or IMSI key types. If not other key is present int he request message and/or configured for correlation, the request is rejected using the Binding Not Found error condition. This condition causes Alarm 22730 Policy and Charging Configuration Error to be generated.

Recovery

1. Determine if one or more AF(s) is not including an APN (Called-Station-ID AVP) in the binding dependent session initiation request messages for subscribers for which the binding dependent sessions initiation request messages for subscribers for which the binding capable sessions were created using an APN other than the one that is currently configured as the Default APN in the Network-Wide Options GUI screen. If this condition is found to be true, the Default APN configuration needs to be correct.
2. Determine if one or more AF(s) is not including an APN (Called-Station-ID AVP) in the binding dependent session initiation request messages for subscribers for which the binding dependent sessions initiation request messages for subscribers for which the binding capable sessions were created using more than one APN, one of which may currently be configured as the Default APN in the Network-Wide Options GUI screen. If this condition is found to be true, it is recommended to switch to Single Pool Mode.