Network layer multicasting in trill networks

Abstract

Systems and techniques for performing network layer multicasting in a TRILL network are described. Some embodiments provide a system that receives multicast packet that includes a network-layer multicast-address. The multicast packet can be received on a first multicast tree associated with a first virtual network. Next, the system can determine, based on the network-layer multicast-address, a second multicast tree associated with a second virtual network over which the multicast packet is to be forwarded. The system can then forward the multicast packet on the first multicast tree associated with the first virtual network, and forward a copy of the multicast packet on the second multicast tree associated with the second virtual network.

Description

BACKGROUND

Technical Field

This disclosure relates to computer networking. More specifically, this disclosure relates to systems and techniques for network layer multicasting in TRILL (Transparent Interconnection of Lots of Links) networks.

Related Art

The insatiable demand for bandwidth and the ever increasing size and complexity of computer networks has created a need for increasing the bandwidth and improving manageability of computer networks.

Computer networks often use multicasting to efficiently distribute high bandwidth content (e.g., streaming video) to multiple end hosts in the network. In multicasting, copies of packets are forwarded over a multicast tree in the network. In some approaches, the network supports a single multicast tree for a given source and multicast address. For purposes of load balancing and failure recovery, it is generally desirable to support multiple multicast trees for a given network layer source and multicast address.

SUMMARY

Some embodiments of the present invention provide systems and techniques for performing network layer multicasting in TRILL networks. Specifically, some embodiments provide a system (e.g., a switch) which can receive a multicast packet that includes a network-layer multicast-address. The multicast packet can be received on a first multicast tree associated with a first virtual network. Next, the system can determine, based on the network-layer multicast-address, a second multicast tree associated with a second virtual network over which the multicast packet is to be forwarded. The system can then forward the multicast packet on the first multicast tree associated with the first virtual network, and forward a copy of the multicast packet on the second multicast tree associated with the second virtual network. In this disclosure, unless otherwise stated, the phrase “based on” means “based solely or partly on.”

In some embodiments, the multicast packet can include a first multicast tree identifier associated with the first multicast tree, and the copy of the multicast packet can include a second multicast tree identifier associated with the second multicast tree. The first multicast tree identifier can be a nickname of a routing bridge at the root of the first multicast tree, and the second multicast tree identifier can be a nickname of a routing bridge at the root of the second multicast tree.

The first virtual network and the second virtual network can be VLANs (Virtual Local Area Networks). The network-layer multicast-address can be an IP (Internet Protocol) multicast address. The multicast packet can be a TRILL multicast packet. The first multicast tree and the second multicast tree can be TRILL multicast trees.

In some embodiments, the system can determine an internal multicast group identifier based on the network-layer multicast-address and a network-layer source-address of the multicast packet, and forward the multicast packet based on the internal multicast group identifier.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates a TRILL network in accordance with some embodiments of the present invention.

FIG. 2 illustrates a portion of an Ethernet packet which includes a TRILL header in accordance with some embodiments of the present invention.

FIG. 3A illustrates how an internal multicast group identifier can be determined in accordance with some embodiments of the present invention.

FIGS. 3B and 3C illustrate different multicast trees for the same source and multicast address in accordance with some embodiments of the present invention.

FIG. 3D illustrates how internal multicast group identifiers can be determined in accordance with some embodiments of the present invention.

FIG. 3E illustrates how an internal multicast group identifier can be used to determine a set of egress ports in accordance with some embodiments of the present invention.

FIG. 4 illustrates how an RBridge can perform network layer multicasting in a TRILL network in accordance with some embodiments of the present invention.

FIG. 5 illustrates a switch in accordance with some embodiments of the present invention.

FIG. 6A presents a flowchart that illustrates a process for forwarding packets based on an internal multicast group identifier in accordance with some embodiments of the present invention.

FIG. 6B presents a flowchart that illustrates a process for performing network layer multicasting in a TRILL network in accordance with some embodiments of the present invention.

FIG. 7 illustrates a system in accordance with some embodiments 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 principles and features disclosed herein.

TRILL (Transparent Interconnection of Lots of Links)

TRILL combines the advantages of bridging and routing. Bridges (e.g., devices that perform layer-2 forwarding) can transparently connect multiple links to create a single local area network. However, the topology on which traffic is forwarded in a bridged network must be a tree to prevent loops. Unfortunately, forwarding the traffic over a tree causes traffic concentration on the links that correspond to the tree edges, leaving other links completely unutilized. Unlike bridges, Internet Protocol (IP) routers (e.g., devices that perform IP forwarding) do not need to create a spanning tree for forwarding traffic. However, routers that forward IP traffic require more configuration than bridges, and moving nodes in an IP network requires changing the IP address of the nodes. Each link in an IP network is associated with an address prefix, and all nodes on that link must have that IP prefix. If a node moves to another link that has a different IP prefix, the node must change its IP address. Unless otherwise stated, the term “IP” refers to both “IPv4” and “IPv6” in this disclosure.

A TRILL network includes “routing bridges” (referred to as RBridges) which route packets, but like bridges, learn layer-2 address locations through receipt of packets. Since packets are routed, packet forwarding is not limited to a spanning tree. Also, since a hop count is included in a TRILL packet, packets do not circulate forever in the network in the presence of loops. Further, since the layer-2 address locations are learned, a TRILL network allows IP nodes to move from one link to another in the network without any restrictions.

FIG. 1 illustrates a TRILL network in accordance with some embodiments of the present invention. TRILL network 100 can be a service provider's network which includes core RBridges 102 and 104 and edge RBridges 106, 108, and 110. RBridges 102, 106, 108, and 110 are coupled to customer devices, whereas RBridge 104 is not. Specifically, port P3 on RBridge 102 can be coupled to a device in customer C3's network at site S1; ports labeled P1 on RBridges 106, 108, and 110 can be coupled to devices in customer C1's networks at sites S2, S3, and S4, respectively; and port P3 on RBridge 110 can be coupled to a device in customer C3's network at site S5. Note that the port numbers in FIG. 1 match the customer numbers, i.e., ports labeled P1 are associated with customer C1, ports labeled P3 are associated with customer C3, etc. This has been done for ease of discourse. In general, any port on any RBridge can potentially be assigned to one or more virtual networks that are associated with one or more customers.

A virtual local area network (VLAN) in a customer's network may span multiple customer sites. For example, VLANs 112 and 114 in customer C3's network include nodes in sites S1 and S5. Similarly, VLANs 116 and 118 in customer C1's network include nodes in sites S2 and S3, and VLAN 120 in customer C1's network includes nodes in sites S3 and S4.

Nodes that belong to the same VLAN, but which are located at different sites, can communicate with each other transparently through TRILL network 100. Specifically, the ingress RBridge can encapsulate a packet (e.g., an Ethernet packet with or without one or more VLAN tags) received from a customer and route the packet within TRILL network 100 using a TRILL header. The egress RBridge can then strip the TRILL header and send the original customer packet on the appropriate port. For example, packet 122 can originate in customer C3's network at site S1, and be received on port P3 of RBridge 102 with a VLAN tag associated with VLAN 112. Next, RBridge 102, which is the ingress RBridge for this packet, can encapsulate packet 122 by adding a TRILL header to obtain packet 124 (the TRILL header is the shaded portion in packet 124). Next, the TRILL header of packet 124 can be used to route packet 124 through TRILL network 100 until packet 124 reaches RBridge 110, which is the egress RBridge for the packet. RBridge 110 can then strip away the TRILL header on packet 124 to obtain the original packet 122, and send packet 122 on port P3 so that the packet can be delivered to the intended destination in VLAN 112 in customer C3's network at site S5. In FIG. 1, the packet that is received at the ingress RBridge and the packet that is sent from the egress RBridge are shown to be the same. However, these packets can be different. For example, if VLAN translation is being performed, then the packet that is received at the ingress RBridge and the packet that is sent from the egress RBridge can have different VLAN tags.

Further details on TRILL and RBridges can be found in Radia Perlman, Rbridges: Transparent Routing, Proceedings of IEEE INFOCOM, 2004, which is incorporated herein by reference. Details on TRILL and RBridges can also be found in Joe Touch and Radia Perlman, TRILL: Problem and Applicability, IETF RFC 5556, May 2009, which is incorporated herein by reference. Details of the TRILL packet format and RBridge forwarding can be found in IETF draft “RBridges: Base Protocol Specification,” available at http://tools.iet.org/html/draft-ietf-trill-rbridge-protocol-16, which is incorporated herein by reference.

Although some examples in this disclosure are presented in the context of a TRILL network that includes RBridges, the present invention is not limited to TRILL networks or RBridges. The terms “frame” or “packet” generally refer to a group of bits. The use of the term “frame” is not intended to limit the present invention to layer-2 networks. Similarly, the use of the term “packet” is not intended to limit the present invention to layer-3 networks. Unless otherwise stated, the terms “frame” or “packet” may be substituted with other terms that refer to a group of bits, such as “cell” or “datagram.”

Network Virtualization

Network virtualization enables a service provider to provision virtual networks (VNs) over a common network infrastructure. To a user on a VN it appears as if the traffic is being carried over a separate network that has been specifically built for the user. However, in reality, the traffic from multiple VNs may be carried over a common network infrastructure.

Network virtualization has many uses. For example, network virtualization can be used to create multiple, logically distinct networks on the same physical network to comply with government regulations. Other uses of network virtualization include, but are not limited to, partitioning network resources between different organizations in a company, reducing network costs and simplifying network management during a merger between two companies by provisioning a virtual private network for each company.

One approach for supporting network virtualization is to duplicate resources (e.g., routers, switches, etc.) in the network so that the resources can be provisioned on a per-customer basis. However, this approach is impractical because it is costly and it is not scalable.

Some embodiments of the present invention implement network virtualization and/or partitioning in the TRILL network by embedding a VPN identifier in a TRILL option field in the TRILL header. Specifically, the ingress RBridge can determine a VPN identifier for each packet it receives from a customer, and embed the VPN identifier in a TRILL option field in the TRILL header. Next, the VPN identifier can be used to support network virtualization and/or partitioning in the TRILL network. Specifically, once the VPN identifier is embedded into the TRILL header, RBridges in the TRILL network can use the VPN identifier to determine how to handle the packet.

