Ccna-2v7.0 Case Study -rev B- May 2026

Case Study:

Company Background

Acme Inc. is a medium-sized company that specializes in providing IT services to small businesses. The company has recently experienced rapid growth and needs to expand its network infrastructure to accommodate its growing number of employees.

Network Requirements

The company has two main buildings: a headquarters building and a satellite building, located about 100 meters apart. The headquarters building has 50 employees, while the satellite building has 20 employees. The company requires a network infrastructure that can:

  1. Provide connectivity between the two buildings.
  2. Support 70 employees with IP phones and computers.
  3. Segment the network into different departments (Sales, Marketing, IT, etc.).
  4. Implement Quality of Service (QoS) to prioritize voice and video traffic.

Current Network Status

The current network consists of:

  • A single Cisco 2960X switch in the headquarters building, connected to a router (Cisco 1841).
  • No connectivity between the two buildings.

Task

Your task is to design and implement a network infrastructure that meets the company's requirements. You will need to:

  1. Choose the right network devices (switches, routers, etc.).
  2. Design a network topology that meets the company's requirements.
  3. Configure the network devices to support the required features (VLANs, QoS, etc.).

CCNA 2 v7.0 Case Study - Rev B

Part 1: Network Design

Using Cisco's Network Assistant tool or Packet Tracer, design a network topology that meets the company's requirements. Your design should include:

  • Two Cisco 2960X switches, one in each building.
  • A Cisco 2851 router to connect the two buildings.
  • A separate VLAN for each department.
  • A QoS policy to prioritize voice and video traffic.

Part 2: Network Configuration

Configure the network devices according to your design:

  • Configure VLANs on the switches.
  • Configure trunking between the switches and the router.
  • Configure QoS on the router.

Part 3: Verification and Troubleshooting

Verify that your network design and configuration meet the company's requirements:

  • Use show commands to verify VLAN configurations.
  • Use Wireshark or Packet Tracer to verify QoS policies.

Deliverables

Your case study should include:

  • A network diagram showing the topology.
  • A list of network devices and their configurations.
  • A verification section showing the output of relevant show commands.

This case study assesses your skills in designing and implementing a network infrastructure using Cisco devices, as well as your ability to configure and troubleshoot network features such as VLANs and QoS. Good luck!

The CCNA-2 v7.0 Case Study -Rev B- is a comprehensive capstone project within the Cisco Networking Academy's Switching, Routing, and Wireless Essentials (SRWE) curriculum. It serves as a practical assessment where students must design, configure, and troubleshoot a multi-site enterprise network that reflects real-world deployment challenges. Objectives of the Case Study

The primary goal of Revision B is to validate your ability to integrate the core technologies introduced in CCNA v7.0. Key objectives include:

VLAN and Trunking Implementation: Segregating traffic for security and performance using 802.1Q trunks.

Redundancy Protocols: Configuring EtherChannel for link aggregation and Spanning Tree Protocol (STP) to prevent loops.

Dynamic Addressing: Setting up DHCPv4 and DHCPv6 (Stateless/Stateful) to automate IP management.

Routing and Security: Implementing Inter-VLAN routing (Router-on-a-Stick or Layer 3 Switching) and securing the infrastructure with SSH and Port Security. Core Configuration Components

The case study typically requires a hands-on approach using Cisco Packet Tracer or physical hardware to meet the following requirements: 1. Layer 2 Redundancy and Switching

Students must ensure high availability by configuring EtherChannel (LACP) between core switches. This allows for increased bandwidth and prevents a single point of failure. Additionally, the STP Bridge Priority must be adjusted to designate specific switches as Root Bridges for different VLANs. 2. Advanced IP Services

A major focus of the Rev B version is DHCP Relay. When the DHCP server is located in a different subnet, students must configure the ip helper-address on the router interfaces to forward local broadcast requests. This ensures that clients in remote branches can still receive dynamic addressing. 3. WLAN Configuration

In line with modern enterprise needs, the study often includes the setup of a Wireless LAN Controller (WLC). This involves: Defining SSIDs with WPA2-PSK or Enterprise authentication. Mapping SSIDs to specific VLANs.

Ensuring seamless connectivity between wired and wireless clients. Troubleshooting and Best Practices

The -Rev B- designation often indicates updated security requirements or revised IP addressing schemes compared to the original version. To succeed, students should follow these Cisco-recommended practices:

Document the Topology: Always maintain an up-to-date IP address table.

Verify Step-by-Step: Use commands like show ip interface brief, show etherchannel summary, and show vlan brief after every major configuration block.

Secure Management: Always disable unused ports and use secret passwords rather than plain-text. Recommended Study Resources

For those preparing for the 200-301 CCNA exam or completing this case study, several platforms provide guided walkthroughs and lab files:

ITExamAnswers: Offers detailed exam answers and lab solutions for SRWE modules.

Pearson: The official CCNA v7 introduction provides the conceptual foundation needed for complex case studies.

Study-CCNA: A high-quality resource for understanding the breadth of the 200-301 curriculum, including wireless and security concepts.

Are there specific Packet Tracer instructions or configuration commands from the Case Study -Rev B- you would like me to explain further?

The CCNA-2 v7.0 Case Study (Rev B) acts as a capstone project for the Switching, Routing, and Wireless Essentials (SRWE) course, requiring the integration of VLANs, STP, security, and routing for the C.I.S. Co. expansion. The project necessitates configuring IPv4/IPv6, EtherChannel, and wireless LAN controllers, commonly documented in resources available on sites like Course Hero and Scribd.

Solved CCNA-2v7.0 Case Study (Rev B) Static Routes, VLANs

CCNA-2 v7.0 Case Study (Rev B) focuses on the "Switching, Routing, and Wireless Essentials" (SRWE) curriculum. It typically centers on a scenario where the Carl I. Samson Company (C.I.S. Co) in Maine acquires a firm called "Big-Corp" with branches in ITExamAnswers

The primary objective is to implement a unified network using static routing , and various Layer 2 security Key Case Study Components

The assignment is generally divided into phases that mirror the SRWE course modules: Phase I: IP Addressing and VLANs IPv4 & IPv6 Design

: Subnetting both protocols to accommodate multiple locations. Inter-VLAN Routing ccna-2v7.0 case study -rev b-

: Implementing router-on-a-stick or SVI-based routing to allow communication between different departmental VLANs. Phase II: Infrastructure Configuration EtherChannel

: Configuring link aggregation (LACP) between switches to increase bandwidth and provide redundancy. Spanning Tree (STP)

: Ensuring a loop-free topology while maintaining redundant paths. DHCP Services

: Configuring a router or dedicated server to provide dynamic addressing for hosts. Phase III: Security and Wireless Switch Security : Applying Port Security DHCP Snooping BPDU Guard to mitigate common Layer 2 attacks. Wireless LAN (WLAN)

: Setting up basic wireless access, often using WPA2-PSK for security. SSH Management

: Securing remote access by disabling Telnet and enabling SSH with local user authentication. ITExamAnswers Implementation Checklist Description Initial Settings

Hostnames, passwords (secret, console, vty), and banner MOTD. VLAN Creation Assigning specific IDs and names; assigning access ports.

Configuring 802.1Q trunks and matching native VLANs on both ends. Static Routing

Defining routes to internal networks and a default route to the ISP. Verification commands (e.g., show ip route show ip int brief show etherchannel summary ) to confirm connectivity.

In the CCNA 2 v7.0 Case Study - Rev B, a particularly interesting feature is the complex implementation of Floating Static Routes integrated with First Hop Redundancy Protocols (FHRP).

This scenario challenges you to move beyond basic static routing by configuring a secondary backup path that only appears in the routing table when the primary link fails. It specifically tests your ability to ensure high availability in a small-to-medium enterprise network. Key Technical Highlights

Floating Static Routes with IP SLA: This feature requires configuring an IP Service Level Agreement (SLA) to monitor the primary link's health. If the SLA probe fails, the floating static route—configured with a higher administrative distance—automatically takes over.

HSRP (Hot Standby Router Protocol) Integration: The case study often requires coordinating these floating routes with HSRP to provide a redundant gateway for end devices, ensuring that even if a router or link fails, the user traffic seamlessly transitions to the backup path.

Inter-VLAN Routing and Security: You must manage data flow between different VLANs while simultaneously applying Access Control Lists (ACLs) to secure the perimeter and internal segments.

Dynamic vs. Static Comparison: The case study forces a practical comparison between manual static route management and the automated discovery provided by dynamic protocols like OSPFv2, highlighting why certain environments might prefer the lower overhead of static routes despite their lack of scalability.

CCNA-2 v7.0 Case Study -Rev B- a comprehensive practical assessment within the Switching, Routing, and Wireless Essentials (SRWE)

. It simulates a real-world scenario where a company (often identified as the Carl I. Samson Company or C.I.S. Co) has acquired another business with multiple locations, requiring a unified, secure network infrastructure. Core Objectives & Scenario

The assessment focuses on designing and implementing a multi-site network (e.g., Bangor, Phoenix, and Chicago) using static routing IPv4 and IPv6 addressing. Key technical areas covered include: Layer 2 Security & Redundancy:

Configuring VLANs, Trunking, Spanning Tree Protocol (STP), and EtherChannel. IP Services:

Implementing DHCPv4/DHCPv6 and configuring wireless settings for remote or home office segments. Routing Operations:

Establishing connectivity through static and default routes, including floating static routes for redundancy. Network Security:

Hardening devices with SSH, port security, and encrypted passwords. ITExamAnswers Implementation Phases 1. Physical & Basic Configuration

Devices must be properly placed in the equipment rack and connected via appropriate cabling. Hostname & Banners: Assign unique names (e.g., ) and configure "Message of the Day" (MOTD) banners. Management Security:

Disable IP domain lookups, encrypt all plain-text passwords using service password encryption , and set a minimum password length. SSH Access:

Generate RSA keys (1024-bit modulus), configure local user databases, and enable SSH on VTY lines for secure remote management. Course Hero 2. VLANs and Inter-VLAN Routing Segmentation:

Create and name VLANs according to the provided addressing table.

Configure 802.1Q trunks between switches, ensuring the native VLAN matches on both ends (often VLAN 77). Router-on-a-Stick:

Configure sub-interfaces on the central router to act as the default gateway for each VLAN. ITExamAnswers 3. Static Routing & Redundancy IPv4 & IPv6 Static Routes:

Manually define paths between site summaries (e.g., Phoenix and Chicago summaries) using exit interfaces or next-hop addresses. Default Routes:

Configure a "gateway of last resort" (0.0.0.0/0 or ::/0) pointing toward the ISP or Border Router. Floating Static Routes: Create backup paths by assigning a higher administrative distance (e.g., >90 for EIGRP backups) to the static route. 4. Dynamic Addressing (DHCP) Exclusions:

Reserve specific IP ranges (e.g., .1 to .15) for static assignments to ensure they are not handed out by the DHCP server. Pool Configuration:

Create pools with defined network ranges, default gateways, and DNS server addresses. DHCP Relay: ip helper-address

command on SVIs or sub-interfaces to forward DHCP requests to a central server. ITExamAnswers 5. Switch & Wireless Security

The air in the Evergreen Network Operations Center (NOC) was thick with the hum of server fans and the smell of slightly over-steeped coffee.

, a junior network engineer, stared at the printed packet on his desk: "CCNA-2v7.0 Case Study -Rev B-"

. This wasn't just a lab; it was the final blueprint for the Oakhaven University

campus expansion, and the "Rev B" meant the stakes—and the complexity—had just been raised. 1. The Challenge: A Network Divided

Oakhaven was growing. The mandate was clear: connect the new Science Wing Student Union to the existing Main Campus

core. But there were complications. The Dean insisted on total isolation for the research data, while the Student Union needed open Wi-Fi that wouldn't bog down the registrar’s office. Alex looked at the topology. It was a classic "Rev B" mess: VLANs 10, 20, and 99 were already saturated. The new wing required DHCP relay because the central server was three hops away. Inter-VLAN routing had to be handled by a new Layer 3 switch , replacing the aging "Router-on-a-Stick" setup. 2. The Implementation: Trunking and Tensions

"Alright, let's light it up," Alex muttered, fingers flying across the mechanical keyboard. First came the trunks. He configured the 802.1Q encapsulation

, ensuring the native VLANs matched across all switches to avoid the dreaded CDP mismatch errors. He watched the console amber lights turn to a steady, rhythmic green. But then, the Science Wing went dark. "STP," Alex realized. The Spanning Tree Protocol

had detected a loop in the redundant links he'd just patched in. Because he hadn't set the Bridge Priority

, the oldest, slowest switch in the basement had elected itself the "Root Bridge," bottlenecking the entire 10Gbps fiber backbone. With a few commands— spanning-tree vlan 1-100 root primary

—he reclaimed control, forcing the core switch to take its rightful place at the center of the universe. 3. The Security Breach Case Study: Company Background Acme Inc

Just as the "Rev B" requirements dictated, Alex had to implement Port Security

. He restricted the Science Wing wall jacks to a single "Sticky" MAC address. Suddenly, an alert flashed: Security Violation on FastEthernet 0/24

A researcher had tried to plug in a rogue wireless access point to get better signal for his tablet. The port had instantly Error-Disabled

. Alex didn't just reset it; he used it as a "teachable moment" about the importance of the Access Control Lists (ACLs)

he was currently writing to keep the research data behind a virtual fortress. 4. The Final Ping By 2:00 AM, the last piece of the Case Study was in place: Static Routing for the backup link and for the primary.

Alex typed the command that every engineer holds their breath for: ping 192.168.10.1

The exclamation points marched across the screen. Success. The Science Wing could talk to the Data Center; the Student Union was isolated but online; and the "Rev B" revisions were fully satisfied. He saved the configuration— copy run start

—and listened to the hum of the NOC, which now sounded a lot less like a threat and a lot more like a job well done. of this case study, such as DHCP configuration VLAN routing

The CCNA-2 v7.0 Case Study (Rev B) involves configuring a merged network for the "Carl I. Samson Company (C.I.S. Co)" following its acquisition of "Big-Corp". The network spans locations in Bangor, Phoenix, and Chicago and requires the implementation of dual-stack IPv4/IPv6 addressing, static routing, and Layer 2 security. 1. Design the Addressing Scheme

You must use Variable Length Subnet Masking (VLSM) to design both IPv4 and IPv6 schemes.

IPv4: Subnet the provided LAN network into sizes that fit the specific host requirements for each branch (Bangor, Phoenix, Chicago).

IPv6: Implement a global unicast addressing scheme. Ensure every router interface and host is configured for dual-stacking (both versions running simultaneously). 2. Configure VLANs and Trunking

Organize the network into logical segments to manage broadcast domains and security.

VLAN Creation: Create and name VLANs on all switches as specified in the case study documentation.

Trunking: Configure ports connecting switches (and switches to routers for Router-on-a-Stick) as 802.1Q trunks.

Inter-VLAN Routing: On the Main Router or Multilayer Switch (MLS), configure sub-interfaces (for Router-on-a-Stick) or Switched Virtual Interfaces (SVIs) to allow communication between different VLANs. 3. Implement Layer 2 Security Secure the switch access layer against common attacks.

Switchport Security: Enable switchport port-security on access ports. Set a maximum number of MAC addresses (typically 1 or 2) and use violation restrict or shutdown.

Unused Ports: Disable all unused ports with the shutdown command and move them to a "Black Hole" VLAN (e.g., VLAN 999). 4. Configure DHCP and Wireless Enable automatic addressing and wireless connectivity.

DHCP Server: Configure R1 or a central server to provide IPv4/IPv6 leases. Use ip dhcp excluded-address to protect static IPs like gateways.

Wireless LAN (WLAN): Set up the Home Router and Access Points with specific SSIDs and WPA2 security. Ensure wireless clients can successfully obtain IP addresses from the DHCP server. 5. Establish Connectivity with Static Routes

Since this revision explicitly calls for static routing, you must manually define the paths between Bangor, Phoenix, and Chicago.

The CCNA 2 v7.0 (Switching, Routing, and Wireless Essentials) curriculum focuses on the architecture, components, and operations of routers and switches in small networks. Developing a case study for this specific version typically involves a scenario where a business must expand its network infrastructure to support multiple LANs and secure wireless access. Scenario Overview

You are a network administrator for a company called "E-MAGINE". The company is merging with another entity and expanding to a Wide Area Network (WAN) with multiple locations. Your goal is to design and implement a network that ensures inter-VLAN communication, secure access, and efficient routing. Core Case Study Components

