SlideShare a Scribd company logo

Bgp Basic Labs

Download as PPT, PDF
S
sami36

The document discusses a basic BGP lab scenario to demonstrate BGP configuration and operation. It describes a network with two ISPs connected to an AS through two boundary routers. In the initial scenario, EBGP is configured between the ISPs and boundary routers, with IGP (RIPv2) routing within the AS. The boundary routers cannot reach networks attached to the opposite ISP due to the lack of IBGP. Configuring IBGP allows the boundary routers to exchange routes and reach all networks.

TechnologyEducation
1 of 77
Downloaded 163 times
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
Cabrillo College Basic BGP Lab Examples Rick Graziani, Instructor November 15, 2001
Note to instructors If you have downloaded this presentation from the Cisco Networking Academy Community FTP Center, this may not be my latest version of this PowerPoint. For the latest PowerPoints for all my CCNA, CCNP, and Wireless classes, please go to my web site: http://www.cabrillo.edu/~rgraziani/ The username is cisco and the password is perlman for all of my materials. If you have any questions on any of my materials or the curriculum, please feel free to email me at graziani@cabrillo.edu (I really don’t mind helping.) Also, if you run across any typos or errors in my presentations, please let me know. I will add “(Updated – date )” next to each presentation on my web site that has been updated since these have been uploaded to the FTP center. Thanks! Rick
Objective These lab examples are not meant to demonstrate proper or realistic BGP configurations, nor does it include all the necessary commands to ensure proper routing operation. The objective of these examples are to show some of the basic BGP configuration commands and their affect on a network, including wrong configurations or misconfigurations. Hopefully this series of configurations and outputs will help explain the how BGP is implemented and its operation.
Our Scenario
Why IBGP? In order for the boundary routers SanJose1 and SanJose2 to exchange BGP routes that they learn from ISP1 and ISP2 respectively, they must do one of the following: Redistribution – Not recommended! Redistribute from BGP into the IGP (RIPv2) so those routes get propagated to the other boundary router. Redistribute from IGP (RIPv2) to BGP to learn routes from the other boundary router or the use of BGP network statements. Disadvantages : Can be a lot of routes being injected into the IGP; may also require the use of route filters so not all routes are injected into the IGP or back out to the other ISP. “ With very few exceptions, interior BGP (IBGP) – BGP between peers in the same AS – is used only in multihomed scenarios.” – Doyle
In order for the boundary routers SanJose1 and SanJose2 to exchange BGP routes that they learn from ISP1 and ISP2 respectively, they must do one of the following: IBGP This allows the boundary routers to share EBGP routes without the redistributing via an IGP. Requires: Synchronization : Can’t advertise via EBGP if the boundary router doesn’t have it in its IGP routing table because the other IGP routers will drop it. (Can turn this off if fully meshed IBGP or non-transit AS!) Must know how to reach the next hop address of the route. (example coming!) Why IBGP? “ With very few exceptions, interior BGP (IBGP) – BGP between peers in the same AS – is used only in multihomed scenarios.” – Doyle
 
Setup RIPv2 running within AS200 10.1.0.0/24 is between SanJose1 and ISP1’s 10.2.0.0/24 networks, both of which are part of 10.0.0.0/8 classful network. RIPv2 was chosen because this will create a different situation than with the two different Class B networks between SanJose2 and ISP2.
Scenario A: Step #1 – EBGP and IGP (RIPv2) EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200 RIP network statements only include those networks in AS200 No IBGP has been configured. There are no static routes.
Results : AS 200 Boundary (SanJose1 and SanJose2) routers can ping peer ISP networks AS 200 Boundary (SanJose1 and SanJose2) routers can NOT ping opposite ISP networks (SanJose1 can not ping 172.16.1.1) ISP routers (ISP1 and ISP2) can ping remote peer’s attached networks only, NOT SanJose3 network (we will see why in a moment). Successful pings
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 SanJose2 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 172.30.1.1 remote-as 300
ISP1#show ip route 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:25:16 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 192.168.1.0 10.1.0.2 0 0 200 i ------------------------------------------------------------------------ ISP2#show ip route   172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:30:51 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISPs only see the BGP routes distributed by themselves and their peers in their BGP tables.
SanJose1#show ip route   10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:32:26 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:11, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:11, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:11, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *> 192.168.1.0 0.0.0.0 0 32768 i Status codes - Status of the table entry. The status is displayed at the beginning of each line in the table. It can be one of the following values: s —The table entry is suppressed. * —The table entry is valid. > —The table entry is the best entry to use for that network. i —The table entry was learned via an internal BGP (iBGP) session SanJose1 only sees the BGP routes distributed by itself and its peer in their BGP tables.
SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:27:08 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:09, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:09, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:09, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 172.16.0.0 172.30.1.1 0 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i SanJose2 only sees the BGP routes distributed by itself and its peer in their BGP tables.
SanJose3#show ip route 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:18, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:07, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3 does not have a route to the ISP networks or the networks between the ISPs and the Boundary routers, so the ICMP Echo Replies fail. SanJose3 does not get any routes from the boundary routers except IGP routes. There are no BGP routes redistributed into the IGP and SanJose3 is not IBGP peering with any BGP speakers.
Step #2 – EBGP, IBGP and IGP (RIPv2) EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200 IBGP is configured between SanJose1 and SanJose3. There are no static routes.
Results : AS 200 Boundary routers can ping peer ISP networks AS 200 Boundary routers can NOT ping opposite ISP networks ISP routers can ping remote peer’s attached networks only, NOT SanJose3 network Synchronization is on, “The BGP synchronization rule states that if an AS provides transit service to another AS, BGP should not advertise a route until all of the routers within the AS have learned about the route via an IGP.” The boundary routers do not forward the “opposite” ISP routes because the other routers in the AS do not know about it.
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200
SanJose1#show ip route 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:09:13 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i * i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i Even though 172.16.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 172.30.1.1 Also, the BGP Synchronization rule keeps the BGP route from being in the routing table, since there is no IGP route. SanJose1 still only sees the BGP routes distributed by itself and its peer in their BGP tables.
SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:11:27 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path * i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Even though 10.2.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 10.1.0.1 Also, the BGP Synchronization rule keeps the BGP route from being in the routing table, since there is no IGP route. SanJose2 still only sees the BGP routes distributed by itself and its peer in their BGP tables.
Step #3 – Adding SanJose3 as a IBGP peer EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200 IBGP is configured between SanJose1, SanJose2 and SanJose3, full-mesh. No synchronization has been configured on all IBGP routers, because we are fully meshed IBGP. There are no static routes.
When an IBGP router receives an update about a destination from an IBGP peer, it tries to verify reachability to that destination via an IGP , such as RIP or OSPF. If the IBGP router can’t find the destination network in it’s IGP routing table, it will not advertise the destination to other BGP peers. If the route is not reachable through the IGP running within the AS, non-BGP routers will not be able to route traffic passing through the AS towards this destination. It is pointless to advertise destinations to external peers if traffic sent through this AS is going to be dropped by some non-BGP router within the AS anyway. Synchronization can be safely turned off on border routers: When all transit routers inside the AS are running fully meshed IBGP. When the AS is not a transit AS. Synchronization
Results: By itself, this will not change the reachability issues, because we have not resolved the problem with the boundary routers being able to reach the next-hop interface (SanJose1 still can not reach 172.30.1.1). We will make another change in a moment. Later, we might see that creating a full-mesh IBGP domain might not be the best configuration choice.
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.197 remote-as 200 SanJose1 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.194 remote-as 200 neighbor 192.168.1.197 remote-as 200 ! SanJose2 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.198 remote-as 200
SanJose1#show ip route 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:09:13 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i * i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i Even though 172.16.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 172.30.1.1 SanJose1 still only sees the BGP routes distributed by itself and its peer in their BGP tables. Same Problem
SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:11:27 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path * i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Even though 10.2.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 10.1.0.1 SanJose2 still only sees the BGP routes distributed by itself and its peer in their BGP tables. Same Problem
Step #4 – Adding the networks between the boundary routers and the ISP routers to the RIP routing domain. EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200, including the 10.0.0.0 and 172.30.0.0 network statements and passive interfaces . IBGP is configured between SanJose1, SanJose2 and SanJose3, full-mesh. No synchronization has been configured on all IBGP routers. There are no static routes. Complete reachability
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.197 remote-as 200 SanJose1 router rip version 2 passive-interface Serial0/1 network 10.0.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.194 remote-as 200 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 passive-interface Serial0/1 network 172.30.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.198 remote-as 200
SanJose1#show ip route  B 172.16.0.0/16 [200/0] via 172.30.1.1, 00:17:56 R 172.30.0.0/16 [120/2] via 192.168.1.194, 00:00:20, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:17:50 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:20, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:20, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:20, Serial0/0 SanJose1#show ip bgp  Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i Now that the networks between the ISPs and the boundary routers are being propagated by RIP, the boundary routers now have a route to the BGP next hops. Because of this the BGP routes to the “opposite” ISP network is reachable and in the routing table.
SanJose2#show ip route  B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:21:51 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:21:40 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:03, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:03, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:03, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:03, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp  Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Not only is the 10.2.0.0 network reachable, but the 10.0.0.0/8 classful network, which includes 10.1.0.0/24. This will come into play in a moment. The BGP route to the “opposite” ISP network is reachable and in the routing table.
SanJose3#show ip route   B 172.16.0.0/16 [200/0] via 172.30.1.1, 00:20:06 R 172.30.0.0/16 [120/1] via 192.168.1.197, 00:00:12, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:19:56 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:11, Serial0/0 192.168.1.0/24 is variably subnetted, 6 subnets, 3 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:12, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:11, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 B 192.168.1.0/24 [200/0] via 192.168.1.193, 00:19:53 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i *>i192.168.1.0 192.168.1.193 0 100 0 i * i 192.168.1.197 0 100 0 i
ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:15:14 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:15:14 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i The 172.16.0.0 network is now propagated from SanJose1 to ISP1.
ISP2#show ip route   172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:23:09 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:23:09 ISP2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i The 10.2.0.0 network (and the 10.0.0.0 network) is now propagated from SanJose1 to ISP1.
SanJose1#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms SanJose1#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/28 ms ------------------------------------- SanJose3#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/56 ms SanJose3#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms --------------------------------------- SanJose2#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms SanJose2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms
ISP2#ping 10.2.0.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) I thought you said all routers could reach all networks? What happened??? ISP2 can reach 10.2.0.1 What do you think the problem is?
ISP2#show ip route  172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:23:09 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:23:09 ISP2#show ip bgp  Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISP1#show ip route  B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:15:14 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:15:14 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 I ISP2 does have a route to 10.2.0.0 and ISP1 has a route to 172.16.0.0 The ping uses a source IP address of 172.30.1.1 and ISP1 does NOT have a route back to this destination address. (This also applies to pings from ISP1.) Extended pings with a reachable source IP address will work!
ISP2#ping Protocol [ip]: Target IP address: 10.2.0.1 Repeat count [5]: Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: y Source address or interface: 172.16.1.1 Type of service [0]: Set DF bit in IP header? [no]: Validate reply data? [no]: Data pattern [0xABCD]: Loose, Strict, Record, Timestamp, Verbose[none]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 108/112/116 ms ISP2 does have a route to 10.2.0.0 and ISP1 has a route to 172.16.0.0 The ping uses a source IP address of 172.30.1.1 and ISP1 does NOT have a route back to this destination address. (This also applies to pings from ISP1.) Extended pings with a reachable source IP address will work!
Scenario B: Step #1 – IBGP between SanJose1 and SanJose2 only EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200, including the 10.0.0.0 and 172.30.0.0 network statements and passive interfaces. IBGP is configured only between SanJose1, SanJose2. No synchronization has been configured on all IBGP routers. There are no static routes.
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 ! no router bgp 200 SanJose1 router rip version 2 passive-interface Serial0/1 network 10.0.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 passive-interface Serial0/1 network 172.30.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200
Results SanJose3 does NOT have a route to 172.16.0.0 on ISP2. SanJose3 does have a route to 10.0.0.0 on ISP1 only because SanJose1 is propagating its 10.1.0.0/24 subnet, so it has a route to the classful 10.0.0.0 network.  SanJose3 does NOT have the specific ISP networks in its routing table so it may drop packets as it is passed through between SanJose1 and SanJose2. SanJose1 and SanJose2 can NOT reach the opposite ISP2’s 172.16.1.1 because SanJose3 does not have a route to 172.16.0.0 on ISP1. However, SanJose1, SanJose2 and SanJose3 can reach ISP1’s 10.2.0.1 because RIP is sending the 10.0.0.0 classful route which includes the serial link between SJ1 and ISP1. ISPs – They will NOT be able to ping each other, because SJ3 has a route for the 10.0.0.0 network but NOT for the 172.16.0.0 network, thus pings from ISP2 to ISP1 will get to ISP2 but the replies will get dropped by SJ3 as it does not have a route for 172.16.0.0.
ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:34:13 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:38:39 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i ISP1#ping 192.168.1.33 Sending 5, 100-byte ICMP Echos to 192.168.1.33, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms ISP1#ping 172.16.1.1 MAKE THIS AN EXTENDED PING Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: U.U.U Success rate is 0 percent (0/5) This looks fine for ISP1, but lets look at the AS200 routers.
SanJose1#show ip route B 172.16.0.0/16 [200/0] via 172.30.1.1, 00:35:40 R 172.30.0.0/16 [120/2] via 192.168.1.194, 00:00:04, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:40:06 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:04, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:04, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:05, Serial0/0 SanJose1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i SanJose1#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms SanJose1#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: U.U.U Success rate is 0 percent (0/5) This looks fine for SJ1, but lets look at SJ3.
SanJose3#show ip route R 172.30.0.0/16 [120/1] via 192.168.1.197, 00:00:25, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:06, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:25, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:06, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms SanJose3#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) Notice that SanJose3 does NOT have a route for 172.16.0.0 . When a packet with a destination address for this network reaches SanJose3 it drops it. Remember, we removed SanJose3 as an IBGP peer. Where’s 172.16.0.0?
SanJose2#show ip route B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:43:13 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:38:57 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:04, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:04, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:05, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:05, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i SanJose2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms SanJose2#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms Again,this looks fine for SJ2, but 172.16.0.0 does NOT exist on SJ3.
ISP2#show ip route 172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:44:58 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:49:15 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISP2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) ISP2#ping 192.168.1.65 Sending 5, 100-byte ICMP Echos to 192.168.1.65, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/88 ms This also looks fine for ISP1, but remember the packets can’t return to ISP2 because SJ3 does not have a route for 172.16.0.0.
Step 2 -  The Solution, Redistributing BGP routes into RIP EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200, including the 10.0.0.0 and 172.30.0.0 network statements and passive interfaces. IBGP is configured only between SanJose1, SanJose2. No synchronization has been configured on all IBGP routers. 172.16.0.0 BGP routes are redistributed into AS200 via RIP There are no static routes. Complete reachability
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 passive-interface Serial0/1 network 10.0.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 network 172.30.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 !
SanJose2#show ip route B 172.16.0.0/16 [20/0] via 172.30.1.1, 01:22:20 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 01:18:04 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:21, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:21, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:21, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:21, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp BGP table version is 4, local router ID is 192.168.1.97 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i SanJose2# As before.
ISP2#show ip route 172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 01:19:44 B 192.168.1.0/24 [20/0] via 172.30.1.2, 01:24:01 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i As before.
SanJose3#show ip route   R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:04, Serial0/1 R 172.30.0.0/16 [120/1] via 192.168.1.197, 00:00:04, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:25, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:04, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:25, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3#ping 172.16.1.1 SanJose3 now has a route for 172.16.0.0 which was redistributed into RIP by SanJose2. This gives us the rest of the connectivity we need. 10.0.0.0 network was already in SanJose2’s routing table because SanJose1’s has a RIP network 10.0.0.0 statement. Remember 10.2.0.0 and 10.1.0.0 belong to this classful network.
SanJose1#show ip route   R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:02, Serial0/0 R 172.30.0.0/16 [120/2] via 192.168.1.194, 00:00:02, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 01:28:18 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:02, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:02, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:02, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i 172.16.0.0 is now redistributed via RIP which has a lower administrative distance (120) than IBGP (200); (EBGP is 20), which was how this route was in SanJose1’s routing table prior to redistribution by SanJose2..
ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 01:25:26 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 01:29:53 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i As before.
Scenario C: Another Way – Step #1 What if we did not want to redistribute the serial networks between the boundary routers and the ISPs into our rip network . What would be the consequences? How could we fix them? Eventually, for ISP1 to reach ISP2 we will use next-hop attribute. SanJose1 can ping 172.16.1.1. We will see that SanJose1 has an IGP route to 172.16.0.0 as this was redistributed by SanJose2 from BGP into rip, so it can ping 172.16.1.1. However, the 172.16.0.0 route in the BGP routing table shows a next hop of 172.30.1.1, in which SanJose1 does not have a route for. Because BGP does not have a route for the next hop, it does not include this route in its update to its EBGP peer, ISP1. ISP2 does have a route to ISP1’s 10.2.0.0/24 network because RIP is advertising the classful 10.0.0.0 network which includes the serial link between ISP1 and SanJose1. However, it can NOT ping it because the reply can NOT get back as explained in the previous paragraph. X
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 10.0.0.0 network 192.168.1.0 router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 172.30.0.0 network 192.168.1.0 router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 !
ISP1#show ip route 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:08:34 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 192.168.1.0 10.1.0.2 0 0 200 i ISP1#ping 192.168.1.97 Sending 5, 100-byte ICMP Echos to 192.168.1.97, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms ISP1#ping Protocol [ip]: Target IP address: 172.16.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) ISP1#ping 172.30.1.1 (Note: This is normal behavior and may not be necessary.) Sending 5, 100-byte ICMP Echos to 172.30.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) Notice: No route for 172.16.0.0/16 (we’ll see why)
SanJose1#show ip route   R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:19, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 01:20:45 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:19, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:19, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:19, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i * i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i SanJose1#ping 10.2.0.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms SanJose1#ping 172.16.1.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms Known via RIP because is was redistributed from BGP. NOT sent to ISP1 via EBGP because Next hop is not reachable. EBGP routes carried into IBGP use the external EBGP next hop.
SanJose3#show ip route   R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:09, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:22, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:09, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:22, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3# SanJose3#ping 10.2.0.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/64 ms SanJose3#ping 172.16.1.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/56 ms
SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 01:23:21 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:31:24 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:25, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:25, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:25, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:25, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i SanJose2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms SanJose2#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms SanJose2 sends 10.2.0.0 to ISP2 via EBGP because Next hop of 10.1.0.1 is reachable, as part of the 10.0.0.0/8 net. RIP redistributed the entire classful 10.0.0.0/8 network.
ISP2#show ip route 172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:33:01 B 192.168.1.0/24 [20/0] via 172.30.1.2, 01:25:53 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISP2#ping Protocol [ip]: Target IP address: 10.2.0.1 ..... Success rate is 0 percent (0/5) Notice: There is a route for 10.2.0.0
Step #2 -  The Solution – next-hop-self EBGP routes carried into IBGP use the external EBGP next hop. SanJose1’s BGP table has 172.30.1.1 as the next hop for 172.16.0.0/16, but does not have a route to 172.30.1.1, so it does not forward this route to ISP1. BGP Path Selection: “ If the path specifies a next hop that is inaccessible, drop the update.” (coming) Lets change the next hop to be the internal IBGP next hop. IBGP peers SanJose1 and SanJose2 will use next-hop self in peering with each other. This will change to next hops from the EBGP next hop to the internal IBGP next hop.   All works!!! Complete reachability
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 10.0.0.0 (from before) network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 neighbor 192.168.1.197 next-hop-self SanJose2 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 172.30.0.0 (from before) network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.193 next-hop-self !
ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:03:49 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:03:22 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i ISP1#ping 192.168.1.33 Sending 5, 100-byte ICMP Echos to 192.168.1.33, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms ISP1#ping Protocol [ip]: Target IP address: 172.16.1.1 Extended commands [n]: y Source address or interface: 10.2.0.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 108/111/112 ms ISP1# Looks good!
SanJose2: neighbor 192.168.1.193 next-hop-self (->192.168.1.197) SanJose1#show ip route   R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:24, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:05:51 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:24, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:24, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:24, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:25, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 192.168.1.197 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i Looks good! Effect of the next-hop-self (was 172.30.1.1) The route to the next hop
SanJose3#show ip route   R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:05, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:26, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:05, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:27, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1
SanJose1: neighbor 192.168.1.197 next-hop-self (->192.168.1.193) SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:09:30 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 192.168.1.193, 00:09:23 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:17, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:17, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:17, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:17, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 192.168.1.193 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Affect of the next-hop-self (was 10.1.0.1) The route to the next hop
More to come… In the near future I will expand this example network to include many more examples including the use of attributes. For now: What if we used a 172.16.1.0/24 mask on ISP2? What if we were running OSPF instead of RIP. More later…
What if we used a 172.16.1.0/24 mask on ISP2? 172.16.0.0/16 route distributed via RIP and BGP. ISP2 BEFORE router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose2#show ip route B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:09:30 SanJose3#show ip route R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:05, Serial0/1 SanJose1#show ip route R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:24, Serial0/0 ISP1#show ip route B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:03:49
What if we used a 172.16.1.0/24 mask on ISP2? 172.16.0.0/16 route distributed via RIP and 172.16.1.0/24 distributed via BGP. ISP2 AFTER router bgp 300 network 172.16.1.0 mask 255.255.255.0 neighbor 172.30.1.2 remote-as 200 SanJose2#show ip route B 172.16.1.0/24 [20/0] via 172.30.1.1, 00:00:35 SanJose3#show ip route R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:05, Serial0/1 SanJose1#show ip route R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:24, Serial0/0 B 172.16.1.0/24 [20/0] via 192.168.1.197, 00:00:32 ISP1#show ip route B 172.16.1.0/16 [20/0] via 10.1.0.2, 00:02:49
Let’s see how OSPF would work with BGP… Notice that the 172.16.1.0/24 network is distributed within OSPF and not the classful 172.16.0.0/16 like with RIP.  All works!!! Complete reachability
ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 mask 255.255.255.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router ospf 1 network 192.168.1.33 0.0.0.0 area 0 network 192.168.1.194 0.0.0.0 area 0 network 192.168.1.198 0.0.0.0 area 0 SanJose1 router ospf 1 redistribute bgp 200 metric 20 subnets network 192.168.1.65 0.0.0.0 area 0 network 192.168.1.193 0.0.0.0 area 0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 neighbor 192.168.1.197 next-hop-self ! access-list 1 permit 10.2.0.0 0.0.0.255 SanJose2 router ospf 1 redistribute bgp 200 metric 20 subnets network 192.168.1.97 0.0.0.0 area 0 network 192.168.1.197 0.0.0.0 area 0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.193 next-hop-self
ISP2#show ip route   172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:26:24 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:26:24 ISP2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.1.0/24 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i
SanJose2#show ip route   172.16.0.0/24 is subnetted, 1 subnets B 172.16.1.0 [20/0] via 172.30.1.1, 00:25:24 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/24 is subnetted, 1 subnets O E2 10.2.0.0 [110/20] via 192.168.1.198, 00:04:02, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 3 masks C 192.168.1.96/27 is directly connected, Loopback0 O 192.168.1.65/32 [110/846] via 192.168.1.198, 00:09:46, Serial0/0 O 192.168.1.33/32 [110/782] via 192.168.1.198, 00:09:47, Serial0/0 O 192.168.1.192/30 [110/845] via 192.168.1.198, 00:09:47, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 192.168.1.193 0 100 0 100 i *> 172.16.1.0/24 172.30.1.1 0 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.193 0 100 0 i
SanJose3#show ip route   172.16.0.0/24 is subnetted, 1 subnets O E2 172.16.1.0 [110/20] via 192.168.1.197, 00:01:53, Serial0/1 10.0.0.0/24 is subnetted, 1 subnets O E2 10.2.0.0 [110/20] via 192.168.1.193, 00:02:23, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 3 masks O 192.168.1.97/32 [110/65] via 192.168.1.197, 00:11:01, Serial0/1 O 192.168.1.65/32 [110/65] via 192.168.1.193, 00:11:01, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1
SanJose1#show ip route   172.16.0.0/24 is subnetted, 1 subnets O E2 172.16.1.0 [110/20] via 192.168.1.194, 00:02:08, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:28:02 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 3 masks O 192.168.1.97/32 [110/846] via 192.168.1.194, 00:11:09, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 O 192.168.1.33/32 [110/782] via 192.168.1.194, 00:11:09, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 O 192.168.1.196/30 [110/845] via 192.168.1.194, 00:11:09, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.1.0/24 192.168.1.197 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i
SanJose1#show ip ospf data   OSPF Router with ID (192.168.1.65) (Process ID 1)     Router Link States (Area 0)   Link ID ADV Router Age Seq# Checksum Link count 192.168.1.33 192.168.1.33 845 0x80000005 0xAB78 5 192.168.1.65 192.168.1.65 921 0x80000004 0x8883 3 192.168.1.97 192.168.1.97 801 0x80000004 0xB8EA 3   Type-5 AS External Link States   Link ID ADV Router Age Seq# Checksum Tag 10.2.0.0 192.168.1.65 193 0x80000001 0xC1C2 100 172.16.1.0 192.168.1.97 165 0x80000001 0x28C1 300
ISP1#show ip route   172.16.0.0/24 is subnetted, 1 subnets B 172.16.1.0 [20/0] via 10.1.0.2, 00:25:00 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:29:04 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.1.0/24 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i
To be continued…

More Related Content

PDF
ivesgimpaya3
guest10184a
 
DOC
Ccna 2 chapter 2 v4.0 answers 2011
Dân Chơi
 
DOCX
Ccna 2 v 4.0 final-exam-19-06-2010
irbas
 
PDF
ivesgimpaya2
guest10184a
 
DOC
Ccna 2 chapter 7 v4.0 answers 2011
Dân Chơi
 
PPTX
BGP Loop Prevention
NetProtocol Xpert
 
PDF
Free CCNP switching workbook by networkershome pdf
Networkershome
 
DOC
Ccna 2 chapter 9 v4.0 answers 2011
Dân Chơi
 
ivesgimpaya3
guest10184a
 
Ccna 2 chapter 2 v4.0 answers 2011
Dân Chơi
 
Ccna 2 v 4.0 final-exam-19-06-2010
irbas
 
ivesgimpaya2
guest10184a
 
Ccna 2 chapter 7 v4.0 answers 2011
Dân Chơi
 
BGP Loop Prevention
NetProtocol Xpert
 
Free CCNP switching workbook by networkershome pdf
Networkershome
 
Ccna 2 chapter 9 v4.0 answers 2011
Dân Chơi
 

What's hot (18)

PPT
Chapter6ccna
robertoxe
 
PDF
CCNP Troubleshooting
Networkershome
 
PPTX
BGP Next-hop-self
NetProtocol Xpert
 
PPT
Ripv2
Vivek Singh
 
PDF
1 using default
guest10184a
 
PDF
Ccnav5.org ccna 2-v5_final_exam_2014
Đồng Quốc Vương
 
PDF
Routing
Ivan Ivanovich Ivanov
 
PDF
Ospf Last Modified Eng
Alp isik
 
DOC
Ccna 2 chapter 1 v4.0 answers 2011
Dân Chơi
 
PDF
Understanding the Routing Table Structure
Makram Ghazzaoui
 
PPTX
OSPF Internal Route Summarization
NetProtocol Xpert
 
PDF
Troubleshooting BGP
APNIC
 
DOC
Ccna 2 chapter 3 v4.0 answers 2011
Dân Chơi
 
PDF
Day 4 LAYER 2 SWITCHING
anilinvns
 
PDF
Ccnav5.org ccna 3-chapter_8_v50_2014_exam_answers
Đồng Quốc Vương
 
PDF
Day 2 IP ROUTING
anilinvns
 
PPTX
13. eigrp and ospf
Swarndeep Singh
 
PPT
routing basics - (static-default-dynamic)
Shanza Sohail
 
Chapter6ccna
robertoxe
 
CCNP Troubleshooting
Networkershome
 
BGP Next-hop-self
NetProtocol Xpert
 
Ripv2
Vivek Singh
 
1 using default
guest10184a
 
Ccnav5.org ccna 2-v5_final_exam_2014
Đồng Quốc Vương
 
Routing
Ivan Ivanovich Ivanov
 
Ospf Last Modified Eng
Alp isik
 
Ccna 2 chapter 1 v4.0 answers 2011
Dân Chơi
 
Understanding the Routing Table Structure
Makram Ghazzaoui
 
OSPF Internal Route Summarization
NetProtocol Xpert
 
Troubleshooting BGP
APNIC
 
Ccna 2 chapter 3 v4.0 answers 2011
Dân Chơi
 
Day 4 LAYER 2 SWITCHING
anilinvns
 
Ccnav5.org ccna 3-chapter_8_v50_2014_exam_answers
Đồng Quốc Vương
 
Day 2 IP ROUTING
anilinvns
 
13. eigrp and ospf
Swarndeep Singh
 
routing basics - (static-default-dynamic)
Shanza Sohail
 
Ad

Viewers also liked (20)

PPTX
JarethPresentation
lmuhleman
 
PPT
12theo_maritini_vasilis_2010
Evelyn G.
 
PPT
Railway postcards
Marc Bostyn
 
PPT
Complex Claims 9 25 09
medmanenator
 
PDF
Google+ Unwrapped
Purple Stripe Productions
 
PDF
Initiativantrag
Sozak
 
PDF
Limit Strength Prediction of Light Gauge Steel I Section by Finite Element Me...
IJERA Editor
 
PPS
Thong diep
phuctrangsankhau
 
PPTX
Why buy Diamond+?
YANtouch Corp.
 
PPT
DCLG Statistics User Engagement Day - Social Housing Sales and Lettings
DCLGStats
 
PPT
Isa abistab poega
Tuuli1968
 
PPTX
Editing graphics 10.31.13
darlanwalker
 
PDF
Supply Level Inc Power Point 2008 Breif
dontyers
 
PDF
ATLAS OF MINERAL RESOURCES OF THE ESCAPE REGION VOLUME 12 GEOLOGY AND MINERAL...
MYO AUNG Myanmar
 
PDF
Japonisme
S.E. Thompson
 
PPTX
Google Docs Pt Feedback
tatiana
 
PDF
Adobe PageMaker 7.0. Oficjalny podręcznik
Wydawnictwo Helion
 
PDF
Bg33341344
IJERA Editor
 
PDF
למה לי פילנתרופיה עכשיו
sheatufim
 
PPT
Jardin
guest9ffa658
 
JarethPresentation
lmuhleman
 
12theo_maritini_vasilis_2010
Evelyn G.
 
Railway postcards
Marc Bostyn
 
Complex Claims 9 25 09
medmanenator
 
Google+ Unwrapped
Purple Stripe Productions
 
Initiativantrag
Sozak
 
Limit Strength Prediction of Light Gauge Steel I Section by Finite Element Me...
IJERA Editor
 
Thong diep
phuctrangsankhau
 
Why buy Diamond+?
YANtouch Corp.
 
DCLG Statistics User Engagement Day - Social Housing Sales and Lettings
DCLGStats
 
Isa abistab poega
Tuuli1968
 
Editing graphics 10.31.13
darlanwalker
 
Supply Level Inc Power Point 2008 Breif
dontyers
 
ATLAS OF MINERAL RESOURCES OF THE ESCAPE REGION VOLUME 12 GEOLOGY AND MINERAL...
MYO AUNG Myanmar
 
Japonisme
S.E. Thompson
 
Google Docs Pt Feedback
tatiana
 
Adobe PageMaker 7.0. Oficjalny podręcznik
Wydawnictwo Helion
 
Bg33341344
IJERA Editor
 
למה לי פילנתרופיה עכשיו
sheatufim
 
Jardin
guest9ffa658
 
Ad

Similar to Bgp Basic Labs (20)

PPT
Bgp Basic Labs
cisconetworker
 
PDF
Bgp fine tuning
Libi Pappachen
 
DOCX
2.6.6 Packet Tracer - Verify Single-Area OSPFv2 - ILM.docx
Josimar Caitano
 
PPTX
BGP Weight Manipulation with Route Map
NetProtocol Xpert
 
DOCX
Lab 9 instructions
trayyoo
 
PDF
Bgp in-large-networks
Sudhakar Ganapareddy
 
PDF
ccna-discowey-final-100
junkut3
 
DOCX
BÀI TẬP 01.docx
ssuseraf0e77
 
DOCX
BÀI TẬP 01.docx
ssuseraf0e77
 
PPT
Ccnp route
Arnold Derrick Kinney
 
PDF
Cisco discovery drs ent module 10 - v.4 in english.
igede tirtanata
 
PDF
BGP Interview Questions for Network Engineers
atulsharmacse
 
DOCX
Ccna 2 v 4.0 final-exam-19-06-2010
irbas
 
DOCX
Practice exam #2
Kris Mofu
 
DOCX
CCNP Route 642 902 BGP
IT Tech
 
PPT
Chapter6ccna
ernestlithur
 
PPTX
IPv6 Static Routes
Irsandi Hasan
 
DOC
Ccna 2 chapter 11 v4.0 answers 2011
Dân Chơi
 
DOC
E routing final exam ccna 2 46
lslsc
 
PDF
Ccnp enterprise workbook v1.0 bgp zero to hero
SagarR24
 
Bgp Basic Labs
cisconetworker
 
Bgp fine tuning
Libi Pappachen
 
2.6.6 Packet Tracer - Verify Single-Area OSPFv2 - ILM.docx
Josimar Caitano
 
BGP Weight Manipulation with Route Map
NetProtocol Xpert
 
Lab 9 instructions
trayyoo
 
Bgp in-large-networks
Sudhakar Ganapareddy
 
ccna-discowey-final-100
junkut3
 
BÀI TẬP 01.docx
ssuseraf0e77
 
BÀI TẬP 01.docx
ssuseraf0e77
 
Ccnp route
Arnold Derrick Kinney
 
Cisco discovery drs ent module 10 - v.4 in english.
igede tirtanata
 
BGP Interview Questions for Network Engineers
atulsharmacse
 
Ccna 2 v 4.0 final-exam-19-06-2010
irbas
 
Practice exam #2
Kris Mofu
 
