Communication system

Abstract

The invention provides a communication system, the communication system comprises a main NC, a standby NC and a plurality of LCs, an NC container is operated in each NC, the plurality of LCs comprise a first type of LCs, and a vNC container is operated in each first type of LC; when the main and standby NC containers in the main and standby NCs fail or the NC network where the main and standby NCs are located fails, one vNC container is selected from a plurality of vNC containers to serve as a new main NC, and the new main NC manages and controls the DDC cluster; if the fault of any one of the main and standby NCs is recovered after restarting, adding a new standby NC into the DDC cluster; if the NC network fault is recovered, the main NC and the new main NC are subjected to double-main combination, after the main NC is restarted, a new standby NC is added into the DDC cluster, and after the standby NC is restarted, the new standby NC is added into the DDC cluster.

Description

Technical Field

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

[0002] Distributed Disaggregated Chassis (DDC) is a DCI role device that decomposes a large chassis and uses box switches to build a large forwarding capability. Compared with traditional large chassis, DDC deployment is decentralized, does not require high-power cabinets, can expand capacity, and has low power consumption per device, so the impact of a single device failure is smaller.

[0003] In the DDC cluster, there are mainly two control engines (English: Network Controller, abbreviated: NC), fabric (English: Fabric, abbreviated: FAB), forwarding switch (English: Line Card, abbreviated: LC), control plane network management switch (English: Management, abbreviated: MGT). Among them, two NCs are used to realize the master-slave work.

[0004] In a DDC cluster, the control plane is separated from the data plane. Two NCs form the control plane, and all LCs and FABs form the data plane. NC centrally controls all LCs and FABs. However, once the control plane fails, the data plane will be unavailable, and the entire cluster will also be unavailable. Summary of the invention

[0005] In view of this, the present application provides a communication system to solve the problem in the existing DDC cluster that a control plane failure will cause the data plane to be unavailable and also make the entire cluster unavailable.

[0006] In a first aspect, the present application provides a communication system, the communication system comprising a primary and backup NC and multiple LCs, each NC running an NC container, the multiple LCs comprising a first type LC, each first type LC running a vNC container;

[0007] When both the active and standby NC containers in the active and standby NC fail or the NC network where the active and standby NCs are located fails, a vNC container is selected from multiple vNC containers as a new active NC, and the new active NC manages and controls the DDC cluster;

[0008] If any of the active and standby NCs recovers after restart, the new standby NC joins the DDC cluster;

[0009] If the NC network failure is recovered, the main NC and the new main NC are merged, and after the main NC is restarted, it joins the DDC cluster as a new standby NC, and after the standby NC is restarted, it joins the DDC cluster as a new standby NC.

[0010] In combination with the first aspect, in a first possible implementation manner, after each LC is started, it sends a registration message to the main NC, and each registration message includes the MAC address and device serial number of the LC;

[0011] After receiving each registration message, the master NC sorts the receiving time of each registration message according to the order of receiving each registration message;

[0012] According to the sorting result, determine the first registration message whose receiving time is the first and the second registration message whose receiving time is the second, and determine the first LC that sends the first registration message and the second LC that sends the second registration message;

[0013] The master NC sends a first ACK message to the first LC, the first ACK message includes a configuration tag, a first DADDR and a first CADDR, and sends a second ACK message to the second LC, the second ACK message includes the configuration tag, a second DADDR and a second CADDR;

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

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

[0016] In combination with the first possible implementation of the first aspect, in a second possible implementation, the master NC sends a third ACK message to each of the other LCs in the DDC cluster except the first LC and the second LC, where the third ACK message includes a third DADDR;

[0017] The other LC receives the third ACK message.

[0018] In combination with 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 master NC sends a first notification message to each device in the DDC cluster, where the first notification message includes an address attribute of each vNC container.

[0020] In combination with the first possible implementation manner of the first aspect, in a fourth possible implementation manner, when the main NC determines that the first LC or the second LC is faulty, the main NC determines, according to the sorting result, a third registration message with a third receiving time, and determines a third LC that sends the third registration message;

