Forum Discussion
Anthony
Nimbostratus
Aug 15, 2013config-sync fail - Can't load monitor instance for /Common/http:359
I've had to roll back out test loadbalancers from 11.4 to 11.2.1 HF3.
I've manaually updated the config on the first box and this is working just fine.
Doing this for the second one and running ...
BinaryCanary_19
Aug 16, 2013Historic F5 Account
Boneyard is actually right. It's a known issue fixed in Hotfix 8 of 11.2.1.
If you fancy it, you can open a support case and ask them to confirm if this is ID 396261.
The workaround is to copy the bigip.conf file from the peer to the affected unit and manually load it with "tmsh load sys config".
Then you just make the unit without an issue the one with the highest commit ID (just open a configuration object and click update), then syncing should work.
Probably good to upgrade to the latest hotfix too.
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects