{
    "id": "ba0b6e43-8702-4e54-9b3a-702a3007e26d",
    "name": "Cisco IOS Basics & IPv4 Subnetting",
    "slug": "cisco-ios-basics-ipv4-subnetting",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "351",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-29T13:55:58.424788Z",
    "modified": "2023-10-03T18:58:59.708794Z",
    "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": "8b0a95ba-694c-46f1-b0a4-3529cf8d91a6",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4721/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-4721/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-4721/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-4721/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: Cisco IOS Essentials & IP Subnetting**\n\n1. Login to device R1 and you'll notice that it has a non-default configuration already on it (as evidenced by its host name). Reset this device to a factory default configuration.\n\n2. Login to every device and configure the following items:\n\n    - A hostname that matches the device name in the topology diagram\n\n    - A command that prevents the device from attempting to resolve via DNS mistyped commands\n\n    - A command that repeats your most recent input/typing to the screen after an interruption by a SYSLOG or other console message.\n\n    - A password of \"***INE***\" to be required whenever anyone attempts to gain access to Privileged EXEC mode.  This password should not be visible in plaintext in the output of the configuration file.\n\n    - Enable every interface shown in the topology diagram and provide a brief interface description such that anyone looking at your configuration will know what that interface connects to.\n\n    - When you are done with this step, utilize CDP on Switch-2, R5 and R4 to confirm those devices can see (as CDP neighbors) other connected Cisco devices.\n\n3. Configure devices R1 and R3 to allow inbound Telnet connections. These connections should be authenticated against a preconfigured password of \"***cisco***\".\n\n4. Configure devices R2 and R5 to allow inbound SSH (version-2) connections. These connections should be authenticated against a username of \"***admin***\" and a (Privilege Level 15) password of \"***ine***\". You may use your own discretion to complete any other required keywords or features required for SSH configuration.\n\n5. Derive an IP addressing scheme for network segments A through F using the following guidelines:\n    - Your starting network should be 180.50.0.0/16\n\n    - Your first/largest subnet should be 180.50.0.0 with a new/different subnet mask.\n\n    - You must use the VLSM method, utilizing the ***fewest/least*** host bits in each network as possible per the host requirements shown below:\n\n    |Network Segment|Required Hosts|Subnet Mask| Prefix|\n    |---|---|---|---|\n    |A| 99|\n    |B| 13|\n    |C| 6|\n    |D| 11|\n    |E| 26|\n    |F| 30|\n\n6. Apply IPv4 addresses to your router interfaces using the following guidelines:\n\n    - Routers connecting to network segments \"A\" through \"D\" should be given the first available host address(s) within each respective subnet.\n\n    - Don't worry about addressing router R3's Gig0/2 interface yet (for Segments-E and F). That will be accomplished in another lab.\n\n    - Routers R3(Gig0/0 and Gig0/1), R4 and R5 should be configured using the IPv4 addresses and masks shown in the topology diagram.\n\n7. Verify your IPv4 addressing configuration by performing the following actions:\n\n    - Confirm that you can Telnet from R2 to R1\n\n    - Confirm that you can Telnet from R4 to R3\n\n    - Confirm that you can SSH from R1 to R2\n\n    - Confirm that you can SSH from R4 to R5",
    "tasks_html": "<p><strong>Task: Cisco IOS Essentials &amp; IP Subnetting</strong></p>\n<ol>\n<li>\n<p>Login to device R1 and you'll notice that it has a non-default configuration already on it (as evidenced by its host name). Reset this device to a factory default configuration.</p>\n</li>\n<li>\n<p>Login to every device and configure the following items:</p>\n<ul>\n<li>\n<p>A hostname that matches the device name in the topology diagram</p>\n</li>\n<li>\n<p>A command that prevents the device from attempting to resolve via DNS mistyped commands</p>\n</li>\n<li>\n<p>A command that repeats your most recent input/typing to the screen after an interruption by a SYSLOG or other console message.</p>\n</li>\n<li>\n<p>A password of \"<strong><em>INE</em></strong>\" to be required whenever anyone attempts to gain access to Privileged EXEC mode.  This password should not be visible in plaintext in the output of the configuration file.</p>\n</li>\n<li>\n<p>Enable every interface shown in the topology diagram and provide a brief interface description such that anyone looking at your configuration will know what that interface connects to.</p>\n</li>\n<li>\n<p>When you are done with this step, utilize CDP on Switch-2, R5 and R4 to confirm those devices can see (as CDP neighbors) other connected Cisco devices.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Configure devices R1 and R3 to allow inbound Telnet connections. These connections should be authenticated against a preconfigured password of \"<strong><em>cisco</em></strong>\".</p>\n</li>\n<li>\n<p>Configure devices R2 and R5 to allow inbound SSH (version-2) connections. These connections should be authenticated against a username of \"<strong><em>admin</em></strong>\" and a (Privilege Level 15) password of \"<strong><em>ine</em></strong>\". You may use your own discretion to complete any other required keywords or features required for SSH configuration.</p>\n</li>\n<li>\n<p>Derive an IP addressing scheme for network segments A through F using the following guidelines:</p>\n<ul>\n<li>\n<p>Your starting network should be 180.50.0.0/16</p>\n</li>\n<li>\n<p>Your first/largest subnet should be 180.50.0.0 with a new/different subnet mask.</p>\n</li>\n<li>\n<p>You must use the VLSM method, utilizing the <strong><em>fewest/least</em></strong> host bits in each network as possible per the host requirements shown below:</p>\n</li>\n</ul>\n<table>\n<thead>\n<tr>\n<th>Network Segment</th>\n<th>Required Hosts</th>\n<th>Subnet Mask</th>\n<th>Prefix</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>A</td>\n<td>99</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>B</td>\n<td>13</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>C</td>\n<td>6</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>D</td>\n<td>11</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>E</td>\n<td>26</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>F</td>\n<td>30</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Apply IPv4 addresses to your router interfaces using the following guidelines:</p>\n<ul>\n<li>\n<p>Routers connecting to network segments \"A\" through \"D\" should be given the first available host address(s) within each respective subnet.</p>\n</li>\n<li>\n<p>Don't worry about addressing router R3's Gig0/2 interface yet (for Segments-E and F). That will be accomplished in another lab.</p>\n</li>\n<li>\n<p>Routers R3(Gig0/0 and Gig0/1), R4 and R5 should be configured using the IPv4 addresses and masks shown in the topology diagram.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Verify your IPv4 addressing configuration by performing the following actions:</p>\n<ul>\n<li>\n<p>Confirm that you can Telnet from R2 to R1</p>\n</li>\n<li>\n<p>Confirm that you can Telnet from R4 to R3</p>\n</li>\n<li>\n<p>Confirm that you can SSH from R1 to R2</p>\n</li>\n<li>\n<p>Confirm that you can SSH from R4 to R5</p>\n</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
}