From: NET HE (he_net@hotmail.com)
Date: Tue Feb 10 2009 - 00:44:33 ARST
Hobbs,
I tried your scenario using udp-echo, and on R1, debug ip packet details
showed "encapsulation for destination 192.168.12.255 failed". Then I changed
it to icmp-echo, the same result as udp-echo. Then I pinged 192.168.12.255, it
send d=255.255.255.255 out.
But I remember I have used RIP version 1 to simulate broadcast and it was
successful. So I tried again, it's successful. It seems IP SLA doesn't support
to convert subnet broadcast to hardware broadcast.
If you have any problems using RIP to simulate it, give me a shout.Best
Regards, Net (Xin) He > Date: Mon, 9 Feb 2009 16:54:50 -0700> Subject: Re:
Testing Multicast Helper-Map with IP SLA> From: deadheadblues@gmail.com> To:
daniel@kutchin.com> CC: ccielab@groupstudy.com> > Got that on both:> > R1#sho
run int s1/0> Building configuration...> > Current configuration : 215 bytes>
!> interface Serial1/0> ip address 192.168.12.1 255.255.255.0> ip
broadcast-address 192.168.12.255> ip directed-broadcast> ip ospf cost 1> ip
ospf 1 area 0> end> > R2#sho run int s1/1> Building configuration...> >
Current configuration : 283 bytes> !> interface Serial1/1> ip address
192.168.12.2 255.255.255.0> ip broadcast-address 192.168.12.255> ip
directed-broadcast> ip pim dense-mode> ip multicast helper-map broadcast
239.0.0.1 100> ip ospf cost 1> ip ospf 1 area 0> end> > R2#sho run | inc
access> access-list 100 permit udp any host 192.168.12.255 eq 4000> R2#> >
R3#sho ip mroute 239.0.0.1> Group 239.0.0.1 not found> R3#> > Still no
luck...I have tried so many different things now I am at a> loss. The DocCD
example is very simple and concise.> > On Mon, Feb 9, 2009 at 4:43 PM, Daniel
Kutchin <daniel@kutchin.com> wrote:> > On the interfaces b/w R1 and R2 (i.e.
R2 as well) add:> >> > ip broadcast-address 192.168.12.255> > ip
directed-broadcast> >> >> > -> > Daniel> >> >> > -----Original Message-----> >
From: Hobbs [mailto:deadheadblues@gmail.com]> > Sent: Dienstag, 10. Februar
2009 00:28> > To: Daniel Kutchin> > Cc: Cisco certification> > Subject: Re:
Testing Multicast Helper-Map with IP SLA> >> > Thank you Daniel,> >> > IP SLA
does not allow 255.255.255.255 on the IOS I have. I think it> > was allowed on
older codes that had the rtr commands (I read an> > example from an IE blog
that used the all 1's address). I originally> > had tried 192.168.12.255 and
it did not work so that is why I changed> > it to 192.168.45.255. I have gone
back to 12.255 now...> >> > I get hits on my ACL:> >> > R2#show access-lists>
> Extended IP access list 100> > 10 permit udp any host 192.168.12.255 eq 4000
(72 matches)> >> > But the conversion is not happening, I don't show anything
for group> > 239.0.0.1 in the mroute table and none of the packets get past R2
now.> > I have verified that R2, R3, and R4 are PIM neighbors.> >> > Has
anyone done a scenario like this?> >> >> > thanks,> >> >> >> >> > On Mon, Feb
9, 2009 at 3:54 PM, Daniel Kutchin <daniel@kutchin.com> wrote:> >> First error
that I spotted,> >>> >>> R1 has the following IP SLA config:> >>>> >>> ip sla
monitor 1> >>> type udpEcho dest-ipaddr 192.168.45.255 dest-port 4000 control
disable> >> ^^> >> Should be:> >> type udpEcho dest-ipaddr 192.168.12.255
dest-port 4000 control disable> >> ^^> >>> >> Then on R1, the interface
linking R1 and R2, add> >> int S0/0> >> desc #- Link R1->R2 --> >> ip
broadcast-address 192.168.12.255> >> ip directed-broadcast> >>> >> or> >>> >>
You could simply use on R1> >>> >> type udpEcho dest-ipaddr 255.255.255.255
dest-port 4000 control disable> >>> >> and> >>> >> ip directed-broadcast> >>>
>>> >>> >> ---> >>> >> Daniel> >>> >>> >>> >> -----Original Message-----> >>
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of> >>
Hobbs> >> Sent: Montag, 9. Februar 2009 23:09> >> To: Cisco certification> >>
Subject: Testing Multicast Helper-Map with IP SLA> >>> >> Hello,> >>> >> I am
trying to get multicast helper-map to work (using SLA for> >> testing) but
having issues. My first hope router is not converting> >> broadcast to
multicast.> >>> >> Topology:> >>> >> R1---R2---R3---R4---R5> >>> >> R1-R2:
192.168.12.0/24> >> R2-R3: 192.168.23.0/24> >> R3-R4: 192.168.34.0/24> >>
R4-R5: 192.168.45.0/24> >>> >> IP Multicast-routing is enabled.> >> PIM-DM on
all interfaces of R2,R3 and R4.> >> All Routes are known via OSPF.> >>> >> R1
has the following IP SLA config:> >>> >> ip sla monitor 1> >> type udpEcho
dest-ipaddr 192.168.45.255 dest-port 4000 control disable> >> frequency 5> >>
ip sla monitor schedule 1 life forever start-time now> >>> >> R2 has the
"First Hop" helper config:> >>> >> ip forward-protocol udp 4000> >>
access-list 100 permit udp host 192.168.12.1 host 192.168.45.255 eq 4000> >>
interface Serial1/1> >> ip address 192.168.12.2 255.255.255.0> >> ip pim
dense-mode> >> ip multicast helper-map broadcast 239.0.0.1 100> >>> >> R4 has
the "Last Hop" help config:> >>> >> ip forward-protocol udp 4000> >>
access-list 100 permit udp host 192.168.12.1 any eq 4000> >> interface
Serial1/1> >> description to R3> >> ip address 192.168.34.4 255.255.255.0> >>
ip pim dense-mode> >> ip multicast helper-map 239.0.0.1 192.168.45.255 100>
>>> >> interface Serial1/0> >> description to R5> >> ip address 192.168.45.4
255.255.255.0> >> ip directed-broadcast> >>> >> R5 has ip sla monitor
responder> >>> >> I am capturing packets and when R4 gets the packets from R3,
they> >> still have the destination of 192.168.45.255, which means the
problem> >> is on R2.> >>> >> In fact, if I debug ip packet on R2 I see this:>
>>> >> *Mar 7 00:05:32.840: IP: s=192.168.12.1 (Serial1/1), d=192.168.45.255>
>> (Serial1/0), g=192.168.23.3, len 44, forward> >> *Mar 7 00:05:32.844: UDP
src=50398, dst=4000> >>> >> But the ACL shows no hits:> >>> >> R2#sho
access-lists> >> Extended IP access list 100> >> 10 permit udp host
192.168.12.1 host 192.168.45.255 eq 4000> >>> >>> >> Can you seen any issues
with this configuration?> >>> >>> >> thank you,> >>> >>> >> Blogs and organic
groups at http://www.ccie.net> >>> >>
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:10 ARST