User`s guide

Chapter 8 Virtual Host Bus Adapters (vHBAs) 143
Parameter Description
Note – The persistent binding can only apply to the target’s level but not to the
Logical Unit Numbers (LUNs) level. Therefore, an array-ordering problem could
arise in the network when a new LUN is added to the topology. In this case, the
persistent binding would need to be redone.
▼ Configure Persistent Mapping for an
Undeployed vHBA
A vHBA is considered deployed when it has been assigned to a slot/port and a
server ID (a server profile that is bound to a host physical connection). The remote
OS has already detected a specific target order. When a vHBA has already been
deployed, XgOS disallows users from changing (setting) this target order
dynamically (on-the-fly). Likewise, when a persistent mapping is already assigned
to a vHBA, XgOS disallows users from modify that persistent mapping. You cannot
add, delete, or modify specific entries. In summary, mapping can be specified only at
vHBA creation time (when the add vhba command is issued).
Parameter Description
add san map Creates an ordered mapping of devices identified by
World Wide Port Names (WWPN). The vHBA uses these
SAN map device IDs in this order. All devices discovered
by XgOS are subject to this binding filter. Missing devices
are skipped and no substitutes are made.
<map-name> User-defined name for a map to configure on a new
vHBA. A SAN map is the order in which the target disks
come up (become active).
<wildcard> Allows specifying selected wildcard characters (for
example, *) to facilitate executing a command for one or
more vHBAs.
entry <order> Order number in the remote OS. The order range is from
0 to 255.
entries Shows a table of all Persistent Mappings within a
configured SAN Map. Persistent Mappings are listed
numerically by the Order number assigned to each
Persistent Map when it was created.
<wwpn> World Wide Port Name. A 64-bit global address, where
each number is delimited by colons (:).