1 / 16

Diameter Agent Overload

Diameter Agent Overload. IETF 88 - Vancouver. Goal. Get consensus from the working group that Agent overload needs to be addressed If so, get guidance on the best path forward. Background. DOC-DT decided to not address handling of overloaded agents in base DOIC specification. Assertion.

lin
Download Presentation

Diameter Agent Overload

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Diameter Agent Overload IETF 88 - Vancouver

  2. Goal • Get consensus from the working group that Agent overload needs to be addressed • If so, get guidance on the best path forward

  3. Background DOC-DT decided to not address handling of overloaded agents in base DOIC specification.

  4. Assertion • A complete solution to handling Diameter overload requires addressing overload of all nodes in a Diameter network, including agents.

  5. Requirements – An agent is a Diameter node. • REQ 1: The solution MUST provide a communication method for Diameter nodes to exchange load and overload information. • REQ 12: When a single network node fails, goes into overload, or suffers from reduced processing capacity, the solution MUST make it possible to limit the impact of this on other nodes in the network. This helps to prevent a small-scale failure from becoming a widespread outage. • Other requirements also apply.

  6. Question 1 • Do we agree that we need to address the handling of Agent Overload?

  7. Behavior • Minimal new behavior required in clients • Behavior for a client is the same as the case where there is a direct connection between the client and multiple servers and the client gets a realm overload report from one of the servers. • Overload abatement is handled by peer on a hop-by-hop basis. • Agents are required to inspect overload reports and act on those from peer agents. • No change in loss abatement algorithm for throttled requests.

  8. Question 2 • How should agent overload handling be specified? • Option 1 – As an extension • Option 2 – As part of the base DOIC specification

  9. BACKUP SLIDES

  10. Use Cases Single Agent Redundant Agents Agent Chains Interaction between agent overload and end-point overload

  11. Agent OverloadMultiple Agents Architecture • Client has active connection to both agent 1 and agent 2 • Client shares the load between the two agents • The load distribution mechanism is local policy to the client Agent1 Server Client Agent2

  12. Agent OverloadMultiple Agents Client Agent1 Agent2 Server No overload Client sends x percent of traffic through agent 1 xxR x% xxA xxR y% Client sends y percent of traffic through agent 2 x + y = 100% xxA

  13. Agent OverloadMultiple Agents Client Agent1 Agent2 Server Agent1 becomes overloaded xxR xxA OLR (A1, R=20%) xxA Agent OVL report contains requested reduction xxR x%-20% Client adjusts distribution of load between agents based on the agent overload report xxA xxR y%+20% xxA

  14. Agent OverloadMultiple Agents Client Agent1 Agent2 Server Agent1 becomes 60% overloaded xxR xxA OLR (A1, R=60%) xxA Agent OVL report contains requested reduction Agent2 becomes 60% overloaded xxR xxA OLR (A2, R=60%) xxA Agent OVL report contains requested reduction xxR At this point the combined agent overload requires throttling to a level the agents are able to handle Throttle at (x% * .6) + (y% * .6))

  15. Agent Overload UC4Agent Chain Architecture Agent2-1 Client Agent1 Server1 Agent2-2

  16. Agent OverloadAgent Chain Client Agent 1 Agent2-1 Agent2-2 Server Agent1 becomes 60% overloaded xxR xxA OLR (A1, R=60%) xxA xxA Agent OVL report contains requested reduction Agent 1 acts on the report and removes it from the message Agent2 becomes 60% overloaded xxR xxA OLR (A2, R=60%) xxA Agent OVL report contains requested reductionAgent 1 acts on the report and removes it from the message xxR xxR At this point the combined agent overload requires throttling to a level the agents are able to handle Throttle at (x% * .6) + (y% * .6))

More Related