WO2013174096A1

WO2013174096A1 - Method, device and system for migration of cloud computing virtual machine

Info

Publication number: WO2013174096A1
Application number: PCT/CN2012/083270
Authority: WO
Inventors: 李广鹏; 于德雷; 刘颖
Original assignee: 华为技术有限公司
Priority date: 2012-05-25
Filing date: 2012-10-22
Publication date: 2013-11-28
Also published as: CN103428252B; CN103428252A

Abstract

Provided are a method, device and system for the migration of a cloud computing virtual machine, which relate to the field of communications, and can allow the traffic heading to a virtual machine after migration to directly arrive at a new data centre without a network side needing to configure a VPN via a management plane. The virtual machine migration method includes: a first CGR constructing a message of MPLS VPN site migration, which contains a parameter indicating the position of a data centre where a second CGR is located, and transmitting same to a first PE; after receiving the message, according to the parameter indicating the position of the data centre where the second CGR is located, the first PE finding a second PE connected to the second CGR, and transmitting to the second PE a control message indicating the MPLS VPN site migration; and after receiving the control message, the second PE transmitting to the second CGR a message indicating the MPLS VPN site migration, so as to migrate an MPLS VPN site into the second CGR. The embodiments of the present invention are applied to a communication network.

Description

Method, device and system for cloud computing virtual machine migration

The present invention relates to the field of communications, and in particular, to a method, device, and system for cloud computing virtual machine migration. BACKGROUND With the increasing scale of the cloud computing market, the network connection capability of cloud service providers has gradually become a bottleneck for further expansion of cloud services. Network operators began to explore the business model of packaging and selling cloud resources and network resources, especially MPLS (Multi-Protocol Label Switching) VPN (Virtual Private Network) resources. However, the organization, management, and operation of cloud resources are almost fully automated, while the operation of MPLS VPNs is slightly behind.

Although some manufacturers have proposed the technology of MPLS VPN dynamic provisioning, automatic site access and revocation, but still can not adapt to the dynamic migration characteristics of cloud computing virtual machines; some operators have proposed to build VPLS between data centers (Virtual Private Lan Service, virtual private LAN service) to complete the migration of cloud computing virtual machines, but this method does not take into account the operating mode of network service providers and third-party cloud service providers.

When an enterprise user connects to a third-party cloud service provider through MPLS IP VPN, how to ensure information security between the carrier network and the cloud service provider infrastructure, and complete the cross-data center migration of the cloud computing virtual machine becomes urgent A problem solved.

At present, the management parameters are generally used to solve the exchange of configuration parameters, such as: management and maintenance of the VPN by the network side VPN controller. When the cloud computing virtual machine is migrated, the cloud manager and the VPN controller first establish two data center spaces. The Layer 2 VPN connection is then used for cloud computing virtual machine migration using cloud computing virtual machine LAN migration technology. Enable cloud managers to cross data by managing and maintaining VPNs between data centers Heart creates and maintains a VPC (Virtual Private Cloud).

Although the technology can complete the migration process of the cloud computing virtual machine across the WAN, the network side needs to configure the VPN through the management plane, and the location of the access point of the cloud computing virtual machine MPLS VPN site does not change before and after the migration. The migration of cloud computing virtual machine traffic needs to go through the original data center and then to the migrated data center, increasing the packet transmission delay. SUMMARY OF THE INVENTION Embodiments of the present invention provide a method, a device, and a system for migrating a cloud computing virtual machine. The network side does not need to configure the VPN through the management plane, and the traffic destined for the cloud computing virtual machine can be directly reached after the migration. data center.

In order to achieve the above object, embodiments of the present invention use the following technical solutions:

In one aspect, a method for cloud computing virtual machine migration is provided, including:

The first cloud data center egress gateway router CGR constructs a multi-protocol label switching virtual private network MPLS VPN site migration message; the packet contains a parameter indicating the location of the data center where the second cloud data center egress gateway CGR is located;

Sending, by the first CGR, the packet to the first carrier edge router PE, so that the first PE, after receiving the packet, finds according to the parameter indicating the location of the data center where the second CGR is located. a second PE that is connected to the second CGR, and sends a control packet indicating the migration of the MPLS VPN site to the second PE; after receiving the control packet, the second PE sends the second CGR to the second CGR. Sending a message indicating the migration of the MPLS VPN site, so that the MPLS VPN site moves to the data center where the second CGR is located.

The first carrier edge router PE receives the first cloud data center exit gateway router

Multi-protocol label switching virtual private network sent by CGR MPLS VPN site migration talent;

The first PE finds a second carrier edge router PE connected to the second CGR according to the parameter indicating the location of the data center where the second CGR is located in the packet migrated by the MPLS VPN site; The first PE constructs a control packet for the MPLS VPN site to be migrated, and sends the control packet to the second PE, so that after the second PE receives the control packet, Sending, to the second CGR, a message indicating that the MPLS VPN site is migrated, so that the MPLS VPN site in the data center where the first CGR is located is moved to the data center where the second CGR is located;

The packet migrated by the MPLS VPN site includes the following parameters: a migration ID indicating the migration process and state of the cloud computing virtual machine; and

Current virtual private network name; and

Indicate the location of the data center where the second CGR is located; and

Instructing to revoke a clear flag associated with the first CGR; and

Indicates the autonomous system number of the second CGR.

The second carrier edge router PE receives the control information of the multi-protocol label switching virtual private network MPLS VPN site migration sent by the first PE, where the control packet is that the first PE receives the first cloud data. After the MPLS VPN site migrates the packet sent by the CGR sent by the central egress gateway router, the MPLS VPN site migrates the packet with the parameter indicating the location of the data center where the second C GR is located.

The second PE constructs a message indicating that the MPL S VPN site is migrated, and sends the message to the second CGR, so that the MPLS VPN site in the data center where the first CGR is located is in the data center where the second CGR is located. Move in;

The control packet includes the following parameters:

Indicates the migration ID of the cloud computing virtual machine migration process and status; and

The name of the lower port of the second PE; and

Current virtual private network name; and

a route specifier/route target on the first PE; and

a virtual private network peer address list on the first PE; and

Indicates the autonomous system number of the second CGR.

The second cloud data center exit gateway router CGR receives the second carrier edge route The message sent by the PE to indicate the multi-protocol label switching virtual private network MPLS VPN site migration; wherein the message is generated after the second PE receives the control packet sent by the first PE and indicates the migration of the MPLS VPN site; After receiving the MPLS VPN site migration message sent by the first CGR, the first PE sends the control message indicating the migration of the MPLS VPN site to the second PE;

The second cloud data center egress gateway router CGR performs the migration of the MPLS VPN site in the data center where the first CGR is located.

In one aspect, a first cloud data center egress gateway router CGR is provided, including: a generating unit, configured to construct a packet of a multi-protocol label switching virtual private network MPLS VPN site migration; the packet includes a second CGR indication The parameters of the location of the data center;

