From: Schulz, Dave (DSchulz@dpsciences.com)
Date: Thu Nov 10 2005 - 13:57:40 GMT-3
Ah, yes! (my bad)....I changed that and also added the ip pim nbma-mode
on serial 0 at the hub and changed to ip pim sparse on this interface.
Still nothing coming through to the hub. I think I may try a reboot on
the router, but didn't want to just jump to that conclusion.
Dave Schulz,
Email: dschulz@dpsciences.com
-----Original Message-----
From: kgannon@gmail.com [mailto:kgannon@gmail.com] On Behalf Of kevin
gannon
Sent: Thursday, November 10, 2005 11:47 AM
To: Schulz, Dave
Cc: Imal kalutotage; Cisco certification
Subject: Re: Sparse-dense mode example on frame - AutoRP
Its a global command not per interface.
Try moving the RP to R1 and leave it as
the mapping agent as well.
Regards
Kevin
On 11/10/05, Schulz, Dave <DSchulz@dpsciences.com> wrote:
> Thanks, Kevin. You are right, it is a hidden command....it takes it,
> but does not show up under the interface config (hidden there too, I
> guess). However, this doesn't seem to have any effect on the groups
from
> the remote being sent to the hub router. I remember the conversation
on
> GS about this, and I'll review it again. Something just seems a
little
> strange.
>
>
> Dave Schulz,
>
> Email: dschulz@dpsciences.com
>
>
>
> -----Original Message-----
> From: kgannon@gmail.com [mailto:kgannon@gmail.com] On Behalf Of kevin
> gannon
> Sent: Thursday, November 10, 2005 10:57 AM
> To: Schulz, Dave
> Cc: Imal kalutotage; Cisco certification
> Subject: Re: Sparse-dense mode example on frame - AutoRP
>
> If I am reading the post right "ip pim autorp listener" will help you
> here usually you will not forward Mcast and out the same interface.
> In your case this would be the Hubs serial. I did a quick check
> and 12.3 mainline should have this command as 12.2T does.
> However be aware that in some code its a hidden command
> so try typing it out exactly.
>
> There was a good discussion about this about a week ago
> with Scott and the brians. It was about what else the listener
> command does rather than just allowing dense mode for the
> autorp groups and nothing else. Worth a read.
>
> Regards
> Kevin
>
> On 11/10/05, Schulz, Dave <DSchulz@dpsciences.com> wrote:
> > Thanks for response, Imal. My software load does not have the auto
rp
> > listener command. I thought that the auto rp listener command
allows
> > the dense mode for the 39/40 groups for the rp and mapping. However,
I
> > am using sparse-dense....doesn't this take control of this issue.
So,
> > is there a way to auto-rp before this command came about?
> >
> >
> >
> >
> >
> > Dave Schulz,
> >
> > Email: dschulz@dpsciences.com <mailto:dschulz@dpsciences.com%20>
> >
> >
> >
> > ________________________________
> >
> > From: Imal kalutotage [mailto:imal.kalutotage@gmail.com]
> > Sent: Thursday, November 10, 2005 1:39 AM
> > To: Schulz, Dave
> > Subject: Re: Sparse-dense mode example on frame - AutoRP
> >
> >
> >
> > In this type of senario, most likely you have have a spoke to spoke
> > tunnel & with static mroutes.
> >
> > Otherwise, use "sparse-mode with ip pim auto rp listner. also use ip
> pim
> > nbma mode on R2 s0/0
> >
> > But this works only for short time & rpf will fail. So you have to
> alter
> > the rpf with static mroute.
> >
> > HTH
> >
> > Imal
> >
> > On 11/9/05, Schulz, Dave <DSchulz@dpsciences.com> wrote:
> >
> > I am having an issue getting this multicast config to work
correctly.
> > Any ideas on what I am missing......
> >
> >
> > R1 is the hub of a frame relay going to R5 and R6 as the remotes,
> > running ospf. R1 is configured the mapping agent, and R5 as an RP
> > (Auto-rp). I am joining to the group 239.6.6.6 at the Ethernet on
R6.
> > When I do a show ip igmp group at R6, I can see the multicast group.
> > However, I cannot see this group show up at R1 and R6. Any
thoughts?
> I
> >
> > am starting to think that I have a problem with the software load
> > 12.3(5e). Sorry for the lengthy email. Any help or just direction
> > would be greatly appreciated.
> >
> > Any thoughts?
> >
> > R1......
> > !
> > ip multicast-routing
> > isdn voice-call-failure 0
> > !
> > !
> > interface Serial0
> > ip address 10.10.10.1 255.255.255.0
> > ip pim sparse-dense-mode
> > encapsulation frame-relay
> > no ip mroute-cache
> > no fair-queue
> > frame-relay map ip 10.10.10.1 105
> > frame-relay map ip 10.10.10.5 105 broadcast
> > frame-relay map ip 10.10.10.6 106 broadcast
> > no frame-relay inverse-arp
> > !
> > router ospf 1
> > router-id 10.10.10.10
> > log-adjacency-changes
> > network 10.10.10.0 0.0.0.255 area 0
> > neighbor 10.10.10.6 priority 1
> > neighbor 10.10.10.5 priority 1
> > !
> > ip pim send-rp-discovery Serial0 scope 15
> >
> >
> > R5.....
> > !
> > ip multicast-routing
> > !
> > interface Ethernet0
> > ip address 10.1.1.5 255.255.255.0
> > !
> > interface Serial0
> > ip address 10.10.10.5 255.255.255.0
> > ip pim sparse-dense-mode
> > encapsulation frame-relay
> > no fair-queue
> > frame-relay map ip 10.10.10.1 501 broadcast
> > frame-relay map ip 10.10.10.5 501
> > frame-relay map ip 10.10.10.6 501
> > no frame-relay inverse-arp
> > !
> > router ospf 1
> > router-id 5.5.5.5
> > log-adjacency-changes
> > network 10.10.10.0 0.0.0.255 area 0
> > !
> > ip pim send-rp-announce Serial0 scope 15
> > !
> >
> >
> > R6......
> > ip multicast-routing
> > !
> > !
> > !
> > interface Loopback0
> > ip address 2.2.2.2 255.255.255.0
> > !
> > interface Ethernet0
> > ip address 10.1.1.6 255.255.255.0
> > ip pim sparse-dense-mode
> > ip igmp join-group 239.6.6.6
> > !
> > interface Serial0
> > ip address 10.10.10.6 255.255.255.0
> > ip pim sparse-dense-mode
> > encapsulation frame-relay
> > frame-relay map ip 10.10.10.1 601 broadcast
> > frame-relay map ip 10.10.10.5 601
> > frame-relay map ip 10.10.10.6 601
> > no frame-relay inverse-arp
> > !
> > router ospf 1
> > router-id 6.6.6.6
> > log-adjacency-changes
> > network 10.10.10.0 0.0.0.255 area 0
> >
> >
> > R6#sh ip igmp group
> > IGMP Connected Group Membership
> > Group Address Interface Uptime Expires Last
> > Reporter
> > 239.6.6.6 Ethernet0 01:14:52 00:02:36
10.1.1.6
> > 224.0.1.39 Serial0 01:16:41 00:02:17
> 10.10.10.1
> > 224.0.1.40 Serial0 01:16:46 00:02:25
> 10.10.10.1
> > R6#
> >
> > R1#sh ip igmp group
> > IGMP Connected Group Membership
> > Group Address Interface Uptime Expires Last
> > Reporter
> > 224.0.1.39 Serial0 01:19:44 00:02:54
> 10.10.10.1
> > 224.0.1.40 Serial0 01:22:30 00:02:50
> 10.10.10.1
> >
> > R1#sh ip mrou
> > 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
> > 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.0.1.39), 01:20:26/stopped, RP 0.0.0.0, flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0, Forward/Sparse-Dense, 01:20:26/00:00:00
> >
> > (10.10.10.5, 224.0.1.39), 01:18:50/00:02:09, flags: PLT
> > Incoming interface: Serial0, RPF nbr 0.0.0.0
> > Outgoing interface list: Null
> >
> > (*, 224.0.1.40), 01:23:13/00:02:07, RP 0.0.0.0, flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0, Forward/Sparse-Dense, 01:23:13/00:00:00
> >
> >
> >
> > R6#sh ip mrou
> > 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
> > 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
> >
> > (*, 239.6.6.6), 01:16:19/00:02:12, RP 10.10.10.5, flags: SJCL
> > Incoming interface: Serial0, RPF nbr 10.10.10.5
> > Outgoing interface list:
> > Ethernet0, Forward/Sparse-Dense, 01:16:19/00:02:12
> >
> > (*, 224.0.1.39 ), 01:17:59/00:02:56, RP 0.0.0.0, flags: DC
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0, Forward/Sparse-Dense, 01:17:59/00:00:00
> >
> > (*, 224.0.1.40), 01:18:05/stopped, RP 0.0.0.0, flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0
> > Outgoing interface list:
> > Serial0, Forward/Sparse-Dense, 01:18:05/00:00:00
> >
> > (10.10.10.1, 224.0.1.40), 01:18:05/00:02:22, flags: PLT
> > Incoming interface: Serial0, RPF nbr 0.0.0.0
> > Outgoing interface list: Null
> >
> >
> > Dave Schulz
> > Email: dschulz@dpsciences.com <mailto: dschulz@dpsciences.com
> > <mailto:dschulz@dpsciences.com> >
> >
> >
>
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3