BGP snmp trap on XR OS

xzjleo2005 · ‎02-21-2013

We are trying to test the snmp trap on IOS-XR for BGP up down, but ASR didn't send out any traps when we brought down the BGP neighbour. When we tested the OSPF, it worked fine. I also tried to use command 'snmp test' to generate the test trap and I got following message, The version is 4.2. Any suggestions? Thanks.

RP/0/RSP0/CPU0:Feb 22 13:58:20.691 : test_trap[65889]: Debug init Done

RP/0/RSP0/CPU0:Feb 22 13:58:21.083 : test_trap[446]: Trap ID: 28

RP/0/RSP0/CPU0:Feb 22 13:58:21.084 : test_trap[446]: make_test_traps: input args 0x0 0x0 (null) (null)

Failed to format BGP Trap

RP/0/RSP0/CPU0:Feb 22 13:58:21.084 : test_trap[446]: get_first_bgp_peer_index: Getting first BGP Peer

RP/0/RSP0/CPU0:Feb 22 13:58:21.104 : test_trap[446]: get_first_bgp_peer_index: Failed to get BGP indices

Current config:

snmp-server host x.x.x.x traps version 2c xxxxxx

snmp-server community encrypted xxxx RO

snmp-server community encrypted yyyy RW

snmp-server traps rf

snmp-server traps bgp cbgp2

snmp-server traps bgp

snmp-server traps ospf state-change neighbor-state-change

snmp-server packetsize 1024

snmp-server trap-source MgmtEth0/RSP0/CPU0/0

snmp-server ifindex persist

Regards. Leo

Parthiv Shah · ‎02-21-2013

Hi

Please provide "show install active summary" and " show snmp" output. If router is in test lab than collect "debug snmp trap" and provide the log.

Thanks

Parthiv

xzjleo2005 · ‎02-21-2013

Hi, here you are, there are two traps have been sent out to two differnet hosts.

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2013.02.22 14:32:11 =~=~=~=~=~=~=~=~=~=~=~=

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#sh install act

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#sh install active sum

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#sh install active summary

Fri Feb 22 14:32:19.364 AEST

Active Packages:

disk0:asr9k-mini-p-4.2.0

disk0:asr9k-doc-p-4.2.0

disk0:asr9k-k9sec-p-4.2.0

disk0:asr9k-p-4.2.0.CSCtw65376-1.0.0

disk0:asr9k-mpls-p-4.2.0

disk0:asr9k-mgbl-p-4.2.0

disk0:asr9k-mcast-p-4.2.0

disk0:asr9k-p-4.2.0.CSCty91147-1.0.0

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#sh snmp

Fri Feb 22 14:32:24.587 AEST

Chassis:

0 SNMP packets input

0 Bad SNMP version errors

0 Unknown community name

0 Illegal operation for community name supplied

0 Encoding errors

0 Number of requested variables

0 Number of altered variables

0 Get-request PDUs

0 Get-next PDUs

0 Set-request PDUs

0 SNMP packets output

0 Too big errors (Maximum packet size 1024)

0 No such name errors

0 Bad values errors

0 General errors

0 Response PDUs

0 Trap PDUs

SNMP logging: Enabled

Logging to Notification host: x.x.x.x, udp-port: 162

Trap Statistics

---------------

Number of pkts in Trap Queue: 0

Maximum length of Trap Queue: 100

Number of pkts sent: 0

Number of pkts dropped: 0

Logging to Notification host: x.x.x.x, udp-port: 162

Trap Statistics

---------------

Number of pkts in Trap Queue: 0

Maximum length of Trap Queue: 100

Number of pkts sent: 0

Number of pkts dropped: 0

Inform Statistics

-----------------

Number of Informs sent: 0

Number of Informs retries: 0

Number of Informs pending: 0

Number of Informs dropped: 0

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#debug snmp trap

Fri Feb 22 14:33:01.524 AEST

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#RP/0/RSP0/CPU0:Feb 22 14:33:29.278 : exec[65888]: %SECURITY-login-6-AUTHEN_SUCCESS : Successfully authenticated user 'lxu1' from '172.31.170.197' on 'vty2'

LC/0/6/CPU0:Feb 22 14:33:41.082 : ifmgr[194]: %PKT_INFRA-LINK-5-CHANGED : Interface TenGigE0/6/0/2, changed state to Administratively Down

