CN118282988A - Congestion management method and communication device - Google Patents

Abstract

The present application provides a congestion management method and a communication device, which are applied to the field of communication technology. The method may include: performing abnormality detection on the first physical member port included in the TRUNK port, and the first physical member port is any physical member port included in the TRUNK port. When the first physical member port is abnormal, the first physical member port is disabled or the speed of the first physical member port is limited. Based on this scheme, when the first physical member port in the TRUNK port is abnormal, the first physical member port can be processed in time to eliminate or alleviate the congestion state of the first physical member port, thereby reducing the impact on the traffic forwarding of other member ports in the TRUNK port.

Description

Congestion management method and communication device

Technical Field

The present application relates to the field of communication technology, and in particular to a congestion management method and a communication device.

Background technique

A TRUNK port (or a TRUNK interface) aggregates multiple physical ports into one logical port, making them work like a channel. After bundling multiple physical ports, not only the bandwidth of the entire network is increased, but also data is transmitted simultaneously through multiple links corresponding to the bound multiple physical ports, which has the function of link redundancy. When one link fails, other links can still work.

Multiple physical ports of a TRUNK port can correspond to multiple user members, and one TRUNK port can transmit traffic from multiple user members. The multiple physical ports bound to the TRUNK port can be called multiple physical member ports.

In one implementation, a device with a trunk port can use a scheduling tree to centrally schedule the traffic of multiple member ports bound to the trunk port. In this case, when an abnormality occurs in one member port of the trunk port, the traffic of the member port will be back-pressured, suppressing the upstream traffic scheduling. Since the traffic of multiple member ports shares a scheduling tree, it will affect the traffic scheduling of other member ports.

Summary of the invention

The present application provides a congestion management method and a communication device, which are used to solve the problem that when the traffic of multiple member ports in a TRUNK port shares a scheduling tree, when congestion back pressure occurs on one member port, it will affect the traffic forwarding of other member ports.

In order to achieve the above objectives, this application adopts the following technical solutions:

In a first aspect, a congestion management method is provided, which may include: performing an abnormality detection on a first physical member port included in a TRUNK port, where the first physical member port is any physical member port included in the TRUNK port. When the first physical member port is abnormal, the first physical member port is disabled or the speed of the first physical member port is limited.

Based on this solution, when the first physical member port in the TRUNK port is abnormal, the first physical member port can be processed in time to eliminate or alleviate the congestion state of the first physical member port, thereby reducing the impact on traffic forwarding of other member ports in the TRUNK port.

In combination with the first aspect above, in a possible implementation, performing abnormality detection on the first physical member port included in the TRUNK port may specifically include: detecting the number of pause frames corresponding to the first physical member port and the traffic rate of the first physical member port. When the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold, and the traffic rate of the first physical member port is less than or equal to a second threshold, it is determined that the first physical member port is abnormal.

In combination with the first aspect, in a possible implementation manner, deactivating the first physical member port may specifically include: configuring the first physical member port to be in a DOWN state.

In combination with the first aspect above, in a possible implementation manner, the method may further include: switching traffic corresponding to the first physical member port to other physical member ports in the TRUNK port except the first physical member port for forwarding.

In combination with the first aspect, in a possible implementation, performing abnormality detection on the first physical member port included in the TRUNK port may specifically include: detecting the flow rate of the first physical member port. When the flow rate of the first physical member port is greater than or equal to the third threshold and the duration is greater than the fourth threshold, determining that the first physical member port is abnormal.

In combination with the first aspect above, in a possible implementation, limiting the rate of the first physical member port may specifically include: configuring a committed access rate CAR for the first physical member port, where CAR is used to limit the traffic rate of the first physical member port.

In a second aspect, a communication device is provided, which may include an anomaly detection module and an anomaly handling module. The anomaly detection module may be used to perform an anomaly detection on a first physical member port included in a TRUNK port, where the first physical member port is any physical member port included in the TRUNK port. The anomaly handling module may be used to disable the first physical member port or limit the speed of the first physical member port when the first physical member port is abnormal.

In combination with the above second aspect, in a possible implementation, the abnormality detection module is used to perform abnormality detection on the first physical member port included in the TRUNK port, which may specifically include: the abnormality detection module is used to detect the number of pause frames corresponding to the first physical member port and the traffic rate of the first physical member port. And, the abnormality detection module may also be used to determine that the first physical member port is abnormal when the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold and the traffic rate of the first physical member port is less than or equal to a second threshold.

