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

Smarts IP: How do you enable ICMP Latency Monitoring? (305148)

Last Updated: 12/17/2018Categories: How toTotal Views: 2801Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

This article explains how to enable ICMP Latency Monitoring in Smarts and how to use the Smarts IP latency monitoring feature.

The ICMP latency monitoring feature in Smarts IP provides round-trip times for all polled IP objects in the environment that are monitored by ICMP.  The round-trip time reflects the latency (in milliseconds) that is observed during the last ICMP poll.

ICMP latency monitoring in Smarts IP - SlowResponseTime events
If the round-trip time between the sending of an ICMP request to an IP address and the receiving of the ICMP response from the IP address exceeds a user-defined latency value, but does not exceed a user-defined timeout value, the Smarts IP Availability Manager generates an IP SlowResponseTime event. The Smarts SAM Global Manager or an external subscriber subscribes and presents the IP SlowResponseTime event.

Enabling ICMP latency monitoring in Smarts IP
The ICMP latency monitoring feature is not enabled by default. The ICMP latency monitoring feature is enabled and configured through the Connectivity Polling setting in the Smarts IP Polling and Thresholds console. You enable and configure the ICMP latency monitoring feature by setting the MaximumLatency parameter to a non-zero value, and by subscribing to the IP::SlowResponseTime event in Smarts SAM or in an external subscriber. This is done as follows:

Set the MaximumLatency parameter to a non-zero number. To do this, open the Smarts IP Polling and Thresholds Console. The Maximum Latency parameter setting is configured under Settings > Connectivity Polling:

Subscribe to the IP::SlowResponseTime event in Smarts SAM or in an external subscriber. In some environments such as Smarts SAM 9.2, this subscription is already set up by default.  To validate whether this subscription already exists, do the following:

Open a command prompt and navigate to the BASEDIR of the Smarts SAM installation (such as /opt/InCharge/SAM).

Change to the <BASEDIR>/smarts/bin directory

Open the dxa-conn-perf.conf configuration file in sm_edit with the following command:

./sm_edit conf/ics/dxa-conn-perf.conf

Scroll down to the Performance section and check whether or not the following line exists:

sub     IP::.*::SlowResponseTime/e

If the above line already exists, no further steps are required. If the above line does not exist, add it to the Performance section, and save and close the dxa-conn-perf.conf configuration file.

If you changed the dxa-conn-perf.conf configuration file, restart the SAM server to implement the change.

Related Information

NOTE1:
To check the status of polling, execute this command in the command line.

dmctl -s <IN Charge domain name>  get ICMP::I-ICMP-IP-<IP address of device> ::RoundTripTime

NOTE2:
To subscribe to the event without changing the above file, execute this command.

./sm_adapter -s <in charge AMPM Domain>   -b localhost:427 --subscribeProp=ICMP::.*::RoundTripTime --output=roundtrip.log --daemon

NOTE3: If you do not follow these instructions by setting the maximum latency value to something other than zero, you will see this result when you query for this value using DMCTL.

dmctl -s <IN Charge AMPM domain name>  get ICMP::I-ICMP-<IP address>160::RoundTripTime

MR-E-NOT_CURRENTLY_MONITORED-Instrumented attribute RoundTripTime is not currently being monitored by accessor; in file "/work/tancurrent/DMT-9.2.0.0/19/smarts/repos/accessors/MR_Accessor.c" at line 951

dmctl -s <IN Charge AMPM domain name>  get ICMP::I-ICMP-IP-<IP address>.160

Properties of ICMP::I-ICMP-IP-192.168.1.219:
Address = 192.168.1.219
CreationClassName = ICMP
Description =
DisplayClassName = IP
DisplayName = 192.168.1.219 [host-192.168.1.219]
DownPollingInterval = 120
IPInstrumentationsReverse = { Router::host-192.168.1.219 }
IPStatus = OK
InstrumentationKey = Fault
InstrumentationOK = TRUE
Instruments = IP::IP-192.168.1.219
InterfaceAdminStatus = UNKNOWN
InterfaceMode = NORMAL
InterfaceName =
InterfaceOperStatus = UNKNOWN
InterfaceStatus = UNKNOWN
InterfaceType = GENERIC
IsResponsive = TRUE
IsSlowToRespond = FALSE
IsUnresponsive = FALSE
MaxClearDelay = 150
MaxFailureRetryCount = 4
MaxNotificationDelay = 180
MaxSuccessRetryCount = 0
MaximumLatency = 0
MetaMemberOf = { }
MinClearPending = 30
MinNotificationPending = 60
Name = I-ICMP-IP-192.168.1.219
Netmask = 255.255.255.0
NetworkNumber = 192.168.1.0
RoundTripTime = <unknown>
ServiceName =.219

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 - SMARTS

Take Our Survey

Support Assistant