Virtual Connect SAN Cookbook.pdf - Sallustio.ch

The automatic failover allows smooth transition without much disruption to the traffic. However, the hosts
will have to perform re-login before resuming their I/O operations. Only a redundant SAN fabric with a
multipathing I/O driver running in the server Operation System can provide a complete transparent
transition.
Requirements
This configuration requires two VC SAN fabrics with two SAN switches that support NPIV, at least two
VC-FC modules, and at least four VC fabric uplink ports connected to the redundant SAN fabric.
For more information about configuring FC switches for NPIV, see "Appendix C: Brocade SAN switch
NPIV configuration" or "Appendix D: Cisco SAN switch NPIV configuration" or "Appendix E: Cisco
NEXUS SAN switch NPIV configuration" depending on your switch model.
Installation and configuration
Switch configuration
Appendices B, C and D provide the steps required to configure NPIV on the upstream SAN switch in a
Brocade, Cisco MDS or Cisco Nexus Fiber Channel infrastructure.
VC CLI commands
In addition to the GUI, many of the configuration settings within VC can be also be accomplished via a
CLI command set. In order to connect to VC via a CLI, open an SSH connection to the IP address of the
active VCM. Once logged in, VC provides a CLI with help menus. The Virtual Connect CLI guide also
provides many useful examples. Throughout this scenario the CLI commands to configure VC for each
setting are provided.
Configuring the VC module
Physically connect the uplink ports on the first VC-FC module to switch port in SAN Fabric 1
Physically connect the uplink ports on the second VC-FC module to switch port in SAN Fabric 2
Defining a new VC SAN Fabric via GUI
To configure the VC-FC modules from the HP Virtual Connect Manager home screen:
Scenario 2: VC SAN fabrics with Dynamic Login Balancing connected to the same redundant SAN fabric 36