In combination with the second aspect, in a possible implementation manner, the exception handling module is used to deactivate the first physical member port, which may specifically include: the exception handling module is used to configure the first physical member port to a DOWN state.

In combination with the above second aspect, in a possible implementation, the exception handling module may also be used to: switch the traffic corresponding to the first physical member port to other physical member ports in the TRUNK port except the first physical member port for forwarding.

In combination with the above second aspect, in a possible implementation, the abnormality detection module is used to perform abnormality detection on the first physical member port included in the TRUNK port, which may specifically include: the abnormality detection module is used to detect the flow rate of the first physical member port. And the abnormality detection module is also used to determine that the first physical member port is abnormal when the flow rate of the first physical member port is greater than or equal to the third threshold and the duration is greater than the fourth threshold.

In combination with the above-mentioned second aspect, in a possible implementation method, the exception handling module is used to limit the speed of the first physical member port, which may specifically include: the exception handling module is used to configure a committed access rate CAR for the first physical member port, and CAR is used to limit the traffic rate of the first physical member port.

In a third aspect, a communication device is provided, comprising: a processor; the processor is used to couple with a memory, and after reading instructions in the memory, execute a congestion management method as described in any one of the first aspects above according to the instructions.

In a fourth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is executed on a computer, the computer can execute the congestion management method described in any one of the above-mentioned first aspects.

In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the congestion management method described in any one of the first aspects.

Among them, the technical effects brought about by any design method in the second to fifth aspects can refer to the technical effects brought about by different design methods in the first aspect, and will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a schematic diagram of a forwarding flow of a network device in a data plane provided by an embodiment of the present application;

FIG2 is a schematic diagram of a functional module of a network device provided in an embodiment of the present application;

FIG3 is a schematic diagram of a hierarchical scheduling model of HQoS provided in an embodiment of the present application;

FIG4 is a schematic diagram of a 5-level scheduling structure of HQoS provided in an embodiment of the present application;

FIG5 is a schematic diagram showing a comparison between QoS and HQoS provided in an embodiment of the present application;

FIG6 is a schematic diagram of scheduling traffic on a TRUNK port provided in an embodiment of the present application;

FIG7 is a schematic diagram of another method for scheduling traffic on a TRUNK port provided in an embodiment of the present application;

FIG8 is a schematic diagram of congestion back pressure provided in an embodiment of the present application;

FIG9 is a flow chart of a congestion management method provided in an embodiment of the present application;

FIG10 is a flow chart of another congestion management method provided in an embodiment of the present application;

FIG11 is a flow chart of another congestion management method provided in an embodiment of the present application;

FIG12 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

FIG13 is a schematic diagram of the structure of another communication device provided in an embodiment of the present application.

Detailed ways

To facilitate understanding, first, a brief introduction is given to the technical terms and related technologies involved in this application.

The physical structure of network devices such as switches and routers can mainly include the following three categories:

Main processing unit (MPU): Responsible for the control plane of the entire system. MPU can be called main control board or management engine, etc.

Switch fabric unit (SFU): responsible for the data plane of the entire system. The data plane provides high-speed, non-blocking data channels to implement service exchange functions between various service modules. SFU can be called a switch card, switch fabric board, or switch matrix, etc.

Line processing unit (LPU): A module used to provide data forwarding functions, providing optical ports, electrical ports and other equipment interfaces of different rates. LPU can be called a line card or interface board, etc.

According to the direction of data flow, the message forwarding of network devices such as switches and routers can be divided into two processes: upstream and downstream. The forwarding flow diagram of network devices such as switches and routers on the data plane can be shown in Figure 1. Referring to Figure 1, the switching network board can be connected to the access side and the network side through a line card respectively, and the traffic on the access side and the traffic on the network side are exchanged on the switching network board. The upstream traffic on the access side can enter the network side through the switching network board and become the downstream traffic on the network side. The upstream traffic on the network side can enter the access side through the switching network board, which is called the downstream traffic on the access side.

On the data plane, the functional modules that the traffic passes through in the device can be shown in Figure 2. Referring to Figure 2, in the upstream direction, after the upstream traffic enters the device, it can pass through the upstream physical interface controller (PIC), the upstream packet forwarding engine (PFE), the upstream traffic manager (TM) and the upstream fabric interface controller (FIC) in sequence, and then enter the switching fabric board. In the downstream direction, the downstream traffic can pass through the downstream FIC, the downstream TM, the downstream PFE and the downstream PIC in sequence from the switching fabric board, and then exit the device. Among them, the downstream PIC can include an egress traffic manager (eTM).

