 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
Configuring a VRF target community using the vrf-target statement causes default VRF import and export policies to be generated that accept and tag routes with the specified target community. You can still create more complex policies by explicitly configuring VRF import and export policies. These policies override the default policies generated when you configure the vrf-target statement.
If you do not configure the import and export options of the vrf-target statement, the specified community string is applied in both directions. The import and export keywords give you more flexibility, allowing you to specify a different community for each direction.
The syntax for the VRF target community is not a name. You must specify it in the format target:x:y. A community name cannot be specified because this would also require you to configure the community members for that community using the policy-options statement. If you define the policy-options statements, then you can just configure VRF import and export policies as usual. The purpose of the vrf-target statement is to simplify the configuration by allowing you to configure most statements at the [edit routing-instances] hierarchy level.
To configure a VRF target, include the vrf-target statement:
-
vrf-target community;
You can include the vrf-target statement at the following hierarchy levels:
An example of how you might configure the vrf-target statement follows:
- [edit routing-instances sample]
- vrf-target target:69:102;
To configure the vrf-target statement with the export and import options, include the following statements:
-
vrf-target {
- export community-name;
- import community-name;
- }
You can include the vrf-target statement at the following hierarchy levels:
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |