![]() TT-2, AT-2, TT-3 and AT-3 are optional but have to be configured in pairs. In an Egress Message Throttling Configuration Set, the Max EMR and the TT-1 and AT-1 Thresholds must be configured. If TT-x (where x can be 1, 2 or 3) of a Connection is exceeded, only Requests with Priority below x are throttled while Requests with Priority x or greater are allowed over the Connection. The offered rate is the value computed for EMRs configured with Convergence Time. For example, if TT-2 is configured, AT-2 must also be configured and if TT-3/AT-3 is configured, TT-2/AT-2 must be configured.Įach EMR Throttle and Abatement Threshold Level pair dictates how the Connection congestion state is updated as indicated in Table 14-6. The Max EMR and the TT-1 and AT-1 Thresholds must be configured. Throttle Threshold Levels - percent of Max EMR when the Threshold exceeds the specified Level, the Connection Congestion Level is raised. Throttle Threshold Levels and Abatement Levels 1, 2, and 3 -Ībatement Threshold Levels - percent of Max EMR when Threshold falls below the specified Level, the Connection Congestion Level is lowered.Max EMR - the maximum volume of traffic that can be served over a particular Connectionįor Peers that are deployed with multiple Connections, it is recommended as a guideline to set the Max EMR on each Connection by dividing the total capacity of the Peer by the number of Connections to the Peer.In each Egress Message Throttling Configuration Set, the following elements can be configured: If both, HSS-3 and HSS-4 exceed Throttle Threshold X, Requests with Priority less than X are discarded.Įgress Throttling Configuration Sets can be configured and assigned to Connections to control egress throttling behavior. If the Connection(s) to both HSS-1 and HSS-2 exceed Throttle Threshold X, Requests with Priority below X are routed to HSS-3 and HSS-4, while Requests with Priorities equal to or greater than X continue to be routed to HSS-1& HSS-2. The Preferred Route Group contains two HSSs, HSS-1 and HSS-2 each with one Connection and the Non-Preferred Route Group contains HSS-3 and HSS-4, each with one Connection. Alternate Routing Across Route Groups is attempted only if the Maximum Per Message Forwarding Allowed (configured in the Diameter Configuration Routing Option Sets) is not exceeded.įor example, a Route List is configured with two Route Groups. Eligible Peers or Connections from the other priority Route Groups of the Route List can be used to deliver a Request after all the Peers or Connections in the current Route Group are exhausted. PCEMT can be used in conjunction with the Alternate Routing Across Route Groups feature to route all throttled Requests using non-preferred Route Groups when all Connections in the preferred Route Group are congested. Interaction with the Alternate Routing Across Route Groups in a route List Feature ![]() If a Message Priority Configuration Set is not assigned to the Connection to specify the Priority, load shedding is still performed but it is primarily restricted to Requests as all Requests are assigned a Priority of 0. The User Configurable Message Priority feature provides the ability to configure Message Priority Configuration Sets that define the Priority. ![]() PCEMT sheds messages as the offered message rate gets closer to the configured Max EMR. The load shedding is performed by dropping Requests based on Priority and the offered message rate. The Per Connection Egress Message Throttling (PCEMT) feature works in conjunction with the User Configurable Message Priority feature to provide intelligent load shedding based on the volume of the offered load as shown in Table 14-6. The allowed maximum egress message rate (Max EMR) can be configured per Connection. The Egress Message Rate (EMR) on a Connection being throttled is equivalent to the egress Request rate + the egress Answer rate on the Connection. To assist with prevention of Diameter Peer overload, signalling provides a method for throttling the volume of Diameter Request traffic sent to a Peer Connection. To protect servers in periods of excessive load, explicit egress message throttling and user-configurable Connection Pending Transaction limiting can be used as messages are aggregated from several ingress Peers (clients) and can overload the egress Peer ( server).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |