Overview
This article provides information regarding the Exinda CLI command monitor
.
You can use the monitor
command to configure details relevant to monitoring charts and the monitoring data that is collected. You can configure how the data is displayed, how the traffic is analyzed for monitoring purposes, which order of resolution methods are tried when resolving IP addresses to hostnames, whether data is collected, and whether collected data is deleted.
Information
- {}: Options are enclosed in braces and are separated by '|'
- []: Optional keywords are enclosed in brackets
- <>: User input is required where variables are enclosed in greater-than and less-than symbols
The following table describes the commands used for performing common actions related to monitor:
Action Description |
Command | Parameter Description |
Configuring APM (Application Performance Management) |
||
To set the normalization size for APM calculation | monitor apm transaction normalize <value> |
<value> - When calculating the network delay experienced during a transaction, the packet size can be normalized to reflect a consistent packet size allowing you to more easily compare delays when the packets are variable in size. Specify the number of bytes used to normalize the calculation of the network delay during a transaction. The default value is 1024, and the maximum value is 1048576. |
Configuring Monitoring Sensitivity |
||
To set bit-torrent monitoring sensitivity | monitor bit-torrent sensitivity {high|med|low} |
{high|med|low} - Setting this to 'high' is recommended for most service provider environments. Setting it to 'low' is recommended in cases of high false positives. |
To set eDonkey monitoring sensitivity | monitor edonkey sensitivity {high|med|low} |
{high|med|low} - Setting this to 'high' is recommended for most service provider environments. Setting it to 'low' is recommended in cases of high false positives. |
To specify the sensitivity of the openVPN traffic monitoring |
monitor openvpn sensitivity {aggressive|safe} |
Not Applicable |
To set the minimum number of packets needed before it is monitored | monitor sensitivity <sensitivity> |
<sensitivity> - Acceptable values are between 1 and 10, with 10 being the lowest sensitivity. |
To set Skype monitoring sensitivity | monitor skype {high|med} |
{high|med} - Setting this to 'high' is recommended for most service provider environments. |
Configuring Displays |
||
To modify how monitoring screens are displayed | monitor display {chart-size|graphing|real-time|table-size|url-size} |
|
Controlling Order of Hostname Resolution Methods |
||
To control the order of resolution methods tried when resolving IP addresses to hostnames | monitor host-resolution {DNS|IP|Netbios|Network_Object} rank <ranking
order> |
There are multiple host resolution methods that can be used to resolve IP addresses to hostnames. The system will attempt to resolve the hostname using one of the methods. If that method fails it will try another method. You can determine the order of host resolution methods that the system will use by ranking the first method as 1, the next as 2, and so on.
|
Configuring Traffic Analysis & Monitoring |
||
To enable viewing flow data in the real-time monitor per bridge or merged into a single flow | [no] monitor dual-bridge-bypass |
When enabled, a flow that traverses more than one bridge will be shown multiple times, once per bridge, in the real-time monitor. |
To enable layer7 monitoring | [no] monitor layer7 |
Controls whether to analyze the application signatures within a packet to further classify the traffic within the reports. For example, when analyzing HTTP and FTP traffic and an MPEG file is detected within the packets, the application associated with the connection is changed to MPEG. When disabled, the Layer 7 signatures within packets are not analyzed and any application detection objects with Layer 7 rules are ignored. |
To enable IPv6 link local traffic monitoring |
[no] monitor linklocal |
Not Applicable |
To configure Application Specific Analysis Modules (ASAM) settings, which enables/disables drill-down monitoring capabilities for the specified application | [no] monitor asam {anonymousproxy|apm|asymm-route|citrix|dcerpc|http|ssl| |
Disable this module to stop the appliance in locations where privacy policy does not permit this type of user identification.
|
Configuring Statistics Collection |
||
To enable ignore internal to internal traffic | [no] monitor ignore-internal |
Your network may have network objects on the WAN side of the appliance that has been configured as Internal objects, for example, a router or firewall. Enabling the Ignore Internal-to-Internal option prevents traffic between network objects being included in the reports. |
To enable collecting statistics | [no] monitor statistics {subnet|subnet-application|virtual-circuit} enable |
|
Deleting Stored Monitoring Data |
||
To clear stored monitoring data |
|
|
Viewing the Configuration |
||
To display the diagnostic configuration, such as graphing format, Layer 7 monitoring, host resolution, and monitoring database status |
show monitor diagnostics |
Not Applicable |
To display the monitoring configuration |
show monitor setup |
Not Applicable |
Example
monitor host-resolution Network_Object rank 1
monitor host-resolution Netbios rank 2
monitor host-resolution DNS rank 3
monitor host-resolution IP rank 4
Find more CLI commands.