Device details - LiveNX - 25.3.0

Device identification panel

Provides essential details for quickly identifying and validating the monitoring device. In practical use it serves to confirm that the monitoring tool can reach the device, and helps verify if the device rebooted unexpectedly.

Alert summary

Visual donut chart helps you spot severity mix at a glance. This is where you can start triaging problems.

Tabs menu

Each tab provides a focused view of the device's system components:

• System: CPU, memory, and overall health metrics
• Interfaces (active tab): name, status, throughput, discards and errors
• Hardware: Power supplies, fans, and temperatures
• VLAN / ARP / Routing / Neighbors: Logical and protocol-level data (L2/L3 topology, neighbor discovery, route tables, etc.)

System tab

Shows resource utilization of the device’s main processing and storage components — CPU load, memory consumption, and available/used storage capacity.

For network devices storage has different properties, as it is usually flash memory and is used to store boot image files and configuration files. In most cases network devices have only one partition unlike servers, loadbalancers and some linux based network devices that may have multple partitons.

CPU core data is shown with usage trend data in percentage of total available CPU. If device has multiple CPUs, they are automatically detected and showed independently.

Interfaces tab

Provides per-interface traffic statistics, health, utilization percentages, discards and error counters - essentially to confirm whether the device is online, passing traffic and operating within expected thresholds. Status of interfaces can usually be up (interface is operative and sends/receives traffic), down (not operational because it is not connected to the other device, or there is interface down on the other side), and administrative down (interface is connected, but deliberately disabled so it doesn’t send/receive traffic).

There are two dynamic metrics shown, “Bits” which shows interface usage at any given moment, and “Pkts” which shows number of packets in second (so regardles of packet size, only headers are counted here). Those values are dependent, but this relation is complex so they are shown independently.

Errors on the interfaces are shown as absolute count of erroneous packets in both direction and this value ideally should be always 0. Discards are also absolute count numbers of packets that do not conform to any parameters that it can be forwarded to the next hop. Reasons can be MTU (Maximum Transfer Unit) or some other packet parameter that doesn’t allow packet to be further processed.

Hardware tab

Displays chassis health data — temperature sensors, power supply and fan status.

Depending on network device, some hardware data can be obtain. On more simple devices, there is usually one temperature sensor, and multiple power supply and fan units, on which only status can be known. Temperature sensors read interchasis temperature in real time and can be shown in the graph. Some more advanced devices support voltage/amps for power supply units, and rpm data for fans, so it can be seen in real time as well.

VLAN tab

The VLAN tab displays the operational status of each VLAN detected on the device.

If interface-level VLAN metrics are available (e.g., tagged traffic statistics, per-port VLAN participation), they are included below the main status view. Otherwise, only the VLAN operational information is shown. Most VLANS do not have virtual interfaces assigned, and for most network devices there are no internal counters to represent traffic for those VLANs. If that is the name, only operation state and name are shown together with VLANid.

ARP tab

Lists ARP table entries with IP–MAC mappings and associated interfaces. In this case, MAC address of foreign device, together with coresponding IP address are shown, together with the interface that it is learned on. In the case that IP address is not local address to the device, default gateway is ARP-ed (that is asked for it’s MAC address) and it is shown in ARP table instead of device that really has that IP address.

Routing tab

Displays active routing entries, protocols, next-hops, and route metrics. Currently, this table shows only “global” or “default” routing table, and it will show routing table even if only default gateway is specified (for L2 switch for instance). Metric of the route are shown as Metric1 filed on SNMP table. Those metrics are not comparable, as they belong from different routing protocols.

Neighbors tab

The Neighbors tab provides Layer 2 topology visibility by listing discovered devices and their connection points.

Data is collected via neighbor discovery protocols such as CDP (Cisco Discovery Protocol) or LLDP (Link Layer Discovery Protocol), depending on device support. LLDP is opened protocol supported by most device vendors including Cisco, and CPD is Cisco exclusive protocol. Those protocols are designed to exchange information of neighbors to each other, including interfaces that interconnect devices, device capabilities, device name and software version.

L3 routing protocols also form neighbor relations, but are not exchanging same information, as they are used for mostly IPv4 and IPv4 routes, some additional parameters like route metrics.