立即与支持人员聊天
与支持团队交流

Foglight for Infrastructure 6.3.0 - Foglight for Net Monitor User and Reference Guide

Monitoring network devices

Foglight Net Monitor provides device availability and packet loss monitoring between monitoring locations and network devices. Use it to:

•
Monitor the network against service level agreements.
•
Check for the presence of devices that are critical to your operating environment.

When you deploy Foglight Net Monitor, a set of predefined dashboards enables you to view the performance of the monitored network devices. This allows you to ensure consistent network device performance by re the collected statistics. Better management of your network devices can be achieved when you are alerted to potential problems before end users are affected.

Foglight Net Monitor relies on the Net Monitor Agent to collect data. The agent collects transaction information from monitored devices and visualizes the collected data in Foglight. You need to configure one agent instance on each monitored location.

Start by installing Foglight Net Monitor on the Management Server, deploying the Net Monitor Agent package, and creating agent instances on one or more hosts. For installation instructions, see the Foglight Net Monitor Release Notes.

Foglight Net Monitor uses the ICMP (Internet Control Message Protocol) service to monitor network devices. You need to configure this service to enable communication with network devices. For more information, see Configuring the ICMP service for monitoring.

As a next step, you can specify the devices that you want to monitor using the Devices Management dashboard. In addition to managing the collection of monitored network devices, this dashboard allows you to edit the data collection settings. For more information, see Managing monitored network devices.

Next, navigate to the Performance Browser. This dashboard displays the state of your system performance, providing a visual representation of the status of the monitored network devices and locations. Using this dashboard on a daily basis you can obtain an in-depth understanding of the state of your monitored network devices. Monitoring the same collection of network devices from different agent locations allows you to rule out any issues that may be related to host connectivity rather than device responsiveness. For more information, see Investigating the performance of network devices.

The Net Monitor Agent is equipped with a set of properties that affect its running state. You can make changes to them, as required. For more information about the Net Monitor Agent properties, see Configuring the agent properties.

For additional information, see the following topics:

•
Generating reports
•
View reference

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
自助服务工具
知识库
通知和警报
产品支持
下载软件
技术说明文件
用户论坛
视频教程
RSS订阅源
联系我们
获得许可 帮助
技术支持
查看全部
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级