[j-nsp] Hidden routes

[Harry Reynolds]

 " So, what am I missing and that route remains hidden in the 
> Juniper1 router?
. . .
> Juniper1 has a route, learned via OSPF, to 10.10.10.1."

I would say you need an lsp between the lo0s of the two JNIs. The active
route for a vpn is normally an LSP housed in the inet.3 table. This LSP
terminates at the BGP next-hop of the PE that is advertising the L2
route. You can do this with either LDP or rsvp, or if anti-mpls, a GRE
tunnel can also tie the two PE routing instances together.

HTHs


> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net 
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of varaillon
> Sent: Tuesday, September 25, 2007 6:06 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Hidden routes
> 
> Hi,
> 
> I have a VRF between two M10 Juniper routers.
> 
> Juniper1====VRF====Juniper2
> 
> The Juniper2 router advertises a prefix (192.168.155.80/28) 
> via BGP to Juniper1.
> 
> This advertised route has the loopback (10.10.10.1) of 
> Juniper2 as next-hop in the BGP table of Juniper1.
> 
> Juniper1 has a route, learned via OSPF, to 10.10.10.1.
> 
> So, what am I missing and that route remains hidden in the 
> Juniper1 router?
> 
> Also, what would be the meaning of "Next hop type: Unusable."?
> 
> --------------------------------------------
> Juniper1# run show route hidden extensive
> 
> 192.168.155.80/28 (1 entry, 0 announced)
>   BGP    Preference: 170/-101
>          Route Distinguisher: 65001:64702
>          Next hop type: Unusable
>          Next-hop reference count: 2
>          State: <Secondary Hidden Int Ext>
>          Local AS: 65001 Peer AS: 65001
>          Age: 1:39:39    Metric: 0
>          Task: BGP_65001. 10.10.10.1+11005
>          AS path: ?
>          Communities: target: 65001:64702
>          VPN Label: 132
>          Localpref: 100
>          Router ID: 10.10.10.1
>          Primary Routing Table bgp.l3vpn.0
>          Indirect next hops: 1
>               Protocol next hop: 10.10.10.1
>               Push 132
>               Indirect next hop: 0 -
> 
> 
> Juniper1# run show route 217.69.0.11 detail
> 
> 217.69.0.11/32 (1 entry, 1 announced)
>  *OSPF   Preference: 10
>     Next-hop reference count: 9
>     Next hop: via e1-0/3/2.0, selected
>     State: <Active Int Ext>
>     Local AS: 16022
>     Age: 2d 4:55:03         Metric: 500     Tag: 0
>     Task: OSPF
>     Announcement bits (5): 0-KRT 4-Aggregate 5-Resolve tree 2 
> 6-IS-IS 8-LDP
>    AS path: I
> --------------------------------------------
> 
> Any comments would be greatly appreciated ;)
> 
> Thanks!
> 
> Christophe
> 
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>