VMware Cloud Community
Strago
Contributor
Contributor

New ESX install - no network connectivity

Building a new vi3 environment. On my new ESX servers, I can't ping the gateway, nor can anything else see ESX. I can ping localhost, and multiple ESX servers can ping each other.

We have a HP Blade c-class, 4 nic's per box, each going to a seperate internal switch. Switches 1 and 2 are etherchanneled back to our core network. NIC's 1-2 are intended for VM's. NIC 3 is for COS, and its switch is connected via cat6 back to switch 1, and also gets to the core via the etherchannel. NIC 4 is on a private VLAN for VMOTION.

From the COS, the 4 NIC's are up and at 1000/full, according to esxconfig-nics. Not sure how to tell if autoneg is on or off, I tried enabling it using esxconfig-nics -a. I've also tried binding each of the 4 NIC's to the service console portgroup using esxcfg-vswitch, in case I had the wrong one.

Anything else I can try before going back to our network guys?

Reply
0 Kudos
9 Replies
PerryWhittle
Enthusiast
Enthusiast

post back results of the following

esxcfg-vswif -l

esxcfg-vswitch -l

esxcfg-nics -l

Please rememeber to award points if you found this helpful or correct
Reply
0 Kudos
indrajeets
Enthusiast
Enthusiast

Check the VLAN ID if you have any in the physical network, if any update in VLAN ID Setting of EXS box network.

Do we have uplink set to the internal blade network to you workstation box network switch!

Do You Have HP SIM To Manage The Blade

Reply
0 Kudos
atdude
Enthusiast
Enthusiast

If you can't ping the gateway, can you check/post the contents of /etc/network/sysconfig

You probably know how to do this; if not, login as root and type:

#cat /etc/network/sysconfig

Reply
0 Kudos
Strago
Contributor
Contributor

esxcfg-vswif -l

vswif0 Service Console 134.179.108.20 255.255.254.0 134.179.109.255 true false

esxcfg-vswitch -l

VM Network portgroup1 0 0 vmnic2

Service console portgroup0 0 1 vmnic2

esxcfg-nics -l

vmnic0 03:00.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom NetXtreme II BCM5798 1000Base-SX

vmnic1 07:00.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom NetXtreme II BCM5798 1000Base-SX

vmnic2 16:00.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom NetXtreme II BCM5798 1000Base-SX

vmnic3 18:00.00 bnx2 Up 1000Mbps Full Broadcom Corporation Broadcom NetXtreme II BCM5798 1000Base-SX

Reply
0 Kudos
Strago
Contributor
Contributor

/etc/sysconfig/network

NETWORKING=yes

GATEWAYDEV=vswif0

HOSTNAME=co-esx2

GATEWAY=134.179.108.1

(typing by hand on these.. lousy ILO, no copy-paste..)

Reply
0 Kudos
tsugliani
VMware Employee
VMware Employee

Any vlan tagging ?

if there is a vlan tagging id you can set it up using the following command (vland id 42 in the example):

-> esxcfg-vswitch -p "Service Console" -v 42 vSwitch0

If you aren't sure about your uplink you could try to test all vmnics for the Service Console using the following commands:

To unlink vmnic2 from vSwitch0:

-> esxcfg-vswitch -U vmnic2 vSwitch0

To link another vmnic (example here vmnic0)

-> esxcfg-vswitch -L vmnic0 vSwitch0

-> ping x.x.x.x

and so on with each vmnic in case vmnic2 was not your "real" uplink.

Hope this helps Smiley Happy

zbenga
Enthusiast
Enthusiast

might be obvious but did you setup the subnet mask as it should?

Message was edited by:

zbenga

Reply
0 Kudos
Strago
Contributor
Contributor

Thanks for the suggestions, guys. This turned out to be networking-related, but I've learned a lot about COS stuff in the process, so not a total loss.

Reply
0 Kudos
mcmillgd
Contributor
Contributor

Ive got the same problem, what was your fix in the end?

Reply
0 Kudos