Connect. Secure. Manage.
BGP Convergence and BFD
Evaluate Cisco BGP failure detection and convergence, testing BFD and timer choices against platform limits, link behaviour and application tolerance.
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.
BGP convergence and BFD work address different parts of network recovery. BFD can help a supported device detect a forwarding-path failure quickly; BGP must then select and install an appropriate alternative. MCI Network Services investigates slow or unstable Cisco routing recovery and designs detection settings around the actual platform, circuit and application. Faster timers are not automatically a better outcome when they cause unnecessary route changes.
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.
Measure the interruption that matters
A customer may report that failover takes too long even though the BGP neighbour drops promptly. We break the event into stages: detecting the fault, changing the route, installing forwarding state and restoring useful application traffic. That separates a detection problem from a missing backup route, a stateful-firewall dependency or an application reconnection delay.
The baseline should include the fault being tested and the observation point. Removing a directly connected cable is different from losing service beyond a carrier handoff while the local interface stays up. We agree representative scenarios and collect timestamps from the relevant systems. Without that context, two teams can describe the same event using incompatible recovery measurements.
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
Decide where BFD is appropriate
Bidirectional Forwarding Detection provides a mechanism for monitoring liveness between participating systems. Integration with BGP depends on the supported platform, software, session type and configuration at both ends. We confirm those details with the peer owner before proposing deployment. A setting available on one Cisco family is not assumed to exist on every other device.
We distinguish single-hop and multihop requirements and review any special behaviour associated with bundled interfaces or virtual routing instances. The design also considers the number of sessions and the resources used to process them. A timer suitable for a small number of hardware-supported sessions may be unsuitable for a much larger or differently implemented estate.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Avoid turning congestion into repeated failover
Aggressive detection can mistake delayed control traffic for a failed path. We examine link quality, queueing, control-plane protections and device load before shortening intervals. A marginal WAN circuit needs investigation; simply making its failure detector more sensitive can create route flapping and a worse user experience.
We agree tolerances and recovery behaviour with the service owner. The objective is a stable, useful response to a real fault, not the lowest number shown in a lab. Where the path crosses a provider network, that provider’s supported settings and operational advice are part of the decision. Both sides need a consistent understanding of the expected detection behaviour.
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 ↗Ensure an alternative route is actually usable
Fast detection is of little benefit if the backup path is filtered, has an unreachable next hop or lacks capacity. We review the route-policy result before and after failure, including internal propagation and firewall paths. A valid BGP alternate still needs compatible forwarding and return traffic through the rest of the network.
We also consider features that intentionally preserve routing state during a restart. Graceful-restart behaviour can be useful in supported circumstances, but its interaction with failure detection needs deliberate assessment. Preserving stale reachability during a genuine forwarding failure is different from maintaining service through a planned control-plane event. The design should state which condition each mechanism is intended to address.
Build a safe test plan
Tests can include peer loss, circuit failure, an intermediate reachability fault and restoration, subject to the available maintenance window. We identify the expected sequence and abort conditions before introducing a fault. Application owners select representative transactions or sessions so that acceptance is not reduced to a router ping.
We record detection time, route changes, observed packet loss and recovery behaviour where measurement is feasible. Repeated tests may be needed to distinguish a stable result from an unusually favourable run. Results are described with their conditions, not promoted as a guarantee that every future failure will recover within the same interval.
Investigate false positives with evidence
When BFD or BGP sessions flap, we inspect interface errors, queueing, session diagnostics and system logs around the same time. We compare both ends and account for clock differences. A loss indication on one router does not, by itself, prove which device or circuit caused the interruption.
Changes are targeted at a supported hypothesis. We avoid altering BFD, BGP timers and routing policy simultaneously unless a wider emergency plan explicitly requires it. A controlled sequence makes the outcome easier to explain and reduces the chance of masking the original fault with a new one.
Hand over a recovery model, not just timers
MCI documents the supported settings, peer dependencies, test results and alarms that indicate lost resilience. Review triggers include platform upgrades, circuit changes and significant growth in session count. This service complements BGP multihoming design and BGP troubleshooting, helping you understand both how quickly a fault is detected and what the network can do next.
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.