[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Flow-Specification Routes for Layer 3 VPNs

The VPN compares the route target extended community in the NLRI to the import policy. If there is a match, the VPN can start using the flow routes to filter and rate-limit packet traffic. Received flow routes are installed into the flow routing table instance-name.inetflow.0.

Flow routes can also be propagated throughout a VPN network and shared among VPNs, providing filter and rate-limiting capabilities.

To enable MP-BGP to carry flow-specification NLRI for the inet-vpn address family, include the flow statement at the [edit protocols bgp group group-name family inet-vpn] hierarchy level:




flow;

Note: VPN flow routes are supported for the default instance only. Instance type is configured by including the instance-type statement at the [edit routing-instance instance-name] hierarchy level.

Flow routes configured for VPNs with family inet-vpn are not automatically validated, so the no-validate statement is not supported at the [edit protocols bgp group group-name family inet-vpn] hierarchy level.

For more information on flow routes, see Configuring a Flow Route and the Internet draft draft-marques-idr-flow-spec-02.txt, Dissemination of Flow Specification Rules.

[Contents] [Prev] [Next] [Index] [Report an Error]