Helpful Hints about INE’s virtual lab environment:

• Save your configuration changes frequently in the event that you get locked out of a device or lose connectivity
• If you are suddenly logged out of the GNS3 lab environment and log back in again, you may see the prompt, “Another GNS3 instance is running, continue? (Y/N)”. Select “Yes”

• If you ever lose console access to one (or more) of your devices you will need to reboot the Ubuntu Virtual Machine that is hosting your GNS3 lab environment. To do this,

  • Minimize your GNS3 window
  • Open the “Terminal” app within the Ubuntu device

  

  • Type “reboot” within the Terminal window
  • Wait 20-30 seconds and then click the “Reconnect” option to log back in.

Lab Notes:

1. On all IOS devices (routers and switches) load the preconfiguration file from flash: memory titled, “Lab-4-Begin”.

2. Once you perform the step above the following will be preconfigured for you:

   • All IPv4 addressing on devices other than PCs as shown in the IPv4 addressing chart
   • Telnet will be preconfigured on R1 and R2
   • VLANs and 802.1q VLAN Trunks
   • Router interfaces will be administratively up.
   • Devices will have pre-configured Enable passwords of “cisco”

If you get stuck at any point during this lab and wish to view the Lab Solution, load the pre-configuration file (on any IOS device) named, “Lab-4-Solution” from flash memory.

NOTE: Please notice there has been an IPv4 addressing change for links F, G, M and N in this lab. They are now all in the same network.

Hot Standby Router Protocol (HSRP) Tasks

1. In all routers and switches, load from flash memory the saved configuration file titled, “Lab-4-Begin”.

2. onfigure PC3 with the static IPv4 address and mask of 10.10.40.4/28 and a default gateway of 10.10.40.1 (R1).

3. From PC3 ensure you can ping Switch-1 at 10.10.10.4

4. Begin your pings again from PC3 to Switch-1 but this time using the “-t” switch so that the pings will continue until you interrupt them with the “Control-C” command Ping 10.10.10.4 -t

5. While PC3 is pinging Switch-1, what do you think would happen if, in router R1, you shutdown interface Gig0/1? Try it?

   • What affect did this action have on your pings from PC3 to Switch-1?
   • Re-enable Gig0/1 in router R1.
   • Stop your pings on PC3

6. Configure HSRP on routers R1 and R2 using the following parameters:

   • HSRP should be activated on the following interfaces:
     • R1: Gig0/1
     • R2: Gig0/2
   • The HSRP Group number should be “8”
   • The HSRP virtual IP address should be the last available host address in the prefix allocated for these two interfaces.

7. Using the IOS “show standby” command, identify which router (R1 or R2) became the HSRP Active router.

8. Login to the router that is currently operating as HSRP Standby and force this router to become the HSRP Active router. You may not disable any links or reload any routers to accomplish this task.

9. Configure PC3 with the static IPv4 address and mask of 10.10.40.4/28 and a default gateway of the HSRP Virtual IP address you configured in the previous step.

10. Start a continuous ping again from PC3 to Switch-1 (10.10.10.4).

11. Login to your HSRP Active Router that was configured in Step-8.

    • Shutdown the interface on your HSRP Active router that connects downstream to Switch-2 while simultaneously monitoring the continuous pings from PC3.
    • Were any of your pings lost when you shutdown that router’s interface?
    • If any of them WERE lost, did the pings resume again at any point? How long did it take?

12. With the continuous pings still going from PC3 to Switch-1, re-enable the router’s interface that you shutdown in the previous step.

13. Once you re-enabled the router’s interface were your pings interrupted at all?