{"id":2175,"date":"2019-07-23T23:09:52","date_gmt":"2019-07-23T23:09:52","guid":{"rendered":"http:\/\/wiki.thomasandsofia.com\/?p=2175"},"modified":"2022-11-29T19:59:53","modified_gmt":"2022-11-29T19:59:53","slug":"section-17-dynamic-routing-protocols","status":"publish","type":"post","link":"https:\/\/wiki.thomasandsofia.com\/?p=2175","title":{"rendered":"Section 17: Dynamic Routing Protocols"},"content":{"rendered":"<p><a href=\"\/section-16-routing-fundamentals\/\">&lt; Section 16<\/a> | <a href=\"\/ccna-udemy-course-outline\/\">Home<\/a> | <a href=\"\/section-18-connectivity-troubleshooting\/\">Section 18 &gt;<\/a><\/p>\n<p>44% Complete!<\/p>\n<h1>103: Dynamic Routing Protocols &#8211; Introduction<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/course\/cisco-icnd1\/learn\/lecture\/8605430#content\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605430#overview<\/a><\/p>\n<p>Discuss different types of protocols then how different routes make it to the routing table.<\/p>\n<p>&nbsp;<\/p>\n<h1>104: Dynamic Routing Protocols vs Static Routes<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605432#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605432#overview<\/a><\/p>\n<p><a href=\"https:\/\/www.udemy.com\/course\/ccna-complete\/learn\/lecture\/7840142#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/course\/ccna-complete\/learn\/lecture\/7840142#overview<\/a><\/p>\n<p>Dynamic Routing Protocols<\/p>\n<ul>\n<li>When a routing protocol is used, routers automatically advertise their best paths to known networks to each other<\/li>\n<li>Routers use this information to determine their own best path to the known destinations.<\/li>\n<li>When the state of the network changes, such as a link going down or a new subnet being added, the routers update each other.<\/li>\n<li>Routers will automatically calculate a new best path and update the routing table if the network changes.<\/li>\n<\/ul>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2176\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1.png\" alt=\"\" width=\"569\" height=\"85\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1.png 569w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-300x45.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-150x22.png 150w\" sizes=\"auto, (max-width: 569px) 100vw, 569px\" \/><\/a><\/p>\n<ul>\n<li>R2 and R3 are not connected to 10.0.1.0\/24 nor 10.0.2.0\/24 so they are not aware of them.<\/li>\n<li>This will require configuring static routing which would require manual entries<\/li>\n<li>Or we can use dynamic routing protocols.<\/li>\n<li>We configure R1, R2 and R3 dynamically so they will share their routes with each other.\n<ul>\n<li>R1 to R2: You can access 10.0.1.0\/24 and 10.0.2.0\/24 through me.<\/li>\n<li>R2 knows this came from R1 from IP 10.0.0.1\/24<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>R2 Routing Table<\/p>\n<pre>10.0.0.0\/24 Connected FE0\/0\r\n10.1.0.0\/24 Connected FE1\/0\r\n10.0.1.0\/24 10.0.0.1 FE0\/0\r\n10.0.2.0\/24 10.0.0.1 FE0\/0<\/pre>\n<ul>\n<li>R2 now tells R3 its available networks\n<ul>\n<li>10.0.0.0\/24<\/li>\n<li>10.0.1.0\/24<\/li>\n<li>10.0.2.0\/24<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>R3 Routing Table<\/p>\n<pre>10.1.1.0\/24 Connected FE0\/0\r\n10.1.0.0\/24 Connected FE1\/0\r\n10.0.0.0\/24 10.1.0.2 FE1\/0\r\n10.0.1.0\/24 10.1.0.2 FE1\/0\r\n10.0.2.0\/24 10.1.0.2 FE1\/0<\/pre>\n<p>This also occurs in the opposite direction so R1 will learn R2&#8217;s routes and R1 and R2 will both learn R3&#8217;s routes.<\/p>\n<h2>Summary Routes<\/h2>\n<ul>\n<li>R1 can be configured to send Summary routes instead of the individual routes.\n<ul>\n<li>R1 to R2: You can access 10.0.0.0\/16 though me<\/li>\n<\/ul>\n<\/li>\n<li>Summary routes lead to less memory usage in routers as their routing tables contain less routes.<\/li>\n<li>They also lead to less CPU usage as changes in the network only affect other routers in the same area<\/li>\n<li>For example: If the link on R1 to the 10.0.11.1\/24 network goes down, R2 will lose its route there and try to compute a new path.\n<ul>\n<li>This will require cpu resources to complete this<\/li>\n<\/ul>\n<\/li>\n<li>R3 will not be affected as its summary route to 10.0.0.0\/16 is unchanged (through R2)<\/li>\n<\/ul>\n<h2>Dynamic Routing Protocols vs Static Routes<\/h2>\n<ul>\n<li>Dynamic routing protocols are more scalable than admin defined static routes.<\/li>\n<li>Using purely static routes is only feasible in very small environments.<\/li>\n<\/ul>\n<h2>Dynamic Routing Protocol Advantages<\/h2>\n<ul>\n<li>Routers automatically advertise available subnets to each other without the4 admin. having to manually enter every route on every router.<\/li>\n<li>If a subnet is added or removed, the routers will automatically discover the changes and update their routing tables.<\/li>\n<li>If the best path to a subnet goes down, routers automatically discover this and will calculate a new best path if one is available.\n<ul>\n<li>If a Static route fails, it cannot self recover, so it will require a lot of admin work again.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Dynamic Routing Protocols vs Static Routes continued<\/h2>\n<ul>\n<li>It is common to find a mix of both static and dynamic routing in the real world\n<ul>\n<li>In this case, dynamic routing carries the bulk of the network information<\/li>\n<\/ul>\n<\/li>\n<li>Static routes can be applied on an as-needed basis.\n<ul>\n<li>For example: For backup purposes or for a static route to access the Internet (which will typically be injected into the dynamic routing protocol and advertised to the rest of the routers).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1>105: Dynamic Routing Protocols Lab Demo<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605464#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605464#overview<\/a><\/p>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2177\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\" alt=\"\" width=\"724\" height=\"181\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png 724w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-300x75.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-150x38.png 150w\" sizes=\"auto, (max-width: 724px) 100vw, 724px\" \/><\/a><\/p>\n<ul>\n<li>Will be using RIP Router Information Protocol.\n<ul>\n<li>Easiest to copy common configurations into a text editor, then copy\/paste them in.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Debug Commands<\/h3>\n<ul>\n<li>Debug commands are updated in real time<\/li>\n<li>Like Show commands, Debug commands are entered at the enable prompt.<\/li>\n<\/ul>\n<h3>debug ip rip<\/h3>\n<ul>\n<li>The system starts displaying messages in real time.<\/li>\n<li>You can see both sending and receiving information from all connected routers<\/li>\n<\/ul>\n<pre>debug ip rip<\/pre>\n<p>This should work with any routing protocol<\/p>\n<pre>debug ip &lt;routing protocol&gt;<\/pre>\n<p>&nbsp;<\/p>\n<h4>Disable debugging on all protocols<\/h4>\n<pre>undebug all<\/pre>\n<h1>106: Routing Protocol Types<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605466#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605466#overview<\/a><\/p>\n<h2><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2178\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-2.png\" alt=\"\" width=\"680\" height=\"410\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-2.png 680w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-2-300x181.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-2-150x90.png 150w\" sizes=\"auto, (max-width: 680px) 100vw, 680px\" \/><\/a><\/h2>\n<h2>Routing Protocol Types<\/h2>\n<ul>\n<li>Routing protocol types can be split into two main types:\n<ul>\n<li>Interior gateway protocols (IGPs)<\/li>\n<li>Exterior gateway protocols (EGPs)<\/li>\n<\/ul>\n<\/li>\n<li>Interior gateway protocols are used for routing within an organization<\/li>\n<li>Exterior gateway protocols are used for routing between organizations over the Internet.<\/li>\n<li>The only EGP in use today is BGP (Border Gateway Protocol)<\/li>\n<\/ul>\n<h2>Interior Gateway protocols<\/h2>\n<ul>\n<li>Interior gateway protocols can be split into two main types:\n<ul>\n<li>Distance vector routing protocols<\/li>\n<li>Link State routing protocols<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Distance Vector Routing Protocols<\/h3>\n<ul>\n<li>In Distance Vector protocols, each router sends its directly connected neighbors a list of all its known networks along with its own distance to each of those networks.<\/li>\n<li>Distance vector routing protocols do not advertise the entire network topology.<\/li>\n<li>A router only knows its directly connected neighbors and the lists of networks those neighbors have advertised.\u00a0 It doesn&#8217;t have detailed topology information beyond its directly connected neighbors.<\/li>\n<li>Distance Vector routing protocols are often called &#8216;Routing by rumor&#8217;.\n<ul>\n<li>&#8220;I know of a route that has been passed along to me&#8221;<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Link State Routing Protocols<\/h3>\n<ul>\n<li>In Link State routing protocols, each router describes itself and its interfaces to its directly connected neighbors<\/li>\n<li>This information passes unchanged from one router to another.<\/li>\n<li>Every router learns the full picture of the network including every router, its interfaces and what they connect to.\n<ul>\n<li>&#8220;I know of a route, here is the exact information that was provided to me.&#8221;<\/li>\n<\/ul>\n<\/li>\n<li>While this protocol is generally more reliable, it also puts a greater strain on the routers because it stores a lot more information.<\/li>\n<\/ul>\n<h2>Commonly used routing protocols<\/h2>\n<ul>\n<li>Interior\n<ul>\n<li>Distance Vector\n<ul>\n<li>RIP: Routing Information Protocol<\/li>\n<li>EIGRP: Enhanced Interior Gateway Routing Protocol\n<ul>\n<li>Cisco proprietary<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Link State\n<ul>\n<li>OSPF: Open Shortest Path First<\/li>\n<li>IS-IS: Intermediate System &#8211; Intermediate System<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>Exterior\n<ul>\n<li>Path Vector\n<ul>\n<li>BGP: Border Gateway Protocol<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Interior Gateway Protocols<\/h2>\n<ul>\n<li>All IGPs do the same job: Advertise routes within an organization and determine the best path or paths.<\/li>\n<li>An organization will typically pick one of the IGPs<\/li>\n<li>If an organization has multiple IGPs in effect (for example, because of a merger), information can be redistributed between them.\n<ul>\n<li>This can get messy, so this should be avoided if possible.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1>107: Routing Protocol Types Lab Demo<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605470?start=0#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605470?start=0#overview<\/a><\/p>\n<h2>Comparison between Distance Vector and Link State Routing Protocols<\/h2>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2177\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\" alt=\"\" width=\"724\" height=\"181\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png 724w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-300x75.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-150x38.png 150w\" sizes=\"auto, (max-width: 724px) 100vw, 724px\" \/><\/a><\/p>\n<pre>R1#show ip protocols\r\n*** IP Routing is NSF aware ***\r\n\r\nRouting Protocol is \"rip\"\r\n...<\/pre>\n<ul>\n<li>Learned routing information is stored in the routing protocol database.\n<ul>\n<li>show ip rip database<\/li>\n<li>show ip ospf database<\/li>\n<li>&#8230;<\/li>\n<\/ul>\n<\/li>\n<li>The &#8216;best&#8217; routes are added to the Routing Table.<\/li>\n<\/ul>\n<p>With Routing Protocols, 3 things happen.<\/p>\n<ul>\n<li>Routers form an adjacency between each other<\/li>\n<li>They exchange routes with each other\n<ul>\n<li>These are stored in the Routing Protocol Database<\/li>\n<\/ul>\n<\/li>\n<li>The &#8216;best&#8217; routes are added to the Routing Table<\/li>\n<\/ul>\n<h1><\/h1>\n<h1>108: Routing Protocol Metrics<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605472#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605472#overview<\/a><\/p>\n<h2>Metric<\/h2>\n<ul>\n<li>A router may receive multiple possible paths to get to a destination network.<\/li>\n<li>Only the best path will make it into the routing table and be used<\/li>\n<li>The different IGPs use different methods to calculate the best path to a destination network..<\/li>\n<li>Each possible path will be assigned a &#8216;metric&#8217; value by the routing protocol which indicates how preferred the path is.<\/li>\n<li>The lowest metric value is preferred.\n<ul>\n<li>Distance Vector routers advertise to each other the networks they know about, and their metric to get to each of them.<\/li>\n<li>Link State routers advertise all the links in their area of the network to each other.<\/li>\n<\/ul>\n<\/li>\n<li>Each router will take this information and then make an independent calculation of its own best path to get to each destination.<\/li>\n<li>If the best path to a destination is lost (for example, a link went down) it will be removed from the routing table and replaced with the next best route if one is available.<\/li>\n<\/ul>\n<h2>RIP Metric &#8211; Hop Count<\/h2>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2177\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\" alt=\"\" width=\"724\" height=\"181\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png 724w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-300x75.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-150x38.png 150w\" sizes=\"auto, (max-width: 724px) 100vw, 724px\" \/><\/a><\/p>\n<ul>\n<li>Routing Information Protocol (Distance Vector)<\/li>\n<li>RIP uses Hop Count as the metric<\/li>\n<li>The maximum hop count by default is 15.\u00a0 Paths which are more than 15 hops away are marked as unreachable..<\/li>\n<li>Path R4 &gt; 5 &gt; 1 will be preferred for 10.0.1.0\/24 in the example above.\n<ul>\n<li>Note the links between R4-R5 and R5-R1 are 10Mbps, so this is actually a much slower route!<\/li>\n<\/ul>\n<\/li>\n<li>RIP is typically used only in small or test environments.<\/li>\n<\/ul>\n<h2>OSPF Metric &#8211; Cost<\/h2>\n<ul>\n<li>Open Shortest Path First (Link State)<\/li>\n<li>OSPF uses &#8216;cost&#8217; as the metric, which is automatically derived from interface bandwidth by default.<\/li>\n<li>You can manually configure the cost of links if you want to manipulate the path.<\/li>\n<li>Path R4 &gt; 3 &gt; 2 &gt; 1 will be preferred for 10.0.1.0\/25 in RIP example above.<\/li>\n<\/ul>\n<h2>IS-IS Metric &#8211; Cost<\/h2>\n<ul>\n<li>Intermediate System &#8211; Intermediate System (Link State)<\/li>\n<li>IS-IS uses &#8216;cost&#8217; as the metric, but it is not automatically derived from interface bandwidth.\u00a0 All links have an equal cost by default.<\/li>\n<li>You can manually configure the cost of links if you want to manipulate the path\n<ul>\n<li>You do not have this ability in RIP<\/li>\n<\/ul>\n<\/li>\n<li>If you do not manually set the link costs then the path with the lowest hop count will be used.<\/li>\n<li>Path R4 &gt; 5 &gt; 1 would be preferred for 10.0.1.0\/24 in the RIP example above.<\/li>\n<\/ul>\n<h2>EIGRP<\/h2>\n<ul>\n<li>Enhanced Interior Gateway Routing Protocol (Distance Vector)<\/li>\n<li>EIGRP uses the bandwidth and delay of links to calculate the metric.\n<ul>\n<li>Load and reliability can also be considered but are ignored by default<\/li>\n<\/ul>\n<\/li>\n<li>A fixed delay value is used based on the interface bandwidth.\u00a0 The protocol does not dynamically measure the current delay.<\/li>\n<li>You can manually configure the delay on links if you want to manipulate the path.<\/li>\n<li>Path R4 &gt; 3 &gt; 2 &gt; 1 would be preferred for 10.0.1.0\/24 in the RIP example above.<\/li>\n<\/ul>\n<h2>Choosing a Routing Protocol<\/h2>\n<ul>\n<li>RIP uses hop count and has a default maximum metric of 15.\u00a0 it is not usually used in production networks because of its scalability limitations.<\/li>\n<li>EIGRP is very easy to maintain, calculate changes quickly and its metric calculation will normally choose the best path by default.\u00a0 it is typically only supported on Cisco routers, however.<\/li>\n<li>OSPF&#8217;s metric calculation will typically choose the best path by default. it is an open standard which is supported by all routers and is the most commonly deployed IGP today.\u00a0 It is, however, more complicated to maintain than EIGRP.<\/li>\n<li>IS-IS links need to be manually configured or it will use hop count to determine the best path.\u00a0 it is typically only used in Service Provider networks or large organizations with their own MPLS network who choose it because of its scalability.<\/li>\n<\/ul>\n<h1>109: Routing Protocol Metrics Lab Demo<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605474#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605474#overview<\/a><\/p>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2177\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png\" alt=\"\" width=\"724\" height=\"181\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1.png 724w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-300x75.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-1-150x38.png 150w\" sizes=\"auto, (max-width: 724px) 100vw, 724px\" \/><\/a><\/p>\n<h2>Initial Configuration<\/h2>\n<ul>\n<li>Interfaces configured with IPs<\/li>\n<li>No routes<\/li>\n<\/ul>\n<h3>RIP Configuration<\/h3>\n<pre>configure terminal\r\nrouter rip\r\nnetwork 10.0.0.0\r\nno auto-summary<\/pre>\n<p>Path from R1 to R4 (10.1.2.0\/24) via R5<\/p>\n<pre>R   10.1.2.0\/24 [120\/2] via 10.0.3.2, 00:00:20, FastEthernet3\/0<\/pre>\n<p>Shutdown FA3\/0<\/p>\n<pre>R1(config)#int f3\/0\r\nR1(conf-if)#shutdown\r\nR1(conf-if)#end\r\nR1#show ip route\r\n...\r\nR   10.1.2.0\/24 [120\/2] via 10.0.0.2, 00:00:20, FastEthernet0\/0<\/pre>\n<h3>IS-IS<\/h3>\n<p>This isn&#8217;t tested much for CCNA because it is seldom used outside of Service Provider networks. If you study for Service Provider certification, you&#8217;ll will be tested heavily in IS-IS<\/p>\n<p>Note: Each router needs a unique net id, so R2=.0002.00, R3=.0003.00, etc.<\/p>\n<pre>configure terminal\r\nrouter isis\r\n  net 49.0001.0000.0000.0001.00\r\n!\r\ninterface f0\/0\r\n ip router isis\r\n!\r\ninterface f1\/0\r\n ip router isis\r\n!\r\ninterface f2\/0\r\n ip router isis\r\n!\r\ninterface f3\/0\r\n ip router isis<\/pre>\n<ul>\n<li>This will replace the RIP configuration in the routing table.<\/li>\n<\/ul>\n<pre>R1#show ip route\r\n...\r\ni L1   10.1.2.0\/24 [115\/2] via 10.0.3.2, 00:00:20https:\/\/www.udemy.com\/course\/ccna-complete\/learn\/lecture\/7840142#overview, FastEthernet3\/0<\/pre>\n<ul>\n<li>Same as RIP because no costs have been set on the links.<\/li>\n<\/ul>\n<p>Shutdown FA3\/0<\/p>\n<pre>R1(config)#int f3\/0\r\nR1(conf-if)#shutdown\r\nR1(conf-if)#end\r\nR1#show ip route\r\n...\r\ni l1   10.1.2.0\/24 [120\/2] via 10.0.0.2, 00:00:20, FastEthernet0\/0<\/pre>\n<h3>OSPF<\/h3>\n<pre>configure terminal\r\nrouter ospf 1\r\nnetwork 10.0.0.0.0 0.255.255.255 area 0<\/pre>\n<pre>ip show route\r\n...\r\nO        10.1.2.0\/24 [110\/4] via 10.0.0.2, 00:00:58, FastEthernet0\/0\r\ni L1  203.0.113.0\/24 [115\/30] via 10.0.3.2, 00:2:25, FastEthernet3\/0<\/pre>\n<p>* 203 route was not included in the OSPF search, so the IS-IS remained!<\/p>\n<p>Since OSPF does include speed as a cost measurement, it routed the fastest route vs. the shortest.<br \/>\nShutdown FA0\/0<\/p>\n<pre>R1(config)#int f0\/0\r\nR1(conf-if)#shutdown\r\nR1(conf-if)#end\r\nR1#show ip route\r\n...\r\nO      10.1.2.0\/24 [110\/21] via 10.0.3.2, 00:00:06, FastEthernet3\/0<\/pre>\n<h3>EIGRP<\/h3>\n<pre>router eigrp 100\r\nno auto-summary\r\nnetwork 10.0.0.0 0.255.255.255<\/pre>\n<pre>R1#show ip route\r\n...\r\nD      10.1.2.0\/24 [90\/35840] via 10.0.0.2, 00:00:11, FastEthernet0\/0<\/pre>\n<p>Shutdown FA0\/0<\/p>\n<pre>R1(config)#int f0\/0\r\nR1(conf-if)#shutdown\r\nR1(conf-if)#end\r\nR1#show ip route\r\n...\r\nD      10.1.2.0\/24 [90\/263680] via 10.0.3.2, 00:00:13, FastEthernet3\/0<\/pre>\n<h1><\/h1>\n<h1>110: Equal Cost Multi Path<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605480#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605480#overview<\/a><\/p>\n<h3>Equal Cost Multi Path (ECMP)<\/h3>\n<p>(This is really the same as load balancing)<\/p>\n<ul>\n<li>If multiple paths to a destination have an equal metric, the router will enter all of the paths into the routing table.<\/li>\n<li>ECMP will load balance the outbound traffic to the destination over the different paths.<\/li>\n<li>All IGP routing protocols will perform ECMP by default.<\/li>\n<li>EIGRP is the only routing protocol which is capable of UnEqual Cost Multi Path.\u00a0 It must be manually configured to support this.<\/li>\n<\/ul>\n<h1>111: Equal Cost Multi Path Lab Demo<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605482#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605482#overview<\/a><\/p>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-3.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2189\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-3.png\" alt=\"\" width=\"808\" height=\"211\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-3.png 808w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-3-300x78.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-3-768x201.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-3-150x39.png 150w\" sizes=\"auto, (max-width: 808px) 100vw, 808px\" \/><\/a><\/p>\n<h2>RIP Load balances R4 &gt; R1 across both routes<\/h2>\n<pre>R4#show ip route\r\n...\r\nR     10.0.1.0\/24 [120\/3] via 10.1.3.2, 00:00:04, FastEthernet2\/0\r\n                  [120\/3] via 10.1.1.2, 00:00:04, FastEthernet0\/0\r\nR     10.0.2.0\/24 [120\/3] via 10.1.3.2, 00:00:04, FastEthernet2\/0\r\n                  [120\/3] via 10.1.1.2, 00:00:04, FastEthernet0\/0<\/pre>\n<h2>OSPF only shows 1 route for R4 &gt; R1<\/h2>\n<p>Same hop count, but different costs due to speed differences.<\/p>\n<pre>R4#show ip route\r\n...\r\nO     10.0.1.0\/24 [110\/3] via 10.1.1.2, 00:00:04, FastEthernet0\/0\r\nO     10.0.2.0\/24 [110\/3] via 10.1.1.2, 00:00:04, FastEthernet0\/0<\/pre>\n<h2>OSPF load balances R4 &gt; R1<\/h2>\n<p>Edit both 10Mbps connections to be 100Mbps<\/p>\n<pre>R4#show ip route\r\n...\r\nO     10.0.1.0\/24 [110\/3] via 10.1.3.2, 00:00:04, FastEthernet2\/0\r\n                  [110\/3] via 10.1.1.2, 00:00:04, FastEthernet0\/0\r\nO     10.0.2.0\/24 [110\/3] via 10.1.3.2, 00:00:04, FastEthernet2\/0\r\n                  [110\/3] via 10.1.1.2, 00:00:04, FastEthernet0\/0<\/pre>\n<h1><\/h1>\n<h1>112: Administrative Distance<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605484#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605484#overview<\/a><\/p>\n<h4>Overview (My notes)<\/h4>\n<ul>\n<li>&#8220;How trusted is the routing protocol that provides a route&#8221;<\/li>\n<li>Used when receiving routes to the same destination via different protocols.<\/li>\n<li>Lowest # wins<\/li>\n<\/ul>\n<h2>Metric<\/h2>\n<ul>\n<li>A router will typically only learn routes to a particular destination from a single routing protocol.<\/li>\n<li>When multiple routes to a destination are learned through a routing protocol, the router will install the path or paths with the best (lowest) metric into the routing table.<\/li>\n<li>Different routing protocols use different methods to calculate the metric.\n<ul>\n<li>RIP Example:\n<ul>\n<li>Path A&gt;B&gt;C&gt;D has a hop count of 3<\/li>\n<li>Path A&gt;B&gt;D has a hop count of 2<\/li>\n<li>A&gt;B&gt;D will be used.<\/li>\n<\/ul>\n<\/li>\n<li>OSPF Example:\n<ul>\n<li>Path A&gt;B&gt;C&gt;D has a cost of 60<\/li>\n<li>Path A&gt;B&gt;D has a cost of 100<\/li>\n<li>A&gt;B&gt;C&gt;D will be used.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>Administrative Distance<\/h2>\n<ul>\n<li>If paths to the same destination are received from different routing protocols, their metrics cannot be compared.<\/li>\n<li>For example: a RIP count of 5 cannot be compared to an OSPF cost of 60.\u00a0 The comparison is meaningless because the routing protocols calculate the metric in completely different ways<\/li>\n<li>The router must use a different method to choose when routes to the same destination are received from different routing protocols.<\/li>\n<li>The Administrative Distance (AD) is used for this.<\/li>\n<li>The Administrative Distance is a measure of how trusted the routing protocol is.<\/li>\n<li>If routes to the same destination are received via different routing protocols, the protocol with the best (lowest) AD wins.<\/li>\n<\/ul>\n<table>\n<tbody>\n<tr>\n<th style=\"text-align: left;\">Route Source<\/th>\n<th>Default AD<\/th>\n<\/tr>\n<tr>\n<td>Connected Interface<\/td>\n<td>0<\/td>\n<\/tr>\n<tr>\n<td>Static Route<\/td>\n<td>1<\/td>\n<\/tr>\n<tr>\n<td>External BGP<\/td>\n<td>20<\/td>\n<\/tr>\n<tr>\n<td>EIGRP<\/td>\n<td>90<\/td>\n<\/tr>\n<tr>\n<td>OSPF<\/td>\n<td>110<\/td>\n<\/tr>\n<tr>\n<td>IS-IS<\/td>\n<td>115<\/td>\n<\/tr>\n<tr>\n<td>RIP<\/td>\n<td>120<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>&nbsp;<\/p>\n<h2>Administrative Distance and Metric<\/h2>\n<ul>\n<li>Administrative Distance is used to choose between multiple paths learned via different routing protocols.<\/li>\n<li>Metric is used to choose between multiple paths learned via. the same protocol.<\/li>\n<li>The Administrative Distance is considered first to narrow the choice down to the single best routing protocol.<\/li>\n<li>The Metric is then considered to choose the best path or paths which make it into the routing table.<\/li>\n<\/ul>\n<h2>Floating Static Routes<\/h2>\n<ul>\n<li>If the best path to a destination is lost (example, the link goes down), it will be removed from the routing table and replaced with the next best route.<\/li>\n<li>We might want to configure a static route as a backup for the route learned via a routing protocol.<\/li>\n<li>A problem is that static routes have a default Administrative Distance of 1, which will always be preferred over routes learned via an IGP.<\/li>\n<li>We can change the default AD value when setting the static route<\/li>\n<\/ul>\n<p><code>R1(config)#ip route 10.0.1.0 255.255.255 10.1.3.2 <span style=\"color: #ff0000;\">115<\/span><\/code><code><\/code><\/p>\n<ul>\n<li>Note:\n<ul>\n<li>The AD value must be higher than the IGR AD value<\/li>\n<li>You must also have a return route!<\/li>\n<li>This can also be used to set priorities in Static Routes\n<ul>\n<li><code>R1(config)#ip route 10.0.1.0 255.255.255 10.1.3.2<\/code><\/li>\n<li><code>R1(config)#ip route 10.0.1.0 255.255.255 10.2.1.2 5<\/code><code><\/code><code><\/code><\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1><\/h1>\n<h1>113: Administrative Distance Lab Demo<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605486#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605486#overview<\/a><\/p>\n<p>Nothing new here&#8230;<\/p>\n<h1><\/h1>\n<h1>114: Loopback Interfaces<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605498#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605498#overview<\/a><\/p>\n<ul>\n<li>Loopback interfaces are logical interfaces<\/li>\n<li>They allow you to assign an IP address to a router or L3 switch, which is not tied to a physical interface<\/li>\n<li>Because they don&#8217;t have any physical attributes which can fail, loopback interfaces never go down.<\/li>\n<li>Loopbacks are logical so they cannot be physically in the same subnet as other devices, so they are usually assigned a \/32 subnet mask to avoid wasting IP addresses.<\/li>\n<\/ul>\n<h2>Loopback Interface Uses<\/h2>\n<ul>\n<li>It is best practice to assign a loopback interface to your routers<\/li>\n<li>The loopback is commonly used for traffic that terminates on the router itself.<\/li>\n<li>This could be management traffic, VoIP, BGP peering, etc.<\/li>\n<li>Ths provides redundancy if there are multiple paths to the router.<\/li>\n<li>The loopback is also used to identify the router (Router ID) in OSPF.<\/li>\n<li>The same loopback interface is usually used for multiple tasks (for example management abd BGP)<\/li>\n<li>Multiple loopbacks can be configured.\u00a0 This is not common and usually only done where another, separate loopback is required for a special use case.<\/li>\n<\/ul>\n<h2>Loopback Interface Example<\/h2>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-4.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2193\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-4.png\" alt=\"\" width=\"843\" height=\"211\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-4.png 843w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-4-300x75.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-4-768x192.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-4-150x38.png 150w\" sizes=\"auto, (max-width: 843px) 100vw, 843px\" \/><\/a><\/p>\n<ul>\n<li>Access PC is on 10.1.2.0 subnet (R4) and need to connect to R1 to manage it.<\/li>\n<li>If the top path goes down you cannot connect to 10.0.0.1<\/li>\n<li>If the bottom path goes down, you cannot connect to 10.0.3.1<\/li>\n<li>Add interface Loopback 0 with IP Address 192.168.1.1\/32<\/li>\n<li>Advertise 192.168.1.1\/32 in the routing protocol<\/li>\n<li>R4 learns both paths to 192.168.1.1<\/li>\n<li>You can still connect to 192.168.1.1 even if the top or bottom path fails.<\/li>\n<\/ul>\n<h2>Loopback Interface Lab<\/h2>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-5.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2194\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-5.png\" alt=\"\" width=\"839\" height=\"218\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-5.png 839w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-5-300x78.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-5-768x200.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-5-150x39.png 150w\" sizes=\"auto, (max-width: 839px) 100vw, 839px\" \/><\/a><br \/>\nR1 Configuration<\/p>\n<pre>R1#configure terminal\r\nR1(config)#interface loopback 0\r\nR1(config-if)#\r\n192.168.1.1 255.255.255.255\r\nno shutdown<\/pre>\n<h1><\/h1>\n<h1>115: Adjacencies and Passive Interfaces<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605510#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605510#overview<\/a><\/p>\n<h2>Adjacencies<\/h2>\n<ul>\n<li>IGP routing protocols are configured under global configuration mode and enabled on individual interfaces.<\/li>\n<li>When the routing protocol is enabled on an interface, the router will look for other devices on the link which are also running the routing protocol<\/li>\n<li>The router does this by sending out and listening for hello packets.<\/li>\n<li>When a matching peer is found, the routers form an adjacency with each other.<\/li>\n<li>They then exchange routing information<\/li>\n<li>Modern routing protocols use multicast for the hello packets.<\/li>\n<li>This is more efficient than broadcast which was used by earlier protocols<\/li>\n<li>Only routers which are running the same routing protocol will process the packet.<\/li>\n<\/ul>\n<h3>Adjacency Example<\/h3>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-6.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2195\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-6.png\" alt=\"\" width=\"449\" height=\"157\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-6.png 449w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-6-300x105.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-6-150x52.png 150w\" sizes=\"auto, (max-width: 449px) 100vw, 449px\" \/><\/a><\/p>\n<ul>\n<li>The IP subnets configured on the interfaces which are enabled for the routing protocol will be included in its updates.\n<ul>\n<li>For example: R1 has a routing protocol enabled on the Loopback0 interface and FastEthernet0\/0 and 1\/0<\/li>\n<li>The routing protocol is not enabled on F2\/0<\/li>\n<li>RC belongs to a partner organization we do not want to send internal network information to.<\/li>\n<\/ul>\n<\/li>\n<li>R1 will send out and listen for hello packets on the Loopback0 interface and F0\/0 and F1\/0<\/li>\n<li>It will form adjacencies with any routers running the same protocol on those links. &#8211; RA and RB<\/li>\n<li>It will NOT send out or listen for hello packets on F2\/0<\/li>\n<li>It will NOT form an adjacency with RC<\/li>\n<li>Instead, we will use static routes for the extranet traffic with RC<\/li>\n<li>R1 will advertise IP subnets to RA and RB\n<ul>\n<li>10.0.0.0\/24<\/li>\n<li>10.0.1.0\/24<\/li>\n<li>192.168.1.1\/32<\/li>\n<\/ul>\n<\/li>\n<li>R1 will not advertise 10.0.2.0\/24<\/li>\n<li>RA and RB will not learn routes to 10.0.2.0\/24<\/li>\n<\/ul>\n<h2>Passive Interfaces<\/h2>\n<ul>\n<li>Passive Interfaces allow you to include an IP subnet in the routing protocol without sending updates out of the interface.\n<ul>\n<li>If F2\/0 is configured as a passive interface, RA and RB will learn routes to 10.0.2.0\/24, but internal network information will not be send to RC<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Loopback Passive Interfaces<\/h3>\n<ul>\n<li>It is best practice to configure loopback interfaces as Passive Interfaces.<\/li>\n<li>It is impossible to form an adjacency on a loopback interface because they are not physical interfaces.<\/li>\n<li>Making the loopback passive means that it will be advertised by the routing protocol, but will not waste resources send out and listening for hello packets.<\/li>\n<\/ul>\n<h3>Passive Interface Use Cases<\/h3>\n<ul>\n<li>Loopback interfaces<\/li>\n<li>Physical interfaces where the devices on the other side belongs to another organization.\n<ul>\n<li>We do not want to send out routing information to them.<\/li>\n<li>We do want our internal devices to know about the link.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h1><\/h1>\n<h1>116: Adjacencies and Passive interfaces Lab Demo<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605514#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605514#overview<\/a><\/p>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-7.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2197\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-7.png\" alt=\"\" width=\"846\" height=\"232\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-7.png 846w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-7-300x82.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-7-768x211.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/a1-7-150x41.png 150w\" sizes=\"auto, (max-width: 846px) 100vw, 846px\" \/><\/a><\/p>\n<h2>How to configure passive interfaces<\/h2>\n<ul>\n<li>R1 &#8211; R5 are all internal<\/li>\n<li>R6 is at a partner.\n<ul>\n<li>We do not want to form an adjacency with R6<\/li>\n<\/ul>\n<\/li>\n<li>R1-Loopback0 should also be configured as passive.<\/li>\n<\/ul>\n<h3>Starting Config<\/h3>\n<ul>\n<li>All IP interfaces configured\n<ul>\n<li>R1 Loopback0 not configured<\/li>\n<\/ul>\n<\/li>\n<li>RIP enabled on R2 &#8211; R5<\/li>\n<li>No routing protocols enabled on R1\n<ul>\n<li>R4 cannot see 10.0.1.0\/24<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Configure R1 Loopback 0<\/h3>\n<pre>R1(config)#interface loopback 0\r\nR1(config-if)#ip address 192.168.1.1 255.255.255.255\r\nR1(config-if)#no shutdown\r\nR1(configif)#exit<\/pre>\n<h3>Configure RIP on R1<\/h3>\n<pre>R1(config)#router rip\r\nR1(config-router)#version 2\r\nR1(config-router)#no auto-summary\r\nR1(config-router)#passive-interface loop0\r\nR1(config-router)#passive-interface f2\/0\r\nR1(config-router)#exit<\/pre>\n<h3>Enable RIP on the desired interfaces<\/h3>\n<pre>R1(config)#router rip\r\nR1(config-router)#network 192.168.1.1\r\nR1(config-router)#network 10.0.0.0\r\nR1(config-router)#end<\/pre>\n<p>After a few moments, RIP should propagate.<\/p>\n<h3>Verify routes can be seen on R4<\/h3>\n<pre>R4#show ip route\r\n...\r\nR      10.0.1.0\/24 [120\/2] via 10.1.3.2, 00:00:03, FastEthernet2\/0\r\nR      10.0.2.0\/24 [120\/2] via 10.1.3.2, 00:00:03, FastEthernet2\/0\r\nR      10.0.3.0\/24 [120\/2] via 10.1.3.2, 00:00:03, FastEthernet2\/0\r\n...\r\nR      192.168.1.1 [120\/2] via 10.1.3.2, 00:00:03, FastEthernet2\/0<\/pre>\n<h3>Check R6 (Partner Network) to see if it learned any routes<\/h3>\n<pre>R6#show ip route\r\n(only locally connected routes available)<\/pre>\n<h1><\/h1>\n<h1>117: Dynamic Routing Protocols &#8211; Lab Exercises<\/h1>\n<p><a href=\"https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605520#overview\" target=\"_blank\" rel=\"noopener\">https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605520#overview<\/a><\/p>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-2199\" src=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols.png\" alt=\"\" width=\"949\" height=\"508\" srcset=\"https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols.png 949w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols-300x161.png 300w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols-768x411.png 768w, https:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols-150x80.png 150w\" sizes=\"auto, (max-width: 949px) 100vw, 949px\" \/><\/a><\/p>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols-Lab-Exercise.pdf\">17 Dynamic Routing Protocols Lab Exercise<\/a><\/p>\n<p><a href=\"http:\/\/wiki.thomasandsofia.com\/wp-content\/uploads\/2019\/07\/17-Dynamic-Routing-Protocols-Answer-Key.pdf\">17 Dynamic Routing Protocols Answer Key<\/a><\/p>\n<h4>Routing Protocol Updates<\/h4>\n<p>1.Configure RIP<\/p>\n<pre>configure terminal\r\nrouter rip\r\nnetwork 10.0.0.0\r\nno auto-summary\r\nend<\/pre>\n<p>&nbsp;<\/p>\n<p>2. debug ip rip<\/p>\n<ul>\n<li>RIP: sending v1 update to 255.255.255.255 (Broadcast!)<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>3. configure terminal<br \/>\nrouter rip<br \/>\nversion 2<\/p>\n<p>&nbsp;<\/p>\n<p>4. RIP: sending v2 update to 224.0.0.9 (Multicast?)<\/p>\n<p>&nbsp;<\/p>\n<p>5. #no debug ip rip<\/p>\n<p>&nbsp;<\/p>\n<p>6. show ip route<\/p>\n<ul>\n<li>Confirmed<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p>7. These routes have the same AD\/Metric [120\/2]<\/p>\n<p>&nbsp;<\/p>\n<h4>Comparing Routing Protocols<\/h4>\n<p>8.<\/p>\n<pre>R1#show ip rip database\r\n10.0.0.0\/8    auto-summary\r\n10.0.0.0\/24    directly connected, FastEthernet0\/0\r\n10.0.1.0\/24    directly connected, FastEthernet1\/0\r\n10.0.2.0\/24    directly connected, FastEthernet2\/0\r\n10.0.3.0\/24    directly connected, FastEthernet3\/0\r\n10.1.0.0\/24\r\n    [1] via 10.0.0.2, 00:00:18, FastEthernet0\/0\r\n10.1.1.0\/24\r\n    [2] via 10.0.3.2, 00:00:15, FastEthernet3\/0\r\n    [2] via 10.0.0.2, 00:00:18, FastEthernet0\/0\r\n10.1.2.0\/24\r\n    [2] via 10.0.3.2, 00:00:15, FastEthernet3\/0\r\n10.1.3.0\/24\r\n    [1] via 10.0.3.2, 00:00:15, FastEthernet3\/0\r\n<\/pre>\n<p>9.<\/p>\n<pre>configure terminal\r\nrouter ospf 1\r\nnetwork 10.0.0.0 0.255.255.255 area 0\r\nend\r\n<\/pre>\n<p>10. No.\u00a0 OSPF has a lower Administrative Distance than RIP so it takes presidence.<\/p>\n<p>&nbsp;<\/p>\n<p>11. While that route has to identical routes per hop count, the path down F0\/0 has faster links, therefore it has a lower metric score and is the better route to use.<\/p>\n<p>&nbsp;<\/p>\n<p>12. Done.\u00a0 All routes via R1-f0\/0 (excluding 10.0.0.0\/24) will change to R1-f3\/0<\/p>\n<p>&nbsp;<\/p>\n<p>13.<\/p>\n<pre>show ip route\r\n      10.0.0.0\/8 is variably subnetted, 12 subnets, 2 masks\r\nC        10.0.0.0\/24 is directly connected, FastEthernet0\/0\r\nL        10.0.0.1\/32 is directly connected, FastEthernet0\/0\r\nC        10.0.1.0\/24 is directly connected, FastEthernet1\/0\r\nL        10.0.1.1\/32 is directly connected, FastEthernet1\/0\r\nC        10.0.2.0\/24 is directly connected, FastEthernet2\/0\r\nL        10.0.2.1\/32 is directly connected, FastEthernet2\/0\r\nC        10.0.3.0\/24 is directly connected, FastEthernet3\/0\r\nL        10.0.3.1\/32 is directly connected, FastEthernet3\/0\r\nO        10.1.0.0\/24 [110\/22] via 10.0.3.2, 00:01:42, FastEthernet3\/0\r\nO        10.1.1.0\/24 [110\/21] via 10.0.3.2, 00:01:42, FastEthernet3\/0\r\nO        10.1.2.0\/24 [110\/21] via 10.0.3.2, 00:01:42, FastEthernet3\/0\r\nO        10.1.3.0\/24 [110\/20] via 10.0.3.2, 00:01:42, FastEthernet3\/0<\/pre>\n<p>14. The routes&#8217; Metric have increased.<\/p>\n<p>&nbsp;<\/p>\n<p>15. OSPF contains data from all routers.\u00a0 RIP now only contains locally connected routes.<\/p>\n<pre>#show ip ospf database\r\n\r\nOSPF Router with ID (10.0.3.1) (Process ID 1)\r\n\r\nRouter Link States (Area 0)\r\n\r\nLink ID ADV Router Age Seq# Checksum Link count\r\n10.0.3.1 10.0.3.1 137 0x80000003 0x00A5EA 4\r\n10.1.0.2 10.1.0.2 118 0x80000002 0x002AAD 2\r\n10.1.1.2 10.1.1.2 107 0x80000003 0x00626F 2\r\n10.1.3.2 10.1.3.2 96 0x80000002 0x008A29 2\r\n203.0.113.1 203.0.113.1 97 0x80000003 0x00AA9A 3\r\n\r\n#show ip rip database\r\n10.0.0.0\/8    auto-summary\r\n10.0.0.0\/24    directly connected, FastEthernet0\/0\r\n10.0.1.0\/24    directly connected, FastEthernet1\/0\r\n10.0.2.0\/24    directly connected, FastEthernet2\/0\r\n10.0.3.0\/24    directly connected, FastEthernet3\/0<\/pre>\n<ul>\n<li>The other routers are sending their best routes?<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h4>Routing Metrics and Administrative Distance<\/h4>\n<p>16. done<\/p>\n<p>17. Yes &#8211; via R5<\/p>\n<p>18. 2<\/p>\n<p>19. R2-F0\/0 was shut down<\/p>\n<p>20.<\/p>\n<pre>R2#conf t\r\nint f0\/0\r\nno shutdown\r\n<\/pre>\n<h4><\/h4>\n<p><strong>21.\u00a0 Enter the commands below on each router to provision a basic EIGRP <\/strong><strong>configuration and enable EIGRP on every interface.<\/strong><\/p>\n<pre>conf t\r\nrouter eigrp 100\r\nno auto-summary\r\nnetwork 10.0.0.0 0.255.255.255\r\nend\r\nshow ip protocols\r\n<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>22. What do you expect to change in the routing tables?<\/strong><\/p>\n<ul>\n<li>All non-connected routes to be replaced with EIGRP routes.<\/li>\n<li>New Administrative Distances and Metrics<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>23. Verify the changes to the routeing table on R1<\/strong><\/p>\n<pre>show ip route\r\n      10.0.0.0\/8 is variably subnetted, 12 subnets, 2 masks\r\nC        10.0.0.0\/24 is directly connected, FastEthernet0\/0\r\nL        10.0.0.1\/32 is directly connected, FastEthernet0\/0\r\nC        10.0.1.0\/24 is directly connected, FastEthernet1\/0\r\nL        10.0.1.1\/32 is directly connected, FastEthernet1\/0\r\nC        10.0.2.0\/24 is directly connected, FastEthernet2\/0\r\nL        10.0.2.1\/32 is directly connected, FastEthernet2\/0\r\nC        10.0.3.0\/24 is directly connected, FastEthernet3\/0\r\nL        10.0.3.1\/32 is directly connected, FastEthernet3\/0\r\nD        10.1.0.0\/24 [90\/30720] via 10.0.0.2, 00:00:51, FastEthernet0\/0\r\nD        10.1.1.0\/24 [90\/33280] via 10.0.0.2, 00:00:11, FastEthernet0\/0\r\nD        10.1.2.0\/24 [90\/35840] via 10.0.0.2, 00:00:11, FastEthernet0\/0\r\nD        10.1.3.0\/24 [90\/261120] via 10.0.3.2, 00:00:11, FastEthernet3\/0<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>24. What is the metric to the 10.1.1.0\/24 network on R1?<\/strong><\/p>\n<ul>\n<li>33280<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>25. Why is there only one route to the 10.1.1.0\/24 network on R1?<\/strong><\/p>\n<ul>\n<li>The displayed route has a lower metric (cost) than the alternative.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>26. Disable RIP and EIGRP on R5 with the commands below.<\/strong><\/p>\n<pre>R5#\r\nconf t\r\nno router rip\r\nno router eigrp 100\r\nend\r\n<\/pre>\n<p><strong>27. Configure the network so that there is still connectivity between all <\/strong><strong>subnets if the link between R1 and R2 goes down. Accomplish this with <\/strong><strong>six commands. Do not enable EIGRP on R5 but note that the routing <\/strong><strong>protocol is expected to be enabled there in the future.<\/strong><\/p>\n<pre>R1(config)#ip route 10.1.0.0 255.255.0.0 10.0.3.2 95\r\nR2(config)#ip route 10.0.0.0 255.255.0.0 10.1.0.1 95\r\nR3(config)#ip route 10.0.0.0 255.255.0.0 10.1.1.1 95\r\nR4(config)#ip route 10.0.0.0 255.255.0.0 10.1.3.2 95\r\nR5(config)#ip route 10.0.0.0 255.255.0.0 10.0.3.1 95\r\nR5(config)#ip route 10.1.0.0 255.255.0.0 10.1.3.1 95\r\n<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>28. What changes do you expect to see to the routing table on R1?<\/strong><\/p>\n<ul>\n<li>The summary route will not be used because it has the smaller network prefix.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>29. Verify the changes to the routing table on R1.<\/strong><\/p>\n<pre>R1#show ip route\r\n\u00a0     10.0.0.0\/8 is variably subnetted, 13 subnets, 3 masks\r\nC        10.0.0.0\/24 is directly connected, FastEthernet0\/0\r\nL        10.0.0.1\/32 is directly connected, FastEthernet0\/0\r\nC        10.0.1.0\/24 is directly connected, FastEthernet1\/0\r\nL        10.0.1.1\/32 is directly connected, FastEthernet1\/0\r\nC        10.0.2.0\/24 is directly connected, FastEthernet2\/0\r\nL        10.0.2.1\/32 is directly connected, FastEthernet2\/0\r\nC        10.0.3.0\/24 is directly connected, FastEthernet3\/0\r\nL        10.0.3.1\/32 is directly connected, FastEthernet3\/0\r\nS        10.1.0.0\/16 [95\/0] via 10.0.3.2\r\nD        10.1.0.0\/24 [90\/30720] via 10.0.0.2, 00:00:31, FastEthernet0\/0\r\nD        10.1.1.0\/24 [90\/33280] via 10.0.0.2, 00:00:31, FastEthernet0\/0\r\nD        10.1.2.0\/24 [90\/35840] via 10.0.0.2, 00:00:31, FastEthernet0\/0\r\nD        10.1.3.0\/24 [90\/266240] via 10.0.0.2, 00:00:31, FastEthernet0\/0\r\n\r\n<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>30. Verify that traffic from PC1 to PC3 still goes via R2.<\/strong><\/p>\n<pre>PC1&gt;trace 10.1.2.10\r\ntrace to 10.1.2.10, 8 hops max, press Ctrl+C to stop\r\n1 10.0.1.1 28.866 ms 15.572 ms 16.134 ms\r\n2 10.0.0.2 53.690 ms 53.243 ms 47.829 ms\r\n3 10.1.0.1 100.586 ms 84.452 ms 84.980 ms\r\n4 10.1.1.1 132.316 ms 138.224 ms 116.710 ms\r\n 5 *10.1.2.10 117.202 ms (ICMP type:3, code:3, Destination port unreachable) *<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>31. Shut down interface FastEthernet 0\/0 on R2<\/strong><\/p>\n<pre>R2#conf t\r\nint f0\/0\r\nshut<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>32. What changes do you expect to see on R1\u2019s routing table?<\/strong><\/p>\n<ul>\n<li>All &#8216;D&#8217; Routes will go away<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>33. Verify the changes to the routing table on R1.<\/strong><\/p>\n<pre>R1#show ip route\r\n 10.0.0.0\/8 is variably subnetted, 9 subnets, 3 masks\r\nC 10.0.0.0\/24 is directly connected, FastEthernet0\/0\r\nL 10.0.0.1\/32 is directly connected, FastEthernet0\/0\r\nC 10.0.1.0\/24 is directly connected, FastEthernet1\/0\r\nL 10.0.1.1\/32 is directly connected, FastEthernet1\/0\r\nC 10.0.2.0\/24 is directly connected, FastEthernet2\/0\r\nL 10.0.2.1\/32 is directly connected, FastEthernet2\/0\r\nC 10.0.3.0\/24 is directly connected, FastEthernet3\/0\r\nL 10.0.3.1\/32 is directly connected, FastEthernet3\/0\r\nS 10.1.0.0\/16 [95\/0] via 10.0.3.2<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>34. Verify connectivity between PC1 and PC3.<\/strong><\/p>\n<pre>R1#ping 10.1.0.1\r\nType escape sequence to abort.\r\nSending 5, 100-byte ICMP Echos to 10.1.0.1, timeout is 2 seconds:\r\n!!!!!\r\nSuccess rate is 100 percent (5\/5), round-trip min\/avg\/max = 104\/123\/156 ms<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>35. Verify the traffic goes via R5.<\/strong><\/p>\n<pre>R1#traceroute 10.1.0.1\r\n  1 10.0.3.2 40 msec 40 msec 68 msec\r\n  2 10.1.3.1 64 msec 100 msec 72 msec\r\n  3 10.1.1.2 128 msec 156 msec 124 msec<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>36. Bring interface FastEthernet 0\/0 on R2 back up.<\/strong><\/p>\n<pre>R3#conf t\r\nint f0\/0\r\nno shutdown<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>37. Enter the commands below on R5 to provision a basic EIGRP <\/strong><strong>configuration and enable EIGRP on every interface.<\/strong><\/p>\n<pre>R5#conf t\r\nrouter eigrp 100\r\nno auto-summary\r\nnetwork 10.0.0.0 0.255.255.255<\/pre>\n<h4>Loopback Interfaces<\/h4>\n<p><strong>38. Configure loopback interface 0 on each router. Assign the IP address<\/strong><br \/>\n<strong>192.168.0.x\/32, where \u2018x\u2019 is the router number (for example<\/strong><br \/>\n<strong>192.168.0.3\/32 on R3.)<\/strong><\/p>\n<pre>R1#conf t\r\nint loopback 0\r\nip address 192.168.0.1 255.255.255.255\r\nend<\/pre>\n<p>* Note: the subnet mask must be \/32 for this to work! With \/24, it thinks the whole 192.168.0.0 network is accessible via that interface!<\/p>\n<p><strong>39. Is there connectivity to the loopback interfaces from the PCs? Why or why<\/strong><br \/>\n<strong>not?<\/strong><\/p>\n<ul>\n<li>Yes, only R1\n<ul>\n<li>PC1 uses its default gateway to reach R1&#8217;s loopback<\/li>\n<li>R1 has a route back to PC1<\/li>\n<\/ul>\n<\/li>\n<li>The others fail because the 192.168.0.0 network is not shared as part of the eigrp protocol<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>40. Enter the commands below on each router to include the loopback<\/strong><br \/>\n<strong>interfaces in EIGRP.<\/strong><\/p>\n<pre>R1#conf t\r\nrouter eigrp 100\r\nnetwork 192.168.0.0 0.0.0.255\r\nend<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>41. Verify the loopback interfaces are in the routing table on R1.<\/strong><\/p>\n<pre>R1#show ip route\r\n10.0.0.0\/8 is variably subnetted, 12 subnets, 2 masks\r\nC 10.0.0.0\/24 is directly connected, FastEthernet0\/0\r\nL 10.0.0.1\/32 is directly connected, FastEthernet0\/0\r\nC 10.0.1.0\/24 is directly connected, FastEthernet1\/0\r\nL 10.0.1.1\/32 is directly connected, FastEthernet1\/0\r\nC 10.0.2.0\/24 is directly connected, FastEthernet2\/0\r\nL 10.0.2.1\/32 is directly connected, FastEthernet2\/0\r\nC 10.0.3.0\/24 is directly connected, FastEthernet3\/0\r\nL 10.0.3.1\/32 is directly connected, FastEthernet3\/0\r\nD 10.1.0.0\/24 [90\/30720] via 10.0.0.2, 00:20:01, FastEthernet0\/0\r\nD 10.1.1.0\/24 [90\/33280] via 10.0.0.2, 00:19:38, FastEthernet0\/0\r\nD 10.1.2.0\/24 [90\/35840] via 10.0.0.2, 00:19:38, FastEthernet0\/0\r\nD 10.1.3.0\/24 [90\/261120] via 10.0.3.2, 00:19:43, FastEthernet3\/0\r\n192.168.0.0\/32 is subnetted, 5 subnets\r\nC 192.168.0.1 is directly connected, Loopback0\r\nD 192.168.0.2 [90\/156160] via 10.0.0.2, 00:00:40, FastEthernet0\/0\r\nD 192.168.0.3 [90\/158720] via 10.0.0.2, 00:00:53, FastEthernet0\/0\r\nD 192.168.0.4 [90\/161280] via 10.0.0.2, 00:01:07, FastEthernet0\/0\r\nD 192.168.0.5 [90\/386560] via 10.0.3.2, 00:01:27, FastEthernet3\/0<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>42. Verify connectivity from PC1 to the loopback interface on R5.<\/strong><\/p>\n<pre>PC1&gt; ping 192.168.0.5\r\n84 bytes from 192.168.0.5 icmp_seq=1 ttl=254 time=48.353 ms\r\n84 bytes from 192.168.0.5 icmp_seq=2 ttl=254 time=61.039 ms\r\n84 bytes from 192.168.0.5 icmp_seq=3 ttl=254 time=62.501 ms\r\n84 bytes from 192.168.0.5 icmp_seq=4 ttl=254 time=46.874 ms\r\n84 bytes from 192.168.0.5 icmp_seq=5 ttl=254 time=62.498 ms<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>43. Enter the command below to verify that R1 has established EIGRP<\/strong><br \/>\n<strong>adjacencies with R2 and R5.<\/strong><\/p>\n<pre>R1#show ip eigrp neighbors\r\nEIGRP-IPv4 Neighbors for AS(100)\r\nH   Address                 Interface              Hold Uptime   SRTT   RTO  Q  Seq\r\n                                                   (sec)         (ms)       Cnt Num\r\n1   10.0.3.2                Fa3\/0                    10 00:26:17   52   312  0  31\r\n0   10.0.0.2                Fa0\/0                    12 00:26:35   60   360  0  31<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>44. Verify that traffic from R5 to the directly connected interfaces on R1 goes<\/strong><br \/>\n<strong>via the FastEthernet 3\/0 interface.<\/strong><\/p>\n<pre>R5#traceroute 10.0.2.1\r\nType escape sequence to abort.\r\nTracing the route to 10.0.2.1\r\nVRF info: (vrf in name\/id, vrf out name\/id)\r\n1 10.0.3.1 64 msec 32 msec 44 msec<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>45. Enter the commands below to configure the loopback interface and the<\/strong><br \/>\n<strong>link to R5 as passive interfaces on R1.<\/strong><\/p>\n<pre>R1#conf t\r\nrouter eigrp 100\r\npassive-interface loopback0\r\npassive-interface fastethernet3\/0<\/pre>\n<p>&nbsp;<\/p>\n<p><strong>46. What changes do you expect to see in the routing table on R5 and why?<\/strong><\/p>\n<ul>\n<li>R5 should lose routes to 10.0.2.0\/24 and 10.0.1.0\/24<\/li>\n<li>Wrong!\u00a0 R5 now routes those via R4!\u00a0 Cool!<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>47. Verify the expected changes to the routing table on R5.<\/strong><\/p>\n<pre>R5#show ip route\r\n10.0.0.0\/8 is variably subnetted, 10 subnets, 2 masks\r\n<strong>D 10.0.0.0\/24 [90\/266240] via 10.1.3.1, 00:05:11, FastEthernet2\/0<\/strong>\r\n<strong>D 10.0.1.0\/24 [90\/268800] via 10.1.3.1, 00:05:11, FastEthernet2\/0<\/strong>\r\n<strong>D 10.0.2.0\/24 [90\/268800] via 10.1.3.1, 00:05:11, FastEthernet2\/0<\/strong>\r\nC 10.0.3.0\/24 is directly connected, FastEthernet3\/0\r\nL 10.0.3.2\/32 is directly connected, FastEthernet3\/0\r\nD 10.1.0.0\/24 [90\/263680] via 10.1.3.1, 00:05:11, FastEthernet2\/0\r\nD 10.1.1.0\/24 [90\/261120] via 10.1.3.1, 01:30:16, FastEthernet2\/0\r\nD 10.1.2.0\/24 [90\/261120] via 10.1.3.1, 01:30:16, FastEthernet2\/0\r\nC 10.1.3.0\/24 is directly connected, FastEthernet2\/0\r\nL 10.1.3.2\/32 is directly connected, FastEthernet2\/0\r\n192.168.0.0\/32 is subnetted, 5 subnets\r\nD 192.168.0.1 [90\/394240] via 10.1.3.1, 00:05:11, FastEthernet2\/0\r\nD 192.168.0.2 [90\/391680] via 10.1.3.1, 00:05:11, FastEthernet2\/0\r\nD 192.168.0.3 [90\/389120] via 10.1.3.1, 01:11:27, FastEthernet2\/0\r\nD 192.168.0.4 [90\/386560] via 10.1.3.1, 01:11:41, FastEthernet2\/0\r\nC 192.168.0.5 is directly connected, Loopback0<\/pre>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&lt; Section 16 | Home | Section 18 &gt; 44% Complete! 103: Dynamic Routing Protocols &#8211; Introduction https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605430#overview Discuss different types of protocols then how different routes make it to the routing table. &nbsp; 104: Dynamic Routing Protocols vs Static Routes https:\/\/www.udemy.com\/cisco-icnd1\/learn\/lecture\/8605432#overview https:\/\/www.udemy.com\/course\/ccna-complete\/learn\/lecture\/7840142#overview Dynamic Routing Protocols When a routing protocol is used, routers automatically advertise ..<\/p>\n<div class=\"clear-fix\"><\/div>\n<p><a href=\"https:\/\/wiki.thomasandsofia.com\/?p=2175\" title=\"read more...\">Read more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,74,45],"tags":[],"class_list":["post-2175","post","type-post","status-publish","format-standard","hentry","category-ccent","category-ccna","category-icnd1-ccent"],"_links":{"self":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/2175","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2175"}],"version-history":[{"count":31,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/2175\/revisions"}],"predecessor-version":[{"id":2182,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=\/wp\/v2\/posts\/2175\/revisions\/2182"}],"wp:attachment":[{"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2175"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2175"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wiki.thomasandsofia.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2175"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}