{
    "id": "da423bda-ed3f-40d0-afc0-d0b8aee27ffd",
    "name": "CCNA Troubleshooting Lab-1",
    "slug": "ccna-troubleshooting-lab-1",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "357",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-31T17:31:50.316185Z",
    "modified": "2023-10-03T18:59:05.421178Z",
    "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": "be8d718c-922a-4800-b02c-fe900bdbc47e",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4324/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-4324/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-4324/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-4324/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: Troubleshooting OSPF Adjacencies**\n\n***NOTE:*** The enable password on router R5 is \"**INE**\"\n\n\n1. Login to router R5 and issue the command, \"**show ip ospf neighbor Gigabit0/1**\". You should notice that this router currently has one OSPF adjacency on this interface.\n\n<pre><code>\n\n    R5#<b>show ip ospf neighbor gigabit0/1</b>\n\n    Neighbor ID     Pri   State           Dead Time   Address         Interface\n    33.33.33.3        1   FULL/DR         00:00:38    5.1.23.99       GigabitEthernet0/1\n    R5#\n\n</pre></code>\n\n2. Router R5 is **SUPPOSED to have three OSPF neighbors on interface Gigabit0/1**. You must troubleshoot why this router is only seeing a single neighbor on this interface.\n\n3. Guidelines for troubleshooting:\n\n    - You may not change the OSPF area or interface IPv4 address of router R5\n    - You are **not allowed to move or delete the white circle** which is covering the topology of Area-51.\n    - Telnet passwords for all routers in Area-51 is **cisco**\n    - Enable passwords for all routers in Area-51 is \"**ine1234**\"\n    - Any configuration changes you make to the Running-Config of routers in Area-51 should **NOT** be saved to their Startup-Config files\n\n4. You will have correctly solved the problems in this lab when the output of \"**show ip ospf neighbor gig0/1**\" on R5 looks like the output below:\n\n<pre><code>\n\n    R5#sho ip ospf neigh gig 0/1               \n\n    Neighbor ID     Pri   State           Dead Time   Address         Interface\n    33.33.33.3        1   FULL/DR         00:00:36    5.1.23.99       GigabitEthernet0/1\n    111.111.111.1     1   FULL/BDR        00:00:32    x.x.x.x       GigabitEthernet0/1\n    222.222.222.2     1   2WAY/DROTHER    00:00:36    x.x.x.x       GigabitEthernet0/1\n    R5#\n\n</pre></code>",
    "tasks_html": "<p><strong>Task: Troubleshooting OSPF Adjacencies</strong></p>\n<p><strong><em>NOTE:</em></strong> The enable password on router R5 is \"<strong>INE</strong>\"</p>\n<ol>\n<li>Login to router R5 and issue the command, \"<strong>show ip ospf neighbor Gigabit0/1</strong>\". You should notice that this router currently has one OSPF adjacency on this interface.</li>\n</ol>\n<pre><code>\n\n    R5#<b>show ip ospf neighbor gigabit0/1</b>\n\n    Neighbor ID     Pri   State           Dead Time   Address         Interface\n    33.33.33.3        1   FULL/DR         00:00:38    5.1.23.99       GigabitEthernet0/1\n    R5#\n\n</pre>\n\n<p></code></p>\n<ol>\n<li>\n<p>Router R5 is <strong>SUPPOSED to have three OSPF neighbors on interface Gigabit0/1</strong>. You must troubleshoot why this router is only seeing a single neighbor on this interface.</p>\n</li>\n<li>\n<p>Guidelines for troubleshooting:</p>\n<ul>\n<li>You may not change the OSPF area or interface IPv4 address of router R5</li>\n<li>You are <strong>not allowed to move or delete the white circle</strong> which is covering the topology of Area-51.</li>\n<li>Telnet passwords for all routers in Area-51 is <strong>cisco</strong></li>\n<li>Enable passwords for all routers in Area-51 is \"<strong>ine1234</strong>\"</li>\n<li>Any configuration changes you make to the Running-Config of routers in Area-51 should <strong>NOT</strong> be saved to their Startup-Config files</li>\n</ul>\n</li>\n<li>\n<p>You will have correctly solved the problems in this lab when the output of \"<strong>show ip ospf neighbor gig0/1</strong>\" on R5 looks like the output below:</p>\n</li>\n</ol>\n<pre><code>\n\n    R5#sho ip ospf neigh gig 0/1               \n\n    Neighbor ID     Pri   State           Dead Time   Address         Interface\n    33.33.33.3        1   FULL/DR         00:00:36    5.1.23.99       GigabitEthernet0/1\n    111.111.111.1     1   FULL/BDR        00:00:32    x.x.x.x       GigabitEthernet0/1\n    222.222.222.2     1   2WAY/DROTHER    00:00:36    x.x.x.x       GigabitEthernet0/1\n    R5#\n\n</pre>\n\n<p></code></p>",
    "published_date": "2022-09-16T21:23:58Z",
    "solutions": "***SOLUTIONS***\n\nThere were two main problems that had to be corrected in this lab:\n\n    - One neighbor had an incorrect interface subnet mask. This needed to be changed to match the subnet mask of R5's Gig0/1 interface.\n    - One neighbor was configured for the wrong area (Area-511 instead of Area-51) and this needed to be changed.\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>There were two main problems that had to be corrected in this lab:</p>\n<pre class=\"codehilite\"><code>- One neighbor had an incorrect interface subnet mask. This needed to be changed to match the subnet mask of R5's Gig0/1 interface.\n- One neighbor was configured for the wrong area (Area-511 instead of Area-51) and this needed to be changed.</code></pre>\n\n\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
}