Wednesday, December 26, 2018

CCIE SPv4 MPLS Multicast VPN - Profile 4 Partitioned MDT - MLDP MP2MP - BGP-AD - PIM C-mcast Signaling

In this post we will take a look at our first Partitioned MDT profile, Profile 4. This profile and Profile 2 are pretty close, the difference is Profile 4 enables BGP Auto Discovery and Data MDTs. Profile 2 did not work during testing and is only supported on XR. Since this is a variation, the entire configuration is pasted in. The main thing about the partitioned tables that I experienced is the on demand adding and deleting of P2MP MDTs in the core. There is still a full mesh of connections, the (*, G) entries, the (S, G) entries are the P2MP connections.

XR1, XR5 and XR6
route-policy RPL_MLDP_PART_MP2MP
  set core-tree mldp-partitioned-mp2mp
end-policy
!
router pim
 vrf CORE
  address-family ipv4
   rpf topology route-policy RPL_MLDP_PART_MP2MP
  !
 !
!
multicast-routing
 address-family ipv4
  mdt source Loopback0
  interface all enable
 !
 vrf CORE
  address-family ipv4
   mdt source Loopback0
   rate-per-route
   interface all enable
   accounting per-prefix
   bgp auto-discovery mldp
   !
   mdt partitioned mldp ipv4 mp2mp
   mdt data mldp 100 immediate-switch



With the configuration in place, we'll begin by verifying the BGP MVPN tables, MPLS MLDP databases and MPLS Forwarding tables for reference later when traffic is initiated and P2MP MDTs are created and forwarding table entries are added. Ironically, MPLS label switching counters have been hit and miss on this lab.

RP/0/0/CPU0:XR1#sh bgp ipv4 mvpn | b Network
Wed Dec 26 19:04:25.869 UTC
   Network            Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 100:100 (default for vrf CORE)
*>i[1][192.0.2.3]/40  192.0.2.3                0    100      0 ?
*>i[1][192.0.2.7]/40  192.0.2.7                0    100      0 ?
*> [1][192.0.2.21]/40 0.0.0.0                                0 i
*>i[1][192.0.2.25]/40 192.0.2.25                    100      0 i
*>i[1][192.0.2.26]/40 192.0.2.26                    100      0 i
*> [3][0][0.0.0.0][0][0.0.0.0][192.0.2.21]/120
                      0.0.0.0                                0 i
*>i[3][0][0.0.0.0][0][0.0.0.0][192.0.2.25]/120
                      192.0.2.25                    100      0 i
*>i[3][0][0.0.0.0][0][0.0.0.0][192.0.2.26]/120
                      192.0.2.26                    100      0 i
*>i[3][0][0.0.0.0][32][224.0.0.13][192.0.2.25]/120
                      192.0.2.25                    100      0 i
*> [3][32][192.0.2.16][32][232.16.16.16][192.0.2.21]/120
                      0.0.0.0                                0 i
*> [3][32][192.0.2.16][32][232.19.19.19][192.0.2.21]/120
                      0.0.0.0                                0 i
*> [3][32][192.0.2.16][32][232.20.20.20][192.0.2.21]/120
                      0.0.0.0                                0 i
*>i[7][100:100][116229][32][192.0.2.16][32][232.16.16.16]/184
                      192.0.2.7                0    100      0 ?


RP/0/0/CPU0:XR1#sh mpls mldp database | in "FEC Root|P2MP|MP2MP|Labels"
Wed Dec 26 19:34:22.686 UTC
LSM-ID: 0x0000D  Type: P2MP  Uptime: 02:29:13
  FEC Root           : 192.0.2.21 (we are the root)
LSM-ID: 0x0000E  Type: P2MP  Uptime: 02:29:12
  FEC Root           : 192.0.2.25 
LSM-ID: 0x00012  Type: P2MP  Uptime: 02:24:23
  FEC Root           : 192.0.2.21 (we are the root)
LSM-ID: 0x00013  Type: P2MP  Uptime: 02:24:16
  FEC Root           : 192.0.2.21 (we are the root)
LSM-ID: 0x0000C  Type: MP2MP  Uptime: 02:29:15
  FEC Root           : 192.0.2.21 (we are the root)
LSM-ID: 0x0000F  Type: MP2MP  Uptime: 02:27:13
  FEC Root           : 192.0.2.25 


