简介
本文档说明在集中控制策略中使用set tloc-action时,重叠管理协议(OMP)路由为什么会保持无效
拓扑
在本示例中,站点40和站点60之间的流量通过站点50导向。该策略在vEdge2上设置中间TLOC,并使用tloc-action primary,以便流量首选通过中间站点的商业Internet路径。

背景
集中控制策略中的tloc-action不起作用,即使数据平面隧道似乎处于启用状态,它描述了如何更正配置。
配置
本文档中的信息都是基于特定实验室环境中的设备编写的。本文档中使用的所有设备最初均采用原始(默认)配置。如果您的网络处于活动状态,请确保您了解所有命令的潜在影响。本文使用vEdge和控制器软件版本18.3.5。
所有站点都连接到biz-internet和private颜色,此表汇总了配置。
| 主机名 |
站点ID |
system-ip |
biz-internet链接上的ip-address |
private1链路上的ip-address |
| vEdge1 |
40 |
192.168.30.104
|
192.168.109.181
|
192.168.110.181
|
| vEdge2 |
50 |
192.168.30.105
|
192.168.109.182
|
192.168.110.182
|
| vEdge3 |
60 |
192.168.30.106
|
192.168.109.183
|
192.168.110.183
|
| vSmart |
1 |
192.168.30.103
|
|
|
vEdge上没有特殊配置。使用两个默认路由的配置非常简单,为了简洁起见,此处省略了这两个默认路由。
在vSmart上,应用了以下配置:
lists
vpn-list VPN_40
vpn 40
!
site-list sites_40_60
site-id 40
site-id 60
!
prefix-list SITE_40
ip-prefix 192.168.40.0/24
!
prefix-list SITE_60
ip-prefix 192.168.60.0/24
!
!
control-policy REDIRECT_VIA_VEDGE2
sequence 10
match route
prefix-list SITE_40
!
action accept
set
tloc-action primary
tloc 192.168.30.105 color biz-internet encap ipsec
!
!
!
sequence 20
match route
prefix-list SITE_60
!
action accept
set
tloc-action primary
tloc 192.168.30.105 color biz-internet encap ipsec
!
!
!
default-action accept
!
apply-policy
site-list sites_40_60
control-policy REDIRECT_VIA_VEDGE2 out
!
!目标是将站点40和站点60之间的流量重定向到站点50,并且首选商业互联网TLOC。
问题
从show omp routes输出中,您可以看到,通过biz-internet的路由无法安装在vEdge1和vEdge3上,并且状态设置为“无效”和“未解析”(Inv,U😞
vedge1# show omp routes | b PATH
PATH ATTRIBUTE
VPN PREFIX FROM PEER ID LABEL STATUS TYPE TLOC IP COLOR ENCAP PREFERENCE
--------------------------------------------------------------------------------------------------------------------------------------
40 192.168.40.0/24 0.0.0.0 68 1002 C,Red,R installed 192.168.30.104 biz-internet ipsec -
0.0.0.0 81 1002 C,Red,R installed 192.168.30.104 private1 ipsec -
40 192.168.50.0/24 192.168.30.103 4 1002 C,I,R installed 192.168.30.105 biz-internet ipsec -
192.168.30.103 10 1002 C,I,R installed 192.168.30.105 private1 ipsec -
40 192.168.60.0/24 192.168.30.103 8 1002 Inv,U installed 192.168.30.105 biz-internet ipsec -
192.168.30.103 9 1002 C,I,R installed 192.168.30.106 biz-internet ipsec - vedge3# show omp routes | b PATH
PATH ATTRIBUTE
VPN PREFIX FROM PEER ID LABEL STATUS TYPE TLOC IP COLOR ENCAP PREFERENCE
--------------------------------------------------------------------------------------------------------------------------------------
40 192.168.40.0/24 192.168.30.103 19 1002 Inv,U installed 192.168.30.105 biz-internet ipsec -
192.168.30.103 20 1002 C,I,R installed 192.168.30.104 biz-internet ipsec -
40 192.168.50.0/24 192.168.30.103 16 1002 C,I,R installed 192.168.30.105 biz-internet ipsec -
192.168.30.103 21 1002 C,I,R installed 192.168.30.105 private1 ipsec -
40 192.168.60.0/24 0.0.0.0 68 1002 C,Red,R installed 192.168.30.106 biz-internet ipsec -
0.0.0.0 81 1002 C,Red,R installed 192.168.30.106 private1 ipsec - 同时,您会看到商业-internet上的数据平面隧道在vEdge1和vEdge3之间启动并运行:
vedge1# show bfd sessions
SOURCE TLOC REMOTE TLOC DST PUBLIC DST PUBLIC DETECT TX
SYSTEM IP SITE ID STATE COLOR COLOR SOURCE IP IP PORT ENCAP MULTIPLIER INTERVAL(msec) UPTIME TRANSITIONS
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
192.168.30.105 50 up biz-internet biz-internet 192.168.109.181 192.168.109.182 12366 ipsec 7 1000 0:02:52:22 0
192.168.30.105 50 up private1 private1 192.168.110.181 192.168.110.182 12366 ipsec 7 1000 0:00:00:12 1
192.168.30.106 60 up biz-internet biz-internet 192.168.109.181 192.168.109.183 12366 ipsec 7 1000 0:02:52:22 0
192.168.30.106 60 up private1 private1 192.168.110.181 192.168.110.183 12366 ipsec 7 1000 0:00:56:28 0 vedge3# show bfd sessions
SOURCE TLOC REMOTE TLOC DST PUBLIC DST PUBLIC DETECT TX
SYSTEM IP SITE ID STATE COLOR COLOR SOURCE IP IP PORT ENCAP MULTIPLIER INTERVAL(msec) UPTIME TRANSITIONS
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
192.168.30.104 40 up biz-internet biz-internet 192.168.109.183 192.168.109.181 12366 ipsec 7 1000 0:02:54:25 0
192.168.30.104 40 up private1 private1 192.168.110.183 192.168.110.181 12366 ipsec 7 1000 0:00:58:30 0
192.168.30.105 50 up biz-internet biz-internet 192.168.109.183 192.168.109.182 12366 ipsec 7 1000 0:02:54:25 0
192.168.30.105 50 up private1 private1 192.168.110.183 192.168.110.182 12366 ipsec 7 1000 0:00:57:26 0 在show omp route detailed输出中,您会看到tloc设置正确,并且还设置了untimate-tloc,但状态为Inv,U,丢失原因为invalid:
vedge3# show omp routes 192.168.40.0/24 detail
---------------------------------------------------
omp route entries for vpn 40 route 192.168.40.0/24
---------------------------------------------------
RECEIVED FROM:
peer 192.168.30.103
path-id 19
label 1002
status Inv,U
loss-reason invalid
lost-to-peer 192.168.30.103
lost-to-path-id 20
Attributes:
originator 192.168.30.104
type installed
tloc 192.168.30.105, biz-internet, ipsec
ultimate-tloc 192.168.30.104, biz-internet, ipsec -- primary
domain-id not set
overlay-id 1
site-id 40
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
unknown-attr-len not set
RECEIVED FROM:
peer 192.168.30.103
path-id 20
label 1002
status C,I,R
loss-reason not set
lost-to-peer not set
lost-to-path-id not set
Attributes:
originator 192.168.30.104
type installed
tloc 192.168.30.104, biz-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 40
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
unknown-attr-len not set注意:ultimate-tloc是中间跳用来建立数据平面隧道(IPsec或通用路由封装(GRE))以到达最终目标的TLOC。
注意:仅当从中间跃点上的相同TLOC建立到源的数据平面隧道时,才支持端到端TLOC,因为中间跃点是从该TLOC建立到最终(最终)目标的隧道。如果从站点到达中间跃点的TLOC与从中间跃点到达最终(最终)目标的TLOC不同,则这会导致使用TLOC操作的策略失败。这也称为脱开衬底。
您可以看到,主要目标未实现,流量沿直接路径传输,如来自192.168.40.0/24子网的主机所示:
traceroute -n 192.168.60.20
traceroute to 192.168.60.20 (192.168.60.20), 30 hops max, 60 byte packets
1 192.168.40.104 0.288 ms 0.314 ms 0.266 ms
2 192.168.60.106 0.911 ms 1.045 ms 1.140 ms
3 192.168.60.20 1.213 ms !X 1.289 ms !X 1.224 ms !X
解决方案
如果操作是accept set tloc-action,请在中间路由器上配置服务TE。
注意:启用服务TE后,中间路由器会通告源路由器用于验证引导路径的TE相关路径信息。实际上,这允许源路由器验证策略选择的确切中间跃点TLOC是否具有通向最终目的地的操作数据平面隧道。
注意:必须避免将vSmart描述为执行数据平面路径的端到端跟踪的组件。在此工作流中,vSmart分配控制平面信息,而源路由器使用通告的TE相关路径信息来确定导向路径是否有效。此机制适用于单个中间跃点。它不提供跨多个中间路由器的链式验证。
因此,当前场景中需要在vEdge2上配置服务TE才能使集中式控制策略生效,因为您基本上是通过任意路径引导来使用流量工程(TE):
vedge2(config)# vpn 40
vedge2(config-vpn-40)# service ?
Possible completions:
FW IDP IDS TE netsvc1 netsvc2 netsvc3 netsvc4
vedge2(config-vpn-40)# service TE
vedge2(config-vpn-40)# commit
Commit complete.
启用服务TE后,中间路由器会通告所需的TE服务信息,并且策略导向的路由可以成功安装。
vsmart1# show omp services | b PATH
PATH
VPN SERVICE ORIGINATOR FROM PEER ID LABEL STATUS
---------------------------------------------------------------------------
40 VPN 192.168.30.104 192.168.30.104 68 1002 C,I,R
192.168.30.104 81 1002 C,I,R
40 VPN 192.168.30.105 192.168.30.105 68 1002 C,I,R
192.168.30.105 81 1002 C,I,R
40 VPN 192.168.30.106 192.168.30.106 68 1002 C,I,R
192.168.30.106 81 1002 C,I,R
40 TE 192.168.30.105 192.168.30.105 68 1007 C,I,R
192.168.30.105 81 1007 C,I,R 请注意,状态策略导向路由设置为C、I、R:
vedge3# show omp routes 192.168.40.0/24 detail
---------------------------------------------------
omp route entries for vpn 40 route 192.168.40.0/24
---------------------------------------------------
RECEIVED FROM:
peer 192.168.30.103
path-id 19
label 1002
status C,I,R
loss-reason not set
lost-to-peer not set
lost-to-path-id not set
Attributes:
originator 192.168.30.104
type installed
tloc 192.168.30.105, biz-internet, ipsec
ultimate-tloc 192.168.30.104, biz-internet, ipsec -- primary
domain-id not set
overlay-id 1
site-id 40
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
unknown-attr-len not set
RECEIVED FROM:
peer 192.168.30.103
path-id 20
label 1002
status R
loss-reason tloc-action
lost-to-peer 192.168.30.103
lost-to-path-id 19
Attributes:
originator 192.168.30.104
type installed
tloc 192.168.30.104, biz-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 40
preference not set
tag not set
origin-proto connected
origin-metric 0
as-path not set
unknown-attr-len not set
vedge3# show ip routes 192.168.40.0/24 | b PROTOCOL
PROTOCOL NEXTHOP NEXTHOP NEXTHOP
VPN PREFIX PROTOCOL SUB TYPE IF NAME ADDR VPN TLOC IP COLOR ENCAP STATUS
---------------------------------------------------------------------------------------------------------------------------------------------
40 192.168.40.0/24 omp - - - - 192.168.30.105 biz-internet ipsec F,S