Table of contents
BGP Federation Synthesis Experiment
Start ospf---IGP protocol in AS2
Modification: The next hop solves the above problems
AS2 internal loop routing information to access each other
Solution: The loopback address 192.168.2.0/24 cannot be declared in any protocol
BGP Federation Synthesis Experiment
Experimental diagram
Network segment division
It is known that the IP address of the entire AS2 is 172.16..0.0/16
172.16.0.0/16 ---- 172.16.2.0/24 ---- R2
172.16.3.0/24 ---- R3
172.16.4.0/24 ---- R4
172.16.5.0/24 ---- R5
172.16.6.0/24 ---- R6
172.16.7.0/24 ---- R7
172.16.0.0/24 ---- P2P
172.16.1.0/24----MA-----172.16.1.0/29-----R2-R3
172.16.1.8/29 ----- R2-R4
172.16.1.16/29 ----- R3-R4
172.16.1.24/29 ----- R4-R7
172.16.1.32/29-----R5-R6
172.16.1.40/29-----R6-R7
172.16.1.48/29
......
basic configuration
R1
[R1]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 4
The number of interface that is DOWN in Physical is 2
The number of interface that is UP in Protocol is 4
The number of interface that is DOWN in Protocol is 2
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 12.0.0.1/24 up up
GigabitEthernet0/0/1 unassigned down down
GigabitEthernet0/0/2 unassigned down down
LoopBack0 192.168.1.1/24 up up(s)
LoopBack1 10.0.0.1/24 up up(s)
NULL0 unassigned up up(s)
R2
[R2]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 5
The number of interface that is DOWN in Physical is 0
The number of interface that is UP in Protocol is 5
The number of interface that is DOWN in Protocol is 0
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 12.0.0.2/24 up up
GigabitEthernet0/0/1 172.16.1.1/29 up up
GigabitEthernet0/0/2 172.16.1.9/29 up up
LoopBack0 172.16.2.1/24 up up(s)
NULL0 unassigned up up(s)
R3
[R3]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 4
The number of interface that is DOWN in Physical is 1
The number of interface that is UP in Protocol is 4
The number of interface that is DOWN in Protocol is 1
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 172.16.1.2/29 up up
GigabitEthernet0/0/1 172.16.1.17/29 up up
GigabitEthernet0/0/2 unassigned down down
LoopBack0 172.16.3.1/24 up up(s)
NULL0 unassigned up up(s)
R4
[R4]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 4
The number of interface that is DOWN in Physical is 1
The number of interface that is UP in Protocol is 4
The number of interface that is DOWN in Protocol is 1
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 172.16.1.18/29 up up
GigabitEthernet0/0/1 172.16.1.25/29 up up
GigabitEthernet0/0/2 unassigned down down
LoopBack0 172.16.4.1/24 up up(s)
NULL0 unassigned up up(s)
[R4]R5
[R5]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 4
The number of interface that is DOWN in Physical is 1
The number of interface that is UP in Protocol is 4
The number of interface that is DOWN in Protocol is 1
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 172.16.1.10/29 up up
GigabitEthernet0/0/1 172.16.1.33/29 up up
GigabitEthernet0/0/2 unassigned down down
LoopBack0 172.16.5.1/24 up up(s)
NULL0 unassigned up up(s)
R6
[R6]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 4
The number of interface that is DOWN in Physical is 1
The number of interface that is UP in Protocol is 4
The number of interface that is DOWN in Protocol is 1
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 172.16.1.34/29 up up
GigabitEthernet0/0/1 172.16.1.41/29 up up
GigabitEthernet0/0/2 unassigned down down
LoopBack0 172.16.6.1/24 up up(s)
NULL0 unassigned up up(s)
R7
[R7]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 5
The number of interface that is DOWN in Physical is 0
The number of interface that is UP in Protocol is 5
The number of interface that is DOWN in Protocol is 0
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 172.16.1.42/29 up up
GigabitEthernet0/0/1 172.16.1.26/29 up up
GigabitEthernet0/0/2 78.0.0.1/24 up up
LoopBack0 172.16.7.1/24 up up(s)
NULL0 unassigned up up(s)
R8
[R8]display ip interface brief
*down: administratively down
^down: standby
(l): loopback
(s): spoofing
The number of interface that is UP in Physical is 4
The number of interface that is DOWN in Physical is 2
The number of interface that is UP in Protocol is 4
The number of interface that is DOWN in Protocol is 2
Interface IP Address/Mask Physical Protocol
GigabitEthernet0/0/0 78.0.0.2/24 up up
GigabitEthernet0/0/1 unassigned down down
GigabitEthernet0/0/2 unassigned down down
LoopBack0 192.168.2.1/24 up up(s)
LoopBack1 11.0.0.1/24 up up(s)
NULL0 unassigned up up(s) routing configuration
Start ospf---IGP protocol in AS2
R2
[R2]ospf 1 router-id 2.2.2.2
[R2-ospf-1]a 0
[R2-ospf-1]a 0
[R2-ospf-1-area-0.0.0.0]netwo
[R2-ospf-1-area-0.0.0.0]network 172.16.0.0 0.0.0.255
[R2-ospf-1-area-0.0.0.0]R3
[R3]ospf 1 router-id 3.3.3.3
[R3-ospf-1]area 0
[R3-ospf-1-area-0.0.0.0]network 172.16.0.0 0.0.255.255
Notice:
Other R4R5, R6, R7, R8 are similar
Detect IGP
R2
[R2]display ip routing-table protocol ospf
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Public routing table : OSPF
Destinations : 9 Routes : 10
OSPF routing table status : <Active>
Destinations : 9 Routes : 10
Destination/Mask Proto Pre Cost Flags NextHop Interface
172.16.1.16/29 OSPF 10 2 D 172.16.1.2 GigabitEthernet
0/0/1
172.16.1.24/29 OSPF 10 3 D 172.16.1.2 GigabitEthernet
0/0/1
172.16.1.32/29 OSPF 10 2 D 172.16.1.10 GigabitEthernet
0/0/2
172.16.1.40/29 OSPF 10 3 D 172.16.1.10 GigabitEthernet
0/0/2
172.16.3.1/32 OSPF 10 1 D 172.16.1.2 GigabitEthernet
0/0/1
172.16.4.1/32 OSPF 10 2 D 172.16.1.2 GigabitEthernet
0/0/1
172.16.5.1/32 OSPF 10 1 D 172.16.1.10 GigabitEthernet
0/0/2
172.16.6.1/32 OSPF 10 2 D 172.16.1.10 GigabitEthernet
0/0/2
172.16.7.1/32 OSPF 10 3 D 172.16.1.10 GigabitEthernet
0/0/2
OSPF 10 3 D 172.16.1.2 GigabitEthernet
0/0/1
OSPF routing table status : <Inactive>
Destinations : 0 Routes : 0
R3
[R3]display ip routing-table protocol ospf
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Public routing table : OSPF
Destinations : 9 Routes : 10
OSPF routing table status : <Active>
Destinations : 9 Routes : 10
Destination/Mask Proto Pre Cost Flags NextHop Interface
172.16.1.8/29 OSPF 10 2 D 172.16.1.1 GigabitEthernet
0/0/0
172.16.1.24/29 OSPF 10 2 D 172.16.1.18 GigabitEthernet
0/0/1
172.16.1.32/29 OSPF 10 3 D 172.16.1.1 GigabitEthernet
0/0/0
172.16.1.40/29 OSPF 10 3 D 172.16.1.18 GigabitEthernet
0/0/1
172.16.2.1/32 OSPF 10 1 D 172.16.1.1 GigabitEthernet
0/0/0
172.16.4.1/32 OSPF 10 1 D 172.16.1.18 GigabitEthernet
0/0/1
172.16.5.1/32 OSPF 10 2 D 172.16.1.1 GigabitEthernet
0/0/0
172.16.6.1/32 OSPF 10 3 D 172.16.1.1 GigabitEthernet
0/0/0
OSPF 10 3 D 172.16.1.18 GigabitEthernet
0/0/1
172.16.7.1/32 OSPF 10 2 D 172.16.1.18 GigabitEthernet
0/0/1
OSPF routing table status : <Inactive>
Destinations : 0 Routes : 0
Start BGP between AS
R1
[R1]bgp 1
[R1-bgp]ro
[R1-bgp]router-id 1.1.1.1
[R1-bgp]pe
[R1-bgp]peer 12.0.0.2 as
[R1-bgp]peer 12.0.0.2 as-number 2
[R1-bgp]R2
[R2]bgp 64512 ---- 有联邦存在的时候写联邦AS号
[R2-bgp]router-id 2.2.2.2
[R2-bgp]confederation id 2 --- 告诉大AS号为2
[R2-bgp]confederation peer-as 64513 --- 指定EBGP对等体关系的AS号
[R2-bgp]peer 12.0.0.1 as-number 1
[R2-bgp]peer 172.16.3.1 as-number 64512 --- 建立 R2 与 R3 的IGP对等体关系
[R2-bgp]peer 172.16.3.1 connect-interface LoopBack 0
[R2-bgp]peer 172.16.5.1 as-number 64513 --- 建立 R2 与 R5 的非直连建邻
[R2-bgp]peer 172.16.5.1 connect-interface LoopBack 0
[R2-bgp]peer 172.16.5.1 ebgp-max-hop --- 将ttl值修改 R3
[R3]bgp 64512
[R3-bgp]router-id 3.3.3.3
[R3-bgp]confederation id 2
[R3-bgp]peer 172.16.2.1 as-number 64512
[R3-bgp]peer 172.16.2.1 connect-interface LoopBack 0
[R3-bgp]peer 172.16.4.1 as-number 64512
[R3-bgp]peer 172.16.4.1 connect-interface LoopBack 0
R4
[R4]bgp 64512
[R4-bgp]router-id 4.4.4.4
[R4-bgp]confederation id 2
[R4-bgp]confederation peer-as 64513
[R4-bgp]peer 172.16.3.1 as 64512
[R4-bgp]peer 172.16.3.1 connect-interface LoopBack 0
[R4-bgp]peer 172.16.7.1 as 64513
[R4-bgp]peer 172.16.7.1 connect-interface LoopBack 0
[R4-bgp]peer 172.16.7.1 ebgp-max-hop
Notice:
R5 is similar to R4, R6 is similar to R3, R7 is similar to R2
R8
[R8]bgp 3
[R8-bgp]router-id 8.8.8.8
[R8-bgp]peer 78.0.0.1 as 2
[R8-bgp]test
R2
[R2]display bgp peer
BGP local router ID : 2.2.2.2
Local AS number : 64512
Total number of peers : 3 Peers in established state : 3
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre
fRcv
12.0.0.1 4 1 19 19 0 00:17:28 Established
0
172.16.3.1 4 64512 14 16 0 00:12:21 Established
0
172.16.5.1 4 64513 8 10 0 00:06:11 Established
0
R3
[R3]display bgp peer
BGP local router ID : 3.3.3.3
Local AS number : 64512
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre
fRcv
172.16.2.1 4 64512 14 14 0 00:12:49 Established
0
172.16.4.1 4 64512 11 14 0 00:09:49 Established
0
[R3]
R4
[R4]display bgp peer
BGP local router ID : 4.4.4.4
Local AS number : 64512
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre
fRcv
172.16.3.1 4 64512 12 12 0 00:10:18 Established
0
172.16.7.1 4 64513 5 7 0 00:03:14 Established
0
[R4]
R5
[R5]display bgp peer
BGP local router ID : 5.5.5.5
Local AS number : 64513
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre
fRcv
172.16.2.1 4 64512 9 9 0 00:07:24 Established
0
172.16.6.1 4 64513 8 9 0 00:06:14 Established
0
[R5]
R6
[R6]display bgp peer
BGP local router ID : 6.6.6.6
Local AS number : 64513
Total number of peers : 2 Peers in established state : 2
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre
fRcv
172.16.5.1 4 64513 8 8 0 00:06:25 Established
0
172.16.7.1 4 64513 6 7 0 00:04:36 Established
0
[R6]
R7
[R7]display bgp peer
BGP local router ID : 7.7.7.7
Local AS number : 64513
Total number of peers : 3 Peers in established state : 3
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre
fRcv
78.0.0.2 4 3 5 6 0 00:03:29 Established
0
172.16.4.1 4 64512 6 6 0 00:04:07 Established
0
172.16.6.1 4 64513 7 7 0 00:05:01 Established
0
R8
[R8]display bgp peer
BGP local router ID : 8.8.8.8
Local AS number : 3
Total number of peers : 1 Peers in established state : 1
Peer V AS MsgRcvd MsgSent OutQ Up/Down State Pre
fRcv
78.0.0.1 4 2 5 5 0 00:03:48 Established
0
[R8]
Advertise R1 routes
R1
[R1-bgp]network 10.0.0.0 24
[R1-bgp]display bgp peer test
[R1-bgp]display bgp routing-table
BGP Local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 10.0.0.0/24 0.0.0.0 0 0 i
<R2>display bgp routing-table
BGP Local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 10.0.0.0/24 12.0.0.1 0 0 1i
<R2>
<R3>display bgp routing-table ---- 收到但不可用
BGP Local router ID is 3.3.3.3
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
i 10.0.0.0/24 12.0.0.1 0 100 0 1i
<R3>
R3 and R5 can receive but not available, so R4, R6 can not receive, including the latter
Modification: The next hop solves the above problems
R2
[R2]bgp 64512
[R2-bgp]peer 172.16.3.1 next-hop-local
[R2-bgp]peer 172.16.5.1 next-hop-local
test
R3
<R3>display bgp routing-table
BGP Local router ID is 3.3.3.3
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 10.0.0.0/24 172.16.2.1 0 100 0 1i
<R3>
R6
<R6>display bgp routing-table
BGP Local router ID is 6.6.6.6
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 10.0.0.0/24 172.16.2.1 0 100 0 (64512) 1i
<R6>Notice:
R4 could not receive it, the reason: the split horizon of IBGP caused
R6 received it, the reason: R5 and R2 belong to EBGP peers for federated BGP, and the routing information learned by EBGP can be sent to its own IBGP peers
R7 can not receive, the reason: the split horizon of IBGP
resolve split horizon
Set up a route reflector
R3 as reflection specifies R2 as client
[R3]bgp
[R3]bgp 64512
[R3-bgp]peer 172.16.2.1 reflect-client --- 指定R2作为客户test
<R4>display bgp routing-table
BGP Local router ID is 4.4.4.4
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 10.0.0.0/24 172.16.2.1 0 100 0 1i
<R4>
<R4>display bgp routing-table 10.0.0.0
BGP local router ID : 4.4.4.4
Local AS number : 64512
Paths: 1 available, 1 best, 1 select
BGP routing table entry information of 10.0.0.0/24:
From: 172.16.3.1 (3.3.3.3)
Route Duration: 00h01m23s
Relay IP Nexthop: 172.16.1.17
Relay IP Out-Interface: GigabitEthernet0/0/0
Original nexthop: 172.16.2.1
Qos information : 0x0
AS-path 1, origin igp, MED 0, localpref 100, pref-val 0, valid, internal-confed
, best, select, active, pre 255, IGP cost 2
Originator: 2.2.2.2
Cluster list: 3.3.3.3
Advertised to such 1 peers:
172.16.7.1
<R4>In the same way, R6 is used as a reflection to specify R7 or R5 as a customer
[R6]bgp 64513
[R6-bgp]peer 172.16.7.1 reflect-client test
[R7]display bgp routing-table
BGP Local router ID is 7.7.7.7
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 2
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 10.0.0.0/24 172.16.2.1 0 100 0 (64512) 1i
* i 172.16.2.1 0 100 0 (64512) 1i
[R7]Receive two identical, R6 reflects one, R4 receives and reflects R7
<R8>display bgp routing-table
BGP Local router ID is 8.8.8.8
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 1
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 10.0.0.0/24 78.0.0.1 0 2 1i
<R8>At present, the sending route of R1 has been fully implemented.
Advertise R8 routes
[R8]bgp 3
[R8-bgp]network 11.0.0.0 24test
[R7]display bgp routing-table
BGP Local router ID is 7.7.7.7
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 10.0.0.0/24 172.16.2.1 0 100 0 (64512) 1i
* i 172.16.2.1 0 100 0 (64512) 1i
*> 11.0.0.0/24 78.0.0.2 0 0 3i
[R7]Because the address of the next hop is 78.0.0.2, R4 and R6 cannot receive routing information. The solution: modify it to local routing information
[R7]bgp 64513 [R7-bgp]peer 172.16.6.1 next-hop-local [R7-bgp]peer 172.16.4.1 next-hop-local [R7-bgp]
<R1>display bgp routing-table
BGP Local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 2
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 10.0.0.0/24 0.0.0.0 0 0 i
*> 11.0.0.0/24 12.0.0.2 0 2 3i
<R1>Because of sending routing information and intercommunication, R1 and R8 routes can already access each other
AS2 internal loop routing information to access each other
route aggregation
Perform route summarization:
172.16.2.0/24
172.16.3.0/24
172.16.4.0/24
172.16.5.0/24
172.16.6.0/24
172.16.7.0/24 ----- 172.16.0.0 / 21
Configure an empty interface
[R2]ip route-static 172.16.0.0 21 NULL 0
[R2]display ip routing-table protocol static
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Public routing table : Static
Destinations : 1 Routes : 1 Configured Routes : 1
Static routing table status : <Active>
Destinations : 1 Routes : 1
Destination/Mask Proto Pre Cost Flags NextHop Interface
172.16.0.0/21 Static 60 0 D 0.0.0.0 NULL0
Static routing table status : <Inactive>
Destinations : 0 Routes : 0
[R2]Publish static routes
[R2]bgp 64512
[R2-bgp]network 172.16.0.0 21
[R2-bgp]display bgp routing-table
BGP Local router ID is 2.2.2.2
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 10.0.0.0/24 12.0.0.1 0 0 1i
*>i 11.0.0.0/24 172.16.7.1 0 100 0 (64513) 3i
*> 172.16.0.0/21 0.0.0.0 0 0 i
[R2-bgp]test
[R1]display bgp routing-table
BGP Local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 10.0.0.0/24 0.0.0.0 0 0 i
*> 11.0.0.0/24 12.0.0.2 0 2 3i
*> 172.16.0.0/21 12.0.0.2 0 0 2i
[R1]
<R7>display bgp routing-table
BGP Local router ID is 7.7.7.7
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 5
Network NextHop MED LocPrf PrefVal Path/Ogn
*>i 10.0.0.0/24 172.16.2.1 0 100 0 (64512) 1i
* i 172.16.2.1 0 100 0 (64512) 1i
*> 11.0.0.0/24 78.0.0.2 0 0 3i
*>i 172.16.0.0/21 172.16.2.1 0 100 0 (64512)i
* i 172.16.2.1 0 100 0 (64512)i
<R7>
<R8>display bgp routing-table
BGP Local router ID is 8.8.8.8
Status codes: * - valid, > - best, d - damped,
h - history, i - internal, s - suppressed, S - Stale
Origin : i - IGP, e - EGP, ? - incomplete
Total Number of Routes: 3
Network NextHop MED LocPrf PrefVal Path/Ogn
*> 10.0.0.0/24 78.0.0.1 0 2 1i
*> 11.0.0.0/24 0.0.0.0 0 0 i
*> 172.16.0.0/21 78.0.0.1 0 2i
<R8>At present, the loopback of all devices in the entire network has been completed and they can access each other
There is a problem:
If R8 sends 172.16.0.1 (routing black hole) to R7, it will eventually be discarded by R2, which will cause the black hole to occupy inside AS2 and waste resources
Solution:
[R7]ip route-static 172.16.0.0 21 NULL 0
[R7]bgp 64513
[R7-bgp]network 172.16.0.0 21
[R7-bgp]Solution: The loopback address 192.168.2.0/24 cannot be declared in any protocol
Make GRE Tunnel
[R1]int t 0/0/0
[R1-Tunnel0/0/0]ip ad
[R1-Tunnel0/0/0]ip address 99.0.0.1 24 ---- 配置网段
[R1-Tunnel0/0/0]
[R1-Tunnel0/0/0]tunnel-protocol gre --- 定义隧道的封装类型
[R1-Tunnel0/0/0]source 10.0.0.1 ---定义封装内容
[R1-Tunnel0/0/0]destination 11.0.0.1
Mar 2 2023 12:18:54-08:00 R1 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP
on the interface Tunnel0/0/0 has entered the UP state.
[R1-Tunnel0/0/0]
[R1-Tunnel0/0/0][R8]int t 0/0/0
[R8-Tunnel0/0/0]ip address 99.0.0.2 24
[R8-Tunnel0/0/0]tunnel-protocol gre
[R8-Tunnel0/0/0]source 11.0.0.1
[R8-Tunnel0/0/0]destination 10.0.0.1
Mar 2 2023 12:18:00-08:00 R8 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP
on the interface Tunnel0/0/0 has entered the UP state.
[R8-Tunnel0/0/0]
[R8-Tunnel0/0/0]Configure static routing
[R1]ip route-static 192.168.2.0 24 99.0.0.2[R8]ip route-static 192.168.1.0 24 99.0.0.1 test
[R8]ping -a 192.168.2.1 192.168.1.1
PING 192.168.1.1: 56 data bytes, press CTRL_C to break
Reply from 192.168.1.1: bytes=56 Sequence=1 ttl=255 time=60 ms
Reply from 192.168.1.1: bytes=56 Sequence=2 ttl=255 time=50 ms
Reply from 192.168.1.1: bytes=56 Sequence=3 ttl=255 time=30 ms
Reply from 192.168.1.1: bytes=56 Sequence=4 ttl=255 time=50 ms
Reply from 192.168.1.1: bytes=56 Sequence=5 ttl=255 time=30 ms
--- 192.168.1.1 ping statistics ---
5 packet(s) transmitted
5 packet(s) received
0.00% packet loss
round-trip min/avg/max = 30/44/60 ms
[R8]