Tom
When I am talking about joins from directly connected interfaces, I am
talking about IGMP joins not PIM joins. It sounds like you are saying that
the RP is not connected to the LAN which is source of the IGMP joins.
Therefore unless you are using ip pim accept-rp X.X.X.X you should not
receive the output you are getting.
Are you receiving multicast traffic at the destination?
Regarding documentation
Routing TCP/IP Volume 2 by Jeff Doyle has a great chapter on Multicast.
Regards
Leon
-----Original Message-----
From: Tom Scott [mailto:telecomtom@dacor.net]
Sent: 01 March 2002 14:08
To: Leon Cozzi
Cc: cisco-nsp@puck.nether.net
Subject: RE: PIM SM rendezvous point
Leon,
In the demonstration-of-concept that we set up, there are only three
routers, with the RP in the middle, hence get RP joins from directly
connected interfaces, both of which generate the %PIM-6-INVALID_RP_JOIN
error. The two links connecting the RP to the other rtrs are p2p
serials. The explanation may be as you suggest, that one must force the
RP to forward joins to itself. If you know of any documentation on that
specific point, we would appreciate the reference.
-- thanks, TT
-------- Original Message --------
Subject: RE: PIM SM rendezvous point
Resent-Date: Fri, 1 Mar 2002 08:13:17 -0500
Resent-From: cisco-nsp@puck.nether.net
Date: Fri, 1 Mar 2002 13:04:25 -0000
From: Leon Cozzi <Leon.Cozzi@uk.didata.com>
To: "'Tom Scott'" <telecomtom@dacor.net>, cisco-nsp@puck.nether.net
Tom
You are correct when stating that the RP does not have to be configured
but
it should be configured to ensure that any joins or registers from a
directly connected LAN are forwarded to itself. In other words if the RP
receives a join from a directly connected interface it needs to be
informed
to send that join to itself.
If the RP is not directly connected to the source:
Are you using any RP filtering such as "ip pim accept-rp X.X.X.X
<access-list>" on the RP. I have seen such an error before when the
access
list in an "ip pim accept-rp" command does not allow the first hop
router to
register.
Also do you have PIM configured on all the interfaces on your RP i.e.
you
are not experiencing RPF failures?
Regards
Leon
-----Original Message-----
From: Tom Scott [mailto:telecomtom@dacor.net]
Sent: 01 March 2002 12:27
To: cisco-nsp@puck.nether.net
Subject: PIM SM rendezvous point
Multicasters,
We're trying to get PIM SM running to support enterprise-wide
conferencing, using a static rendezvous point. According to the
documentation, we shouldn't have to configure the ip pim rp-addr command
on the RP:
http://www.cisco.com/warp/public/105/48.html
"The RP discovers that it is the RP because all the other routers are
pointing to it as their RP and are subsequently sending registers to it.
"
However, we get the following error message on the RP (10.108.1.1):
00:23:26: %PIM-6-INVALID_RP_JOIN: Received (*, 239.255.80.75) Join from
10.108.1.2 for invalid RP 10.108.1.1
When we insert "ip pim rp-addr 10.108.1.1" on the RP, then the error
messages stop. Is the documenatation simply mistaken, or more likely,
are we forgetting to do something simple?
We may later configure a mapping agent with Auto-RP but for now we want
the manual control.
-- TIA, TT
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.
This footnote also confirms that this email message has been swept by
Dimension Data mail system for the presence of computer viruses.
www.uk.didata.com
**********************************************************************
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:35 EDT