← Back to Part 2 Modules
PART 2 · ADVANCED BGP THEORY · MODULE N

Module N – BGP Troubleshooting

Lesson content presented from the approved Part 2 master documentation.

A systematic workflow separates transport/session problems from route advertisement, policy, best-path, RIB and forwarding problems.

Learning objectives

1. Layered workflow

  1. Check neighbour state and record exact FSM state.
  2. Verify peer address, source interface/address and IP reachability.
  3. Check TCP/179, ACL/firewall and authentication.
  4. Verify local ASN, remote-as, update-source and eBGP multihop.
  5. Inspect neighbour detail, notifications and counters.
  6. Check route origination, UPDATE/withdrawal and address-family activation.
  7. Inspect inbound/outbound policy and received/advertised routes.
  8. Check next-hop reachability and best-path selection.
  9. Check BGP table, RIB installation and forwarding separately.
  10. After correction, measure convergence and retain evidence.

2. Key commands

show ip bgp summary
show ip bgp neighbors
show ip bgp <prefix>
show ip route <prefix>
show ip route <peer-address>
show tcp brief
show logging
show ip prefix-list
show route-map

received-routes may require inbound soft-reconfiguration and platform support. Command availability and address-family syntax vary.

3. FSM symptom guide

State / symptomChecks
IdleAdministrative shutdown, configuration, resource or policy conditions; inspect logs/config.
ConnectTCP attempt in progress; verify reachability and TCP/179.
ActiveTCP connection retries; not Established. Check routing, ACLs, source address and peer listener.
OpenSentTCP connected and OPEN sent; inspect ASN, capabilities and OPEN validation.
OpenConfirmWaiting for KEEPALIVE/protocol progress; inspect timers, capture and notifications.
Established but no prefixesCheck origination, address family, filters, route maps, refresh and peer advertisement.

4. Missing route investigation

5. UPDATE, withdrawal and capture

An UPDATE can advertise reachable prefixes and/or withdraw previously advertised prefixes. Determine whether the source withdrew the route, policy filtered it, the session reset or best-path/RIB selection changed.

Wireshark: tcp.port == 179
Linux:
ping <peer-address>
traceroute <peer-address>
nc -vz <peer-address> 179

ICMP failure alone does not prove BGP is unreachable because ICMP may be filtered. Debug commands can be CPU-intensive; use cautiously, preferably in a lab or controlled window.

6. Root-cause report

FieldRecord
Issue / symptomWhat failed and when
Topology / softwareRouter IDs, ASNs, interfaces, image/version
Expected behaviourWhat should have happened
Actual behaviourObserved FSM, route and forwarding state
EvidenceCLI, logs, packet capture and timestamps
Root causeConfirmed cause, not symptom
CorrectionConfiguration/operational change
RegressionTests repeated and results
Impact / recoveryRoute loss, packet loss and convergence

Senior QA scenarios

IDTestExpected result
N-01Block TCP/179Session cannot establish; transport issue diagnosed.
N-02Wrong remote-ASOPEN validation fails; notification/log inspected.
N-03Shutdown peering interfaceSession tears down and routes withdraw.
N-04Restore connectivitySession and routes recover.
N-05Established but filter all prefixesSession up; route table reflects policy.
N-06Withdraw advertised prefixWithdrawal propagates.
N-07Unreachable next hopRoute unusable/not installed as expected.
N-08Wrong update-source/multihopSession failure diagnosed.
N-09Authentication mismatchEstablishment fails.
N-10Controlled Hold expiryTeardown/log/capture align.
N-11Compare BGP table and RIBInstallation discrepancy explained.
N-12Check forwarding planeForwarding matches installed route.

Interview questions

Student Knowledge Assessment – Module N (reconstructed)

Q1. Which command gives a quick overview of BGP peer state?

A. show ip bgp summary

B. show vlan

C. show arp

D. show clock

Correct answer: A. show ip bgp summary

Explanation: The summary displays neighbour states and prefix counts.

Q2. What does BGP Active state indicate?

A. Session fully operational

B. Router attempting/retrying TCP establishment

C. Route is best

D. Peer administratively up

Correct answer: B. Router attempting/retrying TCP establishment

Explanation: Active is a TCP establishment/retry state, not Established.

Q3. What is a first transport check for Connect/Active?

A. TCP/179 reachability

B. DNS MX

C. NTP stratum

D. VLAN name

Correct answer: A. TCP/179 reachability

Explanation: Check IP reachability and TCP port 179.

Q4. Can a BGP session be Established with zero prefixes received?

A. No

B. Yes

C. Only OSPF

D. Only route reflectors

Correct answer: B. Yes

Explanation: Session can be Established while origination or policy prevents route exchange.

Q5. What does an UPDATE carry?

A. Only timers

B. Route advertisements and/or withdrawals

C. Only TCP ACKs

D. Only router IDs

Correct answer: B. Route advertisements and/or withdrawals

Explanation: UPDATE advertises reachable prefixes and can withdraw routes.

Q6. What should be checked when a prefix is missing?

A. Origination, policy, next hop and best path

B. Only hostname

C. Only interface description

D. Only NTP

Correct answer: A. Origination, policy, next hop and best path

Explanation: Check the complete advertisement and selection path.

Q7. Does ping failure prove TCP/179 unavailable?

A. Yes

B. No

C. Only eBGP

D. Only iBGP

Correct answer: B. No

Explanation: ICMP may be filtered; test TCP and inspect routing/firewall evidence.

Q8. What does next-hop reachability affect?

A. Whether a path can be usable/installed

B. Only hostname

C. Only TCP port

D. Only community display

Correct answer: A. Whether a path can be usable/installed

Explanation: An unreachable next hop can prevent route usability or RIB installation.

Q9. Why distinguish BGP table, RIB and FIB?

A. Different stages of selection and forwarding

B. They are identical

C. Only IPv6

D. Only MED

Correct answer: A. Different stages of selection and forwarding

Explanation: A route can be in BGP but not installed in RIB/FIB.

Q10. Why use debug cautiously?

A. It can consume CPU/resources and generate large output

B. It changes ASN

C. It encrypts traffic

D. It disables route maps

Correct answer: A. It can consume CPU/resources and generate large output

Explanation: Debugging can affect router performance.

Source and assessment note

Technical explanations, tables, examples, QA scenarios and assessments are presented from the approved Part 2 master documentation. Verify illustrative CLI syntax against the target router platform and software release before lab or production use.