I am trying to do some test of multicast in local network. The scenario I am trying to test is as follows:
1. Server 1 is the source of multicast traffic and it sends multicast to group 220.127.116.11. Server 2 is on the same VLAN and is able to receive multicast from group 18.104.22.168. Both Server 1 and Server 2 use iperf for the test.
2. Then I configured port mirroring on powerconnect 6248 switch. The source port is configured as the port Server 2 is connected, and destination port (which is on another VLAN) is the port another server (Server 3) is connected.
3. I am expecting to receive the same multicast on Server 3. However, I cannot receive any multicast either using iperf or tcpdump.
No multicast routing protocol configured. No igmp snooping enabled.
Any help is appreciated.
It is possible the multicast packets are timing out. It looks like you would apply this to the VLAN interface where the multicast is entering the switch. ie .. the VLAN that Server 1 is on.
ip multicast ttl-threshold
Use the ip multicast ttl-threshold command in Interface Configuration mode to apply a ttlvalue to a routing interface. ttlvalue is the TTL threshold which is applied to the multicast Data packets forwarded through the interface.
The following example applies a ttlvalue of 5 to the VLAN 15 routing interface.
console(config)#interface vlan 15
console(config-if-vlan15)#ip multicast ttl-threshold 5
Do you still have configuration for a VLAN on the destination mirror port?
Can you provide the output of this command for the destination mirror port that is connected to Server 3?
console#show interfaces detail ethernet x/x
Thanks for the reply.
I tried the multicast ttl-threshold - set to 5, however, it didn't help. I still got no multicast on the mirror destination. Here is the output:
console#show interfaces detail ethernet 1/g36
Port Type Duplex Speed Neg Admin Link
----- ------------------------------ ------ ------- ---- ----- -----
1/g36 Gigabit - Level Full 1000 Auto Up Up
Thanks again for your help.
Somtimes there is another TTL/hop count in the application itself. When routing between vlans I had to increase this for it to work on another VLAN. I used a rather larger number like 16 and it worked. Don't know if your app has this setting, but I did see one when I setup VLC media player.
Another thing you should probably look at is using diffserv to do this.
Barrett, thanks for the reply. It should not be TTL in the application, since I can receive multicast on the mirror source interface. The problem is even I see multicast on the mirror source, I don't see it on mirror destination.
Barrett may have a pretty good point. If it gets to the source port then not to the destination. Something is not keeping it alive, blocking or incorrect configuration.
Thanks. However, I did set application TTL to 16, and still cannot make it work. I am using iperf for the test. The command for the multicast source:
iperf -c 22.214.171.124 -u -T 16 -t 100 -i 1
where -T 16 should set the TTL to 16. And I even cannot see any udp traffic been mirrored to the mirror destination, by using "tcpdump udp -i ethx". (ethx is the interface connects to the mirror destination interface)
Any other possible problems? Thanks.
hmmm. I am not too familiar with iperf, but from what I've read it seems the source (server) has the -s switch whereas the client has the -c switch. I also read that the source must bind the multicast address using the -B switch. So here is one example:
Source: iperf -s -u -B 126.96.36.199 (and of cource the TTL would go here)
Client: iperf -c -188.8.131.52 -u
Actually, it is the other way around. The client is the one sends out the multicast packets and sets the TTL, where the server just listens to the multicast group (binding to the multicast group address).
Can you suggest other tool for testing? I can give it a try. Thanks for your help.