RP/0/0/CPU0:XR1#show mpls forwarding labels 91012 91024
Wed Dec 26 19:35:11.422 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes       
Label  Label       or ID              Interface                    Switched    
------ ----------- ------------------ ------------ --------------- ------------
91012  92024       MLDP: 0x0000c      Gi0/0/0/0.112 100.64.112.120  0           
       4028        MLDP: 0x0000c      Gi0/0/0/0.114 100.64.114.4    0           
91013  4023        MLDP: 0x0000f      Gi0/0/0/0.114 100.64.114.4    0           
91014  24022       MLDP: 0x80002      UNKNOWN intf 0xa12db890 192.0.2.26      0           
91016  Unlabelled  MLDP: 0x0000e
91017  Unlabelled  MLDP: 0x0000f
91021  92024       MLDP: 0x0000c      Gi0/0/0/0.112 100.64.112.120  0           
91022  4029        MLDP: 0x00012      Gi0/0/0/0.114 100.64.114.4    0           
91023  4028        MLDP: 0x0000c      Gi0/0/0/0.114 100.64.114.4    0           
91024  4030        MLDP: 0x00013      Gi0/0/0/0.114 100.64.114.4    0  



RP/0/0/CPU0:XR1#sh mrib vrf CORE route                         
Wed Dec 26 19:39:31.624 UTC

IP Multicast Routing Information Base
Entry flags: L - Domain-Local Source, E - External Source to the Domain,
    C - Directly-Connected Check, S - Signal, IA - Inherit Accept,
    IF - Inherit From, D - Drop, ME - MDT Encap, EID - Encap ID,
    MD - MDT Decap, MT - MDT Threshold Crossed, MH - MDT interface handle
    CD - Conditional Decap, MPLS - MPLS Decap, EX - Extranet
    MoFE - MoFRR Enabled, MoFS - MoFRR State, MoFP - MoFRR Primary
    MoFB - MoFRR Backup, RPFID - RPF ID Set, X - VXLAN
Interface flags: F - Forward, A - Accept, IC - Internal Copy,
    NS - Negate Signal, DP - Don't Preserve, SP - Signal Present,
    II - Internal Interest, ID - Internal Disinterest, LI - Local Interest,
    LD - Local Disinterest, DI - Decapsulation Interface
    EI - Encapsulation Interface, MI - MDT Interface, LVIF - MPLS Encap,
    EX - Extranet, A2 - Secondary Accept, MT - MDT Threshold Crossed,
    MA - Data MDT Assigned, LMI - mLDP MDT Interface, TMI - P2MP-TE MDT Interface
    IRMI - IR MDT Interface

(*,227.1.2.3) RPF nbr: 192.0.2.25 Flags: C RPF
  Up: 02:32:22
  Incoming Interface List
    LmdtCORE Flags: A LMI, Up: 02:32:22
  Outgoing Interface List
    GigabitEthernet0/0/0/0.204 Flags: F NS, Up: 02:32:22

(192.0.2.16,232.16.16.16) RPF nbr: 100.64.204.16 Flags: RPF
  Up: 02:34:22
  Incoming Interface List
    GigabitEthernet0/0/0/0.204 Flags: A, Up: 02:34:22
  Outgoing Interface List
    LmdtCORE Flags: F LMI MA TR, Up: 02:34:22

(192.0.2.16,232.19.19.19) RPF nbr: 100.64.204.16 Flags: RPF
  Up: 02:29:24
  Incoming Interface List
    GigabitEthernet0/0/0/0.204 Flags: A, Up: 02:29:24
  Outgoing Interface List
    LmdtCORE Flags: F LMI MA TR, Up: 02:29:24

(192.0.2.16,232.20.20.20) RPF nbr: 100.64.204.16 Flags: RPF
  Up: 02:29:32
  Incoming Interface List
    GigabitEthernet0/0/0/0.204 Flags: A, Up: 02:29:32
  Outgoing Interface List
    LmdtCORE Flags: F LMI MA TR, Up: 02:29:32

Since R16 will be our source, we check XR1s VRF MRIB to see what routes are present, we see the (*, G) and 3 (S, G) entries. This tells us that signaling is working.

RP/0/0/CPU0:XR5#sh bgp ipv4 mvpn | b Network
Wed Dec 26 19:40:29.337 UTC
   Network            Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 100:100 (default for vrf CORE)
*>i[1][192.0.2.3]/40  192.0.2.3                0    100      0 ?
*>i[1][192.0.2.7]/40  192.0.2.7                0    100      0 ?
*>i[1][192.0.2.21]/40 192.0.2.21                    100      0 i
*> [1][192.0.2.25]/40 0.0.0.0                                0 i
*>i[1][192.0.2.26]/40 192.0.2.26                    100      0 i
*>i[3][0][0.0.0.0][0][0.0.0.0][192.0.2.21]/120
                      192.0.2.21                    100      0 i
*> [3][0][0.0.0.0][0][0.0.0.0][192.0.2.25]/120
                      0.0.0.0                                0 i
*>i[3][0][0.0.0.0][0][0.0.0.0][192.0.2.26]/120
                      192.0.2.26                    100      0 i
*> [3][0][0.0.0.0][32][224.0.0.13][192.0.2.25]/120
                      0.0.0.0                                0 i
*>i[3][32][192.0.2.16][32][232.16.16.16][192.0.2.21]/120
                      192.0.2.21                    100      0 i
*>i[3][32][192.0.2.16][32][232.19.19.19][192.0.2.21]/120
                      192.0.2.21                    100      0 i
*>i[3][32][192.0.2.16][32][232.20.20.20][192.0.2.21]/120
                      192.0.2.21                    100      0 i


RP/0/0/CPU0:XR5#sh mpls mldp database | in "FEC Root|Label|MP2MP|P2MP" 
Wed Dec 26 19:41:27.873 UTC
LSM-ID: 0x00003  Type: P2MP  Uptime: 02:36:17
  FEC Root           : 192.0.2.25 (we are the root)
      Local Label     : 24027 (internal)
LSM-ID: 0x00007  Type: P2MP  Uptime: 02:31:28
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24033             
LSM-ID: 0x00006  Type: MP2MP  Uptime: 02:31:29
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24032             Remote Label (U): 1031
      Local Label     : 24031 (internal)
LSM-ID: 0x00002  Type: MP2MP  Uptime: 02:36:46
  FEC Root           : 192.0.2.25 (we are the root)
      Local Label     : 24022 (internal)


RP/0/0/CPU0:XR5#sh mpls forwarding labels 24027 24033
Wed Dec 26 19:42:05.611 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes       
Label  Label       or ID              Interface                    Switched    
------ ----------- ------------------ ------------ --------------- ------------
24027  1024        MLDP: 0x00003      Gi0/0/0/0.15 100.64.15.1     0           
24028  Unlabelled  MLDP: 0x00002
24031  1031        MLDP: 0x00006      Gi0/0/0/0.15 100.64.15.1     0           
24032  Unlabelled  MLDP: 0x00006
24033  Unlabelled  MLDP: 0x00007


RP/0/0/CPU0:XR5#sh mrib vrf CORE route
Wed Dec 26 19:42:26.159 UTC

IP Multicast Routing Information Base
Entry flags: L - Domain-Local Source, E - External Source to the Domain,
    C - Directly-Connected Check, S - Signal, IA - Inherit Accept,
    IF - Inherit From, D - Drop, ME - MDT Encap, EID - Encap ID,
    MD - MDT Decap, MT - MDT Threshold Crossed, MH - MDT interface handle
    CD - Conditional Decap, MPLS - MPLS Decap, EX - Extranet
    MoFE - MoFRR Enabled, MoFS - MoFRR State, MoFP - MoFRR Primary
    MoFB - MoFRR Backup, RPFID - RPF ID Set, X - VXLAN
Interface flags: F - Forward, A - Accept, IC - Internal Copy,
    NS - Negate Signal, DP - Don't Preserve, SP - Signal Present,
    II - Internal Interest, ID - Internal Disinterest, LI - Local Interest,
    LD - Local Disinterest, DI - Decapsulation Interface
    EI - Encapsulation Interface, MI - MDT Interface, LVIF - MPLS Encap,
    EX - Extranet, A2 - Secondary Accept, MT - MDT Threshold Crossed,
    MA - Data MDT Assigned, LMI - mLDP MDT Interface, TMI - P2MP-TE MDT Interface
    IRMI - IR MDT Interface

(*,227.1.2.3) RPF nbr: 100.64.206.20 Flags: C RPF
  Up: 02:36:13
  Incoming Interface List
    GigabitEthernet0/0/0/0.206 Flags: A, Up: 02:36:13
  Outgoing Interface List
    LmdtCORE Flags: F LMI TR, Up: 02:36:13

