255.255.255.248 128.103.35.18 router rip
redistribute static
default metric 1 Web Links Redistributing Between Classful and Classless Protocols
http://www.cisco.com/en/US/tech/tk365/
technologies_tech_note09186a0080093fd9
.shtml#ospf_longer
Content 5.2 Configuring and Verifying Router Redistribution 5.2.4 Redistributing Routes into a Classless Routing Protocol Figure displays how to configure redistribution from EIGRP AS 100 into OSPF. The router ospf 1 command is used to access OSPF routing process 1 into which routes need to be redistributed. The redistribute command then specifies the routing protocol to be redistributed into OSPF. In this case, it is the EIGRP routing process for AS 100. Figure lists the syntax of the OSPF redistribute command. Figure displays the command parameters. Redistribution into OSPF can also be limited to a defined number of prefixes by the redistribute maximum-prefix maximum [threshold] [warning-only] router configuration command. The threshold parameter defaults to logging a warning at 75 percent of the defined maximum value configured. After reaching the defined maximum number, no further routes are redistributed. If the warning-only parameter is configured, no limitation is placed on redistribution. The maximum value number simply becomes a second point where another warning message is logged. This command was introduced in Cisco IOS Software Release 12.0(25)S and was integrated into Cisco IOS Software Release 12.2(18)S, 12.3(4)T, and later. Web Links RIP and OSPF Redistribution
http://www.cisco.com/univercd/cc/
td/doc/cisintwk/idg4/nd2014.htm
Content 5.2 Configuring and Verifying Router Redistribution 5.2.5 Redistributing Routes into OSPF Example In Figure , the default metric of 20 for OSPF is being used, and the metric type is set to external 1. This setting means that the metric increases in increments whenever updates are passed through the network. The command contains the subnets option, which causes the subnets to be redistributed.
Content 5.2 Configuring and Verifying Router Redistribution 5.2.6 Redistributing Routes into EIGRP Figure displays how to configure redistribution from OSPF into EIGRP AS 100. The router eigrp 100 command is used to access the routing process into which routes need to be redistributed. The redistribute command then specifies the routing protocol to be redistributed into EIGRP AS 100. In this case, it is OSPF routing process 1. Note
When you are redistributing a static or connected route into EIGRP, the default metric is equal to the metric of the associated interface. Figure lists the syntax of the EIGRP redistribute command. Figure displays the command parameters.
Content 5.2 Configuring and Verifying Router Redistribution 5.2.7 Redistributing Routes into EIGRP Example In Figure , routes from OSPF process number 1 are redistributed into EIGRP AS 100. In this case, a metric is specified to ensure that routes are redistributed. The redistributed routes appear in the table of router B as external EIGRP (D EX) routes. External EIGRP routes have a higher administrative distance of 170 than internal EIGRP (D) routes, so internal EIGRP routes are preferred over external EIGRP routes.
Content 5.2 Configuring and Verifying Router Redistribution 5.2.8 Redistributing Routes into IS-IS Figure displays the syntax and how to configure redistribution from EIGRP AS 100 into IS-IS. The router isis command is used to access the routing process into which routes need to be redistributed. The redistribute command specifies the routing protocol to be redistributed into IS-IS. In this case, it is the EIGRP routing process for AS 100. Figure displays the command parameters. When redistributing IS-IS routes into other routing protocols, you can include Level 1, Level 2, or both Level 1 and Level 2 routes. The output in Figure shows the parameters available for choosing these routes. If a level is not specified, all routes are redistributed. You can also limit redistribution into IS-IS to a defined number of prefixes by using the redistribute maximum-prefix maximum [threshold] [warning-only | withdraw] router configuration command. The threshold parameter defaults to logging a warning at 75 percent of the defined maximum value configured. After reaching the defined maximum number, no further routes are redistributed. The optional withdraw parameter also causes IS-IS to rebuild link-state protocol data units (PDUs), which are link-state packets, without the external (redistributed) IP prefixes. If the warning-only parameter is configured, no limitation is placed on redistribution. The maximum value number simply becomes a second point where another warning message is logged. This command was introduced in Cisco IOS Software Release 12.0(25)S and was integrated into Cisco IOS Software Releases 12.2(18)S, 12.3(4)T, and later.
Content 5.2 Configuring and Verifying Router Redistribution 5.2.9 Redistributing Routes into IS-IS Example In Figure , routes are redistributed from EIGRP AS 100 into IS-IS on router A. No metric is given, so these routes have a seed metric of 0. A level type is not given, so the routes are redistributed as Level 2 routes (as displayed in the router B routing table).
Content 5.2 Configuring and Verifying Router Redistribution 5.2.10 Redistributing Static and Connected Routes Along with redistributing routing information between IGPs, it is sometimes necessary to redistribute static route information. For example, in Figure a default static route has been configured on router RTX to reach router RTA, and router RTA has been configured with a static route to reach the 172.16.1.0 LAN network on router RTX. To update other routers connected to router RTA about the route to 172.16.1.0, router RTA must be configured to redistribute static routes into RIP. The redistribute static command tells RIP to import the static routes into RIP and advertise them as part of a RIP update. Note
The passive-interface command is covered in the next lesson. To redistribute directly connected routes, it may also be necessary to use the redistribute connected command. Redistributing directly connected networks into routing protocols is not a common practice; however, it can be done.
Content 5.2 Configuring and Verifying Router Redistribution 5.2.11 Verifying Route Redistribution Figure shows the network of a hypothetical company. The network begins with two routing domains, or autonomous systems, one using OSPF and one using RIP version 2 (RIPv2). Router B is the boundary router. It connects directly to one router within each routing domain and runs both protocols. Router A is in the RIP domain and is advertising subnets 10.1.0.0, 10.2.0.0, and 10.3.0.0 to router B. Router C is in the OSPF domain and is advertising subnets 10.8.0.0, 10.9.0.0, 10.10.0.0, and 10.11.0.0 to router B. Router B’s configuration is shown in the figure. RIP is required to run on the serial 1 interface only. Therefore, the passive-interface command is given for interface serial 2. The passive-interface command prevents RIP from sending route advertisements out that interface. OSPF is configured on serial 2. Figure displays the routing tables of routers A, B, and C. Each routing domain is separate, and routers within them recognize routes that are communicated from their own routing protocols only. The only router with information on all the routes is router B, which is the boundary router that runs both routing protocols and connects to both routing domains.
The goal is for all routers to