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

Products

• VMware

Issue/Introduction

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

Environment

VMware Smart Assurance - SMARTS

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