{
    "id": "c4b7ce8c-e735-4a8b-a8d5-27b5a8fedea5",
    "name": "IPv6 Addressing & Configuration",
    "slug": "ipv6-addressing-configuration",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "352",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-29T14:01:07.177209Z",
    "modified": "2023-10-03T18:59:01.146710Z",
    "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": "a870f641-7d02-4192-90a1-12f406801f95",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4273/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-4273/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-4273/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-4273/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: IPv6 Subnetting and Addressing**\n\nNOTE: Enable password is **INE**\n\n1. Derive an IPv6 addressing scheme for network segments A through F using the following guidelines:\n\n    - Your starting prefix should be **2001:1111:2222:ff00::/56**\n\n    - Each subnet you derive should conform to the IANA IPv6 recommendations and have a **/64 netmask**.\n\n    - Assign your prefixes according to the chart below (examples: Subnet-1 would be 2001:1111:2222:ff00::/64 and Subnet-2 would be 2001:1111:2222:ff01::/64):\n\n    |Network Segment|Subnet Number| Prefix|\n    |---|---|---|\n    |A| 9|\n    |B| 17|\n    |C| 28|\n    |D| 100|\n    |E| 44|\n    |F| 23|\n\n2. Apply IPv6 addresses to your router interfaces using the following guidelines:\n\n    - Don't worry about addressing R3's interface connecting to **Segment-E or Segment-F**. We'll get to that segment in another lab.\n\n    - Routers connecting to network **Segment-A** should utilize EUI-64 dynamic interface-IDs.\n\n    - On **Segment-B**, R1 should have a static interface-ID of ::1. On this same segment router R2 (Gig0/0) should obtain its entire IPv6 address dynamically via SLAAC from router R1.\n\n    - All other router interfaces should have static interface-IDs corresponding to their router number (ie ::3 for router R3).\n\n    - Routers R3(Gig0/0 and Gig0/1), R4 and R5 should be configured using the IPv6 addresses and interface-IDs shown in the topology diagram.\n\n3. Verify your IPv6 addressing configuration by performing the following actions:\n\n    - Confirm that you can Telnet to R1 from R2 across both Segments-A and B.\n\n    - Confirm that you can Telnet to R3 (Gig0/1) from R4.\n\n    - Confirm that you can ping R5's Gig0/0 interface from R4.\n\n4. Log into router R1 and view the output of \"**show interface gig0/0**\". Using the output of that command **ONLY** answer the following questions:\n\n    - What is the IPv6 Link-Local address of this interface?\n    - What is/are the Solicited Node Multicast Addresses of this interface?\n\n5. After completing step-4 above, issue the command, \"**show ipv6 interface gig0/0**\" to confirm if your answers were correct.",
    "tasks_html": "<p><strong>Task: IPv6 Subnetting and Addressing</strong></p>\n<p>NOTE: Enable password is <strong>INE</strong></p>\n<ol>\n<li>\n<p>Derive an IPv6 addressing scheme for network segments A through F using the following guidelines:</p>\n<ul>\n<li>\n<p>Your starting prefix should be <strong>2001:1111:2222:ff00::/56</strong></p>\n</li>\n<li>\n<p>Each subnet you derive should conform to the IANA IPv6 recommendations and have a <strong>/64 netmask</strong>.</p>\n</li>\n<li>\n<p>Assign your prefixes according to the chart below (examples: Subnet-1 would be 2001:1111:2222:ff00::/64 and Subnet-2 would be 2001:1111:2222:ff01::/64):</p>\n</li>\n</ul>\n<table>\n<thead>\n<tr>\n<th>Network Segment</th>\n<th>Subnet Number</th>\n<th>Prefix</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>A</td>\n<td>9</td>\n<td></td>\n</tr>\n<tr>\n<td>B</td>\n<td>17</td>\n<td></td>\n</tr>\n<tr>\n<td>C</td>\n<td>28</td>\n<td></td>\n</tr>\n<tr>\n<td>D</td>\n<td>100</td>\n<td></td>\n</tr>\n<tr>\n<td>E</td>\n<td>44</td>\n<td></td>\n</tr>\n<tr>\n<td>F</td>\n<td>23</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Apply IPv6 addresses to your router interfaces using the following guidelines:</p>\n<ul>\n<li>\n<p>Don't worry about addressing R3's interface connecting to <strong>Segment-E or Segment-F</strong>. We'll get to that segment in another lab.</p>\n</li>\n<li>\n<p>Routers connecting to network <strong>Segment-A</strong> should utilize EUI-64 dynamic interface-IDs.</p>\n</li>\n<li>\n<p>On <strong>Segment-B</strong>, R1 should have a static interface-ID of ::1. On this same segment router R2 (Gig0/0) should obtain its entire IPv6 address dynamically via SLAAC from router R1.</p>\n</li>\n<li>\n<p>All other router interfaces should have static interface-IDs corresponding to their router number (ie ::3 for router R3).</p>\n</li>\n<li>\n<p>Routers R3(Gig0/0 and Gig0/1), R4 and R5 should be configured using the IPv6 addresses and interface-IDs shown in the topology diagram.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Verify your IPv6 addressing configuration by performing the following actions:</p>\n<ul>\n<li>\n<p>Confirm that you can Telnet to R1 from R2 across both Segments-A and B.</p>\n</li>\n<li>\n<p>Confirm that you can Telnet to R3 (Gig0/1) from R4.</p>\n</li>\n<li>\n<p>Confirm that you can ping R5's Gig0/0 interface from R4.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Log into router R1 and view the output of \"<strong>show interface gig0/0</strong>\". Using the output of that command <strong>ONLY</strong> answer the following questions:</p>\n<ul>\n<li>What is the IPv6 Link-Local address of this interface?</li>\n<li>What is/are the Solicited Node Multicast Addresses of this interface?</li>\n</ul>\n</li>\n<li>\n<p>After completing step-4 above, issue the command, \"<strong>show ipv6 interface gig0/0</strong>\" to confirm if your answers were correct.</p>\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
}