CCNP Route 642 902 BGP
IT Tech
 
Chapter6ccna
ernestlithur
 
IPv6 Static Routes
Irsandi Hasan
 
Ccna 2 chapter 11 v4.0 answers 2011
Dân Chơi
 
E routing final exam ccna 2 46
lslsc
 
Ccnp enterprise workbook v1.0 bgp zero to hero
SagarR24
 

Recently uploaded (20)

PDF
Empathic Computing: Creating Shared Understanding
Mark Billinghurst
 
PDF
Encapsulation theory and applications.pdf
gurumoop
 
PDF
Diabetes mellitus diagnosis method based random forest with bat algorithm
IAESIJAI
 
PDF
Reach Out and Touch Someone: Haptics and Empathic Computing
Mark Billinghurst
 
PDF
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
PPTX
Cloud computing and distributed systems.
kkkkkhan
 
PDF
Dropbox Q2 2025 Financial Results & Investor Presentation
Dropbox
 
PDF
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
Safe Software
 
PPTX
MYSQL Presentation for SQL database connectivity
Swati270511
 
PDF
The Rise and Fall of 3GPP – Time for a Sabbatical?
3G4G
 
PPTX
A Presentation on Artificial Intelligence
memembruh336
 
PDF
Machine learning based COVID-19 study performance prediction
IAESIJAI
 
PDF
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
PDF
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
SHREYAS PHANSE
 
PPTX
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
ReZa AdineH
 
PPTX
Digital-Transformation-Roadmap-for-Companies.pptx
David Malick Dieng
 
PDF
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
IAESIJAI
 
PDF
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Jian-Hong Pan
 
PPTX
20250228 LYD VKU AI Blended-Learning.pptx
DatVoNgoc
 
PPTX
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
ReZa AdineH
 
Empathic Computing: Creating Shared Understanding
Mark Billinghurst
 
Encapsulation theory and applications.pdf
gurumoop
 
Diabetes mellitus diagnosis method based random forest with bat algorithm
IAESIJAI
 
Reach Out and Touch Someone: Haptics and Empathic Computing
Mark Billinghurst
 
7 ChatGPT Prompts to Help You Define Your Ideal Customer Profile.pdf
SOFTTECHHUB
 
Cloud computing and distributed systems.
kkkkkhan
 
Dropbox Q2 2025 Financial Results & Investor Presentation
Dropbox
 
Peak of Data & AI Encore- AI for Metadata and Smarter Workflows
Safe Software
 
MYSQL Presentation for SQL database connectivity
Swati270511
 
The Rise and Fall of 3GPP – Time for a Sabbatical?
3G4G
 
A Presentation on Artificial Intelligence
memembruh336
 
Machine learning based COVID-19 study performance prediction
IAESIJAI
 
Architecting across the Boundaries of two Complex Domains - Healthcare & Tech...
Peter Tan
 
Shreyas Phanse Resume: Experienced Backend Engineer | Java • Spring Boot • Ka...
SHREYAS PHANSE
 
Detection-First SIEM: Rule Types, Dashboards, and Threat-Informed Strategy
ReZa AdineH
 
Digital-Transformation-Roadmap-for-Companies.pptx
David Malick Dieng
 
Bridging biosciences and deep learning for revolutionary discoveries: a compr...
IAESIJAI
 
Build a system with the filesystem maintained by OSTree @ COSCUP 2025
Jian-Hong Pan
 
20250228 LYD VKU AI Blended-Learning.pptx
DatVoNgoc
 
Effective Security Operations Center (SOC) A Modern, Strategic, and Threat-In...
ReZa AdineH
 

