CN116418750A

CN116418750A - PFC storm detection method and related equipment

Info

Publication number: CN116418750A
Application number: CN202111643727.8A
Authority: CN
Inventors: 陶佩莹; 吕云屏; 刘和洋; 严金丰; 郑合文; 閤先军; 胡廷波
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-12-29
Filing date: 2021-12-29
Publication date: 2023-07-11

Abstract

The application discloses a PFC storm detection method and related equipment, wherein in the application, a first network device acquires a first threshold value, and the first threshold value is used for representing a threshold value of a frequency of sending PFC pause frames to a second network device by the first network device. The first network device may confirm that a PFC storm has occurred by confirming that the frequency of transmitting PFC pause frames to the second network device reaches a first threshold. The first network device can effectively judge whether the PFC storm occurs or not, and further, after the PFC storm occurs, the first network device can take effective countermeasures to prevent the interruption of the service, so that the service efficiency is improved.

Description

PFC storm detection method and related equipment

Technical Field

The embodiment of the application relates to the field of communication, in particular to a PFC storm detection method and related equipment.

Background

In order to realize no packet loss, a data center widely uses Priority-based flow control (PFC) technology, which is an enhancement of a suspension mechanism in a conventional flow control manner. Conventional flow control mechanisms may block all traffic on one link when the network is congested.

Illustratively, PFC allows 8 virtual channels to be created on one ethernet link and a priority to be assigned to each virtual channel, allowing any one of the virtual channels to be individually suspended and resumed while allowing traffic for the other virtual channels to pass without interruption. This approach enables the network to create a no-packet class of service for a single virtual link that can coexist with other traffic types on the same interface. However, once the depth of the queue of the ingress port of network device a reaches a certain threshold (XOFF), network device a will send PFC pause frames to network device B that sent the message. Network device B receiving the PFC pause frame will cease transmitting packets. The PFC pause frame contains a priority queue and pause time that need to be paused. Once network device a confirms that the length of the queue of the message to be received is less than another threshold (XON), network device a will send a pause frame of duration 0 to network device B, which sent the message, and resume transmission.

In the conventional technology, a buffer in an upstream network device generates backlog when PFC is back-pressed, and a PFC storm (PFC storm) is generated when a link reaction is triggered by a penetrating flow. If PFC storm occurs, the network device does not take effective countermeasures against the PFC storm, which causes service interruption and reduces service efficiency.

Disclosure of Invention

The embodiment of the application provides a PFC storm detection method and network equipment, wherein the network equipment can effectively judge whether the PFC storm occurs or not, and further, after the PFC storm occurs, the network equipment can take effective countermeasures to prevent interruption of service, so that service efficiency is improved.

In a first aspect of the present invention, a method for detecting a PFC storm is provided, where when a first network device in different network systems receives more messages within a certain period of time, that is, when the depth of a queue of an ingress port reaches a threshold value (XOFF), the first network device sends a PFC pause frame to a network device that sends a message, and the network device that receives the PFC pause frame stops sending a data message to the first network device. However, if the frequency of transmitting the PFC pause frame is high, which may cause a PFC storm, the first network device may confirm whether the PFC storm occurs according to the frequency of transmitting the PFC pause frame. The first network device obtains a first threshold value representing a threshold value of a frequency at which the first network device transmits PFC pause frames to the second network device. The first network device may confirm that a PFC storm has occurred by confirming that the frequency of transmitting PFC pause frames to the second network device reaches a first threshold.

In the application, the first network device acquires a first threshold, where the first threshold is used to represent a threshold of a frequency at which the first network device sends PFC pause frames to the second network device. The first network device may confirm that a PFC storm has occurred by confirming that the frequency of transmitting PFC pause frames to the second network device reaches a first threshold. The first network device can effectively judge whether the PFC storm occurs or not, and further, after the PFC storm occurs, the first network device can take effective countermeasures to prevent the interruption of the service, so that the service efficiency is improved.

