sfletcher1959
asked on
IP address on ESX 4.0 server
We have a single ESX Host in our VMWARE lab. I have installed the software on a new server and completed the ESX Server install. Now I want to add the host using VSphere server and it wants the host name or IP address. I know the iLO address for the server, but don't know what IP address were assigned to the two onboard NICs. How can I discover what IP address that the DHCP server assigned to these two nics.
Heu...
"Ipconfig /all" on the guest trought the vmware console ?!
or 'ifconfig' on linux guest
"Ipconfig /all" on the guest trought the vmware console ?!
or 'ifconfig' on linux guest
ASKER
I must have not been clear. I don't have access to the host yet on the vmware console. I must be added first. In order to add, I need the IP address to host name. I don't have either.
ASKER
ifconfig on the server doesn't show an IP address for the nics.
ASKER
Did you give your host a hostname during the install? If so, just ping the hostname from your workstation...that should give you the IP you need.
ASKER
That's the problem, I don't remember having to give it a name.
ASKER
Is there a way to get an IP address if I have the Mac address?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
By default ESX uses DHCP, if you've got no IP addresses, either the NICs are not patched in, not connected, or VLAN issue.
from the hard console where you ran ifconfig, run 'esxcfg-vswif -l' to find out what the IP address is for the service console.
Dear sfletcher1959,
I think you should specify a static IP on your esx server (in the range of your LAN or in a range specified on your PC). I think it's not a good manner to use an IP delivered by a DHCP server for server.
Then you can use this IP in the Vsphere (+ the login & password).
NB: when I see the ifconfig result , I think your ESX server didn't got any IP from DHCP server and can not be reachable
Stefan
I think you should specify a static IP on your esx server (in the range of your LAN or in a range specified on your PC). I think it's not a good manner to use an IP delivered by a DHCP server for server.
Then you can use this IP in the Vsphere (+ the login & password).
NB: when I see the ifconfig result , I think your ESX server didn't got any IP from DHCP server and can not be reachable
Stefan
actually, vswif0 should show here if the ifconfig was ran on an ESX host. Either this isn't from an ESX host or you're missing the service console interface completely and you'll need to recreate it from command line.
Your Scenario:
1. In your case, the esxcfg-vswif -l / ifconfig commands did not give any valid output.
2. You do not remember the hostname.
3. You cannot connect to the host through GUI using vSphere CLient.
4. Its a newly installed ESX host and does not have any virtual machines running on it.
Assuming that all the above are correct:
The best possible and fastest way you can resolve this issue is by reinstalling the ESX host. It hardly takes 20 minutes to complete the installation.
Best Practices:
1. Firstly, plan beforehand for the IP address, hostname and other stuff. So that you can avoid a similar situation, in case any further troubleshooting is required.
2. Secondly, you should always assign a Static IP to the ESX hosts and the vCenter Server.
amit
1. In your case, the esxcfg-vswif -l / ifconfig commands did not give any valid output.
2. You do not remember the hostname.
3. You cannot connect to the host through GUI using vSphere CLient.
4. Its a newly installed ESX host and does not have any virtual machines running on it.
Assuming that all the above are correct:
The best possible and fastest way you can resolve this issue is by reinstalling the ESX host. It hardly takes 20 minutes to complete the installation.
Best Practices:
1. Firstly, plan beforehand for the IP address, hostname and other stuff. So that you can avoid a similar situation, in case any further troubleshooting is required.
2. Secondly, you should always assign a Static IP to the ESX hosts and the vCenter Server.
amit
~coolsport00