Configuring Dynamic BGP VPNv6 Flow Specification

Dynamic BGP VPNv6 Flow Specification allows BGP VPNv6 Flow Specification routes to be transmitted and traffic filtering policies to be generated. The policies improve security of devices in VPNs.

Usage Scenario

When deploying dynamic BGP VPNv6 Flow Specification, a BGP VPNv6 Flow Specification peer relationship needs to be established between the traffic analysis server and each ingress of the network to transmit BGP VPNv6 Flow Specification routes.

In an AS with multiple ingresses, a BGP Flow route reflector (Flow RR) can be deployed to reduce the number of BGP VPNv6 Flow Specification peer relationships and save CPU resources.

Pre-configuration Tasks

Before configuring dynamic BGP VPNv6 Flow Specification, configure BGP peers.

Procedure

Establish a BGP VPNv6 Flow Specification peer relationship.
1. Run system-view
  The system view is displayed.
2. Run bgp as-number
  The BGP view is displayed.
3. Run peer ipv4-address as-number as-number
  An IP address and AS number are specified for the peer.
4. Run ipv6-flow vpnv6
  The BGP-Flow VPNv6 address family is enabled, and its view is displayed.
5. Run peer ipv4-address enable
  A BGP VPNv6 Flow Specification peer relationship is established.
6. Run commit
  The configuration is committed.
(Optional) Configure a Flow RR.
1. Run system-view
  The system view is displayed.
2. Run bgp as-number
  The BGP view is displayed.
3. Run ipv6-flow vpnv6
  The BGP-Flow VPNv6 address family is enabled, and its view is displayed.
4. Run peer ipv4-address reflect-client
  The device is configured as a flow RR, and the specified peer is configured as a client.
  
  The router on which the peer reflect-client command is run functions as a flow RR. The network ingress and traffic analysis server need to be configured as clients of the flow RR.
5. (Optional) Run undo reflect between-clients
  Route reflection between clients through the flow RR is disabled.
  
  If the clients of a flow RR have established full-mesh connections with each other, you can run the undo reflect between-clients command on the flow RR to disable route reflection between clients through the RR to reduce the cost.
6. (Optional) Run reflector cluster-id { cluster-id-value | cluster-id-ipv4 }
  A cluster ID is configured for the flow RR.
  
  If a cluster has multiple flow RRs, you need to run this command to set the same cluster ID for these RRs.
  
  The reflector cluster-id command is applicable only to flow RRs.
7. Run commit
  The configuration is committed.
(Optional) Disable BGP FlowSpec protection.
1. Run system-view
  The system view is displayed.
2. Run flowspec protocol-protect { ipv4 | ipv6 } disable
  BGP FlowSpec protection is disabled.
3. Run commit
  The configuration is committed.

Checking the Configurations

Run the following commands to check the previous configuration.

Run the display bgp flow vpnv6 all peer [ [ ipv4-address ] verbose ] command to check information about all BGP VPN IPv6 Flow Specification and BGP VPNv6 Flow Specification peers.
Run the display bgp flow vpnv6 { all | route-distinguisher route-distinguisher } routing-table [ reindex ] command to check information about all BGP VPN IPv6 Flow Specification and BGP VPNv6 Flow Specification routes or about the BGP VPN IPv6 Flow Specification and BGP VPNv6 Flow Specification routes with a specified RD.
Run the display bgp flow vpnv6 { all | route-distinguisher route-distinguisher } routing-table statistics command to check statistics about all BGP VPN IPv6 Flow Specification and BGP VPNv6 Flow Specification routes or about the BGP VPN IPv6 Flow Specification and BGP VPNv6 Flow Specification routes with a specified RD.
Run the display flowspec ipv6 rule reindex-value slot slot-id command to check information about combined rules in the BGP IPv6 Flow Specification route rule table.
Run the display flowspec ipv6 rule statistics slot slot-id command to check statistics about the rules for BGP IPv6 Flow Specification routes to take effect.