Forum Discussion
Devices are not synchronizing configuration to each other
Hi folks,
I´m new on Big IP and started my studies on LTM. I´ve set up two VEs running 13.1.0.5 software and I´m facing some issues in regards of synchronization of the configuration. I tried to create device-groups manually, rebuild the trust domain, push the last config from both devices, force an specific device to be the leader sync, restart processes (mcpd, devmgmtd, ntpd). Configsync-ips are correct and responding, mcpd connection in Established, I´ve already load conf to default (both VEs), read a lot of forums/discussion and at this time I´m still have no idea about why the status is Always “Not all Devices Synced. Most likely I´m missing something, did something wrong (or both).
Thanks in advance for the help.
I have also run into this caveat. I am running 13.1.1.4 on VMware Workstation 15 on Fedora 29 Linux kernel 5.0.4
Thanks to the help of F5 FSE, I have managed to resolve it by adding the following DB variables on each VM on WMware Workstation 15.x:
tmsh modify /sys db tm.tcplargereceiveoffload value disable
It appears that WMware loses packets when offload is enabled.
- SnlCirrostratus
make sure time is sync in both devices
- DomaiAltostratus
Can you check your logs? Post any errors you see here to diag this issue? Did you configure a sync vlan....can you telnet to each other device on ports 443,22? Are both devices part of device trust? run the below commands
grep -i cmi /var/log/ltm
grep -i configsync /var/log/ltm
- K1974_98730Nimbostratus
Thanks for your reply, snl! I´ve set up a NTP server on both devices and also I tried to set up date and time manually however, it didn´t work.
Regards!
- DomaiAltostratus
Its saying that there is no peer device configured. Can you establish the trust between both and try to sync again?
- DomaiAltostratus
I am using VM workstation as well...and I never see the kind of behavior you are describing. So I am just curious. Anyway good luck.
- DNDTS_361701Nimbostratus
I have the same issues. Have you had a solution for that? Thanks in advance.
- Krystian_BaniakAltocumulus
I have also run into this caveat. I am running 13.1.1.4 on VMware Workstation 15 on Fedora 29 Linux kernel 5.0.4
Thanks to the help of F5 FSE, I have managed to resolve it by adding the following DB variables on each VM on WMware Workstation 15.x:
tmsh modify /sys db tm.tcplargereceiveoffload value disable
It appears that WMware loses packets when offload is enabled.
- loiNimbostratus
Thank you so much Krysitan Baniak, i've tried to run 2 above commands on each VM, it worked.
- K1974_98730Nimbostratus
Hello DNTDS,
Not at all... I´ve removed all the configuration from the VMs, installed again, licensed again and it didn´t work as well. I also tried to use 13.1.0.6 which is not working either. It´s very strange as 13.1.0.5 was working before.
The status in VEs keep on changing from "changes pending" to "awaiting initial config" and so on, other day the traffic-group-1 was have no devices on it...
Not sure what is happening... that´s sad!
- DNDTS_361701Nimbostratus
Have you tried another older version? I tried version 13.0.0.0.0.1645 and it worked.
- ghaNimbostratus
issue still exists in version BIG-IP 14.0.0.2.
I haven't been able to successfully sync two VEs running in VMware Workstation since 13.0.
Last version this worked was 12.1.x.
I do loads of demos, trainings, workshops etc. using the vLab environment. It's a pity I can't show DSC on any current version.
- Oleksandr_MalofAltocumulus
I can partially answer this question. I was able to successfully configure DSC for VE v13.0.0 but with LAB license. Each VE required 8 GB of RAM and 4 CPUs (ESXi environment). Not sure if this works for Trial or Evaluation licenses as far I didn't manage to configure DSC with 4 GB of RAM and 2 CPUs per VE using both of those license types (VMware Fusion environment).
- Sara_the_MemberNimbostratus
Thank you for the tip, it worked! As I already tried many other solutions, I was about to trash my whole configuration + VE trial licences, and rebuild my environment from 0. Thanks to your suggestions, my issue was solved with just these two commands. I am using VMware Workstation Pro 17 + BIG-IP VE 17.0.0 0.0.22 trial version.
More info on the bug:
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