The config_manager/rescue
function provides a means to save a know good running configuration
as a rescue configuration and rollback the current device configuration to rescue configuration
when required.
Below is an example of how to call the config_manager/rescue
function to mark the
current running configuration as rescue config.
- hosts: junos
roles:
- name: ansible-network.juniper_junos
function: config_manager/resuce
config_manager_set_rescue: True
The config_manager/rescue
function also provides support to rollback the current running
configuration to a rescue configuration when required
In order to load the resuce configuration, the function as before but adds the
value config_manager_load_rescue_config: yes
to the playbook to indicate that the configuration should
be rollbacked to te the resuce configuration.
Note: Take caution when doing rescue configuration load that you do not inadvertently replace your access to the device.
- hosts: junos
roles:
- name: ansible-network.juniper_junos
function: config_manager/resuce
config_manager_load_rescue_config: True
Below is an example of how to call the config_manager/rescue
function to delete the
previously set rescue configuration.
- hosts: junos
roles:
- name: ansible-network.juniper_junos
function: config_manager/resuce
config_manager_delete_rescue: True
This setting indicates whether or not the to set the current running configuration as the rescue configuration.
The default value is False
This setting indicates whether or not to replace the current configuration with the rescue configuration.
The default value is False
This setting indicates whether or not the to delete the rescue configuration checkpoint that is already set.
The default value is False