Hi! Let's say that I run this command in tmsh: modify ltm node MYWEB01 state user-down The sync status changes to "Changes Pending"Those changes are not written to the config file. Is there any way of detecting that there are changes not committed to disk? /Patrik

I don't think tmsh saves a status about that, so I don't think is possible. When you do the save command, is just save all configuration (or one partition) from memory to the disk, there is no way to save just last change. You could look the .tmsh-history-user in the user folder, and grep the configuration files to see if those changes were applied. There is a "show running-config", but that just give you the same information as the list command.

Forum Discussion

Patrik_Jonsson

MVP

Oct 09, 2016

Detecting changes not committed to disk

Hi!

Let's say that I run this command in tmsh:

modify ltm node MYWEB01 state user-down

The sync status changes to "Changes Pending"
Those changes are not written to the config file.

Is there any way of detecting that there are changes not committed to disk?

/Patrik

application delivery

TMOS

TMSH

1 Reply

Leonardo_Souza
Cirrocumulus
Oct 09, 2016
I don't think tmsh saves a status about that, so I don't think is possible. When you do the save command, is just save all configuration (or one partition) from memory to the disk, there is no way to save just last change.

You could look the .tmsh-history-user in the user folder, and grep the configuration files to see if those changes were applied.

There is a "show running-config", but that just give you the same information as the list command.