Method and system for realizing IPv6 public network communication of cloud center

Abstract

The invention relates to the technical field of computer network communication, in particular to a method and system for achieving cloud center IPv6 public network communication, and the method comprises the following steps: deploying a cloud center network in a container cluster, managing each service component of a cloud center through a container, initializing a cloud center controller and an IPv6 gateway transponder, wherein the IPv6 gateway transponder is used as an IPv6 router of the cloud center and bears an IPv6 gateway port and an IPv6 forwarding route; the method and the system for realizing the IPv6 public network communication of the cloud center have the beneficial effects that the aim of accessing the public network by the IPv6 of the cloud center is fulfilled by integrating an IS-IS routing protocol. Through container nano-management center equipment, a starting cloud center controller, an IPv6 gateway transponder, a control core switch, nano-management computing nodes and the like, the IPv6 gateway transponder serves as a router of an IPv6 network, routing exchange is carried out between the IPv6 gateway transponder and the core switch through an integrated IS-IS routing protocol, the method is suitable for a large-scale network environment, the networking architecture is simplified, and the purpose that the IPv6 network accesses a public network is achieved.

Description

Technical Field

[0001] The present invention relates to the field of computer network communication technology, and specifically to a method and system for realizing cloud center IPv6 public network communication. Background Art

[0002] With the rapid development of the Internet, IPv6 (Internet Protocol version 6), as the next generation Internet protocol, has gradually become the mainstream trend of global Internet development due to its huge address space, enhanced security and improved service quality. However, in the cloud computing environment, how to efficiently and securely implement IPv6 public network communication is still a challenging technical problem.

[0003] Traditional cloud center network deployment methods often rely on physical network devices, such as routers and switches, which have certain limitations in scalability, flexibility, and cost. In order to overcome these limitations, network deployment solutions based on container clusters have gradually emerged in recent years. Container clusters use virtualization technology to encapsulate multiple container instances into an independent virtual environment, achieving efficient resource utilization and rapid deployment of services. Summary of the invention

[0004] The purpose of the present invention is to provide a method and system for realizing IPv6 public network communication in a cloud center, so as to solve the problems raised in the above-mentioned background technology.

[0005] To achieve the above object, the present invention provides the following technical solution: a method for realizing IPv6 public network communication of a cloud center, the method comprising the following steps:

[0006] Deploy the cloud center network in the container cluster, manage the various service components of the cloud center through containers, initialize the cloud center controller and IPv6 gateway forwarder, where the IPv6 gateway forwarder serves as the IPv6 router of the cloud center, carries the IPv6 gateway port and IPv6 forwarding route, and connects to the core switch through physical lines, establishes IS-IS neighbor relationship, synchronizes link state database routing information, and updates the routing table to guide routing forwarding.

[0007] Preferably, the cloud center controller is responsible for allocating physical networks to IPv6 gateway forwarders and core switches, controlling them to start the integrated IS-IS routing protocol, configuring the system ID, establishing point-to-point P2P neighbor relationships, and providing the function of configuring IPv6 networks, subnets and gateway information, and sending network information to the IPv6 gateway forwarder through Https requests, so that it updates the local link state database table and sends link state data packets LSP to synchronize routing information to the core switch.

[0008] Preferably, the IPv6 gateway forwarder is started and created by the container, with built-in Agent service, quagga plug-in and RADVD routing announcement plug-in, which is used to carry IPv6 gateway and forward routing information, establish a P2P neighbor relationship with the core switch to complete routing information synchronization, and notify RA messages to the cloud server in the domain so that the cloud server can learn the network segment routing.

[0009] Preferably, the Agent service built into the IPv6 gateway forwarder is used to receive Https requests from the cloud center controller, establish an IPv6 gateway interface based on the request and send down IPv6 network segment routes, modify the IS-IS configuration to update the link state database information, and update the RADVD configuration file and periodically send the network segment routes to the cloud server in the domain.

[0010] Preferably, the function of the RADVD routing announcement plug-in of the IPv6 gateway forwarder is to periodically announce RA messages carrying network prefix information to the cloud servers in the domain, assist the cloud servers in learning stateless addresses and network segment routes, and after RADVD is started, it manages the relationship between the gateway interface and the network prefix by receiving the configuration modification of the Agent service, and controls the sending of network information in the RA message.

