Helpful Hints about INE’s virtual lab environment:

• When you start the lab, if you see a message about "Another instance of GNS3 is running" just select "YES".
• 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.

In this lab you will gain experience with the various methods available to inject local prefixes into the BGP table and advertise them to BGP peers.

• The last octet of the IPv4 address of each interface ends with the value of the router's name. For example, the Gig0/0 interface on R6 is addressed with 22.6.22.6 while Gig0/4 on R2 is 22.6.22.2. You will only use a limited subset of this topology for this lab.
• Each device has a Loopback0 interface pre-configured with x.x.x.x as its IPv4 address where "x.x.x.x" corresponds to the Router's name. For example, Loopback0 on R7 is 7.7.7.7 whereas Loopback0 on R2 is 2.2.2.2.

NOTE: Any preconfigured enable passwords on IOS devices will be "INE"