From: Petr Lapukhov (petr@internetworkexpert.com)
Date: Tue Nov 21 2006 - 09:30:31 ART
Dave, here are some "good" debugging outputs (like Brian mentioned,
turn off all route caching both mroute and route):
"Source router R3"
Rack1R3(config)#access-list 100 permit udp any any eq 5575
Rack1R3(config)#exit
Rack1R3#debug ip packet 100
IP packet debugging is on for access list 100
Rack1R3#debug ip mpacket
IP: tableid=0, s=129.1.3.130 (Ethernet0/1), d=129.1.3.255 (Ethernet0/1),
routed via RIB
IP(0): s=129.1.3.130 (Ethernet0/1) d=233.33.33.33 (Serial1/2) id=0, ttl=254,
prot=17, len=44(44), mforward
IP: tableid=0, s=129.1.3.130 (Ethernet0/1), d=129.1.3.255 (Ethernet0/1),
routed via RIB
IP(0): s=129.1.3.130 (Ethernet0/1) d=233.33.33.33 (Serial1/2) id=0, ttl=254,
prot=17, len=44(44), mforward
Rack1R3#show ip mroute
IP Multicast Routing Table
.....
(*, 233.33.33.33), 00:15:56/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Serial1/2, Forward/Dense, 00:15:56/00:00:00
(129.1.3.130, 233.33.33.33), 00:15:56/00:02:58, flags: T
Incoming interface: Ethernet0/1, RPF nbr 0.0.0.0
Outgoing interface list:
Serial1/2, Forward/Dense, 00:15:56/00:00:00
"Receiving router R1"
Rack1R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
Rack1R1(config)#access-list 100 permit udp any any eq 5575
Rack1R1(config)#exit
Rack1R1#debug ip packet 100
IP packet debugging is on for access list 100
Rack1R1#debug ip mpacket
IP multicast packets debugging is on
Rack1R1#
*Mar 1 02:22:43.107: IP(0): s=129.1.3.130 (Serial0/1)
d=233.33.33.33(FastEthernet0/0) id=0, prot=17, len=44(44), mforward
*Mar 1 02:22:44.111: IP: tableid=0, s=129.1.3.130 (Serial0/1), d=
129.1.17.255 (FastEthernet0/0), routed via RIB
*Mar 1 02:22:44.115: IP(0): s=129.1.3.130 (Serial0/1)
d=233.33.33.33(FastEthernet0/0) id=0, prot=17, len=44(44), mforward
*Mar 1 02:22:45.111: IP: tableid=0, s=129.1.3.130 (Serial0/1), d=
129.1.17.255 (FastEthernet0/0), routed via RIB
Rack1R1#show ip mroute
......
(*, 233.33.33.33), 00:27:52/stopped, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:10:09/00:00:00
Serial0/1, Forward/Dense, 00:27:52/00:00:00
(129.1.3.130, 233.33.33.33), 00:16:48/00:02:59, flags: LT
Incoming interface: Serial0/1, RPF nbr 129.1.13.3, Mroute
Outgoing interface list:
FastEthernet0/0, Forward/Dense, 00:10:09/00:00:00
2006/11/21, Schulz, Dave <DSchulz@dpsciences.com>:
>
> Hi Petr -
>
>
>
> I tried what you mentioned and I did not get the info until I used the
> deb ip pack detail. However, the response was not what I expected.....
>
>
>
> *Mar 14 23:21:30.413: IP: s=45.1.1.4 (FastEthernet0/0),
> d=255.255.255.255, len 80, rcvd 2
>
> *Mar 14 23:21:30.413: UDP src=5000, dst=1967
>
>
>
> I am not see the conversion.
>
>
>
> I also check the basics and made sure that I did not have any RPF
> failures and can ping the group at the other end. R5 is doing the B>M.
> R1 is doing the M>B. At R5.....229.9.9.9 is the group being used for
> conversion.
>
>
>
> IP Multicast Statistics
>
> 6 routes using 3688 bytes of memory
>
> 3 groups, 1.00 average sources per group
>
> Forwarding Counts: Pkt Count/Pkts(neg(-) = Drops) per second/Avg Pkt
> Size/Kilobits per second
>
> Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
>
>
>
> Group: 229.9.9.9, Source count: 2, Packets forwarded: 2, Packets
> received: 2
>
> Source: 1.1.1.1/32, Forwarding: 1/0/100/0, Other: 1/0/0
>
> Source: 172.16.1.1/32, Forwarding: 1/0/100/0, Other: 1/0/0
>
>
>
> Group: 225.5.5.5, Source count: 0, Packets forwarded: 0, Packets
> received: 0
>
>
>
> Group: 224.0.1.40, Source count: 1, Packets forwarded: 396, Packets
> received: 493
>
> Source: 1.1.1.1/32, Forwarding: 396/0/54/0, Other: 493/0/97
>
> R5#ping 229.9.9.9
>
>
>
> Type escape sequence to abort.
>
> Sending 1, 100-byte ICMP Echos to 229.9.9.9, timeout is 2 seconds:
>
>
>
> Reply to request 0 from 172.16.1.1, 96 ms
>
> Dave Schulz,
>
> Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com%20>
>
>
>
> ________________________________
>
> From: petrsoft@gmail.com [mailto:petrsoft@gmail.com] On Behalf Of Petr
> Lapukhov
> Sent: Tuesday, November 21, 2006 1:44 AM
> To: Schulz, Dave
> Cc: ccielab@groupstudy.com
> Subject: Re: Multicast Helper Verification
>
>
>
> Dave,
>
> you may try to enable "debug ip mpacket" and "debug ip packet detail"
> on the
> router that does the "M->B" conversion (as well as on the end router
> that
> converts "B->M"). For "debug ip packet" it's better to specify
> access-list , e.g.
>
> conf t
> access-list 100 permit udp any any eq 5000
> end
> debug ip packet detail 100
>
> Also, don't forget to configure the "receiving" side to actually receive
> multicast,
> e.g. with "ip igmp static-group".
>
> HTH
>
> 2006/11/21, Schulz, Dave <DSchulz@dpsciences.com>:
>
> I am looking to do the verification for the multicast helper
> configuration. I believe the best way, is to set up the RTR application
> using udpEcho on a router on the interface, then.... Using the debug on
> the router to verify the broadcast to multicast conversion. However,
> the debugs for ip mpacket do not provide the info. Has anyone been able
> to do this successfully?
>
>
> Dave Schulz,
>
> Email: dschulz@dpsciences.com <mailto: dschulz@dpsciences.com >
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
> --
> Petr Lapukhov, CCIE #16379
> petr@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987
> Outside US: 775-826-4344
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
-- Petr Lapukhov, CCIE #16379 petr@internetworkexpert.comInternetwork Expert, Inc. http://www.InternetworkExpert.com Toll Free: 877-224-8987 Outside US: 775-826-4344
This archive was generated by hypermail 2.1.4 : Fri Dec 01 2006 - 08:05:48 ART