A switch should be selected around the network it must support, not only by counting Ethernet ports.
Practical example: segmenting a 45-user office
Select network equipment from traffic, management and growth requirements.
Scenario: One managed switching environment carries servers, staff devices, VoIP, CCTV and guest WiFi.
| Example VLAN | Purpose | Example policy |
|---|---|---|
| 10 | Servers | Accessible only from authorised business networks |
| 20 | Staff | Access to approved internal services and Internet |
| 30 | Voice | Restricted to required voice and management services |
| 40 | CCTV | Camera traffic restricted to required recording and management systems |
| 50 | Guest WiFi | Internet access, blocked from internal business networks |
Decision: VLANs provide the logical separation. The router, firewall or Layer 3 policy determines which networks may communicate.
Common mistakes and selection checklist
Common mistakes
- Creating VLANs but allowing unrestricted routing between them.
- Using VLAN IDs without documenting IP subnets, DHCP, gateways and access policy.
- Configuring trunk and access ports inconsistently across switches and access points.
What happens if you get it wrong?
The network can look segmented while providing little security benefit, or devices can lose connectivity because tagged and untagged traffic is handled differently at each hop.
Selection checklist
- Define the purpose and subnet of every VLAN.
- Document which VLANs may communicate and on which services.
- Configure gateway or Layer 3 firewall policy explicitly.
- Verify access ports, trunks and native or untagged VLAN behaviour end to end.
- Test DHCP, DNS, Internet access and blocked inter-VLAN paths after deployment.
Start with the connected equipment
List every device that will connect to the switch. Include workstations, servers, printers, wireless access points, IP phones, cameras, NAS systems and uplinks to other switches. Then separate current requirements from expected growth.
Managed or unmanaged?
Cisco describes unmanaged switches as plug-and-play equipment with no settings to configure. Managed switches provide configuration, monitoring and performance information, making them more suitable for larger networks and networks supporting critical operations.
Port count is only the beginning
A 24-port switch with only 1 GbE copper ports is a very different device from a 24-port switch with PoE, multi-gigabit access ports and 10 GbE uplinks. Check the port types, not only the total number printed in the product name.
Consider the uplinks
Switch uplinks carry traffic towards another switch, a router, a server or an aggregation layer. If 24 or 48 access ports all share one undersized uplink, the uplink can become the bottleneck.
Do you need PoE?
PoE can power access points, IP phones, cameras and other compatible devices through Ethernet cabling. The switch must provide the correct PoE standard and enough total power budget for all connected devices.
Do you need VLANs?
If servers, staff devices, guest WiFi, cameras or voice equipment need to be separated, a managed switch with appropriate VLAN support is normally required. The router or Layer 3 switch must then control traffic between those networks.
Practical buying checklist
- Required port count now and in two to three years
- 1 GbE, 2.5 GbE or 10 GbE access ports
- SFP, SFP+ or faster uplinks
- Managed or unmanaged operation
- VLAN and trunk support
- PoE standard and total PoE budget
- Rack-mount or desktop installation
- Redundant uplink or aggregation requirements
A switch often remains in service for years. Uplink speed, PoE capacity and management capability usually matter longer than the number of unused ports on day one.
- Cisco Managed Versus Unmanaged Switches
- Cisco Different Types of Network Switches
- Cisco Power over Ethernet
Technical information is based on current official documentation. Product capabilities vary by model.
Confirm the exact product specification, supported configuration and compatibility before ordering. Platform generation, firmware, licences and optional components can change what a product supports.