Virtual router migration

• US 20110134931A1
• Filed: 12/08/2009
• Published: 06/09/2011
• Est. Priority Date: 12/08/2009
• Status: Abandoned Application

• Current Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Wang, Yi, Rexford, Jennifer Lynn, Merwe, Jacobus Van Der
• Application Number:
  US12/653,079
• Publication Number:
  US 20110134931A1
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0843 based on generic templates
• CPC Class Codes: H04L 41/0897 by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
• CPC Class Codes: H04L 45/586 of virtual routers

Abstract

A Virtual Router (VR) is described that can move freely from one physical router to another in a network. Embodiments enable a network operator to configure a network management primitive that supports live migration of VRs from one physical router to another. To minimize disruptions, VRs allow a migrated control plane from a source router to clone its data plane state from the source router at a destination router while continuing to update its data plane state at the source router. Embodiments temporarily forward packets using both router location data planes to support asynchronous migration of links.

Claims

1. A method for a packet-aware transport network to allow a Virtual Router (VR) to migrate from a source router to a destination router comprising:

prior to migrating a VR, searching for a destination router that does not increase path stretch and is in accordance with physical constraints;

receiving a migrate order at a source router and at a destination router from a Network Management System (NMS) to migrate a VR;

establishing temporary tunnels between the source router and destination router;

copying the VR'"'"'s configuration files at the source router to the file system at the destination router;

cloning the data plane for the migrated VR at the destination router;

redirecting all routing messages destined to the VR at the source router to the destination router;

migrating each link to and from the source router to the destination router, migrating each link independently of the others; and

after all links are migrated to the destination router, removing the VR data plane at the source router and the temporary tunnels.

2. The method according to claim 1 wherein copying the VR'"'"'s configuration files to the file system at the destination router further comprises a stall-and-copy.

3. The method according to claim 1 wherein copying the VR'"'"'s configuration files to the file system at the destination router further comprises an iterative pre-copy and final stall-and-copy.

4. The method according to claim 1 wherein cloning the data plane for the migrated VR further comprises repopulating the destination router'"'"'s VR Forwarding Information Base (FIB) using the control plane Routing Information Base (RIB) and reinstalling Access Control Lists (ACLs) and other data plane states for the migrated VR'"'"'s data plane.

5. The method according to claim 1 further comprising continuing to update the data plane state at the source router when the migrated VR'"'"'s data plane is being cloned at the destination router.

6. The method according to claim 1 further comprising temporarily forwarding packets using the source router and destination router data planes to support asynchronous migration of network links from the source router to the destination router.

7. The method according to claim 1 further comprising configuring routers as carrier substrates on which VRs operate.

8. The method according to claim 1 further comprising not changing the logical topology of the network thereby obviating the need to reconfigure the VRs and avoiding routing protocol convergence delays.

9. The method according to claim 1 wherein to enable VR migration and link migration, the source and destination routers dynamically set-up and change the binding between a VR'"'"'s FIB and its substrate interfaces.

10. A router architecture that provides router virtualization, control and data plane separation, and dynamic interface binding which enables one or more resident Virtual Routers (VRs) to migrate to another router comprising:

a physical substrate coupled to one or more physical interfaces and coupled to one or more tunnel interfaces;

a data plane hypervisor configured to interface between the physical substrate and one or more VR control planes and their respective data planes, and decouple VR control plane software from VR control plane state, a VR'"'"'s control and data plane separation allows the router architecture to migrate the control and data planes of a VR separately; and

a dynamic interface binding configured to allow data structures associated with a particular VR data plane to be dynamically associated with different physical interfaces wherein the isolation between the one or more VRs allows migration of one resident VR without affecting another resident VR and enables VR migration and link migration by dynamically setting-up and changing the binding between a VR'"'"'s Forwarding Information Base (FIB) and its substrate physical interfaces and tunnel interfaces.

11. The router architecture according to claim 10 wherein each VR runs independently with its own control plane and data plane.

12. The router architecture according to claim 11 wherein a VR control plane runs in a physical control processor of the router and the VR'"'"'s data plane may be a partition of a router data plane.

13. The router architecture according to claim 12 wherein a VR control plane includes applications, configurations, routing protocol instances and a Routing Information Base (RIB).

14. The router architecture according to claim 12 wherein a VR data plane includes interfaces, FIB entries and Access Control Lists (ACLs).

15. The router architecture according to claim 10 wherein the data plane hypervisor further comprises:

a first module configured to separate forwarding tables from container contexts;

a second module configured to push the forwarding table entries into a separate data plane; and

a third module configured to dynamically bind virtual interfaces and the forwarding tables.

16. The router architecture according to claim 10 wherein the dynamic interface binding is a configurable switching fabric local to the router.

17. The router architecture according to claim 10 wherein the router architecture partitions resources to support one or more VR instances.