路由反射器

于 2024-07-25 20:12:12 发布
阅读量420 收藏 3
点赞数 5
分类专栏： HCIP-Datacom实验 文章标签： 前端 javascript 服务器
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/m0_66527209/article/details/140698744
版权

组网介绍

R1、R2、R3、R4都属于AS64511，其连接方式、互联接口地址如图所示。每台设备均创建Loopback0接口，IP地址为10.0.x.x/32，其中x为设备编号。R1、R2上的Loopback1地址分别为10.1.1.1/24、10.2.2.2/24，用于模拟用户网段。

所有设备都使用Loopback0地址作为BGP Router ID，R1与R2、R2与R3、R3与R4、R4与R2之间基于直连接口建立IBGP对等体关系，其中R1为R2的路由反射器客户端，R2为R3的路由反射器客户端，R3为R4的路由反射器客户端。

任务思路

  1. 设备基础IP地址配置。
  2. 配置AS内的OSPF，在互联接口、Loopback0接口上激活OSPF。
  3. 配置AS内基于直连接口建立IBGP对等体关系。
  4. 配置路由反射器，将R1配置为R2的客户端、R2配置为R3的客户端、R3配置为R4的客户端。
  5. 在R2上将Loopback1接口路由发布进BGP，观察Originator_ID属性如何实现路由防环。
  6. 在R1上将Loopback1接口路由发布进BGP，观察Cluster_List属性如何实现路由防环。

AR9

The device is running!
<Huawei>sys
Enter system view, return user view with Ctrl+Z.
[Huawei]sys AR9
[AR9]int lo0
[AR9-LoopBack0]ip add 10.0.1.1 32
[AR9-LoopBack0]int lo1
[AR9-LoopBack1]ip add 1024
[AR9-LoopBack1]int g0/0/0
[AR9-GigabitEthernet0/0/0]ip add 10.0.12.1 24
Jul 25 2024 19:28:51-08:00 AR9 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol IP
 on the interface GigabitEthernet0/0/0 has entered the UP state. 
[AR9]ospf 1 rou 10.0.1.1
[AR9-ospf-1]area 0
[AR9-ospf-1-area-0.0.0.0]net 10.0.1.1 0.0.0.0
Jul 25 2024 19:38:44-08:00 AR9 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes ev
ent: neighbor status changed. (ProcessId=256, NeighborAddress=2.12.0.10, Neighbo
rEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR9-ospf-1-area-0.0.0.0]
Jul 25 2024 19:38:49-08:00 AR9 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes ev
ent: neighbor status changed. (ProcessId=256, NeighborAddress=2.12.0.10, Neighbo
rEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart) 
[AR9-ospf-1-area-0.0.0.0]
Jul 25 2024 19:38:49-08:00 AR9 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes ev
ent: neighbor status changed. (ProcessId=256, NeighborAddress=2.12.0.10, Neighbo
rEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exch
ange) 
[AR9-ospf-1-area-0.0.0.0]
Jul 25 2024 19:38:49-08:00 AR9 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes ev
ent: neighbor status changed. (ProcessId=256, NeighborAddress=2.12.0.10, Neighbo
rEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadin
g) 
[AR9-ospf-1-area-0.0.0.0]
Jul 25 2024 19:38:49-08:00 AR9 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes ev
ent: neighbor status changed. (ProcessId=256, NeighborAddress=2.12.0.10, Neighbo
rEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR9-ospf-1-area-0.0.0.0]q
[AR9-ospf-1]q
[AR9]bgp 64511
[AR9-bgp]rou	
[AR9-bgp]route-select
[AR9-bgp]router-id 10.0.1.1
[AR9-bgp]peer 10.0.12.2 as 65411
[AR9-bgp]dis th
[V200R003C00]
#
bgp 64511
 router-id 10.0.1.1
 peer 10.0.12.2 as-number 65411 
 #
 ipv4-family unicast
  undo synchronization
  peer 10.0.12.2 enable
#
return
[AR9-bgp]undo peer 10.0.12.2 
[AR9-bgp]peer 10.0.12.2 as-number 64511
[AR9-bgp]
Jul 25 2024 19:49:47-08:00 AR9 %%01BGP/3/STATE_CHG_UPDOWN(l)[5]:The status of th
e peer 10.0.12.2 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public, 
StateChangeReason=Up)  
[AR9-bgp]
  Please check whether system data has been changed, and save data in time
  Configuration console time out, please press any key to log on
<AR9>sys
Enter system view, return user view with Ctrl+Z.
[AR9]bgp 64511
[AR9-bgp]net 10.1.1.0 24
[AR9-bgp]q
[AR9]display bgp routing-table 10.1.1.0 24
 BGP local router ID : 10.0.1.1
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.1.1.0/24:
 Network route. 
 From: 0.0.0.0 (0.0.0.0)
 Route Duration: 00h00m11s  
 Direct Out-interface: LoopBack1
 Original nexthop: 10.1.1.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, pref-val 0, valid, local, best, select, pre 0
 Advertised to such 1 peers:
    10.0.12.2
[AR9]q
<AR9>save
  The current configuration will be written to the device. 
  Are you sure to continue? (y/n)[n]:y
  It will take several minutes to save configuration file, please wait.......
  Configuration file had been saved successfully
  Note: The configuration file will take effect after being activated

AR10

The device is running!
<Huawei>sys
Enter system view, return user view with Ctrl+Z.
[Huawei]sys AR10
[AR10]int lo0
[AR10-LoopBack0]ip add 10.0.2.2 32
[AR10-LoopBack0]int lo1
[AR10-LoopBack1]ip add 10.1
[AR10-LoopBack1]int g0/0/0
[AR10-GigabitEthernet0/0/0]ip add 10.0.12.2 24
Jul 25 2024 19:30:00-08:00 AR10 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol I
P on the interface GigabitEthernet0/0/0 has entered the UP state. 
[AR10-GigabitEthernet0/0/0]int g0/0/1
[AR10-GigabitEthernet0/0/1]ip add 10.0.24
[AR10-GigabitEthernet0/0/1]
Jul 25 2024 19:30:19-08:00 AR10 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol I
P on the interface GigabitEthernet0/0/1 has entered the UP state. 
[AR10-GigabitEthernet0/0/1]int g0/0/2
[AR10-GigabitEthernet0/0/2]ip add 10.0.23
[AR10-GigabitEthernet0/0/2]
Jul 25 2024 19:30:33-08:00 AR10 %%01IFNET/4/LINK_STATE(l)[2]:The line protocol I
P on the interface GigabitEthernet0/0/2 has entered the UP state. 
[AR10]ospf 1 rou 10.0.2.2
[AR10-ospf-1]area 0
[AR10-ospf-1-area-0.0.0.0]net 10.0.2.2 0.0.0.0
[AR10-ospf-1-area-0.0.0.0]net 10.0.1
[AR10-ospf-1-area-0.0.0.0]net 10.0.12
Jul 25 2024 19:38:49-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=1.12.0.10, Neighb
orEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR10-ospf-1-area-0.0.0.0]net 10.0.12.2 0.0.0.0
Jul 25 2024 19:38:49-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=1.12.0.10, Neighb
orEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) 
[AR10-ospf-1-area-0.0.0.0]net 10.0.12.2 0.0.0.0
Jul 25 2024 19:38:49-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=1.12.0.10, Neighb
orEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) 
[AR10-ospf-1-area-0.0.0.0]net 10.0.12.2 0.0.0.0
Jul 25 2024 19:38:49-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=1.12.0.10, Neighb
orEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exc
hange) 
[AR10-ospf-1-area-0.0.0.0]net 10.0.12.2 0.0.0.0
Jul 25 2024 19:38:49-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=1.12.0.10, Neighb
orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi
ng) 
[AR10-ospf-1-area-0.0.0.0]net 10.0.12.2 0.0.0.
Jul 25 2024 19:38:49-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[5]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=1.12.0.10, Neighb
orEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR10-ospf-1-area-0.0.0.0]net 10.0.1.2 0.0.0.0
[AR10-ospf-1-area-0.0.0.0]net 10.0.24.2 0.0.0.0
[AR10-ospf-1-area-0.0.0.0]net 10.0.23.2 0.0.0.0
[AR10-ospf-1-area-0.0.0.0]dis th
[V200R003C00]
#
 area 0.0.0.0 
  network 10.0.1.2 0.0.0.0 
  network 10.0.2.2 0.0.0.0 
  network 10.0.12.2 0.0.0.0 
  network 10.0.23.2 0.0.0.0 
  network 10.0.24.2 0.0.0.0 
#
return
[AR10-ospf-1-area-0.0.0.0]undo network 10.0.1.2 0.0.0.0 
[AR10-ospf-1-area-0.0.0.0]
[AR10-ospf-1-area-0.0.0.0]
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:15-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[6]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.23.0.10, Neighb
orEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:16-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[7]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.23.0.10, Neighb
orEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:16-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[8]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.23.0.10, Neighb
orEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exc
hange) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:16-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[9]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.23.0.10, Neighb
orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi
ng) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:16-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[10]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=3.23.0.10, Neigh
borEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:08-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[11]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=4.24.0.10, Neigh
borEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:09-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[12]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=4.24.0.10, Neigh
borEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart)
 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:09-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[13]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=4.24.0.10, Neigh
borEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Ex
change) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:09-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[14]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=4.24.0.10, Neigh
borEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Load
ing) 
[AR10-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:09-08:00 AR10 %%01OSPF/4/NBR_CHANGE_E(l)[15]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=4.24.0.10, Neigh
borEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR10-ospf-1-area-0.0.0.0]
[AR10-ospf-1-area-0.0.0.0]q
[AR10-ospf-1]q
[AR10]dis ospf peer b	
[AR10]dis ospf peer brief 
	 OSPF Process 1 with Router ID 10.0.2.2
		  Peer Statistic Information
 ----------------------------------------------------------------------------
 Area Id          Interface                        Neighbor id      State    
 0.0.0.0          GigabitEthernet0/0/0             10.0.1.1         Full        
 0.0.0.0          GigabitEthernet0/0/1             10.0.4.4         Full        
 0.0.0.0          GigabitEthernet0/0/2             10.0.3.3         Full        
 ----------------------------------------------------------------------------
[AR10]bgp 64511
[AR10-bgp]router 10.0.2.2
[AR10-bgp]peer 10.0.12.1 as 64511
[AR10-bgp]peer 10.0.23.3 as 64511
[AR10-bgp]peer 10.0.34.4 as 64511
[AR10-bgp]
Jul 25 2024 19:46:07-08:00 AR10 %%01BGP/3/STATE_CHG_UPDOWN(l)[16]:The status of 
the peer 10.0.23.3 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public
, StateChangeReason=Up)  
[AR10-bgp]q
Jul 25 2024 19:47:56-08:00 AR10 %%01BGP/3/STATE_CHG_UPDOWN(l)[17]:The status of 
the peer 10.0.24.4 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public
, StateChangeReason=Up)  
Jul 25 2024 19:49:47-08:00 AR10 %%01BGP/3/STATE_CHG_UPDOWN(l)[18]:The status of 
the peer 10.0.12.1 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public
, StateChangeReason=Up)  
[AR10]dis bgp peer
 BGP local router ID : 10.0.2.2
 Local AS number : 64511
 Total number of peers : 3		  Peers in established state : 3
  Peer            V          AS  MsgRcvd  MsgSent  OutQ  Up/Down       State Pre
fRcv
  10.0.12.1       4       64511        2        3     0 00:00:07 Established    
   0
  10.0.23.3       4       64511        5        6     0 00:03:48 Established    
   0
  10.0.24.4       4       64511        3        5     0 00:01:58 Established    
   0
[AR10]bgp 64511
[AR10-bgp]peer 10.0.12.1 reflect-client 
[AR10-bgp]q
[AR10]acl 
[AR10-acl-basic-2000]rule 5 permit
[AR10-acl-basic-2000]q
[AR10]rou	
[AR10]route
[AR10]route-policy bgp deny node 10
Info: New Sequence of this List.
[AR10-route-policy]if	
[AR10-route-policy]if-match acl 2000
[AR10-route-policy]q
[AR10]bgp 64511	
[AR10-bgp]peer 10.0.24.4 route-policy bgp export 
[AR10-bgp]net 10.2.2.0 24
[AR10-bgp]q
[AR10]display bgp routing-table 10.2.2.0 24
 BGP local router ID : 10.0.2.2
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.2.2.0/24:
 Network route. 
 From: 0.0.0.0 (0.0.0.0)
 Route Duration: 00h00m16s  
 Direct Out-interface: LoopBack1
 Original nexthop: 10.2.2.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, pref-val 0, valid, local, best, select, pre 0
 Advertised to such 2 peers:
    10.0.23.3
    10.0.12.1
[AR10]display bgp routing-table 10.2.2.0 24
 BGP local router ID : 10.0.2.2
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.2.2.0/24:
 Network route. 
 From: 0.0.0.0 (0.0.0.0)
 Route Duration: 00h01m06s  
 Direct Out-interface: LoopBack1
 Original nexthop: 10.2.2.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, pref-val 0, valid, local, best, select, pre 0
 Advertised to such 2 peers:
    10.0.23.3
    10.0.12.1
[AR10]display bgp peer 10.0.24.4 verbose 
	BGP Peer is 10.0.24.4,  remote AS 64511  
	Type: IBGP link
	BGP version 4, Remote router ID 10.0.4.4
	Update-group ID: 2  
	BGP current state: Established, Up for 00h06m04s 
	BGP current event: KATimerExpired
	BGP last state: OpenConfirm
	BGP Peer Up count: 1
	Received total routes: 0
	Received active routes total: 0
	Advertised total routes: 0
	Port:  Local - 179	Remote - 49606
	Configured: Connect-retry Time: 32 sec
	Configured: Active Hold Time: 180 sec	Keepalive Time:60 sec
	Received  : Active Hold Time: 180 sec
	Negotiated: Active Hold Time: 180 sec	Keepalive Time:60 sec
	Peer optional capabilities:
	Peer supports bgp multi-protocol extension
	Peer supports bgp route refresh capability
	Peer supports bgp 4-byte-as capability
	Address family IPv4 Unicast: advertised and received
 Received: Total 11 messages
		 Update messages 		3 
		 Open messages 			1 
		 KeepAlive messages 		7 
		 Notification messages  	0 
		 Refresh messages 		0
 Sent: Total 12 messages
		 Update messages 		2 
		 Open messages 			3 
		 KeepAlive messages 		7 
		 Notification messages  	0 
		 Refresh messages 		0
 Authentication type configured: None
 Last keepalive received: 2024/07/25 19:53:56 UTC-08:00    
 Last keepalive sent    : 2024/07/25 19:53:56 UTC-08:00    
 Last update    received: 2024/07/25 19:52:57 UTC-08:00    
 Last update    sent    : 2024/07/25 19:52:57 UTC-08:00    
 Minimum route advertisement interval is 15 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Peer Preferred Value: 0
 Routing policy configured:
 No import update filter list
 No export update filter list
 No import prefix list
 No export prefix list
 No import route policy 
 Export route policy is: bgp
 No import distribute policy 
 No export distribute policy 
