Objective

Before ordering OVHcloud Connect, review the requirements below to ensure your environment is ready. Also be aware of the current limitations to plan your implementation effectively.

General

Requirements

• A valid OVHcloud account with billing set up.
• Sufficient permissions to manage network services (Network / vRack).
• A vRack service provisioned (or ready to be created) to associate with OVHcloud Connect.
• You (or your network team) should be familiar with basic IP networking (subnets, routing), BGP concepts, VLAN configuration

Limits

• An OVHcloud Connect service can be associated to one vRack only.
• Maximum number of OVHcloud Connect services per PoP and per vRack: 16.
• Maximum MTU (Jumbo frame): up to 9000 bytes

OVHcloud Connect Direct

Requirements

Administrative requirements

• Access to a co-location facility where OVHcloud has a PoP (see PoP Locations & Regions).
• Ability to order a cross-connect inside the data centre (or arrange one through the facility operator).

Technical requirements

• Your equipment interface should be supported (refer to below table).

• Auto-negotiation shall be disabled (not supported).

Limits

Layer 2 mode

• The number of client-side MAC addresses is limited to 512 per port.

• The maximum bandwidth is 10Gb per port.

• Only one OVHcloud Connect Direct Layer 2 can be attached per vRack.

  • This mode does not support redundant PoP architectures.
  • You may deploy redundant links in the same PoP by enabling LACP.

• The following features are not supported:

  • 802.1p CoS-based
  • DCBX and related protocols (802.1Qbb, 802.1Qaz, 802.1Qau)
  • TRILL, SPF and FabricPath
  • FCoE
  • Spanning Tree
  • IGMP and Multicast
  • EtherChannel, PaGP for aggregation

Layer 3 mode

For OVHcloud Connect Direct Layer 3, see the Layer 3 section below.

OVHcloud Connect Provider

Requirements

• A contract with a supported provider (see Providers).
• The provider must have a presence at your chosen OVHcloud PoP.

Limits

Layer 3 mode

OVHcloud Connect Provider is always a Layer 3 network service. See the Layer 3 section below.

Layer 3 mode

Limits

• Maximum one BGP session between your equipment and the OVHcloud Point of Presence router (no eBGP Multihop). More details in the Configure OCC L3 with BGP.

• Each Availability Zone supports up to 4 BGP peers. More details in the Set up your vRack network.

• Up to 100 prefixes can be announced per BGP session.

• The following features are not supported:

  • IPv6
  • Any QoS mechanism
  • 802.1q tag
  • Multi-VRF
  • eBGP Multi-Hop
  • iBGP
  • Static routing in PoP configuration

What's next?

• Jump to the Quick Start: Direct Connection or Quick Start: Provider Connection

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.