CN108337159B

CN108337159B - Port operation control method and device

Info

Publication number: CN108337159B
Application number: CN201810097373.3A
Authority: CN
Inventors: 刘永奎; 王伟
Original assignee: Hangzhou H3C Technologies Co Ltd
Current assignee: Hangzhou H3C Technologies Co Ltd
Priority date: 2018-01-31
Filing date: 2018-01-31
Publication date: 2021-05-28
Anticipated expiration: 2038-01-31
Also published as: CN108337159A

Abstract

The disclosure relates to a port operation control method and device. The first and second DR devices constitute a DRNI system, the first DR device being an IRF device, and the method for the second DR device includes: when a message from the first DR equipment is received, acquiring an identifier carried in the message and used for representing the running state of the IRF equipment serving as the first DR equipment; and according to the identification, carrying out operation control on the physical port of the second DR equipment receiving the message. The port operation control method and device can ensure that the problems of address conflict, loop and the like can not occur after the IRF device serving as the first DR device is split.

Description

Port operation control method and device

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method and an apparatus for controlling port operations.

Background

In the related art, DRNI (Distributed Resilient Network Interconnect) is a cross-device link aggregation technology, and two physical devices are virtualized into one device on an aggregation layer to implement cross-device link aggregation, thereby providing device-level redundancy protection and traffic load sharing. Two DR (distributed relay) devices in a DRNI typical networking form a DR system through ethernet link aggregation. Fig. 1 illustrates a schematic diagram of a DRNI networking in the related art. As shown in fig. 1, a device a and a device B share load and forward traffic together, and when one device fails, the traffic can be quickly switched to another device, thereby ensuring normal operation of a service.

In the related art, the DRNI defines several interface roles for each DR device: the DR interface is a two-layer aggregation interface for connecting the DR equipment and external equipment. And the DR interfaces connected with the same aggregation group of the DR equipment and the external equipment belong to the same DR group. As shown in fig. 1, the DR interface of device a and the DR interface of device B belong to the same DR group. IPP (Intra-Port, internal control link interface) is a two-layer aggregation interface that connects neighbor DR devices and is used for internal control. A DRCP (Distributed Relay Control Protocol) message may be established between the IPP ports and transmitted between the DR devices through an IPL (Intra-Portal Link). The neighbor state can be detected between DR devices through a Keepalive link.

Disclosure of Invention

In view of this, the present disclosure provides a method and an apparatus for controlling port operations to solve the problems of address conflicts and loops caused by the splitting of IRF devices serving as DR devices in the related art.

According to an aspect of the present disclosure, there is provided a port operation control method for a second DR device, the second DR device constituting a DRNI system, the first DR device being an IRF device, the method comprising:

when a message from the first DR equipment is received, acquiring an identifier carried in the message and used for representing the running state of the IRF equipment serving as the first DR equipment;

and according to the identification, carrying out operation control on the physical port of the second DR equipment receiving the message.

According to another aspect of the present disclosure, there is provided a port operation control method for a first DR device and a second DR device constituting a DRNI system, the first DR device being an IRF device, the method comprising:

generating a message carrying an identifier for indicating the state of the IRF device according to the state of the IRF device as the first DR device, wherein the identifier comprises a state value for indicating whether the IRF device fails;

and sending the message to a physical port corresponding to the IPP port of the second DR equipment and/or a physical port corresponding to a port of a Keepalive link of the second DR equipment, so that the second DR equipment performs operation control on the physical port of the second DR equipment receiving the message according to the identifier carried by the message.

According to another aspect of the present disclosure, there is provided a port operation control apparatus, a first DR device and a second DR device constituting a DRNI system, the first DR device being an IRF device, the apparatus being for the second DR device, including:

an identifier obtaining module, configured to obtain, when a packet from the first DR device is received, an identifier carried in the packet and used to indicate an operating state of the IRF device serving as the first DR device;

and the operation control module is used for carrying out operation control on the physical port of the second DR equipment receiving the message according to the identification.

According to another aspect of the present disclosure, there is provided a port operation control apparatus, a first DR device and a second DR device constituting a DRNI system, the first DR device being an IRF device, the apparatus being for the first DR device, including:

a message generating module, configured to generate, according to a state of the IRF device serving as the first DR device, a message carrying an identifier used to indicate the state of the IRF device, where the identifier includes a state value used to indicate whether the IRF device fails;

and the message sending module is used for sending the message to a physical port corresponding to the IPP port of the second DR equipment and/or a physical port corresponding to the port of the Keepalive link of the second DR equipment, so that the second DR equipment performs operation control on the physical port of the second DR equipment receiving the message according to the identifier carried by the message.

