cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
640
Views
0
Helpful
2
Replies

How to configure multicast service on SR-MPLS TREE-SID

tamatsushita
Level 1
Level 1

Hi all,

I am trying multicast service on SR-MPLS, referencing this documentation.

I would like to configure "Static Segment Routing Tree-SID" for now.

https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5500/segment-routing/72x/b-segment-routing-cg-ncs5500-72x/segment-routing-tree-segment-identifier.pdf

Network Topology is as the figure.

Root node is xr9kv-1, loopback addr is 10.255.0.1.

Leaft node is xr9kv-4, loopback addr is 10.255.0.4.

Multicast source is client1; 192.168.01.

 

The PCE configuration is as below.

 

 

RP/0/RP0/CPU0:xr9kv-4#show running-config pce 
Sun Oct  6 10:04:42.484 UTC
pce
 address ipv4 10.255.0.4
 segment-routing
  traffic-eng
   p2mp
    endpoint-set LEAF
     ipv4 10.255.0.4
    !
    policy TREE-SID
     source ipv4 10.255.0.1
     color 9999 endpoint-set LEAF
     treesid mpls 15200
     candidate-paths
      preference 100
       dynamic
       !
      !
     !
    !
   !
  !
 !
 password encrypted 0614002E581F5B4A
!         

 

 

And, computed status as below.

 

 

RP/0/RP0/CPU0:xr9kv-4#show pce lsp p2mp private 
Sun Oct  6 10:09:26.385 UTC

Tree: TREE-SID, Root: 10.255.0.1 
 PCC: 10.255.0.1
 Label:    15200     Operational: up  Admin: up
 Local LFA FRR: Disabled
 Metric Type: TE
 Transition count: 3
 Uptime: 00:36:13 (since Sun Oct 06 09:33:13 UTC 2024)
 Destinations: 10.255.0.4
 Nodes:
  Node[0]: 10.255.0.1+ (xr9kv-1)
   Role: Ingress
   State Changes: 0x7 (New Node,New Hops,Role Change)
   Endpoints: 10.255.0.4
   Hops:
    Incoming: 15200 CC-ID: 3
    Outgoing: 15200 CC-ID: 3 (10.14.0.4) [xr9kv-4:10.255.0.4]
      Endpoints: 10.255.0.4
  Node[1]: 10.255.0.4+ (xr9kv-4)
   Role: Egress
   State Changes: 0x7 (New Node,New Hops,Role Change)
   Hops:
    Incoming: 15200 CC-ID: 4
          

 

 

 

The root node knows lsp computed on PCE.

 

 

RP/0/RP0/CPU0:xr9kv-1#show seg traffic-eng p2mp policy private 
Sun Oct  6 10:12:45.910 UTC

SR-TE P2MP policy database: 
----------------------
! - Replications with Fast Re-route, * - Stale dynamic policies/endpoints

Policy: TREE-SID  LSM-ID: 0x40003 
 PCE Creator: 10.255.0.4
 Role: Root
 Tree label: 15200
 Head LSM-ID label: 15200
 Replication:
  Incoming label: 15200 CC-ID: 3
   LMRIB rewrite installed
   FIB path is not notified
  Interface: GigabitEthernet0/0/0/2 [10.14.0.4]  Outgoing label: 15200 CC-ID: 3
   LMRIB rewrite installed
   FIB path notified
  Event history (latest first):
   Time                    Event
   Oct  6 09:33:12.951     Forwarding updated: LBL RW ADD LBL: 15200 TBL-ID: 0xe0000000 flags: 0x10 LSM-ID: 0x40003 || OUTINFO ADD LBL: 15200 -> 15200 IFH: 0x1000030 addr: 10.14.0.4 || HEAD LSM-ID SET LBL: 15200 LSM-ID: 0x40003 || LMRIB FLUSH
   Oct  6 09:33:12.951     TreeSID created

 

 

But mrib on the root node does not have specific entry.

I think, it should have the entry like (192.168.0.1, 232.1.1.1)

 

 

RP/0/RP0/CPU0:xr9kv-1#show mrib vrf L3VPN route

(*,224.0.0.0/24) Flags: D P
  Up: 2w3d

(*,224.0.1.39) Flags: S P
  Up: 2w3d
          
(*,224.0.1.40) Flags: S P
  Up: 2w3d
  Outgoing Interface List
    GigabitEthernet0/0/0/3 Flags: II LI, Up: 2w3d

(*,232.0.0.0/8) Flags: D P
  Up: 1d08h

(*,233.0.0.0/8) Flags: D P
  Up: 1d06h

 

 

 

What configuration is missing? 

Configuration of xr9kv-1 is as below. (only related multicast routing)

 

 

RP/0/RP0/CPU0:xr9kv-1#show running-config multicast-routing 
Sun Oct  6 10:23:14.240 UTC
multicast-routing
 address-family ipv4
  interface Loopback0
   enable
  !
  interface all enable
 !
 vrf L3VPN
  address-family ipv4
   interface Loopback0
   !
   interface GigabitEthernet0/0/0/3
    enable
   !
   interface all enable
   mdt static segment-routing
  !
 !
!

RP/0/RP0/CPU0:xr9kv-1#
RP/0/RP0/CPU0:xr9kv-1#show running-config router pim        
Sun Oct  6 10:23:21.470 UTC
router pim
 address-family ipv4
  interface Loopback0
   enable
  !
  interface GigabitEthernet0/0/0/2
   enable
  !
 !
 vrf L3VPN
  address-family ipv4
   rpf topology route-policy sr-p2mp-core-tree
   interface GigabitEthernet0/0/0/3
    enable
   !
   ssm range ssm
   sr-p2mp-policy TREE-SID
    static-group 232.1.1.1 192.168.0.1
    static-group 233.1.1.5 192.168.0.1
   !
  !
 !
!
          

 

 

 

 

topology.png

2 Replies 2

tamatsushita
Level 1
Level 1

I found missing "mdt source Loopback0"

RP/0/RP0/CPU0:xr9kv-1#show running-config multicast-routing 
Sun Oct  6 16:15:19.272 UTC
multicast-routing
 address-family ipv4
  interface Loopback0
   enable
  !
 !
 vrf L3VPN
  address-family ipv4
   mdt source Loopback0       # This line
   interface all enable
   mdt static segment-routing
  !
 !
!

 Then I could see (192.168.0.1, 232.1.1.1) entry in mrib.

RP/0/RP0/CPU0:xr9kv-1#show mrib vrf L3VPN route   
(*,224.0.0.0/24) Flags: D P
  Up: 02:29:53

(*,224.0.1.39) Flags: S P
  Up: 02:29:53
          
(*,224.0.1.40) Flags: S P
  Up: 02:29:53
  Outgoing Interface List
    GigabitEthernet0/0/0/3 Flags: II LI, Up: 02:27:40

(*,232.0.0.0/8) Flags: D P
  Up: 02:07:23

(192.168.0.1,232.1.1.1) RPF nbr: 192.168.0.1 Flags: RPF
  Up: 02:24:33
  Incoming Interface List
    GigabitEthernet0/0/0/3 Flags: A, Up: 02:07:23
  Outgoing Interface List
    TRmdtL3VPN Flags: F NS TRMI, Up: 00:29:29
RP/0/RP0/CPU0:xr9kv-1#  

 

Then i captured packets but I could not see multicast packet encapsulated mpls.

RP/0/RP0/CPU0:xr9kv-1#show segment-routing traffic-eng p2mp policy 
Sun Oct  6 16:19:08.792 UTC

SR-TE P2MP policy database: 
----------------------
! - Replications with Fast Re-route, * - Stale dynamic policies/endpoints

Policy: TREE-SID  LSM-ID: 0x40002 
 Role: Root
 Replication:
  Incoming label: 17000 CC-ID: 13
  Interface: GigabitEthernet0/0/0/2 [10.14.0.4]  Outgoing label: 17000 CC-ID: 13

  

Why? What I need extra configuration?

I found error messages as below.

I think it might related the issue because I can see "17000" .  This is TREE-SID.

fib_mgr[159]: %ROUTING-FIB-3-PLATF_UPD_FAIL : FIB platform update failed: Obj=FIB_DATA_TYPE_MOL[ptr=0x11a7c69f8,refc=0x3,flags=0x1222] Action=MODIFY Proto=mpls. Cerr=Invalid argument  : fib_mgr : (PID=4963) :  -Traceback= 561280e8da62 561280e90fa9 561280e116cf 561280e10228 561280ef331c 561280e04eb7 561280e06557 561280ef32a6 561280f2c009 561280ef331c 561280e04eb7 561280e06557 561280ef32a6 561280e0c7a9 561280d11e26 7fd5c9aa1715


fib_mgr[159]: %ROUTING-FIB-3-PD_FAIL : FIB platform error: fib_mpls_mol_platform_update 202 MOL (LL 17000) (mpi_flags 0x0, lsp_flags 0x0) PD action MODIFY failed rc 0x16 Invalid argument  : fib_mgr : (PID=4963) :  -Traceback= 561280e116cf 561280e10228 561280ef331c 561280e04eb7 561280e06557 561280ef32a6 561280f2c009 561280ef331c 561280e04eb7 561280e06557 561280ef32a6 561280e0c7a9 561280d11e26 7fd5c9aa1715 7fd5c9aab5df 561280d1ad29

fib_mgr[159]: %ROUTING-FIB-3-ASSERT_RL : FIB internal inconsistency detected: mpls mcast ol 210   <<<more info in 'show logging'>>>  : fib_mgr : (PID=4963) :  -Traceback= 7fd5c9c09372 561280e8db4d 561280e90fa9 561280e116cf 561280e10228 561280ef331c 561280e04eb7 561280e06557 561280ef32a6 561280f2c009 561280ef331c 561280e04eb7 561280e06557 561280ef32a6 561280e0c7a9 561280d11e26