cm changes

[suthomas1]

Good day all,

In our clustered big-ip, we have recently seen it showing changes pending.

There have been no changes done, it would only be one of the admin team members browsing to check something.

Will that changes pending in red cause any issues, it is prompting to sync the secondary with primary.

The other thing noticed is dates on changes pending on gui are not the same in tmsh.

Is there any way to see why bigip is giving this error & what pending changes is it referring to.

CM::Sync Status

---------------------------------------------------------------------------------------------------------------------------------------------

Color  red

Status  Changes Pending

Mode   high-availability

Summary There is a possible change conflict between bigip-dev0 and bigip-dev1

Details

     bigip-dev1: connected

     bigip-dev-grp (Changes Pending): There is a possible change conflict between bigip-dev0 and bigip-dev1.

     - Recommended action: Synchronize bigip-dev1 to group bigip-dev-grp

Please help, thank you.

[jaikumar_f5 · Accepted solution]

This would often happen if the engineers try to login to the standby & make some new changes. Or any config push done to the standby device.

Try running this, it will show from the config sync started & if the commit id matches

tmsh run cm watch-devicegroup-device