Abstract:
Statistical and historical values of performance metrics are actively used to influence routing decisions for optimum topologies in a constrained network. Traffic service level is constantly monitored and compared with a service level agreement. If deviation exists between the monitored traffic service level and the terms of the service level agreement, stability metrics are used to maintain paths through the network that meet the terms of the traffic service level agreement or that improve the traffic flow through the network. Backup parent selection for a node in the network is performed based on previous performance of backup parents for the node.
Abstract:
In one embodiment, a node receives a request to initiate a shadow joining operation to shadow join a field area router (FAR) of a computer network, and preserves its data structures and soft states. The shadow joining operation may then be initiated to shadow join the FAR, wherein shadow joining comprises preforming join operations without leaving a currently joined-FAR, and the node measures one or more joining metrics of the shadow joining operation, and reports them accordingly. In another embodiment, a FAR (or other management device) determines a set of nodes to participate in a shadow joining operation, and informs the set of nodes of the shadow joining operation to shadow join the FAR. The device (e.g., FAR) participates in the shadow joining operation, and receives reports of one or more joining metrics of the shadow joining operation measured by the set of nodes.
Abstract:
In one embodiment, a device in a network monitors one or more metrics regarding network traffic associated with a particular application. The device detects an application-centric anomaly based on the monitored one or more metrics. The device causes an anomaly mitigation action to be performed in the network, in response to detecting the application-centric anomaly.
Abstract:
Statistical and historical values of performance metrics are actively used to influence routing decisions for optimum topologies in a constrained network. Traffic service level is constantly monitored and compared with a service level agreement. If deviation exists between the monitored traffic service level and the terms of the service level agreement, stability metrics are used to maintain paths through the network that meet the terms of the traffic service level agreement or that improve the traffic flow through the network. Backup parent selection for a node in the network is performed based on previous performance of backup parents for the node.
Abstract:
In one embodiment, a plurality of communication paths in a second direction in a communication network is determined, based on reversing communication paths established in a first direction in the communication network. Then, a path quality of the communication paths in the second direction is monitored. Based on the monitored path quality, it is then determined whether the communication paths in the second direction satisfy a communication requirement. Finally, a particular communication path of unacceptable quality in the second direction is detected when the particular communication path in the second direction fails to satisfy the communication requirement.
Abstract:
In one embodiment, a request to make a prediction regarding one or more service level agreements (SLAs) in a network is received. A network traffic parameter and an SLA requirement associated with the network traffic parameter according to the one or more SLAs are also determined. In addition, a performance metric associated with traffic in the network that corresponds to the determined network traffic parameter is estimated. It may then be predicted whether the SLA requirement would be satisfied based on the estimated performance metric.
Abstract:
In one embodiment, a device in a computer network determines one or more tunnels affected by a downstream fault in the computer network, and determines one or more common Ethernet segments of the device used by the affected tunnels. As such, the device generates, for each of the one or more common Ethernet segments, a respective fault message aggregating tunnel information of each of one or more particular affected tunnels on the corresponding common Ethernet segment, and sends each respective fault message with aggregated tunnel information over a selected tunnel of the one or more particular affected tunnels on the corresponding common Ethernet segment.
Abstract:
In one embodiment, network metrics are collected and analyzed in a network having nodes interconnected by communication links. Then, it is predicted whether a network element failure is relatively likely to occur based on the collected and analyzed network metrics. In response to predicting that a network element failure is relatively likely to occur, traffic in the network is rerouted in order to avoid the network element failure before it is likely to occur.
Abstract:
In one embodiment, a learning machine may be used to select observer nodes in a LLN such that the liveness of one or more nodes of interest may be monitored indirectly. In particular, a management device may receive network data on one or more network traffic parameters of a computer network. The management device may then determine, based on the network data, a candidate list of potential observer nodes to monitor activity or inactivity of one or more subject nodes. The management device may then dynamically select, using a machine learning model, a set of optimized observer nodes from the candidate list of potential observer nodes.
Abstract:
In one embodiment, a primary root node may detect one or more neighboring root nodes based on information received from a first-hop node and may select a backup root node among the neighboring root nodes. Once selected, the backup root node may send the primary root node a networking identification and a corresponding group mesh key which the primary root node may forward to the first-hop nodes to cause the first-hop nodes to migrate to the backup root node when connectivity to the primary root node fails. In addition, the first-hop root nodes may migrate back to the primary root node when connectivity to the primary root node is restored.