簡介
本文說明在集中控制策略中使用set tloc-action時,重疊管理協定(OMP)路由可能保持無效的原因
拓撲
在本示例中,站點40和站點60之間的流量通過站點50導向。策略設定vEdge2上的中間TLOC,並使用tloc-action primary,以便流量優先使用通過中間站點的企業Internet路徑。

背景
集中控制策略中的tloc-action不起作用,即使資料平面隧道似乎已啟動,並描述了如何更正配置。
組態
本文中的資訊是根據特定實驗室環境內的裝置所建立。文中使用到的所有裝置皆從已清除(預設)的組態來啟動。如果您的網路運作中,請確保您瞭解任何指令可能造成的影響。為了本文的目的,使用了vEdge和控制器軟體版本18.3.5。
所有站點都連線到biz-internet和private顏色,此表彙總了配置。
| 主機名 |
site-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 - 同時,您會看到在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