Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) - Manual (Page 227)

Multi-Service IronWare Routing Configuration Guide 199
53-1003033-02
Adding additional parameters
In the following example, the first three commands configure an extended ACL that denies routes to
any 172.31.39.x destination network and allows all other routes for eligibility to be installed in the
IP route table. The last three commands change the CLI to the OSPF configuration level and
configure an OSPF distribution list that uses the ACL as input. The distribution list prevents routes
to any 172.31.39.x destination network from entering the IP route table. The distribution list does
not prevent the routes from entering the OSPF database.
Brocade(config)# ip access-list extended DenyNet39
Brocade(config-ext-nacl)# deny ip 172.31.39.0 0.0.0.255 any
Brocade(config-ext-nacl)# permit ip any any
Brocade(config)# router ospf
Brocade(config-ospf-router) # area 0
Brocade(config-ospf-router) # distribute-list DenyNet39 in
In the following example, the first command configures a numbered ACL that denies routes to any
172.31.39.x destination network and allows all other routes for eligibility to be installed in the IP
route table. The last three commands change the CLI to the OSPF configuration level and configure
an OSPF distribution list that uses the ACL as input. The distribution list prevents routes to any
172.31.39.x destination network from entering the IP route table. The distribution list does not
prevent the routes from entering the OSPF database.
Brocade(config)# ip access-list 100 deny ip 172.31.39.0 0.0.0.255 any
Brocade(config)# ip access-list 100 permit ip any any
Brocade(config)# router ospf
Brocade(config-ospf-router) # area 0
Brocade(config-ospf-router) # distribute-list 100 in
Syntax: [no] distribute-list acl-name | acl-number in
The distribute-list command is applied globally to all interfaces on the router where it is executed.
Configuring an OSPF distribution list using route maps
You can manage an OSPF Distribution List using route maps that apply match operations as
defined by an ACL or an IP prefix list. Additionally, you can also use other options available within
the route maps and ACLs to further control the contents of the routes that OSPF provides to the IP
route table. This section describes an example where an OSPF distribute list uses a route map to
specify an OSPF Admin Distance for routes identified by an IP Prefix list.
To configure an OSPF distribution list using route maps:
• Configure a route map that identifies the routes you want to manage.
• Optionally configure an OSPF Admin Distance to apply to the OSPF routes
• Configure an OSPF distribution list that uses the route map as input
Example
In the following example, the first two commands identify two routes using the ip prefix-list test1
command. Next, a route-map is created that uses the prefix-list test1 to identify the two routes and
the set distance command to set the OSPF Admin Distance of those routes to 200. A distribute-list
is then configured under the OSPF configuration that uses the route map titled “setdistance” as
input.
Brocade(config)# ip prefix-list test1 seq 5 permit 10.100.1.0/24
Brocade(config)# ip prefix-list test1 seq 10 permit 10.100.2.0/24
Brocade(config)# route-map setdistance permit 1
Brocade(config-routemap setdistance)# match ip address prefix-list test1