Configuring BGP EVPN Route Maps
Route maps can be used in the inbound or
outbound direction for BGP peers for EVPN routes. When a route map is applied to
a BGP peer,
a ROUTE REFRESH message is sent. This results in the remote peer resending all the
EVPN
routes. If a route is already learned from a peer, the route map is applied. This
results in
the route being denied or the matching condition not being found. The learned route
is then
removed.
The following task creates a route map instance and specifies that the EVPN route type for the route map instance is 2. Only Type-2 routes are denied for the route map instance.
- Enter global configuration mode.
- Create a route map instance and allow a matching pattern.
- Permit other EVPN routes.
- Configure the route map to match
on the specified prefix.Only Type-2 routes (MAC/IP advertisement routes) are denied and all other route types (Ethernet Auto-Discovery (A-D) routes, Inclusive Multicast Ethernet Tag (IMET) routes, Ethernet Segment routes and IP Prefix route) are permitted. For full details on these EVPN routes, refer to the
match evpn-route-typecommand in the RUCKUS FastIron Command Reference.
The following example specifies that the EVPN route type for a route-map instance is 2. Only Type-2 routes are denied for the route map instance. Other EVPN routes are permitted.
device# configure terminal device(config)# route-map myroutemap deny 1 device(config)# route-map myroutemap permit 2 device(config-routemap myroutemap)# match evpn-route-type 2
The following example configures the EVPN prefix name to be used for MAC address filtering for a route map instance called "myroutemap".
device# configure terminal device(config)# ip evpn-prefix-list deny 02e0.52cb.55c8 device(config)# ip evpn-prefix-list deny 02e0.52cb.55c9 device(config)# ip evpn-prefix-list plist permit any device(config)# route-map myroutemap permit 1 device(config-routemap myroutemap)# match ip adddress evpn-prefix-list plist