From: Narvaez, Pablo (Pablo.Narvaez@xxxxxxxxxxxxx)
Date: Thu Apr 04 2002 - 21:43:57 GMT-3
It works fine for me over point-to-point FR using sparse-dense without that com
mand ... Now I'm testing Multicast sparse-dense over Multipoint FR where the RP
is the hub: I can multicast-ping from the hub to the spokes, but cannot ping a
mong spokes ... Have you tried that w/o that command with this topology?
-----Original Message-----
From: Bob Sinclair [mailto:bsin@erols.com]
Sent: Jueves, 04 de Abril de 2002 06:19 p.m.
To: Jason Sinclair
Cc: ccielab@groupstudy.com
Subject: Re: Urgent multicast question - lab on Monday
Jason,
There is not a lot of documentation I can find on the ip pim nbma-mode command.
Some of the docs either strongly suggest or demand that you run sparse-mode.
Perhaps it makes a difference that you are using sparse-dense?
Have you tried it without that command. It appears to be optional. I was doin
g multicast over frame last night without ip pim nbma-mode, and it appeared to
work correctly.
-Bob
----- Original Message -----
From: "Jason Sinclair" <sinclairj@powertel.com.au>
To: <ccielab@groupstudy.com>
Sent: Thursday, April 04, 2002 6:27 PM
Subject: Urgent multicast question - lab on Monday
> All,
>
> I have the following topology:
>
>
>
>
>
>
> Router1---------------------router2
> |
> |
> |
> |
> router3
>
> The links are frame relay and I have set the following configs:
>
>
> Router1
> Ip multicast-routing
> Ip pim send-rp-discovery s 0 sc 255
> Int s0
> Ip pim nbma-mode
> Ip pim sparse-dense-mode
> Int lo0
> Ip pim sparse-dense-mode
> Ip igmp join-group 225.2.2.2
>
> Router2
> Ip multicast-routing
> Ip pim send-rp-announce s 0 sc 255
> Int s0
> Ip pim nbma-mode
> Ip pim sparse-dense-mode
>
> Router3
> Ip multicast-routing
> Int s0
> Ip pim nbma-mode
> Ip pim sparse-dense-mode
>
> All the associated routing is their from a unicast perspective. My issue is
> that on R1 I can ping the 225.2.2.2 address BUT NOT from R2. However the RP
> mappings are all fine as below. When I move the C-RP to (the
> send-rp-announce) to R1 it is OK. Any ideas as I have my lab on Monday.
>
> R3#show ip pim rp
> Group: 225.2.2.2, RP: 155.1.123.2, v2, v1, uptime 00:00:07, expires 00:02:52
>
> r3#show ip pim rp map
> PIM Group-to-RP Mappings
>
> Group(s) 224.0.0.0/4
> RP 155.1.123.2 (?), v2v1
> Info source: 155.1.123.1 (?), via Auto-RP
> Uptime: 00:13:47, expires: 00:02:03
>
> r3#show ip mroute
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
> R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
> X - Proxy Join Timer Running
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 224.0.1.39), 00:19:08/00:02:50, RP 0.0.0.0, flags: DJC
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse-Dense, 00:19:08/00:00:00
>
> (*, 224.0.1.40), 00:19:19/00:00:00, RP 0.0.0.0, flags: DJCL
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> Serial0, Forward/Sparse-Dense, 00:19:20/00:00:00
>
> (155.1.123.1, 224.0.1.40), 00:18:46/00:02:04, flags: PCLT
> Incoming interface: Serial0, RPF nbr 0.0.0.0
> Outgoing interface list: Null
>
> (*, 225.2.2.2), 00:03:36/00:02:23, RP 155.1.123.2, flags: SP
> Incoming interface: Serial0, RPF nbr 155.1.123.2
> Outgoing interface list: Null
>
>
>
> Jason Sinclair
> Manager, Network Support Group
> POWERTEL
> Ground Level, 55 Clarence Street,
> SYDNEY NSW 2000
> AUSTRALIA
> office: + 61 2 8264 3820
> mobile: + 61 416 105 858
> * sinclairj@powertel.com.au
>
>
>
>
> **********************************************************************
> PowerTel Limited, winners of
> Broadband Wholesale Carrier of the year, CommsWorld Telecomms Awards 2001
> Best Emerging Telco, Australian Telecom Awards 2001
>
> **********************************************************************
> This email (including all attachments) is intended solely for the named
> addressee. It is confidential and may contain commercially sensitive
> information. If you receive it in error, please let us know by reply email,
> delete it from your system and destroy any copies.
>
> This email is also subject to copyright. No part of it should be reproduced,
> adapted or transmitted without the prior written consent of the copyright own
er.
>
> Emails may be interfered with, may contain computer viruses or other defects
> and may not be successfully replicated on other systems. We give no
> warranties in relation to these matters. If you have any doubts about
> the authenticity of an email purportedly sent by us, please contact us
> immediately.
>
> **********************************************************************
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:55 GMT-3