The OneCommand Utility User Manual
Page 75
Target Mapping Field Definitions
Current Settings Area
•
Active Bind Type - WWPN, WWNN, or a destination identifier (D_ID).
•
Automapping - The current state of SCSI device automapping: enabled (default) or disabled.
•
Auto-Persistent Binding - The current state of the Auto-Persistent binding service. (Not available
on VMware ESX servers being managed through the CIM interface.)
Current Mappings Area
•
This table lists current mapping information for the selected adapter port.
Persistent Binding Configuration Area
•
This table lists persistent binding information for the selected adapter port. (Not available on
VMware ESX servers being managed through the CIM interface.)
Display Mode Radio Buttons
•
Show WWPN, Show WWNN or Show D_ID options enable you to choose how to display
information in the Persistent Binding Configuration table.
Target Mapping Buttons
•
Refresh - Click to refresh the Target Mapping tab.
•
Change Settings - Click to enable or disable automapping, choose a bind type and enable or
disable LUN mapping and unmasking. (Not available on VMware ESX servers being managed
through the CIM interface.)
•
Add Binding - Click to add a persistent binding.
•
Bind New Target - Click to add a target that does not appear in the Persistent Binding table.
•
Remove - Click to remove the selected binding.
•
Remove All Bindings - Click to remove all persistent bindings that are displayed.
Viewing Target Mapping (Linux and VMware ESX)
Use this tab to view target mapping. The Target Mapping tab is read-only.
To view target mapping:
1.
Select Host or Fabric view.
2.
Select the adapter port in the discovery-tree whose target mapping information you want to view.
3.
Select the Target Mapping tab.
Target Mapping Field Definitions
Current Settings Area
•
Active Bind Type - N/A
•
Automapping - N/A
Note: Persistent binding is not supported by the Linux 2.6 kernel, the Emulex 8.2 version of the driver for Linux
or by VMware ESX Server.
Note: Not all information is displayed on systems using CIM provider v1.2.1 on ESX 3i and
CIM provider v2.0 on ESX 4i.
