Hi.

I've noticed that when setting use_commit=true, the first few commands sent through netMiko gets committed automatically. However, after a few minutes, futher configuration commands sent via netMiko are not committed.
The commands do get sent correctly as when the uncommitted configuration is viewed the config sent by netMiko is visible, and when manually committed commits without issue.

This seems to be an issue in the netMiko SOAR app as when the config option is toggled and redeployed to the AppHost it commits again for a while before stopping. That said, the config entry in the file is persistent, only the behaviour isn't.

Futhermore as a workaround, sending 'commit' in the script also commits the config as well, and is what is in the workaround at the moment.

I suppose the question is, can this be fixed? Or is the "use_commit" flag supposed to be used differently than what I have been doing?

Regards,
Pumynt

------------------------------
Pumynt Chooboonraj
Solution Architect
Sphere Grouppe Pty Ltd
Melbourne VIC
------------------------------

Hi Pumynt,

I reviewed the app and I understand issue and defect. We'll look to get a correct out shortly.

------------------------------
Mark Scherfling
------------------------------

Hi Mark.

Thank you for your prompt response!

Looking forward to the updates!

Regards.

------------------------------
Pumynt Chooboonraj
Solution Architect
Sphere Grouppe Pty Ltd
Melbourne VIC
------------------------------

Original Message:
Sent: Fri April 22, 2022 08:39 AM
From: Mark Scherfling
Subject: netMiko for SOAR - use_commit = true not persistent

Hi Pumynt,

I reviewed the app and I understand issue and defect. We'll look to get a correct out shortly.

------------------------------
Mark Scherfling
------------------------------