<AR10>refresh bgp 10.0.24.4 import
<AR10>display bgp peer 10.0.24.4 verbose | in Update
	Update-group ID: 2
	BGP current event: RecvUpdate
		 Update messages 		4
		 Update messages 		2
<AR10>display bgp routing-table 10.2.2.0 24
 BGP local router ID : 10.0.2.2
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.2.2.0/24:
 Network route. 
 From: 0.0.0.0 (0.0.0.0)
 Route Duration: 00h02m14s  
 Direct Out-interface: LoopBack1
 Original nexthop: 10.2.2.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, pref-val 0, valid, local, best, select, pre 0
 Advertised to such 2 peers:
    10.0.23.3
    10.0.12.1
[AR10]bgp 64511
[AR10-bgp]undo net 10.2.2.0 24
[AR10-bgp]q
[AR10]display bgp routing-table 10.1.1.0 24
 BGP local router ID : 10.0.2.2
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.1.1.0/24:
 RR-client route.
 From: 10.0.12.1 (10.0.1.1)
 Route Duration: 00h00m32s  
 Relay IP Nexthop: 0.0.0.0
 Relay IP Out-Interface: GigabitEthernet0/0/0
 Original nexthop: 10.0.12.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, bes
t, select, active, pre 255
 Advertised to such 1 peers:
    10.0.23.3
[AR10]display bgp routing-table
 BGP Local router ID is 10.0.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
 *>i  10.1.1.0/24        10.0.12.1       0          100        0      i
[AR10]display bgp peer 10.0.24.4 verbose
	BGP Peer is 10.0.24.4,  remote AS 64511  
	Type: IBGP link
	BGP version 4, Remote router ID 10.0.4.4
	Update-group ID: 2  
	BGP current state: Established, Up for 00h09m19s 
	BGP current event: KATimerExpired
	BGP last state: OpenConfirm
	BGP Peer Up count: 1
	Received total routes: 0
	Received active routes total: 0
	Advertised total routes: 0
	Port:  Local - 179	Remote - 49606
	Configured: Connect-retry Time: 32 sec
	Configured: Active Hold Time: 180 sec	Keepalive Time:60 sec
	Received  : Active Hold Time: 180 sec
	Negotiated: Active Hold Time: 180 sec	Keepalive Time:60 sec
	Peer optional capabilities:
	Peer supports bgp multi-protocol extension
	Peer supports bgp route refresh capability
	Peer supports bgp 4-byte-as capability
	Address family IPv4 Unicast: advertised and received
 Received: Total 17 messages
		 Update messages 		6 
		 Open messages 			1 
		 KeepAlive messages 		10 
		 Notification messages  	0 
		 Refresh messages 		0
 Sent: Total 16 messages
		 Update messages 		2 
		 Open messages 			3 
		 KeepAlive messages 		10 
		 Notification messages  	0 
		 Refresh messages 		1
 Authentication type configured: None
 Last keepalive received: 2024/07/25 19:56:56 UTC-08:00    
 Last keepalive sent    : 2024/07/25 19:56:56 UTC-08:00    
 Last update    received: 2024/07/25 19:55:54 UTC-08:00    
 Last update    sent    : 2024/07/25 19:52:57 UTC-08:00    
 Minimum route advertisement interval is 15 seconds
 Optional capabilities:
 Route refresh capability has been enabled
 4-byte-as capability has been enabled
 Peer Preferred Value: 0
 Routing policy configured:
 No import update filter list
 No export update filter list
 No import prefix list
 No export prefix list
 No import route policy 
 Export route policy is: bgp
 No import distribute policy 
 No export distribute policy 
[AR10]q
<AR10>refresh bgp 10.0.24.4 import
<AR10>display bgp peer 10.0.24.4 verbose | in Update
	Update-group ID: 2
	BGP current event: RecvUpdate
		 Update messages 		7
		 Update messages 		2
<AR10>display bgp routing-table 10.1.1.0 24
 BGP local router ID : 10.0.2.2
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.1.1.0/24:
 RR-client route.
 From: 10.0.12.1 (10.0.1.1)
 Route Duration: 00h02m00s  
 Relay IP Nexthop: 0.0.0.0
 Relay IP Out-Interface: GigabitEthernet0/0/0
 Original nexthop: 10.0.12.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, bes
t, select, active, pre 255
 Advertised to such 1 peers:
    10.0.23.3
<AR10>save
  The current configuration will be written to the device. 
  Are you sure to continue? (y/n)[n]:y
  It will take several minutes to save configuration file, please wait.......
  Configuration file had been saved successfully
  Note: The configuration file will take effect after being activated

AR11

