233
Locking/unlocking the configuration
The device supports a maximum of 32 NETCONF sessions. A maximum of 32 users can
simultaneously manage and monitor the device using NETCONF. During device configuration and
maintenance or network troubleshooting, a user can lock the configuration to prevent other users
from changing it. After that, only the user holding the lock can change the configuration, and other
users can only read the configuration.
In addition, only the user holding the lock can release the lock. After the lock is released, other users
can change the current configuration or lock the configuration. If the session of the user that holds
the lock is terminated, the system automatically releases the lock.
Locking the configuration
# Copy the following text to the client to lock the configuration:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<lock>
<target>
<running/>
</target>
</lock>
</rpc>
After receiving the lock request, the device returns a response in the following format if the lock
operation is successful:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
Unlocking the configuration
# Copy the following text to the client to unlock the configuration:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<unlock>
<target>
<running/>
</target>
</unlock>
</rpc>
After receiving the unlock request, the device returns a response in the following format if the unlock
operation is successful:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<ok/>
</rpc-reply>
To Next Page
Loading...
Need help?
General