In a possible implementation manner of the first aspect, when the first network device is in a normal connection state, after the first network device obtains the second threshold information according to the first packet, the first network device confirms whether the frequency of sending the PFC pause frame by the third network device reaches the second threshold according to the second threshold information, if so, the PFC storm is considered to occur, and if not, the PFC storm is proved not to occur. In this possible implementation manner, the receiver of the first network device may also determine whether a PFC storm occurs according to the frequency at which the third network device sends the PFC pause frame and the second threshold value, so as to further improve the accuracy of the first network device in determining whether the PFC storm occurs. In this possible implementation manner, the first network device can confirm whether the PFC storm occurs only by one step of judgment, so that the efficiency of the first network device in confirming the PFC storm is improved.

In a possible implementation manner of the first aspect, after the first network device confirms that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold, the first network device further needs to confirm that the first network device does not receive the second packet sent by the third network device, where the second packet is used to indicate a service packet sent by the third network device to the first network device, and in this case, the first network device confirms that a PFC storm occurs. In the possible implementation manner, the first network device can further judge whether the PFC storm occurs according to whether the service message sent by the third network device is received, so that the probability of misjudgment is reduced, and the accuracy of the scheme is improved.

In a possible implementation manner of the first aspect, after the first network device confirms that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold, the first network device confirms that the first network device does not receive the second packet sent by the third network device, where the first network device further needs to confirm that the third packet is not received, the third packet has a priority higher than that of the second packet, and the third packet is used to indicate that a service packet sent to the first network device, where the first network device confirms that a PFC storm occurs. In this possible implementation manner, the first network device may further determine whether a PFC storm occurs according to whether the third packet is received, so as to prevent the probability of misdetermining as the PFC storm when the first network device receives the high-priority packet but does not receive the packet sent by the third network device, thereby further improving accuracy of the scheme.

In a possible implementation manner of the first aspect, the first network device sends a fourth packet to the second network device, where the fourth packet includes the first threshold value. Further, if the second network device confirms that the frequency of the received PFC pause frame sent by the first network device is greater than the first threshold, the second network device confirms that a PFC storm has occurred. And if the second network equipment confirms that the frequency of the received PFC pause frame sent by the first network equipment is smaller than the first threshold value, the second network equipment confirms that the PFC storm does not occur. In this possible implementation manner, the first network device sends the first threshold to the other network devices, so that the other network devices can determine whether the PFC storm occurs according to the first threshold, which is helpful for the system including the first network device to accurately identify the storm.

In one possible implementation manner of the first aspect, the implementation manner of the first message is multiple, and optionally, the first message may be a link layer discovery protocol LLDP message, and this possible implementation manner provides a specific implementation manner of the first message, which improves the implementation manner of the scheme.

In a possible implementation manner of the first aspect, if the first packet is an LLDP packet, optionally, the field including the second threshold in the first packet may be a TLV field, that is, the TLV field in the LLDP packet includes the second threshold, this possible implementation manner provides a specific implementation manner of carrying the second threshold, which improves the implementation manner of the scheme.

In a possible implementation manner of the first aspect, if the first packet is an LLDP packet, optionally, the field including the second threshold in the first packet may be a sub-TLV field, that is, the sub-TLV field in the LLDP packet includes the second threshold, this possible implementation manner provides a specific implementation manner of carrying the second threshold, which improves the feasibility of the scheme.

A second aspect of the present application provides a network device comprising at least one processor and a memory. The processor is coupled to the memory. The memory is for storing instructions that, when executed by the processor, cause the network device to perform the method of the first aspect or any of the possible implementations of the first aspect.

A third aspect of the present application provides a computer readable storage medium storing a program for causing the network device to perform the method of the first aspect or any possible implementation of the first aspect.

A fourth aspect of the present application provides a computer program product storing one or more computer-executable instructions which, when executed by the processor, perform the method of the first aspect or any one of the possible implementations of the first aspect.

A fifth aspect of the present application provides a chip comprising a processor and a communication interface, the processor being coupled to the communication interface, the processor being configured to read instructions to perform the method of the first aspect or any one of the possible implementations of the first aspect.

A sixth aspect of the present application is a network system comprising a network device as described in the first aspect or any one of the possible implementation manners of the first aspect.

From the above technical solutions, the embodiments of the present application have the following advantages:

Drawings

Fig. 1 is a schematic structural diagram of a network system provided in the present application;

fig. 2 is another schematic structural diagram of a network system provided in the present application;

fig. 3 is another schematic structural diagram of a network system provided in the present application;

fig. 4 is another schematic structural diagram of a network system provided in the present application;

fig. 5 is an application schematic diagram of a PFC storm detection method provided in the present application;

fig. 6 is another application schematic diagram of a PFC storm detection method provided in the present application;

fig. 7 is a schematic diagram of transmission of an LLDP message provided in the present application;

fig. 8 is another application schematic diagram of a PFC storm detection method provided in the present application;

fig. 9 is a schematic diagram of TLV fields in an LLDP packet provided in the present application;

fig. 10 is a schematic diagram of TLV fields in an LLDP packet provided in the present application;

fig. 11 is a schematic diagram of TLV fields in a sub-LLDP packet provided in the present application

Fig. 12 is a schematic structural diagram of a network device provided in the present application;

fig. 13 is another schematic structural diagram of a network device provided in the present application.

Detailed Description

Examples provided herein are described below with reference to the accompanying drawings, it being apparent that the examples described are only examples of some, but not all, of the present applications. As one of ordinary skill in the art can appreciate, with the development of technology and the appearance of new scenes, the technical solution provided in the present application is also applicable to similar technical problems.

The terms first, second and the like in the description and in the claims of the present application and in the above-described figures, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the examples described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

In order to solve the problems in the above-mentioned scheme, the present application provides a method for detecting a PFC storm, a network device, and a network system, where the network device may effectively determine whether the PFC storm occurs, and further, after the PFC storm occurs, the first network device may take an effective countermeasure to prevent the interruption of the service, thereby improving service efficiency.

The network system, the PFC storm detection method and the network device provided in the present application will be described below with reference to the accompanying drawings.

The following examples will first introduce the network system provided in the present application in connection with the accompanying drawings.

Fig. 1 is a schematic structural diagram of a network system provided in the present application.

Referring to fig. 1, in the present application, the first network device may be applied to a large-scale CLOS network PFC scene, and optionally, the CLOS network PFC scene may include three switches, one is TOR, a downstream port of which is connected to a server, and an upstream port of which is connected to an AGG switch; one is an AGG switch, the downstream port of the AGG switch is connected with a TOR switch, and the upstream port of the AGG is connected with a SPINE switch; one is a spin switch, which is used to connect AGG switches. The full-network PFC scene is that PFC is started among three layers of switches. Optionally, the first network device may be a TOR switch in the above scenario, the first network device may be an AGG switch in the above scenario, the first network device may also be a spin switch in the above scenario, the first network device may also be another switch, and the first network device may also be a server, which is not limited herein.

Fig. 2 is another schematic structural diagram of a network system provided in the present application.

Referring to fig. 2, in the present application, the first network device may be applied to a large-scale CLOS network PFC Free scenario. Optionally, in this scenario, PFC may be turned on for the TOR switch, or PFC may be turned on for a server below the TOR switch, that is, the first network device may be the TOR switch in the scenario, or may be a server in the scenario, which is not limited herein.

Fig. 3 is another schematic structural diagram of a network system provided in the present application.

Referring to fig. 3, in the present application, the first network device may be applied to a MESH networking PFC scenario. Alternatively, in this scenario, the switches may implement a full interconnect, and the PFC may be turned on by the full network. The first network device may be any switch in the scenario, or may be a server in the scenario, which is not limited herein.

Fig. 4 is another schematic structural diagram of a network system provided in the present application.

