BGP Configuration in Details

BGP configuration examples https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-K...
Border Gateway Protocol (BGP) > BGP configuration examples next
BGP configuration examples

BGP basic configuration
Network requirements
In the following network, run eBGP between Switch A and Switch B and iBGP between Switch B and Switch C so that Switch
C can access the network 8.1.1.0/24 connected to Router A.
Network diagram for BGP basic configuration
Configuration procedure
1. Configure IP addresses for interfaces (omitted.)
2. Configure iBGP.
To prevent route flapping caused by port state changes, this example uses loopback interfaces to establish iBGP
connections.
Because loopback interfaces are virtual interfaces, you need to use the peer connect-interface command to
specify the loopback interface as the source interface for establishing BGP connections.
Enable OSPF in AS 65009 to ensure that Switch B can communicate with Switch C through loopback interfaces.
# Configure Switch B
HP Switch(config)# router bgp 65009
HP Switch(bgp)# bgp router-id 2.2.2.2
HP Switch(bgp)# neighbor 3.3.3.3 remote-as 65009
HP Switch(bgp)# exit
HP Switch(config)# router ospf
HP Switch(ospf)# enable
HP Switch(ospf)# area 0
HP Switch(ospf)# network 2.2.2.2/32
HP Switch(ospf)# exit
HP Switch(config)# vlan 300
HP Switch(vlan-300)# ip ospf
# Configure Switch C
HP Switch(bgp)# neighbor 2.2.2.2 connect-interface loopback 0
1 of 12 17/09/2021, 2:00 PM

HP Switch(config)# vlan 300
HP Switch(vlan-300)# ip ospf
HP Switch(vlan-300)# show ip bgp summary
Peer Information
Remote Address Remote-AS Local-AS State Admin Status

-------------- --------- -------- ------------ -----
2.2.2.2 65009 65009 Established Start
The output information shows that Switch C has established an iBGP peer relationship with Switch B.
3. Configure eBGP.
The eBGP peers, Switch A and Switch B (usually belonging to different carriers), are located in different ASs.
Their loopback interfaces are not reachable to each other, so directly connected interfaces are used for establishing
BGP sessions.
To enable Switch C to access the network 8.1.1.0/24 that is connected directly to Switch A, add network 8.1.1.0/24
to the BGP routing table of Switch A.
# Configure Switch A.
HP Switch(bgp)# network 8.1.1.1/24
# Configure Switch B.
# Show IP bgp peer information on Switch B.

HP Switch(config)# show ip bgp summary
Peer Information
Remote Address Remote-AS Local-AS State Admin Status

-------------- --------- -------- -------- ------------
The output shows that Switch B has established an iBGP peer relationship with Switch C and an eBGP peer relationship
with Switch A.
# Display the BGP routing table on Switch A.

HP Switch(bgp)# show ip bgp
Local AS : 100
Local Router-id : 20.0.0.1
BGP Table Version : 0
Status codes: * - valid, > - best, i - internal, e -
external, s - stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Nexthop Metric LocalPref Weight AsPath

----------------------------------------------------------
*> 8.1.1.0/24 0 32768 I
*> 8.1.1.0/24 0.0.0.0 0 0 I
# Display the BGP routing table on Switch B.

HP Switch# show ip bgp
Local AS : 100

Status codes: * - valid, > - best, i - internal, e - external, s - stale
2 of 12 17/09/2021, 2:00 PM

---------------------------------------------------------
*>e 8.1.1.0/24 0 0 65008i
# Display the BGP routing table on Switch C.

HP Switch(bgp)# show ip bgp
Local AS : 100


---------------------------------------------------------
*>i 8.1.1.0/24 0 0 65008i
NOTE: From the above outputs, you see that Switch A has not learned a route to AS 65009, and Switch C has
learned network 8.1.1.0 but the next hop 3.1.1.2 is unreachable, so the route is invalid.
4. Redistribute connected routes.
Configure BGP to redistribute direct routes on Switch B, so that Switch A can obtain the route to 9.1.1.0/24 and Switch
C can obtain the route to 3.1.1.0/24.
HP Switch(bgp)# redistribute connected
# Display the BGP routing table on Switch A.

HP Switch# show ip bgp
Local AS : 65009


---------------------------------------------------------
*>e 2.2.2.2/32 3.1.1.1 0 0 65009?
*>e 3.1.1.0/24 3.1.1.1 0 0 65009?
*>e 8.1.1.0/24 0 0 65008i
*>e 8.1.1.0/24 0 0 65008i
Two routes 2.2.2.2/32 and 9.1.1.0/24 have been added in Switch A’s routing table.
# Display the BGP routing table on Switch C.

HP Switch(config)# show ip bgp
Local AS : 65009

-------------------------------------------------------
*>e 2.2.2.2/32 9.1.1.1 0 100 I
*>e 3.1.1.0/24 9.1.1.1 0 100 I
*>e 8.1.1.0/24 0 0 65008i
3 of 12 17/09/2021, 2:00 PM
*e 9.1.1.0/24 0 0 65008i
*>e 9.1.1.0/24 0 0 65008i
Route 8.1.1.0 becomes valid with the next hop as Switch A.
5. Verification.
Route filter configuration

In the following figure, Switch B establishes eBGP connections with Switch A and C. Configure the No_Export community
attribute on Switch A so that routes from AS 10 are not advertised by AS 20 to any other AS.
Network diagram for BGP community configuration
2. Configure eBGP.
HP Switch(bgp)# network 9.1.1.0/255.255.255.0/8
HP Switch(config)# bgp 20
# Configure Switch C.

HP Switch(config)# show ip bgp 9.1.1.0
4 of 12 17/09/2021, 2:00 PM
Local AS : 20 Local Router-id : 2.2.2.2

Network : 9.1.1.0/24 Nexthop : 200.1.2.1

Peer : 200.1.2.1 Origin : igp
Metric : 0 Local Pref :
Weight : 0 Calc. Local Pref : 100
Valid : Yes Type : external
Stale : No
Best : Yes (Only Route Available)
AS-Path : 100
Communities :
Switch B advertised routes to Switch C in AS 30.
# Display the routing table on Switch C.

Local AS : 30


-------------------------------------------------------
*>i 9.1.1.0/24 200.1.3.1 0 100 10i
Switch C learned route 9.1.1.0/24 from Switch B.
3. Configure the BGP community.
# Configure a routing policy.

route-map bgp-out permit seq 10
HP Switch(route-map-bgp-out)# set community no-export
HP Switch(route-map-bgp-out)# exit
# Apply the routing policy.

HP Switch(bgp)# neighbor 200.1.2.2 route-map bgp-out out
# Display the route on Switch B.

HP Switch(config)# show ip bgp 9.1.1.0/24
Local AS : 20 Local Router-id : 2.2.2.2

Network : 9.1.1.0/24 Nexthop : 200.1.2.1

Peer : 200.1.2.1 Origin : igp Metric : 0 Local Pref : Weight
: 0 Calc. Local Pref : 100
Valid : Yes Type : external
Stale : No
Best : Yes (Only Route Available) AS-Path : 100
Communities: no-export
# Display the routing table on Switch C.

HP Switch# show ip bgp 9.1.1.0/24
The route 9.1.1.0/24 is not available in the routing table of Switch C.
BGP route reflector configuration

In the following figure, all switches run BGP.
There is an eBGP connection between Switch A and Switch B. There are iBGP connections between SwitchB and
5 of 12 17/09/2021, 2:00 PM
Switch C, and between Switch C and Switch D.
Switch C is a route reflector with clients Switch B and D.
Switch D can learn route 1.0.0.0/8 from Switch C.
Network diagram for BGP route reflector configuration
2. Configure BGP connections.
# Add network 1.0.0.0/8 to the BGP routing table.

HP Switch(bgp)# network 1.0.0.0
HP Switch(bgp)# neighbor 193.1.1.1 next-hop-self
# Configure Switch D.
3. Configure the route reflector.
6 of 12 17/09/2021, 2:00 PM

HP Switch(bgp)# neighbor 193.1.1.2 route-reflector-client
HP Switch(bgp)# neighbor 194.1.1.2 route-reflector-client
4. Verify the above configuration.

Local AS : 200


------------------------------------------------------------
*>i 1.0.0.0/24 200.1.3.1 0 0 100i
# Display the BGP routing table on Switch D.

Local AS : 200


-------------------------------------------------------
*>e 1.0.0.0/24 200.1.3.1 0 100 100i
Switch D learned route 1.0.0.0/8 from Switch C.
BGP path selection configuration

