{
    "id": "fda7cc4d-7aa4-4465-a7da-541b2ba86367",
    "name": "DHCP Snooping Configuration & Verification",
    "slug": "dhcp-snooping-configuration-verification",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "354",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-29T15:21:14.487446Z",
    "modified": "2023-10-03T18:59:12.076990Z",
    "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": "a5ee19ff-91fe-4f10-80fc-bf2bc215b639",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4281/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-4281/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-4281/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-4281/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: DHCP Snooping Configuration & Verification**\n\n***NOTE:*** The enable password on all IOS devices is \"**INE**\"\n\n1. In this lab, router R3 should already be configured as a router-on-a-stick for VLANs-3 and 4 as well as a DHCP server. Confirm this is true. If you don't see this in R3s configuration, configure it yourself.\n\n2. Switch-2 will act as a Rogue DHCP Server in this task. Apply the following configuration to **Switch-2**.\n\n    - Create two switched virtual interfaces on Switch-2:\n        - interface vlan 3: 99.99.99.2 /24\n        - interface vlan 4: 88.88.88.2 /24\n\n    - Create two DHCP pools in Switch-2:\n        - The first pool (name can be whatever you wish) should allocate addresses from the 99.99.99.0/24 network with a default-router of 99.99.99.2\n        - The second pool (name can be whatever you wish) should allocate addresses from the 88.88.88.0/24 network with a default-router of 88.88.88.2\n\n3. On **Switch-3** shutdown/disable interface Gig0/3.\n\n    - On PC5 type the command, \"**ip dhcp -d**\" and verify that it receives an IPv4 address in the 99.99.99.0/24 subnet.\n    - Repeat the step above on PC3 and verify that it receives an IPv4 address in the 88.88.88.0/24 subnet.\n    - Enable interface Gig0/3 on Switch-3.\n\n4. Enable the DHCP Snooping feature on Switch-3 such that PC3 and PC5 can obtain IPv4 addresses via DHCP from R3 but not the Rogue DHCP Server (Switch-2).\n\n    - On PC3 and PC5 issue the command, **ip dhcp -d** and confirm they are receiving DHCP information from the correct DHCP Server (R3)\n    - View the output of \"**show ip dhcp snooping binding**\" on Switch-3 to confirm it has placed learned DHCP information into the DHCP Snooping Binding database.",
    "tasks_html": "<p><strong>Task: DHCP Snooping Configuration &amp; Verification</strong></p>\n<p><strong><em>NOTE:</em></strong> The enable password on all IOS devices is \"<strong>INE</strong>\"</p>\n<ol>\n<li>\n<p>In this lab, router R3 should already be configured as a router-on-a-stick for VLANs-3 and 4 as well as a DHCP server. Confirm this is true. If you don't see this in R3s configuration, configure it yourself.</p>\n</li>\n<li>\n<p>Switch-2 will act as a Rogue DHCP Server in this task. Apply the following configuration to <strong>Switch-2</strong>.</p>\n<ul>\n<li>\n<p>Create two switched virtual interfaces on Switch-2:</p>\n<ul>\n<li>interface vlan 3: 99.99.99.2 /24</li>\n<li>interface vlan 4: 88.88.88.2 /24</li>\n</ul>\n</li>\n<li>\n<p>Create two DHCP pools in Switch-2:</p>\n<ul>\n<li>The first pool (name can be whatever you wish) should allocate addresses from the 99.99.99.0/24 network with a default-router of 99.99.99.2</li>\n<li>The second pool (name can be whatever you wish) should allocate addresses from the 88.88.88.0/24 network with a default-router of 88.88.88.2</li>\n</ul>\n</li>\n</ul>\n</li>\n<li>\n<p>On <strong>Switch-3</strong> shutdown/disable interface Gig0/3.</p>\n<ul>\n<li>On PC5 type the command, \"<strong>ip dhcp -d</strong>\" and verify that it receives an IPv4 address in the 99.99.99.0/24 subnet.</li>\n<li>Repeat the step above on PC3 and verify that it receives an IPv4 address in the 88.88.88.0/24 subnet.</li>\n<li>Enable interface Gig0/3 on Switch-3.</li>\n</ul>\n</li>\n<li>\n<p>Enable the DHCP Snooping feature on Switch-3 such that PC3 and PC5 can obtain IPv4 addresses via DHCP from R3 but not the Rogue DHCP Server (Switch-2).</p>\n<ul>\n<li>On PC3 and PC5 issue the command, <strong>ip dhcp -d</strong> and confirm they are receiving DHCP information from the correct DHCP Server (R3)</li>\n<li>View the output of \"<strong>show ip dhcp snooping binding</strong>\" on Switch-3 to confirm it has placed learned DHCP information into the DHCP Snooping Binding database.</li>\n</ul>\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
}