[0021] The master NC sends a second notification message to the third LC, where the second notification message includes a configuration tag, a fourth DADDR, and a third CADDR;

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

[0023] In combination with the fourth possible implementation of the first aspect, in a fifth possible implementation, the master NC records a third mapping relationship between the fourth DADDR and the third CADDR;

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

[0025] In combination with the first aspect, in a sixth possible implementation manner, the new master NC sends a synchronization message to each new backup NC, where the synchronization message includes data to be synchronized;

[0026] When receiving the fourth ACK message sent by each new standby NC, the new master NC restarts the vNC container where it is located;

[0027] Each new standby NC elects a new master NC again, and the elected new master NC manages and controls the DDC cluster;

[0028] The restarted vNC container joins the DDC cluster again as a new standby NC.

[0029] In combination with the first aspect, in a seventh possible implementation manner, the main NC and the new main NC are merged into a dual-main NC, specifically including:

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

[0031] When the master NC receives the heartbeat message sent by the new master NC, it is determined that there are two masters in the DDC cluster;

[0032] The main NC performs a restart operation.

[0033] In combination with the first to third possible implementation methods of the first aspect, in the third possible implementation method, the address attributes of the vNC container include the DADDR and 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.

[0034] In combination with the first possible implementation of the first aspect, in a sixth possible implementation, the CADDR of the main NC container serving as the new main NC is a minimum CADDR value of multiple NC containers and / or a minimum CADDR value of multiple vNC containers;

[0035] or;

[0036] The CADDR of the main vNC container serving as the new main NC is the minimum CADDR value of multiple NC containers and / or is the minimum CADDR value of multiple vNC containers.

[0037] Therefore, by applying the communication system provided by the present application, the communication system includes a primary and standby NC and multiple LCs, each NC runs an NC container, the multiple LCs include a first type LC, and each first type LC runs a vNC container; when the primary and standby NC containers in the primary and standby NCs both fail or the NC network where the primary and standby NCs are located fails, a vNC container is selected from multiple vNC containers as the new primary NC, and the DDC cluster is managed and controlled by the new primary NC; if any of the primary and standby NCs recovers from the fault after restart, the new standby NC joins the DDC cluster; if the NC network fault is recovered, the primary NC and the new primary NC are merged into a dual-master, and the primary NC joins the DDC cluster as the new standby NC after restart, and the standby NC joins the DDC cluster as the new standby NC after restart.

[0038] In this way, in the scenario where all NCs in the control plane fail, the data plane can continue to work normally under the management of the vNC container. Moreover, 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, it also solves the problem in the existing DDC cluster that a control plane failure will cause the data plane to be unavailable, and also make the entire cluster unavailable. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 A schematic diagram of a communication system network provided in an embodiment of the present application;

[0040] Figure 2 A schematic diagram of another communication system network provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of another communication system network provided in an embodiment of the present application. DETAILED DESCRIPTION

[0042] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0043] The terms used in this application are only for the purpose of describing specific embodiments and are not intended to limit this application. The singular forms of "a", "said" and "the" used in this application and the appended claims are also intended to include plural forms unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in this article refers to and includes any or all possible combinations of one or more corresponding listed items.

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

[0045] The communication system provided by the embodiment of the present application is described in detail below. Figure 1 , Figure 1 A communication system networking diagram provided in an embodiment of the present application. Figure 1 In the communication system, there are NC, MGT, FAB and LC. Each network device has multiple numbers. 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 according to the role of the NC container, NC1 and NC2 have the same role. For example, if the NC container in NC1 is the main NC container, then NC1 is the main NC; if the NC container in NC2 is the backup NC container, then NC2 is the backup NC.

[0047] After NC1 and NC2 are started, all the software started (for example, routing protocol software, system log software, driver process, forwarding) are run in their respective NC containers.

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

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

[0050] After receiving 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, that is, the receiving time of the registration message received first is sorted first, and the receiving time of the registration message received later is sorted later.

[0051] According to the sorting result, the main NC determines the first registration message with the first receiving time and the second registration message with the second receiving time, and determines the first LC for sending the first registration message and the second LC for sending the second registration message. Figure 1 LC1 and LC2 in the DDC cluster. Usually, the master NC selects the registration message with the first two received time sortings and determines the two LCs that send the two registration messages to ensure stability. If there are many LCs in the DDC cluster, multiple LCs can be selected, for example, 3, 4, etc.

[0052] The main NC generates a first confirmation character (English: Acknowledge character, abbreviated: ACK) message and a second ACK message. The first ACK message includes a configuration tag, a first physical device address (English: Device Address, abbreviated: DADDR) and a first container address (English: Container Address, abbreviated: CADDR); the second ACK message includes a configuration tag, a second DADDR and a second CADDR. The main NC sends a first ACK message to the first LC and sends a second ACK message to the second LC. Among them, DADDR can be an Internet Protocol (English: Internet Protocol, abbreviated: IP) address (the IP address includes a specific prefix (network segment) and the MAC address of the LC) and a MAC address assigned by the main NC. CADDR can be a unique identifier of a container, for example, a slot number: 1, 2, 8, 16, etc.

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

[0054] In one implementation, the configuration file of the vNC container is stored locally when the first LC is shipped. At this time, the first LC obtains the configuration file of the vNC container from the local according to the first configuration tag, 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 tag, and 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, and the response message contains the configuration file of the vNC container. The master NC sends a response message to the first LC. After receiving the response message, the first LC obtains the configuration file of the vNC container from it. According to the configuration file of the vNC container, the first LC locally configures and starts the vNC container.

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

[0057] It is understandable that the vNC container included in the first LC and the second LC will join the DDC cluster as a standby NC. The main NC periodically broadcasts and sends 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 main NC. The main NC sends a synchronization message to the vNC container, and the synchronization message includes the data to be synchronized.

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

[0059] As can be seen from the above, each LC in the DDC cluster sends a registration message to the master NC. While sending an ACK message to the first type of LC, the master NC also generates a third ACK message. The third ACK message includes a third DADDR and does not include a configuration tag.

[0060] After receiving the third ACK message, the other LCs obtain the third DADDR from it and use the third DADDR as their own addresses.

[0061] Optionally, in the embodiment of the present application, after the main NC sends ACK messages to the first type LC and other LCs, the main NC will also locally record the first mapping relationship between the first DADDR and the first CADDR, and record the second mapping relationship between the second DADDR and the second CADDR.

[0062] The master NC also generates a first notification message including the address attribute of each vNC container. The master NC sends the first notification message to each device in the DDC cluster so that each device in the DDC cluster determines the location of the vNC.

