SNMP inform request source-interface

Unanswered Question
Dec 12th, 2008

Instead of using SNMP TRAPS I would like to use INFORM requests. When I receive TRAPS everything is working correcty. When I receive INFORM requests, the source interface is reported wrong.

My config:

snmp-server trap-source Loopback0

snmp-server source-interface informs Loopback0

snmp-server enable traps snmp linkup

snmp-server enable traps config

snmp-server host inform version 2c public

snmp-server host version 2c public

The TRAPS report their source address as Loopback0 but the INFORMS report their source address as FastEthernet0.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Joe Clarke Fri, 12/12/2008 - 14:03

Never mind, I see you already had it. This could be a bug. What version of IOS is this?

Joe Clarke Fri, 12/12/2008 - 14:20

I can reproduce in 12.4(22)T, and I cannot find an existing bug on this. I recommend you open a TAC service request so a new bug can be filed.

marko.keca Fri, 01/21/2011 - 03:54


we are also migrating from traps to informs and I can see that this source-interface issue is still open. I can confirm it is happening on Cisco 7609-S with IOS: 12.2.(33)SRD5, SRD6 and SRE2.

In bug toolkit I can see it opened for 6500 under CSCtc43231 ( but there is no any SR release under affected versions.

If anyone knows any workaround, I would appreciate it a lot.

Thanks in advance!

Config T Fri, 01/21/2011 - 07:58

I never did find a work around for this. I gave up on using informs.

Joe Clarke Fri, 01/21/2011 - 08:16

Marko, I think the SR train needs to be added to this bug.  If you have the ability to open a TAC service request, I recommend you do so and the required release train can be added to the list of affected versions.

marko.keca Fri, 01/21/2011 - 12:10

Thanks guys for quick responses!


Thanks for sharing info. Unfortunately, we have to use informs, so I need to find a way to configure it with good source. I'll post solution if I find any.


Thanks for suggestion. I already opened TAC case for affected versions. I'll inform you on the conclusion of the case. Currently I'm collecting all relevant output, debugs and packet captures for developers.



This Discussion