Redistribution Example

Refer to Figure 10-12 for this example of route redistribution, without redundant paths, between different routing protocols.

Figure 10-12 Simple Redistribution Between RIP and EIGRP

Figure 10-12 Simple Redistribution Between RIP and EIGRP

Default a + passive

I Redistribution | of static + RIP RIP one way redistribution = no need for distribution lists

Passive EIGRP

Default a + passive

I Redistribution | of static + RIP RIP one way redistribution = no need for distribution lists

EIGRP -IP summary

RIP passive

Passive EIGRP

vV Static EIGRP

+ RIP passive \\ Default

RIP passive vV Static EIGRP

Figure 10-12 shows local offices connecting to the main office via Frame Relay. Each office has a point-to-point PVC to a router in the main office.

EIGRP is being run through the Frame Relay cloud to reduce the network overhead. The LANs are running IP for NT, and there is no need for a routing protocol to be run on the LAN segments.

RIP is being run at the main office. This is to allow the corporate servers to have an understanding of the network. The servers are UNIX systems running the ROUTED daemon. ROUTED listens only to RIP updates. Redistribution allows the servers to know about the EIGRP networks.

If the EIGRP networks need to know about each other, the RIP networks would need to be redistributed into the EIGRP environment. This is unlikely because the servers are centrally held at the main office, and there will be little lateral traffic flow. The configuration shown in Figure 10-12 is simple because there are no redundant links. The Frame Relay cloud uses point-to-point PVCs. In the future, the company may want to add redundancy by meshing the Frame Relay cloud and consolidating the three core routers into one large router. Currently the company has a simple and low-cost solution using existing equipment.

Was this article helpful?

0 0

Post a comment