Using an ip extcommunity variable with route map – Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) User Manual
Page 754
730
Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
BGP or MPLS VPN sample configurations
6
Using an IP extcommunity variable with route map
, the VRF named “VPN1” on PE 1 is set to import routes with RT 100:14, 100:20 and
100:80. The VRF named “VPN1” on PE 4 is configured to export routes with RT 100:20 and
100:14. The VRF named “VPN2” on PE 4 is configured to export routes with RT 100:6 and 100:20.
A route-map is configured from a BGP neighbor command on PE 1 to not install all routes from PE 4
with RT 100:6. This blocks all routes from VPN2 being sent to PE 1.
FIGURE 79
IP Extcommunity and route-map usage
The following example shows the configuration commands required on the PE 1 router for the
example shown in
. In this example, the route-map ExcludeRoute has a match
extcommunity value that references the extcommunity 20. The extended community list 20
command specifies that routes with RT 100:6 are to be denied. The neighbor route-map command
exports the ExcludeRoute route-map to the BGP neighbor PE 4. Consequently, PE 4 blocks the
export or route-target 100:6 to PE 1. This blocks all routes from VPN2 on PE 4 from being sent to PE
1.
Brocade(config)# router bgp
Brocade(config-bgp)# local-as 100
Brocade(config-bgp)# neighbor 10.22.2.1 remote-as 100
Brocade(config-bgp)# address-family vpnv4 unicast
Brocade(config-bgp-vpnv4u)# neighbor 10.22.2.1 activate
Brocade(config-bgp-vpnv4u)# neighbor 10.22.2.1 route-map in ExcludeRoute
Brocade(config-bgp-vpnv4u)# neighbor 10.22.2.1 send-community extended
Brocade(config-bgp-vpnv4u)# exit
Brocade(config)# route-map ExcludeRoute permit 10
Brocade(config-routemap ExcludeRoute)# match extcommunity 20
Brocade(config-routemap ExcludeRoute)# exit
Brocade(config)# ip extcommunity-list 20 deny RT 100:6
Brocade(config)# vrf VPN1
Brocade(config-vrf-vpn1)# rd 1:1