Forum Discussion
Oleksandr_Malof
Altocumulus
AltocumulusDSC is not coming up for LTM VEs after initial setup
Hi everyone.
It looks like I am facing an issue described here: https://devcentral.f5.com/questions/devices-are-not-synchronizing-configuration-to-each-other-59604. The point is that I was trying to...
The answer to my initial question - yes, it is possible to configure DSC with VE v13, at least, using LAB license. But this requires 8 GB of RAM and 4 CPUs per VE. Not sure if this can be performed with Trial or Evaluation licenses as I have no possibility to test this.
Krystian_BaniakAltocumulus
AltocumulusI 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
I have managed to resolve the problem with the following db variables on the each of cluster members:
tmsh modify /sys db tm.tcplargereceiveoffload value disable
tmsh modify /sys db tm.tcpsegmentationoffload value disable
To be sure, I had to go through devicegroup trust reset and reconfiguration of DSC. Now everything is fine.
It appears VMware has issues with offloading mechanisms. In 12.1.x everything was running fine.
Abreey1Nimbostratus
Krystian Baniak thank you for your help. it's worked awesomely. I was searching why between both f5 cannot sync. you made my day, thank you!
bader1You made my day, thank you for your help!
aproctorEDKrystian - this is genius, thank you. Worked for me (Windows 10, VMWare Workstation 14, BIG-IP 13.1.3). I was seeing exactly the same messages Oleksandr mentioned and your fix solved the issue. I did not need to reset trust, just made your recommended changes and was able to sync straight away. Thanks again, I had been banging my head against a wall!!
Out of interest, if you are able to share how you came upon the solution, I would be interested to hear the story - I had no idea those db variables even existed and would never have known to look for them