VPN Routing/Forwarding (VRF) Instance Configuration
The following steps are needed for VRF instance configurations:
-
Define VRF instances on PE nodes
-
Associate VRF instances with router interfaces
-
Set up routes to PE/CE nodes.
Note: These routes can be static routes or generated by routing protocols
-
Configure BGP neighbors
Defining VRF Tables
The first step in configuring a VRF instance in a network model is to define the VRF tables on each of the PE nodes in the network. Procedure 88 describes how to do this.
Procedure 88: Defining VRF Tables on PE Nodes
-
Open the Attributes dialog box for the PE node.
-
Configure the VRF tables in the VPN > Network Based > VRF Instances attribute. This compound attribute lets you specify the route distinguisher, route target, and import and export policies for each VRF on the node.
-
Close the Attributes dialog box by clicking OK.
End of Procedure 88
Associating VRF Tables with Interfaces
After you have defined the VRF tables on the PE nodes, you must associate the tables with individual router interfaces.
Procedure 89: Associating VRF Tables with Individual Interfaces
-
Open the Attributes dialog box for the PE node.
-
Set the Routing Instance (IP > IP Routing Parameters > Interface Information > Routing Instance) attribute to the appropriate VRF table defined in Procedure 88.
-
Close the Attributes dialog box by clicking OK.
End of Procedure 89
Configuring Routes to PE and CE Nodes
Next you must configure routes to the PE and CE nodes. You can configure these routes in two ways: static routes and routing protocols. See "IP" for information on configuring static routes and routing protocols.
Configuring BGP Neighbors
For BGP neighbors, you need to configure the neighboring nodes to recognize each other as neighbors and thus share routes. This is typically done between all of the PE nodes. See "BGP" for more information on configuring BGP neighbors.
When using BGP-MPLS VPNs, you must also configure the Send-Community attribute on all PE neighbor connections to ensure that DES and Flow Analysis work properly. DES and Flow Analysis explicitly check the value of this attribute to determine whether to keep or strip the route target extended communities from the BGP update.