Network Security Appliances and Controllers
CCNA objective 1.1 asks you to describe the role and function of network components. This lesson takes the devices you met in Lesson 1 — and the ones that secure and manage them — and sorts them by what they do, where they sit, and which header they read to do it.
Why device roles are tested
Objective 1.1 is deceptively simple: “describe the role and function of network components.” In practice the exam checks whether you can look at a one-sentence scenario and name the device it implies. The trick is that the exam describes a behaviour, not a brand. A question rarely says “choose a switch”; it says “which device forwards frames within a single broadcast domain using MAC addresses?” You must translate the behaviour back into the device.
The reliable way to do that is to ask two questions about any device:
- What does it read? — the header it inspects tells you the layer it operates at: MAC address (Layer 2), IP address (Layer 3), port number (Layer 4), or application data (Layer 7).
- Where does it sit? — inside one LAN, at the boundary between networks, or at the network edge facing the Internet. Position follows function.
Routers and switches
A router is a Layer 3 intermediary device that forwards packets between different IP networks. Every interface on a router is in its own subnet, and the router keeps a routing table that maps destination networks to a next hop. It reads the destination IP address of each packet, finds the most specific matching route (the longest-prefix match), and forwards the packet out the correct interface.
Because a router joins dissimilar networks, it is the device that makes the Internet a “network of networks.” It also breaks up broadcast domains: a router will not forward a Layer 2 broadcast out of the interface it arrived on, which is why subnets exist at all. At home, the all-in-one box your ISP supplies is a router with a small switch, an access point, and a basic firewall crammed inside.
A switch is a Layer 2 intermediary device that forwards frames within one local network. It learns which MAC address lives on which port by watching the source MAC of every frame that arrives, and it stores that mapping in its MAC address table. When it later sees a frame for a known destination, it forwards it only out the correct port; when the destination is unknown, it floods the frame out every port except the one it came in on.
A traditional switch operates purely at Layer 2: it never looks at IP addresses. A multilayer switch (often called a Layer 3 switch) adds a routing engine, so it can forward packets between VLANs at wire speed without sending the traffic to a separate router. That is the classic campus-design question: use an L3 switch for inter-VLAN routing in the core/distribution, and keep the router for connectivity to the WAN and ISP.
| Question | Layer 2 switch | Layer 3 switch | Router |
|---|---|---|---|
| PDU handled | Frame | Frame and packet | Packet |
| Address read | MAC (Layer 2) | MAC, then IP (Layer 3) | IP (Layer 3) |
| Scope | Within one VLAN/LAN | Within the campus, across VLANs | Between networks and to the WAN |
| Typical port count | Many (24–48+) | Many (24–48+) | Few |
| Typical location | Access layer | Distribution/core | Network edge |
! A multilayer switch can route between VLANs once ip routing is enabled SW1(config)# ip routing SW1(config)# interface vlan 10 SW1(config-if)# ip address 10.10.10.1 255.255.255.0 SW1(config-if)# no shutdown
Firewalls and next-generation firewalls
A firewall sits at a boundary — between the trusted inside network and the untrusted outside — and decides which traffic is allowed to cross. A classic firewall works from a rule set of permit and deny statements, usually expressed as an ACL: source, destination, protocol, and port. A stateful firewall remembers active connections so that return traffic is permitted automatically without an explicit rule in the other direction.
A next-generation firewall (NGFW) adds layers of awareness on top. It can inspect traffic at the application layer (Layer 7), recognise applications regardless of port, identify users and groups, decrypt and inspect TLS with policy, and integrate threat-intelligence feeds. Where a traditional firewall asks “is port 443 open?”, an NGFW asks “is this the approved application, for this user, and does the payload contain a known threat?”
IPS and IDS: inline vs out-of-band
An intrusion prevention system (IPS) and an intrusion detection system (IDS) both compare traffic against signatures and behavioural baselines to spot attacks. The difference is what they are allowed to do about it, and that difference comes from where they are placed.
| Property | IDS | IPS |
|---|---|---|
| Placement | Out-of-band (a copy of the traffic, e.g. from a SPAN port or TAP) | Inline (traffic must pass through it) |
| Action | Detect and alert only | Detect and block or drop |
| Effect of failure | Traffic keeps flowing | Can stop traffic if it fails (a fail-open/fail-closed design choice) |
| Latency | None added to the live path | Adds a small amount of latency |
VPN concentrators and wireless LAN controllers
A VPN concentrator is a device or appliance that terminates many virtual private network tunnels at once, typically for remote workers or branch sites connecting back to head office over the public Internet. Each client establishes an encrypted tunnel (commonly IPsec or TLS-based) to the concentrator, which authenticates the user and then routes the decrypted traffic into the corporate network.
The word “concentrator” is the clue: its purpose is to aggregate large numbers of tunnels and cryptographic sessions in one place, so a site-to-site or client-to-site VPN can scale. A modern firewall often folds the VPN concentrator function into itself, but on the exam a concentrator is simply the device that terminates and manages many encrypted tunnels.
A wireless access point (AP) bridges wireless clients onto the wired LAN. It converts 802.11 radio frames to 802.3 Ethernet frames and back, and it is the device a laptop or phone associates with. An AP is a Layer 2 device and forms part of one broadcast domain per SSID (mapped to a VLAN).
Managing dozens or hundreds of APs one at a time does not scale, so enterprises use a wireless LAN controller (WLC). The WLC centralises configuration, security policy, roaming, and RF management. In the usual split-MAC design, lightweight APs handle only the real-time radio work while the WLC handles management, authentication, and mobility. The AP and WLC communicate over the CAPWAP protocol (UDP ports 5246 and 5247).
Endpoints and where each device sits
Not every device on the network forwards traffic. Endpoints, also called hosts, are the sources and destinations of data: laptops, desktops, phones, tablets, printers, IP cameras, and IoT sensors. Servers are specialised endpoints that provide a service — web, file, email, database, DNS — to many clients at once. A server is still an endpoint in the topological sense: it originates and consumes data, and the network forwards that data on its behalf.
The distinction to hold in your head is host vs intermediary. A host runs the user’s application and has an address it can be reached by; an intermediary device exists to move that host’s traffic. A firewall, switch, router, AP, and WLC are all intermediaries. A server is a host, no matter how powerful or how central it is.
The diagram below places the CCNA 1.1 devices along a typical path from the Internet to the endpoints. Read it left to right as the path of a packet entering from the Internet, and note the two off-path devices: the IPS, drawn inline in the traffic path, and the WLC, which manages the AP rather than forwarding user data itself.
- Switch vs router: same network → switch; different networks → router.
- L2 vs L3 switch: the words “inter-VLAN routing” point to a multilayer (L3) switch.
- IPS vs IDS: “inline and blocks” is IPS; “monitors a copy and alerts” is IDS.
- AP vs WLC: the AP provides the radio link; the WLC is the central controller for many APs.
- Host vs intermediary: “endpoint” and “server” are hosts, not forwarding devices.
Review
Check what you have learned with these review questions.
| Term | Meaning |
|---|---|
| Router | Layer 3 intermediary device that forwards packets between different IP networks and breaks up broadcast domains. |
| Layer 2 switch | Device that forwards frames within one LAN using its MAC address table; floods unknown destinations. |
| Multilayer (Layer 3) switch | A switch with a routing engine, able to forward packets between VLANs at high speed. |
| Firewall | Boundary device that permits or denies traffic crossing between zones according to a rule set. |
| Next-generation firewall (NGFW) | Firewall that adds application-layer inspection, user identity, and threat intelligence. |
| IDS | Intrusion detection system; monitors a copy of traffic out-of-band and raises alerts but cannot block. |
| IPS | Intrusion prevention system; inspects traffic inline and can drop or block malicious packets. |
| VPN concentrator | Appliance that terminates and aggregates many encrypted tunnels for remote users and sites. |
| Wireless access point (AP) | Layer 2 device that bridges 802.11 wireless clients onto the wired LAN. |
| Wireless LAN controller (WLC) | Central controller that configures and coordinates many lightweight access points. |
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals (1.1 Network components). cisco.com.
- Calhoun, P. et al. RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification (2009). rfc-editor.org/rfc/rfc5415.
- Scarfone, K. & Hoffman, P. NIST SP 800-41 Rev. 1: Guidelines on Firewalls and Firewall Policy (2009). csrc.nist.gov.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
Sources & references
- Cisco. CCNA (200-301) Exam Topics, Network Fundamentals (1.1 Network components). cisco.com.
- Calhoun, P. et al. RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP) Protocol Specification (2009). rfc-editor.org/rfc/rfc5415.
- Scarfone, K. & Hoffman, P. NIST SP 800-41 Rev. 1: Guidelines on Firewalls and Firewall Policy (2009). csrc.nist.gov.
- Socolofsky, T. & Kale, C. RFC 1180: A TCP/IP Tutorial (1991). rfc-editor.org/rfc/rfc1180.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.