Abstract:
In one embodiment, a plurality of virtual private local area network services (VPLSs) are operated among a plurality of packet switching devices, with the plurality of VPLSs including a first VPLS and a different second VPLS. In response to a conversion declaration including a particular Service Instance VLAN ID (I-SID), the first VPLS corresponding to the particular I-SID is converted to a different type of virtual private network (VPN) service, while continuing to operate the different second VPLS which is not related to the particular I-SID. In one embodiment, the different type of VPN service is Provider Backbone Bridging Ethernet VPN (PBB-EVPN). In one embodiment, the conversion declaration is a Border Gateway Protocol (BGP) Network Layer Reachability Information (NLRI) of Route Type 3 Inclusive Multicast Ethernet Tag (IMET) route.
Abstract:
In one embodiment, a plurality of virtual private local area network services (VPLSs) are operated among a plurality of packet switching devices, with the plurality of VPLSs including a first VPLS and a different second VPLS. In response to a conversion declaration including a particular Service Instance VLAN ID (I-SID), the first VPLS corresponding to the particular I-SID is converted to a different type of virtual private network (VPN) service, while continuing to operate the different second VPLS which is not related to the particular I-SID. In one embodiment, the different type of VPN service is Provider Backbone Bridging Ethernet VPN (PBB-EVPN). In one embodiment, the conversion declaration is a Border Gateway Protocol (BGP) Network Layer Reachability Information (NLRI) of Route Type 3 Inclusive Multicast Ethernet Tag (IMET) route.
Abstract:
In one embodiment, when an ingress provider edge (PE) device of a computer network domain receives a frame at the ingress PE device destined to a destination media access control (MAC) address, it can determine whether the frame was received on a root or leaf Ethernet ingress segment, and also whether the destination MAC address is located via a root or leaf Ethernet segment. Accordingly, the ingress PE device may either drop or forward the frame based on the ingress Ethernet segment and destination MAC address Ethernet segment being either a root or a leaf, respectively.
Abstract:
In one embodiment, a source transmits one or more data packets to a destination over a primary pseudowire (PW). When a device on the primary PW detects a downstream failure of the primary PW, and in response to receiving one or more data packets from a source from the failed primary PW, the device adds a loopback packet identifier to the one or more received data packets, and returns the one or more data packets with the loopback packet identifier to the source upstream on the primary PW. Accordingly, in response to receiving the data packet returned with a loopback packet identifier from the primary PW (in response to the downstream failure), the source retransmits the one or more data packets to the destination over a backup PW.
Abstract:
Routing packet traffic using hierarchical forwarding groups is disclosed. In an embodiment, a packet is received at a packet router. Data related to the packet is received at a first forwarding group. Based on a first forwarding policy associated with the first forwarding group, a particular second forwarding group is selected from a set of forwarding groups that are members of the first forwarding group. Each forwarding group of the set of forwarding groups that are members of the first forwarding group is associated with a unique set of paths. Data related to the packet is provided to the particular second forwarding group. Based on a second forwarding policy associated with the particular second forwarding group, a particular path is selected from a set of paths that are associated with the particular second forwarding group. The packet is forwarded to a network node via the particular path.
Abstract:
Selecting remote path using forwarding path preferences is disclosed. In an embodiment, a message of a first network node identifying one or more forwarding path preferences in association with one or more destination addresses is received at a packet router. A particular path corresponding to a particular forwarding path preference from among the one or more forwarding path preferences received in the message is determined and in response a particular label is determined. A forwarding entry associating the particular label with the particular forwarding path preference and the particular path is stored. The particular label is forwarded to a second network node. A packet including the particular label is received at the packet router and the particular path associated with the particular label included with the packet is selected based on the forwarding entry associated with the label. The packet is forwarded to a network node via the selected path.
Abstract:
A method is provided in one example embodiment and includes receiving a request to create a path through a network, wherein the path originates on a first network device and terminates on the second network device; identifying a first controller associated with the first network device, wherein the first controller proxies control plane functions for the first network device; identifying a second controller associated with the second network device, wherein the second controller proxies control plane functions for the second network device; and computing the path using the first controller as a source and the second controller as a destination. The first controller installs the computed path on the first network device and the second controller installs the computed path on the second network device.
Abstract:
An example method for bi-directional flow stickiness in a network environment is provided and includes receiving a packet of a flow from a source address in a network, and destined to a destination address outside the network, looking up a flow table for an entry corresponding to the flow, and caching a forward flow entry and a reverse flow entry in the flow table if the look up results in a miss, the forward flow entry indicating a routing lookup, and the reverse flow entry indicating a previous hop from which the packet was received to maintain a bi-directional flow stickiness. Some embodiments also include receiving another packet from the destination address outside the network destined to the source address in the network, and forwarding it to the previous hop listed in the reverse flow entry.
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:
An example method for bi-directional flow stickiness in a network environment is provided and includes receiving a packet of a flow from a source address in a network, and destined to a destination address outside the network, looking up a flow table for an entry corresponding to the flow, and caching a forward flow entry and a reverse flow entry in the flow table if the look up results in a miss, the forward flow entry indicating a routing lookup, and the reverse flow entry indicating a previous hop from which the packet was received to maintain a bi-directional flow stickiness. Some embodiments also include receiving another packet from the destination address outside the network destined to the source address in the network, and forwarding it to the previous hop listed in the reverse flow entry.