Búsqueda Imágenes Maps Play YouTube Noticias Gmail Drive Más »
Iniciar sesión
Usuarios de lectores de pantalla: deben hacer clic en este enlace para utilizar el modo de accesibilidad. Este modo tiene las mismas funciones esenciales pero funciona mejor con el lector.

Patentes

  1. Búsqueda avanzada de patentes
Número de publicaciónUS9270572 B2
Tipo de publicaciónConcesión
Número de solicitudUS 13/312,903
Fecha de publicación23 Feb 2016
Fecha de presentación6 Dic 2011
Fecha de prioridad2 May 2011
También publicado comoUS20120281700
Número de publicación13312903, 312903, US 9270572 B2, US 9270572B2, US-B2-9270572, US9270572 B2, US9270572B2
InventoresPhanidhar Koganti, Anoop Ghanwani, Suresh Vobbilisetty, Rajiv Krishnamurthy, Nagarajan Venkatesan, Shunjia Yu
Cesionario originalBrocade Communications Systems Inc.
Exportar citaBiBTeX, EndNote, RefMan
Enlaces externos: USPTO, Cesión de USPTO, Espacenet
Layer-3 support in TRILL networks
US 9270572 B2
Resumen
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 corresponds to a local RBridge identifier assigned to the switch; and (3) an outer destination MAC address corresponds to the local MAC address.
Imágenes(14)
Previous page
Next page
Reclamaciones(20)
What is claimed is:
1. A switch, comprising:
layer-2 processing circuitry configured to determine that:
outer and inner destination media access control (MAC) addresses of a packet correspond to a MAC address assigned to the switch, wherein the packet is encapsulated with an inner Ethernet header, a routable header, and an outer Ethernet header;
encapsulation circuitry configured to determine that:
a destination switch identifier of the routable header corresponds to a switch identifier assigned to the switch, wherein the routable header is placed between the outer and inner Ethernet headers;
Internet Protocol (IP) processing circuitry configured to lookup a destination IP address of a layer-3 header of the packet in a local layer-3 forwarding table in the switch, wherein the layer-3 header is distinct from the routable header, and wherein the destination IP address is a virtual IP address assigned to a virtual IP router, which is formed based on the switch in conjunction with at least another physical switch to operate as a single router; and
forwarding circuitry configured to determine an output port and construct a new header for the packet based on looking up the destination IP address in the local layer-3 forwarding table.
2. The switch of claim 1, wherein the layer-2 processing circuitry is further configured to determine a first virtual local area network (VLAN) tag in the inner Ethernet header; and
wherein the new header includes a new inner Ethernet header comprising a second VLAN tag.
3. The switch of claim 1, wherein the switch is a member of a network of interconnected switches, wherein the network of interconnected switches is controlled as a single logical switch.
4. The switch of claim 1, further comprising switching circuitry configured to switch the packet between VLANs based on the destination IP address.
5. The switch of claim 1, wherein the destination switch identifier is a virtual switch identifier; and
wherein the virtual IP router is associated with the virtual switch identifier.
6. The switch of claim 1, wherein the IP processing circuitry is further configured to map the virtual IP address to a virtual media access control (MAC) address.
7. The switch of claim 1, further comprising Address Resolution Protocol (ARP) circuitry configured to generate an ARP response for an IP address assigned to the switch, wherein the ARP response comprises a MAC address assigned to the switch.
8. A method, comprising:
determining that:
outer and inner destination media access control (MAC) addresses of a packet correspond to a MAC address assigned to a switch, wherein the packet is encapsulated with an inner Ethernet header, a routable header, and an outer Ethernet header; and
a destination switch identifier of the routable header corresponds to a switch identifier assigned to the switch, wherein the routable header is placed between the outer and inner Ethernet headers;
looking up a destination Internet Protocol (IP) address of a layer-3 header of the packet in a local layer-3 forwarding table in the switch, wherein the layer-3 header is distinct from the routable header, and wherein the destination IP address is a virtual IP address assigned to a virtual IP router, which is formed based on the switch in conjunction with at least another physical switch to operate as a single router; and
determining an output port and constructing a new header for the packet based on looking up the destination IP address in the local layer-3 forwarding table.
9. The method of claim 8, further comprising:
determining a first virtual local area network (VLAN) tag in the inner Ethernet header; and
including in the new header a new inner Ethernet header comprising a second VLAN tag.
10. The method of claim 8, wherein the switch is a member of a network of interconnected switches wherein the network of interconnected switches is controlled as a single logical switch.
11. The method of claim 8, further comprising switching the packet between VLANs based on the destination IP address.
12. The method of claim 8, wherein the destination switch identifier is a virtual switch identifier; and
wherein the virtual IP router is associated with the virtual switch identifier.
13. The method of claim 8, further comprising mapping the virtual IP address to a virtual media access control (MAC) address.
14. The method of claim 8, further comprising generating an Address Resolution Protocol (ARP) response for an IP address assigned to the switch, wherein the ARP response comprises a MAC address assigned to the switch.
15. A computing system, comprising:
a processor; and
a non-transitory computer-readable storage medium storing instructions which when executed by the processor causes the processor to perform a method, the method comprising:
determining that:
outer and inner destination media access control (MAC) addresses of a packet correspond to a MAC address assigned to the computing system, wherein the packet is encapsulated with an inner Ethernet header, a routable header, and an outer Ethernet header; and
a destination switch identifier of the routable header corresponds to a switch identifier is assigned to the computing system;
looking up a destination Internet Protocol (IP) address of a layer-3 header of the packet in a local layer-3 forwarding table in the computing system, wherein the layer-3 header is distinct from the routable header and wherein the destination IP address is a virtual IP address assigned to a virtual IP router, which is formed based on the switch in conjunction with at least another physical switch to operate as a single router; and
determining an output port and constructing a new header for the packet based on looking up the destination IP address in the local-layer-3 forwarding table.
16. The computing system of claim 15, within the method further comprises:
determining a first virtual local area network (VLAN) tag in the inner Ethernet header; and
including in the new header a new inner Ethernet header comprising a second VLAN tag.
17. The computing system of claim 15, wherein the computing system is a member of a network of interconnected switches, wherein the network of interconnected switches is controlled as a single logical switch.
18. The computing system of claim 15,
wherein the destination switch identifier is a virtual switch identifier; and
wherein the virtual IP router is associated with the virtual switch identifier.
19. The computing system of claim 15, wherein the method further comprises generating an Address Resolution Protocol (ARP) response for an IP address assigned to the computing system, wherein the ARP response comprises a MAC address assigned to the computing system.
20. The computing system of claim 15, whether the method further comprises switching the packet between VLANs based on the destination IP address.
Descripción
RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 61/481,643, 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, 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, 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, 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.

BACKGROUND

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.

SUMMARY

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.

BRIEF DESCRIPTION OF THE FIGURES

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.

DETAILED DESCRIPTION

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.

Overview

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.

Network Architecture

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 in FIG. 1, 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. For example, 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. Similarly, 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. For example, 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. For example, 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.

In FIG. 1, end device 128 is directly coupled to RBridge 103. Hence, 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. On the other hand, 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. Under such a scenario, 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.

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 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.

In embodiments of the present invention, as illustrated in FIG. 1, each frame destined to end device 122 from end device 128, wherein the end devices are on different VLANs, is received at RBridge 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 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, in turn, transmits the frame to end device 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.

Routine Across VLANs

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, a TRILL network 200 includes TRILL RBridges 220 and 230. End device 202 is coupled to RBridge 220 over VLAN 212, and end device 204 is coupled to RBridge 220 over VLAN 214.

In the example in FIG. 2A, 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. 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, in turn, receives the frame and removes its layer-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. In this example, a TRILL network 200 includes TRILL RBridges 220 and 230. End device 202 is coupled to RBridge 220 over VLAN 212, and end device 204 is coupled to RBridge 220 over VLAN 214.

In the example in FIG. 2B, 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. Under such a scenario, 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. Note that, if end device 202 has no knowledge of IP router 225's MAC address, end device 202 obtains the IP address of router 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 VLAN tag corresponding VLAN 214, and forwards it to end device 204 via egress RBridge 220. As the cross-layer-2-domain frame does not need to traverse through TRILL network 200, IP-processing capability at RBridge 220 thereby reduces the bandwidth usage in network 200.

Distributed Layer-3 Processing

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 in FIG. 3A, 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.

In some embodiments, a layer-3 interface on an RBridge corresponding to a VLAN is a Switch Virtual Interface (SVI). For example, 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. End device 318 then forwards the frame to 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.

However, when end device 311 sends a frame to end device 317, 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. As a result, 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. 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. In this example, 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.

In this example, if end device 317 sends a frame to end device 318, 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.

Frame Processing

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 in FIG. 4B is also applicable to embodiments with distributed layer-3 processing, as described in conjunction with FIG. 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 with FIG. 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.

Virtual Switch Formation

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 in FIG. 5, 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. For example, 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. Similarly, 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. Similarly, 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.

In embodiments of the present invention, as illustrated in FIG. 1, 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. Because 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. Hence, 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. In this example, 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. For example, 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.

Also included in network 600 are RBridges 622 and 624, which 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. Furthermore, 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.

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 to VLAN 692, and 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. For 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.

Note that in one embodiment, 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.

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 in TRILL 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 with FIG. 3B. For example, 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.

In some embodiments, 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.

ARP and Frame Processing in a Virtual Switch

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.

Failure Handling

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 a TRILL network 800, RBridges 811, 812, and 813 form a virtual RBridge 840, and 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. Hence, all frames destined to network 880 from end device 870 have the virtual MAC address assigned to virtual IP router 850 as the destination MAC address. Note that these frames can be forwarded by gateway RBridges 811, 812, and 813 for load balancing. Gateway RBridges 811, 812, and 813 also provide redundancy among each other to handle failures.

Suppose that a failure 864 occurs to link 831 adjacent to gateway RBridge 811. As a result, 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).

Suppose that a failure 862 occurs during operation that fails link 836 adjacent to IP router 821. Consequently, IP router 821 is disconnected from network 880 and is incapable of forwarding frames to network 880. Under such a scenario, IP router 821 is removed from virtual IP router 850. As a result, IP router 821 stops operating as a layer-3 gateway router for end device 870. However, gateway RBridge 811 still remains connected to network 800 and continues to operate as a regular TRILL RBridge. As 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. Hence, all frames from end device 870 to network 880 are then distributed among gateway RBridges 812 and 813.

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 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.

Suppose that a node failure 866 occurs at gateway RBridge 811 (and essentially IP router 821 as they are the same physical device). As a result, 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. Under such a scenario, IP router 821 is removed from virtual IP router 850 and gateway RBridge 811 is removed from virtual RBridge 840. As a result, IP router 821 stops operating as a layer-3 gateway node. Furthermore, gateway RBridge 811 is disconnected from network 800 and removed from all TRILL routes in network 800.

With failure 866, as virtual IP router 850 still operates as a default gateway for end device 870, routers 822 and 823 continue operating as layer-3 gateway nodes for end device 870. Hence, all frames from end device 870 to network 880 are distributed between gateway RBridges 812 and 813. Furthermore, if 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.

Exemplary Switch System

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, 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.

During operation, 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.

In some embodiments, 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.

Furthermore, 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.

In some embodiments, 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.

In some embodiments, 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. In some embodiments, logical switch 942 can be configured to operate in conjunction with Ethernet 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.

Citas de patentes
Patente citada Fecha de presentación Fecha de publicación Solicitante Título
US539017322 Oct 199214 Feb 1995Digital Equipment CorporationPacket format in hub for packet data communications system
US580227823 Ene 19961 Sep 19983Com CorporationBridge/router architecture for high performance scalable networking
US587823227 Dic 19962 Mar 1999Compaq Computer CorporationDynamic reconfiguration of network device's virtual LANs using the root identifiers and root ports determined by a spanning tree procedure
US595996830 Jul 199728 Sep 1999Cisco Systems, Inc.Port aggregation protocol
US59732787 May 199826 Oct 1999Eaton CorporationSnap acting charge/discharge and open/closed indicators displaying states of electrical switching apparatus
US598327819 Abr 19969 Nov 1999Lucent Technologies Inc.Low-loss, fair bandwidth allocation flow control in a packet switch
US604104227 May 199721 Mar 2000Cabletron Systems, Inc.Remote port mirroring system and method thereof
US6064671 *8 Dic 199516 May 2000Killian; Michael G.Multi-homed end system for increasing computers network bandwidth
US608523822 Abr 19974 Jul 2000Matsushita Electric Works, Ltd.Virtual LAN system
US610469630 Jun 199915 Ago 2000Broadcom CorporationMethod for sending packets between trunk ports of network switches
US618521411 Sep 19976 Feb 20013Com CorporationUse of code vectors for frame forwarding in a bridge/router
US618524129 Oct 19986 Feb 2001Xerox CorporationMetal spatial filter to enhance model reflectivity in a vertical cavity surface emitting laser
US643810622 Dic 199820 Ago 2002Nortel Networks LimitedInter-class schedulers utilizing statistical priority guaranteed queuing and generic cell-rate algorithm priority guaranteed queuing
US649878113 Ago 199924 Dic 2002International Business Machines CorporationSelf-tuning link aggregation system
US654226624 Jun 19991 Abr 2003Qwest Communications International Inc.System and method for providing broadband data service
US663376111 Ago 200014 Oct 2003Reefedge, Inc.Enabling seamless user mobility in a short-range wireless networking environment
US677161012 Oct 19993 Ago 20043Com CorporationSpanning tree with protocol for bypassing port state transition timers
US687360220 Jul 200029 Mar 2005Fujitsu LimitedNetwork system, switch, and server
US693757617 Oct 200030 Ago 2005Cisco Technology, Inc.Multiple instance spanning tree protocol
US695682414 Jun 200118 Oct 2005Tropic Networks Inc.Extension of link aggregation protocols over the network
US69572693 Ene 200118 Oct 2005Advanced Micro Devices, Inc.Method and apparatus for performing priority-based flow control
US697558112 Nov 200213 Dic 2005Marvell Semiconductor Israel Ltd.VLAN protocol
US69758649 Jun 200313 Dic 2005Symantec CorporationSeamless user mobility in a short-range wireless networking environment
US701635223 Mar 200121 Mar 2006Advanced Micro Devices, Inc.Address modification within a switching device in a packet-switched network
US7061877 *8 Sep 200013 Jun 2006Georgia Tech Reseach CorporationSystem and method for providing high speed wireless media access
US717393418 Abr 20026 Feb 2007Nortel Networks LimitedSystem, device, and method for improving communication network reliability using trunk splitting
US71973081 Ago 200527 Mar 2007Symantec CorporationEnabling seamless user mobility in a short-range wireless networking environment
US720628812 Jun 200217 Abr 2007Cisco Technology, Inc.Methods and apparatus for characterizing a route in fibre channel fabric
US73106646 Feb 200418 Dic 2007Extreme NetworksUnified, configurable, adaptive, network architecture
US73136375 Dic 200325 Dic 2007Hitachi, Ltd.Fabric and method for sharing an I/O device among virtual machines formed in a computer system
US731554529 Mar 20021 Ene 2008Nortel Networks LimitedMethod and apparatus to support differential internet data packet treatment in a base station controller
US73160316 Sep 20021 Ene 2008Capital One Financial CorporationSystem and method for remotely monitoring wireless networks
US73308979 Jul 200212 Feb 2008International Business Machines CorporationMethods and apparatus for storage area network component registration
US73800257 Oct 200327 May 2008Cisco Technology, Inc.Method and apparatus providing role-based configuration of a port of a network element
US739779421 Nov 20028 Jul 2008Juniper Networks, Inc.Systems and methods for implementing virtual switch planes in a physical switch fabric
US743016414 Ago 200230 Sep 2008Hewlett-Packard Development Company, L.P.Path recovery on failure in load balancing switch protocols
US745388827 Ago 200218 Nov 2008Alcatel LucentStackable virtual local area network provisioning in bridged networks
US747789423 Feb 200413 Ene 2009Foundry Networks, Inc.Methods and apparatus for handling wireless roaming among and across wireless area networks
US74802583 Jul 200320 Ene 2009Cisco Technology, Inc.Cross stack rapid transition protocol
US750875716 Sep 200524 Mar 2009Alcatel LucentNetwork with MAC table overflow protection
US75581952 Abr 20077 Jul 2009Foundry Networks, Inc.System and method for providing network route redundancy across layer 2 devices
US755827323 Dic 20037 Jul 2009Extreme Networks, Inc.Methods and systems for associating and translating virtual local area network (VLAN) tags
US757144720 Jun 20054 Ago 2009International Business Machines CorporationLoose coupling of web services
US75999016 Dic 20066 Oct 2009Microsoft CorporationProcessing data-centric business models
US768873623 Sep 200330 Mar 2010Marvell International LtdNetwork switch with quality of service flow control
US768896026 Feb 200230 Mar 2010Sprint Communications Company L.P.Method and system for separating business and device logic in a computing network system
US76900408 Mar 200530 Mar 2010Enterasys Networks, Inc.Method for network traffic mirroring with data privacy
US770625529 Ene 200727 Abr 2010Solace Systems, Inc.Communications apparatus with redundant switching or backpressure mechanism
US771637024 Ene 200711 May 2010Foundry Networks, Inc.Redundancy support for network address translation (NAT)
US77200761 Mar 200418 May 2010Enterasys, Inc.Distributed connection-oriented services for switched communication networks
US77292967 Sep 20071 Jun 2010Force 10 Networks, Inc.Distributed BPDU processing for spanning tree protocols
US77874804 Mar 200931 Ago 2010Juniper Networks, Inc.Routing frames in a trill network using service VLAN identifiers
US77929202 May 20057 Sep 2010Vulcan Inc.Network-accessible control of one or more media devices
US779659328 Ene 200814 Sep 2010Juniper Networks, Inc.Router using internal flood groups for flooding VPLS traffic
US780899230 Dic 20045 Oct 2010Cisco Technology, Inc.Platform independent implementation of private VLANS
US783633218 Jul 200716 Nov 2010Hitachi, Ltd.Method and apparatus for managing virtual ports on storage systems
US784390622 Oct 200530 Nov 2010Habanero Holdings, Inc.Storage gateway initiator for fabric-backplane enterprise servers
US784390722 Oct 200530 Nov 2010Habanero Holdings, Inc.Storage gateway target for fabric-backplane enterprise servers
US786009712 Feb 200528 Dic 2010Habanero Holdings, Inc.Fabric-backplane enterprise servers with VNICs and VLANs
US789895930 Jun 20081 Mar 2011Marvell Israel (Misl) Ltd.Method for weighted load-balancing among network interfaces
US7924837 *31 Jul 200012 Abr 2011Avaya Communication Israel Ltd.IP multicast in VLAN environment
US793775619 Ago 20053 May 2011Cpacket Networks, Inc.Apparatus and method for facilitating network security
US79459411 Jun 200717 May 2011Cisco Technology, Inc.Flexible access control policy enforcement
US794963830 Mar 201024 May 2011Netapp, Inc.System and method for nearly in-band search indexing
US795738614 Abr 20097 Jun 2011Juniper Networks, Inc.Inter-autonomous system (AS) multicast virtual private networks
US801893819 Dic 200613 Sep 2011World Wide Packets, Inc.Translating between a switching format and a transport format
US802735429 Abr 200927 Sep 2011Cisco Technology, Inc.Network consolidation for virtualized servers
US805483230 Dic 20088 Nov 2011Juniper Networks, Inc.Methods and apparatus for routing between virtual resources based on a routing location policy
US806844224 Nov 200829 Nov 2011Juniper Networks, Inc.Spanning tree protocol synchronization within virtual private networks
US807870412 Abr 200713 Dic 2011Hewlett-Packard Development Company, L.P.Provisioning of a service environment using web services
US810278131 Jul 200824 Ene 2012Cisco Technology, Inc.Dynamic distribution of virtual machines in a communication network
US810279125 Jul 200824 Ene 2012Newport Media, Inc.Interleaver address generation in turbo decoders for mobile multimedia multicast system communication systems
US811630723 Sep 200414 Feb 2012Juniper Networks, Inc.Packet structure for mirrored traffic flow
US812592824 Jul 200928 Feb 2012Juniper Networks, Inc.Routing frames in a shortest path computer network for a multi-homed legacy bridge node
US813492212 Sep 200813 Mar 2012Cisco Technology, Inc.Reducing flooding in a bridged network
US815515011 Mar 200910 Abr 2012Juniper Networks, Inc.Cooperative MAC learning/aging in highly distributed forwarding system
US816006325 Mar 200917 Abr 2012Microsoft CorporationData center interconnect and traffic engineering
US81600808 May 200617 Abr 2012Marvell Israel (M.I.S.L.) Ltd.Implementation of reliable synchronization of distributed databases
US817003827 May 20091 May 2012International Business Machines CorporationTwo-layer switch apparatus to avoid first layer inter-switch link data traffic in steering packets through bump-in-the-wire service applications
US819467419 Dic 20085 Jun 2012Quest Software, Inc.System and method for aggregating communications and for translating between overlapping internal network addresses and unique external network addresses
US819577423 May 20085 Jun 2012Vmware, Inc.Distributed virtual switch for virtualized computer systems
US820406123 Jul 200919 Jun 2012Cisco Technology, Inc.Virtual port channel switches with distributed control planes
US821331315 Abr 20093 Jul 2012Tellabs Operations, Inc.Methods and apparatus for shared layer 3 application card in multi-service router
US821333623 Feb 20093 Jul 2012Cisco Technology, Inc.Distributed data center access switch
US82300694 Mar 200824 Jul 2012International Business Machines CorporationServer and storage-aware method for selecting virtual machine migration targets
US823996026 Mar 20107 Ago 2012Enterasys Networks, Inc.Method for network traffic mirroring with data privacy
US824906930 Mar 201021 Ago 2012Cisco Technology, Inc.Forwarding multi-destination packets in a network with virtual port channels
US82704013 Abr 200318 Sep 2012Cisco Technology, Inc.Packet routing and switching device
US829529121 Dic 200923 Oct 2012Juniper Networks, Inc.Computation of next hops within layer two networks
US82959213 Ago 200623 Oct 2012De Montfort UniversityApparatus and method for non-contact electrical impedance imaging
US830168617 Dic 200730 Oct 2012Citrix Systems, Inc.Systems and methods for decentralized computing
US833999427 Ago 200925 Dic 2012Brocade Communications Systems, Inc.Defining an optimal topology for a group of logical switches
US835135214 Jul 20108 Ene 2013Eastlake Iii Donald EMethods and apparatus for RBridge hop-by-hop compression and frame aggregation
US836933524 Mar 20105 Feb 2013Brocade Communications Systems, Inc.Method and system for extending routing domain to non-routing end stations
US836934714 Sep 20095 Feb 2013Futurewei Technologies, Inc.Fiber channel over Ethernet and fiber channel switching based on Ethernet switch fabrics
US839249621 Dic 20095 Mar 2013Watchguard Technologies, Inc.Cluster architecture for network security processing
US846277420 Ene 201111 Jun 2013Alcatel LucentVirtual IP interfaces on multi-chassis link aggregates
US846577413 Feb 200618 Jun 2013Purdue Pharma L.P.Sequestered antagonist formulations
US84673757 Jul 201118 Jun 2013Ciena CorporationHybrid packet-optical private network systems and methods
US85205954 May 201027 Ago 2013Cisco Technology, Inc.Routing to the access layer to support mobility of internet protocol devices
US85998507 Ene 20103 Dic 2013Brocade Communications Systems, Inc.Provisioning single or multistage networks using ethernet service instances (ESIs)
US85998648 Oct 20093 Dic 2013Brocade Communications Systems, Inc.Transit switches in a network of logical switches
US861500811 Jul 200724 Dic 2013Foundry Networks LlcDuplicating network traffic through transparent VLAN flooding
US870690519 Ago 201022 Abr 2014Qlogic, CorporationMethod and system for routing information in a network
US872445614 Sep 201013 May 2014Juniper Networks, Inc.Network path selection for multi-homed edges to ensure end-to-end resiliency
US880603115 Dic 201012 Ago 2014Juniper Networks, Inc.Systems and methods for automatically detecting network elements
US882638515 Abr 20082 Sep 2014Hewlett-Packard Development Company, L.P.Method and apparatus for access security services
US893786527 Sep 201220 Ene 2015Juniper Networks, Inc.Scheduling traffic over aggregated bundles of links
US2001000552731 Mar 199728 Jun 2001Kathleen Michelle VaethThin film fabrication
US2001005527422 Feb 200127 Dic 2001Doug HeggeSystem and method for flow mirroring in a network switch
US2002001990411 May 200114 Feb 2002Katz Abraham YehudaThree-dimensional switch providing packet routing between multiple multimedia buses
US2002002170122 Dic 200021 Feb 2002Lavian Tal I.Dynamic assignment of traffic classes to a priority queue in a packet forwarding device
US2002003935023 Ago 20014 Abr 2002Zarlink Semiconductor V.N. Inc.Buffer management for support of quality-of-service guarantees and data flow control in data switching
US20020054593 *25 Oct 20019 May 2002Tomoo MorohashiAccess network system
US200200917955 Ene 200111 Jul 2002Michael YipMethod and system of aggregate multiple VLANs in a metropolitan area network
US2003004108510 May 200227 Feb 2003Kazuhiko SatoManagement system and method for network devices using information recordable medium
US200301233933 Ene 20023 Jul 2003Feuerstraeter Mark T.Method and apparatus for priority based flow control in an ethernet architecture
US200301747064 Mar 200318 Sep 2003Broadcom CorporationFastpath implementation for transparent local area network (LAN) services over multiprotocol label switching (MPLS)
US200301899054 Jun 20029 Oct 2003Accton Technology CorporationMethod of setting network configuration and device and system thereof
US2003021614328 Feb 200320 Nov 2003Roese John J.Location discovery in a data network
US2004000143318 Jul 20011 Ene 2004Gram Charles AndrewInteractive control of network devices
US2004000309418 Jun 20031 Ene 2004Michael SeeMethod and apparatus for mirroring traffic over a network
US200400106009 Jul 200215 Ene 2004Baldwin Duane MarkMethods and apparatus for storage area network component registration
US200400496996 Sep 200211 Mar 2004Capital One Financial CorporationSystem and method for remotely monitoring wireless networks
US2004005743030 Jun 200325 Mar 2004Ssh Communications Security Corp.Transmission of broadcast packets in secure communication connections between computers
US2004011750820 Feb 200217 Jun 2004Keiichi ShimizuMobile body network
US2004012032630 May 200324 Jun 2004Hyeon-Sik YoonSystem and method for VLAN configuration of E-PON, and recording medium with stored program thereof
US200401563133 Feb 200412 Ago 2004Hofmeister Ralph TheodoreMethod and apparatus for performing data flow ingress/egress admission control in a provider network
US2004016559525 Feb 200326 Ago 2004At&T Corp.Discovery and integrity testing method in an ethernet domain
US200401655961 Ago 200126 Ago 2004Garcia Javier RomeroApparatus and method for flow scheduling based on priorities in a mobile network
US2004021323227 Abr 200428 Oct 2004Alcatel Ip Networks, Inc.Data mirroring in a service
US2005000795111 Jul 200313 Ene 2005Roger LapuhRouted split multilink trunking
US2005004419922 Sep 200324 Feb 2005Kenta ShigaStorage network management system and method
US2005007400112 Nov 20027 Abr 2005Cisco Technology, Inc.System and method for local packet transport services within distributed routers
US2005009456831 Oct 20035 May 2005Josh JuddNetwork path tracing method
US2005009463031 Oct 20035 May 2005Ezio ValdevitNetwork path tracing method
US2005012297915 Nov 20049 Jun 2005David GrossSystem and method for traversing metadata across multiple network domains at various layers of the protocol stack
US2005015764515 Jun 200421 Jul 2005Sameh RabieEthernet differentiated services
US200501577519 Dic 200421 Jul 2005Sameh RabieMethod and system for ethernet and frame relay network interworking
US2005016918812 Jun 20024 Ago 2005Andiamo Systems, Inc.Methods and apparatus for characterizing a route in a fibre channel fabric
US2005019581323 Feb 20058 Sep 2005Sinett CorporationUnified architecture for wired and wireless networks
US2005020742317 May 200522 Sep 2005Broadcom CorporationApparatus and method for managing memory in a network switch
US2005021356126 May 200529 Sep 2005Maxxan Systems, Inc.System, apparatus and method for address forwarding for a computer network
US200502200966 Abr 20046 Oct 2005Robert FriskneyTraffic engineering in frame-based carrier networks
US200502653563 Feb 20051 Dic 2005Fujitsu LimitedMethod and apparatus for keeping track of virtual LAN topology in network of nodes
US200502785658 Mar 200515 Dic 2005Enterasys Networks, Inc.Method for network traffic mirroring with data privacy
US2006000786928 Dic 200412 Ene 2006Fujitsu LimitedMethod for preventing control packet loop and bridge apparatus using the method
US2006001830221 Jul 200526 Ene 2006AlcatelLocal area network with one or more virtual groups of core equipments appropriate for layer 2 switching
US2006002370730 Jul 20042 Feb 2006Makishima Dennis HSystem and method for providing proxy and translation domains in a fibre channel router
US200600342927 Oct 200516 Feb 2006Koji WakayamaApparatus and method for interworking between MPLS network and non-MPLS network
US2006005916319 Ago 200516 Mar 2006Enterasys Networks, Inc.System, method and apparatus for traffic mirror setup, service and security in communication networks
US200600621871 Jul 200323 Mar 2006Johan RuneIsolation of hosts connected to an access network
US200600725506 Oct 20046 Abr 2006Davis Thomas CProviding CALEA/LegaI Intercept information to law enforcement agencies for internet protocol multimedia subsystems (IMS)
US2006008325416 Sep 200520 Abr 2006An GeNetwork with MAC table overflow protection
US2006009858914 Jun 200511 May 2006Cisco Technology, Inc.Forwarding table reduction and multipath network forwarding
US2006014013030 Nov 200529 Jun 2006Broadcom CorporationMirroring in a network device
US2006016810912 Nov 200427 Jul 2006Brocade Communications Systems, Inc.Methods, devices and systems with improved zone merge operation by operating on a switch basis
US2006018493711 Feb 200517 Ago 2006Timothy AbelsSystem and method for centralized software management in virtual machines
US200602219601 Abr 20055 Oct 2006Gaetano BorgionePerforming extended lookups on mac-based tables
US2006023599523 Feb 200619 Oct 2006Jagjeet BhatiaMethod and system for implementing a high availability VLAN
US2006024231119 Jun 200626 Oct 2006Khanh MaiVirtual multicasting
US2006024543928 Abr 20052 Nov 2006Cisco Technology, Inc.System and method for DSL subscriber identification over ethernet network
US200602510676 Abr 20069 Nov 2006Cisco Technology, Inc., A Corporation Of CaliforniaFibre channel over ethernet
US20060256767 *10 Jun 200416 Nov 2006Nec CorporationRouter and network connecting method
US2006026551527 Jul 200623 Nov 2006Hitachi, Ltd.Storage network management system and method
US2006028549914 Jun 200621 Dic 2006Broadcom CorporationLoop detection for a network device
US200602913881 Sep 200628 Dic 2006F5 Networks, Inc.Method and system for scaling network traffic managers
US200700361782 Feb 200615 Feb 2007Susan HaresLayer 2 virtual switching environment
US2007008362529 Sep 200512 Abr 2007Mcdata CorporationFederated management of intelligent service modules
US2007008636215 Dic 200619 Abr 2007Oki Electric Industry Co., Ltd.Network management method and communications network system
US2007009446421 Oct 200526 Abr 2007Cisco Technology, Inc. A Corporation Of CaliforniaMirror consistency checking techniques for storage area networks and network based virtualization
US2007009796818 Oct 20063 May 2007Wenhua DuBridge forwarding method and apparatus
US200700980061 Nov 20053 May 2007Nortel Networks LimitedMultilink trunking for encapsulated traffic
US2007011622428 Oct 200524 May 2007Burke Paul MService chaining
US2007011642226 Ene 200624 May 2007Reynolds Thomas APhotoresponsive polyimide based fiber
US2007015665922 Dic 20065 Jul 2007Blue JungleTechniques and System to Deploy Policies Intelligently
US200701775252 Feb 20062 Ago 2007Ijsbrand WijnandsRoot node redundancy for multipoint-to-multipoint transport trees
US200701775972 Feb 20062 Ago 2007Yu JuEthernet connection-based forwarding process
US200701833138 Feb 20069 Ago 2007Narayanan Manoj TSystem and method for detecting and recovering from virtual switch link failures
US2007021171213 Mar 200613 Sep 2007Nortel Networks LimitedModular scalable switch architecture
US200702584495 May 20068 Nov 2007Broadcom Corporation, A California CorporationPacket routing with payload analysis, encapsulation and service module vectoring
US2007027423425 May 200729 Nov 2007Fujitsu LimitedNetwork management method
US2007028901724 Ago 200713 Dic 2007Lancope, Inc.Network port profiling
US2008005248731 Jul 200728 Feb 2008Shinichi AkahaneNetwork switching device and control method of network switching device
US2008006576011 Sep 200613 Mar 2008AlcatelNetwork Management System with Adaptive Sampled Proactive Diagnostic Capabilities
US2008008051728 Sep 20063 Abr 2008At & T Corp.System and method for forwarding traffic data in an MPLS VPN
US2008009516024 Oct 200624 Abr 2008Cisco Technology, Inc.Subnet Scoped Multicast / Broadcast Packet Distribution Mechanism Over a Routed Network
US2008010138626 Oct 20061 May 2008Ericsson, Inc.MAC (media access control) tunneling and control and method
US2008011240027 Mar 200715 May 2008Futurewei Technologies, Inc.System for Providing Both Traditional and Traffic Engineering Enabled Services
US2008013376021 Oct 20035 Jun 2008Berkvens Winfried Antonius HenMethod and Apparatus Allowing Remote Access in Data Networks
US2008015927717 Dic 20073 Jul 2008Brocade Communications Systems, Inc.Ethernet over fibre channel
US2008017249211 Ene 200717 Jul 2008Mandayam Thondanur RaghunathSystem and method for virtualized resource configuration
US2008018119627 Feb 200731 Jul 2008Alcatel LucentLink aggregation across multiple chassis
US2008018124317 Dic 200731 Jul 2008Brocade Communications Systems, Inc.Ethernet forwarding in high performance fabrics
US200801869816 Feb 20087 Ago 2008Hitachi Cable, Ltd.Switching hub and lan system
US2008020537721 Feb 200828 Ago 2008Blade Network Technologies, Inc.System and methods for providing server virtualization assistance
US2008021917212 Sep 200611 Sep 2008Nortel Networks LimitedForwarding Plane Data Communications Channel for Ethernet Transport Networks
US2008022585215 Mar 200718 Sep 2008Robert RaszukMethods and apparatus providing two stage tunneling
US2008022585313 Feb 200818 Sep 2008Melman DavidLogical bridging system and method
US2008022889712 Mar 200718 Sep 2008Ko Michael ALayering serial attached small computer system interface (sas) over ethernet
US200802401292 Abr 20072 Oct 2008Khaled ElmeleegySystem and method for preventing count-to-infinity problems in ethernet networks
US2008026717930 Abr 200730 Oct 2008Lavigne Bruce EPacket processing
US2008028545816 May 200720 Nov 2008Simula Innovations AsDeadlock free network routing
US2008028555513 May 200820 Nov 2008Nec CorporationNode, communication method, and program for node
US2008029824827 May 20084 Dic 2008Guenter RoeckMethod and Apparatus For Computer Network Bandwidth Control and Congestion Management
US200803044985 Jun 200711 Dic 2008Jorgensen Steven GPacket mirroring
US2008031034212 Jun 200718 Dic 2008Cisco Technology, Inc.Addressing Messages in a Two-Tier Network
US2009002206920 Jul 200722 Ene 2009Cisco Tecnology, Inc.Preventing loops in networks operating different protocols to provide loop-free topology
US2009003760731 Jul 20075 Feb 2009Cisco Technology, Inc.Overlay transport virtualization
US2009004227022 Ago 200812 Feb 2009Allergan, Inc.Activatable recombinant neurotoxins
US200900442707 Ago 200712 Feb 2009Asaf ShellyNetwork element and an infrastructure for a network risk management system
US2009006742216 Jul 200812 Mar 2009Cellcrypt LimitedCommunication system and method
US2009006744210 Nov 200812 Mar 2009Thomas Joseph KillianMethod and system for managing multiple networks over a set of ports
US2009007956027 Dic 200726 Mar 2009General Electric CompanyRemotely monitoring railroad equipment using network protocols
US2009008034521 Sep 200726 Mar 2009Ericsson, Inc.Efficient multipoint distribution tree construction for shortest path bridging
US2009008344524 Sep 200726 Mar 2009Ganga Ilango SMethod and system for virtual port communications
US200900920423 Oct 20089 Abr 2009Honda Motor Co., Ltd.Navigation device and navigation system
US20090092043 *3 Oct 20079 Abr 2009Nortel Networks LimitedProviding an abstraction layer in a cluster switch that includes plural switches
US2009010640523 Oct 200723 Abr 2009Mazarick Michael SSystem and method for initializing and maintaining a series of virtual local area networks contained in a clustered computer system
US2009011638112 May 20087 May 2009Brocade Communications Systems, Inc.Method and system for congestion management in a fibre channel network
US2009012938423 Dic 200821 May 2009Alcatel-Lucent Usa Inc.Data mirroring in a service
US2009013857726 Sep 200828 May 2009Nicira NetworksNetwork operating system for managing and securing networks
US2009013875226 Nov 200728 May 2009Stratus Technologies Bermuda Ltd.Systems and methods of high availability cluster environment failover protection
US2009016158427 Feb 200925 Jun 2009Huawei Technologies Co., Ltd.Method for a root path calculation in a shortest path bridge
US2009016167024 Dic 200725 Jun 2009Cisco Technology, Inc.Fast multicast convergence at secondary designated router or designated forwarder
US2009016864726 Dic 20082 Jul 2009Nortel Networks LimitedInterworking an Ethernet Ring Network and an Ethernet Network with Traffic Engineered Trunks
US2009019917728 Oct 20056 Ago 2009Hewlett-Packard Development Company, L.P.Virtual computing infrastructure
US2009020496526 Ene 200913 Ago 2009Youji TanakaUsb port shared control method
US2009021378314 Nov 200527 Ago 2009Stmicroelectronics R&D Ltd.Roaming Network Stations Using A Mac Address Identifier To Select New Access Point
US200902228793 Mar 20083 Sep 2009Microsoft CorporationSuper policy in information protection systems
US2009023203111 Mar 200817 Sep 2009Jean-Philippe VasseurReceiver-based construction of point-to-multipoint trees using path computation elements in a computer network
US200902451373 Mar 20091 Oct 2009Green Hills Software, Inc.Highly available virtual stacking architecture
US2009024524231 Mar 20081 Oct 2009International Business Machines CorporationVirtual Fibre Channel Over Ethernet Switch
US2009024613725 Mar 20091 Oct 2009Vertex Pharmaceuticals IncorporatedPyridyl derivatives as cftr modulators
US2009025204912 Dic 20058 Oct 2009Reiner LudwigMethod and devices for specifying the quality of service in a transmission of data packets
US200902520618 Abr 20088 Oct 2009David SmallMethods and apparatus to implement a partial mesh virtual private local area network service
US2009026008325 Feb 200915 Oct 2009Foundry Networks, Inc.System and method for source ip anti-spoofing security
US200902795586 May 200212 Nov 2009Ian Edward DavisNetwork routing apparatus for enhanced efficiency and monitoring capability
US2009029285823 May 200826 Nov 2009Vmware, Inc.Distributed Virtual Switch for Virtualized Computer Systems
US2009031672112 May 200824 Dic 2009Brocade Communications Systems, Inc.Method and system for facilitating application-oriented quality of service in a fibre channel network
US200903237084 Oct 200631 Dic 2009Markus IhleSubscriber and Communication Controller of a communication System and Method for Implementing a Gateway Functionality in a Subscriber of a Communication System
US2009032739230 Jun 200831 Dic 2009Sun Microsystems, Inc.Method and system for creating a virtual router in a blade chassis to maintain connectivity
US2009032746227 Jun 200831 Dic 2009International Business Machines CorporationMethod, system and program product for managing assignment of mac addresses in a virtual machine environment
US2010002742031 Jul 20084 Feb 2010Cisco Technology, Inc.Dynamic distribution of virtual machines in a communication network
US201000464716 Feb 200725 Feb 2010Mitsubishi Electric CorporationCommunication system, communication apparatus, wireless base station, and wireless terminal station
US2010005426028 Ago 20094 Mar 2010Blade Network Technologies, Inc.Method and Apparatus to Switch Packets between Virtual Ports
US201000612699 Sep 200811 Mar 2010Cisco Technology, Inc.Differentiated services for unicast and multicast frames in layer 2 topologies
US201000741758 May 200925 Mar 2010Banks Kevin RSystems and methods for wirelessly communicating multidrop packets via wireless networks
US2010009794120 Oct 200822 Abr 2010International Business Machines CorporationRedundant Intermediary Switch Solution for Detecting and Managing Fibre Channel over Ethernet FCoE Switch Failures
US2010010381328 Oct 200829 Abr 2010Nortel Networks LimitedProvisioned provider link state bridging (plsb) with routed back-up
US2010010393924 Oct 200829 Abr 2010Carlson Scott MDetermining the configuration of an ethernet fabric
US2010013163624 Nov 200827 May 2010Vmware, Inc.Application delivery control module for virtual network switch
US2010015802423 Dic 200824 Jun 2010Ali SajassiOptimized forwarding for provider backbone bridges with both i&b components (ib-pbb)
US2010016587730 Dic 20081 Jul 2010Amit ShuklaMethods and apparatus for distributed dynamic network provisioning
US2010016599529 Dic 20081 Jul 2010Juniper Networks, Inc.Routing frames in a computer network using bridge identifiers
US2010016846731 Dic 20081 Jul 2010Johnston Victor JIntegrated process for the production of viny acetate from acetic acid via ethy acetate
US2010016946730 Dic 20081 Jul 2010Amit ShuklaMethod and apparatus for determining a network topology during network provisioning
US2010016994831 Dic 20081 Jul 2010Hytrust, Inc.Intelligent security control system for virtualized ecosystems
US2010018292018 Nov 200922 Jul 2010Fujitsu LimitedApparatus and method for controlling data communication
US2010021504912 Feb 201026 Ago 2010Adc Telecommunications, Inc.Inter-networking devices for use with physical layer information
US201002207242 Mar 20102 Sep 2010Nortel Networks LimitedMetro ethernet service enhancements
US201002263681 Mar 20109 Sep 2010Futurewei Technologies, Inc.Transport Multiplexer - Mechanisms to Force Ethernet Traffic From One Domain to Be Switched in a Different (External) Domain
US201002263814 Mar 20099 Sep 2010Juniper Networks, Inc.Routing frames in a trill network using service vlan identifiers
US2010024638816 Mar 201030 Sep 2010Brocade Communications Systems, Inc.Redundant host connection in a routed network
US201002572631 Abr 20107 Oct 2010Nicira Networks, Inc.Method and apparatus for implementing and managing virtual switches
US2010027196024 Abr 200928 Oct 2010Verizon Patent And Licensing Inc.Tracing routes and protocols
US20100272107 *26 Nov 200728 Oct 2010Oktavian PappTechnique for address resolution in a data transmission network
US2010028110623 Abr 20104 Nov 2010Futurewei Technologies, Inc.Automatic Subnet Creation in Networks That Support Dynamic Ethernet-Local Area Network Services for Use by Operation, Administration, and Maintenance
US2010028441411 May 200911 Nov 2010Brocade Communications Systems, Inc.Flexible stacking port
US2010028441812 Nov 200811 Nov 2010Eric Ward GrayMethod and system for telecommunications including self-organizing scalable ethernet using is-is hierarchy
US201002872627 May 201011 Nov 2010Uri ElzurMethod and system for guaranteed end-to-end data flows in a local networking domain
US201002875486 May 200911 Nov 2010Vmware, Inc.Long Distance Virtual Machine Migration
US2010029047323 Oct 200918 Nov 2010Cisco Technology, Inc.Port grouping for association with virtual interfaces
US201002995279 Jul 200925 Nov 2010Samsung Electronics Co., LtdNear field communication (nfc) device and method for selectively securing records in a near field communication data exchange format (ndef) message
US2010030307126 May 20092 Dic 2010Alcatel-Lucent Usa Inc.System and method for converting unicast client requests into multicast client requests
US2010030307529 May 20092 Dic 2010Sun Microsystems, Inc.Managing traffic on virtualized lanes between a network switch and a virtual machine
US2010030308327 May 20092 Dic 2010International Business Machines CorporationTwo-Layer Switch Apparatus To Avoid First Layer Inter-Switch Link Data Traffic In Steering Packets Through Bump-In-The-Wire Service Applications
US201003098204 Jun 20099 Dic 2010Cisco Technology, Inc.Preventing loss of network traffic due to inconsistent configurations within the network
US201003099125 Jun 20099 Dic 2010Juniper Networks, Inc.Forwarding frames in a computer network using shortest path bridging
US2010032911030 Jun 200930 Dic 2010Laurence RoseMethod for reconvergence after failure in a dual-homing network environment
US2011001967824 Jul 200927 Ene 2011Juniper Networks, Inc.Routing frames in a shortest path computer network for a multi-homed legacy bridge node
US201100329455 Ago 200910 Feb 2011Cisco Technology, Inc.Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers
US2011003548919 Oct 201010 Feb 2011Broadcom CorporationSystem and method for interfacing with a management system
US201100354982 Ago 201010 Feb 2011Hemal ShahMethod and System for Managing Network Power Policy and Configuration of Data Center Bridging
US2011004433921 Ago 200924 Feb 2011Alcatel-Lucent Usa Inc.Server-side load balancing using parent-child link aggregation groups
US201100443523 Mar 200924 Feb 2011France TelecomTechnique for determining a point-to-multipoint tree linking a root node to a plurality of leaf nodes
US2011006408614 Sep 200917 Mar 2011Futurewei Technologies, Inc.Fiber Channel over Ethernet and Fiber Channel Switching Based on Ethernet Switch Fabrics
US2011006408918 May 200917 Mar 2011Youichi HidakaPci express switch, pci express system, and network control method
US2011007220824 Sep 200924 Mar 2011Vmware, Inc.Distributed Storage Resource Scheduler and Load Balancer
US2011008556012 Oct 200914 Abr 2011Dell Products L.P.System and Method for Implementing a Virtual Switch
US2011008556314 Oct 200914 Abr 2011Dell Products, LpVirtualization Aware Network Switch
US2011011026610 Nov 201012 May 2011Li Gordon YongMethods quality of service (qos) from a wireless network to a wired network
US201101348029 Dic 20099 Jun 2011Cisco Technology, Inc.Determining A Routing Tree For Networks With Different Routing Protocols
US2011013480311 Feb 20119 Jun 2011Juniper Networks, Inc.Configuring networks including spanning trees
US201101349252 Nov 20109 Jun 2011Uri SafraiSwitching Apparatus and Method Based on Virtual Interfaces
US2011014205315 Dic 200916 Jun 2011Jacobus Van Der MerweMethods and apparatus to communicatively couple virtual private networks to virtual machines within distributive computing networks
US2011014206215 Dic 200916 Jun 2011Songbo WangiSCSI to FCoE Gateway
US2011016149430 Dic 200930 Jun 2011Verizon Patent And Licensing, Inc.Feature delivery packets for peer-to-peer based feature network
US2011016169519 Ene 201030 Jun 2011Hitachi, Ltd.Power-saving network management server, network system, and method of determining supply of power
US2011018837328 Ene 20114 Ago 2011Shuichi SaitoInterface control system and interface control method
US201101944035 Feb 201011 Ago 2011Cisco Technology, Inc.Fault isolation in trill networks
US201101945633 Jun 201011 Ago 2011Vmware, Inc.Hypervisor Level Distributed Load-Balancing
US2011022878025 Ene 201122 Sep 2011Futurewei Technologies, Inc.Service Prioritization in Link State Controlled Layer Two Networks
US2011023157016 Mar 201022 Sep 2011Brocade Communications Systems, Inc.Method and Apparatus for Mirroring Frames to a Remote Diagnostic System
US2011023157427 May 201122 Sep 2011Peter SaundersonNetwork including snooping
US2011023552324 Mar 201029 Sep 2011Brocade Communications Systems, Inc.Method and system for extending routing domain to non-routing end stations
US2011024313330 Mar 20076 Oct 2011Anil VillaitPort management system
US2011024313630 Mar 20106 Oct 2011Cisco Technology, Inc.Forwarding multi-destination packets in a network with virtual port channels
US201102466699 Feb 20116 Oct 2011Hitachi, Ltd.Method and system of virtual machine migration
US2011025553816 Abr 201020 Oct 2011Udayakumar SrinivasanMethod of identifying destination in a virtual environment
US2011025554018 Abr 201120 Oct 2011Tal MizrahiSystem and Method for Adapting a Packet Processing Pipeline
US2011026182827 Abr 201027 Oct 2011Cisco Technology, Inc.Virtual switching overlay for cloud computing
US201102681202 May 20113 Nov 2011Brocade Communications Systems, Inc.Fabric switching
US2011026812514 Abr 20113 Nov 2011Brocade Communications Systems, Inc.Virtual cluster switching
US2011027398810 May 201010 Nov 2011Jean TourrilhesDistributing decision making in a centralized flow routing system
US201102741146 May 201010 Nov 2011Sandeep DharFCoE ISOLATED PORT CHANNELS AND FCoE SESSION RESYNCHRONIZATION IN vPC/MCEC ENVIRONMENTS USING DCBXP
US2011028057229 Abr 201117 Nov 2011Brocade Communications Systems, Inc.Converged network extension
US20110286457 *24 May 201024 Nov 2011Cheng Tien EeMethods and apparatus to route control packets based on address partitioning
US2011029605228 May 20101 Dic 2011Microsoft CorportationVirtual Data Center Allocation with Bandwidth Guarantees
US2011029939122 Abr 20118 Dic 2011Brocade Communications Systems, Inc.Traffic management for virtual cluster switching
US201102994137 Mar 20118 Dic 2011Brocade Communications Systems, Inc.Port profile management for virtual cluster switching
US2011029941415 Mar 20118 Dic 2011Brocade Communications Systems, Inc.Preserving quality of service across trill networks
US2011029952718 Feb 20118 Dic 2011Brocade Communications Systems, Inc.Supporting multiple multicast trees in trill networks
US2011029952818 Feb 20118 Dic 2011Brocade Communications Systems, Inc.Network layer multicasting in trill networks
US201102995319 Mar 20118 Dic 2011Brocade Communications Systems, Inc.Flooding packets on a per-virtual-network basis
US201102995329 Mar 20118 Dic 2011Brocade Communications Systems, Inc.Remote port mirroring
US2011029953317 Mar 20118 Dic 2011Brocade Communications Systems, Inc.Internal virtual network identifier and internal policy identifier
US2011029953422 Abr 20118 Dic 2011Brocade Communications Systems, Inc.Virtual port grouping for virtual cluster switching
US20110299535 *22 Abr 20118 Dic 2011Brocade Communications Systems, Inc.Name services for virtual cluster switching
US2011029953622 Abr 20118 Dic 2011Brocade Communications Systems, Inc.Method and system for link aggregation across multiple switches
US2011031755917 Dic 201029 Dic 2011Kern AndrasNotifying a Controller of a Change to a Packet Forwarding Configuration of a Network Element Over a Communication Channel
US2011031770329 Jun 201129 Dic 2011Futurewei Technologies, Inc.Asymmetric Network Address Encapsulation
US2012001124016 Sep 201112 Ene 2012Hitachi, Ltd.Method and apparatus for managing virtual ports on storage systems
US2012001426114 Jul 201019 Ene 2012Cisco Technology, Inc.Monitoring A Flow Set To Detect Faults
US2012001438727 May 201119 Ene 2012Futurewei Technologies, Inc.Virtual Layer 2 and Mechanism to Make it Scalable
US2012002022030 Sep 201126 Ene 2012Nec CorporationNetwork system, controller, and network control method
US2012002701730 Jul 20102 Feb 2012Cisco Technology, Inc.Multi-destination forwarding in network clouds which include emulated switches
US201200336635 Ago 20109 Feb 2012Cisco Technology, Inc., A Corporation Of CaliforniaDiscovery of Services Provided by Application Nodes in a Network
US2012003366520 Ene 20119 Feb 2012Alcatel-Lucent Usa Inc.System and method for multi-chassis link aggregation
US2012003366920 Ene 20119 Feb 2012Alcatel-Lucent Usa Inc.System and method for traffic distribution in a multi-chassis link aggregation
US2012007599130 Sep 201129 Mar 2012Nec CorporationNetwork system, control method thereof and controller
US2012009956720 Oct 201026 Abr 2012Brian HartUsing encapsulation to enable 802.1 bridging across 802.11 links
US2012009960210 Jun 201126 Abr 2012Brocade Communications Systems, Inc.End-to-end virtualization
US20120106339 *1 Nov 20103 May 2012Cisco Technology, Inc.Probing Specific Customer Flow in Layer-2 Multipath Networks
US2012013109730 Ene 201224 May 2012Calix, Inc.Isolation vlan for layer two access networks
US2012013128918 Nov 201024 May 2012Hitachi, Ltd.Multipath switching over multiple storage systems
US201201477409 Ago 201014 Jun 2012Eci TelecomTechnique for dual homing interconnection between communication networks
US2012015899715 Dic 201021 Jun 2012Industrial Technology Research InstituteNetwork system and method of address resolution
US2012016316422 Abr 201128 Jun 2012Brocade Communications Systems, Inc.Method and system for remote load balancing in high-availability networks
US201201770397 Ene 201112 Jul 2012Berman Stuart BMethods, systems and apparatus for converged network adapters
US2012024335922 Mar 201127 Sep 2012Taiwan Semiconductor Manufacturing Company, Ltd.Sense amplifier
US2012024353931 May 201127 Sep 2012Avaya Inc.Usage of masked ethernet addresses between transparent interconnect of lots of links (trill) routing bridges
US201202753476 Jul 20121 Nov 2012Cisco Technology, Inc.Differentiated services for unicast and multicast frames in layer 2 topologies
US2012029419219 May 201122 Nov 2012Hitachi, Ltd.Method and apparatus of connectivity discovery between network switch and server based on vlan identifiers
US2012029419418 May 201122 Nov 2012Cisco Technology, Inc.Method and apparatus for preserving extensions in multi-vendor trill networks
US201203208009 Dic 201120 Dic 2012International Business Machines CorporationMac Learning in a Trill Network
US201203209268 Dic 201120 Dic 2012International Business Machines CorporationDistributed Link Aggregation Group (LAG) for a Layer 2 Fabic
US2012032776624 Jun 201127 Dic 2012Cisco Technology, Inc.Level of hierarchy in mst for traffic localization and load balancing
US2012032793715 Jun 201227 Dic 2012Melman DavidFcoe over trill
US2013000353529 Jun 20113 Ene 2013Fujitsu Network Communications, Inc.Systems and methods for distributed service protection across plug-in units
US2013000373730 Sep 20113 Ene 2013David SinicropeE-tree using two pseudowires between edge routers with enhanced learning methods and systems
US201300037383 Nov 20113 Ene 2013Brocade Communications Systems, Inc.Trill based router redundancy
US2013002807227 Jul 201131 Ene 2013Fujitsu Network Communications, Inc.Method and system for management of flood traffic over multiple 0:n link aggregation groups
US201300340155 Ago 20117 Feb 2013International Business Machines CorporationAutomated network configuration in a dynamic virtual environment
US201300674669 Sep 201114 Mar 2013Microsoft CorporationVirtual Switch Extensibility
US2013007076220 Sep 201121 Mar 2013Robert Edward AdamsSystem and methods for controlling network traffic through virtual switches
US201301145959 Oct 20129 May 2013Futurewei Technologies, Co.Method for Multicast Flow Routing Selection
US2013012784830 Nov 201023 May 2013Pushkar P. JoshiSystem and Method for Generating 3D Surface Patches from Unconstrained 3D Curves
US2013019491415 Ene 20131 Ago 2013Brocade Communications Systems, Inc.Link aggregation in software-defined networks
US2013021947322 Feb 201322 Ago 2013Nokia Siemens Networks OyControlling access
US2013025095113 Mar 201326 Sep 2013Brocade Communications Systems, Inc.Overlay tunnel in a fabric switch
US2013025903711 Jul 20073 Oct 2013Foundry Networks, Inc.Duplicating network traffic through transparent vlan flooding
US2013027213511 Abr 201217 Oct 2013Gigamon LlcTraffic visibility in an open networking environment
US201303016429 May 201214 Nov 2013International Business Machines CorporationMethod and system for static trill routing
US201400441268 Ago 201213 Feb 2014Cisco Technology, Inc.Scalable Media Access Control Protocol Synchronization Techniques for Fabric Extender Based Emulated Switch Deployments
US2014010503417 Dic 201317 Abr 2014Huawei Technologies Co., Ltd.Method and ethernet switching device for detecting loop position in ethernet
CN102801599A26 Jul 201228 Nov 2012华为技术有限公司Communication method and system
EP0579567B119 May 199311 Ago 1999International Business Machines CorporationMethods and apparatus for routing packets in packet transmission networks
EP1398920A219 Ago 200317 Mar 2004Alcatel Canada Inc.Stackable virtual local area network provisioning in bridged networks
EP1916807A226 Oct 200730 Abr 2008Ericsson ABTelecommunications system and method for communicating using tunnelling into a MAC address unique to an interface of a device
EP2001167A130 Ago 200710 Dic 2008Huawei Technologies Co LtdA root path computation method in shortest path bridge
WO2008056838A18 Nov 200615 May 2008Chang Hwan ChoSystem and method for controlling network traffic
WO2009042919A226 Sep 20082 Abr 2009Nicira NetworksNetwork operating system for managing and securing networks
WO2010111142A119 Mar 201030 Sep 2010Brocade Communications Systems, Inc .Redundant host connection in a routed network
WO2014031781A121 Ago 201327 Feb 2014Brocade Communications Systems, Inc.Global vlans for fabric switches
Otras citas
Referencia
1"An Introduction to Brocade VCS Fabric Technology", Brocade white paper, http://community.brocade.com/docs/DOC-2954, Dec. 3, 2012.
2"Brocade Fabric OS (FOS) 6.2 Virtual Fabrics Feature Frequently Asked Questions".
3"Switched Virtual Internetworking moved beyond bridges and routers", 8178 Data Communications Sep. 23, 1994, No. 12, New York.
4"Switched Virtual Internetworking moves beyond bridges and routers", Sep. 23, 1994, No. 12, New York, US.
5"The Effortless Network: HyperEdge Technology for the Campus LAN", 2012.
6Abawajy J. "An Approach to Support a Single Service Provider Address Image for Wide Area Networks Environment" Centre for Parallel and Distributed Computing, School of Computer Science Carleton University, Ottawa, Ontario, K1S 5B6, Canada.
7Brocade 'An Introduction to Brocade VCS Fabric Technology', Dec. 3, 2012.
8Brocade Fabric OS (FOS) 6.2 Virtual Fabrics Feature Frequently Asked Questions.
9Brocade Unveils "The Effortless Network", http://newsroom.brocade.com/press-releases/brocade-unveils-the-effortless-network--nasdaq-brcd-0859535, 2012.
10Christensen, M. et al., "Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches", May 2006.
11Eastlake 3rd., Donald et al., "RBridges: TRILL Header Options", Draft-ietf-trill-rbridge-options-00.txt Dec. 24, 2009.
12Eastlake, Donald et al., "RBridges: TRILL Header Options", Dec. 2009.
13FastIron and TurboIron 24X Configuration Guide Supporting FSX 05.1.00 for FESX, FWSX, and FSX; FGS 04.3.03 for FGS, FLS and FWS; FGS 05.0.02 for FGS-STK and FLS-STK, FCX 06.0.00 for FCX; and TIX 04.1.00 for TI24X, Feb. 16, 2010.
14FastIron Configuration Guide Supporting Ironware Software Release 07.0.00, Dec. 18, 2009.
15Foundry FastIron Configuration Guide, Software Release FSX 04.2.00b, Software Release FWS 04.3.00, Software Release FGS 05.0.00a, Sep. 26, 2008.
16Huang, Nen-Fu et al., "An Effective Spanning Tree Algorithm for a Bridged LAN", Mar. 16, 1992.
17J. Touch, et al., "Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement", May 2009.
18Knight, Paul et al., "Layer 2 and 3 Virtual Private Networks: Taxonomy, Technology, and Standardization Efforts", IEEE Communications Magazine, Jun. 2004.
19Knight, Paul et al., "Network based IP VPN Architecture using Virtual Routers", May 2003.
20Knight, S. et al. "Virtual Router Redundancy Protocol", Apr. 1998, XP-002135272.
21Kompella, Ed K. et al., 'Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling' Jan. 2007.
22Kreeger, L. et al., "Network Virtualization Overlay Control Protocol Requirements", Draft-kreeger-nvo3-overlay-cp-00, Jan. 30, 2012.
23Lapuh, Roger et al., "Split Multi-link Trunking (SMLT) draft-lapuh-network-smlt-08", 2008.
24Lapuh, Roger et al., "Split Multi-link Trunking (SMLT)", Oct. 2002.
25Lapuh, Roger et al., 'Split Multi-link Trunking (SMLT) draft-lapuh-network-smlt-08', Jan. 2009.
26Louati, Wajdi et al., "Network-based virtual personal overlay networks using programmable virtual routers", IEEE Communications Magazine, Jul. 2005.
27Mahalingam "VXLAN: A Framework for Overlaying Virtualized Layer 2 Networks over Layer 3 Networks" Oct. 17, 2013 pp. 1-22, Sections 1, 4 and 4.1.
28Mckeown, Nick et al. "OpenFlow: Enabling Innovation in Campus Networks", Mar. 14, 2008, www.openflow.org/documents/openflow-wp-latest.pdf.
29Nadas, S. et al., "Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6", Mar. 2010.
30Narten, T. et al. "Problem Statement: Overlays for Network Virtualization", draft-narten-nvo3-overlay-problem-statement-01, Oct. 31, 2011.
31Office Action dated Apr. 1, 2015 U.S. Appl. No. 13/656,438, filed Oct. 19, 2012.
32Office Action dated Apr. 1, 2015, U.S. Appl. No. 13/656,438, filed Oct. 19, 2012.
33Office Action dated Apr. 22, 2014, U.S. Appl. No. 13/030,806, filed Feb. 18, 2011.
34Office action dated Apr. 25, 2013, U.S. Appl. No. 13/030,688, filed Feb. 18, 2011.
35Office action dated Apr. 26, 2012, U.S. Appl. No. 12/725,249, filed Mar. 16, 2010.
36Office action dated Apr. 30, 2015, U.S. Appl. No. 13/351,513, filed Jan. 17, 2012.
37Office Action dated Apr. 9, 2014, U.S. Appl. No. 13/092,724, filed Apr. 22, 2011.
38Office Action dated Apr. 9, 2014, U.S. Appl. No. 13/092,752, filed Apr. 22, 2011.
39Office action dated Aug. 14, 2014, U.S. Appl. No. 13/092,460, filed Apr. 22, 2011.
40Office Action dated Aug. 19, 2015, U.S. Appl. No. 14/156,374, filed Jan. 15, 2014.
41Office Action dated Aug. 21, 2015, U.S. Appl. No. 13/776,217, filed Feb. 25, 2013.
42Office action dated Aug. 4, 2014, U.S. Appl. No. 13/050,102, filed Mar. 17, 2011.
43Office Action dated Dec. 19, 2014, for U.S. Appl. No. 13/044,326, filed Mar. 9, 2011.
44Office action dated Dec. 2, 2013, U.S. Appl. No. 13/184,526, filed Jul. 16, 2011.
45Office action dated Dec. 20, 2012, U.S. Appl. No. 12/950,974, filed Nov. 19, 2010.
46Office action dated Dec. 21, 2012, U.S. Appl. No. 13/098,490, filed May 2, 2011.
47Office action dated Dec. 3, 2012, U.S. Appl. No. 13/030,806, filed Feb. 18, 2011.
48Office action dated Dec. 5, 2012, U.S. Appl. No. 13/087,239, filed Apr. 14, 2011.
49Office Action dated Feb. 20, 2014, U.S. Appl. No. 13/598,204, filed Aug. 29, 2012.
50Office action dated Feb. 22, 2013, U.S. Appl. No. 13/044,301, filed Mar. 9, 2011.
51Office Action dated Feb. 28, 2014, U.S. Appl. No. 13/351,513, filed Jan. 17, 2012.
52Office action dated Feb. 5, 2013, U.S. Appl. No. 13/092,724, filed Apr. 22, 2011.
53Office action dated Jan. 10, 2014, U.S. Appl. No. 13/092,580, filed Apr. 22, 2011.
54Office action dated Jan. 16, 2014, U.S. Appl. No. 13/042,259, filed Mar. 7, 2011.
55Office action dated Jan. 28, 2013, U.S. Appl. No. 13/092,701, filed Apr. 22, 2011.
56Office action dated Jan. 28, 2013, U.S. Appl. No. 13/148,526, filed Jul. 16, 2011.
57Office action dated Jan. 4, 2013, U.S. Appl. No. 12/950,968, filed Nov. 19, 2010.
58Office action dated Jan. 6, 2014, U.S. Appl. No. 13/092,877, filed Apr. 22, 2011.
59Office action dated Jul. 18, 2013, U.S. Appl. No. 13/092,752, filed Apr. 22, 2011.
60Office action dated Jul. 18, 2013, U.S. Appl. No. 13/365,808, filed Feb. 3, 2012.
61Office action dated Jul. 3, 2013, U.S. Appl. No. 13/092,701, filed Apr. 22, 2011.
62Office Action dated Jul. 31, 2015, U.S. Appl. No. 13/598,204, filed Aug. 29, 2014.
63Office Action dated Jul. 31, 2015, U.S. Appl. No. 14/473,941, filed Aug. 29, 2014.
64Office Action dated Jul. 31, 2015, U.S. Appl. No. 14/488,173, filed Sep. 16, 2014.
65Office action dated Jul. 7, 2014, for U.S. Appl. No. 13/044,326, filed Mar. 9, 2011.
66Office action dated Jul. 9, 2013, U.S. Appl. No. 13/098,490, filed May 2, 2011.
67Office action dated Jun. 10, 2013, U.S. Appl. No. 13/092,580, filed Apr. 22, 2011.
68Office Action Dated Jun. 10, 2015, U.S. Appl. No. 13/890,150, filed May 8, 2013.
69Office action dated Jun. 11, 2013, U.S. Appl. No. 13/030,806, filed Feb. 18, 2011.
70Office action dated Jun. 11, 2013, U.S. Appl. No. 13/044,301, filed Mar. 9, 2011.
71Office action dated Jun. 13, 2013, U.S. Appl. No. 13/312,903, filed Dec. 6, 2011.
72Office Action dated Jun. 16, 2015, U.S. Appl. No. 13/048,817, filed Mar. 15, 2011.
73Office Action dated Jun. 18, 2014, U.S. Appl. No. 13/440,861, filed Apr. 5, 2012.
74Office Action dated Jun. 18, 215, U.S. Appl. No. 13/098,490, filed May 2, 2011.
75Office action dated Jun. 19, 2013, U.S. Appl. No. 13/092,873, filed Apr. 22, 2011.
76Office Action dated Jun. 20, 2014, U.S. Appl. No. 13/092,877, filed Apr. 22, 2011.
77Office action dated Jun. 21, 2013, U.S. Appl. No. 13/092,460, filed Apr. 22, 2011.
78Office Action dated Jun. 6, 2014, U.S. Appl. No. 13/669,357, filed Nov. 5, 2012.
79Office action dated Jun. 7, 2012, U.S. Appl. No. 12/950,968, filed Nov. 19, 2010.
80Office action dated Jun. 8, 2015, U.S. Appl. No. 14/178,042, filed Feb. 11, 2014.
81Office Action dated Mar. 14, 2014, U.S. Appl. No. 13/092,460, filed Apr. 22, 2011.
82Office action dated Mar. 18, 2013, U.S. Appl. No. 13/042,259, filed Mar. 7, 2011.
83Office Action dated Mar. 26, 2014, U.S. Appl. No. 13/092,701, filed Apr. 22, 2011.
84Office action dated Mar. 27, 2014, U.S. Appl. No. 13/098,490, filed May 2, 2011.
85Office action dated Mar. 4, 2013, U.S. Appl. No. 13/092,877, filed Apr. 22, 2011.
86Office Action dated Mar. 6, 2014, U.S. Appl. No. 13/425,238, filed Mar. 20, 2012.
87Office Action dated May 14, 2014, U.S. Appl. No. 13/533,843, filed Jun. 26, 2012.
88Office action dated May 16, 2013, U.S. Appl. No. 13/050,102, filed Mar. 17, 2011.
89Office Action dated May 21, 2015, U.S. Appl. No. 13/288,822, filed Nov. 3, 2011.
90Office action dated May 22, 2013, U.S. Appl. No. 13/087,239, filed Apr. 14, 2011.
91Office action dated May 22, 2013, U.S. Appl. No. 13/148,526, filed Jul. 16, 2011.
92Office action dated May 24, 2012, U.S. Appl. No. 12/950,974, filed Nov. 19, 2010.
93Office action dated May 31, 2013, U.S. Appl. No. 13/098,360, filed Apr. 29, 2011.
94Office Action dated May 9, 2014, U.S. Appl. No. 13/484,072, filed May 30, 2012.
95Office action dated Nov. 12, 2013, U.S. Appl. No. 13/312,903, filed Dec. 6, 2011.
96Office action dated Nov. 29, 2013, U.S. Appl. No. 13/092,873, filed Apr. 22, 2011.
97Office Action dated Nov. 5, 2015, U.S. Appl. No. 14/178,042, filed Feb. 11, 2014.
98Office Action dated Oct. 19, 2015, U.S. Appl. No. 14/215,996, filed Mar. 17, 2014.
99Office action dated Oct. 2, 2013, U.S. Appl. No. 13/044,326, filed Mar. 9, 2011.
100Office action dated Oct. 2, 2014, for U.S. Appl. No. 13/092,752, filed Apr. 22, 2011.
101Office action dated Oct. 26, 2012, U.S. Appl. No. 13/050,102, filed Mar. 17, 2011.
102Office action dated Sep. 12, 2012, U.S. Appl. No. 12/725,249, filed Mar. 16, 2010.
103Office Action dated Sep. 17, 2015, U.S. Appl. No. 14/577,785, filed Dec. 19, 2014.
104Office Action dated Sep. 18, 2015, U.S. Appl. No. 13/345,566, filed Jan. 6, 2012.
105Office action dated Sep. 19, 2012, U.S. Appl. No. 13/092,864, filed Apr. 22, 2011.
106Office Action dated Sep. 2, 2015, U.S. Appl. No. 14/151,693, filed Jan. 9, 2014.
107Office Action dated Sep. 22, 2015 U.S. Appl. No. 13/656,438, filed Oct. 19, 2012.
108Office action dated Sep. 5, 2013, U.S. Appl. No. 13/092,877, filed Apr. 22, 2011.
109Office Action for U.S. Appl. No. 13/030,688, filed Feb. 18, 2011, dated Jul. 17, 2014.
110Office Action for U.S. Appl. No. 13/030,806, filed Feb. 18, 2011, dated Dec. 3, 2012.
111Office Action for U.S. Appl. No. 13/042,259, filed Mar. 7, 2011, dated Feb. 23, 2015.
112Office Action for U.S. Appl. No. 13/042,259, filed Mar. 7, 2011, dated Jan. 16, 2014.
113Office Action for U.S. Appl. No. 13/044,301, dated Mar. 9, 2011.
114Office Action for U.S. Appl. No. 13/044,301, filed Mar. 9, 2011, dated Jan. 29, 2015.
115Office Action for U.S. Appl. No. 13/044,326, filed Mar. 9, 2011, dated Jul. 7, 2014.
116Office Action for U.S. Appl. No. 13/050,102, filed Mar. 17, 2011, dated Jan. 26, 2015.
117Office Action for U.S. Appl. No. 13/087,239, filed Apr. 14, 2011, dated Dec. 5, 2012.
118Office Action for U.S. Appl. No. 13/092,460, filed Apr. 22, 2011, dated Mar. 13, 2015.
119Office Action for U.S. Appl. No. 13/092,580, filed Apr. 22, 2011, dated Jan. 10, 2014.
120Office Action for U.S. Appl. No. 13/092,752, filed Apr. 22, 2011, dated Apr. 9, 2014.
121Office Action for U.S. Appl. No. 13/092,752, filed Apr. 22, 2011, dated Feb. 27, 2015.
122Office Action for U.S. Appl. No. 13/092,873, filed Apr. 22, 2011, dated Jul. 25, 2014.
123Office Action for U.S. Appl. No. 13/092,873, filed Apr. 22, 2011, dated Nov. 29, 2013.
124Office Action for U.S. Appl. No. 13/092,873, filed Apr. 22, 2011, dated Nov. 7, 2014.
125Office Action for U.S. Appl. No. 13/092,877, filed Apr. 22, 2011, dated Jan. 6, 2014.
126Office Action for U.S. Appl. No. 13/092,877, filed Apr. 22, 2011, dated Jun. 20, 2014.
127Office Action for U.S. Appl. No. 13/092,877, filed Apr. 22, 2011, dated Nov. 10, 2014.
128Office Action for U.S. Appl. No. 13/092,887, dated Jan. 6, 2014.
129Office Action for U.S. Appl. No. 13/098,490, filed May 2, 2011, dated Mar. 27, 2014.
130Office Action for U.S. Appl. No. 13/157,942, filed Jun. 10, 2011.
131Office Action for U.S. Appl. No. 13/184,526, filed Jul. 16, 2011, dated Dec. 2, 2013.
132Office Action for U.S. Appl. No. 13/184,526, filed Jul. 16, 2011, dated Jan. 5, 2015.
133Office Action for U.S. Appl. No. 13/312,903, filed Dec. 6, 2011, dated Aug. 7, 2014.
134Office Action for U.S. Appl. No. 13/312,903, filed Dec. 6, 2011, dated Jun. 13, 2013.
135Office Action for U.S. Appl. No. 13/312,903, filed Dec. 6, 2011, dated Nov. 12, 2013.
136Office Action for U.S. Appl. No. 13/351,513, filed Jan. 17, 2012, dated Feb. 28, 2014.
137Office Action for U.S. Appl. No. 13/351,513, filed Jan. 17, 2012, dated Jul. 24, 2014.
138Office Action for U.S. Appl. No. 13/365,993, filed Feb. 3, 2012, from Cho, Hong Sol., dated Jul. 23, 2013.
139Office Action for U.S. Appl. No. 13/425,238, dated Mar. 12, 2015.
140Office Action for U.S. Appl. No. 13/425,238, filed Mar. 20, 2012, dated Mar. 12, 2015.
141Office Action for U.S. Appl. No. 13/425,238, filed Mar. 20, 2012, dated Mar. 6, 2014.
142Office Action for U.S. Appl. No. 13/533,843, filed Jun. 26, 2012, dated Oct. 21, 2013.
143Office Action for U.S. Appl. No. 13/556,061, filed Jul. 23, 2012, dated Jun. 6, 2014.
144Office Action for U.S. Appl. No. 13/598,204, filed Aug. 29, 2012, dated Feb. 20, 2014.
145Office Action for U.S. Appl. No. 13/598,204, filed Aug. 29, 2012, dated Jan. 5, 2015.
146Office Action for U.S. Appl. No. 13/669,357, filed Nov. 5, 2012, dated Jan. 30, 2015.
147Office Action for U.S. Appl. No. 13/742,207 dated Jul. 24, 2014, filed Jan. 15, 2013.
148Office Action for U.S. Appl. No. 13/786,328, filed Mar. 5, 2013, dated Mar. 13, 2015.
149Office Action for U.S. Appl. No. 13/851,026, filed Mar. 26, 2013, dated Jan. 30, 2015.
150Office Action for U.S. Appl. No. 13/950,974, filed Nov. 19, 2010, from Haile, Awet A., dated Dec. 2, 2012.
151Office Action for U.S. Appl. No. 14/577,785, filed Dec. 19, 2014, dated Apr. 13, 2015.
152Perlman R: 'Challenges and opportunities in the design of TRILL: a routed layer 2 technology', 2009 IEEE GLOBECOM Workshops, Honolulu, HI, USA, Piscataway, NJ, USA, Nov. 30, 2009, pp. 1-6, XP002649647, DOI: 10.1109/GLOBECOM.2009.5360776 ISBN: 1-4244-5626-0 [retrieved on Jul. 19, 2011].
153Perlman, Radia "Challenges and Opportunities in the Design of TRILL: a Routed layer 2 Technology", XP-002649647, 2009.
154Perlman, Radia et al., "RBridge VLAN Mapping", Dec. 2009.
155Perlman, Radia et al., "RBridge VLAN Mapping", Draft-ietf-trill-rbridge-vlan-mapping-01.txt Dec. 4, 2009.
156Perlman, Radia et al., "RBridges: Base Protocol Specification", draft-ietf-trill-rbridge-protocol-16.txt, Mar. 3, 2010.
157Perlman, Radia et al., "RBridges: Base Protocol Specification", Mar. 2010.
158Rosen, E. et al., "BGP/MPLS VPNs", Mar. 1999.
159S. Night et al., "Virtual Router Redundancy Protocol", Network Working Group, XP-002135272, Apr. 1998.
160Siamak Azodolmolky et al. "Cloud computing networking: Challenges and opportunities for innovations", IEEE Communications Magazine, vol. 51, No. 7, Jul. 1, 2013.
161Touch, J. et al., "Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement", May 2009.
162Touch, J. et al., 'Transparent Interconnection of Lots of Links (TRILL): Problem and Applicability Statement', May 2009, Network Working Group, pp. 1-17.
163TRILL Working Group Internet-Draft Intended status: Proposed Standard RBridges: Base Protocol Specificaiton Mar. 3, 2010.
164U.S. Appl. No. 12/312,903 Office Action dated Jun. 13, 2013.
165U.S. Appl. No. 12/725,249 Office Action dated Apr. 26, 2013.
166U.S. Appl. No. 12/725,249 Office Action dated Sep. 12, 2012.
167U.S. Appl. No. 12/950,968 Office Action dated Jan. 4, 2013.
168U.S. Appl. No. 12/950,968 Office Action dated Jun. 7, 2012.
169U.S. Appl. No. 12/950,974 Office Action dated Dec. 20, 2012.
170U.S. Appl. No. 12/950,974 Office Action dated May 24, 2012.
171U.S. Appl. No. 13/030,688 Office Action dated Apr. 25, 2013.
172U.S. Appl. No. 13/030,806 Office Action dated Dec. 3, 2012.
173U.S. Appl. No. 13/030,806 Office Action dated Jun. 11, 2013.
174U.S. Appl. No. 13/042,259 Office Action dated Jul. 31, 2013.
175U.S. Appl. No. 13/042,259 Office Action dated Mar. 18, 2013.
176U.S. Appl. No. 13/044,301 Office Action dated Feb. 22, 2013.
177U.S. Appl. No. 13/044,301 Office Action dated Jun. 11, 2013.
178U.S. Appl. No. 13/044,326 Office Action dated Oct. 2, 2013.
179U.S. Appl. No. 13/050,102 Office Action dated May 16, 2013.
180U.S. Appl. No. 13/050,102 Office Action dated Oct. 26, 2012.
181U.S. Appl. No. 13/087,239 Office Action dated Dec. 5, 2012.
182U.S. Appl. No. 13/087,239 Office Action dated May 22, 2013.
183U.S. Appl. No. 13/092,460 Office Action dated Jun. 21, 2013.
184U.S. Appl. No. 13/092,580 Office Action dated Jun. 10, 2013.
185U.S. Appl. No. 13/092,701 Office Action dated Jan. 28, 2013.
186U.S. Appl. No. 13/092,701 Office Action dated Jul. 3, 2013.
187U.S. Appl. No. 13/092,724 Office Action dated Feb. 5, 2013.
188U.S. Appl. No. 13/092,724 Office Action dated Jul. 16, 2013.
189U.S. Appl. No. 13/092,752 Office Action dated Feb. 5, 2013.
190U.S. Appl. No. 13/092,752 Office Action dated Jul. 18, 2013.
191U.S. Appl. No. 13/092,864 Office Action dated Sep. 19, 2012.
192U.S. Appl. No. 13/092,873 Office Action dated Jun. 19, 2013.
193U.S. Appl. No. 13/092,877 Office Action dated Mar. 4, 2013.
194U.S. Appl. No. 13/092,877 Office Action dated Sep. 5, 2013.
195U.S. Appl. No. 13/098,360 Office Action dated May 31, 2013.
196U.S. Appl. No. 13/098,490 Office Action dated Dec. 21, 2012.
197U.S. Appl. No. 13/098,490 Office Action dated Jul. 9, 2013.
198U.S. Appl. No. 13/184,526 Office Action dated Jan. 28, 2013.
199U.S. Appl. No. 13/184,526 Office Action dated May 22, 2013.
200U.S. Appl. No. 13/365,808 Office Action dated Jul. 18, 2013.
201U.S. Appl. No. 13/365,993 Office Action dated Jul. 23, 2013.
202Zhai F. Hu et al. "RBridge: Pseudo-Nickname; draft-hu-trill-pseudonode-nickname-02.txt", May 15, 2012.
203Zhai F. Hu et al. 'RBridge: Pseudo-Nickname; draft-hu-trill-pseudonode-nickname-02.txt', May 15, 2012.
Citada por
Patente citante Fecha de presentación Fecha de publicación Solicitante Título
US20160065503 *12 May 20153 Mar 2016Extreme Networks, Inc.Methods, systems, and computer readable media for virtual fabric routing
US20170041222 *7 Ago 20159 Feb 2017Cisco Technology, Inc.Virtual Expansion of Network Fabric Edge for Multihoming of Layer-2 Switches and Hosts
Clasificaciones
Clasificación internacionalH04L12/18, H04L12/751
Clasificación cooperativaH04L45/02, H04L49/60
Eventos legales
FechaCódigoEventoDescripción
21 Feb 2012ASAssignment
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