Forum Discussion
F5 XC Customer Edge
MVPSee Troubleshooting Manual Site Deployment Registration Issues | F5 Distributed Cloud Technical Knowledge or for secure mesh v2 Troubleshooting Guide for Secure Mesh Site v2 Deployment | F5 Distributed Cloud Technical Knowledge as for upgrade or first registration issues the VPM log may hold the answer. If there is a proxy or firewall that the CE needs to get through be careful as decryption of some of the domains the CE tries to pull may cause issues. See Firewall and Proxy Server Allowlist Reference | F5 Distributed Cloud Technical Knowledge and Proxy for CE Registration and Upgrades Reference | F5 Distributed Cloud Technical Knowledge
If you are trying to deploy 1 CE make certain that you have selected to not be HA otherwise you need to deploy three CE nodes at the same same time, so they can synchronize when they become up.
Hi Nikoo,
Thanks for your support and response. I attempted to delete my post because i think the issue was related to the image it self but was unable to for some reason.
To provide a brief overview of my experience with XC, I initially tried to import the F5 CE image (single nic) onto VMware, which I downloaded from the cloud documentation links. After initializing the new OVA file on the VMware ESXi server, I encountered an issue where several services kept restarting:
stopped argo watch service
starting argo watch service
stopped LCD display service
starting LCD display service
stopped "site console service connecting to vpm.service"
strating"site console service connecting to vpm.service"
I verified the integrity of the CE image, checked network settings, and attempted an initial configuration via the console connection, but I couldn't resolve the issue. However, when I imported the "multi-nic" CE image instead of the "single-nic" version, everything worked fine. The CE was accessible via the GUI, and the previous issues did not occur.
I'm unsure whether there are limitations with the single-nic CE on VMware or if there is another cause.
- Nikoolayy1
Also keep in mind Mohamed_Salah_ that better use Secure Mesh v2 as Secure Mesh 1 will be decomissioned after time as I think you are using secure mesh 1 because of mentioning multi nic as Secure Mesh 2 handles this better Secure Mesh 1. Maybe with you if you added 1 more SLI (site internal interface) to the single nic CE it broke it.
Issues I saw with Secure Mesh 2 just as a note is that you better select DNS and NTP servers and not leave it to the default ones as it did not use them but that was a month ago, so maybe they fixed it. Just do a ping to an fqdn when you deploy the CE to see that it resolves the IP address 😉
Regards,
Nikolay