← Back to Part 1 Modules
PART 1 · BASIC BGP THEORY · MODULE D

Module D – BGP Neighbour Relationships

Lesson content presented from the approved Part 1 master documentation.

Module D – BGP Neighbour Relationships

A BGP neighbour (peer) is another BGP speaker with which a router establishes a session. Neighbours are explicitly configured; BGP does not discover peers through periodic Hello packets.

Session establishment sequence

  • The configured peer address must be reachable at the IP layer.
  • The peers establish a TCP connection using port 179.
  • BGP OPEN messages are exchanged and validated, including AS and capability information.
  • KEEPALIVE messages confirm the OPEN exchange.
  • The session reaches Established and UPDATE messages can exchange reachability information.
  • Prerequisites

  • Correct local ASN and remote-as configuration.
  • Correct neighbour IP address and IP reachability.
  • Interfaces and required routes operational.
  • TCP/179 permitted by ACLs/firewalls.
  • Compatible authentication settings, if configured.
  • Compatible BGP capabilities and address-family configuration.
  • Directly connected eBGP example

    ! R1
    router bgp 65001
     neighbor 11.1.1.2 remote-as 65002
    !
    ! R2
    router bgp 65002
     neighbor 11.1.1.1 remote-as 65001

    Loopback peering and multihop

    Loopback peering requires the peer loopback to be reachable through the routing table, and the BGP session source must be set to the intended local loopback. eBGP loopback peering normally also requires an appropriate eBGP multihop TTL.

    router bgp 65001
     neighbor 192.0.2.2 remote-as 65002
     neighbor 192.0.2.2 update-source Loopback0
     neighbor 192.0.2.2 ebgp-multihop 2
    Troubleshooting distinction The BGP FSM state Active is not the same as an Established or operationally active session. Active means the BGP process is attempting/retrying TCP connection establishment.

    Verification commands

    show ip bgp summary
    show ip bgp neighbors
    show tcp brief
    show ip route <peer-address>
    ping <peer-address>
    show access-lists

    QA test ideas

  • Wrong neighbour address.
  • Incorrect remote-AS value.
  • TCP/179 blocked by an ACL.
  • Peer interface shutdown or link failure.
  • Missing route to loopback peer.
  • Incorrect update-source or eBGP multihop TTL.
  • Authentication mismatch where authentication is enabled.
  • Recovery after restoring the failed condition.
  • Student Knowledge Assessment – Module D

    Q1. How are BGP neighbours normally established?

    A. Automatically through Hello discovery

    B. By explicit neighbour configuration

    C. Through ARP only

    D. Through DHCP

    Correct answer: B. By explicit neighbour configuration Explanation: BGP peers are explicitly configured.

    Q2. Which transport protocol and port does BGP use?

    A. UDP/179

    B. TCP/179

    C. TCP/89

    D. UDP/520

    Correct answer: B. TCP/179 Explanation: BGP uses TCP port 179.

    Q3. What must be true before a BGP TCP session can establish?

    A. The peer address must be reachable

    B. OSPF must be enabled

    C. The router ID must be a public IP

    D. NAT must be enabled

    Correct answer: A. The peer address must be reachable Explanation: IP reachability and TCP connectivity to the peer are prerequisites.

    Q4. What does remote-as specify?

    A. The local interface speed

    B. The peer's expected autonomous system number

    C. The BGP hold timer

    D. The route-map name

    Correct answer: B. The peer's expected autonomous system number Explanation: remote-as configures the expected ASN of the neighbour.

    Q5. What is update-source used for?

    A. Selecting the local source interface/address for the BGP session

    B. Changing the peer ASN

    C. Changing the BGP message type

    D. Setting MED

    Correct answer: A. Selecting the local source interface/address for the BGP session Explanation: It selects the local source interface/address, commonly a loopback.

    Q6. Why may ebgp-multihop be needed?

    A. For eBGP peers not directly connected at Layer 3

    B. For all directly connected iBGP peers

    C. To enable OSPF

    D. To change TCP to UDP

    Correct answer: A. For eBGP peers not directly connected at Layer 3 Explanation: It increases the permitted TTL for eBGP sessions to non-directly connected peers.

    Q7. Which command provides a quick summary of BGP peer states?

    A. show ip bgp summary

    B. show arp

    C. show vlan

    D. show clock

    Correct answer: A. show ip bgp summary
    Explanation: show ip bgp summary lists peers and their session state/prefix counts.

    Q8. What does BGP Active state mean?

    A. The session is Established

    B. The router is attempting/retrying TCP connection establishment

    C. The route is installed

    D. The peer is disabled permanently

    Correct answer: B. The router is attempting/retrying TCP connection establishment Explanation: Active is an FSM state involving TCP connection attempts and retries.

    Q9. Which issue can prevent a BGP session despite correct ASN values?

    A. TCP/179 blocked

    B. A high interface description length

    C. A populated ARP cache

    D. A valid hostname

    Correct answer: A. TCP/179 blocked Explanation: An ACL or firewall blocking TCP/179 can prevent session establishment.

    Q10. What should be tested after correcting a BGP peering fault?

    A. Only configuration syntax

    B. Session recovery and route exchange

    C. Only hostname resolution

    D. Only console access

    Correct answer: B. Session recovery and route exchange Explanation: Validate that the session re-establishes and expected routes are exchanged.

    Source and assessment note

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