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

4. Change the appropriate information.
5. Click OK when you are finished.
6. If you have changed the Initiator WWPN assignments, ensure that you update the LUN
assignments as well.
Deleting a Fibre Channel server connection
Deleting a Fibre Channel server connection stops access to volumes by servers using that server
connection. Access to the same volume by other servers continues.
1. In the navigation window, select the Fibre Channel server connection you want to delete.
2. Click the Details tab.
3. Click Server Tasks, and select Delete Server.
4. Click OK to delete the server.
Completing the Fibre Channel setup
Rescanning the disks
In the disk management tool, rescan the Fibre Channel disks to show the LUNs you just configured.
You will see an individual disk for every path, for each LUN, until you configure MPIO.
IMPORTANT: Do not use the LUN until you configure MPIO.
Setting up MPIO
1. Run the MPIO applet and choose the Discover Multi-paths tab.
2. Select the LEFTHANDP4000 disk for the Device Hardware ID.
3. Click Add.
4. Reboot the storage system when prompted.
Clustering server connections
You can cluster servers to assign multiple server connections to multiple volumes in a single
operation. Cluster existing servers or create new servers to add to the server cluster from the New
Server Cluster window. If you cluster servers that already have volumes assigned to them, all the
servers in the cluster gain access to all the volumes, and inherit the access permissions of the
original pair.
All clustered servers must have the same load balancing and volume access permission settings.
You can verify and update these settings when you create the server cluster. For information about
volume access permissions, see “Server connection permission levels” (page 211). For more
information about iSCSI load balancing, see “iSCSI load balancing” (page 238).
NOTE: When using a Fibre Channel connection to a Microsoft Cluster a situation can occur
where a node that owns the witness disk in the Microsoft Cluster fails over, but does not fail back.
In this case, Microsoft failover cluster quorum is never at risk. If any additional failures occur that
require failover/failback of the witness disk to maintain failover cluster quorum, that failover
happens properly.
See the Microsoft TechNet article http://social.technet.microsoft.com/Forums/en/
windowsserver2008r2highavailability/thread/a762606e-3f85-43a9-995b-d4fee95b08c1 for
more information.
Requirements for clustering servers
• Minimum of two servers for a cluster
• Same access level settings for all volumes assigned to the server cluster
208 Controlling server access to volumes