switch# show device-alias name x
device-alias name x pwwn 21:01:00:e0:8b:2e:80:93
About Device Alias Distribution
By default, device alias distribution is enabled. The device alias feature uses the coordinated distribution
mechanism to distribute the modifications to all switches in a fabric.
If you have not committed the changes and you disable distribution, then a commit task will fail.
Displays a Failed Status
switch# show
device-alias status
Fabric Distribution: Disabled
Database:- Device Aliases 25
Status of the last CFS operation issued from this switch:
==========================================================
Operation: Commit
Status: Failed (Reason: Operation is not permitted as the fabric distribution is
currently disabled.)
From the Cisco MDS NX-OS Release 6.2.9 onwards, the ASCII configuration replay takes longer
time for DDAS (Distributing Device Alias Services) without the write erase command.
Note
About Creating a Device Alias
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:
• 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.
About Device Alias Configuration Best Practices
As a part of the device-alias configuration best practices, the following guidelines need to be adopted within
a device-alias session:
If a device-alias name is reused while configuring a rename command, then the command fails and gets moved
to the rejected list.
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
162
Distributing Device Alias Services
About Device Alias Distribution
To Next Page
Loading...
Need help?
General
