From: Scott Vermillion (scott_ccie_list@it-ag.com)
Date: Wed Nov 07 2007 - 19:39:21 ART
Hey Chris,
I don't have this workbook and I frankly haven't had time to follow the
entire thread. However, I did a quick scan of your below config. I notice
that you have a deny statement on your group-list ACL on R4. It's my
understanding that, although the IOS will accept this deny statement
(because how would it know you were building this ACL for use in Auto RP?),
it is not a valid configuration from an Auto RP perspective. It's my
understanding that you need to use all permit statements *only* in these
group-list ACLs. So if you are expecting R4 to be the RP for everything but
that one 224.8.8.8 group, for which R1 should be the RP, I think you need to
re-work your ACL on R4. I personally have not labbed this scenario up yet,
but I'm expecting to soon, as mcast is on the immediate horizon as I move
through a CoD this week and into next.
Again, I have not followed this thread very closely simply due to my own
intense study schedule this week, but I thought I would throw this out there
for whatever it's worth. If it's totally off base, my apologies to all for
not reading this closer before posting.
Regards,
Scott
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Chris Riling
Sent: Wednesday, November 07, 2007 11:35 AM
To: Tarun Pahuja
Cc: Joseph Brunner; groupstudy
Subject: Re: Soup-to-Nuts: MCAST Lab 5 - Auto RP with Multiple RP's
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 (?), v2v1
Info source: 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 (?), v2v1
Info source: 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 (?), v2v1
Info source: 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 (?), v2v1
Info source: 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 and another for 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 - 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
> > *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 (FastEthernet0/0) d=
> > 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
> > *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 (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 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,
> > > > RP_cnt
> > > > 1, ht 31
> > > > *Mar 3 03:24:23.515: Auto-RP(0): Received RP-announce, from
1.1.1.1,
> > > > RP_cnt
> > > > 1, ht 31
> > > >
> > > >
> > > > but I still don't see an entry for 224.8.8.8:
> > > >
> > > > R4#sh ip pim rp
> > > > Group: 224.11.11.11 , RP: 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 255.0.0.0
> > > > > ip pim sparse-dense-mode
> > > > > !
> > > > > interface FastEthernet0/0
> > > > > ip address 131.1.1.1 255.255.255.0
> > > > > ip pim sparse-dense-mode
> > > > > ip igmp join-group 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 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
> > > > > network 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
> > > > > !
> > > > > !
> > > > > !
> > > > > 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 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 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
> > > > > 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 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 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
> > > > > 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 255.0.0.0
> > > > > ip pim sparse-dense-mode
> > > > > !
> > > > > interface FastEthernet0/0
> > > > > ip address 131.1.34.4 255.255.255.0
> > > > > ip pim sparse-dense-mode
> > > > > ip igmp join-group 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 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
> > > > > network 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
> > > > > access-list 1 permit 224.0.0.0 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:28 ART