Abstract: A system and method for software defined network (SDN) management. Route information is received from a customer edge (CE) device. The route information is parsed to identify at least one virtual routing and forwarding (VRF) instance for which the route information is intended. The route information is imported into the VRF instance.

Abstract: A system and method for software defined network (SDN) management. Route information is received from a customer edge (CE) device. The route information is parsed to identify at least one virtual routing and forwarding (VRF) instance for which the route information is intended. The route information is imported into the VRF instance.

Abstract: A recovery route reflector with a monitoring module and a BGP state establishment module is peered with a plurality of primary route reflectors. Each of the plurality of primary route reflectors is peered with a set of provider edge devices. The BGP state between the recovery route reflector and the plurality of primary route reflectors is periodically monitored. When a primary route reflector fails the BGP state between the recovery route reflector and the failed primary route reflectors is idle, and the recovery route reflector establishes a peer session with the provider edge devices that had been peered with the failed route reflector.

Abstract: Managing prefix lists at edge devices can include detecting, at an edge device, a traffic flow that can include a packet that specifies a destination address. The edge device can measure a bandwidth associated with the traffic flow, identify a flow bandwidth threshold defined for the edge device, and determine if the bandwidth associated with the traffic flow satisfies the flow bandwidth threshold. If a determination is made that the bandwidth associated with the traffic flow satisfies the flow bandwidth threshold, the edge device can include the destination address in a prefix list stored at the edge device. If a determination is made that the bandwidth associated with the traffic flow does not satisfy the flow bandwidth threshold, the edge device can omit the destination address from the prefix list stored at the edge device.

Abstract: A recovery route reflector with a monitoring module and a BGP state establishment module is peered with a plurality of primary route reflectors. Each of the plurality of primary route reflectors is peered with a set of provider edge devices. The BGP state between the recovery route reflector and the plurality of primary route reflectors is periodically monitored. When a primary route reflector fails the BGP state between the recovery route reflector and the failed primary route reflectors is idle, and the recovery route reflector establishes a peer session with the provider edge devices that had been peered with the failed route reflector.

Abstract: A method includes sending a request for services from a Virtual Machine (VM) in an external cloud network to a provider multi-protocol label switching (MPLS) network, establishing a multi-protocol border gateway protocol (MP-BGP) session between the provider MPLS network and the external cloud network, exchanging control plane updates between the provider MPLS network and the cloud network and processing paths between the provider MPLS network and the remote VM.

Abstract: A system for indirect border gateway routing may include a provider edge router, virtual routing and forwarding instance, a point identification list, and a virtual routing and forwarding import instance. The virtual routing and forwarding import instance may be adapted to receive a route from the provider edge router, in which the route may include a pointer identification directing the virtual routing and forwarding import instance to scan the pointer identification list for the route target associated with multiple virtual routing and forwarding instances. The virtual routing and forwarding import instance may be adapted to import the route to at least one virtual routing and forwarding instance having a route target on the pointer identification list.

Abstract: A recovery route reflector with a monitoring module and a BGP state establishment module is peered with a plurality of primary route reflectors. Each of the plurality of primary route reflectors is peered with a set of provider edge devices. The BGP state between the recovery route reflector and the plurality of primary route reflectors is periodically monitored. When a primary route reflector fails the BGP state between the recovery route reflector and the failed primary route reflectors is idle, and the recovery route reflector establishes a peer session with the provider edge devices that had been peered with the failed route reflector.

Abstract: A recovery route reflector with a monitoring module and a BGP state establishment module is peered with a plurality of primary route reflectors. Each of the plurality of primary route reflectors is peered with a set of provider edge devices. The BGP state between the recovery route reflector and the plurality of primary route reflectors is periodically monitored. When a primary route reflector fails the BGP state between the recovery route reflector and the failed primary route reflectors is idle, and the recovery route reflector establishes a peer session with the provider edge devices that had been peered with the failed route reflector.

Abstract: A system comprising a BAFX adapted to provide a route exchange between dissimilar address family interfaces; wherein the BAFX is a control plane BGP speaker that connects directly to each address family interface specific route reflector and wherein each address family interface specific route reflector advertises its BGP content to the BAFX for translation; and the BAFX translates a received address family interface format into a destination address family interface format and announces a reformatted route address to a destination route reflector.

Abstract: A system and method for software defined network (SDN) management. Route information is received from a customer edge (CE) device. The route information is parsed to identify at least one virtual routing and forwarding (VRF) instance for which the route information is intended. The route information is imported into the VRF instance.

