RedHat 5 64 bit on ESXi 4.1 Hypervisor unable to commuincate with the network
I have a vm of Redhat 5 64bit installed and running on VMware hypervisor ESXi 4.1 (the free version) on a DL380 G5 that I want to use for testing.
For some reason I can't get to anythign on the network. I Previously has to other RH 5's installed on Vmware workstation witht eh smae settings. (just testing some backup software) and had no issues.
RH is set to get IP from DHCP server and does. I see the lease but then I notices in the DHCP logs it keep renewing like multiple times in a minute over and over again and again.
testing in RD:
- can't ping default gateway
- can ping loopback
ifconfig eth0 (vm has single vNIC)
shows the vaild ip (and matches lease from DHCP scope), correct broadcast address, correct subnet mask
route -n:
show my correct default gateway
IF I try to ping the RH 5 system it fails from anything elese on the network
RH firewall is set to disabled when installed and verified as well
Not sure why I can't get out and why the DHCP keeps renewing - any help or ideas woudl be much apprecitated!
For some reason I can't get to anythign on the network. I Previously has to other RH 5's installed on Vmware workstation witht eh smae settings. (just testing some backup software) and had no issues.
RH is set to get IP from DHCP server and does. I see the lease but then I notices in the DHCP logs it keep renewing like multiple times in a minute over and over again and again.
testing in RD:
- can't ping default gateway
- can ping loopback
ifconfig eth0 (vm has single vNIC)
shows the vaild ip (and matches lease from DHCP scope), correct broadcast address, correct subnet mask
route -n:
show my correct default gateway
IF I try to ping the RH 5 system it fails from anything elese on the network
RH firewall is set to disabled when installed and verified as well
Not sure why I can't get out and why the DHCP keeps renewing - any help or ideas woudl be much apprecitated!
Did you install vmware-tools on the guest?
ASKER
Well generally you need to update a few things to do that, hence needing network connectivity.
I am pretty sure my other RH test systems had network connectivty when I installed vmware tools on them and I had to connect RH network to download some RPM updates during the process.
Little more work than Windows right click install vmwaret tools and reboot.
I am pretty sure my other RH test systems had network connectivty when I installed vmware tools on them and I had to connect RH network to download some RPM updates during the process.
Little more work than Windows right click install vmwaret tools and reboot.
Is the DHCP server out of available IP for the range it controls?
Now granted I haven't used the exact version of ESX that you are, but I'm pretty sure the concepts are similar. You will have network issues without the vmxnet driver loaded, so having a 100% working network before doing these steps is definitely not a requirement unless you are missing some basic packages in the OS image like tar or gcc for example.
All that needs to be done after you install vmware-tools through the management console is:
Before running those commands however, you may need to run something like vmware-config-tools.pl or vmware-tools.pl or vmware-install etc etc. -- it all depends on what the official path is to install vmware-tools with your version of ESXi
All that needs to be done after you install vmware-tools through the management console is:
/etc/init.d/network stop
rmmod pcnet32
rmmod vmxnet
depmod -a
modprobe vmxnet
/etc/init.d/network startBefore running those commands however, you may need to run something like vmware-config-tools.pl or vmware-tools.pl or vmware-install etc etc. -- it all depends on what the official path is to install vmware-tools with your version of ESXi
I believe peth0 is part of the XEN virtualization available in RedHat.
ASKER
Ok thanks on the peth0 - was just hoping to rule out which sounds liek I can
DHCP scope has available IP's to hand out. Infact gave it one.
Ok Papertrip I'll try vmware tools, sounds like a reasonable idea,
Thanks for everyones time. I'll let you know if I had success when I get a shot to do it.
DHCP scope has available IP's to hand out. Infact gave it one.
Ok Papertrip I'll try vmware tools, sounds like a reasonable idea,
Thanks for everyones time. I'll let you know if I had success when I get a shot to do it.
ASKER
Ran through installation of vmware tools, all goes well up to this error right after is stopps the VMware tools services.
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Looking into how to get them installed, what I have done before with CentOS to get these missing files seems to not work in RedHat.
Before you can compile modules, you need to have the following installed...
make
gcc
kernel headers of the running kernel
Looking into how to get them installed, what I have done before with CentOS to get these missing files seems to not work in RedHat.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
FYI vmware tools are nto required on E1000 network adapater types, confirmed this along the way.
Good to know!
Grats.
ASKER
none
ASKER
- I see eth0 active but peth0 inactive = not sure what peth0 is exactly? I see I could activate it but it shows setup to activate on OS but but for soem reason is not. It aslo is bound to fe.ff.ff.ff.ff.ff MAC which looks to be a broadcast so not sure I want to.
Anyways might help or clarify for me the issue.