12-01-2008, 03:09 PM
|
|
Web Hosting Master
|
|
Join Date: May 2003
Posts: 2,428
|
|
HyperVM openvz... IP's won't work after OS reinstall
Hi,
I had my box reinstalled with same OS as before, Centos x64
I am creating a NEW VPS and assigning it an IP from my Extended network (not primary) and the IPs are not pingable as if GATEWAY= was missing from the ifcfg config on network-scripts.
Has anyone experienced this?
This is the VPS:
Quote:
[root@host /]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:216.151.144.100 P-t-P:216.151.144.100 Bcast:216.151.144.100 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
From the machine that actually host the VPS:
Quote:
eth0 Link encap:Ethernet HWaddr 00:1C:C0:75:56:FE
inet addr:216.151.144.42 Bcast:216.151.144.47 Mask:255.255.255.248
inet6 addr: fe80::21c:c0ff:fe75:56fe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:291 errors:0 dropped:0 overruns:0 frame:0
TX packets:141 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:26545 (25.9 KiB) TX bytes:32740 (31.9 KiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8024 (7.8 KiB) TX bytes:8024 (7.8 KiB)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
__________________
^_^
|
12-01-2008, 03:23 PM
|
|
We need coffee...
|
|
Join Date: Jan 2003
Location: U.S.A.
Posts: 3,906
|
|
You may want to try the following..
-Type "/etc/init.d/network restart"
Check for a ping
-Check if your resolv.conf file has a working resolver IP "cat /etc/resolv.conf". I typically use the ip address 4.2.2.1 and 4.2.2.2 .
-Check "cat /etc/hosts"
__________________HostPenguin - Separate Yourself â A Christian Owned and Operated Hosting Provider!â Shared, Reseller, Virtual Private Server Hosting and Website Integrationshttp://www.HostPenguin.net - http://Integration.HostPenguin.net - Sales@HostPenguin.net
|
12-01-2008, 03:29 PM
|
|
We need coffee...
|
|
Join Date: Jan 2003
Location: U.S.A.
Posts: 3,906
|
|
I forgot to mention check the routing tables in the CT.
Just use the following command "route"
__________________HostPenguin - Separate Yourself â A Christian Owned and Operated Hosting Provider!â Shared, Reseller, Virtual Private Server Hosting and Website Integrationshttp://www.HostPenguin.net - http://Integration.HostPenguin.net - Sales@HostPenguin.net
|
12-01-2008, 03:43 PM
|
|
Web Hosting Master
|
|
Join Date: May 2003
Posts: 2,428
|
|
Quote:
Originally Posted by Matt - HostPenguin
-Check if your resolv.conf file has a working resolver IP "cat /etc/resolv.conf". I typically use the ip address 4.2.2.1 and 4.2.2.2 .
Sames I use
Quote:
Originally Posted by Matt - HostPenguin
-Check "cat /etc/hosts"
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 liberty.navigatoris.net liberty localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
Quote:
Originally Posted by Matt - HostPenguin
route at the VPS
entered into CT 110
[root@host /]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.0.2.0 * 255.255.255.0 U 0 0 0 venet0
169.254.0.0 * 255.255.0.0 U 0 0 0 venet0
default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0
[root@host /]#
thanks for the help!
__________________
^_^
|
12-01-2008, 03:48 PM
|
|
We need coffee...
|
|
Join Date: Jan 2003
Location: U.S.A.
Posts: 3,906
|
|
I would also check on the hostnode and make sure the IP is routing to the correct location. I am not an expert when it comes to network, but hopefully we can get this up for you!
__________________HostPenguin - Separate Yourself â A Christian Owned and Operated Hosting Provider!â Shared, Reseller, Virtual Private Server Hosting and Website Integrationshttp://www.HostPenguin.net - http://Integration.HostPenguin.net - Sales@HostPenguin.net
Last edited by Matt - HostPenguin : 12-01-2008 at 02:53 PM.
|
12-01-2008, 04:00 PM
|
|
Web Hosting Master
|
|
Join Date: May 2003
Posts: 2,428
|
|
Quote:
Originally Posted by Matt - HostPenguin
I would also check on the hostnode and make sure the IP is routing to the correct location. I am not an expert when it comes to network, but hopefully we can get this up for you!
Here's a PING from hostnode:
Quote:
[root@liberty ~]# ping 216.151.144.100
PING 216.151.144.100 (216.151.144.100) 56(84) bytes of data.
64 bytes from 216.151.144.100: icmp_seq=1 ttl=64 time=0.052 ms
64 bytes from 216.151.144.100: icmp_seq=2 ttl=64 time=0.023 ms
64 bytes from 216.151.144.100: icmp_seq=3 ttl=64 time=0.029 ms
64 bytes from 216.151.144.100: icmp_seq=4 ttl=64 time=0.019 ms
64 bytes from 216.151.144.100: icmp_seq=5 ttl=64 time=0.014 ms
64 bytes from 216.151.144.100: icmp_seq=6 ttl=64 time=0.019 ms
--- 216.151.144.100 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 4999ms
rtt min/avg/max/mdev = 0.014/0.026/0.052/0.012 ms
[root@liberty ~]#
Here's from same internal network a different server:
Quote:
PING 216.151.144.100 (216.151.144.100) 56(84) bytes of data.
--- 216.151.144.100 ping statistics ---
20 packets transmitted, 0 received, 100% packet loss, time 19000ms
I setup the network and everything, I am experimenting with VPS technologies and don't see how it could have been a problem at the switch when the previous install was rock solid for 45 days with those IPs.
It seems like the GATEWAY= is not defined, or at least I see this kind of issue on dedicated servers when the server doesnt know which gateway to use to get thru. I dont know in VPS where the settings are managed.
The #route command definetly seems to not be right. At least in my perspective
__________________
^_^
|
12-01-2008, 04:02 PM
|
|
Web Hosting Master
|
|
Join Date: May 2003
Posts: 2,428
|
|
I have a VPS on another provider, here's the output of the #route command
Quote:
root@ns2 [~]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
191.255.255.0 * 255.255.255.0 U 0 0 0 venet0
192.0.2.0 * 255.255.255.0 U 0 0 0 venet0
169.254.0.0 * 255.255.0.0 U 0 0 0 venet0
default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0
root@ns2 [~]#
__________________
^_^
|
12-01-2008, 04:57 PM
|
|
We need coffee...
|
|
Join Date: Jan 2003
Location: U.S.A.
Posts: 3,906
|
|
What is strange is that your able to ping the IP address from inside the hostnode. To me it appears that their was an issue when you assigned the ip addresses to the Hostnode such as the gateway. Do you have any other issues with different IP addresses or just this one in particular?
If you could, please display the route command from the hostnode.
__________________HostPenguin - Separate Yourself â A Christian Owned and Operated Hosting Provider!â Shared, Reseller, Virtual Private Server Hosting and Website Integrationshttp://www.HostPenguin.net - http://Integration.HostPenguin.net - Sales@HostPenguin.net
|
12-01-2008, 05:06 PM
|
|
Web Hosting Master
|
|
Join Date: Jul 2006
Posts: 1,078
|
|
I had this problem about a year ago with our VPS we offered in London based on OpenVZ. We had A2B2's Rus Foster (I think it was him) and another experienced OVZ admin look at it and it just couldnt be solved, this was a year ago and it might have been another isolated issue with a node of ours.
|
12-04-2008, 02:44 AM
|
|
We need coffee...
|
|
Join Date: Jan 2003
Location: U.S.A.
Posts: 3,906
|
|
You may want to take a look at this wiki page at OpenVZ.org http://wiki.openvz.org/Common_Networking_HOWTOs
__________________HostPenguin - Separate Yourself â A Christian Owned and Operated Hosting Provider!â Shared, Reseller, Virtual Private Server Hosting and Website Integrationshttp://www.HostPenguin.net - http://Integration.HostPenguin.net - Sales@HostPenguin.net
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
 Linear Mode
|
| Postbit Selector |
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|
|
| Login: |
|
|
| Advertisement: |
|
|
| Web Hosting News: |
|
|
|