Abstract: A system for indirect border gateway routing comprising a provider edge router; at least one virtual routing and forwarding instance (“VRF”) in communication with the provider edge router, each VRF including a route target; a pointer identification list in communication with the provider edge router, the pointer identification list containing at least one route target associated with a VRF; and a virtual routing and forwarding import instance adapted to receive a route from the provider edge router, the route including a pointer identification directing the virtual routing and forwarding import instance to scan the pointer identification list for the route target associated with the plural VRF, and wherein the virtual routing and forwarding import instance is further adapted to import the route to the at least one virtual routing and forwarding instance having a route target on the pointer identification list.

Abstract: A system for indirect border gateway routing comprising a provider edge router; at least one virtual routing and forwarding instance (“VRF”) in communication with the provider edge router, each VRF including a route target; a pointer identification list in communication with the provider edge router, the pointer identification list containing at least one route target associated with a VRF; and a virtual routing and forwarding import instance adapted to receive a route from the provider edge router, the route including a pointer identification directing the virtual routing and forwarding import instance to scan the pointer identification list for the route target associated with the plural VRF, and wherein the virtual routing and forwarding import instance is further adapted to import the route to the at least one virtual routing and forwarding instance having a route target on the pointer identification list.

Abstract: Methods and apparatus to route traffic in a virtual private network are disclosed herein. Example methods include replacing, by executing an instruction with a processor at a first provider router, a first next hop address included in first route information with a second next hop address. The first next hop address identifies a first edge router of a plurality of edge routers in a first region and the second next hop address identifies the first provider router. The provider router is not at an edge of a provider network included in the virtual private network and the first route information identifies a first route to a customer address in a customer network coupled to the first edge router. The methods also include advertising the first route information having the second next hop address to the plurality of edge routers if data traffic is to access a service.

Abstract: A system comprising a BAFX adapted to provide a route exchange between dissimilar address family interfaces; wherein the BAFX is a control plane BGP speaker that connects directly to each address family interface specific route reflector and wherein each address family interface specific route reflector advertises its BGP content to the BAFX for translation; and the BAFX translates a received address family interface format into a destination address family interface format and announces a reformatted route address to a destination route reflector.

Abstract: A system for indirect border gateway routing comprising a provider edge router; at least one virtual routing and forwarding instance in communication with the provider edge router, each virtual routing and forwarding instance including a route target; a pointer identification list in communication with the provider edge router, the pointer identification list containing at least one route target associated with a virtual routing and forwarding instance; and a virtual routing and forwarding import instance adapted to receive a route from the provider edge router, the route including a pointer identification directing the virtual routing and forwarding import instance to scan the pointer identification list for the route target associated with the plural virtual routing and forwarding instance, and wherein the virtual routing and forwarding import instance is further adapted to import the route to the at least one virtual routing and forwarding instance having a route target on the pointer identification list.

Abstract: Methods and apparatus to route traffic in a virtual private network are disclosed herein. Example methods include replacing, by executing an instruction with a processor at a first provider router, a first next hop address included in first route information with a second next hop address. The first next hop address identifies a first edge router of a plurality of edge routers in a first region and the second next hop address identifies the first provider router. The provider router is not at an edge of a provider network included in the virtual private network and the first route information identifies a first route to a customer address in a customer network coupled to the first edge router. The methods also include advertising the first route information having the second next hop address to the plurality of edge routers if data traffic is to access a service.

Abstract: Methods and apparatus disclosed herein include receiving, at a first provider router that is not an edge router, first route information from a provider edge router. The first route information identifies a customer address in a customer network coupled to the provider edge router. The methods also include replacing, at the first provider router, a first next hop address included in the first route information with a second next hop address. The first next hop address identifies the provider edge router and the second next hop address identifies the first provider router. The methods also include advertising the first route information to a second provider router located in a different region than the first provider router.

Abstract: Methods and apparatus to route traffic in a virtual private network are disclosed herein. An example method to route such traffic includes receiving, at a first provider router that is not an edge router, first route information from a provider edge router. The first route information identifies a customer address in a customer network coupled to the provider edge router. The method also includes replacing, at the first provider router, a first next hop address included in the first route information with a second next hop address. The first next hop address identifies the provider edge router and the second next hop address identifies the first provider router. In some examples, the method also includes advertising the first route information to a second provider router located in a different region than the first provider router.

Abstract: A disclosed method of managing a provider edge (PE) router includes defining a neighbor specific prefix limit and a neighbor specific restart parameter applicable to a neighbor of the PE router. The neighbor may be a customer edge (CE) router connected to the PE router. A neighbor specific count of prefixes advertised by the CE router is monitored against the prefix limit. When a neighbor specific prefix limit violation occurs, the PE-to-CE connection is suspended for a duration determined at least in part by the restart parameter and then automatically resumed. The PE router may define an address family prefix limit and an address family restart parameter applicable to the CE router's address family. Violations of the address family prefix limit may result in temporary suspension of all connections between the PE router and the members of the address family.