According to the port operation control method and device, the first DR equipment and the second DR equipment form a DRNI system, the first DR equipment is IRF equipment, and when the second DR equipment receives a message from the first DR equipment, the second DR equipment performs operation control on a port of the DR equipment receiving the message through an identifier which is carried in the message and used for representing the state of the IRF equipment serving as the first DR equipment, so that the problems of address conflict, loops and the like can be avoided after the IRF equipment serving as the first DR equipment is split.

Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments, features, and aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

Fig. 1 illustrates a schematic diagram of a DRNI networking in the related art.

Fig. 2 shows a schematic diagram of a DRNI network formed by IRF devices in the related art.

Fig. 3 illustrates a schematic diagram of a port operation control method according to an embodiment of the present disclosure.

Fig. 4 illustrates a schematic diagram of a port operation control method according to an embodiment of the present disclosure.

Fig. 5 shows a schematic diagram of a DRNI networking formed by IRF devices according to an embodiment of the present disclosure.

Fig. 6 illustrates a block diagram of a port operation control device according to an embodiment of the present disclosure.

Fig. 7 illustrates a block diagram of a port operation control device according to an embodiment of the present disclosure.

Fig. 8 is a block diagram illustrating a port operation control device 900 according to an exemplary embodiment.

Detailed Description

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.

In the related art, the core idea of the IRF (Intelligent Resilient Framework) is to connect multiple devices together, perform necessary configuration, and virtualize the devices into one device. The virtualization technology can be used for integrating hardware resources and software processing capacity of a plurality of devices, and realizing cooperative work, unified management and uninterrupted maintenance of the plurality of devices.

An IRF link failure may cause one IRF device to become new IRF devices. These IRF devices have three-layer configurations such as the same IP (Internet Protocol) address, which may cause problems such as address collision and loop, resulting in an expansion of failures in the network. In order to improve the usability of the system, a Detection and processing mechanism MAD (Multi-Active Detection) is provided. After the IRF equipment is split, the MAD detection can detect that a plurality of IRF equipment exist in the network at the same time, and corresponding processing is carried out to reduce the influence of the IRF equipment splitting on the service. As described below, MAD detection mainly provides the following functions:

(1) and (3) splitting detection: whether a plurality of IRF devices exist in the network is detected through ARP (Address Resolution Protocol), ND (Neighbor Discovery Protocol), LACP (Link Aggregation Control Protocol), or BFD (Bidirectional Forwarding Detection). In other words, the MAD detection method supported by the IRF device includes: ARP MAD detection, ND MAD detection, LACP MAD detection and BFD MAD detection.

(2) And (3) conflict processing: after the IRF device is split, through a split detection mechanism, the IRF device may detect that there are other IRF devices in an Active state (Active state, that is, indicating that the IRF device is in a normal operating state) in the network. For ARP MAD detection/ND MAD detection/BFD MAD detection, conflict processing can directly enable IRF equipment with small member number of main equipment to be in an active state and continue to work normally; other IRF devices migrate to the disabled state (Recovery state). For the LACP MAD detection, the collision processing can firstly compare the number of member devices in two IRF devices, and the IRF devices with large number are in an active state and continue to work; a small number of transitions to disabled states; if the number of the members is equal, the IRF equipment with the small number of the members of the main equipment is in an active state and continues to work normally; other IRF devices migrate to the disabled state. After the IRF device is migrated to the disabled state, all other physical ports (usually, service interfaces) of all member devices in the IRF device except the reserved port are closed, so as to ensure that the IRF device cannot forward the service packet any more. By default, only the IRF link physical port is a reserved port, and the user can set other ports as reserved ports through the MAD express Interface command line.

(3) And (3) MAD fault recovery: IRF link failures result in IRF device fragmentation, causing multi-activity status conflicts. Therefore, the fault IRF link is repaired, and the MAD fault can be recovered by recombining the conflicted IRF devices into one IRF device. If the IRF equipment in the active state has other faults before the MAD fault is recovered, the IRF equipment in the disabled state can be started through a command line, and the IRF equipment replaces the original IRF equipment to work, so that the service is ensured to be influenced as little as possible, and the MAD fault is recovered.

In the related art, in order to ensure that the DRNI master device can still work normally after the IPP port is closed, the DRNI system needs to configure a Keepalive link. When the IPP port is closed and the Keepalive link is still connected, the closing of the DRNI slave port is detected by the MAD. Except for ports that are configured not to detect shutdown by MAD and system reserved ports. For example, the ports of Keepalive link are configured to be closed without MAD detection, so as to ensure that the DRNI system works normally. Otherwise, after the IPP port is closed, if the port of the DRNI slave device is closed without the MAD detection, two master devices will appear, resulting in problems of address collision, loop, and the like. In order to prevent the problems of address conflict, loops and the like after the stack is split, the IRF device also needs to be configured with MAD detection, so that after the IRF device is split, the port of the IRF device is closed through the MAD detection.

In the related art, if one DR device in the DRNI system is an IRF device, the Keepalive link and the IPL link are connected in a cross-frame aggregation manner. The IPP port is a port which is set by the system and is not closed through MAD detection, and the port of the Keepalive link is a port which is configured and is not closed through MAD detection. When the IRF device is split, the port of the IRF standby device is closed through MAD detection, and the IPP port of the IRF standby device and the port of the Keepalive link are still normally opened. Therefore, after the IRF device is split, the physical ports corresponding to the IPP ports of the IRF master device and the IRF slave device and the physical ports corresponding to the ports of the Keepalive link are both opened, and the DRNI system has the problems of address conflict, loop, and the like.

Fig. 2 shows a schematic diagram of a DRNI network formed by IRF devices in the related art. As shown in fig. 2, the device a and the device B constitute an IRF device, and the IRF device and the device D constitute a DRNI system. Device C is an intermediate device used to perform MAD detection. The device A in the IRF device is an IRF main device, and the device B is an IRF standby device. The IRF device in the DRNI system is a DRNI master device, and the device D is a DRNI slave device. An IPL aggregation link is established between the IRF equipment and the equipment D, and an IPP port is an aggregation port 1. And establishing a Keepalive aggregation link between the IRF device and the device D, wherein a port of the Keepalive aggregation link is an aggregation port 2.

As shown in fig. 2, after the IRF link between the device a and the device B fails, the port of the device B, which is the IRF standby device, can be normally closed through MAD detection. The physical port corresponding to the IPP port and the physical port corresponding to the port of the Keepalive link are not closed through MAD detection. If the aggregation port is dynamic aggregation, only one port of the aggregation port of the device D may be selected, and a situation that the IPL link is between the device a and the device D and the Keepalive link is between the device B and the device D may occur, so that the Keepalive link cannot function normally. If the aggregation port is static aggregation, the physical ports corresponding to the IPP ports of the device a and the device B and the physical ports corresponding to the ports of the Keepalive link can both be opened, and the DRNI system will have problems of address collision, loop, and the like.

To solve the technical problems in the related art, fig. 3 is a schematic diagram illustrating a port operation control method according to an embodiment of the present disclosure. The first and second DR devices form a DRNI system, the first DR device is an IRF device, and the method is used for the second DR device. As shown in fig. 3, the method includes steps S31 to S32.

In step S31, when a message from the first DR device is received, an identifier carried in the message and used for indicating an operation state of the IRF device serving as the first DR device is acquired.

In step S32, according to the identifier, the physical port of the second DR device that receives the message is subjected to operation control.

According to the port operation control method, the first DR equipment and the second DR equipment form a DRNI system, the first DR equipment is IRF equipment, and when the second DR equipment receives a message from the first DR equipment, the second DR equipment performs operation control on a port of the DR equipment receiving the message through an identifier which is carried in the message and used for representing the state of the IRF equipment serving as the first DR equipment, so that the problems of address conflict, loops and the like can be avoided after the IRF equipment serving as the first DR equipment is split.

In one implementation, the physical port of the second DR apparatus includes a physical port corresponding to the IPP port of the second DR apparatus; and/or a physical port corresponding to a port of the Keepalive link of the second DR apparatus. Wherein, the IPP port may refer to a port of the IPL link. DRCP messages can be transmitted between DR equipment through IPL links, and neighbor states can be detected through Keepalive links.

In one implementation, a TLV (Type Length Value) field is extended in the packet, where the TLV field carries an identifier, and the identifier includes a status Value used for indicating whether the IRF device is faulty or not. For example, the identification includes a first status value indicative of IRF device failure; or the identification includes a second status value indicating that the IRF device is not malfunctioning.

In one implementation, the state of the IRF device may include an Active state (Active state) or a disabled state (Recovery state). Whether the IRF equipment fails or not can be judged according to the state of the IRF equipment. When the state of the IRF main equipment is an active state and the state of the IRF standby equipment is a disabled state, the IRF equipment failure is described; and when the states of the IRF main equipment and the IRF standby equipment are active states, the IRF equipment is not in failure.

As one example, the identification may include a first state value indicating that the state of the IRF device is a disabled state or a second state value indicating that the state of the IRF device is an active state. For example, the first state value is 1, which indicates that the state of the IRF device is the disabled state; the second state value is 2, indicating that the state of the IRF device is active.

In one implementation, whether the IRF device fails or not may be determined through IRF MAD detection, and whether the DRNI system fails or not may be determined through DRNI MAD detection. When the IRF standby equipment is detected to be closed through the IRF MAD, the IRF standby equipment is indicated to be in fault; in case the DRNI slave detects shutdown via DRNI MAD, a DRNI system failure is accounted for.

Among them, the ird MAD detection may refer to the MAD detection triggered by the IRF device splitting. DRNI MAD detection may refer to MAD detection triggered due to IPP port closure. And under the condition that the IRF standby equipment is closed through the IRF MAD detection, the IRF equipment fails, so that the state of the IRF main equipment is an active state, and the state of the IRF standby equipment is a disabled state. And under the condition that the DRNI slave device is closed through DRNI MAD detection, the IRF device is not in failure, and the states of the IRF main device and the IRF standby device are active states.

As an example, the identity may include a first state value indicating that the IRF slave device detects shutdown through the IRF MAD, or a second state value indicating that the DRNI slave device detects shutdown through the DRNI MAD, or a third state value indicating that the device in the DRNI system does not detect shutdown through the MAD. For example, when the identifier is 1, it indicates that the IRF standby device is turned off through IRF MAD detection; when the identification is 2, the DRNI slave device is closed through DRNI MAD detection; when the flag is 3, it indicates that the device in the DRNI system is not turned off by MAD detection.

In an implementation manner, the message may be an LLDP (Link Layer Discovery Protocol) message, and the like, which is not limited in this disclosure. The IRF device may send an LLDP message to the second DR device, and transmit the state of the IRF device through the LLDP message, so that the second DR device performs operation control on the port of the second DR device that receives the LLDP message according to the obtained identifier indicating the state of the IRF device.

In one implementation, if the identifier includes a first state value used to indicate the IRF device failure, then according to the identifier, performing operation control on the physical port of the second DR device that receives the packet, including: and closing the physical port of the second DR equipment receiving the message.

As an example, when the flag is 1, the status of the IRF device is a disabled status; when the identifier is 2, the state of the IRF device is an active state. When a message from an IRF device serving as a first DR device is received, a state value of a carried identifier in the message is acquired by a second DR device to be 1, which indicates that the state of the IRF device is a disabled state, and thus a physical port corresponding to an IPP port of the second DR device receiving the message and a physical port corresponding to a port of a Keepalive link are closed.

As another example, when the flag is 1, it indicates that the IRF backup device is turned off through IRF MAD detection; when the identification is 2, the DRNI slave device is closed through DRNI MAD detection; when the flag is 3, it indicates that the device in the DRNI system is not turned off by MAD detection. When receiving a message from an IRF device serving as a first DR device, a state value of a carried identifier in the message, which is acquired by a second DR device, is 1, indicating that the IRF device is closed through an IRF MAD detection, and thus closing a physical port corresponding to an IPP port of the second DR device and a physical port corresponding to a port of a Keepalive link, which receive the message.

In one implementation, if the identifier includes a second state value used to indicate that the IRF device is not in a failure, performing operation control on a physical port of the second DR device that receives the packet according to the identifier, including: and keeping the physical port of the second DR equipment which receives the message open.

As an example, when the flag is 1, the status of the IRF device is a disabled status; when the identifier is 2, the state of the IRF device is an active state. When a message from the IRF device serving as the first DR device is received, the second DR device obtains that the status value carrying the identifier in the message is 2, which indicates that the IRF device is in an active status, and thus keeps opening the physical port corresponding to the IPP port of the second DR device and the physical port corresponding to the port of the Keepalive link, which receive the message.

As another example, when the flag is 1, it indicates that the IRF backup device is turned off through IRF MAD detection; when the identification is 2, the DRNI slave device is closed through DRNI MAD detection; when the flag is 3, it indicates that the device in the DRNI system is not turned off by MAD detection. When receiving a message from an IRF device serving as a first DR device, a second DR device acquires that a status value carrying an identifier in the message is 2, which indicates that a DRNI slave device is closed through DRNI MAD detection, thereby keeping a physical port corresponding to an IPP port of the second DR device receiving the message and a physical port corresponding to a port of a Keepalive link open. Or when receiving a message from the IRF device serving as the first DR device, the second DR device obtains that the status value carrying the identifier in the message is 3, which indicates that the device in the DRNI system is not closed through MAD detection, thereby keeping the physical port corresponding to the IPP port of the second DR device receiving the message and the physical port corresponding to the port of the Keepalive link open.

Fig. 4 illustrates a schematic diagram of a port operation control method according to an embodiment of the present disclosure. The first DR device and the second DR device form a DRNI system, the first DR device is an IRF device, and the method is used for the first DR device. As shown in fig. 4, the method includes steps S41 to S42.

In step S41, according to the state of the IRF device serving as the first DR device, a message carrying an identifier indicating the state of the IRF device is generated, where the identifier includes a state value indicating whether the IRF device fails.

In step S42, the message is sent to the physical port corresponding to the IPP port of the second DR apparatus and/or the physical port corresponding to the port of the Keepalive link of the second DR apparatus, so that the second DR apparatus performs operation control on the physical port of the second DR apparatus that receives the message according to the identifier carried in the message.

In one implementation, generating, according to a state of an IRF device serving as a first DR device, a packet carrying an identifier indicating a state of the IRF device, where the identifier includes a state value indicating whether the IRF device fails, includes: and generating a message carrying an identifier for indicating the state of the IRF equipment under the condition that the IRF equipment fault is detected, wherein the identifier comprises a first state value for indicating the IRF equipment fault.

As an example, when the flag is 1, the status of the IRF device is a disabled status; when the identifier is 2, the state of the IRF device is an active state. When the IRF device is split, the IRF standby device is migrated to a disabled state through IRF MAD detection, and the IRF main device still keeps an active state. Therefore, when the IRF standby device detects that the state is the disabled state, a message carrying an identifier indicating that the state of the IRF standby device is the disabled state is generated, that is, a message carrying the identifier and having a state value of 1 is generated.

As another example, when the flag is 1, it indicates that the IRF backup device is turned off through IRF MAD detection; when the identification is 2, the DRNI slave device is closed through DRNI MAD detection; when the flag is 3, it indicates that the device in the DRNI system is not turned off by MAD detection. When the IRF equipment is split, the IRF standby equipment is closed through IRF MAD detection; and the IRF master device is not closed through the IRF MAD detection and still keeps working. Therefore, when the IRF standby equipment detects that the IRF standby equipment is closed through the IRF MAD detection, the IRF standby equipment generates a message carrying an identifier for indicating that the IRF standby equipment is closed through the IRF MAD detection, namely, the message carrying the identifier and having a state value of 1 is generated. And the IRF master device generates a message carrying an identifier indicating that the device in the DRNI system is not turned off by MAD detection, that is, generates a message carrying an identifier and having a status value of 3.

In one implementation, generating, according to a state of an IRF device serving as a first DR device, a packet carrying an identifier indicating a state of the IRF device, where the identifier includes a state value indicating whether the IRF device fails, includes: and generating a message carrying an identifier for indicating the state of the IRF equipment under the condition that the IRF equipment is detected to be not failed, wherein the identifier comprises a second state value for indicating the IRF equipment failure.

As an example, when the flag is 1, the status of the IRF device is a disabled status; when the identifier is 2, the state of the IRF device is an active state. When the devices in the DRNI system are operating normally, the states of the IRF master device and the IRF slave device are active. Therefore, when the IRF master device and the IRF slave device detect that the state is the active state, a message carrying an identifier indicating that the state of the IRF device is the active state is generated, that is, a message carrying an identifier and having a state value of 2 is generated.

As another example, when the flag is 1, it indicates that the IRF backup device is turned off through IRF MAD detection; when the identification is 2, the DRNI slave device is closed through DRNI MAD detection; when the flag is 3, it indicates that the device in the DRNI system is not turned off by MAD detection. When the IPP port is closed, the DRNI slave closes through DRNI MAD detection. Therefore, when the IRF master device and the IRF slave device detect that the DRNI slave device is closed through DRNI MAD detection due to the closing of the IPP port, a message carrying an identifier indicating that the DRNI slave device is closed through DRNI MAD detection is generated, that is, a message carrying an identifier with a state value of 2 is generated. When the device in the DRNI system is operating normally, the device in the DRNI system is not turned off by MAD detection. Therefore, when the IRF main device and the IRF standby device detect that the IRF main device and the IRF standby device are not closed through the IRF MAD detection, a message carrying an identifier for indicating that the IRF MAD detection is not closed is generated, namely, a message carrying the identifier and having a state value of 3 is generated.

Fig. 5 shows a schematic diagram of a DRNI networking formed by IRF devices according to an embodiment of the present disclosure. As shown in fig. 5, the device a and the device B constitute an IRF device, and the IRF device and the device D constitute a DRNI system. Device C is an intermediate device used to perform MAD detection. The device A in the IRF device is an IRF main device, and the device B is an IRF standby device. The IRF device in the DRNI system is a DRNI master device, and the device D is a DRNI slave device. Therefore, the device A and the device B are virtualized into one IRF device, the IRF device and the device D form load sharing and jointly transmit the flow, when one device fails, the flow can be quickly switched to the other device, and the normal operation of the service is ensured.

As shown in fig. 5, device a has Port1 and Port2, device B has Port5 and Port6, and device D has Port3, Port4, Port7, and Port 8. The aggregate Port formed by Port1 and Port5 is an IPP Port, and the aggregate Port formed by Port3 and Port7 is an IPP Port. The aggregation Port formed by Port2 and Port6 is a Port of a Keepalive link, and the aggregation Port formed by Port4 and Port8 is a Port of a Keepalive link.

In one implementation manner, the first DR device and the second DR device form a DRNI system, the first DR device is an IRF device, a function of sending a packet with an extended TLV field is enabled at a physical port corresponding to an IPP port of the IRF device and a physical port corresponding to a port of a Keepalive link, and the TLV field carries a state value indicating whether the IRF device is faulty or not. Therefore, the IRF device can send a message carrying a state value indicating that the IRF device is faulty or not faulty to the physical port corresponding to the IPP port of the second DR device and the physical port corresponding to the port of the Keepalive link, so that the second DR device performs operation control on the physical port corresponding to the IPP port of the second DR device and the physical port corresponding to the port of the Keepalive link, which receive the message, according to the identifier.

As shown in fig. 5, Port1, Port2 at device a enable the ability to send messages that extend the TLV field that carries an identification that includes a status value that indicates device a as failed or not. Thus, the device A can send messages carrying identifications indicating whether the device A has a fault or a non-fault to the ports 3 and 4 of the device D at preset time intervals. Therefore, the device D can control the operation of the ports 3 and 4 of the device D receiving the message according to the identification.

As shown in fig. 5, Port5, Port6 at device B enable the function of sending a message that extends the TLV field that carries an identification that includes a status value indicating device B as failed or not. Thus, the device B can send a message carrying an identifier indicating whether the device B has failed or has not failed to the ports 7, 8 of the device D every predetermined time interval. Therefore, the device D can control the operation of the ports 7 and 8 of the device D receiving the message according to the identification.

As an example, when the flag is 1, the status of the IRF device is a disabled status; when the identifier is 2, the state of the IRF device is an active state. As shown in fig. 5, the ports 1 and 2 of the device a send messages carrying identifiers indicating the state of the device a to the ports 3 and 4 of the device D at predetermined intervals. The ports 5 and 6 of the device B send messages carrying identifiers indicating the state of the device B to the ports 7 and 8 of the device D at predetermined intervals. Under the condition that the identifier carried by the message is 1, the device D closes the physical port of the device D that receives the message. And under the condition that the identifier carried by the message is 2, the device D ignores the message and keeps the physical port of the device D which receives the message.

As shown in fig. 5, when the link between device a and device B fails, causing the IRF device to split, device B transitions to the disabled state through IRF MAD detection, while device a remains in the active state. Therefore, when detecting that the state is the disabled state, the device B generates a message carrying an identifier indicating that the state of the device B is the disabled state, that is, generates a message carrying an identifier with a state value of 1. Port5 and Port6 of device B send messages carrying the ID with the status value of 1 to Port7 and Port8 of device D. Device D closes Port7 and Port8 of device D that received the message. And the device a generates a message carrying an identifier indicating that the state of the device a is the active state, that is, generates a message carrying an identifier having a state value of 2, when detecting that the state is the active state. Port1 and Port2 of device A send messages carrying the status value of 2 identified to Port3 and Port4 of device D. Device D ignores the message, keeping Port3 and Port4 of device D that receives the message open. Therefore, no matter the aggregation port is dynamic aggregation or static aggregation, the IPL link and the Keepalive link are both between the device A and the device D, the DRNI system can work normally, and the problems of address conflict, loop and the like can not occur.

As another example, when the flag is 1, it indicates that the IRF backup device is turned off through IRF MAD detection; when the identification is 2, the DRNI slave device is closed through DRNI MAD detection; when the flag is 3, it indicates that the device in the DRNI system is not turned off by MAD detection. As shown in fig. 5, the ports 1 and 2 of the device a send messages carrying identifiers indicating the MAD detection result of the device a to the ports 3 and 4 of the device D at preset intervals. And the ports 5 and 6 of the device B send messages carrying the identification for representing the MAD detection result of the device B to the ports 7 and 8 of the device D at preset intervals. Under the condition that the identifier carried by the message is 1, the device D closes the physical port of the device D that receives the message. And under the condition that the identifier carried by the message is 2 or 3, the device D ignores the message and keeps the physical port of the device D which receives the message.

