Dell Emulex Family of Adapters - Manual (Page 141)

OneCommand™ Manager Application P010066-01A Rev. A
8. Managing Adapters and Ports
FC/FCoE
141
fails. By changing the standby adapter's WWPN or WWNN it can assume the identity
and configuration (for example, driver parameters, persistent binding settings, and so
on) of the failed adapter.
There are three options for referencing WWNs:

Factory Default WWN – As shipped from the factory. This value canot be
changed.

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.
Note: 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.
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: The following notes apply when changing FC/FCoE WWPNs or WWNNs:

To avoid address conflicts, do not assign a WWPN with the same WWPN as
another adapter on your SAN. The OneCommand Manager application
checks the WWPN you specify against all the other discovered WWPNs and
if a duplicate is found, an error is displayed and the WWPN is not be
changed.

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.