Configuring Users and Common Roles
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
About Role Databases
Role-based configurations use two databases to accept and implement configurations.
Locking the Fabric
The first action that modifies the database creates the pending database and locks the feature in the entire
fabric. Once you lock the fabric, the following situations apply:
Committing Role-Based Configuration Changes
If you commit the changes made to the pending database, the configuration is committed to all the
switches in the fabric. On a successful commit, the configuration change is applied throughout the fabric
and the lock is released. The configuration database now contains the committed changes and the
pending database is now cleared.
To commit role-based configuration changes, follow these steps:
switch# config t
switch(config)# role commit vsan 3
Discarding Role-Based Configuration Changes
If you discard (abort) the changes made to the pending database, the configuration database remains
unaffected and the lock is released.
OL-16184-01, Cisco MDS SAN-OS Release 3.x
Clearing Sessions, page 39-6
Database Merge Guidelines, page 39-6
Displaying Role-Based Information, page 39-6
Displaying Roles When Distribution is Enabled, page 39-7
Configuration database—The database currently enforced by the fabric.
Pending database—Your subsequent configuration changes are stored in the pending database. If
you modify the configuration, you need to commit or discard the pending database changes to the
configuration database. The fabric remains locked during this period. Changes to the pending
database are not reflected in the configuration database until you commit the changes.
No other user can make any configuration changes to this feature.
A copy of the configuration database becomes the pending database along with the first change.
Enters configuration mode.
Commits the role-based configuration changes.
Cisco MDS 9000 Family CLI Configuration Guide