{
    "id": "2e0e6bd0-bf85-4ab1-8067-3c98459630cf",
    "name": "Port-Security Configuration, Monitoring & Testing",
    "slug": "port-security-configuration-monitoring-testing",
    "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:17:58.543484Z",
    "modified": "2023-10-03T18:58:33.736453Z",
    "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": "a014477a-6779-43b3-aa8a-d009666fd488",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4280/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-4280/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-4280/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-4280/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: Switchport Security Using Port-Security**\n\n***NOTE:*** The enable password on all IOS devices is \"**INE**\"\n\n1. On Switch-2 configure the **spanning-tree portfast edge** feature on interfaces Gig0/1 and Gig0/2.\n\n2. On Switch-2 shutdown interface Gig0/1. Then, implement Port-Security on interface Gig0/1 such that:\n\n    - Only a single MAC address may be dynamically learned on this interface\n    - The first MAC address that is learned on this interface should appear in the Running-Config.\n    - If a Port-Security violation occurs, the interface will be moved into the errdisable state.\n\n3. Enable interface Gig0/1 on Switch-2.  Then login to router R1 and (from this router) ping R2 at **180.50.0.210**.\n\n    - On Switch-2, view the output of \"**show running-config**\" and confirm that R1's MAC address displays in this output beneath Gig0/1's configuration section.\n\n4. On router R1, change its MAC address on interface Gig0/1 to **0211.1111.1111** and then try to ping R2 again at **180.50.0.210**.\n\n    - If your Port-Security configuration on Switch-2 is correct, the ping attempt between R1 and R2 should fail.\n    - Port-Security on Switch-2 should have detected a security violation on interface Gig0/1 and placed this interface into the errdisable state.  Verify this.\n\n5. Once you have verified that Port-Security on Switch-2 (Gigabit0/1) is operating as intended then...\n\n    - Shutdown this interface\n    - Remove the artificial MAC address you configured on R1's Gig0/1 interface\n    - Enable interface Gig0/1 on Switch-2\n    - Confirm that R1 can once again ping R2 at **180.50.0.210**.\n\n\n6. On Switch-2 shutdown interface **Gig0/2**. Then, implement Port-Security on interface Gig0/2 such that:\n\n    - Only two MAC addresses may be dynamically learned on this interface\n    - The first mac address should be statically configured into Port-Security as the MAC address on R2's Gig0/2 interface.\n    - The second MAC address that is learned on this interface should appear in the Running-Config.\n    - If a Port-Security violation occurs, the interface should remain up but discard the offending frames and increment the \"violation counter\" within the **show port-security interface** command output.\n\n7. Enable interface Gig0/2 on Switch-2.  Then login to router R2 and (from this router) ping R1 at **180.50.0.209**.\n\n    - On Switch-2, view the output of \"**show running-config**\" and confirm that R2's MAC address displays in this output beneath Gig0/2's configuration section.\n\n8. On router R2, change its MAC address on interface Gig0/2 to **0422.2222.2222** and then try to ping R1 again at **180.50.0.209**.\n\n    - If your Port-Security configuration on Switch-2 is correct, the ping attempt between R1 and R2 should still succeed.\n    - On router R2, change its MAC address on interface Gig0/2 again to a new value of **0444.4444.44444** and then try to ping R1 again at **180.50.0.209**.\n    - Port-Security on Switch-2 should have detected a security violation on interface Gig0/2 and, while keeping the interface functional, it should have dropped the ping attempts between R2 and R1.\n    - Repeated ping attempts between R2 and R1 should cause additional violations which should be tracked via the \"\" placed this interface into the errdisable state.  Verify this.\n\n9. Once you have verified that Port-Security on Switch-2 (Gigabit0/2) is operating as intended then...\n\n    - Shutdown this interface\n    - Remove the artificial MAC address you configured on R2's Gig0/2 interface\n    - Enable interface Gig0/2 on Switch-2\n    - Confirm that R2 can once again ping R1 at **180.50.0.209**.",
    "tasks_html": "<p><strong>Task: Switchport Security Using Port-Security</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>On Switch-2 configure the <strong>spanning-tree portfast edge</strong> feature on interfaces Gig0/1 and Gig0/2.</p>\n</li>\n<li>\n<p>On Switch-2 shutdown interface Gig0/1. Then, implement Port-Security on interface Gig0/1 such that:</p>\n<ul>\n<li>Only a single MAC address may be dynamically learned on this interface</li>\n<li>The first MAC address that is learned on this interface should appear in the Running-Config.</li>\n<li>If a Port-Security violation occurs, the interface will be moved into the errdisable state.</li>\n</ul>\n</li>\n<li>\n<p>Enable interface Gig0/1 on Switch-2.  Then login to router R1 and (from this router) ping R2 at <strong>180.50.0.210</strong>.</p>\n<ul>\n<li>On Switch-2, view the output of \"<strong>show running-config</strong>\" and confirm that R1's MAC address displays in this output beneath Gig0/1's configuration section.</li>\n</ul>\n</li>\n<li>\n<p>On router R1, change its MAC address on interface Gig0/1 to <strong>0211.1111.1111</strong> and then try to ping R2 again at <strong>180.50.0.210</strong>.</p>\n<ul>\n<li>If your Port-Security configuration on Switch-2 is correct, the ping attempt between R1 and R2 should fail.</li>\n<li>Port-Security on Switch-2 should have detected a security violation on interface Gig0/1 and placed this interface into the errdisable state.  Verify this.</li>\n</ul>\n</li>\n<li>\n<p>Once you have verified that Port-Security on Switch-2 (Gigabit0/1) is operating as intended then...</p>\n<ul>\n<li>Shutdown this interface</li>\n<li>Remove the artificial MAC address you configured on R1's Gig0/1 interface</li>\n<li>Enable interface Gig0/1 on Switch-2</li>\n<li>Confirm that R1 can once again ping R2 at <strong>180.50.0.210</strong>.</li>\n</ul>\n</li>\n<li>\n<p>On Switch-2 shutdown interface <strong>Gig0/2</strong>. Then, implement Port-Security on interface Gig0/2 such that:</p>\n<ul>\n<li>Only two MAC addresses may be dynamically learned on this interface</li>\n<li>The first mac address should be statically configured into Port-Security as the MAC address on R2's Gig0/2 interface.</li>\n<li>The second MAC address that is learned on this interface should appear in the Running-Config.</li>\n<li>If a Port-Security violation occurs, the interface should remain up but discard the offending frames and increment the \"violation counter\" within the <strong>show port-security interface</strong> command output.</li>\n</ul>\n</li>\n<li>\n<p>Enable interface Gig0/2 on Switch-2.  Then login to router R2 and (from this router) ping R1 at <strong>180.50.0.209</strong>.</p>\n<ul>\n<li>On Switch-2, view the output of \"<strong>show running-config</strong>\" and confirm that R2's MAC address displays in this output beneath Gig0/2's configuration section.</li>\n</ul>\n</li>\n<li>\n<p>On router R2, change its MAC address on interface Gig0/2 to <strong>0422.2222.2222</strong> and then try to ping R1 again at <strong>180.50.0.209</strong>.</p>\n<ul>\n<li>If your Port-Security configuration on Switch-2 is correct, the ping attempt between R1 and R2 should still succeed.</li>\n<li>On router R2, change its MAC address on interface Gig0/2 again to a new value of <strong>0444.4444.44444</strong> and then try to ping R1 again at <strong>180.50.0.209</strong>.</li>\n<li>Port-Security on Switch-2 should have detected a security violation on interface Gig0/2 and, while keeping the interface functional, it should have dropped the ping attempts between R2 and R1.</li>\n<li>Repeated ping attempts between R2 and R1 should cause additional violations which should be tracked via the \"\" placed this interface into the errdisable state.  Verify this.</li>\n</ul>\n</li>\n<li>\n<p>Once you have verified that Port-Security on Switch-2 (Gigabit0/2) is operating as intended then...</p>\n<ul>\n<li>Shutdown this interface</li>\n<li>Remove the artificial MAC address you configured on R2's Gig0/2 interface</li>\n<li>Enable interface Gig0/2 on Switch-2</li>\n<li>Confirm that R2 can once again ping R1 at <strong>180.50.0.209</strong>.</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
}