Emulex OneCommand Manager Application User Manual (P006979-01A Version 5.2, August 2011)

The OneCommand Manager User Manual Page 254
WWN Management Commands
ChangeWWN
Supported by: Windows, Solaris, Linux and VMware ESX
Syntax:
hbacmd ChangeWWN <WWPN> <New WWPN> <New WWNN> <Type>
Description: This command changes the volatile or non-volatile state of WWNs. If the volatile change is
requested on an adapter that does not support volatile WWNs, it returns a “not supported error.”
Parameters:
WWPN - Adapter’s WWPN
New WWPN - New adapter’s WWPN
New WWNN - New adapter’s WWNN
Type:
0 = Volatile
1 = Non-Volatile
Note: Supported for FC/FCoE adapter ports only.
Note: WWN Management validates WWNs carefully to avoid name duplication. Therefore,
you may see error and warning messages if a name duplication is detected. Emulex
strongly recommends that the activation requirement be fulfilled after each WWN change
or restore. When running with “pending changes”, some diagnostic and maintenance
features are not allowed.
Note: For managing ESX/ESXi hosts from a Windows client, add the m=cim option to
the command. The default CIM credentials must be set using the SetCimCred
command. See “SetCimCred” on page 244.
Note: When a volatile change is supported, a reboot is required to activate the new
setting. Volatile names are active until system power-down or adapter power-cycle.
Note: For VMware ESX: After changing the WWN of an adapter, be sure your zoning
settings are updated before you reboot your ESX server. If the zoning is not updated
before your reboot, the subsequent boot may take a long time.
Note: For VMware ESX: After changing the WWN of an adapter, you must reboot the
ESX system before trying to access the adapter on that system. For information on
rebooting the ESX system, refer to VMware documentation.
Note: For ESX COS: If you are using the CIM interface to access adapters, after
changing the WWN of an adapter you must restart the CIMOM (that is, SFCB) on the
ESX COS system before trying to access the adapter on that system. For information
on restarting the CIMOM, refer to VMware documentation.