cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
750
Views
0
Helpful
1
Replies
Carlos A. Silva
Beginner

[mvpn ME3800/ASR9k]

Hi,

I have an environment where you have a ME3800 and an ASR9000 as PEs for mVPN.

Within the VPN the control and data plane for ipv4 works just fine. That is I can ping from a loopback on ME3800 to the 9000 (both on a VRF).

regarding the core and mVPN i'm using SSM/MDT and the control plane seems to be happy. even the tunnel interface is up on the ME3800 for traffic within the mVPN. within the mVPN i'm using BSR (ASR9k=RP and ME3800 knows about it).

I have a loopback on ME3800 which i can multicast-ping, via an igmp join. I have the same setup on the ASR, but i cannot simulate to the join on the loopback no the ASR from either the ME3800 nor the ASR.

3800_sw_pruebas#show ip pim vrf mcast rp mapp

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

  RP 10.10.10.2 (?), v2 <---So, Control plane within mVPN works.

    Info source: 10.10.10.2 (?), via bootstrap, priority 192, holdtime 150

         Uptime: 00:10:47, expires: 00:01:38

3800_sw_pruebas#ping vrf mcast 225.0.0.1    

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 225.0.0.1, timeout is 2 seconds:

Reply to request 0 from 10.10.10.1, 1 ms

3800_sw_pruebas#ping vrf mcast 225.0.0.2    

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 225.0.0.2, timeout is 2 seconds:

.     <----multicast ping towards loopback on ASR9k.

3800_sw_pruebas#show run int loo1000

Building configuration...

Current configuration : 141 bytes

!

interface Loopback1000

! interface local to the ME3800

vrf forwarding mcast

ip address 10.10.10.1 255.255.255.255

ip pim sparse-mode

ip igmp join-group 225.0.0.1

end

3800_sw_pruebas#ping vrf mcast 10.10.10.2

!ipv4 ping towards loopback on ASR9k

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.10.10.2, timeout is 2 seconds:

!!!!!

Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms

3800_sw_pruebas#

Now on the ASR9k:

RP/0/RSP0/CPU0:ASR_TEST#show run int loo1000

Thu Jun 20 17:53:02.583 CST

interface Loopback1000

vrf mcast

ipv4 address 10.10.10.2 255.255.255.255

!

RP/0/RSP0/CPU0:ASR_TEST#show run router igmp

Thu Jun 20 17:53:55.838 CST

router igmp

vrf mcast

  interface Loopback1000

   join-group 224.1.1.1

   join-group 225.0.0.2

  !

!

!

RP/0/RSP0/CPU0:ASR_TEST#

RP/0/RSP0/CPU0:ASR_TEST#show run multicast-routing

Thu Jun 20 17:53:05.609 CST

multicast-routing

address-family ipv4

  mdt source Loopback0

  interface all enable

!

vrf mcast

  address-family ipv4

   mdt data 232.232.2.0/24

   mdt default ipv4 232.232.0.1

   interface all enable

  !

!

!

RP/0/RSP0/CPU0:ASR_TEST#show mrib vrf mcast route

Thu Jun 20 17:53:28.364 CST

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, MA - MDT Address, ME - MDT Encap,

    MD - MDT Decap, MT - MDT Threshold Crossed, MH - MDT interface handle

    CD - Conditional Decap, MPLS - MPLS Decap, MF - MPLS Encap, EX - Extranet

    MoFE - MoFRR Enabled, MoFS - MoFRR State

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

(*,224.0.0.0/4) RPF nbr: 10.10.10.2 Flags: L C

  Up: 05:45:42

  Outgoing Interface List

    Un:0x8000220 Flags: NS DI, Up: 05:45:42

    Decapstunnel3 Flags: NS DI, Up: 02:49:45

(*,224.0.0.0/24) Flags: D

  Up: 05:52:30

(*,224.0.1.39) Flags: S

  Up: 05:52:30

(*,224.0.1.40) Flags: S

  Up: 05:52:30

(*,224.1.1.1) RPF nbr: 10.10.10.2 Flags: C

  Up: 01:22:42

  Incoming Interface List

    Decapstunnel3 Flags: A NS, Up: 01:22:42

  Outgoing Interface List

    Loopback1000 Flags: F IC NS II LI, Up: 01:22:42

(*,225.0.0.1) RPF nbr: 10.10.10.2 Flags: C

  Up: 00:15:30

  Incoming Interface List

    Decapstunnel3 Flags: A, Up: 00:15:30

  Outgoing Interface List

    mdtmcast Flags: F NS MI, Up: 00:15:30

(*,225.0.0.2) RPF nbr: 10.10.10.2 Flags: C

  Up: 02:51:00

  Incoming Interface List

    Decapstunnel3 Flags: A NS, Up: 02:49:45

  Outgoing Interface List

    Loopback1000 Flags: F IC NS II LI, Up: 02:51:00

(10.10.10.1,225.0.0.2) RPF nbr: 10.10.10.2 Flags: L

  Up: 00:06:45

  Incoming Interface List

    Decapstunnel3 Flags: A, Up: 00:06:45

  Outgoing Interface List

    mdtmcast Flags: NS MI, Up: 00:06:45

    Loopback1000 Flags: F IC NS, Up: 00:06:45

(*,232.0.0.0/8) Flags: D

  Up: 05:52:30

RP/0/RSP0/CPU0:ASR_TEST#

now, AFAICT,control plane i correct, so I tried the ASR9k which is the BSR and RP within the vrf and when pinging the local multicast group (225.0.0.2) from the ASR9k I get:

RP/0/RSP0/CPU0:ASR_TEST#ping vrf mcast 225.0.0.2

Thu Jun 20 17:56:08.714 CST

Mdef cons get failed for VRF 0x60000001 - No such process

RP/0/RSP0/CPU0:ASR_TEST#

Basically my only question is: has anybody seen this error message? The most basic test for me would be to join a group in my own RP and try to ping it locally on the VRF, but this doesn't work. Any ideas?

TIA,

c.

1 REPLY 1
Bryan Garland
Cisco Employee

Carlos,

When doing a ping in XR to a mcast address be sure to specify a source address.  For example:

ping vrf mcast 225.0.0.2 source loopback1000

Thanks,

Bryan

Content for Community-Ad

This widget could not be displayed.