{
    "id": "4cdea3fe-72c6-4ddd-ad66-a55dfc17a977",
    "name": "CCNA Troubleshooting Lab-2",
    "slug": "ccna-troubleshooting-lab-2",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "369",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-09-12T17:25:42.566131Z",
    "modified": "2023-10-03T18:58:39.472050Z",
    "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": "8f6ff3eb-d71b-48e9-b273-407dde1b0638",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4325/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-4325/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-4325/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-4325/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: CCNA Troubleshooting Lab-2**\n\n***NOTE-1:*** The enable password on all IOS devices (except OSPF Area-51) is \"**INE**\"\n\n***NOTE-2:*** All of the devices in this topology are preconfigured with several features which spikes the host machine's CPU when the lab first comes up. Once you can view the topology please wait approximately 2-3 minutes for the CPU level to decline before attempting to access the CLI of any of the device.\n\n\n1. The problem you must troubleshoot and resolve: **PC1 cannot ping PC5**.\n\n    - **NOTE**: There may be more than one issue you must find and correct before you have completed this lab.\n\n2. Troubleshoot and resolve the issue above but observe the following restrictions:\n\n    - PCs should utilize DHCP for address assignment. This can be accomplished with the command, \"**ip dhcp -d**\" and preconfigured addresses can be viewed with the command, \"**show ip**\"\n    - You may not disable any interfaces that are currently enabled.\n    - You may not enable any interfaces that are currently disabled.\n    - You may not alter the IPv4/IPv6 addresses of any interfaces that match what is displayed in the topology diagram.\n    - You may not disable any dynamic routing protocols.\n    - Any existing preconfigured IOS features that you discover may be modified but may not be entirely removed/deleted.",
    "tasks_html": "<p><strong>Task: CCNA Troubleshooting Lab-2</strong></p>\n<p><strong><em>NOTE-1:</em></strong> The enable password on all IOS devices (except OSPF Area-51) is \"<strong>INE</strong>\"</p>\n<p><strong><em>NOTE-2:</em></strong> All of the devices in this topology are preconfigured with several features which spikes the host machine's CPU when the lab first comes up. Once you can view the topology please wait approximately 2-3 minutes for the CPU level to decline before attempting to access the CLI of any of the device.</p>\n<ol>\n<li>\n<p>The problem you must troubleshoot and resolve: <strong>PC1 cannot ping PC5</strong>.</p>\n<ul>\n<li><strong>NOTE</strong>: There may be more than one issue you must find and correct before you have completed this lab.</li>\n</ul>\n</li>\n<li>\n<p>Troubleshoot and resolve the issue above but observe the following restrictions:</p>\n<ul>\n<li>PCs should utilize DHCP for address assignment. This can be accomplished with the command, \"<strong>ip dhcp -d</strong>\" and preconfigured addresses can be viewed with the command, \"<strong>show ip</strong>\"</li>\n<li>You may not disable any interfaces that are currently enabled.</li>\n<li>You may not enable any interfaces that are currently disabled.</li>\n<li>You may not alter the IPv4/IPv6 addresses of any interfaces that match what is displayed in the topology diagram.</li>\n<li>You may not disable any dynamic routing protocols.</li>\n<li>Any existing preconfigured IOS features that you discover may be modified but may not be entirely removed/deleted.</li>\n</ul>\n</li>\n</ol>",
    "published_date": "2022-09-16T21:23:58Z",
    "solutions": "***SOLUTIONS***\n\nAfter PC1 and PC5 used DHCP to obtain their IPv4 addresses, the main issue that had to be corrected was Access-list 101 configured in router R4. This ACL contained a line denying ICMP Echo Responses from PC5 (inbound on R4's Gig0/1 interface). Once that ACL was edited and this line was removed pings should have worked.\n\nFor more details, view the Solution Video accompanying this lab for the lab solutions and walkthrough.",
    "solutions_html": "<p><strong><em>SOLUTIONS</em></strong></p>\n<p>After PC1 and PC5 used DHCP to obtain their IPv4 addresses, the main issue that had to be corrected was Access-list 101 configured in router R4. This ACL contained a line denying ICMP Echo Responses from PC5 (inbound on R4's Gig0/1 interface). Once that ACL was edited and this line was removed pings should have worked.</p>\n<p>For more details, 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
}