Communication system

Abstract

The application provides a communication system, which comprises a primary and backup NC and a plurality of LCs, an NC container is run in each NC, the plurality of LCs comprise first type LCs, a vNC container is run in each first type LC, when the primary and backup NC containers in the primary and backup NCs both fail or an NC network where the primary and backup NCs are located fails, a vNC container is selected from the plurality of vNC containers as a new primary NC, and the new primary NC controls a DDC cluster; if any of the primary and backup NCs fails to recover after restarting, a new backup NC is added to the DDC cluster; if the NC network recovers, the primary NC and the new primary NC are combined as dual primary, the primary NC adds a new backup NC to the DDC cluster after restarting, and the backup NC adds a new backup NC to the DDC cluster after restarting.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication technology, in particular to a communication system. BACKGROUND

[0002] Distributed decoupling chassis (English: Distributed Disaggregated Chassis, for short: DDC) refers to the decomposition of a large chassis, and the construction of a large forwarding capacity DCI role device by using a box switch. Compared with the traditional large chassis, the DDC is deployed in a scattered manner, does not require a high cabinet, can be expanded to a larger capacity, and has low power consumption of a single device and smaller influence range of a single device failure.

[0003] In the DDC cluster, two network controllers (English: Network Controller, for short: NC), fabric (English: Fabric, for short: FAB), forwarding switches (English: Line Card, for short: LC), and control plane network management switches (English: Management, for short: MGT) are mainly included. Among them, the two NCs are used to realize the master and standby work.

[0004] In the DDC cluster, the control plane and the data plane are separated. Two NCs form the control plane, and all LCs and FABs form the data plane. The NC centrally controls all LCs and FABs. However, once the control plane fails, the data plane will become unavailable, and the entire cluster will also become unavailable. SUMMARY

[0005] Therefore, the present application provides a communication system to solve the problem that in the existing DDC cluster, the failure of the control plane will cause the data plane to become unavailable, and the entire cluster to become unavailable.

[0006] In a first aspect, the present application provides a communication system, which comprises a master and standby NC and a plurality of LCs, an NC container is run in each NC, and the plurality of LCs comprises a first type of LC, a vNC container is run in each first type of LC.

[0007] When the master and standby NC containers in the master and standby NCs both fail or the NC network where the master and standby NCs are located fails, a vNC container is selected from the plurality of vNC containers as a new master NC, and the DDC cluster is controlled and managed by the new master NC.

[0008] If any of the master and standby NCs recovers after restarting, the new standby NC joins the DDC cluster.

[0009] If the NC network recovers, the master NC performs dual-master merging with the new master NC, the master NC, after restarting, joins the DDC cluster as a new backup NC, and the backup NC, after restarting, joins the DDC cluster as a new backup NC.

[0010] With reference to the first aspect, in a first possible implementation manner, each LC, after starting, sends a registration packet to the master NC, and each registration packet comprises a MAC address and a device serial number of the LC.

[0011] After the master NC receives each registration packet, the master NC sorts the receiving time of each registration packet according to the order in which each registration packet is received.

[0012] According to the sorting result, a first registration packet with the first receiving time and a second registration packet with the second receiving time are determined, and a first LC sending the first registration packet and a second LC sending the second registration packet are determined.

[0013] The master NC sends a first ACK packet to the first LC, and the first ACK packet comprises a configuration flag, a first DADDR and a first CADDR, and sends a second ACK packet to the second LC, and the second ACK packet comprises the configuration flag, a second DADDR and a second CADDR.

[0014] The first LC configures and starts the vNC container locally according to the configuration flag, the first DADDR and the first CADDR.

[0015] The second LC configures and starts the vNC container locally according to the configuration flag, the second DADDR and the second CADDR.

[0016] With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the master NC sends a third ACK packet to each LC in the DDC cluster except the first LC and the second LC, and the third ACK packet comprises a third DADDR.

[0017] The other LCs receive the third ACK packet.

[0018] With reference to the first or second possible implementation manner of the first aspect, in a third possible implementation manner, the master NC records a first mapping relationship between the first DADDR and the first CADDR, and records a second mapping relationship between the second DADDR and the second CADDR.

[0019] The main NC sends a first notification message to each device currently in the DDC cluster, the first notification message including an address attribute of each vNC container.

[0020] In a fourth possible implementation of the first aspect, when the main NC determines that the first LC or the second LC fails, according to the sorting result, a third registration message at a third position in time is determined, and a third LC sending the third registration message is determined.

[0021] The main NC sends a second notification message to the third LC, the second notification message including a configuration flag, a fourth DADDR and a third CADDR.

[0022] The third LC locally configures and starts the vNC container according to the configuration flag, the fourth DADDR and the third CADDR.

[0023] In a fifth possible implementation of the fourth possible implementation of the first aspect, the main NC records a third mapping relationship between the fourth DADDR and the third CADDR.

[0024] The main NC sends a third notification message to each device currently in the DDC cluster, the third notification message including an address attribute of each vNC container.

[0025] In a sixth possible implementation of the first aspect, the new main NC sends a synchronization message to each new backup NC, the synchronization message including to-be-synchronized data.

[0026] When receiving a fourth ACK message sent by each new backup NC, the new main NC restarts the vNC container.

[0027] Each new backup NC performs new main NC election again, and the elected new main NC controls the DDC cluster.

[0028] The restarted vNC container re-joins the DDC cluster as a new backup NC.

[0029] In a seventh possible implementation of the first aspect, the main NC and the new main NC perform dual-master merging, specifically including

[0030] The main NC and the new main NC both periodically send heartbeat messages.

[0031] When the main NC receives a heartbeat message sent by the new main NC, it is determined that there is a dual master in the DDC cluster.

[0032] The main NC performs a restart operation.

[0033] In a third possible implementation of the first aspect, in combination with the first to third possible implementations of the first aspect, the address attribute of the vNC container includes a DADDR of the vNC container and a CADDR of the vNC container, and the DADDR of the vNC container is the same as a DADDR of the LC in which the vNC container is located.

[0034] In a sixth possible implementation of the first aspect, in combination with the first possible implementation of the first aspect, the CADDR of the master vNC container of the new master NC is the minimum CADDR of the plurality of NC containers and / or the minimum CADDR of the plurality of vNC containers.

[0035] Or;

[0036] The CADDR of the master vNC container of the new master NC is the minimum CADDR of the plurality of NC containers and / or the minimum CADDR of the plurality of vNC containers.

[0037] Therefore, by applying the communication system provided in the present application, the communication system includes master and backup NCs and a plurality of LCs, one NC container runs in each NC, the plurality of LCs include first type LCs, one vNC container runs in each first type LC; when the master and backup NC containers in the master and backup NCs both fail or the NC network in which the master and backup NCs are located fails, one vNC container is selected from the plurality of vNC containers as a new master NC, and the new master NC controls the DDC cluster; if any of the master and backup NCs recovers after restarting, the new backup NC joins the DDC cluster; if the NC network recovers, the master NC and the new master NC perform dual-master merging, the master NC joins the DDC cluster as a new backup NC after restarting, and the backup NC joins the DDC cluster as a new backup NC after restarting.

[0038] In this way, for the scenario of failure of all NCs in the control plane, the data plane can continue to work normally under the management of the vNC container. After the NC recovers, the NC can rejoin and manage the DDC cluster, greatly improving the stability of the system. At the same time, the problem that the failure of the control plane in the existing DDC cluster will lead to the unavailability of the data plane and the entire cluster is also solved. BRIEF DESCRIPTION OF DRAWINGS

[0039] Figure 1 A communication system networking schematic diagram provided for an embodiment of the present application;

[0040] Figure 2 Another communication system networking schematic diagram provided for an embodiment of the present application;

[0041] Figure 3 Still another communication system networking schematic diagram provided for an embodiment of the present application. Detailed Implementation

[0042] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0043] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used in this application and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the corresponding listed items.

[0044] It should be understood that although the terms first, second, third, etc., may be used in this application to describe various information, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."

[0045] The communication system provided in the embodiments of this application will be described in detail below. See also Figure 1 , Figure 1 This is a schematic diagram of a communication system network provided in an embodiment of this application. Figure 1 In this system, the communication system includes NC, MGT, FAB, and LC. There are multiple of each network device. For example, NC1, NC2; MGT-1, MGT-2; FAB-1...FAB-40; LC1, LC2...LC47, LC48, etc.

[0046] NC1 and NC2 each run one NC container, and NC1 and NC2 have the same role depending on the role of the NC container. For example, if the NC container in NC1 is the primary NC container, then NC1 is the primary NC; if the NC container in NC2 is the backup NC container, then NC2 is the backup NC.

[0047] After NC1 and NC2 start, all the software that will be launched (such as routing protocol software, system log software, driver processes, and forwarding) will run in their respective NC containers.

[0048] Similarly, after each LC is started, all software started by the LC is also run in the LC container.

[0049] Optionally, in the embodiment of the present application, after each LC is started, a registration packet is generated, which includes the media access control (Media Access Control, MAC for short) address of the LC and the device serial number. Each LC sends the registration packet to the master NC (NC1 is hereinafter referred to as the master NC, and NC2 is referred to as the backup NC).

[0050] After the master NC receives each registration packet, the master NC sorts the receiving time of each registration packet according to the order in which each registration packet is received. That is, the receiving time of the registration packet received first is sorted first, and the receiving time of the registration packet received later is sorted later.

[0051] According to the sorting result, the master NC determines the first registration packet with the first receiving time and the second registration packet with the second receiving time, and determines the first LC that sends the first registration packet and the second LC that sends the second registration packet. For example, Figure 1 LC1 and LC2 in the DDC cluster. Generally, the master NC selects the registration packets with the first two receiving times and determines the two LCs that send the two registration packets to ensure stability. If the number of LCs in the DDC cluster is large, multiple LCs can also be selected, for example, 3, 4, etc.

[0052] The master NC generates a first acknowledge character (Acknowledge character, ACK for short) packet and a second ACK packet. The first ACK packet includes a configuration flag, a first device address (Device Address, DADDR for short), and a first container address (Container Address, CADDR for short); the second ACK packet includes a configuration flag, a second DADDR, and a second CADDR. The master NC sends the first ACK packet to the first LC and sends the second ACK packet to the second LC. The DADDR can be an Internet Protocol (Internet Protocol, IP for short) address (the IP address includes a specific prefix (a network segment for networking) and a MAC address of the LC) or a MAC address assigned by the master NC. The CADDR can be a unique identifier of the container, for example, slot numbers 1, 2, 8, 16, etc.

[0053] Take the first LC as an example for illustration. After receiving the first ACK message, the first LC obtains the configuration flag, the first DADDR and the first CADDR therefrom. According to the first configuration flag, the first LC determines to locally configure a virtual-NC (vNC for short) container. The vNC container is a pure software NC container.

[0054] In an implementation, the configuration file of the vNC container is stored locally when the first LC is manufactured. At this time, the first LC obtains the configuration file of the vNC container from the local according to the first configuration flag, and configures and starts the vNC container locally according to the configuration file of the vNC container.

[0055] In another implementation, the first LC sends a request message to the master NC according to the first configuration flag, where the request message is used to obtain the configuration file of the vNC container from the master NC. After receiving the request message, the master NC generates a response message, where the response message carries the configuration file of the vNC container. The master NC sends the response message to the first LC. After receiving the response message, the first LC obtains the configuration file of the vNC container therefrom. According to the configuration file of the vNC container, the first LC configures and starts the vNC container locally.

[0056] After obtaining the first DADDR from the first ACK message, the first LC takes the first DADDR as its own address. After configuring the vNC container locally, the first LC obtains the first CADDR from the first ACK message, and takes the first CADDR as the address of the vNC container.

[0057] It can be understood that the vNC container included in the first LC and the second LC will join the DDC cluster as a standby NC. The master NC periodically broadcasts a heartbeat message, and the vNC container can receive the heartbeat message. According to the heartbeat message, the vNC container requests the master NC for synchronization data. The master NC sends a synchronization message to the vNC container, where the synchronization message includes the data to be synchronized.

[0058] Optionally, in the embodiments of the present application, the DDC cluster includes other LCs in addition to the first LC, for example, Figure 1 LC47 and LC48 in FIG. 4.

[0059] According to the foregoing, each LC in the DDC cluster sends a registration message to the master NC. The master NC generates a third ACK message while sending the ACK message to the first LC. The third ACK message includes a third DADDR and does not include a configuration flag.

[0060] After receiving the third ACK message, the other LCs obtain the third DADDR therefrom. The other LCs take the third DADDR as their own address.

[0061] Optionally, in the embodiment of the present application, after sending the ACK message to the first LC and the other LCs, the master NC also records the first mapping relationship between the first DADDR and the first CADDR, and records the second mapping relationship between the second DADDR and the second CADDR.

[0062] The master NC also generates a first notification message, which includes the address attribute of each vNC container. The master NC sends the first notification message to each device in the in-situ DDC cluster, so that each device in the in-situ DDC cluster determines the location where the vNC is located.

[0063] Optionally, the address attribute of the vNC container includes the DADDR of the vNC container and the CADDR of the vNC container, and the DADDR of the vNC container is the same as the DADDR of the LC where the vNC container is located.

[0064] In Figure 1 , the control plane (shown by the dashed line in Figure 1 ) and the data plane (shown by the solid line in Figure 1 ) of the in-situ DDC cluster are separated. The master NC and the backup NC and the vNC container constitute the control plane, and the LC and the FAB constitute the data plane. The master NC centrally manages and controls all MGTs, FABs and LCs.

[0065] Optionally, in the embodiment of the present application, when the master NC determines that the first LC or the second LC fails (for example, the LC is powered off or the network fails), according to the sorting result, the master NC determines a third registration message received at the third position, and determines a third LC sending the third registration message.

[0066] The master NC generates a second notification message, which includes a configuration flag, a fourth DADDR and a third CADDR. The master NC sends the second notification message to the third LC.

[0067] After receiving the second notification message, the third LC performs the same process as the first LC receiving the first ACK message. The third LC locally configures and starts the vNC container. The third LC takes the fourth DADDR as its own address, and takes the third CADDR as the address of the vNC container.

[0068] It can be understood that the vNC container included in the third LC will join the in-situ DDC cluster as a backup NC. The master NC periodically broadcasts a heartbeat message, and the vNC container can receive the heartbeat message. According to the heartbeat message, the vNC container requests synchronization data from the master NC. The master NC sends a synchronization message to the vNC container, and the synchronization message includes the data to be synchronized.

[0069] As Figure 2 shown, Figure 2Another communication system networking diagram is provided in the embodiment of the present application. In Figure 2 In the embodiment of the present application, the master NC generates and sends a second notification message to the LC3. The LC3 configures and starts the vNC container according to the second notification message. It can be understood that the vNC container included in the LC3 is the backup NC.

[0070] Optionally, in the embodiment of the present application, after the master NC sends the second notification message to the third LC, the master NC also records a third mapping relationship between the fourth DADDR and the third CADDR locally.

[0071] The master NC also generates a third notification message, which includes the address attribute of each vNC container. The master NC sends the first notification message to each device currently in the DDC cluster, so that each device currently in the DDC cluster determines the location of the vNC.

[0072] Optionally, the address attribute of the vNC container includes the DADDR of the vNC container and the CADDR of the vNC container, and the DADDR of the vNC container is the same as the DADDR of the LC where the vNC container is located.

[0073] According to the foregoing example, since the LC2 fails, the master NC does not send the third notification message to the LC2.

[0074] According to the foregoing, in the embodiment of the present application, the plurality of LCs include a first type of LC, and the number of the first type of LC is two, for example, Figure 1 LC1 and LC2 in the foregoing. Each first type of LC runs a vNC container in addition to running an LC container.

[0075] Referring to Figure 3 , Figure 3 Another communication system networking diagram is provided in the embodiment of the present application. In Figure 3 In the embodiment of the present application, the master NC container in the NC1 and the backup NC container in the NC2 both fail, or the NC network between the NC1, the NC2 and the MGT-1, the MGT-2 fails.

[0076] At this time, the master NC has failed to continue to control the MGT, the FAB and the LC. The vNC container as the backup NC also fails to receive the heartbeat message sent by the master NC. The plurality of vNC containers start an election process, select one vNC container as a new master NC from the plurality of vNC containers, and control the DDC cluster by the new master NC, and the other vNC containers are backup NCs.

[0077] Optionally, in the embodiment of the present application, the CADDR of the master vNC container as the new master NC is the minimum value of the CADDR of the plurality of vNC containers.

[0078] The election process is specifically as follows: the two vNC containers generate and send probe packets to each other. After receiving the probe packet, the local vNC container generates and sends an ACK packet to the opposite vNC container, and the ACK packet includes the CADDR of the vNC container. After receiving the ACK, the local vNC container obtains the CADDR of the opposite vNC container. The local vNC container compares the CADDR of itself with the CADDR of the opposite vNC container. If the CADDR of the local vNC container is smaller than the CADDR of the opposite vNC container, the local vNC container is automatically upgraded to a new master NC, and the opposite vNC container still maintains a standby NC; otherwise, the opposite vNC container is automatically upgraded to a new master NC, and the local vNC container still maintains a standby NC.

[0079] It can be understood that if the standby NC container in the NC2 does not fail, the standby NC container and the vNC container start the election process. At this time, the CADDR of the master NC container as the new master NC is the minimum value of the CADDRs of the plurality of vNC containers and the NC container.

[0080] If any of the NC1 and the NC2 recovers from failure after restart, the NC1 and the NC2 after recovery from failure both join the DDC cluster as new standby NCs. That is, the new master NC periodically broadcasts a heartbeat packet, and the NC1 and the NC2 after recovery from failure can receive the heartbeat packet. According to the heartbeat packet, the NC1 and the NC2 after recovery from failure request synchronization data from the new master NC. The new master NC sends a synchronization packet to the NC1 and the NC2 after recovery from failure, and the synchronization packet includes the data to be synchronized.

[0081] If the NC network recovers from failure, the master NC (the original master NC, i.e., the NC1) and the new master NC perform dual-master merging, the master NC joins the DDC cluster as a new standby NC after restart, and the standby NC joins the DDC cluster as a new standby NC after restart.

[0082] It should be noted that after the NC network recovers from failure, since the new master NC periodically broadcasts a heartbeat packet, and the master NC also periodically broadcasts a heartbeat packet, the new master NC and the master NC will both receive the heartbeat packet sent by the other master NC. At this time, the new master NC and the master NC determine that there are dual master NCs in the DDC cluster.

[0083] After determining that there are dual master NCs in the DDC cluster, the master NC automatically restarts and joins the DDC cluster as a new standby NC again after restart.

[0084] It can be understood that before restart, the master NC is a standby NC (the original standby NC, i.e., the NC2), and after restart, the master NC still joins the DDC cluster as a new standby NC again.

[0085] Optionally, in the embodiment of the application, after the vNC container becomes a new master NC, the vNC container controls the DDC cluster.

[0086] The new master NC generates a synchronization message including the data to be synchronized. The new master NC sends the synchronization message to each new standby NC. After each new standby NC receives the synchronization message, it obtains the data to be synchronized therefrom and stores the data to be synchronized locally.

[0087] After each new standby NC stores the data to be synchronized locally, it generates and sends a fourth ACK message to the new master NC.

[0088] After the new master NC receives the fourth ACK message sent by each new standby NC, the new master NC determines that the current DDC cluster is stable. The new master NC restarts the vNC container where it is located. At this time, there is no master NC in the DDC cluster, and all are new standby NCs. Each new standby NC performs new master NC election again, and the elected new master NC controls the DDC cluster.

[0089] In the embodiment of the application, the elected new master NC is an NC container in NC1. At this time, the restarted vNC container re-joins the DDC cluster as a new standby NC. Generally, the CADDR of the NC container in the original master NC1 is set to the minimum value, so that the NC container in the original master NC1 is elected as the master NC again in the election.

[0090] It can be understood that the process of starting the election of the plurality of standby NCs has been described above and will not be repeated here.

[0091] Optionally, in the embodiment of the application, the CADDR of the master NC container as the new master NC is the minimum value of the CADDRs of the plurality of NC containers and / or the minimum value of the CADDRs of the plurality of vNC containers; or

[0092] The CADDR of the master vNC container as the new master NC is the minimum value of the CADDRs of the plurality of NC containers and / or the minimum value of the CADDRs of the plurality of vNC containers.

[0093] Therefore, by applying the communication system provided in the application, the communication system includes master and standby NCs and a plurality of LCs, one NC container runs in each NC, the plurality of LCs include first type LCs, one vNC container runs in each first type LC; when the master and standby NC containers in the master and standby NCs both fail or the NC network where the master and standby NCs are located fails, one vNC container is selected from the plurality of vNC containers as a new master NC, and the DDC cluster is controlled by the new master NC; if any of the master and standby NCs recovers after being restarted, it joins the DDC cluster as a new standby NC; if the NC network recovers, the master and new master NCs perform dual master merging, the master NC joins the DDC cluster as a new standby NC after being restarted, and the standby NC joins the DDC cluster as a new standby NC after being restarted.

