Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 647)

Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide 623
53-1003031-02
Configuring BGP VPNs on a PE
6
The import parameter specifies that routes with route-target extended community attributes
matching the specified route-target variable can be imported into the VRF where this command is
configured.
The export parameter specifies the route-target extended community attributes that are attached
to routes export from the specified VRF.
The both parameter specifies that both the import and export values apply to the specified
route-target variable for the VRF where this command is configured. This is the default state. It
applies when no specific value for this parameter is set.
The route-target variable specifies a target VRF extended community. Like a route distinguisher, it
is either AS-relative or IP address-relative.
Assigning a VRF routing instance to an interface
Once a VRF routing instance is defined, it must be assigned to one or more virtual or physical
interfaces on a PE.
To assign the VRF named VPN1 to Ethernet interface 1/1, enter the following commands.
Brocade(config)# interface ethernet 1/1
Brocade(config-if-e10000-1/1)# vrf forwarding VPN1
Syntax: [no] vrf forwarding vrf-name
The vrf-name variable is the name of the VPN that the interface is being assigned to.
Assigning a VRF routing instance to a LAG interface
A VRF routing instance can be assigned to a dynamic LAG interface. To assign a VRF routing
instance to a LAG the following rules must be observed:
• The dynamic LAG must be configured before assigning any of its ports to a non-default VRF
routing instance.
• Before deployment of the dynamic LAG all members of the LAG must be in the default VRF
routing instance.
• After the LAG is deployed, the primary port can be assigned to a non-default VRF routing
instance.
• Once the dynamic LAG is deployed, all ports are in the LACP_BLOCK state until the LACP
protocol can negotiate with the other end. Once the negotiation with the other end is
completed, all the LAP ports are set to the FORWARD state.
• When the Dynamic LAG is undeployed, the primary port stays in the VRF that it was assigned to
but all secondary ports moves back to the default VRF.
The following configuration creates a dynamic LAG named “red” and assigns port 1/1 as the
primary port and port 1/2 as a secondary port. The LAG is deployed and the primary port (1/1) is
assigned to the VRF routing instance named “VPN1”. All ports in the LAG named “red” are then
assigned to the VRF routing instance named “VPN1”.