| new HW IP - unreachable VMs [message #51771] |
Tue, 18 November 2014 15:29  |
evrynet
Messages: 6
Registered: October 2007
|
Junior Member |
|
|
Hello,
We needed to change the main IP of the node however as soon as we replaced the IP the VMs became unreachable. We rebooted the node, restarted the network etc.. but nothing helped. If we add back the old IP everything starts to work.
What else needs to be updated to get the VPSes reachable with the new main IP of the HW?
Thanks
|
|
|
|
|
|
|
|
| Re: new HW IP - unreachable VMs [message #51775 is a reply to message #51771] |
Wed, 19 November 2014 18:15  |
Paparaciz
Messages: 302
Registered: August 2009
|
Senior Member |
|
|
than..
what os is in HN and CTs? what kernel and openvz tools versions?
is it veth or venet network?
is HN and CT ip addresses from the same subnet?
some custom routing?
arp cache?
does containers not reachable from HN itself?
did you tried stop start CT? rebooting HN can not help because on reboot openvz suspends resume CT.
network firerwalling somewhere else?
did you tried debug it with tcpdump?
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