[0094] Thus, for the scenario of all NC failures in the control plane, the data plane can continue to work normally under the management of the vNC container. After the NC failure is recovered, the NC can rejoin and manage the DDC cluster, greatly improving the stability of the system. At the same time, the problem that the control plane failure in the existing DDC cluster will lead to the data plane being unavailable and the entire cluster being unavailable is also solved.

[0095] The above only describes preferred embodiments of the present application and is not used to limit the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A communication system, characterized by The communication system comprises a master and backup control engine NC and a plurality of forwarding switches LC, one NC container is run in each NC, the plurality of LCs comprise first type LCs, one virtual control engine vNC container is run in each first type LC; When the master and backup NC containers in the master and backup NCs both fail or the NC network where the master and backup NCs are located fails, one vNC container is selected as a new master NC from the plurality of vNC containers, and the new master NC controls and manages a distributed decoupling machine frame DDC cluster; If any of the master and backup NCs recovers after restarting, a new backup NC joins the DDC cluster; If the NC network recovers, the master NC and the new master NC perform dual master merging, the master NC joins the DDC cluster as a new backup NC after restarting, and the backup NC joins the DDC cluster as a new backup NC after restarting; The new master NC sends a synchronization message to each new backup NC, and the synchronization message comprises to-be-synchronized data; When receiving a fourth acknowledgement character ACK message sent by each new backup NC, the new master NC restarts the vNC container where the new master NC is located; Each new backup NC performs new master NC election again, and the elected new master NC controls and manages the DDC cluster; The restarted vNC container joins the DDC cluster as a new backup NC again.

2. The communication system according to claim 1, wherein After each LC starts, the LC sends a registration message to the master NC, and each registration message comprises a media access control address MAC address and a device serial number of the LC; After the master NC receives each registration message, the master NC sorts the receiving time of each registration message according to the order in which each registration message is received; According to the sorting result, a first registration message with the first receiving time and a second registration message with the second receiving time are determined, and a first LC sending the first registration message and a second LC sending the second registration message are determined; The master NC sends a first ACK message to the first LC, and the first ACK message comprises a configuration flag, a first physical device address DADDR and a first container address CADDR, and sends a second ACK message to the second LC, and the second ACK message comprises the configuration flag, a second DADDR and a second CADDR; The first LC configures and starts the vNC container locally according to the configuration flag, the first DADDR and the first CADDR; The second LC configures and starts the vNC container locally according to the configuration flag, the second DADDR and the second CADDR.

3. The communication system according to claim 2, wherein The master NC sends a third ACK message to each LC in the DDC cluster except the first LC and the second LC, and the third ACK message comprises a third DADDR; The other LCs receive the third ACK message.

4. The communication system according to claim 2 or 3, wherein The master NC records a first mapping relationship between the first DADDR and the first CADDR, and records a second mapping relationship between the second DADDR and the second CADDR; The master NC sends a first notification message to each device currently in the DDC cluster, and the first notification message includes an address attribute of each vNC container.

5. The communication system of claim 2, wherein When the master NC determines that the first LC or the second LC fails, according to the sorting result, a third registration message in which a receiving time is in a third position is determined, and a third LC sending the third registration message is determined; The master NC sends a second notification message to the third LC, and the second notification message includes a configuration flag, a fourth DADDR and a third CADDR; The third LC configures and starts the vNC container locally according to the configuration flag, the fourth DADDR and the third CADDR.

6. The communication system of claim 5, wherein The master NC records a third mapping relationship between the fourth DADDR and the third CADDR; The master NC sends a third notification message to each device currently in the DDC cluster, and the third notification message includes an address attribute of each vNC container.

7. The communication system of claim 1, wherein, The master NC and the new master NC perform dual-master merging, specifically including The master NC and the new master NC periodically send heartbeat messages; When the master NC receives the heartbeat message sent by the new master NC, it is determined that there is a dual master in the DDC cluster; The master NC performs a restart operation.

8. The communication system of any one of claims 2-4, wherein The address attribute of the vNC container includes a DADDR and a CADDR of the vNC container, and the DADDR of the vNC container is the same as the DADDR of the LC in which the vNC container is located.

9. The communication system of claim 1, wherein The CADDR of the master NC container as the new master NC is the minimum value of the CADDR of the plurality of NC containers and / or the minimum value of the CADDR of the plurality of vNC containers. Or The CADDR of the master vNC container as the new master NC is the minimum value of the CADDR of the plurality of NC containers and / or the minimum value of the CADDR of the plurality of vNC containers.

Images