vCenter7 webconsole issue with multi VM Kernel Adapter ESXi Host Server

[vmvceplayer]

vCenter7 webconsole can't access & show error msg "The console has been disconnected. Close this window and re-launch the console to reconnect

"

Webconsole issue with multi VM Kernel Adapter ESXi Host Server

Our ESXi Host Severs have two VMkernel adapters

If We remove one of the VMkernel adapter, webconsole can access

If We added an additional VMkernel adapters, webconsole will show "

"The console has been disconnected. Close this window and re-launch the console to reconnect

"

But VMRC (VMware Remote Console) don't have any problem with single or dual VM Kernel Adapter

VM Support follow our case for more than one month but no findings at all
Any one know how to fix this webconsole issue?

[YunyunJung]

Can you share the configuration of vmkernel adapters? Such as services, ip subnet vs.

[vmvceplayer]

Hi YunyunJung

Please find the below settings

vCenter
=====================================================

IP: 172.16.19.63
SN: 255.255.255.0
GW:172.16.19.1

ESX01
=====================================================
VMkernel network adapter: vmk0
Properties

Network label mgmt-vmk0
VLAN ID None (0)
TCP/IP stack Default
Enabled services Management
NIC settings

MTU 1500

VMkernel network adapter: vmk0
IP Settings

DHCP Disabled
IPv4 address 172.16.13.53 (static)
Subnet mask 255.255.255.0
Default gateway 172.16.13.1
DNS server addresses --
IPv6 settings
DHCP Disabled
Router advertisement Enabled
IPv6 addresses
Default gateway --
DNS server addresses --

VMkernel network adapter: vmk0
Policies
Security
Promiscuous mode Reject
MAC address changes Reject
Forged transmits Reject
Traffic shaping
Average bandwidth --
Peak bandwidth --
Burst size --
Teaming and failover
Load balancing Route based on originating virtual port
Network failure detection Link status only
Notify switches Yes
Failback Yes
Active adapters vmnic0, vmnic1
Standby adapters --
Unused adapters --

VMkernel network adapter: vmk1
Properties

Port properties
Network label mgmt-vmk1
VLAN ID 249
TCP/IP stack Default
Enabled services vMotion
NIC settings

MTU 1500

VMkernel network adapter: vmk1
IP Settings

IPv4 settings
DHCP Disabled
IPv4 address 172.16.19.93 (static)
Subnet mask 255.255.255.0
Default gateway 172.16.13.1
DNS server addresses --
IPv6 settings
DHCP Disabled
Router advertisement Disabled
IPv6 addresses fe80::250:56ff:fe6e:8014/64
Default gateway --
DNS server addresses --

VMkernel network adapter: vmk1
Policies
Security
Promiscuous mode Reject
MAC address changes Reject
Forged transmits Reject
Traffic shaping
Average bandwidth --
Peak bandwidth --
Burst size --
Teaming and failover
Load balancing Route based on originating virtual port
Network failure detection Link status only
Notify switches Yes
Failback Yes
Active adapters vmnic4, vmnic6
Standby adapters --
Unused adapters --

[Kinnison · Accepted solution]

Hi,

Looking at what you posted I wonder why you set VMK1 with a gateway IP address belonging to a different subnet.
If I were in your place, I would dedicate a non-routable IP network to the vMotion service with its own TCP / IP stack and if I did not set-up the so-called multi NIC vMotion one of them I would keep as active and the second one as in standby.

Regards,
Ferdinando

[vmvceplayer]

Hi Kinnison

I tried to remove mgmt-vmk1 & added again at the vCenter of that ESX host server
The gateway 172.16.13.1 is added automatically!

How can remove the gateway?
It is supposed to have only one gateway for mgmt-vmk0

Thanks much for your help!

[Kinnison]

Hi,

If I'm honest I'd like to know how networking is configured in the context of your vSphere infrastructure because from what little you write it is not that it is completely understandable. I mean, the VMK1 object shares the default TCP / IP stack and therefore assumes as a gateway a "default" value whose IP address belongs to another subnet and a "different" VLAN that, for what I know and for my doing and conceiving things, does not make practical sense.

That is, I would set up a VMkernel with its own portgroup, VLAN and a IP subnet all this dedicated only to this specific purpose and nothing else. Personally, in my small IP context, but elsewhere as well, I'm used to doing this as often as I can, basically I follow the indications and advice reported in the official documentation:

https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-7DAD15D4-7F41-...
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenterhost.doc/GUID-3B41119A-1276-...

With this I do not guarantee at all that you would solve your problem, I just say that it might be worth a try.
However, in the end you have to decide whether or not to do it according to the peculiarities of your IT context.

Regards,
Ferdinando

[vmvceplayer]

Hi Kinnison

I choose vMotion instead of Default TCP Stack & no gateway with vmk1
Web console are ok now.

Thanks much for help!