Users Guide

Broadcom OCM-APP-LPE-UG124-100
73
Emulex OneCommand Manager Application
User Guide
3. Select the LUN Masking tab (Figure 39). This tab contains a list of the same set of LUNs that appear below the FC target
in the discovery-tree (Figure 4).
4. In the LUN list of the LUN Masking tab, select one or more LUNs. The Mask Selected LUN(s), Unmask Selected
LUN(s), Unmask All LUNs, Restore, and Apply buttons become active as appropriate. For example, if the LUN is
currently unmasked, only the Mask Selected LUN(s) button is active.
5. Change the mask status: click Mask Selected LUN(s), Unmask Selected LUN(s) or Unmask All LUNs as appropriate.
Mask status changes appear in red text.
NOTE: To return all mask settings to their status before you started this procedure, click Restore before you click Apply.
If you click Apply, changes cannot be cancelled by clicking Restore. To unmask all LUNs, click Unmask All LUNs.
This button is always active.
6. Click Apply to commit the changes. An informational message confirms that the mask status has changed and the red
text changes to black.
7.16 Changing the WWPN and WWNN
The Maintenance tab (Figure 40) enables you to change the WWPN and the WWNN of a selected FC function. For
example, you can 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 (for example, driver parameters, persistent binding
settings, and so on) of the failed adapter.
NOTE: You cannot change WWPN and WWNN when FA-PWWN is enabled on the adapter port.
Three options exist for referencing WWNs:
 Factory Default WWN – The value that shipped from the factory. This value cannot be changed.
 Non-volatile WWN – A value that is saved in the adapter’s non-volatile flash memory, and that survives a reboot or a
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 to take effect. Volatile WWN changes are lost on systems
that power-cycle the adapters during the reboot.
To avoid address conflicts, do not assign a WWPN with the same WWPN as another FC function on your SAN.
The OneCommand Manager application checks the WWPN you specify against all the other detected WWPNs
and, if a duplicate is found, an error is displayed and the WWPN is not changed.
CAUTION! Changing volatile WWNs takes the selected adapter offline. Make sure that this adapter is not controlling a boot
device and that all I/O activity on this adapter is stopped before proceeding, or unexpected behavior or data loss
can result.
In an environment where preboot management exists, a WWPN or WWNN modified by the OneCommand Manager
application can be overridden by preboot management, such as BOFM and industry-standard CLP.
For example, in an environment with CLP or BOFM, the OneCommand Manager application modifies the WWNN or 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 or WWPN, or EFIBoot finds the BOFM and uses the default WWNN or WWPN by the
command from the BOFM.