C C N A Day2

Editor's Notes

• #6: Function POST Bootstrap
• #7: Function POST Bootstrap
• #11: Enable router to connect other devices Based on the type we have modular and non modular Non modular are fixed Modular can be added interfaces Ethernet or FA – connecting to switch Line – for the local configuration Router – console port PC- Serial Port Aux – for remote configuration using a modem BRI – for ISDN WAN connectivity Ports are numbered serially
• #12: Note: RAM—Packet buffers, running configurations, running Cisco IOS ROM—POST, ROM monitor, baby Cisco IOS (Rxboot) NVRAM—Backup configurations, config register Flash—Cisco IOS Flash memory is nonvolatile. It behaves like a file system. It is more expensive than NVRAM. It is readable and writeable. The 2500 routers run from Flash. If it is running Cisco IOS from Flash, then the Flash is in the readable state. Use the boot system command to boot Cisco IOS from a TFTP server so the 2500 can run from RAM if you need to write or erase Flash online.
• #13: Emphasize: In a later slide, there is a very detailed flowchart of the router startup process.
• #14: Rommonitor – Safe Mode Rxboot – TFTP Server Flash
• #16: Note: The 2500 series routers do not operate this way. The 2500 series routers normally run Cisco IOS from Flash. The Cisco IOS in Flash is not compressed but it is relocatable. Relocatable means the Cisco IOS image can be run from Flash or from RAM. The 2500 can run from RAM if you use the boot system tftp command to boot the Cisco IOS image. The Rxboot mode is also run from RAM on the 2500 routers.
• #17: Emphasize: Using the default config register value (0x2102), the router will load the config from NVRAM at startup.
• #32: Purpose: This slide presents the show version command. Emphasize: Point out that this command is useful when troubleshooting problems because it gives the versions of the various software components and files. It also displays how long the router has been in operation and where it obtained the image file. Config register is discussed in Chapter 6, “Catalyst Switch Operations.”
• #33: Emphasize: When you exit the setup mode, the configuration can be saved to RAM and NVRAM at the same time. Note: The Catalyst 1900 has no show start command. It automatically saves the running configuration to NVRAM.
• #34: Purpose: This slide shows the format and output of the show running-config and show startup-config commands, which display the active and backup configuration files, respectively. Emphasize: We put these two commands on the same page because it is easy to confuse the two. The show running-config command displays the configuration information in memory, while the show startup-config command displays the backup file. Often in class someone will enter commands and then say that the router did not accept them. This scenario might indicate that the person entered the commands to modify the configuration information in memory, and then entered a show startup-config (show config) to look at the backup file that has not yet been updated to reflect the changes. You must use another command to update the backup file. Default parameters do not display in the running configuration. In Cisco IOS Release 10.2 and earlier, the write terminal command shows the running configuration, and the show config command shows the startup configuration.
• #40: As its name suggests, the most common use of the show version command is to determine which version of the Cisco IOS a device is running. However, this command does much more than that—it actually offers several different uses. Let David Davis introduce you to the many uses of Cisco's show version command, and see how its output varies according to which device you're using. 1. The version of the IOS operating system 2. The version of the ROM bootstrap 3. The version of the boot loader 4. How someone last powered on the device (In addition to powering on in the usual manner, you can also power on a device with a system reset (i.e., warm reboot) or by a system panic.) 5. The time and date the system last started 6. The "uptime" for the system (i.e., how much time has passed since the last power-on) 7. The image file that the device last started (i.e., the actual path to the IOS software) 8. How much RAM the device has 9. The processor board ID, which you can use to determine the version of the device's motherboard 10. The number and type of each interface on the device (e.g., Qty 2 Ethernet, Qty 6 Serial, etc.) 11. The number of terminal lines on the router if a router has asynchronous serial lines attached 12. The amount of nonvolatile RAM (NVRAM), used to hold the SAVED version of the configuration file, also known as the startup-configuration 13. The amount and type of Flash on the device (except on a switch), used to hold the operating system when it isn't in use (Think of it as the equivalent to a hard drive on a PC.) 14. The configuration register on the device, which is a hexadecimal number used to tell the device what to do when it boots. (Typically, this only changes when you need to bypass the configuration file because of a lost password, but you can also change it for other special cases.) 15. The hostname of the device SHOW HISTORY will give all commands available in history bufer By default the buffer size is 10, this can be seen by SHOW TERMINA: Command The terminal history size can be increased by #Terminal History size 25
• #46: Connecting to the Auxiliary Port When a modem is connected to the auxiliary port, a remote user can dial in to the router and configure it. Use the light blue console cable and the DB-9-to-DB-25 connector adapter that came in the router accessory kit. To connect a modem to the router, follow these steps: Step 1- Connect the RJ-45 end of the adapter cable to the black AUX port on the router. Step 2-Connect the DB-9 end of the console cable to the DB-9 end of the modem adapter. Step 3-Connect the DB-25 end of the modem adapter to the modem.
• #51: The router Serial to serial AUI to Host Change Host name to R1 AND R2
• #55: To see the route #Show IP route
• #58: Purpose: this figure states the chapter objectives. Emphasize: Read or state each objective so each student has a clear understanding of the chapter objectives.
• #59: In internetworking , the process of moving a packet of data from source to destination . Routing is usually performed by a dedicated device called a router . Routing is a key feature of the Internet because it enables messages to pass from one computer to another and eventually reach the target machine. Each intermediary computer performs routing by passing along the message to the next computer. Part of this process involves analyzing a routing table to determine the best path. Routing is often confused with bridging, which performs a similar function. The principal difference between the two is that bridging occurs at a lower level and is therefore more of a hardware function whereas routing occurs at a higher level where the software component is more important. And because routing occurs at a higher level, it can perform more complex analysis to determine the optimal path for the packet. A routing protocol sends and receives routing information packets to and from other routers. A routed protocol can be routed by a router, which means that it can be forwarded from one router to another. Yes, there are protocols that can't be routed, such as NetBEUI (Network Basic Input Output System Extended User Interface). That a routed protocol can be routed may seem obvious, but unless you know how to differentiate it from a routing protocol, you may have trouble with the wording for some questions on the exam. A protocol is a set of rules that defines how two devices communicate with one another. It also defines the format for the packets used to transmit data over communications lines. A routed protocol contains the data elements required for a packet to be sent outside its host network or network segment. In other words, a routed protocol can be routed. Protocols used to communicate routing information between routers within an autonomous system are Interior Gateway Protocols (IGP), which are routing protocols, but not routed protocols. Routing protocols gather and share the routing information used to maintain and update routing tables. That routing information is in turn used to route a routed protocol to its final destination. Routing Information Protocol (RIP) and Interior Gateway Routing Protocol (IGRP) are the routing protocols you need to know for the exam. If you can remember what the abbreviations mean, you'll remember that they are routing protocols because they have routing in their names. Remember, too, that they are not routed protocols. In short, routed protocols route your data and routing protocols send routing updates between routers about the status of the network so that your routed protocol data can be routed. Got that? No? Well, try this to help keep it straight:
• #61: Purpose: This figure introduces students to routing. The router must accomplish the items listed in the figure for routing to occur. Emphasize: Path determination occurs at Layer 3, the network layer. The path determination function enables a router to evaluate the available paths to a destination and to establish the best path. Routing services use network topology information when evaluating network paths. This information can be configured by the network administrator (static routes) or collected through dynamic processes (routing protocols) running in the network. Transition: How do you represent the path to the packet’s destination?
• #62: Purpose: This figure explains that routers must learn about paths not directly connected. Emphasize: The router already knows about directly connected networks. It must learn about those networks not connected. This chapter describes how routers learn about those paths.
• #64: 1. Internet Control Message Protocol (ICMP) creates an echo request payload (which is just the alphabet in the data field). 2. ICMP hands that payload to Internet Protocol (IP), which then creates a packet. 3. Once the packet is created, IP determines whether the destination IP address is on the local network or a remote one. 4. Since IP determines that this is a remote request, the packet needs to be sent to the default gateway so the packet can be routed to the remote network. The Registry in Windows is parsed to find the configured default gateway. 5. The default gateway of host 172.16.10.2 (Host_A) is configured to 172.16.10.1. To be able to send this packet to the default gateway, the hardware address of the router’s interface Ethernet 0 (configured with the IP address of 172.16.10.1) must be known. 6. Next, the ARP cache is checked to see if the IP address of the default gateway has already been resolved to a hardware address: If the hardware address isn’t already in the ARP cache of the host, an ARP broadcast is sent out onto the local network to search for the hardware address of 172.16.10.1. The router responds to the request and provides the hardware address of Ethernet 0, and the host caches this address. The router also caches the hardware address of Host_A in its ARP cache. 7. Once the packet and destination hardware address are handed to the Data Link layer, the LAN driver is used to provide media access via the type of LAN being used (in this example, Ethernet). A frame is then generated, encapsulating the packet with control information. Within that frame are the hardware destination and source addresses, plus, in this case, an Ether-Type field that describes the Network layer protocol that handed the packet to the Data Link layer—in this instance, IP. At the end of the frame is something called a Frame Check Sequence (FCS) field that houses the result of the cyclic redundancy check (CRC). 8. Once the frame is completed, it’s handed down to the Physical layer to be put on the physical medium (in this example, twisted-pair wire) one bit at a time. 9. Every device in the collision domain receives these bits and builds the frame. They each run a CRC and check the answer in the FCS field. If the answers don’t match, the frame is discarded. _ If the CRC matches, then the hardware destination address is checked to see if it matches, too (which, in this example, is the router’s interface Ethernet 0). If it’s a match, then the Ether-Type field is checked to find the protocol used at the Network layer. 10. The packet is pulled from the frame, and what is left of the frame is discarded. The packet is handed to the protocol listed in the Ether-Type field—it’s given to IP. 11. IP receives the packet and checks the IP destination address. Since the packet’s destination address doesn’t match any of the addresses configured on the receiving router itself, the router will look up the destination IP network address in its routing table. 12. The routing table must have an entry for the network 172.16.20.0, or the packet will be discarded Immediately and an ICMP message will be sent back to the originating device with a “destination network unreachable” message. 13. If the router does find an entry for the destination network in its table, the packet is switched to the exit interface—in this example, interface Ethernet 1. 14. The router packet-switches the packet to the Ethernet 1 buffer. 15. The Ethernet 1 buffer needs to know the hardware address of the destination host and first checks the ARP cache. If the hardware address of Host_B has already been resolved, then the packet and the hardware address are handed down to the Data Link layer to be framed. If the hardware address has not already been resolved, the router sends an ARP request out E1 looking for the hardware address of 172.16.20.2. Host_B responds with its hardware address, and the packet and destination hardware address are both sent to the Data Link layer for framing. 16. The Data Link layer creates a frame with the destination and source hardware address, Ether-Type field, and FCS field at the end of the frame. The frame is handed to the Physical layer to be sent out on the physical medium one bit at a time. 17. Host_B receives the frame and immediately runs a CRC. If the result matches what’s in the FCS field, the hardware destination address is then checked. If the host finds a match, the Ether-Type field is then checked to determine the protocol that the packet should be handed to at the Network layer—IP, in this example. 18. At the Network layer, IP receives the packet and checks the IP destination address. Since there’s finally a match made, the protocol field is checked to find out whom the payload should be given to. 19. The payload is handed to ICMP, which understands that this is an echo request. ICMP responds to this by immediately discarding the packet and generating a new payload as an echo reply. 20. A packet is then created including the source and destination address, protocol field, and payload. The destination device is now Host_A. 21. IP then checks to see whether the destination IP address is a device on the local LAN or on a remote network. Since the destination device is on a remote network, the packet needs to be sent to the default gateway. 22. The default gateway IP address is found in the Registry of the Windows device, and the ARP cache is checked to see if the hardware address has already been resolved from an IP address. 23. Once the hardware address of the default gateway is found, the packet and destination hardware addresses are handed down to the Data Link layer for framing. 24. The Data Link layer frames the packet of information and includes the following in the header: _ The destination and source hardware address _ The Ether-Type field with 0x0800 (IP) in it _ The FCS field with the CRC result in tow 25. The frame is now handed down to the Physical layer to be sent out over the network medium one bit at a time. 26. The router’s Ethernet 1 interface receives the bits and builds a frame. The CRC is run, and the FCS field is checked to make sure the answers match. 27. Once the CRC is found to be okay, the hardware destination address is checked. Since the router’s interface is a match, the packet is pulled from the frame and the Ether-Type field is checked to see what protocol at the Network layer the packet should be delivered to. 28. The protocol is determined to be IP, so it gets the packet. IP runs a CRC check on the IP header first, and then checks the destination IP address. 29. But the router does know how to get to network 172.16.10.0—the exit interface is Ethernet 0—so the packet is switched to interface Ethernet 0. 30. The router checks the ARP cache to determine whether the hardware address for 172.16.10.2 has already been resolved. 31. Since the hardware address to 172.16.10.2 is already cached from the originating trip to Host_B, the hardware address and packet are handed to the Data Link layer. 32. The Data Link layer builds a frame with the destination hardware address and source hardware address, and then puts IP in the Ether-Type field. A CRC is run on the frame, and the result is placed in the FCS field. 33. The frame is then handed to the Physical layer to be sent out onto the local network one bit at a time. 34. The destination host receives the frame, runs a CRC, checks the destination hardware address, and looks in the Ether-Type field to find out whom to hand the packet to. 35. IP is the designated receiver, and after the packet is handed to IP at the Network layer, it checks the protocol field for further direction. IP finds instructions to give the payload to ICMP, and ICMP determines the packet to be an ICMP echo reply. 36. ICMP acknowledges that it has received the reply by sending an exclamation point (!) to the user interface. ICMP then attempts to send four more echo requests to the destination host.
• #65: The router Serial to serial AUI to Host Change Host name to R1 AND r2
• #66: The router Serial to serial AUI to Host Change Host name to R1 AND R2
• #70: Purpose: This figure describes the command syntax used to establish an IP static route. Emphasize: A static route allows manual configuration of the routing table. No dynamic changes to this table entry will occur as long as the path is active. Routing updates are not sent on a link that is only defined by a static route; hence, conserving bandwidth. The ip route field descriptions are as follows: network —Destination network or subnet mask —Subnet mask address —IP address of next-hop router interface —Name of the interface to use to get to the destination network Transition: The next figure provides a static route configuration example.
• #71: Purpose: This figure describes the command syntax used to establish an IP static route. Emphasize: A static route allows manual configuration of the routing table. No dynamic changes to this table entry will occur as long as the path is active. Routing updates are not sent on a link that is only defined by a static route; hence, conserving bandwidth. Describe the The ip route field descriptions: network—destination network or subnet mask—subnet mask address—IP address of next hop router interface—name of interface to use to get to destination network. Transition: The next figure provides a static route configuration example.
• #72: The router Serial to serial AUI to Host Change Host name to R1 AND R2
• #74: The router Serial to serial AUI to Host Change Host name to R1 AND R2
• #76: Purpose: This figure gives an example of a default route configuration. Emphasize: With an address and subnet mask of 0.0.0.0 0.0.0.0 in the ip route statement, packets for any network not listed in the routing table will be sent to the next hop, 172.16.2.2.
• #79: The router Serial to serial AUI to Host Change Host name to R1 AND r2
• #80: Purpose: This figure introduces students to routing protocols and compares routing protocols to routed protocols. Emphasize: If network 10.120.2.0 wants to know about network 172.16.2.0, it must learn it from its S0 (or possibly S1) interface. If you have100’s of routers it become difficult to configure static routes Static has less overhead,
• #83: Purpose: This figure discusses autonomous systems, IGPs and EGPs. Emphasize: Introduce the interior/exterior distinctions for routing protocols, as follows: Interior routing protocols are used within a single autonomous system Exterior routing protocols are used to communicate between autonomous systems The design criteria for an interior routing protocol require it to find the best path through the network. In other words, the metric and how that metric is used is the most important element in an interior routing protocol. Exterior protocols are used to exchange routing information between networks that do not share a common administration. IP exterior gateway protocols require the following three sets of information before routing can begin: A list of neighbor (or peer) routers or access servers with which to exchange routing information A list of networks to advertise as directly reachable The autonomous system number of the local router
• #84: Purpose: This figure introduces the three classes of routing protocols. Emphasize: There is no single best routing protocol. Note: Distance vector routing protocol operation is covered in detail later in this course. Link state and hybrid are only briefly explained after the distance vector discussion. Refer students to the ACRC to learn more about link-state and hybrid routing protocols.
• #88: Distance vector algorithms do not allow a router to know the exact topology of an internetwork. This information is somewhat same to the information found on signs at a highway intersection. A sign points toward a road leading away from the intersection and indicates the distance to the destination. Further down the highway, another sign also points toward the destination, but now the distance to the destination is shorter. Distance is interm of HOPS Vector is direction Exchange entire routing tables with all neighbors at regular intervals More BW consumed This is also know as routing by rumor
• #89: Basis for All other routing protocol Algorithm Think that you are going for a trip from Mumbai to Delhi, there are two paths one 1500 Kms and another 1200Kms The routing table contains information about two routes But there is a piece of information which tells one route is better than other, that is known as Metric
• #90: RIP uses Hop count as metric, IGRP uses Composite Metric The composite Metric are bandwidth, Delay, Load, Reliability and MTU
• #93: When Network 5 fails, Router E tells Router C. This causes Router C to stop routing to Network5 through Router E. But Routers A, B, and D don’t know about Network 5 yet, so they keep sending out update information. Router C will eventually send out its update and cause B to stop routing to Network 5, but Routers A and D are still not updated. To them, it appears that Network 5 is still available through Router B with a metric of 3. The problem occurs when Router A sends out its regular 30-second “Hello, I’m still here these are the links I know about” message, which includes the ability to reach Network 5 and now Routers B and D receive the wonderful news that Network 5 can be reached from Router A, so Routers B and D then send out the information that Network 5 is available. Any packet destined for Network 5 will go to Router A, to Router B, and then back to Router A. This is a routing loop
• #94: Layer 3 of 3 Emphasize: Layer 3 adds the final entries received some time later that have distances of 2 from routers A and C.
• #95: Slide 1 of 4 Purpose: This figure describes the first of the general problems that a distance vector protocol could face without the corrective influence of some countermeasure. Emphasize: Layer 1 shows the original state of the network and routing tables. All routers have consistent knowledge and correct routing tables. In this example, the cost function is hop count, so the cost of each link is 1. Router C is directly connected to network 10.4.0.0 with a distance of 0. Router A’s path to network 10.4.0.0 is through router B, with a hop count of 2.
• #96: Slide 2 of 4 Emphasize: In Layer 2, router C has detected the failure of network 10.4.0.0 and stops routing packets out its E0 interface. However, router A has not yet received notification of the failure and still believes it can access network 10.4.0.0 through router B. Router A’s routing table still reflects a path to network 10.4.0.0 with a distance of 2.
• #97: Slide 3 of 4 Emphasize: Because router B’s routing table indicates a path to network 10.4.0.0, router C believes it now has a viable path to 10.4.0.0 through router B. Router C updates its routing table to reflect a path to network 10.4.0.0 with a hop count of 2.
• #98: Slide 4 of 4 Emphasize: In Layer 4, router A receives the new routing table from router B, detects the modified distance vector to network 10.4.0.0, and recalculates its own distance vector to network 10.4.0.0 as 3. If all routers in an internetwork do not have up-to-date, accurate information about the state of the internetwork, they might use incorrect routing information to make a routing decision. The use of incorrect information might cause packets to take less-than-optimum paths or paths that return packets to routers that they have already visited.
• #99: Purpose: This figure describes another of the general problems that a distance vector protocol could face without the corrective influence of some countermeasure. Emphasize: Both routers conclude that the best path to network 10.4.0.0 is through each other and continue to bounce packets destined for network 10.4.0.0 between each other, incrementing the distance vector by 1 each time. This condition, called count to infinity, continuously loops packets around the network, despite the fundamental fact that the destination network 10.4.0.0 is down. While the routers are counting to infinity, the invalid information allows a routing loop to exist. A related concept is the Time-to-Live (TTL) parameter. The TTL is a packet parameter that decreases each time a router processes the packet. When the TTL reaches zero, a router discards or drops the packet without forwarding it. A packet caught in a routing loop is removed from the internetwork when its TTL expires.
• #100: Slide 4 of 4 Emphasize: In Layer 4, router A receives the new routing table from router B, detects the modified distance vector to network 10.4.0.0, and recalculates its own distance vector to network 10.4.0.0 as 3. If all routers in an internetwork do not have up-to-date, accurate information about the state of the internetwork, they might use incorrect routing information to make a routing decision. The use of incorrect information might cause packets to take less-than-optimum paths or paths that return packets to routers that they have already visited.
• #101: Purpose: This figure describes a corrective measure that attempts to solve the routing loop problems that a distance vector protocol could face. Emphasize: Routing loops occur only when routing knowledge being propagated has not yet reached the entire internetwork—when the internetwork has not converged after a change. Fast convergence minimizes the chance for a routing loop to occur, but even the smallest interval leaves the possibility open. To avoid prolonging the count-to-infinity time span, distance vector protocols define infinity as some maximum number. This number refers to a routing metric, such as a hop count. With this approach, the routing protocol permits the routing loop until the metric exceeds its maximum allowed value. This example shows this defined maximum as 16 hops. Once the metric value exceeds the maximum, network 10.4.0.0 is considered unreachable.
• #103: Purpose: This figure introduces the corrective measure known as “split horizon.” The split horizon technique attempts to solve routing loops. Emphasize: The split horizon technique attempts to eliminate routing loops and speed up convergence. The rule of split horizon is that it is never useful to send information about a route back in the direction from which the original packet came. In the example: Router C originally announced a route to network 10.4.0.0 to router B. It makes no sense for router B to announce to router C that router B has access to network 10.4.0.0 through router C. Given that router B passed the announcement of its route to network 10.4.0.0 to router A, it makes no sense for router A to announce its distance from network 10.4.0.0 to router B. Because router B has no alternative path to network 10.4.0.0, router B concludes that network 10.4.0.0 is inaccessible. In its basic form, the split-horizon technique simply omits from the message any information about destinations routed on the link. This strategy relies either on routes never being announced or on old announcements fading away through a timeout mechanism. Split horizon also improves performance by eliminating unnecessary routing updates. Under normal circumstances, sending routing information back to the source of the information is unnecessary. * Splithorizon - the routing protocol advertises routes out an interface only if they were not learned from updates entering that interface.
• #104: Split Horizon. In looking at the routing loop example, you should have noticed that Router A ultimately let Router B know about a route to network 172.16.0.0, even though it originally learned that route from Router B. Split horizon is a rule that specifies that a router can never send information about a route back to the router that originally supplied the information. Had split horizon been used in our example, Router A would not have included information about network 172.16.0.0 in its update to Router B.
• #106: Triggered Updates. Obviously the interval between routing table updates is part of the problem that leads to routing loops. Instead of relying on regular periodic updates, distance vector protocols will send out a triggered update when a metric to reach a network increases. In our example, Router C would immediately send out an update about network 172.16.0.0 not being available to Router B, who would then immediately send out an update to Router A. While triggered updates cause a little more network traffic in the short term, they go a long way towards faster convergence on a distance-vector network
• #108: When a router receives an update from a neighbor indicating that a previously accessible network isn’t working and is inaccessible, the holddown timer will start. If a new update arrives from a neighbor with a better metric than the original network entry, the holddown is removed and data is passed. But if an update is received from a neighbor router before the holddown timer expires and it has an equal or lower metric than the previous route, the update is ignored and the holddown timer keeps ticking. This allows more time for the network to stabilize before trying to converge
• #109: RIP versions 1 and 2 also use the concept of hold timers. When a destination has become unreachable (or the metric has increased enough to cause poisoning), the destination goes into "holddown". During this state, no new path will be accepted for the same destination for this amount of time. The hold time indicates how long this state should last. * Hold-down timer - After finding out that a router to a subnet has failed, a router waits a certain period of time before believing any other routing information about that subnet.
• #110: RIP uses only hop count to determine the best path to a network. If RIP finds more than one link to the same remote network with the same hop count, it will automatically perform a round-robin load balancing. RIP can perform load balancing for up to six equal-cost links (four by default). However, a problem with this type of routing metric arises when the two links to a remote network are different bandwidths but the same hop count. Figure 5.9, for example, shows two links to remote network 172.16.10.0. Since network 172.16.30.0 is a T1 link with a bandwidth of 1.544Mbps, and network 172.16.20.0 is a 56K link, you’d want the router to choose the T1 over the 56K link, right? But because hop count is the only metric used with RIP routing, the two links would be seen as being of equal cost. This little snag is called pinhole congestion .
• #114: The router Serial to serial AUI to Host Change Host name to R1 AND r2
• #116: Purpose : This figure displays the show ip route command, which displays the contents of the router’s IP routing table. Emphasize : Discuss the IP routing table in detail. Show the locations of the hop count (metric) and the administrative distance (120). Discuss the following fields: R—Refers to routes learned from RIP. via—Refers to the router that informed us about this route. 00:00:07 timer value—RIP updates are every 30 seconds. Ask, “How long until the next update?” The interfaces used for the best path
• #117: Purpose : This figure shows the debug ip rip command. Emphasize : Explain that debug commands also provide information for monitoring IP. The first highlighted line lists the source of the updates. The router returned information about two destinations. The last highlighted line shows the broadcast address to which the router sent updates.
• #118: 152-5
• #123: Purpose: This chapter introduces the Cisco IOS™ CLI on the Catalyst® 1900 switch and router. Timing: This chapter should take about 2 hours to present. Note: The Catalyst 1900 switch only has a subset of the router Cisco IOS commands available. Contents: Introduction to Cisco IOS. Explain to the student what is IOS? Cisco Device startup procedures in general. IOS configuration source. General introduction to the IOS CLI . Cat 1900 switch startup procedures. Intro to Cat 1900 CLI. This part covers the basic configuration on the switch, like setting the IP address and hostname. More details about the various Cat 1900 switch configuration commands are explained in Chapter 6 and 7. Router startup procedures. More details on the router startup process is discussed in chapter 5. Router IOS CLI.
• #124: Purpose : The figure introduces the IGRP routing protocol. IGRP is a sophisticated distance vector routing protocol. Emphasize: The Interior Gateway Routing Protocol (IGRP) is a dynamic distance-vector routing protocol designed by Cisco in the mid-1980s for routing in an autonomous system that contains large, arbitrarily complex networks with diverse bandwidth and delay characteristics. Historically, IGRP became one of the success factors for the early Cisco IOS software capabilities because of its superiority to RIP version 1. The important IGRP characteristics are as follows: More scalability than RIP Fast response to network changes Sophisticated metric Multiple-path support
• #125: Purpose : This figure presents the IGRP metric with its five possible components. Emphasize : Bandwidth and delay are the two metrics that are most commonly used. They also comprise the default metric. Note : Changing IGRP metrics can have great impact on network performance. Describe the IGRP 24-bit metric field, as follows: Bandwidth—Minimum bandwidth on the route, in kilobits per second. Delay—Route delay, in tens of microseconds. Reliability—Likelihood of successful packet transmission, expressed as an integer from 0 to 255. Loading—Effective bandwidth of path. MTU—Minimum MTU in path, expressed in bytes. The following equation calculates the metric. It is presented for instructors and is not required to be taught: metric = [k1 x bandwidth + (k2 x bandwidth) / (256 - load) + k3 x delay] If k5 does not equal 0, an additional operation is done: metric = metric x (k5/(reliability + k4)) The default constant values are k1 = k3 = 1 and k2 = k4 = k5 = 0. Again, if default values are set, metric = bandwidth + delay. The constants (k1, k2, k3) can be changed using the metric weights command. Changes to the IGRP constant values should be made with great care.
• #126: Can explain pin hole congestion how RIP and IGRP Handles (Load Balancing) IGRP – Hop count 25, default - 100
• #130: The router Serial to serial AUI to Host Change Host name to R1 AND r2