Nokia 7330 - Table 174 Route-Target Command

FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Private LAN Service
Issue: 13 3HH-11985-AAAA-TQZZA 279
5.16.2.49 route-target
Table 174 route-target command
Description This command binds the advertisements received with the route target (RT) that matches the
configured list (either the generic or the specified import) to a specific pw-template. If the RT list
is not present, the pw-template is used for all of them.
The pw-template-binding applies to both BGP-AD and BGP-VPLS if these features are enabled
in the VPLS.
For BGP VPLS, the following rules govern the use of PW-template:
• On transmission, the settings for the L2-Info extended community in the BGP Update are
derived from the PW-template attributes. If multiple pw-templates (with or without import-rt)
are specified for the same VPLS instance, the first pw-template entry will be used.
• On reception, the values of the parameters in te L2-Info extended community of the BGP
Update are compared with the settings from the corresponding pw-template. The following
steps are used to determine the local pw-template:
• The RT values are matched to determine the pw-template.
• If multiple pw-template matches are found from the previous steps, the first configured
pwtemplate entry will be considered.
• If the values used for Layer 2 MTU or C Flag do not match the PW, setup fails.
The tools perform commands can be used to control the application of changes in pw-template
for both BGP-AD and BGP-VPLS.
The no form of the command removes the values from the configuration.
Default none
Parameters policy-id — Specifies an existing policy ID.
split-horizon-group group-name — The specified group-name overrides the split horizon group
template settings.
Values 1..2147483647
Item Description
(2 of 2)
Item Description
Syntax route-target {ext-community|{[export ext-community][import ext-community]}}
no route-target
Context configure>service>vpls>bgp
Description This command configures the route target (RT) component that will be signaled in the related
MPBGP attribute to be used for BGP auto-discovery, BGP VPLS, and BGP Multi-Homing if
these features are configured in this VPLS service.
If this command is not used, the RT is built automatically using the VPLS ID. The ext-comm
can have the same two formats as the VPLS ID: a two-octet AS-specific extended community
and an IPv4 specific extended community.
The following rules apply:
• If BGP AD VPLS-id is configured and no RT is configured under BGP node, RT=VPLS-ID
• If BGP AD VPLS-id is not configured, an RT value must be configured under BGP node
(this is the case when only BGP VPLS is configured).
• If BGP AD VPLS-id is configured and an RT value is also configured under BGP node, the
configured RT value prevails.
(1 of 2)