For another example, as shown in fig. 5, after the link between device a and device B fails to cause the IRF device to split, device B is turned off by the IRF MAD detection, and device a is not turned off by the IRF MAD detection and still remains in operation. Therefore, when the device B detects that the device B is closed through the IRF MAD detection, the device B generates a message carrying an identifier indicating that the device B is closed through the IRF MAD detection, that is, a message carrying an identifier and having a status value of 1. Port5 and Port6 of device B send messages carrying the ID with the status value of 1 to Port7 and Port8 of device D. Device D closes Port7 and Port8 of device D that received the message. And the device a generates a message carrying an identifier indicating that the device a is not closed through the IRF MAD detection, that is, generates a message carrying an identifier with a state value of 3, when detecting that the device a is not closed through the IRF MAD detection. Port1, 2 of device A sends packets carrying the identifier 3 to Port3, 4 of device D. Device D ignores the message, keeping Port3 and Port4 of device D that receives the message open. Therefore, no matter the aggregation port is dynamic aggregation or static aggregation, the IPL link and the Keepalive link are both between the device A and the device D, the DRNI system can work normally, and the problems of address conflict, loop and the like can not occur.

For another example, as shown in fig. 5, after the IPP port (e.g., the aggregation port 1) is closed, the device D detects the closing through the DRNI MAD, so that the device a or the device B generates a message carrying an identifier indicating that the device D detects the closing through the DRNI MAD, that is, a message carrying an identifier 2, when detecting that the closing of the IPP port causes the device D to detect the closing through the DRNI MAD. Port2 of device A sends a packet carrying the identification 2 to Port4 of device D. Device D ignores the message and keeps the Port4 of device D that receives the message open. Therefore, the Keepalive link between the device A and the device D can work normally, and the device D is closed through DRNI MAD detection, so that two main devices cannot be generated, and the problems of address conflict, loop and the like cannot occur.

Fig. 6 illustrates a block diagram of a port operation control device according to an embodiment of the present disclosure. The first DR device and the second DR device form a DRNI system, the first DR device is an IRF device, and the device is used for the second DR device. As shown in fig. 6, the apparatus includes:

an identifier obtaining module 61, configured to, when receiving a message from the first DR device, obtain an identifier, which is carried in the message and used to indicate an operating state of the IRF device serving as the first DR device; and an operation control module 62, configured to perform operation control on the physical port of the second DR device that receives the packet according to the identifier.

In one implementation, the physical port of the second DR apparatus includes a physical port corresponding to the IPP port of the second DR apparatus; and/or a physical port corresponding to a port of a Keepalive link of the second DR device.

In one implementation, the identifier includes a first status value indicating a failure of the IRF device, then the operation control module 62 is configured to: closing the physical port of the second DR equipment receiving the message; or the identification includes a second status value indicating that the IRF device is not malfunctioning, the operation control module 62 is configured to: and keeping the physical port of the second DR equipment receiving the message open.

Fig. 7 illustrates a block diagram of a port operation control device according to an embodiment of the present disclosure. The first DR device and the second DR device form a DRNI system, the first DR device is an IRF device, and the device is used for the first DR device. As shown in fig. 7, the apparatus includes:

a message generating module 71, configured to generate, according to the state of the IRF device serving as the first DR device, a message carrying an identifier used for indicating the state of the IRF device, where the identifier includes a state value used for indicating whether the IRF device fails; a message sending module 72, configured to send the message to a physical port corresponding to the IPP port of the second DR device and/or a physical port corresponding to the port of the Keepalive link of the second DR device, so that the second DR device performs operation control on the physical port of the second DR device that receives the message according to the identifier carried in the message.

In one implementation, the packet generating module 71 includes: a first packet generation module 711, configured to generate, when detecting that the IRF device fails, a packet carrying an identifier used to indicate a state of the IRF device, where the identifier includes a first state value used to indicate that the IRF device fails; or the second packet generating module 712 is configured to generate, when it is detected that the IRF device is not in a failure, a packet carrying an identifier indicating a state of the IRF device, where the identifier includes a second state value indicating that the IRF device is in a failure.

