簡介
本文描述如何在分段路由中配置拓撲無關的無環備用(TI-LFA)。重點將是TI-LFA配置和驗證Cisco IOS® XR。
必要條件
需求
思科建議您瞭解以下主題:
採用元件
本檔案中的資訊是根據Cisco IOS XR。
本文中的資訊是根據特定實驗室環境內的裝置所建立。文中使用到的所有裝置皆從已清除(預設)的組態來啟動。如果您的網路運作中,請確保您瞭解任何指令可能造成的影響。
背景資訊
IP-Fast重新路由
TI-LFA可以在保持IPFRR解決方案簡單性的同時,為這些限制提供解決方案。
TI-LFA
分段路由中的TI-LFA解決了快速重路由(FRR)中的難題,這些難題以前在經典LFA路徑計算中無法實現。
TI-LFA是基於分段路由的LFA FRR,它帶來了:
- 簡單
- 完全自動化
- 沒有定向LDP會話
- 無RSVP-TE通道
- 增量部署
- 收斂後路徑上的最佳備份路徑
- 防止瞬時擁塞和次優路由
未啟用FRR時,RIB中未安裝備份路由。
RP/0/0/CPU0:R1#show route 192.0.2.6
Routing entry for192.0.2.6/32
Known via "isis 111", distance 115, metric 30, labeled SR, type level-2
Routing Descriptor Blocks
198.51.100.2, from 192.0.2.6, via GigabitEthernet0/0/0/0
Route metric is 30
No advertising protos.
PQ節點
rLFA和TI-LFA在計算修復路徑時使用術語,如P空間、Q空間或PQ節點。進一步詳情可在驗證部分找到,
P空間:根據最短路徑樹(SPT)演算法,R1可以到達的一組路由器,無需在收斂前狀態穿越故障路徑。
Q空間:根據SPT演算法,R6可以到達的路由器集,無需在收斂前狀態穿越故障路徑。
PQ空間:R1的P空間和R6的Q空間的交集。
設定
一個簡單的CLI,用於在中間系統到中間系統(ISIS)、開放最短路徑優先(OSPF)介面配置模式下啟用TI-LFA,如下所示。
ISIS
router isis 111
interface GigabitEthernet0/0/0/0
address-family ipv4 unicast
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa
OSPF
router ospf 111
area 0
interface GigabitEthernet0/0/0/0
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa enable
驗證
使用本節內容,確認您的組態是否正常運作。
修復節點是直接鄰居(LFA)
R1(192.0.2.1)通常計算其通向R6(192.0.2.6)的最低開銷路徑,並安裝在RIB中。流量將通過R1 — R2 — R3 — R6(主路徑)從R1轉發到R6。
如果沒有LFA,如果R1 —x— R2之間出現鏈路故障,R1 > R6之間的流量將丟棄幾毫秒,直到R1重新計算並找到通過R4的另一條路由。
啟用LFA後,R1預安裝通過R4到R6的路由作為備份。
在LFA的情況下,此標準應滿足備用路由安裝,
- R4到R6的最低開銷路徑不應通過R1
- 從R4到R6的總開銷應該低於當前的主路徑,即從R1 > R6的開銷,如圖所示。
RP/0/0/CPU0:R1#show route 192.0.2.6/32
Routing entry for192.0.2.6/32
Known via "isis 111", distance 115, metric 30, labeled SR, type level-2
Routing Descriptor Blocks
198.51.100.2, from 192.0.2.6, via GigabitEthernet0/0/0/0, Protected !Primary Path
Route metric is 30
198.51.100.21, from 192.0.2.6, via GigabitEthernet0/0/0/1, Backup (Local-LFA) !Backup Path
Route metric is 32
No advertising protos.
RP/0/0/CPU0:R1#show isis fast-reroute 192.0.2.6/32 detail
L2 192.0.2.6/32 [30/115] medium priority
via 198.51.100.2, GigabitEthernet0/0/0/0, R2, SRGB Base: 48000, Weight: 0
FRR backup via 198.51.100.21, GigabitEthernet0/0/0/1, R4, SRGB Base: 48000, Weight: 0, Metric: 32
P: No, TM: 32, LC: No, NP: Yes, Yes, SRLG: Yes
src R6.00-00, 192.0.2.6, prefix-SID index 6, R:0 N:1 P:0 E:0 V:0 L:0
RP/0/0/CPU0:R1#show cef 192.0.2.6/32 detail
192.0.2.6/32, version 1056, labeled SR, internal 0x1000001 0x81 (ptr 0xa12dbd34) [1], 0x0 (0xa12c12fc), 0xa28 (0xa170e1dc)
local adjacency 198.51.100.2
Prefix Len 32, traffic index 0, precedence n/a, priority 1
via 198.51.100.2/32, GigabitEthernet0/0/0/0, 11 dependencies, weight 0, class 0, protected [flags 0x400]
path-idx 0 bkup-idx 1 NHID 0x0 [0xa175c4b8 0x0]
next hop 198.51.100.2/32
local label 48006 labels imposed {48006}
via 198.51.100.21/32, GigabitEthernet0/0/0/1, 11 dependencies, weight 0, class 0, backup (Local-LFA) [flags 0x300]
path-idx 1 NHID 0x0 [0xa166e338 0x0]
next hop 198.51.100.21/32
local adjacency
local label 48006 labels imposed {48006}
Load distribution: 0 (refcount 2)
Hash OK Interface Address
0 Y GigabitEthernet0/0/0/0 198.51.100.2
修復節點是PQ節點(rLFA)
在大多數情況下,LFA修復路徑不可用(因為它們無法滿足上述標準)。
rLFA通過選擇一個節點作為修復節點來解決LFA的侷限性,即使這些節點不是與R1的直接鄰居。 rLFA在您標識PQ節點時起作用。
R1的P空間包括R1在預融合狀態下不遍歷R1 > R2即可到達的所有節點(當安裝了所有字首並且沒有進一步的更新時達到此狀態)。
R6的Q空間包括R6可以到達的所有節點,而無需在預收斂狀態下遍歷R1> R2。
由於R5是唯一屬於P和Q空間的節點,因此R5被選為PQ節點,並將充當鏈路R1 > R2的修復節點,如下圖所示。
附註:度量已從12更改為30(R4 — R5),以演示rLFA行為。
RP/0/0/CPU0:R1#show route 192.0.2.6/32
Routing entry for 192.0.2.6/32
Known via "isis 111", distance 115, metric 30, labeled SR, type level-2
Routing Descriptor Blocks
198.51.100.2, from 192.0.2.6, via GigabitEthernet0/0/0/0, Protected !Primary path
Route metric is 30
198.51.100.21, from 192.0.2.6, via GigabitEthernet0/0/0/1, Backup (TI-LFA) !Backup path
Repair Node(s): 192.0.2.5
Route metric is 50
No advertising protos.
RP/0/0/CPU0:R1#show isis fast-reroute 192.0.2.6/32 detail
L2 192.0.2.6/32 [30/115] medium priority
via 198.51.100.2, GigabitEthernet0/0/0/0, R2, SRGB Base: 48000, Weight: 0
Backup path: TI-LFA (link), via 198.51.100.21, GigabitEthernet0/0/0/1 R4, SRGB Base: 48000, Weight: 0
P node: R5.00 [192.0.2.5], Label: 48005
Prefix label: 48006
Backup-src: R6.00
P: No, TM: 50, LC: No, NP: No, No, SRLG: Yes
src R6.00-00, 192.0.2.6, prefix-SID index 6, R:0 N:1 P:0 E:0 V:0 L:0
RP/0/0/CPU0:R1#show cef 192.0.2.6/32 detail
192.0.2.6/32, version 1166, labeled SR, internal 0x1000001 0x81 (ptr 0xa12dc41c) [1], 0x0 (0xa12c19e0), 0xa28 (0xa170e1b0)
local adjacency 198.51.100.2
via 198.51.100.2/32, GigabitEthernet0/0/0/0, 10 dependencies, weight 0, class 0, protected [flags 0x400]
path-idx 0 bkup-idx 1 NHID 0x0 [0xa175c4b8 0x0]
next hop 198.51.100.2/32
local label 48006 labels imposed {48006}
via 198.51.100.21/32, GigabitEthernet0/0/0/1, 10 dependencies, weight 0, class 0, backup (TI-LFA) [flags 0xb00]
path-idx 1 NHID 0x0 [0xa166e338 0x0]
next hop 198.51.100.21/32, Repair Node(s): 192.0.2.5
local adjacency
local label 48006 labels imposed {48005 48006}
Load distribution: 0 (refcount 3)
Hash OK Interface Address
0 Y GigabitEthernet0/0/0/0 198.51.100.2
修復是Q節點,最後一個P節點的鄰居(TI-LFA)
如果R4 > R5之間的度量升至50,則rLFA將無法提供保護。R1的鏈路R1 > R2的P空間僅包括R3。R6的鏈路R1> R2的Q空間包括R3、R4和R5。沒有可用的修復節點。
因此,即使rLFA也不能保證所有網路拓撲中都存在備用路徑。 TI-LFA解決了rLFA的侷限性,並在如圖所示的場景中為鏈路R1 > R2提供備用路徑。
附註:度量已從30更改為50(R4 — R5),以演示分段路由TI-LFA行為(在rLFA中無法實現)。
RP/0/0/CPU0:R1#show route 192.0.2.6/32
Routing entry for 192.0.2.6/32
Known via "isis 111", distance 115, metric 30, labeled SR, type level-2
Routing Descriptor Blocks
198.51.100.2, from 192.0.2.6, via GigabitEthernet0/0/0/0, Protected !Primary Path
Route metric is 30
198.51.100.21, from 192.0.2.6, via GigabitEthernet0/0/0/1, Backup (TI-LFA) !Backup Path
Repair Node(s): 192.0.2.4, 192.0.2.5
Route metric is 70
No advertising protos.
RP/0/0/CPU0:R1#show isis fast-reroute 192.0.2.6/32 detail
L2 192.0.2.6/32 [30/115] medium priority
via 198.51.100.2, GigabitEthernet0/0/0/0, R2, SRGB Base: 48000, Weight: 0
Backup path: TI-LFA (link), via 198.51.100.21, GigabitEthernet0/0/0/1 R4, SRGB Base: 48000, Weight: 0
P node: R4.00 [192.0.2.4], Label: ImpNull
Q node: R5.00 [192.0.2.5], Label: 24003
Prefix label: 48006
Backup-src: R6.00
P: No, TM: 70, LC: No, NP: No, No, SRLG: Yes
src R6.00-00, 192.0.2.6, prefix-SID index 6, R:0 N:1 P:0 E:0 V:0 L:0
RP/0/0/CPU0:R1#show cef 192.0.2.6/32 detail
192.0.2.6/32, version 1192, labeled SR, internal 0x1000001 0x81 (ptr 0xa12dc41c) [1], 0x0 (0xa12c165c), 0xa28 (0xa170e310)
local adjacency 198.51.100.2
via 198.51.100.2/32, GigabitEthernet0/0/0/0, 12 dependencies, weight 0, class 0, protected [flags 0x400]
path-idx 0 bkup-idx 1 NHID 0x0 [0xa175c170 0xa175c4b8]
next hop 198.51.100.2/32
local label 48006 labels imposed {48006}
via 198.51.100.21/32, GigabitEthernet0/0/0/1, 12 dependencies, weight 0, class 0, backup (TI-LFA) [flags 0xb00]
path-idx 1 NHID 0x0 [0xa166e16c 0xa166e338]
next hop 198.51.100.21/32, Repair Node(s): 192.0.2.4, 192.0.2.5
local adjacency
local label 48006 labels imposed {ImplNull 24003 48006}
Load distribution: 0 (refcount 7)
Hash OK Interface Address
0 Y GigabitEthernet0/0/0/0 198.51.100.2
RP/0/0/CPU0:R1#
疑難排解
本節提供的資訊可用於對組態進行疑難排解。
請參閱;分段路由故障排除 — Cisco Systems
相關資訊