Abstract: A network analytics controller is established in a network. The network includes a plurality of nodes. A plurality of network analytics agents is established; each agent at a node of the network. Network analytics configuration parameters, including a network analytics scope, are received at the networks analytics controller. A task is assigned to each agent at a node determined to be within the network analytics scope, the task comprising that portion of the network analytics specified in the network analytics configuration parameters relevant to the corresponding node. The assigned task is performed at each agent assigned a task. The networks analytics controller receives the results of each performed task, and aggregates the received results.

Abstract: A network analytics controller is established in a network. The network includes a plurality of nodes. A plurality of network analytics agents is established; each agent at a node of the network. Network analytics configuration parameters, including a network analytics scope, are received at the networks analytics controller. A task is assigned to each agent at a node determined to be within the network analytics scope, the task comprising that portion of the network analytics specified in the network analytics configuration parameters relevant to the corresponding node. The assigned task is performed at each agent assigned a task. The networks analytics controller receives the results of each performed task, and aggregates the received results.

Abstract: Installing on a node of a computer network, an agent of a network system. The installed agent receives a network task via the network. The network task involves a second node of the network. The receiving agent generates a probe implementing the task and targeted to the second node. Either the receiving agent or the generated probe generates a command for the second node. The command is related to the probe and can be in the form of a data link layer protocol data unit for network operations, administration, and maintenance (OAM). The agent or node that generates the command communicates the command to the second node. The second node executes the communicated command. The second node communicates an acknowledgment of the executed command to the first node.

Abstract: An example method for facilitating conflict avoidant traffic routing in a network environment is provided and includes detecting, at a network element, an intent conflict at a peer network element in a network, and changing a forwarding decision at the network element to steer traffic around the conflicted peer network element. The intent conflict refers to an incompatibility between an asserted intent associated with the traffic and an implemented intent associated with the traffic. In specific embodiments, the detecting includes mounting rules from the peer network element into the network element, and analyzing the mounted rules to determine intent conflict. In some embodiments, a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters.

Abstract: Installing on a node of a computer network, an agent of a network system. The installed agent receives a network task via the network. The network task involves a second node of the network. The receiving agent generates a probe implementing the task and targeted to the second node. Either the receiving agent or the generated probe generates a command for the second node. The command is related to the probe and can be in the form of a data link layer protocol data unit for network operations, administration, and maintenance (OAM). The agent or node that generates the command communicates the command to the second node. The second node executes the communicated command. The second node communicates an acknowledgment of the executed command to the first node.

Abstract: Installing on a node of a computer network, an agent of a network system. The installed agent receives a network task via the network. The network task involves a second node of the network. The receiving agent generates a probe implementing the task and targeted to the second node. Either the receiving agent or the generated probe generates a command for the second node. The command is related to the probe and can be in the form of a data link layer protocol data unit for network operations, administration, and maintenance (OAM). The agent or node that generates the command communicates the command to the second node. The second node executes the communicated command. The second node communicates an acknowledgment of the executed command to the first node.

Abstract: A network analytics controller in a computer network receives specification of a network analysis task. The controller creates maplets. Each maplet corresponds to an agent executing on a network node in the computer network. Each maplet specifies the network data collection configuration, collected data processing, and processed data reporting to be performed to support the network analysis task at the node executing the corresponding agent. The controller communicates the maplet corresponding to the agent over the computer network to each agent. Each agent receiving a maplet configures its corresponding network node for network data collection, collected data processing, and processed data reporting in accordance with the received maplet. Each agent receiving a maplet collects and processes network data, and reports the processed data to the controller, in accordance with the configuration. The controller aggregates, as the result of the network analysis task, the data reported from each agent.

Abstract: An example method for facilitating network control and management using semantic reasoners in a network environment is provided and includes generating a fully populated semantics model of the network from network data according to a base network ontology of the network, mapping the fully populated semantics model to a network knowledge base, feeding contents of the network knowledge base to a semantic reasoner, and controlling and managing the network using the semantic reasoner. In specific embodiments, generating the model includes receiving the network data from the network, parsing the network data, loading the parsed network data into in-memory data structures, accessing a manifest specifying binding between a network data definition format and ontology components of the base network ontology, identifying ontology components associated with the network data based on the manifest, and populating the identified ontology components with individuals and properties from the corresponding data structures.

Abstract: Installing on a node of a computer network, an agent of a network system. The installed agent receives a network task via the network. The network task involves a second node of the network. The receiving agent generates a probe implementing the task and targeted to the second node. Either the receiving agent or the generated probe generates a command for the second node. The command is related to the probe and can be in the form of a data link layer protocol data unit for network operations, administration, and maintenance (OAM). The agent or node that generates the command communicates the command to the second node. The second node executes the communicated command. The second node communicates an acknowledgment of the executed command to the first node.

Abstract: An example method for facilitating conflict avoidant traffic routing in a network environment is provided and includes detecting, at a network element, an intent conflict at a peer network element in a network, and changing a forwarding decision at the network element to steer traffic around the conflicted peer network element. The intent conflict refers to an incompatibility between an asserted intent associated with the traffic and an implemented intent associated with the traffic. In specific embodiments, the detecting includes mounting rules from the peer network element into the network element, and analyzing the mounted rules to determine intent conflict. In some embodiments, a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters.

