About MAPI
SteelHead uses the secure inner channel between peer appliances to securely send MAPI traffic. Accelerate MAPI, you’ll also need to set up secure peering between the client-side and server-side appliance peers, setting the traffic type to All.
For out-of-path deployments where you want to accelerate MAPI Exchange by destination port, you’ll need to define a fixed-target in-path rule on the client-side appliance:
• Port 135—The Microsoft Endpoint Mapper port.
• Port 7830—The SteelHead port used for Exchange traffic.
• Port 7840—The SteelHead port used for Exchange Directory NSPI traffic.
For Exchange Server clusters that use load balancers such as Client Access Server (CAS) to provide dynamic MAPI port mappings, you’ll need to do one of these actions on the client-side SteelHead:
• Enable port transparency for MAPI traffic.
• Enable full transparency for MAPI traffic.
• Disable MAPI port remapping using the no protocol mapi port-remap enable command. Requires service restart.