BGPRouter Config

neighbor [ip] update-source [interface]

Sources BGP sessions from a loopback interface to increase session stability in iBGP topologies.

Syntax·Router Config
neighbor <ip-address> update-source <interface-type><interface-number>

When to Use This Command

  • iBGP sessions between routers that have multiple paths between them.
  • Sourcing BGP updates from a stable loopback instead of a physical interface.
  • Required when the neighbor IP is the peer's loopback address.
  • Standard best practice in all iBGP full-mesh configurations.

Command Examples

iBGP session sourced from Loopback0

R1(config)# router bgp 65001 R1(config-router)# neighbor 10.0.0.2 remote-as 65001 R1(config-router)# neighbor 10.0.0.2 update-source Loopback0
R1(config-router)#

Both routers peer via their Loopback0 addresses (10.0.0.1 and 10.0.0.2). The update-source ensures BGP TCP sessions originate from Loopback0, not the outgoing physical interface. This must be configured symmetrically on both peers.

Verify source interface in BGP detail

R1# show ip bgp neighbors 10.0.0.2
BGP neighbor is 10.0.0.2, remote AS 65001, internal link
  BGP version 4, remote router ID 10.0.0.2
  BGP state = Established, up for 01:23:45
  Local host: 10.0.0.1, Local port: 32456
  Foreign host: 10.0.0.2, Foreign port: 179
  Connection established 1; dropped 0
  Last reset never

Local host shows 10.0.0.1 (Loopback0), confirming the session is sourced from the loopback. The session is Established and stable.

Understanding the Output

No direct output from the command. Verify with 'show ip bgp neighbors [ip]' — look for 'Local host' to confirm the source interface IP. Without this command for loopback-peered iBGP, the session will fail because the BGP OPEN will arrive from a physical interface IP that the peer doesn't recognize as a neighbor.

CCNA Exam Tips

1.

CCNA exam tip: When iBGP peers use loopback addresses, BOTH routers need 'neighbor update-source Loopback0' — one-sided config causes the session to fail.

2.

CCNA exam tip: The loopback IP must be reachable via IGP (OSPF, EIGRP) for the iBGP session to establish.

3.

CCNA exam tip: This command is not needed for eBGP over a directly connected link — physical interface is the default source.

4.

CCNA exam tip: Missing update-source is the #1 reason iBGP sessions fail to establish in lab scenarios.

Common Mistakes

Mistake 1: Configuring update-source on only one side — the TCP session fails because the source IP doesn't match what the remote side expects.

Mistake 2: Using update-source without ensuring the loopback is advertised into the IGP — the loopback is unreachable from the peer.

Mistake 3: Configuring update-source for eBGP when it's not needed — though not harmful, it adds unnecessary complexity.

Related Commands

Practice for the CCNA 200-301

Test your knowledge with hundreds of CCNA practice questions covering all exam domains.

Practice CCNA Questions