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 SAM: How do the settings QUEUE_LIMIT_SECONDS and QUEUE_LIMIT_MEGS work in trap adapter/exploder configuration file (trapd.conf)? (317389)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

How do the settings QUEUE_LIMIT_SECONDS and QUEUE_LIMIT_MEGS work in the Smarts SAM trap adapter/exploder configuration file (trapd.conf?)

Please note:  These settings apply only to Smarts SAM trap adapter/exploder configuration.  The trapd.conf parameters do not apply to the IP Trap Receiver Process. Hence the IP domain can be subject to trap floods if the Trap Exploder or other process is sending an excessive number of traps to the IP domain.

The following sections explain how the QUEUE_LIMIT_SECONDS and QUEUE_LIMIT_MEGS function in the Smarts SAM trap adapter/exploder configuration file (trapd.conf).

QUEUE_LIMIT_SECONDS:

# Limits the time that a trap can spend in the internal
# trap queue. This limit is even less exact than the
# size limit above. In general, it's advisable to
# specify both. When the limit is reached, some traps
# will be discarded. The default value is 0, which
# means no limit.

The trap handling code tracks how many traps a second it is removing from the queue and divides the current queue size by the traps/second to estimate how long it would take to drain the queue. Then it compares that value to QUEUE_LIMIT_SECONDS. If the value is over that limit, then it will identify trap sources to discard based on the number of traps they are generating. The reason for this is that it has often been found in trap flood cases that one or a couple of devices are generating enormous numbers of traps. So, rather than discarding traps from all devices, it is better to discard the traps from the devices generating lots of traps and let the others through.

It is possible that a well behaved device that only sends out a trap once in a while will have that trap processed beyond the QUEUE_LIMIT_SECONDS time if a flood of traps from another device is causing it to discard traps. The trap, if it is not selected to be discarded, should make it through the queue at or around the time of QUEUE_LIMIT_SECONDS after it arrives in the queue. This is assuming the rate of traps remains the same and the drainage/drop rate remains the same. This also depends on the overall server workload. Overall, the QUEUE_LIMIT_SECONDS setting is only a rough boundary of the maximum queuing time, but it is unlikely that a trap will stay in the queue significantly longer than the QUEUE_LIMIT_SECONDS setting. It should only be a few seconds longer at most.

QUEUE_LIMIT_MEGS

# Limits the size of internal trap queue to the
# stated size. The limit is not exact - the queue
# may grow slightly larger than that. When the limit
# is reached, some traps will be discarded. The
# default value is 0, which means no limit.

If it is over this limit, then the code will identify trap sources to discard based on the number of traps they are generating. Sometimes in trap flood cases, certain devices generate significantly large numbers of traps compared to others.  Rather than discarding traps from all devices, it is better to discard the traps from the "chatty" devices while still letting the others through.

If the server platform does not have enough processing power (for example,  if the processing rate, traps/sec, falls below 100), then the QUEUE_LIMIT_SECONDS algorithm will not be applied and effectively QUEUE_LIMIT_SECONDS defaults to 0. Therefore, if QUEUE_LIMIT_MEGS is not used, then the queue could eventually grow to an infinite size and much longer queuing delays may be seen. The algorithm for QUEUE_LIMIT_MEGS is always applied regardless.

It is recommended that both QUEUE_LIMIT_MEGS and QUEUE_LIMIT_SECONDS be used together, as this will work best in most situations.

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