Locking The Fabric; Committing Changes - Cisco Nexus 5000 Series Configuration Manual

Device Alias Databases
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:
SUMMARY STEPS
1. switch# configuration terminal
2. switch(config)# device-alias commit
DETAILED STEPS
Command or Action
Step 1
switch# configuration terminal
Step 2
switch(config)# device-alias commit
Cisco Nexus 5000 Series NX-OS SAN Switching Configuration Guide
136
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.
Distributing Device Alias Services
Purpose
Enters configuration mode.
Commits the changes made to the currently active
session.
OL-xxxxx-xx