[j-nsp] Routing-policy - import route into routing-instance

[Matt Levine]

I'm doing this with rib-groups, example:

routing-options {
	carrier-rg {
    		import-rib [ inet.0 carrier.inet.0 ];
	}
}

protocols {
	bgp {
		group foo {
			family inet {
				unicast {
					rib-group carrier-rg;
				}
			}
			import carrier-in;
		}
	}
}

policy-options {
	policy-statement carrier-in {
		term instance {
			to rib carrier.inet.0;
			then {
				local-preference 190;
				accept;
			}
		}
		term default {
			then {
				local-preference 300;
				accept;
			}
		}
	}
}


Hope that's insightful.

Matt

		


> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
> bounces at puck.nether.net] On Behalf Of Sykes, Phil
> Sent: Thursday, October 14, 2004 4:28 AM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Routing-policy - import route into routing-instance
> 
> 
> Hi Folks,
> 
>  I'd like to be able to use routing-policy to import a route from BGP into
> a
> particular routing-instance, based on community, e.g.
> 
> protocols {
> 	bgp {
> 		group foo {
> 			import move-to-instance;
> 		}
> 	}
> }
> 
> policy-options {
> 	policy-statement move-to-instance {
> 		from {
> 			community instance-community;
> 		}
> 		then {
> 			routing-instance different-instance;
> 			^^^^^^^^^^^^^^^^ (this command doesn't exist)
> 		}
> 	}
> }
> 
> routing-instances {
>     different-instance {
>         instance-type forwarding;
>     }
> }
> 
>  I can't import this route via 'instance-import' in routing-instances,
> because it is not (and must not be) the selected route in the router's
> master routing-instance RIB (any way round that also gratefully received
> :-)
> 
> The BGP neighbor that the route is coming from does not necessarily
> support
> multiple routing tables, and needs to be sending routes into the master
> routing-instance.
>  I don't really want to import routes into the different-instance, and
> then
> export them into the master routing-instance, although I recognise that
> might be one way of doing it.
> 
> Cheers,
> 
> Phil
> 
> --
> Phil Sykes, Senior Network Engineer
> IP Engineering, Cable & Wireless Network Services
> p: +49 89 92699 204  m: +49 172 89 79 727  aim: philsykesatcw
> 
> This e-mail has been scanned for viruses by the Cable & Wireless e-mail
> security system - powered by MessageLabs. For more information on a
> proactive managed e-mail security service,  visit
> http://www.cw.com/uk/emailprotection/
> 
> The information contained in this e-mail is confidential and may also be
> subject to legal privilege. It is intended only for the recipient(s) named
> above. If you are not named above as a recipient, you must not read, copy,
> disclose, forward or otherwise use the information contained in this
> email. If you have received this e-mail in error, please notify the sender
> (whose contact details are above) immediately by reply e-mail and delete
> the message and any attachments without retaining any copies.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp