Enterprise Networks / Campus LAN & switching
Campus LAN.From the access port to a dependable core.
A campus network works well when users, applications and operators do not have to think about its transitions. We design Cisco LANs from access to core, renew evolved estates and make resilience and acceptance testable.
Scope of service
What you receive.
This service fits new buildings, site expansions, hardware lifecycle projects and networks whose dependencies have accumulated over many years. We start with requirements, ports, PoE, uplinks, routing and operational boundaries. Those inputs drive the target architecture, bill of materials and migration sequence. A vendor reference design is not copied blindly: building systems, cabling, applications and existing standards have to be considered together.
Architecture and sizing
You receive a reasoned target architecture for access, distribution and core. Port demand, PoE capacity, uplink bandwidth, routing, resilience and management paths are explained rather than reduced to a list of product models.
Configuration standards
VLANs, trunks, spanning tree, first-hop resilience, management and baseline security follow documented standards. Site- or application-specific exceptions stay visible instead of disappearing inside templates.
A migration with a fallback
The cutover plan defines the sequence, maintenance window, dependencies, go/no-go criteria and a technically realistic fallback. Critical applications and connected systems receive explicit functional checks.
Acceptance-ready documentation
Port and device inventory, logical diagrams, configuration baseline, test evidence and residual items are handed over together. Operations begin from a known state rather than a collection of unrelated files.
The delivery path
Three controlled steps.
- 01
Capture the estate and requirements
Review buildings, cabling, endpoints, applications, the operating model and known constraints. Assumptions and measurements that are still missing are marked explicitly.
- 02
Review the design and pilot
Review the target architecture, hardware and standards, then validate critical functions in a representative area or lab before the broad migration starts.
- 03
Migrate and accept
Prepare and approve the change, implement it in controlled sections and test it against the agreed criteria. Documentation and open items move into operations in a controlled handover.
What we agree before starting
Availability depends on the complete path. Redundant switches do not replace separate power paths, suitable cabling, carrier resilience or redundant servers. We identify these dependencies in the design; construction work, active application tests, service hours and replacement hardware are assigned explicitly in the proposal.
Good to know
Your questions. Clear answers.
Does the entire estate have to be replaced at once?
No. A phased migration is often safer. Compatibility, transitional routing, spanning tree, optics and operational risks must be reviewed first. We distinguish equipment that remains fit for purpose from genuine lifecycle or capacity constraints.
Does Configlane specify the hardware?
Yes. We derive roles and sizing from the target architecture and provide a reasoned bill of materials. Procurement, delivery dates, support contracts and any required spares are treated as separate responsibilities.
What is part of technical acceptance?
The exact tests depend on the network. Typical areas include management, routing, resilience, uplinks, PoE, endpoints, monitoring and selected applications. Success criteria and evidence are agreed before the change, not after an incident.
Let’s discuss your requirements
A few details are enough to begin.
You do not need a finished design. We establish the need, boundaries and a dependable next step.
Discuss your campus LANHelpful for the first conversation
- Sites, buildings and approximate port counts
- Critical applications and tolerable interruption
- Existing switches, cabling and network diagrams
- Operational, documentation and approval requirements
Please do not submit passwords, API keys or confidential network plans through the form.
Explore the technical detail
The artefacts required for dependable network acceptanceTechnical background: Cisco Campus LAN and Wireless LAN Design Guide