It can be understood that the uplink and downlink on the access side of the network device and the uplink and downlink on the network side can both be the process shown in Figure 2, and are explained here uniformly.

In practical applications, the forwarding of data streams may have certain requirements for the quality of service (QoS). Therefore, QoS technology can be used on the functional modules in the forwarding process to process the data stream. For example, FIG2 also shows the application of QoS technology on various modules in the process of traffic forwarding. As shown in FIG2, in the upstream direction: the upstream PFE can perform flow classification, internal marking, committed access rate (CAR), unicast reverse path forwarding (URPF), filtering, mirroring, sampling, redirection, statistics, etc. The upper and lower TMs can perform packet-based queue management, which can specifically include congestion avoidance, queue scheduling, traffic shaping, etc. In the downstream direction: the downstream TM can perform packet-based queue management, which can specifically include congestion avoidance, queue scheduling, traffic shaping, etc. The downstream PFE can perform flow classification, internal marking (only meaningful when eTM is included in the downstream PIC), CAR, external marking, filtering, mirroring, sampling, statistics, etc. The eTM in the downstream PIC can perform packet-based queue management, including congestion avoidance, queue scheduling, and traffic shaping.

Hierarchical QoS (HQoS) is a technology that uses a multi-level queue scheduling mechanism to solve the problem of multi-user and multi-service bandwidth guarantee. Traditional QoS uses one-level scheduling, and a single port can only distinguish service priorities, but cannot distinguish users, and cannot differentiate services for a single flow of a single user on the port. HQoS uses a multi-level scheduling method, which can finely distinguish the flow of different users and different services, and provide more refined bandwidth management.

To implement hierarchical scheduling, HQoS adopts a hierarchical scheduling model with a tree structure, as shown in Figure 3. The tree structure can have three types of nodes:

1. Leaf node: at the bottom layer. Each leaf node represents a queue. Leaf nodes are scheduled objects and can only be scheduled.

2. Intermediate node (or branch node): Located in the middle layer, it is both a scheduler and a scheduled object. When acting as a scheduled object, an intermediate node can be regarded as a virtual queue and does not occupy the actual cache.

3. Root node: It is at the highest level and represents the highest level scheduler. The root node is only a scheduler, not a scheduling object.

At present, HQoS of network devices such as routers or switches can have 5 levels of scheduling. Figure 4 shows a schematic diagram of the hierarchical scheduling model of the 5-level scheduling. As shown in Figure 4, the hierarchical scheduling model of the 5-level scheduling is also a tree structure, which can include: flow queue (flow queue, FQ), user queue (subscriber queue, SQ), user group queue (group queue, GQ), virtual sub-interface queue (virtual interface, VI) and port queue (dummy port, DP) from leaf node to root node. The introduction of the 5 scheduling queues is as follows:

1. Flow queue: used to distinguish the service priority within the user. The service priority within the user can include 802.1P priority, Internet protocol (IP) priority or differentiated services code point (DSCP) and so on.

2. User queue: used to distinguish different users. User queue supports deployment of CIR (Committed Information Rate) and PIR (Peak Information Rate).

3. User group queue: used to distinguish different user groups. User group queue supports traffic shaping to limit the bandwidth of the entire user group.

4. Virtual sub-interface queue, which can be used to distinguish different logical sub-interfaces.

5. Port queue: represents the physical exit and usually does not require additional configuration.

The scheduling methods adopted between the above-mentioned flow queues, user queues, user group queues or virtual sub-interface queues may include first in first out (FIFO), strict priority (SP), round robin (RR), weighted round robin (WRR), differential round robin (DRR), weighted deficit round robin (WDRR), or weighted fair queuing (WFQ) and the like.

The HQoS 5-level scheduling model schedules packets as follows:

· Packet queueing: Packets are first placed in the FQ queue. When a packet enters the FQ queue, the system checks the queue status to determine whether to perform tail drop or WRED drop. If the packet is not dropped, it is placed in the FQ queue cache.

Request scheduling: After the message enters the FQ queue, it reports the queue status change to the SQ scheduler and requests scheduling. The SQ scheduler then reports the queue status change to its upper-level GQ scheduler and requests scheduling. The process of requesting scheduling is: FQ→SQ→GQ→VI→DP.

·Step-by-step scheduling: After receiving the request, the DP scheduler starts to select VI downwards, and the selected VI selects GQ. The step-by-step scheduling process is: DP→VI→GQ→SQ→FQ.

