Connect. Secure. Manage.
Catalyst Center LAN Automation
Use Catalyst Center LAN automation on supported Cisco networks, with preparation, address-pool planning and validation of the resulting underlay.
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.
Catalyst Center LAN automation can build a routed network from an agreed design. It still needs the right seed devices, address pools, cables and access. We prepare those inputs and treat the rollout as a controlled change. Tests check the resulting network, so your team knows what was built and how to support it.
Cisco-focused engineering
Design around the platform, traffic and failure behaviour you actually operate.
Change with evidence
Use pre-checks, acceptance criteria and a documented route back.
Operational handover
Keep the configuration, diagrams and responsibilities understandable after delivery.
Confirm the intended underlay
We start with the topology that should exist after automation: device roles, links, addressing and routing. The design must fit the supported hardware and Catalyst Center release. A workflow that works in one reference topology may have different constraints in a current campus with retained links and devices.
The project also identifies whether the equipment is new, reset or already carrying production services. Device state matters to onboarding. We do not assume a current switch can be discovered and reconfigured safely without considering its current users, management path and dependencies. The preparation plan records what must be backed up and what may be replaced by automation.
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
Prepare addressing and shared services
LAN automation needs suitable address pools and consistent site settings. We review the allocation strategy, available capacity and any overlap with the current network. The pools should support the intended rollout and growth, not merely contain enough addresses for the first few devices.
DNS, time services, credentials and network access to the management platform are checked before the session starts. Firewall and routing dependencies are documented with their owners. Resolving these prerequisites in advance is preferable to repeatedly restarting a failed workflow while changing unrelated settings and losing track of the original condition.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Validate seed devices and physical connections
Seed devices form part of the automation process and need the appropriate state, access and supported software. We confirm the intended primary and other participating roles for the chosen workflow. Physical link information is checked against the design so newly discovered devices are not accepted simply because they appeared on an unexpected port.
Cabling and uplink capacity remain engineering duties. Automation cannot establish that fibres use diverse routes or that a power design meets the required availability. We check the physical installation and identify any temporary connections used for staging. The handover should reflect the final topology rather than the arrangement used to make an initial discovery succeed.
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 ↗Define configuration ownership
The customer needs to know which underlay settings are generated and maintained through the platform and which are managed separately. Uncoordinated local changes can make later automated operations unpredictable. We document the boundaries and any supported exceptions before the network enters routine operation.
This is particularly important in a mixed estate. Retained routers, firewalls or third-party devices may not participate in the same workflow. Their interfaces to the automated underlay still require reviewed setup and testing. The automation scope should not imply that every neighbouring device has been provisioned or checked automatically.
Run a controlled provisioning session
The rollout plan defines the device set, expected discovery result, monitoring steps and completion criteria. We observe the workflow and retain useful logs and setup evidence. Unexpected devices, address allocation or topology are investigated before the session is accepted as complete.
Where a step fails, we identify the state of both the platform and the affected equipment before retrying. Repeating an operation without understanding partial completion can make recovery harder. The plan includes the supported recovery or reset procedure and any point beyond which a manual rollback is no longer straightforward.
Verify the resulting network directly
Acceptance includes device identity, assigned addresses, neighbour relationships, underlay routing and reachability between the intended nodes. We also inspect management access and the ability to collect setup and telemetry. A workflow completion message is not a substitute for checking the actual forwarding foundation.
The test plan considers the next stage that will use the underlay. For an SD-Access rollout, the fabric needs influence what must be proven. Selected link or device failures may be tested within an agreed window, with results recorded against the design. Unsupported or untested scenarios remain visible rather than being included in a broad success statement.
Leave a maintainable underlay
The delivery record includes the address allocations, topology, automation session details and configuration-ownership rules. It explains how later devices or links should be added and who may approve those changes. Operations should be able to distinguish an automation issue from a physical or routing fault.
MCI offers this service within SD-Access fabric design or as a focused underlay rollout. A readiness review can identify whether the current estate is suitable before a provisioning window is booked. The goal is a repeatable process with reliable evidence, not a one-off successful session that nobody can reproduce or support.
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.