Differentiate between M&R APG trap severities sent to the Smarts SAM Server?
search cancel

Differentiate between M&R APG trap severities sent to the Smarts SAM Server?

book

Article ID: 327682

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

This article explains about the M&R APG trap severities sent to the Smarts SAM Server.

  • How can we differentiate between M&R APG trap severities sent to the Smarts Service Assurance Manager (Smarts SAM) Server?
  • When sending traps from M&R APG to Smarts SAM server, only severity "2 - notify" and "4 - clear" are recognized

 

Environment

M&R - 7.x

Cause

Without the code modification in the following Fix statement, M&R APG sent to Smarts SAM server will recognize only severity "2 - notify" and "4 - clear".

Resolution

The following code example from the Smarts trap_mgr.conf configuration file shows how to configure Smarts SAM to recognize all M&R APG trap severities:

# Repeater Trap Defintions

# ------------------------

BEGIN_TRAP .1.3.6.1.2.1.22.* 6 1

ClassName: Host

InstanceName: $SYS$

EventName: rptrHealth

Severity: 1

EventText: Repeater Operational Status = $V1$

Map: {

V1

1 = other

2 = ok

3 = rptrFailure

4 = groupFailure

5 = portFailure

6 = generalFailure

}

Expiration: 600

State: NOTIFY

EventType: MOMENTARY

END_TRAP