Cisco & Meraki specialists. Across the UK.
+44 203 196 6566 · option 1sales@proxar.co.uk

Connect. Secure. Manage.

Campus Gateway Deployment

Deploy a supported Cisco Campus Gateway design with the required network preparation, access-point settings and validation of client traffic paths.

Cisco Partner since 2009 Projects & ongoing support

Illustrative Cisco and Meraki fibre network rack with structured cabling
Your network. Properly considered.Design · Implementation · Support
1,000+

Devices supported
across the UK

20+

Client locations
supported

Nearly 8 Tbps

Traffic handled
at peak time

3 min

Average
response time

Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.

Campus Gateway deployment puts an approved Cisco wireless design into use. We prepare switching, identity and Dashboard setup, then test access-point tunnels and upstream paths. Client policy and real user workflows are checked before handover. The agreed service must work and be supportable, beyond the gateway simply appearing online.

01

Coverage and capacity

Design Wi-Fi around the spaces, devices and traffic that depend on it.

02

Secure access

Align authentication, segmentation and guest access with the wider network.

03

Measured performance

Validate roaming, interference and user experience instead of relying on signal bars.

Confirm the implementation baseline

We start with the approved architecture, appliance choice and access-point inventory. Firmware alignment, supported models and the intended feature set are checked against current vendor needs. The delivery record identifies any prerequisite upgrades and the order in which they must occur. A rollout should not rely on the assumption that a current access point can participate simply because it is already managed through dashboard.

Ownership and access are agreed with the customer. We confirm the destination organisation and networks, authorised administrators and the process for claiming or assigning equipment. The project also identifies the teams responsible for switches, firewalls, identity and client testing. Those contacts are part of the rollout plan because a failed commissioning test may need a coordinated change outside the gateway itself.

Illustrative Cisco Meraki wireless access point in a modern office
01Cloud-managed wireless for modern workplaces.
Cisco PartnerCisco Partner
Cisco MerakiCisco Meraki
ISO 9001Quality management
ISO 27001Information security
Cyber EssentialsCyber Essentials
Cyber Essentials PlusCyber Essentials Plus

MCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information

Prepare the physical and upstream connections

Installation preparation covers rack space, power, supported optics, uplinks and any required redundancy connection. We check the actual hardware guide rather than treating available ports as interchangeable. Port-channel and switching setup are reviewed on both sides, with clear interface descriptions and a record of the intended physical paths.

The upstream network is prepared for management and client traffic according to the design. We check addressing, VLAN presentation, routing and the necessary permissions before onboarding. The current network must carry the relevant tunnel traffic correctly, including its MTU needs. A successful reachability check is only one prerequisite. It does not replace validation of the complete data path or the client services beyond the gateway.

Illustrative Cisco and Meraki network rack in a modern office
02The office network: switching, uplinks and structured cabling.

A useful starting point

Not sure where to start?

Bring the requirement. We will help you define the engineering work.

Talk to a specialist

Configure the dashboard relationships

The gateway and supported access points are assigned to the intended management structure. We configure the relevant wireless-service relationships and check how access points are directed to the gateway arrangement. Where the architecture uses supported network groups or shared profiles, those objects are included in the rollout record with their ownership and scope clearly identified.

We check policy before exposing the service widely. Client addressing, authentication, access restrictions and any supported integrations must correspond to the approved design. Corporate and guest services should not inherit an accidental common boundary during commissioning. The team checks both successful app access and destinations that should remain blocked, rather than treating any working internet connection as a complete policy test.

Illustrative Cisco and Meraki network operations centre with monitoring displays
03Visibility, monitoring and operational control.

Commission a representative pilot

The first access points and clients are chosen to exercise the important dependencies. We include relevant switch paths, device types and authentication methods, then trace their traffic through the intended termination. The pilot checks fresh connections, address assignment, normal apps and mobility where it is in scope. Results are recorded against the specific software and setup baseline.

If a test fails, we isolate the relevant stage before expanding the rollout. A tunnel issue, an identity rejection and a missing upstream VLAN require different responses. We retain enough evidence to support a precise diagnosis and avoid changing several unrelated settings at once. Material exceptions need approval and an owner. They are not silently passed to the operations team as an unexplained feature of the new service.

Illustrative Cisco and Meraki equipment in organised data-centre racks
04Data-centre connectivity with clear physical and logical boundaries.

Verify resilience and maintenance access

Where the design includes a cluster, we check its expected state and the agreed failure scenarios. We observe client behaviour during loss and restoration of relevant components, with testing constrained by the customer’s maintenance and safety needs. The Campus Gateway resilience service can provide a dedicated assessment when continuity is the main project concern.

Administrative and recovery access are tested independently of ordinary client forwarding. Engineers need a supported route to gather evidence when dashboard network access or part of the upstream network is unavailable. We document how diagnostics are collected, who can use them and when a disruptive action requires approval. The aim is to avoid a rollout that works normally but has no practical support procedure for an abnormal condition.

Illustrative Cisco and Meraki fibre network rack with structured cabling
05Fibre, switching and the physical path behind the service.

Complete the configuration and handover record

After rollout, we reconcile the installed estate with the design and retain setup, inventory and acceptance records. Temporary commissioning exceptions are removed or clearly assigned for follow-up. Monitoring is checked with the intended operations team so alerts identify actionable service conditions rather than producing notifications without a responsible recipient.

MCI can deliver this work as part of a new Cisco Campus Gateway project or a staged migration from a current architecture. Share the approved design, site-access needs and proposed change window. We will prepare a controlled delivery sequence and clear completion criteria, including the dependencies that must be ready before the gateway can carry production wireless traffic safely.

Illustrative Cisco Meraki wireless access point in a modern office
06Cloud-managed wireless for modern workplaces.

Technical references

Illustrative Cisco and Meraki network rack in a modern office
07The office network: switching, uplinks and structured cabling.

Talk to a specialist

What does your network need next?

Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.

+44 203 196 6566

Choose option 1

sales@proxar.co.uk

UK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.

Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.

Tell us what you need.

A short outline is enough. Please do not include passwords or sensitive network details.

Thank you. Your enquiry has been submitted.

We’ll use these details to respond to your enquiry. Please leave out passwords and sensitive network information. Read our privacy notice.