Using Automapping And Persistent Binding (Windows); Changing Automapping Settings - Emulex ProLiant BL620c - G7 Server User Manual

Onecommand manager application user manual (p004343-01a version 5.0, february 2010)
Table of Contents

Advertisement

3. Select the LUN Masking tab. This tab contains a list of the same set of LUNs that appear below
the SCSI target in the discovery-tree.
4. In the LUN list of the LUN Masking tab, select one or more LUNs. The Mask Selected LUNs,
Unmask Selected LUNs, Unmask All LUNs, Restore and Apply buttons become active as
appropriate. For example, if the LUN is currently unmasked, only the Mask Selected LUNs
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. Once you click Apply, changes cannot
be cancelled by clicking Restore. To unmask all LUNs, click Unmask All
LUNs. This button is always active. Be sure to also click Apply to commit the
changes.
6. Click Apply to commit the changes. An informational message is displayed that confirms the
mask status has changed and the red text changes to black.

Using Automapping and Persistent Binding (Windows)

Set up persistent binding on remote and local adapters. Global automapping assigns a binding type,
target ID, SCSI Bus and SCSI ID to the device. The binding type, SCSI Bus and SCSI ID can change
when the system is rebooted. With persistent binding applied to one of these targets, the WWPN, SCSI
Bus and SCSI ID remain the same when the system is rebooted. (Not available in read-only mode.)
The driver refers to the binding information at during system boot. When you create a persistent binding,
the OneCommand Manager application tries to make that binding dynamic. However, the binding must
meet all of the following criteria to be dynamic:
The SCSI ID (target/bus combination) specified in the binding request must not be mapped to
another target. For example, the SCSI ID must not already appear in the 'Current Mappings'
table under 'SCSI ID'. If the SCSI ID is already in use, then the binding cannot be made
dynamic, and a reboot is required.
The target (WWPN, WWNN or DID) specified in the binding request must not be mapped to a
SCSI ID. If the desired target is already mapped, then a reboot is required.
The bind type (WWPN, WWNN or DID) specified in the binding request must match the currently
active bind type shown in the Current Settings area of the Target Mapping tab. If they do not
match, then the binding cannot be made active.

Changing Automapping Settings

To change automapping settings:
1. Select Host or Fabric view.
2. In the discovery-tree, select the adapter port you want to set up with persistent binding.
3. Select the Target Mapping tab. All targets are displayed.
The OneCommand Utility User Manual
Page 131

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Onecommand manager 5.0

Table of Contents