cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2271
Views
0
Helpful
32
Replies

Multicast VPN issue

gregwoodson
Level 1
Level 1

I've got 2 core routers peered via BGP. I have deployed a Multicast VPN between them based on the following doc:

http://www.cisco.com/en/US/tech/tk828/tech_digest09186a00801a64a3.html

I actually see the multicast routes on all of the VRF's being broadcast from router to router and throughout the entire network. However, I am not able to see Multicast traffic passing. This is a very bizarre problem. Attached is the pertinent configs for the 2 routers.

Any ideas?

32 Replies 32

lee.reade
Level 4
Level 4

Hi,

Assume you have no problems with ipv4 unicast between vpn sites?

Do you see the traffic pass through the core from PE to PE?

Does the mVPN tunnel interface come up?

Can you provide the following;

from PE

show ip pim vrf CustomerA interface

show ip mr vrf CustomerA

from CE

show ip pim interface

show ip mr

HTH

LR

Assume you have no problems with ipv4 unicast between vpn sites?

No problems- traffic flows normally

Do you see the traffic pass through the core from PE to PE?

regular traffic- yes- no problems, multicast traffic- I see the routes only- no multicast data

Does the mVPN tunnel interface come up?

Yes it does- for both VRFs

Greg,

The control plane information looks good indeed. What do you use to generate the multicast stream? Can you check what TTL value you use when you generate these streams.

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

The test program we are using has a ttl of 15. I am looking at the client that we are using as well.

The actual client and multicast server we are using for the application has a ttl of 128.

devang_etcom
Level 7
Level 7

Hi,

What Multicasting mode are you running on your VRF connected routers? as I am not able to find any rp-address configuration under your vrf configuration.

regards

Devang Patel

I mean there should be entry of "ip pim vrf customerx rp-address" if you have PIM SPARSE MODE is running for the customer end.

Devang,

It should be fine as auto-rp is configured on Core router B:

ip pim vrf CustomerA send-rp-announce Loopback2 scope 16

ip pim vrf CustomerA send-rp-discovery Loopback2 scope 16

ip pim vrf CustomerB send-rp-announce Loopback1 scope 16

ip pim vrf CustomerB send-rp-discovery Loopback1 scope 16

!

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Hi,

How are verifying that traffic is not passing?

PEA has no cust vrf PIM neighbours, so the traffic will not flow end to end.

Can you verify that?

LR

Actually, PEA has several vrf PIM neighbors on both VRFs. I have confirmed that multicast traffic flows correctly within the individual PE's, but just not over the tunnel (even though the routing information shows up). I had rebooted both routers at one point, and when that occurred, multicast traffic was flowing over the tunnel, but unicast would not traverse the bgp connection at all. We had to break the tunnel by removing the mdt default statements. Once I put those statements back in, we see what we are seeing now. When the router first rebooted we saw unicast traffic trying to traverse thru the tunnel.

Hi,

So both CE routers see PEA as the RP, via auto-rp?

show ip pim rp map

HTH

LR

Everything sees PEB (Core-2) as the RP via auto-rp- this is on both VRF's

Greg,

Could you please do a "show ip mroute count" for a specific s,g on the CE where you do have receivers. Could you also check that the RPF check is successful using "show ip rpf " on that same CE.

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

CustomerB Site#sh ip mroute 239.195.0.0 count

IP Multicast Statistics

30 routes using 16838 bytes of memory

16 groups, 0.87 average sources per group

Forwarding Counts: Pkt Count/Pkts(neg(-) = Drops) per second/Avg Pkt Size/Kilobits per second

Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)

Group: 239.195.0.0, Source count: 4, Packets forwarded: 333727, Packets received: 333733

RP-tree: Forwarding: 0/0/0/0, Other: 0/0/0

Source: 10.0.36.254/32, Forwarding: 102371/1/486/5, Other: 102377/6/0

Source: 10.0.50.254/32, Forwarding: 39902/1/458/1, Other: 39902/0/0

Source: 192.168.253.252/32, Forwarding: 160692/1/494/2, Other: 160692/0/0

Source: 192.168.253.254/32, Forwarding: 30762/1/392/3, Other: 30762/0/0

CustomerB Site#sh ip rpf 10.0.50.254

RPF information for ? (10.0.50.254)

RPF interface: Multilink1

RPF neighbor: ? (192.168.252.1)

RPF route/mask: 10.0.50.0/24

RPF type: unicast (bgp 65502)

RPF recursion count: 2

Doing distance-preferred lookups across tables

CustomerB Site#

10.0.50.254 is a server broadcasting a multicast stream for CustomerB. Its information is not making it across the Tunnel, even though the route itself is.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: