That message typically means that the router doesn't know where to send joins upstream. Your outputs suggest that connectivity exists, but I'd check the following:
1. Verify that a unicast route to the RP exists. 2. Verify that it exists in the same routing table PIM is using (inet.0 or inet.2) 3. Verify that the upstream router is a PIM neighbor. -Dan On Wed, Apr 8, 2009 at 10:54 AM, Andrew Jimmy <[email protected]> wrote: > When will you get Upstream interface: uknown? PIM-dense-sparse mode has > already been enabled on all interfaces. All the IPs are accessible from > each > router and end clients. There is no connectivity or route reach-ability > issues between routers or multicast source/receiver. > > > > Multicast source is: 192.168.0.1 > > > > I don't know why the heck I'm getting Upstream interface Unknown on PIM > join.. > > > > Here is show multicast rpf on receiver end router: > > > > 1.1.1.1/32 > > Protocol: OSPF > > Interface: lsq-1/3/0.1 > > Neighbor: (null) > > > > 192.168.0.1/24 > > Protocol: OSPF > > Interface: lsq-1/3/0.1 > > Neighbor: (null) > > > > Here is show pim join: > > > > Group: 227.12.22.33 > > Source: * > > RP: 1.1.1.1 > > Flags: sparse,rptree,wildcard > > Upstream interface: unknown (no nexthop) > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
