Committing Changes
If you commit the changes made to the pending database, the following events occur:
1. The pending database contents overwrites the effective database contents.
2. The pending database is emptied of its contents.
3. The fabric lock is released for this feature.
To commit the changes, follow these steps:
Step 1 switch# config terminal
switch(config)#
Enters configuration mode.
Step 2 switch(config)# device-alias commit
Commits the changes made to the currently active session.
Whenever a switch in the fabric gets locked and goes for a blank commit, the following warning is displayed:
WARNING: Device-alias DB is empty in this switch.
Initiating a commit from this switch will clear [wipe out] Device-alias DB across all the
switches in the fabric, losing Device-alias full DB config permanently.
Do you want to continue? (y/n) [n]
Once the "device-alias commit" is done the running configuration has been modified on all switches participating
in device-alias distribution. You can then use the "copy running-config startup-config fabric" command to save
the running-config to the startup-config on all the switches in the fabric.
Note
Enabling the Device Alias Pending Diff Display
To enable the display of the pending-diff and the subsequent confirmation on issuing a device-alias commit,
follow these steps:
Step 1 switch# config t
switch(config)#
Enters configuration mode.
Step 2 switch(config)# device-alias confirm-commit
Enables the confirm commit option for device- alias.
Step 3 switch(config)# device-alias commit
The following device-alias changes are about to be committed
+ device-alias name Device1 pwwn 21:01:00:e0:8b:2e:80:93
Do you want to continue? (y/n) [n] y
Cisco MDS 9000 Series Fabric Configuration Guide, Release 8.x
164
Distributing Device Alias Services
Committing Changes
To Next Page
Loading...
Need help?
General
