Error Code 512

Associated Error Category

Binding Found But Unable To Route

Description

A slave session could not be routed because, on polling the master, sessionRef was early too long.

Associated P-DRA Alarm/Event

N/A

Associated Measurement

SbrEarlyTooLongSrRemoved

Associated Diameter Interface / Message Type

• Gx/Gxx CCR-I
• Rx AAR
• Gx-Prime CCR-I

GUI Configurable

Yes

Recovery

1. Check Early binding Processing with PCRF Pool in the Error Resolution appendix of the Policy and Charging Application User Guide to investigate and understand the circumstances where the error occurs.
2. Go to the PCA SOAM GUI at Main Menu > Status & Manage > Server to obtain the Policy DRA DA-MP and binding SBR status.
3. Go to the Main Menu > Alarms & Events > View History to obtain the congestion alarm/event for Policy DRA DA-MP and/or binding SBR, if congestion occurs. Some congestion conditions may be released after a short while. The error may not persist after the congestion condition is gone.
4. Get the measurement report from Main Menu > Measurements > Report for, but not limited to, "SBR Binding Exception" and "Policy DRA Congestion" Measurement Groups.
5. Go to PCA NOAM GUI at Main Menu > Policy and Charging > Configuration > Policy DRA > Network-Wide Options to check the Maximum Early Binding Lifetime value. Re-configure the value if necessary.

   Note:

   The measurement SbrEarlyTooLongSrRemoved indicates the frequency at which binding sessionRefs are discovered in an early state for longer than expected. This unexpected condition could occur if the binding SBR was in congestion and load shedding prevented the session from being transitioned from the early state to a final state. It could also occur if the Maximum Early Binding Lifetime value is configured to be nearly equal to or shorter than the Diameter transaction timer.