how to activate network for vmware host 2.5.2
I will move some virtual machines running on a vmware server 2.5.2 to a new ESXi5. I found the root and password account, and i have physical access to the console. The VMs are running fine. But – I cannot access to Server with SSH. Ping will not answer. If I go to the console (physically) with ifconfig eth0 I can see the IP, but all traffic counters for this if are 0. I cane not ping anything in the LAN. The vmnic0 looks fine.
How cane I activate the network adapter to manage the vm’s and use ssh? What is blocking the network traffic for the host?
How cane I activate the network adapter to manage the vm’s and use ssh? What is blocking the network traffic for the host?
this is a networking question probably completely unrelated with vmware
we need much more information in order to help because at that state, the problems can range from "the cable is not plugged" to "the network card is dead" ( very unlikely to be the case ) including various possibilities such as a wrong vlan, the ip of the machine is alone in an isolated network...
what IP, what gateway, what mask do you use ?
what physical equipments do you go through from the ESX to it's gateway ?
what happens when you ping the gateway ?
what is the output of "arp -a" after you pinged it ?
...
we need much more information in order to help because at that state, the problems can range from "the cable is not plugged" to "the network card is dead" ( very unlikely to be the case ) including various possibilities such as a wrong vlan, the ip of the machine is alone in an isolated network...
what IP, what gateway, what mask do you use ?
what physical equipments do you go through from the ESX to it's gateway ?
what happens when you ping the gateway ?
what is the output of "arp -a" after you pinged it ?
...
ASKER
Ok – more details and answers to questions:
Yes, i agree, that it is a unix setting, that makes my trouble
-- please belief me , there is only one Ethernet adapter, and the vm is running fine. So cable an everything like hardware is ok. One vm is running on 171.1.1.16.
what IP, what gateway, what mask do you use ?
171.1.1.44 171.1.1.19 255.255.255.0 and yes a know that this is not a private range
what physical equipments do you go through from the ESX to it's gateway ?
I can only use the console directly plug in to hardware. NetAdapter, Cable, unmanaged Switch, Cable, Firewall (Gateway). And this is working fine for the vm - but not for the host.
what happens when you ping the gateway ?
ping results with “Destination Host Unreachable” 20 times … 0 packet received
what is the output of "arp -a" after you pinged it ?
? (171.1.1.19) at >incomplete> on eth0
171.1.1.19 is the gateway, eth0 is one of three adapter when I call ifconfig (eth0, lo, vmnic0)
I am not used with unix. With windows wording it seams like something is disabled, or a local firewall is preventing any network traffic.
Yes, i agree, that it is a unix setting, that makes my trouble
-- please belief me , there is only one Ethernet adapter, and the vm is running fine. So cable an everything like hardware is ok. One vm is running on 171.1.1.16.
what IP, what gateway, what mask do you use ?
171.1.1.44 171.1.1.19 255.255.255.0 and yes a know that this is not a private range
what physical equipments do you go through from the ESX to it's gateway ?
I can only use the console directly plug in to hardware. NetAdapter, Cable, unmanaged Switch, Cable, Firewall (Gateway). And this is working fine for the vm - but not for the host.
what happens when you ping the gateway ?
ping results with “Destination Host Unreachable” 20 times … 0 packet received
what is the output of "arp -a" after you pinged it ?
? (171.1.1.19) at >incomplete> on eth0
171.1.1.19 is the gateway, eth0 is one of three adapter when I call ifconfig (eth0, lo, vmnic0)
I am not used with unix. With windows wording it seams like something is disabled, or a local firewall is preventing any network traffic.
ASKER
and a screenshot from
ping 171.1.1.16
arp -a
Bildschirmfoto-2012-09-15-um-19..png
Bildschirmfoto-2012-09-15-um-19..png
ping 171.1.1.16
arp -a
Bildschirmfoto-2012-09-15-um-19..png
Bildschirmfoto-2012-09-15-um-19..png
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
what is the complete output of ipconfig ?
how many NICs are there ?
all plugged ?
are you sure the eth0 interface is actually plugged to something ?
how many NICs are there ?
all plugged ?
are you sure the eth0 interface is actually plugged to something ?
can you connect with the vSphere Client?
is this ESXi ?
is this ESXi ?
ASKER
Hi skullnobrains
Problem is solved.
Unbelievable! After your opinion I decide to check the hardware. Because I am working remote, I asked the operator once more, but this time, I asked him to send me a picture from the backside of this server. And what did I saw at the piture!! Two cables plug in – but only on one plug LED burning!!
I don’t really know what hi did, but now I can ping.
Thanks you, to go thru with me the checklists.
Problem is solved.
Unbelievable! After your opinion I decide to check the hardware. Because I am working remote, I asked the operator once more, but this time, I asked him to send me a picture from the backside of this server. And what did I saw at the piture!! Two cables plug in – but only on one plug LED burning!!
I don’t really know what hi did, but now I can ping.
Thanks you, to go thru with me the checklists.
you could have used the following ESXi commands
Esxcfg-vswitch
Esxcfg-vmknic
Esxcfg-nics
references to eth0 are really not relevant in ESXi world, ESXi is not really Linux or Unix.
vmnic(x) are the interfaces.
Esxcfg-vswitch
Esxcfg-vmknic
Esxcfg-nics
references to eth0 are really not relevant in ESXi world, ESXi is not really Linux or Unix.
vmnic(x) are the interfaces.
@perolin
not sure i was that helpfull, here, but thanks
sometimes it does come to something dumb
it's good to see you solved your problem
@hanccocka
i believe these commands would have proven helpful, thancks for the input
but just for the record, esxi is a patched redhat5
not sure i was that helpfull, here, but thanks
sometimes it does come to something dumb
it's good to see you solved your problem
@hanccocka
i believe these commands would have proven helpful, thancks for the input
but just for the record, esxi is a patched redhat5
@skull.....ESXi 5.0 has no service console. ESX was nearer Linux.
have you connected with the vSphere Client, and started SSH and ESXi shell?