{
    "id": "541be0f7-7191-44f7-b320-715271de8fd7",
    "name": "Essential Layer-2 Switching",
    "slug": "essential-layer-2-switching",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "352",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-29T14:17:01.850419Z",
    "modified": "2023-10-03T18:58:40.909182Z",
    "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": "8eca2de2-c747-46ab-8a51-d4b442b9b2f5",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4275/diagram.png)\n\n\n**Helpful Hints about INE\u2019s virtual lab environment:**\n\n- 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.\n- To access the CLI (command line interface) of any node, right-click that node and select the \"**console**\" option.\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/Lab-4275/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.",
    "description_html": "<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Lab-4275/diagram.png\" /></p>\n<p><strong>Helpful Hints about INE\u2019s virtual lab environment:</strong></p>\n<ul>\n<li>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.</li>\n<li>To access the CLI (command line interface) of any node, right-click that node and select the \"<strong>console</strong>\" option.</li>\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/Lab-4275/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>",
    "tasks": "**Task: Essential CCNA Switching**\n\nNOTE: Enable password is **INE**\n\n1. MAC addresses that are dynamically learned by switches expire after a certain amount of time if they are inactive. Issue a command on Switch-1 to view the default value of this timer.\n\n    - Change the above-mentioned timer on Switch-1 to expire after 100-seconds of inactivity.\n\n2. Configure all interswitch links on switches Switch-2, Switch-3 and Switch-4 to operate as 802.1q VLAN trunks using the following guidelines:\n\n    - Use the \"**interface range**\" command as often as possible to minimize configuration repetition.\n\n    - Higher-numbered switches should initiate the process of dynamically forming trunks with lower-numbered switches.\n\n    - The Trunk link shared by Switch-2 (Gig0/0) and Switch-3 (Gig0/1) should utilize VLAN-2 as its Native VLAN.\n\n    - All 802.1q VLAN Trunks should be configured such that they **only allow VLANs 1-5**.  Other VLANs that may be added in the future will not be allowed on these trunks.\n\n3. Configure VTP version-2 on all three switches such that:\n\n    - Any VLANs manually configured on Switch-2 will be propagated via VTP to Switch-3.\n\n    - Switch-4 should utilize a VTP mode that will allow manual creation and deletion of VLANs but will not dynamically update any other switches about changes to its VLAN database.\n\n    - VTP should be secured with a password of \"**INE**\".\n\n    - It is up to your own discretion to set any other parameters necessary for VTP to operate.\n\n    - Configure VLANs 1-5 on Switch-4 and apply the following names:\n\n        - VLAN-2 = \"Payroll\"\n        - VLAN-3 = \"Engineering\"\n        - VLAN-4 = \"Marketing\"\n        - VLAN-5 = \"Executives\"\n\n    - Configure the same VLANS as above (with the same names) on Switch-2. Confirm that VTP has propagated this information to Switch-3.\n\n4. Ensure that switchports that connect to either routers or PCs have no possibility of forming VLAN Trunks (**with the exception of Gig0/3 on Switch-3, ignore that port for now**):\n\n\n    | Device name| Switchport| VLAN assignment|\n    |---|---|---|\n    |Switch-2| Gig0/1| VLAN-2|\n    |Switch-2| Gig0/2| VLAN-2|\n    |Switch-3| Gig1/0| VLAN-3|\n    |Switch-3| Gig0/0| VLAN-4|\n    |Switch-4| Gig0/1| VLAN-5|\n\n5. Confirm VLAN creation and port assignment on each switch using the \"**show vlans**\" command.",
    "tasks_html": "<p><strong>Task: Essential CCNA Switching</strong></p>\n<p>NOTE: Enable password is <strong>INE</strong></p>\n<ol>\n<li>\n<p>MAC addresses that are dynamically learned by switches expire after a certain amount of time if they are inactive. Issue a command on Switch-1 to view the default value of this timer.</p>\n<ul>\n<li>Change the above-mentioned timer on Switch-1 to expire after 100-seconds of inactivity.</li>\n</ul>\n</li>\n<li>\n<p>Configure all interswitch links on switches Switch-2, Switch-3 and Switch-4 to operate as 802.1q VLAN trunks using the following guidelines:</p>\n<ul>\n<li>\n<p>Use the \"<strong>interface range</strong>\" command as often as possible to minimize configuration repetition.</p>\n</li>\n<li>\n<p>Higher-numbered switches should initiate the process of dynamically forming trunks with lower-numbered switches.</p>\n</li>\n<li>\n<p>The Trunk link shared by Switch-2 (Gig0/0) and Switch-3 (Gig0/1) should utilize VLAN-2 as its Native VLAN.</p>\n</li>\n<li>\n<p>All 802.1q VLAN Trunks should be configured such that they <strong>only allow VLANs 1-5</strong>.  Other VLANs that may be added in the future will not be allowed on these trunks.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Configure VTP version-2 on all three switches such that:</p>\n<ul>\n<li>\n<p>Any VLANs manually configured on Switch-2 will be propagated via VTP to Switch-3.</p>\n</li>\n<li>\n<p>Switch-4 should utilize a VTP mode that will allow manual creation and deletion of VLANs but will not dynamically update any other switches about changes to its VLAN database.</p>\n</li>\n<li>\n<p>VTP should be secured with a password of \"<strong>INE</strong>\".</p>\n</li>\n<li>\n<p>It is up to your own discretion to set any other parameters necessary for VTP to operate.</p>\n</li>\n<li>\n<p>Configure VLANs 1-5 on Switch-4 and apply the following names:</p>\n<ul>\n<li>VLAN-2 = \"Payroll\"</li>\n<li>VLAN-3 = \"Engineering\"</li>\n<li>VLAN-4 = \"Marketing\"</li>\n<li>VLAN-5 = \"Executives\"</li>\n</ul>\n</li>\n<li>\n<p>Configure the same VLANS as above (with the same names) on Switch-2. Confirm that VTP has propagated this information to Switch-3.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Ensure that switchports that connect to either routers or PCs have no possibility of forming VLAN Trunks (<strong>with the exception of Gig0/3 on Switch-3, ignore that port for now</strong>):</p>\n<table>\n<thead>\n<tr>\n<th>Device name</th>\n<th>Switchport</th>\n<th>VLAN assignment</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Switch-2</td>\n<td>Gig0/1</td>\n<td>VLAN-2</td>\n</tr>\n<tr>\n<td>Switch-2</td>\n<td>Gig0/2</td>\n<td>VLAN-2</td>\n</tr>\n<tr>\n<td>Switch-3</td>\n<td>Gig1/0</td>\n<td>VLAN-3</td>\n</tr>\n<tr>\n<td>Switch-3</td>\n<td>Gig0/0</td>\n<td>VLAN-4</td>\n</tr>\n<tr>\n<td>Switch-4</td>\n<td>Gig0/1</td>\n<td>VLAN-5</td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Confirm VLAN creation and port assignment on each switch using the \"<strong>show vlans</strong>\" command.</p>\n</li>\n</ol>",
    "published_date": "2022-09-16T21:23:58Z",
    "solutions": "***SOLUTIONS***\n\nView the Solution Video accompanying this lab for the lab solutions and walkthrough.",
    "solutions_html": "<p><strong><em>SOLUTIONS</em></strong></p>\n<p>View the Solution Video accompanying this lab for the lab solutions and walkthrough.</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
}