3.60.17 TxPdraAnswersGeneratedConfigErr

Measurement ID

11311

Measurement Group

P-DRA Diameter Exception

Measurement Type

Simple

Measurement Dimension

Single

Description

The number of Diameter Answers generated by P-DRA due to configuration errors when processing session initiation requests.

Collection Interval

5 min

Peg Condition

This measurement is pegged each time when P-DRA generates an error Anser in processing a session initiation request due to

• No PCRF being configured at the site where the request is processed OR
• No PCRF ID being found in PCRF table OR
• The APN contained in the request message not configured.

The measurement is pegged also each time when P-DRA generates an error Answer in processing a binding dependent session initiation request if the APN in te request is not configured in the Policy DRA and the site is configured to correlate on IMSI, MSISDN, or both and no other binding correlation key is successfully used for correlation.

Note:

In binding dependent request cases, this measurement is raised only when the Binding Not Found condition applies, the APN is unconfigured, and an IMSI or MSISDN was used as a possible correlation key.

Measurement Scope

All

Recovery

1. Check the P-DRA System OAM GUI Main Menu: Policy DRA, and then Configuration, and then PCRFs to ensure PCRFs are configured properly.
2. If there is an unconfigured PCRF, it means that the binding capable session initiation request was routed to a PCRF that is not configured in Policy DRA, and then Configuration, and then PCRFs at the site where the request was received. This indicates a mismatch between the PCRF's configuration and the routing configuration. If the PCRF is a valid choice for the request, configure the PCRF in Policy DRA, and then Configuration, and then PCRFs. If the PCRF is not valid for the request, correct the routing table or tables that included the PCRF.
   See also RxBindCapUnknownPcrf.
3. If there is an unconfigured APN and if the APN string is valid, configure the APN at the NOAMP using the Policy DRA, and then Configuration, and then Access Point Names screen. If the APN string is not valid, investigate the policy client to determine why it is sending policy session initiation requests using the invalid APN.
   See also RxBindCapUnknownApn and RxBindDepUnknownApn.
4. If there is a missing APN, investigate the policy client to determine why it is sending policy session initiation requests with no APN.
   See also RxBindCapMissingApn and RxBindDepMissingApn
5. If there are no PCRFs configured, configure PCRFs at the SOAM GUI for the site using Policy DRA, and then Configuration, and then PCRFs.
6. If needed, it is recommended to contact unresolvable-reference.html#GUID-F069C6FD-5BA3-4F31-AE9E-A187D5B5F729 for further assistance.