From: Wang Dehong-DWANG1 (Dehong.Wang@motorola.com)
Date: Sun Nov 13 2005 - 17:41:42 GMT-3
Here is the topology.. R2 is the hub and R1 and R3 are the spokes. Ip
igmp join-group is configured on fa0/0 on R3.. I put R1 as the RP. I can
ping 225.25.25.25 from R1(spoke). I did not use AutoRP but use static RP
instead. Notice that the ip address for the outgoing interface on R2,
which is nmba-mode for.
Rack1R1#ping 225.25.25.25
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 225.25.25.25, timeout is 2 seconds:
Reply to request 0 from 141.141.123.3, 212 ms
======== R1 ===============
Rack1R1#sh run int s0/0
Building configuration...
Current configuration : 285 bytes
!
interface Serial0/0
ip address 141.141.123.1 255.255.255.0
ip pim sparse-mode
encapsulation frame-relay
ip ospf network point-to-multipoint
ip ospf priority 0
frame-relay map ip 141.141.123.2 102 broadcast
frame-relay map ip 141.141.123.3 102
no frame-relay inverse-arp
============== R2================
Rack1R2#sh run int s0/0
Building configuration...
Current configuration : 293 bytes
!
interface Serial0/0
ip address 141.141.123.2 255.255.255.0
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
ip ospf network point-to-multipoint
frame-relay map ip 141.141.123.1 201 broadcast
frame-relay map ip 141.141.123.3 203 broadcast
no frame-relay inverse-arp
ip pim rp-address 150.1.1.1
========= R3 ===========
Rack1R3#sh run int s0/0
Building configuration...
Current configuration : 285 bytes
!
interface Serial0/0
ip address 141.141.123.3 255.255.255.0
ip pim sparse-mode
encapsulation frame-relay
ip ospf network point-to-multipoint
ip ospf priority 0
frame-relay map ip 141.141.123.1 302
frame-relay map ip 141.141.123.2 302 broadcast
no frame-relay inverse-arp
interface FastEthernet0/0
ip address 162.1.38.3 255.255.255.0
ip pim sparse-mode
ip igmp join-group 225.25.25.25
duplex auto
speed auto
ip pim rp-address 150.1.1.1
Rack1R2#sh ip mroute
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
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 225.25.25.25), 00:08:53/stopped, RP 150.1.1.1, flags: S
Incoming interface: Serial0/0, RPF nbr 141.141.123.1
Outgoing interface list:
Serial0/0, 141.141.123.3, Forward/Sparse, 00:06:39/00:02:45
(141.141.123.1, 225.25.25.25), 00:01:00/00:02:01, flags: T
Incoming interface: Serial0/0, RPF nbr 141.141.123.1
Outgoing interface list:
Serial0/0, 141.141.123.3, Forward/Sparse, 00:01:00/00:02:45
(*, 224.0.1.40), 1d22h/00:03:28, RP 150.1.1.1, flags: SJCL
Incoming interface: Serial0/0, RPF nbr 141.141.123.1
Outgoing interface list:
Serial0/0, 141.141.123.3, Forward/Sparse, 1d20h/00:03:28
Rack1R3#sh ip mroute
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
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 225.25.25.25), 00:07:07/stopped, RP 150.1.1.1, flags: SJCLF
Incoming interface: Serial0/0, RPF nbr 141.141.123.2
Outgoing interface list:
FastEthernet0/0, Forward/Sparse, 00:07:07/00:02:52
(141.141.123.1, 225.25.25.25), 00:01:28/00:01:40, flags: LFT
Incoming interface: Serial0/0, RPF nbr 141.141.123.2
Outgoing interface list:
FastEthernet0/0, Forward/Sparse, 00:01:28/00:02:52
(*, 224.0.1.40), 5w5d/00:02:18, RP 150.1.1.1, flags: SJPCL
Incoming interface: Serial0/0, RPF nbr 141.141.123.2
Outgoing interface list: Null
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Schulz, Dave
Sent: Thursday, November 10, 2005 2:55 PM
To: Wang Dehong-DWANG1; kevin gannon
Cc: Imal kalutotage; Cisco certification
Subject: RE: Sparse-dense mode example on frame - AutoRP
This is interesting information! Thanks, Wang. I'll lab that one
up....so, it appears that this is the correct symptom. So, why is it
not possible to ping from the other spoke to the group, even with the ip
pim nbma-mode?
Dave Schulz,
Email: dschulz@dpsciences.com
-----Original Message-----
From: Wang Dehong-DWANG1 [mailto:Dehong.Wang@motorola.com]
Sent: Thursday, November 10, 2005 3:21 PM
To: kevin gannon; Schulz, Dave
Cc: Imal kalutotage; Cisco certification
Subject: RE: Sparse-dense mode example on frame - AutoRP
Only the routers with interested receivers on its directly connected
subnet or with a forced join interface(ip igmp join/static) shows the
joined group. In this case, only R6 will show the joined group.
My understanding is that you have to use the spare-mode on all the pim
interfaces, ip pim auto-rp listerner and ip pim nbma-mode in order to
ping the group from RP if RP is on the spoke.
- Dehong
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
kevin gannon
Sent: Thursday, November 10, 2005 2:00 PM
To: Schulz, Dave
Cc: Imal kalutotage; Cisco certification
Subject: Re: Sparse-dense mode example on frame - AutoRP
I will recreate it in my lab and get back to you.
Regards
Kevin
On 11/10/05, Schulz, Dave <DSchulz@dpsciences.com> wrote:
> Yes, the route is there. Here is something that I may be confused
> with, and, maybe I am thinking that this is not working....when really
> everything is fine......
>
> I do a show ip igmp group...and only show the joined group at the
> router that actually joined the group. Maybe I am confused, but I
> thought that this would show up in ALL routers participating in PIM.
> That must have been a misconception on my part. I go to the R5 router
> (the RP) and I can see both the shared and source paths for this
> group. However, I can ping the group from the hub, but not the RP.
> Should this be the expected behaviour?
>
>
> 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 12:09 PM
> To: Schulz, Dave
> Cc: Imal kalutotage; Cisco certification
> Subject: Re: Sparse-dense mode example on frame - AutoRP
>
> show ip route 10.1.1.0 from Hub and R5......
>
> Regards
> Kevin
>
> On 11/10/05, Schulz, Dave <DSchulz@dpsciences.com> wrote:
> > 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> >
> > > >
> > > >
> > >
> >
> ______________________________________________________________________
> _
> > > > 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
> > > >
> > > > --
> > > > This message has been scanned for viruses and dangerous content
> > > > by MailScanner, and is believed to be clean.
> > >
> > >
> >
> ______________________________________________________________________
> _
> > > Subscription information may be found at:
> > > http://www.groupstudy.com/list/CCIELab.html
> > >
> > > --
> > > This message has been scanned for viruses and dangerous content by
> > > MailScanner, and is believed to be clean.
> > >
> > >
> >
> > --
> > This message has been scanned for viruses and dangerous content by
> > MailScanner, and is believed to be clean.
> >
> >
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
This archive was generated by hypermail 2.1.4 : Thu Dec 01 2005 - 09:12:06 GMT-3