Routing

Hi,

 

I am multicast routing beginner. See enclosed diagram#1 for topology.

We have stream server in our test lab with multiple streams to ex4200 on vlan6. There is also interface vlan.6  on ex4200. I want to route stream from streamer to vlan90. (via interface vlan.90) How can i do that?

 

I was able to do that with different topology. Where both ex4200s purpose was routing (see diagram #2). I only turned on pim dense mode on both ex4200 and igmp ex4200 on port directed to clients.

 

But back to diagram#1. How can I do that with topology #1?

 

I already tried this

ex4200#1

set protocols igmp interface all

(with or without: set protocols pim interface all mode dense)

 

i added also tried it with and without igmp-snooping on other switches (ex4200,ex2200). and also add multicast-routing interface statement as in link i provided

https://www.juniper.net/techpubs/en_US/junos/topics/concept/igmp-snooping-multicast-forwarding.html

 

 

Is it possible to have just three devices: streamer --- ex4200 --- receiver. What will be the configuration for ex?

 

Regards

Jozef Klacko

 

 

Hi

I believe this should be working the way you configured.
Check the following things

1) Your PIM config on EX4200 should look like

pim {
    interface all {
        mode dense;
    }
    interface me0.0 {
        disable;
    }
}

IGMP is automatically enabled on all PIM interfaces. As for IGMP-snooping,
may be its better not to enable it on switches while you are troubleshhoting
this problem, to make sure its not a problem itself.

Does "show pim interfaces" give you the correct interface list? (both vlan
interfaces should be there).

2) Do your receivers send IGMP joins to the multicast group
the server is multicasting? If not sure, you can temporarily
set a static IGMP group with a command like

lab@ex# show protocols igmp   
interface vlan.200 {
    static {
        group 224.4.4.4;
    }
}

(will be vlan.90 in your case).

3) Is your server multicasting any traffic on that group right now?
If not sure, you can use a multicast ping, for example for linux it will be

ping 224.4.4.4 -I eth1 -t 10

(note the -t option: it is the ttl which will be 1 by default (AFAIK))

4) Check out your multicast cache on EX4200:

lab@ex# run show route table inet.1

inet.1: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

224.4.4.4,192.168.1.10/32*[PIM/105] 00:10:20
                      Multicast (IPv4)

You should see the record of this kind.

Other useful commands that can be used for troubleshooting are

show multicast route

(Check "Downstream interface list")

show multicast statistics

(Check for errors such as no route)

Please tell me if you can resolve the problem now.

Hi
Thank you pk

--- The problem was only ttl set to 1. ---

I just checked it by tcpdump on stream server. I have everything else as you wrote.

Thanks again