Skip to content

Commit a6d1727

Browse files
Y0CossY0Coss
authored
Merge pull request #7683 from ovh/sa-bgp-guides-2
BGP diagrams + clarity update
2 parents 4163f30 + 59b9c50 commit a6d1727

17 files changed

+60
-60
lines changed

‎pages/network/bgp_service/bgp_service_config/guide.de-de.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.en-asia.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.en-au.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.en-ca.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.en-gb.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.en-ie.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.en-sg.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.en-us.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.es-es.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

‎pages/network/bgp_service/bgp_service_config/guide.es-us.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: BGP Service configuration
33
excerpt: By using BGP Service, you gain full control over your routing policies and network resilience. Follow this guide to set up and optimize your BGP sessions
4-
updated: 2025-03-07
4+
updated: 2025-03-27
55
---
66

77
## Objective
@@ -57,9 +57,9 @@ You need to provide us with the following parameters so that we can configure th
5757
| :--- | :--- | :--- | :--- |
5858
| Location | RBX | The location on which to deliver the service | |
5959
| vRack ID | 937 | vRack ID on which the BGP sessions will run | |
60-
| BYOIP | Y | IP block coming from the customer | |
61-
| IP block | 198.51.100.0/24 | The IP block to be announced | Allowed range size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported range (/19 to /24) <br>&bull; IPv6 (/56) |
62-
| Private Subnet | 10.0.0.0 | Reserved subnet for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. Netmask should be /28 | |
60+
| BYOIP | Y | IP prefix coming from the customer | |
61+
| IP prefix | 198.51.100.0/24 | The public IP prefix to be used. <br> Subsets of this prefix may be announced: <br>&bull; For IPv4, any subset up to /32 <br>&bull; For IPv6, any subset up to /64 | Allowed prefix size: <br>&bull; OVHcloud IP (/24 to /30) <br>&bull; BYOIP imported prefix (/19 to /24) <br>&bull; IPv6 (/56) |
62+
| Private prefix | 10.0.0.0 | Reserved prefix for BGP peer IPs <br> The 4 last addresses will be used by OVHcloud for OVHcloud side BGP peers. | IPv4: Netmask /28 <br> IPv6: Netmask /124 |
6363
| Peering IP 1 | 10.0.0.1 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6464
| Peering IP 2 | 10.0.0.2 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |
6565
| Peering IP 3 | 10.0.0.3 | Customer IP should be explicitly specified by customer (for OVHcloud-side monitoring) | |

0 commit comments

Comments
 (0)