Cisco Cisco ASR 5700 トラブルシューティングガイド
ASR 5000 Series: "BGPPeerSessionDown" Traps
in Less than Hold Timer Period After Broken
Connectivity Event Occurs
in Less than Hold Timer Period After Broken
Connectivity Event Occurs
Document ID: 119157
Contributed by Dave Damerjian, Cisco TAC Engineer.
Jul 31, 2015
Contents
Introduction
Problem
Solution
Question
Answer
Related Information
Problem
Solution
Question
Answer
Related Information
Introduction
This document explains the timing involved when a Border Gateway Protocol (BGP) peer is marked down
with BGPPeerSessionDown trap with respect to the timing of the event that triggered it. The time it takes for
the peer to get marked down is a value less than the time of the hold timer. This particular issue was reported
on an Cisco Aggregation Services Router (ASR) 5000 but would equally apply to an ASR 5500.
with BGPPeerSessionDown trap with respect to the timing of the event that triggered it. The time it takes for
the peer to get marked down is a value less than the time of the hold timer. This particular issue was reported
on an Cisco Aggregation Services Router (ASR) 5000 but would equally apply to an ASR 5500.
Problem
In this particular case, there was an npumgr process restart on the Demux Packet Switching Card (PSC) 1 on
ASR 5000 due to Micro Engine issue, which is not that uncommon of a transient issue (there is no need for
RMA):
ASR 5000 due to Micro Engine issue, which is not that uncommon of a transient issue (there is no need for
RMA):
2015-Jun-13+13:51:44.198 [sft 58000 info] [1/0/4255 <sft:100>
sft_monitor.c:115]
[software internal system critical-info syslog] SFT : Forced 1 times RX
packet at slot 1, cpu 0, inst 100, inflight packets 30
2015-Jun-13+13:51:45.306 [sft 58000 info] [1/0/4255 <sft:100>
sft_monitor.c:115]
[software internal system critical-info syslog] SFT : Forced 81 times RX
packet at slot 1, cpu 0, inst 100, inflight packets 110
2015-Jun-13+13:51:45.205 [sft 58000 info] [1/0/4255 <sft:100>
sft_monitor.c:115]
[software internal system critical-info syslog] SFT : Forced 71 times RX
packet at slot 1, cpu 0, inst 100, inflight packets 100
Sat Jun 13 13:51:45 2015 Internal trap notification 73 (ManagerFailure)
facility npumgr instance 1 card 1 cpu 1
2015-Jun-13+13:51:45.335 [npuctrl 16019 error] [8/0/4729 <npuctrl:0>
rl_sf_handler.c:2570] [software internal system syslog] SF CTRL:
monitoring_recovery: