You can configure load shedding rules to determine how a device reacts to a processing backlog. 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 each level of busyness, requests that have been queued longer than a configurable time are discarded without further processing, since the originator would have abandoned that request.
On the MRA Advanced Configuration page, there is a default action for each Busyness Level. The default level action is Accept for Level 1, which means to process the message by bypassing load shedding rules. Level actions are configurable.
The following tables show the default load-shedding rules for an MRA. For configuration information, see Configuring MPE and MRA Load Shedding Rules for more information.
| Rule Name | Actions |
|---|---|
| DefaultRule1 | Reject Gx CCR messages with DIAMETER_TOO_BUSY |
| DefaultRule2 | Reject Gxx CCR messages with DIAMETER_TOO_BUSY |
| DefaultRule6 | Accept Gx CCR messages with DRMP priority 0 |
| Rule Name | Actions |
|---|---|
| DefaultRule3 | Accept Drma LNR with ACCEPT |
| DefaultRule4 | Accept Drma LSR with ACCEPT |
| DefaultRule5 | Accept Drma RUR with ACCEPT |