Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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: Trap Adapter platform flag RESOLVE_IP on trap_mgr.conf (510914)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

On Smarts trap adapter platform we can enable RESOLVE_IP flag, while trap parsing which will determines whether unrecognized IP Addresses will be resolved before being assigned to the $SYS$ variable.

<SMARTS Based>smarts/conf/icoi/trap_mgr.conf

RESOLVE_IP = FALSE

uncomment the line RESOLVE_IP and change to TRUE.

restart Smarts Trap adapter platform after the change.

Related Information

Below the explanation in trap_mgr.conf file, also the flag can work with CACHE_HOSTS to use file for name resolution.

# --------------------------------------------------------------------------
# This flag determines whether unrecognized IP Addresses will be resolved
# before being assigned to the $SYS$ variable.  For objects already known
# to the system, this option will have no effect.
# NOTE:  Name resolution can be very slow.  A system receiving thousands of
# traps and calling a name server for every request can seriously impact
# the number of traps that can be processed.  Threading can help somewhat,
# but name resolution is NOT RECOMMENDED in large installations unless the
# server is configured to use only host file resolution and the
# 'CACHE_HOSTS' feature is used.  Alternatively, a caching DNS server can
# be run on the trap host to help somewhat, but performance will still
# be impacted.
# --------------------------------------------------------------------------
# RESOLVE_IP = FALSE

# --------------------------------------------------------------------------
# This flag only has meaning if "RESOLVE_IP" is TRUE.  The flag determines
# whether the system 'hosts' will be cached and used to resolve IP addresses
# instead of calling the system functions which may be slow in some cases.
# NOTE:  This is ONLY useful if DNS name resolution is disabled in the
# Smarts environment.  This is sometimes done to improve performance, but
# it requires an extensive hosts table.  By altering the 'HOSTS_PATH'
# below, it is possible to use a special file to load the hosts cache
# instead of using the same hosts file used by the system that the trap
# processor is running on.
# --------------------------------------------------------------------------
# CACHE_HOSTS = FALSE

# --------------------------------------------------------------------------
# This value only has meaning if "CACHE_HOSTS" is TRUE.  It defines the full
# path to the system 'hosts' file.  (It is possible to use a unique file for
# the cache by specifying its path here.)
# --------------------------------------------------------------------------
# HOSTS_PATH = /etc/hosts

Please note if the IP objects is already known to the system, this option will have no effect. You may remove the IP objects in trap adapter platform to take effect for the new trap.

Also there are impact of the resource on name resolution related to the number of trap processing with RESOLVE_IP enable.

below is related code in trap_mgr_parse.asl file

conf/icoi/trap_mgr.conf
rules/icoi-trapd/trap_mgr_conf.asl
rules/icoi-trapd/trap_mgr_parse.asl
if (resolve_ip == "TRUE") {
if ((glob("<0-255>.<0-255>.<0-255>.<0-255>", elementinstancename)) ||
(glob("[0-9a-fA-F]*:[0-9a-fA-F]*:[0-9a-fA-F]*:[0-9a-fA-F]*:[0-9a-fA-F]*:[0-9a-fA-F]*:[0-9a-fA-F]*:[0-9a-fA-F]*", elementinstancename))) {
tempresolve = "";
if (cache_hosts == "FALSE") {
tempresolve = system->addrToName(elementinstancename) ? LOG, IGNORE ;
}

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