Forum Discussion
high avilability config sync error
I configured two LTM with version 11.1 and leatest hotfix installed.
Configured self ip's for the config sync. Everything works well (failover etc) but not config sync.
I do get the following message in the "Device Management ›› Device Groups : Device Group List ›› Config Sync : "
Status:Sync Failed
Summary:remote sync validation error
Details:[sync error on /Common/zrh-adc-b-bip02.beta.local]: Load failed from /Common/zrh-adc-b-bip01.beta.local 0107146f:3: Self-device state mirroring address cannot reference the non-existant Self IP (10.160.1.6); Create it in the /Common folder first.
Can anybody help?
kr bb
4 Replies
- Michael_Yates
Nimbostratus
Hi BigBrother,
I would suggest checking to make sure that your Sync-Failover VLAN is properly configured.
It's generally a Interface (like 1.1 connected between the devices with a normal Networking Cable (the ports are Universal so it will detect the cable type and make the correct "Cross-Over" Cable adjustments to communicate correctly)) with just two IP Addresses on it. Yours believes that its Self-IP Address on that network is 10.160.1.60.
They can be configured to Sync, Communicate Sub-Second Failovers, and I believe state mirroring across this connection.
See this article for additional details: SOL7511: Configuring the ConfigSync, network failover, and state mirroring utilities to use separate IP addresses. The article says that you can use the Management Interface for this, but like I said earlier, I use a separate interface since I have plenty that aren't being used.
Hope this helps. - Andrea_Arquint
Nimbostratus
Hi Michael
I did not explain my setup detailed. I use two LTM virtual instances running on V11.1HF2. So bigpipe commands are not supported anymore on that version in combination with a cluster.
So I have to investigate more deeper :-)
best regards
bb - nitass
Employee
Details:[sync error on /Common/zrh-adc-b-bip02.beta.local]: Load failed from /Common/zrh-adc-b-bip01.beta.local 0107146f:3: Self-device state mirroring address cannot reference the non-existant Self IP (10.160.1.6); Create it in the /Common folder first.is mirroring configuration really correct? would it be possible to try to remove all mirroring configuration on both units and try config sync again? - Harsh_Kumar_110
Nimbostratus
it helped me out to remove mirroring connections
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
