SR-MPLS Multi AS MP-BGP Practice

Practice repository - Upload the config to work.\ This is Backbone network with SR-MPLS which has multi AS for MP-BGP, and CE routers will be pingable from each edge.

SR-MPLS をベースにしたバックボーン環境を構築する。MP-BGPはマルチASとし、異なるASを接続した通信を実装する。

前提条件

Cisco 製品では、現時点でSRに対応しているのはCisco IOS XRのみ。\ VMの上の仮想環境で構築する。

PE routers & P routers: Cisco XRv
CE routers: Cisco CSR 1000v

Network diagram

Layer 3 IP assignment

Inner-AS: 192.168.xx.xx/24
- Octet 3: Link ID
Inter-AS: 172.24.xx.xx/24
- Octet 3: Link ID
Mgmt IP: 100.64.x.x/32
- Octet 3:
- UG-A: 10
- UG-B: 20
UG AS: 650xx

L3NWD

Layer 2.8 Segment Routing ID assignment

SRGB Range: 16000 - 23999
- Segment ID: 1600x

Layer 2 VLAN assignment

クラウド上に構築するため、リソース節約のため、単一物理ネットワーク上に構築する。\ ルータ間接続はVLANで接続し、他の通信が干渉しないようにする。

L2NWD

Layer 1 Physical port assignment

リソース節約のため、単一物理ネットワーク上に構築する。\ L1レベルではすべて同じスイッチに所属しているように見える。

L1NWD

設計詳細

参考URL: IOS および IOS XR を使用したレイヤ 3 MPLS VPN INTER-AS オプション B の設定と検証
参考URL: MPLS網にSegment Routingを適用してみよう
参考URL: Segment Routing Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR
参考URL: SR IGP Flex Algo - Segment Routing
参考URL: Segment Routingでよく聞かれること

Segment Routing のとは？

Segment Routing のメリット

Benefits

Ready for SDN: Segment routing was built for SDN and is the foundation for Application Engineered Routing (AER). SR prepares networks for business models, where applications can direct network behavior. SR provides the right balance between distributed intelligence and centralized optimization and programming.
Minimal configuration: Segment routing for TE requires minimal configuration on the source router.
Load balancing: Unlike in RSVP-TE, load balancing for segment routing can take place in the presence of equal cost multiple paths (ECMPs).
Supports Fast Reroute (FRR): Fast reroute enables the activation of a pre-configured backup path within 50 milliseconds of path failure.
Plug-and-Play deployment: Segment routing tunnels are interoperable with existing MPLS control and data planes and can be implemented in an existing deployment.

SR-MPLS の基本設定とIGP

参考URL: MPLS網にSegment Routingを適用してみよう
参考URL: Segment Routing Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR

IGPの選択

IS-ISとOSPFが対応。本環境ではFlex-Algo利用を視野に入れていることもあり、Segment Routingが早期から導入されてきたIS-ISを利用する。\ IS-ISのため、NSAPアドレスの設定が必要なので、忘れずに設定する。\ 本環境ではNSAPアドレスはLoopbackアドレス、アドレスファミリーはIPv4を用いる。

router isis core
 net 49.0001.1000.6400.0001.00
 address-family ipv4 unicast
  segment-routing mpls

SRGBの設定

マルチベンダー環境の場合、Segment Routing Global Block (SRGB) の規定値が異なる場合があるので、念のためで設定を投入することが推奨。\ SRGBはルータ内でPrefix-sid / Node-sid 等のGlobal SID付与に使用されるラベル番号の範囲のこと。\ Ciscoのデフォルトは16000 - 23999

router isis core
 segment-routing global-block 16000 23999

Node SID設定

SRGBの範囲内で機器にNode Segment IDを付与。Node-sidはルータ自身を示すSIDであり同一SR Domain内でユニーク（一意）である必要あり。\ 通常、Loopback インターフェースにてIS-ISを動作させ、Node SIDを割り当てている。\ 指定方法にはindex指定と絶対値(absolute)指定の2種類存在。index指定が一般的。\ indexはSRGBの開始値に加算した値がNode-SIDとなる。

router isis core
 interface Loopback1
  passive
  address-family ipv4 unicast
   prefix-sid index 1001

