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
Assigning WWNs to iSLB Initiators
An iSLB host is mapped to an N port's WWNs by one of the following mechanisms:
Assigning WWNs for iSLB initiators is the same as for iSCSI initiators. For information on dynamic and
static mapping, see the
We recommend using the SystemAssign system-assign option. If you manually assign a WWN, you
must ensure its uniqueness (see the
previously assigned WWNs.
Making the Dynamic iSLB Initiator WWN Mapping Static
After a dynamic iSLB initiator has logged in, you may decide to permanently keep the automatically
assigned nWWN/pWWN mapping to allow this initiator to use the same mapping the next time it logs in .
You can convert a dynamic iSLB initiator to a static iSLB 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
static iSCSI initiator.
Making the dynamic mapping for iSLB initiators static is the same as for iSCSI. See the
Dynamic iSCSI Initiator WWN Mapping Static" section on page
Only statically mapped iSLB initiator configuration is distributed throughout the fabric using CFS.
Dynamically and statically configured iSCSI initiator configurations are not distributed.
To permanently keep the automatically assigned nWWN/pWWN mapping, follow these steps:
switch# config terminal
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Dynamic mapping (default)
"WWN Assignment for iSCSI Initiators" section on page
"World Wide Names" section on page
Enters configuration mode.
Cisco MDS 9000 Family CLI Configuration Guide
29-8). You should not use any