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