[0063] Optionally, the address attribute of the vNC container includes DADDR and 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] exist Figure 1 In the DDC cluster, the control plane ( Figure 1 The dashed line in the middle) and the data plane ( Figure 1 The active and standby NCs and vNC containers form the control plane, and the LCs and FABs form the data plane. The active NC centrally manages all MGTs, FABs, and LCs.

[0065] Optionally, in an embodiment of the present application, when the main 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 main NC determines the third registration message with the third receiving time, and determines the third LC that sends the third registration message.

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

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

[0068] It is understandable that the vNC container included in the third LC will join the DDC cluster as a standby NC. The main NC periodically broadcasts and sends heartbeat messages, and the vNC container can receive the heartbeat message. According to the heartbeat message, the vNC container requests synchronization data from the main NC. The main NC sends a synchronization message to the vNC container, and the synchronization message includes the data to be synchronized.

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

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

[0071] The master NC also generates a third notification message including 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 DADDR and 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 above example, since LC2 fails, the master NC does not send the third notification message to LC2.

[0074] According to the foregoing, in the embodiment of the present application, the plurality of LCs include first type LCs, and the number of first type LCs is 2, for example, Figure 1 In each first-class LC, in addition to the LC container, a vNC container is also run.

[0075] See also Figure 3 , Figure 3 A schematic diagram of another communication system network provided in an embodiment of the present application. Figure 3 In the example, the main NC container in NC1 and the backup NC container in NC2 are both faulty, or the NC network between NC1, NC2 and MGT-1, MGT-2 is faulty.

[0076] At this point, the master NC can no longer control MGT, FAB, and LC. The vNC container, which is the backup NC, cannot receive the heartbeat message sent by the master NC. Multiple vNC containers start the election process, and one vNC container is selected from multiple vNC containers as the new master NC. The new master NC controls the DDC cluster, and the other vNC containers are backup NCs.

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

[0078] The election process is specifically as follows: the vNC containers at both ends generate and send detection messages to each other. After receiving the detection message, the local vNC container generates and sends an ACK message to the opposite vNC container, and the ACK message includes the CADDR of the vNC container. After receiving the ACK, the local vNC container obtains the CADDR of the opposite vNC container from it. The local vNC container compares its own CADDR with the CADDR of the opposite vNC container. If its own CADDR is smaller than the CADDR of the opposite vNC container, the local vNC container is automatically upgraded to the new main NC, and the opposite vNC container still maintains the backup NC; otherwise, the opposite vNC container is automatically upgraded to the new main NC, and the local vNC container still maintains the backup NC.

[0079] It is understandable that if the standby NC container in NC2 is not faulty, the standby NC container and the vNC container start the election process. At this time, the CADDR of the main NC container as the new main NC is the minimum CADDR value of multiple vNC containers and NC containers.

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

[0081] If the NC network failure is restored, the active NC (the original active NC, namely NC1) and the new active NC are merged. After the active NC is restarted, it joins the DDC cluster as the new standby NC, and after the standby NC is restarted, it joins the DDC cluster as the new standby NC.

[0082] It should be noted that after the NC network failure is restored, since the new master NC periodically broadcasts and sends heartbeat messages, and the master NC also periodically broadcasts and sends heartbeat messages, the new master NC and the master NC will both receive the heartbeat messages sent by the other master NC. At this time, the new master NC and the master NC determine that there are two master NCs in the DDC cluster.

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

[0084] It is understandable that before the restart, it is a standby NC (the original standby NC, namely NC2), and after the restart, it joins the DDC cluster again as a new standby NC.

[0085] Optionally, in the embodiment of the present application, after the vNC container serves as the new master NC, it will manage and control the DDC cluster.

[0086] The new master NC generates a synchronization message including the data to be synchronized. The new master NC sends a synchronization message to each new standby NC. After receiving the synchronization message, each new standby NC obtains the data to be synchronized 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 NAC.

[0088] When 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 state 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 elects a new master NC again, and the elected new master NC manages and controls the DDC cluster.

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

[0090] It is understandable that the process of initiating election of multiple standby NCs has been described above and will not be repeated here.

[0091] Optionally, in the embodiment of the present application, the CADDR of the main NC container serving as the new main NC is the minimum CADDR value of multiple NC containers and / or the minimum CADDR value of multiple vNC containers; or;

[0092] The CADDR of the primary vNC container serving as the new primary NC is the minimum CADDR value of multiple NC containers and / or is the minimum CADDR value of multiple vNC containers.

[0093] Therefore, by applying the communication system provided by the present application, the communication system includes a primary and standby NC and multiple LCs, each NC runs an NC container, the multiple LCs include a first type LC, and each first type LC runs a vNC container; when the primary and standby NC containers in the primary and standby NCs both fail or the NC network where the primary and standby NCs are located fails, a vNC container is selected from multiple vNC containers as the new primary NC, and the DDC cluster is managed and controlled by the new primary NC; if any of the primary and standby NCs recovers from the fault after restart, the new standby NC joins the DDC cluster; if the NC network fault is recovered, the primary NC and the new primary NC are merged into a dual-master, and the primary NC joins the DDC cluster as the new standby NC after restart, and the standby NC joins the DDC cluster as the new standby NC after restart.

[0094] In this way, in the scenario where all NCs in the control plane fail, the data plane can continue to work normally under the management of the vNC container. Moreover, 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, it also solves the problem in the existing DDC cluster that a control plane failure will cause the data plane to be unavailable, and also make the entire cluster unavailable.

[0095] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A communication system, characterized in that: The communication system includes a primary and standby NC and a plurality of LCs, each NC runs an NC container, the plurality of LCs include a first type LC, and each first type LC runs a vNC container; When both the active and standby NC containers in the active and standby NC fail or the NC network where the active and standby NCs are located fails, a vNC container is selected from multiple vNC containers as a new active NC, and the new active NC manages and controls the DDC cluster; If any of the active and standby NCs recovers after restart, the new standby NC joins the DDC cluster; If the NC network failure is recovered, the main NC and the new main NC are merged, and after the main NC is restarted, it joins the DDC cluster as a new standby NC, and after the standby NC is restarted, it joins the DDC cluster as a new standby NC.

2. The communication system according to claim 1, characterized in that After each LC is started, it sends a registration message to the master NC, each registration message includes the MAC address and device serial number of the LC; After receiving each registration message, the master NC sorts the receiving time of each registration message according to the order of receiving each registration message; According to the sorting result, determine the first registration message whose receiving time is the first and the second registration message whose receiving time is the second, and determine the first LC that sends the first registration message and the second LC that sends the second registration message; The master NC sends a first ACK message to the first LC, the first ACK message includes a configuration tag, a first DADDR and a first CADDR, and sends a second ACK message to the second LC, the second ACK message includes the configuration tag, a second DADDR and a second CADDR; The first LC locally configures and starts the vNC container according to the configuration tag, the first DADDR, and the first CADDR; The second LC locally configures and starts the vNC container according to the configuration tag, the second DADDR, and the second CADDR.

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

4. The communication system according to claim 2 or 3, characterized in that: 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 in the DDC cluster, where the first notification message includes an address attribute of each vNC container.

5. The communication system according to claim 2, characterized in that: When the main NC determines that the first LC or the second LC fails, determining, according to the sorting result, a third registration message with a third receiving time, and determining a third LC that sends the third registration message; The master NC sends a second notification message to the third LC, where the second notification message includes a configuration tag, a fourth DADDR, and a third CADDR; The third LC locally configures and starts the vNC container according to the configuration tag, the fourth DADDR, and the third CADDR.

6. The communication system according to claim 5, characterized in that: 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, where the third notification message includes an address attribute of each vNC container.

7. The communication system according to claim 1, characterized in that: The new master NC sends a synchronization message to each new standby NC, wherein the synchronization message includes data to be synchronized; When receiving the fourth ACK message sent by each new standby NC, the new master NC restarts the vNC container where it is located; Each new standby NC elects a new master NC again, and the elected new master NC manages and controls the DDC cluster; The restarted vNC container joins the DDC cluster again as a new standby NC.

8. The communication system according to claim 1, characterized in that: The main NC and the new main NC perform dual master merging, specifically including: The main NC and the new main NC both periodically send heartbeat messages; When the master NC receives the heartbeat message sent by the new master NC, it is determined that there are two masters in the DDC cluster; The main NC performs a restart operation.

9. The communication system according to any one of claims 2 to 4, characterized in that: The address attribute of the vNC container includes the DADDR and 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.

10. The communication system according to claim 7, characterized in that: The CADDR of the main NC container serving as the new main NC is the minimum CADDR value of multiple NC containers and / or the minimum CADDR value of multiple vNC containers; or; The CADDR of the main vNC container serving as the new main NC is the minimum CADDR value of multiple NC containers and / or is the minimum CADDR value of multiple vNC containers.

Images