Abstract: An example method for facilitating conflict avoidant traffic routing in a network environment is provided and includes detecting, at a network element, an intent conflict at a peer network element in a network, and changing a forwarding decision at the network element to steer traffic around the conflicted peer network element. The intent conflict refers to an incompatibility between an asserted intent associated with the traffic and an implemented intent associated with the traffic. In specific embodiments, the detecting includes mounting rules from the peer network element into the network element, and analyzing the mounted rules to determine intent conflict. In some embodiments, a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters.

Abstract: An example method for automating monitoring using configuration event triggers in a network environment is provided and includes receiving a change request for a configuration change, creating a change impact monitor according to a profile associated with the configuration change, taking a first snapshot of performance indicators when the configuration change is applied, taking a second snapshot of the performance indicators a predetermined duration after applying the configuration change, and generating a change impact notification describing the first snapshot and the second snapshot. The profile can specify the performance indicators for the configuration change. A change agent that creates the change impact monitor may also be invoked. In some embodiments, the method can further include receiving a soak command, and taking a third snapshot of the performance indicators before applying the configuration change.

Abstract: A network analytics controller in a computer network receives specification of a network analysis task. The controller creates maplets. Each maplet corresponds to an agent executing on a network node in the computer network. Each maplet specifies the network data collection configuration, collected data processing, and processed data reporting to be performed to support the network analysis task at the node executing the corresponding agent. The controller communicates the maplet corresponding to the agent over the computer network to each agent. Each agent receiving a maplet configures its corresponding network node for network data collection, collected data processing, and processed data reporting in accordance with the received maplet. Each agent receiving a maplet collects and processes network data, and reports the processed data to the controller, in accordance with the configuration. The controller aggregates, as the result of the network analysis task, the data reported from each agent.

Abstract: An example method for facilitating multi-stage convergence and intent revocation in a network environment is provided and includes sending an intent support request for an intent to a plurality of targets in a network, receiving intent pre-commits from a portion of the plurality of targets and intent pre-aborts from a remaining portion of the plurality of targets, each intent pre-commit indicative of ability to support the intent, and each intent pre-abort indicative of inability to support the intent, determining whether the intent is to be added to the domain in view of potentially impacted intents, and instructing the plurality of targets to commit to the intent if the intent is to be added to the domain.

Abstract: An example method for facilitating conflict avoidant traffic routing in a network environment is provided and includes detecting, at a network element, an intent conflict at a peer network element in a network, and changing a forwarding decision at the network element to steer traffic around the conflicted peer network element. The intent conflict refers to an incompatibility between an asserted intent associated with the traffic and an implemented intent associated with the traffic. In specific embodiments, the detecting includes mounting rules from the peer network element into the network element, and analyzing the mounted rules to determine intent conflict. In some embodiments, a central controller in the network deploys one or more intentlets on a plurality of network elements in the network according to corresponding intent deployment parameters.

Abstract: A network analytics controller is established in a network. The network includes a plurality of nodes. A plurality of network analytics agents is established; each agent at a node of the network. Network analytics configuration parameters, including a network analytics scope, are received at the networks analytics controller. A task is assigned to each agent at a node determined to be within the network analytics scope, the task comprising that portion of the network analytics specified in the network analytics configuration parameters relevant to the corresponding node. The assigned task is performed at each agent assigned a task. The networks analytics controller receives the results of each performed task, and aggregates the received results.

Abstract: An example method for facilitating network control and management using semantic reasoners in a network environment is provided and includes generating a fully populated semantics model of the network from network data according to a base network ontology of the network, mapping the fully populated semantics model to a network knowledge base, feeding contents of the network knowledge base to a semantic reasoner, and controlling and managing the network using the semantic reasoner. In specific embodiments, generating the model includes receiving the network data from the network, parsing the network data, loading the parsed network data into in-memory data structures, accessing a manifest specifying binding between a network data definition format and ontology components of the base network ontology, identifying ontology components associated with the network data based on the manifest, and populating the identified ontology components with individuals and properties from the corresponding data structures.

Abstract: An example method for automating monitoring using configuration event triggers in a network environment is provided and includes receiving a change request for a configuration change, creating a change impact monitor according to a profile associated with the configuration change, taking a first snapshot of performance indicators when the configuration change is applied, taking a second snapshot of the performance indicators a predetermined duration after applying the configuration change, and generating a change impact notification describing the first snapshot and the second snapshot. The profile can specify the performance indicators for the configuration change. A change agent that creates the change impact monitor may also be invoked. In some embodiments, the method can further include receiving a soak command, and taking a third snapshot of the performance indicators before applying the configuration change.

Abstract: The network device is described that comprises an allocator to adaptively allocate respective event message rate limits to client network devices that is in communication with an event-based system logging server to send event messages to the logging server for processing. The adaptively allocated event message rate limits are communicated to the client network devices so that limiting of a global rate of event messages received by the logging server comprises limiting the respective rates at which the client network devices can transmit event messages to the logging server. Measurement of respective event message rates comprises a count of event messages actually received by the logging server from the corresponding client device within a defined time window.

Abstract: The network device is described that comprises an allocator to adaptively allocate respective event message rate limits to client network devices that is in communication with an event-based system logging server to send event messages to the logging server for processing. The adaptively allocated event message rate limits are communicated to the client network devices so that limiting of a global rate of event messages received by the logging server comprises limiting the respective rates at which the client network devices can transmit event messages to the logging server. Measurement of respective event message rates comprises a count of event messages actually received by the logging server from the corresponding client device within a defined time window.