The api configuration lock command locks the current configuration of a device.
The undo api configuration lock command unlocks a device.
By default, the current configuration of a device is not locked.
Usage Scenario
If overlapping management is performed on a device, configurations may be inconsistent, causing service conflicts. To resolve this issue, the controller (for example, SecoManager) can lock the device. After the device is locked, only the controller can configure the device. The device administrator can only run the display commands and cannot configure services on the device.
Generally, the lock/unlock operation of the device is delivered by the controller. The unlock operation can be performed on the device only when the communication between the device and controller is interrupted. In other scenarios, do not perform the unlock operation on the device.
Precautions
Currently, the controller delivers the lock configuration only to devices deployed in standalone or hot standby mirroring mode.
A locked device is still locked after being restarted.
Only the controller can lock the device through the northbound interface. On the device side, only the unlock operation can be performed. The following table lists the support for lock and unlock operations.
Operation |
Controller |
Device |
|---|---|---|
Lock |
Supported When devices are deployed in hot standby mirroring mode, only the active device can be locked. |
Not supported |
Unlock |
Supported |
Supported The system administrator on the device side can run the unlock command. |