A standard "Rev B" (Revision B) case study for CCNA 2 v7.0 should include the following modules: 1. VLAN and Inter-VLAN Routing

Objective: Segment the network for different departments (e.g., Sales, HR, IT). Requirements: Assign specific VLAN IDs and names (e.g., VLAN 10 - Sales). Configure 802.1Q trunking between switches.

Implement Router-on-a-Stick or Layer 3 Switching for Inter-VLAN routing. 2. Redundancy and STP Objective: Prevent loops in a multi-switch environment. Requirements:

Configure Spanning Tree Protocol (STP) to ensure a single loop-free path.

Optimize STP by designating a Root Bridge for specific VLANs.

Configure EtherChannel (Link Aggregation) to increase bandwidth and provide redundancy between switches. 3. Routing Concepts and Configuration Courses and training - PJATK GDAŃSK

Case Study Overview

The case study is set in a fictional company called "ABC Corporation," which has two main offices, one in New York and one in Chicago. The company has a total of 50 employees, with 20 employees at the New York office and 30 employees at the Chicago office. The company's network requirements are as follows:

  • Provide network connectivity between the two offices
  • Support 50 employees with IP addresses
  • Implement a network security plan
  • Ensure network reliability and uptime

Network Topology

The network topology consists of two main sites:

  • New York Office:
    • 1 x 2960X switch
    • 1 x Cisco router ( ISR 4431/K9)
    • 10 x Employee workstations
    • 1 x Printer
  • Chicago Office:
    • 1 x 2960X switch
    • 1 x Cisco router ( ISR 4431/K9)
    • 20 x Employee workstations
    • 1 x Printer

Network Configuration

The network configuration includes:

  • IP Addressing:
    • New York Office: 10.10.10.0/24
    • Chicago Office: 10.10.20.0/24
  • VLANs:
    • VLAN 10: Employees (New York Office)
    • VLAN 20: Employees (Chicago Office)
    • VLAN 30: Management (both offices)
  • Routing:
    • OSPF routing protocol
  • Network Security:
    • Implement a firewall to block unauthorized access
    • Configure access control lists (ACLs) to restrict traffic

Implementation

The implementation phase involves the following steps:

  1. Configure the routers and switches with IP addresses and VLANs.
  2. Implement OSPF routing protocol.
  3. Configure the firewall and ACLs.
  4. Configure network services such as DHCP and DNS.

Configuration Commands

Here are some sample configuration commands:

New York Router:

enable
configure terminal
interface GigabitEthernet0/0
 ip address 10.10.10.1 255.255.255.0
 no shutdown
exit
router ospf 1
 network 10.10.10.0 0.0.0.255 area 0

Chicago Router:

enable
configure terminal
interface GigabitEthernet0/0
 ip address 10.10.20.1 255.255.255.0
 no shutdown
exit
router ospf 1
 network 10.10.20.0 0.0.0.255 area 0

Verification and Troubleshooting

The verification and troubleshooting phase involves:

  1. Verifying IP connectivity between devices.
  2. Verifying network services such as DHCP and DNS.
  3. Troubleshooting any network issues that arise.

Verification Commands

Here are some sample verification commands:

show ip int brief
show ip route
ping 10.10.20.1

The CCNA-2v7.0 Case Study (Rev B) requires configuring a multi-site network for the Carl I. Samson Company (C.I.S. Co) following an acquisition, focusing on integrating Bangor, Phoenix, and Chicago locations. The project mandates implementing IPv4/IPv6 addressing, static routing, VLANs, switchport security, and DHCP services across the infrastructure. Detailed project requirements can be found at Course Hero.

Solved CCNA-2v7.0 Case Study (Rev B) Static Routes, VLANs

CCNA 2 v7.0 Case Study - Rev B: A Comprehensive Guide

The Cisco Certified Network Associate (CCNA) certification is a highly respected credential in the IT industry, and the CCNA 2 v7.0 case study is an integral part of the certification process. In this article, we will provide a comprehensive guide to the CCNA 2 v7.0 case study - Rev B, including an overview of the case study, its objectives, and a step-by-step walkthrough of the solution.

What is CCNA 2 v7.0 Case Study - Rev B?

The CCNA 2 v7.0 case study - Rev B is a real-world scenario-based assessment that tests a candidate's skills and knowledge in designing, implementing, and troubleshooting a network. The case study is part of the CCNA 2 v7.0 curriculum, which focuses on switching, routing, and wireless technologies.

The case study - Rev B is a revised version of the original case study, which was updated to reflect the latest network technologies and industry trends. The case study is designed to evaluate a candidate's ability to apply theoretical knowledge to practical scenarios, making it an essential component of the CCNA certification process.

Objectives of CCNA 2 v7.0 Case Study - Rev B

The primary objectives of the CCNA 2 v7.0 case study - Rev B are:

  1. Design a network topology: Candidates are required to design a network topology that meets the requirements of a fictional company.
  2. Configure network devices: Candidates must configure network devices, including switches, routers, and wireless access points.
  3. Troubleshoot network issues: Candidates are presented with network issues and must troubleshoot them to resolve the problems.

Step-by-Step Walkthrough of CCNA 2 v7.0 Case Study - Rev B

The following is a step-by-step walkthrough of the CCNA 2 v7.0 case study - Rev B:

Step 1: Understand the Company Requirements

The case study presents a fictional company, HQ and two branch offices, Branch1 and Branch2. The company requires a network design that connects all three locations, provides Internet access, and supports wireless connectivity.

Step 2: Design the Network Topology

Candidates must design a network topology that meets the company's requirements. The topology should include:

  • HQ: 2 switches, 1 router, and 1 wireless access point
  • Branch1: 1 switch, 1 router, and 1 wireless access point
  • Branch2: 1 switch, 1 router, and 1 wireless access point

Step 3: Configure Network Devices

Candidates must configure the network devices, including:

  • Switches: Configure VLANs, trunking, and Spanning Tree Protocol (STP)
  • Routers: Configure routing protocols, including OSPF and EIGRP
  • Wireless access points: Configure wireless settings, including SSID, channel, and encryption

Step 4: Troubleshoot Network Issues

The case study presents several network issues that candidates must troubleshoot, including:

  • Connectivity issues between HQ and Branch1
  • Wireless connectivity issues at Branch2
  • Routing issues between HQ and Branch2

Solution to CCNA 2 v7.0 Case Study - Rev B

The following is a sample solution to the CCNA 2 v7.0 case study - Rev B:

Network Topology

The network topology is designed as follows:

  • HQ: 2 switches (SW1 and SW2), 1 router (R1), and 1 wireless access point (AP1)
  • Branch1: 1 switch (SW3), 1 router (R2), and 1 wireless access point (AP2)
  • Branch2: 1 switch (SW4), 1 router (R3), and 1 wireless access point (AP3)

Configurations

The configurations for each device are as follows:

  • Switches:
    • SW1 (HQ): Configure VLANs 10, 20, and 30, trunking, and STP
    • SW2 (HQ): Configure VLANs 10, 20, and 30, trunking, and STP
    • SW3 (Branch1): Configure VLANs 10 and 20
    • SW4 (Branch2): Configure VLANs 10 and 30
  • Routers:
    • R1 (HQ): Configure OSPF and EIGRP routing protocols
    • R2 (Branch1): Configure OSPF and EIGRP routing protocols
    • R3 (Branch2): Configure OSPF and EIGRP routing protocols
  • Wireless access points:
    • AP1 (HQ): Configure SSID, channel, and encryption
    • AP2 (Branch1): Configure SSID, channel, and encryption
    • AP3 (Branch2): Configure SSID, channel, and encryption

Troubleshooting

The network issues are troubleshooted as follows:

  • Connectivity issues between HQ and Branch1: Check the routing table on R1 and R2, and verify that the OSPF and EIGRP routing protocols are configured correctly.
  • Wireless connectivity issues at Branch2: Check the wireless settings on AP3 and verify that the SSID, channel, and encryption are configured correctly.
  • Routing issues between HQ and Branch2: Check the routing table on R1 and R3, and verify that the OSPF and EIGRP routing protocols are configured correctly.

Conclusion

The CCNA 2 v7.0 case study - Rev B is a comprehensive assessment that tests a candidate's skills and knowledge in designing, implementing, and troubleshooting a network. By following the step-by-step walkthrough and solution provided in this article, candidates can prepare themselves for the case study and achieve success in their CCNA certification journey.

