10.5 HP StoreVirtual Storage User Guide (AX696-96269, March 2013)

Planning server connections to management groups
Add each server connection that needs access to a volume to the management group containing
the volume. After you add a server connection to a management group, you can assign the server
connection to one or more volumes or snapshots. For more information, see
• “Planning iSCSI server connections to management groups” (page 203)
• “Planning Fibre Channel server connections to management groups” (page 206)
Using Controlling IP addresses
If you are using application-managed snapshots, you must assign a controlling server IP address
to each server you create in the CMC. The IP address to use depends on your application type
and environment. For Windows Failover Clusters, there will typically be more than one LeftHand
OS server associated with the cluster. For this environment, enter a controlling IP address for each
of the LeftHand OS servers in the Windows Failover Cluster. The table below describes which IP
address should be entered in the controlling server IP address field for the LeftHand OS server.
Table 64 Requirements for controlling IP addresses
NoteIP Address to UseApplication Environment
RequiredvCenter server IP addressVMware
Generally required
1
Physical IP address of the server
hosting the VSS Provider
Windows Volume Shadow Copy
Service (VSS)
RequiredPhysical IP address of each server
hosting a VSS Provider in the
Windows Failover Cluster. Since there
is likely more than one LeftHand OS
server in a Windows Failover Cluster,
enter one physical IP address (as just
described) in each of the related
LeftHand OS server dialogs.
Windows Failover Cluster Environment
1
Required for VSS:
• For pre-10.0 versions of LeftHand OS software when status updates are desired.
• If the application-managed snapshot was created by a client other than the current instance of the CMC (e.g., the
CLI, a schedule, etc.) and status updates are desired.
• For Fibre Channel connection types
Planning iSCSI server connections to management groups
NOTE: A server connection can be configured for both iSCSI and Fibre Channel connectivity.
However, there must be only one connection to a volume by a server.
Prerequisites
• Each server must have an iSCSI initiator installed.
• The initiator node name, or iqn string, for the iSCSI initiator. See “iSCSI and CHAP
terminology” (page 240).
• To use iSCSI VIP load balancing, you must use a compliant iSCSI initiator. Verify the initiator
compliance by going to the HP StoreVirtual 4000 Storage Compatibility Matrix at:
http://www.hp.com/go/StoreVirtualcompatibility
CAUTION: Using a noncompliant iSCSI initiator with load balancing can compromise volume
availability during iSCSI failover events.
Planning server connections to management groups 203