In some embodiments, the system can use a service provider VLAN identifier to implement network virtualization and/or partitioning. Specifically, ingress RBridges can add appropriate S-tags to packets received from customers (note that the S-tag based approach may not work for incoming packets that already have an S-tag). Next, the S-tag can be used to implement virtualization and/or partitioning in the network.

Packet Format

FIG. 2 illustrates a portion of an Ethernet packet which includes a TRILL header in accordance with some embodiments of the present invention. The packet shown in FIG. 2 is for illustration purposes only, and is not intended to limit the present invention.

Packet 200 can include one or more of the following fields: outer MAC (medium access control) addresses 202, outer VLAN tag 204, TRILL header field 206, TRILL option field 208, inner MAC addresses 210, and inner VLAN tags 212. Typically, the packet is transmitted from top to bottom, i.e., the bits associated with outer MAC addresses 202 will appear on the transmission medium before the bits associated with outer VLAN tag 204 appear on the transmission medium, and so forth. The contents of these fields and their uses are discussed below.

Outer MAC addresses 202 can include outer destination MAC address 214 and outer source MAC address 216. These MAC addresses and outer VLAN tag 204 typically change at each TRILL hop as the packet traverses the service provider's network. Specifically, at each hop, outer source MAC address 216 is associated with the MAC address of the source node (e.g., RBridge) for that hop, outer destination MAC address 214 is associated with the MAC address of the destination node (e.g., RBridge) for that hop, and outer VLAN tag 204 is associated with the VLAN that includes the source node and the destination node for that hop.

Outer VLAN tag 204 can include Ethernet type field 218 and outer VLAN identifier 220. The value of Ethernet type field 218 can indicate that the next field is a VLAN identifier. VLAN identifier 220 can be used in the service provider's network to create multiple broadcast domains.

TRILL header field 206 can include Ethernet type field 222 and TRILL header 224. The value of Ethernet type field 222 can indicate that the next field is a TRILL header. TRILL header 224 can include information for routing the packet through a TRILL network that is embedded in the service provider's network. Specifically, as shown in FIG. 2, TRILL header 224 can include version field 246 which indicates the TRILL version, reserved field 248 which may be reserved for future use, multicast field 250 which indicates whether this packet is a multicast packet, TRILL option length 252 which indicates the length (in terms of 32-bit words) of any TRILL option field that follows the TRILL header, and hop count 254 which may be decremented at each RBridge as the packet traverses the service provider's network.

TRILL header 224 also includes egress RBridge nickname 256 and ingress RBridge nickname 258. Ingress RBridge nickname 258 corresponds to the ingress RBridge which receives the packet from the customer's network, and, for unicast packets, egress RBridge nickname 256 corresponds to the egress RBridge which sends the packet to the customer's network. For multicast packets, egress RBridge nickname 256 corresponds to the egress RBridge at the root of the multicast tree on which the packet is to be forwarded. For example, in FIG. 1, when packet 122 is received at ingress RBridge 102, ingress RBridge 102 can use the header information in packet 122 to determine that packet 122 needs to be routed to egress RBridge 110. Next, ingress RBridge 102 can add TRILL header field 206 to packet 122 to obtain packet 124. Specifically, RBridge 102 can set ingress RBridge nickname 258 in packet 124's TRILL header to RBridge 102's nickname, and set egress RBridge nickname 256 in packet 124's TRILL header to RBridge 110's nickname. RBridge 102 can then forward packet 124 based solely or partly on packet 124's TRILL header.

TRILL option field 208 can include bit-encoded options and one or more options encoded in a TLV (type-length-value) format. Specifically, TRILL option field 208 can include bit-encoded options 260 which are one-bit option flags, and TLV-encoded option 226. For example, a 20-bit VPN identifier can be encoded as a TLV-encoded option. Specifically, the value of type field 262 can indicate that this option specifies a VPN identifier. Length field 264 can indicate the length of the data portion of the TLV-encoded option in octets. In the packet shown in FIG. 2, TLV-encoded option 226 is used for specifying a 20-bit VPN identifier, and length field 264 is set to the value 0×6. The data portion of TLV-encoded option 226 begins immediately after length field 264. Specifically, in the packet shown in FIG. 2, the total length (in octets) of fields 266, 268, and 228 is equal to 0×6 as specified by length field 264. Further, as shown in FIG. 2, the last 20 bits of the data portion in TLV-encoded option 226 can be used for specifying VPN identifier 228.

Note that a 20-bit VPN identifier can be specified using a smaller data portion, e.g., only 0×3 octets instead of 0×6 octets. However, some embodiments use the following non-obvious insight: it may be desirable to align the 20-bit VPN identifier with the word boundary to simplify chip design and/or to improve performance. Thus, in some embodiments, 0×6 octets are used instead of 0×3 octets so that the 20-bit VPN identifier is aligned with a 32-bit word boundary. For example, as shown in FIG. 2, VPN identifier 228 is aligned with the 32-bit word boundary.

Inner MAC addresses 210 can include inner source MAC address 232 and inner destination MAC address 230 Inner MAC addresses 210 can be the MAC addresses that were present in the header of the packet that was received from the customer's network. For example, in FIG. 1, suppose a source node in VLAN 112 in customer C3's network at site S1 sends a packet to a destination node in VLAN 112 in customer C3's network at site S5. In this scenario, inner source MAC address 232 can correspond to the source node at site S1, and inner destination MAC address 230 can correspond to the destination node at site S5.

Inner VLAN tags 212 can include one or more VLAN tags that are used within the customer's network. For example, inner VLAN tags 212 can include an S-tag which includes Ethernet type field 234 and S-VLAN-identifier 236, a C-tag which includes Ethernet type field 238 and C-VLAN-identifier 240, and a congestion-notification-tag (CN-TAG) which includes Ethernet type field 242 and flow-identifier 244. Each VLAN tag can also include a three-bit Priority Code Point (PCP) field, e.g., PCP 270, and a one-bit Canonical Form Indicator (CFI) field, e.g., CFI 272. The values in Ethernet type fields 234, 238, and 242 can indicate that the tag includes a VLAN identifier for an S-tag, a VLAN identifier for the C-tag, and a flow-identifier, respectively. The S-tag and the C-tag can be used by the customer to create a stacked-VLAN architecture, e.g., as defined in the Provider Bridging standard. The S-tag may also be used by the service provider to implement network virtualization and/or partitioning. The congestion-notification-tag may be used by the customer to manage network congestion.

Note that a packet may or may not include all of the fields shown in FIG. 2. For example, in some embodiments, a packet may not include inner VLAN tags 212 and/or outer VLAN tag 204. Further, certain combinations of fields may not be allowed in some embodiments. For example, in some embodiments, a packet may include either an S-tag or a TRILL option field, but not both. Additionally, the values of some fields may be related to each other. For example, in some embodiments, S-VLAN-identifier 236 may be copied into the 12 least significant bits of VPNID 228.

VLAN tagging is specified in IEEE (Institute of Electrical and Electronics Engineers) standard IEEE 802.1 Q. The original specification of this standard describes how a single VLAN tag can be added to an Ethernet packet to create multiple broadcast domains within the same local area network (LAN). The term “Q-in-Q tagging” (also referred to as “QinQ tagging”) refers to an amendment of this standard which allows an S-VLAN tag (a service VLAN tag is sometimes referred to as a provider tag) to be stacked in a single Ethernet packet. Q-in-Q tagging enables a service provider to carry VLAN traffic from multiple customers on a shared Q-in-Q network infrastructure without restricting the VLAN address space available to each customer. Further details on Q-in-Q tagging can be found in the specification for standard IEEE 802.1ad.

In some embodiments, the system can add a TRILL header to a Provider Bridging (Q-in-Q) packet. In these embodiments, the packet received from the customer network may include an S-tag. The service provider's network may then add a TRILL header to the packet. In some embodiments, the system may ensure that the priority bits in the outermost VLAN tag are the same as the priority bits in the S-tag.

Supporting Multiple Multicast Trees in TRILL Networks

When a multicast packet is received on an input port, the multicast packet header is processed by the switch to determine the set of output ports on which the multicast packet is to be forwarded. Oftentimes, the forwarding mechanism (e.g., an application-specific integrated circuit designed for performing forwarding look-ups) is the bottleneck in the data path. Consequently, increasing the processing speed and decreasing the size and complexity of the forwarding mechanism is usually very important.

One approach for supporting multiple multicast trees is to have multiple forwarding entries (e.g., one entry per multicast tree) in the forwarding table for a given source address and multicast group address. Unfortunately, this approach can substantially increase the size of the forwarding table or severely limit the number of multicast groups that can be supported by the forwarding table.

Some embodiments determine an internal multicast group identifier based on one or more fields in the multicast packet's header. The multicast group identifier is then used to determine a set of egress ports through which the multicast packet is to be forwarded.

FIG. 3A illustrates how an internal multicast group identifier can be determined in accordance with some embodiments of the present invention.

Internal multicast group identifier 312 is composed of two sets of bits. The first set of bits 308 can be determined by looking up forwarding table 304 using the source address and multicast address 302 of a multicast packet. In some embodiments, forwarding table 304 is implemented using a content-addressable memory. The second set of bits 310 can be determined based on a multicast tree identifier 306 in the multicast packet. If the multicast packet does not have a multicast tree identifier, the switch can select the second set of bits 310 on its own, e.g., by using a hash-based technique.

Note that the forwarding table does not store an entry for each multicast tree supported by the switch. Instead, the forwarding table stores a single entry for a given source address and multicast address. The second set of bits is then used to select a particular tree from the multiple multicast trees that are associated with the given source address and multicast address. Since the forwarding table is not required to store an entry for each multicast tree, some embodiments of the present invention are capable of supporting a substantially greater number of multicast trees than other approaches that require the forwarding table to store an entry for each multicast tree.

FIGS. 3B and 3C illustrate different multicast trees for the same source and multicast address in accordance with some embodiments of the present invention.

