Forum Discussion
How to identify what is causing "Changes Pending" before ConfigSync?
When a BIG-IP device shows "Changes Pending", is there a way to identify exactly what configuration has changed before performing a ConfigSync?
I checked the Audit Log, but it mostly contains commands such as list cm device recursive and other GUI-generated read-only commands, and doesn't clearly show which object was modified.
Also, if I realize the changes were made by mistake, is there a supported way to discard or revert the pending changes without synchronizing them to the peer?
Any recommended commands or best practices would be appreciated.
Thanks!
you can filter out those record using grep -v ....
and have tried the guide below?
https://my.f5.com/manage/s/article/K09050750
1 Reply
you can filter out those record using grep -v ....
and have tried the guide below?
https://my.f5.com/manage/s/article/K09050750
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com