Cascade Deployment
Cascade configurations enable
Figure 10-3. Cascade Deployment
When the Client connects to a server in Site B, HP EFS WAN Accelerator1 and HP EFS WAN Accelerator2 are optimizing the connection. When the Client connects to a server in Site C, HP EFS WAN Accelerator1 and HP EFS WAN Accelerator3 are optimizing the connection.
The following rules apply to cascade deployments:
A cascade deployment can be created on either the client side or on the server side.
In a cascade deployment, only
Peering Rules Peering rules define what to do when an HP EFS WAN Accelerator receives an auto- discovery probe from another HP EFS WAN Accelerator.
In Figure
To configure this example, you do not need any rules on HP EFS WAN Accelerator1 or HP EFS WAN Accelerator3; you need to add peering rules on HP EFS WAN Accelerator2 to process normally connections going to Server1 and to pass all other connections so that connections to Server2 are not optimized by HP EFS WAN Accelerator2. You also need a default rule to pass through inner connections between HP EFS WAN Accelerator1 and HP EFS WAN Accelerator3 (by default connection to destination port 7800).
This example has the following parameters:
Server1 IP address is 10.0.2.2 on a /24
HP STORAGEWORKS ENTERPRISE FILE SERVICES WAN ACCELERATOR 2.1.5 DEPLOYMENT GUIDE | 111 |
10 - SERIAL CLUSTER AND CASCADE DEPLOYMENTS