Adding server connections to management groups, Prerequisites, Guide for servers – HP LeftHand P4000 Virtual SAN Appliance Software User Manual
Page 198: Prerequisites guide for servers
Figure 87 Server assignments in the navigation window and the Volumes and Snapshots tab
1. Servers from a version 7.0 management group in the navigation window
2. Volumes and Snapshots tab shows the assigned volume that the server can access
Adding 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
connections access to volumes” (page 203)
.
Prerequisites
•
Each server must have an iSCSI initiator installed.
•
The initiator node name, or iqn string, for the iSCSI initiator. See
.
•
To use iSCSI load balancing, you must use a compliant iSCSI initiator. Verify the initiator
compliance by going to the HP P4000 SAN Solutions Compatibility Matrix at:
CAUTION:
Using a noncompliant iSCSI initiator with load balancing can compromise volume
availability during iSCSI failover events.
Guide for servers
For detailed information about using iSCSI with the P4000 SAN Solution, including load balancing
and CHAP authentication, see
“iSCSI and the HP P4000 SAN Solution” (page 230)
.
Table 57 Characteristics for servers
Description and requirements
Item
Name of the server that is displayed in the CMC. The server
name is case sensitive and cannot be changed after the
server is created.
Name
[Optional] Description of the server.
Description
Not used for the Application Aware Snapshot Manager
on Windows.
Controlling Server IP Address
Required for the Application Aware Snapshot Manager
on VMware. IP address of the Microsoft Windows server
that is hosting the vCenter Server.
Optional for using VSS on Windows servers.
Allows the server to connect to the client using an iSCSI
initiator.
Allow access via iSCSI
198 Controlling server access to volumes