HP 3PAR Citrix Implementation Guide

Example: The system is booted through an internal SCSI boot disk and has a device instance
sda, which is excluded from being seen by the device mapper by adding the devnode
blacklist structure. The resulting /etc/multipath.conf file blacklist section appears as
follows:
# cat /etc/multipath.conf
blacklist {
wwid 26353900f02796769
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z]"
devnode "^sda$"
devnode "^sda[0-9]"
devnode "^cciss!c[0-9]d[0-9]*"
}
NOTE: Add other devices as necessary to the blacklist structure as per the configured host.
Enabling Multipath
If multipathing has not yet been enabled, use the following procedure to enable multipathing on
each Citrix host with Citrix XenCenter. For details, see Citrix XenServer Design: Configuring
Multipathing for XenServer, available on the following website:
Citrix Knowledge Center
1. In the Resources pane, select the server and set it to Maintenance Mode.
2. On the General tab, click Properties, then click on the Multipathing tab.
3. To enable multipathing, select the Enable multipathing on this server check box.
4. Click OK to apply the new setting and close the dialog box.
5. Exit from Maintenance Mode.
NOTE: Multipathing can also be enabled by using the Citrix XenServer CLI. For details, see the
Citrix XenServer Administrator’s Guide for details, available at the Citrix Knowledge Center:
Citrix Knowledge Center
HP 3PAR OS Persistent Ports
The HP 3PAR OS Persistent Ports (or virtual ports) feature minimizes I/O disruption during an
HP 3PAR StoreServ Storage online upgrade or node-down event (online upgrade, node reboot,
or cable pull test). Port shutdown or reset events do not trigger this feature.
Each FCoE target storage array port has a partner array port automatically assigned by the system.
Partner ports are assigned across array node pairs.
HP 3PAR OS Persistent Ports allows an HP 3PAR StoreServ Storage FCoE port to assume the identity
(port IP address) of a failed port while retaining its own identity. Where a given physical port
assumes the identity of its partner port, the assumed port is designated as a persistent port. Array
port failover and failback with HP 3PAR OS Persistent Ports is transparent to most host-based
multipathing software, which can keep all of its I/O paths active.
NOTE: Use of HP 3PAR OS Persistent Ports technology does not negate the need for properly
installed, configured, and maintained host multipathing software.
For a more complete description of the HP 3PAR OS Persistent Ports feature, its operation, and a
complete list of required setup and connectivity guidelines, see:
• the HP Technical white paper HP 3PAR StoreServ Persistent Ports (HP document
#F4AA4-4545ENW)
This document is available on the following HP SC website:
24 Connecting a Host with Fibre Channel/FCoE