Hi Team. I was wondering if any of you has experiencing this kind of issues on the VeloCloud Edges. I understand that there are certain configuration in the VeloCloud Edges that requires the device to reboot to take effect (even though minor configuration change-https://kb.vmware.com/s/article/60247), however we start seeing issues that the Edges are online as we can ping its external and internal ip addresses, but it is showing down from the Orchestrator. We have to manually unplug the edges from the power to reboot it, and regain connectivity back to the Orchestrator.
Another issue we experienced today while working with VeloCloud Support, the VC TAC started to perform debug and tcpdump on an GE2 interface as we are troubleshooting an SNMP issue, then suddenly the GE2 interface went down from the Orchestrator but we can ping its IP address.
Our set up looks like this -- Two VC Edges in Enchanced HA having two ISP connected on each Edge. What is your take on using Enchanced HA instead of Active-Passive HA? Echanced HA link -- https://docs.vmware.com/en/VMware-SD-WAN/3.3/velocloud-admin-guide-33/GUID-AD69349D-E008-4D11-9F08-550FE3AE9981.html
As you may notice I have a lot of questions, yes this is our first VC setup. So far its doing great in terms of its SDWAN performance, but we have issues on managing it, even making simple changes, and trusting its stability.
No comments:
Post a Comment