Back=right
mouse click.
Concurrent Connections
This is a dynamic display that can have three graphs: one each for FTP, HTTP(S), and application connections. For FTP, the connection measured is the session for both commands and data. For HTTP(S), the connection measured is the session for both requests and responses. The default refresh rate is 30 seconds. Both the X and Y axis scales are variable. The X axis scale is determined by the set refresh rate and the Y axis scale is determined by the number of concurrent connections at a given time.
Bandwidth Control Display
This is a dynamic display that shows the current upstream and downstream bandwidth control status on IWSVA.
Interface Status
The following icons represent the status of the interface:
|
Note:
If the system time is adjusted backward (either manually or
through automatic network time server synchronization), IWSVA stops
gathering real-time statistical information. To have IWSVA collect
real-time statistical information, you must restart the metric management
daemon. Type the following commands:
/etc/iscan/S99ISMetricMgmtd stop
/etc/iscan/S99ISMetricMgmtd start
Hardware Status
The Hardware Status feature provides the administrator with the ability to monitor hardware information about fans, voltage, temperature, etc. on Intelligent Platform Management Interface (IPMI)-enabled devices.
Note: IWSVA hardware monitoring is only compatible with the Baseboard Management Controller (BMC) with Intelligent Platform Management Interface (IPMI) v2.0 support installed on bare metal.
Administrators can query the hardware status information using the IWSVA Web console or by SNMP request. If SNMP trap is enabled, an alert will be sent when critical system events are detected, such as “temperature threshold exceeded”, “voltage threshold exceeded”, etc.
Alerts can be sent to notify administrators of any problems. They are configured at: Notification > SNMP Notifications Settings > Hardware monitoring events (check box).
CPU Usage Display
This is a dynamic display that shows CPU utilization on the local system. For multiple CPUs, the display shows the average IWSVA usage across all CPUs. It does this by displaying a single line for all CPU utilization. IWSVA determines the CPU utilization based on the CPU cycles used, the CPU cycles used by IWSVA, and the total CPU cycles used by the backend, CPU-monitoring API.
By default,
IWSVA samples the CPU usage each second for two minutes, giving you
120 data points (1 data point per sec * 120 sec (2 min) = 120 data
points). In the file /etc/iscan/intscan.ini,
under [metrics]
section, you can change the default refresh rate by modifying the
parameter cpu_refresh.
After modifying the file, restart the Tomcat service by using the
following command:
/etc/iscan/S99IScanHttpd
restart
Clicking the 1-day or 30-day button opens a window that shows a static chart with one or 30 days of CPU usage, respectively. IWSVA retrieves this information from the database. If the database does not contain enough data, then the display shows the data that is available.
Physical Memory Usage Display
This is a dynamic display that shows the amount of physical memory used by the local IWSVA machine.
By default,
IWSVA samples the CPU usage each second for two minutes, giving you
120 data points (1 data point per sec * 120 sec (2 min) = 120 data
points). In the file /etc/iscan/intscan.ini,
under [metrics]
section, you can change the default refresh rate by modifying the
parameter cpu_refresh.
After modifying the file, restart the Tomcat service by using the
following command:
/etc/iscan/S99IScanHttpd
restart
Clicking the 1-day or 30-day button opens a window that shows a static chart with one or 30 days of physical memory usage, respectively. IWSVA retrieves this information from the database. If the database does not contain enough data, then the display shows the data that is available.
Hard Drive Display
This is a static display that shows the status of the disk(s) used by IWSVA for its system files, quarantine space, temporary space, and logs. If the database resides on the same drive as any of these directories, then the database disk usage is also included in the display. The scale along the Y-axis varies according to the data being presented (for example, from 0 to 100%).
You can specify threshold alert values and the frequency of alerts so that you are notified when any of the hard disk statuses reach a critical level. IWSVA can send these alerts either through email, SNMP trap/notification (if enabled), or both.
You cannot
configure the display values in IWSVA web console, but you can edit
the refresh rate in the init file, modify key cpu_refresh
under metrics
section in file /etc/iscan/intscan.ini,
then restart Tomcat services by using the following command:
/etc/iscan/S99IScanHttpd
restart