From: Smithson, Brandon K (brandon.k.smithson@citi.com)
Date: Fri Dec 28 2007 - 20:55:16 ART
I've seen something similar like this before. Make sure your R2 fa0/0
is up. If it is shutdown (I would imagine down also), then the router
will show the source as being from loopback 0, which does not have
multicast enabled, and hence, the pings will not work. I've seen this
exact same thing in a lab before (except there was no fa0/0 interface)
and once multicast was enabled on the loopback interface, everything
worked.
The way I rationalized it before was that the pinging router (source)
needs at least two interfaces up/up with PIM enabled. One to source the
pings (or to replicate the interface that would be receiving the source
traffic) and one interface to send it out towards the RP (for SM). I do
not believe it will work with just one interface up/up with PIM enabled.
Brandon
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Smithson, Brandon K [CCC-OT_IT]
Sent: Friday, December 28, 2007 5:17 PM
To: backbone systems; Victor Cappuccio
Cc: Cisco certification
Subject: RE: IP Multicast Question -- IP pim autorp listner
On all three routers, can you please do a show run, copy your configs
and reply with them? Interesting how on R2 your source address below is
the loopback 0 address when your original configs do not even show
multicast enabled on loopback 0. I would think the source would be
5.5.245.2, your outgoing Serial 0/0.25 interface. If you post your
configs, we can lab it up to replicate the behavior and see what's
possibly wrong.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
backbone systems
Sent: Friday, December 28, 2007 2:48 PM
To: Victor Cappuccio
Cc: Cisco certification
Subject: Re: IP Multicast Question -- IP pim autorp listner
i tried no ip mroute-cache,nbma-mode and bi-dir.nothing is working when
i do debug ip mpacket on R2 i get this which shows some kind of mistake.
R2(config-subif)#do ping 224.1.1.1 re 5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds:
*Mar 2 03:28:44.464: IP(0): s=5.5.2.2 (Loopback0) d=224.1.1.1 id=152,
ttl=254, prot=1, len=100(100), mroute olist null.
*Mar 2 03:28:46.463: IP(0): s=5.5.2.2 (Loopback0) d=224.1.1.1 id=153,
ttl=254, prot=1, len=100(100), mroute olist null.
*Mar 2 03:28:48.467: IP(0): s=5.5.2.2 (Loopback0) d=224.1.1.1 id=154,
ttl=254, prot=1, len=100(100), mroute olist null.
*Mar 2 03:28:50.466: IP(0): s=5.5.2.2 (Loopback0) d=224.1.1.1 id=155,
ttl=254, prot=1, len=100(100), mroute olist null.
*Mar 2 03:28:52.469: IP(0): s=5.5.2.2 (Loopback0) d=224.1.1.1 id=156,
ttl=254, prot=1, len=100(100), mroute olist null
any suggestions?????
BB
On Dec 28, 2007 10:20 PM, Victor Cappuccio <vcappuccio@gmail.com> wrote:
>
> Upssssss ip pim nbma missing there :) for sure that would be needed to
> pass traffic in S0/0 in R5 (like the split-horizon for multicast
> traffic), Now the stange part is that Backbone was able to ping the
> Groups Joined in
> R4
> R2#ping 224.2.2.2 re 5
>
> Type escape sequence to abort.
> Sending 5, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
>
> Reply to request 0 from 5.5.245.4, 136 ms Reply to request 0 from
> 5.5.245.4, 208 ms Reply to request 0 from 5.5.245.4, 176 ms Reply to
> request 1 from 5.5.245.4, 141 ms Reply to request 1 from 5.5.245.4,
> 157 ms...
>
> Now for his output the ip pim sparse must be issued before doing the
> R1#conf ter Enter configuration commands, one per line. End with
> CNTL/Z.
> R1(config)#int
> *Dec 28 19:56:25.083: %SYS-5-CONFIG_I: Configured from console by
> console R1(config)#int lo0 R1(config-if)#ip add 1.1.1.1 255.255.255.0
> R1(config-if)#exit R1(config)#ip pim send-rp-announce Loopback0 scope
> 16 Must first configure PIM mode on the interface: Loopback0
>
> Also I would like to copy this link
> http://groupstudy.com/archives/ccielab/200611/msg01185.html
> is from Mr Caslow on how to debug multicast routing, very nice
> document to read.
> So I would think that Backbone, was not receving an RPF Failure, we
> can see yet that the traffic that he was sourcing the traffic is now
> prunned
>
> (*, 224.2.2.2), 00:03:23/stopped, RP 5.5.5.5, flags: SP Incoming
> interface: Serial0/0.25, RPF nbr 5.5.245.5 Outgoing interface list:
> Null
>
> ( 5.5.245.5, 224.2.2.2), 00:03:23/00:00:03, flags: PT Incoming
> interface: Serial0/0.25, RPF nbr 0.0.0.0 Outgoing interface list:
> Null
>
>
> And for me that reads as an STP Problem, I need to lab this out :D
> Thanks
> Victor.-
>
>
>
> On Dec 28, 2007 7:25 PM, Smithson, Brandon K <
> brandon.k.smithson@citi.com>
> wrote:
>
> > Looks like you might be missing "ip pim nbma-mode" on the hub, and
> > also "ip pim sparse-mode" on your R5 loopback0. Also, I don't know
> > if this applies to yours, but just in the last few days someone
> > posted a similar problem and "no ip mroute-cache" fixed theirs.
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> > Of backbone systems
> > Sent: Friday, December 28, 2007 10:44 AM
> > To: Cisco certification
> > Subject: IP Multicast Question -- IP pim autorp listner
> >
> > Hi all,
> >
> > R5 is hub and R2 and R4 are spokes . i have to use ip pim autorp
> > listner
> >
> > command on all the routers. R5 loopback is the the rp .
> > The problem i am having is that when i ping from R2 to R4 igmp group
> > 224.1.1.1 i get first two replies but rest time out ?? why is this
> > happening .
> > i need real help
> >
> > Here is my config ,
> >
> > R2
> >
> > ip multicast-rou
> >
> > int fas0/0
> > ip pim sparse-mode
> >
> > int ser0/0.25
> > ip pim sparse mode
> >
> > ip pim auto-rp listner
> >
> >
> > R5
> >
> > ip multicast-rou
> >
> > int ser0/0
> > ip pim sparse-mo
> >
> > ip pim auto-rp listner
> >
> > ip pim send-rp-announce Loopback0 scope 16 group-list 10 ip pim
> > send-rp-discovery Loopback0 scope 16
> >
> > access-list 10 per 224.1.1.1
> > access-list 10 per 224.2.2.2
> >
> > R4
> >
> > ip multicast-rou
> >
> > int ser0/0
> > ip pim sparse-mo
> >
> > int fas0/0
> > ip pim sparse-mo
> > ip igmp join-g 224.1.1.1
> > ip igmp join-g 224.2.2.2
> >
> > ip pim auto-rp listner
> >
> >
> > ON R2 some outputs
> >
> > R2#sh ip mr
> > 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, z - MDT-data group sender,
> > Y - Joined MDT-data group, y - Sending to MDT-data group
> > Outgoing interface flags: H - Hardware switched, A - Assert winner
> > Timers: Uptime/Expires
> > Interface state: Interface, Next-Hop or VCD, State/Mode
> >
> > (*, 224.2.2.2), 00:03:23/stopped, RP 5.5.5.5, flags: SP Incoming
> > interface: Serial0/0.25, RPF nbr 5.5.245.5 Outgoing interface list:
> > Null
> >
> > ( 5.5.245.5, 224.2.2.2), 00:03:23/00:00:03, flags: PT Incoming
> > interface: Serial0/0.25, RPF nbr 0.0.0.0 Outgoing interface list:
> > Null
> >
> > (*, 224.0.1.39), 00:29:24/00:02:55, RP 0.0.0.0, flags: DC Incoming
> > interface: Null, RPF nbr 0.0.0.0 Outgoing interface list:
> > Serial0/0.25, Forward/Sparse, 00:29:25/00:00:00
> >
> > (*, 224.0.1.40), 00:29:33/stopped, RP 0.0.0.0, flags: DCL Incoming
> > interface: Null, RPF nbr 0.0.0.0 Outgoing interface list:
> > Serial0/0.25, Forward/Sparse, 00:29:33/00:00:00
> > FastEthernet0/0, Forward/Sparse, 00:29:33/00:00:00
> >
> > (5.5.5.5, 224.0.1.40), 00:29:24/00:02:52, flags: LT Incoming
> > interface: Serial0/0.25, RPF nbr 5.5.245.5 Outgoing interface list:
> > FastEthernet0/0, Forward/Sparse, 00:29:24/00:00:00
> >
> >
> >
> > R2#sh ip pim rp
> > Group: 224.2.2.2, RP: 5.5.5.5, v2, v1, uptime 00:02:47, expires
> > 00:02:10 R2#
> >
> > R2#sh ip pim nei
> > PIM Neighbor Table
> > Mode: B - Bidir Capable, DR - Designated Router, N - Default DR
> > Priority,
> > S - State Refresh Capable
> > Neighbor Interface Uptime/Expires Ver
DR
> > Address
> > Prio/Mode
> > 5.5.245.5 Serial0/0.25 02:32:45/00:01:33 v2 1
/
> > DR S
> > R2#
> >
> > SEE the ping timing out on R2
> >
> > R2#sh ip pim rp
> > Group: 224.2.2.2, RP: 5.5.5.5, v2, v1, uptime 00:02:47, expires
> > 00:02:10
> >
> > R2#ping 224.2.2.2 re 5
> >
> > Type escape sequence to abort.
> > Sending 5, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
> >
> > Reply to request 0 from 5.5.245.4, 136 ms Reply to request 0 from
> > 5.5.245.4, 208 ms Reply to request 0 from 5.5.245.4, 176 ms Reply to
> > request 1 from 5.5.245.4, 141 ms Reply to request 1 from 5.5.245.4,
> > 157 ms...
> >
> >
> >
> > If u need any more outputs please let me know.
> >
> > Thanks to all
> >
> > Regards
> >
> > BB
> >
> > ____________________________________________________________________
> > ___ Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
> > ____________________________________________________________________
> > ___ Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html
> >
>
>
>
> --
>
> Victor Cappuccio
> www.vcappuccio.wordpress.com
This archive was generated by hypermail 2.1.4 : Tue Jan 01 2008 - 12:04:32 ARST