Abstract:
In an embodiment, a method of signaling status at a routing device is provided. In this method, the routing device establishes an inter-chassis control plane channel session with a remote routing device. Here, the routing device and the remote routing device are linked to a multi-homed routing device. The routing device then synchronizes with the remote routing device by way of the inter-chassis control plane channel session to identify a state of a link from the routing device to the multi-homed routing device. The state of the link is thereafter advertised by way of Border Gateway Protocol (BGP). Additionally, a method of discovering inter-chassis communication peers via BGP between the first and remote routing devices is provided.
Abstract:
Techniques for stitching multicast trees in a multiple data center environment. According to one embodiment, a technique for stitching multicast trees is provided, which includes determining, at an edge device of a data center, one or more Virtual Local Area Networks (VLANs) assigned to the edge device as a result of a designated forwarder election. An assigned forwarder message is sent by the edge device to one or more devices on the data center, the assigned forwarder message advertising the edge device as a designated forwarder for the VLANs assigned to the edge device. For each of the VLANs assigned to the edge device, the assigned forwarder message causes the edge device to be included in a multicast tree for the VLAN when the assigned forwarder message is received by specific ones of the devices in the data center that are associated with the VLAN.
Abstract:
In one embodiment, a particular autonomous system border router (ASBR), in a control-plane media access control (MAC) learning (CPML) network, discovers other ASBRs in the CPML network, the particular ASBR and other ASBRs interconnected with respective ASBRs of a data-plane MAC learning (DPML) network. The particular ASBR calculates one or more internal shortest path first (SPF) trees rooted respectively at each of the other ASBRs in the CPML network, and upon receiving a MAC advertisement route for a given MAC address with a given next-hop IP address, it may determine a distance from the particular and each other ASBR in the CPML network to the given IP address based on the internal SPF trees. In response to the distance from the particular ASBR being shorter than the distance from each other ASBR, the particular ASBR is designated as a designated forwarder (DF) for traffic sourced from the given MAC address.
Abstract:
In one embodiment, a particular PE device of a plurality of multi-homing PE devices between a core network and a local network determines a subset of traffic for which the particular PE device is responsible. The particular PE also establishes, with itself as root, a multicast tree within the local network for underlay multicast groups. Traffic received at the particular PE from the core network is admitted into the local network only if the core traffic corresponds to the subset of traffic for which the particular PE device is responsible (and mapped into one of the underlay multicast groups for which the particular PE device is the root). Also, multicast traffic received at the particular PE from the local network is forwarded into the core network only if the multicast traffic corresponds to the subset of traffic for which the particular PE device is responsible.
Abstract:
A system and associated methods provide solutions for reducing a volume of traffic through a multicast network attributed to repeated maintenance messages, which are required in order to maintain a multicast connection. The system configures provider edge devices to generate and send maintenance messages on behalf of members of a multicast group to establish and maintain the multicast connection and provides options for determining unknown locations of sources and/or subscribers, thereby reducing the overall volume of traffic transmitted over the multicast network.
Abstract:
Systems, methods, and computer-readable media are provided for securely advertising autoconfigured prefixes in a cloud environment. In some examples, a method can include, receiving, by a first router, an indication of an available network address prefix. In some aspects, the method can also include selecting, by the first router, a first network address prefix that is within the available network address prefix, wherein the first network address prefix provides at least one route to one or more network elements associated with the first router. In some cases, the method may further include sending, to a second router, a message including a stub registration option that indicates the first network address prefix.
Abstract:
A system and method for adaptive encryption for SD-WAN includes identifying an encrypted conversational flow and determining whether a duration of the encrypted conversational flow exceeds a threshold. The method also includes selecting a header-less tunnel for the encrypted conversational flow when the duration is more than the threshold. The method further includes transmitting the encrypted conversational flow to an egress router over the selected header-less tunnel.
Abstract:
In one embodiment, a method includes receiving, by a route reflector, a subscription request from a first provider edge node in a network and generating a subscription policy for the first provider edge node. The method also includes receiving a first Ethernet Virtual Private Network (EVPN) Type 2 Route from a second provider edge node, assigning a sequence number to the first EVPN Type 2 Route, and communicating the first EVPN Type 2 Route with the sequence number to the first provider edge node. The method further includes receiving a second EVPN Type 2 Route from a third provider edge node, generating an updated sequence number in response to receiving the second EVPN Type 2 Route from the third provider edge node, and communicating the second EVPN Type 2 Route with the updated sequence number to the first provider edge node and the second provider node.
Abstract:
A method includes creating a first routing table at each of a plurality of provider edge nodes in a first data center, the first routing table including a first sequence number tracking intra-data center movement of the host connected to one of the plurality of provider edge nodes; creating a second routing table at a corresponding gateway of each of a plurality of data centers, the plurality of data centers including the first data center, the second routing table including the first sequence number for the host and a second sequence number for tracking inter-data center movement of the host between the plurality of data centers host; and updating one of (1) the first sequence number when the host makes an intra-data center move, or (2) the second sequence number in the second routing table when the host makes an inter-data center move.
Abstract:
Systems and techniques are provided for synchronizing DHCP snoop information. In some examples, a method can include, performing, by a first PE device from a plurality of PE devices, DHCP snooping of a first plurality of DHCP messages between a DHCP client and a DHCP server, wherein the plurality of PE devices is part of an ethernet segment for multihoming the DHCP client. In some aspects, the method includes determining, based on snooping the first plurality of DHCP messages, an association between an IP address corresponding to the DHCP client and a MAC address corresponding to the DHCP client. In some examples, the method includes sending, by the first PE device to at least one other PE device from the plurality of PE devices, a first route advertisement that includes the association between the IP address corresponding to the DHCP client and the MAC address corresponding to the DHCP client.