LC/0/6/CPU0:Feb 22 14:33:41.085 : bfd_agent[124]: %L2-BFD-6-ADJACENCY_DELETE : Adjacency to neighbor x.x.x.x on interface TenGigE0/6/0/2 was deleted

RP/0/RSP0/CPU0:Feb 22 14:33:41.093 : ospf[1011]: %ROUTING-OSPF-5-ADJCHG : Process 1, Nbr x.x.x.x on TenGigE0/6/0/2 in area 0 from FULL to DOWN, Neighbor Down: interface down or detached,vrf default vrfid 0x60000000

RP/0/RSP0/CPU0:Feb 22 14:33:41.102 : snmpd[1110]: t8 Queueing trap:ospfTrap.2.2 qlen:0

RP/0/RSP0/CPU0:Feb 22 14:33:41.104 : snmpd[1110]: t14 Processing trap ospfTrap.2.2

RP/0/RSP0/CPU0:Feb 22 14:33:41.106 : snmpd[1110]: t14 snmp_enqueue_trap:spawning a ping process (ping -R default -c 2 -t 0 x.x.x.x)

RP/0/RSP0/CPU0:Feb 22 14:33:41.109 : mpls_ldp[1042]: %ROUTING-LDP-5-SESSION_PROTECTION : Session hold up initiated for peer x.x.x.x:0

LC/0/6/CPU0:Feb 22 14:33:41.106 : bfd_agent[124]: %L2-BFD-6-SESSION_REMOVED : BFD session to neighbor x.x.x.x on interface TenGigE0/6/0/2 has been removed

RP/0/RSP0/CPU0:Feb 22 14:33:41.502 : snmpd[1110]: t14 Type escape sequence to abort.

RP/0/RSP0/CPU0:Feb 22 14:33:41.888 : snmpd[1110]: t14 Sending 2, 100-byte ICMP Echos to x.x.x.x, timeout is 0 seconds:

RP/0/RSP0/CPU0:Feb 22 14:33:41.996 : snmpd[1110]: t14 ..

RP/0/RSP0/CPU0:Feb 22 14:33:41.996 : snmpd[1110]: t14 Success rate is 0 percent (0/2)

RP/0/RSP0/CPU0:Feb 22 14:33:43.467 : snmpd[1110]: t14 Queueing packet to x.x.x.x-162 from 172.31.165.202-161 (VRF default)

RP/0/RSP0/CPU0:Feb 22 14:33:43.467 : snmpd[1110]: t14 TRAP-LOG: Failed: rc:0x4fdd9c00

RP/0/RSP0/CPU0:Feb 22 14:33:43.468 : snmpd[1110]: t14 snmp_enqueue_trap:spawning a ping process (ping -R default -c 2 -t 0 x.x.x.x)

RP/0/RSP0/CPU0:Feb 22 14:33:43.706 : snmpd[1110]: t14 Type escape sequence to abort.

RP/0/RSP0/CPU0:Feb 22 14:33:44.011 : snmpd[1110]: t14 Sending 2, 100-byte ICMP Echos to x.x.x.x, timeout is 0 seconds:

RP/0/RSP0/CPU0:Feb 22 14:33:44.118 : snmpd[1110]: t14 ..

RP/0/RSP0/CPU0:Feb 22 14:33:44.118 : snmpd[1110]: t14 Success rate is 0 percent (0/2)

RP/0/RSP0/CPU0:Feb 22 14:33:45.587 : snmpd[1110]: t14 Queueing packet to x.x.x.x-162 from 172.31.165.202-161 (VRF default)

RP/0/RSP0/CPU0:Feb 22 14:33:45.587 : snmpd[1110]: t14 TRAP-LOG: Failed: rc:0x4fdd9c00

RP/0/RSP0/CPU0:Feb 22 14:33:45.601 : snmpd[1110]: t1 SNMP trap Packet sent via UDP to x.x.x.x:162 from 172.31.165.202:161 (VRF default)

RP/0/RSP0/CPU0:Feb 22 14:33:45.839 : snmpd[1110]: t1 SNMP trap Packet sent via UDP to x.x.x.x:162 from 172.31.165.202:161 (VRF default)

RP/0/RSP0/CPU0:Feb 22 14:34:03.312 : tcp[424]: %IP-TCP_NSR-5-DISABLED : x.x.x.x:179 <-> x.x.x.x:16515:: NSR disabled for TCP connection because Retransmission threshold exceeded

