CodeBlueEngineers
asked on
Cannot Connect to Vmware Management Port after Upgrade
I have just recently upgraded an entire vcenter system from 4.1 to 5.1. As well as 10 hosts in 1 site and 1 in the other site.
All seemed to go rather well except for the 1 host in the remote site.
I cannot connect to the management port of the host, however when it was first upgraded I could. Not until I upgraded the vsphere tools on the VMs on the host did I lose the connection.
The VMs running on the host are still all connected and working.
In vcenter the host shows as offline and I cannot ping the IP address of the host.
I have tried restarting the management connection and also the whole server.
I did notice last night when I turned off the VMs that after about an hour I could connect to the management port, but then lost the connection again after about an hour.
I can login to the server via ilo so have been able to troubleshoot from there
I tested the management port from the host and I can ping the default gateway but no further. From other servers I can ping the same default gateway but not the host management port.
The host is in a vlan which is properly configured from what I can tell. Especially as it was working before the upgrade.
I have had the networking team investigate and they have confirmed the switches and vlans are correct but they cannot connect to the actual host, although the port on the switch shows it is active.
I have tried disabling the vmtools on the VMs on the host but this has had no effect.
The management port has 2 network connections with 1 running in standby, I have also tried setting the standby as active but to no avail.
The host itself is showing it has properly updated to the correct version of 5.5
The server is an HP DL380 G7 about 2 years old
I can connect to the host via ilo and have even tried changing the IP address which had no effect, as I thought maybe there was an IP clash
The differences between this host and the other hosts is it is HP and the others are Dell, also for the upgrade I upgraded the Dell servers via upgrade Manager, and the HP was initiated by upgrade manager but as there was an upgrade disk in the server I accidentally upgraded it from that, but this still seemed to upgrade fine.
Any help is much appreciated
All seemed to go rather well except for the 1 host in the remote site.
I cannot connect to the management port of the host, however when it was first upgraded I could. Not until I upgraded the vsphere tools on the VMs on the host did I lose the connection.
The VMs running on the host are still all connected and working.
In vcenter the host shows as offline and I cannot ping the IP address of the host.
I have tried restarting the management connection and also the whole server.
I did notice last night when I turned off the VMs that after about an hour I could connect to the management port, but then lost the connection again after about an hour.
I can login to the server via ilo so have been able to troubleshoot from there
I tested the management port from the host and I can ping the default gateway but no further. From other servers I can ping the same default gateway but not the host management port.
The host is in a vlan which is properly configured from what I can tell. Especially as it was working before the upgrade.
I have had the networking team investigate and they have confirmed the switches and vlans are correct but they cannot connect to the actual host, although the port on the switch shows it is active.
I have tried disabling the vmtools on the VMs on the host but this has had no effect.
The management port has 2 network connections with 1 running in standby, I have also tried setting the standby as active but to no avail.
The host itself is showing it has properly updated to the correct version of 5.5
The server is an HP DL380 G7 about 2 years old
I can connect to the host via ilo and have even tried changing the IP address which had no effect, as I thought maybe there was an IP clash
The differences between this host and the other hosts is it is HP and the others are Dell, also for the upgrade I upgraded the Dell servers via upgrade Manager, and the HP was initiated by upgrade manager but as there was an upgrade disk in the server I accidentally upgraded it from that, but this still seemed to upgrade fine.
Any help is much appreciated
if you can get onto the host via iLo, can you ping the default gateway?
is the default gateway set correctly?
is the default gateway set correctly?
ASKER
Hi there, yes I can ping the default gateway but no further. The strange part I do not understand is from other servers I can ping that same DG and it is definitely correct.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I have had our networking team investigate and they have said the switching and routing is correct, and that when connected directly to the switch they cannot connect to the host.
Its strange that it happened directly after the upgrade as well.
Its strange that it happened directly after the upgrade as well.
There have been some networking changes in 5.1 between vmkernel and management network routing.
ASKER
Thanks, I have logged a job with vmware so hopefully they can find the issue. If its to do with the network routing or vmware changes as above I will allocate you the points
Upload your networking screenshot.
ASKER
Just uploaded now, just had to cover the names of the servers.
As you can see VM's and management use the same network port.
Which is strange that it works for the VM's but not the management network
vmware-networking.PNG
As you can see VM's and management use the same network port.
Which is strange that it works for the VM's but not the management network
vmware-networking.PNG
What is glaringly obvious is the host is on a different VLAN
Check vlan configuration is correct on the trunk eg physical network config. On physical switches connected to host server and all other switches in network.
You also have a single nic with all traffic running over....so check whatever config is running on this.
Seems a little on the light your vSwitch I would trunk both NICs so both active active
Check vlan configuration is correct on the trunk eg physical network config. On physical switches connected to host server and all other switches in network.
You also have a single nic with all traffic running over....so check whatever config is running on this.
Seems a little on the light your vSwitch I would trunk both NICs so both active active
ASKER
Yes that does seem to be what is very obvious, I have the networking team checking out the switching and vlans.
Do you think there may be a chance that the management port is being flooded?
Do you think there may be a chance that the management port is being flooded?
We are fans of the management port on its on vSwitch0 with at least two NICs.
Same for VMs its on vSwitch1 with two NICs.
Now you have VLANs which are fine but VLAN diagnosis and asking a network team for virtualization on a specific VLAN needs specific network probes on each vlan and specialist monitoring which your network tram may have so ask them for utilisation figures for each vlan
And of course that's not errors or a total value for the pipe.
Same for VMs its on vSwitch1 with two NICs.
Now you have VLANs which are fine but VLAN diagnosis and asking a network team for virtualization on a specific VLAN needs specific network probes on each vlan and specialist monitoring which your network tram may have so ask them for utilisation figures for each vlan
And of course that's not errors or a total value for the pipe.
ASKER
Just found there is another device on the same subnet which has the same IP address as the default gateway.
Once we removed the device it started working straight away
So you were right hanccocka it was network related
Once we removed the device it started working straight away
So you were right hanccocka it was network related
Glad it was resolved!
ASKER