Forum Discussion
MJ_1024
Altocumulus
AltocumulusErrors in setup of BIGIP-NEXT CM VE on KVM
I've been hammering at trying to get a stable BIGIP-NEXT CM VE running in a lab for a while now and keep running into issues. This would be the new and improved v20.2.0 in KVM (qcow image). It seems...
That does sound frustrating. A few things to try:
1- Make sure you have EXACTLY one network interface on your guest
2- Make sure you have 8 cores and 16GB
3- Check that the hypervisor isn't oversubscribed (CPU or memory): On slow systems, there can be timeout problems. With low memory the pods will constantly crash.
4- On the crashed pods, try checking out the logs:
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_logs/One other thing is that the setup command for both Central Manager and the BIP Next Instances does produce many warnings that can be ignored, and the message you see may be normal.
Lucas_Thompson
Employee
EmployeeThat does sound frustrating. A few things to try:
1- Make sure you have EXACTLY one network interface on your guest
2- Make sure you have 8 cores and 16GB
3- Check that the hypervisor isn't oversubscribed (CPU or memory): On slow systems, there can be timeout problems. With low memory the pods will constantly crash.
4- On the crashed pods, try checking out the logs:
https://kubernetes.io/docs/reference/kubectl/generated/kubectl_logs/
One other thing is that the setup command for both Central Manager and the BIP Next Instances does produce many warnings that can be ignored, and the message you see may be normal.
MJ_1024Altocumulus
AltocumulusYes, from what I could tell several services (pods) were failing to start, although it did often look like 1/2 of them would.
There were enough crashed (or failed to start nodes) that logs were difficult to parse, but I certainly could try collecting them all.
As for performance, the Cores and CPU are matched, but the disk on that system was pretty slow (hdd).
I will try moving it over to faster NVME storage and try some more, here is hoping!