Connect. Secure. Manage.
Catalyst Center Assurance
Configure Catalyst Center assurance around the users and applications that matter, with meaningful baselines, issue investigation and escalation workflows.
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 Assurance is useful when it helps engineers move from a user complaint to relevant network evidence. Health scores and issue dashboards are not an end in themselves. MCI Network Services configures and reviews Cisco assurance workflows around the devices, clients and applications the business needs to support, checking that telemetry is complete enough to inform decisions and that the operations team knows how to interpret 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.
Define the questions operations needs to answer
We start with practical incidents: a user cannot authenticate, wireless service is inconsistent, an application path has changed or a site appears degraded. The required evidence differs for each case. We agree which journeys and device roles the initial assurance deployment should cover, rather than enabling data collection without a clear operating purpose.
This also establishes the limits of the engagement. Network telemetry can help identify a fault, but it may not reveal an application defect or a problem inside another provider’s service. The operating procedure should identify when to collect more evidence and when to involve another owner. A dashboard should narrow uncertainty, not create unjustified certainty.
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 telemetry foundations
The platform needs supported devices, software, entitlements and collection settings for the intended views. We review those prerequisites and the network paths used to deliver data. A device may be reachable for management while a particular telemetry stream is missing or incomplete.
Time synchronisation is especially important when correlating events across systems. We check the relevant clocks and record how timestamps are interpreted. Without that alignment, an authentication failure, a port event and an application alert can appear to occur in the wrong order. Collection health therefore belongs in acceptance alongside the visible health of the network itself.
A useful starting point
Tell us what is happening.
A short description of the problem is enough for an initial discussion.
Build a trustworthy baseline
We exercise representative client journeys and compare the platform’s view with what actually happened. This can include onboarding, address assignment, application access and selected movement or failure events. The objective is to establish whether the collected evidence describes the service accurately enough to be useful.
Missing or stale data is treated as a separate condition from an unhealthy service. A low score may deserve investigation, while an apparently healthy score may conceal an unobserved part of the estate. We explain the coverage and known gaps so that the team does not overextend the meaning of a single indicator.
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 ↗Turn issues into actionable investigation paths
Issue categories and thresholds should lead to a defined response. We identify the team responsible, the first checks to perform and the evidence needed for escalation. A large volume of alerts with no ownership can make genuine incidents harder to see, even when the underlying platform is collecting valuable information.
Automated correlations and suggested causes are validated against device state and representative traffic. We do not describe an algorithm’s suggestion as a confirmed root cause without supporting evidence. The runbook should help an engineer test the hypothesis and distinguish a primary fault from the symptoms it causes elsewhere.
Include the customer’s wider monitoring process
Assurance may sit alongside an existing monitoring, ticketing or security platform. We review the supported integration and agree which events should be forwarded. Duplicate alarms, inconsistent severity and unclear closure rules can create unnecessary work if the systems are connected without a process design.
Data access and retention are considered according to the information being collected. Client identifiers and traffic-related records can be sensitive. We restrict administrative visibility and avoid exporting unrestricted datasets simply because an integration makes it convenient. The customer’s governance requirements remain relevant to a network-management tool.
Test failures without confusing visibility and service
Selected tests can show how the platform reports a lost uplink, failed authentication or missing collector data. We record both the service impact and the monitoring result. A test that proves an alarm appears does not establish that the associated business service recovered successfully.
We also examine the effect of a management-platform outage. The available evidence may change even when existing network forwarding continues. Support procedures should explain alternative investigation methods and how to recognise a telemetry backlog after recovery. This prevents the team from interpreting every delayed event as a new live incident.
Make assurance part of normal operations
The handover includes collection prerequisites, coverage, known gaps, response procedures and review responsibilities. New devices, software changes and altered client workflows should trigger a check that the evidence remains useful. Periodic validation is more valuable than assuming the initial setup will remain accurate indefinitely.
MCI can introduce Assurance after Catalyst Center deployment or improve an existing installation that produces data without clear operational benefit. The engagement should leave your team with better questions, better evidence and a practical route to resolving incidents, rather than another dashboard that requires constant attention but rarely changes the outcome.
Talk to a specialist
Need a specialist view?
Tell us what is affected, what changed and what your team has already checked. A short outline is enough to start.
+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.