RP/0/RSP0/CPU0:Feb 22 14:34:03.313 : bgp[1047]: %ROUTING-BGP-3-NBR_NSR_DISABLED : NSR disabled on neighbor x.x.x.x due to TCP retransmissions

RP/0/RSP1/CPU0:Feb 22 14:34:03.312 : bgp[1047]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor x.x.x.x on standby due to Peer closing down the session (VRF: default)

RP/0/RSP0/CPU0:Feb 22 14:34:03.316 : tcp[424]: %IP-TCP_NSR-5-DISABLED : x.x.x.x:25894 <-> x.x.x.x:179:: NSR disabled for TCP connection because Retransmission threshold exceeded

RP/0/RSP1/CPU0:Feb 22 14:34:03.317 : bgp[1047]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor x.x.x.x on standby due to Peer closing down the session (VRF: default)

RP/0/RSP0/CPU0:Feb 22 14:34:04.025 : tcp[424]: %IP-TCP_NSR-5-DISABLED : x.x.x.x:179 <-> x.x.x.x:51713:: NSR disabled for TCP connection because Retransmission threshold exceeded

RP/0/RSP1/CPU0:Feb 22 14:34:04.026 : bgp[1047]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor x.x.x.x on standby due to Peer closing down the session (VRF: default)

RP/0/RSP0/CPU0:Feb 22 14:34:04.029 : tcp[424]: %IP-TCP_NSR-5-DISABLED : x.x.x.x:179 <-> x.x.x.x:59304:: NSR disabled for TCP connection because Retransmission threshold exceeded

RP/0/RSP1/CPU0:Feb 22 14:34:04.032 : bgp[1047]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor x.x.x.x on standby due to Peer closing down the session (VRF: default)

RP/0/RSP0/CPU0:Feb 22 14:34:19.127 : bgp[1047]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor x.x.x.x Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 1/128, 1/66)

RP/0/RSP0/CPU0:Feb 22 14:34:20.120 : bgp[1047]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor x.x.x.x Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 25/65)

RP/0/RSP0/CPU0:Feb 22 14:34:20.162 : bgp[1047]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor x.x.x.x Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 25/65)

RP/0/RSP0/CPU0:Feb 22 14:34:27.792 : config[65889]: %MGBL-SYS-5-CONFIG_I : Configured from console by lxu1 on vty2 (172.31.170.197)

RP/0/RSP0/CPU0:Feb 22 14:34:29.501 : bgp[1047]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor x.x.x.x Down - BGP Notification sent, hold time expired (VRF: default; AFI/SAFI: 1/128, 1/66)

Parthiv Shah · ‎02-21-2013

Hi

Need the output of "show snmp" after the flap cause that will show whether trap generated? In your case currently it generated OSPF trap. So I would suggest to disable all other trap other than BGP and flap it and collect debug and "show snmp" output before and after the trigegr.

Also wait for few seconds after it actually goes down to collect debug and bringup the neighbor and check whetehr you get any trap.

Thanks

PArthiv

xzjleo2005 · ‎02-25-2013

Hi

I already tried that out, but ASR still didn't send out the trap for BGP up down. I opened a ticket in TAC, from their response, seems XR doesn't support generating snmp traps for BGP session under a vrf, do you know if this is the case?

Thanks. Leo

Parthiv Shah · ‎02-25-2013

Hi Leo

with 4.2.0, you should be able to get the trap. Could you try following :

Define the VRF to context mapping:

(config)# snmp-server vrf context

Define the community string to map to the VRF context:

(config)# snmp-server community RW

Define the mapping from community-string to VRF context:

(config)# snmp-server community-map context

Configure the trap destination for the community-string:

(config)# snmp-server host version 2c

Trap: For SNMPv1/v2c: The community string will be attached. By looking at the community string, your trap receiver needs to figure out the VRF.

For SNMPv3: The trap message will contain the "context string". By looking at the community string, your trap receiver needs to figure out the VRF.

For GET operation, you will provide the same information (community or context information) to identify the VRF.

xzjleo2005 · ‎02-25-2013

Hi

Following is the current config, two strange things here, once I added the commands you suggested, the snmp-server traps bgp command was gone. When I run the snmp test, there still no BGP traps had been generated. The second part is the output of debug snmp test-tarp and debug snmp trap.

