JN0-363 Border Gateway Protocol (BGP)

Border Gateway Protocol (BGP) Detailed Explanation

Overview

Border Gateway Protocol (BGP) is the routing protocol of the internet, designed for exchanging routing information between different autonomous systems (AS). An autonomous system is a network or group of networks under a single administrative domain. BGP is a path-vector protocol, which means it considers the path (via AS numbers) that a route takes to reach its destination.

BGP uses TCP (port 179) for reliable communication between peers, called BGP neighbors or BGP speakers.

Key Topics

1. BGP Message Types

BGP uses four main types of messages to communicate between peers:

• Open:

  • Used to establish a BGP session between two routers.
  • Includes parameters such as AS number, BGP version, and the Hold Timer.
  • Example:
    • Router A sends an Open message to Router B to initiate a BGP session.

• Update:

  • Used to advertise new routes or withdraw invalid routes.
  • Contains the following components:
    • Withdrawn Routes: Routes that are no longer valid.
    • Path Attributes: Information about the route (e.g., AS_PATH, NEXT_HOP).
    • Network Layer Reachability Information (NLRI): Advertised IP prefixes.

• Keepalive:

  • Ensures the session remains active.
  • Sent periodically, usually at one-third of the Hold Timer interval.

• Notification:

  • Sent when an error occurs or to terminate a BGP session.
  • Example: Sent if there is a configuration mismatch between peers.

Key Points to Remember:

• The first message exchanged is always Open.
• After the session is established, Keepalive and Update messages maintain the connection and exchange routing information.

2. BGP Attributes

BGP uses attributes to provide additional information about routes. These attributes influence route selection and propagation.

Well-Known Mandatory Attributes

1. AS_PATH:

   • Lists the sequence of AS numbers a route has traversed.
   • Helps in loop prevention: If a router sees its own AS in the AS_PATH, it discards the route.

2. NEXT_HOP:

   • Specifies the IP address of the next-hop router for a route.
   • Ensures proper forwarding of packets.

3. ORIGIN:

   • Indicates the origin of the route.
   • Possible values:
     • IGP: Originated from an interior routing protocol.
     • EGP: Originated from the legacy Exterior Gateway Protocol.
     • Incomplete: Learned via manual configuration or redistribution.

Optional Transitive Attributes

1. COMMUNITY:
   • Tags routes for grouping and policy implementation.
   • Common community values:
     • no-export: Do not advertise outside the local AS.
     • no-advertise: Do not advertise to any BGP neighbors.

Optional Non-Transitive Attributes

1. MED (Multi-Exit Discriminator):
   • Suggests a preferred entry point into an AS.
   • Lower MED values are preferred.

3. BGP Route Selection Process

BGP uses a step-by-step process to select the best route among multiple available routes:

1. Weight (Cisco-specific, local to the router):

   • Higher weight is preferred.
   • Configurable locally and not shared with other routers.

2. Local Preference:

   • Indicates the preferred path within an AS.
   • Higher Local Preference is preferred.
   • Propagated to all iBGP peers.

3. AS_PATH:

   • Shorter AS_PATH is preferred.

4. Origin:

   • Preference order: IGP > EGP > Incomplete.

5. MED:

   • Lower MED is preferred.

6. eBGP vs. iBGP:

   • eBGP routes are preferred over iBGP routes.

7. Shortest IGP Path to Next-Hop:

   • Determines the closest next-hop router.

8. Oldest Route:

   • BGP prefers the route learned first if all other attributes are equal.

9. Router ID:

   • Lowest Router ID is preferred.

4. iBGP and eBGP

BGP has two operational modes depending on the relationship between peers:

• eBGP (External BGP):

  • Used for routing between different ASes.
  • Default Time-to-Live (TTL) for eBGP is 1, limiting communication to directly connected peers.
  • Example:
    • Router A in AS 65001 establishes an eBGP session with Router B in AS 65002.

• iBGP (Internal BGP):

  • Used for routing within the same AS.
  • Requires a full mesh of peers unless route reflectors are used.
  • iBGP does not advertise routes learned from one iBGP peer to another iBGP peer (to avoid loops).

Configuration Example:

set protocols bgp group EBGP neighbors 192.168.1.1 peer-as 65002
set protocols bgp group IBGP neighbors 10.0.0.1 local-as 65001

5. BGP Route Reflectors (RR)