According to the port operation control device disclosed by the invention, the first DR equipment and the second DR equipment form a DRNI system, the first DR equipment is IRF equipment, and when the second DR equipment receives a message from the first DR equipment, the second DR equipment performs operation control on the port of the DR equipment receiving the message through the identifier which is carried in the message and used for indicating the state of the IRF equipment serving as the first DR equipment, so that the problems of address conflict, loop and the like can be avoided after the IRF equipment serving as the first DR equipment is split.

Fig. 8 is a block diagram illustrating a port operation control device 900 according to an exemplary embodiment. Referring to fig. 8, the apparatus 900 may include a processor 901, a machine-readable storage medium 902 having stored thereon machine-executable instructions. The processor 901 and the machine-readable storage medium 902 may communicate via a system bus 903. Also, the processor 901 performs the above-described port operation control method by reading machine-executable instructions corresponding to the port operation control logic in the machine-readable storage medium 902.

The machine-readable storage medium 902 referred to herein may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: a RAM (random Access Memory), a volatile Memory, a non-volatile Memory, a flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A port operation control method, wherein a first DR device and a second DR device constitute a DRNI system, the first DR device being an IRF device, the method being applied to the second DR device, comprising:

according to the identification, operation control is carried out on the physical port of the second DR equipment receiving the message;

if the identifier includes a second state value indicating that the IRF device is not faulty, performing operation control on a physical port of the second DR device that receives the packet according to the identifier, including: and keeping the physical port of the second DR equipment receiving the message open.

2. The method of claim 1, wherein the physical port of the second DR device comprises a physical port corresponding to an IPP port of the second DR device; and/or a physical port corresponding to a port of a Keepalive link of the second DR device.

3. The method of claim 1,

if the identifier includes a first state value used for indicating the IRF device fault, performing operation control on the physical port of the second DR device receiving the packet according to the identifier, including: and closing the physical port of the second DR equipment receiving the message.

4. A port operation control method, wherein a first DR device and a second DR device constitute a DRNI system, the first DR device being an IRF device, the method being applied to the first DR device, and comprising:

sending the message to a physical port corresponding to the IPP port of the second DR equipment and/or a physical port corresponding to a port of a Keepalive link of the second DR equipment, so that the second DR equipment performs operation control on the physical port of the second DR equipment receiving the message according to an identifier carried by the message;

generating a packet carrying an identifier for indicating the status of the IRF device according to the status of the IRF device as the first DR device, where the identifier includes a status value for indicating whether the IRF device fails, and includes:

and generating a message carrying an identifier for indicating the state of the IRF equipment under the condition that the IRF equipment is detected to be not failed, wherein the identifier comprises a second state value for indicating that the IRF equipment is not failed.

5. The method according to claim 4, wherein generating, according to the state of the IRF device serving as the first DR device, a packet carrying an identifier indicating the state of the IRF device, where the identifier includes a state value indicating whether the IRF device fails includes:

and generating a message carrying an identifier for indicating the state of the IRF equipment under the condition that the IRF equipment fault is detected, wherein the identifier comprises a first state value for indicating the IRF equipment fault.

6. A port operation control apparatus, wherein a first DR device and a second DR device constitute a DRNI system, the first DR device being an IRF device, the apparatus being for the second DR device, comprising:

the operation control module is used for carrying out operation control on the physical port of the second DR equipment receiving the message according to the identification; the identification includes a second status value indicating that the IRF device is not failing, then the operation control module is to: and keeping the physical port of the second DR equipment receiving the message open.

7. The apparatus of claim 6, wherein the physical port of the second DR device comprises a physical port corresponding to an IPP port of the second DR device; and/or a physical port corresponding to a port of a Keepalive link of the second DR device.

8. The apparatus of claim 6,

the identification includes a first status value indicative of a failure of the IRF device, the operation control module is configured to: and closing the physical port of the second DR equipment receiving the message.

9. A port operation control apparatus, wherein a first DR device and a second DR device constitute a DRNI system, the first DR device being an IRF device, the apparatus being for the first DR device, comprising:

a message sending module, configured to send the message to a physical port corresponding to the IPP port of the second DR device and/or a physical port corresponding to the port of the Keepalive link of the second DR device, so that the second DR device performs operation control on the physical port of the second DR device that receives the message according to the identifier carried in the message;

the message generation module comprises:

and a second message generating module, configured to generate, when it is detected that the IRF device is not in a failure, a message carrying an identifier used for indicating a state of the IRF device, where the identifier includes a second state value used for indicating that the IRF device is not in a failure.

10. The apparatus of claim 9, wherein the message generation module comprises:

a first message generating module, configured to generate, when detecting that the IRF device fails, a message carrying an identifier used for indicating a state of the IRF device, where the identifier includes a first state value used for indicating that the IRF device fails.