Network Requirement
As shown in Figure. 1, BGP runs on all the switches.
An EBGP connection is established between Switch A and Switch B, and IBGP fullmesh connections are established between Switch B, Switch C, and Switch D.
Configure IBGP connections between Switch B, Switch C, and Switch D.
Configure an EBGP connection between Switch A and Switch B.
Figure 1. BGP configuration
Procedure
This section describes the steps of how to configure basic BGP functions on SwitchA, SwitchB, SwitchC and SwitchD.
Switch A
Step1 Configure the VLANs and VLAN interfaces.
admin@SwitchA# set vlans vlan-id 10 l3-interface 10 admin@SwitchA# set vlans vlan-id 20 l3-interface 20 admin@SwitchA# set interface gigabit-ethernet te-1/1/1 family ethernet-switching native-vlan-id 10 admin@SwitchA# set interface gigabit-ethernet te-1/1/2 family ethernet-switching native-vlan-id 20 admin@SwitchA# set vlan-interface interface 10 vif 10 address 192.168.10.1 prefix-length 24 admin@SwitchA# set vlan-interface interface 20 vif 20 address 192.168.20.1 prefix-length 24
Step2 Configure an EBGP connection.
admin@SwitchA# set protocols bgp bgp-id 1.1.1.1 admin@SwitchA# set protocols bgp local-as 100 admin@SwitchA# set protocols bgp peer 192.168.20.2 as 200 admin@SwitchA# set protocols bgp peer 192.168.20.2 local-ip 192.168.20.1 admin@SwitchA# set protocols bgp peer 192.168.20.2 next-hop-self true
Step3 Commit the configurations.
admin@SwitchA# commit
Switch B
Step1 Configure the VLANs and VLAN interfaces.
admin@SwitchB# set vlans vlan-id 20 l3-interface 20 admin@SwitchB# set vlans vlan-id 30 l3-interface 30 admin@SwitchB# set vlans vlan-id 40 l3-interface 40 admin@SwitchB# set interface gigabit-ethernet ge-1/1/2 family ethernet-switching native-vlan-id 20 admin@SwitchB# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching native-vlan-id 30 admin@SwitchB# set interface gigabit-ethernet ge-1/1/4 family ethernet-switching native-vlan-id 40 admin@SwitchB# set vlan-interface interface 20 vif 20 address 192.168.20.2 prefix-length 24 admin@SwitchB# set vlan-interface interface 30 vif 30 address 192.168.30.1 prefix-length 24 admin@SwitchB# set vlan-interface interface 40 vif 40 address 192.168.40.1 prefix-length 24
Step2 Configure EBGP and IBGP connections.
admin@SwitchB# set protocols bgp bgp-id 2.2.2.2 admin@SwitchB# set protocols bgp local-as 200 admin@SwitchB# set protocols bgp peer 192.168.20.1 as 100 admin@SwitchB# set protocols bgp peer 192.168.20.1 local-ip 192.168.20.2 admin@SwitchB# set protocols bgp peer 192.168.20.1 next-hop-self true admin@SwitchB# set protocols bgp peer 192.168.30.2 as 200 admin@SwitchB# set protocols bgp peer 192.168.30.2 local-ip 192.168.30.1 admin@SwitchB# set protocols bgp peer 192.168.30.2 next-hop-self true admin@SwitchB# set protocols bgp peer 192.168.40.2 as 200 admin@SwitchB# set protocols bgp peer 192.168.40.2 local-ip 192.168.40.1 admin@SwitchB# set protocols bgp peer 192.168.40.2 next-hop-self true
Step3 Commit the configurations.
admin@SwitchB# commit
Switch C
Step1 Configure the VLANs and VLAN interfaces.
admin@SwitchC# set vlans vlan-id 40 l3-interface 40 admin@SwitchC# set vlans vlan-id 50 l3-interface 50 admin@SwitchC# set interface gigabit-ethernet ge-1/1/4 family ethernet-switching native-vlan-id 40 admin@SwitchC# set interface gigabit-ethernet ge-1/1/5 family ethernet-switching native-vlan-id 50 admin@SwitchC# set vlan-interface interface 40 vif 40 address 192.168.40.2 prefix-length 24 admin@SwitchC# set vlan-interface interface 50 vif 50 address 192.168.50.2 prefix-length 24
Step2 Configure the IBGP connection.
admin@SwitchC# set protocols bgp bgp-id 3.3.3.3 admin@SwitchC# set protocols bgp local-as 200 admin@SwitchC# set protocols bgp peer 192.168.40.1 as 200 admin@SwitchC# set protocols bgp peer 192.168.40.1 local-ip 192.168.40.2 admin@SwitchC# set protocols bgp peer 192.168.40.1 next-hop-self true admin@SwitchC# set protocols bgp peer 192.168.50.1 as 200 admin@SwitchC# set protocols bgp peer 192.168.50.1 local-ip 192.168.50.2 admin@SwitchC# set protocols bgp peer 192.168.50.1 next-hop-self true
Step3 Commit the configurations.
admin@SwitchC# commit
Switch D
Step1 Configure the VLANs and VLAN interfaces.
admin@SwitchD# set vlans vlan-id 30 l3-interface 30 admin@SwitchD# set vlans vlan-id 50 l3-interface 50 admin@SwitchD# set interface gigabit-ethernet ge-1/1/3 family ethernet-switching native-vlan-id 30 admin@SwitchD# set interface gigabit-ethernet ge-1/1/5 family ethernet-switching native-vlan-id 50 admin@SwitchD# set vlan-interface interface 30 vif 40 address 192.168.30.2 prefix-length 24 admin@SwitchD# set vlan-interface interface 50 vif 50 address 192.168.50.1 prefix-length 24
Step2 Configure the IBGP connection.
admin@SwitchD# set protocols bgp bgp-id 4.4.4.4 admin@SwitchD# set protocols bgp local-as 200 admin@SwitchD# set protocols bgp peer 192.168.30.1 as 200 admin@SwitchD# set protocols bgp peer 192.168.30.1 local-ip 192.168.30.2 admin@SwitchD# set protocols bgp peer 192.168.30.1 next-hop-self true admin@SwitchD# set protocols bgp peer 192.168.50.2 as 200 admin@SwitchD# set protocols bgp peer 192.168.50.2 local-ip 192.168.50.1 admin@SwitchD# set protocols bgp peer 192.168.50.2 next-hop-self true
Step3 Commit the configurations.
admin@SwitchD# commit
Viewing BGP Peer Status on Switch B
admin@SwitchB# run show bgp peers detail Peer 2: local 192.168.20.2/179 remote 192.168.20.1/179 Peer ID: 1.1.1.1 Peer State: ESTABLISHED Admin State: START Negotiated BGP Version: 4 Peer AS Number: 100 Updates Received: 20, Updates Sent: 2 Messages Received: 634, Messages Sent: 611 Time since last received update: 1685 seconds Number of transitions to ESTABLISHED: 1 Time since last entering ESTABLISHED state: 15995 seconds Retry Interval: 120 seconds Hold Time: 90 seconds, Keep Alive Time: 30 seconds Configured Hold Time: 90 seconds, Configured Keep Alive Time: 30 seconds Minimum AS Origination Interval: 0 seconds Minimum Route Advertisement Interval: 0 seconds Peer 2: local 192.168.30.1/179 remote 192.168.30.2/179 Peer ID: 4.4.4.4 Peer State: ESTABLISHED Admin State: START Negotiated BGP Version: 4 Peer AS Number: 100 Updates Received: 20, Updates Sent: 2 Messages Received: 634, Messages Sent: 611 Time since last received update: 1685 seconds Number of transitions to ESTABLISHED: 1 Time since last entering ESTABLISHED state: 15995 seconds Retry Interval: 120 seconds Hold Time: 90 seconds, Keep Alive Time: 30 seconds Configured Hold Time: 90 seconds, Configured Keep Alive Time: 30 seconds Minimum AS Origination Interval: 0 seconds Minimum Route Advertisement Interval: 0 seconds Peer 3: local 192.168.40.1/179 remote 192.168.40.2/179 Peer ID: 3.3.3.3 Peer State: ESTABLISHED Admin State: START Negotiated BGP Version: 4 Peer AS Number: 100 Updates Received: 20, Updates Sent: 2 Messages Received: 634, Messages Sent: 611 Time since last received update: 1685 seconds Number of transitions to ESTABLISHED: 1 Time since last entering ESTABLISHED state: 15995 seconds Retry Interval: 120 seconds Hold Time: 90 seconds, Keep Alive Time: 30 seconds Configured Hold Time: 90 seconds, Configured Keep Alive Time: 30 seconds Minimum AS Origination Interval: 0 seconds Minimum Route Advertisement Interval: 0 seconds
Configuring Switch A to Advertise Route 192.168.10.0/24
admin@SwitchA# set policy policy-statement direct-to-bgp term t1 from protocol connected admin@SwitchA# set policy policy-statement direct-to-bgp term t1 from network4 192.168.10.0/24 admin@SwitchA# set policy policy-statement direct-to-bgp term t1 then accept admin@SwitchA# set protocols bgp export direct-to-bgp admin@SwitchA# commit
View the BGP routing table of Switch B:
admin@SwitchD# run show bgp routes Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- *> 192.168.10.0/24 192.168.20.1 1.1.1.1 100 ? admin@SwitchD#
View the BGP routing table of Switch C:
admin@SwitchD# run show bgp routes Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- 192.168.10.0/24 192.168.20.1 2.2.2.2 100 ? admin@SwitchD#
The preceding command output display that the route to destination 192.168.10.0/24 becomes invalid because the next hop address of this route is unreachable.
Configuring Switch B to Advertise a Connected Route
admin@SwitchB# set policy policy-statement direct-to-bgp term t1 from protocol connected admin@SwitchB# set policy policy-statement direct-to-bgp term t1 then accept admin@SwitchB# set protocols bgp export direct-to-bgp admin@SwitchB# commit
Ping 192.168.10.1 on Switch C:
admin@SwitchC# run ping 192.168.10.1 PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data. 64 bytes from 192.168.10.1: icmp_req=1 ttl=63 time=4.68 ms 64 bytes from 192.168.10.1: icmp_req=2 ttl=63 time=4.46 ms 64 bytes from 192.168.10.1: icmp_req=3 ttl=63 time=5.35 ms 64 bytes from 192.168.10.1: icmp_req=4 ttl=63 time=4.52 ms 64 bytes from 192.168.10.1: icmp_req=5 ttl=63 time=4.51 ms 192.168.10.1 ping statistics — 5 packets transmitted, 5 received, 0% packet loss, time 4017ms rtt min/avg/max/mdev = 4.460/4.709/5.358/0.338 ms
View the BGP routing table of Switch C:
admin@SwitchC# run show bgp routes Status Codes: * valid route, > best route Origin Codes: i IGP, e EGP, ? incomplete Prefix Nexthop Peer AS Path ------ ------- ---- ------- 192.168.10.0/24 192.168.20.1 2.2.2.2 100 ? *> 192.168.20.0/24 192.168.40.1 2.2.2.2? *>192.168.30.0/24 192.168.40.1 2.2.2.2?