When optimizing MAPI, it's important that ALL sessions between client and server are optimized by the same SteelHeads. If a SteelHead goes into admission control that could mean some sessions are…

Question

Options

• ADisable admission control on the client side SteelHead.
• BReduce the keep-alive for MAPI sessions.
• CConfigure alerts to be sent when the SteelHead nears admission control.
• DMAPI based admission control can be used.

• A
  11% (4)
• B
  3% (1)
• C
  81% (30)
• D
  5% (2)

Explanation

Example: Issue: Outlook clients are experiencing issues with connectivity through the Riverbed Steelhead Appliance. Solution: Outlook can open multiple connections to an Exchange server, and Outlook can break if some connections are optimized while others are not, and these situations can occur when the Steelhead reaches Admission Control. RiOS 6.1 has implemented new "MAPI-specific admission control" alarm which is meant to prevent MAPI connections from breaking or hanging if approaching that threshold. Note: The MAPI protocol uses several TCP sessions between the client and the server. When doing Latency Optimization on the MAPI protocol, all these TCP sessions between that client and that server need to be optimized between the same two Steelhead appliances. When one of the Steelhead appliances is close to admission control, there is a chance that not all these TCP sessions will become optimized, with a bad result for the client. To overcome this possibility, you can configure the Steelhead appliance to not do MAPI Latency Optimization when it is close to admission control.

No community discussion yet for this question.