×

Ccna-2v7.0 Case Study -rev B- !exclusive! -

The design relies on standard static paths, fully specified paths for IPv6 environments, and summary structures to limit routing table inflation.

The main Phoenix block is 172.25.64.0/23 . This provides 512 total addresses. It must be sliced into functional local area networks (LANs): VLAN ID & Name Required Hosts Subnet Address Subnet Mask / Prefix 172.25.64.0 255.255.255.0 (/24) VLAN 20 - PHX-MGMT 172.25.65.0 255.255.255.224 (/27) VLAN 99 - NATIVE Infrastructure 172.25.65.32 255.255.255.240 (/28) Dual-Stack IPv6 Deployment

For each access switch (S1, S2), apply the following:

With localized Layer 2 domains defined, you must establish multi-subnet communication at the edge router gateways. This is achieved using a topology via explicit sub-interfaces. Multi-Subinterface Provisioning ccna-2v7.0 case study -rev b-

: Build baseline device controls, SSH v2 lines, and modern Layer 2 switch security.

ip route 0.0.0.0 0.0.0.0 [next_hop_ip | exit_interface]

ChicagoRouter# configure terminal ChicagoRouter(config)# ip dhcp excluded-address 172.25.65.0 172.25.65.15 ChicagoRouter(config)# ip dhcp pool PHX-LAN-120 ChicagoRouter(dhcp-config)# network 172.25.65.0 255.255.255.128 ChicagoRouter(dhcp-config)# default-router 172.25.65.1 ChicagoRouter(dhcp-config)# dns-server 209.165.200.225 ChicagoRouter(dhcp-config)# exit Use code with caution. The design relies on standard static paths, fully

The network topology is designed as follows:

Switch# configure terminal Switch(config)# vlan 110 Switch(config-vlan)# name PHX-LAN-110 Switch(config-vlan)# vlan 120 Switch(config-vlan)# name PHX-LAN-120 Switch(config-vlan)# vlan 77 Switch(config-vlan)# name Native-Trunk Switch(config-vlan)# exit Use code with caution. Phase II: Device Initialization and Management Security

! Enterprise Core Sub-Interface Configuration (Router-on-a-Stick) interface GigabitEthernet0/0/1.10 encapsulation dot1Q 10 ip address 192.168.10.1 255.255.255.0 ipv6 address 2001:db8:acad:10::1/64 ipv6 address fe80::1 link-local description MGMT_Gateway interface GigabitEthernet0/0/1.20 encapsulation dot1Q 20 ip address 192.168.20.1 255.255.255.0 ipv6 address 2001:db8:acad:20::1/64 ipv6 address fe80::1 link-local description PROD_Gateway interface GigabitEthernet0/0/1.99 encapsulation dot1Q 99 native description Native_Transit_Drop Use code with caution. Phase 3: Switch Hardening and Infrastructure Security It must be sliced into functional local area

show ip int brief show ip route ping 10.10.20.1

The is a comprehensive hands-on lab assessment found in the Cisco Networking Academy Cisco NetAcad curriculum under the Switching, Routing, and Wireless Essentials (SRWE) course. This comprehensive project challenges network engineering students to apply foundational concepts—including subnetting, static routing, VLAN division, switch security protocols, DHCP deployment, wireless integration, and the Spanning-Tree Protocol (STP) —to design, configure, and troubleshoot an enterprise infrastructure.

Exclude static device assignments and management spaces from the dynamic allocation pools.

The design relies on standard static paths, fully specified paths for IPv6 environments, and summary structures to limit routing table inflation.

The main Phoenix block is 172.25.64.0/23 . This provides 512 total addresses. It must be sliced into functional local area networks (LANs): VLAN ID & Name Required Hosts Subnet Address Subnet Mask / Prefix 172.25.64.0 255.255.255.0 (/24) VLAN 20 - PHX-MGMT 172.25.65.0 255.255.255.224 (/27) VLAN 99 - NATIVE Infrastructure 172.25.65.32 255.255.255.240 (/28) Dual-Stack IPv6 Deployment

For each access switch (S1, S2), apply the following:

With localized Layer 2 domains defined, you must establish multi-subnet communication at the edge router gateways. This is achieved using a topology via explicit sub-interfaces. Multi-Subinterface Provisioning

: Build baseline device controls, SSH v2 lines, and modern Layer 2 switch security.

ip route 0.0.0.0 0.0.0.0 [next_hop_ip | exit_interface]

ChicagoRouter# configure terminal ChicagoRouter(config)# ip dhcp excluded-address 172.25.65.0 172.25.65.15 ChicagoRouter(config)# ip dhcp pool PHX-LAN-120 ChicagoRouter(dhcp-config)# network 172.25.65.0 255.255.255.128 ChicagoRouter(dhcp-config)# default-router 172.25.65.1 ChicagoRouter(dhcp-config)# dns-server 209.165.200.225 ChicagoRouter(dhcp-config)# exit Use code with caution.

The network topology is designed as follows:

Switch# configure terminal Switch(config)# vlan 110 Switch(config-vlan)# name PHX-LAN-110 Switch(config-vlan)# vlan 120 Switch(config-vlan)# name PHX-LAN-120 Switch(config-vlan)# vlan 77 Switch(config-vlan)# name Native-Trunk Switch(config-vlan)# exit Use code with caution. Phase II: Device Initialization and Management Security

! Enterprise Core Sub-Interface Configuration (Router-on-a-Stick) interface GigabitEthernet0/0/1.10 encapsulation dot1Q 10 ip address 192.168.10.1 255.255.255.0 ipv6 address 2001:db8:acad:10::1/64 ipv6 address fe80::1 link-local description MGMT_Gateway interface GigabitEthernet0/0/1.20 encapsulation dot1Q 20 ip address 192.168.20.1 255.255.255.0 ipv6 address 2001:db8:acad:20::1/64 ipv6 address fe80::1 link-local description PROD_Gateway interface GigabitEthernet0/0/1.99 encapsulation dot1Q 99 native description Native_Transit_Drop Use code with caution. Phase 3: Switch Hardening and Infrastructure Security

show ip int brief show ip route ping 10.10.20.1

The is a comprehensive hands-on lab assessment found in the Cisco Networking Academy Cisco NetAcad curriculum under the Switching, Routing, and Wireless Essentials (SRWE) course. This comprehensive project challenges network engineering students to apply foundational concepts—including subnetting, static routing, VLAN division, switch security protocols, DHCP deployment, wireless integration, and the Spanning-Tree Protocol (STP) —to design, configure, and troubleshoot an enterprise infrastructure.

Exclude static device assignments and management spaces from the dynamic allocation pools.