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

The OneCommand Manager User Manual Page 132
Changing World Wide Name Configuration (FC/FCoE Ports Only)
The Maintenance tab enables you to change the World Wide Port Name (WWPN) and the World Wide
Node Name (WWNN) of a selected adapter port. For example, you might want to use an installed
adapter as a standby in case another installed adapter fails. By changing the standby adapter's WWPN
or WWNN it can assume the identity and configuration (e.g. driver parameters, persistent binding
settings, etc.) of the failed adapter.
There are three options for referencing WWNs:
• Factory Default WWN - As shipped from the factory.
• Non-Volatile WWN - Values that are saved in non-volatile adapter’s flash memory that survives a
reboot and/or power outage.
• Volatile WWN - A temporary value that is saved in volatile memory on the flash. If volatile WWNs
are set, they are used instead of the non-Volatile WWNs.
Volatile WWN changes require a warm system reboot in order to take effect. Volatile WWN
changes are lost on systems that power cycle the adapters during the reboot.
To change a port's WWPN or WWNN:
1. Do one of the following:
• From the View menu, click Group Adapters by Host Name.
Caution: Changing volatile WWNs takes the selected adapter offline.
Ensure that this adapter is not controlling a boot device and
all I/O activity on this adapter is stopped before proceeding.
Emulex assumes no responsibility for the consequences of
making volatile WWN changes on a boot adapter.
Note: To avoid address conflicts, do not assign a WWNN or WWPN with the OneCommand
Manager application if you also use another address management tool.
Note: The Change WWN button is disabled for adapters selected on remote hosts running
older versions of the OneCommand Manager application . The WWPN and WWNN in
the Pending Changes area show “n/a” instead of “none”. This also happens when the
remote host is busy processing some critical task and WWN Management cannot
obtain the current state of WWN management.
Note: In an environment where preboot management exists, A WWPN/WWNN modified by
the OneCommand Manager application can be overridden by preboot management
such as IBM BOFM and industry standard CLP.
For example:
1. In an environment with CLP/BOFM:
The OneCommand Manager application modifies the WWNN/WWPN. The
OneCommand Manager application requires a reboot to complete the change. After
reboot, the CLP string is sent during system boot and rewrites the WWNN/WWPN or
EFIBoot finds the BOFM protocol and uses the default WWNN/WWPN per BOFM's
command.
2. In environment without CLP/BOFM:
The OneCommand Manager application modifies the WWNN/WWPN. The
OneCommand Manager application requires a reboot to complete the change. The
system comes up and the OneCommand Manager application-modified WWNN/
WWPN is used.