CN102025617B - Method and device for controlling congestion of Ethernet - Google Patents
Method and device for controlling congestion of Ethernet Download PDFInfo
- Publication number
- CN102025617B CN102025617B CN201010560688.0A CN201010560688A CN102025617B CN 102025617 B CN102025617 B CN 102025617B CN 201010560688 A CN201010560688 A CN 201010560688A CN 102025617 B CN102025617 B CN 102025617B
- Authority
- CN
- China
- Prior art keywords
- message
- cnm
- pfc
- congestion
- inbound port
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
Abstract
The invention discloses method and device for controlling congestion of an Ethernet. The method comprises the following steps of: closing an ingress port of core network equipment with the function of congestion detection to trigger a flow control PFC (Power Factor Correction) mechanism based on priority through a threshold; detecting whether a message forwarded by the ingress port is a CNM (Congestion Notification Message) or not; generating a PFC message according to the CNM if the message forwarded by the ingress port is the CNM; and forwarding the CNM through the ingress port and notifying the opposite-end equipment of suspending the data transfer of a corresponding queue according to the PFC message. With the technical scheme of the invention, the congestion problem can be quickly and effectively solved fundamentally.
Description
Technical field
The present invention relates to field of mobile communication, particularly relate to a kind of Ethernet jamming control method and device.
Background technology
In the related, data center be enterprise's applied business service center is provided, be the center of data operation, exchange, storage.Data center combines advanced network technology and memory technology, carries service request and the memory data output of in network more than 80%, for the health running of client traffic system provides service and operation platform.Fig. 1 is the schematic diagram of data center network framework in prior art; as shown in Figure 1; in enterprise data center; be deployed with three kinds of distinct networks: usually can dispose the Ethernet that is supported IP flow; one or two support that optical-fibre channel stores the Storage are network of flow, support the InfiniBand network that High-Performance Computing Cluster calculates for one.Dispose and manage the distinct network of this three class and can bring high investment and operation cost to enterprise, therefore enterprise urgently wishes to realize integrating on a unified array.
Ethernet, because of advantages such as it is with low cost, technology maturation, favorable expandability, is shown one's talent in numerous integration technology.The local area network (LAN) of data center, storage area network and high-performance calculation application program permeate a single Ethernet interconnect architecture by this Ethernet.The current speed of this Ethernet is 10Gbps, brings up to 40G to 100Gbps the most at last.
At present, Ethernet itself is not because providing storage and high-performance calculation traffic service and carried out optimization, therefore, packet loss phenomenon is likely there is when occurring congested, for addressing this problem, work out the multinomial technology for ensureing harmless ether, comprise quantification congestion notification agreement (the QuantizedCongestion Notification protocol for congestion control, referred to as QCN) and based on the Flow Control (Priority-based Flow Control, referred to as PFC) of priority.Fig. 2 is the schematic diagram of QCN operation principle in prior art, as shown in Figure 2, QCN is a kind of quantification Research of Congestion Control Techniques, backward congestion notification mechanism relatively is accurately have employed relative to other congestion management techniques, at core network device, congestion detection point is set based on outbound port queue, detect that congestion notification message (the Congestion Notification Message comprising Congestion Level SPCC is then set up in congested generation, referred to as CNM), and by CNM back-pressure to causing congested source terminal, it is made to reduce the data transfer rate of respective queue according to CNM instruction, QCN can find congested source relatively accurately, from solving congestion problems at all, but its response speed is slower, surge cannot be tackled, Fig. 3 is the schematic diagram of PFC operation principle in prior art, as shown in Figure 3, PFC is the enhancing in time-out (Pause) mechanism to 802.3ad, flow is divided into 8 priority by the precedence field of VLAN tag in 802.1Q agreement, independently Pause mechanism is realized respectively to the flow of each priority, the response speed of PFC is very fast, can rapid recovery network congestion problem, for network surge or congested in short-term there is positive effect, but, PFC is because of its agreement feature, can only interiorly among a small circle use, and the solution network congestion problem that it is not basic, still packet loss phenomenon is there will be for congested for a long time.Two agreement conbined usage are then by the network congestion of PFC respite, and QCN then utilizes PFC to be the time that it is alleviated, from solving congestion problems at all.
By the integrated application to above-mentioned two standards, effectively can solve the congestion problems of network, reduce packet loss.But, in actual applications, when these two kinds of mechanism use jointly, arranging of these two kinds of machine-processed activation threshold values is difficult to grasp, is easy to the problem causing Failure Of Protocol, even can causes Network Packet Loss.Fig. 4 is the schematic diagram that in prior art, PFC and QCN applies jointly, as shown in Figure 4, equipment of the core network E supports QCN and PFC, the threshold value triggered as PFC arranges lower, so PFC will preact, PFC mechanism is triggered to A, B, C, D, F, and then causes the inefficacy of QCN agreement, when meet with long-time congested time, PFC mechanism then can cause congested diffusion even packet loss.
In the prior art, a solution is had to be the higher of the threshold value setting triggered by PFC, it is relatively lower that the threshold value of QCN is arranged, ensure that QCN acts on prior to PFC as far as possible, the queue that this scheme also has problem: a QCN mechanism to detect, it is the flow converging multiple inbound port, corresponding 3 inbound ports of outbound port as a QCN effect of equipment of the core network E in Fig. 4, the buffer memory of outbound port is greater than inbound port buffer memory under normal circumstances, suppose that the buffer memory of outbound port is 500K, each inbound port buffer memory is 100K, QCN acts on outbound port, arrange that its trigger gate is limited to buffer memory 20%, i.e. 100k, PFC acts on inbound port, arrange that its trigger gate is limited to buffer memory 80%, i.e. 80K, only have when three inbound port a certain priority query buffer memory summations are greater than 100K and each inbound port buffer memory is less than 80K (such as, all reach 34K) time, QCN acts on prior to PFC, if a certain inbound port buffer memory a certain moment is greater than 80k, other two inbound port summations are less than 20K, first the inbound port being so greater than 80K triggers PFC, cause QCN Failure Of Protocol, if congested for a long time, congested diffusion and packet loss can be caused.Visible, passing threshold configuration can not solve well and first trigger QCN Failure Of Protocol after PFC and the problem of the congested diffusion that causes and packet loss.
Summary of the invention
The invention provides a kind of Ethernet jamming control method and device, can not solve first trigger QCN Failure Of Protocol after PFC and the problem of the congested diffusion that causes and packet loss to solve the configuration of prior art passing threshold.
The invention provides a kind of Ethernet jamming control method, comprising:
Close the equipment of the core network inbound port passing threshold triggering with congestion detection function machine-processed based on the Flow Control PFC of priority;
Whether the message detecting inbound port forwarding is congestion notification message CNM, when determining that message is CNM, generates PFC message according to CNM;
Forward CNM by inbound port, and notify that opposite equip. suspends the data transmission of respective queue according to PFC message.
Preferably, when the edge device determination terminal be connected with terminal is not supported to quantize congestion notification agreement QCN, also comprise: whether the message that the inbound port that edge device detects self in a predefined manner forwards is CNM, when determining that message is CNM, generate PFC message according to CNM, and notification terminal suspends the data transmission of respective queue according to PFC message.
Present invention also offers a kind of Ethernet congestion control device, comprising:
Closing module, machine-processed based on the Flow Control PFC of priority for closing the equipment of the core network inbound port passing threshold triggering with congestion detection function;
First detects generation module, and whether the message forwarded for detecting inbound port is congestion notification message CNM, and when determining that message is CNM, generates PFC message according to CNM;
Sending module, for forwarding CNM by inbound port, and notifies that opposite equip. suspends the data transmission of respective queue according to PFC message.
Preferably, Ethernet congestion control device also comprises: second detects generation module, for not supporting in the terminal determining to be connected with self to quantize congestion notification agreement QCN, whether the message that the inbound port detecting self in a predefined manner forwards is CNM, when determining that message is CNM, generate PFC message according to CNM, and notification terminal suspends the data transmission of respective queue according to PFC message.
Beneficial effect of the present invention is as follows:
By the PFC of CNM message trigger respective priority, solve the configuration of passing threshold in prior art can not solve first trigger PFC after the problem of QCN Failure Of Protocol and the congested diffusion that causes and packet loss, when each QCN mechanism produces CNM message, the PFC of port respective priority is triggered by the port that back-pressure is gone back in capital, PFC can respond and alleviating network congestion fast, QCN then carries out the adjustment of respective streams speed by CNM message indicating terminal, fundamentally fast and effeciently solve congestion problems.
Accompanying drawing explanation
Fig. 1 is the schematic diagram of data center network framework in prior art;
Fig. 2 is the schematic diagram of QCN operation principle in prior art;
Fig. 3 is the schematic diagram of PFC operation principle in prior art;
Fig. 4 is the schematic diagram that in prior art, PFC and QCN applies jointly;
Fig. 5 is the flow chart of the Ethernet jamming control method of the embodiment of the present invention;
Fig. 6 is the detailed process figure of the Ethernet jamming control method of the embodiment of the present invention;
Fig. 7 is the network architecture schematic diagram of the embodiment of the present invention;
Fig. 8 is the structural representation of the Ethernet congestion control device of the embodiment of the present invention.
Embodiment
Can not solve first trigger QCN Failure Of Protocol after PFC and the problem of the congested diffusion that causes and packet loss to solve the configuration of prior art passing threshold, the invention provides a kind of Ethernet jamming control method and device, effectively can solve two kinds of agreements in network and use the Failure Of Protocol of generation simultaneously and then cause the problem of packet loss.Below in conjunction with accompanying drawing and embodiment, the present invention is further elaborated.Should be appreciated that specific embodiment described herein only in order to explain the present invention, do not limit the present invention.
Embodiment of the method
According to embodiments of the invention, provide a kind of Ethernet jamming control method, Fig. 5 is the flow chart of the Ethernet jamming control method of the embodiment of the present invention, and as shown in Figure 5, the Ethernet jamming control method according to the embodiment of the present invention comprises following process:
Step 501, the Flow Control PFC that the equipment of the core network inbound port passing threshold that closedown has congestion detection function triggers based on priority is machine-processed, namely closes PFC initiator function.Wherein, the equipment of the core network with congestion detection function has the function by CNM message trigger PFC at inbound port.
Step 502, whether the message detecting inbound port forwarding is congestion notification message CNM, when determining that message is CNM, generates PFC message according to CNM;
Below the emphasis field comprised in CNM and the PFC message related in step 502 and implication thereof are described in detail.
The emphasis field comprised in CNM and implication thereof:
1, CN-TAG: for its CN-TAG of frame extracting directly carrying CN-TAG, for the Frame not carrying CN-TAG, this field is filled with 0.
2、CNM PDU：
Version: full 0, receiving terminal is ignored, and does not deal with;
Reserved: full 0, receiving end is ignored, and does not process;
Quantized feedback: the Fb value that congestion detection point (CP) calculates, is used to indicate terminal RP and carries out speed adjustment;
CPID: unique mark identifying a CP in CDN;
Qoffset (signed integer): the cpQoffset value indicating CP in units of 64octets.
QDelta (signed integer): the cpQDelta value indicating CP in units of 64octets.
Encapsulated priority: the Frame priority value triggering CNM message.
Encapsulated D-mac: the target MAC (Media Access Control) address triggering the Frame of CNM message;
The length of Encapsulated MSDU length: instruction encapsulated MSDU field;
Encapsulated MSDU: maximum 64 eight bit groups, comprises the data frame data unit mac_service_data_unit forward part content triggering CNM message.
The emphasis field that PFC message comprises and implication thereof:
1, Destination Address: order way address can be 01-80-C2-00-00-01;
2, Source Address: source address, can be transmitting terminal address, Ethertype be 88-08;
3, control opcode is that 01-01 represents PFC frame;
4, the least-significant byte bit of Priority_enable_vector field corresponding each priority respectively, whether the time field being used to refer to each priority is below effective;
5, time [n] field represents that each priority class traffic need stop the duration sending.
Particularly, step 502 needs to be handled as follows:
Step 1, the source MAC address of message that inbound port forwards to be detected, judge that whether the source MAC of message is the MAC Address of equipment of itself;
Step 2, if the judgment is Yes, then judge whether identification message is CNM for the protocol Data Unit type of message;
Step 3, if the judgment is Yes, then determine that message is CNM.
That is, in step 1-step 3, during port repeat data message, the source address of message is monitored, in actual applications, can judge according to " the SA=CP bridge address " field comprised in CNM that whether the source MAC of message is self MAC Address, that is, judge whether this message is sent by self; Be the message of own MAC address for source address, according in " PDU TYPE " field comprised in CNM being whether 0X22e7 (0X22e7 is CNM mark), determine whether CNM, if the judgment is Yes, then start the mechanism being triggered PFC by CNM.
Step 4, when determining that message is CNM, according to the encapsulation priority of carrying in CNM, to determine in PFC message the priority corresponding to tentative instruction;
Step 5, according to the field being used to indicate Congestion Level SPCC of carrying in CNM, determine the time span suspending instruction in PFC message.
That is, in step 4-step 5, need to resolve CNM message, according to the encapsulation priority that it carries, trigger the generation of PFC respective priority PAUSE instruction, and according to the field being used to indicate Congestion Level SPCC of carrying in CNM PDU, the time span of instruction pause.Particularly, according to " Encapsulated priority " field in CNM, determine the priority query of PFC machining function, and " priority_enable_vector " field in PFC message is arranged; According to " QntzFb " field in CNM, determine the duration of respective priority pause, and " time (n) " field in PFC message is arranged.
Step 503, forwards CNM by inbound port, and notifies that opposite equip. suspends the data transmission of respective queue according to PFC message.That is, in step 503, CNM message normally forwards at port, and the technical scheme of the embodiment of the present invention does not have an impact to QCN mechanism.
Below in conjunction with accompanying drawing, be described in detail to the handling process of embodiment of the present invention technical scheme, Fig. 6 is the detailed process figure of the Ethernet jamming control method of the embodiment of the present invention, as shown in Figure 6, comprises following process:
Step 601, starting the core network device inbound port of QCN mechanism, closes the PFCinitiator function of its port, starts the function being triggered PFC mechanism by CNM.Wherein, PFC initiator function is the mechanism by triggering PFC to the judgement of inbound port cache threshold;
Step 602, the port starting this function monitors the source MAC that it E-Packets;
Step 603, judges whether message source address is own MAC address, if so, then performs step 604, otherwise goes to step 607;
Step 604, judges message message PDU type, if 0x22e7 then proves that this message is CNM, performs step 605, otherwise goes to step 607;
Step 605, starts the mechanism of the CNM message trigger PFC by QCN, and sets up PFC message according to CNM message encapsulation information.This process should not affect the normal forwarding of CNM message at port;
Step 606, uses the PFC message pause respective queue that step 605 produces;
Step 607, data message is not CNM message, according to normal forwarding process process.
In actual applications, when the edge device determination terminal be connected with terminal is not supported to quantize congestion notification agreement QCN, PFC mechanism can be triggered at QCN network edge, comprise following process: whether the message that the inbound port that edge device detects self in a predefined manner forwards is CNM, when determining that message is CNM, generate PFC message according to CNM, and notification terminal suspends the data transmission of respective queue according to PFC message.Wherein, above-mentioned predetermined way is: edge device judges that whether identification message is CNM for the protocol Data Unit type of message, if the judgment is Yes, then determines that message is CNM.That is, edge device need not judge whether CNM is what self send.
The situation that terminal does not support QCN is mainly tackled in above-mentioned process.In above-mentioned situation, as long as the inbound port function in embodiment of the present invention technical scheme to be displaced downwardly to QCN network edge (network equipment be directly connected with terminal), Fig. 7 is the network architecture schematic diagram of the embodiment of the present invention, under network architecture as shown in Figure 7, suppose that A does not support QCN, namely A can not identify CNM message, then start the mechanism solution congestion problems being triggered PFC by QCN at the inbound port of equipment D.
Below, the technical scheme of composition graphs 7 pairs of embodiment of the present invention is illustrated.
Under network architecture as shown in Figure 7, E is the core network device being configured with congestion detection function, QCN mechanism is provided with congestion detection point CP at its outbound port, this CP carries out congestion detection for the queue that priority is 1, the inbound port of E all starts the function being triggered PFC by QCN, the mechanism of former inbound port threshold triggers PFC is closed, in embodiments of the present invention, suppose that network congestion is caused by device A, the outbound port CP point of equipment E detects congestion situation, then set up the CNM message comprising priority 1, former road back-pressure is to device A, notify that it reduces the data transfer rate of relative priority queue, the inbound port of equipment E detects the forwarding bag that it processes, when judging that message is CNM message according to source address and PDU type field, then CNM is resolved, produce PFC message, in PFC message, priority_enable_vector priority is 1 position, corresponding bit position, time (1) time span is arranged according to Congestion Level SPCC, start PFC mechanism, notice D suspends the data transmission that priority is the queue of 1.
In embodiments of the present invention, if device A does not support QCN, then D resolves the CNM that it receives, judge whether the field " PDU type " in CNM is 0x22e7, if, then confirmation message is CNM, generates PFC message according to CNM, and notice A suspends the data transmission that priority is the queue of 1.
As can be seen from foregoing description, the embodiment of the present invention efficiently solves the problem of the protocol validity of QCN and PFC conbined usage, when core-network entities occurs congested, first outbound port detects congestion situation, create CNM message according to congestion situation, CNM message will by inbound port back-pressure to corresponding terminal, and inbound port is by resolving the identification of CNM, trigger PFC mechanism, the corresponding priority query of pause.Make the congested diffusion problem that PFC mechanism causes, finally also can be solved with coming into force of QCN, fundamentally fast and effeciently can solve congestion problems.
Device embodiment
According to embodiments of the invention, provide a kind of Ethernet congestion control device, Fig. 8 is the structural representation of the Ethernet congestion control device of the embodiment of the present invention, as shown in Figure 8, Ethernet congestion control device according to the embodiment of the present invention comprises: closing module 80, first detects generation module 82, sending module 84, is described in detail below to the modules of the embodiment of the present invention.
Closing module 80 is machine-processed based on the Flow Control PFC of priority for closing the equipment of the core network inbound port passing threshold triggering with congestion detection function, namely closes PFC initiator function.
First detects generation module 82 for detecting whether the message of inbound port forwarding is congestion notification message CNM, and when determining that message is CNM, generates PFC message according to CNM;
Below the emphasis field comprised in CNM and the PFC message related in the first detection generation module 82 and implication thereof are described in detail.
The emphasis field comprised in CNM and implication thereof:
1, CN-TAG: for its CN-TAG of frame extracting directly carrying CN-TAG, for the Frame not carrying CN-TAG, this field is filled with 0.
2、CNM PDU：
Version: full 0, receiving terminal is ignored, and does not deal with;
Reserved: full 0, receiving end is ignored, and does not process;
Quantized feedback: the Fb value that congestion detection point (CP) calculates, is used to indicate terminal RP and carries out speed adjustment;
CPID: unique mark identifying a CP in CDN;
Qoffset (signed integer): the cpQoffset value indicating CP in units of 64octets.
QDelta (signed integer): the cpQDelta value indicating CP in units of 64octets.
Encapsulated priority: the Frame priority value triggering CNM message.
Encapsulated D-mac: the target MAC (Media Access Control) address triggering the Frame of CNM message;
The length of Encapsulated MSDU length: instruction encapsulated MSDU field;
Encapsulated MSDU: maximum 64 eight bit groups, comprises the data frame data unit mac_service_data_unit forward part content triggering CNM message.
The emphasis field that PFC message comprises and implication thereof:
1, Destination Address: order way address can be 01-80-C2-00-00-01;
2, Source Address: source address, can be transmitting terminal address, Ethertype be 88-08;
3, control opcode is that 01-01 represents PFC frame;
4, the least-significant byte bit of Priority_enable_vector field corresponding each priority respectively, whether the time field being used to refer to each priority is below effective;
5, time [n] field represents that each priority class traffic need stop the duration sending.
Particularly, the first detection generation module 82 specifically comprises:
First judges submodule, and the source MAC address for the message forwarded inbound port detects, and judges that whether the source MAC of message is the MAC Address of equipment of itself;
Second judges submodule, for when first judges that submodule is judged as YES, then judges whether identification message is CNM for the protocol Data Unit type of message;
Determine submodule, for when second judges that submodule is judged as YES, determine that message is CNM;
During port repeat data message, first detects generation module 82 needs to monitor the source address of message, in actual applications, first judges that submodule can judge according to " the SA=CP bridge address " field comprised in CNM that whether the source MAC of message is self MAC Address, that is, judge whether this message is sent by self; Be the message of own MAC address for source address, second judges that submodule is according in " PDU TYPE " field comprised in CNM being whether 0X22e7 (0X22e7 is CNM mark), determine whether CNM, if the judgment is Yes, then determine that submodule determination message is CNM, the mechanism being triggered PFC by CNM can be started.
First generates submodule, for according to the encapsulation priority of carrying in CNM, determines the priority corresponding to tentative instruction in PFC message;
Second generates submodule, for according to the field being used to indicate Congestion Level SPCC of carrying in CNM, determines the time span suspending instruction in PFC message.
First detects generation module 82 also needs to resolve CNM message, according to the encapsulation priority that it carries, trigger the generation of PFC respective priority PAUSE instruction, and according to the field being used to indicate Congestion Level SPCC of carrying in CNM PDU, the time span of instruction pause.Particularly, first generates submodule according to " Encapsulated priority " field in CNM, determines the priority query of PFC machining function, and arranges " priority_enable_vector " field in PFC message; Second generates submodule according to " QntzFb " field in CNM, determines the duration of respective priority pause, and arranges " time (n) " field in PFC message.
Sending module 84 for forwarding CNM by inbound port, and notifies that opposite equip. suspends the data transmission of respective queue according to PFC message.That is, CNM message normally forwards at port, and the technical scheme of the embodiment of the present invention does not have an impact to QCN mechanism.
The particular flow sheet of above-mentioned process can be understood with reference to Fig. 6.
In actual applications, when the edge device determination terminal be connected with terminal is not supported to quantize congestion notification agreement QCN, in this device second detects generation module can trigger PFC mechanism at QCN network edge, whether the message that the inbound port detecting self in a predefined manner forwards is CNM, when determining that message is CNM, generate PFC message according to CNM, and notification terminal suspends the data transmission of respective queue according to PFC message.Wherein, above-mentioned predetermined way is: judge that whether identification message is CNM for the protocol Data Unit type of message, if the judgment is Yes, then determines that message is CNM.That is, the second detection generation module need not judge whether CNM is what self send.
The situation that terminal does not support QCN is mainly tackled in above-mentioned process.In above-mentioned situation, as long as the inbound port function in embodiment of the present invention technical scheme to be displaced downwardly to QCN network edge (network equipment be directly connected with terminal), under network architecture as shown in Figure 7, suppose that A does not support QCN, namely A can not identify CNM message, then start the mechanism solution congestion problems being triggered PFC by QCN at the inbound port of equipment D.
Below, the technical scheme of composition graphs 7 pairs of embodiment of the present invention is illustrated.
Under network architecture as shown in Figure 7, E is for being configured with the core network device (the Ethernet congestion control device described in the embodiment of the present invention) of congestion detection function, QCN mechanism is provided with congestion detection point CP at its outbound port, this CP carries out congestion detection for the queue that priority is 1, the inbound port of E all starts the function being triggered PFC by QCN, the mechanism of former inbound port threshold triggers PFC is closed, in embodiments of the present invention, suppose that network congestion is caused by device A, the outbound port CP point of equipment E detects congestion situation, then set up the CNM message comprising priority 1, former road back-pressure is to device A, notify that it reduces the data transfer rate of relative priority queue, the inbound port of equipment E detects the forwarding bag that it processes, when judging that message is CNM message according to source address and PDU type field, then CNM is resolved, produce PFC message, in PFC message, priority_enable_vector priority is 1 position, corresponding bit position, time (1) time span is arranged according to Congestion Level SPCC, start PFC mechanism, notice D suspends the data transmission that priority is the queue of 1.
In embodiments of the present invention, if device A does not support QCN, then D resolves the CNM that it receives, judge whether the field " PDU type " in CNM is 0x22e7, if, then confirmation message is CNM, generates PFC message according to CNM, and notice A suspends the data transmission that priority is the queue of 1.
In sum, the embodiment of the present invention is by the PFC of CNM message trigger respective priority, solve the configuration of passing threshold in prior art can not solve first trigger PFC after the problem of QCN Failure Of Protocol and the congested diffusion that causes and packet loss, when each QCN mechanism produces CNM message, the PFC of port respective priority is triggered by the port that back-pressure is gone back in capital, PFC can respond and alleviating network congestion fast, QCN then carries out the adjustment of respective streams speed by CNM message indicating terminal, fundamentally fast and effeciently solve congestion problems.
Although be example object, disclose the preferred embodiments of the present invention, it is also possible for those skilled in the art will recognize various improvement, increase and replacement, and therefore, scope of the present invention should be not limited to above-described embodiment.
Claims (8)
1. an Ethernet jamming control method, is characterized in that, comprising:
Close the equipment of the core network inbound port passing threshold triggering with congestion detection function machine-processed based on the Flow Control PFC of priority;
Whether the message detecting the forwarding of described inbound port is congestion notification message CNM, when determining that described message is described CNM, generates PFC message according to described CNM; Wherein, whether the message that the described inbound port of described detection forwards is that congestion notification message CNM comprises: detect the source MAC address of the described message that described inbound port forwards, and judges that whether the source MAC of described message is the MAC Address of equipment of itself; If the judgment is Yes, then judging whether the protocol Data Unit type of described message identifies described message is CNM; If the judgment is Yes, then determine that described message is CNM;
Forward described CNM by described inbound port, and notify that opposite equip. suspends the data transmission of respective queue according to described PFC message.
2. the method for claim 1, is characterized in that, described method also comprises:
When the edge device be connected with terminal determines that described terminal is not supported to quantize congestion notification agreement QCN, whether the message that the inbound port that described edge device detects self in a predefined manner forwards is described CNM, when determining that described message is described CNM, generate described PFC message according to described CNM, and notify that described terminal suspends the data transmission of respective queue according to described PFC message.
3. method as claimed in claim 1 or 2, is characterized in that, generates PFC message comprise according to described CNM:
According to the encapsulation priority of carrying in described CNM, determine the priority corresponding to tentative instruction in described PFC message;
According to the field being used to indicate Congestion Level SPCC of carrying in described CNM, determine the time span suspending instruction described in described PFC message.
4. method as claimed in claim 2, it is characterized in that, described predetermined way is:
It is CNM that described edge device judges whether the protocol Data Unit type of described message identifies described message, if the judgment is Yes, then determines that described message is CNM.
5. an Ethernet congestion control device, is characterized in that, comprising:
Closing module, machine-processed based on the Flow Control PFC of priority for closing the equipment of the core network inbound port passing threshold triggering with congestion detection function;
First detects generation module, and whether the message forwarded for detecting described inbound port is congestion notification message CNM, and when determining that described message is described CNM, generates PFC message according to described CNM; Described first detects generation module specifically comprises: first judges submodule, and the source MAC address for the described message forwarded described inbound port detects, and judges that whether the source MAC of described message is the MAC Address of equipment of itself; Second judges submodule, and for when described first judges that submodule is judged as YES, then judging whether the protocol Data Unit type of described message identifies described message is CNM; Determine submodule, for when described second judges that submodule is judged as YES, determine that described message is CNM;
Sending module, for forwarding described CNM by described inbound port, and notifies that opposite equip. suspends the data transmission of respective queue according to described PFC message.
6. device as claimed in claim 5, it is characterized in that, described device also comprises:
Second detects generation module, for not supporting in the terminal determining to be connected with self to quantize congestion notification agreement QCN, whether the message that the inbound port detecting self in a predefined manner forwards is described CNM, when determining that described message is described CNM, generate described PFC message according to described CNM, and notify that described terminal suspends the data transmission of respective queue according to described PFC message.
7. device as claimed in claim 5, is characterized in that, described first detects generation module specifically comprises:
First generates submodule, for according to the encapsulation priority of carrying in described CNM, determines the priority corresponding to tentative instruction in described PFC message;
Second generates submodule, for according to the field being used to indicate Congestion Level SPCC of carrying in described CNM, determines the time span suspending instruction described in described PFC message.
8. device as claimed in claim 6, it is characterized in that, described predetermined way is: judging whether the protocol Data Unit type of described message identifies described message is CNM, if the judgment is Yes, then determines that described message is CNM.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010560688.0A CN102025617B (en) | 2010-11-26 | 2010-11-26 | Method and device for controlling congestion of Ethernet |
| PCT/CN2011/075409 WO2012068864A1 (en) | 2010-11-26 | 2011-06-07 | Method and apparatus for ethernet congestion control |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010560688.0A CN102025617B (en) | 2010-11-26 | 2010-11-26 | Method and device for controlling congestion of Ethernet |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102025617A CN102025617A (en) | 2011-04-20 |
| CN102025617B true CN102025617B (en) | 2015-04-01 |
Family
ID=43866491
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010560688.0A Active CN102025617B (en) | 2010-11-26 | 2010-11-26 | Method and device for controlling congestion of Ethernet |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102025617B (en) |
| WO (1) | WO2012068864A1 (en) |
Families Citing this family (37)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102025617B (en) * | 2010-11-26 | 2015-04-01 | 中兴通讯股份有限公司 | Method and device for controlling congestion of Ethernet |
| US8989009B2 (en) * | 2011-04-29 | 2015-03-24 | Futurewei Technologies, Inc. | Port and priority based flow control mechanism for lossless ethernet |
| CN102255808B (en) * | 2011-07-08 | 2014-04-23 | 福建星网锐捷网络有限公司 | Congestion notification method, device, system and network equipment |
| WO2012162968A1 (en) * | 2011-08-30 | 2012-12-06 | 华为技术有限公司 | Method, apparatus and system for controlling data transmission |
| CN102377672A (en) * | 2011-11-03 | 2012-03-14 | 华为技术有限公司 | Routing method and communication equipment in data center network |
| CN102594676B (en) * | 2012-02-13 | 2015-06-17 | 福建星网锐捷网络有限公司 | Bridge port expansion network and congestion control method thereof, port expander (PE) and control bridge |
| CN102611630B (en) * | 2012-04-12 | 2015-10-07 | 迈普通信技术股份有限公司 | A kind of message acceptance control method and system |
| EP2887590B1 (en) | 2012-09-25 | 2017-09-20 | Huawei Technologies Co., Ltd. | Flow control method, device and network |
| CN102891803B (en) * | 2012-10-10 | 2015-05-13 | 华为技术有限公司 | Congestion processing method and network device |
| US9401857B2 (en) | 2013-03-15 | 2016-07-26 | International Business Machines Corporation | Coherent load monitoring of physical and virtual networks with synchronous status acquisition |
| US9219689B2 (en) | 2013-03-15 | 2015-12-22 | International Business Machines Corporation | Source-driven switch probing with feedback request |
| US9954781B2 (en) | 2013-03-15 | 2018-04-24 | International Business Machines Corporation | Adaptive setting of the quantized congestion notification equilibrium setpoint in converged enhanced Ethernet networks |
| US9253096B2 (en) | 2013-03-15 | 2016-02-02 | International Business Machines Corporation | Bypassing congestion points in a converged enhanced ethernet fabric |
| CN104283808B (en) * | 2013-07-03 | 2019-03-26 | 华为技术有限公司 | Jamming control method, equipment and system |
| WO2015070393A1 (en) * | 2013-11-13 | 2015-05-21 | Qualcomm Incorporated | Method and apparatus for qcn-like cross-chip function in multi-stage ethernet switching |
| CN103746927B (en) * | 2013-12-27 | 2017-02-15 | 杭州华为数字技术有限公司 | Priority-based fluid control PFC (Power Factor Correction) method, transmitting device and receiving device |
| CN104852855B (en) * | 2014-02-19 | 2018-08-21 | 华为技术有限公司 | Jamming control method, device and equipment |
| CN104980359A (en) * | 2014-04-04 | 2015-10-14 | 中兴通讯股份有限公司 | Flow control method of fiber channel over Ethernet (FCoE), flow control device of FCoE and flow control system of FCoE |
| CN103997465B (en) | 2014-05-27 | 2018-02-23 | 华为技术有限公司 | A kind of generation CNM method and apparatus |
| CN105791140A (en) * | 2014-12-19 | 2016-07-20 | 中兴通讯股份有限公司 | Message sending processing method and apparatus and network equipment |
| CN104836743B (en) * | 2015-05-25 | 2018-09-04 | 新华三技术有限公司 | A kind of jamming control method and device |
| CN104917703B (en) * | 2015-06-09 | 2018-04-06 | 上海斐讯数据通信技术有限公司 | Defence line head of line blocking method and system based on SDN |
| CN106330742B (en) * | 2015-06-23 | 2019-12-06 | 华为技术有限公司 | Flow control method and network controller |
| CN106528564A (en) * | 2015-09-11 | 2017-03-22 | ***通信集团河北有限公司 | Congestion data processing method and apparatus |
| CN107817944B (en) * | 2016-09-12 | 2021-05-18 | 华为技术有限公司 | Data processing method and storage device |
| CN107317762A (en) * | 2017-06-29 | 2017-11-03 | 北京东土军悦科技有限公司 | Jamming control method and field layer device based on industry internet field layer device |
| CN109412964B (en) | 2017-08-18 | 2022-04-29 | 华为技术有限公司 | Message control method and network device |
| CN109600320B (en) * | 2017-09-30 | 2022-04-05 | 华为技术有限公司 | Congestion processing method and equipment and data center network |
| US10567300B2 (en) * | 2017-11-22 | 2020-02-18 | Cisco Technology, Inc. | Layer 3 fair rate congestion control notification |
| CN109981471B (en) * | 2017-12-27 | 2023-04-18 | 华为技术有限公司 | Method, equipment and system for relieving congestion |
| CN108243117B (en) * | 2018-01-02 | 2022-05-24 | 新华三技术有限公司 | Flow monitoring method and device and electronic equipment |
| CN108989235B (en) * | 2018-08-28 | 2022-11-01 | 新华三技术有限公司 | Message forwarding control method and device |
| CN112423399A (en) * | 2019-08-23 | 2021-02-26 | 华为技术有限公司 | Data transmission method and device |
| CN113746743B (en) * | 2020-05-29 | 2023-08-08 | 华为技术有限公司 | Data message transmission method and device |
| CN112565087A (en) * | 2020-11-23 | 2021-03-26 | 盛科网络（苏州）有限公司 | PFC (Power factor correction) back-pressure message and processing method thereof |
| CN114760252A (en) * | 2022-03-24 | 2022-07-15 | 北京邮电大学 | Data center network congestion control method and system |
| CN117395206B (en) * | 2023-12-12 | 2024-03-12 | 南京邮电大学 | Rapid and accurate congestion feedback method for lossless data center network |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101026558A (en) * | 2007-01-18 | 2007-08-29 | 华为技术有限公司 | Method and device for realizing mass port backpressure |
| CN101030926A (en) * | 2006-02-28 | 2007-09-05 | 华为技术有限公司 | Method for controlling network data flow of global microwave access inter-operation |
| CN101141406A (en) * | 2007-10-17 | 2008-03-12 | 杭州华三通信技术有限公司 | Distributed flow control method, system and device |
| EP2164209A1 (en) * | 2008-09-11 | 2010-03-17 | Juniper Networks, Inc. | Systems, methods, and apparatus for a data centre |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102025617B (en) * | 2010-11-26 | 2015-04-01 | 中兴通讯股份有限公司 | Method and device for controlling congestion of Ethernet |
-
2010
- 2010-11-26 CN CN201010560688.0A patent/CN102025617B/en active Active
-
2011
- 2011-06-07 WO PCT/CN2011/075409 patent/WO2012068864A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101030926A (en) * | 2006-02-28 | 2007-09-05 | 华为技术有限公司 | Method for controlling network data flow of global microwave access inter-operation |
| CN101026558A (en) * | 2007-01-18 | 2007-08-29 | 华为技术有限公司 | Method and device for realizing mass port backpressure |
| CN101141406A (en) * | 2007-10-17 | 2008-03-12 | 杭州华三通信技术有限公司 | Distributed flow control method, system and device |
| EP2164209A1 (en) * | 2008-09-11 | 2010-03-17 | Juniper Networks, Inc. | Systems, methods, and apparatus for a data centre |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012068864A1 (en) | 2012-05-31 |
| CN102025617A (en) | 2011-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102025617B (en) | Method and device for controlling congestion of Ethernet | |
| US10425328B2 (en) | Load distribution architecture for processing tunnelled internet protocol traffic | |
| US8437352B2 (en) | Method and system for power control based on application awareness in a packet network switch | |
| US8121038B2 (en) | Backward congestion notification | |
| US7817558B2 (en) | Flow based flow control in an ethernet switch backplane | |
| CN102263697B (en) | Method and device for sharing aggregated link traffic | |
| US8929218B2 (en) | Congestion notification across multiple layer-2 domains | |
| EP2129049A1 (en) | A protecting method and device for ethernet tree service | |
| CN101247353B (en) | Stream aging method and network appliance | |
| WO2007084707A2 (en) | System, method, and computer program product for controlling output port utilization | |
| WO2020156288A1 (en) | Congestion control method, terminal and readable storage medium | |
| JP2012074928A (en) | Data transfer device, program and method using retransmission control protocol | |
| WO2008125030A1 (en) | A load sharing method and the apparatus | |
| JP2021516012A (en) | Flow management in the network | |
| KR20110093990A (en) | Reducing cc message transmission in a provider network | |
| CN107819658B (en) | Message transmission method, MEC (message aggregation center) equipment and system | |
| US10009277B2 (en) | Backward congestion notification in layer-3 networks | |
| WO2014019528A1 (en) | Method, device and system for multipath tcp congestion control | |
| CN102255808B (en) | Congestion notification method, device, system and network equipment | |
| WO2022028342A1 (en) | Method for processing congestion flow and device | |
| WO2011143968A1 (en) | Method and system for notifying congestion control information | |
| WO2014040422A1 (en) | Control method and device for medium access control address learning and route bridge | |
| JP2007019851A (en) | Router device | |
| WO2011017892A1 (en) | Method and apparatus for implementing load sharing for communication traffic | |
| JP2008236733A (en) | Bandwidth control apparatus, system, and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |