Chapter 3: Deploying Brocade Virtual Traffic Manager
This chapter describes the procedures for deploying Brocade Virtual Traffic Manager for load-balancing and optimizing Microsoft
Exchange 2013 Client Access Servers (CASs).
Requirements
• Brocade Virtual Traffic Manager (10.1 or later)
•
Microsoft Exchange 2013
Note: This deployment guide was certified while the product was with Riverbed and for 9.x or earlier versions of the Virtual Traffic
Manager.
The following are the prerequisites for deploying Exchange 2013 with Brocade Virtual Traffic Manager:
Exchange 2013 Port Requirements
The following table describes the ports used by Exchange 2013.
CAS Service Name Protocol TCP Port Description
Outlook Anywhere (OA) HTTPS
Autodiscover
Exchange Web Service (EWS)
HTTPS
HTTPS
Exchange Admin Center (EAC) HTTPS
Outlook Web Access (OWA)
Exchange ActiveSync (EAS)
Offline Address Book (OAB)
PowerShell (PS)
POP3
IMAP4
HTTPS
HTTPS
HTTPS
HTTPS
POP3 /
POP3s
IMAP4 /
IMAP4s
443
443
443
443
443
443
443
Also known as RPC over HTTP, allows clients using Microsoft Outlook
2007, 2010, and 2013 to connect to their Exchange servers.
Helps Outlook clients with automatic configuration and profile settings.
Enables client applications to communicate with Exchange servers.
New web-based management console that replaced Exchange
Management Console (EMC) and Exchange Control Panel (ECP) in
Exchange 2010.
Provides access to Outlook and e-mails through the web.
Provides the Exchange protocol for mobile synchronization.
Provides a copy of address lists that the user can access while disconnected from the network.
443
110, 995
Also known as Exchange Management shell, provides a powerful command-line interface for administration tasks and automation.
Post Office Protocol 3 is an e-mail protocol that supports offline mail processing.
143, 993 Interactive Mail Access Protocol is an e-mail protocol that supports offline and online mail processing.
Certificate Requirement
With the Exchange 2013 CAS server, all communications are done via HTTPS. Data is encrypted using certificates. A client can be redirected to a different CAS server in a CAS array other than the CAS server that authenticated it originally. To avoid having the client authenticate again against a different CAS server and to ensure that data is decrypted correctly, use a certificate that is shared among the CAS servers and Brocade Virtual Traffic Manager (vTM).
A single certificate with a Subject Alternative Name (SAN) extension can be used to support all services on a CAS server. If separate certificates are used for different services, ensure that those certificates are imported into all other CAS servers and vTMs.
Brocade Virtual Traffic Manager and Microsoft Exchange 2013 Deployment Guide
53-1003936-02
Page 9
