cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1636
Views
0
Helpful
2
Replies

SNMP Trap issue

Rakloman
Beginner
Beginner

Hi,

After upgrade to 5.1.3 on a ASR9001 router we are receiving these messages.

RP/0/RSP0/CPU0:Jan 20 07:06:41.800 : snmpd[1128]: %SNMP-SNMP-3-INTERNAL : Snmp Trap source issue : Using best possible Src IPV6 address for SNMP Traps. Failed to get the IPv6 address of :(Check the Interface state):Loopback0

RP/0/RSP0/CPU0:Jan 20 16:53:34.179 : snmpd[1128]: %SNMP-SNMP-3-INTERNAL : Snmp Trap source issue : Using best possible Src IPV6 address for SNMP Traps. Failed to get the IPv6 address of :(Check the Interface state):Loopback0

They appear only once during boot-time. On the previous IOS XR version (4.3.1) they weren't present.

There is no IPv6 config on the router. Otherwise the router is sending traps and NMS is receiving them without problems

SNMP config:

#sh run snmp-server
Thu Jan 22 16:03:55.478 CET
snmp-server vrf default
 host 10.10.5.17 traps version 2c BLA
!
snmp-server host 10.10.5.17 traps version 2c BLA
snmp-server community TEST RO SystemOwner
snmp-server community BLA RO SystemOwner
snmp-server traps bgp
snmp-server traps hsrp
snmp-server traps snmp linkup
snmp-server traps snmp linkdown
snmp-server traps snmp coldstart
snmp-server traps snmp warmstart
snmp-server traps snmp authentication
snmp-server traps mpls ldp up
snmp-server traps mpls ldp down
snmp-server traps ospf lsa lsa-originate
snmp-server traps ospf state-change if-state-change
snmp-server traps ospf state-change neighbor-state-change
snmp-server traps fru-ctrl
snmp-server location TEST
snmp-server trap-source Loopback0
snmp-server ifmib ifalias long
snmp-server ifindex persist
snmp-server trap link ietf

#sh run int loopback 0
Thu Jan 22 15:58:41.744 CET
interface Loopback0
 ipv4 address 10.10.10.183 255.255.255.255
!

These are the "debug snmp trap" messages. Are the below failed messages somehow related to this?

RP/0/RSP0/CPU0:Jan 21 10:33:06.983 : snmpd[1128]: t7 Queueing trap:ciscoBgp4MIB.0.2 qlen:0

RP/0/RSP0/CPU0:Jan 21 10:33:06.983 : snmpd[1128]: t11 Processing trap ciscoBgp4MIB.0.2

RP/0/RSP0/CPU0:Jan 21 10:33:06.983 : snmpd[1128]: t7 Queueing trap:bgp.0.2 qlen:0

RP/0/RSP0/CPU0:Jan 21 10:33:06.983 : snmpd[1128]: t11 Queueing packet to 10.10.5.17-162 from 10.10.10.183-161 (VRF default)

RP/0/RSP0/CPU0:Jan 21 10:33:06.984 : snmpd[1128]: t11 TRAP-LOG: Failed: rc:0x4fdd9c00

RP/0/RSP0/CPU0:Jan 21 10:33:06.984 : snmpd[1128]: t11 Queueing packet to 10.10.5.17-162 from 10.10.10.183-161 (VRF default)

RP/0/RSP0/CPU0:Jan 21 10:33:06.984 : snmpd[1128]: t11 TRAP-LOG: Failed: rc:0x4fdd9c00

RP/0/RSP0/CPU0:Jan 21 10:33:06.984 : snmpd[1128]: t11 Processing trap bgp.0.2

RP/0/RSP0/CPU0:Jan 21 10:33:06.984 : snmpd[1128]: t7 Queueing trap:ciscoBgp4MIB.0.1 qlen:0

RP/0/RSP0/CPU0:Jan 21 10:33:06.984 : snmpd[1128]: t11 Queueing packet to 10.10.5.17-162 from 10.10.10.183-161 (VRF default)

RP/0/RSP0/CPU0:Jan 21 10:33:06.985 : snmpd[1128]: t11 Queueing packet to 10.10.5.17-162 from 10.10.10.183-161 (VRF default)

RP/0/RSP0/CPU0:Jan 21 10:33:06.984 : snmpd[1128]: t11 TRAP-LOG: Failed: rc:0x4fdd9c00

RP/0/RSP0/CPU0:Jan 21 10:33:06.985 : snmpd[1128]: t11 TRAP-LOG: Failed: rc:0x4fdd9c00

RP/0/RSP0/CPU0:Jan 21 10:33:06.985 : snmpd[1128]: t11 Queueing packet to 10.10.5.17-162 from 10.10.10.183-161 (VRF default)

RP/0/RSP0/CPU0:Jan 21 10:33:06.985 : snmpd[1128]: t11 TRAP-LOG: Failed: rc:0x4fdd9c00

RP/0/RSP0/CPU0:Jan 21 10:33:06.985 : snmpd[1128]: t11 Processing trap ciscoBgp4MIB.0.1

RP/0/RSP0/CPU0:Jan 21 10:33:06.985 : snmpd[1128]: t11 Queueing packet to 10.10.5.17-162 from 10.10.10.183-161 (VRF default)

RP/0/RSP0/CPU0:Jan 21 10:33:06.985 : snmpd[1128]: t11 TRAP-LOG: Failed: rc:0x4fdd9c00

 

Thank you and best regards,

Karlo.

2 Replies 2

xthuijs
Cisco Employee
Cisco Employee

hi karlo,

You're seeing that syslog because the loopback0 interface doesn't have an ipv6 address.  There was an enhancement made to snmp w.r.t to cpu usage and ipv6 support. The recommendation is to eliminate that syslog, make sure the interface you've configured as "trap-source" under snmp has both a v4/v6 IP address. Eventhough you may not be using v6 transport.

cheers!

xander

 
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers