2547 source的iBGP源接口

Question

我一直试图在VIRL环境中使用“mpls nhrp”设置来获得2547 online，我已经让它使用了我在网上看到的一些示例，但所有在线示例都以中心作为路由反射器，并使用隧道接口进行BGP对等。如果我使用我的隧道接口作为我的iBGP对等源，但如果我不工作，那么出于某种原因，事情停止了吗？

这是我的一些显示命令的输出，我认为这是问题所在，但我不知道如何修复。在“显示ip cef vrf类详细信息”中，我看到前缀，并将其递归解析到隧道接口。在“显示mpls转发表”中，它说要删除标签吗？提前感谢您的帮助。

显示mpls转发表

IR-01#show mpls forwarding-table 
Local Outgoing Prefix Bytes Label Outgoing Next Hop 
Label Label or Tunnel Id Switched interface 
305 202 0.0.0.0/0[V] 0 drop 
307 205 10.10.1.0/24[V] 0 drop 
308 No Label 10.30.1.0/24[V] 0 aggregate/CLASS 
313 307 10.50.1.0/24[V] 0 drop


IR-01#show ip cef vrf CLASS detail 
IPv4 CEF is enabled and running
VRF CLASS
17 prefixes (17/0 fwd/non-fwd)
Table id 0x2
Database epoch: 0 (17 entries at this epoch)

0.0.0.0/0, epoch 0, flags [rib defined all labels, default route]
local label info: other/305
recursive via 10.10.0.251 label 202
recursive via 10.10.0.250/31
nexthop 1.0.2.10 Tunnel102
0.0.0.0/8, epoch 0
Special source: drop
drop
0.0.0.0/32, epoch 0, flags [receive]
Special source: receive
receive
10.10.1.0/24, epoch 0, flags [rib defined all labels]
local label info: other/307
recursive via 10.10.0.251 label 205
recursive via 10.10.0.250/31
nexthop 1.0.2.10 Tunnel102
10.30.1.0/24, epoch 0, flags [attached]
local label info: other/308
attached to Null0
10.30.1.0/31, epoch 0, flags [attached, connected]
attached to Loopback1
10.30.1.1/32, epoch 0, flags [receive, local, source eligible]
Interface source: Loopback1 flags: local, source eligible
receive for Loopback1
10.30.1.32/30, epoch 0, flags [attached, connected, cover dependents, need deagg]
Covered dependent prefixes: 2
need deagg: 2
attached to GigabitEthernet0/2.20
10.30.1.32/32, epoch 0, flags [receive]
Interface source: GigabitEthernet0/2.20 flags: none
Dependent covered prefix type cover need deagg, cover 10.30.1.32/30
receive for GigabitEthernet0/2.20
10.30.1.33/32, epoch 0, flags [receive, local, source eligible]
Interface source: GigabitEthernet0/2.20 flags: local, source eligible
receive for GigabitEthernet0/2.20
10.30.1.35/32, epoch 0, flags [receive]
Interface source: GigabitEthernet0/2.20 flags: none
Dependent covered prefix type cover need deagg, cover 10.30.1.32/30
receive for GigabitEthernet0/2.20
10.50.1.0/24, epoch 0, flags [rib defined all labels]
local label info: other/313
recursive via 10.50.0.251 label 307
recursive via 10.50.0.250/31
nexthop 1.0.2.10 Tunnel102
127.0.0.0/8, epoch 0
Special source: drop
drop
224.0.0.0/4, epoch 0
Special source: drop
drop
224.0.0.0/24, epoch 0, flags [receive]
Special source: receive
receive
240.0.0.0/4, epoch 0
Special source: drop
drop
255.255.255.255/32, epoch 0, flags [receive]
Special source: receive
receive


IR-01#sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area 
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
       a - application route
       + - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

      1.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
C        1.0.2.0/24 is directly connected, Tunnel102
L        1.0.2.30/32 is directly connected, Tunnel102
H        1.0.2.50/32 is directly connected, 00:07:01, Tunnel102
      10.0.0.0/8 is variably subnetted, 15 subnets, 3 masks