a sending unit, configured to send, to the first carrier edge router PE, the packet that is configured by the generating unit, so that the first PE, after receiving the packet, according to the indication in the packet The parameter of the location of the data center where the second CGR is located finds the second PE connected to the second CGR, and sends a control packet indicating the migration of the MPLS VPN site to the second PE; the second PE receives After the control packet, the message indicating the migration of the MPLS VPN site is sent to the second CGR, so that the MPLS VPN site moves to the data center where the second CGR is located.

In one aspect, a first carrier edge router PE is provided, including:

The receiving unit is configured to receive the MPLS VPN site migration of the multi-protocol label switching virtual private network sent by the first cloud data center egress gateway router CGR; the foregoing parameter includes the following parameters:

Current virtual private network name; and

Indicate the location of the data center where the second CGR is located; and

Instructing to revoke a clear flag associated with the first CGR; and

Indicates the autonomous system number of the second CGR;

a processing unit, configured to find a second carrier edge router PE connected to the second CGR according to the parameter indicating a location of the data center where the second CGR is located;

a generating unit, configured to construct a control report indicating the number of migrations of the MPLS VPN site Text

a sending unit, configured to send the control packet configured by the generating unit to the second carrier edge router PE, so that the second PE sends the control packet to the second CGR after receiving the control packet And the message indicating that the MPLS VPN site is migrated, so that the MPLS VPN site in the data center where the first CGR is located is moved to the data center where the second CGR is located.

In one aspect, a second carrier edge router PE is provided, including:

a receiving unit, configured to receive, by the first carrier edge router PE, a control packet indicating that the multi-protocol label switching virtual private network MPLS VPN site migrates, where the control packet is that the first PE receives the first cloud After the data center egress gateway router CGR sends the MPLS VPN site to be migrated, the MPLS VPN site migration packet includes a parameter indicating a location of the data center where the second CGR is located; the control packet includes The following parameters:

The name of the lower port of the second PE; and

Current virtual private network name; and

a route specifier/route target on the first PE; and

a virtual private network peer address list on the first PE; and

Indicates the autonomous system number of the second CGR.

a generating unit, configured to send a message indicating the migration of the MPLS VPN site, and a sending unit, configured to send, by using the generating unit, a message indicating the migration of the MPLS VPN site to the second CGR, to perform the first CGR The MPLS VPN site of the data center moves to the data center where the second CGR is located.

In one aspect, a second cloud data center egress gateway router CGR is provided, including: a receiving unit, configured to receive, by the second carrier edge router PE, a message indicating that the multi-protocol label switching virtual private network MPLS VPN site migrates; The message is generated after the second PE receives the control packet that is sent by the first PE and indicates the migration of the MPLS VPN site; the first PE receives the packet that is migrated by the MPLS VPN site sent by the first CGR. And sending, to the second PE, a control packet indicating the migration of the MPLS VPN site; And a processing unit, configured to perform, according to the message indicating the migration of the MPLS VPN site, received by the receiving unit, the MOL S VPN site of the data center where the first CGR is located.

In one aspect, a network for cloud computing virtual machine migration is provided, including:

The first cloud data center egress gateway router CGR, the first operator edge router PE, the second operator edge router PE, and the second cloud data center egress gateway router CGR.

The method, device, and system for the cloud computing virtual machine migration provided by the embodiment of the present invention, the first CGR sends the MPLS VPN site migration message to the first PE, and then the first PE sends the control message to the second PE. The message sent by the second PE to the second CGR carries the parameter indicating the migration of the MPLS VPN site, so that the PE of the network operator can provide the dynamic migration service of the MPLS VPN site to the data center of the cloud service provider, and the network side PE participates. After the migration process, the traffic to the virtual machine can go directly to the migrated data center after the migration is completed. It is not necessary for the network side to configure the VPN through the management plane, which can improve the efficiency of the VPN operation. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are merely Some embodiments of the present invention may also be used to obtain other drawings based on these drawings without departing from the prior art.

1 is a schematic diagram of a network environment architecture of a cloud computing virtual machine MPLS VPN site migration according to an embodiment of the present invention;

2 is a block diagram 1 of a flow chart of a method for migrating a cloud computing virtual machine according to an embodiment of the present invention;

3 is a schematic block diagram 2 of a method for migrating a cloud computing virtual machine according to another embodiment of the present invention;

4 is a schematic block diagram 3 of a method for migrating a cloud computing virtual machine according to another embodiment of the present invention;

FIG. 5 is a flow chart of a method for migrating a cloud computing virtual machine according to another embodiment of the present invention; Schematic diagram block four;

6 is a schematic block diagram 5 of a method for migrating a cloud computing virtual machine MPLS VPN site according to another embodiment of the present invention;

FIG. 7 is a format of a parameter indicating a MPLS VPN site migration in a path attribute of a BGP Update packet according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural block diagram of a first CGR according to an embodiment of the present invention; FIG. 9 is a schematic structural block diagram of a first PE according to an embodiment of the present invention;

FIG. 10 is a schematic block diagram of another structure of a first PE according to an embodiment of the present invention; FIG. 11 is a schematic structural block diagram of a second PE according to an embodiment of the present invention;