In large networks, a full-mesh iBGP setup is impractical due to the exponential growth of peer connections.

• What is a Route Reflector?

  • A central router that distributes routes between iBGP peers, eliminating the need for full mesh.

• Key Components:

  • Clients: iBGP peers that rely on the route reflector.
  • Cluster ID: Used to prevent loops in route reflection.

Configuration Example:

set protocols bgp group INTERNAL type internal
set protocols bgp group INTERNAL neighbor 10.1.1.1 route-reflector-client

6. BGP Communities

Communities are used to tag routes for policy implementation.

• Common Community Values:
  • no-export: Prevents the route from being advertised outside the local AS.
  • local-AS: Limits the advertisement to the local AS.
  • no-advertise: Prevents the route from being advertised to any peer.

Configuration Example:

set policy-options policy-statement COMMUNITY-EXAMPLE term 1 then community add NO-EXPORT

7. BGP Configuration Example

BGP configuration involves setting up sessions between peers, defining policies, and managing attributes. Below is a detailed breakdown with examples for both eBGP and iBGP setups.

eBGP Configuration Example

Scenario:

• Router A (AS 65001) connects to Router B (AS 65002) via eBGP.
• The goal is to exchange routes between the two autonomous systems.

Configuration on Router A:

set protocols bgp group EBGP type external
set protocols bgp group EBGP local-address 192.168.1.1
set protocols bgp group EBGP peer-as 65002
set protocols bgp group EBGP neighbor 192.168.1.2

Configuration on Router B:

set protocols bgp group EBGP type external
set protocols bgp group EBGP local-address 192.168.1.2
set protocols bgp group EBGP peer-as 65001
set protocols bgp group EBGP neighbor 192.168.1.1

Explanation:

1. type external:
   • Indicates this is an eBGP session.
2. local-address:
   • Specifies the source address for BGP messages.
3. peer-as:
   • Defines the remote AS number.
4. neighbor:
   • Identifies the peer's IP address.

iBGP Configuration Example

Scenario:

• Router A, B, and C belong to AS 65001.
• A full-mesh iBGP is required for route propagation.

Configuration on Router A:

set protocols bgp group IBGP type internal
set protocols bgp group IBGP local-address 10.0.0.1
set protocols bgp group IBGP neighbor 10.0.0.2
set protocols bgp group IBGP neighbor 10.0.0.3

Configuration on Router B:

set protocols bgp group IBGP type internal
set protocols bgp group IBGP local-address 10.0.0.2
set protocols bgp group IBGP neighbor 10.0.0.1
set protocols bgp group IBGP neighbor 10.0.0.3

Configuration on Router C:

set protocols bgp group IBGP type internal
set protocols bgp group IBGP local-address 10.0.0.3
set protocols bgp group IBGP neighbor 10.0.0.1
set protocols bgp group IBGP neighbor 10.0.0.2

Key Points:

• iBGP requires a full mesh unless route reflectors are implemented.
• Routes learned from one iBGP peer are not advertised to another iBGP peer.

Route Reflector Example

Scenario:

• Router A acts as a route reflector.
• Routers B and C are its clients.

Configuration on Router A (Route Reflector):

set protocols bgp group IBGP type internal
set protocols bgp group IBGP neighbor 10.0.0.2 route-reflector-client
set protocols bgp group IBGP neighbor 10.0.0.3 route-reflector-client

Configuration on Routers B and C:

set protocols bgp group IBGP type internal
set protocols bgp group IBGP neighbor 10.0.0.1

Key Points:

• The route reflector advertises routes between its clients.
• Reduces the need for a full-mesh topology.

8. BGP Best Practices

• Path Selection Optimization:

  • Adjust attributes such as Local Preference, AS_PATH, and MED to control route selection.

• Security:

  • Use prefix-lists and route-maps to filter routes.

  • Implement BGP peer authentication using MD5:

    set protocols bgp group EBGP authentication-key securekey
    

• Route Aggregation:

  • Aggregate multiple prefixes to simplify route advertisements:

    set policy-options policy-statement AGGREGATE term 1 from route-filter 192.168.0.0/16 orlonger
    set policy-options policy-statement AGGREGATE term 1 then accept
    set protocols bgp group EBGP export AGGREGATE
    

• Monitoring:

  • Use BGP troubleshooting commands to check peer status and routing table:

    show bgp neighbor
    show route protocol bgp
    

