XRV 5.3.0 Multicast over Traffic Engineering P2MP tunnel

takao.nakamaru · ‎05-09-2015

Hello everyone

I am trying to make a simple test for multicast over MPLS Traffic-Engineering P2MP tunnels for IOS XR. I am using XRV for this test and as far as I can see the control plane works alright. The tunnel comes up the the correspoding MPLS labels are destributed in the test topology.

But I have not been able to test this with multicast traffic (to verify that traffic is flowing from head-end to receivers). For this I am using ping to send multicast packets from router R6 => R2, R1. I have not been successful and my attempts to find the cause of the problem have not been fruitful.

I was wondering if anyone has successfully test multicast over MPLS Traffic-Engineering P2MP tunnels in XRV (Is this feature supported in XRV in the first place?)

Specifically the multicast traffic does not seem to enter the tunnel (much more leave the router):

RP/0/0/CPU0:R6#sh mfib interface tunnel-mte 126
Sat May 9 19:23:38.276 UTC

Interface : tunnel-mte126 (Enabled)
SW Mcast pkts in : 0, SW Mcast pkts out : 2814 <<<<===
TTL Threshold : 0
Ref Count : 5

RP/0/0/CPU0:R6#sh interfaces tunnel-mte 126
Sat May 9 19:27:47.049 UTC
tunnel-mte126 is up, line protocol is up
Interface state transitions: 13
Hardware is Tunnel-MTE
Internet address is 6.6.6.6/32
MTU 1500 bytes, BW 0 Kbit
     reliability 255/255, txload Unknown, rxload Unknown
Encapsulation TUNNEL, loopback not set,
Last input never, output never
Last clearing of "show interface" counters never
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec   <<<<===
     0 packets input, 0 bytes, 0 total input drops
     0 drops for unrecognized upper-level protocol
     Received 0 broadcast packets, 0 multicast packets
     0 packets output, 0 bytes, 0 total output drops
     Output 0 broadcast packets, 0 multicast packets

RP/0/0/CPU0:R6#sh mfib route 232.0.0.1
Sat May 9 19:28:07.067 UTC

Failure Counts: RPF / TTL / Empty Olist / Encap RL / Other

(192.168.60.254,232.0.0.1), Flags:

Up: 1d03h
Last Used: never
SW Forwarding Counts: 0/0/0
SW Replication Counts: 0/0/0
SW Failure Counts: 0/0/0/0/0
tunnel-mte126 Flags: NS EG LVIF, Up:23:37:39
GigabitEthernet0/0/0/0.60 Flags: A, Up:1d03h

Is this an XRV limitation or should I continue try to find the error?

Ildar Gafiatullin · ‎05-15-2015

I am joining to question. But at first I am interested BGP mvpn session.

I have success working NG-MVPN (P2MP signalled RSVP-TE) on juniper devices M-series.

I joined IOSv PE to the working topology. On cisco PE I turned on ipv4 mvpn family and A-D and C-multicast routes had been success recieved from members of multicast VPN

Routes type 1 - received

Route Distinguisher: 10.95.95.52:1 (default for vrf mvpn-tm-pe)
*>i [1][10.95.95.52:1][10.94.94.1]/12
                       10.95.95.1                    100      0 i
*>i [1][10.95.95.52:1][10.94.94.31]/12
                       10.95.95.31                   100      0 i
*>i [1][10.95.95.52:1][10.94.94.38]/12
                       10.95.95.38                   100      0 i
*>i [1][10.95.95.52:1][10.94.94.42]/12
                       10.95.95.42                   100      0 i
*>i [1][10.95.95.52:1][10.95.95.43]/12
                       10.95.95.43                   100      0 i

Routes other types are also received.

But Cisco PE doesn't advertise even A-D route Type-1 as member this VPN.

Then I tried on XRv. 2 PE joined each other.

Config one of PE's

hostname XR6
explicit-path name to5
index 1 next-address strict ipv4 unicast 1.1.1.5
!
vrf A
vpn id 1:1
address-family ipv4 unicast
import route-target
   1:1
!
export route-target
   1:1
