Allied Telesis X8100, x908 manual ACLs Path filters Prefix filters, Route maps

Models: X8100 x908

1 52
Download 52 pages 56.44 Kb
Page 45
Image 45
ACLs

ACLs

Path filters

Prefix filters

Community lists

Route maps

access-list 1 deny x.x.x.x 0.0.0.255

ip as-path access-list <aslist1> ...

... permit <reg-ex>

... deny <reg-ex>

... permit <reg-ex>

ip as-path access-list <aslist2> ...

... permit <reg-ex>

... deny <reg-ex>

ip prefix-list <plist1> ...

... permit x.x.x.x/24

... deny x.x.x.x/24

ip prefix-list <plist2> ...

... permit x.x.x.x/24

... deny x.x.x.x/24

ip community-list <clist1> ...

... deny internet

... permit noexport

Entities in the column above are the possible lists that can be a part of per-peer BGP filtering. These lists can be applied directly to a BGP peer (except for community lists) or added to a route map (middle column), which is then added to a BGP peer (last column).

Ways to use lists in IP route filtering for BGP, with generic command examples

route-map <map1> permit 1 match ip address 1

route-map <map2> deny 1 match as-path <alist2>

route-map <map3> permit 1

match ip address prefix-list <plist2>

ip route-map <map4> permit 1 match community <clist1> set comm-list <clist1> delete

bgp neighbor x.x.x.x distribute-list 1 in

bgp neighbor x.x.x.x filter-list <alist1> in

bgp neighbor x.x.x.x filter-list <alist2> out

bgp neighbor x.x.x.x prefix-list <plist1> in

bgp neighbor x.x.x.x prefix-list <plist2> out

bgp neighbor x.x.x.x route-map <map1> out

bgp neighbor x.x.x.x route-map <map2> in

bgp neighbor x.x.x.x route-map <map3> in

bgp neighbor x.x.x.x route-map <map4> out

Page 45
Image 45
Allied Telesis X8100, x908 manual ACLs Path filters Prefix filters, Route maps