The device is running!
<Huawei>sys
Enter system view, return user view with Ctrl+Z.
[Huawei]sys AR11
[AR11]int lo0
[AR11-LoopBack0]ip add 10.0.3.3 32
[AR11-LoopBack0]int g0/0/2
[AR11-GigabitEthernet0/0/2]ip add 10.0.23.3 24
Jul 25 2024 19:31:27-08:00 AR11 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol I
P on the interface GigabitEthernet0/0/2 has entered the UP state. 
[AR11-GigabitEthernet0/0/2]int g0/0/0
[AR11-GigabitEthernet0/0/0]ip add 10.0.34
Jul 25 2024 19:31:46-08:00 AR11 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol I
P on the interface GigabitEthernet0/0/0 has entered the UP state. 
[AR11-GigabitEthernet0/0/0]
  Please check whether system data has been changed, and save data in time
  Configuration console time out, please press any key to log on
<AR11>sys
Enter system view, return user view with Ctrl+Z.
[AR11]ospf 1 rou 10.0.3.3
[AR11-ospf-1]area 0
[AR11-ospf-1-area-0.0.0.0]net 10.0.3.3 0.0.0.0
[AR11-ospf-1-area-0.0.0.0]net 10.0.23.2 0.0.0.0
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:17-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.23.0.10, Neighb
orEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:17-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.23.0.10, Neighb
orEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:17-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.23.0.10, Neighb
orEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:17-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.23.0.10, Neighb
orEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exc
hange) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:17-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.23.0.10, Neighb
orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi
ng) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:40:17-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[5]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.23.0.10, Neighb
orEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR11-ospf-1-area-0.0.0.0]net 10.0.34
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:15-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[6]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=4.34.0.10, Neighb
orEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:20-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[7]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=4.34.0.10, Neighb
orEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=ExStart) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:20-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[8]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=4.34.0.10, Neighb
orEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exc
hange) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:20-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[9]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=4.34.0.10, Neighb
orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi
ng) 
[AR11-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:20-08:00 AR11 %%01OSPF/4/NBR_CHANGE_E(l)[10]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=4.34.0.10, Neigh
borEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR11-ospf-1-area-0.0.0.0]q
[AR11-ospf-1]q
[AR11]display ospf peer brief 
	 OSPF Process 1 with Router ID 10.0.3.3
		  Peer Statistic Information
 ----------------------------------------------------------------------------
 Area Id          Interface                        Neighbor id      State    
 0.0.0.0          GigabitEthernet0/0/2             10.0.2.2         Full        
 0.0.0.0          GigabitEthernet0/0/0             10.0.4.4         Full        
 ----------------------------------------------------------------------------
[AR11]bgp 64511
[AR11-bgp]router 10.0.3.3
[AR11-bgp]peer 10.0.23.2 as 64511
[AR11-bgp]peer 10.0.34.4 as 64511
[AR11-bgp]
Jul 25 2024 19:46:07-08:00 AR11 %%01BGP/3/STATE_CHG_UPDOWN(l)[11]:The status of 
the peer 10.0.23.2 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public
, StateChangeReason=Up)  
[AR11-bgp]
Jul 25 2024 19:48:08-08:00 AR11 %%01BGP/3/STATE_CHG_UPDOWN(l)[12]:The status of 
the peer 10.0.34.4 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public
, StateChangeReason=Up)  
[AR11-bgp]peer 10.0.23.2 reflect-client 
[AR11-bgp]q
[AR11]display bgp routing-table 10.2.2.0 24
 BGP local router ID : 10.0.3.3
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.2.2.0/24:
 RR-client route.
 From: 10.0.23.2 (10.0.2.2)
 Route Duration: 00h00m33s  
 Relay IP Nexthop: 0.0.0.0
 Relay IP Out-Interface: GigabitEthernet0/0/2
 Original nexthop: 10.0.23.2
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, bes
t, select, active, pre 255
 Advertised to such 1 peers:
    10.0.34.4
[AR11]display bgp routing-table 10.1.1.0 24
 BGP local router ID : 10.0.3.3
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.1.1.0/24:
 RR-client route.
 From: 10.0.23.2 (10.0.2.2)
 Route Duration: 00h00m42s  
 Relay IP Nexthop: 10.0.23.2
 Relay IP Out-Interface: GigabitEthernet0/0/2
 Original nexthop: 10.0.12.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, bes
t, select, active, pre 255, IGP cost 2
 Originator:  10.0.1.1
 Cluster list: 10.0.2.2
 Advertised to such 1 peers:
    10.0.34.4
[AR11]q
<AR11>save
  The current configuration will be written to the device. 
  Are you sure to continue? (y/n)[n]:y
  It will take several minutes to save configuration file, please wait.......
  Configuration file had been saved successfully
  Note: The configuration file will take effect after being activated

AR12

