Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

CiscoWorks DFM SNMP trap forwarding

I have defined SNMP trap forwarding in CiscoWorks to an external trap server. Traps are received by the CiscoWorks server from the nodes, but not forwarded to the external server.

I have verified this with windump on the server.

Coonfigured under:

DFM-Notification Services-SNMP trap forwardning.

6 REPLIES
Cisco Employee

Re: CiscoWorks DFM SNMP trap forwarding

What you have configured is a trap notification. This means that all DFM events that match your given notification subscription, will be converted to traps, and sent to your other NMS. This does not mean all traps received by DFM will be forwarded to your other NMS.

If you want to do true trap forwarding, you need to configure this under DFM > Configuration > Other Configuration > SNMP Trap Forwarding. You must also make sure DFM is configured to listen for traps itself under DFM > Configuration > Other Configuration > SNMP Trap Receiving (set this to 162 for the default trap reception port).

New Member

Re: CiscoWorks DFM SNMP trap forwarding

Hi Joe,

Thank you for your response. I have done the configuration and made sure that the port is 162 in snmp trap receiving. I did a capture using wireshark and filter snmp messages on port 162 but it capture nothing. It seems that DFM didn't forword anything.

BR,

Zied

Cisco Employee

Re: CiscoWorks DFM SNMP trap forwarding

Where did you do the packet capture?  Are you sure the traps are making it to DFM from the devices?

New Member

CiscoWorks DFM SNMP trap forwarding

Hi Joseph,

Our client is experiencing quite the same scenario.They have integrated Clarity NMS to Ciscoworks LMS 3.2.1. So far they are receiving raw alarms/snmp traps but it lacks information of the originating device. Kindly see sample raw alarms below:

2420: 2011-11-25 12:10:46 Received trap ==> Received SNMPv1 Trap

Community=ciscoworks

Enterprise=1.3.6.1.6.3.1.1.5

Generip trap type=2

Specific Trap Type=0

Trap From=10.220.10.1

Trap ID=1.3.6.1.6.3.1.1.5.2

Trap Time=-1436283373

1.3.6.1.2.1.2.2.1.1.83=83

1.3.6.1.2.1.2.2.1.2.83=GigabitEthernet1/40

1.3.6.1.2.1.2.2.1.3.83=6

1.3.6.1.4.1.9.2.2.1.1.20.83=Lost Carrier

EndTrap

10933: 2011-11-24 11:57:53 Received trap ==> Received SNMPv1 Trap

Community=ciscoworks

Enterprise=1.3.6.1.4.1.9.1.291

Generip trap type=2

Specific Trap Type=0

Trap From=10.220.10.1

Trap ID=1.3.6.1.4.1.9.1.291.2

Trap Time=1628056965

1.3.6.1.2.1.2.2.1.1.8=8

1.3.6.1.2.1.2.2.1.2.8=E1 0/0/0

1.3.6.1.2.1.2.2.1.3.8=18

EndTrap

--

As you can see, those raw alarms doesn’t contain any information about the originating equipment or the physical card, port related information where those alarms were generated. Instead those alarms receiving as NMS level alarms.

How do we resolve this so that the inventory of the equipment would be part of the trap to be received by Clarity from Ciscoworks.

Cisco Employee

CiscoWorks DFM SNMP trap forwarding

This is not the issue being described in this thread.  Please start a new thread for your issue.

New Member

CiscoWorks DFM SNMP trap forwarding

Ok thanks, I have already posted a new thread. Hope you could help us.

961
Views
0
Helpful
6
Replies