FIG. 12 is a schematic block diagram of another structure of a second PE according to an embodiment of the present invention; FIG. 13 is a schematic block diagram of a second CGR according to an embodiment of the present invention; FIG. FIG. 15 is a schematic structural diagram of a network of a cloud computing virtual machine migration according to an embodiment of the present invention. The technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. example. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The network architecture of this embodiment is exemplarily shown in FIG. 1. The first PE (Provider Edge, Carrier Edge Router) 12 and the first CGR (Cloud Data Center Egress Gateway Router, the corresponding English expression is Cloud Gateway. Routers 11 are connected, and the first PE 12 and the second PE 13 can be directly or indirectly connected (connected through the backbone network when indirectly connected), and the second PE 13 is connected to the second CGR 14. The VCE (Virtual Customer Edge) 111 and the VCE 141 are respectively configured on the first CGR 11 and the second CGR 14, and are respectively connected to the sub-interfaces of the first PE 12 and the second PE 13 respectively. Logical link, running the border gateway protocol on the logical link A (BGP) routing protocol to exchange routing information.

The method for migrating a cloud computing virtual machine provided by the embodiment of the present invention, as described in FIG. 2, the method includes:

101. The first CGR 11 constructs a packet that is migrated by the MPLS VPN site. The packet migrated by the MPLS VPN site includes a parameter indicating a location of the data center where the second CGR 14 is located.

For example, the MPLS VPN site migration may include the following parameters: a Migration ID indicating the migration process and status of the cloud computing virtual machine; and

Current VPN Name; and

Indicates the Destination DC location of the second CGR; and

Instructing to revoke the Clear Flag connected to the first PE; and

Indicates the AS number (autonomous system number) of the second CGR, and so on.

Further, the above parameters may be encapsulated in the path attribute of the BGP Update (boundary gateway protocol update). For example, the format may be:

As shown in FIG. 7, the first byte 0x90 is fixed, the second byte indicates the type of the attribute of the parameter, and the third and fourth bytes indicate the byte length occupied by the parameter, the 5th to the 20th words. The section stores the Migration ID, the 21st to 24th bytes store the Destination DC location, the 25th byte stores the Clear Flag, the 26th and 27th bytes store the AS number of the second CGR, and the remaining words Section stores the current VPN Name

The first CGR 11 sends the packet migrated by the MPLS VPN site to the first PE 12, so that the first PE 12 receives the packet migrated by the MPLS VPN site, according to the packet migrated by the MPLS VPN site. The parameter indicating the location of the data center where the second CGR 14 is located finds the second PE 13 connected to the second CGR 14, and sends a control message indicating the migration of the MPLS VPN site to the second PE 13; the second PE 13 receives the control After the message, a message indicating the migration of the MPLS VPN site is sent to the second CGR 14 to move the MPLS VPN site to the data center where the second CGR 14 is located. The method for migrating a cloud computing virtual machine provided by the embodiment of the present invention, the first C GR sends a packet migrated by the MPLS VPN site to the first PE, and then the control packet sent by the first PE to the second PE and the second PE The message sent by the CGR carries the parameters indicating the migration of the MPLS VPN site, so that the PE of the network operator can provide the dynamic migration service of the MPLS VPN site to the data center of the cloud service provider, and since the network side PE participates in the migration process, After the migration is complete, traffic to the virtual machine can go directly to the migrated data center. It is not necessary for the network side to configure the VPN through the management plane, which can improve the efficiency of the VPN operation. In addition, during the entire migration process, the network side and the cloud service provider did not send their own device configuration information to the other party, thus ensuring the security of the business information of the two types of operators.

A method for migrating a cloud computing virtual machine according to another embodiment of the present invention, as described in FIG. 3, the method includes:

201. The first PE 12 receives the packet of the MPLS VPN site migration sent by the first CGR 11.

For example, the MPLS VPN site migration packet may include the following parameters: a Migration ID indicating the migration process and status of the cloud computing virtual machine; and a current VPN Name;

a Destination DC location indicating the second CGR; and

Instructing to revoke a Clear Flag connected to the first CGR; and

Indicates the AS Number of the second CGR.

If the Clear Flag in the MPLS VPN site migration received by the first PE 12 indicates that the connection between the first PE and the first CGR 11 is revoked, the VPN routing table setting of the first PE is started. The timer, after the specified time arrives, the first PE revokes the connection with the first CGR 11.

The first PE 12 finds the second PE 13 connected to the second CGR 14 according to the parameter indicating the location of the data center where the second CGR 14 is located in the packet migrated by the MPLS VPN site.

For example, the searching process in the 202 may be: the first PE 12 obtains the IP address of the second PE 13 according to the parameter query indicating the Destination DC location of the second CGR 14 in the packet migrated by the MPLS VPN site, and the Next to the second PE 13 Interface name. Further, the first PE 12 may obtain the RD/RT (route specifier/route target) of the first PE 12 and the VPN peer of the first PE 12 according to the VPN Name in the packet migrated by the MPLS VPN site. Net peer address list).

203. The first PE 12 constructs a control packet indicating the migration of the MPLS VPN site, and sends the control packet to the second PE 13. The second PE 13 sends the control packet to the second CGR 14 after receiving the control packet. A message indicating the migration of the MPLS VPN site, so that the MPLS VPN site of the data center where the first CGR 11 is located migrates to the data center where the second CGR 14 is located.

For example, the control packet of the first PE 12 that indicates the migration of the MPLS VPN site may include the following parameters:

a Migration ID indicating the migration process and status of the cloud computing virtual machine; and a lower port name of the second PE 13;

Current VPN Name; and

RD/RT of the first PE 12; and

VPN peer of the first PE 12; and

Indicates the AS Number of the second CGR 14, and the like.

The method for migrating a cloud computing virtual machine provided by the embodiment of the present invention, the first CGR sends a packet migrated by the MPLS VPN site to the first PE, and then the control packet sent by the first PE to the second PE and the second PE are sent to the second The message sent by the CGR carries the parameters indicating the migration of the MPLS VPN site, so that the PE of the network operator can provide the dynamic migration service of the MPLS VPN site to the data center of the cloud service provider, and since the network side PE participates in the migration process, After the migration is complete, traffic to the virtual machine can go directly to the migrated data center. It is not necessary for the network side to configure the VPN through the management plane, which can improve the efficiency of the VPN operation. During the entire migration process, the network side and the cloud service provider did not send their own device configuration information to each other, which ensured the security of the business information of the two types of operators.

A method for migrating a cloud computing virtual machine according to another embodiment of the present invention, as described in FIG. 4, the method includes:

301. The second PE 13 receives the control packet that is sent by the first PE 12 and indicates the migration of the MPLS VPN site. The control packet is that the first PE 12 receives the first CGR. After the MPLS VPN site migrates the packet, the MPLS VPN site migrates the packet with the parameter indicating the location of the data center where the second CGR 14 is located.

For example, the control packet received by the second PE 13 may include the following parameters: a Migration ID indicating the migration process and status of the cloud computing virtual machine; and a lower port name of the second PE 13;

Current VPN Name; and

RD/RT on the first PE 11; and

VPN peer on the first PE 11; and

Indicates AS Number _{0 of the} second CGR 14

Optionally, the second PE 13 may determine, according to the RD/RT in the control packet indicating the first PE 11, whether the second PE 13 configures the VPN routing forwarding table of the MPLS VPN station.

If the second PE 13 does not configure the VPN routing forwarding table of the MPLS VPN site, a VPN routing forwarding table needs to be created. The second PE 13 applies for a site network segment to the network database connected to the second PE 13 according to the VPN name, and obtains the sub-interface number of the second PE 13 and the used Vlan lD (virtual local area network ID). After the second CGR 14 sends the MPLS VPN site migration message, the second PE 13 also configures the VPN routing forwarding table instance, binds to the sub-interface of the second PE 13 and configures the BGP protocol (Border Gateway Protocol).

If the second PE 13 has configured the VPN routing forwarding table of the MPLS VPN site, the second PE 13 obtains the Vlan ID of the interface bound to the VPN routing forwarding table according to the VPN routing forwarding table.

302. The second PE 13 constructs a message indicating an MPLS VPN site migration.

For example, when the second PE 13 does not configure the VPN routing table of the MPLS VPN site, the MPLS VPN site migration message constructed by the second PE 13 may include the following parameters:

a Migration ID indicating the migration process and status of the cloud computing virtual machine; and Vlan ID; and

Transit IP Section applied by the second PE 13 to the network database (transit IP address) a segment); wherein the transit IP address segment is obtained from the network segment of the site;

The AS number of the domain where the second PE 13 is located.

For example, if the second PE 13 has configured the VPN routing forwarding table of the MPLS VPN site, the message indicating the MPLS VPN site migration configured by the second PE 13 may include the following parameters:

a Migration ID indicating the migration process and status of the cloud computing virtual machine; and

Vlan ID.

It should be noted that, if the second PE 13 has configured the VPN routing forwarding table of the MPLS VPN site, the message constructed by the second PE 13 does not include the Transit IP Section and the second PE 13 applied by the second PE 13 to the network database. The AS number of the domain.

303. The second PE 13 sends, to the second CGR 14, a message indicating that the MPLS VPN site is migrated by the second PE 13; and the data of the MPLS VPN site of the data center where the first CGR 11 is located to the second CGR 14 is performed. The center moved in.

A method for migrating a cloud computing virtual machine according to another embodiment of the present invention, as described in FIG. 5, the method includes:

401. The second CGR 14 receives the message that is sent by the second PE 13 and indicates the migration of the MPLS VPN site. The message is generated by the second PE 13 after receiving the control packet that is sent by the first PE 12 and indicating the migration of the MPLS VPN site. The first PE 12 receives the message of the migration of the MPL S VPN site sent by the first CGR 11, and sends a control message indicating the migration of the MPLS VPN site to the second PE 13. For example, the message that the second CGR 14 receives the MPLS VPN site migration sent by the second PE 13 may include the following parameters:

a Migration ID indicating the migration process and status of the cloud computing virtual machine;

Vlan ID;

Transit IP Section applied by the second PE 13 to the network database;

The AS number of the domain where the second PE 13 is located.

Optionally, the second CGR 14 needs to create a VCE (Virtual User Edge Router) 141 and configure the BGP protocol.

For example, the message indicating the MPLS VPN site migration sent by the second PE 13 received by the second CGR 14 may also include the following parameters:

Vlan ID.

When the second CGR 14 receives the message sent by the PE 13 and does not include the Transit IP Section applied by the second PE 13 to the network database and the AS Number of the domain where the second PE 13 is located, the second CGR 14 may determine that the second PE 13 is configured. The VPN routing forwarding table for the MPLS VPN site.

Optionally, the second CGR 14 obtains the local VCE 141 according to the Migration ID and the Vlan ID.

402. The MPLS VPN site in the data center where the first CGR 11 is located is moved to the data center where the second CGR 14 is located.

The method for migrating a cloud computing virtual machine provided by the embodiment of the present invention, the first C GR sends a packet migrated by the MPLS VPN site to the first PE, and then the control packet sent by the first PE to the second PE and the second PE The message sent by the CGR carries the parameters indicating the migration of the MPLS VPN site, so that the PE of the network operator can provide the dynamic migration service of the MPLS VPN site to the data center of the cloud service provider, and since the network side PE participates in the migration process, After the migration is complete, traffic to the virtual machine can go directly to the migrated data center. It is not necessary for the network side to configure the VPN through the management plane, which can improve the efficiency of the VPN operation. During the entire migration process, the network side and the cloud service provider did not send their own device configuration information to each other, which ensured the security of the business information of the two types of operators. A method for migrating a cloud computing virtual machine according to another embodiment of the present invention is as shown in FIG. 1 . The application scenario assumes that: all virtual machine resources in a subnet in the data center where the first CGR 11 is located need to be migrated to the second CGR 14 is located in the data center. The network side needs to save some information, including information identifying the location of the data center network access point and information about the IP address segment available on the MPLS VPN cloud side site.

Example ')· born:

1. Information identifying the location of the data center network access point

This information is allocated when the data center requests to access the MPLS network, and then stored in a network database accessible by the network device. The network database table is defined as Table 1:

Table 1

2. User IP address segment available on the MPLS VPN cloud side site

This information is registered by the user when applying for VPN, and is defined in the network database as field name. Data type Description

VPN ID Integer

Primary key. Uniquely identifies a VPN

(Virtual Private Network ID) (integer)

PE IP Downside PE connection VCE (virtual user network

IP Address

(PE sub-interface IP ground edge device) Sub-interface needs to be configured

(IP address)

IP address)

VCE IP Upside

IP address VCE connection PE interface needs to be configured (VCE port IP address

IP address of (IP address)

site) Net Mask Integer requires only two available transit IP locations

(netmask) (integer) The network segment of the address, the mask length is generally 30. Is the transit IP address segment already?

Be Used Integer

Used, 0 means not used, 1

(used) (integer)

Indicates that it is used

Table 2

As shown in FIG. 6, the method for migrating a cloud computing virtual machine MPLS VPN site provided by the embodiment of the present invention includes:

501. The first CGR 11 constructs a BGP Update packet that is migrated by the MPLS VPN site, and the parameter indicating the migration of the MPLS VPN site is encapsulated into the path attribute of the BGP Update packet by extending the BGP Update packet. For example, the BGP Update message may include the following parameters indicating the MPLS VPN site migration: a Migration ID indicating the current cloud computing virtual machine migration process and status, a current VPN Name, indicating a Destination DC location of the second CGR 14, Indicates to cancel the Clear Flag of the first CGR 11 and the PE-12, indicating the AS number of the second CGR 14.

Optionally, the migration ID is generated by the cloud side, and uniquely identifies a virtual machine migration process and its status. When the network side completes the site migration, the migration ID needs to be carried when responding to the cloud side. The VPN Name is obtained from the network operator when the user applies for VPN. It can uniquely identify the VPN that the user applies for. The Destination DC location is determined based on the destination data center of the virtual machine resource migration. The Clear Flag identifies whether the first PE 12 needs to clear the VPN routing forwarding table of the VPN.

Optionally, the format of the parameter in the path attribute of the BGP Update packet is as shown in FIG. 7. The first byte 0x90 is a fixed format, and the second byte indicates the type of the attribute of the parameter. 4 bytes indicate the byte length occupied by the parameter, 5-20 bytes store the Migration ID, 21-24 bytes store the Destination DC location, the 25th byte stores the Clear Flag, and the 26th byte stores the The AS number of the second CGR, and the remaining bytes store the VPN Name.

For example, if the Clear Flag indicated by the 25th byte is 1, the first PE 12 starts the timer set in the VPN routing forwarding table of the first PE 12, and after the specified time arrives, the first PE is revoked and A CGR 11 connection.

502. After receiving the BGP Update packet, the first PE 12 is configured according to BGP Update. The parameter indicating the location of the data center where the second CGR is located in the packet finds the second PE 13 connected to the second CGR 14, and sends the control packet of the MPLS VPN site migration to the second PE 13.

For example, the process of the first PE 12 to find the second PE 13 may include: after the first PE 12 identifies that the packet is a BGP Update packet, according to the BGP

The above parameters in the path attribute of the Update message internally generate a query request. Then, the first PE 12 queries the IP address of the second PE 13 and the lower interface name of the second PE 13 by using the information in the above table 1 in the network database according to the parameter indicating the Destination DC location of the second CGR 14. .

Optionally, the first PE 12 may further query, according to the VPN Name, the RD/RT and the VPN peer on the first PE 12.