[0011] A cloud center IPv6 public network communication system, the system comprising:

[0012] The cloud center controller is used for user control and IPv6 communication functions. It is responsible for allocating physical networks for IPv6 gateway forwarders and core switches, controlling the two to start the integrated IS-IS routing protocol, configuring system IDs, establishing point-to-point neighbor relationships, and providing an interface for configuring IPv6 networks, subnets, and gateway information.

[0013] The IPv6 gateway forwarder is started and created by the container. It serves as the IPv6 router of the cloud center, carries the IPv6 gateway port and IPv6 forwarding route, connects to the core switch through a physical line and establishes an IS-IS neighbor relationship, synchronizes the link state database routing information, and guides routing forwarding;

[0014] The core switch establishes a P2P neighbor relationship with the IPv6 gateway forwarder, receives the link state data packet LSP sent by the IPv6 gateway forwarder, parses and updates the local routing table to support outbound access of the intranet cloud server.

[0015] Preferably, the cloud center controller also includes:

[0016] Https request interface, used to receive IPv6 network configuration information input by the user and send the information to the IPv6 gateway forwarder;

[0017] The system configuration module is used to allocate physical network resources to the IPv6 gateway forwarder and core switch, and control the startup and configuration of the two.

[0018] Preferably, the IPv6 gateway forwarder also includes:

[0019] Agent service, used to receive Https requests from the cloud center controller, establish an IPv6 gateway interface and issue IPv6 network segment routes according to the request, modify IS-IS configuration, update link state database information, and control RADVD routing announcement plug-in;

[0020] The quagga plug-in is used to start the integrated IS-IS routing protocol, establish a P2P neighbor relationship with the core switch, and generate and send LSP packets;

[0021] The RADVD routing announcement plug-in is used to periodically announce RA messages to the cloud servers in the domain. The messages carry network prefix information to assist the cloud servers in learning stateless addresses and network segment routes.

[0022] Preferably, the system also includes: a container cluster management module, which is used to deploy and manage the cloud center controller and IPv6 gateway forwarder in the container cluster to achieve the management and expansion of the cloud center service.

[0023] Preferably, the system also includes: a security isolation mechanism for achieving security isolation between containers and between containers and host machines to ensure the safe and stable operation of the communication system.

[0024] Compared with the prior art, the present invention has the following beneficial effects:

[0025] The method and system for realizing IPv6 public network communication of the cloud center proposed in the present invention realize the purpose of cloud center IPv6 accessing the public network by integrating IS-IS routing protocol. Through the container management center equipment, the cloud center controller and IPv6 gateway forwarder are started, the core switch is controlled, and the computing nodes are managed. The IPv6 gateway forwarder acts as a router of the IPv6 network and performs routing exchange with the core switch through the integrated IS-IS routing protocol. It is suitable for large-scale network environment, simplifies the networking architecture, and realizes the purpose of IPv6 network accessing the public network. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 This is the IPv6 network architecture diagram of the cloud center of the present invention;

[0027] Figure 2 A process diagram for establishing an IS-IS neighbor relationship of the present invention;

[0028] Figure 3 This is a flow chart of cross-segment IPv6 mutual access within the cloud center of the present invention;

[0029] Figure 4 This is the flow chart of the cloud center IPv6 accessing the external network of the present invention. DETAILED DESCRIPTION

[0030] In order to make the purpose and technical solution of the present invention clearly and completely described, and the advantages more clearly understood, the embodiments of the present invention are further described in detail with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are part of the embodiments of the present invention, rather than all of the embodiments, and are only used to explain the embodiments of the present invention, and are not used to limit the embodiments of the present invention. All other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0031] Embodiment 1, the present invention provides a technical solution: a method for realizing IPv6 public network communication of a cloud center, the method comprising the following steps:

[0032] Deploy the cloud center network in the container cluster, manage the various service components of the cloud center through containers, initialize the cloud center controller and IPv6 gateway forwarder, where the IPv6 gateway forwarder serves as the IPv6 router of the cloud center, carries the IPv6 gateway port and IPv6 forwarding route, and connects to the core switch through physical lines, establishes IS-IS neighbor relationship, synchronizes link state database routing information, and updates the routing table to guide routing forwarding.

