Choose one of the topics below for SD-WAN Resources to help you on your journey with SD-WAN
This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC!
We will not comment or assist with your TAC case in these forums.
I have a problem with the vManage VM. I have an ESXI with the vManage.
I did the following steps installing vManage:
But the Problem is, vManage is not available. I am on a jump host with no security features. It is with the Server in the same Net. Therefore, i think its not a problem with the firewall...
I can ping the Vm and it is possible to connect via ssh to the cli but connectiong via https is not possible. (Connection Failure)
The steps to configure are:
(config)# vpn 512
(config)# ip route prefix/length next-hop-ip-address
(config-vpn-512)# interface eth0
(config-interface-eth0)# ip address ip-address
(config-interface-eth0)# no shutdown
(config-interface-eth0)# commit and-quit
Do you have any idea to fix the problem?
To help me understand how you have deployed your vManage, can you share the "show run" from it. and also collect "request nms all status"
enclosed you will find two screenshots. One sh run and the other one is the request nms all status.
The IP-Address is a private one and the next hop is the default gateway
Thank you for taking care of the problem.
Any update? I am using port 443 but it does not work, as stated earlier network connectivity is good for Ping and SSH. Any suggestions would be welcome.
i solved the problem. In my case, the actual server was optimal in terms of specifications. By trying out another one that was even newer, vManage ran optimally.
So try to do vManage on a newer better server with ssd etc.
Hope it fixes your problem :)
Can you guide me on your final settings within ESXi? I know vManage is very hungry but as this is an evaluation it is running on a 'skinny' host.