· Packet dequeue: After the FQ is selected, the packet at the front of the FQ queue is dequeued. At the same time, the FQ updates the queue status, and the SQ, GQ, VI, and DP update the token bucket status.

It is understandable that the SQ, GQ, and VI scheduling nodes introduced by HQoS are both schedulers and scheduled objects. Multiple sub-schedulers can be attached to each level. For example, multiple SQs can be attached to a GQ, and multiple GQs can be attached to a VI. This can achieve more fine-grained and multi-level scheduling management of interface resources, and achieve refined allocation and management of interface resources. In actual applications, VI/GQ can be used as resource management for a certain type of business or customer group, and SQ can be used as resource management for specific users.

FIG5 shows a comparative diagram of QoS and HQoS. As shown in FIG5 , QoS is scheduled on ports according to service priorities, while HQoS adds a multi-level scheduling model (FIG5 shows the 5-level scheduling model described above) based on the QoS scheduling mechanism to achieve more refined scheduling of resources.

TRUNK: It is a bundling technology. Multiple physical interfaces are bundled into a logical interface, which is called a TRUNK interface or a TRUNK port. Each physical interface bundled together is called a member interface. TRUNK technology can increase bandwidth, improve reliability and load sharing.

It should be understood that the traffic of a trunk port can include the traffic of multiple users, and the traffic of each user can correspond to multiple services. Therefore, HQoS technology can be used to perform hierarchical and refined scheduling of the traffic of the trunk port. For example, the traffic of the trunk port can also be scheduled through the above 5-level scheduling model.

In one implementation, the traffic of multiple member ports bound to the TRUNK port is centrally managed, and the traffic of multiple member ports is managed through a scheduling tree. FIG6 shows a schematic diagram of scheduling the traffic of the TRUNK port. As shown in FIG6, the TRUNK port is bound to three member ports, namely port 1, port 2 and port 3. Among them, port 1 can correspond to SQ1, port 2 can correspond to SQ2, port 3 can correspond to SQ3, SQ1, SQ2 and SQ3 can be mounted under the same GQ (i.e., GQ1), GQ1 is mounted under VI1, and VI1 is mounted under DP1. The scheduling process of the traffic of port 1 is SQ1→GQ1→VI1→DP1, the scheduling process of the traffic of port 2 is SQ2→GQ1→VI1→DP1, and the scheduling process of the traffic of port 3 is SQ3→GQ1→VI1→DP1. The three scheduling processes share the same scheduling tree.

In another implementation, the traffic of multiple member ports bound to the TRUNK port is managed separately, and the traffic of each member port is managed independently through a scheduling tree. Figure 7 shows another schematic diagram of scheduling the traffic of the TRUNK port. As shown in Figure 7, the TRUNK port is bound to three member ports, namely port 1, port 2 and port 3. Among them, port 1 can correspond to SQ1, port 2 can correspond to SQ2, and port 3 can correspond to SQ3. SQ1 is attached to GQ1, GQ1 is attached to VI1, VI1 is attached to DP1, and the scheduling process of the traffic of port 1 is SQ1→GQ1→VI1→DP1. SQ2 is attached to GQ2, GQ2 is attached to VI2, VI2 is attached to DP2, and the scheduling process of the traffic of port 2 is SQ2→GQ2→VI2→DP2. SQ3 is attached to GQ3, GQ3 is attached to VI3, VI3 is attached to DP3, and the scheduling process of the traffic of port 3 is SQ3→GQ3→VI3→DP3. The three scheduling processes use independent scheduling trees.

It is understandable that if the traffic of each member port in the TRUNK port is scheduled independently, there will be a problem of high consumption of traffic management chip resources. Every time a service traffic management is added to the TRUNK interface, hardware resources need to be consumed on each member scheduling tree of the TRUNK. Therefore, the current commonly used scheduling solution is to centrally manage the traffic of multiple member ports bound to the TRUNK port.

Back pressure: It is a dynamic feedback mechanism about processing capacity in streaming systems, which is feedback from downstream to upstream. When the downstream is not able to process enough traffic, it will gradually transmit back pressure signals to the upstream to instruct the upstream to suspend traffic transmission. The back pressure mechanism alleviates congestion by suppressing sources.

Pause frame: A pause frame is a control frame used to stop the data flow from being sent. If a forwarding device on a traffic path is congested, the device can generate a pause frame and send pause frames to the upstream of the traffic level to stop the data flow from being sent and relieve the congestion. The pause frame is a back pressure signal.

