Multicast Issue - Page 2

dipak jaiswal · ‎08-05-2011

Hi,

We want to implement multicast on our network. We are going to use for online teaching purpose. I am very new at Multicast and not have much idea about it. We are not running any routing protocol in our network, only static route. The multicast server is located at One of our office and it is connected with L2 (Cisco 2960) switch, L2 switch is connected to L3 switch(Cisco 4948). L3(Cisco 4948) and Core Switch(Cisco 6509) with FWSM are connected with E-3 link with tunnel. Router 1 and Router 2 are connected with P2P ILL links which are terminated at serial interface. The Multicast Server IP is 192.168.2.131/25. The scenario of our network are mentioned below:

Multicast Server--->(L2 Switch)--->(L3 Switch)--->(Core Switch)--->(FWSM)--->(Router 1)---->(Router 2)--->(L2 Switch)--->(Multicast Client)

We have created a seprate vlan (i.e. vlan 102, interface IP is 192.168.2.129/25) for multicast at L3 switch, enable multicast routing, defined rp-address(i.e. 192.168.2.129/25), enable sparse-dense mode at multicast vlan as well as at some other vlan also for testing purpose and joined multicast group (i.e. Multicast IP is 224.3.3.5). At core switch we have also enabled multicast routing, defined rp-address (i.e. 19.268.2.129/25), enable sparse-dense mode at user vlan and inside vlan of FWSM and joined multicast group at user vlan and inside vlan. At FWSM we have enabled multicast routing, defined rp-address(192.168.2.129), doesn’t find any option to enable sparse-dense mode and joined Multicast group at inside vlan and router 1 vlan. At Router 1, we have configured the same thing. We have configured mroute at all the devices. We are able to ping from end to end. We are testing multicast by Multicast IP checker tool (provided by vendor). Multicast is working fine at L2 switch, L3 switch and Core Switch, but not from Router 1. Ping is reachable from Router 1. After doing mtrace at Router 1, the following output has come:

Router 1 (Mtrace with destination address 192.168.2.131)

mtrace 172.21.15.2 192.168.2.131 224.3.3.5

Type escape sequence to abort.

Mtrace from 172.21.254.50 to 192.168.2.131 via group 224.3.3.5

From source (?) to destination (?)

Querying full reverse path... * switching to hop-by-hop:

0 192.168.2.131

-1 * * * Timed out receiving responses

Perhaps no local router has a route for source, the receiver is not

a member of the multicast group or the multicast ttl is too low.

Router 1 (Mtrace with destination address 192.168.2.129)

mtrace 172.21.254.50 192.168.2.129 224.3.3.5

Type escape sequence to abort.

Mtrace from 172.21.254.50 to 192.168.2.129 via group 224.3.3.5

From source (?) to destination (?)

Querying full reverse path... * switching to hop-by-hop:

0 192.168.2.129

-1 * 172.31.255.250 PIM/Static Reached RP/Core [default]

-2 * 172.31.255.249 PIM/Static [172.21.254.48/29]

-2 172.21.254.50

192.168.2.129 = Multicast Server Gateway and Vlan 102 ip address

192.168.2.131 = Multicast Server IP address

172.31.255.250 = L3 Switch (Cisco 4948) Tunnel IP address

172.31.255.249 = Core Switch (Cisco 6509) Tunnel IP address

172.21.254.50 = Router 1 interface IP address

If , we do mtrace from gateway IP address(i.e. 192.168.2.129) as destination address then mtrace is getting completed, but if mtrace is done from Mutlicast server IP address(192.168.2.131) as destination address, then mtrace is not getting completed.

We have connected one laptop at Router 1 vlan to test Multicast. The host, which is connected to Router 1 vlan is able to send multicast packet to other host and other host at different vlan are receiving it , but it’s unable to receive multicast packet send by other host of different vlan.

Do I need to enable igmp snooping at L2 switch, L3 switch and Core Switch ?

I am not able to understand or can't figure out where i have configured wrong. Please help.

Thanks a lot in advance for all your help.

Regards

Dipak

dipak jaiswal · ‎08-09-2011

Hi,

Ping and Mroute result from Primary Core Switch and Router 1:

Primary Core Switch # ping

Protocol [ip]:

Target IP address: 224.3.3.5

Repeat count [1]: 5

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]:

Sweep range of sizes [n]:

Type escape sequence to abort.

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

Reply to request 0 from 172.31.255.250, 8 ms

Reply to request 1 from 172.31.255.250, 4 ms

Reply to request 2 from 172.31.255.250, 4 ms

Reply to request 3 from 172.31.255.250, 8 ms

Reply to request 4 from 172.31.255.250, 4 ms

Primary Core Switch # show ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.3.3.5), 3d18h/00:02:54, RP 192.168.2.129, flags: SJCL

Incoming interface: Tunnel3, RPF nbr 0.0.0.0, Mroute, Partial-SC

Outgoing interface list:

Tunnel0, Forward/Sparse-Dense, 02:21:17/00:02:45, H

Vlan201, Forward/Sparse-Dense, 3d18h/00:02:05, H

Note : 172.31.244.250 = tunnel IP of other end Core Switch(Cisco 4948)

Router 1:

Router 1 # ping 224.3.3.5 repeat 5

Type escape sequence to abort.

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

.....

Router 1 # show ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.3.3.5), 4d23h/00:01:33, RP 192.168.2.129, flags: SJCLF

Incoming interface: Tunnel3, RPF nbr 0.0.0.0, Mroute

Outgoing interface list:

GigabitEthernet0/1, Forward/Sparse-Dense, 02:24:35/00:01:33

Please suggest.

Thanks a lot in advance.

Regards

Dipak

Marwan ALshawi · ‎08-09-2011

hi mate

your issue looks like fixed

the ping reply coming frm the tunnel interface

so i think you need to test using you server and client/reciever

by the way try to connect the server directly to the corswitch first as sometimes HSRP has issues with mcast just do it for testing

and make sure in all of the L2 switch you have igmp snooping enabled

HTH

good luck

dipak jaiswal · ‎08-10-2011

Hi,

Multicast server is on a different geographical location. The ping reply which has come from tunnel is the other tunnel ip which is connect between Core Switch( Cisco 4948) and Primary Core Switch(Cisco 6509) via E-3 link where multicast server belongs.We have created tunnel between Primary Core Switch and Router. When we are pinging from Router 1 or Primary Core Switch, the tunnel ip (i.e. 172.31.24.2 & 172.31.24.1) is not pinging and also loopback address is not pinging. IGMP snooping is enabled on all the L2 switch. Multicast is not working between client and server.

Please suggest.

Thanks a lot in advance.

Regards

Dipak

Mohamed Sobair · ‎08-10-2011

Dipak,

Can you perform the following and let me know the result:

Ping from Primary Core Switch the IP 172.21.254.50 with the source interface vlan 100.

Are you able to ping?

Regards,

Mohamed

dipak jaiswal · ‎08-10-2011

Hi,

Yes, we are able to ping. Please go thtorugh the following ping result from Primary Core Switch:

Primary Core Switch #ping 172.21.254.50

Type escape sequence to abort.

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

!!!!!

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

Primary Core Switch#ping

Protocol [ip]:

Target IP address: 172.21.254.50

Repeat count [5]: 20

Datagram size [100]:

Timeout in seconds [2]:

Extended commands [n]: y

Source address or interface: vlan 100

Type of service [0]:

Set DF bit in IP header? [no]:

Validate reply data? [no]:

Data pattern [0xABCD]:

Loose, Strict, Record, Timestamp, Verbose[none]:

Sweep range of sizes [n]:

Type escape sequence to abort.

Sending 20, 100-byte ICMP Echos to 172.21.254.50, timeout is 2 seconds:

Packet sent with a source address of 172.21.254.18

!!!!!!!!!!!!!!!!!!!!

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

Please suggest.

Thanks a lot in advance.

Regards

Dipak

Mohamed Sobair · ‎08-10-2011

Dipak,

Please remove all your Old GRE tunnel configuation and configure a new one as follows:

Router-1:-

no interface tunnel 3

Interface Tunnel 3

IP unnumbered G0/1

Tunnel source G0/1

Tunnel destination 172.21.254.18

IP pim Sparse-dense-mode

Interface Gigaethernet0/1

IP pim sparse-dense modes

IP mroute 0.0.0.0 0.0.0.0 Tunnel 3

Primary Core Switch 1:-

No Interface Tunnel 3

