Table of Contents
Advertisement
Chapter 20
Distributing Device Alias Services
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 .
Table 20-1
Comparison Between Zone Aliases and Device Aliases (continued)
Zone-Based Aliases
You can use any zone member type to specify the end
devices.
Configuration is contained within the Zone Server
database and is not available to other features.
Modifying the Device Alias Database
The device alias feature uses two databases to accept and implement device alias configurations.
•
•
If you modify the device alias configuration, you need to commit or discard the changes as the fabric
remains locked during this period.
Locking The Fabric
When you perform the first device alias task (regardless of which device alias task), the fabric is
automatically locked for the device alias feature. Once you lock the fabric, the following situations
apply:
•
•
To lock the fabric and modify the device alias configuration in the pending database, follow these steps:
Command
Step 1
switch# config t
switch(config)#
Step 2
switch(config)# device-alias database
switch(config-device-alias-db)#
Step 3
switch(config-device-alias-db)# device-alias
name x pwwn 21:01:00:e0:8b:2e:80:93
switch(config-device-alias-db)# no device-alias
name Doc
OL-6973-03, Cisco MDS SAN-OS Release 2.x
Effective database—The database currently used by the fabric.
Pending database—Your subsequent device alias configuration changes are stored in the pending
database.
No other user can make any configuration changes to this feature.
A copy of the effective database is obtained and used as the pending database. Modifications from
this point on are made to the pending database. The pending database remains in effect until you
commit the modifications to the pending database or discard (abort) the changes to the pending
database.
Device Aliases
Only pWWNs are supported along with new device aliases like IP
addresses.
Device aliases are not restricted to zoning. Device alias
configuration is available to the FCNS, zone, fcping, traceroute,
and IVR applications.
Purpose
Enters configuration mode.
Enters the pending database configuration
submode.
Specifies a device name (x) for the device that
is identified by its pWWN. Starts writing to
the pending database and simultaneously
locks the fabric as this is the first-issued
device alias configuration command.
Removes the device name (SampleName) for
the device that is identified by its pWWN.
Cisco MDS 9000 Family Configuration Guide
Modifying the Device Alias Database
20-3
Advertisement
Table of Contents
