Layer 2 refers to the Data Link Layer in the OSI model. It handles MAC addresses, switching, and frame forwarding within a local network segment.
A VLAN is a logical separation within a physical switch.
Devices in different VLANs cannot communicate with each other without a router or Layer 3 switch.
To segregate departments (e.g., HR, Finance, IT).
Improve network performance by reducing broadcast domains.
Enhance security (one department can’t see another’s traffic).
vlan 10
name Finance
!
interface FastEthernet0/1
switchport mode access
switchport access vlan 10
Trunking allows a switch port to carry traffic from multiple VLANs.
Required for:
Switch-to-switch connections
Router-on-a-stick (router doing inter-VLAN routing)
Links to virtualization hosts
Adds a VLAN ID to the Ethernet frame so the receiving device knows which VLAN the frame belongs to.
Native VLAN: untagged VLAN on the trunk (default is VLAN 1).
interface GigabitEthernet0/1
switchport trunk encapsulation dot1q
switchport mode trunk
switchport trunk allowed vlan 10,20,30
This trunk carries VLANs 10, 20, and 30.
STP prevents Layer 2 loops, which can crash a network by endlessly forwarding broadcast frames.
| Version | IEEE Standard | Notes |
|---|---|---|
| STP | 802.1D | Original, slow convergence |
| RSTP | 802.1w | Fast convergence |
| MSTP | 802.1s | Supports multiple VLANs in one instance |
Root Bridge: The “boss” switch — elected based on lowest bridge ID (priority + MAC)
Root Port (RP): Best path to the Root Bridge (one per switch)
Designated Port (DP): Forwarding port for each segment
Blocking Port: Prevents loops
Lower priority = more likely to be Root.
If two switches are connected with multiple cables, STP blocks one link to avoid a loop. If the active link fails, the blocked one becomes active — keeping the network alive.
EtherChannel groups multiple physical links between two devices into one logical link.
Redundancy: If one link fails, others keep running.
Load Balancing: Traffic can be distributed across links.
| Protocol | Standard? | Notes |
|---|---|---|
| PAgP | Cisco proprietary | Both sides must be Cisco |
| LACP | IEEE 802.3ad | Open standard, widely used |
PAgP: desirable / auto
LACP: active / passive
interface range g0/1 - 2
channel-group 1 mode active
!
interface port-channel 1
switchport mode trunk
Used to limit access to switch ports based on MAC addresses. Prevents:
Unauthorized devices
MAC flooding attacks
| Mode | Action on Violation |
|---|---|
| Protect | Drops traffic silently |
| Restrict | Drops + logs |
| Shutdown | Disables port (default mode) |
interface FastEthernet0/1
switchport mode access
switchport access vlan 10
switchport port-security
switchport port-security maximum 1
switchport port-security violation restrict
switchport port-security mac-address sticky
| Feature | Purpose | Common Use |
|---|---|---|
| VLAN | Logical segmentation | Separate departments |
| Trunking | Carry multiple VLANs | Switch-switch, router connections |
| STP | Prevent loops | Redundant links |
| EtherChannel | Link aggregation | Redundancy + speed |
| Port Security | MAC filtering | Prevent rogue devices |
Layer 3 (Network Layer) is responsible for IP addressing and routing — deciding how data travels between networks. Here, we learn both manual and dynamic routing techniques.
A manual routing method where the administrator manually defines routes on routers.
Small networks
Backup links
Route summarization
ip route 192.168.1.0 255.255.255.0 10.1.1.1
This tells the router:
“To reach 192.168.1.0/24, send packets to 10.1.1.1”
Simple
No CPU/memory overhead
Predictable
Doesn’t adapt to network changes
Manual effort increases as network grows
Routers learn and exchange routes automatically using a routing protocol.
Link-state protocol
Uses Dijkstra's SPF algorithm
Fast convergence
Organizes the network into areas
Router ID: Highest IP address or manually set
LSAs (Link-State Advertisements): Share info about links
Area 0 (Backbone Area): All areas must connect to it
router ospf 1
router-id 1.1.1.1
network 192.168.1.0 0.0.0.255 area 0
Cisco proprietary (now open standard)
Uses the DUAL algorithm
Fast convergence
Supports IPv4 and IPv6
Feasible Distance (FD): Best known distance to a destination
Reported Distance (RD): Distance reported by a neighbor
Successor: Best path
Feasible Successor: Backup path
router eigrp 100
network 10.0.0.0
Path-vector protocol
Used between different organizations (ISP to ISP, company to ISP)
Very scalable, but complex
AS (Autonomous System): Group of routers under a single admin
AS-Path: List of ASes the route has passed through
Route Reflectors: Reduce iBGP full-mesh requirement
eBGP vs iBGP:
eBGP = between different ASes
iBGP = inside one AS
router bgp 65001
neighbor 192.0.2.2 remote-as 65002
network 10.0.0.0 mask 255.255.255.0
To prevent a single point of failure at the default gateway, FHRPs provide gateway redundancy.
| Protocol | Standard | Notes |
|---|---|---|
| HSRP | Cisco | Active/Standby |
| VRRP | Open | Master/Backup |
| GLBP | Cisco | All routers active, load balancing |
If your default gateway router fails, another router takes over without interrupting service.
Redistribution allows routes learned by one protocol to be shared with another protocol.
You run OSPF in one area and EIGRP in another
Merging networks during an acquisition
Connecting to legacy networks
router ospf 1
redistribute eigrp 100 metric 1000
This command tells OSPF to accept routes from EIGRP with a given metric.
| Concept | Description | Use Case |
|---|---|---|
| Static Routing | Manual path configuration | Small or stable networks |
| OSPF | Link-state protocol | Medium to large enterprises |
| EIGRP | Advanced distance-vector | Cisco-heavy environments |
| BGP | Internet-scale routing | ISP, multi-organization |
| FHRP | Redundant default gateway | Prevent single point of failure |
| Redistribution | Share routes across protocols | Network merging or transitions |
Wireless networking (Wi-Fi) extends the network to devices like laptops, phones, tablets, and IoT devices without needing physical cabling. Understanding wireless architecture is key to managing performance, security, and mobility.
Wireless networks can be deployed in several architectures, depending on size, scalability, and management needs.
Each AP operates independently.
All configurations, updates, and monitoring must be done manually on each AP.
Best for small environments (e.g., a single office or classroom).
Pros:
Simple to deploy
No controller needed
Cons:
Difficult to scale
No centralized management
Like giving each teacher their own whiteboard, with no shared lesson plan.
Access Points are “lightweight” — they offload their intelligence to a central Wireless LAN Controller (WLC).
The controller handles:
Authentication
Roaming
Channel assignment
Configuration updates
Pros:
Centralized control
Easier scaling
Better monitoring and security
Cons:
Like a school principal coordinating all classrooms to follow the same rules and curriculum.
APs are managed via the cloud using a dashboard interface.
No on-site controller — policies are pushed from the cloud.
Ideal for distributed networks (e.g., retail stores, campuses).
Pros:
Easy to deploy and manage remotely
Built-in analytics and security
Scales globally
Cons:
Dependent on internet connectivity
Subscription model may increase cost over time
Like a virtual principal managing dozens of remote schools through a web portal.
CAPWAP is the protocol used between lightweight APs and WLCs.
Control messages (e.g., configuration, firmware) and data messages (client traffic) are sent via separate tunnels.
Supports encryption and authentication.
The AP handles only the real-time, low-level radio functions (like beaconing).
The WLC handles:
Authentication
Security policies
QoS
Client roaming decisions
Think of CAPWAP like an invisible link that allows the WLC to “remote control” all APs.
The name of the wireless network (e.g., “Office-WiFi”).
Can be broadcast or hidden.
| Method | Description |
|---|---|
| Open | No authentication |
| PSK (Pre-Shared Key) | Password shared among users (e.g., WPA2-PSK) |
| 802.1X | Enterprise-level security using RADIUS for dynamic credentials |
| Standard | Security Level | Notes |
|---|---|---|
| WPA2 | Strong | Still widely used |
| WPA3 | Stronger | Supports 192-bit encryption and improved handshake |
Use WPA2/WPA3 with 802.1X for secure enterprise environments.
Avoid open or WEP networks.
Segment guest Wi-Fi with separate SSIDs or VLANs.
Roaming lets a wireless client move between APs without losing its network connection.
The IP address stays the same.
Client moves between APs on the same VLAN/subnet.
Seamless and fast.
The client moves between APs on different VLANs/subnets.
Requires additional handling (e.g., tunneling to anchor controller).
Used in large or multi-site deployments.
Speeds up authentication when clients roam.
Essential for VoIP over Wi-Fi, real-time video, or mobile scanners in warehouses.
| Feature | Function | Benefit |
|---|---|---|
| Autonomous AP | Standalone APs | Simple, but not scalable |
| Controller-Based | Centralized management via WLC | Scalable, policy-driven |
| Cloud-Managed | Web-based control (e.g., Meraki) | Remote, global control |
| CAPWAP | AP ⇄ WLC communication protocol | Secure, scalable control |
| SSID + Auth | Define Wi-Fi access | Secure, policy-enforced access |
| Roaming | Move between APs | Mobility without disruption |
Network services are the supporting mechanisms that help devices get IP addresses, sync time, report health, and log events. These services ensure smooth operation, diagnostics, and automation in a network.
DHCP automatically assigns:
IP address
Subnet mask
Default gateway
DNS servers
Lease time
to clients that join the network — reducing manual configuration errors.
DISCOVER – Client broadcasts to find a DHCP server.
OFFER – Server replies with an IP offer.
REQUEST – Client requests the offered IP.
ACK – Server confirms assignment.
ip dhcp pool OFFICE
network 192.168.1.0 255.255.255.0
default-router 192.168.1.1
dns-server 8.8.8.8
lease 7
Used when DHCP clients and servers are in different VLANs or subnets.
interface VLAN 10
ip helper-address 192.168.100.10
Option 3: Default gateway
Option 6: DNS server
Option 66: TFTP server for VoIP phones
Accurate log timestamps
Proper certificate validation
Coordinated automation and monitoring
Uses stratum levels (lower = closer to the authoritative time source).
Stratum 0 = Atomic clock
Stratum 1 = Directly connected to Stratum 0
Stratum 2+ = Clients syncing from higher levels
ntp server 192.168.1.1
Use multiple sources for redundancy
Monitor time drift regularly
Secure with authentication if needed
SNMP is a protocol for monitoring and managing network devices. It lets a central NMS (Network Management System) query devices for:
Uptime
Interface status
CPU/Memory usage
| Version | Security | Notes |
|---|---|---|
| v1 | None | Obsolete |
| v2c | Community string (plaintext) | Still used |
| v3 | Auth + encryption | Preferred in secure environments |
Read-only: allows polling
Read-write: allows configuration changes
Devices can send alerts to the NMS (e.g., interface down).
Unlike polling, traps are event-driven.
snmp-server community public RO
snmp-server host 192.168.1.100 version 2c public
Syslog is a logging protocol that allows network devices to send event messages to a centralized Syslog server.
| Level | Meaning |
|---|---|
| 0 | Emergencies |
| 1 | Alerts |
| 2 | Critical |
| 3 | Errors |
| 4 | Warnings |
| 5 | Notifications |
| 6 | Informational |
| 7 | Debugging |
logging host 192.168.1.50
logging trap warnings
| Service | Purpose | Key Configuration |
|---|---|---|
| DHCP | IP address assignment | ip dhcp pool, ip helper-address |
| NTP | Time synchronization | ntp server <IP> |
| SNMP | Monitoring/management | snmp-server community |
| Syslog | Event logging | logging host, logging trap |
IP services enhance the basic functionality of IP networking. These include address translation, IPv6 support, traffic prioritization (QoS), and more — all vital for a scalable, performant, and secure network.
NAT allows private IP addresses (e.g., 192.168.x.x) to communicate with the public internet by translating them to a public IP address.
ip nat inside source static 192.168.1.10 203.0.113.10
ip nat pool PUBLIC_POOL 203.0.113.10 203.0.113.20 netmask 255.255.255.0
ip nat inside source list 1 pool PUBLIC_POOL
ip nat inside source list 1 interface GigabitEthernet0/0 overload
interface GigabitEthernet0/1
ip nat inside
!
interface GigabitEthernet0/0
ip nat outside
IPv6 solves the IPv4 exhaustion problem by using 128-bit addresses (vs. 32-bit in IPv4).
| Type | Purpose |
|---|---|
| Link-local | Always starts with FE80::; used on the same link only |
| Global unicast | Routable on the internet (like IPv4 public IPs) |
| Multicast | One-to-many communication |
| Anycast | Sent to nearest member of a group |
interface GigabitEthernet0/0
ipv6 address 2001:DB8:1::1/64
ipv6 enable
!
ipv6 unicast-routing
OSPFv3: OSPF for IPv6
EIGRP for IPv6: EIGRP adapted for IPv6 networks
Running IPv4 and IPv6 simultaneously on the same network — useful during transition phases.
QoS ensures that important traffic (like voice or video) is prioritized over less critical data (like file downloads).
Identify traffic and mark it for special treatment.
Layer 2: Class of Service (CoS)
Layer 3: DSCP (Differentiated Services Code Point)
Determines how packets are scheduled for transmission.
Types of queues:
FIFO (First-In-First-Out)
WFQ (Weighted Fair Queuing)
LLQ (Low-Latency Queuing) — prioritizes voice
Prevents queues from getting full.
WRED (Weighted Random Early Detection) drops less important packets when queues begin to fill.
Policing: Drops or re-marks packets exceeding a rate limit.
Shaping: Buffers excess traffic to smooth out bursts.
class-map match-any VOICE
match dscp ef
!
policy-map QOS_POLICY
class VOICE
priority 1000
!
interface GigabitEthernet0/0
service-policy output QOS_POLICY
| Feature | Purpose | Common Usage |
|---|---|---|
| Static NAT | One-to-one IP translation | Server publishing |
| PAT | Many-to-one IP translation | Internet access for LAN users |
| IPv6 | 128-bit addressing | Modern networks, IoT, scalability |
| QoS | Prioritize traffic | Voice, video, critical apps |
High availability (HA) and resiliency ensure that a network can continue operating smoothly even when hardware or links fail. These features are critical in enterprise environments where downtime is unacceptable.
Redundancy is the foundation of high availability. It ensures there is always a backup path or backup device ready to take over in case of failure.
Use dual-homed connections so that if one link fails, the second can take over.
Example:
Two switches connected by two trunk links or an EtherChannel — prevents downtime from a single cable cut.
We already covered EtherChannel earlier in Layer 2. It helps combine links for:
Load balancing
Redundancy (if one link fails, traffic continues on the others)
| Device | Redundancy Type | Purpose |
|---|---|---|
| Switches | StackWise / VSS | Logical single switch with hardware backup |
| Routers | HSRP / VRRP / GLBP | Redundant gateways |
| Firewalls | Active/Standby pairs | Seamless failover |
| Power Supplies | Dual PSU | Avoid single-point power failure |
| Supervisor Modules | Dual Sup cards | Continues operation if one fails (e.g., in chassis switches) |
| Technology | Platform | Benefit |
|---|---|---|
| VSS | Catalyst 6500/6800 | Two chassis act as one switch |
| StackWise | Catalyst 3850/9300 | Up to 9 switches managed as one unit |
Both allow for:
Single control plane
Simplified management
Failover within milliseconds
Load balancing is the process of distributing traffic across multiple links or paths to optimize performance and avoid congestion.
Done via EtherChannel — balances traffic across member interfaces using hash algorithms (source/destination MAC/IP/port).
When a router has multiple equal-cost paths to a destination, it can distribute traffic between them.
Supported by OSPF, EIGRP, BGP
Uses hashing to balance traffic
Per-packet or per-flow
router ospf 1
maximum-paths 4
Allows OSPF to use 4 equal-cost routes for load sharing.
| Mode | Behavior | Pros | Cons |
|---|---|---|---|
| Per-Flow | All packets of a session follow one path | Avoids out-of-order packets | Less balanced traffic |
| Per-Packet | Each packet can take a different path | Best load usage | May cause jitter (bad for voice/video) |
| Feature | Purpose | Example |
|---|---|---|
| Redundant Links | Prevent link failure from disrupting service | Dual uplinks |
| Redundant Devices | Hardware-level HA | Dual PSUs, routers, switches |
| VSS / StackWise | Logical chassis for switches | 2–9 switches act as one |
| ECMP | Use multiple routes | OSPF, EIGRP, BGP |
| Load Balancing | Improve performance and redundancy | EtherChannel, ECMP |
To enhance STP security and stability, Cisco implements several protection mechanisms that prevent misbehaving or unauthorized devices from affecting the Layer 2 topology.
| Feature | Purpose | Typical Use |
|---|---|---|
| BPDU Guard | Shuts down access ports that receive unexpected BPDUs | Protects against rogue switches on access ports |
| Root Guard | Prevents a port from becoming the Root Port | Ensures consistent root bridge election |
| Loop Guard | Prevents a blocking port from mistakenly becoming forwarding when BPDUs stop | Protects against unidirectional link failures |
Enable BPDU Guard on all portfast interfaces to prevent users from accidentally plugging in a switch.
Routing filters are essential for controlling the propagation of routing updates. Cisco devices use various tools depending on the protocol and use case.
| Tool | Description | Protocols |
|---|---|---|
| Prefix-list | Filter routes based on prefix/mask; supports greater-than/less-than logic | BGP, OSPF |
| Distribute-list | Restricts incoming or outgoing route advertisements | RIP, EIGRP, OSPF |
| Route-map | Advanced filtering using match/set clauses, can include ACLs, tags | BGP, OSPF, redistribution |
Use a prefix-list + route-map to control which BGP routes are allowed to be advertised to a peer.
To ensure uptime and uninterrupted wireless connectivity, Cisco WLCs support multiple High Availability (HA) architectures.
| Mode | Description | Behavior on Failover |
|---|---|---|
| SSO (Stateful Switchover) | Active and standby share state | Seamless AP and client session continuity |
| N+1 | One WLC backs up multiple others | APs must rejoin the backup WLC |
| N+N | One-to-one active/standby pairs | Fast failover, high hardware cost |
SSO is the most seamless and preferred in enterprise.
N+1 is cost-effective but with recovery delay.
IPv6 replaces many IPv4 legacy protocols with NDP, which operates using ICMPv6 messages.
| Message | Function |
|---|---|
| Router Solicitation (RS) | Host asks routers to send RA |
| Router Advertisement (RA) | Router advertises prefix, gateway, and lifetime |
| Neighbor Solicitation (NS) | Used for address resolution (like ARP) |
| Neighbor Advertisement (NA) | Response to NS |
| Redirect | Router informs host of better first-hop |
NDP provides both Layer 2 address resolution and routing discovery in IPv6 networks.
| DSCP Class | Name | Use Case |
|---|---|---|
| EF (46) | Expedited Forwarding | VoIP |
| AFxx | Assured Forwarding | Mission-critical apps |
| BE (0) | Best Effort | Default traffic |
The trust boundary defines where QoS markings are accepted.
Access ports are usually untrusted, so markings are rewritten at the switch.
Mark trusted traffic at the access switch only if you trust the endpoint device.
Understanding HSRP state transitions is a common exam topic.
Initial – Interface is down or HSRP not configured
Learn – No HSRP messages received, no virtual IP known
Listen – Knows virtual IP, no active/standby router known
Speak – Sending Hello messages, participating in election
Standby – Candidate to become active
Active – The router currently forwarding traffic for the group
Be prepared to order states or identify missing state transitions in scenario-based questions.
Multicast is a scalable solution for one-to-many communications, such as video streaming and IPTV.
| Component | Description |
|---|---|
| PIM (Protocol Independent Multicast) | Builds multicast distribution trees |
| PIM Dense Mode | Assumes receivers are everywhere; flood and prune |
| PIM Sparse Mode | Assumes receivers are few; uses Rendezvous Point |
| IGMP | Hosts join multicast groups via Layer 2 |
| RPF (Reverse Path Forwarding) | Ensures multicast packets arrive on the correct interface toward the source |
Use PIM Sparse Mode for scalable multicast networks.
RPF check prevents loops and ensures correct forwarding paths.
What causes a spanning tree topology change notification (TCN)?
A TCN occurs when a switch port transitions from blocking to forwarding or when a forwarding port goes down.
Topology change notifications inform switches that the Layer-2 topology has changed. When a change occurs, switches shorten their MAC address aging timers to quickly remove outdated forwarding entries. This process helps the network converge faster after topology modifications. However, frequent TCNs may indicate instability such as flapping links or improperly configured edge ports. In enterprise environments, enabling features like PortFast on access ports prevents unnecessary topology change events caused by endpoint devices connecting or disconnecting.
Demand Score: 86
Exam Relevance Score: 90
Which attribute does eBGP evaluate first when selecting the best path?
The weight attribute is evaluated first in Cisco implementations.
BGP uses a sequence of attributes to determine the best route. In Cisco routers, weight is the first attribute examined and it is locally significant. Routes with higher weight values are preferred. If weight is equal, the decision process moves to the next attributes such as local preference, locally originated routes, AS path length, and MED. Engineers frequently misunderstand that weight is not propagated between routers and only influences the local router’s routing decision.
Demand Score: 84
Exam Relevance Score: 91
How does OSPF determine the best path to a destination network?
OSPF selects the path with the lowest cumulative cost metric.
Each interface in OSPF has a cost value typically based on bandwidth. Routers calculate the total cost of reaching a destination by summing the interface costs along the path. The route with the lowest total cost becomes the preferred path in the routing table. If multiple paths have equal cost, OSPF can install them simultaneously for equal-cost load balancing. Engineers often encounter unexpected routing results when interface bandwidth values are incorrectly configured, altering the calculated cost and influencing path selection.
Demand Score: 85
Exam Relevance Score: 92
What factor is most important in determining the root bridge in Spanning Tree Protocol?
The switch with the lowest bridge ID becomes the root bridge.
The bridge ID is composed of the bridge priority and the switch MAC address. During STP election, switches exchange bridge IDs and the lowest value becomes the root bridge. Administrators often influence the election by manually lowering the bridge priority on a preferred switch. If no manual configuration exists, the switch with the lowest MAC address will automatically become the root. This can lead to suboptimal traffic paths if the root bridge is not placed strategically in the network topology.
Demand Score: 83
Exam Relevance Score: 90
What configuration mismatch commonly prevents an EtherChannel from forming between switches?
A mismatch in EtherChannel negotiation protocol settings, such as one side using LACP while the other uses PAgP or static configuration.
EtherChannel requires consistent configuration across participating interfaces. If one switch uses LACP while the other uses PAgP or static mode, the bundle will fail to establish. Additional mismatches such as different trunking modes, VLAN configurations, or speed/duplex settings can also prevent aggregation. When troubleshooting, engineers should verify channel group mode compatibility and examine logs or “show etherchannel summary” outputs to confirm member interface status. Incorrect negotiation protocols are among the most common causes of EtherChannel failures in enterprise switching environments.
Demand Score: 88
Exam Relevance Score: 93
Why might an OSPF neighbor relationship remain stuck in the INIT state?
An OSPF neighbor stays in INIT when a router receives hello packets but does not see its own router ID listed in the neighbor’s hello packet.
The INIT state indicates one-way communication. The receiving router hears hellos from the neighbor but the neighbor has not acknowledged it. Common causes include mismatched hello/dead timers, incorrect network types, or ACLs blocking OSPF packets in one direction. In some cases, multicast traffic may be filtered, preventing bidirectional discovery. Engineers often overlook interface configuration mismatches or passive interfaces when diagnosing this issue. Ensuring timer settings, authentication parameters, and network types match on both routers is essential to progress from INIT to the two-way state.
Demand Score: 91
Exam Relevance Score: 95