A method and system for utilizing fault information of a first system device in a first communication system to change a second communication system is provided. A first fault update is received from the first communication system at a cloud-based fault management service. The first fault update includes a request to update first system device fault information in a common database. The common database is updated by the cloud-based fault management service with the first fault update. The cloud-based fault management service performs smart analytics utilizing the first fault update to change the second communication system.

A method and system for utilizing fault information of a first system device in a first communication system to change a second communication system is provided. A first fault update is received from the first communication system at a cloud-based fault management service. The first fault update includes a request to update first system device fault information in a common database. The common database is updated by the cloud-based fault management service with the first fault update. The cloud-based fault management service performs smart analytics utilizing the first fault update to change the second communication system.

A method of displaying a communication state, the method comprising: obtaining, from a storage device, specification information and history information, the specification information being information indicating a specification of a communication performed in response to an occurrence of an event, the history information being information indicating a history of the communication performed in response to the occurrence of the event; identifying, from the specification information, first specification information corresponding to the communication performed at a relative time point separated from a start point set at an occurrence time point of the event; identifying, out of the history information, first history information corresponding to the communication performed at the relative time point; and outputting, to an output device, first correspondence information in which information indicating the communication corresponding to the first specification information and information on the communication corresponding to the first history information are associated with each other.

Techniques are described by which a network management system (NMS) is configured to generate and monitor an RSSI-based proximity zone for a wireless network using a user interface (UI). The NMS may generate a UI comprising UI elements representing access point (AP) devices configured to provide a wireless network at a site; receive, at the user interface, an indication of a user input selecting one or more UI elements representing selected AP devices; establish a proximity zone for each of the selected AP devices based on an RSSI threshold value; receive network data comprising proximity information of a client device relative to the selected AP devices; generate, based on proximity assessments using the proximity information and the RSSI threshold value of the proximity zone, one or more proximity events indicating the client device relation to the proximity zone; and invoke, based on the proximity events, one or more actions.

An example system includes access point (AP) devices configured to provide a wireless network at a site; and a network management system that stores network data received from the AP devices, the network data collected by the AP devices or client devices associated with the wireless network, and one or more processors configured to: receive a time series of SLE metrics based on the network data, determine, based on the time series, whether a network event has occurred, in response to a determination that a network event has occurred, determine a root cause for the network event, and in response to a determination that the root cause of the network event is associated with an AP device, determine a classification of the AP device, and determine a network management action for the AP device based on the network event and the classification of the AP device.

An example system includes access point (AP) devices configured to provide a wireless network at a site; and a network management system that stores network data received from the AP devices, the network data collected by the AP devices or client devices associated with the wireless network, and one or more processors configured to: receive a time series of SLE metrics based on the network data, determine, based on the time series, whether a network event has occurred, in response to a determination that a network event has occurred, determine a root cause for the network event, and in response to a determination that the root cause of the network event is associated with an AP device, determine a classification of the AP device, and determine a network management action for the AP device based on the network event and the classification of the AP device.

A method includes partitioning a set of configuration management (CM) data for one or more cellular network devices into multiple distinct time intervals, each time interval associated with a distinct set of CM settings at the one or more cellular network devices, the CM data comprising multiple CM parameters. The method also includes determining a regression model based on the set of CM data. The method also includes applying the regression model to compute a distinct set of scores and compare the set of scores to estimate whether a performance of the one or more cellular network devices has changed during a second time interval relative to a first time interval.

Methods, systems, and devices are provided herein for a mechanism to identify link down reasons. As described herein, a first port of a first peer device may be determined to have unexpectedly changed to a port down state. Subsequently, a topology file may be referenced to identify a second port of a second peer device with which the first peer device is intended to have a link if not for the first port being in a port down state. In some examples, port settings of the first port may be compared with port settings of the second port. If a port setting for the first port mismatches an associated port setting for the second port, an alert message may be transmitted to a network administrator indicating this mismatch as a possible reason for the first port being in the port down state.

In the present disclosure, a network monitoring system is provided including an IP network monitoring unit (610) that monitors an IP network to which an IP device is connected; and a non-IP device monitoring unit (630) that monitors a non-IP device. It is possible to monitor both the IP network and the non-IP device in a system that includes the IP network including the IP device and the non-IP device.

In the present disclosure, a network monitoring system is provided including an IP network monitoring unit (610) that monitors an IP network to which an IP device is connected; and a non-IP device monitoring unit (630) that monitors a non-IP device. It is possible to monitor both the IP network and the non-IP device in a system that includes the IP network including the IP device and the non-IP device.