• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1093
  • Last Modified:

Unable to ping red hat 5.6 instance on vmware esx 3.5

hi experts,

 I am running vmware esx 3.5 and I've created an instance of red hat 5.6 and I have put in the static ip address. When I restart the red hat server I am able to ping it from another system but then as soon as it gets to the logon page I can no longer ping it. What can I try or look for? I''m not very linux familiar.
0
frankbustos
Asked:
frankbustos
  • 11
  • 7
  • 4
  • +1
1 Solution
 
farzanjCommented:
Please issue command in Linux RHEL5

ip a

0
 
farzanjCommented:
Also output for me

sysctl -a
0
 
frankbustosAuthor Commented:
farzanj,

  so I did the ip a command and it appears the eth is active and it says up. Now, I did the sysctl -a but I dont' know how to get it to you if don't have network access on that computer? I'm in the gui interface too so I looked at eth0 and it is active.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
farzanjCommented:
I want to see if you are getting ip address, as a starting point.

I also wanted to see if the ping is being blocked because you said that while it was loading you could still ping it.  Ping is not the only network test.

Being up and active doesn't mean it is getting an IP address correctly.  I wanted to see if there is some kernel parameter like icmp_ignore_all = 1 when you issue sysctl -a command
0
 
frankbustosAuthor Commented:
ok but I there is no way for me to get you that output. Do you want me to look for any icmp_ignore_all =1 and write them down ?
0
 
farzanjCommented:
You are on VMWare, so can't you copy paste it?

Can you tell me what IP address you see?

Can you ping an outside network from RHEL5.6

Can you do
nslookup <some website> from RHEL


commands to issue
ip a
netstat -antpu
sysctl -a
iptables -L
route -n
dig yahoo.com +short
0
 
frankbustosAuthor Commented:
ok the ip address I assigned is 192.168.88.4  and gateway is 192.168.88.1 and I can ping the gateway.

i did a route -n and got the following
Destination                    gateway     genmast                       flags      metric ref     use iface
192.168.122.0               0.0.0.0           255.255.255.0             u          0            0      virbro
192.168.88.0                  0.0.0.0          255.255.254.0             u          0            0      etho
i can ping gateway and that is all...anything from there not pingable.  
0
 
frankbustosAuthor Commented:
i think this 192.168.122 is causing the issue.
0
 
wesly_chenCommented:
Add the default gateway first.
# route add default gw 192.168.88.1
0
 
frankbustosAuthor Commented:
i did and i got file already exists...i do have the right gateway setup in the network.
0
 
wesly_chenCommented:
> i did and i got file already exists
then why "route -n" doesn't show the default gateway?

Disable the interface virbro
# ifconfig virbro down

Then try to ping from other machine.

By the way, what's the IP of the other machine which try to ping this VM?
0
 
frankbustosAuthor Commented:
it shows the default gateway and it is correct. I disabled virbro and still same issue. I try to ping it from other machine and can't reach it..the ip address of the other machine is 192.168.88.90. The version on these are 5.6 and I have two of them with this same problem. I have another one running 5.5 and I don't have any problems with the 5.5 version.
0
 
wesly_chenCommented:
Please examine the boot up message
# dmesg | grep -i net
to see if the eth0 get the right MAC address

compare with /etc/sysconfig/network-scripts/ifcfg-eth0

For VM, a lot of time is the MAC address change arbitrarily, which causes network issue.
0
 
frankbustosAuthor Commented:
ok, so im thinking of re-installing the OS and enter the ip address at that point instead of when I get to the gui interface. But its asking me for ip address, prefix and domain server. What is the prefix?
0
 
wesly_chenCommented:
For IPv4, network prefix 192.168.88.x/24.

Check this for details.
http://en.wikipedia.org/wiki/Subnetwork
0
 
wesly_chenCommented:
Or 192.168.88.0 is the prefix for your network if your network mask is 255.255.255.0
0
 
frankbustosAuthor Commented:
Ok so when I reboot the system and it goes through the process I can ping when it gets to the network support and then after it's done and gets to the desktop I can no longer ping it.
0
 
frankbustosAuthor Commented:
NIS domain name is not set is one ad the failure I see when startin vmware instance????
0
 
wesly_chenCommented:
> NIS domain name is not set
It should be ok.
Did you start ypbind or ypserv at boot up?

Check /etc/nsswitch.conf
to see if you use nis for passwd/group/hosts ...
0
 
frankbustosAuthor Commented:
hi, here is some more information.

Here is the issue why Linux 56 failed to recognize the IP Address after rebooting:

Dnsmasq failed to create listening socket: Address already in use.


BUT THE IP ADDRESS IS NOT ALREADY IN USE.
0
 
wesly_chenCommented:
IP is layer 3 protocol and DNSmasq is higher layer protocol. Dnsmasq is on top of TCP (layer 4).
Thus IP address issue is not caused by higher layer application/protocol.

For VM, there are a couple of things might cause network issue:
1. MAC address change
2. VM host  VMware network device
3. VMware tool inside VM guest
4. eth interface switch around due to MAC change or other.

So please check /var/log/message and dmesg for some clues.

It will be very helpful if  you  can provide those information as farzanj mentioned and post here.
http://www.experts-exchange.com/OS/Linux/Q_26981751.html?cid=1572#a35479755
Other, we have no clue.
0
 
lnkevinCommented:
Wow, I am surprised this has not been resolved yet. Here is my 2 Cents

Since you said your RH is a vm, you can try to ping other vm's in the same subnet. If you can ping them, you may have a wrong network configuration on your RH (router, subnet mask). The reason you can ping other vm's because they use virtual router and directly connect to each other without using ext network configuration.

If you cannot ping other vm's in the subnet, check your vm ethernet in vmware to ensure it's checked as connected. However, you said that you can ping the router, I think it's checked.

do you mind to post ifconfig -a?

K
0
 
frankbustosAuthor Commented:
this solved my problem. The user had namually input the same mac address on another host.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 11
  • 7
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now