O        10.10.0.20/30 [110/1001] via 1.0.2.10, 00:42:50, Tunnel102
O        10.10.0.24/30 [110/1002] via 1.0.2.10, 00:42:50, Tunnel102
O        10.10.0.250/31 [110/1001] via 1.0.2.10, 00:42:50, Tunnel102
O        10.10.0.254/31 [110/1002] via 1.0.2.10, 00:42:50, Tunnel102
C        10.30.0.0/30 is directly connected, GigabitEthernet0/1
L        10.30.0.2/32 is directly connected, GigabitEthernet0/1
O        10.30.0.4/30 [110/2] via 10.30.0.1, 10:43:28, GigabitEthernet0/1
C        10.30.0.32/30 is directly connected, GigabitEthernet0/2.10
L        10.30.0.33/32 is directly connected, GigabitEthernet0/2.10
C        10.30.0.64/30 is directly connected, GigabitEthernet0/3
L        10.30.0.65/32 is directly connected, GigabitEthernet0/3
C        10.30.0.250/31 is directly connected, Loopback0
L        10.30.0.251/32 is directly connected, Loopback0
O        10.30.0.253/32 [110/2] via 10.30.0.1, 10:43:28, GigabitEthernet0/1
O        10.50.0.250/31 [110/2001] via 1.0.2.10, 00:42:40, Tunnel102
      192.168.0.0/24 is variably subnetted, 4 subnets, 2 masks
S        192.168.0.0/24 [1/0] via 10.30.0.66
O E2     192.168.0.10/32 [110/100] via 10.30.0.1, 10:42:44, GigabitEthernet0/1
C        192.168.0.30/32 is directly connected, Loopback100
O E2     192.168.0.50/32 [110/100] via 10.30.0.1, 10:43:16, GigabitEthernet0/1
IR-01# sh ip route vrf CLASS 

Routing Table: CLASS
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
       D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area 
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
       ia - IS-IS inter area, * - candidate default, U - per-user static route
       o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
       a - application route
       + - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is 10.10.0.251 to network 0.0.0.0

B*    0.0.0.0/0 [200/0] via 10.10.0.251, 00:42:06
      10.0.0.0/8 is variably subnetted, 7 subnets, 4 masks
B        10.10.1.0/24 [200/0] via 10.10.0.251, 00:42:06
S        10.30.1.0/24 is directly connected, Null0
C        10.30.1.0/31 is directly connected, Loopback1
L        10.30.1.1/32 is directly connected, Loopback1
C        10.30.1.32/30 is directly connected, GigabitEthernet0/2.20
L        10.30.1.33/32 is directly connected, GigabitEthernet0/2.20
B        10.50.1.0/24 [200/0] via 10.50.0.251, 00:42:06
IR-01# 

Answer 1

基于提供的bug链接的

编辑：

这显然是个窃听器。给出了解决方法，我认为您需要按照解决方案中的规定使用隧道接口，直到出现代码修复为止。对于代码错误，我们没有神奇的解决方案。请参阅下面最后一行错误报告中突出显示的文本：

症状: DMVPN轮辐节点之间的分组转发在经过辐式轮辐路径时成功，当遍历直线式辐式路径时失败。如果源或端点是VRF内辐节点上的直接连接接口地址，该接口具有/32掩码，并且使用'mpls‘配置在DMVPN隧道接口上的MPLSoDMVPN，则直接辐辐转发将失败。此外，使用回收站接口在Spokes上执行iBGP窥视也将失败，无论环回接口上的网络掩码是什么，因为iBGP窥视仍将使用/32前缀进行。条件:使用"mpls“配置的MPLSoDMVPN 二五四七设置。要求设置直辐对辐式隧道.解决办法:将接口掩码更改为/32以外的东西，如/31。虽然这最终会浪费每个这样的接口的地址。如果iBGP在环回接口上窥视，请使用隧道接口。