User guide

Configuring IS-IS Configuring IS-IS
OmniSwitch AOS Release 7 Advanced Routing Configuration Guide March 2015 page 3-27
Configuring Access Lists
An IP access list provides a convenient way to add multiple IPv4 addresses to a route map. Using an
access list avoids having to enter a separate route map statement for each individual IP address. Instead, a
single statement is used that specifies the access list name. The route map is then applied to all the
addresses contained within the access list.
Configuring an IP access list involves two steps: creating the access list and adding IP addresses to the list.
To create an IP access list, use the ip access-list and specify a name to associate with the list. For
example,
-> ip access-list ipaddr
To add addresses to an access list, use the ip access-list address command. For example, the following
commands add addresses to an existing access list:
-> ip access-list ipaddr address 16.24.2.1/16
Use the same access list name each time the above commands are used to add additional addresses to the
same access list. In addition, both commands provide the ability to configure if an address and/or its
matching subnet routes are permitted (the default) or denied redistribution. For example:
-> ip access-list ipaddr address 16.24.2.1/16 action deny redist-control all-
subnets
For more information about configuring access list commands, see the “IP Commands” chapter in the
OmniSwitch AOS Release 7 CLI Reference Guide.
Configuring Route Map Redistribution
The ip redist command is used to configure the redistribution of routes from a source protocol into the IS-
IS destination protocol. This command is used on the IS-IS router that will perform the redistribution.
A source protocol is a protocol from which the routes are learned. A destination protocol is the one into
which the routes are redistributed. Make sure that both protocols are loaded and enabled before
configuring redistribution.
Redistribution applies criteria specified in a route map to routes received from the source protocol.
Therefore, configuring redistribution requires an existing route map. For example, the following command
configures the redistribution of RIP routes into the IS-IS network using the rip-to-isis route map:
-> ip redist rip into isis route-map rip-to-isis
RIP routes received by the IS-IS router interface are processed based on the contents of the rip-to-isis
route map. Routes that match criteria specified in this route map are either allowed or denied redistribution
into the IS-IS network. The route map may also specify the modification of route information before the
route is redistributed. See “Using Route Maps” on page 3-24 for more information.
To remove a route map redistribution configuration, use the no form of the ip redist into isis route-map
command. For example:
-> no ip redist rip into isis route-map rip-to-isis