Indeed, the interfaces routes from inet.0 are unknown to your new routing-instance which is as expected. You can use rib-groups (routing table groups) to import the connected interface routes into your new routing-instance.
I haven't tested the exact config below, but the concept is as follows: # define that interface routes should be processed by a new rib-group routing-options { interface-routes { rib-group inet connected; } } # define that the routes matching the new rib-groups are copied from inet.0 to your new routing-instance rib-groups connected { import-rib [ inet.0 PIPPO.0 ]; } } You may call that exporting routes but JUNOS sees it as importing routes. Guess it depends on the perspective. When you do a show you after the commit, the connected routes from inet.0 should show up in PIPPO.0 with "Primary Routing Table inet.0" if you do a "show route detail". Same route, but in a different table. Cheers Martin -----Message d'origine----- De : Bit Gossip [mailto:bit.gos...@chello.nl] Envoyé : mercredi 6 mai 2009 14:48 À : Mogensen,M,Martin,JPECS R Cc : juniper-nsp@puck.nether.net Objet : Re: [j-nsp] how to populate a forwarding routing-instance Martin, as a 'virtual-router' the protocol configuration commits correctly but still I have a little problem: to setup the BGP session, I need the connecting interface in the routing-instance PIPPO as well as in the global routing-instance for normal forwarding and this is not accepted :-( any idea how to work around that? Thanks, bit. martin.mogen...@bt.com wrote: > > Hello > > Try "instance-type virtual-router" instead of "instance-type forwarding" to > be able to support routing protocols - this way the commit should work. > "instance-type virtual-router" also support filter-based forwarding. > > Cheers > Martin > > -----Message d'origine----- > De : juniper-nsp-boun...@puck.nether.net > [mailto:juniper-nsp-boun...@puck.nether.net] De la part de Bit Gossip > Envoyé : mercredi 6 mai 2009 12:18 À : juniper-nsp Objet : [j-nsp] how > to populate a forwarding routing-instance > > Experts, > I want to configure FilterBasedForwarding and so I need a routing-instance of > type forwarding. > I have no issue to populate the routing-instance with static routes; but in > reality I would like to use bgp to populate it; and this doesn't commit. > Is it possible to use bgp for that? If not, any other way to achieve FBF > using a routing protocol rather than static for the alternate forwarding? > Thanks, > bit. > > l...@rc2# show | compare > [edit routing-instances] > + PIPPO { > + instance-type forwarding; > + router-id 1.1.1.1; > + autonomous-system 1; > + } > + protocols { > + bgp { > + group BC { > + neighbor 2.2.2.2 { > + peer-as 2; > + } > + } > + } > + } > + } > > [edit] > l...@rc2# commit check > [edit routing-instances PIPPO] > 'protocols' > Protocol BGP not allowed under forwarding (0x1) instance PIPPO > error: configuration check-out failed > > rc2# run show version > Hostname: rc2 > Model: mx480 > JUNOS Base OS boot [9.3-20090213.1] > > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp