US9270589B2 - Transparent RBridge - Google Patents

Transparent RBridge Download PDF

Info

Publication number
US9270589B2
US9270589B2 US13/857,021 US201313857021A US9270589B2 US 9270589 B2 US9270589 B2 US 9270589B2 US 201313857021 A US201313857021 A US 201313857021A US 9270589 B2 US9270589 B2 US 9270589B2
Authority
US
United States
Prior art keywords
trill
rbridge
vlan
data packet
edge
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US13/857,021
Other languages
English (en)
Other versions
US20130266011A1 (en
Inventor
Youval Nachum
Tal Mizrahi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Marvell Israel MISL Ltd
Original Assignee
Marvell Israel MISL Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US13/717,095 external-priority patent/US9253141B2/en
Application filed by Marvell Israel MISL Ltd filed Critical Marvell Israel MISL Ltd
Priority to US13/857,021 priority Critical patent/US9270589B2/en
Priority to CN201310125033.4A priority patent/CN103368808B/zh
Assigned to MARVELL ISRAEL (M.I.S.L) LTD. reassignment MARVELL ISRAEL (M.I.S.L) LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MIZRAHI, TAL, NACHUM, YOUVAL
Publication of US20130266011A1 publication Critical patent/US20130266011A1/en
Priority to US15/018,474 priority patent/US9749239B2/en
Application granted granted Critical
Publication of US9270589B2 publication Critical patent/US9270589B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's

Definitions

  • the current disclosure relates to computer networking, including, without limitation, computer networking devices configured to operate in Transparent Interconnection of Lots of Links (TRILL) compliant networks.
  • TRILL Transparent Interconnection of Lots of Links
  • TRILL is a standardized protocol to perform bridging using IS-IS (Intermediate System to Intermediate System) link state routing.
  • An RBridge (Routing Bridge) is a device that implements TRILL and is also known as a “Trill Switch”.
  • An RBridge that is attached to an endnode is called an “edge RBridge”.
  • An RBridge that exclusively forwards encapsulated frames is known as a “transit RBridge”.
  • an ingress edge RBridge encapsulates a native Ethernet packet with a TRILL header, and an egress edge RBridge receives a TRILL-encapsulated packet and removes the TRILL header.
  • a conventional ingress edge RBridge keeps an “endnode table” also known as a “forwarding table” that includes (Media Access Control (MAC) address, TRILL egress switch nickname) pairs, for those MAC addresses currently communicating with endnodes to which the ingress edge RBridge is attached.
  • endnode table also known as a “forwarding table” that includes (Media Access Control (MAC) address, TRILL egress switch nickname) pairs, for those MAC addresses currently communicating with endnodes to which the ingress edge RBridge is attached.
  • MAC Media Access Control
  • TRILL egress switch nickname TRILL egress switch nickname
  • the endnode table becomes extremely large. Also, if one of the MAC addresses in the table has moved to a different egress edge RBridge, it is difficult for the ingress edge RBridge to quickly notice movement. As a result traffic will get lost because the ingress edge RBridge tunnels to the incorrect egress edge RBridge.
  • Some transparent RBridges are targeted for massive scaling data centers and define an efficient architecture to transfer Ethernet packets over TRILL networks.
  • the complexity of data transmissions among Virtual Machines (VMs) over a TRILL compliant network is reduced by scaling down edge RBbridge operation complexity.
  • the edge RBridge operation complexity is scaled down by reducing table sizes at the edge RBridge and simplifying VM location, address and labeling architecture.
  • a transparent edge Routing Bridge includes a first communication unit configured to receive a data packet from an access segment of a network, the data packet including an egress device nickname and at least one Virtual Local Area Network (VLAN) tag; a TRansparent Interconnection of Lots of Links (TRILL) header constructing unit configured to construct a TRILL header based on the VLAN tag; and a second communication unit that transmits the data packet, including the TRILL header, to an egress device corresponding to the egress device nickname via a TRILL compliant interconnection layer.
  • VLAN Virtual Local Area Network
  • TRILL TRansparent Interconnection of Lots of Links
  • an access segment includes a server defining a first virtual machine; and a hypervisor configured to transmit a network control message requesting location information of a second virtual machine defined at a second server.
  • the location information including an egress device nickname and at least one Virtual Local Area Network (VLAN) tag, to insert the location information corresponding to the second virtual machine into a data packet to be sent from the first virtual machine to the second virtual machine, and to transmit the data packet to an ingress edge Routing Bridge (RBridge) configured to send the data packet to the second server over a TRansparent Interconnection of Lots of Links (TRILL) compliant interconnect layer.
  • VLAN Virtual Local Area Network
  • a transparent edge Routing Bridge includes a first communication unit configured to receive a data packet designating at least one Virtual Local Area Network (VLAN) tag in an Ethernet header, the at least one VLAN tag being either a single VLAN tag or a double VLAN tag, corresponding to a destination virtual machine in a server, the transparent edge RBridge executing a lookup on the at least one VLAN tag to determine a nickname of an egress device and a VLAN associated with the egress device; a TRansparent Interconnection of Lots of Links (TRILL) header constructing unit that constructs a TRILL header by appending the egress device nickname to the data packet; and a second communication unit that transmits the data packet, including the TRILL header, to a TRILL compliant interconnection layer.
  • VLAN Virtual Local Area Network
  • a method for forwarding packets on a TRansparent Interconnection of Lots of Links (TRILL) compliant network includes receiving, at an edge Routing Bridge (RBridge) located at an interface between a first access segment and a TRILL compliant interconnecting layer, a data packet including an egress device nickname and at least one Virtual Local Area Network (VLAN) tag; constructing, as executed by a processor of the edge RBridge, a TRILL header based on the egress device nickname and the at least one VLAN tag; determining a next hop device for the transmitting the data packet; and transmitting the data packet, including the TRILL header, through a TRILL compliant interconnect layer to the next hop device.
  • RBridge edge Routing Bridge
  • VLAN Virtual Local Area Network
  • a method for transmitting a data packet on a TRansparent Interconnection of Lots of Links (TRILL) compliant network includes in a first access segment of the TRILL compliant network, defining a first hypervisor and a first virtual machine; transmitting, from the first hypervisor, a network control message requesting to receive location information of a second virtual machine defined at a second access segment of the TRILL compliant network, the location information including a nickname for an egress device associated with the second access segment and at least one Virtual Local Area Network (VLAN) tag; inserting, as executed by a processor of the first access segment, the location information received in response to the control message into an Ethernet packet to be sent from the first virtual machine to the second virtual machine; and providing the Ethernet packet from the first access segment to an ingress edge Routing Bridge (RBridge) located at an interface between the first access segment and an interconnect layer of the TRILL compliant network.
  • RBridge ingress edge Routing Bridge
  • a method for forwarding packets on a TRansparent Interconnection of Lots of Links (TRILL) compliant network includes receiving, at a first edge Routing Bridge (RBridge) located at an interface between a first access segment and an interconnecting layer of the TRILL compliant network, a data packet designating either a single Virtual Local Area Network (VLAN) tag or a double VLAN tag in an Ethernet header, the single or double VLAN tag corresponding to a virtual machine defined in a second access segment of the TRILL compliant network; executing, via a processor of the first edge RBridge, a lookup using at least the single or double VLAN tag to determine an egress device nickname and at least one VLAN tag corresponding to a second edge RBridge associated with the second access segment; and appending a TRILL header to the data packet, the TRILL header including the egress device nickname and the at least one VLAN tag.
  • RBridge first edge Routing Bridge
  • FIG. 1 shows a TRILL compliant network 100 according to an embodiment of the present disclosure
  • FIGS. 2A and 2B show variations of example messages shown in FIGS. 1 and 5 ;
  • FIG. 3A shows a flowchart of operations of the hypervisor in some example embodiments
  • FIG. 3B shows a flowchart of operations of the ingress edge RBridge in some example embodiments
  • FIG. 4 shows further variations of example messages shown in FIGS. 1 and 5 ;
  • FIG. 5 shows a TRILL compliant network 600 according to another embodiment of the present disclosure.
  • FIGS. 6A and 6B show example operations explaining how the endnode lookup tables of the example embodiments of the present disclosure are updated.
  • the ingress edge RBridge encapsulates a native Ethernet packet with a TRILL header and the egress edge RBridge then receives a TRILL-encapsulated packet and removes the TRILL header.
  • the ingress edge RBridge In order to encapsulate the native Ethernet packet with a TRILL header, traditionally the ingress edge RBridge must keep an “endnode table” including (Media Access Control (MAC) address, egress RBridge nickname) pairs, for those MAC addresses or nodes currently communicating with endnodes to which the edge RBridge is attached.
  • the conventional ingress edge RBridge has a TRILL header constructing unit that constructs a TRILL header or frame based on information looked up in the endnode table of the ingress edge RBridge.
  • a conventional ingress edge RBridge must keep track of VM location and labeling (native Virtual Local Area Network (VLAN) or Fine Grained Label (FGL), and MAC address fixed or translated) via the endnode table. If the ingress edge RBridge has many attached endnodes, the endnode table becomes extremely large.
  • VLAN Virtual Local Area Network
  • FGL Fine Grained Label
  • endnode table describing the VM location and labeling is distributed from the ingress edge RBridge to the endnodes (for example, VMs or the hypervisors).
  • the endnode for example, a VM or a hypervisor
  • the edge RBridge complexity is greatly simplified and there is no longer a requirement for the ingress edge RBridge to perform a conventional MAC address lookup.
  • the ingress edge RBridge according to one or more example embodiments of the present disclosure is not required to know about the nodes with which a particular endnode is communicating, thereby reducing the size of a table at the edge RBridge.
  • the edge RBridges in the present disclosure can generally be considered somewhat similar to conventional transit RBridges in that they are not required to maintain endnode tables. This is because unlike conventional systems, the endnodes of one or more example embodiments of the present disclosure maintain the endnode table(s). However, unlike conventional transit RBridges and similar to conventional edge RBridges, the edge RBridges of one or more example embodiments include a TRILL header construction unit that constructs TRILL headers from Ethernet frames transmitted from an endnode.
  • the ingress RBridge simply encapsulates the Ethernet frame with a TRILL header and transmits the TRILL encapsulated Ethernet frame to the TRILL compliant interconnection layer.
  • FIG. 1 shows a TRILL compliant network 100 according to an embodiment of the present disclosure.
  • the TRILL compliant network 100 includes a plurality of endnodes (for example servers 200 , 300 , 400 , hypervisors 20 , 30 , virtual machines 21 , 22 , 23 , 31 , 32 , 33 , etc., which are shown for illustrative purposes).
  • a transparent edge RBridge (referred to herein as an edge RBridge).
  • FIG. 1 shows that edge RBridge 25 is located at the edge of server 200 , that edge RBridge 35 is located at the edge of server 300 , and that edge RBridge 45 is located at the edge of server 400 .
  • some or all of the servers include a hypervisor.
  • FIG. 1 shows hypervisors 20 , 30 for illustrative purposes.
  • the hypervisor is software, firmware, or hardware associated with the respective server that defines and runs Virtual Machines (VMs), e.g., 21 , 22 , and 23 ; and 31 , 32 , and 33 , respectively.
  • VMs Virtual Machines
  • the VMs run by a particular server are associated with individual VLANs which may include one or more of traditional 12 bit VLANs and/or 24 bit FGLs.
  • some or all of the servers define and run VMs without the use of a hypervisor. Although three VMs are arbitrarily shown as being defined in server 200 and server 300 , respectively, more or less VMs may be defined.
  • the servers 200 , 300 , and 400 are connected to a TRILL campus 110 also known as TRILL compliant interconnection layer via their respective edge RBridges.
  • TRILL campus 110 includes an arbitrary number of transit RBridges (not shown) which function to connect the various edge RBridges to one another, in an embodiment.
  • the hypervisor 20 maintains multiple endnode tables 26 - 21 , 26 - 22 , and 26 - 23 , one for each of the attached VMs 21 , 22 , and 23 .
  • the end node tables each include a record of the one or more nodes with which the respective VMs are in communication. It is noted that in other example embodiments (see, e.g., FIG. 5 ) each VM maintains its own endnode table rather than having the hypervisor 20 maintain the endnode table as described above.
  • FIGS. 2A and 2B The contents of Ethernet frame 500 A are shown in FIGS. 2A and 2B .
  • FIG. 2A shows a case where the location information includes a double VLAN tag
  • the Ethernet frame 500 A includes the MAC address of VM 31 (MAC-VM 31 ), the MAC address of VM 23 (MAC-VM 23 ), the customer VLAN of VM 23 (VLAN-C 23 ) and the service VLAN of VM 23 (VLAN-S 23 ).
  • FIG. 2B in a case where the location information includes one VLAN tag, the Ethernet frame 500 A includes MAC-VM 31 , MAC-VM 23 , and the VLAN-S 23 .
  • FIG. 3A shows a flowchart describing that the Hypervisor 20 receives Ethernet frame 500 A at 20 - 1 , an in an embodiment, determines which endnode table to use by recognizing which VM the Ethernet frame 500 A is from at 20 - 2 .
  • Ethernet frame 500 A is determined to be from VM 23 as indicated by at least one of VLAN-C 23 , VLAN-S 23 , and MAC-VM 23 and, therefore, endnode table 26 - 23 is used.
  • the hypervisor 20 performs a lookup of MAC-VM 31 using table 26 - 23 in order to find the corresponding remote appointed forwarder RBridge which is associated with MAC-VM 31 .
  • MAC-VM 31 is associated with the egress nickname of edge RBidge 35 .
  • the Hypervisor 20 outputs Ethernet frame 500 B, which includes the egress nickname of RBridge 35 that is associated with VM 31 and either one VLAN tag or a double VLAN tag depending on the particular application.
  • the ingress RBridge 25 receives the Ethernet frame 500 B from Hypervisor 20 and then encapsulates it with a TRILL header so as to be an encapsulated TRILL frame 500 C by using the egress device nickname of the egress RBridge 35 and the VLAN tag VLAN-S 23 or the double VLAN tag VLAN-C 23 and VLAN-S 23 .
  • FIG. 3B shows that the ingress RBridge 25 receives the Ethernet frame 500 B from the Hypervisor 20 at 25 - 1 .
  • the ingress RBridge 25 includes a TRILL header constructing unit (not show) that constructs a TRILL header.
  • the TRILL header constructing unit translates the encoded VLAN tag (VLAN-S 23 ) or the encoded double VLAN tag (VLAN-C 23 and VLAN-S 23 ) to the TRILL VLAN-X or TRILL FGL, respectively.
  • the ingress edge RBridge 25 then outputs the encapsulated TRILL frame 500 C to the TRILL compliant interconnect layer 110
  • the ingress edge RBridge 25 receives the Ethernet frame 500 B via a first communication unit (not shown), in an embodiment.
  • the first communication unit receives and transmits information while in others the first communication unit only receives information.
  • the ingress RBridge 25 then outputs the encapsulated TRILL frame 500 C to the TRILL compliant interconnect layer 110 using a second communication unit (not shown).
  • the second communication unit receives and transmits information, while in others the second communication unit only transmits information.
  • the ingress edge RBridge 25 when an Ethernet frame 500 B having an egress device nickname and VLAN tag (or double VLAN tag in the case of FGL) is received by the ingress edge RBridge 25 , the ingress edge RBridge 25 is configured to simply encapsulate the Ethernet Frame 500 B with a TRILL header using information included in the Ethernet frame 500 B and then simply forward the TRILL encapsulated Ethernet frame 500 C to the edge RBridge 35 whose nickname is in the destination address.
  • the ingress RBridge 25 does not receive an Ethernet frame with an unknown destination address and therefore there is no need for the ingress RBridge to maintain the above-mentioned large endnode forwarding tables.
  • the edge RBridges described herein can easily integrate with Ethernet based networks and reduce TRILL encapsulation complexity that would conventionally be performed at an edge RBridge.
  • edge RBridges described herein can also support applications where Ethernet frames are encapsulated by Ethernet directly (e.g., with no IP layer).
  • the egress edge RBridge 35 is a conventional egress edge RBridge
  • the egress edge RBridge decapsulates the encapsulated TRILL frame 500 C and remaps the VLAN or FGL to the destination VLAN (VM 31 , MAC-VM 31 ).
  • the egress edge RBridge 35 is a same type of edge RBridge as the above-described ingress edge RBridge 25 and the hypervisor 30 is stores endnode tables in a similar manner as the hypervisor 20 , then the egress edge RBridge 35 forwards the encapsulated TRILL frame 500 C to the hypervisor 30 and the hypervisor decapsulates the encapsulated TRILL frame 500 C and remaps the VLAN or FGL to the destination VLAN (VM 31 , MAC-VM 31 ).
  • ingress edge RBridge 25 includes a first communication unit, a TRILL header constructing unit, and a second communication unit as discussed above, for example.
  • the Ethernet frame 500 B in the example embodiment designates a single or a double VLAN tag (e.g., here a double VLAN tag) that corresponds to a destination VM (e.g., VM 31 ) in the server 300 .
  • the ingress edge RBridge 25 in this example embodiment executes a lookup on the double VLAN tag to determine a nickname of an egress device and a VLAN associated with the egress device.
  • the ingress edge RBridge 25 executes this lookup, in an embodiment, using a processor (not shown) or the like.
  • the TRILL header constructing unit constructs a TRILL header by appending the egress device nickname 35 to the Ethernet frame 500 B and by translating the double VLAN tag (VLAN-C 23 , VLAN-S 23 ) to FGL.
  • VM-ID VM identity
  • egress RBridge nickname a remote appointed forwarded RBridge (egress RBridge nickname) with the assigned VLAN tag or double VLAN tag.
  • IP Internet Protocol
  • FC Fiber Channel
  • D_ID Destination IDentity
  • S_ID Source IDentity
  • the endnode table of the hypervisor maps the destination VM-ID to the destination MAC address, and VLAN-Service (VLAN-S) or VLAN-S and VLAN-Customer (VLAN-C). That is, mapping the source VLAN-C to the destination VLAN-C is optional and resolved by IETF TRILL RBridge VLAN mapping techniques. On the other hand, mapping the source VLAN-S is mapped to (VLAN-X (or FGL), egress device nickname), to the destination VLAN-S. This mapping can be resolved in several options.
  • FIG. 6A shows one option which is to have the endnode (Hypervisor 20 or a VM 23 ) transmit a network control message to the ingress edge RBridge 25 at 24 - 1 A.
  • the network control message may be, for instance, an End Station Address Distribution Information (ESADI) message as defined by the ESADI protocol.
  • ESADI End Station Address Distribution Information
  • the ingress edge RBridge 25 transmits the message to the egress edge RBridge 35 using control plane protocol in order to ascertain the address information and then reports back the egress nickname RBridge to the endnode at 24 - 3 A.
  • ESADI End Station Address Distribution Information
  • the network control message does not have to be sent according to the ESADI protocol. Therefore, a second option is to have the endnode transmit a network control message that identifies the egress Rbridge and a double VLAN tag. This is because FGL indicates the correct egress RBridge at the transport layer and identifies the VLAN at which the destination VM is located. With this information, the ingress edge RBridge 25 is able to report back the egress nickname RBridge to the endnode. Using this information, the endnode can transmit an Ethernet packet to the ingress edge RBridge 25 that already includes the egress nickname RBridge. As a result, the ingress edge RBridge 25 is not required to keep a forwarding table that includes (MAC address, TRILL egress RBridge nickname) pairs and, therefore, no MAC address lookup in a forwarding table is required.
  • FIG. 6B shows a third option.
  • the hypervisor is not required.
  • the endnode transmits an ARP request to a VM in another server.
  • the ARP request includes a destination VM identity lookup request and an Ethernet frame conforming with 802.1ad and having VLAN-Service (VLAN-S) and VLAN-Customer (VLAN-C).
  • VLAN-S VLAN-Service
  • VLAN-C VLAN-Customer
  • the ingress edge RBridge 25 traps the ARP request and encapsulates it with an encoded FGL in a TRILL header.
  • the ingress edge RBridge 25 transmits this message to the egress edge RBridge.
  • the egress edge RBridge 35 decapsulates the TRILL header, remaps the FGL and broadcasts the ARP request locally with the Ethernet frame having VLAN-C and VLAN-S.
  • the second endnode receives the ARP request and sends out an ARP reply as an Ethernet Frame.
  • the edge RBridge 35 traps the ARP reply for caching and encapsulates the Ethernet frame as a TRILL header, and transmits the ARP reply to the edge RBridge 25 .
  • the edge RBridge 25 traps the ARP reply for caching, decapsulates the TRILL header and sends the ARP reply as the Ethernet frame with 802.1ad VLAN-C, VLAN-S to the endnode having transmitted the ARP request at 24 - 1 B.
  • the ARP reply indicating at least a MAC address of the egress RBridge 35 .
  • the VM that sent out the ARP request receives the ARP reply, and then updates a lookup table establishing a correspondence between the double VLAN tag, the egress device nickname of the egress edge RBridge, and the VLAN tag corresponding to the second edge RBridge.
  • the ingress edge RBridge 25 reports this information back to endnode (e.g., the hypervisor 20 or the VM 23 depending on the particular application), which is able to transmit an Ethernet frame that includes both the egress RBridge nickname and the VLAN tag or double VLAN tag to the ingress RBridge.
  • endnode e.g., the hypervisor 20 or the VM 23 depending on the particular application
  • the endnode tables may be populated in other ways that are substantially the same way that a conventional edge RBridge populates entries in its tables. For example, by learning from source ingress packets it decapsulates, from End Station Address Distribution Information (ESADI) protocol, by querying a directory, by having some entries configured, by sending a TRILL Hello, etc.
  • ESADI End Station Address Distribution Information
  • the endnode e.g., a VM or a hypervisor
  • the RBridge complexity is greatly simplified and there is no longer a requirement for the ingress edge RBridge 25 to perform a MAC address lookup. Instead, the ingress edge RBridge 25 derives from the VLANs, necessary forwarding information for forwarding packets through the TRILL campus.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)
US13/857,021 2012-04-04 2013-04-04 Transparent RBridge Active 2034-02-13 US9270589B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US13/857,021 US9270589B2 (en) 2012-04-04 2013-04-04 Transparent RBridge
CN201310125033.4A CN103368808B (zh) 2012-04-04 2013-04-07 用于在网络中传输分组的装置、系统和方法
US15/018,474 US9749239B2 (en) 2012-04-04 2016-02-08 Transparent Rbridge

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201261620337P 2012-04-04 2012-04-04
US201261645544P 2012-05-10 2012-05-10
US13/717,095 US9253141B2 (en) 2011-12-16 2012-12-17 Scaling address resolution for massive data centers
US13/857,021 US9270589B2 (en) 2012-04-04 2013-04-04 Transparent RBridge

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/018,474 Continuation US9749239B2 (en) 2012-04-04 2016-02-08 Transparent Rbridge

Publications (2)

Publication Number Publication Date
US20130266011A1 US20130266011A1 (en) 2013-10-10
US9270589B2 true US9270589B2 (en) 2016-02-23

Family

ID=49292256

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/857,021 Active 2034-02-13 US9270589B2 (en) 2012-04-04 2013-04-04 Transparent RBridge
US15/018,474 Active US9749239B2 (en) 2012-04-04 2016-02-08 Transparent Rbridge

Family Applications After (1)

Application Number Title Priority Date Filing Date
US15/018,474 Active US9749239B2 (en) 2012-04-04 2016-02-08 Transparent Rbridge

Country Status (2)

Country Link
US (2) US9270589B2 (zh)
CN (1) CN103368808B (zh)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9083645B2 (en) * 2012-09-07 2015-07-14 Dell Products L.P. Systems and methods providing reverse path forwarding compliance for a multihoming virtual routing bridge
CN103780486B (zh) * 2012-10-26 2017-03-08 杭州华三通信技术有限公司 一种trill网络中的镜像报文传输方法和设备
US8953624B2 (en) * 2012-12-20 2015-02-10 Cisco Technology, Inc. Intelligent host route distribution for low latency forwarding and ubiquitous virtual machine mobility in interconnected data centers
US9197553B2 (en) 2013-03-29 2015-11-24 Cisco Technology, Inc. Using a virtual internet protocol address to represent dually connected hosts in an internet protocol overlay network
US9215147B2 (en) * 2013-07-15 2015-12-15 Cisco Technology, Inc. Flexible and scalable monitoring in a TRILL network
CN104753790B (zh) * 2013-12-26 2018-05-04 华为技术有限公司 一种基于trill网络的报文传输方法及设备
CN105635224B (zh) * 2014-11-07 2021-01-22 中兴通讯股份有限公司 一种信息分发方法及系统
US10437770B2 (en) * 2015-01-28 2019-10-08 Avago Technologies International Sales Pte. Limited Method and apparatus for providing virtual machine information to a network interface
US10503442B2 (en) 2015-01-28 2019-12-10 Avago Technologies International Sales Pte. Limited Method and apparatus for registering and storing virtual machine unique information capabilities
CN106161253B (zh) * 2016-06-23 2020-12-25 新华三技术有限公司 一种报文处理方法及装置
CN107787020B (zh) 2016-08-26 2020-12-08 华为技术有限公司 一种sfc网络中同步拓扑信息的方法及路由网元

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100165995A1 (en) * 2008-12-29 2010-07-01 Juniper Networks, Inc. Routing frames in a computer network using bridge identifiers
US7787480B1 (en) * 2009-03-04 2010-08-31 Juniper Networks, Inc. Routing frames in a trill network using service VLAN identifiers
US20110299406A1 (en) * 2010-06-02 2011-12-08 Brocade Communications Systems, Inc. Path detection in trill networks
US20110299531A1 (en) * 2010-06-08 2011-12-08 Brocade Communications Systems, Inc. Flooding packets on a per-virtual-network basis
US20120014261A1 (en) * 2010-07-14 2012-01-19 Cisco Technology, Inc. Monitoring A Flow Set To Detect Faults
US20120014387A1 (en) * 2010-05-28 2012-01-19 Futurewei Technologies, Inc. Virtual Layer 2 and Mechanism to Make it Scalable
US20120177045A1 (en) * 2011-01-07 2012-07-12 Berman Stuart B Methods, systems and apparatus for the interconnection of fibre channel over ethernet devices using a trill network
US20120243539A1 (en) * 2011-03-21 2012-09-27 Avaya Inc. Usage of masked ethernet addresses between transparent interconnect of lots of links (trill) routing bridges
US20120278804A1 (en) * 2010-11-14 2012-11-01 Brocade Communications Systems, Inc. Virtual machine and application movement over a wide area network
US8601133B1 (en) * 2010-12-14 2013-12-03 Juniper Networks, Inc. Highly scalable data center architecture with address resolution protocol (ARP)-free servers

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7706265B2 (en) * 2006-10-30 2010-04-27 Telefonaktiebolaget L M Ericsson (Publ) Decentralized node, access edge node, and access node for aggregating data traffic over an access domain, and method thereof
CN102577257B (zh) * 2011-04-27 2014-02-19 华为技术有限公司 一种实现虚拟局域网标识转换的方法及装置
CN102223303A (zh) * 2011-06-14 2011-10-19 杭州华三通信技术有限公司 一种基于多链接透明互联的负载均衡方法和路由桥
CN102307144B (zh) * 2011-08-19 2014-06-11 杭州华三通信技术有限公司 一种trill网络中dhcp报文转发方法和路由桥
CN102387078B (zh) * 2011-10-19 2014-11-12 杭州华三通信技术有限公司 一种trill网络中维护邻居关系的方法和路由桥

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100165995A1 (en) * 2008-12-29 2010-07-01 Juniper Networks, Inc. Routing frames in a computer network using bridge identifiers
US7787480B1 (en) * 2009-03-04 2010-08-31 Juniper Networks, Inc. Routing frames in a trill network using service VLAN identifiers
US20120014387A1 (en) * 2010-05-28 2012-01-19 Futurewei Technologies, Inc. Virtual Layer 2 and Mechanism to Make it Scalable
US20110299406A1 (en) * 2010-06-02 2011-12-08 Brocade Communications Systems, Inc. Path detection in trill networks
US20110299531A1 (en) * 2010-06-08 2011-12-08 Brocade Communications Systems, Inc. Flooding packets on a per-virtual-network basis
US20120014261A1 (en) * 2010-07-14 2012-01-19 Cisco Technology, Inc. Monitoring A Flow Set To Detect Faults
US20120278804A1 (en) * 2010-11-14 2012-11-01 Brocade Communications Systems, Inc. Virtual machine and application movement over a wide area network
US8601133B1 (en) * 2010-12-14 2013-12-03 Juniper Networks, Inc. Highly scalable data center architecture with address resolution protocol (ARP)-free servers
US20120177045A1 (en) * 2011-01-07 2012-07-12 Berman Stuart B Methods, systems and apparatus for the interconnection of fibre channel over ethernet devices using a trill network
US20120243539A1 (en) * 2011-03-21 2012-09-27 Avaya Inc. Usage of masked ethernet addresses between transparent interconnect of lots of links (trill) routing bridges

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
IEEE SA-802.1ad-2005-IEEE Standard for Local and Metropolitan Area Networks, "Virtual Bridged Local Area Networks, Amendment 4: Provider Bridges", IEEE Computer Society.
RFC 6325-Routing Bridges (RBridges) Base Protocol Specification.

Also Published As

Publication number Publication date
US20130266011A1 (en) 2013-10-10
CN103368808B (zh) 2019-03-22
US9749239B2 (en) 2017-08-29
CN103368808A (zh) 2013-10-23
US20160156554A1 (en) 2016-06-02

Similar Documents

Publication Publication Date Title
US9749239B2 (en) Transparent Rbridge
US11025677B2 (en) Using symmetric and asymmetric flow response paths from an autonomous system
EP2600573B1 (en) Method for transmitting addresses correspondence relationship in second-layer protocol using link status routing
US11252199B2 (en) Redirecting packets in an autonomous system
US9281955B2 (en) Interoperability of data plane based overlays and control plane based overlays in a network environment
US9432213B2 (en) IP forwarding across a link state protocol controlled ethernet network
WO2021196717A1 (zh) 组播流量传输方法、装置、通信节点及存储介质
EP2580900B1 (en) Enhancing DS-Lite with private IPv4 reachability
US9504016B2 (en) Optimized multicast routing in a Clos-like network
EP2750329B1 (en) Method and device for sending internet protocol packets
CN101552727B (zh) 一种报文发送和接收方法及运营商边缘路由器
US20130343394A1 (en) Method and Apparatus for Converting Virtual Local Area Network Identity
CN105453523A (zh) 大型数据中心中对虚拟机移动性的处理
US11522828B2 (en) Virtualized network functions through address space aggregation
CN104660508A (zh) 一种报文转发方法及装置
US7480306B2 (en) Interworking functionality
CN117811875A (zh) 一种家庭互通网络访问方法和装置
CN104378302A (zh) 应用链路状态路由的二层协议中的地址对应关系发送方法
CN110620715B (zh) 虚拟扩展局域网通信方法、隧道端点和控制器
US8971289B2 (en) Maintaining point of presence for clients roaming within a layer 2 domain
CN105323084B (zh) 三层网管管理trill网络的方法、装置及系统

Legal Events

Date Code Title Description
AS Assignment

Owner name: MARVELL ISRAEL (M.I.S.L) LTD., ISRAEL

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NACHUM, YOUVAL;MIZRAHI, TAL;SIGNING DATES FROM 20130404 TO 20130405;REEL/FRAME:030187/0670

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 8