RE: Multicast-Helper MAP

I would suggest to allow all in access list or eliminate it to make sure
that everything else is OK. If it works you can narrow requirements with
access lists. This method worked for me.

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
masroor ali
Sent: 8-Oct-10 06:14
To: mohmmad imran
Cc: Cisco certification
Subject: Re: Multicast-Helper MAP

hi,

R3---F0/0.34-------R4---F0/0.14---------R1----F0/0.12-------R2

R4 and R1 is running multicast, R3 and R2 is running RIP ver 1

same happening to me, R2 is not receiving Rip updates generated by R3,
please help!!!!

configuration is given below.

R1
interface FastEthernet0/0.14
 encapsulation dot1Q 14
 ip address 10.14.14.1 255.255.255.0
 ip pim dense-mode
 ip multicast helper-map 224.1.1.1 10.12.12.255 101
ip forward-protocol udp rip
!
access-list 101 permit udp any any eq rip log

interface FastEthernet0/0.12
 encapsulation dot1Q 12
 ip address 10.12.12.1 255.255.255.0
 ip directed-broadcast
 ip pim dense-mode

R4
interface FastEthernet0/0.34
 encapsulation dot1Q 34
 ip address 10.34.34.4 255.255.255.0
 ip pim dense-mode
 ip multicast helper-map broadcast 224.1.1.1 101 ttl 4
!
access-list 101 permit udp any any eq rip log

On Thu, Oct 7, 2010 at 10:15 PM, mohmmad imran
<imran_mohmmad_at_yahoo.com>wrote:

> Hi Experts,
>
> I am trying to understand Mutlicast-helper map:-
>
> Fa0/0--R3--S0/1-----S0/0--R5--S0/1-------S0/0--R2--Fa0/0
>
> Pim is enabled on between serial interface along with R2 Fa0/0.
> R2 Fa0/0 has joined a IGMP group 224.1.1.1
> I can ping it from R3
>
>
> Host Connected to R3 Fa0/0 supports only broadcast, if I want to use UDP
> port 2000 to support receive and send multicast traffic what can we do.
>
> I tried to break it flow wise:-
>
> 1)destination as Broadcast from R3 Fa0/0 connected hosts: -
> 2)destination as multicast from R2 Fa0/0 connected hosts: -
>
> for case 1:-
> we can Convert the broadcast traffic into multicast on R3 ingress
interface
> (fa0/0) and then convert it into back to Multicast on R2 (Ingress
interface
> Se0/0).
>
> R3#
> Int fa 0/0
> ip address 192.168.3.3 255.255.255.0
> ip multicast helper-map broadcast 224.1.1.1 100
> !
> ip forward-protocol udp 2000
> access-list 100 permit udp any any eq 2000
>
> R2#
> Int se0/0
> En ppp
> Ip address 192.168.5.2 255.255.255.252
> Ip pim sparse-mode
> ip multicast helper-map 224.1.2.3 173.20.18.255 100
> !
> ip forward-protocol udp 2000
> access-list 100 permit udp any any eq 2000
>
> int fa 0/0
> ip directed-broadcast
>
> From above the config broadcast traffic send by host will be delivered to
> Host connected on R2 Fa0/0 as broadcast.
>
> I am not able to figure out what can be done to take the multicast traffic
> from R2 connected host and delivered it as broadcast to R3 connected
hosts.
>
> Please let me know if its possible, if yes how can I configure that.
>
>
> - Imran
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>

-- 
Regards,
Masroor Ali
P Please don't print this e-mail unless you really need to.
Blogs and organic groups at http://www.ccie.net