Abstract: In one example, a method includes receiving a plurality of network probes originating from a first provider edge router in a service provider network, calculating a plurality of network performance metrics, based on the plurality of network probes, and storing the network performance metrics associated with each network probe of the plurality of network probes in a path metric table, wherein an entry in the path metric table for the each network probe includes a path traveled by the each network probe from the first provider edge router to the processing system, the network performance metrics associated with the each network probe, a community value associated with the each network probe, and a traffic classification value associated with the each network probe.

Abstract: Aspects of the subject disclosure may include, for example, receiving network performance metrics for a plurality of paths through a network, each path extending from a customer equipment to an application server for data communication by the customer equipment with an application running on the application server, selecting a selected path among the plurality of paths, wherein the selecting is based on the network performance metrics, and communicating between the customer equipment and the application server according to the selected path. Border gateway protocol (BGP) community values (BGP CV) add BGP performance metrics community values (BPM CV) to convey network performance metrics to provider edge routers and customer premises equipment for network selection. Other embodiments are disclosed.

Abstract: Aspects of the subject disclosure may include, for example, receiving network performance metrics for a plurality of paths through a network, each path extending from a customer equipment to an application server for data communication by the customer equipment with an application running on the application server, selecting a selected path among the plurality of paths, wherein the selecting is based on the network performance metrics, and communicating between the customer equipment and the application server according to the selected path. Border gateway protocol (BGP) community values (BGP CV) add BGP performance metrics community values (BPM CV) to convey network performance metrics to provider edge routers and customer premises equipment for network selection. Other embodiments are disclosed.

Abstract: Aspects of the subject disclosure may include, for example, network device(s) capable of on-demand virtual routing and forwarding (VRF) table creation. A network device may receive a request from a customer device requesting on-demand VRF creation, and may instantiate and provision a VRF in response. The request made by the customer device may be made by announcing an attribute in a border gateway protocol (BGP) message. Other embodiments are disclosed.

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: 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 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 routing structure is defined for provider edge (PE) routers that will create the ability to recompute best paths based on application criteria. The routing structure may include the use of a network controller which is connected with the internet to receive requests from applications to trigger path re-computation. The controller will peer with PEs to send re-computation information used by the PE to construct an application-aware BGP table and forwarding instance. The PE also defines a new BGP and packet filter to replicate specific BGP paths into the application-aware table. The application-aware BGP and forwarding instance is unique to the requesting application. Thus, each request with a different source/destination combination obtains a discrete table providing separation. When a packet enters the PE from customer edge (CE) or core interface the packet traverses a packet filter that when matched against source/destination is redirected to the appropriate application-aware forwarding table.

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 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.