From: Guyler, Rik (rguyler@shp-dayton.org)
Date: Thu Nov 08 2007 - 17:52:54 ART
Tarun, I have always read as well that deny statements in any ACL should
be acceptable, otherwise your ACLs may not be as accurate or logical as
you would prefer. Maybe this issue that Chris was seeing was some form
of bug or glitch?
Rik
________________________________
From: Tarun Pahuja [mailto:pahujat@gmail.com]
Sent: Thursday, November 08, 2007 3:48 PM
To: Guyler, Rik
Cc: Rich Collins; Chris Riling; Joseph Brunner; groupstudy
Subject: Re: Soup-to-Nuts: MCAST Lab 5 - Auto RP with Multiple RP's
Rik,
A Deny statement is perfectly acceptable as per CCO.
http://cisco.com/en/US/tech/tk828/technologies_tech_note09186a0080094821
.shtml#autowithmult
Thanks,
Tarun
On Nov 8, 2007 2:00 PM, Guyler, Rik <rguyler@shp-dayton.org> wrote:
Well, I'll have to agree there that I've never seen deny
statements in
the ACL. It's reasonable to think that you should be able to
put them
in there, however as sometimes you may just need to but I've
always seen
permits only.
Rik
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
Behalf Of
Rich Collins
Sent: Wednesday, November 07, 2007 6:54 PM
To: Tarun Pahuja
Cc: Chris Riling; Joseph Brunner; groupstudy
Subject: Re: Soup-to-Nuts: MCAST Lab 5 - Auto RP with Multiple
RP's
Hello,
We had a similar thread a couple of weeks ago and I made a
comment
(observation from many lab book examples) that there never
seemed to be
a deny statement in these access-lists describing the multicast
groups.
The auto-rp seems to drop that group range (see the minus (-)
sign) in the rp mapping.
I never spent the time to investigate further. I guess you
create a
list of permit statements and conveniently skip over those
groups you
don't want in....or maybe someone else in GS knows more about
this?
-Rich
ip pim send-rp-announce Loopback0 scope 5 group-list 1 interval
10 !
access-list 1 deny 224.8.8.8 <http://224.8.8.8/>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
access-list 1 permit 224.0.0.0 <http://224.0.0.0/>
15.255.255.255 <http://15.255.255.255/>
R4#sh ip pim rp mapp
PIM Group-to-RP Mappings
This system is an RP (Auto-RP)
This system is an RP-mapping agent
Group(s) 224.0.0.0/4
RP 4.4.4.4 <http://4.4.4.4/> (?), v2v1
Info source: 4.4.4.4 <http://4.4.4.4/> (?), elected via
Auto-RP
Uptime: 02:05:34, expires: 00:00:27
Group(s) (-)224.8.8.8/32 <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
On Nov 7, 2007 1:52 PM, Tarun Pahuja <pahujat@gmail.com> wrote:
> Please use appropriate mask when defining the multicast group
on
> router 1 and 4, seems like the mapping agent thinks that you
are
> trying to advertise the same multicast(group,rp) mapping from
two
> different sources and it is choosing the one with the highest
ip
address.
>
> I see you have google account, we can take this offline if you
want,
> just ping me in Google IM.
>
> HTH,
> Tarun
>
>
>
> On 11/7/07, Chris Riling <criling@gmail.com> wrote:
> >
> > It appears as though the mappings aren't working right:
> >
> > R1:
> >
> >
> > R1#sh ip pim rp mapp
> > PIM Group-to-RP Mappings
> > This system is an RP (Auto-RP)
> > This system is an RP-mapping agent
> >
> > Group(s) 224.0.0.0/4
> > RP 4.4.4.4 <http://4.4.4.4/> (?), v2v1
> > Info source: 4.4.4.4 <http://4.4.4.4/> (?), elected via
Auto-RP
> > Uptime: 01:56:30, expires: 00:00:30
> > Group(s) (-)224.8.8.8/32
> > RP 4.4.4.4 <http://4.4.4.4/> (?), v2v1
> > Info source: 4.4.4.4 <http://4.4.4.4/> (?), elected via
Auto-RP
> > Uptime: 01:56:30, expires: 00:00:29
> >
> >
> >
> > R4:
> >
> >
> > R4#sh ip pim rp mapp
> > PIM Group-to-RP Mappings
> > This system is an RP (Auto-RP)
> > This system is an RP-mapping agent
> >
> > Group(s) 224.0.0.0/4
> > RP 4.4.4.4 <http://4.4.4.4/> (?), v2v1
> > Info source: 4.4.4.4 <http://4.4.4.4/> (?), elected via
Auto-RP
> > Uptime: 02:05:34, expires: 00:00:27
> > Group(s) (-)224.8.8.8/32
> > RP 4.4.4.4 <http://4.4.4.4/> (?), v2v1
> > Info source: 4.4.4.4 <http://4.4.4.4/> (?), elected via
Auto-RP
> > Uptime: 02:05:34, expires: 00:00:27
> >
> > Shouldn't I see one for 1.1.1.1 <http://1.1.1.1/> and
another for 4.4.4.4 <http://4.4.4.4/> on each
router?
> >
> >
> >
> > On 11/7/07, Tarun Pahuja <pahujat@gmail.com> wrote:
> > >
> > > Chris,
> > >
> > > 1) Can you see all routes on all routers? Do you have end
to end
> > > connectivity?
> > > 2) You have two mapping agents in the scenario, can you
see local
> > > mappings on each of them and on the adjoining routers? How
about
> > > across the frame cloud?
> > > 3) Clear mroute table on all routers.
> > >
> > > You should be good to go!
> > > Tarun
> > >
> > >
> > > On 11/7/07, Chris Riling <criling@gmail.com> wrote:
> > > >
> > > > I fixed the RIP issue, that was my bad, but it souldn't
have /
> > > > didn't seem to have any effect on what's going on here
anyway...
> > > > the "debug ip mpacket detail" doesn't seem to say much
either...
> > > > I did it from the router that's a member of 224.8.8.8
<http://224.8.8.8/> - in the
> > > > config above it was R4, but I moved it to R3 just in
case there
> > > > was some oddity with the RP configuration, I wanted to
see what
> > > > would happen if a totally separate router was a member,
not a
router that is also an RP...
> > > >
> > > > *Jul 16 03:31:19.088: IP(0): MAC sa=000b.fd0c.cf80
> > > > (FastEthernet0/0), IP last-hop= 131.1.34.4
<http://131.1.34.4/> *Jul 16 03:31:19.088 :
> > > > IP(0): IP tos=0xC0, len=54, id=4038, ttl=3,
> > > > prot=17
> > > > *Jul 16 03:31: 19.088: IP(0): s=131.1.14.1
<http://131.1.14.1/> (FastEthernet0/0) d=
> > > > 224.0.1.40 <http://224.0.1.40/> (Serial0/0.32) id=4038,
ttl=3, prot=17, len=54(54),
> > > > mforward *Jul 16 03:31:19.918: IP(0): MAC sa=
000b.fd0c.cf80
> > > > (FastEthernet0/0), IP last-hop=131.1.34.4
<http://131.1.34.4/> *Jul 16 03:31:19.918:
> > > > IP(0): IP tos=0xC0, len=54, id=3931, ttl=4,
> > > > prot=17
> > > > *Jul 16 03:31:19.918: IP(0): s= 131.1.34.4
<http://131.1.34.4/> (FastEthernet0/0)
> > > > d=224.0.1.40(Serial0/0.32) id=3931, ttl=4, prot=17,
len=54(54),
> > > > mforward
> > > >
> > > > Thanks,
> > > > Chris
> > > >
> > > >
> > > >
> > > >
> > > > On 11/7/07, Tarun Pahuja <pahujat@gmail.com> wrote:
> > > > >
> > > > > Chris,
> > > > > Please include 131.2.0.0 <http://131.2.0.0/>
network under rip on router
> > > > > number 2. For PIM to work you want to make sure that
the
> > > > > underlying protocol is functioning properly and you
have
proper routers in your routing table.
> > > > > PIM using underlying IGP to calculate RPF.
> > > > >
> > > > > HTH,
> > > > > Tarun
> > > > >
> > > > >
> > > > > On 11/7/07, Joseph Brunner < joe@affirmedsystems.com >
wrote:
> > > > > >
> > > > > > Debug ip mpacket detail
> > > > > >
> > > > > > -----Original Message-----
> > > > > > From: nobody@groupstudy.com
[mailto:nobody@groupstudy.com]
> > > > > > On Behalf Of Chris Riling
> > > > > > Sent: Wednesday, November 07, 2007 10:44 AM
> > > > > > To: Tarun Pahuja
> > > > > > Cc: groupstudy
> > > > > > Subject: Re: Soup-to-Nuts: MCAST Lab 5 - Auto RP
with
> > > > > > Multiple RP's
> > > > > >
> > > > > > BTW - R4 IS receiving announcements from R1:
> > > > > >
> > > > > > *Mar 3 03:24: 23.515: Auto-RP(0): Received
RP-announce, from
> > > > > > 1.1.1.1 <http://1.1.1.1/> , RP_cnt 1, ht 31 *Mar 3
03:24:23.515: Auto-RP(0):
> > > > > > Received RP-announce, from 1.1.1.1 <http://1.1.1.1/>
, RP_cnt 1, ht 31
> > > > > >
> > > > > >
> > > > > > but I still don't see an entry for 224.8.8.8
<http://224.8.8.8/> :
> > > > > >
> > > > > > R4#sh ip pim rp
> > > > > > Group: 224.11.11.11 <http://224.11.11.11/> , RP:
4.4.4.4 <http://4.4.4.4/> , v2, v1, next RP-reachable
> > > > > > in
> > > > > > 00:01:19
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > > Chris
> > > > > >
> > > > > >
> > > > > > On 11/7/07, Chris Riling < criling@gmail.com >
wrote:
> > > > > > >
> > > > > > > I just labbed it up again after a night of sleep
and I'm
> > > > > > > still
> > > > > > seeing the
> > > > > > > same thing...
> > > > > > >
> > > > > > >
> > > > > > > Topology:
> > > > > > >
> > > > > > > R1
> > > > > > > R2
> > > > > > > |
> > > > > > > |
> > > > > > > |
> > > > > > > |
> > > > > > > Frame 131.1.14.0/24
> > > > > > Frame
> > > > > > > 131.1.23.0/24
> > > > > > > |
> > > > > > > |
> > > > > > > |
> > > > > > > |
> > > > > > > R4--------------------------Ethernet
> > > > > > > 131.1.34.0/24-----------------------------R3
> > > > > > >
> > > > > > > Configs:
> > > > > > >
> > > > > > > R1:
> > > > > > >
> > > > > > > !
> > > > > > > version 12.4
> > > > > > > service timestamps debug datetime msec service
timestamps
> > > > > > > log datetime msec no service password-encryption !
> > > > > > > hostname R1
> > > > > > > !
> > > > > > > boot-start-marker
> > > > > > > boot-end-marker
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > resource policy
> > > > > > > !
> > > > > > > no aaa new-model
> > > > > > > no network-clock-participate slot 1 no
> > > > > > > network-clock-participate wic 0 ip subnet-zero !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip cef
> > > > > > > ip multicast-routing
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > interface Loopback0
> > > > > > > ip address 1.1.1.1 <http://1.1.1.1/> 255.0.0.0
<http://255.0.0.0/> ip pim sparse-dense-mode !
> > > > > > > interface FastEthernet0/0
> > > > > > > ip address 131.1.1.1 <http://131.1.1.1/>
255.255.255.0 <http://255.255.255.0/> ip pim
> > > > > > > sparse-dense-mode ip igmp join-group 224.11.11.11
<http://224.11.11.11/> duplex
> > > > > > > auto speed auto !
> > > > > > > interface Serial0/0
> > > > > > > no ip address
> > > > > > > encapsulation frame-relay no frame-relay
inverse-arp !
> > > > > > > interface Serial0/0.14 point-to-point ip address
> > > > > > > 131.1.14.1 <http://131.1.14.1/> 255.255.255.0
<http://255.255.255.0/> ip pim sparse-dense-mode
> > > > > > > frame-relay interface-dlci 104 !
> > > > > > > interface Serial0/1
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > !
> > > > > > > router rip
> > > > > > > version 2
> > > > > > > network 1.0.0.0 <http://1.0.0.0/>
> > > > > > > network 131.1.0.0 <http://131.1.0.0/>
> > > > > > > no auto-summary
> > > > > > > !
> > > > > > > ip classless
> > > > > > > !
> > > > > > > !
> > > > > > > ip http server
> > > > > > > no ip http secure-server
> > > > > > > ip pim send-rp-announce Loopback0 scope 5
group-list 1
> > > > > > > interval
> > > > > > 10
> > > > > > > ip pim send-rp-discovery scope 5 !
> > > > > > > access-list 1 permit 224.8.8.8 <http://224.8.8.8/>
!
> > > > > > > !
> > > > > > > !
> > > > > > > control-plane
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec sir sh ip route alias exec sib sh ip
bgp alias
> > > > > > > exec cir clear ip route * alias exec siib sh ip
int brief
> > > > > > > | e unass !
> > > > > > > line con 0
> > > > > > > logging synchronous
> > > > > > > line aux 0
> > > > > > > line vty 0 4
> > > > > > > login
> > > > > > > !
> > > > > > > !
> > > > > > > end
> > > > > > >
> > > > > > > R2:
> > > > > > >
> > > > > > > !
> > > > > > > version 12.4
> > > > > > > service timestamps debug datetime msec service
timestamps
> > > > > > > log datetime msec no service password-encryption !
> > > > > > > hostname R2
> > > > > > > !
> > > > > > > boot-start-marker
> > > > > > > boot-end-marker
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > resource policy
> > > > > > > !
> > > > > > > no aaa new-model
> > > > > > > no network-clock-participate slot 1 no
> > > > > > > network-clock-participate wic 0 ip subnet-zero !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip cef
> > > > > > > ip multicast-routing
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > interface FastEthernet0/0
> > > > > > > ip address 131.2.2.2 <http://131.2.2.2/>
255.255.255.0 <http://255.255.255.0/> ip pim
> > > > > > > sparse-dense-mode duplex auto speed auto !
> > > > > > > interface Serial0/0
> > > > > > > no ip address
> > > > > > > encapsulation frame-relay no frame-relay
inverse-arp !
> > > > > > > interface Serial0/0.23 point-to-point ip address
> > > > > > > 131.1.23.2 <http://131.1.23.2/> 255.255.255.0
<http://255.255.255.0/> ip pim sparse-dense-mode
> > > > > > > frame-relay interface-dlci 203 !
> > > > > > > interface Serial0/1
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > !
> > > > > > > router rip
> > > > > > > version 2
> > > > > > > network 131.1.0.0 <http://131.1.0.0/>
> > > > > > > no auto-summary
> > > > > > > !
> > > > > > > ip classless
> > > > > > > !
> > > > > > > !
> > > > > > > ip http server
> > > > > > > no ip http secure-server
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > control-plane
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec sir sh ip route alias exec sib sh ip
bgp alias
> > > > > > > exec cir clear ip route * alias exec siib sh ip
int brief
> > > > > > > | e unass !
> > > > > > > line con 0
> > > > > > > logging synchronous
> > > > > > > line aux 0
> > > > > > > line vty 0 4
> > > > > > > login
> > > > > > > !
> > > > > > > !
> > > > > > > end
> > > > > > >
> > > > > > > R3:
> > > > > > >
> > > > > > > !
> > > > > > > version 12.4
> > > > > > > service timestamps debug datetime msec service
timestamps
> > > > > > > log datetime msec no service password-encryption !
> > > > > > > hostname R3
> > > > > > > !
> > > > > > > boot-start-marker
> > > > > > > boot-end-marker
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > resource policy
> > > > > > > !
> > > > > > > no aaa new-model
> > > > > > > no network-clock-participate slot 1 no
> > > > > > > network-clock-participate wic 0 !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip cef
> > > > > > > ip multicast-routing
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > interface FastEthernet0/0
> > > > > > > ip address 131.1.34.3 <http://131.1.34.3/>
255.255.255.0 <http://255.255.255.0/> ip pim
> > > > > > > sparse-dense-mode duplex auto speed auto !
> > > > > > > interface Serial0/0
> > > > > > > no ip address
> > > > > > > encapsulation frame-relay no
dce-terminal-timing-enable
> > > > > > > no frame-relay inverse-arp frame-relay lmi-type
ansi !
> > > > > > > interface Serial0/0.32 point-to-point ip address
> > > > > > > 131.1.23.3 <http://131.1.23.3/> 255.255.255.0
<http://255.255.255.0/> ip pim sparse-dense-mode
> > > > > > > frame-relay interface-dlci 302 !
> > > > > > > interface Serial0/1
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > no dce-terminal-timing-enable !
> > > > > > > router rip
> > > > > > > version 2
> > > > > > > network 131.1.0.0 <http://131.1.0.0/>
> > > > > > > no auto-summary
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip http server
> > > > > > > no ip http secure-server
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > control-plane
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec sir sh ip route alias exec sib sh ip
bgp alias
> > > > > > > exec cir clear ip route * alias exec siib sh ip
int brief
> > > > > > > | e unass !
> > > > > > > line con 0
> > > > > > > logging synchronous
> > > > > > > line aux 0
> > > > > > > line vty 0 4
> > > > > > > login
> > > > > > > !
> > > > > > > !
> > > > > > > end
> > > > > > >
> > > > > > >
> > > > > > > R4:
> > > > > > >
> > > > > > > !
> > > > > > > version 12.4
> > > > > > > service timestamps debug datetime msec service
timestamps
> > > > > > > log datetime msec no service password-encryption !
> > > > > > > hostname R4
> > > > > > > !
> > > > > > > boot-start-marker
> > > > > > > boot-end-marker
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > resource policy
> > > > > > > !
> > > > > > > no aaa new-model
> > > > > > > no network-clock-participate slot 1 no
> > > > > > > network-clock-participate wic 0 ip subnet-zero !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip cef
> > > > > > > ip multicast-routing
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > interface Loopback0
> > > > > > > ip address 4.4.4.4 <http://4.4.4.4/> 255.0.0.0
<http://255.0.0.0/> ip pim sparse-dense-mode !
> > > > > > > interface FastEthernet0/0
> > > > > > > ip address 131.1.34.4 <http://131.1.34.4/>
255.255.255.0 <http://255.255.255.0/> ip pim
> > > > > > > sparse-dense-mode ip igmp join-group 224.8.8.8
<http://224.8.8.8/> duplex
> > > > > > > auto speed auto !
> > > > > > > interface Serial0/0
> > > > > > > no ip address
> > > > > > > encapsulation frame-relay no frame-relay
inverse-arp
> > > > > > > frame-relay lmi-type ansi !
> > > > > > > interface Serial0/0.41 point-to-point ip address
> > > > > > > 131.1.14.4 <http://131.1.14.4/> 255.255.255.0
<http://255.255.255.0/> ip pim sparse-dense-mode
> > > > > > > frame-relay interface-dlci 401 !
> > > > > > > interface Serial0/1
> > > > > > > no ip address
> > > > > > > shutdown
> > > > > > > !
> > > > > > > router rip
> > > > > > > version 2
> > > > > > > network 4.0.0.0 <http://4.0.0.0/>
> > > > > > > network 131.1.0.0 <http://131.1.0.0/>
> > > > > > > no auto-summary
> > > > > > > !
> > > > > > > ip classless
> > > > > > > !
> > > > > > > !
> > > > > > > ip http server
> > > > > > > no ip http secure-server
> > > > > > > ip pim send-rp-announce Loopback0 scope 5
group-list 1
> > > > > > > interval
> > > > > > 10
> > > > > > > ip pim send-rp-discovery scope 5 !
> > > > > > > access-list 1 deny 224.8.8.8 <http://224.8.8.8/>
> > > > > > > access-list 1 permit 224.0.0.0 <http://224.0.0.0/>
15.255.255.255 <http://15.255.255.255/> !
> > > > > > > !
> > > > > > > !
> > > > > > > control-plane
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec sir sh ip route alias exec sib sh ip
bgp alias
> > > > > > > exec cir clear ip route * alias exec siib sh ip
int brief
> > > > > > > | e unass !
> > > > > > > line con 0
> > > > > > > logging synchronous
> > > > > > > line aux 0
> > > > > > > line vty 0 4
> > > > > > > login
> > > > > > > !
> > > > > > > !
> > > > > > > end
> > > > > > >
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Chris
> > > > > > >
> > > > > > >
> > > > > > > On 11/7/07, Tarun Pahuja < pahujat@gmail.com>
wrote:
> > > > > > > >
> > > > > > > > Chris,
> > > > > > > > Sure post the config, 30 seconds
response time
> > > > > > > > might
> > > > > > be
> > > > > > > > difficult since we are in totally different time
zone. I
> > > > > > promise a
> > > > > > Timely
> > > > > > > > response.
> > > > > > > > Thanks,
> > > > > > > > Tarun
> > > > > > > >
> > > > > > > >
> > > > > > > > On 11/7/07, Chris Riling < criling@gmail.com>
wrote:
> > > > > > > >
> > > > > > > > > Hey Guys,
> > > > > > > > >
> > > > > > > > > I got the topology working okay, and I
joined
> > > > > > > > > each of
> > > > > > the groups
> > > > > > > > > on 1
> > > > > > > > > router using "ip igmp join-group" and when I
ping the
> > > > > > > > > group
> > > > > > addresses
> > > > > > > > > and do
> > > > > > > > > a "sh ip pim rp" on another router, the RP for
one of
> > > > > > > > > the
> > > > > > groups shows
> > > > > > > > > up,
> > > > > > > > > but not the other... anyone seen this happen?
If it's
> > > > > > > > > not
> > > > > > something
> > > > > > > > > you can
> > > > > > > > > can answer in like 30 seconds I can post the
config :)
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Chris
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > >
> > > > > >
This archive was generated by hypermail 2.1.4 : Sat Dec 01 2007 - 06:37:29 ART