{
    "id": "14a2663d-0359-478c-8adb-72bf726c1e34",
    "name": "IOS CLI Basics, Switching and IPv4 Subnetting",
    "slug": "ios-cli-basics-switching-and-ipv4-subnetting",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "9581c375-e70d-4e54-a425-51a05c02157a"
        ],
        "pta_sdn": "256",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-15T21:13:22.190694Z",
    "modified": "2023-10-03T18:58:29.989909Z",
    "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": null,
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Day-1-Lab/diagram.png)\n\n\n**Helpful Hints about INE\u2019s virtual lab environment:**\n\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/Day-1-Lab/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/Day-1-Lab/diagram.png\" /></p>\n<p><strong>Helpful Hints about INE\u2019s virtual lab environment:</strong></p>\n<ul>\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/Day-1-Lab/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: Initial Configuration**\n\n1. On all routers and switches, load the configuration file stored in Flash: memory titled, \u201c**default-config**\u201d. An example of this process is shown below:\n\n    <pre><code>\n    Switch>enable\n    Switch#<b>configure replace flash:default-config</b>\n    This will apply all necessary additions and deletions\n    to replace the current running configuration with the\n    contents of the specified configuration file, which is\n    assumed to be a complete configuration, not a partial\n    configuration. Enter Y if you are sure you want to proceed? [no]: <b>yes</b>\n\n    *Jul 26 19:49:30.929: Rollback:Acquired Configuration lock.\n    The rollback configlet from the last pass is listed below:\n\n    !List of Rollback Commands:\n    line vty 0 4\n     no login\n    end\n\n    Rollback aborted after 5 passes\n    Switch#\n    </pre></code>\n\n2. Assign hostnames to each device as reflected in the topology diagram for Lab-1\n\n3. Apply the following set of common parameters to each device:\n    - Devices should not attempt a DNS resolution when a command is entered incorrectly\n    - Devices should repeat your most recent console input when interrupted by a SYSLOG message\n    - All interfaces leading to other devices in the diagram should be administratively up.\n    - All devices should be configured with a password of \u201c**cisco**\u201d which is required to gain access to Privileged EXEC (i.e. \u201cenable\u201d) mode. This password should display in clear-text in your configuration file.\n    - Router R1 should be configured to accept incoming Telnet connections.  These connections should be authenticated using the password of \u201c**cisco**\u201d.\n    - Router R2 should be configured to accept incoming SSHv2 connections.  These connections should be authenticated using the username of \u201cine\u201d and the password of \u201c**cisco**\u201d.\n        - For any SSH configuration steps which require you to select a value, use whatever value you want (other than the username/password combination specified above).\n\n\n**Task: Implementing Basic Switching**\n\n1. Configure VLANs 2 and 3 on switches Sw2, Sw3 and Sw4.\n   \n2. VLAN Configuration\n    - Ensure that the switchport leading to PC3 (**Link-M**) is placed into VLAN-2\n    - Ensure that the switchport leading to R5 (**Link-N**) is placed into VLAN-3\n    - Ensure that the switchport (on Switch-2) leading to R1\u2019s Gig0/1 interface (**Link-F**) is placed into VLAN-2\n\n3. Configure the links identified in the topology diagram as 802.1q VLAN trunks using the following parameters:\n    - Link-G on Switch-2 should not utilize any form of DTP\n    - All other inter switch links (**H, J, K and L**) should rely on DTP for dynamic trunking and trunk maintenance.\n    - Lower-numbered switches should initiate DTP exchanges\n    - Higher-numbered switches should passively wait for ingress DTP messages.\n    - Configure VLAN-2 to be the Native VLAN on Link-J\n    - Interface Gig0/2 on R2 (**Link-G**) should be configure as a router-on-a-stick. IPv4 addressing will be applied in the next step.\n\n\n**IP Addressing and Subnetting Tasks**\n\n1. Starting with the initial network of 10.10.10.0/24\nutilize VLSM in order to complete the following chart:\n\n    |Link ID| Qty of Hosts| Subnet Mask| Network/Prefix|\n    |---|---|---|---|\n    |M/F/G| 29|\n    |N/G| 12|\n    |C| 2|\n\n2. Apply IPv4 addressing and masks to PCs and router interfaces from what you derived in the previous step. Use these guidelines:\n    - Gig0/1 on Router (R1) should be addressed with the second available host address in its subnet.\n    - Gig0/2 on Router (R5) should be addressed with the first available host address in its subnet.\n    - Sub-Interfaces associated with Gig0/2 on R2 (**Link-G**)should be configured using the last available host address from their respective VLANs/subnets.\n        - No IPV4 subnet is provided or needed for VLAN-1\n    - The link shared between R1 and R2 should be configured with the only two available host addresses in Subnet-C.\n    - PC-3 should be addressed with the first available host address in its subnet. Configuration of IPv4 addresses on VPCS nodes in the topology are done using the following command:\n\n        ```\n        PC2> ip 4.4.4.4/24 4.4.4.1\n        The above command is for example only.  In the command,\n        4.4.4.4/24 is the given IP address for PC2 and its default\n        gateway has been assigned as 4.4.4.1\n        ```\n\n        - PC-3\u2019s default gateway should point to whatever IPv4 address you configured on R2's Gig0/2 sub-interface.\n\n\n**Lab Configuration Verification**\n\n1. If your configuration is correct, PC3 should now be able to ping whatever IPv4 addresses you assigned to the following interfaces:\n    - R1 (Gig0/1 and Gig0/0)\n    - R2 (Both Gig0/2 subinterfaces, and Gig0/0)\n\n    ***NOTE:*** PC3 will not be able to ping R5 because R5 doesn't have a route back to PC3's subnet.\n\n2. Router R5 should now be able to SSH into router R2.\n3. Router R2 should be able to Telnet into router R1.\n4. Save your running-configuration to your startup-configuration.\n5. Save another copy of your running-configuration to flash memory and name it, \u201c**Lab1-Completed**\u201d.",
    "tasks_html": "<p><strong>Task: Initial Configuration</strong></p>\n<ol>\n<li>\n<p>On all routers and switches, load the configuration file stored in Flash: memory titled, \u201c<strong>default-config</strong>\u201d. An example of this process is shown below:</p>\n<p><pre><code>\nSwitch&gt;enable\nSwitch#<b>configure replace flash:default-config</b>\nThis will apply all necessary additions and deletions\nto replace the current running configuration with the\ncontents of the specified configuration file, which is\nassumed to be a complete configuration, not a partial\nconfiguration. Enter Y if you are sure you want to proceed? [no]: <b>yes</b></p>\n<p>*Jul 26 19:49:30.929: Rollback:Acquired Configuration lock.\nThe rollback configlet from the last pass is listed below:</p>\n<p>!List of Rollback Commands:\nline vty 0 4\n no login\nend</p>\n<p>Rollback aborted after 5 passes\nSwitch#\n</pre></code></p>\n</li>\n<li>\n<p>Assign hostnames to each device as reflected in the topology diagram for Lab-1</p>\n</li>\n<li>\n<p>Apply the following set of common parameters to each device:</p>\n<ul>\n<li>Devices should not attempt a DNS resolution when a command is entered incorrectly</li>\n<li>Devices should repeat your most recent console input when interrupted by a SYSLOG message</li>\n<li>All interfaces leading to other devices in the diagram should be administratively up.</li>\n<li>All devices should be configured with a password of \u201c<strong>cisco</strong>\u201d which is required to gain access to Privileged EXEC (i.e. \u201cenable\u201d) mode. This password should display in clear-text in your configuration file.</li>\n<li>Router R1 should be configured to accept incoming Telnet connections.  These connections should be authenticated using the password of \u201c<strong>cisco</strong>\u201d.</li>\n<li>Router R2 should be configured to accept incoming SSHv2 connections.  These connections should be authenticated using the username of \u201cine\u201d and the password of \u201c<strong>cisco</strong>\u201d.<ul>\n<li>For any SSH configuration steps which require you to select a value, use whatever value you want (other than the username/password combination specified above).</li>\n</ul>\n</li>\n</ul>\n</li>\n</ol>\n<p><strong>Task: Implementing Basic Switching</strong></p>\n<ol>\n<li>\n<p>Configure VLANs 2 and 3 on switches Sw2, Sw3 and Sw4.</p>\n</li>\n<li>\n<p>VLAN Configuration</p>\n<ul>\n<li>Ensure that the switchport leading to PC3 (<strong>Link-M</strong>) is placed into VLAN-2</li>\n<li>Ensure that the switchport leading to R5 (<strong>Link-N</strong>) is placed into VLAN-3</li>\n<li>Ensure that the switchport (on Switch-2) leading to R1\u2019s Gig0/1 interface (<strong>Link-F</strong>) is placed into VLAN-2</li>\n</ul>\n</li>\n<li>\n<p>Configure the links identified in the topology diagram as 802.1q VLAN trunks using the following parameters:</p>\n<ul>\n<li>Link-G on Switch-2 should not utilize any form of DTP</li>\n<li>All other inter switch links (<strong>H, J, K and L</strong>) should rely on DTP for dynamic trunking and trunk maintenance.</li>\n<li>Lower-numbered switches should initiate DTP exchanges</li>\n<li>Higher-numbered switches should passively wait for ingress DTP messages.</li>\n<li>Configure VLAN-2 to be the Native VLAN on Link-J</li>\n<li>Interface Gig0/2 on R2 (<strong>Link-G</strong>) should be configure as a router-on-a-stick. IPv4 addressing will be applied in the next step.</li>\n</ul>\n</li>\n</ol>\n<p><strong>IP Addressing and Subnetting Tasks</strong></p>\n<ol>\n<li>\n<p>Starting with the initial network of 10.10.10.0/24\nutilize VLSM in order to complete the following chart:</p>\n<table>\n<thead>\n<tr>\n<th>Link ID</th>\n<th>Qty of Hosts</th>\n<th>Subnet Mask</th>\n<th>Network/Prefix</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>M/F/G</td>\n<td>29</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>N/G</td>\n<td>12</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>C</td>\n<td>2</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Apply IPv4 addressing and masks to PCs and router interfaces from what you derived in the previous step. Use these guidelines:</p>\n<ul>\n<li>Gig0/1 on Router (R1) should be addressed with the second available host address in its subnet.</li>\n<li>Gig0/2 on Router (R5) should be addressed with the first available host address in its subnet.</li>\n<li>Sub-Interfaces associated with Gig0/2 on R2 (<strong>Link-G</strong>)should be configured using the last available host address from their respective VLANs/subnets.<ul>\n<li>No IPV4 subnet is provided or needed for VLAN-1</li>\n</ul>\n</li>\n<li>The link shared between R1 and R2 should be configured with the only two available host addresses in Subnet-C.</li>\n<li>\n<p>PC-3 should be addressed with the first available host address in its subnet. Configuration of IPv4 addresses on VPCS nodes in the topology are done using the following command:</p>\n<pre class=\"codehilite\"><code>PC2&gt; ip 4.4.4.4/24 4.4.4.1\nThe above command is for example only.  In the command,\n4.4.4.4/24 is the given IP address for PC2 and its default\ngateway has been assigned as 4.4.4.1</code></pre>\n\n<ul>\n<li>PC-3\u2019s default gateway should point to whatever IPv4 address you configured on R2's Gig0/2 sub-interface.</li>\n</ul>\n</li>\n</ul>\n</li>\n</ol>\n<p><strong>Lab Configuration Verification</strong></p>\n<ol>\n<li>\n<p>If your configuration is correct, PC3 should now be able to ping whatever IPv4 addresses you assigned to the following interfaces:</p>\n<ul>\n<li>R1 (Gig0/1 and Gig0/0)</li>\n<li>R2 (Both Gig0/2 subinterfaces, and Gig0/0)</li>\n</ul>\n<p><strong><em>NOTE:</em></strong> PC3 will not be able to ping R5 because R5 doesn't have a route back to PC3's subnet.</p>\n</li>\n<li>\n<p>Router R5 should now be able to SSH into router R2.</p>\n</li>\n<li>Router R2 should be able to Telnet into router R1.</li>\n<li>Save your running-configuration to your startup-configuration.</li>\n<li>Save another copy of your running-configuration to flash memory and name it, \u201c<strong>Lab1-Completed</strong>\u201d.</li>\n</ol>",
    "published_date": "2020-04-14T18:00:00Z",
    "solutions": "**Solutions:**\n\n&nbsp;&nbsp;&nbsp;&nbsp;**Initial Configuration Solutions:**\n\n1. The following commands would be applied to all devices:\n\n    <pre><code>\n\n    <b>hostname [Device Hostname]</b>\n    !\n    <b>enable password cisco</b>\n    !\n    <b>no ip domain-lookup</b>\n    !\n    interface GigabitEthernetX/Y\n     <b>no shutdown</b>\n    !\n    line con 0\n     <b>logging synchronous</b>\n\n    </pre></code>\n\n\n2. R1 Telnet commands:\n\n    <pre><code>\n    line vty 0 4\n     <b>password cisco</b>\n     login\n     <b>transport input telnet</b>\n    </pre></code>\n\n3. R2 SSH commands:\n\n    <pre><code>\n    R2#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    R2(config)#<b>ip domain-name ine.com</b>\n    R2(config)#<b>ip ssh version 2</b>\n    Please create RSA keys to enable SSH (and of at least 768 bits for SSH v2).\n    R2(config)#<b>crypto key generate rsa</b>\n    The name for the keys will be: R2.ine.com\n    Choose the size of the key modulus in the range of 360 to 4096 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes.\n\n    How many bits in the modulus [512]: <b>1024</b>\n    % Generating 1024 bit RSA keys, keys will be non-    exportable...\n    [OK] (elapsed time was 1 seconds)\n\n    R2(config)#\n    *Jul 26 20:14:11.257: %SSH-5-ENABLED: SSH 2.0 has been  enabled\n    R2(config)#<b>username ine privilege 15 password cisco</b>\n     WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\n    R2(config)#\n    *Jul 26 20:14:30.792: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\n    R2(config)#<b>line vty 0 4</b>\n    R2(config-line)#<b>transport input ssh</b>\n    R2(config-line)#<b>login local</b>\n    R2(config-line)#end\n    R2#\n    </pre></code>\n\n\n&nbsp;&nbsp;&nbsp;&nbsp;**Implementing Basic Switching Solutions:**\n\n\n<pre><code>\n\n    <b>Only relevant portions of the switch configuration are shown below:</b>\n\n    Switch-2#sh run\n    Building configuration...\n\n    !\n    hostname Switch-2\n    !\n    <b>vlan 2-3</b>\n    !\n    !\n    interface GigabitEthernet0/0\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n    \n    !\n    interface GigabitEthernet0/1\n     <b>switchport access vlan 2</b>\n     <b>switchport mode access</b>\n    \n    !\n    interface GigabitEthernet0/2\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode trunk</b>\n     <b>switchport nonegotiate</b>\n    \n    !\n    interface GigabitEthernet0/3\n     <b>switchport trunk native vlan 2</b>\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n    \n    !\n    !\n    end\n\n    Switch-2#\n\n</pre></code>\n\n\n<pre><code>\n\n    [Only relevant portions of the configuration are shown below]\n\n    Switch-3#sh run\n    Building configuration...\n\n    !\n    <b>vlan 2-3</b>\n    !\n    interface GigabitEthernet0/0\n     <b>switchport access vlan 2</b>\n     <b>switchport mode access</b>\n    !\n    interface GigabitEthernet0/1\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n    \n    !\n    interface GigabitEthernet0/2\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n    \n    !\n    interface GigabitEthernet3/0\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n    \n    !\n    end\n\n\n    Switch-3#\n\n</pre></code>\n\n\n<pre><code>\n\n    [Only relevant portions of the configuration are displayed]\n\n    Switch-4#show  run\n    Building configuration...\n    !\n    hostname Switch-4\n    !\n    !\n    <b>vlan 2-3</b>\n    !\n    interface GigabitEthernet0/0\n     <b>switchport trunk native vlan 2</b>\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n    \n    !\n    interface GigabitEthernet0/1\n     <b>switchport access vlan 3</b>\n     <b>switchport mode access</b>\n    \n    !\n    interface GigabitEthernet0/2\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n    \n    !\n    interface GigabitEthernet3/0\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n    \n    !\n    end\n\n    Switch-4#\n\n</pre></code>\n\n\n&nbsp;&nbsp;&nbsp;&nbsp;**IP Addressing and Subnetting Solutions:**\n\n1. Starting network is 10.10.10.0/24\n\n|Link ID| Qty of Hosts| Subnet Mask| Network/Prefix|\n|---|---|---|---|\n|M/F/G| 29| 255.255.255.224 | 10.10.10.0|\n|N/G| 12| 255.255.255.240 | 10.10.10.32 |\n|C| 2| 255.255.255.252 | 10.10.10.48 |\n\n\n|Device| Interface| IPv4 Address|\n|---|---|---|\n|R1| Gig0/0| 10.10.10.49 /30|\n|R1| Gig0/1| 10.10.10.2 /27|\n|R2| Gig0/0| 10.10.10.50 /30|\n|R2| Gig0/2.2| 10.10.10.30 /27|\n|R2| Gig0/2.3| 10.10.10.46 /28|\n|R5| Gig0/2| 10.10.10.33 /28|\n|PC3| Eth0| 10.10.10.1 /27|\n\n2. Configuration of IPv4 addresses:\n\n<pre><code>\n\n    <b>R1 IPv4 interface configuration:</b>\n\n    R1#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    R1(config)#int gig 0/0\n    R1(config-if)#ip address 10.10.10.49 255.255.255.252\n    R1(config-if)#no shutdown\n    R1(config-if)#exit\n    R1(config)#\n    *Jul 28 18:57:52.480: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up\n    *Jul 28 18:57:53.480: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0,     changed state to up\n    R1(config)#int gig 0/1\n    R1(config-if)#ip add 10.10.10.2 255.255.255.224\n    R1(config-if)#no shutdown\n    R1(config-if)#end\n    R1#\n\n</pre></code>\n\n<pre><code>\n\n    <b>R2 IPv4 interface configuration:</b>\n\n    R2#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    R2(config)#interface gig0/0\n    R2(config-if)#ip address 10.10.10.50 255.255.255.252\n    R2(config-if)#no shutdown\n    R2(config-if)#exit\n    *Jul 28 19:00:02.188: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up\n    *Jul 28 19:00:03.188: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0,     changed state to up\n    R2(config-if)#exit\n    R2(config)#interface gig 0/2\n    R2(config-if)#no shutdown\n    R2(config-if)#exit\n    R2(config)#interface gig 0/2.2\n    R2(config-subif)#encapsulation dot1q 2\n    R2(config-subif)#ip address 10.10.10.30 255.255.255.224\n    R2(config-subif)#exit\n    R2(config)#interface gig 0/2.3                   \n    R2(config-subif)#encapsulation dot1q 3                 \n    R2(config-subif)#ip address 10.10.10.46 255.255.255.240\n    R2(config-subif)#end\n</pre></code>\n\n<pre><code>\n\n    <b>R5 IPv4 interface configuration:</b>\n\n    R5#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    R5(config)#interface gig0/2\n    R5(config-if)#ip address 10.10.10.33 255.255.255.240\n    R5(config-if)#no shutdown\n    R5(config-if)#end\n\n</pre></code>\n\n<pre><code>\n\n    <b>PC3 IPv4 Addressing Configuration</b>\n\n    PC3> <b>ip 10.10.10.1/27 10.10.10.30</b>\n    Checking for duplicate address...\n    PC3 : 10.10.10.1 255.255.255.224 gateway 10.10.10.30\n\n</pre></code>\n\n\n***Verification of IPv4 Addressing***\n\nPinging various addresses from PC3\n\n<pre><code>\n    PC3> ping <b>10.10.10.49</b> -c 2\n\n    84 bytes from 10.10.10.49 icmp_seq=1 ttl=255 time=12.907 ms\n    84 bytes from 10.10.10.49 icmp_seq=2 ttl=255 time=9.861 ms\n\n    PC3> ping <b>10.10.10.2</b> -c 2\n\n    84 bytes from 10.10.10.2 icmp_seq=1 ttl=255 time=6.282 ms\n    84 bytes from 10.10.10.2 icmp_seq=2 ttl=255 time=6.699 ms\n\n    PC3> ping <b>10.10.10.50</b> -c 2\n\n    84 bytes from 10.10.10.50 icmp_seq=1 ttl=255 time=7.710 ms\n    84 bytes from 10.10.10.50 icmp_seq=2 ttl=255 time=8.574 ms\n\n    PC3> ping <b>10.10.10.30</b> -c 2\n\n    84 bytes from 10.10.10.30 icmp_seq=1 ttl=255 time=7.186 ms\n    84 bytes from 10.10.10.30 icmp_seq=2 ttl=255 time=9.011 ms\n\n    PC3> ping <b>10.10.10.46</b> -c 2\n\n    84 bytes from 10.10.10.46 icmp_seq=1 ttl=255 time=7.251 ms\n    84 bytes from 10.10.10.46 icmp_seq=2 ttl=255 time=9.625 ms\n\n    PC3>\n\n</pre></code>\n\nValidating that R5 can SSH into R2:\n\n<pre><code>\n    <b>R5#ssh -l ine 10.10.10.46</b>\n\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n    <b>Password:</b>\n\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n    <b>R2#</b>\n\n    Seeing R2's prompt is proof that R5 was successful in SSHing into R2.\n\n</pre></code>\n\n\nValidating that R2 can Telnet into R1:\n\n<pre><code>\n\n    <b>R2#telnet 10.10.10.49</b>   \n    Trying 10.10.10.49 ... <b>Open</b>\n\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n\n    <b>User Access Verification\n\n    Password: </b>\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n    <b>R1></b>\n\n</pre></code>",
    "solutions_html": "<p><strong>Solutions:</strong></p>\n<p>&nbsp;&nbsp;&nbsp;&nbsp;<strong>Initial Configuration Solutions:</strong></p>\n<ol>\n<li>\n<p>The following commands would be applied to all devices:</p>\n<p><pre><code></p>\n<p><b>hostname [Device Hostname]</b>\n!\n<b>enable password cisco</b>\n!\n<b>no ip domain-lookup</b>\n!\ninterface GigabitEthernetX/Y\n <b>no shutdown</b>\n!\nline con 0\n <b>logging synchronous</b></p>\n<p></pre></code></p>\n</li>\n<li>\n<p>R1 Telnet commands:</p>\n<p><pre><code>\nline vty 0 4\n <b>password cisco</b>\n login\n <b>transport input telnet</b>\n</pre></code></p>\n</li>\n<li>\n<p>R2 SSH commands:</p>\n<p><pre><code>\nR2#conf t\nEnter configuration commands, one per line.  End with CNTL/Z.\nR2(config)#<b>ip domain-name ine.com</b>\nR2(config)#<b>ip ssh version 2</b>\nPlease create RSA keys to enable SSH (and of at least 768 bits for SSH v2).\nR2(config)#<b>crypto key generate rsa</b>\nThe name for the keys will be: R2.ine.com\nChoose the size of the key modulus in the range of 360 to 4096 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes.</p>\n<p>How many bits in the modulus [512]: <b>1024</b>\n% Generating 1024 bit RSA keys, keys will be non-    exportable...\n[OK] (elapsed time was 1 seconds)</p>\n<p>R2(config)#\n*Jul 26 20:14:11.257: %SSH-5-ENABLED: SSH 2.0 has been  enabled\nR2(config)#<b>username ine privilege 15 password cisco</b>\n WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\nR2(config)#\n*Jul 26 20:14:30.792: %AAAA-4-CLI_DEPRECATED: WARNING: Command has been added to the configuration using a type 0 password. However, type 0 passwords will soon be deprecated. Migrate to a supported password type\nR2(config)#<b>line vty 0 4</b>\nR2(config-line)#<b>transport input ssh</b>\nR2(config-line)#<b>login local</b>\nR2(config-line)#end\nR2#\n</pre></code></p>\n</li>\n</ol>\n<p>&nbsp;&nbsp;&nbsp;&nbsp;<strong>Implementing Basic Switching Solutions:</strong></p>\n<pre><code>\n\n    <b>Only relevant portions of the switch configuration are shown below:</b>\n\n    Switch-2#sh run\n    Building configuration...\n\n    !\n    hostname Switch-2\n    !\n    <b>vlan 2-3</b>\n    !\n    !\n    interface GigabitEthernet0/0\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n\n    !\n    interface GigabitEthernet0/1\n     <b>switchport access vlan 2</b>\n     <b>switchport mode access</b>\n\n    !\n    interface GigabitEthernet0/2\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode trunk</b>\n     <b>switchport nonegotiate</b>\n\n    !\n    interface GigabitEthernet0/3\n     <b>switchport trunk native vlan 2</b>\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n\n    !\n    !\n    end\n\n    Switch-2#\n\n</pre>\n\n<p></code></p>\n<pre><code>\n\n    [Only relevant portions of the configuration are shown below]\n\n    Switch-3#sh run\n    Building configuration...\n\n    !\n    <b>vlan 2-3</b>\n    !\n    interface GigabitEthernet0/0\n     <b>switchport access vlan 2</b>\n     <b>switchport mode access</b>\n    !\n    interface GigabitEthernet0/1\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n\n    !\n    interface GigabitEthernet0/2\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n\n    !\n    interface GigabitEthernet3/0\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic desirable</b>\n\n    !\n    end\n\n\n    Switch-3#\n\n</pre>\n\n<p></code></p>\n<pre><code>\n\n    [Only relevant portions of the configuration are displayed]\n\n    Switch-4#show  run\n    Building configuration...\n    !\n    hostname Switch-4\n    !\n    !\n    <b>vlan 2-3</b>\n    !\n    interface GigabitEthernet0/0\n     <b>switchport trunk native vlan 2</b>\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n\n    !\n    interface GigabitEthernet0/1\n     <b>switchport access vlan 3</b>\n     <b>switchport mode access</b>\n\n    !\n    interface GigabitEthernet0/2\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n\n    !\n    interface GigabitEthernet3/0\n     <b>switchport trunk encapsulation dot1q</b>\n     <b>switchport mode dynamic auto</b>\n\n    !\n    end\n\n    Switch-4#\n\n</pre>\n\n<p></code></p>\n<p>&nbsp;&nbsp;&nbsp;&nbsp;<strong>IP Addressing and Subnetting Solutions:</strong></p>\n<ol>\n<li>Starting network is 10.10.10.0/24</li>\n</ol>\n<table>\n<thead>\n<tr>\n<th>Link ID</th>\n<th>Qty of Hosts</th>\n<th>Subnet Mask</th>\n<th>Network/Prefix</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>M/F/G</td>\n<td>29</td>\n<td>255.255.255.224</td>\n<td>10.10.10.0</td>\n</tr>\n<tr>\n<td>N/G</td>\n<td>12</td>\n<td>255.255.255.240</td>\n<td>10.10.10.32</td>\n</tr>\n<tr>\n<td>C</td>\n<td>2</td>\n<td>255.255.255.252</td>\n<td>10.10.10.48</td>\n</tr>\n</tbody>\n</table>\n<table>\n<thead>\n<tr>\n<th>Device</th>\n<th>Interface</th>\n<th>IPv4 Address</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>R1</td>\n<td>Gig0/0</td>\n<td>10.10.10.49 /30</td>\n</tr>\n<tr>\n<td>R1</td>\n<td>Gig0/1</td>\n<td>10.10.10.2 /27</td>\n</tr>\n<tr>\n<td>R2</td>\n<td>Gig0/0</td>\n<td>10.10.10.50 /30</td>\n</tr>\n<tr>\n<td>R2</td>\n<td>Gig0/2.2</td>\n<td>10.10.10.30 /27</td>\n</tr>\n<tr>\n<td>R2</td>\n<td>Gig0/2.3</td>\n<td>10.10.10.46 /28</td>\n</tr>\n<tr>\n<td>R5</td>\n<td>Gig0/2</td>\n<td>10.10.10.33 /28</td>\n</tr>\n<tr>\n<td>PC3</td>\n<td>Eth0</td>\n<td>10.10.10.1 /27</td>\n</tr>\n</tbody>\n</table>\n<ol>\n<li>Configuration of IPv4 addresses:</li>\n</ol>\n<pre><code>\n\n    <b>R1 IPv4 interface configuration:</b>\n\n    R1#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    R1(config)#int gig 0/0\n    R1(config-if)#ip address 10.10.10.49 255.255.255.252\n    R1(config-if)#no shutdown\n    R1(config-if)#exit\n    R1(config)#\n    *Jul 28 18:57:52.480: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up\n    *Jul 28 18:57:53.480: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0,     changed state to up\n    R1(config)#int gig 0/1\n    R1(config-if)#ip add 10.10.10.2 255.255.255.224\n    R1(config-if)#no shutdown\n    R1(config-if)#end\n    R1#\n\n</pre>\n\n<p></code></p>\n<pre><code>\n\n    <b>R2 IPv4 interface configuration:</b>\n\n    R2#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    R2(config)#interface gig0/0\n    R2(config-if)#ip address 10.10.10.50 255.255.255.252\n    R2(config-if)#no shutdown\n    R2(config-if)#exit\n    *Jul 28 19:00:02.188: %LINK-3-UPDOWN: Interface GigabitEthernet0/0, changed state to up\n    *Jul 28 19:00:03.188: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0,     changed state to up\n    R2(config-if)#exit\n    R2(config)#interface gig 0/2\n    R2(config-if)#no shutdown\n    R2(config-if)#exit\n    R2(config)#interface gig 0/2.2\n    R2(config-subif)#encapsulation dot1q 2\n    R2(config-subif)#ip address 10.10.10.30 255.255.255.224\n    R2(config-subif)#exit\n    R2(config)#interface gig 0/2.3                   \n    R2(config-subif)#encapsulation dot1q 3                 \n    R2(config-subif)#ip address 10.10.10.46 255.255.255.240\n    R2(config-subif)#end\n</pre>\n\n<p></code></p>\n<pre><code>\n\n    <b>R5 IPv4 interface configuration:</b>\n\n    R5#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    R5(config)#interface gig0/2\n    R5(config-if)#ip address 10.10.10.33 255.255.255.240\n    R5(config-if)#no shutdown\n    R5(config-if)#end\n\n</pre>\n\n<p></code></p>\n<pre><code>\n\n    <b>PC3 IPv4 Addressing Configuration</b>\n\n    PC3> <b>ip 10.10.10.1/27 10.10.10.30</b>\n    Checking for duplicate address...\n    PC3 : 10.10.10.1 255.255.255.224 gateway 10.10.10.30\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Verification of IPv4 Addressing</em></strong></p>\n<p>Pinging various addresses from PC3</p>\n<pre><code>\n    PC3> ping <b>10.10.10.49</b> -c 2\n\n    84 bytes from 10.10.10.49 icmp_seq=1 ttl=255 time=12.907 ms\n    84 bytes from 10.10.10.49 icmp_seq=2 ttl=255 time=9.861 ms\n\n    PC3> ping <b>10.10.10.2</b> -c 2\n\n    84 bytes from 10.10.10.2 icmp_seq=1 ttl=255 time=6.282 ms\n    84 bytes from 10.10.10.2 icmp_seq=2 ttl=255 time=6.699 ms\n\n    PC3> ping <b>10.10.10.50</b> -c 2\n\n    84 bytes from 10.10.10.50 icmp_seq=1 ttl=255 time=7.710 ms\n    84 bytes from 10.10.10.50 icmp_seq=2 ttl=255 time=8.574 ms\n\n    PC3> ping <b>10.10.10.30</b> -c 2\n\n    84 bytes from 10.10.10.30 icmp_seq=1 ttl=255 time=7.186 ms\n    84 bytes from 10.10.10.30 icmp_seq=2 ttl=255 time=9.011 ms\n\n    PC3> ping <b>10.10.10.46</b> -c 2\n\n    84 bytes from 10.10.10.46 icmp_seq=1 ttl=255 time=7.251 ms\n    84 bytes from 10.10.10.46 icmp_seq=2 ttl=255 time=9.625 ms\n\n    PC3>\n\n</pre>\n\n<p></code></p>\n<p>Validating that R5 can SSH into R2:</p>\n<pre><code>\n    <b>R5#ssh -l ine 10.10.10.46</b>\n\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n    <b>Password:</b>\n\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n    <b>R2#</b>\n\n    Seeing R2's prompt is proof that R5 was successful in SSHing into R2.\n\n</pre>\n\n<p></code></p>\n<p>Validating that R2 can Telnet into R1:</p>\n<pre><code>\n\n    <b>R2#telnet 10.10.10.49</b>   \n    Trying 10.10.10.49 ... <b>Open</b>\n\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n\n    <b>User Access Verification\n\n    Password: </b>\n    **************************************************************************\n    * IOSv is strictly limited to use for evaluation, demonstration and IOS  *\n    * education. IOSv is provided as-is and is not supported by Cisco's      *\n    * Technical Advisory Center. Any use or disclosure, in whole or in part, *\n    * of the IOSv Software or Documentation to any third party for any       *\n    * purposes is expressly prohibited except as otherwise authorized by     *\n    * Cisco in writing.                                                      *\n    **************************************************************************\n    <b>R1></b>\n\n</pre>\n\n<p></code></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
}