243
Rolling back the configuration
# Copy the following text to the client to roll back the configuration:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<rollback>
<file>Specify the configuration file name</file>
</rollback>
</rpc>
The name of the specified configuration file must start with the storage media name and end with the
extension .cfg. The total length of the save path and file name must be no more than 191 characters.
After receiving the rollback request, the device returns a response in the following format if the
<rollback> 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>
Loading the configuration
After you perform the <load> operation, the loaded configurations are merged into the current
configuration:
• New configurations are directly loaded.
• Configurations that already exist in the current configuration are replaced by those loaded from
the configuration file.
# Copy the following text to the client to load a configuration file for the device:
<?xml version="1.0" encoding="UTF-8"?>
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<load>
<file>Specify the configuration file name</file>
</load>
</rpc>
The name of the specified configuration file must start with the storage media name and end with the
extension .cfg. The total length of the save path and file name must be no more than 191 characters.
After receiving the load request, the device returns a response in the following format if the <load>
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>
Example for saving the configuration
Network requirements
Save the current configuration to the configuration file my_config.cfg.
To Next Page
Loading...
Need help?
General
