{
    "id": "8e092f57-7ddf-4fc7-87cb-316100d8777b",
    "name": "HSRP & Network Address Translation",
    "slug": "hsrp-network-address-translation",
    "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:10:27.767790Z",
    "modified": "2023-10-03T18:58:50.760184Z",
    "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": "**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-4-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.\n\n**Lab Notes:**\n\n1. On all IOS devices (routers and switches) load the preconfiguration file from flash: memory titled, \u201c**Lab-4-Begin**\u201d.\n\n2. Once you perform the step above the following will be preconfigured for you:\n    - All IPv4 addressing on devices other than PCs as shown in the IPv4 addressing chart\n    - Telnet will be preconfigured on R1 and R2\n    - VLANs and 802.1q VLAN Trunks\n    - Router interfaces will be administratively up.\n    - Devices will have pre-configured Enable passwords of \u201ccisco\u201d\n\nIf you get stuck at any point during this lab and wish to view the Lab Solution, load the pre-configuration file (on any IOS device) named, \u201c***Lab-4-Solution***\u201d from flash memory.\n\n![description](https://assets.ine.com/content/labs/networking-labs/Day-4-Lab/diagram.png)\n\n***NOTE:*** Please notice there has been an IPv4 addressing change for links F, G, M and N in this lab. They are now all in the same network.\n\n***Hot Standby Router Protocol (HSRP) Tasks***\n\n1. In all routers and switches, load from flash memory the saved configuration file titled, \u201cLab-4-Begin\u201d.\n\n2. onfigure PC3 with the static IPv4 address and mask of 10.10.40.4/28 and a default gateway of 10.10.40.1 (R1).\n\n3. From PC3 ensure you can ping Switch-1 at 10.10.10.4\n\n4. Begin your pings again from PC3 to Switch-1 but this time using the \u201c-t\u201d switch so that the pings will continue until you interrupt them with the \u201cControl-C\u201d command\n    Ping 10.10.10.4 -t\n\n5. While PC3 is pinging Switch-1, what do you think would happen if, in router R1, you shutdown interface Gig0/1?  Try it?\n    - What affect did this action have on your pings from PC3 to Switch-1?\n    - Re-enable Gig0/1 in router R1.\n    - Stop your pings on PC3\n\n6. Configure HSRP on routers R1 and R2 using the following parameters:\n    - HSRP should be activated on the following interfaces:\n        - R1: Gig0/1\n        - R2: Gig0/2\n    - The HSRP Group number should be \u201c8\u201d\n    - The HSRP virtual IP address should be the last available host address in the prefix allocated for these two interfaces.\n\n7. Using the IOS \u201cshow standby\u201d command, identify which router (R1 or R2) became the HSRP Active router.\n\n8. Login to the router that is currently operating as HSRP Standby and force this router to become the HSRP Active router.  You may not disable any links or reload any routers to accomplish this task.\n\n9. Configure PC3 with the static IPv4 address and mask of 10.10.40.4/28 and a default gateway of the HSRP Virtual IP address you configured in the previous step.\n\n10. Start a continuous ping again from PC3 to Switch-1 (10.10.10.4).\n\n11. Login to your HSRP Active Router that was configured in Step-8.\n    - Shutdown the interface on your HSRP Active router that connects downstream to Switch-2 while simultaneously monitoring the continuous pings from PC3.\n    - Were any of your pings lost when you shutdown that router\u2019s interface?\n    - If any of them WERE lost, did the pings resume again at any point? How long did it take?\n\n12. With the continuous pings still going from PC3 to Switch-1, re-enable the router\u2019s interface that you shutdown in the previous step.\n\n13. Once you re-enabled the router\u2019s interface were your pings interrupted at all?",
    "description_html": "<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-4-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>\n<p><strong>Lab Notes:</strong></p>\n<ol>\n<li>\n<p>On all IOS devices (routers and switches) load the preconfiguration file from flash: memory titled, \u201c<strong>Lab-4-Begin</strong>\u201d.</p>\n</li>\n<li>\n<p>Once you perform the step above the following will be preconfigured for you:</p>\n<ul>\n<li>All IPv4 addressing on devices other than PCs as shown in the IPv4 addressing chart</li>\n<li>Telnet will be preconfigured on R1 and R2</li>\n<li>VLANs and 802.1q VLAN Trunks</li>\n<li>Router interfaces will be administratively up.</li>\n<li>Devices will have pre-configured Enable passwords of \u201ccisco\u201d</li>\n</ul>\n</li>\n</ol>\n<p>If you get stuck at any point during this lab and wish to view the Lab Solution, load the pre-configuration file (on any IOS device) named, \u201c<strong><em>Lab-4-Solution</em></strong>\u201d from flash memory.</p>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Day-4-Lab/diagram.png\" /></p>\n<p><strong><em>NOTE:</em></strong> Please notice there has been an IPv4 addressing change for links F, G, M and N in this lab. They are now all in the same network.</p>\n<p><strong><em>Hot Standby Router Protocol (HSRP) Tasks</em></strong></p>\n<ol>\n<li>\n<p>In all routers and switches, load from flash memory the saved configuration file titled, \u201cLab-4-Begin\u201d.</p>\n</li>\n<li>\n<p>onfigure PC3 with the static IPv4 address and mask of 10.10.40.4/28 and a default gateway of 10.10.40.1 (R1).</p>\n</li>\n<li>\n<p>From PC3 ensure you can ping Switch-1 at 10.10.10.4</p>\n</li>\n<li>\n<p>Begin your pings again from PC3 to Switch-1 but this time using the \u201c-t\u201d switch so that the pings will continue until you interrupt them with the \u201cControl-C\u201d command\n    Ping 10.10.10.4 -t</p>\n</li>\n<li>\n<p>While PC3 is pinging Switch-1, what do you think would happen if, in router R1, you shutdown interface Gig0/1?  Try it?</p>\n<ul>\n<li>What affect did this action have on your pings from PC3 to Switch-1?</li>\n<li>Re-enable Gig0/1 in router R1.</li>\n<li>Stop your pings on PC3</li>\n</ul>\n</li>\n<li>\n<p>Configure HSRP on routers R1 and R2 using the following parameters:</p>\n<ul>\n<li>HSRP should be activated on the following interfaces:<ul>\n<li>R1: Gig0/1</li>\n<li>R2: Gig0/2</li>\n</ul>\n</li>\n<li>The HSRP Group number should be \u201c8\u201d</li>\n<li>The HSRP virtual IP address should be the last available host address in the prefix allocated for these two interfaces.</li>\n</ul>\n</li>\n<li>\n<p>Using the IOS \u201cshow standby\u201d command, identify which router (R1 or R2) became the HSRP Active router.</p>\n</li>\n<li>\n<p>Login to the router that is currently operating as HSRP Standby and force this router to become the HSRP Active router.  You may not disable any links or reload any routers to accomplish this task.</p>\n</li>\n<li>\n<p>Configure PC3 with the static IPv4 address and mask of 10.10.40.4/28 and a default gateway of the HSRP Virtual IP address you configured in the previous step.</p>\n</li>\n<li>\n<p>Start a continuous ping again from PC3 to Switch-1 (10.10.10.4).</p>\n</li>\n<li>\n<p>Login to your HSRP Active Router that was configured in Step-8.</p>\n<ul>\n<li>Shutdown the interface on your HSRP Active router that connects downstream to Switch-2 while simultaneously monitoring the continuous pings from PC3.</li>\n<li>Were any of your pings lost when you shutdown that router\u2019s interface?</li>\n<li>If any of them WERE lost, did the pings resume again at any point? How long did it take?</li>\n</ul>\n</li>\n<li>\n<p>With the continuous pings still going from PC3 to Switch-1, re-enable the router\u2019s interface that you shutdown in the previous step.</p>\n</li>\n<li>\n<p>Once you re-enabled the router\u2019s interface were your pings interrupted at all?</p>\n</li>\n</ol>",
    "tasks": "***Network Address Translation Tasks***\n\n1. From router R3, ensure you can ping the IP address configured on Gig0/2 of router R2 as well as Telnet to that router.\n\n2. Configure and apply an access-list (named or numbered) on R5 that denies all IP packets sourced from Subnet-S and Subnet-R.  This should prevent router R3 from sending any traffic through R5.\n\n3. Configure NAT on router R4 using the following guidelines:\n    - NAT should only translate packets received on the Gig0/1 interface and that are routed to the Gig0/0 egress interface.\n    - NAT should only translate packets containing a source address of Subnet-R or Subnet-S.\n    - NAT should be configured with a dynamic pool of addresses in the same range as router R4\u2019s Loopback interface (80.80.4.x/24)\n\n4. Once you have completed step-3 above, R3 should once again be able to ping and Telnet to R2.\n    - In your topology, right-click on Link-G and select \u201cStart Capture\u201d. In a few moments the Wireshark application should start.\n    - Reduce the size of the Wireshark application window so you can view it and R3\u2019s console window at the same time.\n    - Ping and/or Telnet from R3 to R2 and take note of the source address of those pings as displayed in Wireshark.  They should now be sourced with an 80.80.4.x address.\n\n5. Ping from R3 to R2 again.\n    - In router R4 familiar yourself with the output of the commands \u201c***show ip nat translation***\u201d and \u201c***show ip nat translation verbose***\u201d.\n    - Notice the value of \u201ctimeout\u201d for the ICMP translation. After your last ping, how long with the ICMP translation exist in R4 until it is deleted?\n\n6. Telnet from R3 to R2 and view the output of \u201cshow ip nat translation verbose\u201d in R4.\n    - What do you notice that is different about the \u201ctimeout\u201d value for the TCP connection (Telnet) as compared to the ICMP sessions?",
    "tasks_html": "<p><strong><em>Network Address Translation Tasks</em></strong></p>\n<ol>\n<li>\n<p>From router R3, ensure you can ping the IP address configured on Gig0/2 of router R2 as well as Telnet to that router.</p>\n</li>\n<li>\n<p>Configure and apply an access-list (named or numbered) on R5 that denies all IP packets sourced from Subnet-S and Subnet-R.  This should prevent router R3 from sending any traffic through R5.</p>\n</li>\n<li>\n<p>Configure NAT on router R4 using the following guidelines:</p>\n<ul>\n<li>NAT should only translate packets received on the Gig0/1 interface and that are routed to the Gig0/0 egress interface.</li>\n<li>NAT should only translate packets containing a source address of Subnet-R or Subnet-S.</li>\n<li>NAT should be configured with a dynamic pool of addresses in the same range as router R4\u2019s Loopback interface (80.80.4.x/24)</li>\n</ul>\n</li>\n<li>\n<p>Once you have completed step-3 above, R3 should once again be able to ping and Telnet to R2.</p>\n<ul>\n<li>In your topology, right-click on Link-G and select \u201cStart Capture\u201d. In a few moments the Wireshark application should start.</li>\n<li>Reduce the size of the Wireshark application window so you can view it and R3\u2019s console window at the same time.</li>\n<li>Ping and/or Telnet from R3 to R2 and take note of the source address of those pings as displayed in Wireshark.  They should now be sourced with an 80.80.4.x address.</li>\n</ul>\n</li>\n<li>\n<p>Ping from R3 to R2 again.</p>\n<ul>\n<li>In router R4 familiar yourself with the output of the commands \u201c<strong><em>show ip nat translation</em></strong>\u201d and \u201c<strong><em>show ip nat translation verbose</em></strong>\u201d.</li>\n<li>Notice the value of \u201ctimeout\u201d for the ICMP translation. After your last ping, how long with the ICMP translation exist in R4 until it is deleted?</li>\n</ul>\n</li>\n<li>\n<p>Telnet from R3 to R2 and view the output of \u201cshow ip nat translation verbose\u201d in R4.</p>\n<ul>\n<li>What do you notice that is different about the \u201ctimeout\u201d value for the TCP connection (Telnet) as compared to the ICMP sessions?</li>\n</ul>\n</li>\n</ol>",
    "published_date": "2020-04-14T18:00:00Z",
    "solutions": "***Solutions***\n\nLab solutions are stored as viewable (and loadable) named configuration files stored in Flash memory on each device. To view the Lab Solution, login to any IOS device in your topology (Routers or Switches) and issue the following command:\n\n<pre><code>\n\n    Router>enable\n    Router#<b>more flash:Lab-4-Solution</b>\n    !\n    version 15.9\n    service timestamps debug datetime msec\n    service timestamps log datetime msec\n    no service password-encryption\n    !\n    hostname R1\n    !\n    boot-start-marker\n    [SNIP]\n\n</pre></code>\n\nTo **Load** the solution configuration onto your device follow the procedure below.  Please NOTE that ***this procedure will completely erase your current configuration file and overwrite it with the solution configuration file***:\n\n<pre><code>\n\n    Router-1#<b>configure replace flash:Lab-4-Solution</b>\n    This will apply all necessary additions and deletions\n    to <b>replace the current running configuration with the\n    contents of the specified configuration file</b>, 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 29 19:10:01.921: Rollback:Acquired Configuration lock.\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\n    *Jul 29 19:10:04.061: %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\n    *Jul 29 19:10:05.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up\n    Total number of passes: 1\n    Rollback Done\n\n    R1#\n\n</pre></code>",
    "solutions_html": "<p><strong><em>Solutions</em></strong></p>\n<p>Lab solutions are stored as viewable (and loadable) named configuration files stored in Flash memory on each device. To view the Lab Solution, login to any IOS device in your topology (Routers or Switches) and issue the following command:</p>\n<pre><code>\n\n    Router>enable\n    Router#<b>more flash:Lab-4-Solution</b>\n    !\n    version 15.9\n    service timestamps debug datetime msec\n    service timestamps log datetime msec\n    no service password-encryption\n    !\n    hostname R1\n    !\n    boot-start-marker\n    [SNIP]\n\n</pre>\n\n<p></code></p>\n<p>To <strong>Load** the solution configuration onto your device follow the procedure below.  Please NOTE that **<em>this procedure will completely erase your current configuration file and overwrite it with the solution configuration file</em></strong>:</p>\n<pre><code>\n\n    Router-1#<b>configure replace flash:Lab-4-Solution</b>\n    This will apply all necessary additions and deletions\n    to <b>replace the current running configuration with the\n    contents of the specified configuration file</b>, 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 29 19:10:01.921: Rollback:Acquired Configuration lock.\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\n    *Jul 29 19:10:04.061: %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\n    *Jul 29 19:10:05.067: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed state to up\n    Total number of passes: 1\n    Rollback Done\n\n    R1#\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
}