snmp-server ifindex persist

snmp-server vrf det

context xxxxxx

!

snmp-server host x.x.x.x traps version 2c xxxxxx

snmp-server host y.y.y.y traps version 2c xxxxxx

snmp-server community encrypted 111D1C1603 RO

snmp-server community encrypted xxxxxx RW

snmp-server traps rf

snmp-server traps ospf state-change neighbor-state-change

snmp-server packetsize 1024

snmp-server trap-source MgmtEth0/RSP0/CPU0/0

snmp-server community-map xxxxxx context xxxxxx

RP/0/RSP0/CPU0:PE1-ASR9000-DC1#snmp test trap routing bgp state-change

Tue Feb 26 08:58:16.941 AEST

RP/0/RSP0/CPU0:Feb 26 08:58:17.022 : test_trap[65888]: Debug init Done

RP/0/RSP0/CPU0:Feb 26 08:58:17.411 : test_trap[446]: Trap ID: 28

RP/0/RSP0/CPU0:Feb 26 08:58:17.411 : test_trap[446]: make_test_traps: input args 0x0 0x0 (null) (null)

RP/0/RSP0/CPU0:Feb 26 08:58:17.411 : test_trap[446]: get_first_bgp_peer_index: Getting first BGP Peer

RP/0/RSP0/CPU0:Feb 26 08:58:17.424 : test_trap[446]: get_first_bgp_peer_index: First BGP bgp_peer=0x996BC701

RP/0/RSP0/CPU0:Feb 26 08:58:17.424 : test_trap[446]: make_test_trap_bgp: BGP Trap for peer_addr = 0x996BC701

RP/0/RSP0/CPU0:Feb 26 08:58:17.429 : test_trap[446]: make_test_trap_bgp: Sending BGP FSM State Change Trap

RP/0/RSP0/CPU0:Feb 26 08:58:17.430 : test_trap[446]: make_test_trap_bgp: Done BGP FSM State Change Trap

RP/0/RSP0/CPU0:Feb 26 08:58:17.430 : snmpd[1110]: t8 Queueing trap:ciscoMgmt.187.0.1 qlen:0

RP/0/RSP0/CPU0:Feb 26 08:58:17.431 : snmpd[1110]: t11 Processing trap ciscoMgmt.187.0.1

Parthiv Shah · ‎02-25-2013

Hi,

I am running 4.2.3 and seems like trap generated. also see the snm-server traps bgp commands in running config.

RP/0/RSP0/CPU0:PE2#show vrf mse_1001 detail

Mon Feb 25 14:58:29.027 PST

VRF mse_1001; RD 65002:1001; VPN ID not set

VRF mode: Regular

Description not set

Interfaces:

GigabitEthernet0/3/0/0.1001

Address family IPV4 Unicast

Import VPN route-target communities:

RT:65001:1001

Export VPN route-target communities:

RT:65001:1001

No import route policy

No export route policy

Address family IPV6 Unicast

Import VPN route-target communities:

RT:65001:1001

Export VPN route-target communities:

RT:65001:1001

No import route policy

No export route policy

RP/0/RSP0/CPU0:PE2#show ipv4 vrf mse_1001 interface brief

Mon Feb 25 14:59:16.154 PST

Interface IP-Address Status Protocol

GigabitEthernet0/3/0/0.1001 101.1.1.1 Up Up

RP/0/RSP0/CPU0:PE2#term mon

Mon Feb 25 14:59:33.803 PST

RP/0/RSP0/CPU0:PE2#conf t

Mon Feb 25 14:59:34.894 PST

RP/0/RSP0/CPU0:PE2(config)#int gi0/3/0/0.1001

RP/0/RSP0/CPU0:PE2(config-subif)#shut

RP/0/RSP0/CPU0:PE2(config-subif)#commit

Mon Feb 25 14:59:46.480 PST

LC/0/3/CPU0:Feb 25 14:59:46.617 : bfd_agent[124]: %L2-BFD-6-ADJACENCY_DELETE : Adjacency to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001 was deleted

RP/0/RSP0/CPU0:Feb 25 14:59:46.621 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 101.1.1.2 Down - Admin. shutdown (VRF: mse_1001)

RP/0/RSP1/CPU0:Feb 25 14:59:46.620 : bgp[1048]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor 101.1.1.2 on standby due to Admin. shutdown (VRF: mse_1001)

RP/0/RSP0/CPU0:Feb 25 14:59:46.626 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 1011:1:1::2 Down - Admin. shutdown (VRF: mse_1001)

RP/0/RSP1/CPU0:Feb 25 14:59:46.622 : bgp[1048]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor 1011:1:1::2 on standby due to Admin. shutdown (VRF: mse_1001)

LC/0/3/CPU0:Feb 25 14:59:46.719 : bfd_agent[124]: %L2-BFD-6-ADJACENCY_DELETE : Adjacency to neighbor 1011:1:1::2 on interface GigabitEthernet0/3/0/0.1001 was deleted

LC/0/3/CPU0:Feb 25 14:59:47.294 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_DOWN : BFD session to neighbor 1011:1:1::2 on interface GigabitEthernet0/3/0/0.1001 has gone down. Reason: Control timer expired

LC/0/3/CPU0:Feb 25 14:59:47.401 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_DOWN : BFD session to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001 has gone down. Reason: Nbor signalled down

RP/0/RSP0/CPU0:Feb 25 14:59:47.513 : config[65903]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000208' to view the changes.

RP/0/RSP0/CPU0:PE2(config-subif)#RP/0/RSP0/CPU0:Feb 25 14:59:47.633 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.2 qlen:0

RP/0/RSP0/CPU0:Feb 25 14:59:47.633 : snmpd[1112]: t8 Queueing trap:bgp.0.2 qlen:1

RP/0/RSP0/CPU0:Feb 25 14:59:47.634 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.8 qlen:2

RP/0/RSP0/CPU0:Feb 25 14:59:47.634 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.6 qlen:3

RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:4

RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:5

RP/0/RSP0/CPU0:Feb 25 14:59:47.635 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.8 qlen:6

RP/0/RSP0/CPU0:Feb 25 14:59:47.636 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.6 qlen:7

RP/0/RSP0/CPU0:Feb 25 14:59:47.636 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:8

RP/0/RSP0/CPU0:Feb 25 14:59:47.637 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.2

RP/0/RSP0/CPU0:Feb 25 14:59:47.637 : snmpd[1112]: t13 Processing trap bgp.0.2

RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.8

RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.6

RP/0/RSP0/CPU0:Feb 25 14:59:47.638 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.1

RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.8

RP/0/RSP0/CPU0:Feb 25 14:59:47.639 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.6

RP/0/RSP0/CPU0:Feb 25 14:59:47.640 : snmpd[1112]: t13 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:PE2(config-subif)#

RP/0/RSP0/CPU0:PE2(config-subif)#end

RP/0/RSP0/CPU0:Feb 25 14:59:55.901 : config[65903]: %MGBL-SYS-5-CONFIG_I : Configured from console by lab on vty0 (223.255.254.249)

RP/0/RSP0/CPU0:PE2#show snmp trap

Mon Feb 25 14:59:59.901 PST

TrapOID Number of Times

bgp.0.2 1

ciscoBgp4MIB.0.1 1

ciscoBgp4MIB.0.2 1

ciscoBgp4MIB.0.6 2

ciscoBgp4MIB.0.7 2

ciscoBgp4MIB.0.8 2

RP/0/RSP0/CPU0:PE2#show running-config snmp-server

Mon Feb 25 15:00:20.221 PST

snmp-server vrf mse_1001

context public

!

snmp-server community public RW

snmp-server traps bgp cbgp2

snmp-server traps bgp

snmp-server traps vrrp events

snmp-server ifindex persist

RP/0/RSP0/CPU0:PE2#conf t

Mon Feb 25 15:02:35.935 PST

RP/0/RSP0/CPU0:PE2(config)#int gi0/3/0/0.1001

RP/0/RSP0/CPU0:PE2(config-subif)#no shut

RP/0/RSP0/CPU0:PE2(config-subif)#commit

Mon Feb 25 15:02:42.609 PST

RP/0/RSP0/CPU0:Feb 25 15:02:43.369 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 101.1.1.2 Up (VRF: mse_1001)

RP/0/RSP0/CPU0:Feb 25 15:02:43.606 : config[65903]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'lab'. Use 'show configuration commit changes 1000000209' to view the changes.