RBridges 322-336 can be in a TRILL network. A multicast group can include RBridges 322, 326, 328, 330, and 336 (the RBridges in the multicast group are shown using a dotted circle). FIGS. 3B and 3C illustrate two multicast trees using dotted lines. Note that both multicast trees are rooted at RBridge 330.

FIG. 3D illustrates how an internal multicast group identifier can be determined in accordance with some embodiments of the present invention.

When a multicast packet is received at RBridge 326, it may use source and multicast address 352 of the multicast packet to look up forwarding table 354 to obtain a first set of bits 358. Source and multicast address 352 can be Ethernet or IP addresses.

Next, RBridge 326 may use the multicast tree identifier in the multicast packet to determine a second set of bits. Note that the multicast tree identifier in the multicast packet identifies the multicast tree over which the multicast packet is to be forwarded. In some embodiments, the multicast tree identifier is an RBridge nickname. For example, RBridge 330 may be associated with multiple nicknames which may correspond to multiple multicast trees rooted at RBridge 330.

The multicast tree illustrated in FIG. 3B can be associated with multicast tree identifier 356, and RBridge 326 may use multicast tree identifier 356 to determine second set of bits 360. The multicast tree illustrated in FIG. 3C can be associated with multicast tree identifier 366, and RBridge 326 may use multicast tree identifier 366 to determine second set of bits 370.

RBridge 326 can then combine the first set of bits and the second set of bits to obtain the internal multicast group identifier. For example, if the multicast packet contains multicast tree identifier 356, RBridge 326 can combine first set of bits 358 with second set of bits 360 to obtain internal multicast group identifier 362. On the other hand, if the multicast packet contains multicast tree identifier 366, RBridge 326 can combine first set of bits 358 with second set of bits 370 to obtain internal multicast group identifier 372.

FIG. 3E illustrates how an internal multicast group identifier can be used to determine a set of egress ports in accordance with some embodiments of the present invention.

Egress port lookup table 380 can be used to determine a set of egress ports based on the internal multicast group identifier. For example, performing a table lookup at RBridge 326 using internal multicast group identifier 362 may output set of egress ports {P-336}. Port P-336 represents a port on RBridge 326 that is coupled to RBridge 336. Similarly, performing a table lookup at RBridge 326 using internal multicast group identifier 372 may output set of egress ports {P-322, P-336}. Port P-322 represents a port on RBridge 326 that is coupled to RBridge 322. Once the set of egress ports has been determined, the system can forward copies of the multicast packet through the egress ports. Egress port lookup table 380 may be implemented as an array that is indexed using the internal multicast group identifier. Each entry in the array may store the set of egress ports.

Network Layer Multicasting in TRILL Networks

Some embodiments provide systems and techniques for performing network layer (e.g., IP layer) multicasting. Computer networking is typically accomplished using a layered software architecture, which is often referred to as a networking stack. Each layer is usually associated with a set of protocols which define the rules and conventions for processing packets in that layer. Each lower layer performs a service for the layer immediately above it to help with processing packets. At the source node, each layer typically adds a header as the payload moves from higher layers to lower layers through the source node's networking stack. The destination node typically performs the reverse process by processing and removing headers of each layer as the payload moves from the lowest layer to the highest layer at the destination node.

The multicast group membership at the network layer (e.g., the IP layer) can span multiple virtual networks, e.g., VPNs and/or VLANs. For example, in FIG. 1, a network layer multicast group may include end-hosts that are part of VLANs 116, 118, and 120 at sites S2, S3, and S4, respectively. In some embodiments, an RBridge can perform network layer multicasting, i.e., the RBridge can forward packets based on a network-layer multicast-address in addition to forwarding packets based on the TRILL header, VPN identifier, MAC addresses, and/or VLAN tags.

FIG. 4 illustrates how an RBridge can perform network layer multicasting in a TRILL network in accordance with some embodiments of the present invention.

RBridges 402-416 can be in a TRILL network which includes multiple virtual networks, e.g., VPNs and/or VLANs. Each virtual network may support multiple TRILL multicast trees. For example, TRILL multicast tree 418, which is illustrated using dotted lines, may belong to VLAN V1, and TRILL multicast tree 420, which is illustrated using dashed lines, may belong to VLAN V2.

A network layer (e.g., IP layer) multicast group can include end-hosts that are spread across multiple virtual networks, e.g., VPNs and/or VLANs. For example, a multicast group may include end-hosts that are in VPNs and/or VLANs coupled to RBridges 402, 408, 412, and 416 (these RBridges have been highlighted by drawing a circle around them). When a multicast packet for this multicast group is received at an RBridge, the RBridge may forward the multicast packet over a TRILL multicast tree on a particular VLAN. For example, when the multicast packet is received at RBridge 404, it may forward the packet over TRILL multicast tree 418 on VLAN V1.

When the multicast packet is received at RBridge 410, it may forward the packet based on the multicast packet's network-layer multicast-address. Specifically, RBridge 410 may determine that the multicast packet needs to be forwarded on both VLAN V1 and VLAN V2. RBridge 410 may forward the multicast packet on any one of the multiple multicast trees that are supported on VLAN V2. However, to ensure correct multicast forwarding, RBridge 410 may need to forward the multicast packet on VLAN V1 along the same multicast tree on which the multicast packet was received. Specifically, if RBridge 410 forwards the multicast packet on a multicast tree on VLAN V1 that is different from the one it was received on, it can create a forwarding loop and/or the multicast packet may not reach all of the end-hosts in the multicast group. Note that these problems do not arise if the network does not support multiple multicast trees.

Note that an RBridge may or may not be configured to perform network layer multicasting. For example, in the above example, RBridge 404 is not configured to perform network layer multicasting, whereas RBridge 410 is configured to perform network layer multicasting.

In some embodiments, the multicast packet can be a TRILL multicast packet, and can include a multicast tree identifier associated with the multicast tree over which the multicast packet is to be forwarded. The header of a TRILL multicast packet can include a multicast field (e.g., multicast field 250 in FIG. 2) which indicates that the TRILL packet is a multicast packet. The egress RBridge nickname (e.g., egress RBridge nickname 256 in FIG. 2) can correspond to the root of the multicast tree over which the multicast packet is to be forwarded.

FIG. 5 illustrates a switch in accordance with some embodiments of the present invention.

Switch 500 can include a plurality of mechanisms which may communicate with one another via a communication channel, e.g., a bus. Switch 500 may be realized using one or more integrated circuits.

In some embodiments, switch 500 is an RBridge (e.g., RBridge 102) which includes receiving mechanism 502, determining mechanism 504, forwarding mechanism 506, encapsulation mechanism 508, and decapsulation mechanism 510. In some embodiments, these mechanisms may be part of an application-specific integrated circuit.

Receiving mechanism 502 may be configured to receive a multicast packet (e.g., an Ethernet or TRILL multicast packet). Determining mechanism 504 may be configured to determine an internal multicast group identifier based on a source address, a multicast address, and a multicast tree identifier field associated with the multicast packet.

Forwarding mechanism 506 may be configured to forward the packet based on the internal multicast group identifier. Specifically, forwarding mechanism 506 may include a table (e.g., an array in memory) which is indexed using the internal multicast group identifier. Each record in the table (e.g., an array element) can include information that indicates how to forward the packet. For example, the record may include a set of egress port identifiers that identifies the egress ports. The record may also include instructions and/or information for modifying one or more fields in the header (e.g., the record may indicate that VLAN translation is to be performed and specify the new VLAN identifier). Additionally, the record may include header fields that need to be added to the packet (e.g., a TRILL header). Multiple copies of a multicast packet may be sent on an egress port of switch 500 if the multicast packet is to be sent to multiple VLANs that are coupled to the egress port.

Encapsulation mechanism 508 may be configured to encapsulate a copy of the multicast packet in a TRILL multicast packet. Specifically, encapsulation mechanism 508 may add a TRILL header to a copy of the multicast packet to obtain a TRILL multicast packet. In some embodiments, the TRILL header and the internal multicast group identifier may be determined concurrently. Once the TRILL header has been added, the TRILL multicast packet can be sent through the outgoing port.

Decapsulation mechanism 510 may be configured to decapsulate a TRILL multicast packet (e.g., by removing the TRILL header) to obtain the multicast packet that was encapsulated in the TRILL multicast packet. The multicast packet can then be forwarded to the customer's network (e.g., a customer VLAN).

In some embodiments, switch 500 (e.g., RBridge 410 in FIG. 4) may be configured to perform network layer multicasting. In these embodiments, receiving mechanism 502 may be configured to receive a multicast packet that includes a network-layer multicast-address. Specifically, receiving mechanism 502 may receive the multicast packet on a first multicast tree (e.g., TRILL multicast tree 418 in FIG. 4) associated with a first virtual network (e.g., VLAN V1). The multicast packet may include a first multicast tree identifier associated with the first multicast tree. The first multicast tree identifier can be the nickname of the RBridge at the root of the first multicast tree.

Determining mechanism 504 may be configured to determine, based on the network-layer multicast-address, one or more multicast trees associated with one or more virtual networks over which the packet is to be forwarded. For example, determining mechanism 504 may be configured to determine, based on the network-layer multicast-address, a second multicast tree (e.g., TRILL multicast tree 420 in FIG. 4) associated with a second virtual network (e.g., VLAN V2) over which the multicast packet is to be forwarded.

Forwarding mechanism 506 may be configured to forward the multicast packet on one or more multicast trees. For example, forwarding mechanism 506 may be configured to forward the multicast packet on the first multicast tree associated with the first virtual network, and forward a copy of the multicast packet on the second multicast tree associated with the second virtual network. The copy of the multicast packet may include a second multicast tree identifier associated with the second multicast tree. The second multicast tree identifier can be the nickname of the RBridge at the root of the second multicast tree.

In some embodiments, determining mechanism 504 may be configured to determine an internal multicast group identifier based on the network-layer multicast-address and a network-layer source-address of the multicast packet, and forwarding mechanism 506 may be configured to forward the multicast packet based on the internal multicast group identifier.

Note that FIG. 5 is for illustration purposes only, and is not intended to limit the present invention to the forms disclosed. Specifically, in some embodiments, switch 500 may not be an RBridge, and/or may include fewer or more mechanisms than those shown in FIG. 5.

FIG. 6A presents a flowchart that illustrates a process for forwarding packets based on an internal multicast group identifier in accordance with some embodiments of the present invention.

The process can be performed by a switch, e.g., RBridge 102. Upon receiving a multicast packet (e.g., an Ethernet or TRILL multicast packet), the switch can determine an internal multicast group identifier based on a source address (e.g., a source MAC or IP address), a multicast address (e.g., a multicast MAC or IP address), and a multicast tree identifier field associated with the multicast packet (operation 602).

In some embodiments, the system can determine the internal multicast group identifier by combining two sets of bits: one set of bits determined based on the source address and the multicast address, and a second set of bits determined based on the multicast tree identifier. Specifically, in some embodiments, combining the two sets of bits involves concatenating the two sets of bits to create the internal multicast group identifier.

For example, the source IP address and the multicast IP address can be used to look up the first set of bits in a context addressable memory. If the multicast packet includes a multicast tree identifier (e.g., RBridge nickname), then the multicast tree identifier can be used to determine the second set of bits. If the multicast packet does not include a multicast tree identifier, then the system can determine the second set of bits by hashing one or more fields in the multicast packet (or by any other means). Next, the first set of bits can be concatenated with the second set of bits to obtain the internal multicast group identifier.

Next, the switch can forward the multicast packet based on the internal multicast group identifier (operation 604). Specifically, the system can determine a set of egress ports based on the internal multicast group identifier. Next, the system can send at least one copy of the multicast packet through each port in the set of egress ports. The switch can additionally encapsulate the multicast packet in a TRILL multicast packet by adding a TRILL header, and send copies of the TRILL multicast packet through the set of egress ports which was determined based on the internal multicast group identifier.

FIG. 6B presents a flowchart that illustrates a process for performing network layer multicasting in a TRILL network in accordance with some embodiments of the present invention.

The process can be performed by a switch, e.g., RBridge 410 in FIG. 4. The switch can receive a multicast packet (e.g., an Ethernet or TRILL multicast packet) that includes a network-layer multicast-address, wherein the multicast packet is received on a first multicast tree associated with a first virtual network (operation 652). For example, RBridge 410 may receive a multicast packet from RBridge 404 over TRILL multicast tree 418 on VLAN V1.

Next, the switch can determine, based on the network-layer multicast-address, a second multicast tree associated with a second virtual network over which the multicast packet is to be forwarded (operation 654). For example, RBridge 410 may determine TRILL multicast tree 420 on VLAN V2 over which the multicast packet is to be forwarded. The second multicast tree can be determined randomly or it can be determined based on link utilization (e.g., by determining the least congested multicast tree).

The switch can then forward the multicast packet on the first multicast tree associated with the first virtual network, and forward a copy of the multicast packet on the second multicast tree associated with the second virtual network (operation 656). For example, RBridge 410 may forward the multicast packet to RBridges 408 and 414 over TRILL multicast tree 418, and forward a copy of the multicast packet to RBridges 406 and 416 over TRILL multicast tree 420.

FIG. 7 illustrates a system in accordance with some embodiments of the present invention.

System 700 can include processor 702 (e.g., a network processor) and memory 704. Processor 702 may be capable of accessing and executing instructions stored in memory 704. For example, processor 702 and memory 704 may be coupled by a bus. Memory 704 may store instructions that when executed by processor 702 cause system 700 to perform the processes illustrated in FIGS. 6A and/or 6B.

Specifically, memory 704 may store instructions for receiving a multicast packet, determining an internal multicast group identifier for a multicast packet based on a source address, a multicast address, and a multicast tree identifier field associated with the multicast packet, and forwarding the multicast packet based on the internal multicast group identifier. Memory 704 may optionally store instructions for encapsulation and/or decapsulation.

In some embodiments, the multicast packet include a network-layer multicast-address and it may be received on a first multicast tree associated with a first virtual network. Memory 704 may store instructions for determining, based on the network-layer multicast-address, a second multicast tree associated with a second virtual network over which the multicast packet is to be forwarded. In these embodiments, memory 704 may also store instructions for forwarding the multicast packet on the first multicast tree associated with the first virtual network, and forwarding a copy of the multicast packet on the second multicast tree associated with the second virtual network.

The data structures and code described in this disclosure can be partially or fully stored on a non-transitory computer-readable storage medium and/or a hardware module and/or a hardware apparatus. A computer-readable storage medium includes, but is not limited to, volatile memory, non-volatile memory, magnetic and optical storage devices such as disk drives, magnetic tape, CDs (compact discs), DVDs (digital versatile discs or digital video discs), or other non-transitory media, now known or later developed, that are capable of storing code and/or data. Hardware modules or apparatuses described in this disclosure include, but are not limited to, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), dedicated or shared processors, and/or other hardware modules or apparatuses now known or later developed. Specifically, the methods and/or processes may be described in a hardware description language (HDL) which may be compiled to synthesize register transfer logic (RTL) circuitry which can perform the methods and/or processes.