In the case of centralized traffic management of multiple member ports bound to a TRUNK port (as shown in FIG6 ), since multiple member ports share a scheduling tree, when the traffic of a member in the TRUNK is abnormal and congestion back pressure is generated, the traffic scheduling of the TRUNK port will be blocked as a whole, affecting the traffic forwarding of other normal member ports in the TRUNK. For example, FIG8 shows a schematic diagram of congestion back pressure, in which, after receiving a pause frame, port 1 will perform hop-by-hop back pressure along the scheduling tree (SQ1→GQ1→VI1→DP1) corresponding to port 1 to suppress source traffic. However, the traffic of port 2 and port 3 also needs to be scheduled through GQ1→VI1→DP1. As a result, the back pressure of port 1 will affect the scheduling capabilities of GQ1, VI1, and DP1 for traffic, and then affect the scheduling and forwarding of the traffic of port 2 and port 3.

When the traffic of multiple member ports bound to a trunk port is centrally managed, how to reduce the impact of member port traffic blocking on the entire trunk port traffic scheduling is a problem that needs to be solved.

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the present application, unless otherwise specified, "/" indicates that the objects associated before and after are in an "or" relationship, for example, A/B can represent A or B; "and/or" in the present application is only a kind of association relationship describing the associated objects, indicating that there can be three relationships, for example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. And, in the description of the present application, unless otherwise specified, "multiple" refers to two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c can be single or multiple. In addition, in order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second" and the like are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first", "second" and the like do not limit the quantity and execution order, and the words "first", "second" and the like do not necessarily limit the difference. At the same time, in the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for easy understanding.

The present application provides a congestion management method, the flowchart of which may be shown in FIG9 . The method may include the following steps:

Step 901: Perform an abnormality detection on a first physical member port included in a TRUNK port, where the first physical member port is any physical member port included in the TRUNK port.

Optionally, a TRUNK port may include multiple physical member ports, and the first physical member port is any one of the multiple physical member ports. For example, taking the TRUNK port in FIG. 6, FIG. 7 or FIG. 8 as an example, the TRUNK port may include three physical member ports, namely port 1, port 2 and port 3, and the first physical member port may be any one of port 1, port 2 or port 3.

Optionally, performing abnormality detection on the first physical member port included in the TRUNK port may specifically include: detecting the number of pause frames corresponding to the first physical member port and the traffic rate of the first physical member port. When the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold, and the traffic rate of the first physical member port is less than or equal to a second threshold, it is determined that the first physical member port is abnormal.

It is understandable that if congestion occurs in a physical member port in a TRUNK port, the device including the TRUNK port will generate a pause frame corresponding to the physical member port, and the pause frame is used to instruct the traffic queue corresponding to the physical member port to suspend sending.

Based on this, in an embodiment of the present application, if a pause frame corresponding to the first physical member port is detected, it means that congestion has occurred in the first physical member port. If the number of pause frames corresponding to the first physical member port detected per unit time is greater, it means that the congestion state of the first physical member port is more serious. In addition, the smaller the traffic rate of the first physical member port, the more serious the congestion state of the first physical member port. Therefore, if the number of pause frames corresponding to the first physical member port detected per unit time is large and the traffic rate of the first physical member port is small, it can be considered that the first physical member port is abnormal.

Optionally, performing an abnormality detection on the first physical member port included in the TRUNK port may specifically include: detecting the flow rate of the first physical member port. When the flow rate of the first physical member port is greater than or equal to a third threshold and the duration is greater than a fourth threshold, determining that the first physical member port is abnormal.

As a possible implementation, the third threshold may be close to the maximum rate/bandwidth of the first physical member port. If the traffic rate of the first physical member port is greater than or equal to the third threshold, it can be considered that the first physical member port is almost in a fully loaded state. It is understandable that if the first physical member port is in a state close to being fully loaded for a long time, then the first physical member port may be at risk of congestion. In order to prevent congestion of the first physical member port, the embodiment of the present application regards this situation as an abnormality of the first physical member port.

Step 902: When the first physical member port is abnormal, the first physical member port is disabled or the speed of the first physical member port is limited.

Optionally, when the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold, and the traffic rate of the first physical member port is less than or equal to a second threshold, the first physical member port may be disabled.

As a possible implementation manner, deactivating the first physical member port may specifically include: configuring the first physical member port to be in a DOWN state.

It is understandable that the state of the physical port may include an UP state and a DOWN state, and a physical port in the DOWN state (eg, the first physical member port) will not work and will not forward traffic.

Optionally, the method may further include: switching the traffic corresponding to the first physical member port to other physical member ports in the TRUNK port except the first physical member port for forwarding.

It should be understood that even if the first physical member port of the TRUNK port is DOWNed, the user traffic corresponding to the original first physical member port is still forwarded by the TRUNK port. In this case, the traffic corresponding to the first physical member port needs to be switched to other physical member ports in the TRUNK port except the first physical member port for forwarding. As a possible implementation method, the user traffic corresponding to the original first physical member port can be allocated to each physical member port in the TRUNK port except the first physical member port for forwarding based on the principle of load balancing.

Optionally, when the traffic rate of the first physical member port is greater than or equal to a third threshold and the duration thereof is greater than a fourth threshold, the rate of the first physical member port may be limited.

As a possible implementation method, limiting the speed of the first physical member port may specifically include: configuring CAR for the first physical member port, where CAR is used to limit the flow rate of the first physical member port. Among them, CAR can make the inbound and outbound flow rate of the first physical member port follow a certain standard upper limit. The present application can set the upper limit of CAR to be lower to achieve the purpose of speed limiting.

It should be understood that by limiting the speed of the first physical member port, the traffic subsequently transmitted by the first physical member port can be reduced, thereby alleviating congestion of the first physical member port and preventing congestion back pressure from being generated.

Optionally, after CAR is configured for the first physical member port, if it is detected that no abnormality occurs on the TRUNK port within a first continuous time period, the CAR rate limit on the first physical member port may be canceled.

In summary, the present application provides a congestion management method, and when a device detects an abnormality in a physical member port in a TRUNK port, the device can deactivate the physical member port or limit the speed of the physical member port, thereby resolving or alleviating the congestion of the physical member port in the TRUNK port. Based on this solution, the back pressure problem caused by the abnormality can be effectively avoided, and the head resistance of the TRUNK port can be reduced.

Next, the detailed process of the congestion management method provided by this application will be introduced in combination with the above description.

As a possible implementation, FIG10 shows a flow chart of another congestion management method provided by the present application, which may include the following steps:

Step 1001: Detect the number of pause frames corresponding to the first physical member port and the traffic rate of the first physical member port.

Step 1002: When the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold and the traffic rate of the first physical member port is less than or equal to a second threshold, determine that the first physical member port is abnormal.

Step 1003: configure the first physical member port to be in the DOWN state, and switch the traffic corresponding to the first physical member port to other physical member ports in the TRUNK port except the first physical member port for forwarding.

As another possible implementation, FIG11 shows a flow chart of another congestion management method provided by the present application, which may include the following steps:

Step 1101: Detect the flow rate of the first physical member port.

Step 1102: When the flow rate of the first physical member port is greater than or equal to the third threshold and the duration of the flow rate is greater than the fourth threshold, determine that the first physical member port is abnormal.

Step 1103: Configure CAR for the first physical member port, where CAR is used to limit the traffic rate of the first physical member port.

Optionally, the congestion management method of the present application can be applied to a network device such as a router or a switch, for example, it can be applied to a network device having the structure shown in Figure 2. As a possible implementation, configuring CAR for the first physical member port can be performed by a PFE in the device, and the detection of the pause frame, the traffic rate, or the traffic rate can be performed by a TM in the device.

Optionally, the embodiment of the present application further provides a communication device, which can be used to implement the above-mentioned various methods. It is understandable that, in order to implement the above-mentioned functions, the communication device includes a hardware structure and/or software module corresponding to each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

The embodiment of the present application can divide the functional modules of the communication device according to the above method embodiment. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

FIG12 shows a schematic diagram of the structure of a communication device 120, which may include an abnormality detection module 1201 and an abnormality handling module 1202. The abnormality detection module 1201 is used to perform abnormality detection on a first physical member port included in a TRUNK port, where the first physical member port is any physical member port included in the TRUNK port. The abnormality handling module 1202 is used to disable the first physical member port or limit the speed of the first physical member port when the first physical member port is abnormal.

Optionally, when performing anomaly detection on the first physical member port included in the TRUNK port, the anomaly detection module 1201 can be specifically used to detect the number of pause frames corresponding to the first physical member port and the traffic rate of the first physical member port. The anomaly detection module 1201 can also be used to determine that the first physical member port is abnormal when the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold and the traffic rate of the first physical member port is less than or equal to a second threshold.

Optionally, when the first physical member port is disabled, the exception handling module 1202 is specifically configured to configure the first physical member port to be in a DOWN state.

Optionally, the exception handling module 1202 may also be configured to switch the traffic corresponding to the first physical member port to other physical member ports in the TRUNK port except the first physical member port for forwarding.

Optionally, when performing anomaly detection on the first physical member port included in the TRUNK port, the anomaly detection module 1201 can be specifically used to detect the flow rate of the first physical member port. The anomaly detection module 1201 can also be used to determine that the first physical member port is abnormal when the flow rate of the first physical member port is greater than or equal to the third threshold and the duration is greater than the fourth threshold.

Optionally, when limiting the rate of the first physical member port, the exception handling module 1202 may be specifically configured to configure a committed access rate CAR for the first physical member port, where CAR is used to limit the traffic rate of the first physical member port.

It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module, which will not be repeated here. Since the communication device 120 provided in this embodiment can execute the above congestion management method, the technical effects that can be obtained can refer to the above method embodiment, which will not be repeated here.

Optionally, in this embodiment, the communication device 120 is presented in the form of dividing various functional modules in an integrated manner. The "module" here may refer to a specific ASIC, circuit, processor and memory that executes one or more software or firmware programs, integrated logic circuit, and/or other devices that can provide the above functions.

In a possible implementation, those skilled in the art may imagine that the communication device 120 may take the form of a communication device 130 shown in FIG13. For example, FIG13 shows a schematic diagram of the structure of another communication device provided in an embodiment of the present application. As shown in FIG13, the communication device 130 includes one or more processors 1301, a communication line 1302, and at least one communication interface (FIG. 13 is only exemplary to include a communication interface 1303 and a processor 1301 as an example for explanation), and may optionally include a memory 1304.

The processor 1301 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

The communication line 1302 may include a pathway for communication between different components.

The communication interface 1303 may be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (WLAN), etc. For example, the transceiver module may be a device such as a transceiver or a transceiver. Optionally, the communication interface 1303 may also be a transceiver circuit located in the processor 1301 to implement signal input and signal output of the processor.

The memory 1304 may be a device with a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory may exist independently and be connected to the processor via a communication line 1302. The memory may also be integrated with the processor.

The memory 1304 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 1301. The processor 1301 is used to execute the computer-executable instructions stored in the memory 1304, thereby implementing the congestion management method provided in the embodiment of the present application.

Alternatively, optionally, in an embodiment of the present application, the processor 1301 may also perform processing-related functions in the congestion management method provided in the following embodiments of the present application, and the communication interface 1303 is responsible for communicating with other devices or communication networks, which is not specifically limited in the embodiments of the present application.

Optionally, the computer-executable instructions in the embodiments of the present application may also be referred to as application code, which is not specifically limited in the embodiments of the present application.

In a specific implementation, as an embodiment, the processor 1301 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 13 .

In a specific implementation, as an embodiment, the communication device 130 may include multiple processors, such as the processor 1301 and the processor 1307 in FIG. 13. Each of these processors may be a single-core processor or a multi-core processor. The processors here may include but are not limited to at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller unit (MCU), or an artificial intelligence processor and other types of computing devices running software, each of which may include one or more cores for executing software instructions to perform calculations or processing.

In a specific implementation, as an embodiment, the communication device 130 may further include an output device 1305 and an input device 1306. The output device 1305 communicates with the processor 1301 and may display information in a variety of ways. For example, the output device 1305 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 1306 communicates with the processor 1301 and may receive user input in a variety of ways.

The above-mentioned communication device 130 may sometimes also be referred to as a communication device, which may be a general device or a dedicated device. For example, the communication device 130 may be a switch, a router, or a device having a similar structure as shown in FIG13. The embodiment of the present application does not limit the type of the communication device 130.

Optionally, the processor 1301 in the communication device 130 shown in FIG. 13 may call computer-executable instructions stored in the memory 1304 to enable the communication device 130 to execute the congestion management method in the above method embodiment.

It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing a computer program instruction on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or may contain one or more servers, data centers and other data storage devices that can be integrated with a medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

As used in this application, the terms "component", "module", "system", etc. are intended to refer to a computer-related entity, which can be hardware, firmware, a combination of hardware and software, software, or software in operation. For example, a component can be, but is not limited to: a process running on a processor, a processor, an object, an executable file, a thread in execution, a program, and/or a computer. As an example, an application running on a computing device and the computing device can both be components. One or more components can exist in a process and/or thread in execution, and a component can be located in a computer and/or distributed between two or more computers. In addition, these components can be executed from various computer-readable media with various data structures thereon. These components can communicate in a local and/or remote process manner, such as according to a signal with one or more data packets (for example, data from a component, which interacts with another component in a local system, a distributed system, and/or interacts with other systems in a signal manner through a network such as the Internet).

The present application presents various aspects, embodiments, or features around a system that may include multiple devices, components, modules, etc. It should be understood and appreciated that each system may include additional devices, components, modules, etc., and/or may not include all of the devices, components, modules, etc. discussed in conjunction with the figures. In addition, combinations of these schemes may also be used.

In addition, in the embodiments of the present application, the word "exemplary" is used to indicate an example, illustration or description. Any embodiment or design described as "exemplary" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the word "exemplary" is used to present concepts in a concrete way.

The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. A person of ordinary skill in the art can appreciate that with the evolution of the network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims (14)

1. A congestion management method, characterized in that the method comprises: Performing an abnormality detection on a first physical member port included in the TRUNK port, where the first physical member port is any physical member port included in the TRUNK port; When the first physical member port is abnormal, the first physical member port is disabled or a speed limit is imposed on the first physical member port. 2. The method according to claim 1, wherein the performing abnormality detection on the first physical member port included in the TRUNK port comprises: Detecting the number of pause frames corresponding to the first physical member port and the traffic rate of the first physical member port; When the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold, and the traffic rate of the first physical member port is less than or equal to a second threshold, it is determined that the first physical member port is abnormal. 3. The method according to claim 2, wherein deactivating the first physical member port comprises: Configure the first physical member port to be in DOWN state. 4. The method according to claim 3, characterized in that the method further comprises: Switch the traffic corresponding to the first physical member port to other physical member ports in the TRUNK port except the first physical member port for forwarding. 5. The method according to claim 1, wherein the performing abnormality detection on the first physical member port included in the TRUNK port comprises: Detecting the flow rate of the first physical member port; When the flow rate of the first physical member port is greater than or equal to the third threshold and the duration thereof is greater than the fourth threshold, it is determined that the first physical member port is abnormal. 6. The method according to claim 5, wherein limiting the rate of the first physical member port comprises: A committed access rate CAR is configured for the first physical member port, where the CAR is used to limit the traffic rate of the first physical member port. 7. A communication device, characterized in that the communication device comprises: an abnormality detection module, configured to perform abnormality detection on a first physical member port included in the TRUNK port, where the first physical member port is any physical member port included in the TRUNK port; The exception handling module is used to disable the first physical member port or limit the speed of the first physical member port when the first physical member port is abnormal. 8. The communication device according to claim 7 is characterized in that the abnormality detection module is used to perform abnormality detection on the first physical member port included in the TRUNK port, including: the abnormality detection module is used to detect the number of pause frames corresponding to the first physical member port and the traffic rate of the first physical member port; the abnormality detection module is also used to determine that the first physical member port is abnormal when the number of pause frames corresponding to the first physical member port detected within a unit time is greater than or equal to a first threshold and the traffic rate of the first physical member port is less than or equal to a second threshold. 9. The communication device according to claim 8 is characterized in that the exception handling module is used to deactivate the first physical member port, including: the exception handling module is used to configure the first physical member port to a DOWN state. 10. The communication device according to claim 9, characterized in that the exception handling module is further used to switch the traffic corresponding to the first physical member port to other physical member ports in the TRUNK port except the first physical member port for forwarding. 11. The communication device according to claim 7 is characterized in that the abnormality detection module is used to perform abnormality detection on the first physical member port included in the TRUNK port, including: the abnormality detection module is used to detect the traffic rate of the first physical member port; the abnormality detection module is also used to determine that the first physical member port is abnormal when the traffic rate of the first physical member port is greater than or equal to a third threshold and the duration is greater than a fourth threshold. 12. The communication device according to claim 11 is characterized in that the exception handling module is used to limit the speed of the first physical member port, including: the exception handling module is used to configure a committed access rate CAR for the first physical member port, and the CAR is used to limit the traffic rate of the first physical member port. 13. A communication device, characterized in that the communication device comprises: a processor and a memory; The memory is used to store computer-executable instructions. When the processor executes the computer-executable instructions, the communication device executes the method according to any one of claims 1 to 6. 14. A computer-readable storage medium, characterized in that a computer program is stored thereon, and when the computer program is executed by a computer, the computer is caused to execute the method according to any one of claims 1 to 6.