The Status page displays status and performance information.
Topics:
- Are the data collection processes running?
- How many records is the data collector processing?
- Are there any data sources that cannot be monitored?
- What is the load on the server?
- How many days of data are stored on the server?
- What ports are being used to receive data?
Are the data collection processes running?
The Data Collection line shows whether the data collection processes are Running or Stopped. If they are stopped you will not be collecting data and the other statistics on the page will be incorrect. Go to the Sentinel:File>Control page to start data collection.
How many records is the data collector processing?
The following statistics describe the amount of data the data collector is processing:
- Interfaces, the number of switch/router interfaces being monitored.
- Flow Agents, the number of switches/routers being monitored for traffic flows (i.e. using sFlow or NetFlow). The number of flow agents cannot exceed the agent limit for the software license, any additional flow agents will be ignored.
- Samples, the rate at which the server is processing traffic samples.
- Bytes, the byte rate of measurement data arriving at the server. In order to prevent data loss, this value must be kept well below the capacity of the link attaching the server to the network.
- Lost, the number of traffic samples that were lost in the network. If this number is high, it might indicate that congestion in the switches, in a link between the server and the switches (see Bytes), or it might indicate that the server itself is unable to keep up with the arriving samples. Increasing the sampling rate will usually reduce the number of lost samples.
Are there any data sources that cannot be monitored?
The following statistics relate to devices where flow monitoring is configured using SNMP:
- Unreachable, the number of interfaces that the server wishes to collect data from, but which have become unreachable over the network. Click on the link to see which interfaces are no longer accessible.
- Other Manager, the number of interfaces that cannot be monitored because another collector is already monitoring them. Click on the link to see which interfaces are unavailable and who is using them.
What is the load on the server?
The following statistics summarize the load on the server:
- CPU Load, the load average on the CPU. This number indicates the average number of tasks ready to run at any instant. If the number is less than 1 then the CPU has spare capacity. The number may exceed 1 during periods when the server is busy handling queries, but a persistently high number might indicate that the server is becoming overloaded (check Lost to see if lack of CPU resources might be causing data loss).
- CPU Count, the number of processing cores on the server.
- Memory, the memory utilization and amount of free memory. It is important to ensure that there is always spare memory capacity, insufficient memory will cause the server to slow down and cause data to be lost (see Lost).
- Disk, the disk utilization and amount of free disk space.
How many days of data are stored on the server?
The History Database line summarize the interval for which data is stored on the server.
Note: The size of the database is controlled by settings on the File>Configure page.
What ports are being used to receive data?
The UDP and TCP ports that Traffic Sentinel is listening on for measurement data are listed at the bottom of the table. If you intend to use one of these measurement protocols, then you must ensure that any firewall on the server is configured to allow connections from your network devices to these ports. If you are using devices configured automatically via SNMP using the sFlow MIB, then the ports listed as Other Ports must be open too.
Note: If these port numbers need to be changed then they can be configured in the global.prefs file.