{
    "id": "df98e086-35ca-41cd-860d-a7e43e521a4f",
    "name": "Implementing Essential Switching",
    "slug": "implementing-essential-switching",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "84511766-3c0b-48c4-bba4-4cca692382bf"
        ],
        "pta_sdn": "242",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-07-07T13:35:45.567199Z",
    "modified": "2023-10-03T18:59:06.427553Z",
    "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/ptp/Keith/VOD-5333/Lab-3916/diagram.png)\n\n\n***NOTE:*** Please read the following lab guidelines before working on this lab.\n- If any device contains preconfigured login credentials use, **cisco/cisco**\n- If you plan working on more than one Lab Task during the day (all related to the same course), open the first lab environment and keep it open for subsequent labs (unless instructed otherwise) to save yourself excessive bootup time. Simply read the Lab Objectives from subsequent labs and perform them on your first, opened lab environment.",
    "description_html": "<p><img alt=\"description\" src=\"https://assets.ine.com/content/ptp/Keith/VOD-5333/Lab-3916/diagram.png\" /></p>\n<p><strong><em>NOTE:</em></strong> Please read the following lab guidelines before working on this lab.\n- If any device contains preconfigured login credentials use, <strong>cisco/cisco</strong>\n- If you plan working on more than one Lab Task during the day (all related to the same course), open the first lab environment and keep it open for subsequent labs (unless instructed otherwise) to save yourself excessive bootup time. Simply read the Lab Objectives from subsequent labs and perform them on your first, opened lab environment.</p>",
    "tasks": "**Task-1: Setting A Switch To Factory Default**\n\n\n1. Login to Switch-2 and you'll immediately notice (by viewing the device hostname) that this device has a non-default configuration. You can also confirm this by viewing the output of the command, \"***show vlan***\" and you'll see that in addition to the factory-default VLAN (VLAN-1) this switch also contains VLANs 2-4.\n\n```\nSwitch-2#show vlan\nVLAN Name                             Status    Ports\n---- -------------------------------- --------- -------------------------------\n1    default                          active    Gi0/0, Gi0/1, Gi0/2, Gi0/3\n                                                Gi1/0, Gi1/1, Gi1/2, Gi1/3\n                                                Gi2/0, Gi2/1, Gi2/2, Gi2/3\n                                                Gi3/0, Gi3/1, Gi3/2, Gi3/3\n2    VLAN0002                         active    \n3    VLAN0003                         active    \n4    VLAN0004                         active    \n```\n\n2. Set Switch-2 back to a factory-default state. When finished, the switch should display the default hostname of \"Switch\" and VLANs 2-4 should no longer be present.\n\n\n**Task-2: Applying Basic Switch Parameters**\n\n1. Assign the IPv4 address of ***10.0.0.3/26*** to PC1 using the following process:\n\n    <pre><code>\n    PC1> <b>ip 10.0.0.3/26 10.0.0.1</b>  \n    Checking for duplicate address...\n    PC1 : 10.0.0.3 255.255.255.192 gateway 10.0.0.1\n    </pre></code>\n\n2. Complete the following objectives on Switch-2:\n\n    |Objective|Command used to complete the objective|\n    |---|---|\n    |Change Switch-2's hostname to \"Switch-2\"|\n    |Use a single command to administratively disable ports Gig2/0 through Gig3/3|\n    |Apply a comment within Gig0/1 that reads, \"Connected to Switch-1\"|\n    |Apply a management IPv4 address of 10.0.0.22/26 that will be reachable by all hosts in VLAN-1|\n    |Login to PC-1 and ping the management IPv4 address of Switch-2|\n\n3. Use a Cisco IOS command on Switch-2 to confirm that interfaces Gig2/0 through 3/3 are administratively down.\n\n    - You may ***NOT*** use the \"show running-config\" command\n    - The command should display the status of all interfaces on a single screen\n    - The command should also confirm the VLAN each port is in and the duplex.\n\n\n**Task-3: Extracting Information From The MAC Address-Table**\n\n1. From PC-1, ping the address of 10.0.0.22 (management address of Switch-2).\n\n2. Issue a command on Switch-2 that allows you to discern the MAC address of PC-1.\n\n3. Login to router R1 and confirm that this router has been pre-configured with the IPv4 address of 10.0.0.1 on interface Gig0/1.  If you DON'T see that IPv4 address on that interface, configure it and ensure the interface is Up/Up.\n\n4. Ping from PC-1 to R1 (10.0.0.1).  Determine the path these pings took through the switched network.",
    "tasks_html": "<p><strong>Task-1: Setting A Switch To Factory Default</strong></p>\n<ol>\n<li>Login to Switch-2 and you'll immediately notice (by viewing the device hostname) that this device has a non-default configuration. You can also confirm this by viewing the output of the command, \"<strong><em>show vlan</em></strong>\" and you'll see that in addition to the factory-default VLAN (VLAN-1) this switch also contains VLANs 2-4.</li>\n</ol>\n<pre class=\"codehilite\"><code>Switch-2#show vlan\nVLAN Name                             Status    Ports\n---- -------------------------------- --------- -------------------------------\n1    default                          active    Gi0/0, Gi0/1, Gi0/2, Gi0/3\n                                                Gi1/0, Gi1/1, Gi1/2, Gi1/3\n                                                Gi2/0, Gi2/1, Gi2/2, Gi2/3\n                                                Gi3/0, Gi3/1, Gi3/2, Gi3/3\n2    VLAN0002                         active    \n3    VLAN0003                         active    \n4    VLAN0004                         active    </code></pre>\n\n<ol>\n<li>Set Switch-2 back to a factory-default state. When finished, the switch should display the default hostname of \"Switch\" and VLANs 2-4 should no longer be present.</li>\n</ol>\n<p><strong>Task-2: Applying Basic Switch Parameters</strong></p>\n<ol>\n<li>\n<p>Assign the IPv4 address of <strong><em>10.0.0.3/26</em></strong> to PC1 using the following process:</p>\n<p><pre><code>\nPC1&gt; <b>ip 10.0.0.3/26 10.0.0.1</b><br />\nChecking for duplicate address...\nPC1 : 10.0.0.3 255.255.255.192 gateway 10.0.0.1\n</pre></code></p>\n</li>\n<li>\n<p>Complete the following objectives on Switch-2:</p>\n<table>\n<thead>\n<tr>\n<th>Objective</th>\n<th>Command used to complete the objective</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>Change Switch-2's hostname to \"Switch-2\"</td>\n<td></td>\n</tr>\n<tr>\n<td>Use a single command to administratively disable ports Gig2/0 through Gig3/3</td>\n<td></td>\n</tr>\n<tr>\n<td>Apply a comment within Gig0/1 that reads, \"Connected to Switch-1\"</td>\n<td></td>\n</tr>\n<tr>\n<td>Apply a management IPv4 address of 10.0.0.22/26 that will be reachable by all hosts in VLAN-1</td>\n<td></td>\n</tr>\n<tr>\n<td>Login to PC-1 and ping the management IPv4 address of Switch-2</td>\n<td></td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Use a Cisco IOS command on Switch-2 to confirm that interfaces Gig2/0 through 3/3 are administratively down.</p>\n<ul>\n<li>You may <strong><em>NOT</em></strong> use the \"show running-config\" command</li>\n<li>The command should display the status of all interfaces on a single screen</li>\n<li>The command should also confirm the VLAN each port is in and the duplex.</li>\n</ul>\n</li>\n</ol>\n<p><strong>Task-3: Extracting Information From The MAC Address-Table</strong></p>\n<ol>\n<li>\n<p>From PC-1, ping the address of 10.0.0.22 (management address of Switch-2).</p>\n</li>\n<li>\n<p>Issue a command on Switch-2 that allows you to discern the MAC address of PC-1.</p>\n</li>\n<li>\n<p>Login to router R1 and confirm that this router has been pre-configured with the IPv4 address of 10.0.0.1 on interface Gig0/1.  If you DON'T see that IPv4 address on that interface, configure it and ensure the interface is Up/Up.</p>\n</li>\n<li>\n<p>Ping from PC-1 to R1 (10.0.0.1).  Determine the path these pings took through the switched network.</p>\n</li>\n</ol>",
    "published_date": "2022-07-18T16:06:42Z",
    "solutions": "**Solutions:**\n\n***Task-1 Solution***\n\n1. Erasing the startup configuration files\n\n    ```\n    Switch-2#erase startup-config\n    Erasing the nvram filesystem will remove all configuration files! Continue? [confirm]\n    [OK]\n    Erase of nvram: complete\n    Switch-2#\n    ```\n\n2. Erasing the VLAN.dat file\n\n    ***NOTE:*** On a real Cisco switch, the VLAN.dat file would also need to be deleted (which is stored in \"flash:\" memory).  If     you don't delete this file, your non-default VLANs will persist after a reload.  However, because the switches in this lab     environment are emulated, their VLAN.dat file is stored in NVRAM. Hopefully you discovered this for yourself using the     command, \"***dir all***\" to search for the location of this file.\n\n    <pre><code>\n    <b>Here we see that attempting to delete the vlan.dat file from its normal location fails:</b>\n\n    Switch-2#<b>delete flash:vlan.dat</b>\n    Delete filename [vlan.dat]?\n    Delete flash0:/vlan.dat? [confirm]\n    %Error deleting flash0:/vlan.dat <b>(File not found)</b>\n\n    Switch-2#dir all\n    Directory of flash0:/\n\n        1  drw-           0  Jan 30 2013 00:00:00 +00:00  boot\n      264  drw-           0  Oct 14 2013 00:00:00 +00:00  config\n\n    [Output Omitted For Brevity]\n\n    No space information available\n    <b>Directory of nvram</b>:/\n\n      254  -rw-           0                    <no date>  startup-config\n      255  ----           0                    <no date>  private-config\n        1  ----          31                    <no date>  udi\n        2  ----          35                    <no date>  persistent-data\n        3  -rw-         736                    <no date>  <b>vlan.dat</b>  <-----\n        4  -rw-           0                    <no date>  ifIndex-table\n\n    Switch-2#delete nvram:vlan.dat\n    Delete filename [vlan.dat]?\n    Delete nvram:vlan.dat? [confirm]\n    Switch-2#\n\n    Switch-2#<b>reload</b>\n    Proceed with reload? [confirm]\n\n    *Jun 29 13:59:42.708: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload command.\n     *Jun 29 13:59:45.728\n\n    </pre></code>\n\n3. Verification of success:\n\n    <pre><code>\n\n    <b>Switch</b>>  <-----Hostname is back to the default name for a Cisco switch\n    Switch>enable\n    Switch#<b>show vlan</b>\n\n    VLAN Name                             Status    Ports\n    ---- -------------------------------- --------- -------------------------------\n    1    default                          active    Gi0/0, Gi0/1, Gi0/2, Gi0/3\n                                                    Gi1/0, Gi1/1, Gi1/2, Gi1/3\n                                                    Gi2/0, Gi2/1, Gi2/2, Gi2/3\n                                                    Gi3/0, Gi3/1, Gi3/2, Gi3/3\n    1002 fddi-default                     act/unsup\n\n    <b>VLANs 2-4 are now gone.</b>\n\n    </pre></code>\n\n\n\n***Task-2 Solution***\n\n1. Change Switch-2's hostname to \"Switch-2\"\n\n    <pre><code>\n    Switch>\n    Switch>enable\n    Switch#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    Switch(config)#<b>hostname Switch-2</b>\n    Switch-2(config)#end\n    Switch-2#\n    </pre></code>\n\n2. Use a single command to administratively disable ports Gig2/0 through Gig3/3\n\n    <pre><code>\n    Switch-2#config t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    Switch-2(config)#<b>interface range gig 2/0 - 3 , gig 3/0 - 3</b>\n    Switch-2(config-if-range)#shutdown\n    Switch-2(config-if-range)#end\n    Switch-2#\n    *Jun 29 14:24:56.352: %SYS-5-CONFIG_I: Configured from console by console\n    *Jun 29 14:24:57.028: %LINK-5-CHANGED: Interface GigabitEthernet2/0, changed state to administratively down\n    </pre></code>\n\n3. Apply a comment within Gig0/1 that reads, \"Connected to Switch-1\"\n\n    <pre><code>\n    Switch-2#\n    Switch-2#config t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    Switch-2(config)#interface gig 0/1\n    Switch-2(config-if)#<b>description Connected to Switch-1</b>\n    Switch-2(config-if)#end\n    Switch-2#\n    Switch-2#\n    *Jun 29 14:25:43.403: %SYS-5-CONFIG_I: Configured from console by console\n    Switch-2#show run interface gig 0/1\n    Building configuration...\n\n    Current configuration : 89 bytes\n    !\n    interface GigabitEthernet0/1\n     <b>description Connected to Switch-1</b>\n     negotiation auto\n    end\n    </pre></code>\n\n\n4. Apply a management IPv4 address of 10.0.0.22/26 that will be reachable by all hosts in VLAN-1\n\n    <pre><code>\n    Switch-2#conf t\n    Enter configuration commands, one per line.  End with CNTL/Z.\n    Switch-2(config)#<b>interface vlan 1</b>\n    Switch-2(config-if)#<b>ip address 10.0.0.22 255.255.255.192</b>\n    Switch-2(config-if)#<b>no shutdown</b>\n    Switch-2(config-if)#end\n    Switch-2#\n    *Jun 29 14:27:13.256: %SYS-5-CONFIG_I: Configured from console by console\n    Switch-2#\n    *Jun 29 14:27:14.233: %LINK-3-UPDOWN: Interface Vlan1, changed state to up\n    *Jun 29 14:27:15.233: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up\n    Switch-2#\n    </pre></code>\n\n5. Login to PC-1 and ping the management IPv4 address of Switch-2\n\n    ```\n    PC1> ping 10.0.0.22\n    84 bytes from 10.0.0.22 icmp_seq=1 ttl=255 time=1.855 ms\n    84 bytes from 10.0.0.22 icmp_seq=2 ttl=255 time=1.524 ms\n    84 bytes from 10.0.0.22 icmp_seq=3 ttl=255 time=1.478 ms\n    ```\n\n6. The command that meets the criteria for viewing the interface status is \"***show interfaces status***\"\n\n    ```\n    Switch-2#show interfaces status\n    Port      Name               Status       Vlan       Duplex  Speed Type\n    Gi0/0                        connected    1          a-full   auto RJ45\n    Gi0/1     Connected to Switc connected    1          a-full   auto RJ45\n    Gi0/2                        connected    1          a-full   auto RJ45\n    Gi0/3                        notconnect   1          a-full   auto RJ45\n    Gi1/0                        notconnect   1          a-full   auto RJ45\n    Gi1/1                        notconnect   1          a-full   auto RJ45\n    Gi1/2                        notconnect   1          a-full   auto RJ45\n    Gi1/3                        notconnect   1          a-full   auto RJ45\n    Gi2/0                        disabled     1            auto   auto RJ45\n    Gi2/1                        disabled     1            auto   auto RJ45\n    Gi2/2                        disabled     1            auto   auto RJ45\n    Gi2/3                        disabled     1            auto   auto RJ45\n    Gi3/0                        disabled     1            auto   auto RJ45\n    Gi3/1                        disabled     1            auto   auto RJ45\n    Gi3/2                        disabled     1            auto   auto RJ45\n    Gi3/3                        disabled     1            auto   auto RJ45\n    ```\n\n***Task-3 Solutions***\n\n1. Pinging from PC-1 to 10.0.0.22\n\n    ```\n    PC1> ping 10.0.0.22\n    84 bytes from 10.0.0.22 icmp_seq=1 ttl=255 time=1.415 ms\n    84 bytes from 10.0.0.22 icmp_seq=2 ttl=255 time=1.528 ms\n    84 bytes from 10.0.0.22 icmp_seq=3 ttl=255 time=1.494 ms\n    84 bytes from 10.0.0.22 icmp_seq=4 ttl=255 time=1.455 ms\n    84 bytes from 10.0.0.22 icmp_seq=5 ttl=255 time=1.408 ms\n    PC1>\n    ```\n\n2. Discerning the MAC address of PC-1 by viewing output from Switch-2:\n\n    <pre><code>\n    Switch-2#<b>show mac address-table dynamic interface gig0/0</b>\n              Mac Address Table\n    -------------------------------------------\n\n    Vlan    Mac Address       Type        Ports\n    ----    -----------       --------    -----\n       1    <b>0050.7966.6800</b>    DYNAMIC     Gi0/0\n    Total Mac Addresses for this criterion: 1\n    Switch-2#\n    </pre></code>\n\n3. Confirming an IP address on router R1:\n\n    ```\n    Router#show ip interface brief\n    Interface                  IP-Address      OK? Method Status                Protocol\n    GigabitEthernet0/0         unassigned      YES NVRAM  administratively down down    \n    GigabitEthernet0/1         10.0.0.1        YES NVRAM  up                    up  \n    ```\n\n4. Once you learned the MAC address of PC-1 (in Task-3: Step-2) you can now view the MAC Address-tables of all three switches and identify which ports learned of this MAC. The ports upon which this MAC was learned are the ONLY ports that will receive frames from this source MAC, and transmit frames BACK to this source MAC.\n\n    <pre><code>\n\n    <b>In my topology, PC-1's MAC address was 0050.7966.6800</b>:\n\n    Switch-2#show mac address-table dynamic interface gig0/0\n              Mac Address Table\n    -------------------------------------------\n\n    Vlan    Mac Address       Type        Ports\n    ----    -----------       --------    -----\n       1    <b>0050.7966.6800</b>    DYNAMIC     Gi0/0\n    </pre></code>\n\n\n    <pre><code>\n    <b>Switch-1 learned of this MAC on port Gig0/3</b>:\n\n    Switch-1#show mac address-table address 0050.7966.6800\n              Mac Address Table\n    -------------------------------------------\n\n    Vlan    Mac Address       Type        Ports\n    ----    -----------       --------    -----\n       1    <b>0050.7966.6800    DYNAMIC     Gi0/3</b>\n    </pre></code>\n\n\n    <pre><code>\n    <b>Switch-3 learned of this MAC on port Gig0/2</b>:\n\n    Switch-3#show mac address-table address 0050.7966.6800\n              Mac Address Table\n    -------------------------------------------\n\n    Vlan    Mac Address       Type        Ports\n    ----    -----------       --------    -----\n       1    <b>0050.7966.6800    DYNAMIC     Gi0/2</b>\n    Total Mac Addresses for this criterion: 1\n    Switch-3#\n    </pre></code>\n\n\n\nSo the path through the switched network for frames to/from PC-1 and R1 was as follows:\n\n![description](https://assets.ine.com/content/ptp/Keith/VOD-5333/Lab-3916/switched-path.png)",
    "solutions_html": "<p><strong>Solutions:</strong></p>\n<p><strong><em>Task-1 Solution</em></strong></p>\n<ol>\n<li>\n<p>Erasing the startup configuration files</p>\n<pre class=\"codehilite\"><code>Switch-2#erase startup-config\nErasing the nvram filesystem will remove all configuration files! Continue? [confirm]\n[OK]\nErase of nvram: complete\nSwitch-2#</code></pre>\n\n</li>\n<li>\n<p>Erasing the VLAN.dat file</p>\n<p><strong><em>NOTE:</em></strong> On a real Cisco switch, the VLAN.dat file would also need to be deleted (which is stored in \"flash:\" memory).  If     you don't delete this file, your non-default VLANs will persist after a reload.  However, because the switches in this lab     environment are emulated, their VLAN.dat file is stored in NVRAM. Hopefully you discovered this for yourself using the     command, \"<strong><em>dir all</em></strong>\" to search for the location of this file.</p>\n<p><pre><code>\n<b>Here we see that attempting to delete the vlan.dat file from its normal location fails:</b></p>\n<p>Switch-2#<b>delete flash:vlan.dat</b>\nDelete filename [vlan.dat]?\nDelete flash0:/vlan.dat? [confirm]\n%Error deleting flash0:/vlan.dat <b>(File not found)</b></p>\n<p>Switch-2#dir all\nDirectory of flash0:/</p>\n<pre class=\"codehilite\"><code>1  drw-           0  Jan 30 2013 00:00:00 +00:00  boot</code></pre>\n\n\n<p>264  drw-           0  Oct 14 2013 00:00:00 +00:00  config</p>\n<p>[Output Omitted For Brevity]</p>\n<p>No space information available\n<b>Directory of nvram</b>:/</p>\n<p>254  -rw-           0                    <no date>  startup-config\n  255  ----           0                    <no date>  private-config\n    1  ----          31                    <no date>  udi\n    2  ----          35                    <no date>  persistent-data\n    3  -rw-         736                    <no date>  <b>vlan.dat</b>  &lt;-----\n    4  -rw-           0                    <no date>  ifIndex-table</p>\n<p>Switch-2#delete nvram:vlan.dat\nDelete filename [vlan.dat]?\nDelete nvram:vlan.dat? [confirm]\nSwitch-2#</p>\n<p>Switch-2#<b>reload</b>\nProceed with reload? [confirm]</p>\n<p>*Jun 29 13:59:42.708: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload command.\n *Jun 29 13:59:45.728</p>\n<p></pre></code></p>\n</li>\n<li>\n<p>Verification of success:</p>\n<p><pre><code></p>\n<p><b>Switch</b>&gt;  &lt;-----Hostname is back to the default name for a Cisco switch\nSwitch&gt;enable\nSwitch#<b>show vlan</b></p>\n<p>VLAN Name                             Status    Ports</p>\n<hr />\n<p>1    default                          active    Gi0/0, Gi0/1, Gi0/2, Gi0/3\n                                                Gi1/0, Gi1/1, Gi1/2, Gi1/3\n                                                Gi2/0, Gi2/1, Gi2/2, Gi2/3\n                                                Gi3/0, Gi3/1, Gi3/2, Gi3/3\n1002 fddi-default                     act/unsup</p>\n<p><b>VLANs 2-4 are now gone.</b></p>\n<p></pre></code></p>\n</li>\n</ol>\n<p><strong><em>Task-2 Solution</em></strong></p>\n<ol>\n<li>\n<p>Change Switch-2's hostname to \"Switch-2\"</p>\n<p><pre><code>\nSwitch&gt;\nSwitch&gt;enable\nSwitch#conf t\nEnter configuration commands, one per line.  End with CNTL/Z.\nSwitch(config)#<b>hostname Switch-2</b>\nSwitch-2(config)#end\nSwitch-2#\n</pre></code></p>\n</li>\n<li>\n<p>Use a single command to administratively disable ports Gig2/0 through Gig3/3</p>\n<p><pre><code>\nSwitch-2#config t\nEnter configuration commands, one per line.  End with CNTL/Z.\nSwitch-2(config)#<b>interface range gig 2/0 - 3 , gig 3/0 - 3</b>\nSwitch-2(config-if-range)#shutdown\nSwitch-2(config-if-range)#end\nSwitch-2#\n*Jun 29 14:24:56.352: %SYS-5-CONFIG_I: Configured from console by console\n*Jun 29 14:24:57.028: %LINK-5-CHANGED: Interface GigabitEthernet2/0, changed state to administratively down\n</pre></code></p>\n</li>\n<li>\n<p>Apply a comment within Gig0/1 that reads, \"Connected to Switch-1\"</p>\n<p><pre><code>\nSwitch-2#\nSwitch-2#config t\nEnter configuration commands, one per line.  End with CNTL/Z.\nSwitch-2(config)#interface gig 0/1\nSwitch-2(config-if)#<b>description Connected to Switch-1</b>\nSwitch-2(config-if)#end\nSwitch-2#\nSwitch-2#\n*Jun 29 14:25:43.403: %SYS-5-CONFIG_I: Configured from console by console\nSwitch-2#show run interface gig 0/1\nBuilding configuration...</p>\n<p>Current configuration : 89 bytes\n!\ninterface GigabitEthernet0/1\n <b>description Connected to Switch-1</b>\n negotiation auto\nend\n</pre></code></p>\n</li>\n<li>\n<p>Apply a management IPv4 address of 10.0.0.22/26 that will be reachable by all hosts in VLAN-1</p>\n<p><pre><code>\nSwitch-2#conf t\nEnter configuration commands, one per line.  End with CNTL/Z.\nSwitch-2(config)#<b>interface vlan 1</b>\nSwitch-2(config-if)#<b>ip address 10.0.0.22 255.255.255.192</b>\nSwitch-2(config-if)#<b>no shutdown</b>\nSwitch-2(config-if)#end\nSwitch-2#\n*Jun 29 14:27:13.256: %SYS-5-CONFIG_I: Configured from console by console\nSwitch-2#\n*Jun 29 14:27:14.233: %LINK-3-UPDOWN: Interface Vlan1, changed state to up\n*Jun 29 14:27:15.233: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up\nSwitch-2#\n</pre></code></p>\n</li>\n<li>\n<p>Login to PC-1 and ping the management IPv4 address of Switch-2</p>\n<pre class=\"codehilite\"><code>PC1&gt; ping 10.0.0.22\n84 bytes from 10.0.0.22 icmp_seq=1 ttl=255 time=1.855 ms\n84 bytes from 10.0.0.22 icmp_seq=2 ttl=255 time=1.524 ms\n84 bytes from 10.0.0.22 icmp_seq=3 ttl=255 time=1.478 ms</code></pre>\n\n</li>\n<li>\n<p>The command that meets the criteria for viewing the interface status is \"<strong><em>show interfaces status</em></strong>\"</p>\n<pre class=\"codehilite\"><code>Switch-2#show interfaces status\nPort      Name               Status       Vlan       Duplex  Speed Type\nGi0/0                        connected    1          a-full   auto RJ45\nGi0/1     Connected to Switc connected    1          a-full   auto RJ45\nGi0/2                        connected    1          a-full   auto RJ45\nGi0/3                        notconnect   1          a-full   auto RJ45\nGi1/0                        notconnect   1          a-full   auto RJ45\nGi1/1                        notconnect   1          a-full   auto RJ45\nGi1/2                        notconnect   1          a-full   auto RJ45\nGi1/3                        notconnect   1          a-full   auto RJ45\nGi2/0                        disabled     1            auto   auto RJ45\nGi2/1                        disabled     1            auto   auto RJ45\nGi2/2                        disabled     1            auto   auto RJ45\nGi2/3                        disabled     1            auto   auto RJ45\nGi3/0                        disabled     1            auto   auto RJ45\nGi3/1                        disabled     1            auto   auto RJ45\nGi3/2                        disabled     1            auto   auto RJ45\nGi3/3                        disabled     1            auto   auto RJ45</code></pre>\n\n</li>\n</ol>\n<p><strong><em>Task-3 Solutions</em></strong></p>\n<ol>\n<li>\n<p>Pinging from PC-1 to 10.0.0.22</p>\n<pre class=\"codehilite\"><code>PC1&gt; ping 10.0.0.22\n84 bytes from 10.0.0.22 icmp_seq=1 ttl=255 time=1.415 ms\n84 bytes from 10.0.0.22 icmp_seq=2 ttl=255 time=1.528 ms\n84 bytes from 10.0.0.22 icmp_seq=3 ttl=255 time=1.494 ms\n84 bytes from 10.0.0.22 icmp_seq=4 ttl=255 time=1.455 ms\n84 bytes from 10.0.0.22 icmp_seq=5 ttl=255 time=1.408 ms\nPC1&gt;</code></pre>\n\n</li>\n<li>\n<p>Discerning the MAC address of PC-1 by viewing output from Switch-2:</p>\n<p><pre><code>\nSwitch-2#<b>show mac address-table dynamic interface gig0/0</b>\n          Mac Address Table</p>\n<hr />\n<p>Vlan    Mac Address       Type        Ports\n----    -----------       --------    -----\n   1    <b>0050.7966.6800</b>    DYNAMIC     Gi0/0\nTotal Mac Addresses for this criterion: 1\nSwitch-2#\n</pre></code></p>\n</li>\n<li>\n<p>Confirming an IP address on router R1:</p>\n<pre class=\"codehilite\"><code>Router#show ip interface brief\nInterface                  IP-Address      OK? Method Status                Protocol\nGigabitEthernet0/0         unassigned      YES NVRAM  administratively down down    \nGigabitEthernet0/1         10.0.0.1        YES NVRAM  up                    up  </code></pre>\n\n</li>\n<li>\n<p>Once you learned the MAC address of PC-1 (in Task-3: Step-2) you can now view the MAC Address-tables of all three switches and identify which ports learned of this MAC. The ports upon which this MAC was learned are the ONLY ports that will receive frames from this source MAC, and transmit frames BACK to this source MAC.</p>\n<p><pre><code></p>\n<p><b>In my topology, PC-1's MAC address was 0050.7966.6800</b>:</p>\n<p>Switch-2#show mac address-table dynamic interface gig0/0\n          Mac Address Table</p>\n<hr />\n<p>Vlan    Mac Address       Type        Ports\n----    -----------       --------    -----\n   1    <b>0050.7966.6800</b>    DYNAMIC     Gi0/0\n</pre></code></p>\n<p><pre><code>\n<b>Switch-1 learned of this MAC on port Gig0/3</b>:</p>\n<p>Switch-1#show mac address-table address 0050.7966.6800\n          Mac Address Table</p>\n<hr />\n<p>Vlan    Mac Address       Type        Ports\n----    -----------       --------    -----\n   1    <b>0050.7966.6800    DYNAMIC     Gi0/3</b>\n</pre></code></p>\n<p><pre><code>\n<b>Switch-3 learned of this MAC on port Gig0/2</b>:</p>\n<p>Switch-3#show mac address-table address 0050.7966.6800\n          Mac Address Table</p>\n<hr />\n<p>Vlan    Mac Address       Type        Ports\n----    -----------       --------    -----\n   1    <b>0050.7966.6800    DYNAMIC     Gi0/2</b>\nTotal Mac Addresses for this criterion: 1\nSwitch-3#\n</pre></code></p>\n</li>\n</ol>\n<p>So the path through the switched network for frames to/from PC-1 and R1 was as follows:</p>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/ptp/Keith/VOD-5333/Lab-3916/switched-path.png\" /></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
}