SNMP Traps not forwarded by HPSIM server

[Köhne]

Certain SNMP traps are not forwarded by HPSIM server! Why?

I have checked:

- Mib loaded

- Enable Trap Handling=YES

- system managed

- traps shows up in HPSIM event view

- traps are shown in task results at automated event handling.

- snmp trap receiver is up ad running and processing same traps from different HPSIM server!

- HPSIM server sends forwards other traps

[Tushar Bajpai]

Can you share like which trap ?

[Köhne]

It is our own trap.

Here is the MIB file:

RWE-MIB DEFINITIONS ::= BEGIN

-- $Log: rwe.mib,v $

-- Revision 1.1  2011/08/08 10:46:08  r994463

-- Initial revision

--

        IMPORTS

                enterprises    FROM RFC1155-SMI

                OBJECT-TYPE    FROM RFC-1212

                DisplayString  FROM RFC1213-MIB

                TRAP-TYPE      FROM RFC-1215;

-- ******************************************************************

-- RWE MIB for Heartbeat Events

-- ******************************************************************

rwe     OBJECT IDENTIFIER ::= { enterprises 4482 }

rweHeartbeatScriptVersion OBJECT-TYPE

        SYNTAX DisplayString (SIZE (3..17))

        ACCESS not-accessible

        STATUS mandatory

        DESCRIPTION

        "Version of Heartbeat script."

        ::= { rwe 1 }

rweHeartbeat TRAP-TYPE

        ENTERPRISE rwe

        VARIABLES  { rweHeartbeatScriptVersion }

        DESCRIPTION

        "Heartbeat"

        ::= 1

rweHPSIMHeartbeat TRAP-TYPE

        ENTERPRISE rwe

        VARIABLES  { rweHeartbeatScriptVersion }

        DESCRIPTION

        "Heartbeat for HPSIM2TEC"

        ::= 2

END

[Köhne]

Here is the content of the cfg file (mcompile):

#-MIBFILE: rwe.mib

RWE-MIB DEFINITIONS ::= BEGIN

DisplayString ::=         OCTET STRING

PhysAddress ::=         OCTET STRING

rwe OBJECT IDENTIFIER ::= { enterprises 4482 }

rweHeartbeatScriptVersion OBJECT-TYPE         SYNTAX DisplayString (SIZE(3..17))         ACCESS read-only         STATUS mandatory         DESCRIPTION "Version of Heartbeat script."         ::= { rwe 1 }

rweHeartbeat TRAP-TYPE         ENTERPRISE rwe         VARIABLES { rweHeartbeatScriptVersion } DESCRIPTION "Heartbeat"         ::= 1

rweHPSIMHeartbeat TRAP-TYPE         ENTERPRISE rwe         VARIABLES { rweHeartbeatScriptVersion } DESCRIPTION "Heartbeat for HPSIM2TEC"         ::= 2

END

[Köhne]

The RWE events are correctly shown within HPSIM:

Event Details: (SNMP) rweHPSIMHeartbeat

Event Identification and Details

Event Severity   Informational Cleared Status Cleared Event Source s010a0035 Associated System s010a0035 Associated System Status   Normal Event Time Mittwoch, 15.05.2013, 11:13 MESZ Description Heartbeat for HPSIM2TEC Event Category Status Events Assignee    Comments   

Trap Details

Variable Description Value NO DATA  Version of Heartbeat script. 1.0 

Mib Information The associated MIB File Name for this trap is rwe.mib and the MIB identifier RWE-MIB 

They also trigger the "Automatic Event Handling" task which forwrds the traps to our SNMP receiver. The same task works for other HPSIM traps!!!

Task instance results 

 Job status:    Complete   Start time:   5/15/13 11:13 AM  JobID:  179983_s010a0035.group.rwe.com   End time:   5/15/13 11:13 AM  Run by:  GROUP\srvsimpw   Duration:   0s 

Summary status:   8  Complete  

Click a row to select and view action results.   Total: 8  Target NameEvent TypeDescriptionActionStatus Target Name Event Type Description Action Status        s010a0035 Status Events (SNMP) rweHPSIMHeartbeat Forward as SNMP trap  Complete  s010a0035 Status Events (SNMP) rweHPSIMHeartbeat Clear event

[Köhne]

Apparently all client traps are not forwarded, HPSIM server traps (e.g. "System not available") are forwarded.

Very strange problem!

[eberk]

Hi,

Has anyone had any luck in finding a resolution for this issue? I am having the exact same problem on one of our systems. All System Insight Manager traps are forwarded to the external system, but traps from all other MIBs are not forwarded (but do appear in HP-SIM event list)

I would appreciate any updates on any actions taken by others to resolve this issue.

Thanks!