CN106657355B - Cluster management method and device - Google Patents
Cluster management method and device Download PDFInfo
- Publication number
- CN106657355B CN106657355B CN201611245816.6A CN201611245816A CN106657355B CN 106657355 B CN106657355 B CN 106657355B CN 201611245816 A CN201611245816 A CN 201611245816A CN 106657355 B CN106657355 B CN 106657355B
- Authority
- CN
- China
- Prior art keywords
- cluster
- slave
- slave device
- master
- indication bit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
- H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
- H04L67/1048—Departure or maintenance mechanisms
Abstract
A cluster management method and equipment are applied to a cluster, the cluster comprises a master device and a slave device, and the method comprises the following steps: when a protocol channel between the master device and the slave device fails, the slave device is switched to a master device role; the slave device sends the cluster detection message to the master device through a data channel; after receiving a cluster response message sent by the master device, the slave device exits the cluster according to the cluster response message; the slave device closes the port of the slave device. By adopting the scheme, the phenomenon that BGP of the master equipment and the slave equipment vibrates repeatedly can be avoided.
Description
Technical Field
The present invention relates to the field of virtual cluster technologies, and in particular, to a cluster management method and device.
Background
The virtual machine cluster technology can reduce the operation cost, expand the number of single-node ports and the like, and is increasingly applied to router products at present; such as an enterprise network scenario (e.g., radio, commercial bank, thailand PEA, UK, etc.). When the virtual cluster technology is used, after a protocol channel between a master device and a slave device in a cluster fails, a situation of dual master devices may exist.
Due to the presence of the two master devices, the two master devices can establish a Border Gateway Protocol (BGP) neighbor with the upstream device and the downstream device of the cluster where the two master devices are currently located, so that a BGP Protocol repeatedly oscillates, and routing oscillation of networking is affected, so that traffic of a node cannot be normally forwarded.
Disclosure of Invention
The invention provides a cluster management method and cluster management equipment, which can solve the problem that BGP protocols of main equipment and slave equipment in the prior art vibrate repeatedly.
A first aspect provides a cluster management method, which is applicable to a cluster that is a group of mutually independent computers interconnected through a network by a protocol, and that forms a network and is managed in a single system mode. The devices in the cluster can share resources, share cost, share channel devices and services and the like. The cluster comprises a master device and at least one slave device, wherein the master device is used for controlling the cluster. The slave device is used for collecting data. The master device and the slave device can perform operations such as traffic forwarding and the like with each device which is in uplink and downlink communication connection with the master device and the slave device. When the protocol channel is normal, the device role of the master device is the master device role, and the device role of the slave device is the slave device role. The method comprises the following steps:
when a protocol channel between the master device and the slave device fails, the slave device is switched to a master device role, then the slave device sends a cluster detection message to the master device through a data channel, and after receiving a cluster response message sent by the master device, the slave device can determine that the cluster where the slave device is located is distributed, and then the slave device can quit the cluster according to the cluster response message.
And after exiting the cluster in which the slave device is positioned, the slave device closes the port of the slave device. The closed ports include ge0/0/0, loopback interface (loopback), virtual local area network interface (vlan), service port and the like.
Compared with the existing mechanism, in the invention, after the protocol channel fails, the slave device which is converted into the role of the master device sends the cluster detection message to the master device through the data channel, and then forcibly closes the port of the slave device after receiving the cluster response message sent by the master device, thereby isolating the original slave device. The original main equipment is not processed at all, and the protocol between the original main equipment and the uplink and downlink equipment of the original main equipment can be established, so that the original service data can be continuously forwarded, the flow forwarding of the original main equipment cannot be influenced, and the phenomenon that BGP (border gateway protocol) of the main equipment and the slave equipment repeatedly vibrates is avoided.
In some possible designs, the cluster detection packet includes a first cluster detection field, and the cluster reply packet includes a second cluster detection field.
The first cluster detection field comprises a first indication bit, a second indication bit and a third indication bit, the first indication bit in the first cluster detection field is used for indicating the device role of the slave device sending the cluster detection message before the protocol channel failure, the second indication bit in the first cluster detection field indicates the device role of the slave device sending the cluster detection message after the protocol channel failure, and the third indication bit in the first cluster detection field indicates the slave device to apply for closing the port of the slave device.
The second cluster detection fields all include a first indication bit, a second indication bit and a third indication bit, the first indication bit in the second cluster detection fields is used for indicating the device role of the master device sending the cluster response message before the protocol channel failure, the second indication bit in the second cluster detection fields indicates the device role of the master device sending the cluster response message after the protocol channel failure, and the third indication bit in the second cluster detection fields indicates that the slave device is allowed to close the port of the slave device.
In some possible designs, when more than two slave devices are included in the cluster and a protocol channel between a master device and at least one slave device fails, the method further comprises:
and the slave equipment with the fault protocol channel between the two or more slave equipment and the master equipment receives the cluster detection message sent by the master equipment and returns a cluster response message to the master equipment, so that the master equipment closes the port of the master equipment.
For example, after a protocol channel between a master device and at least one slave device fails, if the number of current master devices is smaller than the number of slave devices in the cluster system, the original master device may send a cluster detection packet to the slave device that is converted into the master device in each slave device, and the original master device may down. After receiving the cluster detection message sent by the master device, each slave device converted into the master device role returns a cluster response message to the master device, so that the original master device considers that the cluster is disassembled, and each port of the master device is closed.
If the number of the master devices is equal to the number of the slave devices in the cluster system, and a protocol channel between the master device and the slave device fails, the slave device generally preferentially sends a cluster detection message, the original master device returns a cluster response message, and the slave device closes its port after receiving the cluster response message returned by the master device. In other embodiments, the master device may also send a cluster detection message to the slave device, and then close its own port after receiving a cluster response message returned by the slave device.
In some possible designs, after the protocol channel between the slave device and the master device is recovered from the failure, the slave device whose current device role is the master device role is recovered to the slave device role;
the slave device opens the ports of the slave device, and the slave device can automatically release the down state of each port and can also manually release the down state of each port through a command line.
In some possible designs, after the slave device closes the port of the slave device, the method further includes:
the slave device configures the port state of each closed port of the slave device to a down state, so that after the protocol channel between the slave device and the master device is recovered from a failure, the slave device with the current device role as the master device role is recovered to the slave device role, and then the slave device opens the port of the slave device. In the invention, the slave equipment can automatically release the down state of each port and can manually release the down state of each port through a command line.
A second aspect of the present invention provides a cluster device having a function of implementing the cluster management method provided corresponding to the first aspect described above. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions, which may be software and/or hardware.
In one possible design, a cluster device is applied to a cluster, the cluster including a master device and a slave device, the cluster device including:
the processing module is used for converting the slave equipment into a master equipment role after a protocol channel between the master equipment and the slave equipment fails;
the receiving and sending module is used for sending the cluster detection message to the main equipment through a data channel;
the processing module is further configured to quit the cluster according to the cluster response message after receiving the cluster response message sent by the master device through the transceiver module; and closing the port of the slave device.
Optionally, the cluster detection packet includes a first cluster detection field, and the cluster response packet includes a second cluster detection field.
In some possible designs, the first trunking detection field includes a first indication bit, a second indication bit, and a third indication bit, the first indication bit in the first trunking detection field is used to indicate a device role of a slave device that sends the trunking detection packet before the protocol path failure, the second indication bit in the first trunking detection field indicates a device role of the slave device that sends the trunking detection packet after the protocol path failure, and the third indication bit in the first trunking detection field indicates that the slave device applies for closing a port of the slave device.
In some possible designs, the second trunking detection field includes a first indication bit, a second indication bit, and a third indication bit, where the first indication bit in the second trunking detection field is used to indicate a device role of a master device that sends the trunking response packet before the protocol path failure, the second indication bit in the second trunking detection field indicates a device role of a master device that sends the trunking response packet after the protocol path failure, and the third indication bit in the second trunking detection field indicates that a slave device is permitted to close a port of the slave device.
In some possible designs, when more than two slave devices are included in the cluster, the transceiver module is further to:
and receiving a cluster detection message sent by the main equipment, and returning a cluster response message to the main equipment so that the main equipment closes the port of the main equipment.
In some possible designs, the processing module is further to:
when the protocol channel between the slave equipment and the master equipment is recovered from the fault, recovering the current master equipment role of the slave equipment to the slave equipment role;
opening a port of the slave device.
In some possible designs, the processing module is further configured to, after the slave device closes the port of the slave device:
configuring a port state of each closed port of the slave device to a down state.
In one possible design, a cluster device is applied to a cluster, the cluster including a master device and a slave device, the cluster device including:
at least one processor, memory, and transceiver;
wherein the memory is configured to store program code, and the processor is configured to call the program code in the memory to:
when a protocol channel between the master device and the slave device fails, the slave device is switched to a master device role;
sending the cluster detection message to the main equipment through a data channel by a transceiver;
after receiving a cluster response message sent by the master device through the transceiver, exiting the cluster according to the cluster response message; and closing the port of the slave device.
Compared with the prior art, in the scheme provided by the invention, after the protocol channel fails, the slave device which is converted into the role of the master device sends the cluster detection message to the master device through the data channel, and then forcibly closes the port of the slave device after receiving the cluster response message sent by the master device, thereby isolating the original slave device. The original main equipment is not processed at all, and the protocol between the original main equipment and the uplink and downlink equipment of the original main equipment can be established, so that the original service data can be continuously forwarded, the flow forwarding of the original main equipment cannot be influenced, and the phenomenon that the BGP protocol of the main equipment and the BGP protocol of the slave equipment repeatedly vibrate is avoided. Therefore, the node is guaranteed to be available with one device, and the influence on the current network is extremely small.
Drawings
Fig. 1 is a schematic diagram of a network topology of a cluster in this embodiment;
FIG. 2 is a flowchart illustrating a cluster management method according to the present embodiment;
fig. 3 is another schematic flow chart of the cluster management method in this embodiment;
fig. 4 is a schematic structural diagram of a cluster device in this embodiment;
fig. 5 is a schematic structural diagram of an entity apparatus for executing the cluster management method in this embodiment.
Detailed Description
The terms "first," "second," and the like in the description and in the claims, and in the drawings described above, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprise," "include," and "have," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules expressly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus, the division of modules herein shown is merely a logical division and may be implemented in a practical application in a different manner, such that multiple modules may be combined or integrated into another system or certain features may be omitted or not implemented, and such that mutual or direct coupling or communicative coupling between the modules shown or discussed may be through interfaces, and indirect coupling or communicative coupling between the modules may be electrical or other similar, are not intended to be limiting herein. Furthermore, the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in a plurality of circuit modules, and some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present invention.
The embodiment of the invention provides a cluster management method and equipment, which are mainly used in the technical field of virtual clusters, for example, the cluster management method and equipment are applied to a cluster system, and can avoid repeated oscillation of BGP (Border gateway protocol) protocols of a master device and a slave device and ensure normal forwarding of traffic of nodes. The details will be described below.
The cluster in the present invention refers to a group of mutually independent computers interconnected through a network by a protocol, which form a network and are managed in a single system mode. The devices in the cluster can share resources, share cost, share channel devices and services, and the like, and can be a virtual cluster which is a single logic core router consisting of a plurality of single machine frames. The cluster may include a master and at least one slave, both of which may be laid out in subracks. The master device is used for controlling the cluster in which the master device is located. The slave device is used for collecting data. The master device and the slave device can perform operations such as traffic forwarding and the like with each device which is in uplink and downlink communication connection with the master device and the slave device. As shown in fig. 1, fig. 1 is a schematic diagram of a network topology structure of a cluster, where a master device (device a) and a slave device (device B) are deployed in the same network through a protocol, and their respective physical locations are not limited. In fig. 1, device C and device D are uplink and downlink devices of the cluster, i.e., BGP neighbors.
A protocol channel and a data channel exist between the master equipment and the slave equipment, the protocol channel refers to a communication link which is in communication connection between cluster machine frames through a master control board interface, and the protocol channel can be used for transmitting protocol messages in a cluster. The data channel refers to a link which is in communication connection between the cluster machine frames through the service control board interface, and the data channel can be used for transmitting data messages between the virtual cluster machine frames.
Since the slave device may be changed into the role of the master device after the protocol channel fails, a phenomenon that more than two master devices appear in one cluster occurs, and meanwhile, the device with the protocol channel failure exits the cluster where the protocol channel failed before the failure. In order to solve the above technical problems, embodiments of the present invention mainly provide the following technical solutions:
after the slave device is converted into the role of the master device, the slave device sends the cluster detection message to the original master device through the data channel, and then forcibly closes the port of the slave device after receiving the cluster response message sent by the original master device, thereby isolating the slave device.
Through the technical scheme, the problem that the BGP protocol vibrates repeatedly when more than two main devices appear can be avoided, and normal forwarding of the flow of each node can be ensured.
Referring to fig. 2, the following illustrates a cluster management method according to the present invention, where the method is applied to a cluster, where the cluster includes a master device and a slave device, a protocol channel and a data channel exist between the master device and the slave device, the number of the slave devices in a cluster may include more than one, and in a normal case of the protocol channel, there is only one master device in a cluster. The method comprises the following steps:
101. and when the protocol channel between the master device and the slave device fails, the slave device is switched to the master device role.
102. And the slave equipment sends the cluster detection message to the master equipment through a data channel.
Wherein the cluster detection packet includes a first cluster detection field. The first cluster detection field comprises a first indication bit, a second indication bit and a third indication bit, the first indication bit in the first cluster detection field is used for indicating that slave equipment sending the cluster detection message is in an equipment role before the protocol channel failure, the second indication bit in the first cluster detection field indicates that the slave equipment sending the cluster detection message is in an equipment role after the protocol channel failure, and the third indication bit in the first cluster detection field indicates that the slave equipment applies for closing a port of the slave equipment.
In some application scenarios, the cluster detection packet may adopt an extension of a uniform link layer Management (CLM for short) and fiber link layer Management (FLM for short) link layer protocol, and a first cluster detection field is added, where the first cluster detection field occupies 2 bytes, and the format is defined as follows: the first 1-2 bits are first indication bits for indicating the device role of the cluster device before the protocol channel failure, where 01 indicates the slave role (slave) and 10 indicates the master role (master). Bits 3-4 are second indication bits for indicating the current device role of the cluster device, where 01 indicates the slave role (slave) and 10 indicates the master role (master). The 5 th to 6 th bits indicate whether or not to apply for down, wherein 01 indicates to apply for down. For example, in a cluster detection message, the first cluster detection field may be shown as 0110010000000000.
103. And after receiving the cluster detection message, the master device sends a cluster response message to the slave device.
Wherein the cluster reply message includes a second cluster detection field. The second cluster detection fields all include a first indication bit, a second indication bit and a third indication bit, the first indication bit in the second cluster detection fields is used for indicating the device role of the master device sending the cluster response message before the protocol channel failure, the second indication bit in the second cluster detection fields indicates the device role of the master device sending the cluster response message after the protocol channel failure, and the third indication bit in the second cluster detection fields indicates that the slave device is allowed to close the port of the slave device.
Correspondingly, the above-mentioned cluster response message may also adopt extension of CLM/FLM link layer protocol, and add a second cluster detection field, where the second cluster detection field occupies 2 bytes, and the defined format is as follows: the first 1-2 bits represent a first indication bit for indicating the device role of the cluster device before the protocol channel failure, where 01 represents the slave role (slave) and 10 represents the master role (master). Bits 3-4 represent a second indication bit for indicating the current device role of the cluster device, wherein 01 represents the slave role (slave) and 10 represents the master role (master). Bits 5-6 indicate whether or not to apply for down, where 10 indicates to approve down. For example, in the cluster reply message, the second cluster detection field may be shown as 1010110000000000.
As for the cluster detection packet and the cluster response packet, the communication format of the cluster detection packet and the cluster response packet may be one of the following table 1, or may be obtained by transforming the communication format of the cluster detection packet and the cluster response packet based on the following table 1, and the specific invention is not limited thereto.
TABLE 1
The specific meanings of the elements in the above table 1 can be referred to in the following table 2.
TABLE 2
In table 2, CMD refers to cluster multi-frame detection (CMD for short), and may be used to detect a protocol for resolving a cluster, where CMD is a specific implementation manner of a cluster detection message or a cluster response message, and may have other names, and the present invention is not limited in particular.
104. And after receiving the cluster response message sent by the master device, the slave device exits the cluster according to the cluster response message.
105. The slave device closes the port of the slave device.
The closed ports include ge0/0/0, a loopback interface (loopback), a virtual local area network interface (vlan), a service port, and the like. After the ports of the slave device are closed, the slave device may further configure the port state of each closed port of the slave device to a down state, so that after the protocol channel between the slave device and the master device is recovered due to a failure, the slave device whose current device role is the master device role is recovered to the slave device role, and then the slave device opens the port of the slave device. In the invention, the slave equipment can automatically release the down state of each port and can manually release the down state of each port through a command line.
Compared with the existing mechanism, in the embodiment of the invention, after a protocol channel fails, the slave device which is converted into the role of the master device sends the cluster detection message to the master device through the data channel, and then forcibly closes the port of the slave device after receiving the cluster response message sent by the master device, thereby isolating the original slave device. The original main equipment is not processed at all, and the protocol between the original main equipment and the uplink and downlink equipment of the original main equipment can be established, so that the original service data can be continuously forwarded, the flow forwarding of the original main equipment cannot be influenced, and the phenomenon that BGP (border gateway protocol) of the main equipment and the slave equipment repeatedly vibrates is avoided.
In other words, when more than two masters are detected, the original slave can be isolated by forcibly closing the port of the original slave. In the above steps 104 and 105, the original master device may continue to forward the original service data without performing any processing on the original master device, so that the traffic forwarding of the original master device is not affected. Therefore, the node is guaranteed to be available with one device, and the influence on the current network is extremely small. Meanwhile, the influence of more than two main devices on the network can be further reduced to millisecond level through the characteristic of linkage BFD.
Optionally, in some inventive embodiments, when more than two slave devices are included in the cluster, the protocol channel between the master device and at least one slave device fails. Since the number of the original slave devices is greater than that of the original master device, in this case, the following rule may be set:
the cluster detection message may be sent by the master device to each slave device in the cluster (including the slave device that is converted to the master device role and/or the slave device that is still in the slave device role). Each slave device receives the cluster detection message sent by the master device and returns a cluster response message to the master device, so that the original master device considers that the cluster is already dispersed, and each port of the master device is closed (the same as or similar to the port of the partial closed slave device).
It should be noted that, when the numbers of the master device and the slave device in the cluster are the same, if a protocol channel between the master device and the slave device fails, the slave device generally preferentially sends a cluster detection message to the master device, and then the slave device closes its port after receiving a cluster response message returned by the master device. In other embodiments, the master device may also send a cluster detection message to the slave device, and then close its own port after receiving a cluster response message returned by the slave device.
For convenience of understanding, the cluster management method of the present invention is illustrated below with reference to a specific application scenario: as shown in fig. 3, the cluster includes a Master subrack (Master) and a Slave subrack (Slave) between which protocol channels (connected via #17 ports and #18 ports) and data channels (connected via #11 ports and #12 ports, for example) are established. After the protocol channel fails, the Slave sends a cluster detection message to the Master through the data channel, and then the Master returns a cluster response message to the Slave. After the Slave receives the cluster response message, if the cluster is considered to be disassembled, the port of the cluster is closed, and the cluster exits.
In the above description, a cluster management method according to the present invention is described, and cluster devices executing the cluster management method are described below.
Referring to fig. 4, a cluster device 40 is described, where the cluster device is applied to a cluster, the cluster includes a master device and a slave device, and the cluster device 40 includes:
a processing module 401, configured to convert the slave device into a master device role after a protocol channel between the master device and the slave device fails;
a transceiver module 402, configured to send a cluster detection packet to the master device through a data channel;
the processing module 401 is further configured to exit the cluster according to the cluster response message after receiving the cluster response message sent by the master device through the transceiver module 402; and closing the port of the slave device.
In the embodiment of the present invention, after a protocol channel fails, the processing module 401 converts the slave device into a master device role, the transceiver module 402 sends a cluster detection message to the master device through a data channel, and then after receiving a cluster response message sent by the master device, the processing module 401 forcibly closes a port of the slave device, thereby isolating the original slave device. The original main equipment is not processed, and the original main equipment can continue to forward the original service data, so that the flow forwarding of the original main equipment is not influenced, and the phenomenon that BGP of the main equipment and the slave equipment repeatedly vibrates is avoided. Therefore, the node is guaranteed to be available with one device, and the influence on the current network is extremely small.
Optionally, the cluster detection packet includes a first cluster detection field, and the cluster response packet includes a second cluster detection field.
Optionally, in some embodiments of the present invention, the first cluster detection field includes a first indication bit, a second indication bit, and a third indication bit, where the first indication bit in the first cluster detection field is used to indicate a device role of a slave device that sends the cluster detection packet before the protocol channel failure, the second indication bit in the first cluster detection field indicates a device role of the slave device that sends the cluster detection packet after the protocol channel failure, and the third indication bit in the first cluster detection field indicates that the slave device applies for closing a port of the slave device.
Optionally, in some embodiments of the present invention, the second cluster detection field includes a first indication bit, a second indication bit, and a third indication bit, where the first indication bit in the second cluster detection field is used to indicate a device role of the master device that sends the cluster response packet before the protocol path failure, the second indication bit in the second cluster detection field indicates a device role of the master device that sends the cluster response packet after the protocol path failure, and the third indication bit in the second cluster detection field indicates that the slave device is permitted to close the port of the slave device.
Optionally, in some inventive embodiments, when more than two slave devices are included in the cluster, the transceiver module 402 is further configured to:
and receiving a cluster detection message sent by the main equipment, and returning a cluster response message to the main equipment so that the main equipment closes the port of the main equipment.
Optionally, in some embodiments of the present invention, the processing module 401 is further configured to:
when the protocol channel between the slave equipment and the master equipment is recovered from the fault, recovering the current master equipment role of the slave equipment to the slave equipment role;
opening a port of the slave device.
Optionally, in some embodiments of the present invention, after the slave device closes the port of the slave device, the processing module 401 is further configured to:
configuring a port state of each closed port of the slave device to a down state.
It should be noted that, in the embodiment corresponding to fig. 4 of the present invention, the entity device corresponding to the transceiver module may be a transceiver, and the entity device corresponding to the processing module may be a processor. The apparatus shown in fig. 4 may have a structure as shown in fig. 5, when one of the apparatuses has the structure as shown in fig. 5, the processor and the transceiver in fig. 5 implement the same or similar functions of the processing module and the transceiver module provided in the apparatus embodiment corresponding to the apparatus, and the memory in fig. 5 stores program codes that the processor needs to call when executing the cluster management method.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the module described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and in actual implementation, there may be other divisions, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other media capable of storing program codes.
The technical solutions provided by the present invention are described in detail above, and the principle and the implementation of the present invention are explained in this document by applying specific examples, and the descriptions of the above examples are only used to help understanding the method and the core idea of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (6)
1. A cluster management method is applied to a cluster, wherein the cluster comprises a master device and a slave device, and the method comprises the following steps:
when a protocol channel between the master device and the slave device fails, the slave device is switched to a master device role;
the slave device sends the cluster detection message to the master device through a data channel;
after receiving a cluster response message sent by the master device, the slave device exits the cluster according to the cluster response message;
the slave device closes a port of the slave device;
the cluster detection message comprises a first cluster detection field, and the cluster response message comprises a second cluster detection field;
the first cluster detection field includes a first indication bit, a second indication bit and a third indication bit, the first indication bit in the first cluster detection field is used to indicate a device role of a slave device sending the cluster detection packet before the protocol channel failure, the second indication bit in the first cluster detection field indicates a device role of the slave device sending the cluster detection packet after the protocol channel failure, and the third indication bit in the first cluster detection field indicates that the slave device applies for closing a port of the slave device;
the second cluster detection field includes a first indication bit, a second indication bit and a third indication bit, the first indication bit in the second cluster detection field is used to indicate a device role of the master device sending the cluster response packet before the protocol channel failure, the second indication bit in the second cluster detection field indicates a device role of the master device sending the cluster response packet after the protocol channel failure, and the third indication bit in the second cluster detection field indicates that the slave device agrees to close a port of the slave device;
when more than two slave devices are included in the cluster, the method further comprises:
and the slave equipment with the fault protocol channel between the two or more slave equipment and the master equipment receives the cluster detection message sent by the master equipment and returns a cluster response message to the master equipment, so that the master equipment closes the port of the master equipment.
2. The method of claim 1, further comprising:
when the protocol channel between the slave device and the master device is recovered from the fault, the slave device with the current device role as the master device role is recovered to the slave device role;
the slave device opens a port of the slave device.
3. The method of claim 1, wherein after the slave device closes the port of the slave device, the method further comprises:
the slave device configures a port state of each closed port of the slave device to a down state.
4. A cluster device, wherein the cluster device is applied to a cluster, wherein the cluster comprises a master device and a slave device, and wherein the cluster device comprises:
the processing module is used for converting the slave equipment into a master equipment role after a protocol channel between the master equipment and the slave equipment fails;
the receiving and sending module is used for sending the cluster detection message to the main equipment through a data channel;
the processing module is further configured to quit the cluster according to the cluster response message after receiving the cluster response message sent by the master device through the transceiver module; and closing the port of the slave device;
the cluster detection message comprises a first cluster detection field, and the cluster response message comprises a second cluster detection field;
the first cluster detection field includes a first indication bit, a second indication bit and a third indication bit, the first indication bit in the first cluster detection field is used to indicate a device role of a slave device sending the cluster detection packet before the protocol channel failure, the second indication bit in the first cluster detection field indicates a device role of the slave device sending the cluster detection packet after the protocol channel failure, and the third indication bit in the first cluster detection field indicates that the slave device applies for closing a port of the slave device;
the second cluster detection field includes a first indication bit, a second indication bit and a third indication bit, the first indication bit in the second cluster detection field is used to indicate a device role of the master device sending the cluster response packet before the protocol channel failure, the second indication bit in the second cluster detection field indicates a device role of the master device sending the cluster response packet after the protocol channel failure, and the third indication bit in the second cluster detection field indicates that the slave device agrees to close a port of the slave device;
when more than two slave devices are included in the cluster, the transceiver module is further configured to:
and receiving a cluster detection message sent by the main equipment, and returning a cluster response message to the main equipment so that the main equipment closes the port of the main equipment.
5. The cluster device of claim 4, wherein the processing module is further configured to:
when the protocol channel between the slave equipment and the master equipment is recovered from the fault, recovering the current master equipment role of the slave equipment to the slave equipment role;
opening a port of the slave device.
6. The cluster device of claim 4, wherein the processing module, after the slave device closes the port of the slave device, is further configured to:
configuring a port state of each closed port of the slave device to a down state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611245816.6A CN106657355B (en) | 2016-12-29 | 2016-12-29 | Cluster management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611245816.6A CN106657355B (en) | 2016-12-29 | 2016-12-29 | Cluster management method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106657355A CN106657355A (en) | 2017-05-10 |
| CN106657355B true CN106657355B (en) | 2020-10-16 |
Family
ID=58835941
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611245816.6A Expired - Fee Related CN106657355B (en) | 2016-12-29 | 2016-12-29 | Cluster management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106657355B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107579918B (en) * | 2017-08-15 | 2020-05-12 | 新华三技术有限公司 | Method and device for maintaining neighbor relation |
| CN112737944B (en) * | 2020-12-25 | 2022-07-08 | 浪潮思科网络科技有限公司 | Bfd-based peer-link state detection method, device and medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101309185A (en) * | 2008-07-16 | 2008-11-19 | 杭州华三通信技术有限公司 | Processing method of multi-host apparatus in stacking system and stacking member equipment |
Family Cites Families (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6670882B1 (en) * | 1999-07-28 | 2003-12-30 | Cisco Technology, Inc. | Multi drop stack bus detector method and apparatus |
| CN101610182B (en) * | 2009-06-26 | 2011-09-07 | 杭州华三通信技术有限公司 | Multi-primary apparatus conflict detection method in stack and stack member apparatus |
| CN101714932B (en) * | 2009-12-03 | 2012-01-04 | 杭州华三通信技术有限公司 | MAD testing method and device for IRF stacker |
| US8634662B2 (en) * | 2010-08-25 | 2014-01-21 | Apple Inc. | Detecting recurring events in consumer image collections |
| CN102457402B (en) * | 2010-10-14 | 2014-07-16 | 杭州华三通信技术有限公司 | Method for detecting multiple active equipment conflict and apparatus thereof |
| CN102209008A (en) * | 2011-05-18 | 2011-10-05 | 杭州华三通信技术有限公司 | Multi-activation detection method and device used for intelligent elastic framework |
| CN102355366B (en) * | 2011-08-24 | 2014-12-10 | 杭州华三通信技术有限公司 | Member-stacking device and method for managing member-stacking device at split stacking moment |
| CN102315975B (en) * | 2011-10-17 | 2014-03-19 | 杭州华三通信技术有限公司 | Fault processing method based on intelligent resilient framework (IRF) system and equipment thereof |
| CN102724069B (en) * | 2012-06-14 | 2015-04-22 | 福建星网锐捷网络有限公司 | Collision detection method, device and network device of dual-master device in thermal staking system |
| CN103001831B (en) * | 2012-12-19 | 2016-03-09 | 迈普通信技术股份有限公司 | A kind of system and method testing many activation detection perform |
| CN103166811B (en) * | 2013-03-06 | 2016-12-28 | 杭州华三通信技术有限公司 | A kind of MAD detection method and equipment |
| CN103560955B (en) * | 2013-10-24 | 2016-09-28 | 华为技术有限公司 | Redundance unit changing method and device |
| CN103825766B (en) * | 2014-02-28 | 2017-04-12 | 杭州华三通信技术有限公司 | Device and method for detecting BFD links |
-
2016
- 2016-12-29 CN CN201611245816.6A patent/CN106657355B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101309185A (en) * | 2008-07-16 | 2008-11-19 | 杭州华三通信技术有限公司 | Processing method of multi-host apparatus in stacking system and stacking member equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106657355A (en) | 2017-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11223514B2 (en) | Method and system of a dynamic high-availability mode based on current wide area network connectivity | |
| CN114124806B (en) | Method and equipment for generating route | |
| EP2553886B1 (en) | Aggregating data traffic from access domains | |
| EP2731313A1 (en) | Distributed cluster processing system and message processing method thereof | |
| EP4047888A1 (en) | Method for issuing oam configuration information and control node | |
| CN103944828A (en) | Method and equipment for transmitting protocol messages | |
| CN107615710B (en) | Direct reply actions in SDN switches | |
| US11799767B2 (en) | Detecting and communicating with silent hosts in software-defined networks | |
| CN110493069B (en) | Fault detection method and device, SDN controller and forwarding equipment | |
| CN104869057A (en) | OpeFlow switch graceful restart processing method, device and OpeFlow controller | |
| CN109660441A (en) | The method and device of multicast replication in Overlay network | |
| US20170005947A1 (en) | Systems and methods to create highly scalable network services | |
| CN101631060B (en) | Method and device for managing edge port | |
| EP3817293B1 (en) | Bulk discovery of devices behind a network address translation device | |
| CN106657355B (en) | Cluster management method and device | |
| KR102455367B1 (en) | Packet transmission method, apparatus and system, and storage medium | |
| CN114257494A (en) | Method, equipment and system for realizing service path detection | |
| CN111327524B (en) | Flow forwarding method and system, SDN controller and computer readable storage medium | |
| CN110830598B (en) | Method and network equipment for establishing and transmitting interface address and alias in BGP (Border gateway protocol) session | |
| EP3079327B1 (en) | Information transmission method, device and system | |
| CN112751701B (en) | System, method and computer readable medium for managing network devices | |
| CN114401324A (en) | Message forwarding method, network equipment and system | |
| JP5889122B2 (en) | Control node and communication control method | |
| CN107659499B (en) | Routing method and forwarding equipment | |
| CN114629834B (en) | Communication method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20201016 Termination date: 20211229 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |