About Device Alias Distribution; Locking The Fabric; Committing Changes - Cisco AP775A - Nexus Converged Network Switch 5010 Configuration Manual

Distributing Device Alias Services
Viewing the Device Alias Mode Setting
To view the current device alias mode setting, enter the show device-alias status command.
switch# show device-alias status
Fabric Distribution: Enabled
Database:- Device Aliases 0 Mode: Basic
Locked By:- User "admin" SWWN 20:00:00:0d:ec:30:90:40
Pending Database:- Device Aliases 0 Mode: Basic

About Device Alias Distribution

By default, device alias distribution is enabled. The device alias feature uses CFS to distribute the modifications
to all switches in a fabric.
If device alias distribution is disabled, database changes are not distributed to the switches in the fabric. The
same changes would have to be performed manually on all switches in the fabric to keep the device alias
database up-to-date. Database changes immediately take effect, so there would not be any pending database
and commit or abort operations either. If you have not committed the changes and you disable distribution,
then a commit task will fail.
The following example displays a failed device alias 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.)

Locking the Fabric

When you perform any device alias configuration 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. Subsequent modifications

Committing Changes

If you commit the changes made to the pending database, the following events occur:
• The pending database content overwrites the effective database content.
• The pending database is distributed to the switches in the fabric and the effective database on those
• The pending database is emptied of its contents.
• The fabric lock is released for this feature.
To commit the changes, perform this task:
OL-16597-01
are made to the pending database. The pending database remains in use until you commit the modifications
to the pending database or discard (abort) the changes to the pending database.
switches is overwritten with the new changes.
Cisco Nexus 5000 Series Switch CLI Software Configuration Guide
About Device Alias Distribution
571