From: Imal kalutotage (imal.kalutotage@gmail.com)
Date: Mon Oct 03 2005 - 20:07:58 GMT-3
Hi all,
I also doing a simlar kind of senario with
R3 --------R4 -------------R6
s0/0 s0/0.1 s0/0
R3 has groups 224.3.3.3 <http://224.3.3.3> joined on e0/0
R6 has 224.6.6.6 <http://224.6.6.6>
R3 is the RP, R4 as the MA & R4 ha the ip pim nbma mode
also I have dlci s pointing to R4 with broadcast keyword.
when I try to ping the 224.3.3.3 <http://224.3.3.3> from R6 with extended
ping it want ping.
The I noticed that at R4 it cannot find the OIL even with the ip pim nbma
mode command.
But when u ping from R3 to 224.6.6.6 <http://224.6.6.6> it pings.
interestingly this time it make the OIL with the Ip addresses of the R6 &
R3.
I tried this with both Aoto RP & BSR.Also with the static RP.
Only solution worked for me is a spoke to spoke tunnel. with static mroute
pointing to R6 loopback.
Can somebody confirm this,.
Because most people say this will work only with ip pim nbma mode command at
the hub.
But this has never worked for me..
Am I missing something here?
Cheers,
Imal
On 10/3/05, Mike Flanagan <mikenoc@mindspring.com> wrote:
>
> If I do a show ip pim rp mapping the on the spokes it says this
> system is an RP and on the mapping agent it shows the groups. I have
> an output of that from each router below. I do not have anything
> joining these groups so no ip igmp join-group or static group
> commands. I think it may not be working properly because I do not see
> the multicast routes when doing a show ip mroute. Do I have to have
> something joining the group to see the entry multicast network
> announced from the RP in the mroute table ?
>
>
> Thanks,
>
> Mike F.
>
>
>
>
> On Oct 3, 2005, at 8:03 AM, Bob Sinclair wrote:
>
> > Mike,
> >
> > The nbma-mode on the hub was a good idea. Here are a few things to
> > check. Do
> > all three routers get the RP information? Issue the command: show
> > ip pim rp
> > mapping. Do you have clients configured on the spoke routers? If
> > so, you
> > should see (*,G) entries for them locally. Make sure that when you
> > test you
> > do an extended ping with a high repeat count; otherwise the state
> > may timeout
> > before you can see it. A few more helpful commands: debug ip
> > mpacket; show
> > ip pim interface count.
> >
> > HTH,
> >
> > Bob Sinclair
> > CCIE #10427, CCSI 30427, CISSP
> > www.netmasterclass.net <http://www.netmasterclass.net>
> >
> > ----- Original Message -----
> > From: Mike Flanagan
> > To: Cisco certification
> > Sent: Monday, October 03, 2005 4:03 AM
> > Subject: Trouble with multicast over NBMA
> >
> >
> > Hello,
> >
> > I originally posted this a few weeks ago and then got sick and
> > have
> > not touched this. What I am trying to do here is get multicast
> > working over 3 routers. Router R2 is the hub and is the mapping
> > agent
> > and R1 and R3 are RP's for two different multicast networks. If you
> > do a show ip rp map on R2 you see that it has the two multicast
> > networks on it. if you do a show ip mroute on and of these 3 routers
> > you do not see the networks at all. I tried adding ip pim nbma mode
> > on R2 due to the fact that you cannot announce a multicast group
> > back
> > out an interface that was learned. With the theory in mind of
> > changing the OIL from using the interface to an IP address but that
> > did not work. I am not sure if I am missing something simple "which
> > is highly likely ;)" or if maybe I need to make a tunnel between R1
> > and R3.
> >
> >
> > Please advise.
> >
> > Thanks,
> >
> > Mike F.
> >
> >
> >
> > R2
> > / \
> > / \
> > R1 R3
> >
> >
> > R1#sh run int ser 0/0.5
> > Building configuration...
> >
> > Current configuration : 227 bytes
> > !
> > interface Serial0/0.5 multipoint
> > ip address 1.1.0.1 <http://1.1.0.1> 255.255.255.0 <http://255.255.255.0>
> > ip pim nbma-mode
> > ip pim sparse-dense-mode
> > ip ospf priority 0
> > frame-relay map ip 1.1.0.2 <http://1.1.0.2> 105 broadcast
> > frame-relay map ip 1.1.0.3 <http://1.1.0.3> 102
> > end
> >
> > R1#
> >
> > ip pim send-rp-announce Loopback0 scope 16 group-list 11
> > R1#
> > R1#sh access-lists 11
> > Standard IP access list 11
> > 10 permit 224.0.0.0 <http://224.0.0.0>, wildcard bits
7.255.255.255<http://7.255.255.255>
> > R1#
> >
> >
> >
> > R1#sh ip pim nei
> > PIM Neighbor Table
> > Neighbor Interface Uptime/Expires
> > Ver DR
> > Address
> > Prio/Mode
> > 1.1.0.2 <http://1.1.0.2> Serial0/0.5 00:09:09/00:01:20 v2
> > 1 / DR S
> > R1#
> >
> > R1#sh ip pim rp map
> > PIM Group-to-RP Mappings
> > This system is an RP (Auto-RP)
> >
> > R1#
> >
> >
> > R1#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
> >
> > (*, 224.0.1.39 <http://224.0.1.39>), 00:41:50/stopped, RP
0.0.0.0<http://0.0.0.0>,
> flags: DC
> > Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0>
> > Outgoing interface list:
> > Serial0/0.5, Forward/Sparse-Dense, 00:41:50/00:00:00
> >
> > (1.1.1.1 <http://1.1.1.1>, 224.0.1.39 <http://224.0.1.39>),
> 00:41:24/00:02:35, flags: T
> > Incoming interface: Loopback0, RPF nbr 0.0.0.0 <http://0.0.0.0>
> > Outgoing interface list:
> > Serial0/0.5, Forward/Sparse-Dense, 00:41:24/00:00:00
> >
> > (*, 224.0.1.40 <http://224.0.1.40>), 00:42:19/stopped, RP
0.0.0.0<http://0.0.0.0>,
> flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0>
> > Outgoing interface list:
> > Serial0/0.5, Forward/Sparse-Dense, 00:41:54/00:00:00
> > Loopback0, Forward/Sparse-Dense, 00:42:20/00:00:00
> >
> > (1.1.2.2 <http://1.1.2.2>, 224.0.1.40 <http://224.0.1.40>),
> 00:04:26/00:02:37, flags: LT
> > Incoming interface: Serial0/0.5, RPF nbr 1.1.0.3 <http://1.1.0.3>
> > Outgoing interface list:
> > Loopback0, Forward/Sparse-Dense, 00:04:26/00:00:00
> >
> > R1#
> >
> > -----------------------------------------
> >
> > R2#sh run int ser 0/0.1
> > Building configuration...
> >
> > Current configuration : 202 bytes
> > !
> > interface Serial0/0.1 multipoint
> > ip address 1.1.0.2 <http://1.1.0.2> 255.255.255.0 <http://255.255.255.0>
> > ip pim nbma-mode
> > ip pim sparse-dense-mode
> > frame-relay map ip 1.1.0.1 <http://1.1.0.1> 501 broadcast
> > frame-relay map ip 1.1.0.3 <http://1.1.0.3> 502 broadcast
> > end
> >
> > R2#
> >
> > ip pim send-rp-discovery Loopback0 scope 16
> >
> >
> > R2#sh ip pim nei
> > PIM Neighbor Table
> > Neighbor Interface Uptime/Expires
> > Ver DR
> > Address
> > Prio/Mode
> > 1.1.0.3 <http://1.1.0.3> Serial0/0.1 00:06:28/00:01:31 v2
> > 1 / DR S
> > 1.1.0.1 <http://1.1.0.1> Serial0/0.1 00:07:50/00:01:18
> > v2 1 / S
> > R2#
> >
> > R2#sh ip pim rp map
> > PIM Group-to-RP Mappings
> > This system is an RP-mapping agent (Loopback0)
> >
> > Group(s) 224.0.0.0/5 <http://224.0.0.0/5>
> > RP 1.1.1.1 <http://1.1.1.1> (?), v2v1
> > Info source: 1.1.1.1 <http://1.1.1.1> (?), elected via Auto-RP
> > Uptime: 00:02:29, expires: 00:02:29
> > Group(s) 232.0.0.0/5 <http://232.0.0.0/5>
> > RP 1.1.3.3 <http://1.1.3.3> (?), v2v1
> > Info source: 1.1.3.3 <http://1.1.3.3> (?), elected via Auto-RP
> > Uptime: 00:13:48, expires: 00:01:12
> > R2#
> >
> >
> >
> >
> > R2#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
> >
> > (*, 224.0.1.39 <http://224.0.1.39>), 00:30:18/stopped, RP
0.0.0.0<http://0.0.0.0>,
> flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0>
> > Outgoing interface list:
> > Loopback0, Forward/Sparse-Dense, 00:30:18/00:00:00
> > Serial0/0.1, Forward/Sparse-Dense, 00:30:18/00:00:00
> >
> > (1.1.1.1 <http://1.1.1.1>, 224.0.1.39 <http://224.0.1.39>),
> 00:09:01/00:02:59, flags: LT
> > Incoming interface: Serial0/0.1, RPF nbr 1.1.0.1 <http://1.1.0.1>
> > Outgoing interface list:
> > Loopback0, Forward/Sparse-Dense, 00:09:01/00:00:00
> >
> > (1.1.2.2 <http://1.1.2.2>, 224.0.1.39 <http://224.0.1.39>),
> 00:00:25/00:02:35, flags: LT
> > Incoming interface: Loopback0, RPF nbr 0.0.0.0 <http://0.0.0.0>
> > Outgoing interface list:
> > Serial0/0.1, Forward/Sparse-Dense, 00:00:25/00:00:00
> >
> > (*, 224.0.1.40 <http://224.0.1.40>), 00:30:19/stopped, RP
0.0.0.0<http://0.0.0.0>,
> flags: DCL
> > Incoming interface: Null, RPF nbr 0.0.0.0 <http://0.0.0.0>
> > Outgoing interface list:
> > Loopback0, Forward/Sparse-Dense, 00:30:19/00:00:00
> > Serial0/0.1, Forward/Sparse-Dense, 00:30:19/00:00:00
> >
> > (1.1.2.2 <http://1.1.2.2>, 224.0.1.40 <http://224.0.1.40>),
> 00:13:09/00:02:54, flags: L
> > Incoming interface: Loopback0, RPF nbr 0.0.0.0 <http://0.0.0.0>
> > Outgoing interface list:
> > Serial0/0.1, Forward/Sparse-Dense, 00:12:21/00:00:00
> >
> > R2#
> >
> > -----------------------------------------
> >
> > R3#sh run int ser 0/0
> > Building configuration...
> >
> > Current configuration : 318 bytes
> > !
> > interface Serial0/0
> > ip address 1.1.0.3 <http://1.1.0.3> 255.255.255.0 <http://255.255.255.0>
> > ip pim sparse-dense-mode
> > encapsulation frame-relay
> > ip ospf priority 0
> > frame-relay map ip 1.1.0.1 <http://1.1.0.1> 201
> > frame-relay map ip 1.1.0.2 <http://1.1.0.2> 205 broadcast
> > no frame-relay inverse-arp
> > frame-relay lmi-type cisco
> > end
> >
> > R3#
> >
> >
> > R3#sh ip pim nei
> > PIM Neighbor Table
> > Neighbor Interface Uptime/Expires
> > Ver DR
> > Address
> > Prio/Mode
> > 1.1.0.2 <http://1.1.0.2> Serial0/0 00:13:08/00:01:17
> > v2 1 / S
> > R3#
> >
> > R3#sh ip pim rp map
> > PIM Group-to-RP Mappings
> > This system is an RP (Auto-RP)
> >
> > R3#
> >
> > R3#sh ip pim rp map
> > PIM Group-to-RP Mappings
> > This system is an RP (Auto-RP)
> >
> > R3#
> >
> >
> > R3#sh ip pim rp map
> > PIM Group-to-RP Mappings
> > This system is an RP (Auto-RP)
> >
> > R3#
> >
> > ip pim send-rp-announce Loopback0 scope 16 group-list 1
> > R3#sh access-li
> > R3#sh access-lists 1
> > Standard IP access list 1
> > 10 permit 232.0.0.0 <http://232.0.0.0>, wildcard bits
7.255.255.255<http://7.255.255.255>
> > R3#
> >
> >
> > ______________________________________________________________________
> > _
> > 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
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Nov 06 2005 - 22:00:49 GMT-3