8.3.1.2 Packet Tracer

 

Last Updated on April 29, 2018 by

8.3.1.2 Packet Tracer – CCNA Skills Integration Challenge

8.3.1.2 Packet Tracer Answers

Packet Tracer – CCNA Skills Integration Challenge

8.3.1.2 Packet Tracer - EIGRP IPv4 and IPv6 Skills Integration Challenge 8.3.1.2 Packet Tracer - EIGRP IPv4 and IPv6 Skills Integration Challenge This one took me a long time because I could not summirize the ipv6 addresses. Packet Tracer does not currently grade EIGRP for IPv6 summary routes. Therefore, part of your grade depends on routing table verification by your instructor.

Answer Note: Red font color or gray highlights indicate text that appears in the Answer copy only.

Contribute to ebvjr/ccna2-v6-pkt development by creating an account on GitHub. Download PDF - 8.3.1.2 Packet Tracer - Skills Integration Challenge Instructions qn8rk60k7kl1. Read Online 8 3 1 2 Packet Tracer Skills Integration Challenge Answers 8 3 1 2 Packet Tracer Skills Integration Challenge Answers Yeah, reviewing a books 8 3 1 2 packet tracer skills integration challenge answers could be credited with your close contacts listings. This is just one of the solutions for you to be successful.

Topology

8.3.1.2 Packet Tracer – CCNA Skills Integration Challenge

Addressing Table

DeviceInterfaceIP AddressSubnet Mask
HQG0/010.0.1.1255.255.255.0
G0/1192.0.2.1255.255.255.0
S0/0/010.255.255.1255.255.255.252
S0/0/110.255.255.253255.255.255.252
S0/1/0209.165.201.1255.255.255.252
B1G0/0.1010.1.10.1255.255.255.0
G0/0.2010.1.20.1255.255.255.0
G0/0.3010.1.30.1255.255.255.0
G0/0.9910.1.99.1255.255.255.0
S0/0/010.255.255.2255.255.255.252
B1-S2VLAN 9910.1.99.22255.255.255.0

VLAN Configurations and Port Mappings

VLAN NumberNetwork AddressVLAN NamePort Mappings
1010.1.10.0/24AdminF0/6
2010.1.20.0/24SalesF0/11
3010.1.30.0/24ProductionF0/16
9910.1.99.0/24Mgmt&NativeF0/1-4
999N/ABlackHoleUnused Ports

Scenario

In this comprehensive CCNA skills activity, the XYZ Corporation uses a combination of eBGP and PPP for WAN connections. Other technologies include NAT, DHCP, static and default routing, EIGRP for IPv4, inter-VLAN routing, and VLAN configurations. Security configurations include SSH, port security, switch security, and ACLs.

Note: Only HQ, B1, B1-S2, and the PCs are accessible. The user EXEC password is cisco and the privileged EXEC password is class.

Requirements

PPP

  • Configure the WAN link from HQ to the Internet using PPP encapsulation and CHAP authentication.
    • Create a user ISP with the password of cisco.
  • Configure the WAN link from HQ to NewB using PPP encapsulation and PAP authentication.
    • Create a user NewB with the password of cisco.

Note: The ppp pap sent-username is not graded by Packet Tracer. However, it must be configured before the link will come up between HQ and NewB.

eBGP

  • Configure eBGP between HQ and the Internet.
    • HQ belongs to AS 65000.
    • The IP address for the BGP router in the Internet cloud is 209.165.201.2.
    • Advertise the 192.0.2.0/24 network to the Internet.

NAT

  • Configure dynamic NAT on HQ
    • Allow all addresses for the 10.0.0.0/8 address space to be translated using a standard access list named NAT.
    • XYZ Corporation owns the 209.165.200.240/29 address space. The pool, HQ, uses addresses .241 to .245 with a /29 mask. Bind the NAT ACL to the pool HQ. Configure PAT.
    • The connections to the Internet and HQ-DataCenter are outside XYZ Corporation.

8.3.1.2 Packet Tracer

Inter-VLAN Routing

  • Configure B1 for inter-VLAN routing.
    • Using the addressing table for branch routers, configure and activate the LAN interface for inter-VLAN routing. VLAN 99 is the native VLAN.

Static and Default Routing

  • Configure HQ with a static route to the NewB LAN. Use the exit interface as an argument.
  • Configure B1 with a default route to HQ. Use the next-hop IP address as an argument.

EIGRP Routing

8.1.3.3 packet tracer answer
  • Configure and optimize HQ and B1 with EIGRP routing.
    • Use autonomous system 100.
    • Disable EIGRP updates on appropriate interfaces.

VLANs and Trunking Configurations

