Brocade Virtual Traffic Manager Platform Support
Brocade Virtual Traffic Manager is available on different platforms such as Linux, Solaris, Hyper-V, and VMware; it can be installed as pure software or as a virtual appliance. The Brocade Virtual Traffic Manager is available for download at http://my.Brocade.com
.
Configuration Steps for Multiple Virtual Servers for Each Exchange HTTP Service
The Exchange 2013 architecture supports the use of Layer 4 load balancing for CAS arrays since no protocol or service is rendered on the CAS server. Because of this architecture change, CAS servers are now stateless, and persistence on the Virtual
Traffic Manager is not required.
Deploying the Virtual Traffic Manager with multiple virtual servers requires provisioning an IP address for each virtual server created for Exchange HTTP services; this approach provides health monitoring per HTTP service, and each virtual server can be managed independently from one another.
Component Procedure Description
Virtual Traffic Manager
(repeat for each service)
Virtual Traffic Manager
(repeat for each service)
Virtual Traffic Manager
(repeat for each service)
Virtual Traffic Manager
(as required)
Create a traffic IP group for each Exchange HTTP service. A traffic IP group must be created for each Exchange
service. For details, see the “Creating Traffic IP
Groups” section.
Create a pool for each Exchange HTTP service. Enter the host name or IP address of the node along
with the TCP/UDP port. For details, see the “Creating
Pools” section.
Select a monitor for the pool.
Create a virtual server for each Exchange HTTP service. Create and associate a virtual server to the server pool of choice and the traffic IP group to listen on. For
details, see “Creating Virtual Servers” section.
Configure SSL decryption.
Select a health monitor for the pool. For details, see
“Creating Monitors” section.
Configure SSL decryption to enable SSL offloads.
For details, see “SSL Decryption” section.
Creating Traffic IP Groups
Identify Exchange HTTP services being offered by CAS servers, and create a traffic IP group for each service. Create a traffic IP group (also known as a virtual IP) on which the virtual server will be listening. To create a new traffic IP group:
1. Select Services > Traffic IP Groups, and scroll down to Create a new Traffic IP Group.
2. Fill in the fields as follows:
•
Name: A descriptive name for the traffic IP group (e.g., owa.company.com)
•
IP Addresses: An IP address that will be associated to the FQDN of this service
3. Click the Create Traffic Group button.
Repeat Step 1 through Step 3 for each Exchange HTTP service that will be load-balanced through Brocade Virtual Traffic
Manager.
Page 10 Brocade Virtual Traffic Manager and Microsoft Exchange 2013 Deployment Guide
53-1003936-02
Creating Pools
For each of the identified Exchange HTTP services, create a pool using the following steps:
1. Select Services > Pools, and scroll down to Create a new Pool.
2. Fill in the fields as follows:
•
Pool Name: A descriptive name for the pool (e.g., OWA Service)
•
Nodes: hostname:443 or ipaddress:443
•
Monitor: No monitor (this is covered in detail in a later section)
3. In the next screen, click Load Balancing.
4. Under Algorithm, select Perceptive.
5. Click the Update button to apply changes.
6. Click SSL Settings.
7. Check the Yes button next to ssl_encrypt.
8. Click the Update button to apply changes.
9. Select Pool > Connection Management, and make the following changes:
• Max_connect_time: 5–10 sec (left to user preference)
• Max_reply_time: 120 sec (default RPC and ISS timeout template in Exchange 2013)
• Queue_timeout: 120 sec (default RPC and ISS timeout template in Exchange 2013)
•
Node_connclose: yes (make sure to cut traffic to a node when failure occurs)
Repeat Step 1 through Step 9 to create a pool for each Exchange HTTP service.
Creating Monitors
This section details the steps to create health monitors.
Note: Advanced external monitors can be written in any language of choice and can be associated with the pool. Create a health monitor to monitor the health of a pool.
1. Select Catalogs > Monitors.
2. Scroll down to Create new monitor.
3. Give the new monitor a descriptive name.
4. Set the type to HTTP monitor and the scope to Node.
5. Click Create Monitor to create the monitor.
6. In the subsequent configuration page, scroll down and set use_ssl to Yes.
7. Change host_header to the service URL path (e.g., owa.company.com).
8. Change Path to /<Path>/healthcheck.htm (e.g., /OWA/healthcheck.htm).
9. Change status_regex to ^200$.
10. Change body_regex to .*200 OK.
11. Scroll down to Apply Changes, and click the Update button.
12. Select Services > Pools, and select the pool that the monitor will be attached to.
Brocade Virtual Traffic Manager and Microsoft Exchange 2013 Deployment Guide
53-1003936-02
Page 11
13. Scroll down and click Health Monitoring.
14. Add the appropriate health monitor.
Repeat Step 1 through Step 14 to create a health monitor for each Exchange HTTP service pool. Refer to the following table for the path that should be used for each service.
Service Name Path
Outlook Anywhere (OA)
Autodiscover
Exchange Web Service (EWS)
Exchange Admin Center (EAC)
Outlook Web Access (OWA)
Exchange ActiveSync (EAS)
Offline Address Book (OAB)
PowerShell (PS)
/rpc/healthcheck.htm
/Autodiscover/healthcheck.htm
/EWS/healthcheck.htm
/ECP/healthcheck.htm
/OWA/healthcheck.htm
/Microsoft-Server-ActiveSync/healthcheck.htm
/OAB/healthcheck.htm
/PowerShell/healthcheck.htm
Creating Virtual Servers
For each of the identified Exchange HTTP services, create a virtual server using the following steps:
1. Select Services > Virtual Servers, and scroll down to Create a new Virtual Server.
2. Enter the following:
• Virtual Server Name: A descriptive name for the virtual server (e.g., owa.company.com)
• Protocol: HTTP
• Port: 443
• Default Traffic Pool: The pool created for this service in the previous section
3. Click Create Virtual Server.
4. In the next screen, under Listening on, select Traffic IP Groups, and check the appropriate traffic IP group that was created for the OWA service.
5. Set Enabled to Yes.
6. Click the Update button to apply changes.
Repeat Step 1 through Step 6 to create a virtual server for each Exchange HTTP service.
SSL Decryption
In order to perform SSL decryption, the certificate and the private key used for the virtual server created in the previous task must be imported into the Virtual Traffic Manager.
1. Select Catalogs > SSL > SSL Certificates.
2. Click Import Certificate to import the appropriate certificate.
Page 12 Brocade Virtual Traffic Manager and Microsoft Exchange 2013 Deployment Guide
53-1003936-02