9. Troubleshooting BGP

BGP issues often arise from misconfigurations, attribute mismatches, or connectivity problems. Key steps for troubleshooting:

• Verify Neighbor State:

  show bgp neighbor
  

  • Check for states like Idle, Active, or Established.
  • Idle/Active indicates connection issues.

• Check Routes:

  show route protocol bgp
  

  • Verify that expected prefixes are present.

• Debugging:

  monitor start file bgp-log
  monitor stop
  

  • Captures detailed logs for analysis.

• Common Issues:

  1. AS Path Loops:
     • Occurs when a router sees its own AS in the AS_PATH.
     • Use as-path-ignore cautiously to avoid loop prevention mechanisms.
  2. NEXT_HOP Unreachable:
     • Ensure the NEXT_HOP attribute is reachable.

Summary of BGP Key Topics

1. BGP Message Types:
   • Open, Update, Keepalive, Notification.
2. BGP Attributes:
   • AS_PATH, NEXT_HOP, ORIGIN, COMMUNITY, MED.
3. Route Selection Process:
   • Weight > Local Preference > AS_PATH > MED > eBGP over iBGP.
4. iBGP and eBGP:
   • iBGP: Within AS, full mesh or route reflector.
   • eBGP: Between ASes, uses TTL of 1.
5. BGP Communities:
   • no-export, no-advertise, local-AS.
6. Route Reflectors:
   • Simplify iBGP by centralizing updates.
7. Configuration:
   • Basic examples for eBGP, iBGP, and route reflectors.
8. Best Practices and Troubleshooting:
   • Secure, optimize, and monitor BGP sessions effectively.

Border Gateway Protocol (BGP) (Additional Content)

Overview

BGP is a path-vector routing protocol used to exchange routing information between autonomous systems (ASes). It is the core protocol of the internet, and also used within enterprises for inter-domain routing. BGP supports policy-based routing and uses attributes like AS_PATH, NEXT_HOP, and LOCAL_PREF to make route selection decisions.

1. iBGP Route Propagation Rule

While iBGP (Internal BGP) is used within a single AS, it has a strict rule that significantly impacts design and scalability:

iBGP-learned routes are not advertised to other iBGP peers.

• This loop prevention mechanism ensures routing stability.

• To ensure full reachability, networks must:

  • Use a full mesh of iBGP sessions, or

  • Deploy Route Reflectors to overcome scalability limitations.

This behavior contrasts with eBGP, where learned routes are freely propagated to other peers.

2. AS_PATH Loop Prevention

BGP uses the AS_PATH attribute to prevent routing loops across autonomous systems.

By default, a BGP router will reject any route that contains its own AS number in the AS_PATH.

• This simple but effective mechanism ensures that routes do not loop indefinitely between ASes.

• It’s visible in the routing table as a string of AS numbers.

• The as-path-ignore option (in Junos and other vendors) can override this behavior, but it should be used with extreme caution.

3. BGP Session State Machine

When establishing a BGP session, the protocol goes through a series of states defined by the BGP Finite State Machine (FSM). Understanding these states is crucial for troubleshooting peer establishment issues.

State	Description
Idle	Initial state. BGP waits for a Start event to begin TCP connection.
Connect	TCP connection initiated; waiting for response.
Active	TCP connection still being attempted (e.g., retry after Connect fails).
OpenSent	TCP connection established. Open message sent to peer.
OpenConfirm	Awaiting Keepalive message from peer after Open has been acknowledged.
Established	BGP session is fully established. Route updates can now be exchanged.

Troubleshooting Tip:

Use show bgp neighbor to see the current session state. Common failure points include:

• Stuck in Active: TCP connectivity issue (e.g., port 179 blocked).

• OpenSent/OpenConfirm: Misconfigured BGP parameters (e.g., AS number mismatch).

• Established flapping: Possibly due to Keepalive or Hold timer mismatches, or authentication failures.

Summary of Additions

Topic	Key Detail
iBGP Propagation Rule	iBGP does not advertise routes learned from other iBGP peers. Requires full mesh or route reflectors.
AS_PATH Loop Prevention	Routes containing the router's own AS are dropped by default to prevent loops.
BGP FSM States	Idle → Connect → Active → OpenSent → OpenConfirm → Established. Essential for troubleshooting BGP session issues.