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 SAM: How do you set up aggregate notifications for traps? (325383)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 4288Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

How do you set up Smarts SAM to subscribe to aggregate notifications for traps?

How can you aggregate specific traps into a single Notification in Smarts SAM?

Traps are currently configured to create independent notifications

Resolution

The following sections of this Fix statement explain how to set up a Smarts SAM subscription to aggregate notifications for traps and how to aggregate specific traps into a single Notification in Smarts SAM.

Setting up a Smarts SAM subscription to aggregate notifications
By default, SAM does not subscribe to aggregated component notifications/events. This can be changed by modifying the appropriate configuration file. The file used to configure aggregate notifications for traps is the ics dxa configuration file which is used to connect Smarts SAM to AMPM. The default file name for this configuration file is dxa-conn-perf.conf. In this configuration file, the following entry is configured by default:

sub     NetworkAdapter_Performance::.*::.*/e

To configure Smarts SAM to subscribe to aggregated events, change this entry to the following:

sub     NetworkAdapter_Performance::.*::.*/ae

With this entry configured, SAM will subscribe to aggregated events. The aggregate notifications will be called Resource Exception notifications and will have a tab called Aggregates.

Using the Aggregate property to aggregate notifications for specific traps
You can set up aggregate notifications for specific traps in Smarts SAM by using the Aggregate property for each trap.  The three traps in the following example are all related to Environmental conditions on a router (VoltageWarning, TemperatureWarning, and FanWarning).  Each of the trap definitions have been changed to include the Aggregate property. If any of these traps are received, the notification will have the EventName of DegradedEnv. If the same system sends other environmental traps below, they will be added to the Aggregates tab of the DegradedEnv notification.

BEGIN_TRAP .1.3.6.1.4.1.9.9.13.3.* 6 2
ClassName:             Router
InstanceName:       Voltage-$SYS$
EventName:            VoltageWarning
EventText:             Voltage out of range on $SYS$
EventType:            DURABLE
Expiration:             7200
Severity:                2
State:                     NOTIFY
Aggregate: {
EventName: DegradedEnv
ElementName: $SYS$
}
END_TRAP

BEGIN_TRAP .1.3.6.1.4.1.9.9.13.3.* 6 3
ClassName:             Router
InstanceName:       Temperature-$SYS$
EventName:            TemperatureWarning
EventText:             Temperature out of range on $SYS$
EventType:            DURABLE
Expiration:             7200
Severity:                2
State:                     NOTIFY
Aggregate: {
EventName: DegradedEnv
ElementName: $SYS$
}
END_TRAP

BEGIN_TRAP .1.3.6.1.4.1.9.9.13.3.* 6 4
ClassName:             Router
InstanceName:       Fan-$SYS$
EventName:            FanWarning
EventText:             Fan out of range on $SYS$
EventType:            DURABLE
Expiration:             7200
Severity:               2
State:                   NOTIFY
Aggregate: {
EventName: DegradedEnv
ElementName: $SYS$
}
END_TRAP

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