auto-export
Syntax
auto-export {
disable;
family inet {
disable;
flow {
disable;
rib-group rib-group;
}
multicast {
disable;
rib-group rib-group;
}
unicast {
disable;
rib-group rib-group;
}
}
family inet6 {
disable;
multicast {
disable;
rib-group rib-group;
}
unicast {
disable;
rib-group rib-group;
}
}
family iso {
disable;
unicast {
disable;
rib-group rib-group;
}
}
traceoptions {
file filename <files number> <size maximum-file-size> <world-readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
}
}
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options], [edit logical-systems logical-system-name routing-options], [edit routing-instances routing-instance-name routing-options], [edit routing-options]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Export routes between routing instances.
This statement enables you to leak routes between VPN routing and forwarding (VRF) instances that are locally configured on a provider edge (PE) router. Auto export is always applied on the local PE router, because it applies to only local prefix leaking by evaluating the export policy of each VRF and determining which route targets can be leaked. The standard VRF import and export policies affect remote PE prefix leaking.
To enable auto-export functionality, you need to configure auto-export on both export and import routing instance to leak routes from export routing instance to import routing instance.
We recommend you to consider your design requirements because when you add
auto-export on the import routing instance, the import routing instance also exports
its own routes to other routing instance with same import route-targets (RT), which
leads to unwanted route leaks. To prevent unwanted route leaks, use the
vrf-export statement at [edit
routing-instances] hierarchy level to manipulate route-targets attached
to the routes.
You can use this statement as an alternative to using the VRF import and export policies.
Default
auto-export is disabled by default. If you want to export routes
between routing instances, include the auto-export CLI statement at
the [edit routing-options] or at the [edit routing-instances
routing-instance-name routing-options] hierarchy levels. You
can use the show route export CLI command to verify the route
export information.
Options
family—Address family.
inet—IP version 4 (IPv4) address family.
multicast—Multicast routing information.
unicast—Unicast routing information.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.