Professional Documents
Culture Documents
WRITTEN
BY:
ASHWIN KOHLI
CCIE
# 8877
Trademark Acknowledgments
All terms mentioned in this book that are known to be trademarks or service marks have been appropriately
capitalized. Netcg, Inc. or Network Learning, Inc. cannot attest to the accuracy of this information. Use of
a team in this book should not be regarded as affecting the validity of any trademark or service mark.
Feedback Information
At Network Learning Inc., our goal is to create in-depth technical books of the highest quality and value.
Each book is crafted with care and precision, undergoing rigorous development that involves the unique
expertise of members from the professional technical community.
Readers feedback is a natural continuation of this process. If you have any comments regarding how we
could improve the quality of this book, or otherwise alter it to better suit your needs, you can contact us
through email at sales@ccbootcamp.com. Please make sure to include the book title in your message.
We greatly appreciate the assistance.
BGP
TABLE OF CONTENTS
1.0
2.0
3.0
4.0
5.0
6.0
7.0
8.0
9.0
10.0
64
11.0
12.0
13.0
14.0
15.0
16.0
SAMPLE DOCUMENT
17.0
18.0
19.0
20.0
21.0
22.0
23.0
24.0
25.0
26.0
27.0
28.0
29.0
30.0
31.0
32.0
33.0
BGP
34.0
35.0
36.0
SAMPLE DOCUMENT
23.0
BGP Soft-Reconfiguration
VLAN 11
137.1.1 .0 /0
AS 21994
AS 714
Frame-relay
137.1.200.1
Router1
137.1.200.2
Router2
1. Configure the frame-relay using only physical interfaces on all routers. Create a DLCI from
Router1 to reach Router2.
2. Configure an EBGP peer relationship between Router1 to Router2.
3. Advertise the following networks from Router1 into BGP
a. Fe0/0 - 137.1.1.0 /24
b. Loopback 0 - 11.11.11.0 /24
c. Loopback 1 33.33.33.0 /24
4. Configure a prefix-list in Router1 to initially disallow both the loopbacks from being
advertised only to Router2 and to allow all other networks to be advertised.
5. Test your configuration in Router2 that you are only receiving 137.1.1.0 subnet.
6. Now, change the prefix-list to advertise 137.1.1.0 and loopback 1 subnet, but continue to still
disallow loopback 0 subnet from being advertised.
7. Test your configuration in Router2. Which routes are you receiving?
8. Clear the bgp peer relationship on Router1.
9. Test you configuration in Router2. Which routes are you receiving?
10. Now configure soft-reconfiguration on both routers
11. Redo Step 4, 5, 6 and 7 above.
12. Now only do a soft clear for the bgp relationship?
13. Test your configuration in Router2. Are you receiving both the routes?
BGP
ANSWER
Whenever there is a change in the routing policy (e.g. new routes being added or old
routes deleted being or changes to route attributes being advertised via BGP), the BGP
session must be reset (cleared) for the new policy to take effect and the routing table to be
reconfigured. Using a hard reset to clear a BGP session can have a negative impact on
network operation as whole BGP database has to be re-learnt from the BGP neighbors.
Soft reset is recommended because it allows routing table policies to be reconfigured and
activated without clearing the BGP session. Soft reset is done on a per-neighbor basis.
Soft resets can be inbound or outbound:
When soft reset is used to generate inbound updates from a neighbor, it is called
dynamic inbound soft reset.
When soft reset is used to send a new set of updates to a neighbor, it is called
outbound soft reset.
Router1
Interface loopback 0
Ip address 11.11.11.11 255.255.255.0
Interface loopback 1
Ip address 33.33.33.33 255.255.255.0
Interface f0/0
Ip address 137.1.1.1 255.255.255.0
Interface s0/0
Ip address 137.1.200.1 255.255.255.0
Encapsulation frame-relay
No frame-relay inverse-arp
Frame-relay map ip 137.1.200.2 101 broadcast
Router bgp 21994
No synchronization
No auto-summary
Bgp log-neighbor-changes
Network 137.1.1.0 mask 255.255.255.0
Neighbor 137.1.200.2 remote-as 714
Neighbor 137.1.200.2 description <<< EBGP peer with Router2 >>>
Neighbor 137.1.200.2 next-hop-self
Neighbor 137.1.200.2 soft-reconfiguration inbound
Neighbor 137.1.200.2 prefix-list 1 out
ip prefix-list 1 seq 1 deny 11.11.11.0/24
ip prefix-list 1 seq 2 deny 33.33.33.0/24
ip prefix-list 1 seq 3 permit 0.0.0.0/0 le 32
SAMPLE DOCUMENT
Router2
Interface s0/0
Ip address 137.1.200.2 255.255.255.0
Encapsulation frame-relay
No frame-relay inverse-arp
Frame-relay map ip 137.1.200.1 110 broadcast
Router bgp 714
No synchronization
No auto-summary
Bgp log-neighbor-changes
Neighbor 137.1.200.1 remote-as 21994
Neighbor 137.1.200.1 description <<< EBGP peer with Router1>>>
Neighbor 137.1.200.1 soft-reconfiguration inbound
The following shows the output BEFORE the soft-reconfiguration configuration and the
prefix-list is blocking both the loopback addresses from being advertised.
Router1 has established an EBGP relationship with Router2
!Because of the Pre-fix list in Router1, Router2 only receives the subnet 137.1.1.0
10
BGP
<output truncated>
!The original configuration blocking the two loopback addresses
ip prefix-list 1 seq 1 deny 11.11.11.0/24
ip prefix-list 1 seq 2 deny 33.33.33.0/24
ip prefix-list 1 seq 3 permit 0.0.0.0/0 le 32
!
!
<output truncated.>
router1#config t
Enter configuration commands, one per line. End with CNTL/Z.
router1(config)#no ip prefix-list 1 seq 2 deny 33.33.33.0/24
!There has been a change in the BGP routing policy, but Router2 still does not show the updated
policy being advertised from Router1.
The following shows the output AFTER the soft-reconfiguration configuration and the
prefix-list is blocking both the loopback addresses from being advertised.
Router1 has established an EBGP relationship with Router2
SAMPLE DOCUMENT
11
!Because of the Pre-fix list in Router1, Router2 only receives the subnet 137.1.1.0
!The a soft clear is done to the BGP relationship was cleared in Router1. You can either
clear it on Router2 inwards or on Router1 outwards.
router1#clear ip bgp * soft out
12
router1#
or
router2#clear ip bgp * soft in
router2#
!Router2 now receives the subnet
BGP
SAMPLE DOCUMENT
13