RP/0/RSP0/CPU0:PE2(config-subif)#LC/0/3/CPU0:Feb 25 15:02:44.223 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_UP : BFD session to neighbor 101.1.1.2 on interface GigabitEthernet0/3/0/0.1001 is up

RP/0/RSP0/CPU0:Feb 25 15:02:44.286 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:0

RP/0/RSP0/CPU0:Feb 25 15:02:44.286 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:1

RP/0/RSP0/CPU0:Feb 25 15:02:44.287 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:2

RP/0/RSP0/CPU0:Feb 25 15:02:44.287 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:3

RP/0/RSP0/CPU0:Feb 25 15:02:44.288 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:4

RP/0/RSP0/CPU0:Feb 25 15:02:44.289 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:5

RP/0/RSP0/CPU0:Feb 25 15:02:44.289 : snmpd[1112]: t8 Queueing trap:bgp.0.1 qlen:6

RP/0/RSP0/CPU0:Feb 25 15:02:44.290 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.5 qlen:7

RP/0/RSP0/CPU0:Feb 25 15:02:44.291 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.1 qlen:8

RP/0/RSP0/CPU0:Feb 25 15:02:44.291 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:9

RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1

RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:Feb 25 15:02:44.292 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1

RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1

RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:Feb 25 15:02:44.293 : snmpd[1112]: t10 Processing trap bgp.0.1

RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.5

RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.1

RP/0/RSP0/CPU0:Feb 25 15:02:44.294 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:PE2(config-subif)#

RP/0/RSP0/CPU0:PE2(config-subif)#end

RP/0/RSP0/CPU0:Feb 25 15:02:48.825 : config[65903]: %MGBL-SYS-5-CONFIG_I : Configured from console by lab on vty0 (223.255.254.249)

RP/0/RSP0/CPU0:PE2#conf tRP/0/RSP0/CPU0:Feb 25 15:02:49.418 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:0

RP/0/RSP0/CPU0:Feb 25 15:02:49.419 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:1

RP/0/RSP0/CPU0:Feb 25 15:02:49.420 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:Feb 25 15:02:49.421 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

show running-config snmp-server RP/0/RSP0/CPU0:Feb 25 15:02:50.510 : bgp[1048]: %ROUTING-BGP-5-ADJCHANGE : neighbor 1011:1:1::2 Up (VRF: mse_1001)

show snmp trapLC/0/3/CPU0:Feb 25 15:02:51.046 : bfd_agent[124]: %L2-BFD-6-SESSION_STATE_UP : BFD session to neighbor 1011:1:1::2 on interface GigabitEthernet0/3/0/0.1001 is up

RP/0/RSP0/CPU0:Feb 25 15:02:51.516 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:0

RP/0/RSP0/CPU0:Feb 25 15:02:51.516 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.5 qlen:1

RP/0/RSP0/CPU0:Feb 25 15:02:51.517 : snmpd[1112]: t8 Queueing trap:ciscoBgp4MIB.0.7 qlen:2

RP/0/RSP0/CPU0:Feb 25 15:02:51.519 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

RP/0/RSP0/CPU0:Feb 25 15:02:51.520 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.5

RP/0/RSP0/CPU0:Feb 25 15:02:51.520 : snmpd[1112]: t10 Processing trap ciscoBgp4MIB.0.7

Mon Feb 25 15:02:54.118 PST

TrapOID Number of Times

bgp.0.1 1

bgp.0.2 1

ciscoBgp4MIB.0.1 5

ciscoBgp4MIB.0.2 1

ciscoBgp4MIB.0.5 2

ciscoBgp4MIB.0.6 2

ciscoBgp4MIB.0.7 10

ciscoBgp4MIB.0.8 2

RP/0/RSP0/CPU0:PE2#

Thanks

Parthiv

xzjleo2005 · ‎02-25-2013

Hi

From your debug, it only showed trap has been queueing, but it has not been sent out. From my snmp test trap debug, I could see it's queueing, but it hadn't been sent out at the end.

Thanks. Leo

Parthiv Shah · ‎02-25-2013

Hi Leo

There was no host configured for trap receiver and reachable but I was seeing the trap queued. Do you have server reachable under that VRF else you might need to leak the route from that VRF to server.

Thanks

Parthiv

xzjleo2005 · ‎02-26-2013

Hi Parthiv,

The ASR can reach the SNMP server, if I tested the OSPF trap, it will be sent out.

Thanks. Leo