[0033] The cloud center controller is responsible for allocating physical networks to IPv6 gateway forwarders and core switches, controlling them to start the integrated IS-IS routing protocol, configuring system IDs, establishing point-to-point P2P neighbor relationships, and providing the function of configuring IPv6 networks, subnets, and gateway information. It sends network information to the IPv6 gateway forwarder through Https requests, allowing it to update the local link state database table and send link state data packets LSP to synchronize routing information to the core switch.

[0034] The IPv6 gateway forwarder is started and created by the container, with built-in Agent service, quagga plug-in and RADVD routing announcement plug-in, which is used to carry IPv6 gateway and forward routing information, establish a P2P neighbor relationship with the core switch to complete routing information synchronization, and notify RA messages to the cloud server in the domain so that the cloud server can learn the network segment routing.

[0035] The built-in Agent service of the IPv6 gateway forwarder is used to receive Https requests from the cloud center controller, establish an IPv6 gateway interface based on the request and issue IPv6 network segment routes, modify the IS-IS configuration to update the link state database information, and update the RADVD configuration file and periodically send the network segment routes to the cloud servers in the domain.

[0036] The function of the RADVD routing announcement plug-in of the IPv6 gateway forwarder is to regularly notify the cloud servers in the domain of RA messages carrying network prefix information, assisting the cloud servers in learning stateless addresses and network segment routes. After RADVD is started, it manages the relationship between the gateway interface and the network prefix by receiving the configuration modification of the Agent service, and controls the sending of network information in the RA message.

[0037] Example 2, based on Example 1, please refer to Figures 1 to 4 , the present invention is further described in conjunction with the accompanying drawings and specific implementation methods.

[0038] Attached Figure 1 This is the IPv6 networking architecture diagram of the cloud center. The cloud center is deployed in a container cluster. The cloud center controller and IPv6 gateway forwarder are initialized through containers. The cloud center controller manages computing nodes, IPv6 gateway forwarders, and core switches to provide users with a unified operation interface.

[0039] The cloud center controller provides a page for configuring basic IPv6 configuration, including configuring the physical network, IS-IS interface of the core switch, and IS-IS neighbor system ID. The physical network in this solution uses a VLAN network, which is specified by the operation and maintenance personnel and configured through the cloud center controller. The cloud center controller notifies the core switch of the VLAN gateway information through NetConf, configures the VLAN, VLAN Interface, and VLAN Interface on the core switch to start the IS-IS configuration, and opens the VLAN on the uplink port. The cloud center controller creates the VLAN network and assigns an IPv6 address from the VLAN network to the IPv6 gateway forwarder, configures the default route for the IPv6 gateway forwarder to point to the core switch, calls the IPv6 gateway forwarder through Https to perform integrated IS-IS routing protocol configuration, specifies the interface where the VLAN is located as the interface established by IS-IS, specifies the IS-IS neighbor system ID, and the IPv6 gateway forwarder and the core switch establish a neighbor relationship through Hello messages and start link state database synchronization. The process is shown in the attached figure. Figure 2 .

[0040] The cloud center controller provides monitoring of IS-IS neighbor status information, which can ensure that users can view neighbor status in real time and locate the cause of abnormal traffic.

[0041] When a user creates an IPv6 network through the cloud center controller, the cloud center controller notifies the IPv6 network prefix / mask and gateway information to the IPv6 gateway forwarder through Https requests, and mounts the gateway interface to the IPv6 gateway forwarder. The IPv6 gateway forwarder configures the gateway interface and adds network segment routing. The Agent service configures IS-IS routing information through quagga and sends LSP data packets to the core switch to update the link state database information. The IPv6 gateway forwarder modifies the RADVD configuration file through the Agent service and starts to send RA packets to the cloud server in the domain at regular intervals so that the cloud server can obtain the network prefix information.

[0042] After the IPv6 network is ready, you can create a cloud server for communication. Figure 3 This is the cross-segment cloud server communication process within the cloud center. For cloud server information, refer to the attached Figure 1 , the specific steps are as follows:

[0043] (1) Cloud server 1 initiates a ping6 message to request cloud server 4. The cross-segment request does not match the segment route within the cloud server, so the default gateway route is used;

[0044] (2) After matching the default gateway route, the message is sent to the gateway 1 interface of the IPv6 gateway forwarder. Gateway 1 is the gateway port of the IPv6 network where cloud server 1 is located;

[0045] (3) Gateway 1 interface selects the network segment route in the IPv6 gateway forwarder and forwards the message to Gateway 2 interface where server 4 is located;

[0046] (4) After the gateway 2 interface receives the message, it becomes IPv6 communication between the same network segments, and the message is sent to cloud server 4;

[0047] (5) After receiving the message, cloud server 4 parses the message and encapsulates the return message to complete the communication.

[0048] Attached Figure 4 This is the process of cloud server accessing the external network. For cloud server information, please refer to the attached Figure 1 , the specific steps are as follows:

[0049] (1) Cloud server 1 initiates a ping6 message to request the Internet, but fails to match the network segment route and matches the default gateway route;

[0050] (2) After matching the default gateway route, the message is sent to the gateway 1 interface of the IPv6 gateway forwarder;

[0051] (3) Gateway 1 interface matches the message with the network segment route. If no match is found, the message is matched with the default gateway route and forwarded to the core switch.

[0052] (4) After receiving the message, the core switch first learns the source address and source MAC carried by the message, and forwards the message to the firewall according to the destination network segment. The firewall then sends the message to the Internet destination address;

[0053] (5) The Internet destination receives the message, parses it, and then encapsulates the return message in response to the request. At this point, the virtual machine completes the public network access process.

[0054] The above is the solution of this patent based on the integrated IS-IS routing protocol to enable the cloud center cloud server to access the public network through the IPv6 protocol.

[0055] Embodiment 3, based on embodiment 1, proposes a system for realizing cloud center IPv6 public network communication, the system comprising:

[0056] The cloud center controller is used for user control and implementation of IPv6 communication functions. It is responsible for allocating physical networks to IPv6 gateway forwarders and core switches, controlling the two to start the integrated IS-IS routing protocol, configuring the system ID, establishing point-to-point neighbor relationships, and providing an interface for configuring IPv6 networks, subnets, and gateway information; it also includes: an Https request interface for receiving IPv6 network configuration information input by users and sending the information to the IPv6 gateway forwarder; a system configuration module for allocating physical network resources to IPv6 gateway forwarders and core switches, and controlling the startup and configuration of the two.

[0057] The IPv6 gateway forwarder is started and created by the container. It serves as the IPv6 router of the cloud center, carries the IPv6 gateway port and IPv6 forwarding route, connects to the core switch through a physical line and establishes an IS-IS neighbor relationship, synchronizes the link state database routing information, and guides routing forwarding; it also includes: Agent agent service, which is used to receive Https requests from the cloud center controller, establish an IPv6 gateway interface and issue IPv6 network segment routes according to the request, modify the IS-IS configuration, update the link state database information, and control the RADVD routing announcement plug-in; quagga plug-in, which is used to start the integrated IS-IS routing protocol, establish a P2P neighbor relationship with the core switch, and generate and send LSP data packets;

[0058] The RADVD routing announcement plug-in is used to periodically announce RA messages to the cloud servers in the domain. The messages carry network prefix information to assist the cloud servers in learning stateless addresses and network segment routes.

[0059] The core switch establishes a P2P neighbor relationship with the IPv6 gateway forwarder, receives the link state data packet LSP sent by the IPv6 gateway forwarder, parses and updates the local routing table to support outbound access of the intranet cloud server.

[0060] The system also includes: a container cluster management module, which is used to deploy and manage the cloud center controller and IPv6 gateway forwarder in the container cluster to achieve the management and expansion of cloud center services; a security isolation mechanism, which is used to achieve security isolation between containers and between containers and host machines to ensure the safe and stable operation of the communication system.

[0061] Although embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the appended claims and their equivalents.

Claims

1. A method for realizing IPv6 public network communication in a cloud center, characterized in that: The method comprises the following steps: Deploy the cloud center network in the container cluster, manage the various service components of the cloud center through containers, initialize the cloud center controller and IPv6 gateway forwarder, where the IPv6 gateway forwarder serves as the IPv6 router of the cloud center, carries the IPv6 gateway port and IPv6 forwarding route, and connects to the core switch through physical lines, establishes IS-IS neighbor relationship, synchronizes link state database routing information, and updates the routing table to guide routing forwarding.

