Access
Endpoint ports, PoE, VLAN assignment, authentication and edge security.
Campus, Core and Data Centre Networking
Intelligent Switching for Secure Enterprise Networks
Build a resilient wired foundation for users, Wi-Fi, voice, CCTV, IoT and applications with switching designed around traffic, segmentation, power, availability and operations.
Campus switching topologyNODE 01 NODE 02 NODE 03 NODE 04
What makes a switch intelligent?
Fabric
Resilient uplinks, distribution, core, routing and traffic engineering.
Policy
Identity, segmentation, QoS, ACLs and approved service paths.
Assurance
Telemetry, configuration control, alerts, baselines and troubleshooting.
Policy lanes
Enterprise switching design, deployment and modernisation
Network assessmentMap switches, ports, VLANs, traffic, errors, uplinks, PoE use, support status and connected endpoints.POLICY 01
Access-to-core architectureDesign topology, routing, redundancy, bandwidth, multicast and failure behavior.POLICY 02
Segmentation and NAC readinessDefine identity, 802.1X, role or VLAN assignment, exceptions and enforcement.POLICY 03
QoS and application policyPrioritise voice, video and critical services with end-to-end marking and queue design.POLICY 04
PoE and multigigabit planningSize switch power and port speeds for Wi-Fi, CCTV, phones and connected devices.POLICY 05
Management and observabilityCentralise configuration, backups, firmware, alerts, telemetry and lifecycle reporting.POLICY 06
Operational assurance
Design the network around endpoint and service journeys
Port, endpoint and
Port, endpoint and traffic inventory
Topology and oversubscription
Topology and oversubscription model
VLAN, routing, NAC
VLAN, routing, NAC and QoS policy
PoE, optics, uplink
PoE, optics, uplink and resiliency design
Migration waves, test
Migration waves, test plan and as-built records
Campus network risk quadrantQ1 Q2 Q3 Q4 Q5 Q6
Switching problems surface as application, Wi-Fi and voice problems
Oversubscribed uplinks
Access capacity can exceed distribution or core paths during busy periods.
Insufficient PoE
Cameras, phones and access points may exceed per-port or total switch power budgets.
VLAN sprawl
Inconsistent segmentation and undocumented trunks increase risk and troubleshooting time.
Unauthenticated access
Open ports and shared networks allow unmanaged devices to connect too broadly.
Single points of failure
Stacking, uplinks, power, routing and management dependencies need defined failure behavior.
Limited visibility
Without telemetry and configuration history, intermittent packet loss becomes expensive to isolate.
Switching design and migration questions.
What is the difference between a smart switch and a fully managed enterprise switch?
Smart switches provide a limited management feature set. Enterprise managed switches typically offer deeper routing, security, redundancy, QoS, telemetry, automation and central operations. The right class depends on site criticality and requirements.
How many switch ports should we buy?
Count current endpoints by location, include access points, phones, cameras, printers, IoT and uplinks, then add realistic growth and spare capacity. Port speed and PoE class matter as much as quantity.
Do Wi-Fi 6E or Wi-Fi 7 access points need new switches?
They may benefit from multigigabit ports, higher PoE and faster uplinks. The requirement depends on AP model, radio design, client density and expected traffic. emtech validates the wired path during wireless design.
What is network segmentation?
Segmentation separates users, devices and services into controlled trust zones using VLANs, routing, ACLs, firewalls or identity-based policy. It limits unnecessary access and can improve operations.
Can emtech implement 802.1X network access control?
Yes. Scope can include identity sources, certificates, device profiling, policy, guest or contractor access, exception handling, pilot groups and staged enforcement.
How is switch resilience designed?
Options include redundant power, stacking or chassis redundancy, dual uplinks, link aggregation, resilient routing and diverse paths. The design should also cover software upgrades and failure testing.
Can old and new switches run together during migration?
Often yes, if protocols, optics, VLANs, routing and management allow it. A coexistence plan reduces cutover risk but should have a defined end state.
What documentation is included after a switch deployment?
Typical records include topology, rack and port schedules, VLAN and IP plans, trunk and uplink details, device inventory, configuration backups, software versions, test evidence and support information.
Planning a campus network refresh or solving recurring performance issues?
Request a switching assessment. emtech will review topology, traffic, PoE, segmentation, support status and operational requirements before recommending a platform.