Resolving problems with multiple-point two-way routing republishing: routing pruning

Source: Internet
Author: User
Tags config

Let's see where we're going to use the bidirectional redistribution of routes.

Scene One: The company has 2 technical directors, respectively, management Headquarters and division, the level is similar, director a thinks my side of the router performance is poor, with RIP protocol is enough to use. The head of headquarters thinks that OSPF is better than OSPF. Because of disagreements that led to the division using RIP and the headquarters using OSPF, there is a need to use a two-way redistribution of routes to solve the problem of a company using 2 different routing protocols

Scenario two: For companies of larger size, the acquisition of another company, because the original company used the OSPF protocol, and the acquisition of the company is using the EIGRP protocol, in order to prevent the redeployment of the network caused by network disruption, which leads to the integration of 2 of the network between companies need to use the two-way redistribution of the route

Scenario Three: This is a bit more biased, perhaps for business reasons, the company ran a rip on some UNIX or Linux protocol, for docking the other network of the company to carry out the route to redistribute (this is not very common)

There are 4 ways to redistribute a route:

Single-point bi-directional re-publishing

Single-point one-way re-publishing

Multiple-point one-way republishing

Multi-point re-publishing

This blog post analyzes and solves some of the problems arising from multiple-point bidirectional republishing

First set up the entire required environment (configuration interface address, enable routing these migrant-level configuration in order not to waste the layout will not be posted,)

Bidirectional redistribution of RIP and OSPF on R1

R1 (config) #router rip

R1 (config-router) #redistribute OSPF 1 metric 1 #注意在RIP和EIGRP这些距离矢量型的路由协议中重发布其它路由协议时一定要加上metric, the default is infinity if not added, Redistribution to rip should be noted not to be greater than 15 because the maximum number of RIP hops is 16

R1 (config) #router OSPF 1

R1 (config-router) #redistribute RIP subnets

The same is true of R3.

R3 (config) #router rip

R3 (config-router) #redistribute OSPF 1 metric 1

R3 (config) #router OSPF 1

R3 (config-router) #redistribute RIP subnets

Review the routing table for each router after republishing

R1 routing Table

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.