Patent classifications
H04L43/0817
Communicating with a Data Center Management and Monitoring Console via a Broker
A system, method, and computer-readable medium are disclosed for performing a data center monitoring and management operation. The data center monitoring and management operation includes: identifying data center asset data to monitor; monitoring data center assets within a data center; selecting an asset data broker, the asset data broker performing an asset data aggregation operation, the asset data aggregation operation collecting and aggregating the data center asset data; and, providing aggregated data center asset data to a data center monitoring and management console.
UPGRADE OF NETWORK OBJECTS USING SECURITY ISLANDS
Systems and techniques to upgrade network objects using security islands are described herein. Security islands of node groupings are created based on trust relationships between nodes in an edge network. An upgrade request may be received to upgrade a target edge node in the edge network. Building blocks may be identified for a package installed on the target edge node to be upgraded. A state backup may be stored for the building blocks. An upgrade command and an upgrade payload may be transmitted to the target edge node. The target edge node may be queried to obtain a status of the target edge node. An upgrade action may be determined based on the status and the upgrade action may be executed.
Systems and methods for discovering and monitoring devices using search patterns for object identifiers and values
The present disclosure is directed to systems and methods of managing remote devices. The system can include a server with memory, a detection module, and a collection module. The memory can store a management information base (MIB) having a hierarchical tree of object identifiers and corresponding object values. The detection module can query devices and receive a first object identifier and its first object value, which can vary from those in the MIB; and use patterns to match the first object identifier and object value; and generate an identification of the device from the matches. The collection module can use the identification to select a collection template, which can indicate a subtree of the MIB and a collection pattern; traverse the subtree and identify a second object identifier that matches the collection pattern, and its second object value; and associate the second object value with the first object value.
Systems and methods for discovering and monitoring devices using search patterns for object identifiers and values
The present disclosure is directed to systems and methods of managing remote devices. The system can include a server with memory, a detection module, and a collection module. The memory can store a management information base (MIB) having a hierarchical tree of object identifiers and corresponding object values. The detection module can query devices and receive a first object identifier and its first object value, which can vary from those in the MIB; and use patterns to match the first object identifier and object value; and generate an identification of the device from the matches. The collection module can use the identification to select a collection template, which can indicate a subtree of the MIB and a collection pattern; traverse the subtree and identify a second object identifier that matches the collection pattern, and its second object value; and associate the second object value with the first object value.
ROUND-TRIP TIME AS A LATENCY PERFORMANCE INDICATOR
Methods, systems, and devices for wireless communications are described. A wireless communications entity, such as a user equipment (UE), a base station, a network core, or an application server, may identify a round-trip time (RTT) latency requirement that may pertain to a round-trip latency in wireless communications between the UE and the base station. The wireless communications entity may identify a one one-way directional delay budget that satisfies the RTT latency requirement for an application of an application server. The application server may be in communication with the UE via the base station. The wireless communications entity may modify a value of the one-way directional delay budget and transmit a message that is associated with the modified value of the one one-way directional delay budget.
ROUND-TRIP TIME AS A LATENCY PERFORMANCE INDICATOR
Methods, systems, and devices for wireless communications are described. A wireless communications entity, such as a user equipment (UE), a base station, a network core, or an application server, may identify a round-trip time (RTT) latency requirement that may pertain to a round-trip latency in wireless communications between the UE and the base station. The wireless communications entity may identify a one one-way directional delay budget that satisfies the RTT latency requirement for an application of an application server. The application server may be in communication with the UE via the base station. The wireless communications entity may modify a value of the one-way directional delay budget and transmit a message that is associated with the modified value of the one one-way directional delay budget.
APPLICATION SERVICE LEVEL EXPECTATION HEALTH AND PERFORMANCE
Techniques are described for monitoring application performance in a computer network. For example, a network management system (NMS) includes a memory storing path data received from a plurality of network devices, the path data reported by each network device of the plurality of network devices for one or more logical paths of a physical interface from the given network device over a wide area network (WAN). Additionally, the NMS may include processing circuitry in communication with the memory and configured to: determine, based on the path data, one or more application health assessments for one or more applications, wherein the one or more application health assessments are associated with one or more application time periods for a site, and in response to determining at least one failure state, output a notification including identification of a root cause of the at least one failure state.
APPLICATION SERVICE LEVEL EXPECTATION HEALTH AND PERFORMANCE
Techniques are described for monitoring application performance in a computer network. For example, a network management system (NMS) includes a memory storing path data received from a plurality of network devices, the path data reported by each network device of the plurality of network devices for one or more logical paths of a physical interface from the given network device over a wide area network (WAN). Additionally, the NMS may include processing circuitry in communication with the memory and configured to: determine, based on the path data, one or more application health assessments for one or more applications, wherein the one or more application health assessments are associated with one or more application time periods for a site, and in response to determining at least one failure state, output a notification including identification of a root cause of the at least one failure state.
NETWORK QUALITY TESTING
Systems and methods for network quality testing are provided. Synthetic traffic may be sent through a first flow path and a second flow path. The second flow path includes a portion apportionable to the first flow path, internal to a server, and a portion apportionable to an external flow path, external to the server. Durations of traffic traveling through the first flow path and the second flow path are compared to determine the portion of the second flow path apportionable to the external flow path. In an example, time stamping may be performed by component(s) of the server, such as a kernel, to determine the durations of the traffic traveling through the first flow path and the second flow path.
NETWORK QUALITY TESTING
Systems and methods for network quality testing are provided. Synthetic traffic may be sent through a first flow path and a second flow path. The second flow path includes a portion apportionable to the first flow path, internal to a server, and a portion apportionable to an external flow path, external to the server. Durations of traffic traveling through the first flow path and the second flow path are compared to determine the portion of the second flow path apportionable to the external flow path. In an example, time stamping may be performed by component(s) of the server, such as a kernel, to determine the durations of the traffic traveling through the first flow path and the second flow path.