Explains how to customize routes for IS-IS, including example procedures for redistributing IS-IS routes between multiple instances to support complex routing environments.
Use this task to perform route customization in IS-IS. You can inject default routes, redistribute routes from other IS-IS instances, and adjust routing preferences. Customization is optional and depends on your network design.
Procedure
| 1. | Enable IS-IS routing for a specific instance. Example:
Enables IS-IS routing for the specified routing process, and places the router in router configuration mode. By default, all IS-IS instances are automatically Level 1 and Level 2. You can change the level of routing to be performed by a particular routing instance by using the is-type command. |
|
| 2. | (Optional) Set the overload bit if needed. Example:
|
|
| 3. | Specify the address family. Example:
|
|
| 4. | (Optional) Inject a default route into the routing domain. Example:
|
|
| 5. | (Optional) Redistribute routes from one IS-IS instance into another. Example:
In this example, an IS-IS instance redistributes Level 1 routes from another IS-IS instance. |
|
| 6. | (Optional) Summarize IPv4 or IPv6 prefixes. Example:
or
|
|
| 7. | (Optional) Configure the maximum number of parallel paths allowed. Example:
Sets the maximum parallel paths in the routing table. |
|
| 8. | (Optional) Define administrative distance for IS-IS routes. You can also configure the attached bit in Level 1 LSPs. Example:
Example:
|