The device is running!
<Huawei>sys
Enter system view, return user view with Ctrl+Z.
[Huawei]sys AR12
[AR12]int lo0
[AR12-LoopBack0]ip add 10.0.4.4 32
[AR12-LoopBack0]int g0/0/0
[AR12-GigabitEthernet0/0/0]ip add 10.0.34.4 24
Jul 25 2024 19:32:35-08:00 AR12 %%01IFNET/4/LINK_STATE(l)[0]:The line protocol I
P on the interface GigabitEthernet0/0/0 has entered the UP state. 
[AR12-GigabitEthernet0/0/0]int g0/0/2
[AR12-GigabitEthernet0/0/2]ip add 10.0.2
Jul 25 2024 19:32:53-08:00 AR12 %%01IFNET/4/LINK_STATE(l)[1]:The line protocol I
P on the interface GigabitEthernet0/0/2 has entered the UP state. 
[AR12-GigabitEthernet0/0/2]
  Please check whether system data has been changed, and save data in time
  Configuration console time out, please press any key to log on
<AR12>sys
Enter system view, return user view with Ctrl+Z.
[AR12]ospf 1 rou 10.0.4.4
[AR12-ospf-1]area 0
[AR12-ospf-1-area-0.0.0.0]net 10.0.4.4 0.0.0.0
[AR12-ospf-1-area-0.0.0.0]net 10.0.24.2 0.0.0.0
[AR12-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:10-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[0]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.24.0.10, Neighb
orEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR12-ospf-1-area-0.0.0.0]net 10.0.24.4 0.0.0.0
Jul 25 2024 19:41:10-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[1]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.24.0.10, Neighb
orEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) 
[AR12-ospf-1-area-0.0.0.0]net 10.0.24.4 0.0.0.0
Jul 25 2024 19:41:10-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[2]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.24.0.10, Neighb
orEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) 
[AR12-ospf-1-area-0.0.0.0]net 10.0.24.4 0.0.0.0
Jul 25 2024 19:41:10-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[3]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.24.0.10, Neighb
orEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exc
hange) 
[AR12-ospf-1-area-0.0.0.0]net 10.0.24.4 0.0.0.0
Jul 25 2024 19:41:10-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[4]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.24.0.10, Neighb
orEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Loadi
ng) 
[AR12-ospf-1-area-0.0.0.0]net 10.0.24.4 0.0.0.0
Jul 25 2024 19:41:10-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[5]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=2.24.0.10, Neighb
orEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR12-ospf-1-area-0.0.0.0]net 10.0.34.3 0.0.0.0
[AR12-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:21-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[6]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.34.0.10, Neighb
orEvent=HelloReceived, NeighborPreviousState=Down, NeighborCurrentState=Init) 
[AR12-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:21-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[7]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.34.0.10, Neighb
orEvent=2WayReceived, NeighborPreviousState=Init, NeighborCurrentState=2Way) 
[AR12-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:21-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[8]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.34.0.10, Neighb
orEvent=AdjOk?, NeighborPreviousState=2Way, NeighborCurrentState=ExStart) 
[AR12-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:21-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[9]:Neighbor changes e
vent: neighbor status changed. (ProcessId=256, NeighborAddress=3.34.0.10, Neighb
orEvent=NegotiationDone, NeighborPreviousState=ExStart, NeighborCurrentState=Exc
hange) 
[AR12-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:21-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[10]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=3.34.0.10, Neigh
borEvent=ExchangeDone, NeighborPreviousState=Exchange, NeighborCurrentState=Load
ing) 
[AR12-ospf-1-area-0.0.0.0]
Jul 25 2024 19:41:21-08:00 AR12 %%01OSPF/4/NBR_CHANGE_E(l)[11]:Neighbor changes 
event: neighbor status changed. (ProcessId=256, NeighborAddress=3.34.0.10, Neigh
borEvent=LoadingDone, NeighborPreviousState=Loading, NeighborCurrentState=Full) 
[AR12-ospf-1-area-0.0.0.0]q
[AR12-ospf-1]q
[AR12]dis ospf routing 
	 OSPF Process 1 with Router ID 10.0.4.4
		  Routing Tables 
 Routing for Network 
 Destination        Cost  Type       NextHop         AdvRouter       Area
 10.0.4.4/32        0     Stub       10.0.4.4        10.0.4.4        0.0.0.0
 10.0.24.0/24       1     Transit    10.0.24.4       10.0.4.4        0.0.0.0
 10.0.34.0/24       1     Transit    10.0.34.4       10.0.4.4        0.0.0.0
 10.0.1.1/32        2     Stub       10.0.24.2       10.0.1.1        0.0.0.0
 10.0.2.2/32        1     Stub       10.0.24.2       10.0.2.2        0.0.0.0
 10.0.3.3/32        1     Stub       10.0.34.3       10.0.3.3        0.0.0.0
 10.0.12.0/24       2     Transit    10.0.24.2       10.0.1.1        0.0.0.0
 10.0.23.0/24       2     Transit    10.0.24.2       10.0.2.2        0.0.0.0
 10.0.23.0/24       2     Transit    10.0.34.3       10.0.2.2        0.0.0.0
 Total Nets: 9  
 Intra Area: 9  Inter Area: 0  ASE: 0  NSSA: 0 
[AR12]bgp 64511
[AR12-bgp]router 10.0.4.4
[AR12-bgp]peer 10.0.24.2 as 64511
[AR12-bgp]peer 10.0.34.3 as 64511
[AR12-bgp]
Jul 25 2024 19:47:57-08:00 AR12 %%01BGP/3/STATE_CHG_UPDOWN(l)[12]:The status of 
the peer 10.0.24.2 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public
, StateChangeReason=Up)  
[AR12-bgp]
Jul 25 2024 19:48:08-08:00 AR12 %%01BGP/3/STATE_CHG_UPDOWN(l)[13]:The status of 
the peer 10.0.34.3 changed from OPENCONFIRM to ESTABLISHED. (InstanceName=Public
, StateChangeReason=Up)  
[AR12-bgp]peer 10.0.34.3 reflect-client 
[AR12-bgp]q
[AR12]display bgp routing-table 10.2.2.0 24
 BGP local router ID : 10.0.4.4
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.2.2.0/24:
 RR-client route.
 From: 10.0.34.3 (10.0.3.3)
 Route Duration: 00h00m43s  
 Relay IP Nexthop: 10.0.24.2
 Relay IP Out-Interface: GigabitEthernet0/0/2
 Original nexthop: 10.0.23.2
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, bes
t, select, active, pre 255, IGP cost 2
 Originator:  10.0.2.2
 Cluster list: 10.0.3.3
 Advertised to such 1 peers:
    10.0.24.2