The first PE 12 constructs a control packet sent to the second PE 13. The information of the control packet may include: a Migration ID indicating the current cloud computing virtual machine migration process and status, a lower connection port name of the second PE 13, The current VPN Name, the RD/RT on the first PE 12, the VPN peer on the first PE 12, and the AS Number indicating the second CGR 14.

503. The second PE 13 receives the control packet, and determines, by using the RD/RT on the first PE 12 carried in the control packet, whether the second PE 13 configures a VPN routing forwarding table of the MPLS VPN site. If the second PE 13 does not configure the VPN routing forwarding table of the MPLS VPN site, go to 504; if the second PE 13 has configured the VPN routing forwarding table of the MPLS VPN site, go to 506.

504. The second PE 13 creates a VPN routing forwarding table.

The second PE 13 applies for a site network segment to the network database connected to the second PE 13 according to the VPN Name in the control packet, and then takes two addresses from the network segment of the site, such as the PE shown in Table 2. IP Downside and VCE IP Upside, configure the PE IP Downside to the lower interface of the second PE, and write the PE IP Downside and the VCE IP Upside into the message indicating the MPLS VPN site migration of the second PE 13 to The second CGR is used to perform the related configuration of the VCE 141 when receiving the message; and the sub-interface number of the second PE 13 and the used Vlan ID are also obtained.

The second PE 13 constructs a message indicating the migration of the MPLS VPN site, and may include the following parameters: a Migration ID indicating the current cloud computing virtual machine migration process and status, and Vlan The ID, the Transit IP section applied by the second PE 13 to the network database, the AS Number of the domain in which the second PE 13 is located, and the message is sent to the second CGR 14 connected to the second PE 13. The information of the Transit IP section includes the above PE IP Downside and VCE IP Upside.

Then, the second PE 13 configures the VPN routing forwarding table instance and binds to the sub-interface of the lower interface, and configures the BGP protocol.

505. The second CGR 14 receives the message indicating the MPLS VPN site migration sent by the second PE 13, creates a VCE 141, configures the BGP protocol, and migrates the MPLS VPN site of the data center where the first CGR 11 corresponding to the Migration ID is located. Enter the VCE 141.

506. The second PE 13 obtains the Vlan ID of the interface to which the VPN routing forwarding table is bound according to the VPN routing forwarding table, and constructs a message indicating the migration of the MPLS VPN site, which may include the following parameters: indicating the cloud computing virtual machine migration process. And the status of the Migration ID, Vlan ID; but the message does not include the Transit IP Section that the second PE 13 applies to the network database and the AS Number of the domain where the second PE 13 is located. Further, the second PE 13 sends a message indicating the migration of the MPLS VPN site to the second CGR 14 connected to the second PE 13.

507. After receiving the foregoing message indicating the MPLS VPN site migration sent by the second PE 13, the second CGR 14 obtains the local VCE 141 according to the Migration ID and the Vlan ID, and the MPLS of the data center where the first CGR 11 corresponding to the Migration ID is located. The VPN site moves into VCE 141.

The method for migrating a cloud computing virtual machine provided by the embodiment of the present invention, the first CGR sends a packet migrated by the MPLS VPN site to the first PE, and then the control packet sent by the first PE to the second PE and the second PE are sent to the second The message sent by the CGR carries the parameters indicating the migration of the MPLS VPN site, so that the PE of the network operator can provide the dynamic migration service of the MPLS VPN site to the data center of the cloud service provider, and since the network side PE participates in the migration process, After the migration is complete, traffic to the virtual machine can go directly to the migrated data center. It is not necessary for the network side to configure the VPN through the management plane, which can improve the efficiency of the VPN operation. During the entire migration process, the network side and the cloud service provider did not send their own device configuration information to each other, which ensured the security of the business information of the two types of operators. It should be noted that, in this embodiment, the MPLS Update packet is configured as the BGP Update packet, and the parameter indicating the MPLS VPN site migration is encapsulated in the path attribute of the BGP Update packet, but The present invention is not limited thereto, and may be other messages, and may also encapsulate information indicating parameters of the MPLS VPN site migration in other attributes.

In this embodiment, all the virtual machine resources in a subnet in the data center where the first CGR is located need to be migrated to the data center where the second CGR is located, but the embodiment is not limited thereto, and may be the second CGR. All the virtual machine resources in a subnet in the data center need to be migrated to the data center where the first CGR is located. That is, the first CGR can perform all actions of the second CGR, and the second CGR can also perform all actions of the first CGR. The first PE may perform all actions of the second PE, and the second PE may also perform all actions of the first PE.

The first cloud data center egress gateway router (CGR) 60 provided by the embodiment of the present invention can be applied to the foregoing method embodiment, and all operations of the first CGR 11 in the foregoing method embodiment can be performed. For details, refer to the foregoing embodiment. I will not repeat them here.

As shown in FIG. 8, the first CGR 60 provided by the embodiment of the present invention includes: a generating unit 601, configured to construct an MPLS VPN site migration document; and the parameter includes a parameter indicating a location of a data center where the second CGR is located.

The sending unit 602 is configured to send, to the first PE, the packet that is migrated by the MPLS VPN site configured by the generating unit 601, so that the first PE, after receiving the packet migrated by the MPLS VPN site, migrates according to the MPLS VPN site. The parameter indicating the location of the data center where the second CGR is located in the packet finds the second PE connected to the second CGR, and sends a control packet indicating the migration of the MPLS VPN site to the second PE. After receiving the control text, the second PE receives the control packet. And sending a message indicating that the MPLS VPN site is migrated to the second CGR, so that the MPLS VPN site moves to the data center where the second CGR is located.

The first CGR provided by the embodiment of the present invention sends an MPLS VPN site-migrated packet to the first PE, and then the control packet sent by the first PE to the second PE and the second PE sends a message to the second CGR. The MPL S VPN site migration parameters enable the network operator's PE to provide the MPLS VPN site dynamic migration service for the cloud service provider's data center, and since the network-side PE participates in the migration process, after the migration is completed, the migration to the The virtual machine's traffic can go directly to the migrated data center. No network required The configuration of the VPN through the management plane can improve the efficiency of VPN operations.

The first carrier edge router PE 70 provided by the embodiment of the present invention can be applied to the foregoing method embodiments, and all the operations of the first PE 12 in the foregoing method embodiment can be performed. For details, refer to the foregoing embodiment, and Narration.

As shown in FIG. 9, the first PE 70 provided by the embodiment of the present invention includes:

The receiving unit 701 is configured to receive the MPLS VPN site migration packet sent by the first CGR, and the MPLS VPN site migration packet; the MPLS VPN site migration packet includes the following parameters:

Current virtual private network name; and

Indicate the location of the data center where the second CGR is located; and

Instructing to revoke a clear flag associated with the first CGR; and

Indicates the autonomous system number of the second CGR;

The processing unit 702 finds the second PE connected to the second CGR according to the parameter indicating the location of the data center where the second CGR is located, and provides the information to the generating unit 703.

The generating unit 703 is configured to construct a control packet indicating the migration of the MPLS VPN site. The sending unit 704 is configured to send the control packet configured by the generating unit 703 to the second PE, so that after receiving the control packet, the second PE sends a message indicating the migration of the MPLS VPN site to the second CGR, so as to perform The MPLS VPN site in the data center where the first CGR is located is moved to the data center where the second CGR is located.

Optionally, as shown in FIG. 10, the receiving unit 701 in the first PE 70 further includes:

The BGP module 7001 is configured to: after receiving the packet of the MPLS VPN site that is sent by the first CGR, the receiving unit 701 identifies the packet as a BGP Update packet, and preprocesses the BGP Update packet and sends the packet to the migration module 7002. .

The processing unit 702 in the first PE 70 further includes:

After receiving the pre-processed BGP Update message sent by the BGP module 7001, the migration module 7002 sends a query request to the query module 7003, and receives the query result returned by the query module 7003.

The query module 7003, according to the query request sent by the migration module 7002, in the database The second PE connected to the second CGR is found according to the parameter indicating the location of the data center where the second CGR is located, and the query result is sent to the migration module 7002.

The first PE provided by the embodiment of the present invention receives the packet migrated by the MPLS VPN site sent by the first CGR, and then the control packet sent by the first PE to the second PE and the message sent by the second PE to the second CGR are both Carrying the parameters indicating the migration of the MPLS VPN site, so that the PE of the network operator can provide the dynamic migration service of the MPLS VPN site to the data center of the cloud service provider, and since the network side PE participates in the migration process, after the migration is completed, the migration is completed. The virtual machine's traffic can go directly to the migrated data center. It is not necessary to configure the VPN through the management plane on the network side, which can improve the efficiency of VPN operations.

The second carrier edge router PE 80 provided by the embodiment of the present invention can be applied to the foregoing method embodiment, and all operations of the second PE 13 in the foregoing method embodiment can be performed. For details, refer to the foregoing embodiment, where Narration.

As shown in FIG. 11, the second PE 80 provided by the embodiment of the present invention includes:

The receiving unit 801 is configured to receive, by the first PE, a control packet that is sent by the MPLS VPN station, where the first PE receives the MPLS VPN site migration message sent by the first CGR, where The packet migrated by the MPLS VPN site includes a parameter indicating a location of the data center where the second CGR is located. The control packet includes the following parameters:

The name of the lower port of the second PE; and

Current virtual private network name; and

a route specifier/route target on the first PE; and

a virtual private network peer address list on the first PE; and

Indicates the autonomous system number of the second CGR.

The generating unit 802 is configured to construct a message indicating the migration of the MPLS VPN site.

The sending unit 803 is configured to send, to the second CGR, a message indicating that the MPLS VPN site is migrated by the generating unit 802, so that the MPLS VPN site of the data center where the first CGR is located is moved to the data center where the second CGR is located.

Optionally, as shown in FIG. 12, the generating unit 802 in the second PE 80 further includes: The determining module 8001 is configured to determine whether the second PE is configured with a VPN routing forwarding table of the MPLS VPN site to be migrated.

The configuration module 8002 is configured to: when the determining module 8001 determines that the second PE does not configure the VPN routing forwarding table of the MPLS VPN site to be migrated, the receiving unit 801 receives the indication that the first PE sends the MPLS VPN site migration. After the control packet is configured, the VPN routing forwarding table of the MPLS VPN site to be migrated is created, and the VPN routing forwarding table instance is configured, and is bound to the sub-interface of the lower interface to configure the BGP protocol.

At this time, the sending unit 803 is further configured to send, to the second CGR, configuration parameters of the VPN routing forwarding table of the MPLS VPN site to be migrated created by the configuration module 8002.

The second PE provided by the embodiment of the present invention receives the control packet indicating the MPLS VPN site migration sent by the first PE, and then the second PE sends a message indicating the migration of the MPLS VPN site to the second CGR, so that the network operator's PE is obtained. The dynamic migration service of the MPLS VPN site can be provided for the data center of the cloud service provider, and since the network side PE participates in the migration process, after the migration is completed, the traffic to the virtual machine can directly reach the migrated data center. It is not necessary for the network side to configure the VPN through the management plane, which can improve the efficiency of the VPN operation. During the entire migration process, the network side and the cloud service provider did not send their own device configuration information to each other, which ensured the security of the business information of the two types of operators.

The second cloud data center egress gateway router CGR 90 provided by the embodiment of the present invention can be applied to the foregoing method embodiment, and all operations of the second CGR 14 in the foregoing method embodiment can be performed. For details, refer to the foregoing embodiment, where No longer.

As shown in FIG. 13, the second CGR 90 provided by the embodiment of the present invention includes: a receiving unit 901, configured to receive, by the second PE, a message indicating that the MPLS VPN site is migrated; where the message is received by the second PE. After the PE sends a control packet indicating the MPLS VPN site migration, the first PE receives the MPLS VPN site migration packet sent by the first CGR, and then sends a control packet indicating the MPLS VPN site migration to the second PE.

The processing unit 902 is configured to perform the migration of the MPLS VPN site of the data center where the first CGR is located according to the message that is sent by the second PE that is received by the receiving unit 901 to indicate the migration of the MPLS VPN site. Optionally, as shown in FIG. 14, the processing unit 902 in the second CGR 90 further includes:

The determining module 9001 is configured to determine whether the second PE connected to the second CGR 90 is configured with a VPN routing forwarding table of the MPLS VPN site to be migrated.

The configuration module 9002 is configured to: when the determining module 9001 determines that the second PE does not configure the VPN routing forwarding table of the MPLS VPN site to be migrated, the receiving unit 901 receives the indication that the second PE sends the MPLS VPN site migration. After the message is created, the VCE 141 is created and the BGP protocol is configured; in order to perform the migration of the MPLS VPN site in the data center where the first CGR is located.

The second CGR provided by the embodiment of the present invention receives the message indicating the MPLS VPN site migration sent by the second PE, so that the network operator can provide the cloud service provider with the dynamic migration service of the MPLS VPN site. And because the network side participates in the migration process, after the migration is completed, the traffic destined for the virtual machine can directly reach the new data center, and the network side is not required to configure the VPN through the management plane, which can improve the efficiency of the VPN operation; During the entire migration process, the network side and the cloud service provider did not send their own device configuration information to each other, which ensured the security of the business information of the two types of operators.

The cloud migration virtual machine migration network mentioned in the embodiment of the present invention, as shown in FIG. 15, includes:

The first CGR 60, the first PE 70, the second PE 80, and the second CGR 90 are provided in the above device embodiments.

The structures of the first CGR 60, the first PE 70, the second PE 80, and the second CGR 90 have been described in the foregoing embodiments, and are not described herein again.

The first CGR 60, the first PE 70, the second PE 80, and the second CGR 90 may be applied to the foregoing method embodiment, and the first CGR 11, the first PE 12, and the first For details of the operations of the second PE 13 and the second CGR 14, please refer to the above embodiments, and details are not described herein again.

The network that the cloud computing virtual machine migrates in the embodiment of the present invention, the first C GR sends the MPLS VPN site migration message to the first PE, and then the control packet sent by the first PE to the second PE and the second PE The message sent by the CGR carries the parameters indicating the migration of the MPLS VPN site, so that the PE of the network operator can be the cloud service provider. The data center provides the dynamic migration service of the MPLS VPN site, and since the network-side PE participates in the migration process, after the migration is completed, the traffic to the virtual machine can directly reach the migrated data center. It is not necessary for the network side to configure the VPN through the management plane, which can improve the efficiency of the VPN operation. During the entire migration process, the network side and the cloud service provider did not send their own device configuration information to each other, which ensured the security of the business information of the two types of operators.

The above is only a specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the appended claims.

Claims

Rights request

1. A method for migrating cloud computing virtual machines, characterized by comprising: the first cloud data center egress gateway router CGR constructs a multi-protocol label switching virtual private network MPLS VPN site migration message; the MPLS VPN site migration message The message contains parameters indicating the location of the data center where the egress gateway CGR of the second cloud data center is located;

The first CGR sends the MPLS VPN site migration message to the first operator edge router PE; so that after receiving the MPLS VPN site migration message, the first PE performs the first migration according to the instruction. Find the second PE connected to the second CGR based on the location parameters of the data center where the second CGR is located, and send a control message indicating MPLS VPN site migration to the second PE; the second PE receives the control message After receiving the message, a message instructing migration of the MPLS VPN site is sent to the second CGR so that the MPLS VPN site can be migrated to the data center where the second CGR is located.

2. The method according to claim 1, characterized in that the MPLS VPN site migration message also includes the following parameters:

Migration ID indicating the migration process and status of this cloud computing virtual machine; and

Current VPN name; and

a clear flag indicating withdrawal of the connection with said first PE; and

Indicates the autonomous system number of the second CGR.

3. The method according to claim 2, characterized in that the parameters in the MPLS VPN site migration message are encapsulated in the path attribute of the Border Gateway Protocol update message, and the format is:

The first byte 0x90 is fixed, the second byte indicates the type of attribute of the parameter, the third and fourth bytes indicate the length of bytes occupied by the parameter, and the fifth to 20th bytes store the migration ID. , the 21st to 24th bytes store the location indicating the data center where the second CGR is located, the 25th byte stores the clear flag, the 26th and 27th bytes store the autonomous system number of the second CGR, and the rest Bytes store the current VPN name.

4. A method for migrating cloud computing virtual machines, characterized by including: the first operator edge router PE receiving the first cloud data center egress gateway router Multi-protocol label switching virtual private network MPLS VPN site migration document sent by CGR;

The first PE finds the second operator edge router PE connected to the second CGR based on the parameter indicating the location of the data center where the second CGR is located in the MPLS VPN site migration message;

The first PE constructs a control message instructing the MPLS VPN site migration, and sends the control message to the second PE; so that after receiving the control message, the second PE Send a message instructing the migration of the MPLS VPN site to the second CGR, so that the MPLS VPN site in the data center where the first CGR is located can migrate to the data center where the second CGR is located;

The MPLS VPN site migration message includes the following parameters: a migration ID indicating the migration process and status of the cloud computing virtual machine; and

Current VPN name; and

Indicates the location of the data center where the second CGR is located; and

a clear flag indicating withdrawal of the connection with said first CGR; and

Indicates the autonomous system number of the second CGR.

5. The method according to claim 4, further comprising: if the clear flag in the received MPLS VPN site migration message indicates that the connection with the first CGR is revoked, initiating the A timer is set in the VPN routing table of the first PE. When the timer expires, the first PE cancels the connection with the first CGR.

6. The method according to claim 4, characterized in that, the first PE finding the second PE connected to the second CGR based on the parameter indicating the location of the data center where the second CGR is located includes:

The first PE queries to obtain the IP address of the second PE and the name of the downstream port of the second PE based on the parameter indicating the location of the data center where the second CGR is located.

7. The method according to claim 6, characterized in that the control message instructing migration of the MPLS VPN site includes the following parameters:

The name of the downstream port of the second PE; and

Current VPN name; and

The route discriminator/route target of the first PE; and The virtual private network peer address list of the first PE; and

Indicates the autonomous system number of the second CGR;

Wherein, the route discriminator/route target of the first PE and the virtual private network peer address list of the first PE are obtained based on the current virtual private network name.

8. A method for migrating a cloud computing virtual machine, characterized by including: the second operator edge router PE receiving a control message sent by the first PE indicating multi-protocol label switching virtual private network MPLS VPN site migration; wherein , the control message is generated after the first PE receives the MPLS VPN site migration message sent by the first cloud data center egress gateway router CGR, and the MPLS VPN site migration message contains instructions for the second C Parameters of the location of the data center where GR is located;

The second PE constructs a message instructing the migration of the MPLS VPN site and sends it to the second CGR so that the MPLS VPN site in the data center where the first CGR is located moves to the data center where the second CGR is located. move in;

Wherein, the control message includes the following parameters:

The name of the downstream port of the second PE; and

Current VPN name; and

the route discriminator/route target on the first PE; and

A list of virtual private network peer addresses on the first PE; and

Indicates the autonomous system number of the second CGR.

9. The method according to claim 8, characterized in that, after the second PE receives the control message, it further includes:

If it is determined that the second PE is not configured with the VPN routing and forwarding table of the MPLS VPN site based on the route distinguisher/route target on the first PE, create a VPN routing and forwarding table;

Apply for a site network segment from the network database connected to the second PE according to the virtual private network name, and obtain the sub-interface number of the downstream port of the second PE and the virtual LAN ID used.

10. The method according to claim 9, characterized in that the message indicating the migration of the MPLS VPN site includes the following parameters:

Virtual office or network ID; and The transit IP address segment applied by the second PE to the network database; wherein, the transit IP address segment is obtained from the site network segment; and

The autonomous system number of the domain where the second PE is located.

11. The method according to claim 10, wherein after sending the message indicating the MPLS VPN site migration to the second CGR, the method further includes:

Configure a VPN routing forwarding table instance, bind it to the sub-interface of the downstream port of the second PE, and configure a border gateway protocol.

12. The method according to claim 8, characterized in that, after the second PE receives the control message, it further includes:

If it is determined based on the route distinguisher/routing target that the second PE has been configured with the VPN routing and forwarding table of the MPLS VPN site, then the interface bound to the VPN routing and forwarding table is obtained based on the VPN routing and forwarding table. The virtual LAN ID.

13. The method according to claim 12, wherein the message indicating migration of the MPLS VPN site includes the following parameters:

Virtual LAN ID; does not include the transit IP address segment applied by the second PE to the network database and the autonomous system number of the domain where the second PE is located.

14. A method for migrating a cloud computing virtual machine, characterized by comprising: the second cloud data center egress gateway router CGR receiving an instruction sent by the second operator edge router PE to migrate the multi-protocol label switching virtual private network MPLS VPN site message; wherein the message is generated after the second PE receives a control message sent by the first PE indicating the migration of the MPLS VPN site; the first PE receives the MPLS VPN site migration message sent by the first CGR. After sending the control message indicating migration of the MPLS VPN site to the second PE;

The second cloud data center egress gateway router CGR moves in the MPLS VPN site of the data center where the first CGR is located.

15. The method according to claim 14, wherein the second CGR's migration of the MPLS VPN site in the data center where the first CGR is located includes:

When the second CGR receives the message sent by the second PE, the following parameters are included:

The migration ID indicating the migration process and status of this cloud computing virtual machine; and Virtual office or network ID; and

The transit IP address segment applied by the second PE to the network database; and

The autonomous system number of the domain where the second PE is located;

Create a virtual customer edge router VCE; configure the border gateway protocol;

And migrate the MPLS VPN site in the data center where the first CGR corresponding to the migration ID is located into the VCE.

16. The method according to claim 14, wherein the second CGR's migration of the MPLS VPN site in the data center where the first CGR is located includes:

Virtual LAN ID; but does not include the transit IP address segment applied by the second PE to the network database and the autonomous system number of the domain where the second PE is located;

Obtain the local VCE according to the migration ID and the virtual LAN ID;

And migrate the MPLS VPN site in the data center where the first CGR corresponding to the migration ID is located to the local VCE.

17. A first cloud data center egress gateway router CGR, which is characterized by including:

A generation unit configured to construct a multi-protocol label switching virtual private network MPLS VPN site migration message; the message contains parameters indicating the location of the data center where the second CGR is located;

A sending unit, configured to send the MPLS VPN site migration message constructed by the generating unit to the first operator edge router PE; so that the first PE will receive the MPLS VPN site migration message after receiving the MPLS VPN site migration message. , find the second PE connected to the second CGR according to the parameter indicating the location of the data center where the second CGR is located in the MPLS VPN site migration message, and send the MPLS indication to the second PE A control message for VPN site migration; after receiving the control message, the second PE sends a message instructing the migration of the MPLS VPN site to the second CGR so that the MPLS VPN site can migrate to the third CGR. The data center where the second CGR is located is moved in.

18. A first operator edge router PE, characterized in that it includes: a receiving unit, configured to receive the CGR sent by the first cloud data center egress gateway router The multi-protocol label switching virtual private network MPLS VPN site migration message; The MPLS VPN site migration message includes the following parameters:

Current VPN name; and

Indicates the location of the data center where the second CGR is located; and

a clear flag indicating withdrawal of the connection with said first CGR; and

Indicates the autonomous system number of the second CGR;

A processing unit configured to find the second operator edge router PE connected to the second CGR according to the parameter indicating the location of the data center where the second CGR is located;

A generating unit, configured to construct a control message indicating migration of the MPLS VPN site; A sending unit, configured to send the control message constructed by the generating unit to the second operator edge router PE; so that the first After receiving the control message, the second PE sends a message instructing the migration of the MPLS VPN site to the second CGR, so that the MPLS VPN site in the data center where the first CGR is located moves to the second CGR. The data center where CGR is located is moved in.

19. The first operator edge router PE according to claim 18, characterized in that,

The receiving unit includes: a BGP module, configured to, after the receiving unit receives the MPLS VPN site migration message sent by the first CGR, identify the message as a BGP Update message, and convert the BGP The Update message is pre-processed and sent to the migration module;

The processing unit includes: a migration module, which sends a query request to the query module after receiving the preprocessed BGP Update message sent by the BGP module; receives the query result returned by the query module; the query module, according to In the query request issued by the migration module, in the database, the second PE connected to the second CGR is found according to the parameter indicating the location of the data center where the second CGR is located, and the query result is sent to the migration module.

20. A second operator edge router PE, characterized in that it includes: a receiving unit, configured to receive a control message sent by the first operator edge router PE indicating multi-protocol label switching virtual private network MPLS VPN site migration; Wherein, the control message is generated after the first PE receives the MPLS VPN site migration message sent by the first cloud data center egress gateway router CGR, and the MPLS The VPN site migration message contains parameters indicating the location of the data center where the second CGR is located; the control message contains the following parameters:

The name of the downstream port of the second PE; and

Current VPN name; and

the route discriminator/route target on the first PE; and

A list of virtual private network peer addresses on the first PE; and

Indicates the autonomous system number of the second CGR.

A generating unit, configured to construct a message indicating the migration of the MPLS VPN site; A sending unit, configured to send the message indicating the migration of the MPLS VPN site constructed by the generating unit to the second CGR; in order to carry out the process where the first CGR is located The MPLS VPN site in the data center moves to the data center where the second CGR is located.

21. The second operator edge router PE according to claim 20, characterized in that,

The generating unit includes:

A judgment module, used to judge whether the second PE is configured with the VPN routing forwarding table of the MPLS VPN site to be migrated;

A configuration module configured to: when the judgment module determines that the second PE does not configure the VPN routing and forwarding table of the MPLS VPN site to be migrated, when the receiving unit receives the instruction sent by the first PE After receiving the control packet for the MPL S VPN site migration, create a VPN routing and forwarding table for the MPLS VPN site to be migrated, configure a VPN routing and forwarding table instance, bind it to the sub-interface of the downstream port, and configure the border gateway protocol .

The sending unit is also configured to send the configuration parameters of the VPN routing and forwarding table created by the configuration module to the second CGR; so that the MPLS VPN site in the data center where the first CGR is located sends a message to the second CGR. data center moved into.

22. A second cloud data center egress gateway router CGR, characterized by including:

The receiving unit is configured to receive a message sent by the second operator edge router PE indicating the migration of the multi-protocol label switching virtual private network MPLS VPN site; wherein, the message is that the second PE receives the message sent by the first PE indicating the MPLS Generated after VPN site migration control message; the first PE receives the MPLS sent by the first CGR After the VPN site migration message is sent to the second PE, a control message indicating the MPLS VPN site migration is sent;

A processing unit, configured to migrate the MPLS VPN site in the data center where the first CGR is located based on the message received by the receiving unit indicating migration of the MPLS VPN site.

23. The second cloud data center egress gateway router CGR according to claim 22, characterized in that,

The processing unit includes:

A judgment module, configured to judge whether the second PE connected to the second CGR is configured with the VPN routing forwarding table of the MPLS VPN site to be migrated;

Configuration module, used when the judgment module determines that the second PE does not configure the VPN routing and forwarding table of the MPLS VPN site to be migrated, when the receiving unit receives the instruction sent by the second PE. After receiving the MPLS VPN site migration message, create a virtual customer edge router VCE, and configure a border gateway protocol; in order to migrate the MPLS VPN site in the data center where the first CGR is located.

24. A network for cloud computing virtual machine migration, characterized in that it includes: the first cloud data center egress gateway router CGR described in claim 17;

The first operator edge router PE according to either claim 18 or 19;

The second operator edge router PE according to either claim 20 or 21;

And the second cloud data center egress gateway router CGR described in either claim 22 or 23.