RE: Multicast Helper address - broadcast to multicast

From: Jongsoo.Kim@Intelsat.com
Date: Fri Mar 18 2005 - 10:00:24 GMT-3


Let me lab for you as this maybe a good 2 point question in mcast topic.
 
 

-----Original Message-----
From: gladston@br.ibm.com [mailto:gladston@br.ibm.com]
Sent: Friday, March 18, 2005 7:27 AM
To: Kim, Jongsoo; ccielab@groupstudy.com
Subject: RE: Multicast Helper address - broadcast to multicast

Sorry the confusion, it is because I tried first using the sender connected
to R9's f0/0.39 (12.2.1d IOS version). As it did not work I moved the
sender to R7's e1 (R7 runs 12.2T).

================================
quoted
f0/0.39 of R9 needs to convert multicast to broadcast.
R9
interface FastEthernet0/0.39
ip multicast helper-map 239.1.1.1 178.21.34.255 181
================================
  
I must say I thought it was that way too. Cisco Doc Univercd does not do a
good job on this topic.
Williamson says it is a common mistake and we should use the command to
convert back to broadcast (ip multicast helper-map 239.1.1.1 178.21.34.255
181) on the input interface of the remote router, not the interface where
the receiver is located.

But anyway, it is not working.

Cordially,
------------------------------------------------------------------
Alaerte Gladston Vidali
IBM Global Services - SO
Tel.55+11+2121-2879 Fax:55+11+2121-2449

Jongsoo.Kim@Intelsat.com

17/03/2005 19:22

To
Alaerte Gladston Vidali/Brazil/IBM@IBMBR, ccielab@groupstudy.com

cc

Subject
RE: Multicast Helper address - broadcast to multicast

        

My understanding of topology below email is
Bcast source --e1 R7 e0---f0/0.79 R9 f0/0.39---Bcast receiver.

Then, with an assumption that multicasting is working
the below is what I am thinking

e1 of R7 needs to convert broadcast to multicast and
R7
interface Ethernet0
ip multicast helper-map broadcast 239.1.1.1 181

f0/0.39 of R9 needs to convert multicast to broadcast.
R9
interface FastEthernet0/0.39
ip multicast helper-map 239.1.1.1 178.21.34.255 181

Regards

Jongsoo

-----Original Message-----
From: gladston@br.ibm.com [mailto:gladston@br.ibm.com]
Sent: Thursday, 17 March, 2005 1:53 PM
To: ccielab@groupstudy.com
Subject: Multicast Helper address - broadcast to multicast

Have you ever get multicast helper work?

I am using the config from Williamson book without success. I used version
12.2(15)T9 and 12.1.17.

The broadcast source is connected to R7's eth 1.
The broadcast receiver is connected to R9's fasth0/0.39
R7 eth0 connects to R9 fa0/0.79

I am generating UDP broadcast with Hping2. R7 receives it but does not
convert to multicast.

R7
ip multicast-routing
!
interface Ethernet0
ip address 172.16.79.7 255.255.255.0
ip pim sparse-dense-mode
ip multicast helper-map 239.1.1.1 172.16.78.255 181
no ip route-cache
no ip mroute-cache
!
interface Ethernet1
ip address 172.16.78.7 255.255.255.0
ip directed-broadcast
ip multicast helper-map broadcast 239.1.1.1 181
!
ip forward-protocol udp 2000
!
access-list 181 permit udp any any eq 2000

R9
ip multicast-routing
!
interface FastEthernet0/0.79
encapsulation isl 79
ip address 172.16.79.9 255.255.255.0
ip pim sparse-dense-mode
ip igmp join-group 239.1.1.1
ip multicast helper-map 239.1.1.1 172.16.39.255 181
!
interface FastEthernet0/0.39
encapsulation isl 39
ip address 172.16.39.9 255.255.255.0
ip directed-broadcast
!
ip forward-protocol udp 2000
!
access-list 181 permit udp any any eq 2000

r7#deb ip pac det
IP packet debugging is on (detailed)
r7#
*Jun 9 02:38:27.015: IP: s=172.16.78.100 (Ethernet1), d=172.16.78.255
(Ethernet1), len 2
8, rcvd 3
*Jun 9 02:38:27.019: UDP src=2571, dst=2000
*Jun 9 02:38:27.811: IP: s=172.16.79.7 (local), d=224.0.0.13 (Ethernet0),
len 54, sendin
g broad/multicast, proto=103
*Jun 9 02:38:28.015: IP: s=172.16.78.100 (Ethernet1), d=172.16.78.255
(Ethernet1), len 2
8, rcvd 3
*Jun 9 02:38:28.019: UDP src=2572, dst=2000

r7#no deb all
All possible debugging has been turned off
r7#sh 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
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.1.1.1), 03:50:05/00:02:39, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial0, Forward/Sparse-Dense, 03:50:05/00:00:00
Ethernet0, Forward/Sparse-Dense, 03:50:05/00:00:00



This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:47 GMT-3