Abstract: A set of remote Virtual Extensible LAN (VxLAN) tunnel endpoints (VTEPs) and an ingress VTEP associated different Ethernet Segments (ESs) elect amongst themselves designated forwarder (DF) for forwarding broadcast, unknown-unicast, and multicast traffic (BUM) traffic by triggering an RFC 7432 election mechanism on each of the VTEPs. In embodiments, DF election involves exchanging configuration information, such as Type-4 routes for ESs via Border Gateway Protocol (BGP), without being confined to a particular ES that is local to all VTEPs, i.e., irrespective of local ES and internet identifiers. This allows performing targeted forwarding of BUM traffic to intended VTEPs which avoiding unnecessary ingress replication of BUM traffic in the ingress VTEP, thereby, saving hardware buffer resources and avoiding unnecessary flooding of frames to a set of non-forwarding egress VTEPs, ultimately, reducing the load on the egress VTEP and freeing up packet processing resources.

Abstract: An aggregated BIER networking system includes first and second aggregated BFER devices that are each directly connected to first and second receiver devices. The first aggregated BFER device receives a request from the first receiver device for multicast data packets generated by a source device and transmits the request to a BFIR device. The first aggregated BFER device also receives an identification from the second aggregated BFER device of the second receiver device that has requested multicast data packets generated by the source device. The first aggregated BFER device advertises a virtual BFER device that appears to be directly connected to each of the first and second aggregated BFER devices, and each of the first and second receiver devices. The first aggregated BFER device then receives a multicast data packet identifying the virtual BFER device, and forwards the multicast data packet to each of the first and second receiver devices.

Abstract: A set of remote Virtual Extensible LAN (VxLAN) tunnel endpoints (VTEPs) and an ingress VTEP associated different Ethernet Segments (ESs) elect amongst themselves designated forwarder (DF) for forwarding broadcast, unknown-unicast, and multicast traffic (BUM) traffic by triggering an RFC 7432 election mechanism on each of the VTEPs. In embodiments, DF election involves exchanging configuration information, such as Type-4 routes for ESs via Border Gateway Protocol (BGP), without being confined to a particular ES that is local to all VTEPs, i.e., irrespective of local ES and internet identifiers. This allows performing targeted forwarding of BUM traffic to intended VTEPs which avoiding unnecessary ingress replication of BUM traffic in the ingress VTEP, thereby, saving hardware buffer resources and avoiding unnecessary flooding of frames to a set of non-forwarding egress VTEPs, ultimately, reducing the load on the egress VTEP and freeing up packet processing resources.

Abstract: An aggregated BIER networking system includes first and second aggregated BFER devices that are each directly connected to first and second receiver devices. The first aggregated BFER device receives a request from the first receiver device for multicast data packets generated by a source device and transmits the request to a BFIR device. The first aggregated BFER device also receives an identification from the second aggregated BFER device of the second receiver device that has requested multicast data packets generated by the source device. The first aggregated BFER device advertises a virtual BFER device that appears to be directly connected to each of the first and second aggregated BFER devices, and each of the first and second receiver devices. The first aggregated BFER device then receives a multicast data packet identifying the virtual BFER device, and forwards the multicast data packet to each of the first and second receiver devices.

Abstract: A VXLAN multi-tenant inter-networking device packet forwarding system includes a first aggregated networking device coupled to a first host device and a second aggregated networking device that is coupled to second host devices. The first aggregated networking device receives a data packet from the first host device and, in response, identifies a virtual network associated with the first host device. Based on a first and second portion of a virtual network identifier that identifies the virtual network, the first aggregated networking device generates respective first and second packet forwarding identifiers. The first aggregated networking device then provides the first and second packet forwarding identifiers in the data packet, and forwards the data packet to the second aggregated networking device. The second aggregated networking device may then forward the data packet to one of the second host devices based on the first and second packet forwarding identifiers in the data packet.

Abstract: A VXLAN multi-tenant inter-networking device packet forwarding system includes a first aggregated networking device coupled to a first host device and a second aggregated networking device that is coupled to second host devices. The first aggregated networking device receives a data packet from the first host device and, in response, identifies a virtual network associated with the first host device. Based on a first and second portion of a virtual network identifier that identifies the virtual network, the first aggregated networking device generates respective first and second packet forwarding identifiers. The first aggregated networking device then provides the first and second packet forwarding identifiers in the data packet, and forwards the data packet to the second aggregated networking device. The second aggregated networking device may then forward the data packet to one of the second host devices based on the first and second packet forwarding identifiers in the data packet.

Abstract: Described herein are systems and methods that provide for auto-discovery of VXLAN tunnel endpoints (VTEPs) using a protocol-independent multicast (PIM) bootstrap router (BSR). In one or more embodiments, a node may be configured via PIM messaging in which nodes of a network provide their candidate-rendezvous point (RP) advertisements send their information of candidate-RP to multicast group information to an elected BSR. The elected BSR consolidates the candidate-RP to multicast group information and propagates this information to nodes through PIM messages to all PIM routers in the network. In one or more embodiments, a node uses this information in combination with its local configuration mapping of VNIDs-to-multicast-group information to generate a remote VTEP-IP-(RP)-to-VNID mapping, which can be used to auto configure the node's VXLAN with remote-VTEP and VNI profiles in static VXLAN deployments.

Abstract: Various embodiments of the invention allow for rapid communication in virtual link trunking (VLT) networks in which network traffic flows over not all-homed VLT peer devices, while honoring Equal Cost Multi Path (ECMP) decisions and normal route decisions about next hops. Traffic flow is made deterministic and free of sub-optimal paths that otherwise cause unnecessary traffic over inter-node links in the VLT domain. In embodiments, this is accomplished by using receiving VLAN interface-IP addresses from VLT devices in order to create and use a sub-LAG egress table from which sets of ports that lead to intended VLT devices are derived. In embodiments, instead of a VLAN interface-IP addresses a routing MAC address is used when forming the sub-LAG.

Abstract: Embodiments are directed to facilitate multiple tunnels to be reachable via inter-chassis ling from virtual link trunking (VLT) peers and also to avoid traffic tromboning with an optimal path to all next hops. During initialization, a default egress object is created through an ICL with the next hop defined as VLT peer2 by setting the MAC address to be the MAC address of the VLT peer2, and the VLAN to be any one of the L3 spanned VLANs. When any of the VXLAN tunnels are resolved through ICL LAG, the process uses the default egress object created on ICL. Using the default egress object created on ICL, any traffic from VLT peer1 intended to go through ICL is terminated on VLT peer2 and will get routed again to their respective next hops. This creates a single egress object to the VLT peer and allowing multiple VXLAN tunnels to be reachable through ICL with optimal path towards all next hops.

Abstract: Embodiments are directed to facilitate multiple tunnels to be reachable via inter-chassis ling from virtual link trunking (VLT) peers and also to avoid traffic tromboning with an optimal path to all next hops. During initialization, a default egress object is created through an ICL with the next hop defined as VLT peer2 by setting the MAC address to be the MAC address of the VLT peer2, and the VLAN to be any one of the L3 spanned VLANs. When any of the VXLAN tunnels are resolved through ICL LAG, the process uses the default egress object created on ICL. Using the default egress object created on ICL, any traffic from VLT peer1 intended to go through ICL is terminated on VLT peer2 and will get routed again to their respective next hops. This creates a single egress object to the VLT peer and allowing multiple VXLAN tunnels to be reachable through ICL with optimal path towards all next hops.

Abstract: A method of routing traffic for multi-cast routing through a node of a network that utilizes loop-free alternative paths is presented. The method includes receiving a join in the node from a second node in the network on a shortest path between the node and the second node; retrieving loop-free alternative paths to the second node; and adding an entry to a multi-cast routing table at the node that is based on a group that includes the shortest path to the second node and the loop-free alternative paths to the second node as cost equivalent paths.

Abstract: A switch (110R.3) uses a forwarding database (140F) to forward multicast packets. The switch participates in a multicast protocol (e.g. PIM) with other switches, and also uses a snooping database (e.g. for IGMP snooping) to learn about local group members, i.e. members for which the router serves as a local multicast router (e.g. the local members do not participate in the multicast protocol). When the switch learns of a local member of a multicast group, the switch updates the snooping database but may or may not install the snooping information in the forwarding database. Thus, the forwarding database is not necessarily provisioned for locally sourced data packets addressed to the group until receipt of a locally sourced data packet addressed to the group. If no such packets are received, the forwarding database is not provisioned for such packets, and therefore its size is reduced. Other features are also provided.

Abstract: A layer 3 routing loop prevention system includes a port extender coupled to a first and second control bridges by a Link Aggregation Group (LAG). The first and second control bridges are coupled by an interchassis link. When the first control bridge receives a packet and determines that its LAG link to the port extender is unavailable, it provides a control bridge failover identifier in the packet and performs layer 3 forwarding to send the packet to the second control bridge over the interchassis link. When the second control bridge receives the packet though the interchassis link and determines that its LAG link to the port extender is unavailable, that the packet includes the first control bridge failover identifier, and that layer 3 forwarding will result in the packet being sent back to the first control bridge device, the packet is dropped to prevent layer 3 routing loops.

Abstract: Each router in a group of routers (110R.2, 110R.3) includes an interface (P4) assigned a common virtual address for multicast (VAM). The common VAM is advertised in router advertisings for multicast traffic; other addresses are advertised for unicast. The member routers in the group share multicast forwarding databases. Increased throughput is therefore provided for multicast traffic without traffic replication. Any router in the group can service requests from end-point sources and receivers of multicast traffic, e.g. requests to join or leave a multicast group, or requests presented as multicast packets for forwarding to a multicast group.

Abstract: Aspects of the present invention include a port extender environment using the port extenders to dynamically select a data path. In embodiments of the present invention, each port extender can communicate data traffic to another port extender or to a host receiver. The communication path is selected in the port extender using a hashing system.

Abstract: An information handling system is provided. The information handling system includes a plurality of aggregation devices configured to distribute information in a virtual link trunk and a plurality of nodes coupled to the aggregation devices. When one of the plurality of aggregation devices received a reboot command, that aggregation device is configured to transmit a first message to the nodes indicating that the aggregation device is rebooting, receive a first acknowledgement message from the nodes indicating that they will not send any information to the rebooting aggregation device.

Abstract: A method of routing traffic for multi-cast routing through a node of a network that utilizes loop-free alternative paths is presented. The method includes receiving a join in the node from a second node in the network on a shortest path between the node and the second node; retrieving loop-free alternative paths to the second node; and adding an entry to a multi-cast routing table at the node that is based on a group that includes the shortest path to the second node and the loop-free alternative paths to the second node as cost equivalent paths.

Abstract: A switch (110R.3) uses a forwarding database (140F) to forward multicast packets. The switch participates in a multicast protocol (e.g. PIM) with other switches, and also uses a snooping database (e.g. for IGMP snooping) to learn about local group members, i.e. members for which the router serves as a local multicast router (e.g. the local members do not participate in the multicast protocol). When the switch learns of a local member of a multicast group, the switch updates the snooping database but may or may not install the snooping information in the forwarding database. Thus, the forwarding database is not necessarily provisioned for locally sourced data packets addressed to the group until receipt of a locally sourced data packet addressed to the group. If no such packets are received, the forwarding database is not provisioned for such packets, and therefore its size is reduced. Other features are also provided.

Abstract: A method of routing traffic for multi-cast routing through a node of a network that utilizes loop-free alternative paths is presented. The method includes receiving a join in the node from a second node in the network on a shortest path between the node and the second node; retrieving loop-free alternative paths to the second node; and adding an entry to a multi-cast routing table at the node that is based on a group that includes the shortest path to the second node and the loop-free alternative paths to the second node as cost equivalent paths.

Abstract: A layer 3 routing loop prevention system includes a port extender coupled to a first and second control bridges by a LAG. The first and second control bridges are coupled by an interchassis link. When the first control bridge receives a packet and determines that its LAG link to the port extender is unavailable, it provides a control bridge failover identifier in the packet and performs layer 3 forwarding to send the packet to the second control bridge over the interchassis link. When the second control bridge receives the packet though the interchassis link and determines that its LAG link to the port extender is unavailable, that the packet includes the first control bridge failover identifier, and that layer 3 forwarding will result in the packet being sent back to the first control bridge device, the packet is dropped to prevent layer 3 routing loops.