Monitor Your OVHcloud Connect

Ver como Markdown

Discover the tools and metrics available to monitor your OVHcloud Connect service

Objective

Monitoring your OVHcloud Connect service ensures that the connection is healthy, performant, and meeting your expectations. This guide covers the tools and metrics available.

Log in to your and go to Network > OVHcloud Connect.

Monitoring tools

OVHcloud Control Panel

The primary interface for monitoring your connection provides visibility into the following metrics:

MetricDescription
Connection statusWhether the physical link is up or down
BGP session statusWhether BGP peering is Established, Active, or Idle
Bandwidth usageCurrent and historical throughput (inbound/outbound)
Port statusPhysical interface state and error counters
Service detailsPoP, bandwidth tier, vRack association, configuration

OVHcloud API

For programmatic monitoring and integration with your own tools:

import ovh

client = ovh.Client(endpoint='ovh-eu')

service_name = "your-occ-service-uuid"

# Get service status
service = client.get(f"/ovhCloudConnect/{service_name}")
print(f"Status: {service['status']}")

# Get PoP configuration and BGP state
pop_config = client.get(f"/ovhCloudConnect/{service_name}/config/pop")
print(pop_config)

Full API reference: eu.api.ovh.com/console

Your own monitoring tools

Complement OVHcloud's monitoring with your own infrastructure:

  • SNMP — Poll your router's interfaces for traffic counters, error rates, and interface status.
  • BGP monitoring — Use tools like bgpstream, exabgp, or your router's built-in monitoring to track BGP session stability and prefix changes.
  • Ping / latency probes — Set up regular pings or latency measurements between your on-premises network and OVHcloud resources.
  • Third-party platforms — Tools like Datadog, Zabbix, PRTG, or Grafana can aggregate metrics from both your infrastructure and OVHcloud's API.

On-demand diagnostics

You can launch on-demand diagnostics from the OVHcloud Control Panel to get a point-in-time status report of your OVHcloud Connect service. Each diagnostic runs in real time against the OVHcloud-side equipment and returns a result you can view or download.

Available diagnostics

Layer 3 mode:

DiagnosticDescription
BGP Peering TestFetches the BGP session state and related information.
RoutesFetches the routing table learned by OVHcloud via BGP (routes received from your side).
Advertised-RoutesFetches the routing table advertised by OVHcloud to your side.

Layer 2 mode:

DiagnosticDescription
MAC AddressFetches the list of MAC addresses seen on the Layer 2 segment between your network devices and the vRack.

Launch a diagnostic

  1. Open the OVHcloud Connect service you want to diagnose.
  2. At the bottom of the "POP Configuration" panel, in the "Diagnostic POP" segment, click the ellipsis button ....
  3. Select the diagnostic to run — for example BGP Peering Test in Layer 3 mode, or Get the list of my MAC addresses in Layer 2 mode.
  4. Confirm by clicking Launch diagnostic.

Retrieve a result

  1. Open the Diagnostics tab of the service. Each diagnostic is listed with its ID and timestamp.
  2. Click the ellipsis button ... next to the entry.
  3. Select See result to open the output in a new window, or Download result to save a .txt file.

Limits

LimitValue
RetentionOnly diagnostics initiated within the last seven days are accessible. Download and archive the ones you need to keep.
Rate limit10 diagnostics per type, per service, per 24 hours. This applies independently to each diagnostic type (BGP Peering Test, Routes, Advertised-Routes, MAC Address).
Info

Diagnostics are also available programmatically through the OVHcloud API under the /ovhCloudConnect/{serviceName}/diagnostic/... endpoints. Refer to the API console for the full list.

Key metrics to watch

Key metrics to watch

Critical alerts (set these up immediately)

AlertTriggerAction
Link downPhysical port state changes to "down"Check cross-connect, SFP, and contact data centre or provider
BGP session downBGP session state changes from "Established"Check router configuration, peer reachability, and firewall rules
High bandwidth usageThroughput exceeds 80% of provisioned capacityPlan a bandwidth upgrade or optimise traffic
Latency spikeRTT increases significantly above baselineRun traceroute and check for congestion or routing changes
Prefix count changeUnexpected increase or decrease in received/sent prefixesInvestigate route leaks or configuration changes

Monitoring commands on your router

Cisco IOS

show interfaces GigabitEthernet0/0
show ip bgp summary
show ip bgp neighbors 192.0.2.1 received-routes
show ip bgp neighbors 192.0.2.1 advertised-routes
show ip route bgp

Juniper JunOS

show interfaces terse
show bgp summary
show route receive-protocol bgp 192.0.2.1
show route advertising-protocol bgp 192.0.2.1
show route protocol bgp

Best practices

  • Monitor from both sides — Check metrics on your router and in the OVHcloud Control Panel.
  • Baseline your metrics — Record normal bandwidth, latency, and prefix counts so you can detect anomalies.
  • Automate alerting — Don't rely on manual checks. Set up automated notifications for critical events.
  • Review regularly — Check monitoring dashboards weekly to spot trends (growing bandwidth, increasing latency).
  • Test failover — If you have a Multi-AZ setup, periodically test failover and verify that monitoring detects the switch.

What's next?

Go further

For training or technical assistance implementing our solutions, contact your sales representative or visit our Professional Services page to request a quote and have your project analyzed by our experts.

Join our community of users.

Esta página foi útil?