{"id":24517,"date":"2026-11-16T11:47:07","date_gmt":"2026-11-16T03:47:07","guid":{"rendered":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html"},"modified":"2026-11-16T11:47:07","modified_gmt":"2026-11-16T03:47:07","slug":"how-to-check-bgp-flapping-in-cisco","status":"publish","type":"post","link":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html","title":{"rendered":"How to Check BGP Flapping in Cisco"},"content":{"rendered":"<p>Border Gateway Protocol (BGP) instability is one of the most critical issues a network engineer can face. When BGP flaps, it consumes router CPU cycles, invalidates forwarding tables, and introduces severe packet loss and routing black holes across autonomous systems. <\/p>\n<p>Diagnosing BGP flapping on Cisco IOS, IOS-XE, and NX-OS devices requires recognizing a fundamental distinction: <strong>BGP route flapping<\/strong> versus <strong>BGP neighbor (session) flapping<\/strong>. Route flapping occurs when specific prefixes are repeatedly announced and withdrawn while the underlying peer session remains up. Neighbor flapping occurs when the TCP port 179 peering session itself repeatedly transitions between the <code>Established<\/code> and down states (<code>Idle<\/code>, <code>Active<\/code>, or <code>Connect<\/code>). <\/p>\n<p>This guide walks through how to verify flapping prefixes using route flap statistics, analyze syslog notifications and reset codes, troubleshoot session drops step by step, configure flap dampening, automate proactive monitoring, and collect diagnostic data according to Cisco Technical Assistance Center (TAC) standards.<\/p>\n<hr \/>\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_17 counter-hierarchy counter-decimal ez-toc-light-blue\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" style=\"display: none;\"><i class=\"ez-toc-glyphicon ez-toc-icon-toggle\"><\/i><\/a><\/span><\/div>\n<nav><ul class=\"ez-toc-list ez-toc-list-level-1\"><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Checking_Route_Flap_History_and_Metrics_with_show_ip_bgp_flap-statistics\" title=\"Checking Route Flap History and Metrics with show ip bgp flap-statistics\">Checking Route Flap History and Metrics with show ip bgp flap-statistics<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_1_Confirm_BGP_Dampening_Is_Active\" title=\"Step 1: Confirm BGP Dampening Is Active\">Step 1: Confirm BGP Dampening Is Active<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_2_Inspect_Global_Flap_Statistics\" title=\"Step 2: Inspect Global Flap Statistics\">Step 2: Inspect Global Flap Statistics<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_3_Interpret_Output_Columns_and_Status_Flags\" title=\"Step 3: Interpret Output Columns and Status Flags\">Step 3: Interpret Output Columns and Status Flags<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_4_Run_Targeted_Filters_on_Specific_Prefixes_or_Autonomous_Systems\" title=\"Step 4: Run Targeted Filters on Specific Prefixes or Autonomous Systems\">Step 4: Run Targeted Filters on Specific Prefixes or Autonomous Systems<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_5_Clear_Flap_History_After_Stabilization\" title=\"Step 5: Clear Flap History After Stabilization\">Step 5: Clear Flap History After Stabilization<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Decoding_Cisco_BGP_Syslog_Messages_and_Peer_Reset_Reasons\" title=\"Decoding Cisco BGP Syslog Messages and Peer Reset Reasons\">Decoding Cisco BGP Syslog Messages and Peer Reset Reasons<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#What_does_BGP-5-ADJCHANGE_neighbor_Down_mean\" title=\"What does %BGP-5-ADJCHANGE: neighbor ... Down mean?\">What does %BGP-5-ADJCHANGE: neighbor ... Down mean?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#What_is_the_difference_between_BGP_Notification_sent_and_BGP_Notification_received\" title=\"What is the difference between BGP Notification sent and BGP Notification received?\">What is the difference between BGP Notification sent and BGP Notification received?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#What_do_the_standard_RFC_4271_BGP_Notification_Error_Codes_mean\" title=\"What do the standard RFC 4271 BGP Notification Error Codes mean?\">What do the standard RFC 4271 BGP Notification Error Codes mean?<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#How_do_you_find_the_historical_peer_reset_reason_on_a_Cisco_router\" title=\"How do you find the historical peer reset reason on a Cisco router?\">How do you find the historical peer reset reason on a Cisco router?<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step-by-Step_Troubleshooting_for_BGP_Neighbor_Flapping\" title=\"Step-by-Step Troubleshooting for BGP Neighbor Flapping\">Step-by-Step Troubleshooting for BGP Neighbor Flapping<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-13\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_1_Check_Physical_and_Data_Link_Layer_Health\" title=\"Step 1: Check Physical and Data Link Layer Health\">Step 1: Check Physical and Data Link Layer Health<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-14\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_2_Test_for_MTU_Mismatches_and_Path_MTU_Discovery_PMTUD_Failures\" title=\"Step 2: Test for MTU Mismatches and Path MTU Discovery (PMTUD) Failures\">Step 2: Test for MTU Mismatches and Path MTU Discovery (PMTUD) Failures<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-15\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_3_Check_for_High_CPU_Load_and_Control_Plane_Policing_CoPP_Drops\" title=\"Step 3: Check for High CPU Load and Control Plane Policing (CoPP) Drops\">Step 3: Check for High CPU Load and Control Plane Policing (CoPP) Drops<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-16\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_4_Verify_Timers_and_Bidirectional_Forwarding_Detection_BFD\" title=\"Step 4: Verify Timers and Bidirectional Forwarding Detection (BFD)\">Step 4: Verify Timers and Bidirectional Forwarding Detection (BFD)<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-17\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_5_Check_for_Routing_Recursion_and_Next-Hop_Loops\" title=\"Step 5: Check for Routing Recursion and Next-Hop Loops\">Step 5: Check for Routing Recursion and Next-Hop Loops<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-18\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Configuring_BGP_Route_Flap_Dampening_in_Cisco_IOS\" title=\"Configuring BGP Route Flap Dampening in Cisco IOS\">Configuring BGP Route Flap Dampening in Cisco IOS<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-19\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Global_BGP_Dampening_Configuration_Template\" title=\"Global BGP Dampening Configuration Template\">Global BGP Dampening Configuration Template<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-20\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Selective_Dampening_Configuration_Template_Recommended\" title=\"Selective Dampening Configuration Template (Recommended)\">Selective Dampening Configuration Template (Recommended)<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-21\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Verification_and_Operational_Inspection\" title=\"Verification and Operational Inspection\">Verification and Operational Inspection<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-22\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Setting_Up_Proactive_Monitoring_SNMP_Traps_Syslog_Alerts_and_EEM\" title=\"Setting Up Proactive Monitoring: SNMP Traps, Syslog Alerts, and EEM\">Setting Up Proactive Monitoring: SNMP Traps, Syslog Alerts, and EEM<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-23\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_1_Enable_BGP_SNMP_Traps\" title=\"Step 1: Enable BGP SNMP Traps\">Step 1: Enable BGP SNMP Traps<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-24\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_2_Configure_Centralized_Syslog_Alerting\" title=\"Step 2: Configure Centralized Syslog Alerting\">Step 2: Configure Centralized Syslog Alerting<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-25\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_3_Automate_Diagnostic_Capture_with_Cisco_EEM\" title=\"Step 3: Automate Diagnostic Capture with Cisco EEM\">Step 3: Automate Diagnostic Capture with Cisco EEM<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-26\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Step_4_Stream_Real-Time_Telemetry_IOS-XE\" title=\"Step 4: Stream Real-Time Telemetry (IOS-XE)\">Step 4: Stream Real-Time Telemetry (IOS-XE)<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-27\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Cisco_TAC_Technical_Reference_and_Diagnostic_Data_Collection\" title=\"Cisco TAC Technical Reference and Diagnostic Data Collection\">Cisco TAC Technical Reference and Diagnostic Data Collection<\/a><ul class=\"ez-toc-list-level-3\"><li class=\"ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-28\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Architectural_Scoping_and_Definitions\" title=\"Architectural Scoping and Definitions\">Architectural Scoping and Definitions<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-29\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Mandatory_TAC_Diagnostic_Command_Matrix\" title=\"Mandatory TAC Diagnostic Command Matrix\">Mandatory TAC Diagnostic Command Matrix<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-3\"><a class=\"ez-toc-link ez-toc-heading-30\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Production_Safety_Guidelines_Debugging_Restrictions\" title=\"Production Safety Guidelines: Debugging Restrictions\">Production Safety Guidelines: Debugging Restrictions<\/a><\/li><\/ul><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-31\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\/#Conclusion\" title=\"Conclusion\">Conclusion<\/a><\/li><\/ul><\/nav><\/div>\n<h2><span class=\"ez-toc-section\" id=\"Checking_Route_Flap_History_and_Metrics_with_show_ip_bgp_flap-statistics\"><\/span>Checking Route Flap History and Metrics with <code>show ip bgp flap-statistics<\/code><span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When individual prefixes flap without tearing down the entire BGP peering session, Cisco routers track churn through BGP flap metrics. The primary tool for viewing this behavior is <code>show ip bgp flap-statistics<\/code>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Confirm_BGP_Dampening_Is_Active\"><\/span>Step 1: Confirm BGP Dampening Is Active<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Cisco routers only collect flap statistics if BGP Route Flap Dampening is enabled. If dampening is disabled, the command will return an empty table or a notification stating that dampening is inactive. Verify your base configuration before investigating:<\/p>\n<pre><code class=\"language-ios\">Router# show ip bgp dampening parameters\n<\/code><\/pre>\n<p>If dampening is active, proceed to verify the flap history across your routing information base (RIB).<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Inspect_Global_Flap_Statistics\"><\/span>Step 2: Inspect Global Flap Statistics<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Run <code>show ip bgp flap-statistics<\/code> (or <code>show bgp ipv4 unicast flap-statistics<\/code> in modern IOS-XE\/NX-OS) to view all prefixes that have accumulated penalty points:<\/p>\n<pre><code class=\"language-text\">Router# show ip bgp flap-statistics\nBGP table version is 14205, local router ID is 192.168.10.1\nStatus codes: s suppressed, d damped, h history, * valid, &gt; best, i - internal\nOrigin codes: i - IGP, e - EGP, ? - incomplete\n\n   Network          From            Flaps Duration Reuse    Path\n*d 10.100.1.0\/24    192.168.1.2         4 00:08:12 00:22:45 65001 65002 ?\n*h 172.16.50.0\/24   192.168.1.2         2 00:03:10          65001 65003 i\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Interpret_Output_Columns_and_Status_Flags\"><\/span>Step 3: Interpret Output Columns and Status Flags<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Each column in the output reveals how severely a prefix is misbehaving:<\/p>\n<ul>\n<li><strong>Status Codes (<code>*<\/code>, <code>d<\/code>, <code>h<\/code>, <code>s<\/code>):<\/strong><\/li>\n<li><code>*<\/code> (Valid): The route is valid and can be considered for best-path calculation.<\/li>\n<li><code>d<\/code> (Damped): The route has exceeded the suppress threshold and is currently withheld from the routing table.<\/li>\n<li><code>h<\/code> (History): The route flapped, was withdrawn, and is not currently reachable, but the router retains penalty history.<\/li>\n<li><code>s<\/code> (Suppressed): The route is suppressed due to dampening policy.<\/li>\n<li><strong>From:<\/strong> The IP address of the peer advertising the unstable prefix.<\/li>\n<li><strong>Flaps:<\/strong> The total count of flap events recorded since the history was created or cleared.<\/li>\n<li><strong>Duration:<\/strong> The elapsed time since the first flap event occurred.<\/li>\n<li><strong>Reuse:<\/strong> The remaining time before the route&#8217;s penalty drops below the reuse threshold, allowing it to become active again.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Run_Targeted_Filters_on_Specific_Prefixes_or_Autonomous_Systems\"><\/span>Step 4: Run Targeted Filters on Specific Prefixes or Autonomous Systems<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>On production routers carrying full Internet tables, running an unfiltered flap command can overwhelm the CLI buffer. Filter by specific prefix, subnet mask, regular expression, or AS-path filter list:<\/p>\n<pre><code class=\"language-ios\">! Filter on a specific subnet\nRouter# show ip bgp flap-statistics 10.100.1.0 255.255.255.0\n\n! Filter on paths passing through AS 65002\nRouter# show ip bgp flap-statistics regexp _65002_\n\n! Inspect full penalty details for a single route\nRouter# show ip bgp 10.100.1.0\/24\n<\/code><\/pre>\n<p>In the detailed <code>show ip bgp &lt;prefix&gt;<\/code> view, locate the lines showing <code>Flap-count<\/code>, <code>penalty<\/code>, and dampening status to see the exact penalty points assigned.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_Clear_Flap_History_After_Stabilization\"><\/span>Step 5: Clear Flap History After Stabilization<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Once the upstream provider or peering link stabilizes, manually reset accumulated penalties and flap counts:<\/p>\n<pre><code class=\"language-ios\">Router# clear ip bgp flap-statistics 10.100.1.0 255.255.255.0\n<\/code><\/pre>\n<blockquote>\n<p><strong>Takeaway:<\/strong> The <code>show ip bgp flap-statistics<\/code> command allows you to view historical prefix churn, penalty counters, and reuse timers, but it requires BGP dampening to be enabled on the router.<\/p>\n<\/blockquote>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Decoding_Cisco_BGP_Syslog_Messages_and_Peer_Reset_Reasons\"><\/span>Decoding Cisco BGP Syslog Messages and Peer Reset Reasons<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When the issue is neighbor flapping rather than route flapping, Cisco routers generate specific syslog events and record termination codes in the peer state table.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"What_does_BGP-5-ADJCHANGE_neighbor_Down_mean\"><\/span>What does <code>%BGP-5-ADJCHANGE: neighbor ... Down<\/code> mean?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>This message is logged whenever a BGP adjacency drops. The suffix of the log entry provides the immediate trigger:<\/p>\n<pre><code class=\"language-text\">%BGP-5-ADJCHANGE: neighbor 192.168.1.2 Down Hold time expired\n%BGP-5-ADJCHANGE: neighbor 192.168.1.2 Down Interface flap\n%BGP-5-ADJCHANGE: neighbor 192.168.1.2 Down Peer closed the session\n<\/code><\/pre>\n<ul>\n<li><strong><code>Hold time expired<\/code>:<\/strong> The local router did not receive any BGP KEEPALIVE or UPDATE packets within the agreed hold time window (default 180 seconds).<\/li>\n<li><strong><code>Interface flap<\/code>:<\/strong> The physical interface or subinterface over which the peer is reached went down, triggering an immediate teardown.<\/li>\n<li><strong><code>Peer closed the session<\/code>:<\/strong> The remote peer cleanly closed the underlying TCP connection via a TCP FIN or RST.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"What_is_the_difference_between_BGP_Notification_sent_and_BGP_Notification_received\"><\/span>What is the difference between <code>BGP Notification sent<\/code> and <code>BGP Notification received<\/code>?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong><code>Notification sent<\/code>:<\/strong> The <em>local<\/em> Cisco router detected a protocol violation or condition (such as an expired hold timer, malformed attribute, or administrative shutdown) and sent an RFC 4271 NOTIFICATION message to the peer before closing the session.<\/li>\n<li><strong><code>Notification received<\/code>:<\/strong> The <em>remote<\/em> peer detected an issue and sent an error code to the local router.<\/li>\n<\/ul>\n<p>The syslog entry typically includes the error code and subcode:<\/p>\n<pre><code class=\"language-text\">%BGP-3-NOTIFICATION: sent to neighbor 192.168.1.2 4\/0 (hold time expired) 0 bytes\n%BGP-3-NOTIFICATION: received from neighbor 192.168.1.2 2\/2 (bad peer AS) 2 bytes\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"What_do_the_standard_RFC_4271_BGP_Notification_Error_Codes_mean\"><\/span>What do the standard RFC 4271 BGP Notification Error Codes mean?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>BGP notifications use a <code>Code\/Subcode<\/code> format:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Error Code<\/th>\n<th style=\"text-align: left;\">Name<\/th>\n<th style=\"text-align: left;\">Common Triggers<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>1<\/strong><\/td>\n<td style=\"text-align: left;\">Message Header Error<\/td>\n<td style=\"text-align: left;\">Connection synchronized improperly, invalid marker, or incorrect message length.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>2<\/strong><\/td>\n<td style=\"text-align: left;\">OPEN Message Error<\/td>\n<td style=\"text-align: left;\">Subcode 2 indicates Bad Peer AS (mismatched AS numbers); Subcode 1 indicates Unsupported Version; Subcode 3 indicates Bad BGP Identifier.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>3<\/strong><\/td>\n<td style=\"text-align: left;\">UPDATE Message Error<\/td>\n<td style=\"text-align: left;\">Malformed attributes, missing well-known mandatory attributes, or invalid network layer reachability information (NLRI).<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>4<\/strong><\/td>\n<td style=\"text-align: left;\">Hold Timer Expired<\/td>\n<td style=\"text-align: left;\">Keepalives were lost in transit due to MTU issues, congestion, or high CPU utilization.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>5<\/strong><\/td>\n<td style=\"text-align: left;\">Finite State Machine Error<\/td>\n<td style=\"text-align: left;\">An unexpected packet was received while in a specific state (e.g., receiving an OPEN while already Established).<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>6<\/strong><\/td>\n<td style=\"text-align: left;\">Cease<\/td>\n<td style=\"text-align: left;\">Subcode 1 indicates Maximum Number of Prefixes Reached; Subcode 2 indicates Administrative Shutdown (<code>neighbor shutdown<\/code>); Subcode 3 indicates Peer De-configured.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"How_do_you_find_the_historical_peer_reset_reason_on_a_Cisco_router\"><\/span>How do you find the historical peer reset reason on a Cisco router?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If the syslog buffer has rolled over, you can retrieve the last drop reason directly from the peer\u2019s data structure:<\/p>\n<pre><code class=\"language-ios\">Router# show ip bgp neighbors 192.168.1.2 | include Last reset\nLast reset 00:04:12, due to Peer closed the session\n  Last reset reason: BGP Notification received, hold time expired\n<\/code><\/pre>\n<p>You can also check the counter history:<\/p>\n<pre><code class=\"language-ios\">Router# show ip bgp neighbors 192.168.1.2 | section Notification\n<\/code><\/pre>\n<p>This shows the timestamp, code, and raw hex bytes of the last sent and received notification messages.<\/p>\n<blockquote>\n<p><strong>Takeaway:<\/strong> Syslog messages containing <code>%BGP-5-ADJCHANGE<\/code> and <code>%BGP-3-NOTIFICATION<\/code> specify whether the local or remote router triggered the drop, while <code>show ip bgp neighbors &lt;IP&gt;<\/code> retains the precise reset reason even after the event has passed.<\/p>\n<\/blockquote>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Step-by-Step_Troubleshooting_for_BGP_Neighbor_Flapping\"><\/span>Step-by-Step Troubleshooting for BGP Neighbor Flapping<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>If BGP neighbor sessions drop and re-establish periodically, follow this structured diagnostic workflow to isolate the root cause.<\/p>\n<pre><code>+-------------------------------------------------------------------+\n|               BGP Neighbor Flapping Diagnostic Flow               |\n+-------------------------------------------------------------------+\n                                  |\n                                  v\n+-------------------------------------------------------------------+\n| Step 1: Check Physical \/ Link Layer (Errors, Drops, Carrier Flaps)|\n+-------------------------------------------------------------------+\n                                  | Link is Clean\n                                  v\n+-------------------------------------------------------------------+\n| Step 2: Validate MTU &amp; PMTUD (DF-bit Ping with Large Packets)     |\n+-------------------------------------------------------------------+\n                                  | MTU Passes (1500+ bytes)\n                                  v\n+-------------------------------------------------------------------+\n| Step 3: Inspect CPU &amp; Control Plane Policing (CoPP Drops)         |\n+-------------------------------------------------------------------+\n                                  | Control Plane Uncongested\n                                  v\n+-------------------------------------------------------------------+\n| Step 4: Verify Timers &amp; Fast Failure Detection (BFD Stability)    |\n+-------------------------------------------------------------------+\n                                  | Timers Sane \/ BFD Stable\n                                  v\n+-------------------------------------------------------------------+\n| Step 5: Check Routing Recursion &amp; Next-Hop Flapping               |\n+-------------------------------------------------------------------+\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Check_Physical_and_Data_Link_Layer_Health\"><\/span>Step 1: Check Physical and Data Link Layer Health<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>An unstable BGP session is frequently caused by intermittent physical connectivity. Check the underlying interface:<\/p>\n<pre><code class=\"language-ios\">Router# show interfaces GigabitEthernet0\/0\/0 | include line protocol|input errors|CRC|drops\nGigabitEthernet0\/0\/0 is up, line protocol is up\n     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored\n     142 carrier transitions\n<\/code><\/pre>\n<ul>\n<li><strong>Carrier transitions:<\/strong> Indicates link flaps at Layer 1\/2.<\/li>\n<li><strong>CRC \/ Input errors:<\/strong> Indicates faulty cabling, optics, or duplex\/speed mismatches causing TCP retransmissions and eventual session teardown.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Test_for_MTU_Mismatches_and_Path_MTU_Discovery_PMTUD_Failures\"><\/span>Step 2: Test for MTU Mismatches and Path MTU Discovery (PMTUD) Failures<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>A classic signature of an MTU issue is a BGP session that reaches <code>Established<\/code>, stays up for 90 to 180 seconds, and then collapses. <\/p>\n<p>During session establishment, small 64-byte KEEPALIVE packets negotiate the link. However, when the routers exchange their routing tables, BGP sends full-sized UPDATE packets (up to 1500 bytes or 4096 bytes if jumbo frames are configured). If an intermediate device drops packets larger than its MTU, the UPDATE packet never arrives, keepalives are blocked behind it, and the hold timer expires.<\/p>\n<p>Verify MTU reachability using sweeping ping tests with the Don&#8217;t Fragment (DF) bit set:<\/p>\n<pre><code class=\"language-ios\">Router# ping 192.168.1.2 size 1500 df-bit\nType escape sequence to abort.\nSending 5, 1500-byte ICMP Echos to 192.168.1.2, timeout is 2 seconds:\nPacket sent with the DF bit set\n.....\nSuccess rate is 0 percent (0\/5)\n<\/code><\/pre>\n<p>If the ping fails at 1500 bytes but succeeds at 1400 bytes, an MTU mismatch or dropped ICMP Type 3 Code 4 (Fragmentation Needed) packet is breaking Path MTU Discovery. <\/p>\n<p><strong>Fix:<\/strong> Correct the interface MTU across the path, or enforce PMTUD and maximum segment sizing on the BGP peer:<\/p>\n<pre><code class=\"language-ios\">Router(config)# router bgp 65000\nRouter(config-router)# neighbor 192.168.1.2 path-mtu-discovery\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Check_for_High_CPU_Load_and_Control_Plane_Policing_CoPP_Drops\"><\/span>Step 3: Check for High CPU Load and Control Plane Policing (CoPP) Drops<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If the router&#8217;s control plane is overwhelmed by process-switched traffic or route churn, the BGP process (<code>BGP Router<\/code>) may not get scheduled in time to process incoming keepalive packets before the hold timer expires.<\/p>\n<p>Check CPU utilization:<\/p>\n<pre><code class=\"language-ios\">Router# show processes cpu sorted | exclude 0.00%\nCPU utilization for five seconds: 98%\/12%; one minute: 95%; five minutes: 91%\n PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process\n 184   129482100   4829102      26812  48.20% 45.10% 42.15%   0 BGP Router\n<\/code><\/pre>\n<p>Check whether Control Plane Policing is dropping TCP port 179 packets under heavy traffic:<\/p>\n<pre><code class=\"language-ios\">Router# show policy-map control-plane | section class-default|bgp\n<\/code><\/pre>\n<p>Look for incrementing &#8220;drop&#8221; counters in classes matching BGP or routing protocol traffic.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Verify_Timers_and_Bidirectional_Forwarding_Detection_BFD\"><\/span>Step 4: Verify Timers and Bidirectional Forwarding Detection (BFD)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>If keepalive and hold timers are tuned too aggressively (e.g., 1-second keepalive, 3-second hold time) over a jittery WAN link, transient delay will drop the session. Similarly, if BFD is configured with sub-second timers over a congested link, BFD will pull down the BGP session prematurely.<\/p>\n<p>Inspect active timers:<\/p>\n<pre><code class=\"language-ios\">Router# show ip bgp neighbors 192.168.1.2 | include Hold time\n  Hold time is 180, keepalive interval is 60 seconds\n<\/code><\/pre>\n<p>If BFD is active, verify its stability:<\/p>\n<pre><code class=\"language-ios\">Router# show bfd neighbors details\n<\/code><\/pre>\n<p>Look for high flap counters or mismatched detection multipliers.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_5_Check_for_Routing_Recursion_and_Next-Hop_Loops\"><\/span>Step 5: Check for Routing Recursion and Next-Hop Loops<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>For multi-hop eBGP or iBGP sessions peered to loopback addresses, the router resolves the peer IP via an Interior Gateway Protocol (IGP) like OSPF or IS-IS. If the route to the peer&#8217;s loopback address is accidentally redistributed into BGP, a recursive routing loop occurs:<br \/>\n1. BGP establishes via the IGP route.<br \/>\n2. BGP learns the peer route, which has a better administrative distance or replaces the forwarding path.<br \/>\n3. The next-hop becomes recursive or invalid.<br \/>\n4. The BGP session drops, restoring the IGP route.<br \/>\n5. The cycle repeats continuously.<\/p>\n<p>Verify how the peer IP is routed:<\/p>\n<pre><code class=\"language-ios\">Router# show ip route 192.168.1.2\n<\/code><\/pre>\n<p>Ensure the route to the peer loopback is strictly learned via an IGP or static route, never via BGP.<\/p>\n<blockquote>\n<p><strong>Takeaway:<\/strong> Neighbor flapping is almost always caused by physical link errors, MTU\/PMTUD black holes during large UPDATE bursts, control plane starvation, or recursive routing loops affecting the peer&#8217;s IP address.<\/p>\n<\/blockquote>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Configuring_BGP_Route_Flap_Dampening_in_Cisco_IOS\"><\/span>Configuring BGP Route Flap Dampening in Cisco IOS<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When external peers flap routes rapidly, configuring BGP Route Flap Dampening (RFD) prevents those updates from destabilizing your internal network. Dampening assigns penalty points (1000 points per route withdrawal, 500 per attribute change). If the penalty exceeds the <strong>suppress limit<\/strong>, the route is dampened. Once the flapping stops and the penalty decays below the <strong>reuse limit<\/strong>, the route is reinstated.<\/p>\n<p>Use the following production templates to configure dampening globally or selectively via route maps.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Global_BGP_Dampening_Configuration_Template\"><\/span>Global BGP Dampening Configuration Template<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Apply dampening across an entire BGP address family using default or custom decay timers.<\/p>\n<pre><code class=\"language-ios\">router bgp &lt;LOCAL_AS&gt;\n address-family ipv4 unicast\n  ! Syntax: bgp dampening [&lt;half-life&gt; &lt;reuse&gt; &lt;suppress&gt; &lt;max-suppress-time&gt;]\n  ! Default: half-life=15m, reuse=750, suppress=2000, max-suppress=60m\n  bgp dampening 15 750 2000 60\n exit-address-family\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Selective_Dampening_Configuration_Template_Recommended\"><\/span>Selective Dampening Configuration Template (Recommended)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Applying aggressive dampening to critical routes (such as internal prefixes or major internet transit routes) can create extended outages. Use a <code>route-map<\/code> to apply differentiated dampening parameters based on prefix length.<\/p>\n<pre><code class=\"language-ios\">! Step 1: Define prefixes to match (e.g., golden routes vs small prefixes)\nip prefix-list CRITICAL_PREFIXES permit 10.0.0.0\/8 le 16\nip prefix-list VOLATILE_PREFIXES permit 0.0.0.0\/0 ge 24\n\n! Step 2: Define route-map with customized dampening metrics\nroute-map BGP_DAMPENING_POLICY permit 10\n match ip address prefix-list CRITICAL_PREFIXES\n ! Mild dampening for large\/critical blocks: half-life 10m, reuse 1000, suppress 3000, max 30m\n set dampening 10 1000 3000 30\n!\nroute-map BGP_DAMPENING_POLICY permit 20\n match ip address prefix-list VOLATILE_PREFIXES\n ! Aggressive dampening for small subnets: half-life 20m, reuse 500, suppress 1500, max 60m\n set dampening 20 500 1500 60\n!\nroute-map BGP_DAMPENING_POLICY permit 30\n ! Default action: fallback to standard dampening\n set dampening 15 750 2000 60\n\n! Step 3: Apply the route-map under the BGP process\nrouter bgp &lt;LOCAL_AS&gt;\n address-family ipv4 unicast\n  bgp dampening route-map BGP_DAMPENING_POLICY\n exit-address-family\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Verification_and_Operational_Inspection\"><\/span>Verification and Operational Inspection<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<pre><code class=\"language-ios\">! Display active dampening configuration parameters\nRouter# show ip bgp dampening parameters\n\n! Display only paths that are currently suppressed\/dampened\nRouter# show ip bgp dampened-paths\n<\/code><\/pre>\n<blockquote>\n<p><strong>Takeaway:<\/strong> Use selective dampening via route-maps rather than global dampening to avoid penalizing well-aggregated, business-critical prefixes while suppressing volatile customer or edge subnets.<\/p>\n<\/blockquote>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Setting_Up_Proactive_Monitoring_SNMP_Traps_Syslog_Alerts_and_EEM\"><\/span>Setting Up Proactive Monitoring: SNMP Traps, Syslog Alerts, and EEM<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Rather than waiting for users to report connectivity loss, configure automated alerting to detect BGP state changes and flapping routes as they happen.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_1_Enable_BGP_SNMP_Traps\"><\/span>Step 1: Enable BGP SNMP Traps<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Configure the router to send standard SNMP traps whenever a peer transitions between finite state machine (FSM) states:<\/p>\n<pre><code class=\"language-ios\">! Enable generation of traps when BGP neighbor drops or establishes\nRouter(config)# snmp-server enable traps bgp state-changes\n\n! Direct traps to your Network Management System (NMS)\nRouter(config)# snmp-server host 10.200.1.50 version 2c COMMUNITY_STRING bgp\n<\/code><\/pre>\n<p>Key SNMP Object Identifiers (OIDs) monitored by network surveillance platforms include:<br \/>\n* <strong><code>bgpPeerStateChange<\/code> (1.3.6.1.2.1.15.7.1 or 1.3.6.1.2.1.15.0.1):<\/strong> Standard RFC 1657 trap sent on any state change.<br \/>\n* <strong><code>cbgpPeerStateChangeBackwardTransition<\/code> (1.3.6.1.4.1.9.9.187.0.1):<\/strong> Cisco-specific trap generated whenever a session transitions backward (e.g., from <code>Established<\/code> to <code>Idle<\/code>).<br \/>\n* <strong><code>bgpPeerLastError<\/code> (1.3.6.1.2.1.15.3.1.14):<\/strong> Contains the 2-byte error code and subcode of the last notification.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_2_Configure_Centralized_Syslog_Alerting\"><\/span>Step 2: Configure Centralized Syslog Alerting<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Ensure all neighbor change events (<code>%BGP-5-ADJCHANGE<\/code>) are forwarded to a SIEM or centralized logging collector:<\/p>\n<pre><code class=\"language-ios\">Router(config)# logging host 10.200.1.60\nRouter(config)# logging trap notifications\nRouter(config)# logging source-interface Loopback0\nRouter(config)# service timestamps log datetime msec show-timezone\n<\/code><\/pre>\n<p>Configure your SIEM or log management tool to alert on the string <code>%BGP-5-ADJCHANGE: neighbor .* Down<\/code>.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Step_3_Automate_Diagnostic_Capture_with_Cisco_EEM\"><\/span>Step 3: Automate Diagnostic Capture with Cisco EEM<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>When a flap occurs intermittently, the state has often recovered by the time an engineer logs in. Use Cisco Embedded Event Manager (EEM) to capture state data at the exact moment of the flap:<\/p>\n<pre><code class=\"language-ios\">Router(config)# event manager applet BGP_NEIGHBOR_FLAP_MONITOR\nRouter(config-applet)# event syslog pattern &quot;%BGP-5-ADJCHANGE: neighbor .* Down&quot;\nRouter(config-applet)# action 1.0 syslog msg &quot;EEM: BGP flap detected. Capturing diagnostics.&quot;\nRouter(config-applet)# action 2.0 cli command &quot;enable&quot;\nRouter(config-applet)# action 3.0 cli command &quot;show ip bgp summary | redirect bootflash:bgp_diag_sum.txt&quot;\nRouter(config-applet)# action 4.0 cli command &quot;show processes cpu sorted | redirect bootflash:bgp_diag_cpu.txt&quot;\nRouter(config-applet)# action 5.0 cli command &quot;show policy-map control-plane | redirect bootflash:bgp_diag_copp.txt&quot;\n<\/code><\/pre>\n<h3><span class=\"ez-toc-section\" id=\"Step_4_Stream_Real-Time_Telemetry_IOS-XE\"><\/span>Step 4: Stream Real-Time Telemetry (IOS-XE)<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>For modern network architectures, configure Model-Driven Telemetry (MDT) to stream BGP state changes in real time via gRPC or NETCONF using the <code>Cisco-IOS-XE-bgp-oper<\/code> YANG model. This provides microsecond-level visibility into peer state changes without the polling overhead of SNMP.<\/p>\n<blockquote>\n<p><strong>Takeaway:<\/strong> Combine SNMP backward-transition traps for immediate paging with an EEM diagnostic-capture script to ensure you have control plane, CPU, and peer data preserved at the moment a session drops.<\/p>\n<\/blockquote>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Cisco_TAC_Technical_Reference_and_Diagnostic_Data_Collection\"><\/span>Cisco TAC Technical Reference and Diagnostic Data Collection<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>When escalating an unresolved BGP flapping case to the Cisco Technical Assistance Center (TAC), adhering to official diagnostic methodology accelerates root-cause identification.<\/p>\n<h3><span class=\"ez-toc-section\" id=\"Architectural_Scoping_and_Definitions\"><\/span>Architectural Scoping and Definitions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>BGP Session Flapping:<\/strong> Governed by RFC 4271. Refers to failure of the transport connection (TCP port 179) or expiration of the FSM keepalive mechanism.<\/li>\n<li><strong>BGP Route Flap Dampening:<\/strong> Governed by RFC 2439. Defines the mathematical decay model used to penalize fluctuating NLRI without dropping the transport session.<\/li>\n<\/ul>\n<h3><span class=\"ez-toc-section\" id=\"Mandatory_TAC_Diagnostic_Command_Matrix\"><\/span>Mandatory TAC Diagnostic Command Matrix<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<p>Collect and attach the following outputs before opening a TAC service request:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Diagnostic Scope<\/th>\n<th style=\"text-align: left;\">Command Syntax<\/th>\n<th style=\"text-align: left;\">Purpose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Global BGP State<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show ip bgp summary<\/code><\/td>\n<td style=\"text-align: left;\">Identifies neighbor up\/down duration and state\/prefix counts.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Peer Deep Dive<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show ip bgp neighbors &lt;PEER_IP&gt;<\/code><\/td>\n<td style=\"text-align: left;\">Details last reset reason, notification history, and negotiated timers.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Route Churn<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show ip bgp flap-statistics<\/code><\/td>\n<td style=\"text-align: left;\">Verifies prefix flap history and accumulated penalties.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Control Plane<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show processes cpu sorted<\/code><\/td>\n<td style=\"text-align: left;\">Checks for BGP Router process starvation or high interrupt CPU load.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Buffer History<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show logging<\/code><\/td>\n<td style=\"text-align: left;\">Preserves timestamped notification codes and FSM transitions.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Aggregated Data<\/strong><\/td>\n<td style=\"text-align: left;\"><code>show tech-support bgp<\/code><\/td>\n<td style=\"text-align: left;\">Generates a comprehensive snapshot of memory, configuration, and protocol data.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3><span class=\"ez-toc-section\" id=\"Production_Safety_Guidelines_Debugging_Restrictions\"><\/span>Production Safety Guidelines: Debugging Restrictions<span class=\"ez-toc-section-end\"><\/span><\/h3>\n<ul>\n<li><strong>Never run unconstrained debug commands:<\/strong> Avoid running <code>debug ip bgp<\/code> or <code>debug ip bgp updates<\/code> on production routers. On a router carrying Internet routes, this will overwhelm the CPU and cause cascading outages.<\/li>\n<li><strong>Apply conditional debugging:<\/strong> If debugging is requested by TAC, always isolate the debug scope to the specific flapping neighbor:<br \/>\n  <code>ios<br \/>\n  Router# debug ip bgp conditional group<br \/>\n  Router# debug ip bgp neighbors 192.168.1.2 updates<\/code><\/li>\n<li><strong>Verify control-plane limits:<\/strong> Run debugs with logging redirected to the internal buffer (<code>logging buffered<\/code>), never to the console terminal (<code>no logging console<\/code>).<\/li>\n<\/ul>\n<blockquote>\n<p><strong>Takeaway:<\/strong> Cisco TAC requires targeted neighbor statistics, logging buffers, and control plane load metrics to troubleshoot session instability; never run unconstrained global BGP debugs on production equipment.<\/p>\n<\/blockquote>\n<hr \/>\n<h2><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span>Conclusion<span class=\"ez-toc-section-end\"><\/span><\/h2>\n<p>Systematically isolating BGP flapping on Cisco routers requires separating route-level churn from session-level drops. Use <code>show ip bgp flap-statistics<\/code> and route flap dampening to view and control flapping prefixes across the routing table. When the peering session itself is bouncing, rely on syslog <code>%BGP-5-ADJCHANGE<\/code> messages, notification error codes, and targeted MTU and control-plane checks to identify the root cause. Backed by automated SNMP traps and EEM data collection, this structured approach ensures BGP instability is detected, analyzed, and resolved before it impacts business traffic.<\/p>\n<div class='sfsi_Sicons' style='width: 100%; display: inline-block; vertical-align: middle; text-align:left'><div style='margin:0px 8px 0px 0px; line-height: 24px'><span>Please follow and like us:<\/span><\/div><div class='sfsi_socialwpr'><div class='sf_fb_share sf_icon' style='text-align:left;vertical-align: middle;'><a href='https:\/\/www.facebook.com\/sharer\/sharer.php?u=https%3A%2F%2Fcciedump.spoto.net%2Fblog%2Fhow-to-check-bgp-flapping-in-cisco_24517.html' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Facebook Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/fbshare_bck.png'  \/><\/a><\/div><div class='sf_twiter sf_icon' style='display: inline-block;vertical-align: middle;width: auto;margin-left: 7px;'>\r\n\t\t\t\t\t\t<a target='_blank' href='https:\/\/twitter.com\/intent\/tweet?text=How+to+Check+BGP+Flapping+in+Cisco+https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html'style='display:inline-block' >\r\n\t\t\t\t\t\t\t<img data-pin-nopin= true width='auto' class='sfsi_wicon' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/visit_icons\/en_US_Tweet.svg' alt='Tweet' title='Tweet' >\r\n\t\t\t\t\t\t<\/a>\r\n\t\t\t\t\t<\/div><div class='sf_pinit sf_icon' style='text-align:left;vertical-align: middle;float:left;line-height: 33px;width:auto;margin: 0 -2px;'><a href='#'  onclick='sfsi_pinterest_modal_images(event,\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\",\"How to Check BGP Flapping in Cisco\")' style='display:inline-block;'  > <img class='sfsi_wicon'  data-pin-nopin='true' width='auto' height='auto' alt='fb-share-icon' title='Pin Share' src='https:\/\/cciedump.spoto.net\/blog\/wp-content\/plugins\/ultimate-social-media-icons\/images\/share_icons\/Pinterest_Save\/en_US_save.svg'  \/><\/a><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>Border Gateway Protocol (BGP) instability is one of the most critical issues a network engineer can face. When BGP flaps, it consumes router CPU cycles, invalidates forwarding tables, and introduces severe packet loss and routing black holes across autonomous systems. Diagnosing BGP flapping on Cisco IOS, IOS-XE, and NX-OS devices requires recognizing a fundamental distinction:&#8230; &raquo; <a class=\"read-more-link\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\">read more<\/a><\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[3,608],"tags":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v18.0 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>How to Check BGP Flapping in Cisco - SPOTO Official Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Check BGP Flapping in Cisco - SPOTO Official Blog\" \/>\n<meta property=\"og:description\" content=\"Border Gateway Protocol (BGP) instability is one of the most critical issues a network engineer can face. When BGP flaps, it consumes router CPU cycles, invalidates forwarding tables, and introduces severe packet loss and routing black holes across autonomous systems. Diagnosing BGP flapping on Cisco IOS, IOS-XE, and NX-OS devices requires recognizing a fundamental distinction:... &raquo; read more\" \/>\n<meta property=\"og:url\" content=\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\" \/>\n<meta property=\"og:site_name\" content=\"SPOTO Official Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-16T03:47:07+00:00\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"SPOTO \u7f16\u8f91\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"15 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\",\"name\":\"SPOTO Club\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg\",\"caption\":\"SPOTO Club\"},\"logo\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\"},\"description\":\"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205\",\"sameAs\":[\"https:\/\/cciedump.spoto.net\/\"]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/\",\"name\":\"SPOTO Official Blog\",\"description\":\"Focus on Online IT Training for 20+ Years\",\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#webpage\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\",\"name\":\"How to Check BGP Flapping in Cisco - SPOTO Official Blog\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#website\"},\"datePublished\":\"2026-11-16T03:47:07+00:00\",\"dateModified\":\"2026-11-16T03:47:07+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/cciedump.spoto.net\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Check BGP Flapping in Cisco\"}]},{\"@type\":\"Article\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#article\",\"isPartOf\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#webpage\"},\"author\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\"},\"headline\":\"How to Check BGP Flapping in Cisco\",\"datePublished\":\"2026-11-16T03:47:07+00:00\",\"dateModified\":\"2026-11-16T03:47:07+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#webpage\"},\"wordCount\":2142,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638\"},\"articleSection\":[\"CCNA Certification\",\"Cisco Certification\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#respond\"]}]},{\"@type\":\"Person\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1\",\"name\":\"SPOTO \u7f16\u8f91\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\/\/cciedump.spoto.net\/blog\/#personlogo\",\"inLanguage\":\"en-US\",\"url\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"contentUrl\":\"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155\",\"caption\":\"SPOTO \u7f16\u8f91\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Check BGP Flapping in Cisco - SPOTO Official Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html","og_locale":"en_US","og_type":"article","og_title":"How to Check BGP Flapping in Cisco - SPOTO Official Blog","og_description":"Border Gateway Protocol (BGP) instability is one of the most critical issues a network engineer can face. When BGP flaps, it consumes router CPU cycles, invalidates forwarding tables, and introduces severe packet loss and routing black holes across autonomous systems. Diagnosing BGP flapping on Cisco IOS, IOS-XE, and NX-OS devices requires recognizing a fundamental distinction:... &raquo; read more","og_url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html","og_site_name":"SPOTO Official Blog","article_published_time":"2026-11-16T03:47:07+00:00","twitter_card":"summary_large_image","twitter_misc":{"Written by":"SPOTO \u7f16\u8f91","Est. reading time":"15 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":["Person","Organization"],"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638","name":"SPOTO Club","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/uploads\/2020\/03\/spoto-facemask-96x96.jpg","caption":"SPOTO Club"},"logo":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo"},"description":"SPOTO is an excellent leader in IT certification training for 20+ years. We offer 100% real Cisco CCNA, CCNP exam dumps, CCIE Lab study materials, PMP, CISA, CISM, AWS, Palo Alto, and other IT exam dumps. We have helped thousands of candidates around the world to pass their IT exams on the first try! As the first-class online IT training organization in China, SPOTO cooperates with many giant Internet companies in China like Tencent, Baidu, and Alibaba. What\u2019s more, we have won lots of awards in IT education training such as \u201cTop Ten Influential Brands In Online Education Industry\u201d given by Baidu, \u201cOfficial IT Online Training Organization\u201d awarded by Tencent Class, etc. Join us: https:\/\/cciedump.spoto.net\/ Contact us: E-mail: support@spoto.net Phone \/ WhatsApp: +86 18344981205","sameAs":["https:\/\/cciedump.spoto.net\/"]},{"@type":"WebSite","@id":"https:\/\/cciedump.spoto.net\/blog\/#website","url":"https:\/\/cciedump.spoto.net\/blog\/","name":"SPOTO Official Blog","description":"Focus on Online IT Training for 20+ Years","publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/cciedump.spoto.net\/blog\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#webpage","url":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html","name":"How to Check BGP Flapping in Cisco - SPOTO Official Blog","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#website"},"datePublished":"2026-11-16T03:47:07+00:00","dateModified":"2026-11-16T03:47:07+00:00","breadcrumb":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/cciedump.spoto.net\/blog"},{"@type":"ListItem","position":2,"name":"How to Check BGP Flapping in Cisco"}]},{"@type":"Article","@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#article","isPartOf":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#webpage"},"author":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1"},"headline":"How to Check BGP Flapping in Cisco","datePublished":"2026-11-16T03:47:07+00:00","dateModified":"2026-11-16T03:47:07+00:00","mainEntityOfPage":{"@id":"https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#webpage"},"wordCount":2142,"commentCount":0,"publisher":{"@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/25594d4796697ccb1ef63d55c269c638"},"articleSection":["CCNA Certification","Cisco Certification"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/cciedump.spoto.net\/blog\/how-to-check-bgp-flapping-in-cisco_24517.html#respond"]}]},{"@type":"Person","@id":"https:\/\/cciedump.spoto.net\/blog\/#\/schema\/person\/4edd6074d9632c14eda17a2205a88dd1","name":"SPOTO \u7f16\u8f91","image":{"@type":"ImageObject","@id":"https:\/\/cciedump.spoto.net\/blog\/#personlogo","inLanguage":"en-US","url":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","contentUrl":"https:\/\/cciedump.spoto.net\/blog\/wp-content\/litespeed\/avatar\/f525ded90e4ff384a19ebdbe47c80d22.jpg?ver=1794560155","caption":"SPOTO \u7f16\u8f91"}}]}},"_links":{"self":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24517"}],"collection":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/comments?post=24517"}],"version-history":[{"count":0,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/posts\/24517\/revisions"}],"wp:attachment":[{"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/media?parent=24517"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/categories?post=24517"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cciedump.spoto.net\/blog\/wp-json\/wp\/v2\/tags?post=24517"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}