SD-WAN vManage Problem with Port 8443

[FabOrth]

Hi together,

I have a problem with the vManage VM. I have an ESXI with the vManage.

I did the following steps installing vManage:

https://sdwan-docs.cisco.com/Product_Documentation/Getting_Started/Viptela_Overlay_Network_Bringup/03Deploy_the_vManage_NMS/01Create_vManage_NMS_Instance_on_ESXi

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
(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
#

Website link:

https://ip-address:8443/

Do you have any idea to fix the problem?

Thanks :)

[elesani]

Hi, 

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" 

Regards,
Ehsan

[FabOrth]

Hello Elesani,

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.

Regards

FabOrth

[g.ghir]

I am having the same issue?  Any updates please?

[g.ghir]

BTW, I can SSH and Ping the vManage Server but not HTTPS to it.

[ekhabaro]

You should use tcp port 443: https://sdwan-docs.cisco.com/Product_Documentation/Getting_Started/Viptela_Overlay_Network_Bringup/01Bringup_Sequence_of_Events/Firewall_Ports_for_Viptela_Deployments

8443 is used for clusters and multitenant deployments.

[g.ghir]

Does not seem to make any difference?

Config:
vmanage# sh run
system
host-name vmanage
admin-tech-on-failure
aaa
auth-order local radius tacacs
usergroup basic
task system read write
task interface read write
!
usergroup netadmin
!
usergroup operator
task system read
task interface read
task policy read
task routing read
task security read
!
usergroup tenantadmin
!
user admin
password $6$HBJoZjMzTIVTzdIa$mQbaGtnVT/R9HDQX7Uzt1dnYaVBE9VTmZvCbCmazSp7mBvCacjwoB3Dd71pNZUTaFGiHzE2lzrLsynyVyFI0h/
!
!
logging
disk
enable
!
!
!
vpn 0
interface eth0
ip dhcp-client
ipv6 dhcp-client
no shutdown
!
!
vpn 512
name ***Management_VPN***
interface eth1
ip address 10.44.136.25/24
no shutdown
!
!

[g.ghir]

vmanage# request nms all status
NMS application server
Enabled: true
Status: waiting
NMS configuration database
Enabled: true
Status: running PID:23460 for 1113s
NMS coordination server
Enabled: true
Status: running PID:23488 for 1113s
NMS messaging server
Enabled: true
Status: not running
NMS statistics database
Enabled: true
Status: running PID:23376 for 1114s
NMS data collection agent
Enabled: true
Status: not running
NMS cloud agent
Enabled: true
Status: running PID:23837 for 1107s
NMS container manager
Enabled: false
Status: not running
NMS SDAVC proxy
Enabled: true
Status: running PID:328 for 6095s

[g.ghir]

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.

[g.ghir]

I ran a port scan on the vManage server running on ESXi and the only ports open are 22 and another ssh port?? Any advice would be welcome at this point as I need to understand if this behaviour is normal?

[FabOrth]

Hello g.ghir,

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 :)

[g.ghir]

Thanks FabOrth,

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.  

[Mi7]

what's the exact solution to the issue?

[mm6646]

I Have same problem too, did you get fix the issue?

[g.ghir]

My vManage server did not have the horsepower needed so I left it there.