2. A method for realizing cloud center IPv6 public network communication according to claim 1, characterized in that: The cloud center controller is responsible for allocating physical networks to IPv6 gateway forwarders and core switches, controlling them to start the integrated IS-IS routing protocol, configuring system IDs, establishing point-to-point P2P neighbor relationships, and providing the function of configuring IPv6 networks, subnets, and gateway information. It sends network information to the IPv6 gateway forwarder through Https requests, allowing it to update the local link state database table and send link state data packets LSP to synchronize routing information to the core switch.

3. A method for realizing cloud center IPv6 public network communication according to claim 1, characterized in that: The IPv6 gateway forwarder is started and created by the container, with built-in Agent service, quagga plug-in and RADVD routing announcement plug-in, which is used to carry IPv6 gateway and forward routing information, establish a P2P neighbor relationship with the core switch to complete routing information synchronization, and notify RA messages to the cloud server in the domain so that the cloud server can learn the network segment routing.

4. A method for realizing cloud center IPv6 public network communication according to claim 3, characterized in that: The built-in Agent service of the IPv6 gateway forwarder is used to receive Https requests from the cloud center controller, establish an IPv6 gateway interface based on the request and issue IPv6 network segment routes, modify the IS-IS configuration to update the link state database information, and update the RADVD configuration file and periodically send the network segment routes to the cloud servers in the domain.

5. A method for realizing cloud center IPv6 public network communication according to claim 3, characterized in that: The function of the RADVD routing announcement plug-in of the IPv6 gateway forwarder is to regularly notify the cloud servers in the domain of RA messages carrying network prefix information, assisting the cloud servers in learning stateless addresses and network segment routes. After RADVD is started, it manages the relationship between the gateway interface and the network prefix by receiving the configuration modification of the Agent service, and controls the sending of network information in the RA message.

6. A cloud center IPv6 public network communication system for implementing the method for implementing cloud center IPv6 public network communication according to any one of claims 1 to 5, characterized in that: The system comprises: The cloud center controller is used for user control and IPv6 communication functions. It is responsible for allocating physical networks for IPv6 gateway forwarders and core switches, controlling the two to start the integrated IS-IS routing protocol, configuring system IDs, establishing point-to-point neighbor relationships, and providing an interface for configuring IPv6 networks, subnets, and gateway information. The IPv6 gateway forwarder is started and created by the container. It serves as the IPv6 router of the cloud center, carries the IPv6 gateway port and IPv6 forwarding route, connects to the core switch through a physical line and establishes an IS-IS neighbor relationship, synchronizes the link state database routing information, and guides routing forwarding; The core switch establishes a P2P neighbor relationship with the IPv6 gateway forwarder, receives the link state data packet LSP sent by the IPv6 gateway forwarder, parses and updates the local routing table to support outbound access of the intranet cloud server.

7. A cloud center IPv6 public network communication system according to claim 6, characterized in that: The cloud center controller also includes: Https request interface, used to receive IPv6 network configuration information input by the user and send the information to the IPv6 gateway forwarder; The system configuration module is used to allocate physical network resources to the IPv6 gateway forwarder and core switch, and control the startup and configuration of the two.

8. A cloud center IPv6 public network communication system according to claim 6, characterized in that: IPv6 gateway forwarders also include: Agent service, used to receive Https requests from the cloud center controller, establish an IPv6 gateway interface and issue IPv6 network segment routes according to the request, modify IS-IS configuration, update link state database information, and control RADVD routing announcement plug-in; The quagga plug-in is used to start the integrated IS-IS routing protocol, establish a P2P neighbor relationship with the core switch, and generate and send LSP packets; The RADVD routing announcement plug-in is used to periodically announce RA messages to the cloud servers in the domain. The messages carry network prefix information to assist the cloud servers in learning stateless addresses and network segment routes.

9. A cloud center IPv6 public network communication system according to claim 6, characterized in that: The system also includes: a container cluster management module, which is used to deploy and manage the cloud center controller and IPv6 gateway forwarder in the container cluster to achieve the management and expansion of cloud center services.

10. A cloud center IPv6 public network communication system according to claim 6, characterized in that: The system also includes: a secure isolation mechanism for achieving secure isolation between containers and between containers and host machines, ensuring the safe and stable operation of the communication system.

Images