Abstract: In an embodiment, a method comprises detecting, by a network control entity associated with a software-defined network, a network event in the software-defined network. The network control entity determines, based on the network event, an application for installation at the network control entity or in the software-defined network. The application is automatically installed at the network control entity or in the software-defined network.

Abstract: In an embodiment, a method comprises detecting, by a network control entity associated with a software-defined network, a network event in the software-defined network. The network control entity determines, based on the network event, an application for installation at the network control entity or in the software-defined network. The application is automatically installed at the network control entity or in the software-defined network.

Abstract: In one embodiment, a device in a network receives data from one or more other devices in the network via one or more protocol adaptors. The device transforms the received data into a common data model. The device executes a containerized application. The device exposes the transformed data to the application.

Abstract: In one embodiment, a device in a network receives data from one or more other devices in the network via one or more protocol adaptors. The device transforms the received data into a common data model. The device executes a containerized application. The device exposes the transformed data to the application.

Abstract: Embodiments described herein permit a mobile device to transfer a configuration package to a network device which automatically configures (i.e., without user intervention) the network device using a bootstrapping process. Specifically, the mobile device may use near field communication (NFC) to transfer the configuration package to the network device. The configuration package may include the information required to bootstrap the network device such as an operating system (OS) image and configuration information (e.g., user name, passwords, etc.). Once NFC is established, the mobile device transfers the configuration package to the network device which then begins the bootstrap process using the data contained in the package.

Abstract: In one embodiment, a method includes receiving label data that indicates all interface labels that belong to each path ID of multiple path IDs associated with corresponding multiple paths between provider edge nodes in a Multi-Protocol Label Switching (MPLS) network. Each interface label is associated with a network interface on a node in the MPLS network. Based on the label data, an untested list that holds data that indicates all unique interface labels is generated. A tested interface selected from the untested list is scheduled for testing. After scheduling, the interface label of the tested interface is removed from the untested list. It is determined whether the untested list still includes data for at least one interface label. If not, then a test of the MPLS network is completed without testing every path end to end, thus conserving network resources.

Abstract: In one embodiment, a method includes receiving label data that indicates all interface labels that belong to each path ID of multiple path IDs associated with corresponding multiple paths between provider edge nodes in a Multi-Protocol Label Switching (MPLS) network. Each interface label is associated with a network interface on a node in the MPLS network. Based on the label data, an untested list that holds data that indicates all unique interface labels is generated. A tested interface selected from the untested list is scheduled for testing. After scheduling, the interface label of the tested interface is removed from the untested list. It is determined whether the untested list still includes data for at least one interface label. If not, then a test of the MPLS network is completed without testing every path end to end, thus conserving network resources.

Abstract: In one embodiment, a method includes receiving label data that indicates all interface labels that belong to each path ID of multiple path IDs associated with corresponding multiple paths between provider edge nodes in a Multi-Protocol Label Switching (MPLS) network. Each interface label is associated with a network interface on a node in the MPLS network. Based on the label data, an untested list that holds data that indicates all unique interface labels is generated. A tested interface selected from the untested list is scheduled for testing. After scheduling, the interface label of the tested interface is removed from the untested list. It is determined whether the untested list still includes data for at least one interface label. If not, then a test of the MPLS network is completed without testing every path end to end, thus conserving network resources.

Abstract: In one embodiment, a method includes receiving label data that indicates all interface labels that belong to each path ID of multiple path IDs associated with corresponding multiple paths between provider edge nodes in a Multi-Protocol Label Switching (MPLS) network. Each interface label is associated with a network interface on a node in the MPLS network. Based on the label data, an untested list that holds data that indicates all unique interface labels is generated. A tested interface selected from the untested list is scheduled for testing. After scheduling, the interface label of the tested interface is removed from the untested list. It is determined whether the untested list still includes data for at least one interface label. If not, then a test of the MPLS network is completed without testing every path end to end, thus conserving network resources.