Referring to fig. 4, in the present application, the first network device may be applied to Dragonfly networking PFC scenarios. Optionally, the switches in the scenario may be divided into multiple packets, and the switches of each packet may implement full interconnection, packet-to-packet, and full interconnection. The PFC can be turned on by the whole network. The first network device may be any switch in the scenario, or may be a server in the scenario, which is not limited herein.

In this application, the first network device may be applied to other scenarios besides the scenarios described in fig. 1 to 4, which are not limited herein.

Based on the network systems described in fig. 1 to fig. 4, the PFC storm detection method provided in the present application is described.

Fig. 5 is an application schematic diagram of a PFC storm detection method provided in the present application.

Referring to fig. 5, an example of the PFC storm detection method provided in the present application includes steps 201 to 203. Next, a method for detecting PFC storms provided in the present application is described with reference to fig. 5.

201. The first network device obtains a first threshold.

In this application, the first threshold is used to represent a threshold of a frequency at which the first network device transmits PFC pause frames to the second network device.

In the application, a first network device acquires an interval set by a chip for sending a PFC pause frame to a second network device. For example: the interval (Pause Gap) of PFC Pause frames=n (n is the time required for the physical layer chip to transmit 512 bits of data), so that the threshold value of the frequency of the PFC Pause frames transmitted to the second network device, that is, the judgment information of whether the local terminal TX generates the frequency threshold value of the PFC Pause frames of PFC storm, can be calculated according to n.

It will be appreciated that, alternatively, the first network device may store the first threshold value in a different register for a different second network device, the value of the first threshold value may be different, and is not limited herein in particular.

202. The first network device acknowledges that the frequency of sending PFC pause frames to the second network device reaches a first threshold.

203. The first network device acknowledges the occurrence of the PFC storm.

The method for detecting PFC storms provided in the present application will be described by way of example with reference to a specific device, and a switch will be described.

The above steps 201 to 203 are described below taking the example that the first network device is a 6865 switch.

For example, the first network device obtains an interval for sending PFC pause frames set in a chip of the local device, taking 6865 switches as an example, pfc_refresh_timer is an interval for sending PFC pause frames exceeding a waterline, and pfc_xoff_timer is an interval for letting the opposite end pause to send messages carried in a TIME field in the PFC pause frames. The interval pfc_refresh_timer=0x900 of the PFC pause frame, according to the interval of the PFC pause frame, the first threshold u1= (2304)/(100 x 2 x 30 bit/s) = (2304)/(100 x 2 x 21) s=0.000010986328125 s, and 1/u1= 91022/s, so that the maximum capability of transmitting the PFC pause frame is 91022/s before the PFC storm occurs in the 6865 switch. If 6865 switch acknowledges that the frequency of sending PFC pause frames reaches 91022/s, 6865 switch acknowledges that a PFC storm has occurred.

The steps 201 to 203 are described below by taking the first network device as a 1822 network card as an example.

For example, the first network device obtains an interval for sending PFC Pause frames set in a chip of the local device, taking 1822 network cards as an example, pause_gap is an interval for sending PFC Pause frames exceeding a waterline, and pause_time is an interval for letting the opposite terminal Pause to send messages carried in a TIME field in the PFC Pause frames. The interval of PFC Pause frames, pause_gap=0xff=255, and according to the interval of PFC Pause frames, the first threshold value u1=255×512 bat/100 gbps=0.000001239375346769s, 1/u1= 822412/s, and the capability of the network card to generate PFC frames when a storm occurs is 822412/s at maximum. It can be seen that the capacity of the 1822 network card to send PFC pause frames is 822412/s at maximum before PFC storms occur. If 1822 the network card confirms that the frequency of sending PFC pause frames reaches 822412/s, 1822 the network card confirms that PFC storm has occurred.

Fig. 6 is a schematic diagram of another application of a PFC storm detection method provided in the present application.

Referring to fig. 6, in the PFC storm detection method provided in the present application, in addition to the steps 201 to 203, the first network device may further receive a first message, and further determine whether a PFC storm occurs according to the first message, and the possible implementation manner will be described in detail below.

301. The first network device receives a first message.

In the application, the first network device may receive a first packet sent by the third network device, where the first packet includes a second threshold, and the second threshold is used to indicate a threshold of a frequency at which the third network device sends PFC pause frames to the first network device.

302. The first network device acknowledges receipt of the PFC pause frame sent by the third network device with a frequency up to a second threshold.

303. The first network device acknowledges the occurrence of the PFC storm.

In the application, when the first network device is in a normal connection state, after the first network device acquires the second threshold information according to the first message, determining whether the frequency of the third network device for sending the PFC pause frame can reach the second threshold according to the second threshold information, if so, considering that the PFC storm occurs, and if not, proving that the PFC storm does not occur. In this possible implementation manner, the receiver of the first network device may also determine whether a PFC storm occurs according to the frequency at which the third network device sends the PFC pause frame and the second threshold value, so as to further improve the accuracy of the first network device in determining whether the PFC storm occurs.

In the present application, when the first network device is in an initial state, the first network device may start a self-learning function. I.e. the first network device may receive the first messages sent by the plurality of third network devices. Or when the first network device re-accesses the network again, that is, the switch port or the server port has a down-up phenomenon, the frequency threshold of the PFC pause frame when the local terminal RX has the PFC storm can be reset, and the first network device is triggered again to acquire the frequency threshold of the PFC pause frame when the local terminal RX has the PFC storm according to the second message. The receiver of the first network device may also determine whether a PFC storm occurs according to the frequency at which the PFC pause frame is sent by the third network device and the second threshold.

Fig. 7 is a schematic diagram of transmission of an LLDP packet provided in the present application.

Illustratively, the first network device is exemplified as a switch or server. In the initial state, the switch or the server has no PFC frequency threshold information (second threshold information) that the local RX has a PFC storm. When the switch or server receives a specific LLDP message (second message), as shown in fig. 7:

if the Pause gap=0x900 in the LLDP message is calculated as 100G link, u1=2304×512 bat/100 gbps= 0.000010986328125s. 1/u1= 91022/1 s. It can be seen that the frequency threshold of PFC pause frames where RX of the local device has a PFC storm is 91022/s.

In the method for detecting PFC storm provided in the present application, in step 303, the first network device confirms that PFC storm occurs, and has a specific confirmation method, and the specific confirmation method will be described below.

Mode one:

the first network device acknowledges that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold, and the first network device acknowledges that the PFC storm has occurred.

In the application, the first network device only needs to confirm that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold value, and the first network device can confirm that the PFC storm occurs. In this possible implementation manner, the first network device can confirm whether the PFC storm occurs only by one step of judgment, so that the efficiency of the first network device in confirming the PFC storm is improved.

Mode two:

the first network device confirms that the frequency of receiving the PFC pause frame sent by the third network device reaches a second threshold, and the first network device confirms that the first network device does not receive the second message in the first period, and the first network device confirms that PFC storm occurs.

In the application, after the first network device confirms that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold, the first network device needs to confirm that the first network device does not receive the second packet sent by the third network device, where the second packet is used to indicate a service packet sent by the third network device to the first network device, and in this case, the first network device can confirm that a PFC storm occurs. In the possible implementation manner, the first network device can further judge whether the PFC storm occurs according to whether the service message sent by the third network device is received, so that the probability of misjudgment is reduced, and the accuracy of the scheme is improved.

Mode three:

the first network device confirms that the frequency of receiving the PFC pause frame sent by the third network device reaches a second threshold, the first network device confirms that the first network device does not receive the second message in a first period, the first network device confirms that the first network device does not receive the third message in the first period, and the first network device confirms that PFC storm occurs.

Fig. 8 is an application schematic diagram of a PFC storm detection method provided in the present application.

Referring to fig. 8, in the present application, after the first network device confirms that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold, the first network device confirms that the first network device does not receive the second packet sent by the third network device, and further needs to confirm that the third packet is not received, where the third packet has a higher priority than the second packet, and the third packet is used to indicate a service packet sent to the first network device, where the first network device confirms that a PFC storm occurs. In this possible implementation manner, the first network device may further determine whether a PFC storm occurs according to whether the third packet is received, so as to prevent the probability of misdetermining as the PFC storm when the first network device receives the high-priority packet but does not receive the packet sent by the third network device, thereby further improving accuracy of the scheme.

In the PFC storm detection method provided in the present application, in addition to the foregoing steps 201 to 203, the first network device may further send a fourth packet to the second network device, so that the second network device may determine whether a PFC storm occurs according to the fourth packet, and the possible implementation manner will be described in detail below.

In the application, the first network device sends a fourth message to the second network device, where the fourth message includes the first threshold value. Further, if the second network device confirms that the frequency of the received PFC pause frame sent by the first network device is greater than the first threshold, the second network device confirms that a PFC storm has occurred. And if the second network equipment confirms that the frequency of the received PFC pause frame sent by the first network equipment is smaller than the first threshold value, the second network equipment confirms that the PFC storm does not occur. In this possible implementation manner, the first network device sends the first threshold to the other network devices, so that the other network devices can determine whether the PFC storm occurs according to the first threshold, which is helpful for the system including the first network device to accurately identify the storm.

In the PFC storm detection method provided in the present application, the first packet and the fourth packet mentioned in the foregoing examples may be LLDP packets, and the first packet and the fourth packet may also be other types of packets, which are not limited herein specifically.

For example, assuming that the first packet and the fourth packet are LLDP packets, there are multiple implementations when the first packet carries the second threshold, and similarly, there are multiple implementations when the fourth packet carries the first threshold. The following description will take the example that the first message carries the second threshold value.

Mode one: the TLV field in the LLDP message carries a second threshold.

Fig. 9 is a schematic diagram of TLV fields in an LLDP packet provided in the present application.

In this application, for example, TLVs that can extend 1 LLDP protocol carry a first threshold, for example, as shown in fig. 9, a temporarily unused Type 9 can be used to carry the first threshold. Pause Gap represents the frequency threshold of PFC Pause frames where PFC storms occur at port or portal TX, if 16 bits (0-0 xffff) can be used for one port, then a 32 port switch is used 64B.

Fig. 10 is a schematic diagram of TLV fields in an LLDP packet provided in the present application.

In this application, as an example, organizationally Specific Tlv can be extended, organizationally Specific Tlv of TLV type=127 is used, and subtype=20 that is not used temporarily is used. The Pause Gap carries per 16 bits PFC frequency information of the port/portal occurrence TX PFC boom assuming the switch has 32 ports, 32 x 16/8=64b.

Mode two: the sub-TLV field in the LLDP message carries a second threshold.

Fig. 11 is a schematic diagram of a sub-TLV field in an LLDP packet provided in the present application.

In this application, by way of example, the Priority-based flow Control TLV of existing subtype=11 is extended, and an extra field Pause is defined at the end of the information field, where Pause carries PFC frequency information of TX PFC boom every 16 bits, assuming that the switch has 32 ports, 32×16/8=64b.

The foregoing examples provide different embodiments of a method for detecting a PFC storm, and the following provides a network device 40, as shown in fig. 12, where the network device 40 is configured to perform steps performed by the network device in the foregoing examples, and the performing steps and corresponding beneficial effects are specifically understood with reference to the foregoing corresponding examples, which are not repeated herein, where the network device 40 includes:

an obtaining unit 401, configured to obtain a first threshold, where the first threshold is used to represent a threshold of a frequency at which the first network device sends priority-based traffic control PFC pause frames to a second network device;

the confirmation unit 402 is configured to:

confirming that the frequency of sending PFC pause frames to the second network device reaches the first threshold;

the occurrence of PFC storm is confirmed.

