Redistribution and Route-Maps (part 1)

This post will be about redistribution and the use of route-maps to influence the redistribution process.

When companies merge, the network has to merge too. Often the networks don’t use the same routing protocols. Sometimes it’s possible to migrate a netwerk from let’s say OSPF to EIGRP, but when the company’s don’t use Cisco only, it’s is hard to migrate.

To tackle this problem it’s is possible to redistribute the OSPF routes into EIGRP and also the other way around. This means that all the routes from OSPF are known in the EIGRP cloud, and al the EIGRP routes are known in the OSPF cloud. Sometimes it is not necessary for the EIGRP cloud to know al the OSPF routes. That’s when route-maps come in. With a route-map it is possible to make sure certain routes will never get to the routing table.

In the next section a configuration example.

First have a look a the network layout:

Network Layout

Al routers have two intfaces to connect to their neighbours and one loopback interface to identify the router.
Below an example of router R3:

Interfaces R3

After that configure OSPF:

EIGRP_redistribute R3

Make sure you configure these steps on all the OSPF routers.
To make sure the configuration is correct, check if the “show ip ospf neighbours” command shows two neighbours
OSPF_neighbours R3


After configuring the correct interfaces, configure EIGRP:


The initial configuration is done. Now the redistribution part can be configured. To make redistribution possible there has to be a redistribution point, in other words, there has to be a router which has an interface (or interfaces) in the OSPF aswell as the EIGRP cloud. In this example R5 is the redistribution point.

Below an example of the redistribution between OSPF and EIGRP on R5:

OSPF_redistribute EIGRP_redistribute R3

As shown in the examples the redistribution command has some options. The default values are enough to make the redistribution work.

To make sure the redistribution works, use the command show ip route on for example router R4.

Routes R4 after redistribution

As can be seen in the above example the EIGRP routes are learned as E2 routes. To make sure the connectivity is correct, use the ping command. As can be seen in the next example, the ping command is succesfull from router R1 to router R7.



In part 2 I will describe the route-map configuration.




Good old Kron

Nowadays there are several ways to backup a Cisco router or switch configuration. Solarwinds is one of these tools, very often used by myself.
Still there are customers who don’t own one of these program’s or don’t want to invest in such a solution.
But even when a customer won’t invest in such a solution it is possible to backup your router and switch configurations. Cisco uses good old “Kron”.
Kron functions in the same way as cron on a Linux distribution. With Kron it is possible to make a (or more) scheduled event(s).
Beneath a how to:

First of all you want the startup-config to be the same as the running-config, so first create a job that writes the running-config to the startup-config

kron occurrence ; at ; recurring
policy-list ;
kron policy-list ;
cli write

Now that the startup and running-config are the same you can backup the startup-config to a tftp server

kron occurrence ; at ; recurring
policy-list ;
kron policy-list ;
cli show startup-config | redirect tftp:///;/;

With Kron it is possible to automatically write several different commando’s to a tftp server.