Locking The Fabric; Committing Role-Based Configuration Changes; Discarding Role-Based Configuration Changes - Cisco MDS 9000 Series Configuration Manual

Common Roles
Note
As soon as the customer encounters syslog"%VSHD-4-VSHD_ROLE_DATABASE_OUT_OF_SYNC",
Role configuration database is found to be different between the switches during merge. Role configuration
database is recommended to be identical among all switches in the fabric. Edit the configuration on one of
the switches to obtain the desired role configuration database and then commit it.

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:
• 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.

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:
Procedure
Step 1
switch# configure terminal
switch(config)#
Enters configuration mode.
Step 2 switch(config)# role commit vsan 3
Commits the role-based configuration changes.

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.
To discard role-based configuration changes, follow these steps:
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.
Cisco MDS 9000 Series Security Configuration Guide, Release 8.x
Locking the Fabric
17