[CCNAv6 S1] 8.4.1.2 Packet Tracer - Skills Integration Challenge



Packet Tracer - Skills Integration Challenge
Addressing Table


Scenario

As a network technician familiar with IPv4 and IPv6 addressing implementations, you are now ready to take an existing network infrastructure and apply your knowledge and skills to finalize the configuration. In this activity, the network administrator has already configured some commands on the routers. Do not erase or modify those configurations. Your task is to complete the IPv4 and IPv6 addressing scheme, implement IPv4 and IPv6 addressing, and verify connectivity.

Requirements

·         Configure the initial settings on Branch-A and Branch-B, including the hostname, banner, lines, and passwords. Use cisco as the user EXEC password and class as the privileged EXEC password. Encrypt all passwords.
·         LAN A1 is using the subnet 172.20.16.0/23. Assign the next available subnet to LAN A2 for a maximum of 250 hosts.
·         LAN B1 is using the subnet 2001:DB8:FADE:00FF::/64. Assign the next available subnet to LAN B2.
·         Finish documenting the addressing scheme in the Addressing Table using the following guidelines:
-       Assign the first IP address for LAN A1, LAN A2, LAN B1, and LAN B2 to the router interface.
-       For the IPv4 networks, assign the last IPv4 address to the PCs.
-       For the IPv6 networks, assign the 16th IPv6 address to the PCs.
·         Configure the routers addressing according to your documentation. Include an appropriate description for each router interface. Branch-B uses FE80::B as the link-local address.
·         Configure PCs with addressing according to your documentation. The DNS Server addresses for IPv4 and IPv6 are shown in the topology.
·         Verify connectivity between the IPv4 PCs and between the IPv6 PCs.
·         Verify the IPv4 PCs can access the web page at central.pka.
·         Verify the IPv6 PCs can access the web page at centralv6.pka.
Suggested Scoring Rubric



Configuration Branch-A:

enable
configure terminal
hostname Branch-A
banner motd #Warning#
line console 0
 password cisco
 login
line vty 0 15
 password cisco
 login
exit
enable secret class
service password-encryption
interface g0/0
 ip add 172.20.16.1 255.255.254.0
 no shutdown
interface g0/1
 ip add 172.20.18.1 255.255.255.0
 no shutdown
interface g0/2
 ip add 172.20.31.254 255.255.255.252
 no shutdown
 exit
!


Configuration Branch-B:

enable
configure terminal
hostname Branch-B
banner motd #Warning#
line console 0
 password cisco
 login
line vty 0 15
 password cisco
 login
exit
enable secret class
service password-encryption
interface g0/0
 ipv6 address 2001:DB8:FADE:00FF::1/64
 ipv6 address FE80::B link-local
 no shutdown
interface g0/1
 ipv6 address 2001:DB8:FADE:0100::1/64
 ipv6 address FE80::B link-local
 no shutdown
interface g0/2
 ipv6 address 2001:DB8:FFFF:FFFF::2/64
 ipv6 address FE80::B link-local
 no shutdown
 exit
!
Configuration PC-A1:



Configuration PC-A2:



Configuration PC-B1:




Configuration PC-B1:





Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

[CCNAv6 S2] 2.2.2.4 Packet Tracer - Configuring IPv4 Static and Default Routes

Hình ảnh
Packet Tracer - Configuring IPv4 Static and Default Routes Addressing Table Objectives Part 1: Examine the Network and Evaluate the Need for Static Routing Part 2: Configure Static and Default Routes Part 3: Verify Connectivity Background In this activity, you will configure static and default routes. A static route is a route that is entered manually by the network administrator to create a reliable and safe route. There are four different static routes that are used in this activity: a recursive static route, a directly attached static route, a fully specified static route, and a default route. Part 1:     Examine the Network and Evaluate the Need for Static Routing a.     Looking at the topology diagram, how many networks are there in total? b.    How many networks are directly connected to R1, R2, and R3? c.     How many static routes are required by each router to reach networks that are not directly connected? d.    Test connectivity to the R2 and R3
Đọc thêm

[CCNAv6 S3] 7.2.3.5 Packet Tracer - Troubleshooting EIGRP for IPv4

Hình ảnh
Packet Tracer – Troubleshooting EIGRP for IPv4 Addressing Table Scenario In this activity, you will troubleshoot EIGRP neighbor issues. Use show commands to identify errors in the network configuration. Then, you will document the errors you discover and implement an appropriate solution. Finally, you will verify full end-to-end connectivity is restored. Troubleshooting Process 1.     Use testing commands to discover connectivity problems in the network and document the problem in the Documentation Table. 2.     Use verification commands to discover the source of the problem and devise an appropriate solution to implement. Document the proposed solution in the Documentation Table. 3.     Implement each solution one at a time and verify if the problem is resolved. Indicate the resolution status in the Documentation Table. 4.     If the problem is not resolved, it may be necessary to first remove the implemented solution before returning to Step 2. 5.     Once al
Đọc thêm

[CCNAv6 S2] 8.3.1.2 Packet Tracer - Skills Integration Challenge

Hình ảnh
Packet Tracer – Skills Integration Challenge Addressing Table VLAN Port Assignments and DHCP Information 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. - 
Đọc thêm