Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

How do I install and configure the ICMP poller in Watch4net (320477)

Last Updated: 3/22/2024Categories: How toTotal Views: 2636Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

About the ICMP-Collector:

This APG collector is used to ping a list of hosts and determine if they are up (responding to ICMP
echos) or down. This collector will attempt to poll all hosts within the specified period, while preserving
system resources as much as possible by smoothing out the polling on the available time.

Note: In order to run properly root permissions will be needed

Metrics include:

Icmp echo round trip time (default name: icmpRtt): The average time for an icmp echo resquest
response. This value is impacted by the drop-max-value setting.

Icmp reachability ratio (default name: icmpReachability): The ratio of responses versus the
number of pings sent to the target. Values are between 0 and 1. If one ping is specified, 0 or 1
is returned, which corresponds to basic Icmp availability.

Optional: Icmp availability (default name: icmpOk): Indicates that the target answered any of the
pings sent (value = 100) or none (value = 0). This can be set up by using a filter.

How to install the ICMP-Collector:

1. Navigate to bin directory

Default path for Linux: /opt/APG/bin

Default path for Windows: C:\Program Files\APG\bin

2. Make sure the ICMP-collector is available

Command for Linux: ./manage-modules.sh list available | grep ICMP

Command for Windows:manage-modules.cmd list available | findstr ICMP

You should receive an output similar to below:

# ./manage-modules.sh list available | grep ICMP
* icmp-collector-5.6u1-linux-x64                      : Collecting       ICMP-Collector                        v5.6u1    linux-x64
* icmp-collector-5.6u2-linux-x64                      : Collecting       ICMP-Collector                        v5.6u2    linux-x64

3. Install ICMP-Collector ( you can use the output from the above command for the full name of the collector)

Command for Linux: ./manage-modules.sh install icmp-collector-5.6u1-linux-x64

Hit enter or type yes to continue with the operation.

How to configure the ICMP-Collector:

After installing the ICMP-Collector you must enable the ICMP collector by enabling it on a Collector-Manger instance.

Modify the collecting,xml

1. Edit your chosen Collector-Manager instance collecting.xml by declaring the ICMP-Collector  (APG/Collecting/Collector-Manager/ <INSTANCE NAME> /conf/collecting.xml)

Add the declaration in the collector section.

Example:

<collectors>
... other collectors
<collector enabled="true" name="ICMP-Collector" next="SomeFilter" type="icmpCollector" config="ICMP-Collector/<INSTANCE_NAME>/conf/icmp-collector.xml"/>
... other collectors
</collectors>

* The 'next' field will need to point to the next place to send data filter in your collecting.xml usually some filter.
** The 'config' field will need to point to the absolute or relative path of your icmp-collector.xml

Note:
It is strongly recommended to use a distinct instance of the Collector-Manager to run the ICMP-Collector. Some collectors, such as the APG-Selft-Monitoring collector, are not designed to run as root.

Verify icmp-collecting.xml

1. Navigate to icmp-collecting.xml ( APG/Collecting/ICMP-Collector/Default/conf/icmp-collector.xml)

2. Verify the fields in the configuration.

<maxIcmpThreads>1</maxIcmpThreads> : 1 thread. This is enough for a small POC (10-15 devices)
<periodicity>240</periodicity>: 4 minute polling period. May be set to 5 minutes to match other SNMP or SMARTS metrics
collection.
<source-property>icmpCollector</source-property>: Source name is icmpCollector : this value appears in the raw values source property. And should match your declaration in the collecting.xml
<snmp-polling-distribution>conf/snmp-polling-distribution.xml</snmp-polling-distribution>: No editing is needed if this suits your requirements. If you are not using the SNMP Collector, please use a < targetsFile > instead of the < snmp  polling  distribution > file.

Enable root privledges for the collector

1. Navigate to unix-service.properties for the Collecting-Manager instance running the ICMP-Collector. (APG/Collecting/Collector-Manager/conf/unix-service.properties)

2. Uncomment the following lines by removing the # at the start of the line.

#apg.user=root
# jvm.param.#=-Djava.rmi.server.hostname=$HOSTNAME$
# jvm.param.#=-Dcom.sun.management.config.file=conf/stats.properties

Update modules

1. Update the Collector Manager instance that you are running ICMP-Collector on. This is the collector that you gave root access to.

Run the following command to update  APG/bin/manage-modules.sh service install collector-manager (instance name) .

2. Update the ICMP-Collector

Run the following command "./manage-modules.sh update icmp-collector"

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - Watch4Net/M&R

Take Our Survey

Support Assistant