MRA Default Load Shedding Rules

You can configure load shedding rules to determine how an MRA device reacts to a processing backlog. (Refer to Configuring Load Shedding for an MRA Device.) This state is called “busyness.” Levels of busyness can be configured to accept, reject, or drop select messages at each level. An MRA has two busyness levels. At any level of busyness, request that have been queued longer than a configurable time are silently discarded without further processing, since the originator would have already given up on that request.

On the MRA Advanced Configuration page, there is a default Level Action for each busyness level. The valid actions are:

Accept: (Default) Processes the message by bypassing load shedding instead of rejecting it.
Drop: Drops and does not process the message.
Answer With: Selects an appropriate code to answer the message.
Answer With Code: Allows you to manually enter the code to answer the message.
Vendor ID: Allows you to manually enter a specific ID for answering the message.

Level actions are configurable. The Table 1 and Table 2 tables show the default load-shedding rules for an MRA device.

The default action for Level 1 is Accept.

MRA Busyness Level 1 Rules
Rule Name	Actions
DefaultRule1	Reject Gx CCR messages with DIAMETER_TOO_BUSY
DefaultRule2	Reject Gxx CCR messages with DIAMETER_TOO_BUSY

The default action for Level 4 is Drop, which applies to all messages other than the Drma messages that are accepted by default.

Note: The DRMA rule configuration is only displayed when the Diameter-based protocol is in use.

MRA Busyness Level 2 Rules
Rule Name	Actions
DefaultRule3	Accept Drma LNR with ACCEPT
DefaultRule4	Accept Drma LNR with ACCEPT
DefaultRule5	Accept Drma LNR with ACCEPT