[AR12]display bgp routing-table 10.1.1.0 24
 BGP local router ID : 10.0.4.4
 Local AS number : 64511
 Paths:   1 available, 1 best, 1 select
 BGP routing table entry information of 10.1.1.0/24:
 RR-client route.
 From: 10.0.34.3 (10.0.3.3)
 Route Duration: 00h00m50s  
 Relay IP Nexthop: 10.0.24.2
 Relay IP Out-Interface: GigabitEthernet0/0/2
 Original nexthop: 10.0.12.1
 Qos information : 0x0
 AS-path Nil, origin igp, MED 0, localpref 100, pref-val 0, valid, internal, bes
t, select, active, pre 255, IGP cost 2
 Originator:  10.0.1.1
 Cluster list: 10.0.3.3, 10.0.2.2
 Advertised to such 1 peers:
    10.0.24.2
[AR12]q
<AR12>save
  The current configuration will be written to the device. 
  Are you sure to continue? (y/n)[n]:y
  It will take several minutes to save configuration file, please wait.......
  Configuration file had been saved successfully
  Note: The configuration file will take effect after being activated

BGP 路由反射器
yangheng48的博客
01-04 1643
Cisco BGP 路由高级特性-反射器详解
利用route-reflector路由反射器打破IBGP防环机制.doc
07-06
**路由反射器（Route-Reflector，RR）**在BGP（边界网关协议）中是一种重要的工具，用于解决IBGP（内部BGP）的防环机制问题。IBGP的一个核心防环策略是，从一个IBGP邻居学到的路由不会被转发给另一个IBGP邻居，除非...
08 BGP路径属性与路由反射器.pptx
01-25
08 BGP路径属性与路由反射器
Router Reflector(路由反射器）
weixin_63058714的博客
09-23 908
BGP路由反射器
RR路由反射器
热门推荐
weixin_45537413的博客
04-09 1万+
1 路由反射器简介 路由反射器（RR）的作用主要是为了简化IBGP邻居配置，使用反射器后允许反射器将来自IBGP邻居的路由信息发给另一个或一组IBGP邻居。路由器让被配置为路由反射器的路由器向其他IBGP对等体传输由IBGP所学到的路由来修改BGP的横向隔离规则，也就不再需要全互连的IBGP对等体。 1.1 BGP反射器RR的相关角色 路由反射器：是被配置为允许它把通过IBGP所学到的路由通告（或反射）到其他IBGP对等体的路由器； 客户：是和路由反射器有IBGP对等关系并配置成反射邻...
1.路由反射器
m0_70976024的博客
01-03 1141
为保证IBGP对等体之间的连通性，需要在IBGP对等体之间建立全连接Full-mesh）关系。假设在一个AS内部有n台路由器，那么应该建立的IBGP连接数就为n(n-1)/2。当IBGP对等体数目很多时，对网络资源和CPU资源的消耗都很大。利用路由反射可以解决这一问题。在一个AS内，其中一台路由器作为路由反射器RR（Route Reflector），其它路由器作为客户机（Client）。客户机与路由反射器之间建立IBGP连接。路由反射器和它的客户机组成一个集群（Cluster）。路由反射器。
保障IBGP路由传递的利器——路由反射器RR.doc
07-17
《保障IBGP路由传递的利器——路由反射器RR》 在大规模自治系统(AS)中，内部边界网关协议(IBGP)的水平分割策略导致了一个关键问题：从一个IBGP邻居学到的路由不会被转发给其他IBGP邻居，从而限制了路由信息的全面...
bgp路由反射器实验解析
07-08
"bgp路由反射器实验解析" 本实验旨在介绍BGP路由协议和路由反射器的原理与实验解析，通过搭建实验环境，模拟实施过程中遇到的问题。 路由反射器的概念 在一个BGP域中，一个路由器通过IBGP从另一个路由器学习到的...
路由反射器 route reflector {RR}
weixin_34082695的博客
03-07 638
实验目标: PC-1 ----> PC-2 1.配置 PC-1/2 的IP地址和网关IP地址： 192.168.1.1 255.255.255.0192.168.1.254 192.168.2.1 255.255.255.0 192.168.2.254 2.配置网络中的 IGP ： OSPF R1:interface loopback 13ip address 10.10.1.1 255...
路由反射器和联邦
最新发布
weixin_74227828的博客
05-17 805
路由器从IBGP对等体收到一条IBGP路由，并且该路由所携带的起源者ID属性与本地的BGP RID相同时，则会意识到该路由信息是从本地始发的信息，将忽略这条路由信息的更新。当一台==路由反射器==收到BGP路由时，若发现该路由携带簇列表，并且簇列表中包含自己本地的簇ID，则忽略这条路由信息的更新。我们将RR与其的客户端所构成的系统称为路由反射簇，每一个路由反射簇都将使用RR的RID作为簇ID，来标识不同的反射簇。成员AS之间的EBGP对等体关系是一种特殊的EBGP对等体，被称为联邦EBGP邻居关系。
BGP路由反射器
a18515004352_的博客
06-07 5363
路由反射器（Route Reflector）　　在使用BGP路由协议的网络中，为保证IBGP对等体之间的连通性，需要在IBGP对等体之间建立全连接关系。假设在一个AS内部有n台路由器，那么应该建立的IBGP连接数就为n(n-1)/2.当IBGP对等体数目很多时，对网络资源和CPU资源的消耗都很大。　　一、路由反射器的定义　　利用路由反射可以解决这一问题。在一个AS内，其中一台路由器作为路由反射器R...
路由反射器（Route Reflector）简介
weixin_30398227的博客
01-09 326
关键字：Reflector 客户机 反射器 路由技术路由器 　　在使用BGP路由协议的网络中，为保证IBGP对等体之间的连通性，需要在IBGP对等体之间建立全连接关系。假设在一个AS内部有n台路由器，那么应该建立的IBGP连接数就为n(n-1)/2.当IBGP对等体数目很多时，对网络资源和CPU资源的消耗都很大。 　　一、路由反射器的定义 　　利用路由反射可以解决这一问题。...
路由反射器、联邦
weixin_56094492的博客
04-14 926
RFC4456IBGP水平分割:路由器无法将从IBGP对等体学习到的路由信息传递给其他IBGP对等体。IBGP水平分割解决了AS内部环路的问题，但是产生了新的问题----
BGP 路由反射器详解，RR反射簇与RR的防环机制介绍与实验
Hades_Ling的CSDN博客
04-03 1万+
RR（Route Reflector）：路由反射器由于水平分割的原因，为了保证AS内所有的BGP路由器都能学习到完整的BGP路由，就必须在AS内实现IBGP全互联。然而实现IBGP全互联存在诸多短板：路由器需维护大量的TCP及BGP连接，尤其在路由器数量较多时。AS内BGP网络的可扩展性较差，因为通过纯手工配置命令。为了解决该问题，可应用到RR路由反射器技术。
路由反射器 RR 配置实验
01-30 774
Cluster：集群，RR 及其 客户机的集合，Cluster_List 用来集群间防环（RR 和它的客户机组成一个集群 Cluster，使用AS内唯一的Cluster ID 做为标识 ，当RR收到一条更新路由时，会检查Cluster List，如果列表中已经有本地的 Cluster ID ，则丢弃该路由，如果没有，则将其加入 Cluster List，然后反射该路由）；在 R4 上配置路由反射，R3 为反射客户端，在 R3 上查看 BGP 路由表，发现有 R6 的路由了，测试可 Ping 通；
路由反射器，联邦，BGP选路原则，社团属性
m0_55651966的博客
07-28 491
路由反射器，联邦，BGP选路原则，社团属性
BGP路由反射器RR
11-06
BGP路由反射器RR（Route Reflector）是一种BGP机制，用于解决BGP在大规模网络中的路由反馈问题。在传统的BGP网络中，所有的BGP路由器都需要与其他BGP路由器建立全互联关系，这会导致网络中的路由信息过多，造成网络拓扑复杂，维护成本高。而BGP路由反射器RR则可以减少BGP路由器之间的互联关系，降低网络的复杂度和维护成本。 BGP路由反射器RR的工作原理是将某些BGP路由器指定为路由反射器，其他BGP路由器则成为其客户端。路由反射器会将其收到的路由信息反射给其客户端，客户端再将路由信息反射给其它客户端，从而实现路由信息的分发。这样，BGP路由器之间的互联关系就可以减少，网络的复杂度和维护成本也会降低。 需要注意的是，在BGP路由反射器RR环境中，可能会出现路由反射环路的问题，即某个路由信息从一个路由反射器反射到另一个路由反射器，然后再反射回原来的路由反射器，形成一个环路。这种情况下，BGP路由器可能会学习到重复的路由信息，导致网络出现问题。为了解决这个问题，可以使用BGP路由反射器RR集群或者BGP路由服务器来避免路由反射环路的问题。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值