US20120281700A1 - Layer-3 support in trill networks - Google Patents
Layer-3 support in trill networks Download PDFInfo
- Publication number
- US20120281700A1 US20120281700A1 US13/312,903 US201113312903A US2012281700A1 US 20120281700 A1 US20120281700 A1 US 20120281700A1 US 201113312903 A US201113312903 A US 201113312903A US 2012281700 A1 US2012281700 A1 US 2012281700A1
- Authority
- US
- United States
- Prior art keywords
- rbridge
- virtual
- switch
- destination
- router
- 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.)
- Granted
Links
Images
Classifications
-
- 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/02—Topology update or discovery
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/60—Software-defined switches
Definitions
- the present disclosure relates to network design. More specifically, the present disclosure relates to a method and system for constructing a scalable switching system that supports layer-3 routing while facilitating automatic configuration.
- switch stacking One way to increase the throughput of a switch system is to use switch stacking.
- switch stacking multiple smaller-scale, identical switches are interconnected in a special pattern to form a larger logical switch.
- the amount of required manual configuration and topological limitations for switch stacking becomes prohibitively tedious when the stack reaches a certain size, which precludes switch stacking from being a practical option in building a large-scale switching system.
- TRILL Transparent Interconnection of Lots of Links
- TRILL brings many desirable features to layer-2 networks, some issues remain unsolved when layer-3 processing is desired.
- the switch includes an IP header processor and a forwarding mechanism.
- the IP header processor identifies a destination IP address in a packet encapsulated with an inner Ethernet header, a TRILL header, and an outer Ethernet header.
- the forwarding mechanism determines an output port and constructs a new header for the packet based on the destination IP address.
- the switch also includes a packet processor which determines whether (1) an inner destination media access control (MAC) address corresponds to a local MAC address assigned to the switch; (2) a destination RBridge identifier (RBridge ID) corresponds to a local RBridge identifier assigned to the switch; and (3) an outer destination MAC address corresponds to the local MAC address.
- MAC media access control
- the packet processor determines a first virtual local area network (VLAN) tag in the inner Ethernet header, wherein the new header includes a new inner Ethernet header which comprises a second VLAN tag.
- VLAN virtual local area network
- the switch includes a control mechanism which forms a virtual cluster switch in conjunction with one or more additional switches.
- the virtual cluster switch is an Ethernet fabric switch functioning as a logical Ethernet switch.
- the switch includes a switching mechanism switches the packet between VLANs based on the destination IP address.
- the RBridge identifier is a virtual RBridge identifier and the destination IP address is a virtual IP address assigned to a virtual IP router associated with the virtual RBridge identifier.
- the virtual IP router is formed by operating the switch in conjunction with at least another physical switch as a single logical router.
- FIG. 1 illustrates an exemplary TRILL network that includes a plurality of RBridges with IP processing capabilities, in accordance with an embodiment of the present invention.
- FIG. 2A illustrates an exemplary configuration of end devices belonging to different VLANs and coupled to a TRILL network, wherein one RBridge is IP capable, in accordance with an embodiment of the present invention.
- FIG. 2B illustrates an exemplary configuration of end devices belonging to different VLANs and coupled to a TRILL network, wherein all RBridges are IP capable, in accordance with an embodiment of the present invention.
- FIG. 3A illustrates an exemplary TRILL network with multiple VLANs, in accordance with an embodiment of the present invention.
- FIG. 3B illustrates an exemplary TRILL network with multiple VLANs, wherein each RBridge belongs to all VLANs, in accordance with an embodiment of the present invention.
- FIG. 4A presents a flowchart illustrating the process of an RBridge transmitting a frame, in accordance with an embodiment of the present invention.
- FIG. 4B presents a flowchart illustrating the process of an IP-capable RBridge transmitting a frame, in accordance with an embodiment of the present invention.
- FIG. 5 illustrates an exemplary network where a virtual RBridge and an associated virtual IP router are created based on a plurality of physical gateway RBridges with IP processing capabilities, in accordance with an embodiment of the present invention.
- FIG. 6A illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to a number of gateway RBridges in a TRILL network, in accordance with an embodiment of the present invention.
- FIG. 6B illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to all RBridges in a TRILL network where each RBridge has IP processing capability, in accordance with an embodiment of the present invention.
- FIG. 7A presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge responding to an Address Resolution Protocol (ARP) query, in accordance with an embodiment of the present invention.
- ARP Address Resolution Protocol
- FIG. 7B presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge forwarding a TRILL frame, in accordance with an embodiment of the present invention.
- FIG. 8 illustrates a scenario where one of the RBridges associated with the virtual RBridge experiences a link failure and/or a node failure, in accordance with an embodiment of the present invention.
- FIG. 9 illustrates an exemplary architecture of a switch with IP processing capabilities, in accordance with an embodiment of the present invention.
- the problem of providing scalable and flexible layer-3 (e.g., IP) support in a TRILL network is solved by facilitating IP routing in a number of RBridges in the TRILL network.
- the availability of IP processing within a TRILL network allows cross-layer-2-domain traffic (e.g., traffic across different VLANs) to be forwarded within a TRILL network, which reduces forwarding overhead.
- the IP router portion of one of these IP-capable RBridges is assigned as a default gateway router to an end device coupled to a TRILL network. Wherever the end device sends a frame to outside of its local network (e.g., a VLAN), the frame is forwarded to and processed by the IP router portion of the RBridge.
- This layer-3 processing occurs within the TRILL network. Note that, in a conventional TRILL network, such layer-3 processing has to be done by an IP router residing outside the TRILL network.
- the end-device may be coupled to the TRILL network via an ingress RBridge without IP processing capability.
- the TRILL RBridge portion of an IP-capable RBridge acts as an egress RBridge and the IP router portion of the RBridge can act as the default gateway router.
- a frame from the end device is received at the ingress RBridge and encapsulated in a TRILL packet, wherein the TRILL packet sets the egress RBridge identifier as the destination RBridge identifier, and the MAC address of the egress RBridge as the inner destination MAC address.
- the packet is then forwarded though the TRILL network and reaches the egress RBridge, where the outer destination MAC address of the packet is the MAC address of the egress RBridge.
- the IP router portion of the egress RBridge then processes the IP header in the frame and makes the layer-3 forwarding decision based on the destination IP address of the frame.
- the IP router portion of an IP-capable RBridge may be associated with multiple VLANs associated with the TRILL network. If the destination end device of the frame belongs to one of the associated VLANs, the IP router can obtain the MAC address of the destination end device using ARP requests within that VLAN. The corresponding RBridge of the IP router then sets the RBridge to which the destination end device is coupled as the egress RBridge and forwards the frame to the egress RBridge over the TRILL network.
- embodiments of the present invention are not limited to TRILL networks, or networks defined in a particular Open System Interconnection Reference Model (OSI reference model) layer.
- OSI reference model Open System Interconnection Reference Model
- RBridge refers to routing bridges, which are bridges implementing the TRILL protocol as described in IETF Request for Comments (RFC) “Routing Bridges (RBridges): Base Protocol Specification,” available at http://tools.ietf.org/html/rfc6325, which is incorporated by reference herein. Embodiments of the present invention are not limited to applications among RBridges. Other types of switches, routers, and forwarders can also be used.
- edge port refers to a port which sends/receives data frames in native Ethernet format.
- TRILL port refers to a port which sends/receives data frames encapsulated with a TRILL header and outer MAC header.
- End device refers to a network device that is typically not TRILL-capable. “End device” is a relative term with respect to the TRILL network. However, “end device” does not necessarily mean that the network device is an end host. An end device can be a host, a conventional layer-2 switch, or any other type of network device. Additionally, an end device can be coupled to other switches or hosts further away from the TRILL network. In other words, an end device can be an aggregation point for a number of network devices to enter the TRILL network.
- IP-capable RBridge refers to a physical RBridge that can process and route IP packets.
- An IP-capable RBridge can be coupled to a layer-3 network and can forward IP packets from end devices to the layer-3 network.
- a number of IP-capable RBridges can form a virtual RBridge and a corresponding virtual IP router, thereby facilitating a virtual gateway router for end devices that supports redundancy and load-balancing.
- an RBridge which forms a virtual RBridge and a virtual IP router is also referred to as a “gateway” RBridge.
- a gateway RBridge responds to ARP requests for the virtual IP address with a virtual MAC address.
- gateway RBridges can form the virtual RBridge.
- gateway RBridges can process both TRILL and IP packets, in this disclosure the term “gateway RBridge” can refer to a physical RBridge in a TRILL network or a physical router in an IP network.
- IP router refers to the IP-capable portion of an RBridge or a stand-alone IP router.
- IP router and “router” are used interchangeably.
- frame refers to a group of bits that can be transported together across a network. “Frame” should not be interpreted as limiting embodiments of the present invention to layer-2 networks. “Frame” can be replaced by other terminologies referring to a group of bits, such as “packet,” “cell,” or “datagram.”
- RBridge identifier refers to a group of bits that can be used to identify an RBridge.
- TRILL standard uses “RBridge ID” to denote a 48-bit intermediate-system-to-intermediate-system (IS-IS) System ID assigned to an RBridge, and “RBridge nickname” to denote a 16-bit value that serves as an abbreviation for the “RBridge ID.”
- RBridge identifier is used as a generic term and is not limited to any bit format, and can refer to “RBridge ID” or “RBridge nickname” or any other format that can identify an RBridge.
- FIG. 1 illustrates an exemplary TRILL network that includes a plurality of RBridges with IP processing capabilities, in accordance with an embodiment of the present invention.
- a TRILL network 100 includes RBridges, 101 , 102 , 103 , 104 , 105 , 106 , and 107 .
- RBridges 101 , 102 , and 103 are IP capable and coupled to a layer-3 network 150 as IP routers, 111 , 112 , and 113 , respectively.
- IP routers 111 , 112 , and 113
- RBridge 101 and IP router 111 are the same physical device (represented by dotted lines), where its TRILL RBridge portion is denoted by RBridges 101 and its IP router portion is denoted by router 111 .
- RBridge 102 and IP router 112 , and RBridge 103 and IP router 113 are the same physical devices, respectively.
- RBridges in network 100 use edge ports to communicate to end devices and TRILL ports to communicate to other RBridges.
- RBridge 104 is coupled to end device 122 via an edge port and to RBridges 105 , 101 , and 102 via TRILL ports.
- An end host coupled to an edge port may be a host machine or an aggregation node.
- end devices 122 , 124 , 126 , and 128 are host machines, wherein end devices 122 and 128 are directly coupled to network 100 , and end devices 124 and 126 are coupled to network 100 via their aggregation node, a layer-2 bridge 130 .
- end device 128 is directly coupled to RBridge 103 .
- IP router 113 can act as the default gateway for end device 128 . Consequently, all frames from end device 128 destined to IP network 150 are received at IP router 113 and forwarded to network 150 .
- RBridge 104 couples end device 122 to network 100 and acts as the ingress RBridge for all frames from end device 122 .
- One of the IP-capable RBridges (e.g., RBridge 101 ) acts as the egress RBridge for frames from end device 122 to network 150 .
- the frame destined to network 150 is encapsulated in a TRILL packet with the RBridge identifier of RBridge 101 as the destination RBridge identifier, and the MAC address of RBridge 101 as the inner destination MAC address.
- the TRILL packet is then forwarded to RBridge 101 , where the outer destination MAC address of the packet is the MAC address of RBridge 101 .
- IP router 111 then processes the IP header in the frame and makes the layer-3 forwarding decision based on the destination IP address of the frame.
- an end device coupled to the TRILL network may select the default gateway from a layer-3 network and use the corresponding IP address as a default gateway router address. For example, in FIG. 1 , end device 128 selects the default gateway router from IP network 150 . Any frame destined to network 150 from end device 128 is sent to the default gateway. Under such a scenario, if end devices 122 and 128 are on different VLANs, any communication between these end devices will go through network 150 . If end device 128 sends a frame to end device 122 , the frame first goes to the default gateway in network 150 . Consequently, the default gateway processes the IP header in the frame and makes layer-3 forwarding decision toward end device 122 . As a result, routing and bandwidth management will be inefficient and the frame will incur higher latency.
- IP router 113 processes the IP header in the frame and makes the forwarding decision toward end device 122 (which involves forwarding the frame on end device 122 's VLAN through TRILL network 100 ). Consequently, RBridge 103 forwards the frame to a corresponding egress RBridge 104 over TRILL network 100 .
- RBridge 104 transmits the frame to end device 122 .
- enabling layer-3 support on RBridges in a TRILL network provides higher efficiency in routing and bandwidth management.
- the TRILL network may be a virtual cluster switch (VCS).
- VCS virtual cluster switch
- any number of RBridges in any arbitrary topology may logically operate as a single switch. Any new RBridge may join or leave the VCS in “plug-and-play” mode without any manual configuration.
- TRILL is only used as a transport between the switches within network 100 . This is because TRILL can readily accommodate native Ethernet frames. Also, the TRILL standards provide a ready-to-use forwarding mechanism that can be used in any routed network with arbitrary topology. Embodiments of the present invention should not be limited to using only TRILL as the transport. Other protocols (such as multi-protocol label switching (MPLS)), either public or proprietary, can also be used for the transport.
- MPLS multi-protocol label switching
- FIG. 2A illustrates an exemplary configuration of how end devices belonging to different VLANs and coupled to a TRILL network, wherein one RBridge is IP capable, in accordance with an embodiment of the present invention.
- a TRILL network 200 includes TRILL RBridges 220 and 230 .
- End device 202 is coupled to RBridge 220 over VLAN 212
- end device 204 is coupled to RBridge 220 over VLAN 214 .
- RBridge 230 is IP capable and IP router 235 is the IP router portion of RBridge 230 (denoted in dotted line). IP router 235 functions as a default gateway router for end devices 202 and 204 . Consequently, although RBridge 220 couples both end devices 202 and 204 to network 200 , any traffic between end devices 202 and 204 will be routed via IP router 235 because end devices 202 and 204 belong to different VLANs. For example, if end device 202 sends a frame to end device 204 , it first assembles an IP packet with end device 204 's IP address.
- end device 202 Based on its local forwarding table, end device 202 realizes that it does not have a direct route to end device 204 , and therefore needs to send the packet to gateway router 235 . Hence, end device 202 encapsulates the IP packet in an Ethernet frame, whose destination MAC address is set to be gateway router 235 's MAC address. Note that, if end device 202 has no knowledge of IP router 235 's MAC address, end device 202 can send out an ARP request corresponding to the IP address of router 235 . Router 235 then replies to the ARP request with its MAC address. Subsequently, end device 202 forwards the frame to RBridge 230 via ingress RBridge 220 .
- IP router 235 receives the frame and removes its leayer-2 header (including the VLAN tag corresponding to VLAN 212 ). IP router 235 then performs a lookup in its IP forwarding table based on the packet's destination IP address, and encapsulates the packet with a new Ethernet header which includes a VLAN tag corresponding VLAN 214 . RBridge 230 then encapsulates the Ethernet frame with a TRILL header and forwards it to end device 204 via egress RBridge 220 .
- FIG. 2B illustrates an exemplary configuration of end devices belonging to different VLANs and coupled to a TRILL network, wherein all RBridges are IP capable, in accordance with an embodiment of the present invention.
- a TRILL network 200 includes TRILL RBridges 220 and 230 .
- End device 202 is coupled to RBridge 220 over VLAN 212
- end device 204 is coupled to RBridge 220 over VLAN 214 .
- both RBridges 220 and 230 are IP capable and IP routers 225 and 235 are the IP router portion of RBridges 220 and 230 , respectively.
- IP router 225 can be the default gateway router for end devices 202 and 204 . Consequently, any traffic between end devices 202 and 204 can be routed via IP router 225 . For example, if end device 202 sends a frame to end device 204 , it assembles an IP packet with end device 204 's IP address, encapsulates the IP packet in an Ethernet frame with destination MAC address as router 225 's MAC address, and forwards the frame to RBridge 225 via ingress RBridge 220 .
- end device 202 obtains the IP address of router 225 using ARP.
- IP router 225 receives the frame, performs a lookup in its IP forwarding table, encapsulates the packet with a new Ethernet header which includes a VLAN tag corresponding VLAN 214 , and forwards it to end device 204 via egress RBridge 220 .
- IP-processing capability at RBridge 220 thereby reduces the bandwidth usage in network 200 .
- layer-3 processing capabilities can be distributed to multiple or all TRILL RBridges. In some embodiments, layer-3 processing capabilities associated different the VLANs can be distributed selectively across multiple RBridges.
- FIG. 3A illustrates an exemplary TRILL network with multiple VLANs, in accordance with an embodiment of the present invention.
- network 300 includes RBridges 304 , 305 , 306 , and 307 . Each of these RBridges is IP capable.
- RBridge 304 is coupled to end devices 311 and 312 ; RBridge 305 is coupled to end devices 312 , 313 , and 314 ; RBridge 306 is coupled to end devices 315 , 316 , and 317 ; and RBridge 307 is coupled to end devices 317 and 318 .
- RBridges 305 and 306 belong to VLAN 328 ; RBridges 304 , 306 , and 307 , and end devices 312 and 318 belong to VLAN 326 ; RBridges 304 , 305 , and 306 , and end device 311 belong to VLAN 324 ; and RBridges 305 , 306 , and 307 , and end device 317 belong to VLAN 322 .
- a layer-3 interface on an RBridge corresponding to a VLAN is a Switch Virtual Interface (SVI).
- SVI Switch Virtual Interface
- RBridge 304 in FIG. 3A has SVIs for VLANs 324 and 326 (although these SVIs can be on the same physical interface). Consequently, RBridge 304 and end device 318 , and RBridge 304 and end device 311 , are on the same VLAN segment. If end device 311 sends a frame to end device 318 , the destination is outside of VLAN 324 . Consequently, end device 318 sets the destination MAC address of the frame as the MAC address of the SVI on VLAN 324 at RBridge 304 , which is the layer-3 gateway on VLAN 324 .
- SVI Switch Virtual Interface
- End device 318 then forwards the frame to RBridge 304 .
- RBridge 304 Upon receiving the frame, RBridge 304 recognizes that the frame's destination MAC address is a local MAC address. RBridge 304 then removes the frame's Ethernet header, performs a lookup in its IP forwarding table based on the frame's destination IP address, and encapsulates the frame with a new Ethernet header with a destination MAC address corresponding to end device 318 in VLAN 326 . Finally, RBridge 304 forwards the frame to end device 318 via egress RBridge 307 .
- RBridge 304 cannot forward the frame to end device 317 because RBridge 304 does not have an SVI on VLAN 322 , to which end device 317 belongs.
- RBridge 304 upon receiving a frame destined to end device 317 from end device 311 , RBridge encapsulates the frame using a TRILL header with egress RBridge identifier corresponding to RBridge 306 because it has SVIs to all VLANs.
- RBridge 304 then forwards the frame to RBridge 306 .
- the frame is routed though the TRILL network and reaches RBridge 306 when the outer destination MAC addresses match the MAC address of RBridge 306 .
- RBridge 306 Upon receiving the frame, RBridge 306 recognizes that the frame's outer destination MAC address is a local MAC address. RBridge 306 then removes the TRILL encapsulations, encapsulates the IP packet with a new Ethernet header with a destination MAC address corresponding to end device 317 in VLAN 322 , and forwards the frame accordingly.
- FIG. 3B illustrates an exemplary TRILL network with multiple VLANs, wherein each RBridge belongs to all VLANs, in accordance with an embodiment of the present invention.
- TRILL network 300 includes RBridges 304 , 305 , 306 , and 307 . Each of these RBridges is IP capable. End device 312 is coupled to RBridges 304 and 305 , end device 317 is coupled to RBridges 306 and 307 , and end device 318 is coupled to RBridge 307 . All RBridges in network 300 have SVIs for VLANs 322 and 326 . End devices 312 and 318 belong to VLAN 322 , and end device 317 belongs to VLAN 326 .
- the frame can be routed on layer-3 at RBridge 307 because RBridge 307 has SVIs for VLANs 322 and 326 . As the frame does not travel to any other RBridge in network 300 , it incurs lower latency while saving bandwidth in network 300 . Similarly, if end device 317 sends a frame to end device 312 , the frame can be routed on layer-3 at the IP router portion of either RBridge 306 or 307 as both have SVIs for VLANs 322 and 326 . If all RBridges in the TRILL network have SVIs for all VLANs, inter-VLAN switching is possible at each RBridge.
- FIG. 4A presents a flowchart illustrating the process of an RBridge transmitting a frame, in accordance with an embodiment of the present invention.
- an RBridge receives a frame (operation 402 ) and determines the type of port at which the frame was received (operation 404 ). If the frame is received at an edge port, then the RBridge checks whether the destination is coupled to a local edge port (operation 410 ). If the destination is not coupled to a local edge port, the RBridge encapsulates the frame in a TRILL packet and sets the RBridge identifier of the RBridge to which the end device is coupled as the egress RBridge identifier (operation 416 ). The RBridge then forwards the TRILL packet to the TRILL network (operation 418 ). Note that the MAC learning process allows an RBridge to learn about the port to which the end device is coupled.
- the RBridge transmits the frame to the destination end device coupled to a local edge port (operation 414 ).
- the RBridge checks whether itself is the egress RBridge of the TRILL packet (operation 408 ). If not, then the RBridge forwards the TRILL packet to the TRILL network (operation 418 ). Otherwise, the RBridge transmits the frame to the destination end device coupled to a local edge port (operation 414 ).
- FIG. 4B presents a flowchart illustrating the process of an IP-capable RBridge transmitting a frame, in accordance with an embodiment of the present invention.
- the exemplary process in FIG. 4B is also applicable to embodiments with distributed layer-3 processing, as described in conjunction with FIG. 3A .
- an RBridge receives a frame (operation 452 ) and determines the type of port at which the frame is received (operation 454 ). If the frame is received at an edge port, then the RBridge inspects the frame to determine whether the end device with the destination MAC address is coupled to a local edge port (operation 456 ). If so, the frame is forwarded to the destination via the TRILL network (operation 464 ), as described in conjunction with FIG. 4A .
- the RBridge determines whether the frame's destination MAC address is the RBridge's MAC address (operation 458 ). If the destination MAC address is not the RBridge's MAC address, then the RBridge encapsulates the frame in a TRILL packet and sets the RBridge identifier of a gateway RBridge as the egress RBridge identifier (operation 466 ). The RBridge then forwards the TRILL packet to the TRILL network (operation 476 ). On the other hand, if the frame's destination MAC address is the RBridge's MAC address (operation 458 ), then the RBridge performs layer-3 processing on the frame (operation 468 ) and determines the outgoing port (operation 470 ).
- the RBridge determines the type of the outgoing port (operation 462 ). If the outgoing port is an edge port, which means the destination end device is coupled locally, the RBridge forwards the frame, which is Ethernet encapsulated with the end device's MAC address as the destination MAC address, to the destination end device (operation 480 ).
- the end device can be a layer-3 (e.g., IP) router. If the outgoing port is a TRILL port, then the end device is connected to a remote RBridge. Hence, the RBridge obtains the
- RBridge identifier of the RBridge to which the destination end device is coupled to based on the MAC address of the destination end device (operation 472 ).
- the RBridge then encapsulates the frame in a TRILL packet and sets the obtained RBridge identifier as the egress RBridge identifier (operation 474 ).
- the RBridge then forwards the TRILL packet to the TRILL network (operation 476 ).
- the RBridge checks whether itself is the egress RBridge of the TRILL packet (operation 460 ). If not, then the RBridge forwards the TRILL packet to the TRILL network (operation 476 ). Otherwise, the RBridge forwards the frame to the destination end device coupled to a local edge port (operation 480 ).
- the end device can be a layer-3 router, in which case the forwarding includes layer-3 processing on the frame.
- a number of TRILL RBridges with IP processing capabilities may act as layer-3 routers for an end device. These RBridges can form a virtual RBridge, which is assigned with a virtual RBridge identifier. Furthermore, these RBridges form a virtual IP router, which is assigned with a virtual IP address and a corresponding virtual MAC address. This virtual IP router operates as a default gateway router, which can provide redundancy and load balancing.
- FIG. 5 illustrates an exemplary network where a virtual RBridge and an associated virtual IP router are created based on a plurality of physical gateway RBridges with IP processing capabilities, in accordance with an embodiment of the present invention.
- a TRILL network 500 includes RBridges 504 , 505 , 506 , 507 , 511 , 512 , and 513 .
- RBridges 511 , 512 , and 513 operate as gateway RBridges and are coupled to a layer-3 network 150 as IP routers 521 , 522 , and 523 , respectively.
- gateway RBridge 511 and IP router 521 are same physical device (represented by dotted lines), where its TRILL RBridge portion is denoted by gateway RBridge 511 and its IP router portion is denoted by IP router 521 .
- gateway RBridge 512 and IP router 522 , and gateway RBridge 513 and IP router 523 are the same physical devices, respectively.
- Gateway RBridges 511 , 512 , and 513 form a virtual RBridge 530 by operating as a single logical RBridge in TRILL network 500 .
- the corresponding IP routers 521 , 522 , and 523 form a virtual IP router 540 by operating as a single logical IP router.
- An end device 562 coupled to network 500 through RBridge 507 can use virtual IP router 540 as the default gateway router to layer-3 network 550 .
- Virtual RBridge 530 is considered to be logically coupled to gateway RBridges 511 , 512 , and 513 , optionally with zero-cost links represented by dashed lines. Furthermore, gateway RBridges 511 , 512 , and 513 can advertise their respective connectivity (optionally via zero-cost links) to virtual RBridge 530 . As a result, other RBridges in the TRILL network can learn that virtual RBridge 530 is reachable via gateway RBridges 511 , 512 , and 513 , and establish TRILL paths to virtual RBridge 530 using a corresponding virtual RBridge identifier through these gateway RBridges.
- All the IP-layer router portions of these gateway RBridges are configured to operate as the layer-3 gateway router (i.e., virtual IP router 540 ) for end device 562 .
- End device 562 uses virtual IP router 540 as the default gateway.
- virtual RBridge 530 is associated with virtual IP router 540 , incoming frames from end device 562 destined to network 550 are marked with virtual RBridge 530 's identifier as the egress RBridge identifier. Consequently, all frames from end device 562 to network 550 are delivered to one of the gateway RBridges 511 , 512 , and 513 .
- load balancing can be achieved among gateway RBridges 511 , 512 , and 513 for frames sent to virtual RBridge 530 .
- FIG. 6A illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to a number of gateway RBridges in a TRILL network, in accordance with an embodiment of the present invention.
- a TRILL network 600 includes a number of TRILL RBridges 602 , 604 , and 606 .
- Network 600 also includes RBridges 616 and 618 , each with a number of edge ports which can be coupled to external networks.
- RBridges 616 and 618 are coupled with end devices 652 and 654 via 10GE edge ports.
- RBridges in network 600 are in communication with each other using TRILL protocol.
- RBridges 622 and 624 are layer-3 capable and coupled to an IP network 680 .
- Gateway RBridges 622 and 624 form virtual RBridge 640 with a virtual RBridge identifier 645 .
- Physically co-located IP Routers 632 and 634 within gateway RBridges 622 and 624 respectively, form a virtual IP router 670 which is assigned a virtual IP address 660 and a virtual MAC address 650 .
- Virtual IP address 660 maps to virtual MAC address 650 for ARP requests directed to virtual IP router 670 .
- virtual RBridge identifier 645 is associated with virtual MAC address 650 .
- End devices 652 and 654 can set virtual IP address 660 as their default gateway router address and use ARP to obtain virtual MAC address 650 .
- End devices 652 and 654 send frames with virtual MAC address 650 as the destination address into network 600 .
- the frames are encapsulated in TRILL packets and routed toward virtual RBridge 640 using the corresponding virtual RBridge identifier 645 .
- a virtual IP address can be assigned for each VLAN associated with a TRILL network.
- end device 652 may belong to VLAN 692
- end device 654 may belong to VLAN 694 .
- Different virtual IP addresses may be used for VLANs 692 and 694 , respectively.
- End devices 652 and 654 then use the virtual IP address associated with VLAN 692 and VLAN 694 as their respective default gateway router addresses. Consequently, end devices 652 and 654 perceive virtual IP router 670 to be in VLAN 692 and VLAN 694 , respectively.
- ARP requests for either virtual IP address the same virtual MAC address 650 is sent in reply. All data frames injected to TRILL network 600 with virtual MAC address 650 as the destination MAC address are routed toward virtual RBridge 640 .
- the virtual MAC address is known to all RBridges in the network 600 . Otherwise, both IP routers 632 and 634 receive a frame forwarded to virtual MAC address 650 and results in packet duplication. Hence, after formation of virtual RBridge 640 and virtual IP router 670 , all RBridges in network 600 are provided with the knowledge about virtual MAC address 650 . That is, virtual MAC address 650 is always “known” to all ingress RBridges in network 600 , and frames destined to virtual MAC address 650 are routed through network 600 using TRILL unicast.
- only one gateway RBridge is elected to reply to ARP requests for the virtual IP address. This election can also be VLAN specific.
- FIG. 6B illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to all RBridges in a TRILL network where each RBridge has IP processing capability, in accordance with an embodiment of the present invention.
- all RBridges in TRILL network 600 have IP processing capabilities.
- IP processing capacity at all RBridges enables them to route across VLANs, as described in conjunction with FIG. 3B .
- any traffic between VLANs 692 and 694 can be switched at RBridges 616 and 618 without requiring the traffic to travel to another RBridge in network 600 .
- all RBridges in network 600 are associated with virtual RBridge 640 and a virtual IP router 670 , and share a virtual RBridge identifier 645 , a virtual IP address 660 , and a virtual MAC address 650 . In some embodiments, all RBridges in network 600 may be connected to IP network 680 .
- FIG. 7A presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge responding to an Address Resolution Protocol (ARP) query, in accordance with an embodiment of the present invention.
- the gateway RBridge Upon receiving an ARP request packet for an IP address (operation 702 ), the gateway RBridge checks whether the ARP request is for a virtual IP address (operation 704 ). If not, the gateway RBridge responds based on the IP address in the ARP request (assuming that IP address is the gateway RBridge's physical IP address) (operation 720 ). Otherwise, the gateway RBridge checks whether it is elected to respond to an ARP request for the virtual IP address (operation 706 ). If not, the ARP request is discarded.
- ARP Address Resolution Protocol
- the gateway RBridge retrieves the virtual MAC address for the virtual IP address (operation 708 ) and generates an ARP reply containing the virtual MAC address (operation 710 ).
- the gateway RBridge transmits the ARP reply to the TRILL network (operation 712 ).
- an ARP request is disseminated in the TRILL network using multicast and each IP-capable RBridge, including the one elected to respond to ARP requests for the virtual IP address, receives the query.
- the ARP reply is sent as a unicast transmission in the TRILL network to the end device.
- FIG. 7B presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge forwarding a TRILL frame, in accordance with an embodiment of the present invention.
- the RBridge Upon receiving a TRILL frame (operation 752 ), the RBridge checks whether the egress RBridge identifier in the TRILL header of the frame corresponds to a virtual RBridge (operation 754 ). If the identifier does not correspond to the virtual RBridge, the RBridge inspects whether the egress RBridge identifier in the TRILL header of the frame corresponds to the local RBridge. If not, then the TRILL frame is forwarded to the next-hop RBridge based on the egress RBridge identifier (operation 762 ).
- the RBridge removes the TRILL encapsulation and send the frame to a local egress port (operation 764 ). If the RBridge identifier corresponds to the virtual RBridge, the RBridge checks whether the destination MAC address of the Ethernet frame encapsulated in the TRILL frame is the associated virtual MAC address (operation 756 ). If so, then the frame is destined to an IP network the gateway RBridge is coupled to. Hence, the IP packet is extracted from the Ethernet payload of the frame (operation 772 ). The gateway RBridge checks the IP address of the IP packet and performs layer-3 IP forwarding toward the IP network (operation 774 ).
- the virtual RBridge removes the TRILL encapsulation and send the frame to locally connected egress port (operation 764 ).
- Operation of virtual RBridges for multi-homed end devices, such as forwarding multicast frames, is specified in the U.S. Patent Publication No. 2010/0246388, titled “Redundant Host Connection in a Routed Network,” the disclosure of which is incorporated herein in its entirety.
- FIG. 8 illustrates a scenario where one of the RBridges associated with the virtual RBridge experiences a link failure and/or a node failure, in accordance with an embodiment of the present invention.
- RBridges 811 , 812 , and 813 form a virtual RBridge 840
- their respective IP-router portions denoted as IP routers 821 , 822 , and 823 form a virtual IP router 850 .
- Also included are four RBridges 804 , 805 , 806 , and 807 .
- An end device 870 is connected to network 800 using RBridge 804 as the ingress RBridge.
- Virtual IP router 850 is set as a default gateway router for end device 870 .
- gateway RBridges 811 , 812 , and 813 for load balancing.
- Gateway RBridges 811 , 812 , and 813 also provide redundancy among each other to handle failures.
- link 831 is removed from routing decisions in network 800 .
- All frames from end device 870 are still using the virtual MAC address as the destination address, and thus are still forwarded to any of the gateway RBridges via alternative links (e.g., links 832 , 833 , and 834 ).
- IP router 821 is disconnected from network 880 and is incapable of forwarding frames to network 880 .
- IP router 821 is removed from virtual IP router 850 .
- IP router 821 stops operating as a layer-3 gateway router for end device 870 .
- gateway RBridge 811 still remains connected to network 800 and continues to operate as a regular TRILL RBridge.
- virtual IP router 850 still operates as a default gateway for end device 870
- IP routers 822 and 823 can continue to operate as layer-3 gateway routers (as virtual IP router 850 ) for end device 870 .
- all frames from end device 870 to network 880 are then distributed among gateway RBridges 812 and 813 .
- an elected gateway RBridge stops responding to ARP requests for the virtual IP address and notifies other gateway RBridges. Consequently, the other gateway RBridges then elect among themselves another gateway RBridge to respond to ARP requests.
- IP router 821 might not immediately remove its membership from virtual IP router 850 and might continue to receive layer-3 traffic from end devices. Under such circumstances, gateway RBridge 811 , the TRILL counterpart of IP router 821 , forwards the layer-3 traffic with TRILL encapsulation to other gateway RBridges (e.g., gateway RBridge 812 ) which, in turn, forward the traffic to network 880 . However, if all similar IP routers suffer link failures and lose their connection to network 880 , IP router 821 along with the other gateway RBridges with link failures are removed from virtual IP router 850 . However, all gateway RBridges continue operating as TRILL RBridges.
- gateway RBridge 811 (and essentially IP router 821 as they are the same physical device).
- links 831 , 833 , 835 , and 836 fail as well. Consequently, gateway RBridge 811 and IP router 821 are disconnected from both network 800 and network 880 , and are incapable of transmitting to or receiving from either network.
- IP router 821 is removed from virtual IP router 850 and gateway RBridge 811 is removed from virtual RBridge 840 .
- IP router 821 stops operating as a layer-3 gateway node.
- gateway RBridge 811 is disconnected from network 800 and removed from all TRILL routes in network 800 .
- FIG. 9 illustrates an exemplary architecture of a switch with IP processing capabilities, in accordance with an embodiment of the present invention.
- an RBridge 900 includes a number of TRILL ports 904 , a TRILL management and forwarding module 920 , an IP management module 930 , an Ethernet frame processor 910 , and a storage 950 .
- TRILL management and forwarding module 920 further includes a TRILL header processing module 922 .
- IP management module 930 further includes an ARP module 934 and an IP header processing module 936 .
- TRILL ports 904 include inter-switch communication channels for communication with one or more RBridges.
- This inter-switch communication channel can be implemented via a regular communication port and based on any open or proprietary format. Furthermore, the inter-switch communication between RBridges is not required to be direct port-to-port communication.
- TRILL ports 904 receive TRILL frames from (and transmit frames to) other RBridges.
- TRILL header processing module 922 processes TRILL header information of the received frames and performs routing on the received frames based on their TRILL headers, as described in conjunction with FIG. 4B .
- TRILL management and forwarding module 920 forwards frames in the TRILL network toward other RBridges and frames destined to a layer-3 node toward the IP management module 930 .
- IP header processing module 936 forwards frames across VLANs.
- RBridge 900 may form a virtual RBridge and a virtual IP address, wherein TRILL management and forwarding module 920 further includes a virtual RBridge configuration module 924 , and IP management module 930 further includes a virtual IP router configuration module 938 .
- TRILL header processing module 922 generates the TRILL header and outer Ethernet header for ingress frames corresponding to the virtual RBridge.
- Virtual RBridge configuration module 924 manages the communication with gateway RBridges and handles various inter-switch communications, such as link and node failure notifications.
- Virtual RBridge configuration module 924 allows a user to configure and assign the identifier for the virtual RBridges, and decides whether a frame has to be promoted to layer-3, as described in conjunction with FIG. 7B .
- virtual IP router configuration module 938 handles various inter-switch communications, such as layer-3 link failure notifications.
- Virtual IP router configuration module 938 allows a user to configure and assign virtual IP addresses and a virtual MAC address.
- ARP module 934 is responsible for ARP request replies, as described in conjunction with FIG. 4B .
- ARP module 934 also maintains mappings between a virtual MAC address and a virtual IP address and stores the mappings in Storage 950 .
- Storage 950 also includes TRILL and IP routing information.
- gateway RBridge 900 may include a number of edge ports 902 , as described in conjunction with FIG. 1 .
- Edge ports 902 receive frames from (and transmit frames to) end devices.
- Ethernet frame processor 910 extracts and processes header information from the received frames.
- Ethernet frame processor 910 forwards the frames to IP management module 930 if there is no other intermediate RBridge between the end device and RBridge 900 .
- gateway RBridge 900 may include a VCS configuration module 944 that includes a virtual switch management module 940 and a logical switch 942 as described in conjunction with FIG. 1 .
- VCS configuration module 944 maintains a configuration database in storage 950 that maintains the configuration state of every switch within the VCS.
- Virtual switch management module 940 maintains the state of logical switch 942 , which is used to join other VCS switches.
- logical switch 942 can be configured to operate in conjunction with Ethernet frame processor 910 as a logical Ethernet switch.
- modules can be implemented in hardware as well as in software.
- these modules can be embodied in computer-executable instructions stored in a memory which is coupled to one or more processors in gateway RBridge 900 . When executed, these instructions cause the processor(s) to perform the aforementioned functions.
- embodiments of the present invention provide a switch, a method and a system for providing layer-3 support in a TRILL network.
- the switch includes an IP header processor and a forwarding mechanism.
- the IP header processor identifies a destination IP address in a packet encapsulated with an inner Ethernet header, a TRILL header, and an outer Ethernet header.
- the forwarding mechanism determines an output port and constructs a new header for the packet based on the destination IP address.
- the switch also includes a packet processor which determines whether (1) an inner destination media access control (MAC) address corresponds to a local MAC address assigned to the switch; (2) a destination RBridge identifier corresponds to a local RBridge identifier assigned to the switch; and (3) an outer destination MAC address corresponds to the local MAC address.
- MAC media access control
- the methods and processes described herein can be embodied as code and/or data, which can be stored in a computer-readable non-transitory storage medium.
- a computer system reads and executes the code and/or data stored on the computer-readable non-transitory storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the medium.
- the methods and processes described herein can be executed by and/or included in hardware modules or apparatus.
- These modules or apparatus may include, but are not limited to, an application-specific integrated circuit (ASIC) chip, a field-programmable gate array (FPGA), a dedicated or shared processor that executes a particular software module or a piece of code at a particular time, and/or other programmable-logic devices now known or later developed.
- ASIC application-specific integrated circuit
- FPGA field-programmable gate array
- a dedicated or shared processor that executes a particular software module or a piece of code at a particular time
- other programmable-logic devices now known or later developed.
Abstract
Description
- This application claims the benefit of U.S. Provisional Application No. 61/481,643, Attorney Docket Number BRCD-3093.0.1.US.PSP, titled “Layer-3 Support in Virtual Cluster Switching,” by inventors Phanidhar Koganti, Anoop Ghanwani, Suresh Vobbilisetty, Rajiv Krishnamurthy, Nagarajan Venkatesan, and Shunjia Yu, filed 2 May 2011, and U.S. Provisional Application No. 61/503,265, Attorney Docket Number BRCD-3093.0.2.US.PSP, titled “IP Routing in VCS,” by inventors Phanidhar Koganti, Anoop Ghanwani, Suresh Vobbilisetty, Rajiv Krishnamurthy, Nagarajan Venkatesan, and Shunjia Yu, filed 30 Jun. 2011, which are incorporated by reference herein.
- The present disclosure is related to U.S. patent application Ser. No. 13/087,239, (attorney docket number BRCD-3008.1.US.NP), titled “Virtual Cluster Switching,” by inventors Suresh Vobbilisetty and Dilip Chatwani, filed 14 Apr. 2011, and U.S. patent application Ser. No. 12/725,249, (attorney docket number BRCD-112-0439US), titled “Redundant Host Connection in a Routed Network,” by inventors Somesh Gupta, Anoop Ghawani, Phanidhar Koganti, and Shunjia Yu, filed 16 Mar. 2010, the disclosures of which are incorporated by reference herein.
- 1. Field
- The present disclosure relates to network design. More specifically, the present disclosure relates to a method and system for constructing a scalable switching system that supports layer-3 routing while facilitating automatic configuration.
- 2. Related Art
- The growth of the Internet has brought with it an increasing demand for bandwidth. As a result, equipment vendors race to build larger and faster switches with versatile capabilities, such as layer-3 forwarding, to move more traffic efficiently. However, the size of a switch cannot grow infinitely. It is limited by physical space, power consumption, and design complexity, to name a few factors. Furthermore, switches with higher capability are usually more complex and expensive. More importantly, because an overly large and complex system often does not provide economy of scale, simply increasing the size and capability of a switch may prove economically unviable due to the increased per-port cost.
- One way to increase the throughput of a switch system is to use switch stacking. In switch stacking, multiple smaller-scale, identical switches are interconnected in a special pattern to form a larger logical switch. The amount of required manual configuration and topological limitations for switch stacking becomes prohibitively tedious when the stack reaches a certain size, which precludes switch stacking from being a practical option in building a large-scale switching system.
- Meanwhile, layer-2 (e.g., Ethernet) switching technologies continue to evolve. More routing-like functionalities, which have traditionally been the characteristics of layer-3 (e.g., Internet Protocol or IP) networks, are migrating into layer-2. Notably, the recent development of the Transparent Interconnection of Lots of Links (TRILL) protocol allows Ethernet switches to function more like routing devices. TRILL overcomes the inherent inefficiency of the conventional spanning tree protocol, which forces layer-2 switches to be coupled in a logical spanning-tree topology to avoid looping. TRILL allows routing bridges (RBridges) to be coupled in an arbitrary topology without the risk of looping by implementing routing functions in switches and including a hop count in the TRILL header.
- While TRILL brings many desirable features to layer-2 networks, some issues remain unsolved when layer-3 processing is desired.
- One embodiment of the present invention provides a switch. The switch includes an IP header processor and a forwarding mechanism. The IP header processor identifies a destination IP address in a packet encapsulated with an inner Ethernet header, a TRILL header, and an outer Ethernet header. The forwarding mechanism determines an output port and constructs a new header for the packet based on the destination IP address. The switch also includes a packet processor which determines whether (1) an inner destination media access control (MAC) address corresponds to a local MAC address assigned to the switch; (2) a destination RBridge identifier (RBridge ID) corresponds to a local RBridge identifier assigned to the switch; and (3) an outer destination MAC address corresponds to the local MAC address.
- In a variation on this embodiment, the packet processor determines a first virtual local area network (VLAN) tag in the inner Ethernet header, wherein the new header includes a new inner Ethernet header which comprises a second VLAN tag.
- In a variation on this embodiment, the switch includes a control mechanism which forms a virtual cluster switch in conjunction with one or more additional switches.
- In a variation on this embodiment, the virtual cluster switch is an Ethernet fabric switch functioning as a logical Ethernet switch.
- In a variation on this embodiment, the switch includes a switching mechanism switches the packet between VLANs based on the destination IP address.
- In a variation on this embodiment, the RBridge identifier is a virtual RBridge identifier and the destination IP address is a virtual IP address assigned to a virtual IP router associated with the virtual RBridge identifier.
- In a variation on this embodiment, the virtual IP router is formed by operating the switch in conjunction with at least another physical switch as a single logical router.
-
FIG. 1 illustrates an exemplary TRILL network that includes a plurality of RBridges with IP processing capabilities, in accordance with an embodiment of the present invention. -
FIG. 2A illustrates an exemplary configuration of end devices belonging to different VLANs and coupled to a TRILL network, wherein one RBridge is IP capable, in accordance with an embodiment of the present invention. -
FIG. 2B illustrates an exemplary configuration of end devices belonging to different VLANs and coupled to a TRILL network, wherein all RBridges are IP capable, in accordance with an embodiment of the present invention. -
FIG. 3A illustrates an exemplary TRILL network with multiple VLANs, in accordance with an embodiment of the present invention. -
FIG. 3B illustrates an exemplary TRILL network with multiple VLANs, wherein each RBridge belongs to all VLANs, in accordance with an embodiment of the present invention. -
FIG. 4A presents a flowchart illustrating the process of an RBridge transmitting a frame, in accordance with an embodiment of the present invention. -
FIG. 4B presents a flowchart illustrating the process of an IP-capable RBridge transmitting a frame, in accordance with an embodiment of the present invention. -
FIG. 5 illustrates an exemplary network where a virtual RBridge and an associated virtual IP router are created based on a plurality of physical gateway RBridges with IP processing capabilities, in accordance with an embodiment of the present invention. -
FIG. 6A illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to a number of gateway RBridges in a TRILL network, in accordance with an embodiment of the present invention. -
FIG. 6B illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to all RBridges in a TRILL network where each RBridge has IP processing capability, in accordance with an embodiment of the present invention. -
FIG. 7A presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge responding to an Address Resolution Protocol (ARP) query, in accordance with an embodiment of the present invention. -
FIG. 7B presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge forwarding a TRILL frame, in accordance with an embodiment of the present invention. -
FIG. 8 illustrates a scenario where one of the RBridges associated with the virtual RBridge experiences a link failure and/or a node failure, in accordance with an embodiment of the present invention. -
FIG. 9 illustrates an exemplary architecture of a switch with IP processing capabilities, in accordance with an embodiment of the present invention. - The following description is presented to enable any person skilled in the art to make and use the invention, and is provided in the context of a particular application and its requirements. Various modifications to the disclosed embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments and applications without departing from the spirit and scope of the present invention. Thus, the present invention is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the claims.
- In embodiments of the present invention, the problem of providing scalable and flexible layer-3 (e.g., IP) support in a TRILL network is solved by facilitating IP routing in a number of RBridges in the TRILL network. The availability of IP processing within a TRILL network allows cross-layer-2-domain traffic (e.g., traffic across different VLANs) to be forwarded within a TRILL network, which reduces forwarding overhead. Usually, the IP router portion of one of these IP-capable RBridges is assigned as a default gateway router to an end device coupled to a TRILL network. Wherever the end device sends a frame to outside of its local network (e.g., a VLAN), the frame is forwarded to and processed by the IP router portion of the RBridge. This layer-3 processing occurs within the TRILL network. Note that, in a conventional TRILL network, such layer-3 processing has to be done by an IP router residing outside the TRILL network.
- In some embodiments, the end-device may be coupled to the TRILL network via an ingress RBridge without IP processing capability. Under such a scenario, the TRILL RBridge portion of an IP-capable RBridge acts as an egress RBridge and the IP router portion of the RBridge can act as the default gateway router. A frame from the end device is received at the ingress RBridge and encapsulated in a TRILL packet, wherein the TRILL packet sets the egress RBridge identifier as the destination RBridge identifier, and the MAC address of the egress RBridge as the inner destination MAC address. The packet is then forwarded though the TRILL network and reaches the egress RBridge, where the outer destination MAC address of the packet is the MAC address of the egress RBridge. The IP router portion of the egress RBridge then processes the IP header in the frame and makes the layer-3 forwarding decision based on the destination IP address of the frame.
- In some embodiments, the IP router portion of an IP-capable RBridge may be associated with multiple VLANs associated with the TRILL network. If the destination end device of the frame belongs to one of the associated VLANs, the IP router can obtain the MAC address of the destination end device using ARP requests within that VLAN. The corresponding RBridge of the IP router then sets the RBridge to which the destination end device is coupled as the egress RBridge and forwards the frame to the egress RBridge over the TRILL network.
- Although the present disclosure is presented using examples based on the TRILL protocol, embodiments of the present invention are not limited to TRILL networks, or networks defined in a particular Open System Interconnection Reference Model (OSI reference model) layer.
- The term “RBridge” refers to routing bridges, which are bridges implementing the TRILL protocol as described in IETF Request for Comments (RFC) “Routing Bridges (RBridges): Base Protocol Specification,” available at http://tools.ietf.org/html/rfc6325, which is incorporated by reference herein. Embodiments of the present invention are not limited to applications among RBridges. Other types of switches, routers, and forwarders can also be used.
- In this disclosure, the term “edge port” refers to a port which sends/receives data frames in native Ethernet format. The term “TRILL port” refers to a port which sends/receives data frames encapsulated with a TRILL header and outer MAC header.
- The term “end device” refers to a network device that is typically not TRILL-capable. “End device” is a relative term with respect to the TRILL network. However, “end device” does not necessarily mean that the network device is an end host. An end device can be a host, a conventional layer-2 switch, or any other type of network device. Additionally, an end device can be coupled to other switches or hosts further away from the TRILL network. In other words, an end device can be an aggregation point for a number of network devices to enter the TRILL network.
- The term “IP-capable RBridge” refers to a physical RBridge that can process and route IP packets. An IP-capable RBridge can be coupled to a layer-3 network and can forward IP packets from end devices to the layer-3 network. A number of IP-capable RBridges can form a virtual RBridge and a corresponding virtual IP router, thereby facilitating a virtual gateway router for end devices that supports redundancy and load-balancing. In this disclosure, an RBridge which forms a virtual RBridge and a virtual IP router is also referred to as a “gateway” RBridge. A gateway RBridge responds to ARP requests for the virtual IP address with a virtual MAC address. In various embodiments, any arbitrary number of gateway RBridges can form the virtual RBridge. As gateway RBridges can process both TRILL and IP packets, in this disclosure the term “gateway RBridge” can refer to a physical RBridge in a TRILL network or a physical router in an IP network.
- The term “IP router” refers to the IP-capable portion of an RBridge or a stand-alone IP router. In this disclosure, the terms “IP router” and “router” are used interchangeably.
- The term “frame” refers to a group of bits that can be transported together across a network. “Frame” should not be interpreted as limiting embodiments of the present invention to layer-2 networks. “Frame” can be replaced by other terminologies referring to a group of bits, such as “packet,” “cell,” or “datagram.”
- The term “RBridge identifier” refers to a group of bits that can be used to identify an RBridge. Note that the TRILL standard uses “RBridge ID” to denote a 48-bit intermediate-system-to-intermediate-system (IS-IS) System ID assigned to an RBridge, and “RBridge nickname” to denote a 16-bit value that serves as an abbreviation for the “RBridge ID.” In this disclosure, “RBridge identifier” is used as a generic term and is not limited to any bit format, and can refer to “RBridge ID” or “RBridge nickname” or any other format that can identify an RBridge.
-
FIG. 1 illustrates an exemplary TRILL network that includes a plurality of RBridges with IP processing capabilities, in accordance with an embodiment of the present invention. As illustrated inFIG. 1 , aTRILL network 100 includes RBridges, 101, 102, 103, 104, 105, 106, and 107.RBridges network 150 as IP routers, 111, 112, and 113, respectively. For example,RBridge 101 andIP router 111 are the same physical device (represented by dotted lines), where its TRILL RBridge portion is denoted byRBridges 101 and its IP router portion is denoted byrouter 111. Similarly,RBridge 102 andIP router 112, andRBridge 103 andIP router 113, are the same physical devices, respectively. - RBridges in
network 100 use edge ports to communicate to end devices and TRILL ports to communicate to other RBridges. For example,RBridge 104 is coupled to enddevice 122 via an edge port and toRBridges end devices end devices network 100, and enddevices network 100 via their aggregation node, a layer-2bridge 130. - In
FIG. 1 ,end device 128 is directly coupled toRBridge 103. Hence,IP router 113 can act as the default gateway forend device 128. Consequently, all frames fromend device 128 destined toIP network 150 are received atIP router 113 and forwarded tonetwork 150. On the other hand,RBridge 104 couples enddevice 122 to network 100 and acts as the ingress RBridge for all frames fromend device 122. One of the IP-capable RBridges (e.g., RBridge 101) acts as the egress RBridge for frames fromend device 122 tonetwork 150. Under such a scenario, the frame destined to network 150 is encapsulated in a TRILL packet with the RBridge identifier ofRBridge 101 as the destination RBridge identifier, and the MAC address ofRBridge 101 as the inner destination MAC address. The TRILL packet is then forwarded toRBridge 101, where the outer destination MAC address of the packet is the MAC address ofRBridge 101.IP router 111 then processes the IP header in the frame and makes the layer-3 forwarding decision based on the destination IP address of the frame. - During operation that does not involve layer-3 processing in RBridges, an end device coupled to the TRILL network may select the default gateway from a layer-3 network and use the corresponding IP address as a default gateway router address. For example, in
FIG. 1 ,end device 128 selects the default gateway router fromIP network 150. Any frame destined to network 150 fromend device 128 is sent to the default gateway. Under such a scenario, ifend devices network 150. Ifend device 128 sends a frame to enddevice 122, the frame first goes to the default gateway innetwork 150. Consequently, the default gateway processes the IP header in the frame and makes layer-3 forwarding decision towardend device 122. As a result, routing and bandwidth management will be inefficient and the frame will incur higher latency. - In embodiments of the present invention, as illustrated in
FIG. 1 , each frame destined to enddevice 122 fromend device 128, wherein the end devices are on different VLANs, is received atRBridge 103.IP router 113 processes the IP header in the frame and makes the forwarding decision toward end device 122 (which involves forwarding the frame onend device 122's VLAN through TRILL network 100). Consequently,RBridge 103 forwards the frame to acorresponding egress RBridge 104 overTRILL network 100.RBridge 104, in turn, transmits the frame to enddevice 122. Hence, enabling layer-3 support on RBridges in a TRILL network provides higher efficiency in routing and bandwidth management. - In some embodiments, the TRILL network may be a virtual cluster switch (VCS). In a VCS, any number of RBridges in any arbitrary topology may logically operate as a single switch. Any new RBridge may join or leave the VCS in “plug-and-play” mode without any manual configuration.
- Note that TRILL is only used as a transport between the switches within
network 100. This is because TRILL can readily accommodate native Ethernet frames. Also, the TRILL standards provide a ready-to-use forwarding mechanism that can be used in any routed network with arbitrary topology. Embodiments of the present invention should not be limited to using only TRILL as the transport. Other protocols (such as multi-protocol label switching (MPLS)), either public or proprietary, can also be used for the transport. -
FIG. 2A illustrates an exemplary configuration of how end devices belonging to different VLANs and coupled to a TRILL network, wherein one RBridge is IP capable, in accordance with an embodiment of the present invention. In this example, aTRILL network 200 includesTRILL RBridges End device 202 is coupled toRBridge 220 overVLAN 212, andend device 204 is coupled toRBridge 220 overVLAN 214. - In the example in
FIG. 2A ,RBridge 230 is IP capable andIP router 235 is the IP router portion of RBridge 230 (denoted in dotted line).IP router 235 functions as a default gateway router forend devices RBridge 220 couples bothend devices network 200, any traffic betweenend devices IP router 235 becauseend devices end device 202 sends a frame to enddevice 204, it first assembles an IP packet withend device 204's IP address. Based on its local forwarding table,end device 202 realizes that it does not have a direct route to enddevice 204, and therefore needs to send the packet togateway router 235. Hence,end device 202 encapsulates the IP packet in an Ethernet frame, whose destination MAC address is set to begateway router 235's MAC address. Note that, ifend device 202 has no knowledge ofIP router 235's MAC address,end device 202 can send out an ARP request corresponding to the IP address ofrouter 235.Router 235 then replies to the ARP request with its MAC address. Subsequently,end device 202 forwards the frame toRBridge 230 viaingress RBridge 220.IP router 235, in turn, receives the frame and removes its leayer-2 header (including the VLAN tag corresponding to VLAN 212).IP router 235 then performs a lookup in its IP forwarding table based on the packet's destination IP address, and encapsulates the packet with a new Ethernet header which includes a VLANtag corresponding VLAN 214.RBridge 230 then encapsulates the Ethernet frame with a TRILL header and forwards it to enddevice 204 viaegress RBridge 220. -
FIG. 2B illustrates an exemplary configuration of end devices belonging to different VLANs and coupled to a TRILL network, wherein all RBridges are IP capable, in accordance with an embodiment of the present invention. In this example, aTRILL network 200 includesTRILL RBridges End device 202 is coupled toRBridge 220 overVLAN 212, andend device 204 is coupled toRBridge 220 overVLAN 214. - In the example in
FIG. 2B , bothRBridges IP routers RBridges IP router 225 can be the default gateway router forend devices end devices IP router 225. For example, ifend device 202 sends a frame to enddevice 204, it assembles an IP packet withend device 204's IP address, encapsulates the IP packet in an Ethernet frame with destination MAC address asrouter 225's MAC address, and forwards the frame toRBridge 225 viaingress RBridge 220. Note that, ifend device 202 has no knowledge ofIP router 225's MAC address,end device 202 obtains the IP address ofrouter 225 using ARP.IP router 225, in turn, receives the frame, performs a lookup in its IP forwarding table, encapsulates the packet with a new Ethernet header which includes a VLANtag corresponding VLAN 214, and forwards it to enddevice 204 viaegress RBridge 220. As the cross-layer-2-domain frame does not need to traverse throughTRILL network 200, IP-processing capability atRBridge 220 thereby reduces the bandwidth usage innetwork 200. - In some embodiments, layer-3 processing capabilities can be distributed to multiple or all TRILL RBridges. In some embodiments, layer-3 processing capabilities associated different the VLANs can be distributed selectively across multiple RBridges.
FIG. 3A illustrates an exemplary TRILL network with multiple VLANs, in accordance with an embodiment of the present invention. In the example inFIG. 3A ,network 300 includesRBridges RBridge 304 is coupled to enddevices RBridge 305 is coupled to enddevices RBridge 306 is coupled to enddevices RBridge 307 is coupled to enddevices RBridges VLAN 328;RBridges devices VLAN 326;RBridges end device 311 belong toVLAN 324; andRBridges end device 317 belong toVLAN 322. - In some embodiments, a layer-3 interface on an RBridge corresponding to a VLAN is a Switch Virtual Interface (SVI). For example,
RBridge 304 inFIG. 3A has SVIs forVLANs 324 and 326 (although these SVIs can be on the same physical interface). Consequently,RBridge 304 andend device 318, andRBridge 304 andend device 311, are on the same VLAN segment. Ifend device 311 sends a frame to enddevice 318, the destination is outside ofVLAN 324. Consequently,end device 318 sets the destination MAC address of the frame as the MAC address of the SVI onVLAN 324 atRBridge 304, which is the layer-3 gateway onVLAN 324.End device 318 then forwards the frame toRBridge 304. Upon receiving the frame,RBridge 304 recognizes that the frame's destination MAC address is a local MAC address.RBridge 304 then removes the frame's Ethernet header, performs a lookup in its IP forwarding table based on the frame's destination IP address, and encapsulates the frame with a new Ethernet header with a destination MAC address corresponding to enddevice 318 inVLAN 326. Finally,RBridge 304 forwards the frame to enddevice 318 viaegress RBridge 307. - However, when
end device 311 sends a frame to enddevice 317,RBridge 304 cannot forward the frame to enddevice 317 becauseRBridge 304 does not have an SVI onVLAN 322, to whichend device 317 belongs. As a result, upon receiving a frame destined to enddevice 317 fromend device 311, RBridge encapsulates the frame using a TRILL header with egress RBridge identifier corresponding toRBridge 306 because it has SVIs to all VLANs.RBridge 304 then forwards the frame toRBridge 306. The frame is routed though the TRILL network and reachesRBridge 306 when the outer destination MAC addresses match the MAC address ofRBridge 306. Upon receiving the frame,RBridge 306 recognizes that the frame's outer destination MAC address is a local MAC address.RBridge 306 then removes the TRILL encapsulations, encapsulates the IP packet with a new Ethernet header with a destination MAC address corresponding to enddevice 317 inVLAN 322, and forwards the frame accordingly. -
FIG. 3B illustrates an exemplary TRILL network with multiple VLANs, wherein each RBridge belongs to all VLANs, in accordance with an embodiment of the present invention. In this example,TRILL network 300 includesRBridges End device 312 is coupled toRBridges end device 317 is coupled toRBridges end device 318 is coupled toRBridge 307. All RBridges innetwork 300 have SVIs forVLANs End devices VLAN 322, andend device 317 belongs toVLAN 326. - In this example, if
end device 317 sends a frame to enddevice 318, the frame can be routed on layer-3 atRBridge 307 becauseRBridge 307 has SVIs forVLANs network 300, it incurs lower latency while saving bandwidth innetwork 300. Similarly, ifend device 317 sends a frame to enddevice 312, the frame can be routed on layer-3 at the IP router portion of eitherRBridge VLANs -
FIG. 4A presents a flowchart illustrating the process of an RBridge transmitting a frame, in accordance with an embodiment of the present invention. During operation, an RBridge receives a frame (operation 402) and determines the type of port at which the frame was received (operation 404). If the frame is received at an edge port, then the RBridge checks whether the destination is coupled to a local edge port (operation 410). If the destination is not coupled to a local edge port, the RBridge encapsulates the frame in a TRILL packet and sets the RBridge identifier of the RBridge to which the end device is coupled as the egress RBridge identifier (operation 416). The RBridge then forwards the TRILL packet to the TRILL network (operation 418). Note that the MAC learning process allows an RBridge to learn about the port to which the end device is coupled. - If the frame is received on an edge port and the destination is coupled to a local edge port (operation 410), then the RBridge transmits the frame to the destination end device coupled to a local edge port (operation 414).
- If the frame is received from a TRILL port (operation 404), the RBridge checks whether itself is the egress RBridge of the TRILL packet (operation 408). If not, then the RBridge forwards the TRILL packet to the TRILL network (operation 418). Otherwise, the RBridge transmits the frame to the destination end device coupled to a local edge port (operation 414).
-
FIG. 4B presents a flowchart illustrating the process of an IP-capable RBridge transmitting a frame, in accordance with an embodiment of the present invention. The exemplary process inFIG. 4B is also applicable to embodiments with distributed layer-3 processing, as described in conjunction withFIG. 3A . During operation, an RBridge receives a frame (operation 452) and determines the type of port at which the frame is received (operation 454). If the frame is received at an edge port, then the RBridge inspects the frame to determine whether the end device with the destination MAC address is coupled to a local edge port (operation 456). If so, the frame is forwarded to the destination via the TRILL network (operation 464), as described in conjunction withFIG. 4A . - If the frame's destination MAC address is not coupled to a local edge port, then the RBridge determines whether the frame's destination MAC address is the RBridge's MAC address (operation 458). If the destination MAC address is not the RBridge's MAC address, then the RBridge encapsulates the frame in a TRILL packet and sets the RBridge identifier of a gateway RBridge as the egress RBridge identifier (operation 466). The RBridge then forwards the TRILL packet to the TRILL network (operation 476). On the other hand, if the frame's destination MAC address is the RBridge's MAC address (operation 458), then the RBridge performs layer-3 processing on the frame (operation 468) and determines the outgoing port (operation 470).
- The RBridge then determines the type of the outgoing port (operation 462). If the outgoing port is an edge port, which means the destination end device is coupled locally, the RBridge forwards the frame, which is Ethernet encapsulated with the end device's MAC address as the destination MAC address, to the destination end device (operation 480). In some embodiments, the end device can be a layer-3 (e.g., IP) router. If the outgoing port is a TRILL port, then the end device is connected to a remote RBridge. Hence, the RBridge obtains the
- RBridge identifier of the RBridge to which the destination end device is coupled to based on the MAC address of the destination end device (operation 472). The RBridge then encapsulates the frame in a TRILL packet and sets the obtained RBridge identifier as the egress RBridge identifier (operation 474). The RBridge then forwards the TRILL packet to the TRILL network (operation 476).
- If the frame is received from a TRILL port (operation 454), the RBridge checks whether itself is the egress RBridge of the TRILL packet (operation 460). If not, then the RBridge forwards the TRILL packet to the TRILL network (operation 476). Otherwise, the RBridge forwards the frame to the destination end device coupled to a local edge port (operation 480). In some embodiments, the end device can be a layer-3 router, in which case the forwarding includes layer-3 processing on the frame.
- In some embodiments, a number of TRILL RBridges with IP processing capabilities may act as layer-3 routers for an end device. These RBridges can form a virtual RBridge, which is assigned with a virtual RBridge identifier. Furthermore, these RBridges form a virtual IP router, which is assigned with a virtual IP address and a corresponding virtual MAC address. This virtual IP router operates as a default gateway router, which can provide redundancy and load balancing.
-
FIG. 5 illustrates an exemplary network where a virtual RBridge and an associated virtual IP router are created based on a plurality of physical gateway RBridges with IP processing capabilities, in accordance with an embodiment of the present invention. As illustrated inFIG. 5 , aTRILL network 500 includesRBridges RBridges network 150 asIP routers IP router 521 are same physical device (represented by dotted lines), where its TRILL RBridge portion is denoted by gateway RBridge 511 and its IP router portion is denoted byIP router 521. Similarly,gateway RBridge 512 andIP router 522, andgateway RBridge 513 andIP router 523 are the same physical devices, respectively. -
Gateway RBridges virtual RBridge 530 by operating as a single logical RBridge inTRILL network 500. Similarly, the correspondingIP routers virtual IP router 540 by operating as a single logical IP router. Anend device 562 coupled tonetwork 500 throughRBridge 507 can usevirtual IP router 540 as the default gateway router to layer-3network 550. - In embodiments of the present invention, as illustrated in
FIG. 1 ,Virtual RBridge 530 is considered to be logically coupled togateway RBridges gateway RBridges virtual RBridge 530. As a result, other RBridges in the TRILL network can learn thatvirtual RBridge 530 is reachable viagateway RBridges virtual RBridge 530 using a corresponding virtual RBridge identifier through these gateway RBridges. - All the IP-layer router portions of these gateway RBridges are configured to operate as the layer-3 gateway router (i.e., virtual IP router 540) for
end device 562.End device 562 usesvirtual IP router 540 as the default gateway. Becausevirtual RBridge 530 is associated withvirtual IP router 540, incoming frames fromend device 562 destined to network 550 are marked withvirtual RBridge 530's identifier as the egress RBridge identifier. Consequently, all frames fromend device 562 to network 550 are delivered to one of thegateway RBridges gateway RBridges virtual RBridge 530. -
FIG. 6A illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to a number of gateway RBridges in a TRILL network, in accordance with an embodiment of the present invention. In this example, aTRILL network 600 includes a number ofTRILL RBridges Network 600 also includesRBridges RBridges end devices network 600 are in communication with each other using TRILL protocol. - Also included in
network 600 areRBridges IP network 680.Gateway RBridges virtual RBridge 640 with avirtual RBridge identifier 645. Physicallyco-located IP Routers gateway RBridges virtual IP router 670 which is assigned avirtual IP address 660 and avirtual MAC address 650.Virtual IP address 660 maps tovirtual MAC address 650 for ARP requests directed tovirtual IP router 670. Furthermore,virtual RBridge identifier 645 is associated withvirtual MAC address 650.End devices virtual IP address 660 as their default gateway router address and use ARP to obtainvirtual MAC address 650.End devices virtual MAC address 650 as the destination address intonetwork 600. The frames are encapsulated in TRILL packets and routed towardvirtual RBridge 640 using the correspondingvirtual RBridge identifier 645. - In some embodiments, a virtual IP address can be assigned for each VLAN associated with a TRILL network. For example, in
FIG. 6A ,end device 652 may belong toVLAN 692, andend device 654 may belong toVLAN 694. Different virtual IP addresses may be used forVLANs End devices VLAN 692 andVLAN 694 as their respective default gateway router addresses. Consequently,end devices virtual IP router 670 to be inVLAN 692 andVLAN 694, respectively. For ARP requests for either virtual IP address, the samevirtual MAC address 650 is sent in reply. All data frames injected toTRILL network 600 withvirtual MAC address 650 as the destination MAC address are routed towardvirtual RBridge 640. - Note that in one embodiment, the virtual MAC address is known to all RBridges in the
network 600. Otherwise, bothIP routers virtual MAC address 650 and results in packet duplication. Hence, after formation ofvirtual RBridge 640 andvirtual IP router 670, all RBridges innetwork 600 are provided with the knowledge aboutvirtual MAC address 650. That is,virtual MAC address 650 is always “known” to all ingress RBridges innetwork 600, and frames destined tovirtual MAC address 650 are routed throughnetwork 600 using TRILL unicast. - In some embodiments, only one gateway RBridge is elected to reply to ARP requests for the virtual IP address. This election can also be VLAN specific.
-
FIG. 6B illustrates an exemplary configuration of how a virtual RBridge and an associated virtual IP router can be logically coupled to all RBridges in a TRILL network where each RBridge has IP processing capability, in accordance with an embodiment of the present invention. In this example, all RBridges inTRILL network 600 have IP processing capabilities. Even though only RBridges 622 and 624 are connected to an IP network, IP processing capacity at all RBridges enables them to route across VLANs, as described in conjunction withFIG. 3B . For example, any traffic betweenVLANs RBridges network 600. - In some embodiments, all RBridges in
network 600 are associated withvirtual RBridge 640 and avirtual IP router 670, and share avirtual RBridge identifier 645, avirtual IP address 660, and avirtual MAC address 650. In some embodiments, all RBridges innetwork 600 may be connected toIP network 680. -
FIG. 7A presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge responding to an Address Resolution Protocol (ARP) query, in accordance with an embodiment of the present invention. Upon receiving an ARP request packet for an IP address (operation 702), the gateway RBridge checks whether the ARP request is for a virtual IP address (operation 704). If not, the gateway RBridge responds based on the IP address in the ARP request (assuming that IP address is the gateway RBridge's physical IP address) (operation 720). Otherwise, the gateway RBridge checks whether it is elected to respond to an ARP request for the virtual IP address (operation 706). If not, the ARP request is discarded. Otherwise the gateway RBridge retrieves the virtual MAC address for the virtual IP address (operation 708) and generates an ARP reply containing the virtual MAC address (operation 710). The gateway RBridge transmits the ARP reply to the TRILL network (operation 712). Note that an ARP request is disseminated in the TRILL network using multicast and each IP-capable RBridge, including the one elected to respond to ARP requests for the virtual IP address, receives the query. However, the ARP reply is sent as a unicast transmission in the TRILL network to the end device. -
FIG. 7B presents a flowchart illustrating the process of a gateway RBridge associated with a virtual RBridge forwarding a TRILL frame, in accordance with an embodiment of the present invention. Upon receiving a TRILL frame (operation 752), the RBridge checks whether the egress RBridge identifier in the TRILL header of the frame corresponds to a virtual RBridge (operation 754). If the identifier does not correspond to the virtual RBridge, the RBridge inspects whether the egress RBridge identifier in the TRILL header of the frame corresponds to the local RBridge. If not, then the TRILL frame is forwarded to the next-hop RBridge based on the egress RBridge identifier (operation 762). Otherwise, the RBridge removes the TRILL encapsulation and send the frame to a local egress port (operation 764). If the RBridge identifier corresponds to the virtual RBridge, the RBridge checks whether the destination MAC address of the Ethernet frame encapsulated in the TRILL frame is the associated virtual MAC address (operation 756). If so, then the frame is destined to an IP network the gateway RBridge is coupled to. Hence, the IP packet is extracted from the Ethernet payload of the frame (operation 772). The gateway RBridge checks the IP address of the IP packet and performs layer-3 IP forwarding toward the IP network (operation 774). On the other hand, if the destination MAC address is not the virtual MAC address, then the virtual RBridge is for multi-homed layer-2 end devices. Accordingly, the RBridge removes the TRILL encapsulation and send the frame to locally connected egress port (operation 764). Operation of virtual RBridges for multi-homed end devices, such as forwarding multicast frames, is specified in the U.S. Patent Publication No. 2010/0246388, titled “Redundant Host Connection in a Routed Network,” the disclosure of which is incorporated herein in its entirety. -
FIG. 8 illustrates a scenario where one of the RBridges associated with the virtual RBridge experiences a link failure and/or a node failure, in accordance with an embodiment of the present invention. In this example, in aTRILL network 800,RBridges virtual RBridge 840, and their respective IP-router portions denoted asIP routers virtual IP router 850. Also included are fourRBridges end device 870 is connected to network 800 usingRBridge 804 as the ingress RBridge.Virtual IP router 850 is set as a default gateway router forend device 870. Hence, all frames destined to network 880 fromend device 870 have the virtual MAC address assigned tovirtual IP router 850 as the destination MAC address. Note that these frames can be forwarded bygateway RBridges Gateway RBridges - Suppose that a
failure 864 occurs to link 831 adjacent togateway RBridge 811. As a result, link 831 is removed from routing decisions innetwork 800. All frames fromend device 870 are still using the virtual MAC address as the destination address, and thus are still forwarded to any of the gateway RBridges via alternative links (e.g.,links - Suppose that a
failure 862 occurs during operation that fails link 836 adjacent toIP router 821. Consequently,IP router 821 is disconnected fromnetwork 880 and is incapable of forwarding frames tonetwork 880. Under such a scenario,IP router 821 is removed fromvirtual IP router 850. As a result,IP router 821 stops operating as a layer-3 gateway router forend device 870. However,gateway RBridge 811 still remains connected tonetwork 800 and continues to operate as a regular TRILL RBridge. Asvirtual IP router 850 still operates as a default gateway forend device 870,IP routers end device 870. Hence, all frames fromend device 870 to network 880 are then distributed amonggateway RBridges - In some embodiments, with
failure 862, an elected gateway RBridge stops responding to ARP requests for the virtual IP address and notifies other gateway RBridges. Consequently, the other gateway RBridges then elect among themselves another gateway RBridge to respond to ARP requests. - In some embodiments, with
failure 862,IP router 821 might not immediately remove its membership fromvirtual IP router 850 and might continue to receive layer-3 traffic from end devices. Under such circumstances,gateway RBridge 811, the TRILL counterpart ofIP router 821, forwards the layer-3 traffic with TRILL encapsulation to other gateway RBridges (e.g., gateway RBridge 812) which, in turn, forward the traffic tonetwork 880. However, if all similar IP routers suffer link failures and lose their connection tonetwork 880,IP router 821 along with the other gateway RBridges with link failures are removed fromvirtual IP router 850. However, all gateway RBridges continue operating as TRILL RBridges. - Suppose that a
node failure 866 occurs at gateway RBridge 811 (and essentiallyIP router 821 as they are the same physical device). As a result,links gateway RBridge 811 andIP router 821 are disconnected from bothnetwork 800 andnetwork 880, and are incapable of transmitting to or receiving from either network. Under such a scenario,IP router 821 is removed fromvirtual IP router 850 andgateway RBridge 811 is removed fromvirtual RBridge 840. As a result,IP router 821 stops operating as a layer-3 gateway node. Furthermore,gateway RBridge 811 is disconnected fromnetwork 800 and removed from all TRILL routes innetwork 800. - With
failure 866, asvirtual IP router 850 still operates as a default gateway forend device 870,routers end device 870. Hence, all frames fromend device 870 to network 880 are distributed betweengateway RBridges IP router 821 had been an elected router, it stops responding to ARP requests for the virtual IP address. Other RBridges coupled to the failed gateway RBridge can detect the failure and notify all RBridges, including other active gateway RBridges. Consequently, the active gateway RBridges can elect another gateway RBridge to respond to ARP requests. -
FIG. 9 illustrates an exemplary architecture of a switch with IP processing capabilities, in accordance with an embodiment of the present invention. In this example, anRBridge 900 includes a number ofTRILL ports 904, a TRILL management andforwarding module 920, anIP management module 930, anEthernet frame processor 910, and astorage 950. TRILL management andforwarding module 920 further includes a TRILLheader processing module 922.IP management module 930 further includes anARP module 934 and an IPheader processing module 936. -
TRILL ports 904 include inter-switch communication channels for communication with one or more RBridges. This inter-switch communication channel can be implemented via a regular communication port and based on any open or proprietary format. Furthermore, the inter-switch communication between RBridges is not required to be direct port-to-port communication. - During operation,
TRILL ports 904 receive TRILL frames from (and transmit frames to) other RBridges. TRILLheader processing module 922 processes TRILL header information of the received frames and performs routing on the received frames based on their TRILL headers, as described in conjunction withFIG. 4B . TRILL management andforwarding module 920 forwards frames in the TRILL network toward other RBridges and frames destined to a layer-3 node toward theIP management module 930. IPheader processing module 936 forwards frames across VLANs. - In some embodiments,
RBridge 900 may form a virtual RBridge and a virtual IP address, wherein TRILL management andforwarding module 920 further includes a virtualRBridge configuration module 924, andIP management module 930 further includes a virtual IProuter configuration module 938. TRILLheader processing module 922 generates the TRILL header and outer Ethernet header for ingress frames corresponding to the virtual RBridge. VirtualRBridge configuration module 924 manages the communication with gateway RBridges and handles various inter-switch communications, such as link and node failure notifications. VirtualRBridge configuration module 924 allows a user to configure and assign the identifier for the virtual RBridges, and decides whether a frame has to be promoted to layer-3, as described in conjunction withFIG. 7B . - Furthermore, virtual IP
router configuration module 938 handles various inter-switch communications, such as layer-3 link failure notifications. Virtual IProuter configuration module 938 allows a user to configure and assign virtual IP addresses and a virtual MAC address. -
ARP module 934 is responsible for ARP request replies, as described in conjunction withFIG. 4B .ARP module 934 also maintains mappings between a virtual MAC address and a virtual IP address and stores the mappings inStorage 950.Storage 950 also includes TRILL and IP routing information. - In some embodiments,
gateway RBridge 900 may include a number ofedge ports 902, as described in conjunction withFIG. 1 .Edge ports 902 receive frames from (and transmit frames to) end devices.Ethernet frame processor 910 extracts and processes header information from the received frames.Ethernet frame processor 910 forwards the frames toIP management module 930 if there is no other intermediate RBridge between the end device andRBridge 900. - In some embodiments,
gateway RBridge 900 may include a VCS configuration module 944 that includes a virtualswitch management module 940 and alogical switch 942 as described in conjunction withFIG. 1 . VCS configuration module 944 maintains a configuration database instorage 950 that maintains the configuration state of every switch within the VCS. Virtualswitch management module 940 maintains the state oflogical switch 942, which is used to join other VCS switches. In some embodiments,logical switch 942 can be configured to operate in conjunction withEthernet frame processor 910 as a logical Ethernet switch. - Note that the above-mentioned modules can be implemented in hardware as well as in software. In one embodiment, these modules can be embodied in computer-executable instructions stored in a memory which is coupled to one or more processors in
gateway RBridge 900. When executed, these instructions cause the processor(s) to perform the aforementioned functions. - In summary, embodiments of the present invention provide a switch, a method and a system for providing layer-3 support in a TRILL network. In one embodiment, the switch includes an IP header processor and a forwarding mechanism. The IP header processor identifies a destination IP address in a packet encapsulated with an inner Ethernet header, a TRILL header, and an outer Ethernet header. The forwarding mechanism determines an output port and constructs a new header for the packet based on the destination IP address. The switch also includes a packet processor which determines whether (1) an inner destination media access control (MAC) address corresponds to a local MAC address assigned to the switch; (2) a destination RBridge identifier corresponds to a local RBridge identifier assigned to the switch; and (3) an outer destination MAC address corresponds to the local MAC address. Such configuration provides a scalable and flexible solution to enable layer-3 processing in the switch.
- The methods and processes described herein can be embodied as code and/or data, which can be stored in a computer-readable non-transitory storage medium. When a computer system reads and executes the code and/or data stored on the computer-readable non-transitory storage medium, the computer system performs the methods and processes embodied as data structures and code and stored within the medium.
- The methods and processes described herein can be executed by and/or included in hardware modules or apparatus. These modules or apparatus may include, but are not limited to, an application-specific integrated circuit (ASIC) chip, a field-programmable gate array (FPGA), a dedicated or shared processor that executes a particular software module or a piece of code at a particular time, and/or other programmable-logic devices now known or later developed. When the hardware modules or apparatus are activated, they perform the methods and processes included within them.
- The foregoing descriptions of embodiments of the present invention have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit this disclosure. Accordingly, many modifications and variations will be apparent to practitioners skilled in the art. The scope of the present invention is defined by the appended claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/312,903 US9270572B2 (en) | 2011-05-02 | 2011-12-06 | Layer-3 support in TRILL networks |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161481643P | 2011-05-02 | 2011-05-02 | |
US201161503265P | 2011-06-30 | 2011-06-30 | |
US13/312,903 US9270572B2 (en) | 2011-05-02 | 2011-12-06 | Layer-3 support in TRILL networks |
Publications (2)
Publication Number | Publication Date |
---|---|
US20120281700A1 true US20120281700A1 (en) | 2012-11-08 |
US9270572B2 US9270572B2 (en) | 2016-02-23 |
Family
ID=47090208
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/312,903 Expired - Fee Related US9270572B2 (en) | 2011-05-02 | 2011-12-06 | Layer-3 support in TRILL networks |
Country Status (1)
Country | Link |
---|---|
US (1) | US9270572B2 (en) |
Cited By (70)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103200100A (en) * | 2013-03-12 | 2013-07-10 | 杭州华三通信技术有限公司 | Method and device for packet transmitting |
US20130305344A1 (en) * | 2012-05-14 | 2013-11-14 | Alcatel-Lucent India Limited | Enterprise network services over distributed clouds |
US20140029412A1 (en) * | 2012-07-27 | 2014-01-30 | Dell Products L.P. | Systems and methods for providing anycast mac addressing in an information handling system |
US20140122704A1 (en) * | 2012-10-26 | 2014-05-01 | Hangzhou H3C Technologies Co., Ltd. | Remote port mirroring |
US20140204761A1 (en) * | 2013-01-22 | 2014-07-24 | Brocade Communications Systems, Inc. | Optimizing traffic flows via dynamic routing protocol modifications when using server virtualization with dynamic routing |
US20150016462A1 (en) * | 2012-07-10 | 2015-01-15 | Hangzhou H3C Technologies Co., Ltd. | Traffic forwarding in a layer 2 edge network |
CN104301226A (en) * | 2013-07-16 | 2015-01-21 | 杭州华三通信技术有限公司 | Designated routing bridge (DRB) election method, equipment and system |
CN104348726A (en) * | 2013-08-02 | 2015-02-11 | 杭州华三通信技术有限公司 | Message forwarding method and device |
US20150071122A1 (en) * | 2013-09-06 | 2015-03-12 | Brocade Communications Systems, Inc. | Transparent inteconnection of ethernet fabric switches |
US9036646B2 (en) * | 2012-06-20 | 2015-05-19 | International Business Machines Corporation | Distributed routing mechanisms for a virtual switch enabled by a trill-based fabric |
CN104660519A (en) * | 2013-11-25 | 2015-05-27 | 华为技术有限公司 | Method and device for processing forwarding path in TRILL network |
US20150215205A1 (en) * | 2012-10-11 | 2015-07-30 | Huawei Technologies Co., Ltd. | Method, Routing Bridge, and System For Sending Packet |
US9130836B2 (en) | 2013-02-04 | 2015-09-08 | Cisco Technology, Inc. | Provisoning of a new node joining an existing cluster in a data center environment |
WO2015154421A1 (en) * | 2014-07-01 | 2015-10-15 | 中兴通讯股份有限公司 | Method, device and system for managing trill network using three-layer network manager |
US20150365316A1 (en) * | 2013-01-23 | 2015-12-17 | Zte Corporation | Message Processing Method and System in Multi-Homing Access Overlay Network |
US9286047B1 (en) | 2013-02-13 | 2016-03-15 | Cisco Technology, Inc. | Deployment and upgrade of network devices in a network environment |
US20160142287A1 (en) * | 2013-08-02 | 2016-05-19 | Hangzhou H3C Technologies Co., Ltd. | Packet forwarding |
CN105939216A (en) * | 2016-03-16 | 2016-09-14 | 杭州迪普科技有限公司 | Message transmission method and device |
CN105991446A (en) * | 2015-02-06 | 2016-10-05 | 中国移动通信集团公司 | Three-layer networking method, device and system and data processing method, device and system of TRILL network |
US9571394B1 (en) * | 2014-01-10 | 2017-02-14 | Juniper Networks, Inc. | Tunneled packet aggregation for virtual networks |
US9590855B2 (en) | 2013-11-18 | 2017-03-07 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Configuration of transparent interconnection of lots of links (TRILL) protocol enabled device ports in edge virtual bridging (EVB) networks |
WO2017149157A1 (en) * | 2016-03-03 | 2017-09-08 | Andrew Wireless Systems Gmbh | Hybrid ran/digital das repeater system with ethernet transport |
US9848040B2 (en) | 2010-06-07 | 2017-12-19 | Brocade Communications Systems, Inc. | Name services for virtual cluster switching |
US9912614B2 (en) | 2015-12-07 | 2018-03-06 | Brocade Communications Systems LLC | Interconnection of switches based on hierarchical overlay tunneling |
US9912612B2 (en) | 2013-10-28 | 2018-03-06 | Brocade Communications Systems LLC | Extended ethernet fabric switches |
US9942097B2 (en) | 2015-01-05 | 2018-04-10 | Brocade Communications Systems LLC | Power management in a network of interconnected switches |
US9942173B2 (en) | 2010-05-28 | 2018-04-10 | Brocade Communications System Llc | Distributed configuration management for virtual cluster switching |
US9998365B2 (en) | 2012-05-18 | 2018-06-12 | Brocade Communications Systems, LLC | Network feedback in software-defined networks |
US10003552B2 (en) | 2015-01-05 | 2018-06-19 | Brocade Communications Systems, Llc. | Distributed bidirectional forwarding detection protocol (D-BFD) for cluster of interconnected switches |
US10038592B2 (en) | 2015-03-17 | 2018-07-31 | Brocade Communications Systems LLC | Identifier assignment to a new switch in a switch group |
US10044568B2 (en) | 2014-05-13 | 2018-08-07 | Brocade Communications Systems LLC | Network extension groups of global VLANs in a fabric switch |
US10063473B2 (en) | 2014-04-30 | 2018-08-28 | Brocade Communications Systems LLC | Method and system for facilitating switch virtualization in a network of interconnected switches |
US10075394B2 (en) | 2012-11-16 | 2018-09-11 | Brocade Communications Systems LLC | Virtual link aggregations across multiple fabric switches |
US10116531B2 (en) | 2015-06-05 | 2018-10-30 | Cisco Technology, Inc | Round trip time (RTT) measurement based upon sequence number |
US10142353B2 (en) | 2015-06-05 | 2018-11-27 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10164883B2 (en) | 2011-11-10 | 2018-12-25 | Avago Technologies International Sales Pte. Limited | System and method for flow management in software-defined networks |
US10171303B2 (en) | 2015-09-16 | 2019-01-01 | Avago Technologies International Sales Pte. Limited | IP-based interconnection of switches with a logical chassis |
US10237090B2 (en) | 2016-10-28 | 2019-03-19 | Avago Technologies International Sales Pte. Limited | Rule-based network identifier mapping |
US10250446B2 (en) | 2017-03-27 | 2019-04-02 | Cisco Technology, Inc. | Distributed policy store |
US10284469B2 (en) | 2014-08-11 | 2019-05-07 | Avago Technologies International Sales Pte. Limited | Progressive MAC address learning |
US10348643B2 (en) | 2010-07-16 | 2019-07-09 | Avago Technologies International Sales Pte. Limited | System and method for network configuration |
US10355879B2 (en) | 2014-02-10 | 2019-07-16 | Avago Technologies International Sales Pte. Limited | Virtual extensible LAN tunnel keepalives |
US10374904B2 (en) | 2015-05-15 | 2019-08-06 | Cisco Technology, Inc. | Diagnostic network visualization |
US10419276B2 (en) | 2010-06-07 | 2019-09-17 | Avago Technologies International Sales Pte. Limited | Advanced link tracking for virtual cluster switching |
US10439929B2 (en) | 2015-07-31 | 2019-10-08 | Avago Technologies International Sales Pte. Limited | Graceful recovery of a multicast-enabled switch |
US10462049B2 (en) | 2013-03-01 | 2019-10-29 | Avago Technologies International Sales Pte. Limited | Spanning tree in fabric switches |
US10476698B2 (en) | 2014-03-20 | 2019-11-12 | Avago Technologies International Sales Pte. Limited | Redundent virtual link aggregation group |
US10523512B2 (en) | 2017-03-24 | 2019-12-31 | Cisco Technology, Inc. | Network agent for generating platform specific network policies |
US10523541B2 (en) | 2017-10-25 | 2019-12-31 | Cisco Technology, Inc. | Federated network and application data analytics platform |
US10554501B2 (en) | 2017-10-23 | 2020-02-04 | Cisco Technology, Inc. | Network migration assistant |
US10574575B2 (en) | 2018-01-25 | 2020-02-25 | Cisco Technology, Inc. | Network flow stitching using middle box flow stitching |
US10579406B2 (en) | 2015-04-08 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Dynamic orchestration of overlay tunnels |
US10581758B2 (en) | 2014-03-19 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Distributed hot standby links for vLAG |
US10594542B2 (en) | 2017-10-27 | 2020-03-17 | Cisco Technology, Inc. | System and method for network root cause analysis |
US10594560B2 (en) | 2017-03-27 | 2020-03-17 | Cisco Technology, Inc. | Intent driven network policy platform |
US10616108B2 (en) | 2014-07-29 | 2020-04-07 | Avago Technologies International Sales Pte. Limited | Scalable MAC address virtualization |
US10673703B2 (en) | 2010-05-03 | 2020-06-02 | Avago Technologies International Sales Pte. Limited | Fabric switching |
US10680887B2 (en) | 2017-07-21 | 2020-06-09 | Cisco Technology, Inc. | Remote device status audit and recovery |
US10708152B2 (en) | 2017-03-23 | 2020-07-07 | Cisco Technology, Inc. | Predicting application and network performance |
US10708183B2 (en) | 2016-07-21 | 2020-07-07 | Cisco Technology, Inc. | System and method of providing segment routing as a service |
US10764141B2 (en) | 2017-03-27 | 2020-09-01 | Cisco Technology, Inc. | Network agent for reporting to a network policy system |
US10798015B2 (en) | 2018-01-25 | 2020-10-06 | Cisco Technology, Inc. | Discovery of middleboxes using traffic flow stitching |
US10797970B2 (en) | 2015-06-05 | 2020-10-06 | Cisco Technology, Inc. | Interactive hierarchical network chord diagram for application dependency mapping |
US10826803B2 (en) | 2018-01-25 | 2020-11-03 | Cisco Technology, Inc. | Mechanism for facilitating efficient policy updates |
US10873794B2 (en) | 2017-03-28 | 2020-12-22 | Cisco Technology, Inc. | Flowlet resolution for application performance monitoring and management |
US10972388B2 (en) | 2016-11-22 | 2021-04-06 | Cisco Technology, Inc. | Federated microburst detection |
US10999149B2 (en) | 2018-01-25 | 2021-05-04 | Cisco Technology, Inc. | Automatic configuration discovery based on traffic flow data |
US11128700B2 (en) | 2018-01-26 | 2021-09-21 | Cisco Technology, Inc. | Load balancing configuration based on traffic flow telemetry |
US11233821B2 (en) | 2018-01-04 | 2022-01-25 | Cisco Technology, Inc. | Network intrusion counter-intelligence |
US11675637B2 (en) | 2018-08-23 | 2023-06-13 | Arrcus Inc. | Host routed overlay with deterministic host learning and localized integrated routing and bridging |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20160065503A1 (en) * | 2014-08-29 | 2016-03-03 | Extreme Networks, Inc. | Methods, systems, and computer readable media for virtual fabric routing |
US9917771B2 (en) * | 2015-08-07 | 2018-03-13 | Cisco Technology, Inc. | Virtual expansion of network fabric edge for multihoming of layer-2 switches and hosts |
CN106385366B (en) * | 2016-08-31 | 2019-07-02 | 迈普通信技术股份有限公司 | TRILL network management method and device |
EP3692685B1 (en) * | 2017-10-06 | 2023-04-19 | Telefonaktiebolaget LM Ericsson (publ) | Remotely controlling network slices in a network |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6064671A (en) * | 1995-12-08 | 2000-05-16 | Killian; Michael G. | Multi-homed end system for increasing computers network bandwidth |
US20020054593A1 (en) * | 2000-10-26 | 2002-05-09 | Tomoo Morohashi | Access network system |
US7061877B1 (en) * | 1999-09-10 | 2006-06-13 | Georgia Tech Reseach Corporation | System and method for providing high speed wireless media access |
US20060256767A1 (en) * | 2003-06-11 | 2006-11-16 | Nec Corporation | Router and network connecting method |
US20090092043A1 (en) * | 2007-10-03 | 2009-04-09 | Nortel Networks Limited | Providing an abstraction layer in a cluster switch that includes plural switches |
US20100272107A1 (en) * | 2007-11-26 | 2010-10-28 | Oktavian Papp | Technique for address resolution in a data transmission network |
US7924837B1 (en) * | 2000-07-31 | 2011-04-12 | Avaya Communication Israel Ltd. | IP multicast in VLAN environment |
US20110286457A1 (en) * | 2010-05-24 | 2011-11-24 | Cheng Tien Ee | Methods and apparatus to route control packets based on address partitioning |
US20110299535A1 (en) * | 2010-06-07 | 2011-12-08 | Brocade Communications Systems, Inc. | Name services for virtual cluster switching |
US20120106339A1 (en) * | 2010-11-01 | 2012-05-03 | Cisco Technology, Inc. | Probing Specific Customer Flow in Layer-2 Multipath Networks |
Family Cites Families (344)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5309433A (en) | 1992-06-18 | 1994-05-03 | International Business Machines Corp. | Methods and apparatus for routing packets in packet transmission networks |
US5390173A (en) | 1992-10-22 | 1995-02-14 | Digital Equipment Corporation | Packet format in hub for packet data communications system |
US5802278A (en) | 1995-05-10 | 1998-09-01 | 3Com Corporation | Bridge/router architecture for high performance scalable networking |
US5684800A (en) | 1995-11-15 | 1997-11-04 | Cabletron Systems, Inc. | Method for establishing restricted broadcast groups in a switched network |
US5983278A (en) | 1996-04-19 | 1999-11-09 | Lucent Technologies Inc. | Low-loss, fair bandwidth allocation flow control in a packet switch |
US6085238A (en) | 1996-04-23 | 2000-07-04 | Matsushita Electric Works, Ltd. | Virtual LAN system |
US5878232A (en) | 1996-12-27 | 1999-03-02 | Compaq Computer Corporation | Dynamic reconfiguration of network device's virtual LANs using the root identifiers and root ports determined by a spanning tree procedure |
US20010005527A1 (en) | 1997-03-31 | 2001-06-28 | Kathleen Michelle Vaeth | Thin film fabrication |
US6041042A (en) | 1997-05-27 | 2000-03-21 | Cabletron Systems, Inc. | Remote port mirroring system and method thereof |
US5959968A (en) | 1997-07-30 | 1999-09-28 | Cisco Systems, Inc. | Port aggregation protocol |
US6185214B1 (en) | 1997-09-11 | 2001-02-06 | 3Com Corporation | Use of code vectors for frame forwarding in a bridge/router |
US7430164B2 (en) | 1998-05-04 | 2008-09-30 | Hewlett-Packard Development Company, L.P. | Path recovery on failure in load balancing switch protocols |
US5973278A (en) | 1998-05-07 | 1999-10-26 | Eaton Corporation | Snap acting charge/discharge and open/closed indicators displaying states of electrical switching apparatus |
IL125272A0 (en) | 1998-07-08 | 1999-03-12 | Galileo Technology Ltd | Vlan protocol |
US6792500B1 (en) | 1998-07-08 | 2004-09-14 | Broadcom Corporation | Apparatus and method for managing memory defects |
US6560229B1 (en) | 1998-07-08 | 2003-05-06 | Broadcom Corporation | Network switching architecture with multiple table synchronization, and forwarding of both IP and IPX packets |
US6185241B1 (en) | 1998-10-29 | 2001-02-06 | Xerox Corporation | Metal spatial filter to enhance model reflectivity in a vertical cavity surface emitting laser |
US6438106B1 (en) | 1998-12-22 | 2002-08-20 | Nortel Networks Limited | Inter-class schedulers utilizing statistical priority guaranteed queuing and generic cell-rate algorithm priority guaranteed queuing |
US6771610B1 (en) | 1999-01-19 | 2004-08-03 | 3Com Corporation | Spanning tree with protocol for bypassing port state transition timers |
US6542266B1 (en) | 1999-06-24 | 2003-04-01 | Qwest Communications International Inc. | System and method for providing broadband data service |
JP4148605B2 (en) | 1999-08-06 | 2008-09-10 | 富士通株式会社 | Network system and server |
US6498781B1 (en) | 1999-08-13 | 2002-12-24 | International Business Machines Corporation | Self-tuning link aggregation system |
EP2267008B1 (en) | 1999-08-25 | 2014-07-02 | Allergan, Inc. | Activatable recombinant neurotoxins |
AU2001245335A1 (en) | 2000-02-22 | 2001-09-03 | Top Layer Networks, Inc. | System and method for flow mirroring in a network switch |
JP2001313670A (en) | 2000-04-28 | 2001-11-09 | Oki Electric Ind Co Ltd | Method for managing network |
AU2001256635A1 (en) | 2000-05-11 | 2001-11-20 | Firemedia Communications (Israel) Ltd. | Three-dimensional switch providing packet routing between multiple multimedia buses |
JP4168574B2 (en) | 2000-06-02 | 2008-10-22 | 株式会社日立製作所 | Packet transfer apparatus, packet transfer control method, and packet transfer apparatus setting method |
WO2002003614A2 (en) | 2000-06-29 | 2002-01-10 | Cachestream Corporation | Virtual multicasting |
US6633761B1 (en) | 2000-08-11 | 2003-10-14 | Reefedge, Inc. | Enabling seamless user mobility in a short-range wireless networking environment |
US8619793B2 (en) | 2000-08-21 | 2013-12-31 | Rockstar Consortium Us Lp | Dynamic assignment of traffic classes to a priority queue in a packet forwarding device |
CA2355473A1 (en) | 2000-09-29 | 2002-03-29 | Linghsiao Wang | Buffer management for support of quality-of-service guarantees and data flow control in data switching |
US6937576B1 (en) | 2000-10-17 | 2005-08-30 | Cisco Technology, Inc. | Multiple instance spanning tree protocol |
US6957269B2 (en) | 2001-01-03 | 2005-10-18 | Advanced Micro Devices, Inc. | Method and apparatus for performing priority-based flow control |
US6912592B2 (en) | 2001-01-05 | 2005-06-28 | Extreme Networks, Inc. | Method and system of aggregate multiple VLANs in a metropolitan area network |
CA2436710C (en) | 2001-01-31 | 2011-06-14 | Lancope, Inc. | Network port profiling |
US7016352B1 (en) | 2001-03-23 | 2006-03-21 | Advanced Micro Devices, Inc. | Address modification within a switching device in a packet-switched network |
US7450595B1 (en) | 2001-05-01 | 2008-11-11 | At&T Corp. | Method and system for managing multiple networks over a set of ports |
US7102996B1 (en) | 2001-05-24 | 2006-09-05 | F5 Networks, Inc. | Method and system for scaling network traffic managers |
US20070116422A1 (en) | 2001-06-06 | 2007-05-24 | Reynolds Thomas A | Photoresponsive polyimide based fiber |
US6956824B2 (en) | 2001-06-14 | 2005-10-18 | Tropic Networks Inc. | Extension of link aggregation protocols over the network |
US20040001433A1 (en) | 2001-07-18 | 2004-01-01 | Gram Charles Andrew | Interactive control of network devices |
US7382787B1 (en) | 2001-07-30 | 2008-06-03 | Cisco Technology, Inc. | Packet routing and switching device |
WO2003015352A1 (en) | 2001-08-01 | 2003-02-20 | Nokia Corporation | Apparatus and method for flow scheduling based on priorities in a mobile network |
US20030157168A1 (en) | 2001-08-06 | 2003-08-21 | Christopher Breder | Sequestered antagonist formulations |
JP2003069573A (en) | 2001-08-23 | 2003-03-07 | Allied Tereshisu Kk | System and method for managing network equipment using information recording medium |
US7173934B2 (en) | 2001-09-10 | 2007-02-06 | Nortel Networks Limited | System, device, and method for improving communication network reliability using trunk splitting |
US20030084219A1 (en) | 2001-10-26 | 2003-05-01 | Maxxan Systems, Inc. | System, apparatus and method for address forwarding for a computer network |
US20070094465A1 (en) | 2001-12-26 | 2007-04-26 | Cisco Technology, Inc., A Corporation Of California | Mirroring mechanisms for storage area networks and network based virtualization |
US20030123393A1 (en) | 2002-01-03 | 2003-07-03 | Feuerstraeter Mark T. | Method and apparatus for priority based flow control in an ethernet architecture |
WO2003071749A1 (en) | 2002-02-20 | 2003-08-28 | Mitsubishi Denki Kabushiki Kaisha | Mobile body network |
US7688960B1 (en) | 2002-02-26 | 2010-03-30 | Sprint Communications Company L.P. | Method and system for separating business and device logic in a computing network system |
US7606938B2 (en) | 2002-03-01 | 2009-10-20 | Enterasys Networks, Inc. | Verified device locations in a data network |
US20030174706A1 (en) | 2002-03-15 | 2003-09-18 | Broadcom Corporation | Fastpath implementation for transparent local area network (LAN) services over multiprotocol label switching (MPLS) |
US7315545B1 (en) | 2002-03-29 | 2008-01-01 | Nortel Networks Limited | Method and apparatus to support differential internet data packet treatment in a base station controller |
TW550902B (en) | 2002-04-03 | 2003-09-01 | Accton Technology Corp | Method of setting network configuration and device and system thereof |
US7209435B1 (en) | 2002-04-16 | 2007-04-24 | Foundry Networks, Inc. | System and method for providing network route redundancy across Layer 2 devices |
US20090279558A1 (en) | 2002-05-06 | 2009-11-12 | Ian Edward Davis | Network routing apparatus for enhanced efficiency and monitoring capability |
US7206288B2 (en) | 2002-06-12 | 2007-04-17 | Cisco Technology, Inc. | Methods and apparatus for characterizing a route in fibre channel fabric |
US20040003094A1 (en) | 2002-06-27 | 2004-01-01 | Michael See | Method and apparatus for mirroring traffic over a network |
FI113127B (en) | 2002-06-28 | 2004-02-27 | Ssh Comm Security Corp | Broadcast packet handling method for gateway computer, involves encapsulating packet into form acceptable for transmission over Internet protocol security protected connection and transmitting packet to logical network segment |
US7330897B2 (en) | 2002-07-09 | 2008-02-12 | International Business Machines Corporation | Methods and apparatus for storage area network component registration |
US7453888B2 (en) | 2002-08-27 | 2008-11-18 | Alcatel Lucent | Stackable virtual local area network provisioning in bridged networks |
US7316031B2 (en) | 2002-09-06 | 2008-01-01 | Capital One Financial Corporation | System and method for remotely monitoring wireless networks |
DE60334126D1 (en) | 2002-10-04 | 2010-10-21 | Ericsson Telefon Ab L M | ISOLATION OF HOSTS ASSOCIATED WITH AN ACCESS NETWORK |
US7647427B1 (en) | 2002-10-18 | 2010-01-12 | Foundry Networks, Inc. | Redundancy support for network address translation (NAT) |
JP2006505992A (en) | 2002-11-08 | 2006-02-16 | コーニンクレッカ フィリップス エレクトロニクス エヌ ヴィ | Method and apparatus for permitting remote access in a data network |
US7424014B2 (en) | 2002-11-12 | 2008-09-09 | Cisco Technology, Inc. | System and method for local packet transport services within distributed routers |
US7397794B1 (en) | 2002-11-21 | 2008-07-08 | Juniper Networks, Inc. | Systems and methods for implementing virtual switch planes in a physical switch fabric |
KR100480366B1 (en) | 2002-12-24 | 2005-03-31 | 한국전자통신연구원 | A system for VLAN configuration of E-PON and method thereof, its program stored recording medium |
US7417950B2 (en) | 2003-02-03 | 2008-08-26 | Ciena Corporation | Method and apparatus for performing data flow ingress/egress admission control in a provider network |
JP4256693B2 (en) | 2003-02-18 | 2009-04-22 | 株式会社日立製作所 | Computer system, I / O device, and virtual sharing method of I / O device |
US20040165595A1 (en) | 2003-02-25 | 2004-08-26 | At&T Corp. | Discovery and integrity testing method in an ethernet domain |
US7411973B2 (en) | 2003-03-11 | 2008-08-12 | Broadcom Corporation | System and method for interfacing with a management system |
US7486674B2 (en) | 2003-04-28 | 2009-02-03 | Alcatel-Lucent Usa Inc. | Data mirroring in a service |
US7370346B2 (en) | 2003-04-29 | 2008-05-06 | Hewlett-Packard Development Company, L.P. | Method and apparatus for access security services |
US7561590B1 (en) | 2003-05-05 | 2009-07-14 | Marvell International Ltd. | Network switch having virtual input queues for flow control |
US7516487B1 (en) | 2003-05-21 | 2009-04-07 | Foundry Networks, Inc. | System and method for source IP anti-spoofing security |
US7480258B1 (en) | 2003-07-03 | 2009-01-20 | Cisco Technology, Inc. | Cross stack rapid transition protocol |
US7463579B2 (en) | 2003-07-11 | 2008-12-09 | Nortel Networks Limited | Routed split multilink trunking |
JP4123088B2 (en) | 2003-08-06 | 2008-07-23 | 株式会社日立製作所 | Storage network management apparatus and method |
US7380025B1 (en) | 2003-10-07 | 2008-05-27 | Cisco Technology, Inc. | Method and apparatus providing role-based configuration of a port of a network element |
US8050180B2 (en) | 2003-10-31 | 2011-11-01 | Brocade Communications Systems, Inc. | Network path tracing method |
US8179808B2 (en) | 2003-10-31 | 2012-05-15 | Brocade Communication Systems, Inc. | Network path tracing method |
WO2005050950A1 (en) | 2003-11-13 | 2005-06-02 | Cryptek, Inc. | System and method for traversing access control metadata across multiple network domains |
US7558273B1 (en) | 2003-12-23 | 2009-07-07 | Extreme Networks, Inc. | Methods and systems for associating and translating virtual local area network (VLAN) tags |
US7701948B2 (en) | 2004-01-20 | 2010-04-20 | Nortel Networks Limited | Metro ethernet service enhancements |
US7333508B2 (en) | 2004-01-20 | 2008-02-19 | Nortel Networks Limited | Method and system for Ethernet and frame relay network interworking |
US8804728B2 (en) | 2004-01-20 | 2014-08-12 | Rockstar Consortium Us Lp | Ethernet differentiated services conditioning |
US7310664B1 (en) | 2004-02-06 | 2007-12-18 | Extreme Networks | Unified, configurable, adaptive, network architecture |
US7860097B1 (en) | 2004-02-13 | 2010-12-28 | Habanero Holdings, Inc. | Fabric-backplane enterprise servers with VNICs and VLANs |
US7843907B1 (en) | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway target for fabric-backplane enterprise servers |
US7843906B1 (en) | 2004-02-13 | 2010-11-30 | Habanero Holdings, Inc. | Storage gateway initiator for fabric-backplane enterprise servers |
US20050195813A1 (en) | 2004-02-23 | 2005-09-08 | Sinett Corporation | Unified architecture for wired and wireless networks |
US7477894B1 (en) | 2004-02-23 | 2009-01-13 | Foundry Networks, Inc. | Methods and apparatus for handling wireless roaming among and across wireless area networks |
US7690040B2 (en) | 2004-03-10 | 2010-03-30 | Enterasys Networks, Inc. | Method for network traffic mirroring with data privacy |
US20050220096A1 (en) | 2004-04-06 | 2005-10-06 | Robert Friskney | Traffic engineering in frame-based carrier networks |
US7792920B2 (en) | 2004-04-30 | 2010-09-07 | Vulcan Inc. | Network-accessible control of one or more media devices |
JP4373271B2 (en) | 2004-05-14 | 2009-11-25 | 富士通株式会社 | Method and program for grasping network configuration of virtual LAN in node network |
JP4397292B2 (en) | 2004-07-09 | 2010-01-13 | 富士通株式会社 | Control packet loop prevention method and bridge device using the same |
FR2873524B1 (en) | 2004-07-22 | 2006-10-27 | Alcatel Sa | LOCAL NETWORK WITH VIRTUAL GROUP (S) OF HEART EQUIPMENT WHICH IS CLEAR AT THE LEVEL TWO SWITCHING |
US7466712B2 (en) | 2004-07-30 | 2008-12-16 | Brocade Communications Systems, Inc. | System and method for providing proxy and translation domains in a fibre channel router |
EP1782293A2 (en) | 2004-08-20 | 2007-05-09 | Enterasys Networks, Inc. | System, method and apparatus for traffic mirror setup, service and security in communication networks |
US7463597B1 (en) | 2004-08-27 | 2008-12-09 | Juniper Networks, Inc. | Spanning tree protocol synchronization within virtual private networks |
US7558219B1 (en) | 2004-08-30 | 2009-07-07 | Juniper Networks, Inc. | Multicast trees for virtual private local area network (LAN) service multicast |
US8116307B1 (en) | 2004-09-23 | 2012-02-14 | Juniper Networks, Inc. | Packet structure for mirrored traffic flow |
US7764768B2 (en) | 2004-10-06 | 2010-07-27 | Alcatel-Lucent Usa Inc. | Providing CALEA/legal intercept information to law enforcement agencies for internet protocol multimedia subsystems (IMS) |
US7508757B2 (en) | 2004-10-15 | 2009-03-24 | Alcatel Lucent | Network with MAC table overflow protection |
US7801125B2 (en) | 2004-10-22 | 2010-09-21 | Cisco Technology, Inc. | Forwarding table reduction and multipath network forwarding |
US8238347B2 (en) | 2004-10-22 | 2012-08-07 | Cisco Technology, Inc. | Fibre channel over ethernet |
GB2419701A (en) | 2004-10-29 | 2006-05-03 | Hewlett Packard Development Co | Virtual overlay infrastructure with dynamic control of mapping |
EP1657853A1 (en) | 2004-11-12 | 2006-05-17 | STMicroelectronics (Research & Development) Limited | Roaming network stations using a MAC address identifier to select a new access point |
US8700799B2 (en) | 2004-11-12 | 2014-04-15 | Brocade Communications Systems, Inc. | Methods, devices and systems with improved zone merge operation by operating on a switch basis |
US8005084B2 (en) | 2004-11-30 | 2011-08-23 | Broadcom Corporation | Mirroring in a network device |
US7808992B2 (en) | 2004-12-30 | 2010-10-05 | Cisco Technology, Inc. | Platform independent implementation of private VLANS |
US20070036178A1 (en) | 2005-02-02 | 2007-02-15 | Susan Hares | Layer 2 virtual switching environment |
US20060184937A1 (en) | 2005-02-11 | 2006-08-17 | Timothy Abels | System and method for centralized software management in virtual machines |
US7586895B2 (en) | 2005-04-01 | 2009-09-08 | Cisco Technology, Inc. | Performing extended lookups on MAC-based tables including level 3 multicast group destination addresses |
US7673068B2 (en) | 2005-04-18 | 2010-03-02 | Alcatel Lucent | Method and system for implementing a high availability VLAN |
GB2425681A (en) | 2005-04-27 | 2006-11-01 | 3Com Corporaton | Access control by Dynamic Host Configuration Protocol snooping |
US7835370B2 (en) | 2005-04-28 | 2010-11-16 | Cisco Technology, Inc. | System and method for DSL subscriber identification over ethernet network |
US8751649B2 (en) | 2005-06-07 | 2014-06-10 | Extreme Networks | Port management system |
US20060285499A1 (en) | 2005-06-17 | 2006-12-21 | Broadcom Corporation | Loop detection for a network device |
US7571447B2 (en) | 2005-06-20 | 2009-08-04 | International Business Machines Corporation | Loose coupling of web services |
GB0516158D0 (en) | 2005-08-05 | 2005-09-14 | Univ Montfort | An apparatus and method for `non-contact' electrical impedance imaging |
US7937756B2 (en) | 2005-08-19 | 2011-05-03 | Cpacket Networks, Inc. | Apparatus and method for facilitating network security |
EP1924864B1 (en) | 2005-09-12 | 2015-03-04 | Rockstar Consortium US LP | Forwarding plane data communications channel for ethernet transport networks |
US9143841B2 (en) | 2005-09-29 | 2015-09-22 | Brocade Communications Systems, Inc. | Federated management of intelligent service modules |
DE102005048585A1 (en) | 2005-10-06 | 2007-04-12 | Robert Bosch Gmbh | Subscriber and communication controller of a communication system and method for implementing a gateway functionality in a subscriber of a communication system |
CN100442772C (en) | 2005-10-19 | 2008-12-10 | 华为技术有限公司 | Bridge-connection transmitting method |
US9497600B2 (en) | 2005-10-28 | 2016-11-15 | Hewlett Packard Enterprise Development Lp | Service chaining |
US7697528B2 (en) | 2005-11-01 | 2010-04-13 | Nortel Networks Limited | Multilink trunking for encapsulated traffic |
DE602005022638D1 (en) | 2005-12-12 | 2010-09-09 | Ericsson Telefon Ab L M | METHOD AND DEVICES FOR SPECIFYING THE SERVICE QUALITY WHEN TRANSMITTING DATA PACKAGES |
US7716240B2 (en) | 2005-12-29 | 2010-05-11 | Nextlabs, Inc. | Techniques and system to deploy policies intelligently |
US7835378B2 (en) | 2006-02-02 | 2010-11-16 | Cisco Technology, Inc. | Root node redundancy for multipoint-to-multipoint transport trees |
US20070177597A1 (en) | 2006-02-02 | 2007-08-02 | Yu Ju | Ethernet connection-based forwarding process |
US7639605B2 (en) | 2006-02-08 | 2009-12-29 | Cisco Technology, Inc. | System and method for detecting and recovering from virtual switch link failures |
US8189575B2 (en) | 2006-03-13 | 2012-05-29 | Rockstar Bidco, L.P. | Modular scalable switch architecture |
US7948977B2 (en) | 2006-05-05 | 2011-05-24 | Broadcom Corporation | Packet routing with payload analysis, encapsulation and service module vectoring |
US8160080B1 (en) | 2006-05-08 | 2012-04-17 | Marvell Israel (M.I.S.L.) Ltd. | Implementation of reliable synchronization of distributed databases |
JP2007318553A (en) | 2006-05-26 | 2007-12-06 | Fujitsu Ltd | Network managing method |
US8018938B1 (en) | 2006-06-02 | 2011-09-13 | World Wide Packets, Inc. | Translating between a switching format and a transport format |
JP4834493B2 (en) | 2006-08-25 | 2011-12-14 | アラクサラネットワークス株式会社 | Network relay device and method for controlling network relay device |
CN100583825C (en) | 2006-08-30 | 2010-01-20 | 华为技术有限公司 | Method of generating symmetrical tree in the shortest path bridge |
US8396945B2 (en) | 2006-09-11 | 2013-03-12 | Alcatel Lucent | Network management system with adaptive sampled proactive diagnostic capabilities |
US20080080517A1 (en) | 2006-09-28 | 2008-04-03 | At & T Corp. | System and method for forwarding traffic data in an MPLS VPN |
US8208463B2 (en) | 2006-10-24 | 2012-06-26 | Cisco Technology, Inc. | Subnet scoped multicast / broadcast packet distribution mechanism over a routed network |
US7697556B2 (en) | 2006-10-26 | 2010-04-13 | Telefonaktiebolaget L M Ericsson (Publ) | MAC (media access control) tunneling and control and method |
US7720889B1 (en) | 2006-10-31 | 2010-05-18 | Netapp, Inc. | System and method for nearly in-band search indexing |
WO2008056838A1 (en) | 2006-11-08 | 2008-05-15 | Chang Hwan Cho | System and method for controlling network traffic |
US20080112400A1 (en) | 2006-11-15 | 2008-05-15 | Futurewei Technologies, Inc. | System for Providing Both Traditional and Traffic Engineering Enabled Services |
US7599901B2 (en) | 2006-12-06 | 2009-10-06 | Microsoft Corporation | Processing data-centric business models |
US20080159277A1 (en) | 2006-12-15 | 2008-07-03 | Brocade Communications Systems, Inc. | Ethernet over fibre channel |
US20080181243A1 (en) | 2006-12-15 | 2008-07-31 | Brocade Communications Systems, Inc. | Ethernet forwarding in high performance fabrics |
US8973098B2 (en) | 2007-01-11 | 2015-03-03 | International Business Machines Corporation | System and method for virtualized resource configuration |
US7706255B1 (en) | 2007-01-29 | 2010-04-27 | Solace Systems, Inc. | Communications apparatus with redundant switching or backpressure mechanism |
US20080181196A1 (en) | 2007-01-31 | 2008-07-31 | Alcatel Lucent | Link aggregation across multiple chassis |
WO2008099446A1 (en) | 2007-02-06 | 2008-08-21 | Mitsubishi Electric Corporation | Communication system, communication device, wireless base station and wireless terminal station |
JP4259581B2 (en) | 2007-02-07 | 2009-04-30 | 日立電線株式会社 | Switching hub and LAN system |
US7796594B2 (en) | 2007-02-14 | 2010-09-14 | Marvell Semiconductor, Inc. | Logical bridging system and method |
US9661112B2 (en) | 2007-02-22 | 2017-05-23 | International Business Machines Corporation | System and methods for providing server virtualization assistance |
US8140696B2 (en) | 2007-03-12 | 2012-03-20 | International Business Machines Corporation | Layering serial attached small computer system interface (SAS) over ethernet |
US8077721B2 (en) | 2007-03-15 | 2011-12-13 | Cisco Technology, Inc. | Methods and apparatus providing two stage tunneling |
US7916741B2 (en) | 2007-04-02 | 2011-03-29 | William Marsh Rice University | System and method for preventing count-to-infinity problems in ethernet networks |
US8078704B2 (en) | 2007-04-12 | 2011-12-13 | Hewlett-Packard Development Company, L.P. | Provisioning of a service environment using web services |
US8301686B1 (en) | 2007-04-16 | 2012-10-30 | Citrix Systems, Inc. | Systems and methods for decentralized computing |
US7873038B2 (en) | 2007-04-30 | 2011-01-18 | Hewlett-Packard Development Company, L.P. | Packet processing |
US7724674B2 (en) | 2007-05-16 | 2010-05-25 | Simula Innovations As | Deadlock free network routing |
JP4862743B2 (en) | 2007-05-17 | 2012-01-25 | 日本電気株式会社 | Node, communication method and node program |
US20080298248A1 (en) | 2007-05-28 | 2008-12-04 | Guenter Roeck | Method and Apparatus For Computer Network Bandwidth Control and Congestion Management |
US7945941B2 (en) | 2007-06-01 | 2011-05-17 | Cisco Technology, Inc. | Flexible access control policy enforcement |
US8054833B2 (en) | 2007-06-05 | 2011-11-08 | Hewlett-Packard Development Company, L.P. | Packet mirroring |
US20080310342A1 (en) | 2007-06-12 | 2008-12-18 | Cisco Technology, Inc. | Addressing Messages in a Two-Tier Network |
US7898959B1 (en) | 2007-06-28 | 2011-03-01 | Marvell Israel (Misl) Ltd. | Method for weighted load-balancing among network interfaces |
US8615008B2 (en) | 2007-07-11 | 2013-12-24 | Foundry Networks Llc | Duplicating network traffic through transparent VLAN flooding |
GB0713785D0 (en) | 2007-07-16 | 2007-08-22 | Cellfire Security Technologies | Voice over IP system |
US20090044270A1 (en) | 2007-08-07 | 2009-02-12 | Asaf Shelly | Network element and an infrastructure for a network risk management system |
US7836332B2 (en) | 2007-07-18 | 2010-11-16 | Hitachi, Ltd. | Method and apparatus for managing virtual ports on storage systems |
US7864712B2 (en) | 2007-07-20 | 2011-01-04 | Cisco Technology, Inc. | Preventing loops in networks operating different protocols to provide loop-free topology |
US8166205B2 (en) | 2007-07-31 | 2012-04-24 | Cisco Technology, Inc. | Overlay transport virtualization |
US7729296B1 (en) | 2007-09-07 | 2010-06-01 | Force 10 Networks, Inc. | Distributed BPDU processing for spanning tree protocols |
US20090080345A1 (en) | 2007-09-21 | 2009-03-26 | Ericsson, Inc. | Efficient multipoint distribution tree construction for shortest path bridging |
US8798056B2 (en) | 2007-09-24 | 2014-08-05 | Intel Corporation | Method and system for virtual port communications |
EP2193630B1 (en) | 2007-09-26 | 2015-08-26 | Nicira, Inc. | Network operating system for managing and securing networks |
US20090079560A1 (en) | 2007-09-26 | 2009-03-26 | General Electric Company | Remotely monitoring railroad equipment using network protocols |
JP5030063B2 (en) | 2007-10-05 | 2012-09-19 | 本田技研工業株式会社 | Navigation device and navigation system |
US7975033B2 (en) | 2007-10-23 | 2011-07-05 | Virtudatacenter Holdings, L.L.C. | System and method for initializing and maintaining a series of virtual local area networks contained in a clustered computer system |
US8949392B2 (en) | 2007-11-07 | 2015-02-03 | Brocade Communications Systems, Inc. | Workload management with network dynamics |
WO2009064407A1 (en) | 2007-11-16 | 2009-05-22 | Ericsson Ab | Method and system for telecommunications including self-organizing scalable ethernet using is-is hierarchy |
US8117495B2 (en) | 2007-11-26 | 2012-02-14 | Stratus Technologies Bermuda Ltd | Systems and methods of high availability cluster environment failover protection |
US8194674B1 (en) | 2007-12-20 | 2012-06-05 | Quest Software, Inc. | System and method for aggregating communications and for translating between overlapping internal network addresses and unique external network addresses |
US7796593B1 (en) | 2007-12-21 | 2010-09-14 | Juniper Networks, Inc. | Router using internal flood groups for flooding VPLS traffic |
US7860093B2 (en) | 2007-12-24 | 2010-12-28 | Cisco Technology, Inc. | Fast multicast convergence at secondary designated router or designated forwarder |
US8018841B2 (en) | 2007-12-31 | 2011-09-13 | Ciena Corporation | Interworking an ethernet ring network and an ethernet network with traffic engineered trunks |
JP2009187368A (en) | 2008-02-07 | 2009-08-20 | Hitachi Ltd | Method for controlling sharing of usb port |
US20090245137A1 (en) | 2008-03-03 | 2009-10-01 | Green Hills Software, Inc. | Highly available virtual stacking architecture |
US20090222879A1 (en) | 2008-03-03 | 2009-09-03 | Microsoft Corporation | Super policy in information protection systems |
US8230069B2 (en) | 2008-03-04 | 2012-07-24 | International Business Machines Corporation | Server and storage-aware method for selecting virtual machine migration targets |
US20110044352A1 (en) | 2008-03-04 | 2011-02-24 | France Telecom | Technique for determining a point-to-multipoint tree linking a root node to a plurality of leaf nodes |
US7801137B2 (en) | 2008-03-11 | 2010-09-21 | Cisco Technology, Inc. | Receiver-based construction of point-to-multipoint trees using path computation elements in a computer network |
JP5622285B2 (en) | 2008-03-31 | 2014-11-12 | バーテックスファーマシューティカルズ インコーポレイテッドVertex Pharmaceuticalsincorporated | Pyridyl derivatives as CFTR modulators |
US7792148B2 (en) | 2008-03-31 | 2010-09-07 | International Business Machines Corporation | Virtual fibre channel over Ethernet switch |
US8743740B2 (en) | 2008-04-08 | 2014-06-03 | At&T Intellectual Property I, L.P. | Methods and apparatus to implement a partial mesh virtual private local area network service |
US7911982B1 (en) | 2008-05-01 | 2011-03-22 | Juniper Networks, Inc. | Configuring networks including spanning trees |
US8625615B2 (en) | 2008-05-16 | 2014-01-07 | Nec Corporation | PCI express switch, PCI express system, and network control method |
US8195774B2 (en) | 2008-05-23 | 2012-06-05 | Vmware, Inc. | Distributed virtual switch for virtualized computer systems |
US8160063B2 (en) | 2008-06-09 | 2012-04-17 | Microsoft Corporation | Data center interconnect and traffic engineering |
US7873711B2 (en) | 2008-06-27 | 2011-01-18 | International Business Machines Corporation | Method, system and program product for managing assignment of MAC addresses in a virtual machine environment |
US7941539B2 (en) | 2008-06-30 | 2011-05-10 | Oracle America, Inc. | Method and system for creating a virtual router in a blade chassis to maintain connectivity |
KR101508794B1 (en) | 2008-07-09 | 2015-04-06 | 삼성전자주식회사 | Method for selectively securing records in a ndef message |
US8102791B2 (en) | 2008-07-25 | 2012-01-24 | Newport Media, Inc. | Interleaver address generation in turbo decoders for mobile multimedia multicast system communication systems |
US8102781B2 (en) | 2008-07-31 | 2012-01-24 | Cisco Technology, Inc. | Dynamic distribution of virtual machines in a communication network |
US9426095B2 (en) | 2008-08-28 | 2016-08-23 | International Business Machines Corporation | Apparatus and method of switching packets between virtual ports |
US8259569B2 (en) | 2008-09-09 | 2012-09-04 | Cisco Technology, Inc. | Differentiated services for unicast and multicast frames in layer 2 topologies |
US8134922B2 (en) | 2008-09-12 | 2012-03-13 | Cisco Technology, Inc. | Reducing flooding in a bridged network |
US8392606B2 (en) | 2008-09-23 | 2013-03-05 | Synapse Wireless, Inc. | Wireless networks and methods using multiple valid network identifiers |
US7944812B2 (en) | 2008-10-20 | 2011-05-17 | International Business Machines Corporation | Redundant intermediary switch solution for detecting and managing fibre channel over ethernet FCoE switch failures |
US8571052B2 (en) | 2008-10-24 | 2013-10-29 | International Business Machines Corporation | Determining the configuration of an ethernet fabric |
US9100269B2 (en) | 2008-10-28 | 2015-08-04 | Rpx Clearinghouse Llc | Provisioned provider link state bridging (PLSB) with routed back-up |
US7962647B2 (en) | 2008-11-24 | 2011-06-14 | Vmware, Inc. | Application delivery control module for virtual network switch |
US8316113B2 (en) | 2008-12-19 | 2012-11-20 | Watchguard Technologies, Inc. | Cluster architecture and configuration for network security devices |
US7929554B2 (en) | 2008-12-23 | 2011-04-19 | Cisco Technology, Inc. | Optimized forwarding for provider backbone bridges with both I and B components (IB-PBB) |
US8509248B2 (en) | 2008-12-29 | 2013-08-13 | Juniper Networks, Inc. | Routing frames in a computer network using bridge identifiers |
US8255496B2 (en) | 2008-12-30 | 2012-08-28 | Juniper Networks, Inc. | Method and apparatus for determining a network topology during network provisioning |
US8054832B1 (en) | 2008-12-30 | 2011-11-08 | Juniper Networks, Inc. | Methods and apparatus for routing between virtual resources based on a routing location policy |
US8331362B2 (en) | 2008-12-30 | 2012-12-11 | Juniper Networks, Inc. | Methods and apparatus for distributed dynamic network provisioning |
US7820853B2 (en) | 2008-12-31 | 2010-10-26 | Celanese International Corporation | Integrated process for the production of vinyl acetate from acetic acid via ethyl acetate |
US8336079B2 (en) | 2008-12-31 | 2012-12-18 | Hytrust, Inc. | Intelligent security control system for virtualized ecosystems |
JP5168166B2 (en) | 2009-01-21 | 2013-03-21 | 富士通株式会社 | Communication apparatus and communication control method |
US9043621B2 (en) | 2009-01-21 | 2015-05-26 | Hitachi, Ltd. | Power-saving network management server, network system, and method of determining supply of power |
AU2010213547B9 (en) | 2009-02-13 | 2015-06-04 | Adc Telecommunications, Inc. | Aggregation of physical layer information related to a network |
US8213336B2 (en) | 2009-02-23 | 2012-07-03 | Cisco Technology, Inc. | Distributed data center access switch |
US7787480B1 (en) | 2009-03-04 | 2010-08-31 | Juniper Networks, Inc. | Routing frames in a trill network using service VLAN identifiers |
US8238340B2 (en) | 2009-03-06 | 2012-08-07 | Futurewei Technologies, Inc. | Transport multiplexer—mechanisms to force ethernet traffic from one domain to be switched in a different (external) domain |
US8155150B1 (en) | 2009-03-11 | 2012-04-10 | Juniper Networks, Inc. | Cooperative MAC learning/aging in highly distributed forwarding system |
US8665886B2 (en) | 2009-03-26 | 2014-03-04 | Brocade Communications Systems, Inc. | Redundant host connection in a routed network |
CA3204215A1 (en) | 2009-04-01 | 2010-10-07 | Nicira, Inc. | Method and apparatus for implementing and managing virtual switches |
US8213313B1 (en) | 2009-04-15 | 2012-07-03 | Tellabs Operations, Inc. | Methods and apparatus for shared layer 3 application card in multi-service router |
US8116213B2 (en) | 2009-04-24 | 2012-02-14 | Verizon Patent And Licensing Inc. | Tracing routes and protocols |
US8027354B1 (en) | 2009-04-29 | 2011-09-27 | Cisco Technology, Inc. | Network consolidation for virtualized servers |
US8874709B2 (en) | 2009-05-01 | 2014-10-28 | Futurewei Technologies, Inc. | Automatic subnet creation in networks that support dynamic ethernet-local area network services for use by operation, administration, and maintenance |
US8429647B2 (en) | 2009-05-06 | 2013-04-23 | Vmware, Inc. | Virtual machine migration across network by publishing routes to the associated virtual networks via virtual router after the start of migration of the virtual machine |
US20100287262A1 (en) | 2009-05-08 | 2010-11-11 | Uri Elzur | Method and system for guaranteed end-to-end data flows in a local networking domain |
US9282057B2 (en) | 2009-05-11 | 2016-03-08 | Brocade Communication Systems, Inc. | Flexible stacking port |
US8472443B2 (en) | 2009-05-15 | 2013-06-25 | Cisco Technology | Port grouping for association with virtual interfaces |
US8165122B2 (en) | 2009-05-26 | 2012-04-24 | Alcatel Lucent | System and method for converting unicast client requests into multicast client requests |
US8170038B2 (en) | 2009-05-27 | 2012-05-01 | International Business Machines Corporation | Two-layer switch apparatus to avoid first layer inter-switch link data traffic in steering packets through bump-in-the-wire service applications |
US8174984B2 (en) | 2009-05-29 | 2012-05-08 | Oracle America, Inc. | Managing traffic on virtualized lanes between a network switch and a virtual machine |
US7944860B2 (en) | 2009-06-04 | 2011-05-17 | Cisco Technology, Inc. | Preventing loss of network traffic due to inconsistent configurations within the network |
US8199753B2 (en) | 2009-06-05 | 2012-06-12 | Juniper Networks, Inc. | Forwarding frames in a computer network using shortest path bridging |
US8102760B2 (en) | 2009-06-30 | 2012-01-24 | Alcatel Lucent | Method for reconvergence after failure in a dual-homing network environment |
US8351352B1 (en) | 2009-07-15 | 2013-01-08 | Eastlake Iii Donald E | Methods and apparatus for RBridge hop-by-hop compression and frame aggregation |
US8204061B1 (en) | 2009-07-23 | 2012-06-19 | Cisco Technology, Inc. | Virtual port channel switches with distributed control planes |
US8125928B2 (en) | 2009-07-24 | 2012-02-28 | Juniper Networks, Inc. | Routing frames in a shortest path computer network for a multi-homed legacy bridge node |
US8341725B2 (en) | 2009-07-30 | 2012-12-25 | Calix, Inc. | Secure DHCP processing for layer two access networks |
US8503329B2 (en) | 2009-08-05 | 2013-08-06 | Cisco Technology, Inc. | Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers |
US8504690B2 (en) | 2009-08-07 | 2013-08-06 | Broadcom Corporation | Method and system for managing network power policy and configuration of data center bridging |
IL200504A0 (en) | 2009-08-20 | 2011-08-01 | Eci Telecom Ltd | Technique for dual homing interconnection between communication networks |
US8369332B2 (en) | 2009-08-21 | 2013-02-05 | Alcatel Lucent | Server-side load balancing using parent-child link aggregation groups |
US8706905B1 (en) | 2009-08-24 | 2014-04-22 | Qlogic, Corporation | Method and system for routing information in a network |
US8339994B2 (en) | 2009-08-27 | 2012-12-25 | Brocade Communications Systems, Inc. | Defining an optimal topology for a group of logical switches |
US8369347B2 (en) | 2009-09-14 | 2013-02-05 | Futurewei Technologies, Inc. | Fiber channel over Ethernet and fiber channel switching based on Ethernet switch fabrics |
US8599850B2 (en) | 2009-09-21 | 2013-12-03 | Brocade Communications Systems, Inc. | Provisioning single or multistage networks using ethernet service instances (ESIs) |
US8914598B2 (en) | 2009-09-24 | 2014-12-16 | Vmware, Inc. | Distributed storage resource scheduler and load balancer |
US8599864B2 (en) | 2009-10-08 | 2013-12-03 | Brocade Communications Systems, Inc. | Transit switches in a network of logical switches |
US20110085560A1 (en) | 2009-10-12 | 2011-04-14 | Dell Products L.P. | System and Method for Implementing a Virtual Switch |
US8693485B2 (en) | 2009-10-14 | 2014-04-08 | Dell Products, Lp | Virtualization aware network switch |
EP2497234B1 (en) | 2009-11-02 | 2018-09-19 | Marvell World Trade Ltd. | Network device and method based on virtual interfaces |
US9668230B2 (en) | 2009-11-10 | 2017-05-30 | Avago Technologies General Ip (Singapore) Pte. Ltd. | Security integration between a wireless and a wired network using a wireless gateway proxy |
US20110134802A1 (en) | 2009-12-09 | 2011-06-09 | Cisco Technology, Inc. | Determining A Routing Tree For Networks With Different Routing Protocols |
US8705513B2 (en) | 2009-12-15 | 2014-04-22 | At&T Intellectual Property I, L.P. | Methods and apparatus to communicatively couple virtual private networks to virtual machines within distributive computing networks |
WO2011074516A1 (en) | 2009-12-15 | 2011-06-23 | 日本電気株式会社 | Network system, method for controlling same, and controller |
US8270420B2 (en) | 2009-12-15 | 2012-09-18 | Hewlett-Packard Development Company, L.P. | iSCSI to FCoE gateway |
US8295291B1 (en) | 2009-12-21 | 2012-10-23 | Juniper Networks, Inc. | Computation of next hops within layer two networks |
US8161156B2 (en) | 2009-12-30 | 2012-04-17 | Verizon Patent And Licensing, Inc. | Feature delivery packets for peer-to-peer based feature network |
WO2011081020A1 (en) | 2010-01-04 | 2011-07-07 | 日本電気株式会社 | Network system, controller, network control method |
JP5493926B2 (en) | 2010-02-01 | 2014-05-14 | 日本電気株式会社 | Interface control method, interface control method, and interface control program |
US8619595B2 (en) | 2010-02-05 | 2013-12-31 | Cisco Technology, Inc. | Fault isolation in trill networks |
CN102158386B (en) | 2010-02-11 | 2015-06-03 | 威睿公司 | Distributed load balance for system management program |
US8996720B2 (en) | 2010-03-16 | 2015-03-31 | Brocade Communications Systems, Inc. | Method and apparatus for mirroring frames to a remote diagnostic system |
US8873401B2 (en) | 2010-03-16 | 2014-10-28 | Futurewei Technologies, Inc. | Service prioritization in link state controlled layer two networks |
US8369335B2 (en) | 2010-03-24 | 2013-02-05 | Brocade Communications Systems, Inc. | Method and system for extending routing domain to non-routing end stations |
US8249069B2 (en) | 2010-03-30 | 2012-08-21 | Cisco Technology, Inc. | Forwarding multi-destination packets in a network with virtual port channels |
JP5190084B2 (en) | 2010-03-30 | 2013-04-24 | 株式会社日立製作所 | Virtual machine migration method and system |
US8599854B2 (en) | 2010-04-16 | 2013-12-03 | Cisco Technology, Inc. | Method of identifying destination in a virtual environment |
US8611352B2 (en) | 2010-04-20 | 2013-12-17 | Marvell World Trade Ltd. | System and method for adapting a packet processing pipeline |
US8345692B2 (en) | 2010-04-27 | 2013-01-01 | Cisco Technology, Inc. | Virtual switching overlay for cloud computing |
US9231890B2 (en) | 2010-06-08 | 2016-01-05 | Brocade Communications Systems, Inc. | Traffic management for virtual cluster switching |
US9461840B2 (en) | 2010-06-02 | 2016-10-04 | Brocade Communications Systems, Inc. | Port profile management for virtual cluster switching |
US8625616B2 (en) | 2010-05-11 | 2014-01-07 | Brocade Communications Systems, Inc. | Converged network extension |
US8989186B2 (en) | 2010-06-08 | 2015-03-24 | Brocade Communication Systems, Inc. | Virtual port grouping for virtual cluster switching |
US8867552B2 (en) | 2010-05-03 | 2014-10-21 | Brocade Communications Systems, Inc. | Virtual cluster switching |
US8520595B2 (en) | 2010-05-04 | 2013-08-27 | Cisco Technology, Inc. | Routing to the access layer to support mobility of internet protocol devices |
US8335236B2 (en) | 2010-05-06 | 2012-12-18 | Cisco Technology, Inc. | FCoE isolated port channels and FCoE session resynchronization in vPC/MCEC environments using DCBXP |
US8503307B2 (en) | 2010-05-10 | 2013-08-06 | Hewlett-Packard Development Company, L.P. | Distributing decision making in a centralized flow routing system |
US8724456B1 (en) | 2010-05-19 | 2014-05-13 | Juniper Networks, Inc. | Network path selection for multi-homed edges to ensure end-to-end resiliency |
US8667171B2 (en) | 2010-05-28 | 2014-03-04 | Microsoft Corporation | Virtual data center allocation with bandwidth guarantees |
CA2781060C (en) | 2010-05-28 | 2016-03-08 | Huawei Technologies Co., Ltd. | Virtual layer 2 and mechanism to make it scalable |
US9806906B2 (en) | 2010-06-08 | 2017-10-31 | Brocade Communications Systems, Inc. | Flooding packets on a per-virtual-network basis |
US8446914B2 (en) | 2010-06-08 | 2013-05-21 | Brocade Communications Systems, Inc. | Method and system for link aggregation across multiple switches |
US9608833B2 (en) | 2010-06-08 | 2017-03-28 | Brocade Communications Systems, Inc. | Supporting multiple multicast trees in trill networks |
US9628293B2 (en) | 2010-06-08 | 2017-04-18 | Brocade Communications Systems, Inc. | Network layer multicasting in trill networks |
US20110299533A1 (en) | 2010-06-08 | 2011-12-08 | Brocade Communications Systems, Inc. | Internal virtual network identifier and internal policy identifier |
US10033650B2 (en) | 2010-06-08 | 2018-07-24 | Brocade Communication Systems Llc | Preserving quality of service across trill networks |
US9246703B2 (en) | 2010-06-08 | 2016-01-26 | Brocade Communications Systems, Inc. | Remote port mirroring |
US8897134B2 (en) | 2010-06-25 | 2014-11-25 | Telefonaktiebolaget L M Ericsson (Publ) | Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel |
SG10201505168TA (en) | 2010-06-29 | 2015-09-29 | Huawei Tech Co Ltd | Asymmetric network address encapsulation |
US8588081B2 (en) | 2010-07-14 | 2013-11-19 | Cisco Technology, Inc. | Monitoring a flow set to detect faults |
US8873551B2 (en) | 2010-07-30 | 2014-10-28 | Cisco Technology, Inc. | Multi-destination forwarding in network clouds which include emulated switches |
US8767735B2 (en) | 2010-08-04 | 2014-07-01 | Alcatel Lucent | System and method for multi-chassis link aggregation |
US9049098B2 (en) | 2010-08-05 | 2015-06-02 | Cisco Technology, Inc. | Discovery of services provided by application nodes in a network |
US8665267B2 (en) | 2010-09-24 | 2014-03-04 | Adobe Systems Incorporated | System and method for generating 3D surface patches from unconstrained 3D curves |
US8705502B2 (en) | 2010-10-20 | 2014-04-22 | Cisco Technology, Inc. | Using encapsulation to enable 802.1 bridging across 802.11 links |
US20120099602A1 (en) | 2010-10-25 | 2012-04-26 | Brocade Communications Systems, Inc. | End-to-end virtualization |
US8762668B2 (en) | 2010-11-18 | 2014-06-24 | Hitachi, Ltd. | Multipath switching over multiple storage systems |
US8521884B2 (en) | 2010-12-15 | 2013-08-27 | Industrial Technology Research Institute | Network system and method of address resolution |
US8806031B1 (en) | 2010-12-15 | 2014-08-12 | Juniper Networks, Inc. | Systems and methods for automatically detecting network elements |
US20120163164A1 (en) | 2010-12-27 | 2012-06-28 | Brocade Communications Systems, Inc. | Method and system for remote load balancing in high-availability networks |
US8559335B2 (en) | 2011-01-07 | 2013-10-15 | Jeda Networks, Inc. | Methods for creating virtual links between fibre channel over ethernet nodes for converged network adapters |
US8755383B2 (en) | 2011-03-21 | 2014-06-17 | Avaya, Inc. | Usage of masked ethernet addresses between transparent interconnect of lots of links (TRILL) routing bridges |
US8675433B2 (en) | 2011-03-22 | 2014-03-18 | Taiwan Semiconductor Manufacturing Company, Ltd. | Sense amplifier |
US9054999B2 (en) | 2012-05-09 | 2015-06-09 | International Business Machines Corporation | Static TRILL routing |
US8605626B2 (en) | 2011-05-18 | 2013-12-10 | Cisco Technology, Inc. | Method and apparatus for preserving extensions in multi-vendor trill networks |
US20120294192A1 (en) | 2011-05-19 | 2012-11-22 | Hitachi, Ltd. | Method and apparatus of connectivity discovery between network switch and server based on vlan identifiers |
US9497073B2 (en) | 2011-06-17 | 2016-11-15 | International Business Machines Corporation | Distributed link aggregation group (LAG) for a layer 2 fabric |
CN102232279B (en) | 2011-06-17 | 2013-09-11 | 华为技术有限公司 | Method for detecting loop position in Ethernet, and Ethernet switching device |
US9736065B2 (en) | 2011-06-24 | 2017-08-15 | Cisco Technology, Inc. | Level of hierarchy in MST for traffic localization and load balancing |
US9380132B2 (en) | 2011-06-27 | 2016-06-28 | Marvell Israel (M.I.S.L.) Ltd. | FCoE over trill |
US20130003738A1 (en) | 2011-06-29 | 2013-01-03 | Brocade Communications Systems, Inc. | Trill based router redundancy |
US8537810B2 (en) | 2011-06-29 | 2013-09-17 | Telefonaktiebolaget L M Ericsson (Publ) | E-tree using two pseudowires between edge routers with enhanced learning methods and systems |
US8559302B2 (en) | 2011-06-29 | 2013-10-15 | Fujitsu Limited | Systems and methods for distributed service protection across plug-in units |
US8467375B2 (en) | 2011-07-07 | 2013-06-18 | Ciena Corporation | Hybrid packet-optical private network systems and methods |
US8705551B2 (en) | 2011-07-27 | 2014-04-22 | Fujitsu Limited | Method and system for management of flood traffic over multiple 0:N link aggregation groups |
US20130034015A1 (en) | 2011-08-05 | 2013-02-07 | International Business Machines Corporation | Automated network configuration in a dynamic virtual environment |
US8966499B2 (en) | 2011-09-09 | 2015-02-24 | Microsoft Technology Licensing, Llc | Virtual switch extensibility |
US9185056B2 (en) | 2011-09-20 | 2015-11-10 | Big Switch Networks, Inc. | System and methods for controlling network traffic through virtual switches |
US8885643B2 (en) | 2011-11-04 | 2014-11-11 | Futurewei Technologies, Inc. | Method for multicast flow routing selection |
US8995272B2 (en) | 2012-01-26 | 2015-03-31 | Brocade Communication Systems, Inc. | Link aggregation in software-defined networks |
EP2817934A1 (en) | 2012-02-22 | 2014-12-31 | Nokia Solutions and Networks Oy | Controlling access |
US9154416B2 (en) | 2012-03-22 | 2015-10-06 | Brocade Communications Systems, Inc. | Overlay tunnel in a fabric switch |
US9184995B2 (en) | 2012-04-11 | 2015-11-10 | Gigamon Inc. | Traffic visibility in an open networking environment |
CN102801599B (en) | 2012-07-26 | 2015-09-30 | 华为技术有限公司 | A kind of communication means and system |
US8855117B2 (en) | 2012-08-08 | 2014-10-07 | Cisco Technology, Inc. | Scalable media access control protocol synchronization techniques for fabric extender based emulated switch deployments |
US9602430B2 (en) | 2012-08-21 | 2017-03-21 | Brocade Communications Systems, Inc. | Global VLANs for fabric switches |
US8937865B1 (en) | 2012-08-21 | 2015-01-20 | Juniper Networks, Inc. | Scheduling traffic over aggregated bundles of links |
-
2011
- 2011-12-06 US US13/312,903 patent/US9270572B2/en not_active Expired - Fee Related
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6064671A (en) * | 1995-12-08 | 2000-05-16 | Killian; Michael G. | Multi-homed end system for increasing computers network bandwidth |
US7061877B1 (en) * | 1999-09-10 | 2006-06-13 | Georgia Tech Reseach Corporation | System and method for providing high speed wireless media access |
US7924837B1 (en) * | 2000-07-31 | 2011-04-12 | Avaya Communication Israel Ltd. | IP multicast in VLAN environment |
US20020054593A1 (en) * | 2000-10-26 | 2002-05-09 | Tomoo Morohashi | Access network system |
US20060256767A1 (en) * | 2003-06-11 | 2006-11-16 | Nec Corporation | Router and network connecting method |
US20090092043A1 (en) * | 2007-10-03 | 2009-04-09 | Nortel Networks Limited | Providing an abstraction layer in a cluster switch that includes plural switches |
US20100272107A1 (en) * | 2007-11-26 | 2010-10-28 | Oktavian Papp | Technique for address resolution in a data transmission network |
US20110286457A1 (en) * | 2010-05-24 | 2011-11-24 | Cheng Tien Ee | Methods and apparatus to route control packets based on address partitioning |
US20110299535A1 (en) * | 2010-06-07 | 2011-12-08 | Brocade Communications Systems, Inc. | Name services for virtual cluster switching |
US20120106339A1 (en) * | 2010-11-01 | 2012-05-03 | Cisco Technology, Inc. | Probing Specific Customer Flow in Layer-2 Multipath Networks |
Cited By (161)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10673703B2 (en) | 2010-05-03 | 2020-06-02 | Avago Technologies International Sales Pte. Limited | Fabric switching |
US9942173B2 (en) | 2010-05-28 | 2018-04-10 | Brocade Communications System Llc | Distributed configuration management for virtual cluster switching |
US10419276B2 (en) | 2010-06-07 | 2019-09-17 | Avago Technologies International Sales Pte. Limited | Advanced link tracking for virtual cluster switching |
US9848040B2 (en) | 2010-06-07 | 2017-12-19 | Brocade Communications Systems, Inc. | Name services for virtual cluster switching |
US11438219B2 (en) | 2010-06-07 | 2022-09-06 | Avago Technologies International Sales Pte. Limited | Advanced link tracking for virtual cluster switching |
US10924333B2 (en) | 2010-06-07 | 2021-02-16 | Avago Technologies International Sales Pte. Limited | Advanced link tracking for virtual cluster switching |
US11757705B2 (en) | 2010-06-07 | 2023-09-12 | Avago Technologies International Sales Pte. Limited | Advanced link tracking for virtual cluster switching |
US10348643B2 (en) | 2010-07-16 | 2019-07-09 | Avago Technologies International Sales Pte. Limited | System and method for network configuration |
US10164883B2 (en) | 2011-11-10 | 2018-12-25 | Avago Technologies International Sales Pte. Limited | System and method for flow management in software-defined networks |
US20130305344A1 (en) * | 2012-05-14 | 2013-11-14 | Alcatel-Lucent India Limited | Enterprise network services over distributed clouds |
US9998365B2 (en) | 2012-05-18 | 2018-06-12 | Brocade Communications Systems, LLC | Network feedback in software-defined networks |
US9036646B2 (en) * | 2012-06-20 | 2015-05-19 | International Business Machines Corporation | Distributed routing mechanisms for a virtual switch enabled by a trill-based fabric |
US20150016462A1 (en) * | 2012-07-10 | 2015-01-15 | Hangzhou H3C Technologies Co., Ltd. | Traffic forwarding in a layer 2 edge network |
US9154419B2 (en) * | 2012-07-10 | 2015-10-06 | Hangzhou H3C Technologies Co., Ltd. | Traffic forwarding in a layer 2 edge network |
US9614759B2 (en) * | 2012-07-27 | 2017-04-04 | Dell Products L.P. | Systems and methods for providing anycast MAC addressing in an information handling system |
US20140029412A1 (en) * | 2012-07-27 | 2014-01-30 | Dell Products L.P. | Systems and methods for providing anycast mac addressing in an information handling system |
US20150215205A1 (en) * | 2012-10-11 | 2015-07-30 | Huawei Technologies Co., Ltd. | Method, Routing Bridge, and System For Sending Packet |
US9641433B2 (en) * | 2012-10-11 | 2017-05-02 | Huawei Technologies Co., Ltd. | Method, routing bridge, and system for sending packet |
US20140122704A1 (en) * | 2012-10-26 | 2014-05-01 | Hangzhou H3C Technologies Co., Ltd. | Remote port mirroring |
US10075394B2 (en) | 2012-11-16 | 2018-09-11 | Brocade Communications Systems LLC | Virtual link aggregations across multiple fabric switches |
US20140204761A1 (en) * | 2013-01-22 | 2014-07-24 | Brocade Communications Systems, Inc. | Optimizing traffic flows via dynamic routing protocol modifications when using server virtualization with dynamic routing |
US9559962B2 (en) * | 2013-01-22 | 2017-01-31 | Brocade Communications Systems, Inc. | Optimizing traffic flows via dynamic routing protocol modifications when using server virtualization with dynamic routing |
US20150365316A1 (en) * | 2013-01-23 | 2015-12-17 | Zte Corporation | Message Processing Method and System in Multi-Homing Access Overlay Network |
US10230619B2 (en) * | 2013-01-23 | 2019-03-12 | Xi'an Zhongxing New Software Co., Ltd. | Message processing method and system in multi-homing access overlay network |
US9130836B2 (en) | 2013-02-04 | 2015-09-08 | Cisco Technology, Inc. | Provisoning of a new node joining an existing cluster in a data center environment |
US9286047B1 (en) | 2013-02-13 | 2016-03-15 | Cisco Technology, Inc. | Deployment and upgrade of network devices in a network environment |
US10177977B1 (en) | 2013-02-13 | 2019-01-08 | Cisco Technology, Inc. | Deployment and upgrade of network devices in a network environment |
US10462049B2 (en) | 2013-03-01 | 2019-10-29 | Avago Technologies International Sales Pte. Limited | Spanning tree in fabric switches |
CN103200100A (en) * | 2013-03-12 | 2013-07-10 | 杭州华三通信技术有限公司 | Method and device for packet transmitting |
CN104301226A (en) * | 2013-07-16 | 2015-01-21 | 杭州华三通信技术有限公司 | Designated routing bridge (DRB) election method, equipment and system |
WO2015007178A1 (en) * | 2013-07-16 | 2015-01-22 | Hangzhou H3C Technologies Co., Ltd. | Electing designated routing bridge |
US20160142287A1 (en) * | 2013-08-02 | 2016-05-19 | Hangzhou H3C Technologies Co., Ltd. | Packet forwarding |
CN104348726A (en) * | 2013-08-02 | 2015-02-11 | 杭州华三通信技术有限公司 | Message forwarding method and device |
US10397023B2 (en) * | 2013-08-02 | 2019-08-27 | Hewlett Packard Enterprise Development Lp | Packet forwarding |
US20160149725A1 (en) * | 2013-08-02 | 2016-05-26 | Hangzhou H3C Technologies Co., Ltd. | Packet forwarding |
US9806949B2 (en) * | 2013-09-06 | 2017-10-31 | Brocade Communications Systems, Inc. | Transparent interconnection of Ethernet fabric switches |
US20150071122A1 (en) * | 2013-09-06 | 2015-03-12 | Brocade Communications Systems, Inc. | Transparent inteconnection of ethernet fabric switches |
US9912612B2 (en) | 2013-10-28 | 2018-03-06 | Brocade Communications Systems LLC | Extended ethernet fabric switches |
US9590855B2 (en) | 2013-11-18 | 2017-03-07 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Configuration of transparent interconnection of lots of links (TRILL) protocol enabled device ports in edge virtual bridging (EVB) networks |
CN104660519A (en) * | 2013-11-25 | 2015-05-27 | 华为技术有限公司 | Method and device for processing forwarding path in TRILL network |
US9571394B1 (en) * | 2014-01-10 | 2017-02-14 | Juniper Networks, Inc. | Tunneled packet aggregation for virtual networks |
US9674088B1 (en) | 2014-01-10 | 2017-06-06 | Juniper Networks, Inc. | Receive packet steering for virtual networks |
US9942148B1 (en) | 2014-01-10 | 2018-04-10 | Juniper Networks, Inc. | Tunneled packet aggregation for virtual networks |
US10355879B2 (en) | 2014-02-10 | 2019-07-16 | Avago Technologies International Sales Pte. Limited | Virtual extensible LAN tunnel keepalives |
US10581758B2 (en) | 2014-03-19 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Distributed hot standby links for vLAG |
US10476698B2 (en) | 2014-03-20 | 2019-11-12 | Avago Technologies International Sales Pte. Limited | Redundent virtual link aggregation group |
US10063473B2 (en) | 2014-04-30 | 2018-08-28 | Brocade Communications Systems LLC | Method and system for facilitating switch virtualization in a network of interconnected switches |
US10044568B2 (en) | 2014-05-13 | 2018-08-07 | Brocade Communications Systems LLC | Network extension groups of global VLANs in a fabric switch |
WO2015154421A1 (en) * | 2014-07-01 | 2015-10-15 | 中兴通讯股份有限公司 | Method, device and system for managing trill network using three-layer network manager |
US10291430B2 (en) | 2014-07-01 | 2019-05-14 | Zte Corporation | Method, device and system for managing TRILL network using three-layer network manager |
US10616108B2 (en) | 2014-07-29 | 2020-04-07 | Avago Technologies International Sales Pte. Limited | Scalable MAC address virtualization |
US10284469B2 (en) | 2014-08-11 | 2019-05-07 | Avago Technologies International Sales Pte. Limited | Progressive MAC address learning |
US10003552B2 (en) | 2015-01-05 | 2018-06-19 | Brocade Communications Systems, Llc. | Distributed bidirectional forwarding detection protocol (D-BFD) for cluster of interconnected switches |
US9942097B2 (en) | 2015-01-05 | 2018-04-10 | Brocade Communications Systems LLC | Power management in a network of interconnected switches |
CN105991446A (en) * | 2015-02-06 | 2016-10-05 | 中国移动通信集团公司 | Three-layer networking method, device and system and data processing method, device and system of TRILL network |
US10038592B2 (en) | 2015-03-17 | 2018-07-31 | Brocade Communications Systems LLC | Identifier assignment to a new switch in a switch group |
US10579406B2 (en) | 2015-04-08 | 2020-03-03 | Avago Technologies International Sales Pte. Limited | Dynamic orchestration of overlay tunnels |
US10374904B2 (en) | 2015-05-15 | 2019-08-06 | Cisco Technology, Inc. | Diagnostic network visualization |
US10693749B2 (en) | 2015-06-05 | 2020-06-23 | Cisco Technology, Inc. | Synthetic data for determining health of a network security system |
US11368378B2 (en) | 2015-06-05 | 2022-06-21 | Cisco Technology, Inc. | Identifying bogon address spaces |
US10305757B2 (en) | 2015-06-05 | 2019-05-28 | Cisco Technology, Inc. | Determining a reputation of a network entity |
US10320630B2 (en) | 2015-06-05 | 2019-06-11 | Cisco Technology, Inc. | Hierarchichal sharding of flows from sensors to collectors |
US10326673B2 (en) | 2015-06-05 | 2019-06-18 | Cisco Technology, Inc. | Techniques for determining network topologies |
US10326672B2 (en) | 2015-06-05 | 2019-06-18 | Cisco Technology, Inc. | MDL-based clustering for application dependency mapping |
US11431592B2 (en) | 2015-06-05 | 2022-08-30 | Cisco Technology, Inc. | System and method of detecting whether a source of a packet flow transmits packets which bypass an operating system stack |
US10230597B2 (en) | 2015-06-05 | 2019-03-12 | Cisco Technology, Inc. | Optimizations for application dependency mapping |
US11405291B2 (en) | 2015-06-05 | 2022-08-02 | Cisco Technology, Inc. | Generate a communication graph using an application dependency mapping (ADM) pipeline |
US11477097B2 (en) | 2015-06-05 | 2022-10-18 | Cisco Technology, Inc. | Hierarchichal sharding of flows from sensors to collectors |
US10181987B2 (en) | 2015-06-05 | 2019-01-15 | Cisco Technology, Inc. | High availability of collectors of traffic reported by network sensors |
US10177998B2 (en) | 2015-06-05 | 2019-01-08 | Cisco Technology, Inc. | Augmenting flow data for improved network monitoring and management |
US10439904B2 (en) | 2015-06-05 | 2019-10-08 | Cisco Technology, Inc. | System and method of determining malicious processes |
US10686804B2 (en) | 2015-06-05 | 2020-06-16 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10454793B2 (en) | 2015-06-05 | 2019-10-22 | Cisco Technology, Inc. | System and method of detecting whether a source of a packet flow transmits packets which bypass an operating system stack |
US11252060B2 (en) | 2015-06-05 | 2022-02-15 | Cisco Technology, Inc. | Data center traffic analytics synchronization |
US10171319B2 (en) | 2015-06-05 | 2019-01-01 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US10505828B2 (en) | 2015-06-05 | 2019-12-10 | Cisco Technology, Inc. | Technologies for managing compromised sensors in virtualized environments |
US10516586B2 (en) | 2015-06-05 | 2019-12-24 | Cisco Technology, Inc. | Identifying bogon address spaces |
US10516585B2 (en) | 2015-06-05 | 2019-12-24 | Cisco Technology, Inc. | System and method for network information mapping and displaying |
US11252058B2 (en) | 2015-06-05 | 2022-02-15 | Cisco Technology, Inc. | System and method for user optimized application dependency mapping |
US11924073B2 (en) | 2015-06-05 | 2024-03-05 | Cisco Technology, Inc. | System and method of assigning reputation scores to hosts |
US10536357B2 (en) | 2015-06-05 | 2020-01-14 | Cisco Technology, Inc. | Late data detection in data center |
US11924072B2 (en) | 2015-06-05 | 2024-03-05 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US10567247B2 (en) | 2015-06-05 | 2020-02-18 | Cisco Technology, Inc. | Intra-datacenter attack detection |
US11902122B2 (en) | 2015-06-05 | 2024-02-13 | Cisco Technology, Inc. | Application monitoring prioritization |
US10142353B2 (en) | 2015-06-05 | 2018-11-27 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US10129117B2 (en) | 2015-06-05 | 2018-11-13 | Cisco Technology, Inc. | Conditional policies |
US11902120B2 (en) | 2015-06-05 | 2024-02-13 | Cisco Technology, Inc. | Synthetic data for determining health of a network security system |
US11902121B2 (en) | 2015-06-05 | 2024-02-13 | Cisco Technology, Inc. | System and method of detecting whether a source of a packet flow transmits packets which bypass an operating system stack |
US10116530B2 (en) | 2015-06-05 | 2018-10-30 | Cisco Technology, Inc. | Technologies for determining sensor deployment characteristics |
US10623283B2 (en) | 2015-06-05 | 2020-04-14 | Cisco Technology, Inc. | Anomaly detection through header field entropy |
US10623284B2 (en) | 2015-06-05 | 2020-04-14 | Cisco Technology, Inc. | Determining a reputation of a network entity |
US10623282B2 (en) | 2015-06-05 | 2020-04-14 | Cisco Technology, Inc. | System and method of detecting hidden processes by analyzing packet flows |
US10659324B2 (en) | 2015-06-05 | 2020-05-19 | Cisco Technology, Inc. | Application monitoring prioritization |
US10116531B2 (en) | 2015-06-05 | 2018-10-30 | Cisco Technology, Inc | Round trip time (RTT) measurement based upon sequence number |
US10862776B2 (en) | 2015-06-05 | 2020-12-08 | Cisco Technology, Inc. | System and method of spoof detection |
US10243817B2 (en) | 2015-06-05 | 2019-03-26 | Cisco Technology, Inc. | System and method of assigning reputation scores to hosts |
US11153184B2 (en) | 2015-06-05 | 2021-10-19 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US11496377B2 (en) | 2015-06-05 | 2022-11-08 | Cisco Technology, Inc. | Anomaly detection through header field entropy |
US11502922B2 (en) | 2015-06-05 | 2022-11-15 | Cisco Technology, Inc. | Technologies for managing compromised sensors in virtualized environments |
US10728119B2 (en) | 2015-06-05 | 2020-07-28 | Cisco Technology, Inc. | Cluster discovery via multi-domain fusion for application dependency mapping |
US10735283B2 (en) | 2015-06-05 | 2020-08-04 | Cisco Technology, Inc. | Unique ID generation for sensors |
US10742529B2 (en) | 2015-06-05 | 2020-08-11 | Cisco Technology, Inc. | Hierarchichal sharding of flows from sensors to collectors |
US11936663B2 (en) | 2015-06-05 | 2024-03-19 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US11700190B2 (en) | 2015-06-05 | 2023-07-11 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US10797970B2 (en) | 2015-06-05 | 2020-10-06 | Cisco Technology, Inc. | Interactive hierarchical network chord diagram for application dependency mapping |
US11695659B2 (en) | 2015-06-05 | 2023-07-04 | Cisco Technology, Inc. | Unique ID generation for sensors |
US11894996B2 (en) | 2015-06-05 | 2024-02-06 | Cisco Technology, Inc. | Technologies for annotating process and user information for network flows |
US11637762B2 (en) | 2015-06-05 | 2023-04-25 | Cisco Technology, Inc. | MDL-based clustering for dependency mapping |
US11601349B2 (en) | 2015-06-05 | 2023-03-07 | Cisco Technology, Inc. | System and method of detecting hidden processes by analyzing packet flows |
US10904116B2 (en) | 2015-06-05 | 2021-01-26 | Cisco Technology, Inc. | Policy utilization analysis |
US10917319B2 (en) | 2015-06-05 | 2021-02-09 | Cisco Technology, Inc. | MDL-based clustering for dependency mapping |
US11128552B2 (en) | 2015-06-05 | 2021-09-21 | Cisco Technology, Inc. | Round trip time (RTT) measurement based upon sequence number |
US11516098B2 (en) | 2015-06-05 | 2022-11-29 | Cisco Technology, Inc. | Round trip time (RTT) measurement based upon sequence number |
US10979322B2 (en) | 2015-06-05 | 2021-04-13 | Cisco Technology, Inc. | Techniques for determining network anomalies in data center networks |
US11528283B2 (en) | 2015-06-05 | 2022-12-13 | Cisco Technology, Inc. | System for monitoring and managing datacenters |
US11522775B2 (en) | 2015-06-05 | 2022-12-06 | Cisco Technology, Inc. | Application monitoring prioritization |
US11121948B2 (en) | 2015-06-05 | 2021-09-14 | Cisco Technology, Inc. | Auto update of sensor configuration |
US11102093B2 (en) | 2015-06-05 | 2021-08-24 | Cisco Technology, Inc. | System and method of assigning reputation scores to hosts |
US10439929B2 (en) | 2015-07-31 | 2019-10-08 | Avago Technologies International Sales Pte. Limited | Graceful recovery of a multicast-enabled switch |
US10171303B2 (en) | 2015-09-16 | 2019-01-01 | Avago Technologies International Sales Pte. Limited | IP-based interconnection of switches with a logical chassis |
US9912614B2 (en) | 2015-12-07 | 2018-03-06 | Brocade Communications Systems LLC | Interconnection of switches based on hierarchical overlay tunneling |
US9917622B2 (en) | 2016-03-03 | 2018-03-13 | Andrew Wireless Systems Gmbh | Hybrid RAN/digital DAS repeater system with ethernet transport |
US11190238B2 (en) | 2016-03-03 | 2021-11-30 | Andrew Wireless Systems Gmbh | Hybrid RAN/digital DAS repeater system with ethernet transport |
WO2017149157A1 (en) * | 2016-03-03 | 2017-09-08 | Andrew Wireless Systems Gmbh | Hybrid ran/digital das repeater system with ethernet transport |
US10355753B2 (en) | 2016-03-03 | 2019-07-16 | Andrew Wireless Systems Gmbh | Hybrid RAN/digital DAS repeater system with ETHERNET transport |
CN105939216A (en) * | 2016-03-16 | 2016-09-14 | 杭州迪普科技有限公司 | Message transmission method and device |
US10708183B2 (en) | 2016-07-21 | 2020-07-07 | Cisco Technology, Inc. | System and method of providing segment routing as a service |
US11283712B2 (en) | 2016-07-21 | 2022-03-22 | Cisco Technology, Inc. | System and method of providing segment routing as a service |
US10237090B2 (en) | 2016-10-28 | 2019-03-19 | Avago Technologies International Sales Pte. Limited | Rule-based network identifier mapping |
US10972388B2 (en) | 2016-11-22 | 2021-04-06 | Cisco Technology, Inc. | Federated microburst detection |
US11088929B2 (en) | 2017-03-23 | 2021-08-10 | Cisco Technology, Inc. | Predicting application and network performance |
US10708152B2 (en) | 2017-03-23 | 2020-07-07 | Cisco Technology, Inc. | Predicting application and network performance |
US11252038B2 (en) | 2017-03-24 | 2022-02-15 | Cisco Technology, Inc. | Network agent for generating platform specific network policies |
US10523512B2 (en) | 2017-03-24 | 2019-12-31 | Cisco Technology, Inc. | Network agent for generating platform specific network policies |
US11146454B2 (en) | 2017-03-27 | 2021-10-12 | Cisco Technology, Inc. | Intent driven network policy platform |
US10764141B2 (en) | 2017-03-27 | 2020-09-01 | Cisco Technology, Inc. | Network agent for reporting to a network policy system |
US11509535B2 (en) | 2017-03-27 | 2022-11-22 | Cisco Technology, Inc. | Network agent for reporting to a network policy system |
US10250446B2 (en) | 2017-03-27 | 2019-04-02 | Cisco Technology, Inc. | Distributed policy store |
US10594560B2 (en) | 2017-03-27 | 2020-03-17 | Cisco Technology, Inc. | Intent driven network policy platform |
US11202132B2 (en) | 2017-03-28 | 2021-12-14 | Cisco Technology, Inc. | Application performance monitoring and management platform with anomalous flowlet resolution |
US10873794B2 (en) | 2017-03-28 | 2020-12-22 | Cisco Technology, Inc. | Flowlet resolution for application performance monitoring and management |
US11683618B2 (en) | 2017-03-28 | 2023-06-20 | Cisco Technology, Inc. | Application performance monitoring and management platform with anomalous flowlet resolution |
US11863921B2 (en) | 2017-03-28 | 2024-01-02 | Cisco Technology, Inc. | Application performance monitoring and management platform with anomalous flowlet resolution |
US10680887B2 (en) | 2017-07-21 | 2020-06-09 | Cisco Technology, Inc. | Remote device status audit and recovery |
US11044170B2 (en) | 2017-10-23 | 2021-06-22 | Cisco Technology, Inc. | Network migration assistant |
US10554501B2 (en) | 2017-10-23 | 2020-02-04 | Cisco Technology, Inc. | Network migration assistant |
US10523541B2 (en) | 2017-10-25 | 2019-12-31 | Cisco Technology, Inc. | Federated network and application data analytics platform |
US10904071B2 (en) | 2017-10-27 | 2021-01-26 | Cisco Technology, Inc. | System and method for network root cause analysis |
US10594542B2 (en) | 2017-10-27 | 2020-03-17 | Cisco Technology, Inc. | System and method for network root cause analysis |
US11750653B2 (en) | 2018-01-04 | 2023-09-05 | Cisco Technology, Inc. | Network intrusion counter-intelligence |
US11233821B2 (en) | 2018-01-04 | 2022-01-25 | Cisco Technology, Inc. | Network intrusion counter-intelligence |
US10574575B2 (en) | 2018-01-25 | 2020-02-25 | Cisco Technology, Inc. | Network flow stitching using middle box flow stitching |
US10798015B2 (en) | 2018-01-25 | 2020-10-06 | Cisco Technology, Inc. | Discovery of middleboxes using traffic flow stitching |
US10999149B2 (en) | 2018-01-25 | 2021-05-04 | Cisco Technology, Inc. | Automatic configuration discovery based on traffic flow data |
US10826803B2 (en) | 2018-01-25 | 2020-11-03 | Cisco Technology, Inc. | Mechanism for facilitating efficient policy updates |
US11128700B2 (en) | 2018-01-26 | 2021-09-21 | Cisco Technology, Inc. | Load balancing configuration based on traffic flow telemetry |
US11861419B2 (en) | 2018-08-23 | 2024-01-02 | Arrcus Inc. | Asynchronous object manager in a network routing environment |
US11675637B2 (en) | 2018-08-23 | 2023-06-13 | Arrcus Inc. | Host routed overlay with deterministic host learning and localized integrated routing and bridging |
US11868824B2 (en) | 2018-08-23 | 2024-01-09 | Arrcus Inc. | Single node and multiple node datastore architecture in a network routing environment |
US11693716B2 (en) | 2018-08-23 | 2023-07-04 | Arrcus Inc. | Independent datastore in a network routing environment |
US11941460B2 (en) | 2018-08-23 | 2024-03-26 | Arrcus Inc. | Host routed overlay with deterministic host learning and localized integrated routing and bridging |
Also Published As
Publication number | Publication date |
---|---|
US9270572B2 (en) | 2016-02-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9270572B2 (en) | Layer-3 support in TRILL networks | |
US9019976B2 (en) | Redundant host connection in a routed network | |
US9112817B2 (en) | Efficient TRILL forwarding | |
US9887916B2 (en) | Overlay tunnel in a fabric switch | |
CN108476160B (en) | switch interconnect based on layered overlay tunneling | |
US8369335B2 (en) | Method and system for extending routing domain to non-routing end stations | |
US9143445B2 (en) | Method and system for link aggregation across multiple switches | |
US20130003738A1 (en) | Trill based router redundancy | |
US9742693B2 (en) | Dynamic service insertion in a fabric switch | |
US10581758B2 (en) | Distributed hot standby links for vLAG | |
US10075394B2 (en) | Virtual link aggregations across multiple fabric switches | |
US20120163164A1 (en) | Method and system for remote load balancing in high-availability networks | |
US9806949B2 (en) | Transparent interconnection of Ethernet fabric switches |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BROCADE COMMUNICATIONS SYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KOGANTI, PHANIDHAR;GHANWANI, ANOOP;VOBBILISETTY, SURESH;AND OTHERS;SIGNING DATES FROM 20120105 TO 20120202;REEL/FRAME:027739/0258 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: BROCADE COMMUNICATIONS SYSTEMS LLC, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:BROCADE COMMUNICATIONS SYSTEMS, INC.;REEL/FRAME:044891/0536 Effective date: 20171128 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED, SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROCADE COMMUNICATIONS SYSTEMS LLC;REEL/FRAME:047270/0247 Effective date: 20180905 Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROCADE COMMUNICATIONS SYSTEMS LLC;REEL/FRAME:047270/0247 Effective date: 20180905 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20200223 |