4 Replies Latest reply: Aug 14, 2019 9:15 PM by Elvin Arias RSS

    MVPN profile 10

    Anton Alipov

      Hi all,

       

      I'm trying to get MVPN profile 10 working with XRv, but the head-end does not seem inclined to send multicast packets into the tunnel. (There was no such problem with profile 8).

       

      My configs:

       

      Head-end:

       

      router igmp

        vrf CUST

         interface tunnel-mte46

          static-group 232.1.2.3 172.16.126.12

      !

      multicast-routing

        address-family ipv4

         interface Loopback0

          enable

        !

         mdt source Loopback0

      !

        vrf CUST

         address-family ipv4

         !

          interface GigabitEthernet0/0/0/1

           enable

         !

          bgp auto-discovery p2mp-te

         !

          mdt static p2mp-te tunnel-mte46

       

      Tail-end:

       

      multicast-routing

        address-family ipv4

         interface Loopback0

          enable

        !

         mdt source Loopback0

      !

        vrf CUST

         address-family ipv4

          interface GigabitEthernet0/0/0/3

           enable

         !

          core-tree-protocol rsvp-te

          bgp auto-discovery p2mp-te

       

      The Gi interfaces enabled under multicast-routing are CE-facing VRF interfaces. IPv4 MVPN AF is also enabled on both ends.

       

      The P2MP TE tunnel is configured and up:

       

      RP/0/0/CPU0:R6#sh mpls tr tu br

      Mon Jul 29 19:09:16.567 UTC

       

                           TUNNEL NAME         DESTINATION      STATUS  STATE

                          tunnel-mte46           192.0.2.4          up  up

      Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 0) tails

      Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

       

      Here's what I observe on the head-end when the source (the attached CE) is pinging the group from 172.16.126.12:

       

      RP/0/0/CPU0:R6#RP/0/0/CPU0:Jul 29 18:59:51.416 : netio[314]:  MFIB-ingress : TID 0xe0000011 Pkt (172.16.126.12, 232.1.2.3) matched (*,232.0.0.0/8) incoming Gi0/0/0/1 dropped [Destined to non-routable group]

       

      IGMP looks fine:

       

      RP/0/0/CPU0:R6#sh igmp vrf CUST gr

      Mon Jul 29 19:02:01.447 UTC

      IGMP Connected Group Membership

      Group Address   Interface                     Uptime    Expires   Last Reporter

      232.1.2.3       tunnel-mte46                  00:27:54  never     192.0.2.6

       

      And so does PIM:

       

      RP/0/0/CPU0:R6#sh pim vrf CUST int

      Mon Jul 29 19:03:28.661 UTC

       

      PIM interfaces in VRF CUST

      Address               Interface                     PIM  Nbr   Hello  DR    DR

                                                               Count Intvl  Prior

       

      192.0.2.6             tunnel-mte46                  on   1     30     1     this system

      172.16.126.6          GigabitEthernet0/0/0/1        on   2     30     1     this system


      RP/0/0/CPU0:R6#sh pim vrf CUST nei

      Mon Jul 29 19:04:34.107 UTC

       

      PIM neighbors in VRF CUST

      Flag: B - Bidir capable, P - Proxy capable, DR - Designated Router,

            E - ECMP Redirect capable

            * indicates the neighbor created for this router

       

      Neighbor Address             Interface              Uptime    Expires  DR pri   Flags

       

      172.16.126.6*                GigabitEthernet0/0/0/1 00:32:51  00:01:43 1 (DR) B E

      172.16.126.12                GigabitEthernet0/0/0/1 00:32:49  00:01:22 0      P

      192.0.2.6*                   tunnel-mte46           00:30:27  00:01:21 1 (DR) B E

       

      But the multicast tree for 232.1.2.3 is not built:

       

      RP/0/0/CPU0:R6#sh pim vrf CUST to 232.1.2.3

      Mon Jul 29 19:08:23.701 UTC

      No PIM topology table entries found.


      The tail-end sees the head-end in BGP:

       

      RP/0/0/CPU0:R4#sh bgp ipv4 mvpn


      Route Distinguisher: 100:4 (default for vrf CUST)

      *>i[1][192.0.2.6]/40  192.0.2.6                     100      0 i

      Route Distinguisher: 100:6

      *>i[1][192.0.2.6]/40  192.0.2.6                     100      0 i

       

      but not vice versa:

       

      RP/0/0/CPU0:R6#sh bgp ipv4 mvpn

       

      Route Distinguisher: 100:6 (default for vrf CUST)

      *> [1][192.0.2.6]/40  0.0.0.0                                0 i

       

      I'm not sure if this is the expected behaviour.


      The RPF is fine on the tail-end:

       

      RP/0/0/CPU0:R4#sh pim vrf CUST rpf 172.16.126.12

      Mon Jul 29 19:26:51.298 UTC

       

      Table: IPv4-Unicast-default

      * 172.16.126.12/32 [200/0]

          via MPLS  with rpf neighbor 192.0.2.6

          Connector: 100:6:192.0.2.6, Nexthop: 192.0.2.6

       

       

      Anything I'm missing?

       

      Thanks in advance!