Node Report
The Node Report provides details about a selected node. Node details such as status, sysName, ip address, type, model, uptime, interfaces, location, contact, description, last update, vendor, object name, group role and net and the interface table are provided.
Interfaces and storage items are details if present.
Graphs are provided which details the following: reachability, availability and health, response time, CPU utilisation, number of routes, ip utilisation, IP fragmentation/reassembly (as a % of packets received), buffer utilisation.
Node Health Report
Display the attributes for a selected node for a given period. Attributes displayed are: Status, Device, Availability, Interface Availability, %CPU, 95th% CPU, Max %CPU, CPU Exc., %Mem Free, 95th% Mem Used, Max %Mem Used, %Mem Util, %IO/VIR Mem Free, 95th% IO Mem Used, Max %IO Mem Used, %IO/VIR Mem Util, Conditions, Actions.
Interface charts are provided for packets per second, errors and discards, bits per second and CBQoS for each interface.
The formulas used for calculation of the reporting conditions are configured in the opReports Configuration file.
Device Availablity = Condition: "Device has LOW or VERY LOW availability"
Action: Investigate causes for low availability
Formula used for Calculation:
- Very Low device avaliability less than 99.9
- Low device avaliability less than 99.999
Interface Availablity = Condition: "Device has LOW or VERY LOW interface availability"
Action: Investigate causes for low interface availability
Formula used for Calculation:
- Very Low interface avaliability less than 80
- Low interface avaliability less than 95
CPU Utilisation = Condition: "Device has VERY HIGH, HIGH or MODERATE CPU utilisation"
Action: Investigate causes for CPU utilisation
Formula used for Calculation:
- Very High CPU utilisation: greater than 30%
- High CPU utilisation: greater than 20%
- Moderate CPU utilisation: greater than 12%
If the node has multiple CPUs then the utilisation measure is averaged over all CPUs.
CPU Exceptions
The count of times the CPU utilisation exceeded the "CPU Exception Threshold" of 20%. If the node has multiple CPUs then this is the sum of the exception counts of all CPUs.
Memory Utilisation = Condition: "Device has VERY LOW or LOW main memory free"
Action: Investigate causes for free low main memory
Formula used for Calculation:
- Very Low free main memory less than 10
- Low free main memory less than 25
IO or Virtual Memory Utilisation = Condition: "Device has VERY LOW or LOW IO or Virtual memory free"
Action: Investigate causes for low free IO or Virtual memory
Formula used for Calculation:
- Very Low free main memory less than 10
- Low free main memory less than 25
WAN Report
Display the WAN Link performance for a selected node.
Node details displayed are: status, conditions, actions, device, availability and response time.
For each interface on the node, the following are displayed: interface, speed, average utilisation, maximum utilisation, average inbound errors (in %), average outbound errors (in %), average inbound discards (in %), average outbound discards (in %), average inbound utilisation (in %), average outbound utilisation (in %), maximum inbound utilisation (in %), maximum outbound utilisation (in %).
Formula used for Calculation
Maximum and Average input and output utilisation is calculated for the interface. The larger of maximum and average input and output utilisation is used in formula.
Link Availablity = Condition: "Router has LOW interface availability"
Action: Investigate carrier for interface problems
Interface avaliability less than 99.9%
Link Availablity = Condition: "Router has VERY LOW interface availability"
Action: Investigate carrier for interface problems
Interface avaliability less than 95%
Overutilised Links = Condition: "WAN link has VERY HIGH utilisation"
Action: Investigate WAN Upgrade Urgently
Average link utilisation is above 80% average utilisation
Overutilised Links = Condition: "WAN link has HIGH utilisation"
Action: Investigate WAN Upgrade
Average link utilisation is above 65% average utilisation
Links Considered Normal = Condition: "WAN link has acceptable utilisation"
Action: WAN utilisation is OK
Average link utilisation is less than 65%
Input and/or Output Errors = Condition: "WAN link has input/output errors"
Action: Investigate cause of interface errors, likely transmission
Error rates higher than 1% of input or output packets
Input and/or Output Discards = Condition: "WAN link has input/output discards"
Action: Investigate cause of interface discards, likely related to QoS or buffer overruns.
Discard rates higher than 1% of input or output packets
QoS Report
The QoS report is intended to provide an overview of the QoS configuration and utilisation of the network. NB. To have QoS reporting, NMIS has to be collecting cbqos stats, which is configured in the NMIS System Configuration, updating the Node details.
Rules
To assist in the assimilation of the data, a few simple rules have been applied to the statistics to assist with highlighting some possible problem areas.
Queue Drop
This condition indicates that a QoS Policy is being exceeded and packets in this class have been dropped. It may or may not be impacting applications, depending on how they handle packet loss. For example, HTTP will generally handle packet loss with no problems, while voice and video do not suffer packet loss very well at all.
If an interface utilisation is greater than 0% input and 0% output;
AND DropPkt is greater than 1 packet per second;
THEN this class is highlighted yellow.
Class Under Utilised
This condition indicates that the QoS class was configured to be used for traffic, and there are VERY low levels of traffic in that class. It might be possible to update the QoS policy allocating some of this bandwidth to other classes.
If an interface utilisation is greater than 0% input and 0% output;
AND the Policy Percent is greater than 0 percent;
AND PrePolicyUtil is less than 1 percent;
THEN this class is highlighted yellow.
Class Utilisation Exceeding Policy
This condition indicates that QoS class was configured for a certain bandwidth and the traffic levels have exceeded the configured policy. This may not be a problem, depending on QoS configuration, traffic may be being forwarded or discarded, if necessary increase the bandwidth allocated to this class.
If an interface utilisation is greater than 0% input and 0% output;
AND PrePolicyUtil exceeds the classes configured bandwidth Percent;
THEN this class is highlighted yellow.
Uptime Report
Display the uptime data for a given node.
The Uptime report is intended to provide an overview of devices which have restarted in the last 7 days as well as devices which have been up for over 365 days.
A reason for the devices restarting in the last 7 days should be known.
Response Time Report
The Response Time report tabulates the selected nodes in descending order of their average response time. Besides the average and maximum measurements, the report also shows the 95th percentile of the response time. These readings are in milliseconds.
Response Time Exceptions
This column shows the number of times a device's response time exceeded the exception threshold. This threshold is configured in the opReports.nmis configuration file, and its current value is 10 ms.