In one possible implementation of the method, the method comprises,

a receiving unit, configured to receive a first packet, where the first packet includes a second threshold, where the second threshold is used to represent a threshold of a frequency at which a third network device sends PFC pause frames to the first network device;

the confirmation unit 402 is configured to confirm that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold;

the confirmation unit 402 is configured to confirm that a PFC storm occurs.

In a possible implementation manner, the confirmation unit 402 is configured to:

confirming that the first network equipment does not receive a second message in a first period of time, wherein the second message is used for representing a service message sent by the third network equipment to the first network equipment;

the occurrence of PFC storm is confirmed.

confirming that the first network equipment does not receive a third message within a first period, wherein the third message has a higher priority than the second message, and the third message is used for representing a service message sent to the first network equipment;

the occurrence of PFC storm is confirmed.

In one possible implementation of the method, the method comprises,

and the sending unit is further used for sending a fourth message to the second network device, wherein the fourth message comprises the first threshold value.

In a possible implementation manner, the first message is a link layer discovery protocol LLDP message.

In a possible implementation, the TLV field in the LLDP packet includes the second threshold.

In a possible implementation, the Sub-TLV field in the LLDP packet includes the second threshold.

It should be noted that, since the content of information interaction, execution process and the like between the modules of the network device 40 is based on the same concept as the method example of the present application, the execution steps thereof are consistent with the details of the method steps, and reference may be made to the description at the method example.

The foregoing examples provide different embodiments of a network device 40, and the following provides a network device 50, as shown in fig. 13, where the network device 50 is configured to perform steps performed by the network device in the foregoing examples, and the performing steps and the corresponding beneficial effects are specifically understood with reference to the foregoing corresponding examples, which are not repeated herein.

Referring to fig. 13, a schematic structural diagram of a network device is provided herein, where the network device 50 includes: processor 502, communication interface 503, memory 501. Alternatively, bus 504 may be included. Wherein the communication interface 503, the processor 502 and the memory 501 may be interconnected via a bus 504; bus 504 may be a peripheral component interconnect standard (Peripheral Component Interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus, or the like. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in fig. 13, but not only one bus or one type of bus. The network device 50 may implement the functions of the network device in the example shown in fig. 12. The processor 502 and the communication interface 503 may perform the operations corresponding to the network device in the method example described above.

The following describes the components of the network device in detail with reference to fig. 13:

wherein the memory 501 may be a volatile memory (RAM), such as a random-access memory (RAM); or a nonvolatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a hard disk (HDD) or a Solid State Drive (SSD); or a combination of the above, for storing program code, configuration files, or other content that may be used to implement the methods of the present application.

The processor 502 is a control center of the controller, and may be a central processing unit (central processing unit, CPU), an application specific integrated circuit (application specific integrated circuit, ASIC), or one or more integrated circuits configured to implement examples provided herein, such as: one or more digital signal processors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).

The communication interface 503 is used to communicate with other network devices.

The processor 502 may perform the operations performed by the network device in the foregoing example shown in fig. 12, which are not described herein in detail.

It should be noted that, since the content of information interaction, execution process and the like between the modules of the network device 50 is based on the same concept as the method example of the present application, the execution steps thereof are consistent with the details of the method steps, and reference may be made to the description at the method example.

The present application provides a chip comprising a processor and a communication interface, the processor being coupled to the communication interface, the processor being configured to read instructions to perform operations performed by a network device in the embodiments described above with reference to fig. 5-11.

The present application provides a network system comprising a network device as described in the embodiments described above with reference to fig. 5 to 11.

It will be clear to those skilled in the art that for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing examples, and are not repeated herein.

In the several examples provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus examples described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the object of this example.

In addition, each functional unit in each example of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the examples of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (RAM, random access memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

While the foregoing embodiments have been described in some detail for purposes of clarity of understanding, it will be appreciated that various embodiments of the invention may be practiced otherwise than as specifically described, and that no limitations are intended to the scope of the invention, except as may be modified, practiced with respect to any combination, modification, equivalent replacement, or improvement made within the spirit or principles of the invention. The foregoing examples are merely illustrative of the technical solutions of the present application, and are not limiting thereof; although the present application has been described in detail with reference to the foregoing examples, it will be understood by those of ordinary skill in the art that: the technical scheme recorded in each example can be modified or part of technical features in the technical scheme can be replaced equivalently; such modifications and substitutions do not depart from the essence of the corresponding technical solutions from the scope of the various example technical solutions of the present application.

Claims

1. A method for detecting a PFC storm, comprising:

the method comprises the steps that a first network device obtains a first threshold value, wherein the first threshold value is used for representing the threshold value of the frequency of the PFC pause frame sent by the first network device to a second network device;

the first network device confirms that the frequency of sending PFC pause frames to the second network device reaches the first threshold;

the first network device acknowledges the occurrence of a priority-based flow control PFC storm.

2. The method of claim 1, further comprising:

the first network device receives a first message, wherein the first message comprises a second threshold value, and the second threshold value is used for representing a threshold value of the frequency of a PFC pause frame sent by a third network device to the first network device;

the first network device confirms that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold;

the first network device acknowledges the occurrence of the PFC storm.

3. The method of claim 2, wherein after the first network device acknowledges that the frequency of receiving PFC pause frames sent by the third network device reaches the second threshold, the method further comprises:

the first network device confirms that the first network device does not receive a second message in a first period, wherein the second message is used for representing a service message sent by the third network device to the first network device.

4. The PFC storm detection method of claim 3 wherein the first network device acknowledges that the first network device did not receive the second message within a first period of time, the method further comprising:

the first network device confirms that the first network device does not receive a third message within a first period, the third message has a higher priority than the second message, and the third message is used for representing a service message sent to the first network device.

5. The method of detecting PFC storms according to any of claims 1 to 4, further comprising:

the first network device sends a fourth message to the second network device, wherein the fourth message comprises the first threshold value.

6. The PFC storm detection method according to any of claims 2-4, wherein the first message is a link layer discovery protocol LLDP message.

7. The PFC storm detection method of claim 6 wherein a TLV field in the LLDP message includes the second threshold.

8. The PFC storm detection method of claim 6, wherein a Sub-TLV field in the LLDP message includes the second threshold.

9. A network device, comprising:

an obtaining unit, configured to obtain a first threshold, where the first threshold is used to represent a threshold of a frequency at which the first network device sends priority-based traffic control PFC pause frames to a second network device;

the confirmation unit is used for:

the occurrence of PFC storm is confirmed.

10. The network device of claim 9, wherein the network device,

the confirmation unit is configured to confirm that the frequency of receiving the PFC pause frame sent by the third network device reaches the second threshold;

and the confirmation unit is used for confirming that the PFC storm occurs.

11. The network device of claim 10, wherein the network device,

the confirmation unit is further configured to:

and confirming that the first network equipment does not receive a second message in a first period, wherein the second message is used for representing a service message sent by the third network equipment to the first network equipment.

12. The network device of claim 11, wherein the network device,

the confirmation unit is further configured to:

and confirming that the first network equipment does not receive a third message within a first period, wherein the third message has higher priority than the second message, and the third message is used for representing a service message sent to the first network equipment.

13. The network device according to any one of claims 9 to 12, characterized in that,

14. The network device according to any of claims 10 to 12, wherein the first message is a link layer discovery protocol, LLDP, message.

15. The network device of claim 14, wherein a TLV field in the LLDP message includes the second threshold.

16. The network device of claim 14, wherein a Sub-TLV field in the LLDP message includes the second threshold.

17. A network device, comprising:

a processor and a memory;

the processor is configured to execute instructions stored in the memory to cause the network device to perform the method of any one of claims 1 to 8.

18. A network system comprising a first network device included in the PFC storm detection method of any of claims 1 to 8.