Additional Tips and Recommendations

  • Practice, practice, practice: The CCNA 2 v7.0 case study - Rev B requires hands-on experience and practice. Candidates should practice configuring and troubleshooting networks using Cisco equipment or simulators.
  • Understand the exam format: The CCNA 2 v7.0 case study - Rev B is a simulation-based exam. Candidates should understand the exam format and practice using the simulation tools provided by Cisco.
  • Review the CCNA 2 v7.0 curriculum: The CCNA 2 v7.0 case study - Rev B is based on the CCNA 2 v7.0 curriculum. Candidates should review the curriculum and ensure they understand the concepts and technologies covered.

By following these tips and recommendations, candidates can achieve success in their CCNA 2 v7.0 case study - Rev B and take a significant step towards achieving their CCNA certification.

The CCNA-2v7.0 Case Study (Rev B), often associated with Packet Tracer activity 14.6.1, is a comprehensive, hands-on lab designed to test practical application of CCNA 2 (Switching, Routing, and Wireless Essentials - SRWE) concepts . It requires learners to implement a secure, multi-site network for the "Carl I. Samson Company" (C.I.S. Co), involving Phoenix, Chicago, and Bangor locations . Core Components & Objectives

Topology: Involves complex routing between multiple geographical locations (Bangor, Chicago, Phoenix) . IP Addressing: Subnetting the 10.10.64.0/21 range .

VLANs & Trunking: Setting up VLANs, Access Ports, and Trunk Ports .

Static Routing: Implementing IPv4 and IPv6 static routes, including potential floating static routes .

Switch Security: Configuring DHCP Snooping, Port Security, and Dynamic ARP Inspection (DAI) .

Wireless: Configuring a Wireless LAN Controller (WLC) and Access Points .

Spanning Tree Protocol (STP): Configuring and optimizing STP for redundancy . Detailed Review CCNA-1 Case-Study-7.0 -.docx - Course Hero

3.2 VLAN and Trunking (Switches)

  • On S1:
    • VLAN 10 – Sales, VLAN 20 – Engineering
    • Assign ports: Fa0/1 to VLAN 10, Fa0/2 to VLAN 20
    • Trunk port (to router or L3 switch): switchport mode trunk
  • On S2: similarly configured for other end devices.

4. DHCP for Dynamic IP Allocation

Manually assigning IP addresses to every end device is impractical. Thus, the case study requires configuring a DHCP server, often on the router. For each VLAN, a DHCP pool is defined:

ip dhcp pool MGMT_POOL
 network 192.168.10.0 255.255.255.0
 default-router 192.168.10.1
 dns-server 8.8.8.8

IP addresses are excluded for static devices (e.g., the default gateway and management station) using ip dhcp excluded-address. Verification on a client PC involves using ipconfig (or show ip dhcp binding on the router) to ensure leases are obtained correctly.

Network Topology (logical)

  • Router HQ (R1) — serial WAN — Router Branch (R2)
  • Branch switch (S1) with 3 VLANs: VLAN 10 (Sales), VLAN 20 (Engineering), VLAN 30 (HR)
  • Router-on-a-stick: subinterfaces on R2 for VLAN routing
  • Server farm: 1 Application Server (IP-managed), 1 Printer (shared)
  • DHCP server function is provided by R2 (or a dedicated server per instructor note)
  • Internet edge handled via HQ router with NAT for branch traffic as appropriate

Step 5.3: PAT Overload (NAT)

To let both Employee and Guest VLANs reach the internet:

R1(config)# access-list 101 permit ip 192.168.10.0 0.0.0.255 any
R1(config)# access-list 101 permit ip 192.168.20.0 0.0.0.255 any
R1(config)# ip nat inside source list 101 interface g0/0/0 overload
R1(config)# interface g0/0/0
R1(config-if)# ip nat outside
R1(config)# interface g0/0/1.10
R1(config-if)# ip nat inside
R1(config)# interface g0/0/1.20
R1(config-if)# ip nat inside

Verification: From PC-B (Guest), ping 8.8.8.8. Use show ip nat translations to see dynamic entries.