Chatta subito con l'assistenza
Chat con il supporto

Foglight for Infrastructure 5.9.8 - Infrastructure Utilities User Guide

Monitoring Web transactions
Configuring credentials for Web sites requiring user or proxy authentication Exploring your collection of monitored Web sites Investigating the performance of Web transactions and monitoring locations Exploring Web Monitor services Generating reports Configuring Web Monitor agent properties View reference
Monitoring network devices

Configuring the ICMP service for monitoring

Foglight Net Monitor uses the ICMP (Internet Control Message Protocol) service to communicate with network devices. There are two versions of this service that are available for use:

•
Foglight Agent Manager ICMP service uses the udp2icmp application, that is installed with the Agent Manager, and can be used to issue ICMP messages to target devices.
•
OS-specific ICMP services use the following OS-level commands to issue ICMP messages to target devices:
•
ping
•
tracert (Microsoft Windows only) or traceroute (Linux only)

Both types of ICMP services are started through an executable application and require proper permissions to execute. For more information, see Configuring the Agent Manager ICMP service and Configuring OS-Level ICMP services.

By default, Foglight Net Monitor uses the Agent Manager ICMP service for monitoring. OS-level ICMP services can be configured, if needed, using the following option

-Dnetmonitor.icmpprovider=OS

There are two ways to specify this option:

•
On the command line, when you start up the Agent Manager. For example:
fglam -s -Dnetmonitor.icmpprovider=OS
•
As a JVM system property, in the <fglam_home>/state/default/config/baseline.jvmargs.config file. For example:
-Dnetmonitor.icmpprovider=OS

Other options are available. For more information, see ICMP service command-line options.

ICMP service command-line options

The following table describes the Foglight Net Monitor parameters that can be used to configure the ICMP service. You can specify these options on the command line, or in an Agent Manager configuration file. For more information, see Configuring the Agent Manager ICMP service.

 
Table 1. Foglight Net Monitor parameters used to configure the ICMP service
Option
Description
netmonitor.icmpprovider

All agent instances managed by this Agent Manager uses the OS-level ICMP service. This type of ICMP service uses ping and traceroute/tracert commands. The login user must have proper permissions to execute these commands, without providing a password.

netmonitor.ping.path

Unix/Linux only. If the login user does not have the permissions to execute the ping command, use this option to specify the command path.

netmonitor.traceroute.path

Unix/Linux only. If the login user does not have the permissions to execute the traceroute command, use this option to specify the command path.

netmonitor.threadpool.size

Unix/Linux only. Sets the thread pool size. You should specify at least 10.

Configuring the Agent Manager ICMP service

Windows configuration
•
The user account launching the Agent Manager application must be an Administrator.
•
To prevent time-outs in the trace route responses for all hops except the first and the last when the firewall is on, configure the firewall to enable inbound ICMP network traffic. For more information, visit http://technet.microsoft.com/en-us/library/cc972926%28v=ws.10%29.aspx.
Specifically, for IPv4, you need to use the following configuration:
ICMP Echo Request (Type 8, Code 8)
ICMP Echo Reply (Type 0, Code 0)
ICMP TTL Expired (Type 11, Code 0)
ICMP Port Unreachable (Type 3, Code 3)
UNIX/Linux configuration
•
If the user account launching the Agent Manager application is not the root user, they must be granted permissions to execute the <fglam_home>/client/<build id>/bin/udp2icmp application without providing a password.
•
If the Agent Manager secure-launcher is configured with a sudo path, requiretty must not be set.

Configuring OS-Level ICMP services

Windows configuration
•
Ensure that the ping and tracert commands are available.
•
The user account launching the Agent Manager application must have permissions to execute both ping and tracert commands.
UNIX/Linux configuration
•
Ensure that the ping and traceroute commands are available.
•
The user account launching the Agent Manager application must have permissions to execute both ping and traceroute commands.
•
For Suse Linux with the apparmor module, enable traceroute to execute with the -I option. For example:
# Execute blow commands to enable traceroute -I option
complain /usr/sbin/traceroute
/etc/init.d/boot.apparmpr restart

Managing monitored network devices

The Devices Management dashboard displays a list of the monitored network devices. It allows you to add or remove network devices from the collection, and to edit their data collection parameters.

 
* 
NOTE: Before adding new network devices for the first time using this dashboard, you must ensure that the following steps are completed:
•
Deploy the Net Monitor Agent package to one or more desired monitoring locations (hosts).
•
Create one or more Net Monitor Agent instances.
•
Set the running mode for the newly agent created instances (Quick Check more or Normal mode).
•
Configure data collection intervals for the newly created agent instances.
•
Activate the newly created agent instances, and start their data collection. If you need to monitor the same collection of sub-network devices, you can specify private network properties, as required.

You can add one or more network devices using the Devices Management dashboard, and select desired agents (monitoring locations). Use this dashboard to gain an understanding of the complexity of your monitored environment and to review any alarms associated with the monitored devices.

For complete details about the views appearing on this dashboard, see Net Monitor Devices Management views.

To explore the collection of monitored network devices:
1
Log in to the Foglight browser interface.
2
On the navigation panel, under Dashboards, click Infrastructure > NetMonitor > Devices Management.
The Devices Management dashboard appears in the display area.

For more information, see the following topics:

•
Expanding your collection of monitored network devices
•
Removing network devices from the existing collection
•
Viewing and editing individual network device details
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione