{
    "id": "fde5530a-f87b-4bee-b9b1-bc9d48480331",
    "name": "IPv6 Addressing, OSPFv2 & Access Control Lists",
    "slug": "ipv6-addressing-ospfv2-access-control-lists",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "9581c375-e70d-4e54-a425-51a05c02157a"
        ],
        "pta_sdn": "256",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-15T21:01:55.104126Z",
    "modified": "2023-10-03T18:59:11.952699Z",
    "is_beta": false,
    "lab_objectives": [],
    "main_learning_area": "e73fd5a8-2ead-4159-9a25-38b50ad4ab20",
    "learning_areas": [
        {
            "id": "e73fd5a8-2ead-4159-9a25-38b50ad4ab20",
            "name": "Networking",
            "slug": "networking"
        }
    ],
    "categories": [],
    "tags": [],
    "difficulty": null,
    "is_web_access": false,
    "is_lab_experience": false,
    "is_featured": false,
    "cve": null,
    "severity": null,
    "year": null,
    "external_url": "",
    "solution_video": null,
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Day-3-Lab/diagram.png)\n\n\n**Helpful Hints about INE\u2019s virtual lab environment:**\n\n- Save your configuration changes frequently in the event that you get locked out of a device or lose connectivity\n- If you are suddenly logged out of the GNS3 lab environment and log back in again, you may see the prompt, \u201cAnother GNS3 instance is running, continue? (Y/N)\u201d.  Select \u201cYes\u201d\n- 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,\n    - Minimize your GNS3 window\n    - Open the \u201cTerminal\u201d app within the Ubuntu device\n\n    ![description](https://assets.ine.com/content/labs/networking-labs/Day-3-Lab/terminal.png)\n\n    - Type \u201creboot\u201d within the Terminal window\n    - Wait 20-30 seconds and then click the \u201cReconnect\u201d option to log back in.\n\n**Lab Notes:**\n\n1. On all IOS devices (routers and switches) load the preconfiguration file from flash: memory titled, \u201c**Lab-3-Begin**\u201d.\n\n2. Once you perform the step above the following will be preconfigured for you:\n    - All IPv4 addressing on devices other than PCs as shown in the IPv4 addressing chart\n    - Telnet will be preconfigured on R1 and R2\n    - VLANs and 802.1q VLAN Trunks\n    - Router interfaces will be administratively up.\n    - Devices will have pre-configured Enable passwords of \u201ccisco\u201d\n\nIf 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, \u201c***Lab-3-Solution***\u201d from flash memory.",
    "description_html": "<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Day-3-Lab/diagram.png\" /></p>\n<p><strong>Helpful Hints about INE\u2019s virtual lab environment:</strong></p>\n<ul>\n<li>Save your configuration changes frequently in the event that you get locked out of a device or lose connectivity</li>\n<li>If you are suddenly logged out of the GNS3 lab environment and log back in again, you may see the prompt, \u201cAnother GNS3 instance is running, continue? (Y/N)\u201d.  Select \u201cYes\u201d</li>\n<li>\n<p>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,</p>\n<ul>\n<li>Minimize your GNS3 window</li>\n<li>Open the \u201cTerminal\u201d app within the Ubuntu device</li>\n</ul>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Day-3-Lab/terminal.png\" /></p>\n<ul>\n<li>Type \u201creboot\u201d within the Terminal window</li>\n<li>Wait 20-30 seconds and then click the \u201cReconnect\u201d option to log back in.</li>\n</ul>\n</li>\n</ul>\n<p><strong>Lab Notes:</strong></p>\n<ol>\n<li>\n<p>On all IOS devices (routers and switches) load the preconfiguration file from flash: memory titled, \u201c<strong>Lab-3-Begin</strong>\u201d.</p>\n</li>\n<li>\n<p>Once you perform the step above the following will be preconfigured for you:</p>\n<ul>\n<li>All IPv4 addressing on devices other than PCs as shown in the IPv4 addressing chart</li>\n<li>Telnet will be preconfigured on R1 and R2</li>\n<li>VLANs and 802.1q VLAN Trunks</li>\n<li>Router interfaces will be administratively up.</li>\n<li>Devices will have pre-configured Enable passwords of \u201ccisco\u201d</li>\n</ul>\n</li>\n</ol>\n<p>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, \u201c<strong><em>Lab-3-Solution</em></strong>\u201d from flash memory.</p>",
    "tasks": "**IPv6 Addressing & Static Routing Tasks**\n\nYou are one of several network engineers that work for your company which consists of a large enterprise network that spans multiple buildings across several campuses. You have been placed in charge of all networks within buildings-5 and 6 of your campus.\n\nThe Network Architect for your company has obtained the IPv6 prefix of\n\n2001:aaaa:bbbb::/48 and decided to break this into multiple /56 subnets for each campus. Considering that you are in charge of Building-5 and 6 on your campus, you have been given the subnet of 2001:aaaa:bbbb:5600::/56.  \n\n\n\n1. Starting with the IPv6 prefix of **2004:aaaa:bbbb:5600::/56** subnet this into multiple /64 subnets for each of the links below (the first one has been done for you). Each router will also have a Loopback0 interface configured with a /128 IPv6 host address:\n\n    |Link ID| Prefix|\n    |---|---|\n    | S| 2001:aaaa:bbbb:5600::/64|\n    | R|\n    | P|\n    | N|\n    | Loopback0 (/128 mask)| 2001:aaaa:bbbb:56__ __::(router value)/128|\n\n2. Configure an IPv6 address from what you derived in the step above on every interface on routers R3, R4 and R5 that connects to links S, R, P and N. Follow these guidelines:\n\n    - R3 connecting to Link-S should utilize the first available host address in the assigned prefix\n    - R3 connecting to Link-R should utilize the first available host address in the assigned prefix\n    - R4 connecting to Link-R and Link-P should utilize eui-64 interface-IDs for its respective prefixes.\n    - R5 connecting to Link-P should utilize SLAAC to dynamically obtain an IPv6 address from R4\u2026and an EUI-64 interface-ID for its interface connecting to Link-N\n    - All routers should have a /128 IPv6 address configured on their Loopback0 interfaces.\n\n\n3. Issue a command on all three routers (R3, R4 and R5) such that they will be able to perform IPv6 routing in the future.\n\n    - View the output of the IPv6 routing table on R4 with the command, \u201c**show ipv6 route**\u201d just to familiarize yourself with the output.\n\n\n4. On router R3 view the output of \u201c**show interface Gig0/0**\u201d.  Using the output you see from that command, see if you can predict what the IPv6 Link-Local address is on this interface and write that down here:\n\n\n5. Without looking at any command output, what IPv6 multicast addresses do you think interface Gigabit0/1 on R3 is subscribed to? Write one-or-more of them down here:\n\n6. On R3, issue the command, \u201c**show ipv6 interface Gig0/0**\u201d followed by the same command for Gig0/1 and verify if your answers to the previous two questions were correct.\n\n7. Configure IPv6 static routes on whichever routers are necessary so that routers R3, R4 and R5 can all IPv6 Ping each other\u2019s physical interface IPv6 addresses as well as the IPv6 addresses you\u2019ve configured on their Loopback0 interfaces.\n\n    - Usage of IPv6 default routes is encouraged.\n    - On router R3, use the IPv6 Link-Local address of R4 as the next-hop for any static routes configured on R3.\n\n\n8. Verify that you now have end-to-end IPv6 reachability by pinging the Loopback0 IPv6 address of R5, as well as R5\u2019s IPv6 address on Gig0/2 from router R3.\n\n**OSPF Dynamic IPv4 Routing Tasks**\n\n1. Configure OSPFv2 (for IPv4) on routers R1 and R2 using the following guidelines:\n\n    - All links (physical **and logical**) that contain IPv4 addresses on these routers should be activated for OSPF and be placed into the backbone area.\n    - Router R1 should advertise itself into OSPF with a Router-ID of 0.0.0.1\n    - Router R2 should advertise itself into OSPF with a Router-ID of 0.0.0.2\n        - Confirm that OSPF router-ids have been correctly applied by viewing the output of the command, \u201c**show ip ospf**\u201d on both routers.\n\n2. Routers R1 and R2 will form OSPF adjacencies with each other across links B & D, and Link-C.\n    - When an OSPF adjacency forms between R1 and R2 (on Links-A and B) ensure that router R1 becomes the OSPF Designated Router. This should be done by modification of OSPF interface priority values.\n    - When an OSPF adjacency forms between R1 and R2 (on Links-A and B) ensure that router R1 becomes the OSPF Designated Router. This should be done by modification of OSPF interface priority values.\n\n\n3. On R1, view the output of the following commands and answer the following questions:\n    - \u201c**Show ip ospf neighbor**\u201d: What \u201cstate\u201d is listed for the adjacency with R2?\n\n    - \u201c**Show ip route**\u201d: What letter precedes the OSPF route R1 learned about R2\u2019s Loopback0 interface prefix?\n\n    - What is the next-hop for the OSPF route leading to R2\u2019s Loopback0 network?\n\n    - \u201c**Show ip protocols**\u201d: Which networks are being routed by OSPF according to this output?\n\n4. Configure OSPFv2 (for IPv4) on all IPv4 enabled links of Switch-2, Switch-3 or Switch-4 as well as Gig0/2 (Link-N) on R5 (including Loopbacks if they exist). These should all be placed into OSPF Area-0.\n\n5. Configure OSPFv2 (for IPv4) on all remaining IPv4 enabled links of routers R3, R4 and R5. These should all be placed into OSPF** Area-88 (including the Loopback interfaces of R3 and R4)**.\n\n6. View the output of the command, \u201c**show ip route ospf**\u201d on R3 and answer the following questions:\n    - What letter precedes the OSPF route to the prefix residing on Link-P?\n    - What letter precedes the OSPF route to the prefix residing on Link-N?\n    - What Administrative Distance value has been assigned to your OSPF routes?\n        - Does this value vary depending on whether the routes are shown as \u201cO\u201d or \u201cO IA\u201d?\n\n7. Verify that you have end-to-end IPv4 reachability by pinging whatever IPv4 address has been assigned to R1\u2019s Gig0/2 interface (Link-B) from router R3.\n\n**Access-List Tasks**\n\n1. If it hasn\u2019t already been done, configure router R2 such that it can accept incoming SSH sessions as long as they provide the username/password of \u201ccisco/cisco\u201d.\n\n2. From router R3 do the following:\n\n    - Confirm R3 can ping the Loopback0 addresses on R1 and R2 using interface Gig0/1 as the source of those pings.    \n        - Repeat using interface Gig0/0 as the source\n\n    - Confirm R3 can Telnet to R1 and R2 using Gig0/1 as the source interface.    \n        - Repeat using interface Gig0/0 as the source        \n\n    - Confirm R3 can SSH to R2\n\n3. Answer the following question; Is it possible, by implementing a numbered Standard Access-List to prevent R3 from pinging the Loopback0 address of R1 but still allowing R3 to Telnet to this address?\n    - If you answered \u201cyes\u201d...try it.\n    - If you answered \u201cno\u201d, why not?\n\n4. Answer the following question; Is it possible, by implementing a numbered Extended Access-List to prevent **R5** from pinging the Loopback0 address of R1 but still allowing **R5 **to Telnet to this address?\n    - If you answered \u201cyes\u201d...try it.\n    - If you answered \u201cno\u201d, why not?\n\n5. Implement a named, extended Access-List **on R4** that accomplishes the following:\n    - Allows R3 to Telnet to any IPv4 address configured on R1 but only if R3 is sourcing those packets from its Gig0/0 interface.\n        - Any other packets that R3 sends to any IPv4 address on R1 should be denied.\n    - Allows R3 to SSH to R2 but only if the source of those packets is from the Link-R subnet.\n    - Pings from R3 to R2 (from any source) should be permitted.\n    - Telnet from R3 to R2 (from any source) is denied\n    - All other types of packets R3 might attempt to transmit through R4 should be allowed.\n\n\n6. Test the Access-Lists you created by generating various Ping, Telnet, and SSH requests from R3.",
    "tasks_html": "<p><strong>IPv6 Addressing &amp; Static Routing Tasks</strong></p>\n<p>You are one of several network engineers that work for your company which consists of a large enterprise network that spans multiple buildings across several campuses. You have been placed in charge of all networks within buildings-5 and 6 of your campus.</p>\n<p>The Network Architect for your company has obtained the IPv6 prefix of</p>\n<p>2001:aaaa:bbbb::/48 and decided to break this into multiple /56 subnets for each campus. Considering that you are in charge of Building-5 and 6 on your campus, you have been given the subnet of 2001:aaaa:bbbb:5600::/56.  </p>\n<ol>\n<li>\n<p>Starting with the IPv6 prefix of <strong>2004:aaaa:bbbb:5600::/56</strong> subnet this into multiple /64 subnets for each of the links below (the first one has been done for you). Each router will also have a Loopback0 interface configured with a /128 IPv6 host address:</p>\n<table>\n<thead>\n<tr>\n<th>Link ID</th>\n<th>Prefix</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>S</td>\n<td>2001:aaaa:bbbb:5600::/64</td>\n</tr>\n<tr>\n<td>R</td>\n<td></td>\n</tr>\n<tr>\n<td>P</td>\n<td></td>\n</tr>\n<tr>\n<td>N</td>\n<td></td>\n</tr>\n<tr>\n<td>Loopback0 (/128 mask)</td>\n<td>2001:aaaa:bbbb:56__ __::(router value)/128</td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Configure an IPv6 address from what you derived in the step above on every interface on routers R3, R4 and R5 that connects to links S, R, P and N. Follow these guidelines:</p>\n<ul>\n<li>R3 connecting to Link-S should utilize the first available host address in the assigned prefix</li>\n<li>R3 connecting to Link-R should utilize the first available host address in the assigned prefix</li>\n<li>R4 connecting to Link-R and Link-P should utilize eui-64 interface-IDs for its respective prefixes.</li>\n<li>R5 connecting to Link-P should utilize SLAAC to dynamically obtain an IPv6 address from R4\u2026and an EUI-64 interface-ID for its interface connecting to Link-N</li>\n<li>All routers should have a /128 IPv6 address configured on their Loopback0 interfaces.</li>\n</ul>\n</li>\n<li>\n<p>Issue a command on all three routers (R3, R4 and R5) such that they will be able to perform IPv6 routing in the future.</p>\n<ul>\n<li>View the output of the IPv6 routing table on R4 with the command, \u201c<strong>show ipv6 route</strong>\u201d just to familiarize yourself with the output.</li>\n</ul>\n</li>\n<li>\n<p>On router R3 view the output of \u201c<strong>show interface Gig0/0</strong>\u201d.  Using the output you see from that command, see if you can predict what the IPv6 Link-Local address is on this interface and write that down here:</p>\n</li>\n<li>\n<p>Without looking at any command output, what IPv6 multicast addresses do you think interface Gigabit0/1 on R3 is subscribed to? Write one-or-more of them down here:</p>\n</li>\n<li>\n<p>On R3, issue the command, \u201c<strong>show ipv6 interface Gig0/0</strong>\u201d followed by the same command for Gig0/1 and verify if your answers to the previous two questions were correct.</p>\n</li>\n<li>\n<p>Configure IPv6 static routes on whichever routers are necessary so that routers R3, R4 and R5 can all IPv6 Ping each other\u2019s physical interface IPv6 addresses as well as the IPv6 addresses you\u2019ve configured on their Loopback0 interfaces.</p>\n<ul>\n<li>Usage of IPv6 default routes is encouraged.</li>\n<li>On router R3, use the IPv6 Link-Local address of R4 as the next-hop for any static routes configured on R3.</li>\n</ul>\n</li>\n<li>\n<p>Verify that you now have end-to-end IPv6 reachability by pinging the Loopback0 IPv6 address of R5, as well as R5\u2019s IPv6 address on Gig0/2 from router R3.</p>\n</li>\n</ol>\n<p><strong>OSPF Dynamic IPv4 Routing Tasks</strong></p>\n<ol>\n<li>\n<p>Configure OSPFv2 (for IPv4) on routers R1 and R2 using the following guidelines:</p>\n<ul>\n<li>All links (physical <strong>and logical</strong>) that contain IPv4 addresses on these routers should be activated for OSPF and be placed into the backbone area.</li>\n<li>Router R1 should advertise itself into OSPF with a Router-ID of 0.0.0.1</li>\n<li>Router R2 should advertise itself into OSPF with a Router-ID of 0.0.0.2<ul>\n<li>Confirm that OSPF router-ids have been correctly applied by viewing the output of the command, \u201c<strong>show ip ospf</strong>\u201d on both routers.</li>\n</ul>\n</li>\n</ul>\n</li>\n<li>\n<p>Routers R1 and R2 will form OSPF adjacencies with each other across links B &amp; D, and Link-C.</p>\n<ul>\n<li>When an OSPF adjacency forms between R1 and R2 (on Links-A and B) ensure that router R1 becomes the OSPF Designated Router. This should be done by modification of OSPF interface priority values.</li>\n<li>When an OSPF adjacency forms between R1 and R2 (on Links-A and B) ensure that router R1 becomes the OSPF Designated Router. This should be done by modification of OSPF interface priority values.</li>\n</ul>\n</li>\n<li>\n<p>On R1, view the output of the following commands and answer the following questions:</p>\n<ul>\n<li>\n<p>\u201c<strong>Show ip ospf neighbor</strong>\u201d: What \u201cstate\u201d is listed for the adjacency with R2?</p>\n</li>\n<li>\n<p>\u201c<strong>Show ip route</strong>\u201d: What letter precedes the OSPF route R1 learned about R2\u2019s Loopback0 interface prefix?</p>\n</li>\n<li>\n<p>What is the next-hop for the OSPF route leading to R2\u2019s Loopback0 network?</p>\n</li>\n<li>\n<p>\u201c<strong>Show ip protocols</strong>\u201d: Which networks are being routed by OSPF according to this output?</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Configure OSPFv2 (for IPv4) on all IPv4 enabled links of Switch-2, Switch-3 or Switch-4 as well as Gig0/2 (Link-N) on R5 (including Loopbacks if they exist). These should all be placed into OSPF Area-0.</p>\n</li>\n<li>\n<p>Configure OSPFv2 (for IPv4) on all remaining IPv4 enabled links of routers R3, R4 and R5. These should all be placed into OSPF** Area-88 (including the Loopback interfaces of R3 and R4)**.</p>\n</li>\n<li>\n<p>View the output of the command, \u201c<strong>show ip route ospf</strong>\u201d on R3 and answer the following questions:</p>\n<ul>\n<li>What letter precedes the OSPF route to the prefix residing on Link-P?</li>\n<li>What letter precedes the OSPF route to the prefix residing on Link-N?</li>\n<li>What Administrative Distance value has been assigned to your OSPF routes?<ul>\n<li>Does this value vary depending on whether the routes are shown as \u201cO\u201d or \u201cO IA\u201d?</li>\n</ul>\n</li>\n</ul>\n</li>\n<li>\n<p>Verify that you have end-to-end IPv4 reachability by pinging whatever IPv4 address has been assigned to R1\u2019s Gig0/2 interface (Link-B) from router R3.</p>\n</li>\n</ol>\n<p><strong>Access-List Tasks</strong></p>\n<ol>\n<li>\n<p>If it hasn\u2019t already been done, configure router R2 such that it can accept incoming SSH sessions as long as they provide the username/password of \u201ccisco/cisco\u201d.</p>\n</li>\n<li>\n<p>From router R3 do the following:</p>\n<ul>\n<li>\n<p>Confirm R3 can ping the Loopback0 addresses on R1 and R2 using interface Gig0/1 as the source of those pings.    </p>\n<ul>\n<li>Repeat using interface Gig0/0 as the source</li>\n</ul>\n</li>\n<li>\n<p>Confirm R3 can Telnet to R1 and R2 using Gig0/1 as the source interface.    </p>\n<ul>\n<li>Repeat using interface Gig0/0 as the source        </li>\n</ul>\n</li>\n<li>\n<p>Confirm R3 can SSH to R2</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Answer the following question; Is it possible, by implementing a numbered Standard Access-List to prevent R3 from pinging the Loopback0 address of R1 but still allowing R3 to Telnet to this address?</p>\n<ul>\n<li>If you answered \u201cyes\u201d...try it.</li>\n<li>If you answered \u201cno\u201d, why not?</li>\n</ul>\n</li>\n<li>\n<p>Answer the following question; Is it possible, by implementing a numbered Extended Access-List to prevent <strong>R5</strong> from pinging the Loopback0 address of R1 but still allowing *<em>R5 *</em>to Telnet to this address?</p>\n<ul>\n<li>If you answered \u201cyes\u201d...try it.</li>\n<li>If you answered \u201cno\u201d, why not?</li>\n</ul>\n</li>\n<li>\n<p>Implement a named, extended Access-List <strong>on R4</strong> that accomplishes the following:</p>\n<ul>\n<li>Allows R3 to Telnet to any IPv4 address configured on R1 but only if R3 is sourcing those packets from its Gig0/0 interface.<ul>\n<li>Any other packets that R3 sends to any IPv4 address on R1 should be denied.</li>\n</ul>\n</li>\n<li>Allows R3 to SSH to R2 but only if the source of those packets is from the Link-R subnet.</li>\n<li>Pings from R3 to R2 (from any source) should be permitted.</li>\n<li>Telnet from R3 to R2 (from any source) is denied</li>\n<li>All other types of packets R3 might attempt to transmit through R4 should be allowed.</li>\n</ul>\n</li>\n<li>\n<p>Test the Access-Lists you created by generating various Ping, Telnet, and SSH requests from R3.</p>\n</li>\n</ol>",
    "published_date": "2020-04-14T18:00:00Z",
    "solutions": "***Solution***\n\nLab solutions are stored as viewable (and loadable) named configuration files stored in Flash memory on each device. To view the Lab Solution, login to any IOS device in your topology (Routers or Switches) and issue the following command:\n\n<pre><code>\n\n    Router>enable\n    Router#<b>more flash:Lab-3-Solution</b>\n    !\n    version 15.9\n    service timestamps debug datetime msec\n    service timestamps log datetime msec\n    no service password-encryption\n    !\n    hostname R1\n    !\n    boot-start-marker\n    [SNIP]\n\n</pre></code>\n\nTo **Load** the solution configuration onto your device follow the procedure below.  Please NOTE that ***this procedure will completely erase your current configuration file and overwrite it with the solution configuration file***:\n\n<pre><code>\n\n    Router-1#<b>configure replace flash:Lab-3-Solution</b>\n    This will apply all necessary additions and deletions\n    to <b>replace the current running configuration with the\n    contents of the specified configuration file</b>, which is\n    assumed to be a complete configuration, not a partial\n    configuration. Enter Y if you are sure you want to proceed. ? [no]: <b>yes</b>\n\n    *Jul 29 19:10:01.921: Rollback:Acquired Configuration lock.\n     WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\n\n    *Jul 29 19:10:04.061: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\n\n    *Jul 29 19:10:05.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up\n    Total number of passes: 1\n    Rollback Done\n\n    R1#\n\n</pre></code>\nFooter",
    "solutions_html": "<p><strong><em>Solution</em></strong></p>\n<p>Lab solutions are stored as viewable (and loadable) named configuration files stored in Flash memory on each device. To view the Lab Solution, login to any IOS device in your topology (Routers or Switches) and issue the following command:</p>\n<pre><code>\n\n    Router>enable\n    Router#<b>more flash:Lab-3-Solution</b>\n    !\n    version 15.9\n    service timestamps debug datetime msec\n    service timestamps log datetime msec\n    no service password-encryption\n    !\n    hostname R1\n    !\n    boot-start-marker\n    [SNIP]\n\n</pre>\n\n<p></code></p>\n<p>To <strong>Load** the solution configuration onto your device follow the procedure below.  Please NOTE that **<em>this procedure will completely erase your current configuration file and overwrite it with the solution configuration file</em></strong>:</p>\n<pre><code>\n\n    Router-1#<b>configure replace flash:Lab-3-Solution</b>\n    This will apply all necessary additions and deletions\n    to <b>replace the current running configuration with the\n    contents of the specified configuration file</b>, which is\n    assumed to be a complete configuration, not a partial\n    configuration. Enter Y if you are sure you want to proceed. ? [no]: <b>yes</b>\n\n    *Jul 29 19:10:01.921: Rollback:Acquired Configuration lock.\n     WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\n\n    *Jul 29 19:10:04.061: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\n\n    *Jul 29 19:10:05.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up\n    Total number of passes: 1\n    Rollback Done\n\n    R1#\n\n</pre>\n\n<p></code>\nFooter</p>",
    "flags": [],
    "min_points_to_pass": null,
    "access_type": "default",
    "user_status": "unstarted",
    "user_lab_status": null,
    "user_status_modified": null,
    "user_flags": [],
    "global_running_session": null
}