Set primary/secondary root for different VLANs (load balancing).
spanning-tree vlan 10 root primary
spanning-tree vlan 20 root secondary
This assumes a typical scenario where you are given a network topology with multiple routers, switches, VLANs, static/dynamic routing, ACLs, NAT, and DHCP.
Adjust the IP addressing and device names to match your specific case study details.
Do not proceed until you draw the topology from the case study document. Label all interfaces, IP networks, and VLAN IDs. This visual map is your single source of truth.
The modern enterprise relies on networks that are not only functional but also scalable, secure, and efficiently segmented. The CCNA 2 v7.0 Case Study – Rev B provides a practical scenario where a network engineer must design, configure, and verify a multi-switch, multi-router environment. This essay outlines the key implementation tasks, including VLAN segmentation, trunking, inter-VLAN routing, DHCP configuration, and remote management security, while highlighting best practices and verification strategies.
One of the most time-consuming parts of the Rev B case study is configuring DHCP for all VLANs. The case study usually prohibits using a separate server; R1 or R2 must act as the DHCP server.
If you are currently working on this case study, here is a breakdown of the typical tasks involved in Rev B so you can verify your work:
1. Addressing Table Design
2. VLAN Configuration
3. Inter-VLAN Routing
4. Services (DHCP/SSH)
5. Verification
Note on Versions:
The CCNA-2v7.0 Case Study (Rev B) is a comprehensive practical assessment within the Cisco Networking Academy "Switching, Routing, and Wireless Essentials" (SRWE) curriculum. It simulates a real-world merger scenario involving the Carl I. Samson Company (C.I.S. Co), which has expanded its Bangor, Maine headquarters by acquiring "Big-Corp" offices in Phoenix and Chicago.
This case study challenges students to integrate multiple core networking concepts into a single, cohesive infrastructure using both IPv4 and IPv6. Core Objectives and Requirements ccna-2v7.0 case study -rev b-
The Rev B assessment focuses on several key technological pillars of the SRWE course:
Static Routing: Implementing primary and backup (floating) static routes for both IPv4 and IPv6 to ensure connectivity between geographic sites.
VLANs and Inter-VLAN Routing: Organizing local traffic into segments and configuring "Router-on-a-Stick" or Layer 3 switch SVIs for communication.
Switch Security: Applying best practices like port security, disabling unused ports, and configuring encrypted management access via SSH.
DHCP Services: Configuring routers to act as DHCPv4 and DHCPv6 servers to automate host addressing.
WLAN and Redundancy: Setting up Wireless LANs and ensuring network stability through EtherChannel and Spanning Tree Protocol (STP). Phase-by-Phase Implementation 1. IP Addressing and VLAN Design
In the initial phase, you must develop an addressing scheme based on specific user requirements for each site.
Phoenix (PHX): Typically requires sub-interfacing on the Phoenix router to support multiple VLANs (e.g., VLAN 120).
Chicago (CHG): Often acts as a central hub for specific services like DHCP.
Bangor (BAN): The headquarters router, frequently used to handle IPv6 DHCP pools (e.g., "DHCP-DNS"). 2. Basic Device Configuration
Security is a priority from the start. On all routers and switches (like CHG-RTR, PHX-SW-1, and BAN-RTR), you must:
Secure the IOS: Encrypt all passwords, set a minimum password length (often 10 characters), and disable IP domain lookups.
Management Access: Configure a domain name (e.g., cisco.com), generate 1024-bit RSA keys, and enable SSH version 2 on VTY lines.
Brute-Force Protection: Use commands to block login attempts for a specified period (e.g., 1 minute) after 3 failures in 60 seconds. 3. Advanced Layer 2 and Layer 3 Features This assumes a typical scenario where you are
The core of the "Rev B" study involves complex connectivity tasks: Chegghttps://www.chegg.com
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
: 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 Do not proceed until you draw the topology
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.
If you want, I can produce:
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.
It looks like you’re looking for a proper guide for the CCNA v7.0 (2.7.0) Case Study – Revision B.
First, a quick clarification:
The official Cisco NetAcad curriculum for CCNA 2 v7.0 (Switching, Routing, and Wireless Essentials) includes several Case Studies depending on the instructor or region — but the most common “Rev B” case study focuses on multi-switch configuration, VLANs, trunking, STP, EtherChannel, and inter-VLAN routing, often using Packet Tracer.
Below is a structured guide to complete the standard CCNA 2 v7.0 Revision B Case Study successfully.
Completing the configuration is only half the battle. The CCNA-2v7.0 Case Study -Rev B- includes specific verification questions (e.g., "Can PC-A ping the server?"). You must demonstrate functional connectivity.
Use this checklist before submitting: