VMware Cloud Community
John_Balsillie
Enthusiast
Enthusiast

No network access after ESX 4.0 install

Hi all,

I am hoping you can help me out. I have just installed ESX 4.0 natively onto a Dell Latitude D630 (8GB RAM) for demo purposes. The install was flawless and ESX 4.0 boots perfectly. Only problem is networking is dead. vmnic0 and vswif0 are both present and look good with the nic reporting a connected "up" connection to my network.There is no connectivity from the service console out to the network or from the network into the service console.

esxcfg-nics, -vswif and -vswitch all look good. ifconfig also looks good but pings out to the same subnet show destination host unreachable. Same results for an install with static IP and for DHCP.

Any tips would be very welcome. Thanks.

JohnB

John Balsillie VCI VCP5 VCAP4-DCA VCP4 VCP3 Explorer IT Services Pty Ltd
Tags (4)
0 Kudos
7 Replies
Alethay
Enthusiast
Enthusiast

Have you set a VLAN ID in service console during the installation?

Try to remove that!

0 Kudos
John_Balsillie
Enthusiast
Enthusiast

No, I didn't set a VLAN id during install. Just to be sure, how do I get full parameters for the vswif from the command line? ifconfig shows me ip and mask but not VLAN id, gw, or dns addresses.

JohnB

John Balsillie VCI VCP5 VCAP4-DCA VCP4 VCP3 Explorer IT Services Pty Ltd
0 Kudos
Alethay
Enthusiast
Enthusiast

There are some vlan configured on the physical switch where do you attach the host?

Esxcfg-vswitch -l show you VLAN ID, name and physical nic assigned to vswitch.

0 Kudos
John_Balsillie
Enthusiast
Enthusiast

No VLANs. There is only currently a "VM Network" port group and a "Service Console" port group, both on vmnic0 and both have VLAN id of 0.

The physical nic is connected to a 10/100 switch and esxcfg-nics - l shows the link speed also at 100Mbps.

As a ping out from the command line to the gw address that I conigured at install time shows "destination host unreachable" (and not "request timed out") I suspect that this is a routing issue.

The /etc/sysconfig/network file correctly lists the gateway address at 192.168.0.1 (my router) and the route command output also looks good. However, pings to the gw adress fail with destination host unreachable.

???

JohnB

John Balsillie VCI VCP5 VCAP4-DCA VCP4 VCP3 Explorer IT Services Pty Ltd
0 Kudos
Alethay
Enthusiast
Enthusiast

I don't know your network infrastructure, but yes seems to be a routing problem. Ther's another switch between you and your esx or between the esx and your gateway? Try to attach your client on the same 10/100 switch and try to ping your esx s.c.

0 Kudos
John_Balsillie
Enthusiast
Enthusiast

Its a very basic setup. One ESX laptop direct connected to a router with built-in 4 port 10/100 switch. One XP desktop connected to same switch. The router/switch can see both devices but the esx laptop cannot ping the router/switch.

JohnB

John Balsillie VCI VCP5 VCAP4-DCA VCP4 VCP3 Explorer IT Services Pty Ltd
0 Kudos
Alethay
Enthusiast
Enthusiast

Try to restart network services, if the interface bring up succesfull maybe is an hardware compatibility issue.

0 Kudos