Helpful Hints about INE’s virtual lab environment:

• Most INE Networking Labs will timeout after 55-minutes (unless otherwise specified). If you haven't completed a lab within 45-minutes, save your configurations to an external text editor, restart the lab, and then paste in your saved configs to resume where you left off.
• To access the CLI (command line interface) of any node, right-click that node and select the "console" option.
• 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.

SOLUTIONS

You would have realized right away that there was a problem when PC3 was unable to obtain an IPv4 address via DHCP. There were two problems that had to be identified and fixed in this lab.

- R3's subinterface that was designed for PC3's VLAN had the wrong VLAN tag value configured.
- Access-list 101 in router R5 had an additional line denying Ping responses from the 180.50.x.x subnet.

For more details, view the Solution Video accompanying this lab for the lab solutions and walkthrough.