From: Daniel Kutchin (daniel@kutchin.com)
Date: Mon Feb 09 2009 - 20:54:06 ARST
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