Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

advertise-from-main-vpn-tables

Syntax

advertise-from-main-vpn-tables;

Hierarchy Level

[edit logical-systems logical-system-name protocols bgp],[edit logical-systems logical-system-name routing-instances routing-instance-name protocols bgp],[edit protocols bgp],[edit routing-instances routing-instance-name protocols bgp],

Release Information

Statement introduced in Junos OS Release 12.3.

Description

Advertise VPN routes from the main VPN tables in the master routing instance (for example, bgp.l3vpn.0, bgp.mvpn.0) instead of advertising VPN routes from the tables in the VPN routing instances (for example, instance-name.inet.0, instance-name.mvpn.0).

When this statement is enabled, before advertising a route for a VPN prefix, the path selection algorithm is run on all routes (local and received) that have the same route distinguisher (RD).

Note: Adding or removing this statement causes all BGP sessions that have VPN address families to be removed and then added again. On the other hand, having this statement in the configuration prevents BGP sessions from going down when route reflector (RR) or autonomous system border router (ASBR) functionality is enabled or disabled on a routing device that has VPN address families configured.

Default

If you do not include this statement, VPN routes are advertised from the tables in the VPN routing instances.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Published: 2013-04-03