(192.0.2.16,232.20.20.20) RPF nbr: 192.0.2.21 Flags: RPF
  Up: 02:32:28
  Incoming Interface List
    LmdtCORE Flags: A LMI, Up: 02:32:28
  Outgoing Interface List
    GigabitEthernet0/0/0/0.206 Flags: F NS, Up: 02:32:28

Checking XR5s VRF MRIB, we see the (*, G) and (S, G) entries.

RP/0/0/CPU0:XR6#sh bgp ipv4 mvpn | b Network
Wed Dec 26 19:43:22.724 UTC
   Network            Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 100:100 (default for vrf CORE)
*>i[1][192.0.2.3]/40  192.0.2.3                0    100      0 ?
*>i[1][192.0.2.7]/40  192.0.2.7                0    100      0 ?
*>i[1][192.0.2.21]/40 192.0.2.21                    100      0 i
*>i[1][192.0.2.25]/40 192.0.2.25                    100      0 i
*> [1][192.0.2.26]/40 0.0.0.0                                0 i
*>i[3][0][0.0.0.0][0][0.0.0.0][192.0.2.21]/120
                      192.0.2.21                    100      0 i
*>i[3][0][0.0.0.0][0][0.0.0.0][192.0.2.25]/120
                      192.0.2.25                    100      0 i
*> [3][0][0.0.0.0][0][0.0.0.0][192.0.2.26]/120
                      0.0.0.0                                0 i
*>i[3][0][0.0.0.0][32][224.0.0.13][192.0.2.25]/120
                      192.0.2.25                    100      0 i
*>i[3][32][192.0.2.16][32][232.16.16.16][192.0.2.21]/120
                      192.0.2.21                    100      0 i
*>i[3][32][192.0.2.16][32][232.19.19.19][192.0.2.21]/120
                      192.0.2.21                    100      0 i
*>i[3][32][192.0.2.16][32][232.20.20.20][192.0.2.21]/120
                      192.0.2.21                    100      0 i


RP/0/0/CPU0:XR6#sh mpls mldp database | in "FEC Root|P2MP|MP2MP|Label"
Wed Dec 26 19:43:57.922 UTC
LSM-ID: 0x00003  Type: P2MP  Uptime: 02:38:47
  FEC Root           : 192.0.2.25 
      Local Label (D) : 24023             
LSM-ID: 0x00007  Type: P2MP  Uptime: 02:33:51
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24032             
LSM-ID: 0x00006  Type: MP2MP  Uptime: 02:33:52
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24031             Remote Label (U): 2028
      Local Label     : 24030 (internal)
LSM-ID: 0x00004  Type: MP2MP  Uptime: 02:37:46
  FEC Root           : 192.0.2.25 
      Local Label (D) : 24028             Remote Label (U): 2011
      Local Label     : 24027 (internal)
LSM-ID: 0x00002  Type: MP2MP  Uptime: 02:39:02
  FEC Root           : 192.0.2.26 (we are the root)
      Local Label     : 24022 (internal)


RP/0/0/CPU0:XR6#sh mpls forwarding labels 24022 24032
Wed Dec 26 19:44:35.299 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes       
Label  Label       or ID              Interface                    Switched    
------ ----------- ------------------ ------------ --------------- ------------
24023  Unlabelled  MLDP: 0x00003
24024  Pop         192.0.2.3/32       Gi0/0/0/0.63 100.64.63.3     24337       
24025  Unlabelled  192.0.2.19/32[V]   Gi0/0/0/0.215 100.64.215.19   1600        
24027  2011        MLDP: 0x00004      Gi0/0/0/0.26 100.64.26.2     0           
24028  Unlabelled  MLDP: 0x00004
24030  2028        MLDP: 0x00006      Gi0/0/0/0.26 100.64.26.2     0           
24031  Unlabelled  MLDP: 0x00006
24032  Unlabelled  MLDP: 0x00007



R16#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
       L - Local, P - Pruned, R - RP-bit set, F - Register flag,
       T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
       U - URD, I - Received Source Specific Host Report, 
       Z - Multicast Tunnel, z - MDT-data group sender, 
       Y - Joined MDT-data group, y - Sending to MDT-data group, 
       G - Received BGP C-Mroute, g - Sent BGP C-Mroute, 
       N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed, 
       Q - Received BGP S-A Route, q - Sent BGP S-A Route, 
       V - RD & Vector, v - Vector, p - PIM Joins on route, 
       x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
 Timers: Uptime/Expires
 Interface state: Interface, Next-Hop or VCD, State/Mode

(192.0.2.16, 232.20.20.20), 02:36:13/00:03:15, flags: sT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet1.204, Forward/Sparse, 02:36:13/00:03:15

(192.0.2.16, 232.19.19.19), 02:36:06/00:03:25, flags: sT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet1.204, Forward/Sparse, 02:36:06/00:03:25

(192.0.2.16, 232.16.16.16), 02:41:03/00:03:25, flags: sT
  Incoming interface: Loopback0, RPF nbr 0.0.0.0
  Outgoing interface list:
    GigabitEthernet1.204, Forward/Sparse, 02:41:03/00:03:25

(*, 227.1.2.3), 02:39:04/00:02:06, RP 192.0.2.20, flags: SJCL
  Incoming interface: GigabitEthernet1.204, RPF nbr 100.64.204.11
  Outgoing interface list:
    Loopback0, Forward/Sparse, 02:39:04/00:02:06

R16 has all 4 mroute entries.

R20#sh ip pim rp map
PIM Group-to-RP Mappings
This system is a candidate RP (v2)
This system is the Bootstrap Router (v2)

Group(s) 224.0.0.0/4
  RP 192.0.2.20 (?), v2
    Info source: 192.0.2.20 (?), via bootstrap, priority 0, holdtime 150
         Uptime: 03:03:36, expires: 00:01:48

R20 is the customer RP, and it states that.

RP/0/0/CPU0:XR1#sh pim vrf CORE rp map
Wed Dec 26 19:47:13.193 UTC
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
  RP 192.0.2.20 (?), v2
    Info source: 192.0.2.25 (?), elected via bsr, priority 0, holdtime 150
      Uptime: 02:41:02, expires: 00:01:36

Checking XR1, the PE connected to the customer source, we check the VRF aware PIM table and see that XR1 sees R20 as the customer RP router.

R16#sh ip pim rp map
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
  RP 192.0.2.20 (?), v2
    Info source: 192.0.2.20 (?), via bootstrap, priority 0, holdtime 150
         Uptime: 02:41:21, expires: 00:02:16

Checking R16, the RP mapping is populated.

R16#ping 227.1.2.3 repeat 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 227.1.2.3, timeout is 2 seconds:

Reply to request 0 from 192.0.2.16, 34 ms
Reply to request 0 from 192.0.2.19, 46 ms
Reply to request 0 from 100.64.215.19, 45 ms
Reply to request 0 from 192.0.2.20, 39 ms
Reply to request 1 from 192.0.2.16, 3 ms
Reply to request 1 from 192.0.2.19, 50 ms
Reply to request 1 from 100.64.215.19, 26 ms
Reply to request 1 from 192.0.2.20, 13 ms
Reply to request 1 from 192.0.2.20, 13 ms

We ping the ASM group first from R16.

XR1
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x00016 [global-id 2] P2MP 192.0.2.21, Add PIM MDT branch remote label no_label 
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x00016 [global-id 2] P2MP 192.0.2.21, Add LDP 192.0.2.4:0 branch remote label 4025 
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x00017 [global-id 6] P2MP 192.0.2.21, Add PIM MDT branch remote label no_label 
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x00017 [global-id 6] P2MP 192.0.2.21, Add LDP 192.0.2.4:0 branch remote label 4026

XR6
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x0000A [global-id 2] P2MP 192.0.2.21, Add PIM MDT branch remote label no_label 
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x0000B [global-id 6] P2MP 192.0.2.21, Add PIM MDT branch remote label no_label

XR5
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x0000A [global-id 2] P2MP 192.0.2.21, Add PIM MDT branch remote label no_label
mpls_ldp[1181]: %ROUTING-MLDP-5-BRANCH_ADD : 0x0000B [global-id 6] P2MP 192.0.2.21, Add PIM MDT branch remote label no_label

We see several labels get generated in the log. This is the behavior you want to see, these labels are generated on demand since the Partitioned MDT is designed to build MDTs for traffic when the traffic needs to be sent. Then tear down the MDT when traffic is finished, this cuts down on the amount of state in the core.

RP/0/0/CPU0:XR6#sh mpls mldp database | in "FEC Root|P2MP|MP2MP|Label"
Wed Dec 26 19:50:04.137 UTC
LSM-ID: 0x0000A  Type: P2MP  Uptime: 00:01:50
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24026             
LSM-ID: 0x00003  Type: P2MP  Uptime: 02:44:54
  FEC Root           : 192.0.2.25 
      Local Label (D) : 24023             
LSM-ID: 0x00007  Type: P2MP  Uptime: 02:39:57
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24032             
LSM-ID: 0x0000B  Type: P2MP  Uptime: 00:01:48
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24029             
LSM-ID: 0x00006  Type: MP2MP  Uptime: 02:39:58
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24031             Remote Label (U): 2028
      Local Label     : 24030 (internal)
LSM-ID: 0x00004  Type: MP2MP  Uptime: 02:43:53
  FEC Root           : 192.0.2.25 
      Local Label (D) : 24028             Remote Label (U): 2011
      Local Label     : 24027 (internal)
LSM-ID: 0x00002  Type: MP2MP  Uptime: 02:45:08
  FEC Root           : 192.0.2.26 (we are the root)
      Local Label     : 24022 (internal)

Checking XR6, we see new labels, specifically A is 24026 and B is 24029.

RP/0/0/CPU0:XR6#sh mpls forwarding labels 24022 24032                 
Wed Dec 26 19:51:09.522 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes       
Label  Label       or ID              Interface                    Switched    
------ ----------- ------------------ ------------ --------------- ------------
24023  Unlabelled  MLDP: 0x00003
24024  Pop         192.0.2.3/32       Gi0/0/0/0.63 100.64.63.3     25063       
24025  Unlabelled  192.0.2.19/32[V]   Gi0/0/0/0.215 100.64.215.19   1600        
24026  Unlabelled  MLDP: 0x0000a
24027  2011        MLDP: 0x00004      Gi0/0/0/0.26 100.64.26.2     0           
24028  Unlabelled  MLDP: 0x00004
24029  Unlabelled  MLDP: 0x0000b
24030  2028        MLDP: 0x00006      Gi0/0/0/0.26 100.64.26.2     0           
24031  Unlabelled  MLDP: 0x00006
24032  Unlabelled  MLDP: 0x00007

Labels 24026 and 24029 are added to the forwarding table

RP/0/0/CPU0:XR5#sh mpls mldp database | in "FEC Root|Label|MP2MP|P2MP"
Wed Dec 26 19:50:23.536 UTC
LSM-ID: 0x0000A  Type: P2MP  Uptime: 00:02:09
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24026             
LSM-ID: 0x00003  Type: P2MP  Uptime: 02:45:13
  FEC Root           : 192.0.2.25 (we are the root)
      Local Label     : 24027 (internal)
LSM-ID: 0x00007  Type: P2MP  Uptime: 02:40:24
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24033             
LSM-ID: 0x0000B  Type: P2MP  Uptime: 00:02:07
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24029             
LSM-ID: 0x00006  Type: MP2MP  Uptime: 02:40:25
  FEC Root           : 192.0.2.21 
      Local Label (D) : 24032             Remote Label (U): 1031
      Local Label     : 24031 (internal)
LSM-ID: 0x00002  Type: MP2MP  Uptime: 02:45:42
  FEC Root           : 192.0.2.25 (we are the root)
      Local Label     : 24022 (internal)

Same thing with XR5, labels 24029 and 24026 are allocated.

R16#ping 232.20.20.20 source lo0 repeat 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 232.20.20.20, timeout is 2 seconds:
Packet sent with a source address of 192.0.2.16 

Reply to request 0 from 192.0.2.20, 9 ms
Reply to request 0 from 192.0.2.20, 9 ms
Reply to request 1 from 192.0.2.20, 7 ms
Reply to request 1 from 192.0.2.20, 7 ms


R16#ping 232.19.19.19 source lo0 repeat 2
Type escape sequence to abort.
Sending 2, 100-byte ICMP Echos to 232.19.19.19, timeout is 2 seconds:
Packet sent with a source address of 192.0.2.16 

Reply to request 0 from 192.0.2.19, 14 ms
Reply to request 0 from 192.0.2.19, 14 ms
Reply to request 1 from 192.0.2.19, 10 ms
Reply to request 1 from 192.0.2.19, 10 ms

The SSM groups are pinged, however there isn't a verification on XR to prove the traffic is being label switched.

Thanks for stopping by!
Rob RIker, CCIE #50693

No comments:

Post a Comment