[j-nsp] PIM-SM / registor / ISIS

[bert.todts at alcatel.be]

Yes ,
This unicast route is or ISIS learned or OSPF learned  ( I even configured
this RP address as an static route and it didn't help ).
Bert

Leonard Giuliano wrote:

> Bert- do you have a unicast route for the RP address?  Can you ping it?
>
> -Lenny
>
> On Tue, 4 Mar 2003 bert.todts at alcatel.be wrote:
>
> -)
> -) Did anybody encountered following problem ?
> -)
> -) -I am using Junos 5.5R1.2 and I am SDR  and not RP for a PIM_SM domain.
> -) -I was using ospf as IGP and every things worked fine.
> -) -The RP is static configured.
> -) -Now I am switched to ISIS and  I am not sending registor msg's and the
> -) multicast route stays as mdiscard in the routing table.
> -) -show multicast route shows  IfMismatch increasing.
> -) -Source @ip is direct connected.
> -) -Rp @IP is known in routing table.
> -)
> -) Bert
> -)
> -) run show multicast route extensive
> -)  Family: INET
> -) Group           Source prefix     Act Pru NHid  Packets    IfMismatch
> -) Timeout
> -) 227.1.1.1       70.70.70.2     /32 A   P  0     0
> -) 9450       170
> -)     Upstream interface: local
> -)     Session name: Unknown
> -)     Forwarding rate: 0 kBps (0 pps)
> -)
> -) inet.1: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
> -)
> -)
> -) 227.1.1.1.70.70.70.2/64 (1 entry, 1 announced)
> -) TSI:
> -) KRT in-kernel 227.1.1.1.70.70.70.2/64 -> {mdiscard}
> -)         *PIM    Preference: 105
> -)                 Next hop type: Multicast (IPv4)
> -)                 State: <Active Int>
> -)                 Age: 3:53
> -)                 Task: PIM.master
> -)                 Announcement bits (1): 0-KRT
> -)
> -)
> -) _______________________________________________
> -) juniper-nsp mailing list juniper-nsp at puck.nether.net
> -) http://puck.nether.net/mailman/listinfo/juniper-nsp
> -)
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp