{
    "id": "fb416c6a-d7b7-44ca-a395-3cca7fb445ef",
    "name": "Etherchannel, Spanning-Tree, IOS DHCP Server & Static Routing",
    "slug": "etherchannel-spanning-tree-ios-dhcp-server-static-routing",
    "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-15T20:57:52.305230Z",
    "modified": "2023-10-03T18:59:11.459790Z",
    "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-2-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-2-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\n    1. On all IOS devices (routers and switches) load the preconfiguration file from flash: memory titled, \u201c**IP-Only**\u201d.\n    2. 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\n    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***Lab-2-Solution***\u201d from flash memory.",
    "description_html": "<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Day-2-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-2-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<pre class=\"codehilite\"><code>1. On all IOS devices (routers and switches) load the preconfiguration file from flash: memory titled, \u201c**IP-Only**\u201d.\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-2-Solution***\u201d from flash memory.</code></pre>",
    "tasks": "**Etherchannel Tasks**\n\n1. Group Link-K and Link-L into a Layer-2 LACP Etherchannel\n    - Switch-3 should initiate LACP message exchange\n    - Switch-4 should passively listen for incoming LACP messages\n    - Use whatever channel number you wish\n\n2. Verify that your Etherchannel is functional in the output of \u201c**show etherchannel summary**\u201d on Switch-3 and Switch-4\n\n\n**Spanning-Tree Tasks**\n\n1. Determine what mode/version of Spanning-tree is running on switches Switch-2, Switch-3 and Switch-4.\n\n2. Configure whatever command(s) is needed so that the three switches above are running rapid Spanning-Tree.\n\n3. Among Switch-2, Switch-3 and Switch-4 determine which switch is the RSTP Root ridge for VLAN-2 and VLAN-3.  Ensure you can determine WHY each switch won the RSTP Root ridge election for the respective VLAN.\n\n4. Configure whatever command is necessary to take Switch-4 the RSTP Root Bridge for VLAN-2.\n\n5. Configure the IPv4 address and mask of **10.10.40.2/28** onto PC3 (DHCP will be configured later) and point PC3 to R1 (Link-F) as its default gateway.\n\n    - Ensure PC3 can ping R1(Gig0/1) after his step.\n\n\n6. With Switch-4 now the RSTP Root Bridge the path that pings should be taking between PC3 and R1 (Gig0/1) should be as follows:\n\n    ![description](https://assets.ine.com/content/labs/networking-labs/Day-2-Lab/stp-path.png)\n\n    - Verify using the appropriate \u201cshow\u201d commands that your pings are indeed taking the path shown above.\n\n7. Without changing the placement of the VLAN-2 RSTP Root Bridge, modify RSTP (on whichever devices are necessary) such that pings between PC3 and R1 travel across Link-H instead of Link-J.\n\n**Switched Virtual Interfaces Tasks**\n\n1. Configure Switched Virtual Interfaces (i.e. VLAN interfaces) on Switch-4 for both VLAN-2 and VLAN-3. Utilize the _last available host address_ in each subnet to address these interfaces.\n\n2. Configure any other necessary commands on Switch-4 so that it will be able to utilize these new SVIs to route between VLANs-2 and 3.\n\n**IOS DHCP Server Tasks**\n\n\n1. Configure Switch-4 as a DHCP Server utilizing the following parameters\n    - The DHCP Pool for VLAN-2 hosts should be named \u201cVLAN2\u201d\n    - The DHCP Pool for VLAN-3 hosts should be named \u201cVLAN3\u201d\n    - Addresses should be allocated from each pool according to the IPv4 addressing chart shown at the top of this lab.\n    - The switch should advertise its own IPv4 addresses (configured on its Switched Virtual Interfaces) as the default router for each respective VLAN.\n    - Addresses should have a valid lifetime of 12-hours and 30-minutes\n    - Ensure that IPv4 addresses configured on router interfaces for these same subnets are excluded from DHCP allocation.\n\n2. Configure PC3 to obtain its IPv4 information via DHCP by using the following command on PC3:\n\n    **ip dhcp -d**\n\n    **NOTE:** the \u201c-d\u201d option allows you to see the DHCP transactions as they occur on PC3 which is useful for troubleshooting.\n\n3. For testing purposes only, configure R5\u2019s Gig0/2 interface to obtain an IP address via DHCP using the command, \u201c**ip address dhcp**\u201d.\n\n4. If your SVIs and DHCP configurations are correct, PC3 and R5 (which are in different VLANs) should now be able to ping each other.\n\n5. Once you have confirmed that PC3 and R5 can ping each other, on R5 replace its running-configuration with the \u201c**IP-Only**\u201d configuration file in flash memory.\n\n\n**Static Routing Tasks**\n\n1. Configure PC1, PC2 and PC4 with their respective IPv4 addresses as shown in the topology diagram and IPv4 addressing chart. Each PC should point to the IPv4 address of its connected router as its default gateway.\n\n2. On all routers and switches, configure static IPv4 routes to achieve end-to-end IPv4 reachability. Use the following guidelines:\n    - Default static routes can be used when appropriate\n    - Configure the fewest static routes possible on each device\n    - Next-hops for static routes should be IPv4 addresses of directly-connected devices.\n    - Once this step is complete, PC4 should be able to ping all other PCs.",
    "tasks_html": "<p><strong>Etherchannel Tasks</strong></p>\n<ol>\n<li>\n<p>Group Link-K and Link-L into a Layer-2 LACP Etherchannel</p>\n<ul>\n<li>Switch-3 should initiate LACP message exchange</li>\n<li>Switch-4 should passively listen for incoming LACP messages</li>\n<li>Use whatever channel number you wish</li>\n</ul>\n</li>\n<li>\n<p>Verify that your Etherchannel is functional in the output of \u201c<strong>show etherchannel summary</strong>\u201d on Switch-3 and Switch-4</p>\n</li>\n</ol>\n<p><strong>Spanning-Tree Tasks</strong></p>\n<ol>\n<li>\n<p>Determine what mode/version of Spanning-tree is running on switches Switch-2, Switch-3 and Switch-4.</p>\n</li>\n<li>\n<p>Configure whatever command(s) is needed so that the three switches above are running rapid Spanning-Tree.</p>\n</li>\n<li>\n<p>Among Switch-2, Switch-3 and Switch-4 determine which switch is the RSTP Root ridge for VLAN-2 and VLAN-3.  Ensure you can determine WHY each switch won the RSTP Root ridge election for the respective VLAN.</p>\n</li>\n<li>\n<p>Configure whatever command is necessary to take Switch-4 the RSTP Root Bridge for VLAN-2.</p>\n</li>\n<li>\n<p>Configure the IPv4 address and mask of <strong>10.10.40.2/28</strong> onto PC3 (DHCP will be configured later) and point PC3 to R1 (Link-F) as its default gateway.</p>\n<ul>\n<li>Ensure PC3 can ping R1(Gig0/1) after his step.</li>\n</ul>\n</li>\n<li>\n<p>With Switch-4 now the RSTP Root Bridge the path that pings should be taking between PC3 and R1 (Gig0/1) should be as follows:</p>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Day-2-Lab/stp-path.png\" /></p>\n<ul>\n<li>Verify using the appropriate \u201cshow\u201d commands that your pings are indeed taking the path shown above.</li>\n</ul>\n</li>\n<li>\n<p>Without changing the placement of the VLAN-2 RSTP Root Bridge, modify RSTP (on whichever devices are necessary) such that pings between PC3 and R1 travel across Link-H instead of Link-J.</p>\n</li>\n</ol>\n<p><strong>Switched Virtual Interfaces Tasks</strong></p>\n<ol>\n<li>\n<p>Configure Switched Virtual Interfaces (i.e. VLAN interfaces) on Switch-4 for both VLAN-2 and VLAN-3. Utilize the <em>last available host address</em> in each subnet to address these interfaces.</p>\n</li>\n<li>\n<p>Configure any other necessary commands on Switch-4 so that it will be able to utilize these new SVIs to route between VLANs-2 and 3.</p>\n</li>\n</ol>\n<p><strong>IOS DHCP Server Tasks</strong></p>\n<ol>\n<li>\n<p>Configure Switch-4 as a DHCP Server utilizing the following parameters</p>\n<ul>\n<li>The DHCP Pool for VLAN-2 hosts should be named \u201cVLAN2\u201d</li>\n<li>The DHCP Pool for VLAN-3 hosts should be named \u201cVLAN3\u201d</li>\n<li>Addresses should be allocated from each pool according to the IPv4 addressing chart shown at the top of this lab.</li>\n<li>The switch should advertise its own IPv4 addresses (configured on its Switched Virtual Interfaces) as the default router for each respective VLAN.</li>\n<li>Addresses should have a valid lifetime of 12-hours and 30-minutes</li>\n<li>Ensure that IPv4 addresses configured on router interfaces for these same subnets are excluded from DHCP allocation.</li>\n</ul>\n</li>\n<li>\n<p>Configure PC3 to obtain its IPv4 information via DHCP by using the following command on PC3:</p>\n<p><strong>ip dhcp -d</strong></p>\n<p><strong>NOTE:</strong> the \u201c-d\u201d option allows you to see the DHCP transactions as they occur on PC3 which is useful for troubleshooting.</p>\n</li>\n<li>\n<p>For testing purposes only, configure R5\u2019s Gig0/2 interface to obtain an IP address via DHCP using the command, \u201c<strong>ip address dhcp</strong>\u201d.</p>\n</li>\n<li>\n<p>If your SVIs and DHCP configurations are correct, PC3 and R5 (which are in different VLANs) should now be able to ping each other.</p>\n</li>\n<li>\n<p>Once you have confirmed that PC3 and R5 can ping each other, on R5 replace its running-configuration with the \u201c<strong>IP-Only</strong>\u201d configuration file in flash memory.</p>\n</li>\n</ol>\n<p><strong>Static Routing Tasks</strong></p>\n<ol>\n<li>\n<p>Configure PC1, PC2 and PC4 with their respective IPv4 addresses as shown in the topology diagram and IPv4 addressing chart. Each PC should point to the IPv4 address of its connected router as its default gateway.</p>\n</li>\n<li>\n<p>On all routers and switches, configure static IPv4 routes to achieve end-to-end IPv4 reachability. Use the following guidelines:</p>\n<ul>\n<li>Default static routes can be used when appropriate</li>\n<li>Configure the fewest static routes possible on each device</li>\n<li>Next-hops for static routes should be IPv4 addresses of directly-connected devices.</li>\n<li>Once this step is complete, PC4 should be able to ping all other PCs.</li>\n</ul>\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-2-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-2-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        *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        *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>",
    "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-2-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-2-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        *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        *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></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
}