{
    "id": "bdd5339c-8324-44cc-8ba4-e65df8f6bbb2",
    "name": "CCNA Bootcamp - Final Lab",
    "slug": "ccna-bootcamp-final-lab",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "8aad3d56-4db5-4e20-a300-aba9b925bfd4",
            "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-15T20:00:01.218747Z",
    "modified": "2023-10-03T18:58:59.503905Z",
    "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/Final-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\n![description](https://assets.ine.com/content/labs/networking-labs/Final-Lab/diagram.png)\n\nThis lab will test your knowledge and skills at implementing eleven of the most important features and protocols that were covered within INE's CCNA Learning Path.",
    "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/Final-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><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Final-Lab/diagram.png\" /></p>\n<p>This lab will test your knowledge and skills at implementing eleven of the most important features and protocols that were covered within INE's CCNA Learning Path.</p>",
    "tasks": "***Task-1: Initial Configuration & CDP***\n\n1. Load the configuration file stored in Flash: memory titled, \u201cdefault-config\u201d\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\n    - Devices should repeat your most recent console input when interrupted by a SYSLOG message\n\n    - All interfaces leading to other devices in the diagram should be administratively up.\n\n    - All devices should be configured with a password of \u201ccisco\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\n    - Router R1 should be configured to accept incoming Telnet connections.  These connections should be authenticated using the password of \u201ccisco\u201d.\n\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 \u201ccisco\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    - Save your running-configuration file to your startup-configuration file on each device.\n\n    - Confirm that each IOS device can see its directly connected neighbors via CDP (Cisco Discovery Protocol)\n\n---\n\n***Task-2: Basic Switching***\n\n1. Configure VLANs 4 and 5 on switches Sw2, Sw3 and Sw4.\n    - Ensure VLAN-4 displays with a name of \u201cPayroll\u201d in the output of \u201cshow vlans\u201d and VLAN-5 displays with a name of \u201cEngineering\u201d on all three switches.\n\n\n2. Interface Configuration\n    - Configure interfaces on switches that connect directly to routers or PCs in such a way that they belong to only a single VLAN and will not participate in VLAN Trunking.\n\n    - Ensure that the switchports leading to PC3 (Link-M) and R2 (Link-G) are placed into VLAN-4\n\n    - Ensure that the switchports leading to R5 (Link-N) and R1 (Link-F) are placed into VLAN-5\n\n3. Configure the links identified in the topology diagram as 802.1q VLAN trunks using the following parameters:\n\n    - 802.1q VLAN Trunks should only allow VLANs 1, 4 and 5\n\n    - All interswitch 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\n    - Configure VLAN-4 to be the Native VLAN on Link-J\n\n---\n\n***Task-3: IP Addressing and Subnetting***\n\n1. Starting with the initial network of 50.50.50.0/24, utilize VLSM in order to complete the following chart:\n\n    |Link ID| Qty of Hosts| Subnet Mask| Network/Prefix|\n    |---|---|---|---|\n    |A/B/D| 6|\n    |C| 2|\n    |E| 30|\n    |F/N| 40|\n    |G/M| 12|\n\n\n2. Starting with the initial network of 70.70.70.0/24, utilize VLSM in order to complete the following chart:\n\n    |Link ID| Qty of Hosts| Subnet Mask| Network/Prefix|\n    |---|---|---|---|\n    |S| 100|\n    |R| 55|\n    |P| 22|\n\n3. Apply IPv4 addressing to router interfaces from what you derived in the previous step.  Use these guidelines:\n    - Router interfaces should be configured with the first available host addresses in their connected networks.\n    - When you\u2019re done with this step, routers should be able to ping other, directly-connected routers.\n\n\n4. From router R2, Telnet into R1 using the credentials provided in the first task.\n\n5. From router R1, SSH into R2 using the credentials provided in the first task.\n\n---\n\n***Task-4: HSRP***\n\n1. Configure HSRP on router R1 (Gig0/2) and R2 (Gig0/3).\n    - Utilize the last available host address from Subnet A/B/D as your HSRP Virtual IP address\n\n    - Configure Router R1 such that it is always the HSRP Active router, even it is crashes and then comes back online again.\n\n---\n\n***Task-5: Cisco IOS DHCP Server***\n\n1. Configure router R2 as a DHCP server such that it can dynamically allocate IPv4 addresses to:\n\n    - PC1 (from the subnet assigned to Link-A/B/C)\n        - The default-gateway address assigned to PC1 should be the HSRP virtual-IP address you determined in the steps above.\n\n    - PC3 (from the subnet assigned to Link-M)\n\n    - PC2 (from the subnet assigned to Link-E)\n\n    - Every PC should obtain a DHCP address with a Lease timer of 2-days, 12-hours and 30-minutes.\n\n2. Configure router R3 as a DHCP server such that it can dynamically allocate IPv4 addresses to PC4 (from the subnet assigned to Link-S)\nThe default-gateway address assigned to PC4 should be the IPv4 address you configured on R3\u2019s Gig0/0 interface.\n\n3. Confirm DHCP functionality by initializing DHCP on VPCS nodes in the topology using the following command:\n\n    <pre><code>\n    PC2> ip dhcp -d\n    </pre></code>\n\n---\n\n***Task-6: Implementing Spanning-Tree***\n\n1. Configure whatever command(s) is needed so switches Sw2, Sw3, and Sw4 are running Rapid Spanning-Tree.\n\n2. Configure Sw2 as the Root Bridge for VLAN-1 (if it isn\u2019t by default).\n\n3. Configure Sw3 as the Root Bridge for VLAN-4 (if it isn\u2019t by default).\n\n4. Configure Sw4 as the Root Bridge for VLAN-5 (if it isn\u2019t by default).\n\n5. Configure ports on switches that connect directly to routers or PCs with a Spanning-Tree feature so that RSTP recognizes them as Edge ports.\n\n6. Bundle both links connecting Switch-3 to Switch-4 into an Etherchannel.\n\n    - An IEEE dynamic bundling protocol should be used with Switch-3 initiating the exchange of negotiation frames.\n\n\n7. Modify RSTP using whatever commands you wish so that frames/packets between PC3 and R2 take the following path:\n\n    ![description](https://assets.ine.com/content/labs/networking-labs/Final-Lab/stp-path.png)\n\n---\n\n***Task-7: Static IPv4 Routing***\n\n1. Configure IPv4 static routes on router R3, R4 and R5 such that:\n    - R3 and R4 should be able to ping the IPv4 address assigned to the Gig0/2 interface of R5\n\n    - R5 should be able to ping the DHCP address allocated to PC4\n\n---\n\n***Task-8: OSPF Dynamic Routing***\n\n1. Configure OSPF on routers R1, R2 and R5 such that:\n\n    - Links-B, C, D and E are placed into Area-0\n    - Links-F, G, and N are placed into Area-1\n\n\n2. Ensure routers R1, R2 and R5 are using OSPF Router-IDs in the form of 0.0.0.x where \u201cx\u201d denotes the router number. This should be verified using the command, \u201cshow ip ospf\u201d on each router.\n\n3. Configure router R5 such that it injects a default route into the OSPF domain.\n\n4. When this task is completed all PCs (including PC4) should be able to ping each other.\n\n---\n\n***Task-9: Network Address Translation***\n\n1. Configure a Loopback interface on router R2 with the IPv4 address of 22.22.22.1/28\n\n2. Advertise the network you created above into your OSPF domain and ensure that PC4 can ping it.\n\n3. Configure a NAT Pool on router R2 that utilizes all remaining IPv4 addresses from the 22.22.22.0/28 network and ensure that whenever PC2 pings PC4, that PC2\u2019s source IPv4 address is translated to an address in your NAT pool.\n\n4. Confirm that PC2 can still ping PC4 and, when a Wireshark sniffer trace is performed on Link-N you can see that PC2\u2019s source address has been changed by NAT.\n\n---\n\n***Task-10: IPv6 Addressing and Routing***\n\n1. Subnet the IPv6 prefix of 2001:aaaa:bbbb:cc00::/56 into IPv6 subnets, each having a /64 mask.\n    - The 5th IPv6 subnet should be allocated to Link-S\n\n    - The 12th IPv6 subnet should be allocated to Link-R\n\n    - The 40th IPv6 subnet should be allocated to Link-P\n\n    - Router interfaces on R3 should be configured using static interface IDs ending with ::3\n\n    - Router interfaces on R4 should be configured with the relevant prefixes but the interface-IDs should be dynamically derived using the EUI-64 method.\n\n    - R5\u2019s interface Gig0/0 should obtain its IPv6 interface address using SLAAC.\n\n2. Configure an \u201cinterface Loopback1\u201d in router R5 and give it the IPv6 address of 2001:5555:5555::5/64\n\n3. Configure IPv6 static routes on routers R3, R4 and R5 such that:\n    - R3 and R4 should be able to ping the IPv6 address assigned to the Loopback1 interface of R5\n\n    - R5 should be able to ping the IPv6 address configured on interface Gig0/0 of R3\n\n---\n\n***Task-11: Access Control Lists***\n\n1. Confirm that both R3 and R4 can:\n    - Ping PC1\n    - Telnet to R1\n    - SSH to R2\n\n2. Configure and apply an Access Control List (on whichever device you feel is most appropriate such that:\n    - PC1 may only be pinged from addresses sourced from Links-R and P. Pings from any other link in this topology should be denied.\n\n    - R3 (using any of its source IPv4 addresses) should not be allowed to Telnet to R1 but SHOULD be permitted to SSH to R2\n\n    - R4 (using any of its source IPv4 addresses) should not be allowed to SSH to R2 but SHOULD be permitted to Telnet to R1.\n\n    - Any other traffic not explicitly denied should be permitted.\n\n3. Verify that your ACL configuration is working per the stated objectives by doing the following:\n\n    |Traffic Source| Destination| Protocol| Expected Outcome|\n    |---|---|---|---|\n    |R3|PC1|Ping|Allowed|\n    |R4|PC1|Ping|Allowed|\n    |R1|PC1|Ping|Denied|\n    |R2|PC1|Ping|Denied|\n    |R3|R1|Telnet|Denied|\n    |R2|R2|SSH|Allowed|\n    |R4|R1|Telnet|Allowed|\n    |R4|R3|SSH|Denied|",
    "tasks_html": "<p><strong><em>Task-1: Initial Configuration &amp; CDP</em></strong></p>\n<ol>\n<li>\n<p>Load the configuration file stored in Flash: memory titled, \u201cdefault-config\u201d</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>\n<p>Devices should not attempt a DNS resolution when a command is entered incorrectly</p>\n</li>\n<li>\n<p>Devices should repeat your most recent console input when interrupted by a SYSLOG message</p>\n</li>\n<li>\n<p>All interfaces leading to other devices in the diagram should be administratively up.</p>\n</li>\n<li>\n<p>All devices should be configured with a password of \u201ccisco\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.</p>\n</li>\n<li>\n<p>Router R1 should be configured to accept incoming Telnet connections.  These connections should be authenticated using the password of \u201ccisco\u201d.</p>\n</li>\n<li>\n<p>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 \u201ccisco\u201d.</p>\n<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<li>\n<p>Save your running-configuration file to your startup-configuration file on each device.</p>\n</li>\n<li>\n<p>Confirm that each IOS device can see its directly connected neighbors via CDP (Cisco Discovery Protocol)</p>\n</li>\n</ul>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-2: Basic Switching</em></strong></p>\n<ol>\n<li>\n<p>Configure VLANs 4 and 5 on switches Sw2, Sw3 and Sw4.</p>\n<ul>\n<li>Ensure VLAN-4 displays with a name of \u201cPayroll\u201d in the output of \u201cshow vlans\u201d and VLAN-5 displays with a name of \u201cEngineering\u201d on all three switches.</li>\n</ul>\n</li>\n<li>\n<p>Interface Configuration</p>\n<ul>\n<li>\n<p>Configure interfaces on switches that connect directly to routers or PCs in such a way that they belong to only a single VLAN and will not participate in VLAN Trunking.</p>\n</li>\n<li>\n<p>Ensure that the switchports leading to PC3 (Link-M) and R2 (Link-G) are placed into VLAN-4</p>\n</li>\n<li>\n<p>Ensure that the switchports leading to R5 (Link-N) and R1 (Link-F) are placed into VLAN-5</p>\n</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>\n<p>802.1q VLAN Trunks should only allow VLANs 1, 4 and 5</p>\n</li>\n<li>\n<p>All interswitch links (H, J, K and L) should rely on DTP for dynamic trunking and trunk maintenance.</p>\n<ul>\n<li>Lower-numbered switches should initiate DTP exchanges</li>\n<li>Higher-numbered switches should passively wait for ingress DTP messages.</li>\n</ul>\n</li>\n<li>\n<p>Configure VLAN-4 to be the Native VLAN on Link-J</p>\n</li>\n</ul>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-3: IP Addressing and Subnetting</em></strong></p>\n<ol>\n<li>\n<p>Starting with the initial network of 50.50.50.0/24, utilize 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>A/B/D</td>\n<td>6</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<tr>\n<td>E</td>\n<td>30</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>F/N</td>\n<td>40</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>G/M</td>\n<td>12</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Starting with the initial network of 70.70.70.0/24, utilize 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>S</td>\n<td>100</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>R</td>\n<td>55</td>\n<td></td>\n<td></td>\n</tr>\n<tr>\n<td>P</td>\n<td>22</td>\n<td></td>\n<td></td>\n</tr>\n</tbody>\n</table>\n</li>\n<li>\n<p>Apply IPv4 addressing to router interfaces from what you derived in the previous step.  Use these guidelines:</p>\n<ul>\n<li>Router interfaces should be configured with the first available host addresses in their connected networks.</li>\n<li>When you\u2019re done with this step, routers should be able to ping other, directly-connected routers.</li>\n</ul>\n</li>\n<li>\n<p>From router R2, Telnet into R1 using the credentials provided in the first task.</p>\n</li>\n<li>\n<p>From router R1, SSH into R2 using the credentials provided in the first task.</p>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-4: HSRP</em></strong></p>\n<ol>\n<li>\n<p>Configure HSRP on router R1 (Gig0/2) and R2 (Gig0/3).</p>\n<ul>\n<li>\n<p>Utilize the last available host address from Subnet A/B/D as your HSRP Virtual IP address</p>\n</li>\n<li>\n<p>Configure Router R1 such that it is always the HSRP Active router, even it is crashes and then comes back online again.</p>\n</li>\n</ul>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-5: Cisco IOS DHCP Server</em></strong></p>\n<ol>\n<li>\n<p>Configure router R2 as a DHCP server such that it can dynamically allocate IPv4 addresses to:</p>\n<ul>\n<li>\n<p>PC1 (from the subnet assigned to Link-A/B/C)</p>\n<ul>\n<li>The default-gateway address assigned to PC1 should be the HSRP virtual-IP address you determined in the steps above.</li>\n</ul>\n</li>\n<li>\n<p>PC3 (from the subnet assigned to Link-M)</p>\n</li>\n<li>\n<p>PC2 (from the subnet assigned to Link-E)</p>\n</li>\n<li>\n<p>Every PC should obtain a DHCP address with a Lease timer of 2-days, 12-hours and 30-minutes.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Configure router R3 as a DHCP server such that it can dynamically allocate IPv4 addresses to PC4 (from the subnet assigned to Link-S)\nThe default-gateway address assigned to PC4 should be the IPv4 address you configured on R3\u2019s Gig0/0 interface.</p>\n</li>\n<li>\n<p>Confirm DHCP functionality by initializing DHCP on VPCS nodes in the topology using the following command:</p>\n<p><pre><code>\nPC2&gt; ip dhcp -d\n</pre></code></p>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-6: Implementing Spanning-Tree</em></strong></p>\n<ol>\n<li>\n<p>Configure whatever command(s) is needed so switches Sw2, Sw3, and Sw4 are running Rapid Spanning-Tree.</p>\n</li>\n<li>\n<p>Configure Sw2 as the Root Bridge for VLAN-1 (if it isn\u2019t by default).</p>\n</li>\n<li>\n<p>Configure Sw3 as the Root Bridge for VLAN-4 (if it isn\u2019t by default).</p>\n</li>\n<li>\n<p>Configure Sw4 as the Root Bridge for VLAN-5 (if it isn\u2019t by default).</p>\n</li>\n<li>\n<p>Configure ports on switches that connect directly to routers or PCs with a Spanning-Tree feature so that RSTP recognizes them as Edge ports.</p>\n</li>\n<li>\n<p>Bundle both links connecting Switch-3 to Switch-4 into an Etherchannel.</p>\n<ul>\n<li>An IEEE dynamic bundling protocol should be used with Switch-3 initiating the exchange of negotiation frames.</li>\n</ul>\n</li>\n<li>\n<p>Modify RSTP using whatever commands you wish so that frames/packets between PC3 and R2 take the following path:</p>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Final-Lab/stp-path.png\" /></p>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-7: Static IPv4 Routing</em></strong></p>\n<ol>\n<li>\n<p>Configure IPv4 static routes on router R3, R4 and R5 such that:</p>\n<ul>\n<li>\n<p>R3 and R4 should be able to ping the IPv4 address assigned to the Gig0/2 interface of R5</p>\n</li>\n<li>\n<p>R5 should be able to ping the DHCP address allocated to PC4</p>\n</li>\n</ul>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-8: OSPF Dynamic Routing</em></strong></p>\n<ol>\n<li>\n<p>Configure OSPF on routers R1, R2 and R5 such that:</p>\n<ul>\n<li>Links-B, C, D and E are placed into Area-0</li>\n<li>Links-F, G, and N are placed into Area-1</li>\n</ul>\n</li>\n<li>\n<p>Ensure routers R1, R2 and R5 are using OSPF Router-IDs in the form of 0.0.0.x where \u201cx\u201d denotes the router number. This should be verified using the command, \u201cshow ip ospf\u201d on each router.</p>\n</li>\n<li>\n<p>Configure router R5 such that it injects a default route into the OSPF domain.</p>\n</li>\n<li>\n<p>When this task is completed all PCs (including PC4) should be able to ping each other.</p>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-9: Network Address Translation</em></strong></p>\n<ol>\n<li>\n<p>Configure a Loopback interface on router R2 with the IPv4 address of 22.22.22.1/28</p>\n</li>\n<li>\n<p>Advertise the network you created above into your OSPF domain and ensure that PC4 can ping it.</p>\n</li>\n<li>\n<p>Configure a NAT Pool on router R2 that utilizes all remaining IPv4 addresses from the 22.22.22.0/28 network and ensure that whenever PC2 pings PC4, that PC2\u2019s source IPv4 address is translated to an address in your NAT pool.</p>\n</li>\n<li>\n<p>Confirm that PC2 can still ping PC4 and, when a Wireshark sniffer trace is performed on Link-N you can see that PC2\u2019s source address has been changed by NAT.</p>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-10: IPv6 Addressing and Routing</em></strong></p>\n<ol>\n<li>\n<p>Subnet the IPv6 prefix of 2001:aaaa:bbbb:cc00::/56 into IPv6 subnets, each having a /64 mask.</p>\n<ul>\n<li>\n<p>The 5th IPv6 subnet should be allocated to Link-S</p>\n</li>\n<li>\n<p>The 12th IPv6 subnet should be allocated to Link-R</p>\n</li>\n<li>\n<p>The 40th IPv6 subnet should be allocated to Link-P</p>\n</li>\n<li>\n<p>Router interfaces on R3 should be configured using static interface IDs ending with ::3</p>\n</li>\n<li>\n<p>Router interfaces on R4 should be configured with the relevant prefixes but the interface-IDs should be dynamically derived using the EUI-64 method.</p>\n</li>\n<li>\n<p>R5\u2019s interface Gig0/0 should obtain its IPv6 interface address using SLAAC.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Configure an \u201cinterface Loopback1\u201d in router R5 and give it the IPv6 address of 2001:5555:5555::5/64</p>\n</li>\n<li>\n<p>Configure IPv6 static routes on routers R3, R4 and R5 such that:</p>\n<ul>\n<li>\n<p>R3 and R4 should be able to ping the IPv6 address assigned to the Loopback1 interface of R5</p>\n</li>\n<li>\n<p>R5 should be able to ping the IPv6 address configured on interface Gig0/0 of R3</p>\n</li>\n</ul>\n</li>\n</ol>\n<hr />\n<p><strong><em>Task-11: Access Control Lists</em></strong></p>\n<ol>\n<li>\n<p>Confirm that both R3 and R4 can:</p>\n<ul>\n<li>Ping PC1</li>\n<li>Telnet to R1</li>\n<li>SSH to R2</li>\n</ul>\n</li>\n<li>\n<p>Configure and apply an Access Control List (on whichever device you feel is most appropriate such that:</p>\n<ul>\n<li>\n<p>PC1 may only be pinged from addresses sourced from Links-R and P. Pings from any other link in this topology should be denied.</p>\n</li>\n<li>\n<p>R3 (using any of its source IPv4 addresses) should not be allowed to Telnet to R1 but SHOULD be permitted to SSH to R2</p>\n</li>\n<li>\n<p>R4 (using any of its source IPv4 addresses) should not be allowed to SSH to R2 but SHOULD be permitted to Telnet to R1.</p>\n</li>\n<li>\n<p>Any other traffic not explicitly denied should be permitted.</p>\n</li>\n</ul>\n</li>\n<li>\n<p>Verify that your ACL configuration is working per the stated objectives by doing the following:</p>\n<table>\n<thead>\n<tr>\n<th>Traffic Source</th>\n<th>Destination</th>\n<th>Protocol</th>\n<th>Expected Outcome</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td>R3</td>\n<td>PC1</td>\n<td>Ping</td>\n<td>Allowed</td>\n</tr>\n<tr>\n<td>R4</td>\n<td>PC1</td>\n<td>Ping</td>\n<td>Allowed</td>\n</tr>\n<tr>\n<td>R1</td>\n<td>PC1</td>\n<td>Ping</td>\n<td>Denied</td>\n</tr>\n<tr>\n<td>R2</td>\n<td>PC1</td>\n<td>Ping</td>\n<td>Denied</td>\n</tr>\n<tr>\n<td>R3</td>\n<td>R1</td>\n<td>Telnet</td>\n<td>Denied</td>\n</tr>\n<tr>\n<td>R2</td>\n<td>R2</td>\n<td>SSH</td>\n<td>Allowed</td>\n</tr>\n<tr>\n<td>R4</td>\n<td>R1</td>\n<td>Telnet</td>\n<td>Allowed</td>\n</tr>\n<tr>\n<td>R4</td>\n<td>R3</td>\n<td>SSH</td>\n<td>Denied</td>\n</tr>\n</tbody>\n</table>\n</li>\n</ol>",
    "published_date": "2020-04-14T18:00:00Z",
    "solutions": "***Solutions***\n\n***Task-1 Solutions***\n\nConfiguration to apply to all ***routers***:\n\n<pre><code>\n\n    enable\n    config t\n    no ip domain-lookup\n    line con 0\n     logging synch\n     exit\n    enable password cisco\n    !\n    interface gig0/0\n      no shut\n      exit\n    !\n    interface gig0/1\n      no shut\n      exit\n    !\n    interface gig0/2\n      no shut\n      exit\n    !\n    interface gig0/3\n      no shut\n      exit\n    !\n    hostname [device hostname]\n\n</pre></code>\n\n\nOn all ***switches***:\n\n\n<pre><code>\n\n    enable\n    config t\n    no ip domain-lookup\n    line con 0\n     logging synch\n     exit\n    enable password cisco\n    !\n    hostname [device hostname]\n</pre></code>\n\nR1-specific (for ***Telnet***)\n\n\n<pre><code>\n\n    line vty 0 4\n    password cisco\n    login\n    transport input telnet\n\n</pre></code>\n\nR2-specific (for ***SSH***)\n\n<pre><code>\n\n    hostname R2\n    ip domain-name ine.com\n    crypto key generate rsa\n    How many bits in the modulus [512]: 1024\n\n    ip ssh ver 2\n    username ine privilege 15 pass cisco\n    line vty 0 4\n    transport input ssh\n    login local\n    end\n\n</pre></code>\n\n\nOn all devices:\n\n\n<pre><code>\n\n    copy running-config startup-config\n    ...or...\n    write memory\n\n    show cdp neighbor\n\n</pre></code>\n\n\n\n***Task-2 Solutions***\n\n\nSwitches-2, 3 and 4:\n\n<pre><code>\n\n    enable\n    config t\n    vlan 4\n     name Payroll\n     exit\n    vlan 5\n     name Engineering\n     exit\n\n</pre></code>\n\n\nSwitch-2:\n\n\n<pre><code>\n\n    enable\n    config t\n    interface gig0/1\n      switchport mode access\n      switchport access vlan 5\n      exit\n    !\n    interface gig0/2\n      switchport mode access\n      switchport access vlan 4\n      exit\n    !\n    interface range gig0/0 , gig0/3\n      switchport trunk encapsulation dot1q\n      switchport mode dynamic desirable\n      switchport trunk allowed vlan 1,4-5\n      exit\n    !\n    interface gig0/3\n      switchport trunk native vlan 4\n    end\n    wr\n\n</pre></code>\n\n\nSwitch-3:\n\n<pre><code>\n\n    enable\n    config t\n    interface gig0/0\n      switchport mode access\n      switchport access vlan 4\n      exit\n    !\n    interface range gig0/1-2 , gig3/0\n      switchport trunk encapsulation dot1q\n      switchport trunk allowed vlan 1,4-5\n      exit\n    !\n    interface range gig0/2 , gig3/0\n      switchport mode dynamic desirable\n      exit\n    !\n    end\n    wr\n\n</pre></code>\n\nSwitch-4:\n\n<pre><code>\n\n    enable\n    config t\n    interface gig0/1\n      switchport mode access\n      switchport access vlan 5\n      exit\n    !\n    interface range gig0/0, gig0/2 , gig3/0\n      switchport trunk encapsulation dot1q\n      switchport trunk allowed vlan 1,4-5\n      exit\n    !\n    interface gig 0/0\n     switchport trunk native vlan 4\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n\n***Task-3 Solutions***\n\n- Starting Network: 50.50.50.0/24\n\n|Link ID| Qty of Hosts| Subnet Mask| Network/Prefix|\n|---|---|---|---|\n|A/B/D| 6| /29| 50.50.50.112|\n|C| 2| /30| 50.50.50.120|\n|E| 30| /27| 50.50.50.64|\n|F/N| 40| /26| 50.50.50.0|\n|G/M| 12| /28| 50.50.50.96|\n\n\n\n- Starting Network 70.70.70.0/24\n\n|Link ID| Qty of Hosts| Subnet Mask| Network/Prefix|\n|---|---|---|---|\n|S| 100| /25| 70.70.70.0|\n|R| 55| /26| 70.70.70.128|\n|P| 22| /27| 70.70.70.192|\n\n\n\n- R1 IPv4 Addressing Configuration\n\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 50.50.50.121 255.255.255.252\n     exit\n    !\n    int gig 0/1\n     ip address 50.50.50.1 255.255.255.192\n     exit\n    !\n    int gig 0/2\n     ip address 50.50.50.113 255.255.255.248\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- R2 IPv4 Addressing Configuration\n\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 50.50.50.122 255.255.255.252\n     exit\n    !\n    int gig 0/1\n     ip address 50.50.50.65 255.255.255.224\n     exit\n    !\n    int gig 0/2\n     ip address 50.50.50.97 255.255.255.240\n     exit\n    !\n    int gig 0/3\n     ip address 50.50.50.114 255.255.255.248\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- R5 IPv4 Addressing Configuration\n\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 70.70.70.193 255.255.255.224\n     exit\n    !\n    int gig 0/2\n     ip address 50.50.50.2 255.255.255.192\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- R4 IPv4 Addressing Configuration\n\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 70.70.70.194 255.255.255.224\n     exit\n    !\n    int gig 0/1\n     ip address 70.70.70.129 255.255.255.192\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- R3 IPv4 Addressing Configuration\n\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 70.70.70.1 255.255.255.128\n     exit\n    !\n    int gig 0/1\n     ip address 70.70.70.130 255.255.255.192\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n\n***Task-4 Solutions***\n\n- R1 HSRP Configuration\n\n<pre><code>\n\n    config t\n    !\n    int gig 0/2\n     standby 1 ip 50.50.50.118\n     standby 1 priority 101\n     standby 1 preempt\n     exit\n    end\n    wr\n\n</pre></code>\n\n\n- R2 HSRP Configuration\n\n<pre><code>\n\n    config t\n    !\n    int gig 0/3\n     standby 1 ip 50.50.50.118\n     exit\n    end\n    wr\n\n</pre></code>\n\n\n\n***Task-5 Solutions***\n\n- R2 DHCP Server Configuration\n\n<pre><code>\n\n    config t\n    !\n    ip dhcp pool PC1\n      network 50.50.50.112 /29\n      default-router 50.50.50.118\n      lease 2 12 30\n    !\n    ip dhcp pool PC2\n      network 50.50.50.64 /27\n      default-router 50.50.50.65\n      lease 2 12 30\n    !\n    ip dhcp pool PC3\n      network 50.50.50.96 /28\n      default-router 50.50.50.97\n      lease 2 12 30\n    !\n    end\n    wr\n\n</pre></code>\n\n- R3 DHCP Server Configuration\n\n<pre><code>\n\n    config t\n    !\n    ip dhcp pool PC4\n      network 70.70.70.0 /25\n      default-router 70.70.70.1\n    !\n    end\n    wr\n\n</pre></code>\n\n\n\n***Task-6 Solutions***\n\n- Switch-2 RSTP Configuration\n\n<pre><code>\n\n    config t\n    spanning-tree mode rapid-pvst\n    !\n    spanning-tree vlan 1 root primary\n    !\n    interface range gig 0/1 - 2\n     spanning-tree portfast edge\n     exit\n    !\n    interface gig 0/0\n     spanning-tree vlan 4 cost 100\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- Switch-3 RSTP Configuration\n\n<pre><code>\n\n    config t\n    spanning-tree mode rapid-pvst\n    !\n    spanning-tree vlan 4 root primary\n    !\n    interface gig 0/0\n     spanning-tree portfast edge\n     exit\n    !\n    interface range gig 0/2 , gig 3/0\n     channel-group 1 mode active\n    !\n    end\n    wr\n\n</pre></code>\n\n- Switch-4 RSTP Configuration\n\n<pre><code>\n\n    config t\n    spanning-tree mode rapid-pvst\n    !\n    spanning-tree vlan 5 root primary\n    !\n    interface gig 0/1\n     spanning-tree portfast edge\n     exit\n    !\n    interface range gig 0/2 , gig 3/0\n     channel-group 1 mode passive\n    !\n    end\n    wr\n\n</pre></code>\n\n\n***Task-7 Solutions***\n\n- R3 IPv4 Static Route Configuration\n\n<pre><code>\n\n    config t\n    !\n    ip route 0.0.0.0 0.0.0.0 70.70.70.129\n    end\n    wr\n\n</pre></code>\n\n\n- R4 IPv4 Static Route Configuration\n\n<pre><code>\n\n    config t\n    !\n    ip route 0.0.0.0 0.0.0.0 70.70.70.193\n    ip route 70.70.70.0 255.255.255.128 70.70.70.130\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- R5 IPv4 Static Route Configuration\n\n<pre><code>\n\n    config t\n    !\n    ip route 70.0.0.0 255.0.0.0 70.70.70.194\n    !\n    end\n    wr\n\n</pre></code>\n\n\n\n***Task-8 Solutions***\n\n- R1 OSPFv2 Configuration\n\n<pre><code>\n\n    config t\n    !\n    router ospf 1\n     router-id 0.0.0.1\n     exit\n    !\n    interface range gig 0/0, gig 0/2\n      ip ospf 1 area 0\n      exit\n    !\n    interface gig0/1\n     ip ospf 1 area 1\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n- R2 OSPFv2 Configuration\n\n<pre><code>\n\n    config t\n    !\n    router ospf 1\n     router-id 0.0.0.2\n     exit\n    !\n    interface range gig 0/0-1, gig 0/3\n      ip ospf 1 area 0\n      exit\n    !\n    interface gig0/2\n     ip ospf 1 area 1\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- R5 OSPFv2 Configuration\n\n<pre><code>\n\n    config t\n    !\n    router ospf 1\n     router-id 0.0.0.5\n     default-information originate always\n     exit\n    !\n    interface gig0/2\n     ip ospf 1 area 1\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n***Task-9 Solutions***\n\n- R2 NAT Configuration\n\n<pre><code>\n\n    config t\n    !\n    interface loopback0\n     ip address 22.22.22.1 255.255.255.240\n     ip ospf network point-to-point\n     exit\n    !\n    router ospf 1\n     network 22.22.22.0 0.0.0.255 area 0\n     exit\n    !\n    access-list 1 permit host 50.50.50.66\n    !\n    ip nat pool Final-Lab 22.22.22.2 22.22.22.14 netmask     255.255.255.240\n    ip nat inside source list 1 pool Final-Lab\n    !\n    interface gig 0/1\n     ip nat inside\n     exit\n    !\n    interface range gig 0/0 , gig 0/3\n     ip nat outside\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n***Note:*** Viewing the IP routing table within R2 shows that to reach Subnet-S, R2 would need to use the OSPF default route that it has learned.  And this default route shows two, equal cost paths...one through Gig0/0 and another through Gig0/3. So because you don't know which path will be selected when PC2 sends packets to PC4 you should make both of them NAT Outside interfaces.\n\n<pre><code>\n\n    R2#sho ip route\n    [SNIP]\n\n    O*E2  0.0.0.0/0 [110/1] via 50.50.50.121, 01:01:57,     GigabitEthernet0/0\n                    [110/1] via 50.50.50.113, 01:01:57,     GigabitEthernet0/3\n          50.0.0.0/8 is variably subnetted, 9 subnets, 6 masks\n    [SNIP]\n\n</pre></code>\n\n\n***Task-10 Solutions***\n\n- Starting Prefix = 2001:aaaa:bbbb:cc00::/56\n\n    - First subnet = 2001:aaaa:bbbb:cc00::/64\n    - Second subnet = 2001:aaaa:bbbb:cc01::/64\n    - Third subnet = 2001:aaaa:bbbb:cc02::/64\n\n    - ***5th subnet = 2001:aaaa:bbbb:cc04::/64 (LINK-S)***\n\n    - ***12th subnet = 2001:aaaa:bbbb:cc0b::/64 (LINK-R)***\n\n    - ***40th subnet = 2001:aaaa:bbbb:cc27::/64 (LINK-P)***\n\n\n***Step-1 of Task-10 is assigning relevant IPv6 addresses to interfaces***\n\n- R4 IPv6 Interface Configuration\n\n<pre><code>\n\n    conf t\n    ipv6 unicast-routing\n    !\n    interface gig0/1\n     ipv6 address 2001:aaaa:bbbb:cc0b::/64 eui-64\n     exit\n    !\n    interface gig0/0\n     ipv6 address 2001:aaaa:bbbb:cc27::/64 eui-64\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n\n- R3 IPv6 Interface Configuration\n\n<pre><code>\n\n    conf t\n    ipv6 unicast-routing\n    !\n    interface gig0/0\n     ipv6 address 2001:aaaa:bbbb:cc04::3/64\n     exit\n    !\n    interface gig0/1\n     ipv6 address 2001:aaaa:bbbb:cc0b::3/64\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n- R5 IPv6 Interface Configuration\n\n<pre><code>\n\n    conf t\n    ipv6 unicast-routing\n    !\n    interface gig0/0\n     ipv6 address autoconfig\n     exit\n    !\n    interface loopback1\n     ipv6 address 2001:5555:5555::5/64\n     exit\n    !\n    end\n    wr\n\n</pre></code>\n\n***Step-2 for Task-10 is determining the interface-IDs for router interfaces that obtained dynamic addresses. This will be needed for our IPv6 static routes later.***\n\n- R5:\n\n<pre><code>\n\n    Router-5#<b>show ipv6 interface brief</b>\n    GigabitEthernet0/0     [up/up]\n        FE80::E68:6BFF:FE6A:0\n        <b>2001:AAAA:BBBB:CC27:E68:6BFF:FE6A:0</b>\n\n</pre></code>\n\n\n\n- R4\n\n<pre><code>\n\n    Router-4#<b>show ipv6 interface brief</b>\n    GigabitEthernet0/0     [up/up]\n        FE80::E04:78FF:FE85:0\n        <b>2001:AAAA:BBBB:CC27:E04:78FF:FE85:0</b>\n    GigabitEthernet0/1     [up/up]\n        FE80::E04:78FF:FE85:1\n        <b>2001:AAAA:BBBB:CC0B:E04:78FF:FE85:1</b>\n\n</pre></code>\n\n\n***Step-3 for Task-10 is configuring the IPv6 Static Routes***\n\n- R3:\n\n<pre><code>\n\n    config t\n    !\n    ipv6 route ::/0 2001:AAAA:BBBB:CC0B:E04:78FF:FE85:1\n    end\n    wr\n\n</pre></code>\n\n\n- R4\n\n<pre><code>\n\n    config t\n    !\n    ipv6 route 2001:aaaa:bbbb:cc04::/64 2001:aaaa:bbbb:cc0b::3\n    ipv6 route 2001:5555:5555::/64 2001:AAAA:BBBB:CC27:E68:6BFF:FE6A:0\n    end\n    wr\n\n</pre></code>\n\n\n- R5\n\n<pre><code>\n\n    config t\n    !\n    ipv6 route ::/0 2001:AAAA:BBBB:CC27:E04:78FF:FE85:0\n    !\n    end\n    wr\n\n</pre></code>\n\n\n***Task-11 Solutions***\n\nAll of the tasks in this ACL section could be accomplished by configuring and applying them to routers R1 and R2.\n\nBecause (in your verification steps) it was inferred that neither R1 nor R2 should be allowed to ping PC1 (yet they are in the same subnet as PC1) the only way to accomplish the first ACL requirement of restricting pings would be to apply an ACL \"***inbound\" on Gig0/2 of R1 and Gig0/3 of R2***:\n\nIn the solutions below, PC1 was given the DHCP address of 50.50.50.115. Your lab may be different.\n\n- R1 ACL Configuration\n\n<pre><code>\n\n    config t\n    !\n    access-list 101 permit icmp host 50.50.50.115 70.70.70.128 0.0.0.127\n    access-list 101 deny icmp host 50.50.50.115 any\n    access-list 101 permit ip any any\n    !\n    access-list 2 deny 70.70.70.1\n    access-list 2 deny 70.70.70.130\n    access-list 2 permit any\n    !\n    interface gig0/2\n     ip access-group 101 in\n     exit\n    !\n    line vty 0 4\n     access-class 2 in\n     exit\n    end\n\n    wr\n\n</pre></code>\n\n- R2 ACL Configuration\n\n<pre><code>\n\n    config t\n    !\n    access-list 101 permit icmp host 50.50.50.115 70.70.70.128 0.0.0.127\n    access-list 101 deny icmp host 50.50.50.115 any\n    access-list 101 permit ip any any\n    !\n    access-list 2 deny 70.70.70.194\n    access-list 2 deny 70.70.70.129\n    access-list 2 permit any\n    !\n    interface gig0/3\n     ip access-group 101 in\n     exit\n    !\n    line vty 0 4\n     access-class 2 in\n     exit\n    end\n    wr\n    \n</pre></code>",
    "solutions_html": "<p><strong><em>Solutions</em></strong></p>\n<p><strong><em>Task-1 Solutions</em></strong></p>\n<p>Configuration to apply to all <strong><em>routers</em></strong>:</p>\n<pre><code>\n\n    enable\n    config t\n    no ip domain-lookup\n    line con 0\n     logging synch\n     exit\n    enable password cisco\n    !\n    interface gig0/0\n      no shut\n      exit\n    !\n    interface gig0/1\n      no shut\n      exit\n    !\n    interface gig0/2\n      no shut\n      exit\n    !\n    interface gig0/3\n      no shut\n      exit\n    !\n    hostname [device hostname]\n\n</pre>\n\n<p></code></p>\n<p>On all <strong><em>switches</em></strong>:</p>\n<pre><code>\n\n    enable\n    config t\n    no ip domain-lookup\n    line con 0\n     logging synch\n     exit\n    enable password cisco\n    !\n    hostname [device hostname]\n</pre>\n\n<p></code></p>\n<p>R1-specific (for <strong><em>Telnet</em></strong>)</p>\n<pre><code>\n\n    line vty 0 4\n    password cisco\n    login\n    transport input telnet\n\n</pre>\n\n<p></code></p>\n<p>R2-specific (for <strong><em>SSH</em></strong>)</p>\n<pre><code>\n\n    hostname R2\n    ip domain-name ine.com\n    crypto key generate rsa\n    How many bits in the modulus [512]: 1024\n\n    ip ssh ver 2\n    username ine privilege 15 pass cisco\n    line vty 0 4\n    transport input ssh\n    login local\n    end\n\n</pre>\n\n<p></code></p>\n<p>On all devices:</p>\n<pre><code>\n\n    copy running-config startup-config\n    ...or...\n    write memory\n\n    show cdp neighbor\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-2 Solutions</em></strong></p>\n<p>Switches-2, 3 and 4:</p>\n<pre><code>\n\n    enable\n    config t\n    vlan 4\n     name Payroll\n     exit\n    vlan 5\n     name Engineering\n     exit\n\n</pre>\n\n<p></code></p>\n<p>Switch-2:</p>\n<pre><code>\n\n    enable\n    config t\n    interface gig0/1\n      switchport mode access\n      switchport access vlan 5\n      exit\n    !\n    interface gig0/2\n      switchport mode access\n      switchport access vlan 4\n      exit\n    !\n    interface range gig0/0 , gig0/3\n      switchport trunk encapsulation dot1q\n      switchport mode dynamic desirable\n      switchport trunk allowed vlan 1,4-5\n      exit\n    !\n    interface gig0/3\n      switchport trunk native vlan 4\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p>Switch-3:</p>\n<pre><code>\n\n    enable\n    config t\n    interface gig0/0\n      switchport mode access\n      switchport access vlan 4\n      exit\n    !\n    interface range gig0/1-2 , gig3/0\n      switchport trunk encapsulation dot1q\n      switchport trunk allowed vlan 1,4-5\n      exit\n    !\n    interface range gig0/2 , gig3/0\n      switchport mode dynamic desirable\n      exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p>Switch-4:</p>\n<pre><code>\n\n    enable\n    config t\n    interface gig0/1\n      switchport mode access\n      switchport access vlan 5\n      exit\n    !\n    interface range gig0/0, gig0/2 , gig3/0\n      switchport trunk encapsulation dot1q\n      switchport trunk allowed vlan 1,4-5\n      exit\n    !\n    interface gig 0/0\n     switchport trunk native vlan 4\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-3 Solutions</em></strong></p>\n<ul>\n<li>Starting Network: 50.50.50.0/24</li>\n</ul>\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>A/B/D</td>\n<td>6</td>\n<td>/29</td>\n<td>50.50.50.112</td>\n</tr>\n<tr>\n<td>C</td>\n<td>2</td>\n<td>/30</td>\n<td>50.50.50.120</td>\n</tr>\n<tr>\n<td>E</td>\n<td>30</td>\n<td>/27</td>\n<td>50.50.50.64</td>\n</tr>\n<tr>\n<td>F/N</td>\n<td>40</td>\n<td>/26</td>\n<td>50.50.50.0</td>\n</tr>\n<tr>\n<td>G/M</td>\n<td>12</td>\n<td>/28</td>\n<td>50.50.50.96</td>\n</tr>\n</tbody>\n</table>\n<ul>\n<li>Starting Network 70.70.70.0/24</li>\n</ul>\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>S</td>\n<td>100</td>\n<td>/25</td>\n<td>70.70.70.0</td>\n</tr>\n<tr>\n<td>R</td>\n<td>55</td>\n<td>/26</td>\n<td>70.70.70.128</td>\n</tr>\n<tr>\n<td>P</td>\n<td>22</td>\n<td>/27</td>\n<td>70.70.70.192</td>\n</tr>\n</tbody>\n</table>\n<ul>\n<li>R1 IPv4 Addressing Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 50.50.50.121 255.255.255.252\n     exit\n    !\n    int gig 0/1\n     ip address 50.50.50.1 255.255.255.192\n     exit\n    !\n    int gig 0/2\n     ip address 50.50.50.113 255.255.255.248\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R2 IPv4 Addressing Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 50.50.50.122 255.255.255.252\n     exit\n    !\n    int gig 0/1\n     ip address 50.50.50.65 255.255.255.224\n     exit\n    !\n    int gig 0/2\n     ip address 50.50.50.97 255.255.255.240\n     exit\n    !\n    int gig 0/3\n     ip address 50.50.50.114 255.255.255.248\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R5 IPv4 Addressing Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 70.70.70.193 255.255.255.224\n     exit\n    !\n    int gig 0/2\n     ip address 50.50.50.2 255.255.255.192\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R4 IPv4 Addressing Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 70.70.70.194 255.255.255.224\n     exit\n    !\n    int gig 0/1\n     ip address 70.70.70.129 255.255.255.192\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R3 IPv4 Addressing Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    int gig 0/0\n     ip address 70.70.70.1 255.255.255.128\n     exit\n    !\n    int gig 0/1\n     ip address 70.70.70.130 255.255.255.192\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-4 Solutions</em></strong></p>\n<ul>\n<li>R1 HSRP Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    int gig 0/2\n     standby 1 ip 50.50.50.118\n     standby 1 priority 101\n     standby 1 preempt\n     exit\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R2 HSRP Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    int gig 0/3\n     standby 1 ip 50.50.50.118\n     exit\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-5 Solutions</em></strong></p>\n<ul>\n<li>R2 DHCP Server Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ip dhcp pool PC1\n      network 50.50.50.112 /29\n      default-router 50.50.50.118\n      lease 2 12 30\n    !\n    ip dhcp pool PC2\n      network 50.50.50.64 /27\n      default-router 50.50.50.65\n      lease 2 12 30\n    !\n    ip dhcp pool PC3\n      network 50.50.50.96 /28\n      default-router 50.50.50.97\n      lease 2 12 30\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R3 DHCP Server Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ip dhcp pool PC4\n      network 70.70.70.0 /25\n      default-router 70.70.70.1\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-6 Solutions</em></strong></p>\n<ul>\n<li>Switch-2 RSTP Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    spanning-tree mode rapid-pvst\n    !\n    spanning-tree vlan 1 root primary\n    !\n    interface range gig 0/1 - 2\n     spanning-tree portfast edge\n     exit\n    !\n    interface gig 0/0\n     spanning-tree vlan 4 cost 100\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>Switch-3 RSTP Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    spanning-tree mode rapid-pvst\n    !\n    spanning-tree vlan 4 root primary\n    !\n    interface gig 0/0\n     spanning-tree portfast edge\n     exit\n    !\n    interface range gig 0/2 , gig 3/0\n     channel-group 1 mode active\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>Switch-4 RSTP Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    spanning-tree mode rapid-pvst\n    !\n    spanning-tree vlan 5 root primary\n    !\n    interface gig 0/1\n     spanning-tree portfast edge\n     exit\n    !\n    interface range gig 0/2 , gig 3/0\n     channel-group 1 mode passive\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-7 Solutions</em></strong></p>\n<ul>\n<li>R3 IPv4 Static Route Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ip route 0.0.0.0 0.0.0.0 70.70.70.129\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R4 IPv4 Static Route Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ip route 0.0.0.0 0.0.0.0 70.70.70.193\n    ip route 70.70.70.0 255.255.255.128 70.70.70.130\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R5 IPv4 Static Route Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ip route 70.0.0.0 255.0.0.0 70.70.70.194\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-8 Solutions</em></strong></p>\n<ul>\n<li>R1 OSPFv2 Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    router ospf 1\n     router-id 0.0.0.1\n     exit\n    !\n    interface range gig 0/0, gig 0/2\n      ip ospf 1 area 0\n      exit\n    !\n    interface gig0/1\n     ip ospf 1 area 1\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R2 OSPFv2 Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    router ospf 1\n     router-id 0.0.0.2\n     exit\n    !\n    interface range gig 0/0-1, gig 0/3\n      ip ospf 1 area 0\n      exit\n    !\n    interface gig0/2\n     ip ospf 1 area 1\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R5 OSPFv2 Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    router ospf 1\n     router-id 0.0.0.5\n     default-information originate always\n     exit\n    !\n    interface gig0/2\n     ip ospf 1 area 1\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-9 Solutions</em></strong></p>\n<ul>\n<li>R2 NAT Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    interface loopback0\n     ip address 22.22.22.1 255.255.255.240\n     ip ospf network point-to-point\n     exit\n    !\n    router ospf 1\n     network 22.22.22.0 0.0.0.255 area 0\n     exit\n    !\n    access-list 1 permit host 50.50.50.66\n    !\n    ip nat pool Final-Lab 22.22.22.2 22.22.22.14 netmask     255.255.255.240\n    ip nat inside source list 1 pool Final-Lab\n    !\n    interface gig 0/1\n     ip nat inside\n     exit\n    !\n    interface range gig 0/0 , gig 0/3\n     ip nat outside\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Note:</em></strong> Viewing the IP routing table within R2 shows that to reach Subnet-S, R2 would need to use the OSPF default route that it has learned.  And this default route shows two, equal cost paths...one through Gig0/0 and another through Gig0/3. So because you don't know which path will be selected when PC2 sends packets to PC4 you should make both of them NAT Outside interfaces.</p>\n<pre><code>\n\n    R2#sho ip route\n    [SNIP]\n\n    O*E2  0.0.0.0/0 [110/1] via 50.50.50.121, 01:01:57,     GigabitEthernet0/0\n                    [110/1] via 50.50.50.113, 01:01:57,     GigabitEthernet0/3\n          50.0.0.0/8 is variably subnetted, 9 subnets, 6 masks\n    [SNIP]\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-10 Solutions</em></strong></p>\n<ul>\n<li>\n<p>Starting Prefix = 2001:aaaa:bbbb:cc00::/56</p>\n<ul>\n<li>First subnet = 2001:aaaa:bbbb:cc00::/64</li>\n<li>Second subnet = 2001:aaaa:bbbb:cc01::/64</li>\n<li>\n<p>Third subnet = 2001:aaaa:bbbb:cc02::/64</p>\n</li>\n<li>\n<p><strong><em>5th subnet = 2001:aaaa:bbbb:cc04::/64 (LINK-S)</em></strong></p>\n</li>\n<li>\n<p><strong><em>12th subnet = 2001:aaaa:bbbb:cc0b::/64 (LINK-R)</em></strong></p>\n</li>\n<li>\n<p><strong><em>40th subnet = 2001:aaaa:bbbb:cc27::/64 (LINK-P)</em></strong></p>\n</li>\n</ul>\n</li>\n</ul>\n<p><strong><em>Step-1 of Task-10 is assigning relevant IPv6 addresses to interfaces</em></strong></p>\n<ul>\n<li>R4 IPv6 Interface Configuration</li>\n</ul>\n<pre><code>\n\n    conf t\n    ipv6 unicast-routing\n    !\n    interface gig0/1\n     ipv6 address 2001:aaaa:bbbb:cc0b::/64 eui-64\n     exit\n    !\n    interface gig0/0\n     ipv6 address 2001:aaaa:bbbb:cc27::/64 eui-64\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R3 IPv6 Interface Configuration</li>\n</ul>\n<pre><code>\n\n    conf t\n    ipv6 unicast-routing\n    !\n    interface gig0/0\n     ipv6 address 2001:aaaa:bbbb:cc04::3/64\n     exit\n    !\n    interface gig0/1\n     ipv6 address 2001:aaaa:bbbb:cc0b::3/64\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R5 IPv6 Interface Configuration</li>\n</ul>\n<pre><code>\n\n    conf t\n    ipv6 unicast-routing\n    !\n    interface gig0/0\n     ipv6 address autoconfig\n     exit\n    !\n    interface loopback1\n     ipv6 address 2001:5555:5555::5/64\n     exit\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Step-2 for Task-10 is determining the interface-IDs for router interfaces that obtained dynamic addresses. This will be needed for our IPv6 static routes later.</em></strong></p>\n<ul>\n<li>R5:</li>\n</ul>\n<pre><code>\n\n    Router-5#<b>show ipv6 interface brief</b>\n    GigabitEthernet0/0     [up/up]\n        FE80::E68:6BFF:FE6A:0\n        <b>2001:AAAA:BBBB:CC27:E68:6BFF:FE6A:0</b>\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R4</li>\n</ul>\n<pre><code>\n\n    Router-4#<b>show ipv6 interface brief</b>\n    GigabitEthernet0/0     [up/up]\n        FE80::E04:78FF:FE85:0\n        <b>2001:AAAA:BBBB:CC27:E04:78FF:FE85:0</b>\n    GigabitEthernet0/1     [up/up]\n        FE80::E04:78FF:FE85:1\n        <b>2001:AAAA:BBBB:CC0B:E04:78FF:FE85:1</b>\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Step-3 for Task-10 is configuring the IPv6 Static Routes</em></strong></p>\n<ul>\n<li>R3:</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ipv6 route ::/0 2001:AAAA:BBBB:CC0B:E04:78FF:FE85:1\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R4</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ipv6 route 2001:aaaa:bbbb:cc04::/64 2001:aaaa:bbbb:cc0b::3\n    ipv6 route 2001:5555:5555::/64 2001:AAAA:BBBB:CC27:E68:6BFF:FE6A:0\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R5</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    ipv6 route ::/0 2001:AAAA:BBBB:CC27:E04:78FF:FE85:0\n    !\n    end\n    wr\n\n</pre>\n\n<p></code></p>\n<p><strong><em>Task-11 Solutions</em></strong></p>\n<p>All of the tasks in this ACL section could be accomplished by configuring and applying them to routers R1 and R2.</p>\n<p>Because (in your verification steps) it was inferred that neither R1 nor R2 should be allowed to ping PC1 (yet they are in the same subnet as PC1) the only way to accomplish the first ACL requirement of restricting pings would be to apply an ACL \"<strong><em>inbound\" on Gig0/2 of R1 and Gig0/3 of R2</em></strong>:</p>\n<p>In the solutions below, PC1 was given the DHCP address of 50.50.50.115. Your lab may be different.</p>\n<ul>\n<li>R1 ACL Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    access-list 101 permit icmp host 50.50.50.115 70.70.70.128 0.0.0.127\n    access-list 101 deny icmp host 50.50.50.115 any\n    access-list 101 permit ip any any\n    !\n    access-list 2 deny 70.70.70.1\n    access-list 2 deny 70.70.70.130\n    access-list 2 permit any\n    !\n    interface gig0/2\n     ip access-group 101 in\n     exit\n    !\n    line vty 0 4\n     access-class 2 in\n     exit\n    end\n\n    wr\n\n</pre>\n\n<p></code></p>\n<ul>\n<li>R2 ACL Configuration</li>\n</ul>\n<pre><code>\n\n    config t\n    !\n    access-list 101 permit icmp host 50.50.50.115 70.70.70.128 0.0.0.127\n    access-list 101 deny icmp host 50.50.50.115 any\n    access-list 101 permit ip any any\n    !\n    access-list 2 deny 70.70.70.194\n    access-list 2 deny 70.70.70.129\n    access-list 2 permit any\n    !\n    interface gig0/3\n     ip access-group 101 in\n     exit\n    !\n    line vty 0 4\n     access-class 2 in\n     exit\n    end\n    wr\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
}