The methods and processes described in this disclosure can be partially or fully embodied as code and/or data stored in a computer-readable storage medium or device, so that when a computer system reads and/or executes the code and/or data, the computer system performs the associated methods and processes. The methods and processes can also be partially or fully embodied in hardware modules or apparatuses, so that when the hardware modules or apparatuses are activated, they perform the associated methods and processes. Further, the methods and processes can be embodied using a combination of code, data, and hardware modules or apparatuses.

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 the present invention to the forms disclosed. Accordingly, many modifications and variations will be apparent to practitioners having ordinary skill in the art. Additionally, the above disclosure is not intended to limit the present invention. The scope of the present invention is defined by the appended claims.

Claims

1. A switch, comprising: determining circuitry configured to determine, for a first multicast packet, a first internal multicast group identifier comprising a first and a second sets of bits, and for a second multicast packet, a second internal multicast group identifier comprising the first and a third sets of bits, wherein the first set of bits is determined based on a multicast-address and a source address of the first multicast packet, wherein the second set of bits is determined based on a first multicast tree identifier, which is a switch identifier of a root switch of a first multicast tree corresponding to a first virtual network, and wherein the third set of bits is determined based on a second multicast tree identifier, which is a switch identifier of a root switch of a second multicast tree corresponding to a second virtual network;forwarding circuitry configured to: determine, for the first multicast packet, one or more output ports associated with the first multicast tree associated with the first virtual network based on the first internal multicast group identifier; and determine, for the second multicast packet, one or more output ports associated with the second multicast tree based on the second internal multicast group identifier.

2. The switch of claim 1, wherein the first virtual network and the second virtual network are VLANs (Virtual Local Area Networks).

3. The switch of claim 1, wherein the first multicast packet includes a network-layer multicast address.

4. The switch of claim 1, wherein the first and second multicast packets are routed multicast packets, and wherein the first multicast tree and the second multicast tree are multicast trees in a routed network.

5. A system, comprising: a processor; anda memory storing instructions that when executed by the processor cause the system to perform a method, the method comprising:determining, for a first multicast packet, a first internal multicast group identifier comprising a first and a second sets of bits, and for a second multicast packet, a second internal multicast group identifier comprising the first and a third sets of bits, wherein the first set of bits is determined based on a multicast-address and a source address of the first multicast packet, wherein the second set of bits is determined based on a first multicast tree identifier, which is a switch identifier of a root switch of a first multicast tree corresponding to a first virtual network, and wherein the third set of bits is determined based on a second multicast tree identifier, which is a switch identifier of a root switch of a second multicast tree corresponding to a second virtual network;determining, for the first multicast packet, one or more output ports associated with the first multicast tree associated with the first virtual network based on the first internal multicast group identifier; anddetermining , for the second multicast packet, one or more output ports associated with the second multicast tree based on the second internal multicast group identifier.

6. The system of claim 5, wherein the first virtual network and the second virtual network are VLANs (Virtual Local Area Networks).

7. The system of claim 5, wherein the first multicast packet includes a network-layer multicast address.

8. The system of claim 5, wherein the first and second multicast packets are routed multicast packets, and wherein the first multicast tree and the second multicast tree are multicast trees in a routed network.

9. A method, comprising: determining, by a computer for a first multicast packet, a first internal multicast group identifier comprising a first and a second sets of bits, and for a second multicast packet, a second internal multicast group identifier comprising the first and a third sets of bits, wherein the first set of bits is determined based on a multicast-address and a source address of the first multicast packet, wherein the second set of bits is determined based on a first multicast tree identifier, which is a switch identifier of a root switch of a first multicast tree corresponding to a first virtual network, and wherein the third set of bits is determined based on a second multicast tree identifier, which is a switch identifier of a root switch of a second multicast tree corresponding to a second virtual network;determining, for the first multicast packet, one or more output ports associated with the first multicast tree associated with the first virtual network based on the first internal multicast group identifier; anddetermining, for the second multicast packet, one or more output ports associated with the second multicast tree based on the second internal multicast group identifier.

10. The method of claim 9, wherein the first virtual network and the second virtual network are VLANs (Virtual Local Area Networks).

11. The system of claim 5, wherein the first multicast packet includes a network-layer multicast address.

12. The system of claim 5, wherein the first and second multicast packets are routed multicast packets, and wherein the first multicast tree and the second multicast tree are multicast trees in a routed network.

13. The switch of claim 1, wherein the first multicast packet includes the first multicast tree identifier, and wherein the second multicast packet includes the second multicast tree identifier.

14. The switch of claim 13, wherein in response to the first multicast packet not including the first multicast tree identifier, generating the second set of bits based on a hash-based technique.

15. The system of claim 5, wherein the first multicast packet includes the first multicast tree identifier, and wherein the second multicast packet includes the second multicast tree identifier.

16. The system of claim 15, wherein in response to the first multicast packet not including the first multicast tree identifier, generating the second set of bits based on a hash-based technique.

17. The method of claim 9, wherein the first multicast packet includes the first multicast tree identifier, and wherein the second multicast packet includes the second multicast tree identifier.

18. The method of claim 17, wherein in response to the first multicast packet not including the first multicast tree identifier, generating the second set of bits based on a hash-based technique.