Interface Tunnel 3

IP unnumbered vlan 100

Tunnel Source Vlan 100

Tunnel destination 172.21.254.50

IP pim sparse-dense-mode

IP mroute 0.0.0.0 0.0.0.0 Tunnel 3

Please now check the GRE Tunnel Status if its UP, and then do your multicast Test by pinging the mentioned group from Core-Switch 1 and Router 1 and post the result here.

Regards,

Mohamed

Mohamed Sobair · ‎08-10-2011

Dipak,

Could you please let us know if its working with you now or not.

Regards,

Mohamed

dipak jaiswal · ‎08-10-2011

Hi,

As suggested by you, i have configured the same thing. The scenario has changed after configuring, but multicast is still not working. Please go through the following output after configuring the same as suggested by you.

Router 1:

Router 1#ping 224.3.3.5

Type escape sequence to abort.

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

Reply to request 0 from 172.21.254.50, 1 ms

Reply to request 0 from 172.31.255.250, 4 ms

Reply to request 0 from 172.21.254.18, 1 ms

Router 1#show ip pim neighbor

PIM Neighbor Table

Neighbor Interface Uptime/Expires Ver DR

Address Prio/Mode

172.21.254.49 GigabitEthernet0/1 4d18h/00:01:37 v2 1 /

172.21.254.18 Tunnel3 00:51:08/00:01:15 v2 1 / S

Router 1#show ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 224.3.3.5), 5d23h/00:03:05, RP 192.168.2.129, flags: SJCLF

Incoming interface: Tunnel3, RPF nbr 172.21.254.18, Mroute

Outgoing interface list:

GigabitEthernet0/1, Forward/Sparse-Dense, 00:51:10/00:01:20

(172.21.15.12, 224.3.3.5), 00:32:46/00:02:59, flags: LJT

Incoming interface: Tunnel3, RPF nbr 172.21.254.18, Mroute

Outgoing interface list:

GigabitEthernet0/1, Forward/Sparse-Dense, 00:32:46/00:01:20

(172.21.254.50, 224.3.3.5), 00:00:41/00:02:49, flags: LFT

Incoming interface: GigabitEthernet0/1, RPF nbr 0.0.0.0

Outgoing interface list:

Tunnel3, Forward/Sparse-Dense, 00:00:41/00:03:05

(172.21.254.53, 224.3.3.5), 00:33:38/00:03:29, flags: LFT

Incoming interface: GigabitEthernet0/1, RPF nbr 0.0.0.0

Outgoing interface list:

Tunnel3, Forward/Sparse-Dense, 00:32:46/00:03:05

(192.168.2.132, 224.3.3.5), 00:00:24/00:03:05, flags:

Incoming interface: Tunnel3, RPF nbr 172.21.254.18, Mroute

Outgoing interface list:

GigabitEthernet0/1, Forward/Sparse-Dense, 00:00:24/00:02:35

(192.168.3.11, 224.3.3.5), 00:02:12/00:01:17, flags: L

Incoming interface: Tunnel3, RPF nbr 172.21.254.18, Mroute

Outgoing interface list:

GigabitEthernet0/1, Forward/Sparse-Dense, 00:02:12/00:02:34

(192.168.4.113, 224.3.3.5), 00:02:39/00:00:50, flags: L

Incoming interface: Tunnel3, RPF nbr 172.21.254.18, Mroute

Outgoing interface list:

GigabitEthernet0/1, Forward/Sparse-Dense, 00:02:39/00:02:34

Router 1#mtrace 172.21.254.50 192.168.2.131 224.3.3.5

Type escape sequence to abort.

Mtrace from 172.21.254.50 to 192.168.2.131 via group 224.3.3.5

From source (?) to destination (?)

Querying full reverse path...

0 192.168.2.131

-1 172.31.255.250 PIM Reached RP/Core [172.21.254.0/24]

-2 172.31.255.249 PIM/Static [default]

-3 172.21.254.50 PIM [172.21.254.48/29]

Primary Core Switch:

Primary Core Switch #ping 224.3.3.5

Type escape sequence to abort.

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

Reply to request 0 from 172.21.254.18, 8 ms

Reply to request 0 from 172.31.255.250, 12 ms

Reply to request 0 from 172.21.15.2, 8 ms

Reply to request 0 from 172.21.254.50, 8 ms

Primary Core Switch # show ip pim neighbor

PIM Neighbor Table

Neighbor Interface Uptime/Expires Ver DR

Address Prio/Mode

172.21.18.3 Vlan207 1w2d/00:01:25 v2 1 / DR S

172.31.255.250 Tunnel0 5d18h/00:01:26 v2 1 / S

172.21.254.17 Vlan100 4d18h/00:01:28 v2 1 /

172.21.254.19 Vlan100 6d22h/00:01:25 v2 1 / DR S

172.21.254.50 Tunnel3 00:57:44/00:01:43 v2 1 / S

Primary Core Switch #show ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

L - Local, P - Pruned, R - RP-bit set, F - Register flag,

T - SPT-bit set, J - Join SPT, M - MSDP created entry,

X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

U - URD, I - Received Source Specific Host Report,

Z - Multicast Tunnel, z - MDT-data group sender,

Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

Timers: Uptime/Expires

(*, 224.3.3.5), 4d18h/00:03:19, RP 192.168.2.129, flags: SJCLF

Incoming interface: Tunnel3, RPF nbr 172.21.254.50, Mroute, Partial-SC

Outgoing interface list:

Tunnel0, Forward/Sparse-Dense, 01:02:02/00:00:59, H

Vlan201, Forward/Sparse-Dense, 4d18h/00:02:33, H

(172.21.15.12, 224.3.3.5), 00:44:22/00:03:29, flags: LFT

Incoming interface: Vlan201, RPF nbr 0.0.0.0, Partial-SC

Outgoing interface list:

Tunnel3, Forward/Sparse-Dense, 00:37:04/00:02:50, H

Tunnel0, Forward/Sparse-Dense, 00:44:22/00:02:48, H

(172.21.254.18, 224.3.3.5), 00:02:01/00:01:29, flags: LT

Incoming interface: Vlan100, RPF nbr 0.0.0.0, Partial-SC

Outgoing interface list:

Tunnel3, Forward/Sparse-Dense, 00:02:01/00:03:26, H

Vlan201, Forward/Sparse-Dense, 00:02:01/00:02:33, H

Tunnel0, Forward/Sparse-Dense, 00:02:01/00:02:48, H

(172.21.254.53, 224.3.3.5), 00:42:42/00:03:28, flags: LT

Incoming interface: Tunnel3, RPF nbr 172.21.254.50, Mroute, Partial-SC

Outgoing interface list:

Vlan201, Forward/Sparse-Dense, 00:42:42/00:02:14, H

Tunnel0, Forward/Sparse-Dense, 00:42:42/00:03:24, H, A

(192.168.2.132, 224.3.3.5), 00:01:41/00:01:18, flags: L

Incoming interface: Tunnel3, RPF nbr 172.21.254.50, Mroute

Outgoing interface list:

Vlan201, Forward/Sparse-Dense, 00:01:41/00:02:14

Tunnel0, Forward/Sparse-Dense, 00:01:41/00:01:18

(192.168.3.11, 224.3.3.5), 00:00:05/00:02:54, flags: LJ

Incoming interface: Tunnel3, RPF nbr 172.21.254.50, Mroute

Outgoing interface list:

Vlan201, Forward/Sparse-Dense, 00:00:05/00:02:54

Tunnel0, Forward/Sparse-Dense, 00:00:05/00:02:54

Do i need to join tunnel 3 and vlan 42 to igmp group ?

I have enable igmp snooping at L2 switch.

After configuring as suggested by you, ping, mtrace, and pim neighbor relationship is working, but only mutlicast is not working.

Please suggest.

Thanks a lot in advance.

Regards

Dipak

Mohamed Sobair · ‎08-11-2011

Dipak,

Thats Good News, Now you have multicast enabled Network and your Multicast can easily be transfered withing your Network.

all the outputs indicate that every thing is working as expected.

I will now ask you, wht do you mean by multicast is still not working? where is actually your Multicast Server and where is the Reciever connected? also what software you are using for Multicast? is VLC or some other one?

while checking your real multicast traffic, please check the multicast (TTL Value) on the software as well as some comes with a TTL value of 1 which prevent multicast to travel but only one Hop a way.

Please let me know back,

Regards,

Mohamed