!
!
address-family ipv4 multicast
!
!
interface Loopback0
ipv4 address 6.6.6.6 255.255.255.255
!
interface Loopback1
vrf A
ipv4 address 172.16.0.6 255.255.255.255
!
interface tunnel-mte1
ipv4 unnumbered Loopback0
destination 1.1.1.5
path-option 1 explicit name to5
!
signalled-bandwidth 1000
!
interface MgmtEth0/0/CPU0/0
shutdown
!
interface GigabitEthernet0/0/0/0
ipv4 address 1.1.1.6 255.255.255.0
!
route-policy rpf
set core-tree p2mp-te
end-policy
!
route-policy pim-to-bgp
if destination in (5.5.5.5/32) then
    set c-multicast-routing bgp
endif
end-policy
!
router isis 1
is-type level-2-only
net 49.0000.0000.0006.00
address-family ipv4 unicast
metric-style wide
mpls traffic-eng level-2-only
mpls traffic-eng router-id Loopback0
mpls traffic-eng multicast-intact
!
interface Loopback0
passive
address-family ipv4 unicast
!
!
interface GigabitEthernet0/0/0/0
address-family ipv4 unicast
!
!
!
router bgp 1
bgp router-id 6.6.6.6
address-family ipv4 unicast
!
address-family ipv4 multicast
network 6.6.6.6/32
!
address-family vpnv4 unicast
!
address-family ipv4 mvpn
retain route-target all
!
address-family vpnv4 multicast
!
neighbor 5.5.5.5
remote-as 1
update-source Loopback0
address-family ipv4 unicast
!
address-family ipv4 multicast
!
address-family vpnv4 unicast
!
address-family ipv4 mvpn
!
address-family vpnv4 multicast
!
!
vrf A
rd 1:6
bgp router-id 172.16.0.6
address-family ipv4 unicast
   network 172.16.0.6/32
!
address-family ipv4 multicast
!
address-family ipv4 mvpn
!
!
!
rsvp
interface GigabitEthernet0/0/0/0
bandwidth
!
!
mpls traffic-eng
interface GigabitEthernet0/0/0/0
!
!
mpls ldp
address-family ipv4
!
interface GigabitEthernet0/0/0/0
!
!
multicast-routing
address-family ipv4
interface tunnel-mte1
   enable
!
mdt source Loopback0
core-tree-protocol rsvp-te
bgp auto-discovery p2mp-te
   leaf-info-required
!
mdt static p2mp-te tunnel-mte1
!
vrf A
address-family ipv4
   interface Loopback1
    enable
   !
   bgp auto-discovery p2mp-te
    segmented
    leaf-info-required
   !
!
!
!
router igmp
vrf A
interface Loopback1
   join-group 239.59.0.1
!
!
!
router pim
address-family ipv4
mdt data announce-interval 3
interface tunnel-mte1
   enable
!
!
vrf A
address-family ipv4
   rpf topology route-policy rpf
   mdt c-multicast-routing bgp
    unicast-reachability source-as enable
   !
   rp-address 172.16.0.6
   interface Loopback1
    enable
   !
!
!
!
end

I got the same result. No advertise even 1-type routes.

Experts like Luc de Gein we are waiting your answer.

Remus Grobei · ‎05-27-2015

Hello,

There is a fix so the control-plane is working for the mVPN, I tested several profiles but the forwarding is not supported.

Maybe in XRv 9000 they will have full forwarding capabilities also for mVPN.

Ildar Gafiatullin · ‎05-27-2015

Hello

I have even not working control plane between 2 XRv. No any AD routes. Show me your config and issue "show bgp ipv4 mvpn summ" pls

Remus Grobei · ‎05-28-2015

Hey,

You need a SMU for this to work.

I any case I'll recommend to use SSM if you plan to put this in production, for learning purposes is ok.

There are a few wrong or missing parts in your configuration.

I have a running topology with profile 26 Partitioned MDT - P2MP TE - BGP-AD - BGP C-mcast signaling not very different from your profile 18 default Static MDT - P2MP TE - BGP-AD - PIM C-mcast signaling.

Here are some relevant parts of the config

RP/0/RSP0/CPU0:PE01#sh run multicast-routing
Thu May 28 01:10:10.348 UTC
multicast-routing
address-family ipv4
interface Loopback0
enable
!
interface Loopback1
enable
!
ssm range SSM-MDT
!
vrf vrf1
address-family ipv4
interface GigabitEthernet0/0/0/2
enable
!
mdt source Loopback1
ssm range C-MULTICAST
rate-per-route
accounting per-prefix
bgp auto-discovery p2mp-te
leaf-info-required
!
mdt partitioned p2mp-te attribute-set VRF1
!
!
!

RP/0/RSP0/CPU0:PE01#sh run router pim
Thu May 28 01:10:31.333 UTC
router pim
address-family ipv4
interface Loopback0
enable
!
interface Loopback1
enable
!
!
vrf vrf1
address-family ipv4
rpf topology route-policy P2MP-TE-PARTITIONED
mdt c-multicast-routing bgp
!
interface GigabitEthernet0/0/0/2
enable
!
!
!
!
RP/0/RSP0/CPU0:PE01#sh run mpls traffic-eng
Thu May 28 01:10:40.535 UTC
mpls traffic-eng
interface GigabitEthernet0/0/0/0
!
interface GigabitEthernet0/0/0/1
!
logging events preemption
logging events frr-protection
auto-tunnel p2mp
tunnel-id min 1000 max 2000
!
auto-tunnel backup
timers removal unused 20
tunnel-id min 5000 max 6000
!
reoptimize 1
attribute-set p2mp-te VRF1
logging events lsp-status reoptimize
logging events lsp-status reroute
logging events lsp-status bw-change
logging events lsp-status insufficient-bandwidth
signalled-bandwidth 10000 class-type 0
fast-reroute
!

!
RP/0/RSP0/CPU0:PE01#sh run ipv4 unnumbered mpls traffic-eng
Thu May 28 01:11:47.214 UTC
ipv4 unnumbered mpls traffic-eng Loopback1

RP/0/RSP0/CPU0:PE01#sh run router bgp
Thu May 28 01:13:32.744 UTC
router bgp 12345
bgp router-id 192.168.0.10
address-family ipv4 unicast
additional-paths receive
network 192.168.1.10/32 route-policy RPL-PE-MVPN
allocate-label route-policy RPL-ALLOCATE-LABEL-LBGP
!
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
address-family l2vpn vpls-vpws
!
address-family ipv4 mvpn
!
neighbor-group PE-RR-VPN
remote-as 12345
update-source Loopback1
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
address-family l2vpn vpls-vpws
!
address-family ipv4 mvpn
!
!
neighbor-group DR-RR-IPV4
remote-as 12345
update-source Loopback0
address-family ipv4 unicast
!
!
neighbor-group DR-RR-LBGP
remote-as 12345
update-source Loopback2
address-family ipv4 labeled-unicast
route-policy RPL-DR-RR-LBGP-IN in
route-policy RPL-DR-RR-LBGP-OUT out
!
!
neighbor 192.168.0.9
use neighbor-group DR-RR-IPV4
!
neighbor 192.168.1.9
use neighbor-group PE-RR-VPN
!
neighbor 192.168.2.9
use neighbor-group DR-RR-LBGP
!
vrf vrf1
rd 1:1
address-family ipv4 unicast
redistribute connected
redistribute static
!
address-family ipv4 mvpn
!
!
!

Ildar Gafiatullin · ‎05-28-2015

let me issie "show bgp ipv4 mvpn su" pls

and show advertise mvpn routes pls

Remus Grobei · ‎05-28-2015

Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale, N Nexthop-discard
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 1:1 (default for vrf vrf1)
*>i[1][192.168.1.1]/40
192.168.1.1 100 0 i
*> [1][192.168.1.10]/40
0.0.0.0 0 i
*>i[3][0][0.0.0.0][0][0.0.0.0][192.168.1.1]/120
192.168.1.1 100 0 i
*> [3][0][0.0.0.0][0][0.0.0.0][192.168.1.10]/120
0.0.0.0 0 i
*>i[4][3][1:1][0][0.0.0.0][0][0.0.0.0][192.168.1.10][192.168.1.1]/224
192.168.1.1 100 0 i
*>i[7][1:1][16422][32][192.168.232.46][32][233.232.0.14]/184
192.168.1.1 100 0 i

Ildar Gafiatullin · ‎05-28-2015

Is it configuration on XRv or on real XR?

Remus Grobei · ‎05-28-2015

XRv, on hardware box the forwarding works but on XRv not.

Ildar Gafiatullin · ‎05-28-2015

I understood. Type me in PM your skype