In the figure below, all switches run BGP. eBGP connections are between Switch A and Switch B, and between Switch
A and Switch C. iBGP connections are between Switch B and Switch D, and between Switch C and Switch D.
OSPF is the IGP protocol in AS 200.
Configure the routing policies. Switch D should use the route 1.0.0.0/8 from Switch C as the optimal route.
Network diagram for BGP path selection configuration
7 of 12 17/09/2021, 2:00 PM
Device Interface IP address Device Interface IP address

Switch A Vlan101 1.0.0.0/8 Switch D Vlan400 195.1.1.1/24
Vlan100 192.1.1.1/24 Vlan300 194.1.1.1/24
Vlan200 193.1.1.1/24 Switch C Vlan400 195.1.1.2/24
Switch B Vlan100 192.1.1.2/24 Vlan200 193.1.1.2/24
Vlan300 194.1.1.2/24
2. Configure OSPF on Switch B, C, and D.
HP Switch(ospf)# network 192.1.1.0/ 0.0.0.255
3. Configure BGP connections.
# Add network 1.0.0.0/8 to the BGP routing table on Switch A.

8 of 12 17/09/2021, 2:00 PM
4. Configure attributes for route 1.0.0.0/8, making Switch D give priority to the route learned from Switch C.
# Configure a higher MED value for the route 1.0.0.0/8 advertised from Switch A to peer 192.1.1.2.
# Define a prefix-list to permit route 1.0.0.0/8.

HP Switch(config)# ip prefix-list pl_1 permit 1.0.0.0/24
# Define two routing policies, apply_med_50, which sets the MED for route 1.0.0.0/8 to 50, and apply_med_100, which
sets the MED for route 1.0.0.0/8 to 100.
HP Switch(config)# route-map apply_med_50 permit
HP Switch(route-map-apply_med_50)# match ip address prefix-list pl_1
HP Switch(route policy)# set metric 50
HP Switch(route policy)route-map apply_med_50 permit seq 20
HP Switch(route policy)# exit
HP Switch(config)# route-map apply_med_100 permit

HP Switch(route policy)# match ip address prefix-list pl_1
HP Switch(route policy)# set metric 100
HP Switch(route policy)# route-map apply_med_100 permit seq 20
HP Switch(route policy)# exit
# Apply routing policy apply_med_50 to the route advertised to peer 193.1.1.2 (Switch C), and apply_med_100 to the
route advertised to peer 192.1.1.2 (Switch B.)
HP Switch(bgp)# neighbor 193.1.1.2 route-map apply_med_50 out
HP Switch(bgp)# neighbor 192.1.1.2 route-policy apply_med_100 out
# Display the BGP routing table on Switch D.

Local AS : 100


-------------------------------------------------------
*>e 1.0.0.0/24 194.1.1.2 50 0 100i
*>e 1.0.0.0/24 195.1.1.2 100 0 100i
You can ensure that route 1.0.0.0/8 is the optimal route. Configure different local preferences on Switch B and C for
route 1.0.0.0/ 8, making Switch D give priority to the route from Switch C.
# Define an ip prefix-list on Router C, permitting route 1.0.0.0/8.

HP Switch(config)# ip prefix-list pl_1 permit 1.0.0.0/8
# Configure a routing policy named localpref on Switch C, setting the local preference of route 1.0.0.0/8 to 200 (the
default is 100.)
HP Switch(config)# route-map localpref permit seq 10
HP Switch(route-policy)# match ip address prefix-list pl_1
HP Switch(route-policy)# set local-preference 200
HP Switch(route-policy)# route-map localpref permit seq 20
# Apply routing policy localpref to routes from peer 193.1.1.1.
9 of 12 17/09/2021, 2:00 PM

HP Switch(bgp)# neighbor 193.1.1.1 route-map localpref in
# Display the routing table on Switch D.

Local AS : 100


-------------------------------------------------------
*>e 1.0.0.0/24 200.1.3.1 200 0 100i
* i 1.0.0.0/24 100 0 100i
You can see that route 1.0.0.0/8 from Switch D to Switch C is the optimal route.
BGP GR configuration
In the following figure, all switches are BGP switches. There is a eBGP connection between Switch A and Switch B. Switch B
and Switch C are connected over an iBGP connection. Enable GR for BGP so that the communication between Switch A and
Switch C is not affected when an active/ standby main board switchover occurs on Switch B.
Network diagram for BGP GR configuration
1. Configure Switch A.
# Configure IP addresses for interfaces (omitted.)
# Configure the eBGP connection.

# Configure BGP GR stalepath-timeout (optional.)

HP Switch(bgp)# bgp graceful-restart stalepath-time 360
# Add network 8.0.0.0/8 to the BGP routing table.

# Enable GR for BGP Peer.

HP Switch(bgp)# neighbor 200.1.1.1 graceful-restart
10 of 12 17/09/2021, 2:00 PM
2. Configure Switch B.
# Configure the eBGP connection.

HP Switch(bgp)# router bgp 65009
# Configure BGP GR restart-time and stalepath-timeout (Optional.)

HP Switch(bgp)# bgp graceful-restart restart-time 120
stalepath-time 360
# Configure the iBGP connection.

# Configure BGP to redistribute direct routes.

# Enable GR capability for BGP Peers.

# Configure BGP for non-stop forwarding

HP Switch(bgp)# non-stop
3. Configure Switch C.
# Configure the iBGP connection.

# Configure BGP to redistribute direct routes.

BGP Configuration Example
# Enable GR for BGP Peer.

Verification
After completing the above configuration, perform an active/standby switchover on Switch B. Switch A and Switch C should
be able to ping each other without any packet drops. Also ensure that there are no flaps of BGP learned routes on the peer
switches.
prev up next
11 of 12 17/09/2021, 2:00 PM
Displaying information about BGP configuration home BGP show routines
Copyright © 2015 Hewlett-Packard Development Company, L.P.
12 of 12 17/09/2021, 2:00 PM

BGP Configuration in Details

Uploaded by

Copyright:

Available Formats

You might also like

BGP Configuration in Details

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BGP Configuration in Details

Uploaded by

Copyright:

Available Formats

BGP configuration examples https://techhub.hpe.com/eginfolib/networking/docs/switches/K-KA-K...

Border Gateway Protocol (BGP) > BGP configuration examples next

BGP configuration examples

Network diagram for BGP basic configuration

1. Configure IP addresses for interfaces (omitted.)

HP Switch(ospf)# network 9.1.1.0/24

Remote Address Remote-AS Local-AS State Admin Status

# Show IP bgp peer information on Switch B.

Remote Address Remote-AS Local-AS State Admin Status

# Display the BGP routing table on Switch A.

Network Nexthop Metric LocalPref Weight AsPath

# Display the BGP routing table on Switch B.

BGP Table Version : 0

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Nexthop Metric LocalPref Weight AsPath

# Display the BGP routing table on Switch C.

BGP Table Version : 0

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Nexthop Metric LocalPref Weight AsPath

4. Redistribute connected routes.

# Display the BGP routing table on Switch A.

BGP Table Version : 0

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Nexthop Metric LocalPref Weight AsPath

# Display the BGP routing table on Switch C.

BGP Table Version : 1

Status codes: * - valid, > - best, i - internal, e - external, s - stale

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Nexthop Metric LocalPref Weight AsPath

Route 8.1.1.0 becomes valid with the next hop as Switch A.

Route filter configuration

Network diagram for BGP community configuration

1. Configure IP addresses for interfaces (omitted.)

# Display the BGP routing table on Switch B.

Local AS : 20 Local Router-id : 2.2.2.2

Network : 9.1.1.0/24 Nexthop : 200.1.2.1

Switch B advertised routes to Switch C in AS 30.

# Display the routing table on Switch C.

BGP Table Version : 1

Origin codes: i - IGP, e - EGP, ? - incomplete

Network Nexthop Metric LocalPref Weight AsPath

Switch C learned route 9.1.1.0/24 from Switch B.

3. Configure the BGP community.

# Configure a routing policy.

# Apply the routing policy.

# Display the route on Switch B.

Local AS : 20 Local Router-id : 2.2.2.2

Network : 9.1.1.0/24 Nexthop : 200.1.2.1

# Display the routing table on Switch C.

The route 9.1.1.0/24 is not available in the routing table of Switch C.

BGP route reflector configuration

In the following figure, all switches run BGP.

Switch C, and between Switch C and Switch D.

Switch C is a route reflector with clients Switch B and D.

Switch D can learn route 1.0.0.0/8 from Switch C.

Network diagram for BGP route reflector configuration

1. Configure IP addresses for interfaces (omitted.)

2. Configure BGP connections.