Abstract: Some embodiments provide a method for providing redundancy and fast convergence for modules operating in a network. The method configures modules to use a same anycast inner IP address, anycast MAC address, and to associate with a same anycast VTEP IP address. In some embodiments, the modules are operating in an active-active mode and all nodes running modules advertise the anycast VTEP IP addresses with equal local preference. In some embodiments, modules are operating in active-standby mode and the node running the active module advertises the anycast VTEP IP address with higher local preference.

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: Some embodiments provide a method for determining a router identifier for a centralized routing component of a logical router. The method determines that a dynamic routing protocol is enabled for the centralized routing component. When a router identifier was previously stored for the centralized routing component, the method assigns the stored router identifier as the router identifier for the centralized routing component only when the stored router identifier matches one of a set of valid addresses for the centralized routing component. When the centralized routing component does not have a previously stored router identifier that matches one of the set of valid addresses, the method assigns one of the set of valid addresses as the router identifier for the centralized routing component according to a hierarchy among the set of valid addresses.

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, 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: In one embodiment, a network controller identifies a first sign of life for an edge device in a communication network (e.g., when the network controller receives an encapsulated workflow request for the edge device over a control plane of the communication network). The network controller further imports the encapsulated workflow request from the edge device over the control plane, determines configuration parameters for a tenant and a tenant network from the encapsulated workflow request, and transmits the configuration parameters to the edge device to provision the edge device for the tenant according to the configuration parameters.

Abstract: A system and method for advertising out-of-resources (OOR) conditions for entities, such as nodes, line cards and data links, in a manner that does not involve using a maximum cost to indicate the entity is “out-of-resources.” According to the technique, an OOR condition for an entity is advertised in one or more type-length-value (TLV) objects contained in an advertisement message. The advertisement message is flooded to nodes on a data network to inform them of the entity's OOR condition. Head-end nodes that process the advertisement message may use information contained in the TLV object to determine a path for a new label switched path (LSP) that does not include the entity associated with the OOR condition.

Abstract: In one embodiment, a network controller identifies a first sign of life for an edge device in a communication network (e.g., when the network controller receives an encapsulated workflow request for the edge device over a control plane of the communication network). The network controller further imports the encapsulated workflow request from the edge device over the control plane, determines configuration parameters for a tenant and a tenant network from the encapsulated workflow request, and transmits the configuration parameters to the edge device to provision the edge device for the tenant according to the configuration parameters.

Abstract: In one embodiment, an access component of a local network edge device receives traffic, and generates a frame for the traffic that includes a remote context label that identifies an access component of the remote network edge device to which the traffic is to be forwarded upon arrival at the remote network edge device, and a virtual circuit label corresponding to a particular virtual service of the traffic. The local network edge device forwards the frame towards the remote network edge device. In another embodiment, the frame may be received at a core component of the remote network edge device, an in response to the remote context label identifying an access component of the remote network edge device, forwarded to the access component, which determines the particular virtual service, and forwards the traffic from the frame out the access component towards an endpoint for the traffic.

Abstract: A method and system are disclosed for distributing (advertising) segment identifiers in network functions virtualization and/or software defined networking environments. An exemplary method includes receiving a route advertisement that includes a prefix with a forwarding address for a first network element and receiving a segment identifier (SID) advertisement that includes a prefix SID for the prefix. The route advertisement may be received from a second network element proxying control plane functions for the first network element. Reachability information for the first network element is updated based on the route advertisement and the SID advertisement.

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: In one embodiment, a network controller identifies a first sign of life for an edge device in a communication network (e.g., when the network controller receives an encapsulated workflow request for the edge device over a control plane of the communication network). The network controller further imports the encapsulated workflow request from the edge device over the control plane, determines configuration parameters for a tenant and a tenant network from the encapsulated workflow request, and transmits the configuration parameters to the edge device to provision the edge device for the tenant according to the configuration parameters.

Abstract: Systems, methods, and computer-readable media for an intelligent load balancer. In some embodiments, a system can analyze activity data for egress links associated with a network. The system can also receive a service request originating from a remote device. Next, the system can select a server in the network for receiving the service request. Based on the activity data, the system can also select an egress link from the egress links for communicating data associated with the service request from the network to a remote destination location, such as the remote device. The system can then send a signal to the selected server which can include the service request and an indication of the egress link to be used for the data associated with the service request. The system can also later change the selected egress link for the service request if the system subsequently identifies a better egress link.

Abstract: An example method is provided that includes determining whether an address resolution protocol reply from a local machine has been received at an edge node; updating a local cache based on the reply from the local machine; and sending the reply to a plurality of edge nodes through a data plane of a data center interconnect. In more specific implementations, the method can include determining whether an address resolution protocol request has been received from the local machine. The method could also include updating a local machine cache based on the request. In certain implementations, the method can include determining whether the request is targeting the local machine; and dropping the request if the request is targeting the local machine. The method could also include sending the request through the data center interconnect if the request is not targeting the local machine.

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.