|
| 1 | +--- |
| 2 | +title: How to initiate a diagnostic for OVHcloud Connect from the OVHcloud Control Panel |
| 3 | +excerpt: Find out how to get a status report of your OVHcloud Connect services |
| 4 | +updated: 2025-04-10 |
| 5 | +--- |
| 6 | + |
| 7 | +## Objective |
| 8 | + |
| 9 | +With OVHcloud Connect, you can link your company network to your private OVHcloud vRack network, without creating a VPN tunnel through the internet. This will give you a quicker, more stable connection with guaranteed bandwidth. |
| 10 | + |
| 11 | +**This guide will show you how to get a status report of your OVHcloud Connect services via the OVHcloud Control Panel.** |
| 12 | + |
| 13 | + |
| 14 | +## Requirements |
| 15 | + |
| 16 | +- an [OVHcloud Connect solution](https://www.ovhcloud.com/en-gb/network-security/ovhcloud-connect/) with a valid POP configuration |
| 17 | + |
| 18 | +## List of available diagnostics |
| 19 | + |
| 20 | +### Layer 3 mode |
| 21 | + |
| 22 | +- **Default**: Fetches the BGP session states and all related information |
| 23 | +- **Routes**: Fetches the routing table learned by OVHcloud via BGP |
| 24 | +- **Advertised-Routes**: Fetches the routing table advertised by OVHcloud via BGP |
| 25 | + |
| 26 | +### Layer 2 mode |
| 27 | + |
| 28 | +- ***Ask for access to an OCC service which can use layer 2 mode, or simply the list of available diagnostics on this mode*** |
| 29 | + |
| 30 | +## Instructions |
| 31 | + |
| 32 | +In your OVHcloud Control Panel, in the Network section, you can find the list of your OVHcloud Connect services. |
| 33 | + |
| 34 | +{.thumbnail} |
| 35 | + |
| 36 | +Open the service for which you want to get a diagnosis: |
| 37 | + |
| 38 | +{.thumbnail} |
| 39 | + |
| 40 | +At the bottom of the "POP Configuration" panel, you will find a segment named "Diagnostic POP", and an ellipsis **(...)** button. Click it, and then select "BGP Peering Test": |
| 41 | + |
| 42 | +{.thumbnail} |
| 43 | + |
| 44 | +A window will open. Select the type of diagnostics you wish to use, and click "launch diagnostic": |
| 45 | + |
| 46 | +{.thumbnail} |
| 47 | + |
| 48 | +You can now access the list of your diagnostics by opening the "Diagnostics" tab. |
| 49 | + |
| 50 | +{.thumbnail} |
| 51 | + |
| 52 | +Each diagnostic is referred to using an ID and a timecode. |
| 53 | +You can read the contents of the diagnostics by clicking on the ellipsis located to the right of each one listed. You can select either "See result" to have a window open with the contents of the desired diagnostic, or "Download result" to get a *.txt* file with the same contents. |
| 54 | + |
| 55 | +{.thumbnail} |
| 56 | + |
| 57 | +## Limits |
| 58 | + |
| 59 | +- **Retention time of diagnostics**: You can only view diagnostics you have initiated **during the past seven days.** We recommend you download them and properly archive them, in case you need future access. |
| 60 | + |
| 61 | +- **Maximum number of diagnostics**: On a 24 hour period, you can initiate a maximum of 10 diagnostics per type of diagnostic, and per service. For example, if you have two OVHcloud Connect services configured on your OVHcloud Control Panel, both configured in Layer 3 mode, you can theoretically launch 10 of each diagnostic type per service, for a total of 60. |
| 62 | +<br> ***Maybe remove this*** This limit has been set in order to restrict the amount of resources used by the OVHcloud infrastructures, as the diagnostics are launched in real-time. |
0 commit comments