CROSS REFERENCE TO RELATED APPLICATION
1. TECHNICAL FIELD
The present disclosure is related to information handling systems. In particular, embodiments disclosed herein are related to traffic an interconnect links between network devices.
2. DISCUSSION OF RELATED ART
As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
Currently, some information handling systems may take the form of a plurality of Layer-2 switches connected together in various arrangements using a variety of protocols. In some information handling systems, groups of links between one switch and another switch may be joined together and managed as a group. To provide redundancy and to enable load balancing, one switch may be connected to a pair of switches by two groups of links that are managed together as a single group. However, such link aggregation can become counterproductive in the event of a link failure. Thus, current aggregation handling in information handling systems has not been completely satisfactory. [Insert new description page 2a]
The present invention is defined in the appended independent claim 1 to which reference should be made.
Advantageous features are set out in the appended dependent claims.
 US 2011/0044339 A1
relates to a method and related network node including one or more of the following: establishing, at the network node, a first Child Link Aggregation Group (CLAG), wherein the first CLAG includes at least one link to a first downstream node; establishing, at the network node, a second CLAG, wherein the second CLAG includes at least one link to a second downstream node; establishing, at the network node, a Parent Link Aggregation Group (PLAG), wherein the PLAG includes the first CLAG and the second CLAG; receiving, at the network node, a packet including an address of a destination of the packet; determining that the destination of the packet is associated with the PLAG; and transmitting the packet over both the first CLAG and the second CLAG.
"Dell Force10 VLT Technical Guide" focusses on VLT performance technical details and assumes a minimum knowledge of VLT as provided by the FTOS configuration guide.
 US 2008/002570 A1
relates to a redundancy method in a network including an upper switch apparatus, middle switch apparatuses connected to the upper switch apparatuses via transmission lines and lower switch apparatuses each being connected to the middle switch apparatuses via transmission lines.
These and other embodiments will be described in further detail below with respect to the following figures.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1A is a diagram of an information handling system that includes two switches configured as a single logical switch during ordinary operation.
FIG. 1B is a diagram of an information handling system that includes two switches configured as a single logical switch during a downstream link failure.
FIG. 2A is a diagram of an information handling system that includes two switches configured as a single logical switch during a downstream link failure according to an embodiment.
FIG. 2B is a diagram of an information handling system that includes two switches configured as a single logical switch during a downstream link failure according to an embodiment.
FIG. 3 is an additional diagram of an information handling system that includes two switches configured as a single logical switch in Operation during a downstream link failure according to an embodiment.
FIG. 4A is a diagram of an information handling system that includes a four switches configured as two interconnected logical switches during a downstream link failure.
FIG. 4B is an additional diagram of an information handling system that includes four switches configured as two interconnected logical switches during a downstream link failure according to an embodiment.
FIG. 5 is a flowchart of method for directing traffic through a set of redundant links during failure of a downstream link according to an embodiment.
FIG. 6 is a flowchart of an additional method for directing traffic through a set ofredundant links during failure of a downstream link according to an embodiment.
For clarity of discussion, elements having the same designation in the drawings may have the same or similar functions. The drawings may be better understood by referring to the following Detailed Description.
In the following description specific details are set forth describing certain embodiments. It will be apparent, however, to one skilled in the art that the disclosed embodiments may be practiced without some or all of these specific details. The specific embodiments presented are meant to be illustrative, but not limiting.
For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display.
The information handling system may also include one or more buses operable to transmit communications between the various hardware components.
Some embodiments of information handling systems include non-transient, tangible, machine-readable media that include executable code that when run by a processor, may cause the processor to perform the steps of methods described herein. Some common forms of machirre-readable media include, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, and/or any other medium from which a processor or computer is adapted to read.
FIG. 1 depicts an information handling system 100 that includes a first network device 102A and a second network device 102B joined together by interconnect links (ICL) 104, thereby forming an aggregation domain 106. In the depicted embodiment, network devices 102A and 102B are Layer-2 switching devices connected in a virtual link or line trunking (VLT) configuration by links 104 in order to form a VLT domain 106. VLT is a Layer-2 link aggregation protocol that allows servers, hosts, or any other switching device to be connected to different switches to provide redundancy and load-balancing between a server and two different logical switches. Hereafter, network devices 102A and 102B are referred to as switch 102A and switch 102B, respectively. However, the disclosure provided herein is applicable beyond Layer-2 switching devices. By configuring switches 102A and 102B in VLT domain 106, switches 102A and 102B may be visible in information handling system 100 as two distinct switches. In other embodiments of information handling system 100, switches 102A and 102B may be configured in in a stacking arrangement, such that both switches together are visible in information handling system 100 as a single logical device.
Switches 102A and 102B are connected to a top node 110 and a bottom node 112 as depicted in FIG. 1A. In the depicted embodiment top node 110 and bottom node 112 are servers, while in other embodiments they may be top-of-rack switches connected to a plurality of servers. In FIG. 1A, and through the other figures, the links between one of switches 102A and 102B and one of the nodes 110 and 112 appear as a single line. However, in each case, the single line represents a plurality or a set of links.
Thus, while a single line in FIG. 1A connects switch 102A and node 110, a set of links is present between switch 102A and node 110, and another set of links is present between switch 102B and node 110. Depicted on the other side of VLT domain 106, a set of links couples switch 102A to node 112 and another set of links couples switch 102B to node 112. The two sets of links on the top and on the two on the bottom of FIG. 1A are each grouped together to form a VLT. Thus, when node 110 sends a frame to node 112, the frame is hashed on a link aggregation group (LAG) 120 that includes the two sets of links between node 110 and switches 102A and 102B. The packets may be hashed to either of the two switches and then over the set of links between that receiving switch and node 112, which receives the frame as on a LAG 122. In some embodiments, nodes 110 and 112 may be connected to more than two logical switches in a VLT domain, i.e. more than switches 102A and 102B.
Numbered arrows are provided on FIG. 1A to demonstrate how information handling system 100 may normally operate to send frames between nodes 110 and 112. As an example, a Layer-2 frame that includes a media access control (MAC) address is first hashed on LAG 120 and is directed by the hash to switch 102B. Second, switch 102B receives the frame and recognizes that the MAC address, included as the frame's destination MAC address, is located at node 112. Rather than send the frame over links 104, switch 102B forwards the packet directly to node 112, which receives the packet as on LAG 122. Third, the frame elicits a response from node 112, which is hashes a responsive frame on LAG 122 to switch 102A. In this example, the hash sends the responsive frame to switch 102A rather than 102B. Fourth, switch 102A forwards the packet on to node 110, which receives the frame on LAG 120. In the preceding example, the hashes performed by node 110 to send the frame out on a member port of LAG 120 and by node 112 to send the responsive frame out on a member port of LAG 122 could have resulted in the frames being sent on the other sets of links in their respective LAGs such that the frame may go to the switch other than the one in the example.
FIG. 1B contains the same features as described above in connection with FIG. 1A. However, as depicted in FIG. 1B, the information handling system 100 now is experiencing a link failure 130 on the set of links between node 112 and switch 102B. Due to the link failure 130, no frames may be sent directly between node 112 and switch 102B. For example, while a frame from node 110 may still be hashed to switch 102B, the frame is then sent by switch 102B, which detects and responds to link failure 130, over links 104 to switch 102A. From switch 102A, the frame is sent to node 112. Node 112 also detects the link failure 130 and hashes a responsive frame only on the set of links between it and switch 102A, which then forwards the responsive frame directly to node 110.
In FIG. 1B, the path of the frame sent from node 110 to node 112 contains an extra hop, adding latency to the flow of data between these nodes. Also, the frame had to be sent between switches 102A and 102B over links 104 which may be oversubscribed and not able to carry the extra traffic. In this manner, link failure 130 degrades the performance of information handling system 100.
FIG. 2A is a diagram of an information handling system 200 that is similar in many respects to information handling system 100 of FIGs. 1A and 1B. Thus, information handling system 200 includes switches 102A and 102B and nodes 110 and 112 configured largely as seen in information handling system 100. However, through the operation of link layer discovery protocol (LLDP) on nodes 110 and 112 and switches 102A and 102B, node 110 knows that it is connected to switches 102A and to switch 102B, which node 110 knows are two separate switches.
LLDP functions by the exchange of LLDP data units among the nodes and switches in information handling system 200. Each of the LLDP data units includes a source MAC address of the sender, chassis identifiers, and other information. The chassis identifier is a type-length-value (TLV) element, Chassis ID TLV. Node 110 is configured to receive LLDP data units and to extract information from them so that node 110 can determine which of its plurality of ports are connected to switch 102A and which are connected to switch 102B. Node 110 is further configured to form two sub-LAGs, a first sub-LAG 202 including the links to switch 102A and a second sub-LAG 204 including the links to switch 102B. All of the links in the first and second sub-LAGs are members of LAG 120, which hereinafter is referred to as parent LAG 120. Alternatively, the links connecting node 110 to switches 102A and 102B and node 112 to switches 102A and 102B are configured as port-channels, a port-channel being similar in many respects to a LAG. In such an instance, sub-LAGs 202 and 204 are sub-port-channels of a parent port-channel.
When a frame is being sent from node 110 to node 112, the destination MAC of the frame is used to perform a lookup in a MAC address tables stored in a local memory of node 110. If the MAC address table includes an entry associating the MAC address of node 112 (being used as the destination MAC of the frame) with parent LAG 120, then the frame is hashed on parent LAG 120. In such an instance, the frame could be sent to any of the member ports of parent LAG 120, so that the frame could be sent to either switch 102A or 102B. If the MAC address table includes an entry associating the MAC address with first sub-LAG 202, then the frame is forwarded on one of the links to switch 102A, not to switch 102B. The MAC address table stored in the local memory of node 110 may also include a field for virtual local area network identifiers (VLAN IDs).
In general, node 110 learns to associate the MAC address of node 112 with parent LAG 120 by receiving frames from node 112 that include the MAC address as the source MAC address and include a particular VLAN ID. However, node 110 is configured to alter the MAC address table when a frame is received that includes a downstream link failure indicator. In information handling system 200, when node 110 receives a frame having the downstream link failure indicator set to a first value and the frame includes a destination MAC address, node 110 can rewrite its MAC address table so that the MAC address and VLAN ID contained in the frame are associated with whichever sub-LAG receives the frame.
FIG. 2A depicts the receipt of a frame at node 110 from node 112. The frame may be a responsive frame, responsive to an earlier frame from sent from node 110 to node 112. When the frame is sent from node 112, it includes the MAC address of node 112, M1, as its source MAC address. The frame also includes a downstream link failure indicator set to a value that does not indicate the presence of the downstream link failure 130. In this example, the downstream link failure indicator is a Canonical Format Indicator (CFI) bit that is present in tagged frames, frames having a VLAN tag header. The bit is set to "0", which does not indicate the presence of the link failure 130. In other embodiments where the frame is not a tagged frame when sent from node 112 to switch 102A, switch 102A may be configured to add a priority tag that includes a CFI bit to the frame before forwarding it on to node 110.
Switch 102A receives the frame, and having notice from switch 102B of the link failure 130, sets the value of the downstream link failure indicator. In this example, switch 102A sets the CFI bit to "1" to indicate that a downstream link failure has been detected. In embodiments in which the frame was not sent from node 112 to switch 102A as a tagged frame including the CFI bit, a priority tag is added by switch 102A that includes a CFI set to "1" and the priority set to "0". Thus, the frame moving between switch 102A and node 110 includes the CFI bit set to "1" and M1 as the source MAC address.
Node 110 receives the frame having the CFI bit set to "1" to indicate the downstream link failure. Because the frame is received by node 110 on the links between it and switch 102A, by configuration it interprets this information as indicating that the link between node 112 and switch 102B has failed. Node 110 is configured to understand that the frame containing the downstream link failure indicator is received on links that are not coupled to the switch experiencing the failure, in this case switch 102B. In response to the downstream link failure indicator having the value indicating the presence of a link failure 130, node 110 re-writes the entry in its MAC address to associate the MAC address M1 with sub-LAG 202, the sub-LAG that contains the ports on which the indicator was received.
In FIG. 2B, the information handling system 200 with its MAC address table directing traffic to M1 to be sent out on sub-LAG 202 behaves differently than information handling system 100 of FIGs 1A and 1B. First, a frame arrives at node 110 having M1 as its destination MAC address. To send it out, node 110 performs a look-up in its MAC address table that indicates the frame should be sent out on sub-LAG 202. Second, the frame is hashed on sub-LAG 202 and sent out on a member port to switch 102A. Because the look-up did not indicate the frame was to be sent out on parent LAG 120, the frame could not have been forwarded to switch 102B. Third, the frame arrives at switch 102A, which then forwards it on to node 112. By hashing the frame on sub-LAG 202 rather than parent LAG 120, the frame is not sent to switch 102B, which would have required sending the frame over links 104, adding in latency and traffic on links 104.
While switch 102B detects the failed link between it and node 112, it continues to communicate this status to switch 102A until the failed link is restored. Alternatively, switch 102A sets the downstream link failure indicator to indicate the failure until switch 102B communicates that the link has been restored. When the link has been restored, switch 102A sets the indicator to show that the failure is no longer present. In embodiments where the CFI bit is used as the downstream link failure indicator, the CFI is set to a second value of "0" in frames travelling from node 112 to node 110. When a frame from M1 is received by node 110 having its CFI bit set to "0", node 110 re-writes the entry in the MAC address table to associate M1 with parent LAG 120. Thereafter (absent another downstream link failure), frames received by node 110 that include M1 as their destination address are hashed on parent LAG 120 and so may be sent to either switch 102A or switch 102B.
In some embodiments of information handling system 200, some actions may be taken to ensure that the computer processor of node 110 does not re-write the MAC address table entry associated with M1 before node 110 receives indication of the link restoration. For example, in some embodiments sub-LAG 202 and sub-LAG 204 are used only for frames egressing from node 110, while ingressing frames may be received as on parent LAG 120. In such an instance, the normal MAC learning operations may cause undesired station moves that over-write a MAC address table entry associating a MAC address with a sub-LAG.
One option for preventing unwanted station moves may include using class-based station moves. In such an embodiment, each port or port-channel on node 110 may be assigned a class or a priority. A higher class priority may be assigned to sub-LAG associations than to parent LAG associations, to prevent unwanted station moves from a sub-LAG to a parent LAG. An embodiment that uses a BROADCOM® TRIDENT™ chipset provided by BROADCOM of Irvine, CA, may provide such class or priority-based station moves, though other chipsets providing the same or similar functions may be used as well.
As long as frames do not reach the CPU, the CPU does not extract the information to update the MAC address table entry. In some embodiments, the MAC address table includes a class identification field, which can be used as a qualifier in the ingress field processor (IFP) entry. For MAC address table entries that the CPU re-writes to point to a sub-LAG, a designated class identification value is set in the entry. When the IFP applies rules to copy frames to the CPU, resources may be conserved by only copying frames that don't have a class identification value associated in the MAC address table for the MAC address at issue.
FIG. 3 is a functional diagram of an information handling device 300 that may be useful in understanding how node 110 of FIGs. 2A and 2B operates. Information handling device 300 may be a server or a switch, such as a top-of-rack switch or the VLT peer switches of information handling system 200. Hereinafter, information handling device 300 is referred to as node 300.
Node 300 includes a computer processor 302 in communication with a memory 310 and a plurality of ports 320A-D. While depicted as a single processor in FIG. 3, computer processor 302 may be a plurality of computer processors functioning together to provide various capabilities and features. In the depicted embodiment, computer processor 302 provides a type-length-value (TLV) processing module 304 and a control plane unit 306. When an LLDP data unit is received on one of ports 320A-D, the frame is processed by computer processor 302's TLV processing module 304. LLDP data units may be used to form sub-LAGs 202 and 204.
Any TLVs and any information included in the LLDP data units may be extracted by the TLV processing module 304. For example, as described above in connection with information handling system 200, an LLDP data unit may include a TLV that indicates the sender of the LLDP data unit, such as the Chassis ID TLV. When the TLV processing module 304 processes the Chassis ID TLV and other TLVs, it may extract the chassis identifier and store it, in connection with the port on which the LLDP data unit was received, in one or more look-tables including a MAC address table 312. In addition to the TLV processing module 304, node 300 includes a TLV library 316 that has a plurality of TLVs that can be included in LLDP data units sent by node 300 to any devices connected to ports 320A-D.
When sending a data packet or frame received on node 300 from an attached host (not depicted), computer processor 302 performs a look-up in MAC address table 312 stored in memory 310. The frame's VLAN ID and destination MAC address may be used to determine, by performing the look-up, that the frame may be hashed on the first sub-LAG 202. Computer processor may select from a plurality of hashing algorithms 314 stored in memory 310 to hash the frame to either port 320A or 320B, the member ports of the first sub-LAG 202 in the depicted embodiment. Also in the depicted embodiment, if MAC address table 312 indicates that frames with the particular destination MAC address may be hashed on parent LAG 120, then computer processor 302 hashes the frame on one of ports 320A, 320B, 320C, or 320D, the member ports of parent LAG 120. By controlling the LAG on which the frame is hashed, node 300 may send the frame more directly to another node in order to avoid detour through interconnect links 104 due to a failed VLT link.
FIGs. 4A and 4B depict an information handling system 400, which in many respects is similar to information handling system 200 of FIG. 2. Whereas the configuration of nodes and VLT peers in FIGs. 1A, 1B, 2A, and 2B may be referred to as a triangular VLT configuration, information handling system 400 may be referred to as a square VLT configuration. In a square VLT configuration information handling system 400 includes a first VLT domain 106 that includes two VLT peers: network devices 102A and 102B. Information handling system 400 also has a second VLT domain 406 that includes network devices or switches 402A and 402B as VLT peers connected by interconnect links 404. Each VLT peer of VLT domain 106 is connected to each VLT peer of VLT domain 406, and each VLT peer may be similar to information handling device 300 of FIG. 3.
In FIG. 4A, a frame is sent from node 110 having a destination MAC address accessible by node 112. Depicted in solid lines, the frame travels from node 110 to network device 402B in VLT domain 406. For brevity, the network devices in FIGs. 4A and 4B are referred to hereafter as "switches." In another example, the frame may be hashed on LAG 120 to switch 402A, rather than switch 402B.
From switch 402B, the frame is hashed on one of two sub-LAGs (only one being depicted) connected to switches 102A and 102B in VLT domain 106. As depicted the frame is sent from switch 402B to switch 102B and then to node 112. An exemplary responsive frame is depicted as travelling from node 112 to network device 102A, to network device 402A, and then finally to node 110. Again, the hashing performed by the nodes or switches in information handling system 400 may be different from those in the depicted frame flow and in many cases are.
In FIG. 4B, a link failure 130 is present on the link between switch 102B and node 112, such that traffic cannot flow over this link. Information handling system 400 is configured to mitigate the effects of link failure 130 in the following manner. Switch 102B is aware of link failure 130 and communicates the presence of the failure to switch 102A over interconnect links 104. Once switch 102A receives information of the failure from switch 102B, switch 102A begins setting the value of the CFI bit contained in frames sent upstream from node 112 to a first value that indicates the presence of link failure 130. In the depicted embodiment, the first value is "1". As explained in connection with information handling system 200 of FIG. 2B, if the frame received from node 112 does not have a CFI bit, a priority tag may be added to the frame to contain the CFI bit.
In the depicted embodiment, the frame is hashed to switch 402A, while in other embodiments the frame may be hashed to switch 402B. When switch 402A receives the packet with the CFI bit set to the first value indicating the presence of link failure 130, switch 402A reacts similarly to node 110 as described in the discussion of node 110's response in the information handling system 200 in FIGs. 2A and 2B. Thus, switch 402A associates the MAC address M1 with sub-LAG 410 in a MAC address table entry contained in internal memory. When switch 402A receives a frame with M1 as its destination MAC address, it hashes the frame only on sub-LAG 410, which is a LAG or port-channel half that includes all links connecting switch 402A to switch 102A and excludes all links connecting switch 402A and 102B, which switch 402A may recognize as part of an additional sub-LAG (not depicted). Thus, switch 402A sends frames to switch 102A, preventing the extra hop and added latency that may occur by sending frames to switch 102B.
This behavior is achieved without node 110 reacting to the link failure. Switch 402A transmits the frame on to node 110 with the CFI bit set to the second value, in this example "0", thus not indicating any link failure, since the link failure is mitigated by switches 402A and 402B. Thus, node 110 does not need to be made aware of the link failure and so switch 402A may be configured to reset the CFI bit from "1" to "0" before forwarding any received frames to it. Frames are received on switch 102A in such a way that the MAC address table entry is not over-written until the CFI bit's value reverts to a second value of "0", indicating the end of the link failure 130.
Additionally, switch 402A communicates the link failure to switch 402B over interconnect links 404. Switch 402B alters an entry in its MAC address table so that it behaves the same as switch 402A with respect to frames having the M1 MAC address. Thus switch 402B hashes frames received from node 110 that include M1 as the destination MAC address on a sub-LAG 412 to switch 102A, rather than on a parent LAG (not depicted) that could result in the frame being sent to switch 102B. When switch 402A receives communication indicating the link failure is resolved, this may be communicated to switch 402B over interconnect links 404 as well, allowing the MAC address table entry to re-associated M1 with the parent LAG.
FIG. 5 is a flowchart of a method 500 for directing traffic through a set of aggregated links during a failure of a downstream link. Method 500 begins in step 502 when a network device, such as information handling system 300 of FIG. 3, detects a downstream failure indicator having a first value in a header of a first frame received with a MAC address as its source MAC address. The network device determines whether the first frame was received on a first set of links or a second set of links, in step 504. In step 506, the network device associates the source MAC address with the set of links on which the first frame was received, and hashes a plurality of frames on the set of links on which the first frame was received, the plurality of frames having the MAC address as their destination MAC address, in step 508.
In operation, it may be useful to understand how method 500 may be carried out by a network device having the features of node 300 of FIG. 3 in an information handling system like information handling system 200 of FIG. 2A and 2B. For example, node 110 receives a frame from node 112 with M1 as its source MAC address and that has a VLAN ID and a downstream link failure indicator set in its header (step 502). The downstream link failure indicator is a CFI bit set to "1" in the header. Node 110 determines whether the frame was received on the set of links connecting to switch 102A or the set of links connecting to switch 102B (step 504). Node 110 associates the source MAC address of the frame with whichever set of links on which the frame was received in a MAC address table (step 506). In so doing, node 110 may associate the source MAC address and VLAN ID with either sub-LAG 202 or sub-LAG 204 in the MAC address table. When node 110 needs to send a frame to the device or service identified by the source MAC address, the frame is hashed on either sub-LAG 202 or sub-LAG 204, as associated in the MAC address table (step 508). Method 500 can also be explained in the context of information handling system 400 of FIG. 4. In such examples, switches 402A or 402B may implement method 500 rather than node 110.
FIG. 6 is a flowchart of a method 600 for directing traffic through a set of aggregated links during a failure of a downstream link. Method 600 may begin in step 602 when a first VLT peer network device receives a communication from a second VLT peer that the second VLT peer is experiencing a link failure on a link with a downstream node. In step 604, the first VLT peer receives a frame from the downstream node, the frame includes a MAC address of the downstream node. In step 606, the first VLT peer sets a downstream link failure indicator in the frame to a first value, and then forwards the frame to an upstream network device, in step 608.
Method 600 may be better understood with reference to FIGs. 2A, 2B, 4A, and 4B. For example, method 600 may be performed when switch 102A receives a communication from switch 102B that the link or links between switch 102B and node 112 are down (step 602). Switch 102A receives a frame from node 112 that includes a MAC address accessible at or through node 112 (step 604). Before transmitting the packet upstream toward node 110, switch 102A sets a CFI bit to "1" to communicate the presence of the downstream link failure to network devices upstream and then forwards the frame to an upstream network device (steps 606 and 608). As depicted in FIGs. 2A and 2B, the upstream network device is node 110. However, in embodiments like that depicted in FIG. 4, the upstream network device is an additional switch, like switch 402 in VLT domain 406.
Some embodiments of information handling systems 200 and 400 include non-transient, tangible, machine-readable media that include executable code that when run by a processor, such as computer processor 302 of node 300 in FIG. 3, may cause the processor to perform the steps of method 500 or 600 as described above. Some common forms of machine-readable media that may include the steps of methods 500 and/or 600 are, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, and/or any other medium from which a processor or computer is adapted to read. The machine-readable media may be memory 310 of FIG. 3.
The examples provided above are exemplary only and are not intended to be limiting. One skilled in the art may readily devise other systems consistent with the disclosed embodiments which are intended to be within the scope of this disclosure. As such, the application is limited only by the following claims.
Informationsverarbeitungssystem (100, 200), umfassend:
einen ersten NetzwerkSwitch (102B), wobei der erste NetzwerkSwitch umfasst:
einen Computerprozessor (302) in Verbindung mit einer Vielzahl von Anschlüssen (320A, 320B, 320C, 320D) zum Empfangen und Senden von Frames, wobei der Computerprozessor zum Lesen von Frames konfiguriert ist, wobei jeder Frame einen Header aufweist;
einen Speicher (310), der mit dem Computerprozessor gekoppelt ist und eine Medienzugriffssteuer, MAC, -Adresstabelle beinhaltet;
und wobei der Computerprozessor (302) konfiguriert ist, um eine Ziel-MAC-Adresse und einen virtuelles lokales Zugriffsnetzwerk, VLAN, -Identifikator mit einer Eltern-Link-Aggregationsgruppe, LAG, (120) zuzuordnen, außer während ein Downstream-Link-Fehler (130) erfasst wird, wobei der Computerprozessor (302) konfiguriert ist, um den Downstream-Link-Fehler durch Lesen von Headern von Frames, die die MAC-Adresse als ihre Quell-MAC-Adresse beinhalten, zu erfassen, wobei der Computerprozessor (302) konfiguriert ist, um die Ziel-MAC-Adresse und den VLAN-Identifikator einer Sub-LAG (202, 204) zuzuordnen, während der Downstream-Link-Fehler (130) anstelle des Eltern-LAG (120) erfasst wird,
wobei die Sub-LAG (202, 204) ein Mitglied der Eltern-LAG (120) ist.
2. Informationsverarbeitungssystem nach Anspruch 1, wobei die Header eine Downstream-Link-Fehleranzeige beinhalten, die auf einen ersten Wert eingestellt ist, um das Vorhandensein des Downstream-Link-Fehlers anzuzeigen, wobei die Downstream-Link-Fehleranzeige ein kanonisches Formatindikatorbit in einem VLAN-Tag-Header ist.
Informationsverarbeitungssystem nach Anspruch 1, ferner umfassend eine Steuerebeneneinheit (CPU) und einen Eingangsfeldprozessor (IFP), der vom Computerprozessor bereitgestellt wird, wobei:
der IFP eine Menge von Regeln anwendet, die bestimmen, ob Frames auf die CPU kopiert werden oder nicht; und
die CPU die MAC-Adresse der Eltern-LAG oder der Sub-LAG in der MAC-Adresstabelle zuordnet.
Informationsverarbeitungssystem nach Anspruch 1, ferner umfassend:
einen zweiten NetzwerkSwitch und einen dritten NetzwerkSwitch, wobei der zweite und dritte NetzwerkSwitch in einer Virtual Link Trunking (VLT)-Domäne konfiguriert sind und mit dem ersten NetzwerkSwitch durch die Eltern-LAG und mit einem vierten NetzwerkSwitch durch eine zusätzliche LAG gekoppelt sind, und wobei
die Eltern-LAG eine erste Menge von Links, die den ersten und zweiten NetzwerkSwitch koppeln, und eine zweite Menge von Links, die den ersten und dritten NetzwerkSwitch koppeln, enthält, und
die zusätzliche LAG eine dritte Menge von Links, die den vierten und zweiten NetzwerkSwitch und eine vierte Satz von Links, die den vierten und dritten NetzwerkSwitch koppeln, enthält.
5. Informationsverarbeitungssystem nach Anspruch 1, wobei sich der erste Switch und ein zweiter Switch in einer ersten virtuellen Link Trunking (VLT)-Domäne befinden und mit einer zweiten VLT-Domäne gekoppelt sind, und wobei der erste Switch konfiguriert ist, um den Downstream-Link-Fehler an den zweiten Switch zu kommunizieren, so dass ein Computerprozessor des zweiten Switchs die MAC-Adresse für eine Dauer des Downstream-Link-Fehlers mit einer zweiten Sub-LAG und nicht mit einer zweiten Eltern-LAG verknüpft, wobei die zweite Eltern-LAG und die zweite Sub-LAG durch den zweiten Switch bereitgestellt werden und Links von dem zweiten Switch zur zweiten VLT-Domäne beinhalten.