BGP综合实验

原创已于 2025-08-08 20:23:26 修改 · 632 阅读

8 ·

CC 4.0 BY-SA版权

文章标签：

#网络 #服务器 #php

于 2025-08-08 20:02:34 首次发布

一、实验拓扑

二、实验要求

1、AS1存在两个环回，一个地址为192.168.1.0/24该地址不能在任何协议中宣告，AS3中存在两个环回，一个地址为192.168.2.0/24该地址不能在任何协议中宣告，最终要求这两个环回可以ping通；

2、R1-R8建邻环回用x.x.x.x/32表示；

3、整个AS2的IP地址为172.16.0.0/16，R3-R7各有一个业务网段，请合理划分，并内部配置OSPF；

4、AS间的骨干链路IP地址随意定制；

5、使用BGP协议让整个网络所有设备的环回可以互相访问；

6、减少路由条自数量，避免环路出现。

三、实验思路

1、配置ip地址，配置ospf让AR内部可通

2、配置BGP建邻

IBGP的水平分割--使用联邦解决

AS by AS原则修改下一跳为本地

3、BGP路由聚合实现优化、防环

四、实验步骤

1、配置IP地址

2、配置OSPF

[R2]ospf 1 r 2.2.2.2
[R2-ospf-1]a 0
[R2-ospf-1-area-0.0.0.0]net 172.16.1.1 0.0.0.0
[R2-ospf-1-area-0.0.0.0]net 172.16.1.21 0.0.0.0
[R2-ospf-1-area-0.0.0.0]net 2.2.2.2 0.0.0.0

R3、R4-R7类似

[R3]ospf 1 r 3.3.3.3
[R3-ospf-1]a 0
[R3-ospf-1-area-0.0.0.0]n 3.3.3.3 0.0.0.0
[R3-ospf-1-area-0.0.0.0]n 172.16.1.2 0.0.0.0
[R3-ospf-1-area-0.0.0.0]n 172.16.1.5 0.0.0.0
[R3-ospf-1-area-0.0.0.0]n 172.16.3.0 0.0.0.255

测试R3-R4环回

测试R5-R6环回

R4路由表

3、配置BGP

[R1]bgp 1
[R1-bgp]peer 12.1.1.2 as-number 2

[R2]bgp 64512
[R2-bgp]confederation id 2
[R2-bgp]confederation peer-as 64513 说明自己的联盟邻居
[R2-bgp]peer 12.1.1.1 as 1 与AR1建邻
[R2-bgp]peer 3.3.3.3 as 64512 与AR3建邻
Aug 8 2025 12:37:04-08:00 R2 %%01BGP/3/STATE_CHG_UPDOWN(l)[0]:The status of the
peer 12.1.1.1 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, St
ateChangeReason=Up)
[R2-bgp]peer 3.3.3.3 connect-interface l0 修改更新原为环回口
[R2-bgp]peer 3.3.3.3 next-hop-local 修改下一条为本机
[R2-bgp]peer 172.16.1.22 as 64513
[R2-bgp]peer 172.16.1.22 next-hop-local

[R3]bgp 64512
[R3-bgp]confederation id 2
[R3-bgp]confederation peer-as 64513
[R3-bgp]peer 2.2.2.2 as 64512
[R3-bgp]peer 2.2.2.2 connect-interface l0
[R3-bgp]peer 4.4.4.4 as 64512
[R3-bgp]peer 4.4.4.4 con l0
Aug 8 2025 12:44:05-08:00 R3 %%01BGP/3/STATE_CHG_UPDOWN(l)[0]:The status of the
peer 2.2.2.2 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)

[R4]bgp 64512
[R4-bgp]con id 2
[R4-bgp]con peer-as 64513
[R4-bgp]peer 3.3.3.3 as 64512
[R4-bgp]peer 3.3.3.3 connect-interface l0

[R4-bgp]peer 172.16.1.10 as 64513
[R4-bgp]peer 172.16.1.10 next-hop-l

[R5]bgp 64513
[R5-bgp]con id 2
[R5-bgp]con peer 64512
[R5-bgp]peer 2.2.2.2 as 64512
[R5-bgp]peer 2.2.2.2 con l0
[R5-bgp]peer 2.2.2.2 next-hop-invariable
[R5-bgp]peer 2.2.2.2 next-hop-local
[R5-bgp]peer 6.6.6.6 as 64513
[R5-bgp]peer 6.6.6.6 con l0
[R5-bgp]peer 6.6.6.6 next-hop-local
[R5-bgp]peer 172.16.1.21 as 64512
Aug 8 2025 12:57:59-08:00 R5 %%01BGP/3/STATE_CHG_UPDOWN(l)[0]:The status of the
peer 172.16.1.21 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public,
StateChangeReason=Up)
[R5-bgp]peer 172.16.1.21 next-hop-local

[R6]bgp 64513
[R6-bgp]con id 2
[R6-bgp]peer 5.5.5.5 as 64513
[R6-bgp]peer 5.5.5.5 con l0
[R6-bgp]peer 5
Aug 8 2025 13:06:04-08:00 R6 %%01BGP/3/STATE_CHG_UPDOWN(l)[0]:The status of the
peer 5.5.5.5 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)
[R6-bgp]peer 5 next-hop-l.5.5.5 next-hop-l
[R6-bgp]peer 5.5.5.5 next-hop-l
[R6-bgp]peer 7.7.7.7 as 64513
[R6-bgp]peer 7.7.7.7 con l0
[R6-bgp]peer 7.7.7.7 next-hop-local

[R7]bgp 64513
[R7-bgp]con id 2
[R7-bgp]peer 6.6.6.6 as 64513
[R7-bgp]peer 6.6.6.6 con l0
[R7-bgp]peer 6.6.6.6 next-hop-l
[R7-bgp]peer 34.1.1.2 as 3
Aug 8 2025 13:09:12-08:00 R7 %%01BGP/3/STATE_CHG_UPDOWN(l)[0]:The status of the
peer 6.6.6.6 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, Sta
teChangeReason=Up)
[R7-bgp]peer 172.16.1.9 as 64512
[R7-bgp]peer 172.16.1.9 next-hop-l

[R8]bgp 3
[R8-bgp]peer 34.1.1.1 as-number 2

AS2的路由宣告自己的客户端网段：

[R2]bgp 64512
[R2-bgp]n 172.16.2.0 24

[R3]bgp 64512
[R3-bgp]net 172.16.3.0 24

[R4]bgp 64512
[R4-bgp]net 172.16.4.0 24

[R5]bgp 64513
[R5-bgp]net 172.16.5.0 24

[R7]bgp 64513
[R7-bgp]net 172.16.7.0 24

[R1]bgp 1
[R1-bgp]net 1.1.1.1 32

[R1-bgp]n 12.1.1.1 24

[R8]bgp 3
[R8-bgp]net 8.8.8.8 32

[R8-bgp]n 34.1.1.1 24

做路由反射器：