HP Cisco MDS 9216 - Fabric Switch Configuration Manual page 1005

Cisco mds 9000 family fabric manager configuration guide, release 3.x (ol-8222-10, april 2008)
Hide thumbs Also See for Cisco MDS 9216 - Fabric Switch:
Table of Contents

Advertisement

Chapter 50
Configuring iSCSI
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m
Optionally set the AuthUser field if authentication is enabled. Also see the
Step 8
Authentication" section on page
Step 9
Click Create to create this iSCSI initiator.
If the system-assign option is used to configure WWNs for an iSCSI initiator, when the configuration is
Note
saved to an ASCII file the system-assigned WWNs are also saved. Subsequently if you perform a write
erase, you must manually delete the WWN configuration from the ASCII file. Failing to do so can cause
duplicate WWN assignments if the ASCII configuration file is reapplied on the switch.
Making the Dynamic iSCSI Initiator WWN Mapping Static
After a dynamic iSCSI initiator has already logged in, you may decide to permanently keep the
automatically assigned nWWN/pWWN mapping so this initiator uses the same mapping the next time it
logs in.
You can convert a dynamic iSCSI initiator to static iSCSI initiator and make its WWNs persistent (see
"Dynamic Mapping" section on page
You cannot convert a dynamic iSCSI initiator to a static iSLB initiator or a dynamic iSLB initiator to a
Note
static iSCSI initiator.
Making the dynamic pWWNs static after the initiator is created is supported only through the CLI, not
Note
through Device Manager or Fabric Manager. In Fabric Manager or Device Manager, you must delete and
then recreate this initiator to have the pWWNs static.
Checking for WWN Conflicts
WWNs assigned to static iSCSI initiators by the system can be inadvertently returned to the system when
an upgrade fails or you downgrade the system software . In these instances, the system can later assign
those WWNs to other iSCSI initiators (dynamic or static) and cause conflicts.
You can address this problem by checking for and removing any configured WWNs that belong to the
system whenever such scenarios occur.
To permanently keep the automatically assigned nWWN mapping using Fabric Manager, follow these
steps:
Step 1
Choose End Devices > iSCSI in the Physical Attributes pane.
You see the iSCSI tables in the Information pane (see
Step 2
Click the Initiators tab.
You see the iSCSI initiators configured.
Step 3
Check the Persistent Node WWN check box for the iSCSI initiators that you want to make static.
Click the Apply Changes icon to save these changes.
Step 4
OL-16184-01, Cisco MDS SAN-OS Release 3.x
50-28.
50-17).
Figure
Cisco MDS 9000 Family CLI Configuration Guide
Configuring iSCSI
"iSCSI Session
50-5).
50-19

Advertisement

Table of Contents
loading

Table of Contents