Use the
Load Shedding Configuration section of the
Advanced Configuration page to edit, reorder, or add new rules at each level of busyness for a device based on the amount of backlog. To reach a configured level of busyness:
- The backlog of outstanding messages in a node crosses a predefined threshold for the level.
- The backlog has been above the busyness level threshold for a minimum amount of time.
At each level, the device can be configured to take one of the following actions (referred to as rules) until the busyness level clears:
- Accept the message.
- Drop the message.
- Reject new messages with a specific result code (the default is DIAMETER_TOO_BUSY).
Refer to MPE Default Load Shedding Rules and MRA Default Load Shedding Rules for more information on default rules.
Note: Configuration keys must also be used in configuring load shedding options. Contact My Oracle Support for assistance.
Configure the load shedding rules as follows:
The settings are applied to the selected device.