Editing VPS Migration with OSPF

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 2: Line 2:
 
[[Category:Networking]]
 
[[Category:Networking]]
  
This article presents how to be able to migrate a container between different subnets in the network by using a dynamic routing protocol such as OSPF. An already working OSPF setup is mandatory, this article only shows the OpenVZ specifics.
+
This article presents how to be able to migrate a VE between different subnets in the network by using a dynamic routing protocol such as OSPF. An already working OSPF setup is mandatory, this article only shows the OpenVZ specifics.
  
 
== Quagga installation ==
 
== Quagga installation ==
Line 25: Line 25:
 
</pre>
 
</pre>
  
In /etc/quagga/ospfd.conf configure the OSPF network and area in which is OpenVZ server will be and configure the redistribution of routes generated by the container.
+
In /etc/quagga/ospfd.conf configure the OSPF network and area in which is OpenVZ server will be and configure the redistribution of routes generated by the VE.
  
 
<pre>
 
<pre>
Line 42: Line 42:
 
== Usage ==
 
== Usage ==
  
Once your OpenVZ server takes part in the OSPF network, you can easily use the ‘vzmigrate’ command to migrate a container between different subnet of the network and the IP of the container will be redistributed in the whole network as a /32 (host route).
+
Once your OpenVZ server takes part in the OSPF network, you can easily use the ‘vzmigrate’ command to migrate a VE between different subnet of the network and the IP of the VE will be redistributed in the whole network as a /32 (host route).
  
 
== Bugs ==
 
== Bugs ==
  
To avoid problems with this setup the IP addresses of your container must be taken outside of any other subnet configured on your network. If the IP address of the container is taken from an actual subnet, the other hosts of the subnet won't be able to communicate with it, except if you use proxy arp on the router.
+
To avoid problems with this setup the IP addresses of your VE must be taken outside of any other subnet configured on your network. If the IP address of the VE is taken from an actual subnet, the other hosts of the subnet won't be able to communicate with it, except if you use proxy arp on the router.

Please note that all contributions to OpenVZ Virtuozzo Containers Wiki may be edited, altered, or removed by other contributors. If you don't want your writing to be edited mercilessly, then don't submit it here.
If you are going to add external links to an article, read the External links policy first!

To edit this page, please answer the question that appears below (more info):

Cancel Editing help (opens in new window)