The OneCommand Utility User Manual
Page 192
WWN Management Commands
ChangeWWN
Supported by: Windows, Solaris SFS, Linux and VMware ESX Server
Syntax: ChangeWWN <WWPN> <New WWPN> <New WWNN> <Type>
Description; Changes the volatile or non-volatile state of WWNs. If the volatile change is requested on
an adapter that does not support Volatile WWNs, a “not supported” error is displayed.
Parameters:
WWPN - World Wide Port Name of object adapter.
New WWPN - New World Wide Port Name of object adapter.
New WWNN - New World Wide Node Name of object adapter.
Type - 0 = Volatile, 1 = Non-Volatile
Get Capabilities
(GetWWNCap on VMware and Solaris)
Supported by: Windows, Solaris SFS, Linux and VMware ESX Server
Syntax: hbacmd getwwncap <WWPN>
Description: Shows if volatile change is supported for the WWPN.
Parameters:
Note: Supported for Fibre Channel and FCoE adapters only.
Note: WWN Management validates WWNs very carefully to avoid name duplication. Therefore,
you may see error and warning messages if a name duplication is detected. It is strongly
recommended 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: 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 Server: After changing the WWN of an adapter, be sure your zon-
ing 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 4i: After changing the WWN of an adapter, you must reboot the
ESX 4i system before trying to access the adapter on that system. For information on
rebooting the ESX 4i system, refer to VMware documentation.
Note: For ESX 4.0 COS: If you are using the CIM Interface to access adapters, after
changing the WWN of an adapter you must restart the CIMOM (i.e. SFCB) on the
ESX 4.0 COS system before trying to access the adapter on that system. For
information on restarting the CIMOM, refer to VMware documentation.
