{
    "id": "f4772321-b402-4e47-b8a1-42253b19d3ff",
    "name": "Gateway Redundancy with HSRP",
    "slug": "gateway-redundancy-with-hsrp",
    "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-29T16:09:11.800257Z",
    "modified": "2023-10-03T18:59:10.452081Z",
    "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": "a75f5988-0cc5-4a4a-b01a-6164c3cefcc8",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4310/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-4310/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-4310/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-4310/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: Gateway Redundancy with HSRP**\n\n***NOTE:*** The enable password on all IOS devices is \"**INE**\"\n\n\n1. Confirm that PC1 is able to obtain an IPv4 address via DHCP by entering the command, \"**ip dhcp -d**\"\n\n2. Verify that PC1 can ping the IPv4 address of Interface VLAN-2 on Switch-4 (**180.50.0.214**).\n\n3. Identify which router (R1 or R2) is currently serving as the default gateway for PC1.\n\n4. From PC1, initiate an extended ping of 50-pings destined for 180.50.0.214 (interface VLAN-2 on Switch-4)\n\n    - While that ping is in progress, shutdown the downstream interface (connecting to Switch-2) of the default-gateway router used by PC1.\n    - If you shutdown the correct interface on the correct router, the pings should begin to fail on PC1.\n    - Re-enable the downstream interface on the default-gateway router.\n    - If PC1 is still attempting to ping, you can stop those pings on PC1 by pressing \"Control\" and \"C\" on your keyboard at the same time.\n\n5. Configure HSRP on R1 (Gig0/2) and R2 (Gig0/3) using the following guidelines\n\n    - You may select whatever HSRP group number you wish.\n    - Select the last usable IPv4 host address from PC1's subnet as the HSRP virtual IP address.\n    - Router R2 should always be elected to the role of HSRP Active Router as long as interface Gig0/3 on this router is enabled.\n    - Modify HSRP timers such that:\n        - HSRP Hello packets are transmitted every 1-second\n        - The HSRP Hold Time is set to 3-seconds\n\n6. On either router R1 or R2 issue the command, \"**show standby**\" to confirm that R2 is the HSRP Active router.\n\n7. Modify the DHCP pool in R1 and R2 (that is associated with PC1s subnet) so that the default-gateway address they allocate is the same value as the HSRP virtual IP address.\n\n8. Use the \"**ip dhcp -d**\" command on PC1 to have this PC obtain a new IPv4 address.  \n\n    - Confirm that its assigned default-gateway is the HSRP virtual IP address.\n    - Confirm that PC1 can still ping Switch-4 at 180.50.0.214\n\n9. Login to router R1 and implement the following commands in order to debug HSRP:\n\n    <pre><code>\n\n        R1#conf t\n        Enter configuration commands, one per line.  End with CNTL/Z.\n        R1(config)#<b>logging console 6</b>\n        R1(config)#<b>logging buffer debug</b>\n        R1(config)#<b>end</b>\n        R1#\n        R1#<b>debug standby events</b>\n        HSRP Events debugging is on\n        R1#<b>clear log</b>\n\n    </pre></code>\n\n10. Begin an extended ping again from PC1 to 180.50.0.214 with a repeat count of 100.\n\n11. As the ping is happening, go to R2 and disable its Gig0/3 interface. Watch PC1 while you do this.  Did you lose any pings?\n\n12. Move over to router R1 and view the debug output with the command, \"**show log**\".  Can you see when R1 took over as the HSRP Active router?\n\n13. Cancel the debug on R1 by typing, \"**undebug all**\"\n\n14. Move back to router R2 and re-enable interface Gig0/3. Within moments this router should reclaim the role of HSRP Active.",
    "tasks_html": "<p><strong>Task: Gateway Redundancy with HSRP</strong></p>\n<p><strong><em>NOTE:</em></strong> The enable password on all IOS devices is \"<strong>INE</strong>\"</p>\n<ol>\n<li>\n<p>Confirm that PC1 is able to obtain an IPv4 address via DHCP by entering the command, \"<strong>ip dhcp -d</strong>\"</p>\n</li>\n<li>\n<p>Verify that PC1 can ping the IPv4 address of Interface VLAN-2 on Switch-4 (<strong>180.50.0.214</strong>).</p>\n</li>\n<li>\n<p>Identify which router (R1 or R2) is currently serving as the default gateway for PC1.</p>\n</li>\n<li>\n<p>From PC1, initiate an extended ping of 50-pings destined for 180.50.0.214 (interface VLAN-2 on Switch-4)</p>\n<ul>\n<li>While that ping is in progress, shutdown the downstream interface (connecting to Switch-2) of the default-gateway router used by PC1.</li>\n<li>If you shutdown the correct interface on the correct router, the pings should begin to fail on PC1.</li>\n<li>Re-enable the downstream interface on the default-gateway router.</li>\n<li>If PC1 is still attempting to ping, you can stop those pings on PC1 by pressing \"Control\" and \"C\" on your keyboard at the same time.</li>\n</ul>\n</li>\n<li>\n<p>Configure HSRP on R1 (Gig0/2) and R2 (Gig0/3) using the following guidelines</p>\n<ul>\n<li>You may select whatever HSRP group number you wish.</li>\n<li>Select the last usable IPv4 host address from PC1's subnet as the HSRP virtual IP address.</li>\n<li>Router R2 should always be elected to the role of HSRP Active Router as long as interface Gig0/3 on this router is enabled.</li>\n<li>Modify HSRP timers such that:<ul>\n<li>HSRP Hello packets are transmitted every 1-second</li>\n<li>The HSRP Hold Time is set to 3-seconds</li>\n</ul>\n</li>\n</ul>\n</li>\n<li>\n<p>On either router R1 or R2 issue the command, \"<strong>show standby</strong>\" to confirm that R2 is the HSRP Active router.</p>\n</li>\n<li>\n<p>Modify the DHCP pool in R1 and R2 (that is associated with PC1s subnet) so that the default-gateway address they allocate is the same value as the HSRP virtual IP address.</p>\n</li>\n<li>\n<p>Use the \"<strong>ip dhcp -d</strong>\" command on PC1 to have this PC obtain a new IPv4 address.  </p>\n<ul>\n<li>Confirm that its assigned default-gateway is the HSRP virtual IP address.</li>\n<li>Confirm that PC1 can still ping Switch-4 at 180.50.0.214</li>\n</ul>\n</li>\n<li>\n<p>Login to router R1 and implement the following commands in order to debug HSRP:</p>\n<p><pre><code></p>\n<pre class=\"codehilite\"><code>R1#conf t\nEnter configuration commands, one per line.  End with CNTL/Z.\nR1(config)#&lt;b&gt;logging console 6&lt;/b&gt;\nR1(config)#&lt;b&gt;logging buffer debug&lt;/b&gt;\nR1(config)#&lt;b&gt;end&lt;/b&gt;\nR1#\nR1#&lt;b&gt;debug standby events&lt;/b&gt;\nHSRP Events debugging is on\nR1#&lt;b&gt;clear log&lt;/b&gt;</code></pre>\n\n\n<p></pre></code></p>\n</li>\n<li>\n<p>Begin an extended ping again from PC1 to 180.50.0.214 with a repeat count of 100.</p>\n</li>\n<li>\n<p>As the ping is happening, go to R2 and disable its Gig0/3 interface. Watch PC1 while you do this.  Did you lose any pings?</p>\n</li>\n<li>\n<p>Move over to router R1 and view the debug output with the command, \"<strong>show log</strong>\".  Can you see when R1 took over as the HSRP Active router?</p>\n</li>\n<li>\n<p>Cancel the debug on R1 by typing, \"<strong>undebug all</strong>\"</p>\n</li>\n<li>\n<p>Move back to router R2 and re-enable interface Gig0/3. Within moments this router should reclaim the role of HSRP Active.</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
}