why cannot ping ESX server ?

[ingsamsam]

I installed ESX server. after compeleting the installation I can t ping it .

below my configuration :

ifconfig -l

Lo:

Link encap : Local LoopBack

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metrics:1

RX packets:27 errors:0 dropped:0 overruns:0 frame:0

TX packets:27 errors:0 dropped:0 overruns:0 carrier:0

collisions: 0 txqueue len:0

RX bytes:1464 (1.4 Kb) TX bytes:1464 (1.4 Kb)

vmnic0 :

Link encap : Ethernet HWaddr 00:18:8B:36:E5:EF

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets : 0 errors :smileyshocked: dropped : 0 overruns:0 frame:0

TX packets : 37 errors: 0 dropped:0 overruns:0 carrier:0

collisions: 0 txqueue len:1000

RX Bytes:0(0.0 b) TX bytes:2220 (2.1 Kb)

Interrupt: 105 Memory :f8000000-f8012100

vmnic1 :

Link encap : Ethernet HWaddr 00:18:8B:36:E5:F1

UP BROADCAST MULTICAST MTU:1500 Metric:1

RX packets : 2715 errors :smileyshocked: dropped : 0 overruns:0 frame:0

TX packets : 0 errors: 0 dropped:0 overruns:0 carrier:0

collisions: 0 txqueue len:1000

RX Bytes:245947 (240.1 Kb) TX bytes:0 (0.0 Kb)

Interrupt: 105 Memory :f4000000-f4012100

vswif0 :

Link encap : Ethernet HWaddr 00:50:56:48:AA:CF

inet addr:2.130.88.93 Bcast:2.130.91.255 Mask:255.255.252.0

up BROADCAST MULTICAST MTU:1500 Metric:1

RX packets : 0 errors :smileyshocked: dropped : 0 overruns:0 frame:0

TX packets : 4 errors: 0 dropped:0 overruns:0 carrier:0

collisions: 0 txqueue len:1000

RX Bytes:0 (0.0 b) TX bytes:168 (168.0 b)

esxcfg-nics -l

Name	PCI	Driver	Link	Speed	Duplex	MTU	DESSCRIPTION
vmnic	09:00.00	bnx2	up	100Mbps	fULL	1500	BroadCom Corporation Broadcom NetXtreme II BCM5708 1000Base-T
vmnic	05:00.00	bnx2	down	100Mbps	half	1500	BroadCom Corporation Broadcom NetXtreme II BCM5708 1000Base-T

esxcfg-vswitch -l

Switch Name Num Ports Used Ports configured Ports MTU Uplinks

vSwitch0 64 4 64 1500 vmnic0

PortGroup Name VLAN ID Used Ports uplinks

VM Network 0 0 vmnic0

Service Console 0 1 vmnic0

esxcfg-vswif -l

Name Port Group IP ADRESS Netmask BroadCast Enabled DHCP

Vswif0 Service Console 2.130.88.93 255.255.252.0 2.130.91.255 True false

Should I do something else once the installation completed

Can someone help ? thansk a lot in advance.

[JeffDrury]

It looks like you are getting TX and RX errors on both NIC's. NIC1 is connected at 100 Full but NIC2 is not connected at all. It looks like your physical network settings may be suspect. Have you checked cables, connections, etc?

Also your service console is set with an IP of 2.130.88.93 which is a public routable IP address. I would not recommend placing an ESX service console on a publicly routable network. This interface should definately be sitting behind a firewall on a non-routable private network.

Usually you would not have to do anything beyond the initial configuration to ping the service console addresss. With your TX and RX errors in addition to the public IP address I do not think you will be able to ping the address. Once those issues are resolved you should be good.

[COdlk]

From your service console can you ping another host? Can you ping your gateway? Check your physical switch and see how the port your ESX server is plugged into is configured correctly.

david

[avlieshout]

Make sure that the duplex settings on both the ESX server and your physical switch are matching.

1 nic is not connected, so check cabling and/or switch port.

Only vmnic0 is connected to the service console which could be just that nic that is not connected, try adding vmnic1 to see if that resolves the ping issue.

on the other hand you are using a public class A network address, which not recommended. Change IP settings of your service console to a private IP range, which is far more secure.

-Arnim van Lieshout

-

---

Blogging: http://www.van-lieshout.com

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

[ingsamsam]

Thanks JeffDrury,

Nic2 is not connected . I didn t connect any cable on it.

I have no error on Tx and RX . I have 0 errors as you can see on my previous message.

I m testing the esx server in test environnement it will not have this adress once in prod.

should give vmnic0 and vmnic1 an an Ip adress ?

Thanks

[JeffDrury]

You cannot give NIC's an IP address in ESX. You can only assign those NIC's to a vSwitch and then assign devices on the vSwitch an IP address. In this case you have given your service console an IP address of 2.130.88.93. Unfortunately because this is a publicly routable IP address it is likely that when you try to ping the address your computer is going out to the internet to ping the address. If you do a trace route and see more than one hop to the address then you are routing across the internet to get to the device. In this routing there are firewalls, etc that are likely dropping your connection to the ESX host. You will not be able to ping or connect to the ESX host until you put it on an isolated private network.

[ingsamsam]

ZawizZ, I m new in this . how can I add vmnic1 ?.

and how can i Make sure that the duplex settings on both the ESX server and your physical switch are matching.?

Thks

[ingsamsam]

COdlk, I can t ping the gateway no any pc in my the same subnet.

[avlieshout]

To add vmnic1 from the console use the following command:

esxcfg-vswitch -L vmnic1 vswitch0

For setting speed/duplex settings use:

esxcfg-nics -s <speed> -d <duplex> <vmnic>

where

<speed> = 10/100/1000

<duplex> = full or half

<vmnic> = vmnic0 or vmnic1

esxcfg-nics -a <vmnic> will set it back to autodetect.

Hint: For a quick test it is perhaps easier to switch the cabling on the back of the server.

-Arnim van Lieshout

-

---

Blogging:

Twitter:

If you find this information useful, please award points for "correct" or "helpful".

[ingsamsam]

thxs Arnim

switch the cabling on the back of the server , doesn't help.

I make duplex as full. same problem.

[ingsamsam]

Thanks everybody

thanks Arnim , By adding vmnic1 to the vswicth0 I can ping now

thx a lot