WO2014019494A1 - Message forwarding in data center network - Google Patents

Message forwarding in data center network Download PDF

Info

Publication number
WO2014019494A1
WO2014019494A1 PCT/CN2013/080397 CN2013080397W WO2014019494A1 WO 2014019494 A1 WO2014019494 A1 WO 2014019494A1 CN 2013080397 W CN2013080397 W CN 2013080397W WO 2014019494 A1 WO2014019494 A1 WO 2014019494A1
Authority
WO
WIPO (PCT)
Prior art keywords
core device
core
devices
forwarding
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.)
Ceased
Application number
PCT/CN2013/080397
Other languages
French (fr)
Inventor
Huifeng CHANG
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hangzhou H3C Technologies Co Ltd
Original Assignee
Hangzhou H3C Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Hangzhou H3C Technologies Co Ltd filed Critical Hangzhou H3C Technologies Co Ltd
Priority to US14/374,201 priority Critical patent/US20150032815A1/en
Publication of WO2014019494A1 publication Critical patent/WO2014019494A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H04L45/245—Link aggregation, e.g. trunking
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Definitions

  • a data center network may aim to realize non-blocking, non-loop and single-layer high performance switching for example at 10GB rate.
  • a typical data center network may include: CORE devices and ACCESS devices, wherein the CORE devices employ a high performance switching structure to realize non-blocking switching, and the ACCESS devices realize non-blocking uplink for example at 10GB.
  • ACCESS devices and CORE devices may be fully connected, i.e. each of the ACCESS devices is connected to different CORE devices and the different CORE devices are interconnected.
  • FIG. 1 is a schematic drawing of a networking of a data center network provided by an example of the present disclosure
  • Fig. 2 is a flow chart of a method that is applied to the data center network of Fig. 1 provided by an example of the present disclosure
  • FIG. 3 is a structural diagram of a CORE device provided by an example of the present disclosure.
  • Fig. 4 is a structural diagram of an ACCESS device provided by an example of the present disclosure.
  • Fig. 1 is a schematic drawing of a networking of a data center network provided by an example of the present disclosure.
  • Said data center network at least comprises CORE devices and ACCESS devices, wherein all the CORE devices form a stack system through stacking, for example, the CORE devices form an IRF system through an IRF technique, and in the data center network, the ACCESS devices are connected to the stack system through aggregate links, here, an aggregate link between an ACCESS device and the stack system is obtained by aggregating links through which the ACCESS device is connected to each of the CORE devices in the stack system, and said links through which the ACCESS device is connected to each of the CORE devices in the stack system are member links of said aggregate link.
  • Fig. 2 is a flow chart of a method provided by an example. The method is applied to the data center network of Fig. 1.
  • an ACCESS device can perform the following blocks:
  • Block 201 recording local aggregation member ports of each of the CORE devices in the stack system.
  • the stack system is connected to an ACCESS device through an aggregate link, but in practical application, said aggregate link is obtained by aggregating links through which the ACCESS device is connected to each of the CORE devices in the stack system, and said aggregated links are called member links of the aggregate link.
  • the stack system is connected to ACCESS device # 1 through an aggregate link (labeled as Aggl), said Aggl being formed by aggregating Linkl-l ⁇ Linkl-4 through which the ACCESS device #1 is connected to CORE device #l ⁇ CORE device #4, and Linkl-l ⁇ Linkl-4 being member links of Aggl .
  • ports of member links in said aggregate link are distributed on different CORE devices in the stack system respectively, while as for each CORE device, it may call the port distributed thereon as a local aggregate member port.
  • ACCESS device #1 , ACCESS device #2 and ACCESS device #n are connected to the stack system through aggregate link 1 (labeled as Aggl), aggregate link 2 (labeled as Agg2) and Aggregate link 3 (labeled as Aggn), respectively, while one of other ACCESS devices may be connected to the stack system through an aggregate link or through only one link, and the present disclosure does not specifically limit this; wherein, Aggl is formed by aggregating Linkl-l ⁇ Linkl-4 through which the ACCESS device #1 is connected to CORE device #l ⁇ CORE device #4, i.e.
  • Linkl-l ⁇ Linkl-4 are member links of Aggl
  • Agg2 is formed by aggregating Link2-l ⁇ Link2-4 through which the ACCESS device #2 is connected to CORE device #l ⁇ CORE device #4, i.e. Link2-l ⁇ Link2-4 are member links of Agg2
  • Aggn is formed by aggregating Linkn-l ⁇ Linkn-4 through which the ACCESS device #n is connected to CORE device #l ⁇ CORE device #4, i.e. Linkn-l ⁇ Linkn-4 are member links of Aggn
  • the following ports present on the CORE device #1 are local aggregate member ports: a port of the CORE device # 1 on which a member link, i.e.
  • Linkl-1, of Aggl is distributed, a port of the CORE device #1 on which a member link, i.e. Link2-1 , of Agg2 is distributed, and a port of the CORE device # 1 on which a member link, i.e. Linkn-1, of Aggn is distributed (herein the CORE device # 1 in the stack system is taken as an example, while as for the rest CORE devices, the similar principle applies).
  • each ACCESS device may have more than one link connection with a same CORE device depending on the bandwidth requirement, in this case, when the ACCESS device aggregates links connected to the CORE devices in the stack system, it may aggregate all links connected to each of the CORE devices to form an aggregate link.
  • the ACCESS device may aggregate all links connected to each of the CORE devices to form an aggregate link.
  • the Linkl-1 between the ACCESS device # 1 and CORE device #1 is replaced by Linkl-1-1 and Linkl-1-2, namely, the ACCESS device # 1 is connected to the CORE device #1 through two links, i.e.
  • Link 1-1-1 and Link 1-1-2 simultaneously, while the links between the ACCESS device #1 and CORE device #2 ⁇ CORE device #4 are Link 1-2, Link 1-3 and Link 1-4, thus in the present example, the ACCESS device #1 aggregates Linkl-1-1, Link 1-1-2, Linkl-2, Link 1-3 and Link 1-4 to obtain an aggregate link.
  • ports of the CORE device # 1 on which Linkl-1-1, Linkl-1-2, Link2-1, Link3-1 and Link4-1 are distributed are the local aggregate member ports of the CORE device #1.
  • the local aggregate member ports of each CORE device can be called effective aggregate member ports.
  • Block 202 recording information of connection between each CORE device in the stack system and its peer ACCESS devices.
  • Block 202 may be implemented at the initial stage.
  • recording information of connection between each CORE device in the stack system and its peer ACCESS devices comprises: recording information of connection between each CORE device in the stack system and its peer ACCESS devices through the local aggregate member ports.
  • the information of connection between one CORE device and one of its peer ACCESS devices is recorded, it would mean that said CORE device is in effective connection with said peer ACCESS device currently.
  • each ACCESS device may have more than one link connection with a same CORE device depending on the bandwidth requirement, so in said block 202, as long as one of the links between the CORE device and the ACCESS device is in effective connection, the information of connection between said CORE device and said ACCESS device will be recorded.
  • Block 203 upon determining a change in the information of connection between any CORE device and its peer ACCESS devices, labeling said CORE device with a low-forwarding-capability identifier and controlling any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
  • determining a change in the information of connection between any CORE device and its peer ACCESS devices includes:
  • controlling any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding may include:
  • Block 1 searching the recorded local aggregate member ports of all CORE devices for local aggregate member ports of the CORE device labeled with a low-forwarding-capability identifier;
  • Block 2 determining each of the searched ports as a non-selected port and controlling a port of an ACCESS device on which a member link connected to the non-selected port is distributed to be a non-selected port, so that any ACCESS device, when transmitting a message, can locally select a port other than the non-selected port to transmit the message.
  • any ACCESS device when transmitting a message, to locally select a port other than the non-selected port to transmit the message, it is possible to ensure that any ACCESS device, when transmitting a message, can select a CORE device from other CORE devices than the CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
  • determining each of the searched ports as a non-selected port and controlling a port of an ACCESS device on which a member link connected to the non-selected port is distributed to be a non-selected port may specifically include:
  • the aggregate port upon receiving a notice, the aggregate port determining the port labeled with an aggregate non-selected identifier to be a non-selected port, and triggering its corresponding peer aggregate port to determine a corresponding member port (i.e. a port of an ACCESS device on which a member link connected to the non-selected port is distributed) to be a non-selected port according to an aggregate protocol mechanism.
  • the aggregate protocol mechanism is specifically that when an aggregate port determines one of its member ports to be a non-selected port, the peer aggregate port corresponding to said aggregate port in one-to-one correspondence will also determine its corresponding member port having connection to said determined non-selected port to be a non-selected port.
  • the CORE device # 1 has the following aggregate member ports thereon: a port (which is called aggregate member port 1 ) of CORE device # 1 on which the member link Link 1 - 1 in Aggl is distributed, a port (which is called aggregate member port 2) of CORE device # 1 on which the member link Link 2- 1 in Agg2 is distributed, and a port (which is called aggregate member port n) of CORE device # 1 on which the member link Link n- 1 in Aggn is distributed, besides, the CORE device # 1 is in effective connection to the ACCESS device # 1 through the aggregate member port 1 , to ACCESS device #2 through the aggregate member port 2, and to ACCESS device #n through the aggregate member port n.
  • an ACCESS device can forward traffic according to HASH algorithm, and in order to avoid transmission of traffic across CORE devices, a Core device in the stack system forwards traffic in the manner of local preference forwarding.
  • a Core device in the stack system forwards traffic in the manner of local preference forwarding.
  • the ACCESS device #n selects a member link from the aggregate link Aggn (consisting of Link n- l ⁇ Link n-4 through which ACCESS device #n is connected to Core device # l ⁇ Core device #4, respectively) between the ACCESS device #n and the stack system using the HASH algorithm to send traffic to the stack system, suppose that the member link selected by ACCESS device #n is Link n-1 , then Core device # 1 in the stack system will receive traffic sent by ACCESS device #n. Upon receiving the traffic sent by ACCESS device #n, Core device # 1 forwards said received traffic to ACCESS device # 1 through Link 1 - 1 connecting to ACCESS device # 1 in the
  • CORE device # 1 then based on the flow shown in Fig. 2, it is needed to label the CORE device # 1 with a low-forwarding-capability identifier and determine all aggregate member ports, i.e. aggregate members 1 , 2 and n on said CORE device # 1 to be non-selected ports; meanwhile, determine ports of ACCESS devices on which member links connected to the non-selected ports are distributed, namely, a port of ACCESS device # 1 on which the member link Link 1 - 1 in Aggl is distributed, a port of ACCESS device #2 on which the member link Link 2- 1 in Agg2 is distributed, and a port of ACCESS device #n on which the member link Link n-1 in Aggn is distributed, as the non-selected ports.
  • the ACCESS device # 1 , #2 or #n will forward messages through other local ports than the non-selected ports, which ensures that no message will be sent to CORE device # 1. Since the CORE device # 1 does not receive any message, even if the information of connection between said CORE device # 1 and its peer ACCESS devices changes, the increasing of load on inter-chassis link caused by the CORE device # 1 forwarding traffic through an inter-chassis link between CORE devices can be avoided, and the traffic forwarding performance can be improved.
  • Fig. 3 is a CORE device provided by an example. Said CORE device and all other CORE devices form a stack system through stacking; as shown in Fig. 3, said CORE device comprises: a recording unit to record information of connection between said CORE device and its peer ACCESS devices;
  • a controlling unit to, upon determining a change in the information of connection between the CORE device and its peer ACCESS devices, label said CORE device with a low-forwarding-capability identifier and control any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
  • said recording unit further records the local aggregate member ports of the CORE device.
  • the local aggregate member ports of the CORE device include a port of the present CORE device on which a member link in an aggregate link between the stack system and any ACCESS device is distributed.
  • the recording unit recording information of connection between the CORE device in the stack system and its peer ACCESS devices includes: recording information of connection of the CORE device in the stack system and its peer ACCESS devices through local aggregate member ports.
  • a change in the information of connection between said CORE device and its peer ACCESS devices includes that the connection between the CORE device and its peer ACCESS devices via the local aggregate member ports is disconnected.
  • the controlling unit controlling any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding includes:
  • a port of a ACCESS device on which a link connected to each of the non-selected ports is distributed to be a non-selected port, so that any ACCESS device, when transmitting a message, locally selects a port other than the non-selected port to transmit the message.
  • FIG. 4 is a structural diagram of an ACCESS device provided by an example. As shown in Fig. 4, said ACCESS device comprises:
  • a selecting unit to select a CORE device from other CORE devices than the CORE device labeled with a low-forwarding-capability identifier when transmitting a message, wherein a CORE device is labeled with a low-forwarding-capability identifier when determining a change in the information of connection between the CORE device and its peer ACCESS devices;
  • a transmitting unit to forward a message to the selected CORE device.
  • the above examples can be implemented by hardware, software or firmware or a combination thereof.
  • the various methods, processes and functional modules described herein may be implemented by a processor (the term processor is to be interpreted broadly to include a CPU, processing unit, ASIC, logic unit, or programmable gate array etc.).
  • the processes, methods and functional modules may all be performed by a single processor or split between several processers; reference in this disclosure or the claims to a 'processor' should thus be interpreted to mean 'one or more processors' .
  • the processes, methods and functional modules be implemented as machine readable instructions executable by one or more processors, hardware logic circuitry of the one or more processors or a combination thereof. Further the teachings herein may be implemented in the form of a software product.
  • the computer software product is stored in a storage medium and comprises a plurality of instructions for making a computer device (which can be a personal computer, a server or a network device such as a router, switch, access point etc.) implement the method recited in the examples of the present disclosure.
  • a computer device which can be a personal computer, a server or a network device such as a router, switch, access point etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Description

Message Forwarding in Data Center Network
Background
[001] Currently, a data center network may aim to realize non-blocking, non-loop and single-layer high performance switching for example at 10GB rate. A typical data center network may include: CORE devices and ACCESS devices, wherein the CORE devices employ a high performance switching structure to realize non-blocking switching, and the ACCESS devices realize non-blocking uplink for example at 10GB.
[002] In a data center network, in order to make full use of the forwarding capability of CORE devices and to realize load sharing and disaster backup among CORE devices, ACCESS devices and CORE devices may be fully connected, i.e. each of the ACCESS devices is connected to different CORE devices and the different CORE devices are interconnected.
Description of Drawings
[003] Fig. 1 is a schematic drawing of a networking of a data center network provided by an example of the present disclosure;
[004] Fig. 2 is a flow chart of a method that is applied to the data center network of Fig. 1 provided by an example of the present disclosure;
[005] Fig. 3 is a structural diagram of a CORE device provided by an example of the present disclosure;
[006] Fig. 4 is a structural diagram of an ACCESS device provided by an example of the present disclosure.
Detailed Description
[007] Fig. 1 is a schematic drawing of a networking of a data center network provided by an example of the present disclosure. Said data center network at least comprises CORE devices and ACCESS devices, wherein all the CORE devices form a stack system through stacking, for example, the CORE devices form an IRF system through an IRF technique, and in the data center network, the ACCESS devices are connected to the stack system through aggregate links, here, an aggregate link between an ACCESS device and the stack system is obtained by aggregating links through which the ACCESS device is connected to each of the CORE devices in the stack system, and said links through which the ACCESS device is connected to each of the CORE devices in the stack system are member links of said aggregate link.
[008] Fig. 2 is a flow chart of a method provided by an example. The method is applied to the data center network of Fig. 1.
[009] Based on this, as shown in Fig. 2, an ACCESS device can perform the following blocks:
[0010] Block 201 , recording local aggregation member ports of each of the CORE devices in the stack system.
[0011] In the present example, the stack system is connected to an ACCESS device through an aggregate link, but in practical application, said aggregate link is obtained by aggregating links through which the ACCESS device is connected to each of the CORE devices in the stack system, and said aggregated links are called member links of the aggregate link. For example, in the networking shown in Fig. 1, the stack system is connected to ACCESS device # 1 through an aggregate link (labeled as Aggl), said Aggl being formed by aggregating Linkl-l~Linkl-4 through which the ACCESS device #1 is connected to CORE device #l~CORE device #4, and Linkl-l~Linkl-4 being member links of Aggl .
[0012] Based on this, with respect to an aggregate link between the stack system and an ACCESS device, from the perspective of the stack system, ports of member links in said aggregate link are distributed on different CORE devices in the stack system respectively, while as for each CORE device, it may call the port distributed thereon as a local aggregate member port.
[0013] Taking the networking shown in Fig. 1 as an example, if
ACCESS device #1 , ACCESS device #2 and ACCESS device #n are connected to the stack system through aggregate link 1 (labeled as Aggl), aggregate link 2 (labeled as Agg2) and Aggregate link 3 (labeled as Aggn), respectively, while one of other ACCESS devices may be connected to the stack system through an aggregate link or through only one link, and the present disclosure does not specifically limit this; wherein, Aggl is formed by aggregating Linkl-l~Linkl-4 through which the ACCESS device #1 is connected to CORE device #l~CORE device #4, i.e. Linkl-l~Linkl-4 are member links of Aggl, Agg2 is formed by aggregating Link2-l~Link2-4 through which the ACCESS device #2 is connected to CORE device #l~CORE device #4, i.e. Link2-l~Link2-4 are member links of Agg2, and Aggn is formed by aggregating Linkn-l~Linkn-4 through which the ACCESS device #n is connected to CORE device #l~CORE device #4, i.e. Linkn-l~Linkn-4 are member links of Aggn, then, the following ports present on the CORE device #1 are local aggregate member ports: a port of the CORE device # 1 on which a member link, i.e. Linkl-1, of Aggl is distributed, a port of the CORE device #1 on which a member link, i.e. Link2-1 , of Agg2 is distributed, and a port of the CORE device # 1 on which a member link, i.e. Linkn-1, of Aggn is distributed (herein the CORE device # 1 in the stack system is taken as an example, while as for the rest CORE devices, the similar principle applies).
[0014] In addition, in the present example, each ACCESS device may have more than one link connection with a same CORE device depending on the bandwidth requirement, in this case, when the ACCESS device aggregates links connected to the CORE devices in the stack system, it may aggregate all links connected to each of the CORE devices to form an aggregate link. For example, in the networking shown in Fig. 1, suppose that in Fig. 1 , the Linkl-1 between the ACCESS device # 1 and CORE device #1 is replaced by Linkl-1-1 and Linkl-1-2, namely, the ACCESS device # 1 is connected to the CORE device #1 through two links, i.e. Link 1-1-1 and Link 1-1-2, simultaneously, while the links between the ACCESS device #1 and CORE device #2~CORE device #4 are Link 1-2, Link 1-3 and Link 1-4, thus in the present example, the ACCESS device #1 aggregates Linkl-1-1, Link 1-1-2, Linkl-2, Link 1-3 and Link 1-4 to obtain an aggregate link. As a result, with respect to CORE device # 1, ports of the CORE device # 1 on which Linkl-1-1, Linkl-1-2, Link2-1, Link3-1 and Link4-1 are distributed are the local aggregate member ports of the CORE device #1.
[0015] In the present example, the local aggregate member ports of each CORE device can be called effective aggregate member ports.
[0016] Block 202: recording information of connection between each CORE device in the stack system and its peer ACCESS devices.
[0017] Block 202 may be implemented at the initial stage.
[0018] In block 202, recording information of connection between each CORE device in the stack system and its peer ACCESS devices comprises: recording information of connection between each CORE device in the stack system and its peer ACCESS devices through the local aggregate member ports. Here, if the information of connection between one CORE device and one of its peer ACCESS devices is recorded, it would mean that said CORE device is in effective connection with said peer ACCESS device currently.
[0019] Still taking the networking of Fig. 1 as an example, suppose that the CORE device #1 has the following aggregate member ports locally: a port (which is called aggregate member port 1) of the CORE device #1 on which a member link Linkl-1 of Aggl is distributed, a port (which is called aggregate member port 2) of the CORE device #1 on which a member link Link2-1 of Agg2 is distributed, and a port (which is called aggregate member port n) of the CORE device # 1 on which a member link Linkn-1 of Aggn is distributed, then in this block 202, recording that the CORE device # 1 is in effective connection with the ACCESS device # 1 through the aggregate member port 1, recording that the CORE device # 1 is in effective connection with the ACCESS device #2 through the aggregate member port 2, and recording that the CORE device # 1 is in effective connection with the ACCESS device #n through the aggregate member port n.
[0020] As mentioned above, each ACCESS device may have more than one link connection with a same CORE device depending on the bandwidth requirement, so in said block 202, as long as one of the links between the CORE device and the ACCESS device is in effective connection, the information of connection between said CORE device and said ACCESS device will be recorded.
[0021] Block 203 : upon determining a change in the information of connection between any CORE device and its peer ACCESS devices, labeling said CORE device with a low-forwarding-capability identifier and controlling any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
[0022] In said block 203, determining a change in the information of connection between any CORE device and its peer ACCESS devices includes:
comparing the recorded information of connection between said CORE device and its peer ACCESS devices to the current information of connection between said CORE device and its peer ACCESS devices;
if they are the same, it shows that the information of connection between said CORE device and its peer ACCESS devices has not changed; if they are not the same, it is determined that the information of connection between said CORE device and its peer ACCESS devices changes when at least one peer ACCESS device which has been effectively connected to said CORE device disconnects from said CORE device.
[0023] Moreover, in said block 203, controlling any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding may include:
[0024] Block 1 : searching the recorded local aggregate member ports of all CORE devices for local aggregate member ports of the CORE device labeled with a low-forwarding-capability identifier; [0025] Block 2: determining each of the searched ports as a non-selected port and controlling a port of an ACCESS device on which a member link connected to the non-selected port is distributed to be a non-selected port, so that any ACCESS device, when transmitting a message, can locally select a port other than the non-selected port to transmit the message. Here, through making any ACCESS device, when transmitting a message, to locally select a port other than the non-selected port to transmit the message, it is possible to ensure that any ACCESS device, when transmitting a message, can select a CORE device from other CORE devices than the CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
[0026] In addition, since the stack system and an ACCESS device are connected through an aggregate link, there is a port for said aggregate link at the ACCESS device side, which is called an aggregate port, and said aggregate port is virtual and includes ports (which are called member ports) of the ACCESS device on which member links in said aggregate link are distributed. Likewise, there is another port for said aggregate link at the stack system side, which is also called an aggregate port, and said aggregate port also includes ports (which are also called member ports) of CORE devices of the stack system on which the member links in said aggregate link are distributed. These two aggregate ports are ports at the two ends of one and the same aggregate link, and they are of one-to-one correspondence.
[0027] Thus, if each ACCESS device in the data center network is connected to the stack system through an aggregate link, then each ACCESS device has an aggregate port thereon, and the stack system has N aggregate ports thereon, N being the number of the ACCESS devices. Therefore, in the above-mentioned block 2, determining each of the searched ports as a non-selected port and controlling a port of an ACCESS device on which a member link connected to the non-selected port is distributed to be a non-selected port may specifically include:
labeling each of the searched ports with an aggregate non-selected identifier;
notifying the aggregate port where the port labeled with an aggregate non-selected identifier locates;
upon receiving a notice, the aggregate port determining the port labeled with an aggregate non-selected identifier to be a non-selected port, and triggering its corresponding peer aggregate port to determine a corresponding member port (i.e. a port of an ACCESS device on which a member link connected to the non-selected port is distributed) to be a non-selected port according to an aggregate protocol mechanism. The aggregate protocol mechanism is specifically that when an aggregate port determines one of its member ports to be a non-selected port, the peer aggregate port corresponding to said aggregate port in one-to-one correspondence will also determine its corresponding member port having connection to said determined non-selected port to be a non-selected port.
[0028] So far, the flow shown in Fig. 2 is completed. Now the flow shown in Fig. 2 will be described using a specific example.
[0029] Taking CORE device # 1 in the networking shown in Fig. 1 as an example, suppose that ACCESS device # 1 , ACCESS device #2 and ACCESS device #n are connected to the stack system through aggregate link 1 (labeled as Aggl ), aggregate link 2 (labeled as Agg2) and aggregate link 3 (labeled as Aggn), then in the initial stage, as shown in Fig. 1 , the CORE device # 1 has the following aggregate member ports thereon: a port (which is called aggregate member port 1 ) of CORE device # 1 on which the member link Link 1 - 1 in Aggl is distributed, a port (which is called aggregate member port 2) of CORE device # 1 on which the member link Link 2- 1 in Agg2 is distributed, and a port (which is called aggregate member port n) of CORE device # 1 on which the member link Link n- 1 in Aggn is distributed, besides, the CORE device # 1 is in effective connection to the ACCESS device # 1 through the aggregate member port 1 , to ACCESS device #2 through the aggregate member port 2, and to ACCESS device #n through the aggregate member port n. In this initial stage, an ACCESS device can forward traffic according to HASH algorithm, and in order to avoid transmission of traffic across CORE devices, a Core device in the stack system forwards traffic in the manner of local preference forwarding. As shown in Fig. 1, when ACCESS device #n forwards traffic to ACCESS device # 1 through the stack system, first, the ACCESS device #n selects a member link from the aggregate link Aggn (consisting of Link n- l~Link n-4 through which ACCESS device #n is connected to Core device # l~Core device #4, respectively) between the ACCESS device #n and the stack system using the HASH algorithm to send traffic to the stack system, suppose that the member link selected by ACCESS device #n is Link n-1 , then Core device # 1 in the stack system will receive traffic sent by ACCESS device #n. Upon receiving the traffic sent by ACCESS device #n, Core device # 1 forwards said received traffic to ACCESS device # 1 through Link 1 - 1 connecting to ACCESS device # 1 in the manner of local preference forwarding.
[0030] However, if the ACCESS device # 1 disconnects from the
CORE device # 1 , then based on the flow shown in Fig. 2, it is needed to label the CORE device # 1 with a low-forwarding-capability identifier and determine all aggregate member ports, i.e. aggregate members 1 , 2 and n on said CORE device # 1 to be non-selected ports; meanwhile, determine ports of ACCESS devices on which member links connected to the non-selected ports are distributed, namely, a port of ACCESS device # 1 on which the member link Link 1 - 1 in Aggl is distributed, a port of ACCESS device #2 on which the member link Link 2- 1 in Agg2 is distributed, and a port of ACCESS device #n on which the member link Link n-1 in Aggn is distributed, as the non-selected ports. In this case, the ACCESS device # 1 , #2 or #n will forward messages through other local ports than the non-selected ports, which ensures that no message will be sent to CORE device # 1. Since the CORE device # 1 does not receive any message, even if the information of connection between said CORE device # 1 and its peer ACCESS devices changes, the increasing of load on inter-chassis link caused by the CORE device # 1 forwarding traffic through an inter-chassis link between CORE devices can be avoided, and the traffic forwarding performance can be improved.
[0031 ] The method according to an example of the present disclosure is described in the above. Now the apparatus according to an example of the present disclosure will be described.
[0032] Referring to Fig. 3, which is a CORE device provided by an example. Said CORE device and all other CORE devices form a stack system through stacking; as shown in Fig. 3, said CORE device comprises: a recording unit to record information of connection between said CORE device and its peer ACCESS devices;
a controlling unit to, upon determining a change in the information of connection between the CORE device and its peer ACCESS devices, label said CORE device with a low-forwarding-capability identifier and control any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
[0033] In the present example, said recording unit further records the local aggregate member ports of the CORE device. The local aggregate member ports of the CORE device include a port of the present CORE device on which a member link in an aggregate link between the stack system and any ACCESS device is distributed. Thus the recording unit recording information of connection between the CORE device in the stack system and its peer ACCESS devices includes: recording information of connection of the CORE device in the stack system and its peer ACCESS devices through local aggregate member ports.
[0034] In the present example, a change in the information of connection between said CORE device and its peer ACCESS devices includes that the connection between the CORE device and its peer ACCESS devices via the local aggregate member ports is disconnected.
[0035] In the present example, the controlling unit controlling any ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding includes:
searching the recording unit for the local aggregate member ports of the CORE device labeled with a low-forwarding-capability identifier and determining them to be non-selected ports;
controlling a port of a ACCESS device on which a link connected to each of the non-selected ports is distributed to be a non-selected port, so that any ACCESS device, when transmitting a message, locally selects a port other than the non-selected port to transmit the message.
[0036] Referring to Fig. 4, which is a structural diagram of an ACCESS device provided by an example. As shown in Fig. 4, said ACCESS device comprises:
a selecting unit to select a CORE device from other CORE devices than the CORE device labeled with a low-forwarding-capability identifier when transmitting a message, wherein a CORE device is labeled with a low-forwarding-capability identifier when determining a change in the information of connection between the CORE device and its peer ACCESS devices;
a transmitting unit to forward a message to the selected CORE device.
[0037] It can be seen from the above technical solutions that in the present disclosure, when the information of connection between any CORE device and its peer ACCESS devices changes, said CORE device is labeled with a low-forwarding-capability identifier and any ACCESS is controlled, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding, thus the CORE device which has a change in the information of connection to its peer ACCESS devices will not receive any message, and accordingly, the increasing of load on the inter-chassis link caused by using the inter-chassis link between the CORE devices to perform traffic forwarding can be avoided and the traffic forwarding performance can be improved.
[0038] The above examples can be implemented by hardware, software or firmware or a combination thereof. For example the various methods, processes and functional modules described herein may be implemented by a processor (the term processor is to be interpreted broadly to include a CPU, processing unit, ASIC, logic unit, or programmable gate array etc.). The processes, methods and functional modules may all be performed by a single processor or split between several processers; reference in this disclosure or the claims to a 'processor' should thus be interpreted to mean 'one or more processors' . The processes, methods and functional modules be implemented as machine readable instructions executable by one or more processors, hardware logic circuitry of the one or more processors or a combination thereof. Further the teachings herein may be implemented in the form of a software product. The computer software product is stored in a storage medium and comprises a plurality of instructions for making a computer device (which can be a personal computer, a server or a network device such as a router, switch, access point etc.) implement the method recited in the examples of the present disclosure.
[0039] While the present disclosure describes various examples, these examples are to be understood as illustrative and do not limit the claim scope. Many variations, modifications, additions and improvements of the described examples are possible. All such variations, modifications, additions and improvements are within the scope of the present disclosure.

Claims

1. A message forwarding method in a data center network, said data center network comprising CORE devices and ACCESS devices, wherein the CORE devices form a stack system through stacking, wherein said method comprises:
recording information of connection between each CORE device in the stack system and its peer ACCESS devices;
upon determining a change in the information of connection between any CORE device and its peer ACCESS devices, labeling said CORE device with a low-forwarding-capability identifier and controlling any ACCESS device, when transmitting a message, to select a CORE device other than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
2. The method according to claim 1 , wherein said method further comprises:
recording local aggregation member ports of each of the CORE devices in the stack system, the local aggregate member ports of a CORE device include a port of said CORE device on which a member link in an aggregate link between the stack system and any ACCESS device is distributed;
said recording information of connection between each CORE device in the stack system and its peer ACCESS devices comprises: recording information of connection between each CORE device in the stack system and its peer ACCESS devices via the local aggregate member ports.
3. The method according to claim 2, wherein a change in the information of connection between a CORE device and its peer ACCESS devices includes that the connection between the CORE device and its peer ACCESS devices via the local aggregate member ports is disconnected.
4. The method according to claim 2, wherein said controlling any
ACCESS device, when transmitting a message, to select a CORE device from other CORE devices than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding includes:
searching the recorded local aggregate member ports of the CORE devices for local aggregate member ports of the CORE device labeled with a low-forwarding-capability identifier;
determining the searched local aggregate member ports of the CORE device labeled with a low-forwarding-capability identifier as non-selected ports;
controlling a port of an ACCESS device on which a member link connected to each of the non-selected ports is distributed to be a non-selected port, so that any ACCESS device, when transmitting a message, locally selects a port other than the non-selected port to transmit the message.
5. A CORE device for use in a data center network, said CORE device being capable of forming a stack system together with other CORE devices, wherein said CORE device comprises:
a recording unit to record information of connection between said CORE device and its peer ACCESS devices;
a controlling unit to label said CORE device with a low-forwarding-capability identifier upon determining a change in the information of connection between said CORE device and its peer ACCESS devices, and control any ACCESS device, when transmitting a message, to select a CORE device other than said CORE device labeled with a low-forwarding-capability identifier to perform message forwarding.
6. The CORE device according to claim 5, wherein said recording unit is further to record local aggregate member ports of the CORE device, and the local aggregate member ports of the CORE device include a port of the CORE device on which a member link in an aggregate link between the stack system and any ACCESS device is distributed;
the recording unit is to: record information of connection of the CORE device in the stack system and its peer ACCESS devices through the local aggregate member ports.
7. The CORE device according to claim 6, wherein a change in the information of connection between the CORE device and its peer ACCESS devices includes that the connection between the CORE device and its peer ACCESS devices via the local aggregate member ports is disconnected.
8. The CORE device according to claim 6, wherein the controlling unitis to:
determine the local aggregate member ports of the CORE device labeled with a low-forwarding-capability identifier recorded in the recording unit to be non-selected ports;
and control a port of a ACCESS device on which a link connected to each of the non-selected ports is distributed to be a non-selected port, so that any ACCESS device, when transmitting a message, locally selects a port other than the non-selected port to transmit the message.
9. An ACCESS device for use in a data center network which comprises CORE devices which are stacked together to form a stack system through stacking, said ACCESS device comprising:
a selecting unit to select a CORE device from other CORE devices than the CORE device labeled with a low-forwarding-capability identifier when transmitting a message, wherein a CORE device is labeled with a low-forwarding-capability identifier when determining a change in the information of connection between the CORE device and its peer ACCESS devices;
a transmitting unit to forward a message to the selected CORE device.
PCT/CN2013/080397 2012-07-31 2013-07-30 Message forwarding in data center network Ceased WO2014019494A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/374,201 US20150032815A1 (en) 2012-07-31 2013-07-30 Message forwarding in data center network

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210269080.1 2012-07-31
CN201210269080.1A CN103581058B (en) 2012-07-31 2012-07-31 Message forwarding method and device in data central network

Publications (1)

Publication Number Publication Date
WO2014019494A1 true WO2014019494A1 (en) 2014-02-06

Family

ID=50027254

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/080397 Ceased WO2014019494A1 (en) 2012-07-31 2013-07-30 Message forwarding in data center network

Country Status (3)

Country Link
US (1) US20150032815A1 (en)
CN (1) CN103581058B (en)
WO (1) WO2014019494A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106936609B (en) * 2015-12-29 2020-10-16 南京中兴新软件有限责任公司 Method for controlling forwarding equipment cluster in software defined network and controller
CN106101210B (en) * 2016-06-08 2018-11-16 常熟理工学院 A kind of data-centered radio network data communication method
CN108696460B (en) * 2018-05-29 2020-10-27 新华三技术有限公司 Message forwarding method and device
CN111327543A (en) * 2018-12-14 2020-06-23 中兴通讯股份有限公司 Message forwarding method and device, storage medium, and electronic device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101465782A (en) * 2009-01-12 2009-06-24 杭州华三通信技术有限公司 Method for switching optimizing link of RRPP loop, system and network node
CN102316021A (en) * 2011-07-04 2012-01-11 杭州华三通信技术有限公司 Method for realizing load sharing of switch aggregation port and switch
CN102347905A (en) * 2011-10-31 2012-02-08 杭州华三通信技术有限公司 Network equipment and forwarded information updating method
CN102412979A (en) * 2010-09-26 2012-04-11 杭州华三通信技术有限公司 Method and communication equipment for reducing message loss of link aggregation port

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000209287A (en) * 1999-01-20 2000-07-28 Fujitsu Ltd Network system
CN101340456B (en) * 2008-08-15 2012-04-18 杭州华三通信技术有限公司 Distributed link aggregation fault convergence method and stacking equipment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101465782A (en) * 2009-01-12 2009-06-24 杭州华三通信技术有限公司 Method for switching optimizing link of RRPP loop, system and network node
CN102412979A (en) * 2010-09-26 2012-04-11 杭州华三通信技术有限公司 Method and communication equipment for reducing message loss of link aggregation port
CN102316021A (en) * 2011-07-04 2012-01-11 杭州华三通信技术有限公司 Method for realizing load sharing of switch aggregation port and switch
CN102347905A (en) * 2011-10-31 2012-02-08 杭州华三通信技术有限公司 Network equipment and forwarded information updating method

Also Published As

Publication number Publication date
CN103581058A (en) 2014-02-12
CN103581058B (en) 2017-02-15
US20150032815A1 (en) 2015-01-29

Similar Documents

Publication Publication Date Title
EP3014826B1 (en) Link aggregation
EP3082309B1 (en) Sdn controller, data centre system and router connection method
US20140301401A1 (en) Providing aggregation link groups in logical network device
CN102006184B (en) Management method, device and network device of stack link
EP2618521B1 (en) Method, apparatus and system for link aggregation failure protection
US9769027B2 (en) Topology discovery in a stacked switches system
US9350665B2 (en) Congestion mitigation and avoidance
CN102347905B (en) Network equipment and forwarded information updating method
EP2798800B1 (en) Expanding member ports of a link aggregation group between clusters
US20130229912A1 (en) Device-level redundancy protection method and system based on link aggregation control protocol
CN103095568B (en) Rack switching equipment realizes stacking system and method
CN108243111A (en) The method and apparatus for determining transmission path
JP6551547B2 (en) Traffic-aware group reconfiguration in multi-group P2P networks
US20140369230A1 (en) Virtual Chassis Topology Management
EP2541852A1 (en) Method and device for converging layer 2 multicast network
CN102255751A (en) Stacking conflict resolution method and equipment
CN105743816A (en) Link aggregation method and device
CN110278094B (en) Link recovery method, device, system, storage medium and electronic device
WO2016206635A1 (en) Lacp-based forwarding detection method and system
US20150032815A1 (en) Message forwarding in data center network
CN118612145A (en) A link abnormality processing method, device and related equipment
EP3213441A1 (en) Redundancy for port extender chains
US9231859B2 (en) System and method for ingress port identification in aggregate switches
US10819628B1 (en) Virtual link trunking control of virtual router redundancy protocol master designation
CN102857436B (en) Flow transmission method and flow transmission equipment based on IRF (intelligent resilient framework) network

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13826540

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14374201

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13826540

Country of ref document: EP

Kind code of ref document: A1