Locking the Network
Locking the Network
When you configure (first-time configuration) a feature (application) that uses the CFS infrastructure, that
feature starts a CFS session and locks the network. When a network is locked, the switch software allows
configuration changes to this feature only from the switch that holds the lock. If you make configuration
changes to the feature from another switch, the switch issues a message to inform the user about the locked
status. The configuration changes are held in a pending database by that application.
If you start a CFS session that requires a network lock but forget to end the session, an administrator can clear
the session. If you lock a network at any time, your username is remembered across restarts and switchovers.
If another user (on the same machine) tries to perform configuration tasks, that user's attempts are rejected.
Verifying CFS Lock Status
The show cfs lock command displays all the locks that are currently acquired by any application. For each
application the command displays the application name and scope of the lock taken. If the application lock
is taken in the physical scope, then this command displays the switch WWN, IP address, user name, and user
type of the lock holder. If the application is taken in the logical scope, then this command displays the VSAN
in which the lock is taken, the domain, IP address, user name, and user type of the lock holder.
switch# show cfs lock
Application: ntp
Scope
--------------------------------------------------------------------
Switch WWN
--------------------------------------------------------------------
20:00:00:05:30:00:6b:9e
Total number of entries = 1
Application: port-security
Scope
-----------------------------------------------------------
VSAN
-----------------------------------------------------------
1
2
Total number of entries = 2
The show cfs lock name command displays the lock details for the specified application.
switch# show cfs lock name ntp
Scope
--------------------------------------------------------------------
Switch WWN
--------------------------------------------------------------------
20:00:00:05:30:00:6b:9e
Total number of entries = 1
Committing Changes
A commit operation saves the pending database for all application peers and releases the lock for all switches.
The commit function does not start a session; only a lock function starts a session. However, an empty commit
is allowed if configuration changes are not previously made. In this case, a commit operation results in a
session that acquires locks and distributes the current database.
Cisco Nexus 5000 Series NX-OS System Management Configuration Guide, Release 5.2(1)N1(1)
48
: Physical
IP Address
10.76.100.167
: Logical
Domain
IP Address
238
10.76.100.167
211
10.76.100.167
: Physical
IP Address
10.76.100.167
User Name
User Type
admin
CLI/SNMP v3
User Name
User Type
admin
CLI/SNMP v3
admin
CLI/SNMP v3
User Name
User Type
admin
CLI/SNMP v3
Using Cisco Fabric Services