Note: Logging to the console is turned off on B1-S2 so that the Native VLAN mismatch messages will not interrupt your configurations. If you would prefer to view console messages, enter the global configuration command logging console.

  • Configure trunking and VLANs on B1-S2.
    • Create and name the VLANs listed in the VLAN Configuration and Port Mappings table on B1-S2 only.
    • Configure the VLAN 99 interface and default gateway.
    • Set trunking mode to on for F0/1 – F0/4.
    • Assign VLANs to the appropriate access ports.
    • Disable all unused ports and assign the BlackHole VLAN.

Port Security

  • Use the following policy to establish port security on the B1-S2 access ports:
    • Allow two MAC addresses to be learned on the port.
    • Configure the learned MAC addresses to be added to the configuration.
    • Set the port to send a message if there is a security violation. Traffic is still allowed from the first two MAC addresses learned.

SSH

  • Configure HQ to use SSH for remote access.
    • Set the modulus to 2048. The domain name is CCNASkills.com.
    • The username is admin and the password is adminonly.
    • Only SSH should be allowed on VTY lines.
    • Modify the SSH defaults: version 2; 60-second timeout; two retries.

DHCP

  • On B1, configure a DHCP pool for the Sales VLAN 20 using the following requirements:
    • Exclude the first 10 IP addresses in the range.
    • The case-sensitive pool name is VLAN20.
    • Include the DNS server attached to the HQ LAN as part of the DHCP configuration.
  • Configure the Sales PC to use DHCP.

Click Sales PC > Desktop > IP Configuration
Change to DHCP and verify PC gets addressing information

Access List Policy

  • Because HQ is connected to the Internet, configure and apply a named ACL called HQINBOUND in the following order:
    • Allow inbound BGP updates (TCP port 179) for any source to any destination.
    • Allow inbound HTTP requests from any source to the HQ-DataCenter network.
    • Allow only established TCP sessions from the Internet.
    • Allow only inbound ping replies from the Internet.
    • Explicitly block all other inbound access from the Internet.

Connectivity

  • Verify full connectivity from each PC to WWW.pka and www.cisco.pka.
  • The Outside Host should be able to access the webpage at WWW.pka.
  • All the test in Scenario 0 should be successful.

Last Updated on March 20, 2018 by

8.3.1.2 Packet Tracer – Skills Integration Challenge

Packet Tracer – Skills Integration Challenge (Answer Version)

Answer Note: Red font color or Gray highlights indicate text that appears in the Answer copy only.

Topology

8.3.1.2 Packet Tracer – Skills Integration Challenge

Addressing Table

DeviceInterfaceIP AddressSubnet MaskDefault Gateway
R1G0/0.10172.31.10.1255.255.255.224N/A
G0/0.20172.31.20.1255.255.255.240N/A
G0/0.30172.31.30.1255.255.255.128N/A
G0/0.40172.31.40.1255.255.255.192N/A
G0/1DHCP AssignedDHCP AssignedN/A
PC1NICDHCP AssignedDHCP AssignedDHCP Assigned
PC2NICDHCP AssignedDHCP AssignedDHCP Assigned
PC3NICDHCP AssignedDHCP AssignedDHCP Assigned
PC4NICDHCP AssignedDHCP AssignedDHCP Assigned

VLAN Port Assignments and DHCP Information

Packet Tracer 8.4.1.2 Solution

PortsVLAN Number – NameDHCP Pool NameNetwork
Fa0/5 – 0/9VLAN 10 – SalesVLAN_10172.31.10.0/27
Fa0/10 – Fa0/14VLAN 20 – ProductionVLAN_20172.31.20.0/28
Fa0/15 – Fa0/19VLAN 30 – MarketingVLAN_30172.31.30.0/25
Fa0/20 – Fa0/24VLAN 40 – HRVLAN_40172.31.40.0/26

Scenario

In this culminating activity, you will configure VLANs, trunks, DHCP Server, DHCP relay agents, and configure a router as a DHCP client.

Requirements

Using the information in the tables above, implement the following requirements:

  • Create VLANs on S2 and assign VLANs to appropriate ports. Names are case-sensitive
  • Configure S2 ports for trunking.
  • Configure all non-trunk ports on S2 as access ports.
  • Configure R1 to route between VLANs. Subinterface names should match the VLAN number.
  • Configure R1 to act as a DHCP server for the VLANs attached to S2.
    • Create a DHCP pool for each VLAN. Names are case-sensitive.
    • Assign the appropriate addresses to each pool.
    • Configure DHCP to provide the default gateway address
    • Configure the DNS server 209.165.201.14 for each pool.
    • Prevent the first 10 addresses from each pool from being distributed to end devices.
  • Verify that each PC has an address assigned from the correct DHCP pool.
  • Note: DHCP address assignments may take some time. Click Fast Forward Time to speed up the process.
  • Configure R1 as a DHCP client so that it receives an IP address from the ISP network.
  • Verify all devices can now ping each other and www.cisco.pka.

Router R1

Switch S2