Connect. Secure. Manage.
Network Staging and Preconfiguration
Prepare Cisco and Meraki equipment before it reaches site, validating software, addressing, configuration and recovery access in a controlled environment.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Network staging and preconfiguration move suitable preparation work out of the production change window. MCI prepares Cisco and Meraki equipment against an accepted design, checking the hardware, software, configuration and identification before it is delivered to a live site. The purpose is to reduce avoidable uncertainty when engineers are working against a fixed maintenance or opening schedule.
Staging is not a substitute for site commissioning. Some dependencies only exist in the production environment, and those still need testing. A useful staging process makes that boundary explicit: what has already been checked, what remains to be verified and which assumptions the site team must confirm.
A clear requirement
Turn the business need into a practical network scope with visible dependencies.
A controlled delivery
Plan implementation, testing and rollback before production changes begin.
A supportable result
Leave useful records, ownership and escalation routes behind.
Agree the build baseline before preparation starts
The equipment needs an identifiable design and configuration version. We establish the intended device roles, software requirements, licences and site-specific information before applying settings. Missing addressing or uplink details are recorded as prerequisites rather than filled with convenient guesses.
Where several sites are involved, the standard build and each variation need to be distinguishable. A device prepared for one branch should not be capable of being mistaken for another simply because the hardware is identical.
Low-level design supplies the implementation detail where it is not already available. Staging then checks the equipment against that design instead of becoming an informal design exercise of its own.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Check the equipment and required accessories
We verify the supplied equipment against the intended build, including relevant optics, power components and mounting requirements. The aim is to identify missing or unsuitable items before they delay on-site work.
Initial hardware and software checks can establish that the device is ready for its role. Where a software change is required, the process needs to account for compatibility, configuration handling and the evidence that the intended version is in place.
This is also an opportunity to identify equipment that does not match the order or the design. An apparently minor substitution may alter ports, power, feature support or the physical installation arrangement and should be assessed before it reaches the site.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Prepare configuration without creating live conflicts
Preconfiguration can include management settings, interface roles and other design elements that are safe to establish in the staging environment. Site addressing and routing information must be handled carefully so a test connection does not accidentally advertise or use production values in the wrong place.
For Meraki deployments, organisation placement, network assignment and administrator access are part of the preparation. Shared templates need to be considered for their effect on the wider estate, not treated as an isolated staging convenience.
For Cisco devices, the configuration is tied to the actual platform and software baseline. Commands and features should not be copied between unlike models on the assumption that a familiar syntax produces the same operational result.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Test what the staging environment can establish
The test scope can cover configuration consistency, relevant interface behaviour, management access and representative integration. The important point is to state the conditions under which the tests were performed.
Some production requirements cannot be fully reproduced. A carrier circuit, building radio environment or an application controlled by another organisation may only be available later. The staging record identifies those limitations so a successful bench test is not mistaken for complete site acceptance.
Where a material design uncertainty exists, a proof of concept may be needed before staging begins. Staging verifies a chosen build; a proof of concept helps determine whether the proposed approach is suitable in the first place.
Package the equipment for an unambiguous site handover
Device labels, connection information and the site build record should make it easy to identify what belongs where. The installation team needs the approved configuration version, outstanding checks and any actions that must occur before production connectivity is enabled.
Sensitive credentials are handled through an appropriate controlled route, not printed indiscriminately on equipment or included in a general delivery note. The handover also identifies who can authorise a change if the site conditions differ from the plan.
For a multi-site rollout, these records make repeated delivery more manageable. Each site’s preparation can be checked against the same process while retaining its own addressing, circuit and acceptance information.
Staging and preconfiguration questions
Can you stage equipment that will be installed by our team?
Yes. We agree the build, tests and handover information your installers need. The receiving team must understand which checks are complete and which still depend on the live site, so responsibilities remain clear after dispatch.
Does staging remove all on-site configuration work?
No. Some settings and tests depend on the production environment. The benefit is reducing unnecessary work and uncertainty during the site window, not claiming that every installation can be completed without local engineering judgement.
How are last-minute design changes handled?
They need a controlled update to the build record and, where relevant, retesting. Otherwise equipment can arrive with a configuration that no longer matches the latest plan. The impact on prepared devices and other sites should be assessed before the change is accepted.
What should we provide to start?
The equipment scope, accepted design, site-specific values and intended installation dates are needed. Arrange network staging and preconfiguration before delivery logistics are fixed, particularly where many similar devices are being prepared for different locations.
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 6566Choose option 1
sales@proxar.co.ukUK-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.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.