Juniper SRX exit the configuration mode before committing

Is below code correct for Juniper SRX? This works for MX’s but with SRX, what I see is in debug mode, code exists the configuration mode without committing the changes. Workaround is to send a commit CLI as part of configuration commands sent along configuration items.

net_connect.config_mode()
if net_connect.check_config_mode():
    print("Successfully in config mode")
    net_connect.send_config_set(config_cmds)
    net_connect.commit()
    net_connect.exit_config_mode()

[ktbyers]

@tee-lake You should be able to do the following then:

net_connect.send_config_set(config_commands, exit_config_mode=False)
net_connect.commit(and_quit=True)

Basically, don’t exit config mode on the changes. Then use the commit() method to commit the changes (and_quit just causes it to exit config mode after the commit).

[tee-lake]

I’ll have to test if the above provides the desired result. However a quick look into “exit configuration-mode”. I do not think this works as demonstrated above for high-end srx device. Please see below {primary:node0} srx-5800-01> edit warning: Clustering enabled; using private edit warning: uncommitted changes will be discarded on exit Entering configuration mode {primary:node0}[edit] srx-5800-01# set security zones security-zone zoneA address-book address 10.10.10.10/32 10.10.10.10/32

{primary:node0}[edit] srx-5800-01# sh|compare [edit security zones security-zone zoneA address-book] address 10.12.19.0/18 { … } + address 10.10.10.10/32 10.10.10.10/32;

{primary:node0}[edit] srx-5800-01# exit configuration-mode The configuration has been changed but not committed Exiting configuration mode

{primary:node0} srx-5800-01> configure warning: Clustering enabled; using private edit warning: uncommitted changes will be discarded on exit Entering configuration mode

{primary:node0}[edit] srx-5800-01# sh|compare

{primary:node0}[edit] srx-5800-01#

Thus I believe the config pasted is discarded once you leave config mode.