Connecting Volumes To Multiple Subnets In A Multi-Site San Using The Microsoft Iscsi Initiator; Using Multiple Cluster Vips When Connecting To A Multi-Site San; Connecting Application Servers With Single Or Multiple Nics To A Multi-Site San - HP StoreVirtual 4000 Configuration Manual

Lefthand storage multi-site configuration guide

Hide thumbs Also See for StoreVirtual 4000:

Table of Contents

Figure 6 Multi-Site SAN mapping to subnets, VIPs, and application servers

1. Dual redundant GigE links

Connecting volumes to multiple subnets in a Multi-Site SAN using the Microsoft iSCSI initiator

Connecting to volumes in a multiple subnet configuration is similar to connecting to volumes in a

single-site configuration, with the following important differences:

You must configure all cluster VIPs for discovery, for proper failover/failback configuration of

a Multi-Site SAN. List the VIPs in the preferred order of connection. For example, if Site A is

the first preference for connection, put the VIP associated to Site A first in the discovery list.

You must also log on to the volumes with the default Target Portal setting.

Use the Virtual IP address of the cluster when connecting to volumes. In a multiple subnet

configuration, you must enter both of the VIPs of the multi-site cluster on all the application servers.

In addition, all the application servers must have the VIPs listed in the same order. A sample

Multi-Site SAN configuration is shown in

three sites: Site A, Site B, and Site C. Site A is primary.

On each application server, enter the cluster VIPs in the same order as on the Discovery tab

of the iSCSI Initiator Properties window.

Designing a Multi-Site SAN

Figure 7 (page

11). In this configuration, the cluster has

Table of Contents