Bgp Basic Labs

  • 1. Cabrillo College Basic BGP Lab Examples Rick Graziani, Instructor November 15, 2001
  • 2. Note to instructors If you have downloaded this presentation from the Cisco Networking Academy Community FTP Center, this may not be my latest version of this PowerPoint. For the latest PowerPoints for all my CCNA, CCNP, and Wireless classes, please go to my web site: http://www.cabrillo.edu/~rgraziani/ The username is cisco and the password is perlman for all of my materials. If you have any questions on any of my materials or the curriculum, please feel free to email me at graziani@cabrillo.edu (I really don’t mind helping.) Also, if you run across any typos or errors in my presentations, please let me know. I will add “(Updated – date )” next to each presentation on my web site that has been updated since these have been uploaded to the FTP center. Thanks! Rick
  • 3. Objective These lab examples are not meant to demonstrate proper or realistic BGP configurations, nor does it include all the necessary commands to ensure proper routing operation. The objective of these examples are to show some of the basic BGP configuration commands and their affect on a network, including wrong configurations or misconfigurations. Hopefully this series of configurations and outputs will help explain the how BGP is implemented and its operation.
  • 5. Why IBGP? In order for the boundary routers SanJose1 and SanJose2 to exchange BGP routes that they learn from ISP1 and ISP2 respectively, they must do one of the following: Redistribution – Not recommended! Redistribute from BGP into the IGP (RIPv2) so those routes get propagated to the other boundary router. Redistribute from IGP (RIPv2) to BGP to learn routes from the other boundary router or the use of BGP network statements. Disadvantages : Can be a lot of routes being injected into the IGP; may also require the use of route filters so not all routes are injected into the IGP or back out to the other ISP. “ With very few exceptions, interior BGP (IBGP) – BGP between peers in the same AS – is used only in multihomed scenarios.” – Doyle
  • 6. In order for the boundary routers SanJose1 and SanJose2 to exchange BGP routes that they learn from ISP1 and ISP2 respectively, they must do one of the following: IBGP This allows the boundary routers to share EBGP routes without the redistributing via an IGP. Requires: Synchronization : Can’t advertise via EBGP if the boundary router doesn’t have it in its IGP routing table because the other IGP routers will drop it. (Can turn this off if fully meshed IBGP or non-transit AS!) Must know how to reach the next hop address of the route. (example coming!) Why IBGP? “ With very few exceptions, interior BGP (IBGP) – BGP between peers in the same AS – is used only in multihomed scenarios.” – Doyle
  • 7.  
  • 8. Setup RIPv2 running within AS200 10.1.0.0/24 is between SanJose1 and ISP1’s 10.2.0.0/24 networks, both of which are part of 10.0.0.0/8 classful network. RIPv2 was chosen because this will create a different situation than with the two different Class B networks between SanJose2 and ISP2.
  • 9. Scenario A: Step #1 – EBGP and IGP (RIPv2) EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200 RIP network statements only include those networks in AS200 No IBGP has been configured. There are no static routes.
  • 10. Results : AS 200 Boundary (SanJose1 and SanJose2) routers can ping peer ISP networks AS 200 Boundary (SanJose1 and SanJose2) routers can NOT ping opposite ISP networks (SanJose1 can not ping 172.16.1.1) ISP routers (ISP1 and ISP2) can ping remote peer’s attached networks only, NOT SanJose3 network (we will see why in a moment). Successful pings
  • 11. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 SanJose2 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 172.30.1.1 remote-as 300
  • 12. ISP1#show ip route 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:25:16 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 192.168.1.0 10.1.0.2 0 0 200 i ------------------------------------------------------------------------ ISP2#show ip route   172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:30:51 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISPs only see the BGP routes distributed by themselves and their peers in their BGP tables.
  • 13. SanJose1#show ip route   10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:32:26 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:11, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:11, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:11, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *> 192.168.1.0 0.0.0.0 0 32768 i Status codes - Status of the table entry. The status is displayed at the beginning of each line in the table. It can be one of the following values: s —The table entry is suppressed. * —The table entry is valid. > —The table entry is the best entry to use for that network. i —The table entry was learned via an internal BGP (iBGP) session SanJose1 only sees the BGP routes distributed by itself and its peer in their BGP tables.
  • 14. SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:27:08 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:09, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:09, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:09, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 172.16.0.0 172.30.1.1 0 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i SanJose2 only sees the BGP routes distributed by itself and its peer in their BGP tables.
  • 15. SanJose3#show ip route 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:18, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:07, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3 does not have a route to the ISP networks or the networks between the ISPs and the Boundary routers, so the ICMP Echo Replies fail. SanJose3 does not get any routes from the boundary routers except IGP routes. There are no BGP routes redistributed into the IGP and SanJose3 is not IBGP peering with any BGP speakers.
  • 16. Step #2 – EBGP, IBGP and IGP (RIPv2) EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200 IBGP is configured between SanJose1 and SanJose3. There are no static routes.
  • 17. Results : AS 200 Boundary routers can ping peer ISP networks AS 200 Boundary routers can NOT ping opposite ISP networks ISP routers can ping remote peer’s attached networks only, NOT SanJose3 network Synchronization is on, “The BGP synchronization rule states that if an AS provides transit service to another AS, BGP should not advertise a route until all of the routers within the AS have learned about the route via an IGP.” The boundary routers do not forward the “opposite” ISP routes because the other routers in the AS do not know about it.
  • 18. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 network 192.168.1.0 ! router bgp 200 network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200
  • 19. SanJose1#show ip route 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:09:13 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i * i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i Even though 172.16.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 172.30.1.1 Also, the BGP Synchronization rule keeps the BGP route from being in the routing table, since there is no IGP route. SanJose1 still only sees the BGP routes distributed by itself and its peer in their BGP tables.
  • 20. SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:11:27 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path * i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Even though 10.2.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 10.1.0.1 Also, the BGP Synchronization rule keeps the BGP route from being in the routing table, since there is no IGP route. SanJose2 still only sees the BGP routes distributed by itself and its peer in their BGP tables.
  • 21. Step #3 – Adding SanJose3 as a IBGP peer EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200 IBGP is configured between SanJose1, SanJose2 and SanJose3, full-mesh. No synchronization has been configured on all IBGP routers, because we are fully meshed IBGP. There are no static routes.
  • 22. When an IBGP router receives an update about a destination from an IBGP peer, it tries to verify reachability to that destination via an IGP , such as RIP or OSPF. If the IBGP router can’t find the destination network in it’s IGP routing table, it will not advertise the destination to other BGP peers. If the route is not reachable through the IGP running within the AS, non-BGP routers will not be able to route traffic passing through the AS towards this destination. It is pointless to advertise destinations to external peers if traffic sent through this AS is going to be dropped by some non-BGP router within the AS anyway. Synchronization can be safely turned off on border routers: When all transit routers inside the AS are running fully meshed IBGP. When the AS is not a transit AS. Synchronization
  • 23. Results: By itself, this will not change the reachability issues, because we have not resolved the problem with the boundary routers being able to reach the next-hop interface (SanJose1 still can not reach 172.30.1.1). We will make another change in a moment. Later, we might see that creating a full-mesh IBGP domain might not be the best configuration choice.
  • 24. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.197 remote-as 200 SanJose1 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.194 remote-as 200 neighbor 192.168.1.197 remote-as 200 ! SanJose2 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.198 remote-as 200
  • 25. SanJose1#show ip route 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:09:13 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:27, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i * i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i Even though 172.16.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 172.30.1.1 SanJose1 still only sees the BGP routes distributed by itself and its peer in their BGP tables. Same Problem
  • 26. SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:11:27 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:19, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path * i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Even though 10.2.0.0 network is in BGP table it is not in routing table because there is no route to the next hop of 10.1.0.1 SanJose2 still only sees the BGP routes distributed by itself and its peer in their BGP tables. Same Problem
  • 27. Step #4 – Adding the networks between the boundary routers and the ISP routers to the RIP routing domain. EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200, including the 10.0.0.0 and 172.30.0.0 network statements and passive interfaces . IBGP is configured between SanJose1, SanJose2 and SanJose3, full-mesh. No synchronization has been configured on all IBGP routers. There are no static routes. Complete reachability
  • 28. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 ! router bgp 200 no synchronization neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.197 remote-as 200 SanJose1 router rip version 2 passive-interface Serial0/1 network 10.0.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.194 remote-as 200 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 passive-interface Serial0/1 network 172.30.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.198 remote-as 200
  • 29. SanJose1#show ip route  B 172.16.0.0/16 [200/0] via 172.30.1.1, 00:17:56 R 172.30.0.0/16 [120/2] via 192.168.1.194, 00:00:20, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:17:50 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:20, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:20, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:20, Serial0/0 SanJose1#show ip bgp  Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i Now that the networks between the ISPs and the boundary routers are being propagated by RIP, the boundary routers now have a route to the BGP next hops. Because of this the BGP routes to the “opposite” ISP network is reachable and in the routing table.
  • 30. SanJose2#show ip route  B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:21:51 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:21:40 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:03, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:03, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:03, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:03, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp  Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Not only is the 10.2.0.0 network reachable, but the 10.0.0.0/8 classful network, which includes 10.1.0.0/24. This will come into play in a moment. The BGP route to the “opposite” ISP network is reachable and in the routing table.
  • 31. SanJose3#show ip route   B 172.16.0.0/16 [200/0] via 172.30.1.1, 00:20:06 R 172.30.0.0/16 [120/1] via 192.168.1.197, 00:00:12, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:19:56 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:11, Serial0/0 192.168.1.0/24 is variably subnetted, 6 subnets, 3 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:12, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:11, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 B 192.168.1.0/24 [200/0] via 192.168.1.193, 00:19:53 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i *>i192.168.1.0 192.168.1.193 0 100 0 i * i 192.168.1.197 0 100 0 i
  • 32. ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:15:14 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:15:14 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i The 172.16.0.0 network is now propagated from SanJose1 to ISP1.
  • 33. ISP2#show ip route   172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:23:09 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:23:09 ISP2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i The 10.2.0.0 network (and the 10.0.0.0 network) is now propagated from SanJose1 to ISP1.
  • 34. SanJose1#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms SanJose1#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/28 ms ------------------------------------- SanJose3#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/56 ms SanJose3#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms --------------------------------------- SanJose2#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms SanJose2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms
  • 35. ISP2#ping 10.2.0.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) I thought you said all routers could reach all networks? What happened??? ISP2 can reach 10.2.0.1 What do you think the problem is?
  • 36. ISP2#show ip route  172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:23:09 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:23:09 ISP2#show ip bgp  Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISP1#show ip route  B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:15:14 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:15:14 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 I ISP2 does have a route to 10.2.0.0 and ISP1 has a route to 172.16.0.0 The ping uses a source IP address of 172.30.1.1 and ISP1 does NOT have a route back to this destination address. (This also applies to pings from ISP1.) Extended pings with a reachable source IP address will work!
  • 37. ISP2#ping Protocol [ip]: Target IP address: 10.2.0.1 Repeat count [5]: Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: y Source address or interface: 172.16.1.1 Type of service [0]: Set DF bit in IP header? [no]: Validate reply data? [no]: Data pattern [0xABCD]: Loose, Strict, Record, Timestamp, Verbose[none]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 108/112/116 ms ISP2 does have a route to 10.2.0.0 and ISP1 has a route to 172.16.0.0 The ping uses a source IP address of 172.30.1.1 and ISP1 does NOT have a route back to this destination address. (This also applies to pings from ISP1.) Extended pings with a reachable source IP address will work!
  • 38. Scenario B: Step #1 – IBGP between SanJose1 and SanJose2 only EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200, including the 10.0.0.0 and 172.30.0.0 network statements and passive interfaces. IBGP is configured only between SanJose1, SanJose2. No synchronization has been configured on all IBGP routers. There are no static routes.
  • 39. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 ! no router bgp 200 SanJose1 router rip version 2 passive-interface Serial0/1 network 10.0.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 passive-interface Serial0/1 network 172.30.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200
  • 40. Results SanJose3 does NOT have a route to 172.16.0.0 on ISP2. SanJose3 does have a route to 10.0.0.0 on ISP1 only because SanJose1 is propagating its 10.1.0.0/24 subnet, so it has a route to the classful 10.0.0.0 network.  SanJose3 does NOT have the specific ISP networks in its routing table so it may drop packets as it is passed through between SanJose1 and SanJose2. SanJose1 and SanJose2 can NOT reach the opposite ISP2’s 172.16.1.1 because SanJose3 does not have a route to 172.16.0.0 on ISP1. However, SanJose1, SanJose2 and SanJose3 can reach ISP1’s 10.2.0.1 because RIP is sending the 10.0.0.0 classful route which includes the serial link between SJ1 and ISP1. ISPs – They will NOT be able to ping each other, because SJ3 has a route for the 10.0.0.0 network but NOT for the 172.16.0.0 network, thus pings from ISP2 to ISP1 will get to ISP2 but the replies will get dropped by SJ3 as it does not have a route for 172.16.0.0.
  • 41. ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:34:13 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:38:39 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i ISP1#ping 192.168.1.33 Sending 5, 100-byte ICMP Echos to 192.168.1.33, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms ISP1#ping 172.16.1.1 MAKE THIS AN EXTENDED PING Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: U.U.U Success rate is 0 percent (0/5) This looks fine for ISP1, but lets look at the AS200 routers.
  • 42. SanJose1#show ip route B 172.16.0.0/16 [200/0] via 172.30.1.1, 00:35:40 R 172.30.0.0/16 [120/2] via 192.168.1.194, 00:00:04, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:40:06 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:04, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:04, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:05, Serial0/0 SanJose1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i SanJose1#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms SanJose1#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: U.U.U Success rate is 0 percent (0/5) This looks fine for SJ1, but lets look at SJ3.
  • 43. SanJose3#show ip route R 172.30.0.0/16 [120/1] via 192.168.1.197, 00:00:25, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:06, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:25, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:06, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms SanJose3#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) Notice that SanJose3 does NOT have a route for 172.16.0.0 . When a packet with a destination address for this network reaches SanJose3 it drops it. Remember, we removed SanJose3 as an IBGP peer. Where’s 172.16.0.0?
  • 44. SanJose2#show ip route B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:43:13 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:38:57 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:04, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:04, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:05, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:05, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i SanJose2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms SanJose2#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms Again,this looks fine for SJ2, but 172.16.0.0 does NOT exist on SJ3.
  • 45. ISP2#show ip route 172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:44:58 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:49:15 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISP2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) ISP2#ping 192.168.1.65 Sending 5, 100-byte ICMP Echos to 192.168.1.65, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/88 ms This also looks fine for ISP1, but remember the packets can’t return to ISP2 because SJ3 does not have a route for 172.16.0.0.
  • 46. Step 2 -  The Solution, Redistributing BGP routes into RIP EBGP is configured between ISP routers and AS200 boundary routers. RIPv2 is running within AS200, including the 10.0.0.0 and 172.30.0.0 network statements and passive interfaces. IBGP is configured only between SanJose1, SanJose2. No synchronization has been configured on all IBGP routers. 172.16.0.0 BGP routes are redistributed into AS200 via RIP There are no static routes. Complete reachability
  • 47. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 passive-interface Serial0/1 network 10.0.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 network 172.30.0.0 network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 !
  • 48. SanJose2#show ip route B 172.16.0.0/16 [20/0] via 172.30.1.1, 01:22:20 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 01:18:04 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:21, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:21, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:21, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:21, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp BGP table version is 4, local router ID is 192.168.1.97 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i SanJose2# As before.
  • 49. ISP2#show ip route 172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 01:19:44 B 192.168.1.0/24 [20/0] via 172.30.1.2, 01:24:01 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i As before.
  • 50. SanJose3#show ip route   R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:04, Serial0/1 R 172.30.0.0/16 [120/1] via 192.168.1.197, 00:00:04, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:25, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:04, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:25, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3#ping 172.16.1.1 SanJose3 now has a route for 172.16.0.0 which was redistributed into RIP by SanJose2. This gives us the rest of the connectivity we need. 10.0.0.0 network was already in SanJose2’s routing table because SanJose1’s has a RIP network 10.0.0.0 statement. Remember 10.2.0.0 and 10.1.0.0 belong to this classful network.
  • 51. SanJose1#show ip route   R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:02, Serial0/0 R 172.30.0.0/16 [120/2] via 192.168.1.194, 00:00:02, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 01:28:18 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:02, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:02, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:02, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 172.30.1.1 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i 172.16.0.0 is now redistributed via RIP which has a lower administrative distance (120) than IBGP (200); (EBGP is 20), which was how this route was in SanJose1’s routing table prior to redistribution by SanJose2..
  • 52. ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 01:25:26 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 01:29:53 ISP1#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i As before.
  • 53. Scenario C: Another Way – Step #1 What if we did not want to redistribute the serial networks between the boundary routers and the ISPs into our rip network . What would be the consequences? How could we fix them? Eventually, for ISP1 to reach ISP2 we will use next-hop attribute. SanJose1 can ping 172.16.1.1. We will see that SanJose1 has an IGP route to 172.16.0.0 as this was redistributed by SanJose2 from BGP into rip, so it can ping 172.16.1.1. However, the 172.16.0.0 route in the BGP routing table shows a next hop of 172.30.1.1, in which SanJose1 does not have a route for. Because BGP does not have a route for the next hop, it does not include this route in its update to its EBGP peer, ISP1. ISP2 does have a route to ISP1’s 10.2.0.0/24 network because RIP is advertising the classful 10.0.0.0 network which includes the serial link between ISP1 and SanJose1. However, it can NOT ping it because the reply can NOT get back as explained in the previous paragraph. X
  • 54. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 10.0.0.0 network 192.168.1.0 router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 SanJose2 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 172.30.0.0 network 192.168.1.0 router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 !
  • 55. ISP1#show ip route 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:08:34 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 192.168.1.0 10.1.0.2 0 0 200 i ISP1#ping 192.168.1.97 Sending 5, 100-byte ICMP Echos to 192.168.1.97, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms ISP1#ping Protocol [ip]: Target IP address: 172.16.1.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) ISP1#ping 172.30.1.1 (Note: This is normal behavior and may not be necessary.) Sending 5, 100-byte ICMP Echos to 172.30.1.1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) Notice: No route for 172.16.0.0/16 (we’ll see why)
  • 56. SanJose1#show ip route   R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:19, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 01:20:45 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:19, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:19, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:19, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i * i172.16.0.0 172.30.1.1 0 100 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.197 0 100 0 i SanJose1#ping 10.2.0.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms SanJose1#ping 172.16.1.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms Known via RIP because is was redistributed from BGP. NOT sent to ISP1 via EBGP because Next hop is not reachable. EBGP routes carried into IBGP use the external EBGP next hop.
  • 57. SanJose3#show ip route   R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:09, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:22, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:09, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:22, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1 SanJose3# SanJose3#ping 10.2.0.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/57/64 ms SanJose3#ping 172.16.1.1   Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/56 ms
  • 58. SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 01:23:21 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 10.1.0.1, 00:31:24 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:25, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:25, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:25, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:25, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 10.1.0.1 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i SanJose2#ping 10.2.0.1 Sending 5, 100-byte ICMP Echos to 10.2.0.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 84/84/84 ms SanJose2#ping 172.16.1.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms SanJose2 sends 10.2.0.0 to ISP2 via EBGP because Next hop of 10.1.0.1 is reachable, as part of the 10.0.0.0/8 net. RIP redistributed the entire classful 10.0.0.0/8 network.
  • 59. ISP2#show ip route 172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:33:01 B 192.168.1.0/24 [20/0] via 172.30.1.2, 01:25:53 ISP2#show ip bgp Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.0.0 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i ISP2#ping Protocol [ip]: Target IP address: 10.2.0.1 ..... Success rate is 0 percent (0/5) Notice: There is a route for 10.2.0.0
  • 60. Step #2 -  The Solution – next-hop-self EBGP routes carried into IBGP use the external EBGP next hop. SanJose1’s BGP table has 172.30.1.1 as the next hop for 172.16.0.0/16, but does not have a route to 172.30.1.1, so it does not forward this route to ISP1. BGP Path Selection: “ If the path specifies a next hop that is inaccessible, drop the update.” (coming) Lets change the next hop to be the internal IBGP next hop. IBGP peers SanJose1 and SanJose2 will use next-hop self in peering with each other. This will change to next hops from the EBGP next hop to the internal IBGP next hop.   All works!!! Complete reachability
  • 61. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router rip version 2 network 192.168.1.0 SanJose1 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 10.0.0.0 (from before) network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 neighbor 192.168.1.197 next-hop-self SanJose2 router rip version 2 redistribute bgp 200 metric 2 passive-interface Serial0/1 no network 172.30.0.0 (from before) network 192.168.1.0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.193 next-hop-self !
  • 62. ISP1#show ip route   B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:03:49 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:03:22 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.0.0 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i ISP1#ping 192.168.1.33 Sending 5, 100-byte ICMP Echos to 192.168.1.33, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 56/56/60 ms ISP1#ping Protocol [ip]: Target IP address: 172.16.1.1 Extended commands [n]: y Source address or interface: 10.2.0.1 Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 108/111/112 ms ISP1# Looks good!
  • 63. SanJose2: neighbor 192.168.1.193 next-hop-self (->192.168.1.197) SanJose1#show ip route   R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:24, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:05:51 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/2] via 192.168.1.194, 00:00:24, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:24, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.194, 00:00:24, Serial0/0 R 192.168.1.196/30 [120/1] via 192.168.1.194, 00:00:25, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.0.0 192.168.1.197 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i Looks good! Effect of the next-hop-self (was 172.30.1.1) The route to the next hop
  • 64. SanJose3#show ip route   R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:05, Serial0/1 R 10.0.0.0/8 [120/1] via 192.168.1.193, 00:00:26, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks R 192.168.1.96/27 [120/1] via 192.168.1.197, 00:00:05, Serial0/1 R 192.168.1.64/27 [120/1] via 192.168.1.193, 00:00:27, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1
  • 65. SanJose1: neighbor 192.168.1.197 next-hop-self (->192.168.1.193) SanJose2#show ip route   B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:09:30 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks B 10.2.0.0/24 [200/0] via 192.168.1.193, 00:09:23 R 10.0.0.0/8 [120/2] via 192.168.1.198, 00:00:17, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 2 masks C 192.168.1.96/27 is directly connected, Loopback0 R 192.168.1.64/27 [120/2] via 192.168.1.198, 00:00:17, Serial0/0 R 192.168.1.32/27 [120/1] via 192.168.1.198, 00:00:17, Serial0/0 R 192.168.1.192/30 [120/1] via 192.168.1.198, 00:00:17, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 192.168.1.193 0 100 0 100 i *> 172.16.0.0 172.30.1.1 0 0 300 i * i192.168.1.0 192.168.1.193 0 100 0 i *> 0.0.0.0 0 32768 i Affect of the next-hop-self (was 10.1.0.1) The route to the next hop
  • 66. More to come… In the near future I will expand this example network to include many more examples including the use of attributes. For now: What if we used a 172.16.1.0/24 mask on ISP2? What if we were running OSPF instead of RIP. More later…
  • 67. What if we used a 172.16.1.0/24 mask on ISP2? 172.16.0.0/16 route distributed via RIP and BGP. ISP2 BEFORE router bgp 300 network 172.16.0.0 neighbor 172.30.1.2 remote-as 200 SanJose2#show ip route B 172.16.0.0/16 [20/0] via 172.30.1.1, 00:09:30 SanJose3#show ip route R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:05, Serial0/1 SanJose1#show ip route R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:24, Serial0/0 ISP1#show ip route B 172.16.0.0/16 [20/0] via 10.1.0.2, 00:03:49
  • 68. What if we used a 172.16.1.0/24 mask on ISP2? 172.16.0.0/16 route distributed via RIP and 172.16.1.0/24 distributed via BGP. ISP2 AFTER router bgp 300 network 172.16.1.0 mask 255.255.255.0 neighbor 172.30.1.2 remote-as 200 SanJose2#show ip route B 172.16.1.0/24 [20/0] via 172.30.1.1, 00:00:35 SanJose3#show ip route R 172.16.0.0/16 [120/2] via 192.168.1.197, 00:00:05, Serial0/1 SanJose1#show ip route R 172.16.0.0/16 [120/3] via 192.168.1.194, 00:00:24, Serial0/0 B 172.16.1.0/24 [20/0] via 192.168.1.197, 00:00:32 ISP1#show ip route B 172.16.1.0/16 [20/0] via 10.1.0.2, 00:02:49
  • 69. Let’s see how OSPF would work with BGP… Notice that the 172.16.1.0/24 network is distributed within OSPF and not the classful 172.16.0.0/16 like with RIP.  All works!!! Complete reachability
  • 70. ISP1 router bgp 100 network 10.2.0.0 mask 255.255.255.0 neighbor 10.1.0.2 remote-as 200 ISP2 router bgp 300 network 172.16.0.0 mask 255.255.255.0 neighbor 172.30.1.2 remote-as 200 SanJose3 router ospf 1 network 192.168.1.33 0.0.0.0 area 0 network 192.168.1.194 0.0.0.0 area 0 network 192.168.1.198 0.0.0.0 area 0 SanJose1 router ospf 1 redistribute bgp 200 metric 20 subnets network 192.168.1.65 0.0.0.0 area 0 network 192.168.1.193 0.0.0.0 area 0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 10.1.0.1 remote-as 100 neighbor 192.168.1.197 remote-as 200 neighbor 192.168.1.197 next-hop-self ! access-list 1 permit 10.2.0.0 0.0.0.255 SanJose2 router ospf 1 redistribute bgp 200 metric 20 subnets network 192.168.1.97 0.0.0.0 area 0 network 192.168.1.197 0.0.0.0 area 0 ! router bgp 200 no synchronization network 192.168.1.0 neighbor 172.30.1.1 remote-as 300 neighbor 192.168.1.193 remote-as 200 neighbor 192.168.1.193 next-hop-self
  • 71. ISP2#show ip route   172.16.0.0/24 is subnetted, 1 subnets C 172.16.1.0 is directly connected, Loopback0 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/0 10.0.0.0/24 is subnetted, 1 subnets B 10.2.0.0 [20/0] via 172.30.1.2, 00:26:24 B 192.168.1.0/24 [20/0] via 172.30.1.2, 00:26:24 ISP2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 172.30.1.2 0 200 100 i *> 172.16.1.0/24 0.0.0.0 0 32768 i *> 192.168.1.0 172.30.1.2 0 0 200 i
  • 72. SanJose2#show ip route   172.16.0.0/24 is subnetted, 1 subnets B 172.16.1.0 [20/0] via 172.30.1.1, 00:25:24 172.30.0.0/24 is subnetted, 1 subnets C 172.30.1.0 is directly connected, Serial0/1 10.0.0.0/24 is subnetted, 1 subnets O E2 10.2.0.0 [110/20] via 192.168.1.198, 00:04:02, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 3 masks C 192.168.1.96/27 is directly connected, Loopback0 O 192.168.1.65/32 [110/846] via 192.168.1.198, 00:09:46, Serial0/0 O 192.168.1.33/32 [110/782] via 192.168.1.198, 00:09:47, Serial0/0 O 192.168.1.192/30 [110/845] via 192.168.1.198, 00:09:47, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/0 SanJose2#show ip bgp   Network Next Hop Metric LocPrf Weight Path *>i10.2.0.0/24 192.168.1.193 0 100 0 100 i *> 172.16.1.0/24 172.30.1.1 0 0 300 i *> 192.168.1.0 0.0.0.0 0 32768 i * i 192.168.1.193 0 100 0 i
  • 73. SanJose3#show ip route   172.16.0.0/24 is subnetted, 1 subnets O E2 172.16.1.0 [110/20] via 192.168.1.197, 00:01:53, Serial0/1 10.0.0.0/24 is subnetted, 1 subnets O E2 10.2.0.0 [110/20] via 192.168.1.193, 00:02:23, Serial0/0 192.168.1.0/24 is variably subnetted, 5 subnets, 3 masks O 192.168.1.97/32 [110/65] via 192.168.1.197, 00:11:01, Serial0/1 O 192.168.1.65/32 [110/65] via 192.168.1.193, 00:11:01, Serial0/0 C 192.168.1.32/27 is directly connected, Loopback0 C 192.168.1.192/30 is directly connected, Serial0/0 C 192.168.1.196/30 is directly connected, Serial0/1
  • 74. SanJose1#show ip route   172.16.0.0/24 is subnetted, 1 subnets O E2 172.16.1.0 [110/20] via 192.168.1.194, 00:02:08, Serial0/0 10.0.0.0/24 is subnetted, 2 subnets B 10.2.0.0 [20/0] via 10.1.0.1, 00:28:02 C 10.1.0.0 is directly connected, Serial0/1 192.168.1.0/24 is variably subnetted, 5 subnets, 3 masks O 192.168.1.97/32 [110/846] via 192.168.1.194, 00:11:09, Serial0/0 C 192.168.1.64/27 is directly connected, Loopback0 O 192.168.1.33/32 [110/782] via 192.168.1.194, 00:11:09, Serial0/0 C 192.168.1.192/30 is directly connected, Serial0/0 O 192.168.1.196/30 [110/845] via 192.168.1.194, 00:11:09, Serial0/0 SanJose1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 10.1.0.1 0 0 100 i *>i172.16.1.0/24 192.168.1.197 0 100 0 300 i * i192.168.1.0 192.168.1.197 0 100 0 i *> 0.0.0.0 0 32768 i
  • 75. SanJose1#show ip ospf data   OSPF Router with ID (192.168.1.65) (Process ID 1)     Router Link States (Area 0)   Link ID ADV Router Age Seq# Checksum Link count 192.168.1.33 192.168.1.33 845 0x80000005 0xAB78 5 192.168.1.65 192.168.1.65 921 0x80000004 0x8883 3 192.168.1.97 192.168.1.97 801 0x80000004 0xB8EA 3   Type-5 AS External Link States   Link ID ADV Router Age Seq# Checksum Tag 10.2.0.0 192.168.1.65 193 0x80000001 0xC1C2 100 172.16.1.0 192.168.1.97 165 0x80000001 0x28C1 300
  • 76. ISP1#show ip route   172.16.0.0/24 is subnetted, 1 subnets B 172.16.1.0 [20/0] via 10.1.0.2, 00:25:00 10.0.0.0/24 is subnetted, 2 subnets C 10.2.0.0 is directly connected, Loopback0 C 10.1.0.0 is directly connected, Serial0 B 192.168.1.0/24 [20/0] via 10.1.0.2, 00:29:04 ISP1#show ip bgp   Network Next Hop Metric LocPrf Weight Path *> 10.2.0.0/24 0.0.0.0 0 32768 i *> 172.16.1.0/24 10.1.0.2 0 200 300 i *> 192.168.1.0 10.1.0.2 0 0 200 i