1. Alarms and KPIs
  2. Alarms and Events
  3. Policy and Charging Application (PCA) Alarms and Events (22700-22799)
  4. 22730 - Policy and Charging Configuration Error

22730 - Policy and Charging Configuration Error

Alarm Group:
PCA
Description:
Policy and Charging message processing could not be successfully completed due to a configuration error.
Severity:
Major
Instance:
<ConfigurationError>
HA Score:
Normal
OID:
pdraPdraConfigErrorNotify
Auto Clear Seconds:
300 (5 minutes)
Cause:
  • The session initiation request message was received with a missing or un-configured APN.
  • Binding capable session initiation answers was coming from an unconfigured PCRF.
  • The binding independent session initiation request was routed to an OCS that is not configured.
Diagnostic Information:
  • Check DSR configuration
  • Check Diameter message PCAP.

Recovery:

  1. If there is an unconfigured PCRF, it means the binding capable session initiation request was routed to a PCRF that is not configured in Policy and Charging, and then Configuration, and then Policy DRA, 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 and Charging, and then Configuration, and then Policy DRA, and then PCRFs. If the PCRF is not valid for the request, correct the routing table or tables included the PCRF.
    Also see measurement RxBindCapUnknownPcrf in the DSR Measurement Reference.
  2. If there is an unconfigured APN and if the APN string is valid, configure the APN at the NOAM using the Policy and Charging, 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.
    Also see measurements RxBindCapUnknownApn and RxBindDepUnknownApn in the DSR Measurement Reference.
  3. If there is a missing APN, investigate the policy client to determine why it is sending policy session initiation requests with no APN.
    Also see measurements RxBindCapMissingApn and RxBindDepMissingApn in the DSR Measurement Reference.
  4. If there are no PCRFs configured, configure PCRFs at the SOAM GUI for the site using Policy and Charging, and then Configuration, and then PCRFs.
  5. If there is an unconfigured OCS, it means that the binding independent session initiation request was routed to an OCS that is not configured in Policy and Charging, and then Configuration, and then Online Charging DRA, and then OCSs. This indicates a mismatch between the OCSs configuration and the routing configuration. If the OCS named in the alarm additional information is a valid choice for the request, configure the OCS at the SOAMP using Policy and Charging, and then Configuration, and then Online Charging DRA, and then OCSs. If the OCS is not valid for the request, correct the routing table or tables included the OCS.
  6. It is recommended to contact My Oracle Support.