rcvassallo's Posts

Unfortunately for me there is no patch panel in the mix. The servers are connected directly to the switch. I've tried 3 different ports with the same result. I will have to see if power-cycling t... See more...
Unfortunately for me there is no patch panel in the mix. The servers are connected directly to the switch. I've tried 3 different ports with the same result. I will have to see if power-cycling the switch does any good but other than that I am at a loss for resolving this.
Well at least I'm not the only one with this issue. Both of my DL380G6 hosts are running ESXi 4.0.0 release 208167 which I believe is the Update 1 build. What has me most confused is t... See more...
Well at least I'm not the only one with this issue. Both of my DL380G6 hosts are running ESXi 4.0.0 release 208167 which I believe is the Update 1 build. What has me most confused is that my 2 hosts are basically identical. The server hardware is the same and all NICs are connected to the same switch, yet only one of the NICs comes up as 100mbps
The server is in the hardware compatibility list. HP ProLiant DL380 G6 IIRC, the host disconnect occured shortly after I rebooted a Windows Server 2008 guest from the vCenter conso... See more...
The server is in the hardware compatibility list. HP ProLiant DL380 G6 IIRC, the host disconnect occured shortly after I rebooted a Windows Server 2008 guest from the vCenter console. That's when I first noticed the disconnected status icon anyway. The only things I can find in the task&event log are the error from when I attempted to reconnect to this host. - Reconnect host vmhost1.texasfirstbank.local Cannot contact the specified host (vmhost1.texasfirstbank.local). The host may not be available on the network, a network configuration problem may exist, or the management services on this host may not be responding. 3/22/2010 2:47:34 PM 3/22/2010 2:47:34 PM 3/22/2010 2:48:38 PM
I was working with an ESXi 4.0 host today, configuring a new VM using the vCenter console. All was going well until I rebooted the VM and lost connectivity to the host in vCenter.</span> ... See more...
I was working with an ESXi 4.0 host today, configuring a new VM using the vCenter console. All was going well until I rebooted the VM and lost connectivity to the host in vCenter.</span> I tried right clicking the host in vCenter to connect it again, but this resulted in an "unable to connect" error message. I tried to ping the host's management IP but that timed out, so I logged in at the console and used the “Test Management Network” tool. All tests failed, so my next step was to restart the management network. After that I ran the test tool again and it completed successfully, but I was still unable to ping the host or reconnect it to vCenter.</span> After this I found that I could still access the hosted VMs via remote desktop, so I logged in to each one and shut them down prior to rebooting the host. I was unable to restart the host via the console interface because it stopped responding to input after I used the tools to test and restart the management network, so I physically powered the host off. </span> The cold boot of the host resolved the issues with the management network which allowed me to ping it and then reconnect to the host in vCenter so I am in good shape again, but if anyone could shed some light more on what may have caused this, please let me know. Is there anything else I could have tried to get the management network to respond?</span></font>
The patch cables are all brand new Cat5e, but I went ahead and swapped it out anyway. vCenter still shows 100mbps. The switch is HP Procurve 1810. The management interface reports that the... See more...
The patch cables are all brand new Cat5e, but I went ahead and swapped it out anyway. vCenter still shows 100mbps. The switch is HP Procurve 1810. The management interface reports that the NIC-in-question running at 100mbps half duplex mode. I looked around in the BIOS of the host DL380G6 I did not find any settings related to the NIC speed. Appreciate the help. Any other ideas?
All the physical ports on my switch are set to auto-sense the link speed. I have tried 3 different ports with the same result. The other 7 NICs are connected to this same switch without any iss... See more...
All the physical ports on my switch are set to auto-sense the link speed. I have tried 3 different ports with the same result. The other 7 NICs are connected to this same switch without any issues. When I attempted to force it to run at 1000mbps, I received the following error: Error during the configuration of the host. Forcing 1000mbps or faster may not be supported on this network device.
I have two HP DL380G6 servers running ESX4i. These servers are equipped with four 1-gigabit NICs. On Server1 all 4NICs are configured and running at 1000mbps. However, Server2 indicates th... See more...
I have two HP DL380G6 servers running ESX4i. These servers are equipped with four 1-gigabit NICs. On Server1 all 4NICs are configured and running at 1000mbps. However, Server2 indicates that one of the network cards is working at 100mbps instead of 1000mbps. 100mbps is listed for both the configured and actual speed, but I can't seem to change it within vSphere/vCenter. The other 3 NICs in server2 are running at 1000mbps. Any advice would be greatly appreciated!