lhrslsshahi
asked on
Redhat 6.5 VM Clone - In frequent ping responses
Hi,
I have cloned a RHEL 6.5 VM and I am having problems as I get in-frequent ping responses. I am very familiar with the changes that are required after cloning below are the steps that have worked in the past for me;
rm -f /etc/udev/rules.d/70-persi
vim /etc/sysconfig/networking/
reboot VM
The message I get when I run 'service network restart'
Shuttding down interface eth1: OK
Shutting down loopback interface OK
Bringing up loopback interface OK
Bring up interface eth1: Determining if ip address 192.168.70.140 is already in use for device eth1... OK
Ping sent from my PC
eply from 192.168.70.140: bytes=32 time=4ms TTL=59
eply from 192.168.70.140: bytes=32 time=2ms TTL=59
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
eply from 192.168.70.140: bytes=32 time=3ms TTL=59
eply from 192.168.70.140: bytes=32 time=3ms TTL=59
eply from 192.168.130.140: bytes=32 time=2ms TTL=59
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
eply from 192.168.70.140: bytes=32 time=6ms TTL=59
eply from 192.168.70.140: bytes=32 time=2ms TTL=59
eply from 192.168.70.140: bytes=32 time=3ms TTL=59
I have cloned a RHEL 6.5 VM and I am having problems as I get in-frequent ping responses. I am very familiar with the changes that are required after cloning below are the steps that have worked in the past for me;
rm -f /etc/udev/rules.d/70-persi
vim /etc/sysconfig/networking/
reboot VM
The message I get when I run 'service network restart'
Shuttding down interface eth1: OK
Shutting down loopback interface OK
Bringing up loopback interface OK
Bring up interface eth1: Determining if ip address 192.168.70.140 is already in use for device eth1... OK
Ping sent from my PC
eply from 192.168.70.140: bytes=32 time=4ms TTL=59
eply from 192.168.70.140: bytes=32 time=2ms TTL=59
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
eply from 192.168.70.140: bytes=32 time=3ms TTL=59
eply from 192.168.70.140: bytes=32 time=3ms TTL=59
eply from 192.168.130.140: bytes=32 time=2ms TTL=59
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
equest timed out.
eply from 192.168.70.140: bytes=32 time=6ms TTL=59
eply from 192.168.70.140: bytes=32 time=2ms TTL=59
eply from 192.168.70.140: bytes=32 time=3ms TTL=59
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I normally install VMware Tools and VMXnet 3 after I can get the IPs working.
I will install VMware Tools and comeback to you.
Using static, no ip conflict to be found.
I will install VMware Tools and comeback to you.
Using static, no ip conflict to be found.
ASKER
I get the below when trying to install VmWare Tools.
tar: vmware-tools-distrib/INSTA
Never had this before.
tar: vmware-tools-distrib/INSTA
Never had this before.
ASKER
Managed to install VmWare Tools and vmxnet 3, my vm is now working!
Thanks again hancock.
Thanks again hancock.
ASKER
Started working
Maybe there is another machine using same IP and you have a IP conflict?
You can run "ifconfig" to check the ip on this machine, shut it down, and ping its ip from another machine, see if this IP is still pingable.