(参考) SRGBの開始値が16000の時、下記2つの設定は同一。

   prefix-sid index 1001
   prefix-sid absolute 17001

Adjacency-SID設定

Adj-sidはユーザが設定する必要は無く自動的に付与されるが、自身で設定する場合には下記\ Cisco デフォルトの SRLB は 15000 - 15999 のため、index指定の場合はSRGB同様、SRLB開始値に加算される。

router isis core
 segment-routing global-block 16000 23999
 !
 interface GigabitEthernet0/0/0/0.12
  point-to-point
  address-family ipv4 unicast
   adjacency-sid index 12
  !
 !
 interface GigabitEthernet0/0/0/0.13
  point-to-point
  address-family ipv4 unicast
   adjacency-sid index 13
  !
segment-routing
 global-block 16000 23999
 adjacency-sid
  interface GigabitEthernet0/0/0/0.12
   address-family ipv4 unicast
    l2-adjacency-sid absolute 15012 next-hop 192.168.12.2
   !
  !
  interface GigabitEthernet0/0/0/0.13
   address-family ipv4 unicast
    l2-adjacency-sid absolute 15013 next-hop 192.168.13.3

TI-LFA設定

SR環境でFRR（Fast ReRoute : 高速迂回）を実現するための機能であるTI-LFA（Topology Independent Loop Free Alternate）の設定を実施。\ TI-LFAを使用するとルータは最適pathとは異なる迂回用のpathをprefix毎に計算し、それを保持。\ 最適pathの障害時には保持している迂回用pathに通信を切り替えることで高速迂回を実現。

router isis core
 interface GigabitEthernet0/0/0/0.12
  address-family ipv4 unicast
   fast-reroute per-prefix
   fast-reroute per-prefix ti-lfa
  !
 !
 interface GigabitEthernet0/0/0/0.13
  address-family ipv4 unicast
   fast-reroute per-prefix
   fast-reroute per-prefix ti-lfa

Overlay MP-BGP - iBGP 設定

基本的にはMPLSと特に設定差分は存在しない。\ VRF上のユーザプレフィックスを伝搬するのはVPNv4アドレスファミリーなので、必ず設定する。\ また、Route-Reflectorとして動作させる機器にはroute-reflector-clientも設定する。

router bgp 65090
 bgp router-id 100.64.0.1
 address-family ipv4 unicast
 address-family vpnv4 unicast
 !
neighbor 100.64.0.2
  remote-as 65090
  update-source Loopback1
  address-family ipv4 unicast
   next-hop-self
   soft-reconfiguration inbound always
  address-family ipv4 labeled-unicast
  address-family vpnv4 unicast
   next-hop-self
   soft-reconfiguration inbound always

Overlay MP-BGP - eBGP + VRF 設定

基本的にはMPLSと特に設定差分は存在しない。\ XRvの制約として、eBGPにroute-policy適用が必須となっているので注意。

vrf UG-A
 rd 100.64.10.1:10
 address-family ipv4 unicast
  import route-target
   89:10
  !
  export route-target
   89:10
router bgp 65090
 vrf UG-A
  address-family ipv4 unicast
   redistribute connected
  !
  neighbor 172.24.18.8
   remote-as 65018
   address-family ipv4 unicast
    route-policy PERMIT-ALL-IN in
    route-policy PERMIT-ALL-OUT out
    soft-reconfiguration inbound always

Segment Routing 環境での Inter AS MP-BGP

基本的にはMPLSと特に設定差分は存在しない。\ XRvの制約として、eBGPピア向けのStaticが必須となっているので注意。（バグか？）

router static
 address-family ipv4 unicast
  172.24.34.4/32 GigabitEthernet0/0/0/0.34
 !
router bgp 65090
 neighbor 172.24.34.4
 remote-as 65091
 address-family vpnv4 unicast
 route-policy DEFAULT in
 route-policy DEFAULT out

SR-MPLSの状態確認

ルーティングテーブル

TI-LFAが有効化されているため、IGP部分については2行表示されている。

i L1 100.64.0.2/32 [115/10] via 192.168.12.2, 05:42:41, GigabitEthernet0/0/0/0.12
                   [115/20] via 192.168.13.3, 05:42:41, GigabitEthernet0/0/0/0.13 (!)
i L1 100.64.0.3/32 [115/20] via 192.168.12.2, 05:42:41, GigabitEthernet0/0/0/0.12 (!)
                   [115/10] via 192.168.13.3, 05:42:41, GigabitEthernet0/0/0/0.13

LFIBテーブル

SR Pfx (idx 1002)の部分が他のNode SID。\ 一部、Flex-Algoの設定箇所についてNode-SIDやSR-TEのラベルが増えている。

RP/0/RP0/CPU0:cisco-kudo-11#show mpls forwarding

Wed Dec 30 08:19:22.230 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes       
Label  Label       or ID              Interface                    Switched    
------ ----------- ------------------ ------------ --------------- ------------
15012  Pop         SRLB (idx 12)      Gi0/0/0/0.12 192.168.12.2    0           
15013  Pop         SRLB (idx 13)      Gi0/0/0/0.13 192.168.13.3    0           
16281  16281       SR Pfx (idx 281)   Gi0/0/0/0.13 192.168.13.3    0           
16282  16282       SR Pfx (idx 282)   Gi0/0/0/0.13 192.168.13.3    0           
16283  Pop         SR Pfx (idx 283)   Gi0/0/0/0.13 192.168.13.3    0           
16291  16291       SR Pfx (idx 291)   Gi0/0/0/0.13 192.168.13.3    0           
       16291       SR Pfx (idx 291)   Gi0/0/0/0.12 192.168.12.2    0           
16292  Pop         SR Pfx (idx 292)   Gi0/0/0/0.12 192.168.12.2    0           
       16292       SR Pfx (idx 292)   Gi0/0/0/0.13 192.168.13.3    0            (!)
16293  Pop         SR Pfx (idx 293)   Gi0/0/0/0.13 192.168.13.3    0           
       16293       SR Pfx (idx 293)   Gi0/0/0/0.12 192.168.12.2    0            (!)
16301  16301       SR Pfx (idx 301)   Gi0/0/0/0.13 192.168.13.3    0           
       16301       SR Pfx (idx 301)   Gi0/0/0/0.12 192.168.12.2    0           
16302  Pop         SR Pfx (idx 302)   Gi0/0/0/0.12 192.168.12.2    0           
16303  Pop         SR Pfx (idx 303)   Gi0/0/0/0.13 192.168.13.3    0           
17002  Pop         SR Pfx (idx 1002)  Gi0/0/0/0.12 192.168.12.2    11614       
       17002       SR Pfx (idx 1002)  Gi0/0/0/0.13 192.168.13.3    0            (!)
17003  Pop         SR Pfx (idx 1003)  Gi0/0/0/0.13 192.168.13.3    15455       
       17003       SR Pfx (idx 1003)  Gi0/0/0/0.12 192.168.12.2    0            (!)
24000  Pop         SR Adj (idx 0)     Gi0/0/0/0.13 192.168.13.3    0           
       17003       SR Adj (idx 0)     Gi0/0/0/0.12 192.168.12.2    0            (!)
24001  Pop         SR Adj (idx 2)     Gi0/0/0/0.13 192.168.13.3    0           
24002  Pop         SR Adj (idx 1)     Gi0/0/0/0.13 192.168.13.3    0           
       17003       SR Adj (idx 1)     Gi0/0/0/0.12 192.168.12.2    0            (!)
24003  Pop         SR Adj (idx 3)     Gi0/0/0/0.13 192.168.13.3    0           
24004  Pop         SR Adj (idx 0)     Gi0/0/0/0.12 192.168.12.2    0           
       17002       SR Adj (idx 0)     Gi0/0/0/0.13 192.168.13.3    0            (!)
24005  Pop         SR Adj (idx 2)     Gi0/0/0/0.12 192.168.12.2    0           
24006  Pop         SR Adj (idx 1)     Gi0/0/0/0.12 192.168.12.2    0           
       17002       SR Adj (idx 1)     Gi0/0/0/0.13 192.168.13.3    0            (!)
24007  Pop         SR Adj (idx 3)     Gi0/0/0/0.12 192.168.12.2    0           
24008  Pop         192.168.23.0/24    Gi0/0/0/0.12 192.168.12.2    0           
       Pop         192.168.23.0/24    Gi0/0/0/0.13 192.168.13.3    0           
24009  Pop         100.64.0.3/32      Gi0/0/0/0.13 192.168.13.3    158723      
       24009       100.64.0.3/32      Gi0/0/0/0.12 192.168.12.2    0            (!)
24010  Pop         100.64.0.2/32      Gi0/0/0/0.12 192.168.12.2    151294      
       24009       100.64.0.2/32      Gi0/0/0/0.13 192.168.13.3    0            (!)
24011  Aggregate   UG-A: Per-VRF Aggr[V]   \
                                      UG-A                         1020        
24012  24012       100.64.10.3/32[V]               100.64.0.3      0           
24020  Aggregate   UG-B: Per-VRF Aggr[V]   \
                                      UG-B                         0           
24021  24012       100.64.10.2/32[V]               100.64.0.2      0           
24022  24012       172.24.28.0/24[V]               100.64.0.2      0           
24025  Pop         No ID              srte_c_128_e point2point     0           
24026  Pop         No ID              srte_c_130_e point2point     0           
24027  Pop         SR TE: 1 [TE-INT]  Gi0/0/0/0.13 192.168.13.3    0           
24028  Pop         SR TE: 2 [TE-INT]  Gi0/0/0/0.13 192.168.13.3    0           
24029  Unlabelled  100.64.10.18/32[V] Gi0/0/0/0.18 172.24.18.8     0           
24030  Unlabelled  100.64.20.38/32[V] Gi0/0/0/0.38 172.24.38.8     0           
24031  24030       100.64.10.28/32[V]              100.64.0.2      0

SRv6 の基本設定

参考URL: Segment Routing Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.6.x

Locatorの設定

SRv6のノードを指し示す、Locator と Node SID を設定\ ついでに、カプセル化する送信元アドレスも設定（任意）\ 合わせて、Locatorのステータス変更のログを取得（任意）

segment-routing
 srv6
  logging locator status
  encapsulation
   source-address fd00:5:5::5
  !
  locators
   locator No5
    prefix fd00:5:5::/64

IGPの設定

IS-ISとOSPFv3の両方が利用可能。\ 今回はSR-MPLSと同様にIS-ISを利用する。\ IPv6環境の上に構築するため、アドレスファミリーはIPv6のみで十分。

router isis core
 net 49.0001.1000.6400.0005.00
 distribute link-state
 address-family ipv6 unicast
  segment-routing srv6
   locator No5
 interface Loopback5
  passive
  address-family ipv6 unicast
 interface GigabitEthernet0/0/0/0.45
  address-family ipv6 unicast
 interface GigabitEthernet0/0/0/0.56
  address-family ipv6 unicast

Overlay MP-BGP - iBGP 設定

本検証当時(Dec. 2020)、End.DT6等のIPv6をVPN上でやりとりする機能がCisco機器に実装されておらず、End.DT4 or DX4のみであったため、\ アドレスファミリーはIPv4とVPNv4のみとし、IPv6関連は設定しない。\ IPv6関連が実装されるのはしばらく先になる見込み。

router bgp 65091
 timers bgp 15 45
 bgp router-id 100.64.0.5
 address-family ipv4 unicast
  segment-routing srv6
   locator No5
 address-family vpnv4 unicast
  segment-routing srv6
   locator No5
 address-family link-state link-state
 !
 neighbor fd00:4:4::4
  remote-as 65091
  description ***XRv-01***
  update-source Loopback4
  address-family ipv4 unicast
   next-hop-self
   soft-reconfiguration inbound always
  address-family vpnv4 unicast
   next-hop-self
   soft-reconfiguration inbound always

Overlay MP-BGP - eBGP + VRF 設定

VRFごとにFunctionの指定が可能。ただ、VRFテーブル⇔グローバルテーブルの変換を行う場合は基本的にEnd.DT4を利用。

Per-VRF mode: End.DT4. End.DT4 represents the Endpoint with decapsulation and IPv4 table lookup.
Per-CE mode: End.DX4. End.DX4 represents the Endpoint with decapsulation and IPv4 cross-connect.

router bgp 65091
 vrf UG-A
  address-family ipv4 unicast
   segment-routing srv6
    alloc mode per-vrf
   redistribute connected
  neighbor 172.24.19.9
   remote-as 65019
   address-family ipv4 unicast
    route-policy PERMIT-ALL-IN in
    route-policy PERMIT-ALL-OUT out
    soft-reconfiguration inbound always

SRv6の状態確認

ルーティングテーブル

UG-A: 
B    100.64.10.19/32 [20/0] via 172.24.19.9, 00:36:42
B    100.64.10.29/32 [200/0] via fd00:6:6::6 (nexthop in vrf default), 00:36:42

SRv6 情報

RP/0/RP0/CPU0:cisco-kudo-02#show segment-routing srv6 manager
Thu Jan  7 10:13:06.339 UTC
Parameters:
  SRv6 Enabled: Yes
  Encapsulation:
    Source Address:
      Configured: fd00:5:5::5
      Default: fd00:5:5::5
    Hop-Limit: Default
Summary:
  Number of Locators: 1 (1 operational)
  Number of SIDs: 8 (0 stale)
  Max SIDs: 8000
  OOR:
    Thresholds: Green 400, Warning 240
    Status: Resource Available (0 cleared, 0 warnings, 0 full)
Platform Capabilities:
  SRv6: Yes
  TILFA: Yes
  Microloop-Avoidance: Yes
  End Functions:
    End (PSP)
    End.X (PSP)
    End.DX4
    End.DT4
    End.OP
  Transit Functions:
    T
    T.Insert.Red
    T.Encaps.Red
  Security rules:
    SEC-1
    SEC-2
    SEC-3
    SEC-4
  Counters:
    CNT-1
    CNT-3
  Signaled Parameters:
    Max-SL          : 4
    Max-End-Pop-SRH : 4
    Max-T-Insert    : 4
    Max-T-Encap     : 5
    Max-End-D       : 5
  Max SIDs: 8000
  SID Holdtime: 30 mins
RP/0/RP0/CPU0:cisco-kudo-02#
RP/0/RP0/CPU0:cisco-kudo-02#show segment-routing srv6 locator No5 detail
Thu Jan  7 10:13:42.187 UTC
Name                  ID       Prefix                    Status
--------------------  -------  ------------------------  -------
No5*                  1        fd00:5:5::/64             Up
  Interface:
    Name: srv6-No5
    IFH : 0x00000014
    IPv6 address: fd00:5:5::/64
  Chkpt Obj ID: 0x2f60
  Created: Jan  7 05:02:14.468 (05:11:27 ago)
RP/0/RP0/CPU0:cisco-kudo-02#
RP/0/RP0/CPU0:cisco-kudo-02#show segment-routing srv6 locator No5 sid
Thu Jan  7 10:14:01.102 UTC
SID                         Behavior     Context                           Owner               State  RW
--------------------------  -----------  ------------------------------    ------------------  -----  --
fd00:5:5:0:1::              End (PSP)    'default':1                       sidmgr              InUse  Y
fd00:5:5:0:11::             End.OP       'default'                         sidmgr              InUse  Y
fd00:5:5:0:40::             End.X (PSP)  [Gi0/0/0/0.56, Link-Local]        isis-core           InUse  Y
fd00:5:5:0:41::             End.X (PSP)  [Gi0/0/0/0.45, Link-Local]        isis-core           InUse  Y
fd00:5:5:0:42::             End.DT4      'UG-A'                            bgp-65091           InUse  Y
fd00:5:5:0:43::             End.DT4      'UG-B'                            bgp-65091           InUse  Y
fd00:5:5:0:44::             End.DT4      'UG-C'                            bgp-65091           InUse  Y
fd00:5:5:0:45::             End.DX4      'UG-B':1                          bgp-65091           InUse  Y
RP/0/RP0/CPU0:cisco-kudo-02#

SRv6 ルート情報

End.DT4 Egress ルート

SRv6-VPNに入ってきて、HeadendとなるPEが処理し、他ノードへSRv6で配信するノードでの情報

SRv6-VPN SID: fd00:5:5:0:42::/128

RP/0/RP0/CPU0:cisco-kudo-02#show bgp vpnv4 uni rd 100.64.10.5:10 100.64.10.19/32
Thu Jan  7 10:26:19.202 UTC
BGP routing table entry for 100.64.10.19/32, Route Distinguisher: 100.64.10.5:10
Versions:
  Process           bRIB/RIB  SendTblVer
  Speaker                232         232
    SRv6-VPN SID: fd00:5:5:0:42::/128
Last Modified: Jan  7 05:20:28.381 for 05:05:51
Paths: (2 available, best #1)
  Advertised to update-groups (with more than one peer):
    0.2
  Path #1: Received by speaker 0
  Advertised to update-groups (with more than one peer):
    0.2
  65019
    172.24.19.9 from 172.24.19.9 (100.64.10.19)
      Origin incomplete, metric 0, localpref 100, valid, external, best, group-best, import-candidate
      Received Path ID 0, Local Path ID 1, version 232
      Extended community: RT:89:10
  Path #2: Received by speaker 0
  Not advertised to any peer
  65019, (received-only)
    172.24.19.9 from 172.24.19.9 (100.64.10.19)
      Origin incomplete, metric 0, localpref 100, valid, external
      Received Path ID 0, Local Path ID 0, version 0

End.DT4 Ingress ルート

SRv6-VPN経由で受信したルート\ 送信元のSID情報も合わせて受信している\ SRv6-VPN-SID: T1-fd00:6:6:0:42:: [total 1]\ また、Segment-list情報も受信している SRv6 SID-list { fd00:6:6:0:42:: }\ CEFテーブルから、下記もわかる。

Locator: fd00:6:6::/128
Segment List: {fd00:6:6:0:42::}
Next-hop IP: fe80::56:6

RP/0/RP0/CPU0:cisco-kudo-02#show bgp vpnv4 uni rd 100.64.10.5:10 100.64.10.29/32
Thu Jan  7 10:26:30.216 UTC
BGP routing table entry for 100.64.10.29/32, Route Distinguisher: 100.64.10.5:10
Versions:
  Process           bRIB/RIB  SendTblVer
  Speaker                235         235
    SRv6-VPN SID: fd00:5:5:0:42::/128
Last Modified: Jan  7 05:20:28.381 for 05:06:02
Paths: (1 available, best #1)
  Not advertised to any peer
  Path #1: Received by speaker 0
  Not advertised to any peer
  65029, (received & used)
    fd00:6:6::6 (metric 10) from fd00:6:6::6 (100.64.0.6)
      Received Label 3
      Origin incomplete, metric 0, localpref 100, valid, internal, best, group-best, import-candidate, imported
      Received Path ID 0, Local Path ID 1, version 235
      Extended community: RT:89:10
      SRv6-VPN-SID: T1-fd00:6:6:0:42:: [total 1]
      Source AFI: VPNv4 Unicast, Source VRF: default, Source Route Distinguisher: 100.64.10.6:10

RP/0/RP0/CPU0:cisco-kudo-02#show route vrf UG-A 100.64.10.29/32 detail
Thu Jan  7 10:37:03.674 UTC

Routing entry for 100.64.10.29/32
  Known via "bgp 65091", distance 200, metric 0
  Tag 65029, type internal
  Installed Jan  7 05:20:28.259 for 05:16:35
  Routing Descriptor Blocks
    fd00:6:6::6, from fd00:6:6::6
      Nexthop in Vrf: "default", Table: "default", IPv6 Unicast, Table Id: 0xe0800000
      Route metric is 0
      Label: None
      Tunnel ID: None
      Binding Label: None
      Extended communities count: 0
      Source RD attributes: 0x0001:25664:168165386
      NHID:0x0(Ref:0)
      SRv6 Transit Type: T.Encaps.Red
      SRv6 SID-list { fd00:6:6:0:42:: }
  Route version is 0x1 (1)
  No local label
  IP Precedence: Not Set
  QoS Group ID: Not Set
  Flow-tag: Not Set
  Fwd-class: Not Set
  Route Priority: RIB_PRIORITY_RECURSIVE (12) SVD Type RIB_SVD_TYPE_REMOTE
  Download Priority 3, Download Version 10
  No advertising protos.

RP/0/RP0/CPU0:cisco-kudo-02#show cef vrf UG-A 100.64.10.29/32 detail location 0/0/CPU0
Thu Jan  7 10:40:47.265 UTC
100.64.10.29/32, version 10, SRv6 Transit, internal 0x5000001 0x0 (ptr 0x197b5764) [1], 0x0 (0x0), 0x0 (0x1cd92418)
 Updated Jan  7 05:20:28.424
 Prefix Len 32, traffic index 0, precedence n/a, priority 3
  gateway array (0x1e4af360) reference count 3, flags 0x2010, source rib (7), 0 backups
                [1 type 3 flags 0x48441 (0x18d39658) ext 0x0 (0x0)]
  LW-LDI[type=0, refc=0, ptr=0x0, sh-ldi=0x0]
  gateway array update type-time 1 Jan  7 05:05:10.743
 LDI Update time Jan  7 05:05:10.743

  Level 1 - Load distribution: 0
  [0] via fd00:6:6::/128, recursive

   via fd00:6:6::/128, 9 dependencies, recursive [flags 0x6000]
    path-idx 0 NHID 0x0 [0x19b48364 0x0]
    next hop VRF - 'default', table - 0xe0800000
    next hop fd00:6:6::/128 via fd00:6:6::/64
    SRv6 T.Encaps.Red SID-list {fd00:6:6:0:42::}

    Load distribution: 0 (refcount 1)

    Hash  OK  Interface                 Address
    0     Y   GigabitEthernet0/0/0/0.56 fe80::56:6

End.DX4 Egress ルート

RP/0/RP0/CPU0:cisco-kudo-02#show bgp vpnv4 uni rd 100.64.20.5:20 100.64.20.39/32
Thu Jan  7 10:47:24.566 UTC
BGP routing table entry for 100.64.20.39/32, Route Distinguisher: 100.64.20.5:20
Versions:
  Process           bRIB/RIB  SendTblVer
  Speaker                231         231
    SRv6-VPN SID: fd00:5:5:0:45::/128
    Gateway Array ID: 1, Resilient per-CE nexthop set ID: 1
Last Modified: Jan  7 05:20:28.381 for 05:26:56
Paths: (2 available, best #1)
  Advertised to update-groups (with more than one peer):
    0.2
  Path #1: Received by speaker 0
  Advertised to update-groups (with more than one peer):
    0.2
  65039
    172.24.39.9 from 172.24.39.9 (100.64.20.39)
      Origin incomplete, metric 0, localpref 100, valid, external, best, group-best, import-candidate
      Received Path ID 0, Local Path ID 1, version 231
      Extended community: RT:89:20
  Path #2: Received by speaker 0
  Not advertised to any peer
  65039, (received-only)
    172.24.39.9 from 172.24.39.9 (100.64.20.39)
      Origin incomplete, metric 0, localpref 100, valid, external
      Received Path ID 0, Local Path ID 0, version 0

End.DX4 Ingress ルート

RP/0/RP0/CPU0:cisco-kudo-02#show bgp vpnv4 uni rd 100.64.20.5:20 100.64.20.49/32
Thu Jan  7 10:48:07.907 UTC
BGP routing table entry for 100.64.20.49/32, Route Distinguisher: 100.64.20.5:20
Versions:
  Process           bRIB/RIB  SendTblVer
  Speaker                236         236
Last Modified: Jan  7 05:20:28.381 for 05:27:39
Paths: (1 available, best #1)
  Not advertised to any peer
  Path #1: Received by speaker 0
  Not advertised to any peer
  65049, (received & used)
    fd00:6:6::6 (metric 10) from fd00:6:6::6 (100.64.0.6)
      Received Label 3
      Origin incomplete, metric 0, localpref 100, valid, internal, best, group-best, import-candidate, imported
      Received Path ID 0, Local Path ID 1, version 236
      Extended community: RT:89:20
      SRv6-VPN-SID: T1-fd00:6:6:0:45:: [total 1]
      Source AFI: VPNv4 Unicast, Source VRF: default, Source Route Distinguisher: 100.64.20.6:20

RP/0/RP0/CPU0:cisco-kudo-02#show bgp vrf UG-B nexthop-set
Thu Jan  7 10:51:17.510 UTC

 Resilient per-CE nexthop set, ID 1
 Number of nexthops 1, Label 0, Flags 0x2100
 SRv6-VPN SID: fd00:5:5:0:45::/128
 Nexthops:
 172.24.39.9
 Reference count 2,

RP/0/RP0/CPU0:cisco-kudo-02#show route vrf UG-B 100.64.20.49/32 detail
Thu Jan  7 10:49:29.987 UTC

Routing entry for 100.64.20.49/32
  Known via "bgp 65091", distance 200, metric 0
  Tag 65049, type internal
  Installed Jan  7 05:20:28.259 for 05:29:01
  Routing Descriptor Blocks
    fd00:6:6::6, from fd00:6:6::6
      Nexthop in Vrf: "default", Table: "default", IPv6 Unicast, Table Id: 0xe0800000
      Route metric is 0
      Label: None
      Tunnel ID: None
      Binding Label: None
      Extended communities count: 0
      Source RD attributes: 0x0001:25664:335937556
      NHID:0x0(Ref:0)
      SRv6 Transit Type: T.Encaps.Red
      SRv6 SID-list { fd00:6:6:0:45:: }
  Route version is 0x1 (1)
  No local label
  IP Precedence: Not Set
  QoS Group ID: Not Set
  Flow-tag: Not Set
  Fwd-class: Not Set
  Route Priority: RIB_PRIORITY_RECURSIVE (12) SVD Type RIB_SVD_TYPE_REMOTE
  Download Priority 3, Download Version 10
  No advertising protos.

RP/0/RP0/CPU0:cisco-kudo-02#show cef vrf UG-B 100.64.20.49/32 detail location 0/0/CPU0
Thu Jan  7 10:50:32.096 UTC
100.64.20.49/32, version 10, SRv6 Transit, internal 0x5000001 0x0 (ptr 0x197b586c) [1], 0x0 (0x0), 0x0 (0x1cd92520)
 Updated Jan  7 05:20:28.425
 Prefix Len 32, traffic index 0, precedence n/a, priority 3
  gateway array (0x1e4af618) reference count 1, flags 0x2010, source rib (7), 0 backups
                [1 type 3 flags 0x48441 (0x18d3d2d0) ext 0x0 (0x0)]
  LW-LDI[type=0, refc=0, ptr=0x0, sh-ldi=0x0]
  gateway array update type-time 1 Jan  7 05:20:28.424
 LDI Update time Jan  7 05:20:28.424

  Level 1 - Load distribution: 0
  [0] via fd00:6:6::/128, recursive

   via fd00:6:6::/128, 9 dependencies, recursive [flags 0x6000]
    path-idx 0 NHID 0x0 [0x19b48364 0x0]
    next hop VRF - 'default', table - 0xe0800000
    next hop fd00:6:6::/128 via fd00:6:6::/64
    SRv6 T.Encaps.Red SID-list {fd00:6:6:0:45::}

    Load distribution: 0 (refcount 1)

    Hash  OK  Interface                 Address
    0     Y   GigabitEthernet0/0/0/0.56 fe80::56:6

toshi01kudo / SR-MPLS_Multi_AS_MPBGP_Practice

readme

SR-MPLS Multi AS MP-BGP Practice

前提条件

Network diagram

Layer 3 IP assignment

Layer 2.8 Segment Routing ID assignment

Layer 2 VLAN assignment

Layer 1 Physical port assignment

設計詳細

Segment Routing のとは？

Segment Routing のメリット

SR-MPLS の基本設定とIGP

IGPの選択

SRGBの設定

Node SID設定

Adjacency-SID設定

TI-LFA設定

Overlay MP-BGP - iBGP 設定

Overlay MP-BGP - eBGP + VRF 設定

Segment Routing 環境での Inter AS MP-BGP

SR-MPLSの状態確認

ルーティングテーブル

LFIBテーブル

SRv6 の基本設定

Locatorの設定

IGPの設定

Overlay MP-BGP - iBGP 設定

Overlay MP-BGP - eBGP + VRF 設定

SRv6の状態確認

ルーティングテーブル

SRv6 情報

SRv6 ルート情報

End.DT4 Egress ルート

End.DT4 Ingress ルート

End.DX4 Egress ルート

End.DX4 Ingress ルート