Spectrum & Nimsoft Integration issue - Nimsoft Traps not being decoded.

book

Article ID: 35066

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

Symptoms


Customer receiving Nimsoft traps in Spectrum, however, those are not being recognized (unknown).

An example of a trap not being decoded is as fllows

Unknown alert received from device server02-ns of type NimsoftHostServer. Device Time 0+00:00:00. (Trap type 1.3.6.1.4.1.4055.1.6.0) Trap var bind data: OID: 1.3.6.1.2.1.1.1.0 Value: NimBUS/SNMP gateway OID: 1.3.6.1.4.1.4055.1.1.0 Value: 0 OID: 1.3.6.1.4.1.4055.1.2.0 Value: 1.1.1 OID: 1.3.6.1.4.1.4055.1.3.0 Value: Fetched CPU data ok OID: 1.3.6.1.4.1.4055.1.4.0 Value: cpu/GetCpuInfo OID: 1.3.6.1.4.1.4055.1.5.0 Value: cdm OID: 1.3.6.1.4.1.4055.1.8.0 Value: server02-nshub OID: 1.3.6.1.4.1.4055.1.9.0 Value: 192.168.1.242 OID: 1.3.6.1.4.1.4055.1.10.0 Value: 1421932010 OID: 1.3.6.1.4.1.4055.1.11.0 Value: 0 OID: 1.3.6.1.4.1.4055.1.12.0 Value: EY84287665-00004 OID: 1.3.6.1.4.1.4055.1.13.0 Value: server02-ns OID: 1.3.6.1.4.1.4055.1.14.0 Value: server02-nsdom





Solution


The previous unknown alert message was showing a 6 0 trap having been
received, however Spectrum is configured to process 6 2 to 6 7 traps, so the mapping Tab
needs to be configured accordingly


Ex.

Trap Mapping
Default: 5
Clear: 7 Minor: 2
Information: 5 Major: 3
Warning: 6 Critical: 4

Spectrum is configured for
1.3.6.1.4.1.4055.1.6.2
1.3.6.1.4.1.4055.1.6.3
1.3.6.1.4.1.4055.1.6.4
1.3.6.1.4.1.4055.1.6.5
1.3.6.1.4.1.4055.1.6.6
1.3.6.1.4.1.4055.1.6.7
?

Environment

Release:
Component: UIMSGW