Use this command to add or delete entries in the import and export lists for route target extended communities for a specified VPN VRF.
| vrf_name | Specifies the name of a VPN VRF. |
| import | Specifies that the specified route target extended community is to be added to or deleted from the import list for the VRF. |
| export | Specifies that the specified route target extended community is to be added to or deleted from the export list for the VRF. |
| both | Specifies that the specified route target extended community is to be added to or deleted from both the import and export lists for the VRF. |
| add | Specifies that the specified route target extended community is to be added to the specified list for the VRF. |
| delete | Specifies that the specified route target extended community is to be deleted from the specified list for the VRF. |
| route_target_extended_community | Specifies the route target extended community. It can be represented in two formats: ASN-related or IP-Address-related. |
No default route targets. If you do not specify the import or export options at the CLI, by default both is assumed.
This command creates lists of import and export route target extended communities for the specified VRF. Route Target attributes are used to control the VPNv4 route distribution by BGP. Learned routes (from the PE) that carry a specific route target extended community are imported into all VRFs configured with that extended community as an import target. Routes learned from a VRF site are labeled with export route target extended communities configured for that VRF. This is used to control the VRFs into which the route is imported.
A route target extended community can be specified in the following formats:
To configure multiple route target extended communities in import or export lists, execute this command with add option multiple times, once for each extended community. Use the delete option to remove an extended community from an import or export list. You cannot use this command for a heavy-weight traditional VR.
The following examples configure route target extended communities using the two supported formats:
configure vr corporate-extreme route-target both add 172.16.186.230:9823 configure vr corporate-guest route-target both add 9643:7002
This command was first available in ExtremeXOS 15.3.
This command is available on BlackDiamond8900 xl- and xm-series modules and Summit X460, X480, X670, and X770 switches.
Print
this page
Email this topic
Feedback
View PDF
Download EPUB