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

624 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
Configuring BGP VPNs on a PE
6
Brocade(config)# lag red dynamic
Brocade(config-lag-red)# ports ethernet 1/1 to 1/2
Brocade(config-lag-red)# primary port 1/1
Brocade(config-lag-red)# ports ethernet 1/2
Brocade(config-lag-red)# deploy
Brocade(config-lag-red)# exit
Brocade(config)# interface ethernet 1/1
Brocade(config-if-e10000-1/1)# vrf forwarding VPN1
When the dynamic LAG named “red” is undeployed as shown in the following, port 1/1 remains in
the VRF routing instance named “VPN1” but port 1/2 is returned to the default VRF.
Brocade(config)# lag red dynamic
Brocade(config-lag-red)# no deploy
Setting up cooperative route filtering
Automatic route filtering in VRFs is provided through the route-target import command. By placing
this command in the VRF configuration, routes can be filtered from being imported into a given VRF.
Routes with extended community route targets matching the VRF’s import route-targets are
permitted into a VRF. Otherwise, the routes are rejected.
The cooperative route filtering feature requires that the user sets a send command on the device
that is sending the ORF, and a receive command on the device that is installing the ORF. To
configure the sending device, use the following command in the VPNv4 address family.
Brocade(config-bgp-vpnv4u)# neighbor 10.3.3.1 capability orf extended-community
send-vrf-filter
Syntax: [no] neighbor neighbor_IPaddress capability orf extended-community send-vrf-filter
To configure the peering device use the following command in the VPNv4 address family.
Brocade(config-bgp-vpnv4u)# neighbor 10.3.3.2 capability orf extended-community
receive
Syntax: [no] neighbor neighbor_IPaddress capability orf extended-community receive
Importing and exporting route maps
Route-maps configured using the route-map command can be applied to a VRF to provide filtering
of VPNv4 routes between PEs in a BGP or MPLS VPN. When a route-map is applied to a VRF, only
VPNv4 routes are filtered. Other routes such as static routes, connected routes, OSPF VRF routes,
or BGP CE side routes are not affected. Because the route map is applied to the VRF, it filters traffic
to all connected PEs. This is in contrast to applying a route-map using the BGP neighbor. In that
case, the route map applies to routes imported from or exported to the neighbor that is specified.