From 70593e8bf8ec40906aeed48b293af2460ed92e6b Mon Sep 17 00:00:00 2001 From: Slimane ALI Date: Fri, 12 Sep 2025 01:39:07 +0200 Subject: [PATCH 1/3] ESXi 8 reintroduction + updates Guids detailing the installation and configuration of ESXi have been updated to better reflect ESXi 8, as it is being reintroduced starting on the 15th of September 2025. The "End of Support" guide has thus been removed, and disclaimers about the introduction also have been added to the existing guides. The ESXi partitioning guide has been renamed to reflect that it both refers to the installation of ESXi and the partitioning necessary for that installation. --- .../esxi-end-of-support/guide.de-de.md | 37 ------ .../esxi-end-of-support/guide.en-asia.md | 33 ----- .../esxi-end-of-support/guide.en-au.md | 33 ----- .../esxi-end-of-support/guide.en-ca.md | 33 ----- .../esxi-end-of-support/guide.en-gb.md | 33 ----- .../esxi-end-of-support/guide.en-ie.md | 33 ----- .../esxi-end-of-support/guide.en-sg.md | 33 ----- .../esxi-end-of-support/guide.en-us.md | 33 ----- .../esxi-end-of-support/guide.es-es.md | 37 ------ .../esxi-end-of-support/guide.es-us.md | 37 ------ .../esxi-end-of-support/guide.fr-ca.md | 33 ----- .../esxi-end-of-support/guide.fr-fr.md | 33 ----- .../esxi-end-of-support/guide.it-it.md | 37 ------ .../esxi-end-of-support/guide.pl-pl.md | 37 ------ .../esxi-end-of-support/guide.pt-pt.md | 37 ------ .../esxi-end-of-support/meta.yaml | 2 - .../esxi-hardening/guide.en-gb.md | 13 +- .../esxi-hardening/guide.fr-fr.md | 11 ++ .../esxi-partitioning/guide.en-gb.md | 53 +++++--- .../esxi-partitioning/guide.fr-fr.md | 115 +++++++++++------- 20 files changed, 131 insertions(+), 582 deletions(-) delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.de-de.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-asia.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-au.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ca.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-gb.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ie.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-sg.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-us.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-es.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-us.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-ca.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-fr.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.it-it.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pl-pl.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pt-pt.md delete mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/meta.yaml diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.de-de.md deleted file mode 100644 index 88e4dae440a..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.de-de.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: VMware ESXi auf OVHcloud Dedicated Servern - End of Support -excerpt: End of Support für VMware Free vSphere Hypervisor (ESXi) auf Dedicated Servern bei OVHcloud -updated: 2024-09-13 ---- - -> [!primary] -> Diese Übersetzung wurde durch unseren Partner SYSTRAN automatisch erstellt. In manchen Fällen können ungenaue Formulierungen verwendet worden sein, z.B. bei der Beschriftung von Schaltflächen oder technischen Details. Bitte ziehen Sie im Zweifelsfall die englische oder französische Fassung der Anleitung zu Rate. Möchten Sie mithelfen, diese Übersetzung zu verbessern? Dann nutzen Sie dazu bitte den Button "Beitragen" auf dieser Seite. -> - -## VMware ESXi - End of Support - -Im Zuge der Übernahme von VMware durch Broadcom entschied Broadcom, die allgemeine Verfügbarkeit des Free vSphere Hypervisor (ESXi) einzustellen. Seit dem 6. Juni 2024 werden daher alle ESXi Images aus dem Katalog an Betriebssystem-Templates für unsere Bare Metal Dedicated Server entfernt. Diese Änderung hat keine Auswirkungen auf Ihre Server, die derzeit ESXi Images verwenden. Sie können Ihren bestehenden Server jedoch nicht neu installieren oder einen neuen Server mit einem der zuvor von OVHcloud bereitgestellten ESXi Templates installieren. - -> [!primary] -> Weitere Informationen zur Entscheidung von Broadcom, die allgemeine Verfügbarkeit seiner vSphere Free Edition Images zu beenden, finden Sie in diesem Knowledge Base-Artikel: . - -Obwohl es technisch möglich sein kann, ESXi auf unseren Dedicated Servern zu installieren, können wir keine Hilfen oder Support bei der Konfiguration oder dem Betrieb von VMware ESXi anbieten. Wir empfehlen Ihnen, einen der von uns unterstützten Hypervisor zu verwenden, um die bestmögliche Benutzererfahrung zu gewährleisten. - -Wenn Sie einen Hypervisor für die Verwendung mit unseren Dedicated Servern benötigen, empfehlen wir Ihnen die Verwendung eines der folgenden: - -- Proxmox VE -- Microsoft Hyper-V - -Wir empfehlen Ihnen als Alternative auch die [OVHcloud Hosted Private Cloud Angebote](/links/hosted-private-cloud/hosted-private-cloud) in Betracht zu ziehen. - -## Unsere Hilfen zu ESXi - -- [ESXi Dedicated Server absichern](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Server - ESXi-Partitionierung](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) (EN) -- [ESXi Dedicated Server - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) (EN) - -## Weiterführende Informationen - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) (EN) - -Treten Sie unserer [User Community](/links/community) bei. diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-asia.md deleted file mode 100644 index a8f223a5082..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-asia.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi on OVHcloud Dedicated Servers - End of Support" -excerpt: "Notification of End-of-Support for Vmware Free vSphere Hypervisor (ESXi) on OVHcloud Dedicated Servers" -updated: 2024-09-13 ---- - -## VMware ESXi End of Support - -Due to Broadcom’s acquisition of VMware, Broadcom has decided to end the general availability of its Free vSphere Hypervisor (ESXi). Since June 6, 2024, all ESXi images have been removed from our catalog of operating system models for our Bare Metal Dedicated Servers. However, this change will not affect your servers currently using ESXi images. However, you will not be able to reinstall your current server or install a new server using any of the ESXi templates previously provided by OVHcloud. - -> [!primary] -> For more information on Broadcom's decision to end the general availability of its vSphere Free Edition images, please see its Knowledge Base article: . - -Although it may be technically feasible to install ESXi on our dedicated servers, we cannot assist or support the configuration or operation of VMware ESXi. We recommend using one of the hypervisors we officially support to ensure the best possible user experience. - -If you are looking for a hypervisor to use with our dedicated servers, we recommend using one of the following: - -- Proxmox VE -- Microsoft Hyper-V - -We also recommend considering [OVHcloud Hosted Private Cloud solutions](/links/hosted-private-cloud/hosted-private-cloud). - -## Our guides on ESXi - -- [Manage and secure your ESXi dedicated server from the outset](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Servers - ESXi partitioning](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [ESXi Dedicated Servers - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) - -## Go further - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) - -Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-au.md deleted file mode 100644 index a8f223a5082..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-au.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi on OVHcloud Dedicated Servers - End of Support" -excerpt: "Notification of End-of-Support for Vmware Free vSphere Hypervisor (ESXi) on OVHcloud Dedicated Servers" -updated: 2024-09-13 ---- - -## VMware ESXi End of Support - -Due to Broadcom’s acquisition of VMware, Broadcom has decided to end the general availability of its Free vSphere Hypervisor (ESXi). Since June 6, 2024, all ESXi images have been removed from our catalog of operating system models for our Bare Metal Dedicated Servers. However, this change will not affect your servers currently using ESXi images. However, you will not be able to reinstall your current server or install a new server using any of the ESXi templates previously provided by OVHcloud. - -> [!primary] -> For more information on Broadcom's decision to end the general availability of its vSphere Free Edition images, please see its Knowledge Base article: . - -Although it may be technically feasible to install ESXi on our dedicated servers, we cannot assist or support the configuration or operation of VMware ESXi. We recommend using one of the hypervisors we officially support to ensure the best possible user experience. - -If you are looking for a hypervisor to use with our dedicated servers, we recommend using one of the following: - -- Proxmox VE -- Microsoft Hyper-V - -We also recommend considering [OVHcloud Hosted Private Cloud solutions](/links/hosted-private-cloud/hosted-private-cloud). - -## Our guides on ESXi - -- [Manage and secure your ESXi dedicated server from the outset](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Servers - ESXi partitioning](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [ESXi Dedicated Servers - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) - -## Go further - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) - -Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ca.md deleted file mode 100644 index a8f223a5082..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ca.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi on OVHcloud Dedicated Servers - End of Support" -excerpt: "Notification of End-of-Support for Vmware Free vSphere Hypervisor (ESXi) on OVHcloud Dedicated Servers" -updated: 2024-09-13 ---- - -## VMware ESXi End of Support - -Due to Broadcom’s acquisition of VMware, Broadcom has decided to end the general availability of its Free vSphere Hypervisor (ESXi). Since June 6, 2024, all ESXi images have been removed from our catalog of operating system models for our Bare Metal Dedicated Servers. However, this change will not affect your servers currently using ESXi images. However, you will not be able to reinstall your current server or install a new server using any of the ESXi templates previously provided by OVHcloud. - -> [!primary] -> For more information on Broadcom's decision to end the general availability of its vSphere Free Edition images, please see its Knowledge Base article: . - -Although it may be technically feasible to install ESXi on our dedicated servers, we cannot assist or support the configuration or operation of VMware ESXi. We recommend using one of the hypervisors we officially support to ensure the best possible user experience. - -If you are looking for a hypervisor to use with our dedicated servers, we recommend using one of the following: - -- Proxmox VE -- Microsoft Hyper-V - -We also recommend considering [OVHcloud Hosted Private Cloud solutions](/links/hosted-private-cloud/hosted-private-cloud). - -## Our guides on ESXi - -- [Manage and secure your ESXi dedicated server from the outset](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Servers - ESXi partitioning](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [ESXi Dedicated Servers - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) - -## Go further - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) - -Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-gb.md deleted file mode 100644 index 1c11375bb71..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-gb.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi on OVHcloud Dedicated Servers - End of Support" -excerpt: "Notification of End-of-Support for Vmware Free vSphere Hypervisor (ESXi) on OVHcloud Dedicated Servers" -updated: 2024-09-13 ---- - -## VMware ESXi End of Support - -Due to Broadcom’s acquisition of VMware, Broadcom has decided to end the general availability of its Free vSphere Hypervisor (ESXi). Since June 6, 2024, all ESXi images have been removed from our catalog of operating system models for our Bare Metal Dedicated Servers. However, this change will not affect your servers currently using ESXi images. However, you will not be able to reinstall your current server or install a new server using any of the ESXi templates previously provided by OVHcloud. - -> [!primary] -> For more information on Broadcom's decision to end the general availability of its vSphere Free Edition images, please see its Knowledge Base article: . - -Although it may be technically feasible to install ESXi on our dedicated servers, we cannot assist or support the configuration or operation of VMware ESXi. We recommend using one of the hypervisors we officially support to ensure the best possible user experience. - -If you are looking for a hypervisor to use with our dedicated servers, we recommend using one of the following: - -- Proxmox VE -- Microsoft Hyper-V - -We also recommend considering [OVHcloud Hosted Private Cloud solutions](/links/hosted-private-cloud/hosted-private-cloud). - -## Our guides on ESXi - -- [Manage and secure your ESXi dedicated server from the outset](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Servers - ESXi partitioning](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [ESXi Dedicated Servers - FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi) - -## Go further - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) - -Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ie.md deleted file mode 100644 index a8f223a5082..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-ie.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi on OVHcloud Dedicated Servers - End of Support" -excerpt: "Notification of End-of-Support for Vmware Free vSphere Hypervisor (ESXi) on OVHcloud Dedicated Servers" -updated: 2024-09-13 ---- - -## VMware ESXi End of Support - -Due to Broadcom’s acquisition of VMware, Broadcom has decided to end the general availability of its Free vSphere Hypervisor (ESXi). Since June 6, 2024, all ESXi images have been removed from our catalog of operating system models for our Bare Metal Dedicated Servers. However, this change will not affect your servers currently using ESXi images. However, you will not be able to reinstall your current server or install a new server using any of the ESXi templates previously provided by OVHcloud. - -> [!primary] -> For more information on Broadcom's decision to end the general availability of its vSphere Free Edition images, please see its Knowledge Base article: . - -Although it may be technically feasible to install ESXi on our dedicated servers, we cannot assist or support the configuration or operation of VMware ESXi. We recommend using one of the hypervisors we officially support to ensure the best possible user experience. - -If you are looking for a hypervisor to use with our dedicated servers, we recommend using one of the following: - -- Proxmox VE -- Microsoft Hyper-V - -We also recommend considering [OVHcloud Hosted Private Cloud solutions](/links/hosted-private-cloud/hosted-private-cloud). - -## Our guides on ESXi - -- [Manage and secure your ESXi dedicated server from the outset](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Servers - ESXi partitioning](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [ESXi Dedicated Servers - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) - -## Go further - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) - -Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-sg.md deleted file mode 100644 index a8f223a5082..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-sg.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi on OVHcloud Dedicated Servers - End of Support" -excerpt: "Notification of End-of-Support for Vmware Free vSphere Hypervisor (ESXi) on OVHcloud Dedicated Servers" -updated: 2024-09-13 ---- - -## VMware ESXi End of Support - -Due to Broadcom’s acquisition of VMware, Broadcom has decided to end the general availability of its Free vSphere Hypervisor (ESXi). Since June 6, 2024, all ESXi images have been removed from our catalog of operating system models for our Bare Metal Dedicated Servers. However, this change will not affect your servers currently using ESXi images. However, you will not be able to reinstall your current server or install a new server using any of the ESXi templates previously provided by OVHcloud. - -> [!primary] -> For more information on Broadcom's decision to end the general availability of its vSphere Free Edition images, please see its Knowledge Base article: . - -Although it may be technically feasible to install ESXi on our dedicated servers, we cannot assist or support the configuration or operation of VMware ESXi. We recommend using one of the hypervisors we officially support to ensure the best possible user experience. - -If you are looking for a hypervisor to use with our dedicated servers, we recommend using one of the following: - -- Proxmox VE -- Microsoft Hyper-V - -We also recommend considering [OVHcloud Hosted Private Cloud solutions](/links/hosted-private-cloud/hosted-private-cloud). - -## Our guides on ESXi - -- [Manage and secure your ESXi dedicated server from the outset](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Servers - ESXi partitioning](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [ESXi Dedicated Servers - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) - -## Go further - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) - -Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-us.md deleted file mode 100644 index a8f223a5082..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.en-us.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi on OVHcloud Dedicated Servers - End of Support" -excerpt: "Notification of End-of-Support for Vmware Free vSphere Hypervisor (ESXi) on OVHcloud Dedicated Servers" -updated: 2024-09-13 ---- - -## VMware ESXi End of Support - -Due to Broadcom’s acquisition of VMware, Broadcom has decided to end the general availability of its Free vSphere Hypervisor (ESXi). Since June 6, 2024, all ESXi images have been removed from our catalog of operating system models for our Bare Metal Dedicated Servers. However, this change will not affect your servers currently using ESXi images. However, you will not be able to reinstall your current server or install a new server using any of the ESXi templates previously provided by OVHcloud. - -> [!primary] -> For more information on Broadcom's decision to end the general availability of its vSphere Free Edition images, please see its Knowledge Base article: . - -Although it may be technically feasible to install ESXi on our dedicated servers, we cannot assist or support the configuration or operation of VMware ESXi. We recommend using one of the hypervisors we officially support to ensure the best possible user experience. - -If you are looking for a hypervisor to use with our dedicated servers, we recommend using one of the following: - -- Proxmox VE -- Microsoft Hyper-V - -We also recommend considering [OVHcloud Hosted Private Cloud solutions](/links/hosted-private-cloud/hosted-private-cloud). - -## Our guides on ESXi - -- [Manage and secure your ESXi dedicated server from the outset](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Dedicated Servers - ESXi partitioning](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [ESXi Dedicated Servers - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) - -## Go further - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) - -Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-es.md deleted file mode 100644 index fe8ba8c1204..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-es.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: "VMware ESXi en los servidores dedicados OVHcloud - End of Support" -excerpt: "Notificación de fin de soporte para VMware Free vSphere Hypervisor (ESXi) en los servidores dedicados OVHcloud" -updated: 2024-09-13 ---- - -> [!primary] -> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón "Contribuir" de esta página. -> - -## VMware ESXi - End of Support - -Debido a la adquisición de VMware por parte de Broadcom, Broadcom ha decidido suspender la disponibilidad general de su hipervisor Free vSphere Hypervisor (ESXi). Desde el 6 de junio de 2024, todas las imágenes ESXi han sido eliminadas de nuestro catálogo de modelos de sistemas operativos para nuestros servidores dedicados Bare Metal. Sin embargo, este cambio no afectará a los servidores que utilicen imágenes ESXi en la actualidad. Sin embargo, no podrá reinstalar su servidor actual ni instalar un nuevo servidor utilizando uno de los modelos ESXi anteriormente proporcionados por OVHcloud. - -> [!primary] -> Para más información sobre la decisión de Broadcom de poner fin a la disponibilidad general de sus imágenes vSphere Free Edition, consulte este artículo de su KB: . - -Aunque a veces es técnicamente posible instalar ESXi en nuestros servidores dedicados, no podemos ofrecer ayuda ni soporte técnico para la configuración o el funcionamiento de VMware ESXi. Le recomendamos que utilice uno de los hipervisores admitidos oficialmente para garantizar la mejor experiencia de usuario posible. - -Si está buscando un hipervisor para utilizar con nuestros servidores dedicados, le recomendamos que utilice uno de los siguientes: - -- Proxmox VE -- Microsoft Hyper-V - -Asimismo, le recomendamos que analice las [soluciones Hosted Private Cloud de OVHcloud](/links/hosted-private-cloud/hosted-private-cloud). - -## Nuestras guías sobre ESXi - -- [Domine y proteja su servidor dedicado ESXi desde su primer inicio](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Servidores dedicados - Partición de ESXi](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [Servidores dedicados ESXi - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) (EN) - -## Más información - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) (EN) - -Interactúe con nuestra [comunidad de usuarios](/links/community). \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-us.md deleted file mode 100644 index fe8ba8c1204..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.es-us.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: "VMware ESXi en los servidores dedicados OVHcloud - End of Support" -excerpt: "Notificación de fin de soporte para VMware Free vSphere Hypervisor (ESXi) en los servidores dedicados OVHcloud" -updated: 2024-09-13 ---- - -> [!primary] -> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón "Contribuir" de esta página. -> - -## VMware ESXi - End of Support - -Debido a la adquisición de VMware por parte de Broadcom, Broadcom ha decidido suspender la disponibilidad general de su hipervisor Free vSphere Hypervisor (ESXi). Desde el 6 de junio de 2024, todas las imágenes ESXi han sido eliminadas de nuestro catálogo de modelos de sistemas operativos para nuestros servidores dedicados Bare Metal. Sin embargo, este cambio no afectará a los servidores que utilicen imágenes ESXi en la actualidad. Sin embargo, no podrá reinstalar su servidor actual ni instalar un nuevo servidor utilizando uno de los modelos ESXi anteriormente proporcionados por OVHcloud. - -> [!primary] -> Para más información sobre la decisión de Broadcom de poner fin a la disponibilidad general de sus imágenes vSphere Free Edition, consulte este artículo de su KB: . - -Aunque a veces es técnicamente posible instalar ESXi en nuestros servidores dedicados, no podemos ofrecer ayuda ni soporte técnico para la configuración o el funcionamiento de VMware ESXi. Le recomendamos que utilice uno de los hipervisores admitidos oficialmente para garantizar la mejor experiencia de usuario posible. - -Si está buscando un hipervisor para utilizar con nuestros servidores dedicados, le recomendamos que utilice uno de los siguientes: - -- Proxmox VE -- Microsoft Hyper-V - -Asimismo, le recomendamos que analice las [soluciones Hosted Private Cloud de OVHcloud](/links/hosted-private-cloud/hosted-private-cloud). - -## Nuestras guías sobre ESXi - -- [Domine y proteja su servidor dedicado ESXi desde su primer inicio](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Servidores dedicados - Partición de ESXi](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [Servidores dedicados ESXi - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) (EN) - -## Más información - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) (EN) - -Interactúe con nuestra [comunidad de usuarios](/links/community). \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-ca.md deleted file mode 100644 index 15b797d706d..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-ca.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi sur les Serveurs Dédiés OVHcloud - End of Support" -excerpt: "Notification de fin de support pour VMware Free vSphere Hypervisor (ESXi) sur les serveurs dédiés OVHcloud" -updated: 2024-09-13 ---- - -## VMware ESXi - End of Support - -En raison de l'acquisition de VMware par Broadcom, Broadcom a décidé de mettre fin à la disponibilité générale de son hyperviseur Free vSphere Hypervisor (ESXi). Depuis le 6 juin 2024, toutes les images ESXi ont été supprimés de notre catalogue de modèles de systèmes d’exploitation pour nos serveurs dédiés Bare Metal. Cette modification n'a toutefois aucun impact sur vos serveurs utilisant actuellement des images ESXi. Cependant, vous ne pourrez pas réinstaller votre serveur actuel ou installer un nouveau serveur en utilisant l'un des modèles ESXi précédemment fournis par OVHcloud. - -> [!primary] -> Pour plus d'informations sur la décision de Broadcom de mettre fin à la disponibilité générale de ses images vSphere Free Edition, veuillez consulter cet article de leur base de connaissances : . - -Bien qu'il soit parfois techniquement possible d'installer ESXi sur nos serveurs dédiés, nous ne pouvons pas apporter notre aide ou notre support pour la configuration ou le fonctionnement de VMware ESXi. Nous vous recommandons d'utiliser l'un des hyperviseurs que nous prenons en charge officiellement pour vous assurer la meilleure expérience utilisateur possible. - -Si vous êtes à la recherche d'un hyperviseur pour utiliser avec nos serveurs dédiés, nous vous recommandons d'utiliser l'un des suivants : - -- Proxmox VE -- Microsoft Hyper-V - -Nous vous conseillons d'étudier également les [offres Hosted Private Cloud proposées par OVHcloud](/links/hosted-private-cloud/hosted-private-cloud). - -## Nos guides sur ESXi - -- [Maîtriser et sécuriser votre serveur dédié ESXi dès son premier démarrage](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Serveurs Dédiés - Partitionnement d'ESXi](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [Serveurs dédiés ESXi - FAQ](https://help.ovhcloud.com/csm/fr-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056391) - -## Aller plus loin - -- [VMware by Broadcom : Nouvelles Offres et Opportunités](https://blog.ovhcloud.com/vmware-on-ovhcloud-nouvelle-offre-vcd-vcf/) - -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-fr.md deleted file mode 100644 index 64604a7483e..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.fr-fr.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: "VMware ESXi sur les Serveurs Dédiés OVHcloud - End of Support" -excerpt: "Notification de fin de support pour VMware Free vSphere Hypervisor (ESXi) sur les serveurs dédiés OVHcloud" -updated: 2024-09-13 ---- - -## VMware ESXi - End of Support - -En raison de l'acquisition de VMware par Broadcom, Broadcom a décidé de mettre fin à la disponibilité générale de son hyperviseur Free vSphere Hypervisor (ESXi). Depuis le 6 juin 2024, toutes les images ESXi ont été supprimés de notre catalogue de modèles de systèmes d’exploitation pour nos serveurs dédiés Bare Metal. Cette modification n'a toutefois aucun impact sur vos serveurs utilisant actuellement des images ESXi. Cependant, vous ne pourrez pas réinstaller votre serveur actuel ou installer un nouveau serveur en utilisant l'un des modèles ESXi précédemment fournis par OVHcloud. - -> [!primary] -> Pour plus d'informations sur la décision de Broadcom de mettre fin à la disponibilité générale de ses images vSphere Free Edition, veuillez consulter cet article de leur base de connaissances : . - -Bien qu'il soit parfois techniquement possible d'installer ESXi sur nos serveurs dédiés, nous ne pouvons pas apporter notre aide ou notre support pour la configuration ou le fonctionnement de VMware ESXi. Nous vous recommandons d'utiliser l'un des hyperviseurs que nous prenons en charge officiellement pour vous assurer la meilleure expérience utilisateur possible. - -Si vous êtes à la recherche d'un hyperviseur pour utiliser avec nos serveurs dédiés, nous vous recommandons d'utiliser l'un des suivants : - -- Proxmox VE -- Microsoft Hyper-V - -Nous vous conseillons d'étudier également les [offres Hosted Private Cloud proposées par OVHcloud](/links/hosted-private-cloud/hosted-private-cloud). - -## Nos guides sur ESXi - -- [Maîtriser et sécuriser votre serveur dédié ESXi dès son premier démarrage](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Serveurs Dédiés - Partitionnement d'ESXi](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) -- [Serveurs dédiés ESXi - FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi) - -## Aller plus loin - -- [VMware by Broadcom : Nouvelles Offres et Opportunités](https://blog.ovhcloud.com/vmware-on-ovhcloud-nouvelle-offre-vcd-vcf/) - -Échangez avec notre [communauté d'utilisateurs](/links/community). \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.it-it.md deleted file mode 100644 index 731b8e6f6ac..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.it-it.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: "VMware ESXi sui Server Dedicati OVHcloud - End of Support" -excerpt: "Notifica di fine supporto per VMware Free vSphere Hypervisor (ESXi) sui server dedicati OVHcloud" -updated: 2024-09-13 ---- - -> [!primary] -> Questa traduzione è stata generata automaticamente dal nostro partner SYSTRAN. I contenuti potrebbero presentare imprecisioni, ad esempio la nomenclatura dei pulsanti o alcuni dettagli tecnici. In caso di dubbi consigliamo di fare riferimento alla versione inglese o francese della guida. Per aiutarci a migliorare questa traduzione, utilizza il pulsante "Contribuisci" di questa pagina. -> - -## VMware ESXi - End of Support - -A seguito dell'acquisizione di VMware da parte di Broadcom, Broadcom ha deciso di porre fine alla disponibilità generale del suo hypervisor Free vSphere Hypervisor (ESXi). Dal 6 giugno 2024, tutte le immagini ESXi sono state rimosse dal nostro catalogo di modelli di sistemi operativi per i server dedicati Bare Metal. Questa modifica non ha alcun impatto sui server che utilizzano attualmente immagini ESXi. Tuttavia, non sarà possibile reinstallare il server attuale o installare un nuovo server utilizzando uno dei modelli ESXi precedentemente forniti da OVHcloud. - -> [!primary] -> Per maggiori informazioni sulla decisione di Broadcom di interrompere la disponibilità generale delle immagini vSphere Free Edition, consulta questo articolo della knowledge base: . - -Sebbene sia tecnicamente possibile installare ESXi sui nostri server dedicati, non possiamo fornire assistenza o supporto per la configurazione o il funzionamento di VMware ESXi. È consigliabile utilizzare uno degli hypervisor ufficialmente supportati per garantire la migliore esperienza utente possibile. - -Se cerchi un hypervisor da utilizzare con i nostri server dedicati, ti consigliamo di utilizzare uno di questi: - -- Proxmox VE -- Microsoft Hyper-V - -Ti consigliamo di studiare anche le [offerte Hosted Private Cloud proposte da OVHcloud](/links/hosted-private-cloud/hosted-private-cloud). - -## Guide su ESXi - -- [Controllare e mettere in sicurezza il tuo server dedicato ESXi al primo avvio](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Server Dedicati - Partizionamento di ESXi](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) (EN) -- [Server dedicati ESXi - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) (EN) - -## Per saperne di più - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) (EN) - -Contatta la nostra [Community di utenti](/links/community). \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pl-pl.md deleted file mode 100644 index 856c49d5ecf..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pl-pl.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: "VMware ESXi na serwerach dedykowanych OVHcloud - End of Support" -excerpt: "Powiadomienie o zakończeniu wsparcia dla VMware Free vSphere Hypervisor (ESXi) na serwerach dedykowanych OVHcloud" -updated: 2024-09-13 ---- - -> [!primary] -> Tłumaczenie zostało wygenerowane automatycznie przez system naszego partnera SYSTRAN. W niektórych przypadkach mogą wystąpić nieprecyzyjne sformułowania, na przykład w tłumaczeniu nazw przycisków lub szczegółów technicznych. W przypadku jakichkolwiek wątpliwości zalecamy zapoznanie się z angielską/francuską wersją przewodnika. Jeśli chcesz przyczynić się do ulepszenia tłumaczenia, kliknij przycisk "Zgłoś propozycję modyfikacji” na tej stronie. -> - -## VMware ESXi - Dodatkowe wsparcie - -W związku z przejęciem firmy VMware przez Broadcom firma Broadcom podjęła decyzję o zakończeniu ogólnej dostępności swojego hypervisora Free vSphere Hypervisor (ESXi). Od 6 czerwca 2024 wszystkie obrazy ESXi zostały usunięte z naszego katalogu modeli systemów operacyjnych dla serwerów dedykowanych Bare Metal. Modyfikacja nie ma jednak wpływu na serwery, które aktualnie używają obrazów ESXi. Nie będziesz jednak mógł wykonać reinstalacji aktualnego serwera lub zainstalować nowego, korzystając z jednego z modeli ESXi wcześniej dostarczonych przez OVHcloud. - -> [!primary] -> Więcej informacji na temat decyzji firmy Broadcom o wyłączeniu ogólnego dostępu do obrazów vSphere Free Edition można znaleźć w tym artykule w bazie wiedzy firmy Broadcom: . - -Mimo że czasami instalacja ESXi na naszych serwerach dedykowanych jest technicznie możliwa, nie możemy zaoferować wsparcia ani pomocy w konfiguracji ani w działaniu VMware ESXi. Zalecamy korzystanie z jednego z hypervisorów, które oficjalnie obsługujemy, aby zapewnić jak najlepsze doświadczenie użytkownika. - -Jeśli szukasz hypervisora do użycia z naszymi serwerami dedykowanymi, zalecamy użycie jednego z następujących: - -- Proxmox VE -- Microsoft Hyper-V - -Warto również zapoznać się z [ofertami Hosted Private Cloud proponowanymi przez OVHcloud](/links/hosted-private-cloud/hosted-private-cloud). - -## Nasze przewodniki dotyczące ESXi - -- [Zarządzanie serwerem dedykowanym ESXi od pierwszego uruchomienia](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Serwery dedykowane - Partycjonowanie ESXi](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) (EN) -- [Serwery dedykowane ESXi - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) (EN) - -## Sprawdź również - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) (EN) - -Dołącz do [grona naszych użytkowników](/links/community). \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pt-pt.md deleted file mode 100644 index ee5ba7eaea9..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/guide.pt-pt.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -title: "VMware ESXi nos Servidores Dedicados OVHcloud - End of Support" -excerpt: "Notificação de fim de suporte para o VMware Free vSphere Hypervisor (ESXi) nos servidores dedicados OVHcloud" -updated: 2024-09-13 ---- - -> [!primary] -> Esta tradução foi automaticamente gerada pelo nosso parceiro SYSTRAN. Em certos casos, poderão ocorrer formulações imprecisas, como por exemplo nomes de botões ou detalhes técnicos. Recomendamos que consulte a versão inglesa ou francesa do manual, caso tenha alguma dúvida. Se nos quiser ajudar a melhorar esta tradução, clique em "Contribuir" nesta página. -> - -## VMware ESXi - End of Support - -Devido à aquisição da VMware pela Broadcom, a Broadcom decidiu pôr fim à disponibilidade geral do seu hypervisor Free vSphere Hypervisor (ESXi). Desde 6 de junho de 2024, todas as imagens ESXi foram eliminadas do nosso catálogo de modelos de sistemas operativos para os nossos servidores dedicados Bare Metal. No entanto, esta alteração não terá qualquer impacto nos servidores que estejam a utilizar imagens ESXi. No entanto, não poderá reinstalar o seu servidor atual ou instalar um novo servidor utilizando um dos modelos ESXi anteriormente fornecidos pela OVHcloud. - -> [!primary] -> Para mais informações acerca da decisão da Broadcom de suspender a disponibilidade geral das suas imagens vSphere Free Edition, consulte este artigo na sua Base de Dados de Conhecimento: . - -Embora, por vezes, seja tecnicamente possível instalar o ESXi nos nossos servidores dedicados, não podemos ajudar nem fornecer suporte para a configuração ou o funcionamento do VMware ESXi. Recomendamos que utilize um dos hipervisores que oficialmente lhe oferecemos para garantir a melhor experiência de utilizador possível. - -Se procura um hipervisor para trabalhar com os nossos servidores dedicados, recomendamos a utilização de um dos seguintes: - -- Proxmox VE -- Microsoft Hyper-V - -Aconselhamos que estude igualmente as [ofertas Hosted Private Cloud disponibilizadas pela OVHcloud](/links/hosted-private-cloud/hosted-private-cloud). - -## Os nossos guias sobre ESXi - -- [Controlar e proteger o seu servidor dedicado ESXi desde o primeiro arranque](/pages/bare_metal_cloud/dedicated_servers/esxi-hardening) -- [Servidores Dedicados - Particionamento do ESXi](/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning) (EN) -- [Servidores dedicados ESXi - FAQ](https://help.ovhcloud.com/csm/en-gb-dedicated-servers-esxi-faq?id=kb_article_view&sysparm_article=KB0056381) (EN) - -## Quer saber mais? - -- [VMware by Broadcom: New Offerings and Opportunities](https://blog.ovhcloud.com/vmware-by-broadcom-new-offerings-and-opportunities-vcf/) (EN) - -Fale com nossa [comunidade de utilizadores](/links/community). \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/meta.yaml b/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/meta.yaml deleted file mode 100644 index ac3a1a917b7..00000000000 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support/meta.yaml +++ /dev/null @@ -1,2 +0,0 @@ -id: 447418d1-d5f9-4976-ac31-7631f1bd45be -full_slug: dedicated-servers-esxi-end-of-support \ No newline at end of file diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md index 72c35b11573..e85bbae8243 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md @@ -4,9 +4,6 @@ excerpt: 'Discover the various ways you can effectively secure your ESXi dedicat updated: 2024-09-13 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective The purpose of this guide is to help you optimise security for your ESXi system. @@ -122,6 +119,11 @@ It is recommended that you filter legitimate access in this way: #### Manipulation via the graphical interface +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + **Services** Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. @@ -158,6 +160,11 @@ Example that only allows connections from IP 192.168.1.10: **Services** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + Disable unnecessary services: - SLP Service diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md index 387e7267943..609c6c00e7b 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md @@ -120,8 +120,14 @@ Il est donc recommandé de filtrer les accès légitimes de cette manière : > Ceci est valable également pour les accès au **shell**. > Ne prévilégiez que le strict nécessaire pour chacun de vos besoins. + #### Manipulation via l'interface graphique +> [!primary] +> +> Dans ESXi 8.0 GA et les versions ultérieures, le service SLP est renforcé, désactivé par défaut et filtré par le pare-feu ESXi. Cela signifie que vous n’avez plus besoin de le désactiver manuellement. Vous trouverez plus d’informations dans [cet article officiel du blog VMware](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) + + **Services** Cliquez sur le menu `Host`{.action} et accédez à la section `Manage`{.action} puis cliquez sur `Services`{.action}. @@ -156,6 +162,11 @@ Exemple autorisant uniquement les connexions depuis l'IP 192.168.1.10 : #### Manipulation via le shell +> [!primary] +> +> Dans ESXi 8.0 GA et les versions ultérieures, le service SLP est renforcé, désactivé par défaut et filtré par le pare-feu ESXi. Cela signifie que vous n’avez plus besoin de le désactiver manuellement. Vous trouverez plus d’informations dans [cet article officiel du blog VMware](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) + + **Services** Désactivez les services inutiles : diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md index 310ffe6f662..c84bd75ff4f 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md @@ -1,25 +1,22 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on an dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) - Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) > [!alert] @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-fr.md index 8fe16083411..92afdc0983f 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-fr.md @@ -1,27 +1,24 @@ --- -title: "Serveurs Dédiés - Partitionnement d'ESXi" -excerpt: "Utilisez l'espace client OVHcloud ou l'API OVHcloud pour personnaliser la taille de la partition système d'ESXi" -updated: 2025-04-29 +title: "Installer VMware ESXi 8 sur un serveur dédié" +excerpt: "Découvrez comment installer et configurer VMware ESXi 8 sur un serveur dédié en utilisant un template fourni par OVHcloud" +updated: 2025-09-15 --- -> [!warning] -> L'hyperviseur ESXi n'est plus supporté par OVHcloud. Retrouvez plus d'informations sur [cette page dédiée](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objectif -Avec les [serveurs dédiés OVHcloud](/links/bare-metal/bare-metal), vous pouvez [personnaliser le partitionnement](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). Cela vous donne des possibilités de configuration assez vastes lors de l'installation du système d'exploitation. ESXi ne le permet pas à cause de ses spécificités car il s'agit d'un système propriétaire UNIX avec un installateur propriétaire. Par conséquent, OVHcloud est dépendant de l'éditeur pour l'installation de l'OS. Depuis ESXi 7.0, il est possible de choisir entre 4 schémas de partitionnement prédéfinis par l'éditeur. - -**Cet article a pour objectif de vous montrer comment choisir un schéma de partitionnement dans l'[espace client OVHcloud](/links/manager) ou l'[API OVHcloud](/links/api).** - > [!primary] > -> ESXi 7.0 est souvent utilisé comme exemple sur cette page, mais la documentation est valable pour les versions 7.0 et ultérieures d'ESXi. +> Depuis le 15 septembre 2025, OVHcloud propose un template d'installation ESXi 8 pour ses serveurs dédiés. > +Avec les [serveurs dédiés OVHcloud](/links/bare-metal/bare-metal), vous pouvez [personnaliser le partitionnement](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). Cela vous donne des possibilités de configuration assez vastes lors de l'installation du système d'exploitation. ESXi ne le permet pas à cause de ses spécificités car il s'agit d'un système propriétaire UNIX avec un installateur propriétaire. Par conséquent, les installations ESXi d'OVHcloud sont conformes à la configuration définie par l'éditeur du logiciel. Depuis ESXi 7.0, il est possible de choisir entre 4 schémas de partitionnement prédéfinis. + +Ce guide a pour objectif de vous montrer comment installer ESXi 8 et sélectionner un schéma de partitionnement dans l'[espace client OVHcloud](/links/manager) ou via l'[API OVHcloud](/links/api). + ## Prérequis -- Un [serveur dédié](/links/bare-metal/bare-metal) dans votre compte OVHcloud, **prêt à être installé/réinstallé**. -- Avoir accès à l'[espace client OVHcloud](/links/manager) et/ou à l'[API OVHcloud](/links/api). +- Un [serveur dédié](/links/bare-metal/bare-metal) **prêt à être installé/réinstallé** dans votre compte OVHcloud, compatible avec les [exigences matérielles d'ESXi 8](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-hardware-requirements-upgrade.html) +- Avoir accès à l'[espace client OVHcloud](/links/manager) et/ou à l'[API OVHcloud](/links/api) > [!alert] > @@ -30,44 +27,45 @@ Avec les [serveurs dédiés OVHcloud](/links/bare-metal/bare-metal), vous pouvez ## En pratique -ESXi 7.0 introduit une [option d'amorçage permettant de configurer la taille de la partition système ESXi](https://kb.vmware.com/s/article/81166). Cette fonctionnalité a été introduite par l'éditeur car l'augmentation de la taille de la partition système pouvait poser problème, en particulier sur les machines où les disques sont de petite taille. OVHcloud propose désormais cette fonctionnalité qui est disponible aussi bien depuis l'[espace client OVHcloud](https://www.ovh.com/manager/#/dedicated/configuration) que via l'[API OVHcloud](/links/api). +ESXi 7.0 et les versions ultérieures ont introduit une [option d'amorçage permettant de configurer la taille des partitions système d'ESXi](https://kb.vmware.com/s/article/81166). Cette fonctionnalité a été introduite par l'éditeur car l'augmentation de la taille de la partition système pouvait poser problème, en particulier sur les machines avec de petits disques. OVHcloud a inclus cette fonctionnalité qui est disponible aussi bien depuis l'[espace client OVHcloud](https://www.ovh.com/manager/#/dedicated/configuration) que via l'[API OVHcloud](/links/api). -Malgré le fait que votre serveur ait plusieurs disques, l'installation d'ESXi n'est possible que sur le premier disque de la grappe de disques sélectionnée pour l'installation (voir « [API OVHcloud et installation d'un OS - Grappes de disques](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group) » ), les autres disques pouvant être configurés par la suite par l'utilisateur pour être utilisés pour stocker les machines virtuelles (voir « [Configuration du stockage d'un serveur HGR-STOR-2](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) » ). +Même si votre serveur dispose de plusieurs disques, l'installation d'ESXi utilise uniquement le premier disque du groupe de disques ciblé (voir « [API OVHcloud et installation d'un OS - Grappes de disques](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group) »). Les autres disques peuvent être configurés par la suite pour être utilisés pour les machines virtuelles (voir « [Comment ajouter un datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) »). -4 valeurs sont possibles : +Il existe 4 valeurs différentes : |Valeur|Taille Système¹|Datastore³| |---|---|---| -|`default`|130 Gio|Tout l'epace restant²| -|`min`|32 Gio|Tout l'epace restant²| -|`small`|64 Gio|Tout l'epace restant²| +|`default`|130 Gio|Tout l'espace restant²| +|`min`|32 Gio|Tout l'espace restant²| +|`small`|64 Gio|Tout l'espace restant²| |`max`|Tout l'espace disponible²|❌⁴| -¹ Seul le premier disque de la grappe de disques sélectionnée pour l'installation de l'OS.
-² Espace disque sur lequel l'OS va être installé.
-³ Un datastore est une partition de disque (parfois aussi appelée « container ») qu'ESXi va utiliser pour stocker ses machines virtuelles. Retrouvez plus de détails sur [cette documentation VMware (EN)](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-5EE84941-366D-4D37-8B7B-767D08928888.html).
-⁴ Le client pourra toujours [ajouter un datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) par la suite, mais uniquement sur les autres disques.
+¹ Sur le premier disque du groupe de disques ciblé pour l'installation de l'OS.
+² Espace sur le disque sur lequel l'OS sera installé.
+³ Un datastore est une partition de disque (parfois aussi appelée « conteneur ») qu'ESXi va utiliser pour stocker les machines virtuelles. [Plus de détails](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-5EE84941-366D-4D37-8B7B-767D08928888.html).
+⁴ Les clients peuvent toujours [ajouter un datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) par la suite sur les autres disques. -Comme vous pouvez le constater, aucun datastore n'est créé sur le premier disque lors de l'utilisation du schéma `max`. +Comme vous pouvez le constater, aucun datastore n'est créé sur le premier disque avec le schéma de partitionnement `max`. > [!primary] > > Le saviez-vous ? +> > Les solutions [VMware on OVHcloud](/links/hosted-private-cloud/vmware) sont basées sur des installations ESXi avec le schéma de partitionnement `small`. > ### Comment sélectionner le schéma de partitionnement ? -Comme vous pouvez le deviner, si le schéma n'est pas spécifié, le schéma de partitionnement `default` sera alors utilisé. +Le schéma de partitionnement `default` sera utilisé sauf si un autre est sélectionné. #### Via l'espace client OVHcloud > [!primary] > -> Cette procédure est très similaire à celle [des autres OS](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server), à l'exception qu'il n'est pas possible de sélectionner `Personnaliser la configuration des partitions`{.action} et qu'il y a une liste déroulante permettant de sélectionner le schéma de partitionnment à la quatrième et dernière étape. +> La procédure est très similaire [aux autres systèmes d'exploitation](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server), à l'exception que vous ne pouvez pas cocher la case `Personnaliser la configuration des partitions`{.action} et qu'il y a une liste déroulante pour choisir le schéma de partitionnement à la quatrième et dernière étape. > -Dans l'[espace client OVHcloud](/links/manager), sous l'onglet `Informations générales`{.action}, cliquez sur `...`{.action} en face du système d'exploitation puis cliquez sur `Installer`{.action}. +Connectez-vous à l'[espace client OVHcloud](/links/manager). Depuis l'onglet `Informations générales`{.action}, cliquez sur le bouton `...`{.action} à côté du système d'exploitation, puis cliquez sur `Installer`{.action}. ![Bouton Réinstaller](images/reinstalling-your-server-00.png){.thumbnail} @@ -80,28 +78,29 @@ Ensuite, choisissez `Virtualisation`{.action}, `UNIX`{.action} et sélectionnez > [!primary] > -> Comme vous pouvez le constater, vous ne pouvez pas cocher l'option `Personnaliser la configuration des partitions`{.action}, comme expliqué ci-dessus. +> L'option `Personnaliser la configuration des partitions`{.action} n'est pas disponible, pour les raisons expliquées ci-dessus. > -Choisissez la grappe de disques sur laquelle vous souhaitez qu'ESXi soit installé. Notez que seul le premier disque de la grappe va être utilisé pour installer le système d'exploitation. Retrouvez plus d'information dans [ce guide](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group). +Choisissez le groupe de disques sur lequel vous souhaitez qu'ESXi soit installé. Notez que seul le premier disque de ce groupe sera utilisé pour installer l'OS. Retrouvez plus d'informations dans [ce guide](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group). Cliquez sur `Suivant`{.action} pour continuer. -![Choix d'ESXi comme OS à installer](images/reinstalling-your-server-02.png){.thumbnail} +![Choix d'ESXi](images/reinstalling-your-server-02.png){.thumbnail} -Dans la liste déroulante `Schéma de partitionnement`{.action}, sélectionnez le schéma de partitionnement désiré. L'aperçu est mis à jour dès que vous basculez vers un autre schéma de partitionnement, de telle sorte que vous puissiez avoir une idée de la configuration sur votre serveur dédié. +Dans la liste déroulante `Schéma de partitionnement`{.action}, sélectionnez le schéma de partitionnement désiré. L'aperçu est mis à jour dès que vous sélectionnez un autre schéma de partitionnement, de telle sorte que vous puissiez avoir une idée de la configuration sur votre serveur dédié. -Complétez les autres détails et cliquez sur `Confirmer`{.action} afin de démarrer l'installation d'ESXi sur votre serveur dédié. +Remplissez les autres détails et cliquez sur `Confirmer`{.action} pour lancer l'installation d'ESXi sur votre serveur dédié. > [!primary] > -> Le champ `Nombre de disques partitionnés`{.action} est grisé et sa valeur est de 1 même si votre serveur dispose de plusieurs disques sur la grappe choisie, comme expliqué ci-dessus. +> Le champ `Nombre de disques partitionnés`{.action} est grisé et sa valeur est de 1, même si votre serveur dispose de plus d'un disque sur le groupe de disques ciblé pour l'installation de l'OS, comme expliqué ci-dessus. +> -![Choix du schéma de partitionnement](images/esxi-custom-scheme-00.png){.thumbnail} +![Sélection du schéma de partitionnement](images/esxi-custom-scheme-00.png){.thumbnail} #### Via l'API OVHcloud -Lorsque vous lancez une installation d'OS, vous pouvez fournir une option `partitionSchemeName` afin de spécifier le schéma de partitionnement qui sera utilisé : +Lorsque vous lancez une installation d'OS, le client peut éventuellement fournir un `partitionSchemeName` afin de spécifier le schéma de partitionnement à utiliser : > [!api] > @@ -112,14 +111,14 @@ Exemple de requête : ```json { - "operatingSystem": "esxi70_64", - "storage": [ - { - "partitioning": { - "schemeName": "small" - } - } - ] +    "operatingSystem": "esxi80_64", +    "storage": [ +        { +            "partitioning": { +                "schemeName": "small" +            } +        } +    ] } ``` @@ -130,7 +129,7 @@ Pour lister les différents schémas de partitionnement d'un template OS OVHclou > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -Exemple de retour pour `esxi70_64` : +Exemple de retour pour `esxi80_64` : ```json [ @@ -148,6 +147,17 @@ Afin d'obtenir les détails du schéma de partitionnement de manière dynamique, > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +Exemple de retour pour `default`: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + Vous pouvez utiliser l'appel API suivant afin d'obtenir le détail de chaque partition : > [!api] @@ -155,6 +165,23 @@ Vous pouvez utiliser l'appel API suivant afin d'obtenir le détail de chaque par > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +Exemple de retour pour `/bootbank`: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Aller plus loin [Option d'amorçage permettant de configurer la taille de la partition système ESXi [EN]](https://kb.vmware.com/s/article/81166) From 95283ffb0df7e608670c3a140db21394edb64182 Mon Sep 17 00:00:00 2001 From: Yoann Cosse Date: Fri, 12 Sep 2025 09:29:45 +0200 Subject: [PATCH 2/3] Proofreading + Duplication + cleanup --- .../configure-an-ipv6-on-a-vm/guide.de-de.md | 4 - .../guide.en-asia.md | 4 - .../configure-an-ipv6-on-a-vm/guide.en-au.md | 4 - .../configure-an-ipv6-on-a-vm/guide.en-ca.md | 4 - .../configure-an-ipv6-on-a-vm/guide.en-gb.md | 4 - .../configure-an-ipv6-on-a-vm/guide.en-ie.md | 4 - .../configure-an-ipv6-on-a-vm/guide.en-sg.md | 4 - .../configure-an-ipv6-on-a-vm/guide.en-us.md | 4 - .../configure-an-ipv6-on-a-vm/guide.es-es.md | 4 - .../configure-an-ipv6-on-a-vm/guide.es-us.md | 4 - .../configure-an-ipv6-on-a-vm/guide.fr-ca.md | 3 - .../configure-an-ipv6-on-a-vm/guide.fr-fr.md | 3 - .../configure-an-ipv6-on-a-vm/guide.it-it.md | 4 - .../configure-an-ipv6-on-a-vm/guide.pl-pl.md | 4 - .../configure-an-ipv6-on-a-vm/guide.pt-pt.md | 4 - .../esxi-hardening/guide.de-de.md | 198 +++++------ .../esxi-hardening/guide.en-asia.md | 17 +- .../esxi-hardening/guide.en-au.md | 17 +- .../esxi-hardening/guide.en-ca.md | 17 +- .../esxi-hardening/guide.en-gb.md | 2 +- .../esxi-hardening/guide.en-ie.md | 17 +- .../esxi-hardening/guide.en-sg.md | 17 +- .../esxi-hardening/guide.en-us.md | 307 ++++++++++++++++++ .../esxi-hardening/guide.es-es.md | 205 ++++++------ .../esxi-hardening/guide.es-us.md | 205 ++++++------ .../esxi-hardening/guide.fr-ca.md | 16 +- .../esxi-hardening/guide.fr-fr.md | 5 +- .../esxi-hardening/guide.it-it.md | 205 ++++++------ .../esxi-hardening/guide.pl-pl.md | 211 ++++++------ .../esxi-hardening/guide.pt-pt.md | 209 ++++++------ .../esxi-partitioning/guide.de-de.md | 55 +++- .../esxi-partitioning/guide.en-asia.md | 55 +++- .../esxi-partitioning/guide.en-au.md | 55 +++- .../esxi-partitioning/guide.en-ca.md | 55 +++- .../esxi-partitioning/guide.en-gb.md | 6 +- .../esxi-partitioning/guide.en-ie.md | 55 +++- .../esxi-partitioning/guide.en-sg.md | 55 +++- .../esxi-partitioning/guide.en-us.md | 55 +++- .../esxi-partitioning/guide.es-es.md | 55 +++- .../esxi-partitioning/guide.es-us.md | 55 +++- .../esxi-partitioning/guide.fr-ca.md | 115 ++++--- .../esxi-partitioning/guide.it-it.md | 55 +++- .../esxi-partitioning/guide.pl-pl.md | 55 +++- .../esxi-partitioning/guide.pt-pt.md | 55 +++- .../dedicated_servers/faq-esxi/guide.en-gb.md | 3 - .../dedicated_servers/faq-esxi/guide.fr-fr.md | 3 - .../network_bridging/guide.de-de.md | 5 - .../network_bridging/guide.en-asia.md | 5 - .../network_bridging/guide.en-au.md | 5 - .../network_bridging/guide.en-ca.md | 5 - .../network_bridging/guide.en-gb.md | 5 - .../network_bridging/guide.en-ie.md | 5 - .../network_bridging/guide.en-sg.md | 5 - .../network_bridging/guide.en-us.md | 5 - .../network_bridging/guide.es-es.md | 5 - .../network_bridging/guide.es-us.md | 5 - .../network_bridging/guide.fr-ca.md | 5 - .../network_bridging/guide.fr-fr.md | 5 - .../network_bridging/guide.it-it.md | 5 - .../network_bridging/guide.pl-pl.md | 5 - .../network_bridging/guide.pt-pt.md | 5 - pages/index.md | 3 +- 62 files changed, 1563 insertions(+), 1008 deletions(-) create mode 100644 pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-us.md diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.de-de.md index f99894a58d4..976e3307431 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.de-de.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-asia.md index d207214738b..525de618e8c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-asia.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-au.md index d207214738b..525de618e8c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-au.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ca.md index d207214738b..525de618e8c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ca.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-gb.md index d207214738b..525de618e8c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-gb.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ie.md index d207214738b..525de618e8c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-ie.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-sg.md index d207214738b..525de618e8c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-sg.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-us.md index d207214738b..525de618e8c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.en-us.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-es.md index c691942b640..5f03f1f5638 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-es.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-us.md index c691942b640..5f03f1f5638 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.es-us.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-ca.md index 47948a98491..fbed3166f48 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-ca.md @@ -25,9 +25,6 @@ Notre infrastructure vous permet également de configurer l'IPv6 sur vos machine - Avoir toutes les informations relatives à votre IPv6 (préfixe, passerelle, etc.). - Avoir des connaissances de base en SSH et en réseau. -> [!warning] -> Veuillez noter que [nous ne proposons plus Vmware EXSi en tant que système d’exploitation](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). Par conséquent, les exemples de configuration de ce guide se concentreront sur Proxmox VE et Windows Hyper-V. - ## En pratique Les sections suivantes contiennent les configurations des distributions que nous proposons actuellement et les distributions/systèmes d’exploitation les plus couramment utilisés. La première étape consiste toujours à vous connecter à votre serveur en SSH ou via une session de connexion GUI (RDP pour un serveur Windows). diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-fr.md index 47948a98491..fbed3166f48 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.fr-fr.md @@ -25,9 +25,6 @@ Notre infrastructure vous permet également de configurer l'IPv6 sur vos machine - Avoir toutes les informations relatives à votre IPv6 (préfixe, passerelle, etc.). - Avoir des connaissances de base en SSH et en réseau. -> [!warning] -> Veuillez noter que [nous ne proposons plus Vmware EXSi en tant que système d’exploitation](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). Par conséquent, les exemples de configuration de ce guide se concentreront sur Proxmox VE et Windows Hyper-V. - ## En pratique Les sections suivantes contiennent les configurations des distributions que nous proposons actuellement et les distributions/systèmes d’exploitation les plus couramment utilisés. La première étape consiste toujours à vous connecter à votre serveur en SSH ou via une session de connexion GUI (RDP pour un serveur Windows). diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.it-it.md index d21c8254f29..09366a43fea 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.it-it.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pl-pl.md index d5852f8a7cd..3913b1f0588 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pl-pl.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pt-pt.md index 35c8f266218..e00b5403b19 100644 --- a/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/configure-an-ipv6-on-a-vm/guide.pt-pt.md @@ -25,10 +25,6 @@ Our infrastructure also allows you to configure IPv6 on your virtual machines. - You must have all the information related to your IPv6 (prefix, gateway, etc.). - Basic knowledge of SSH and networking. -> [!warning] -> Please note that [we no longer offer VMware EXSi as an operating system](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). As a result, the configuration examples in this guide will focus on Proxmox VE and Windows Hyper-V. -> - ## Instructions The following sections contain the configurations of the distributions we currently offer and the most commonly used distributions/operating systems. The first step is always to connect to your server via SSH or via a GUI (RDP for a Windows server) connection session. diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.de-de.md index 8b50681b5ff..ead1a7fb30a 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.de-de.md @@ -1,72 +1,68 @@ --- -title: 'Sichere Verwaltung eines ESXi Dedicated Server' +title: 'Sichere Verwaltung eines ESXi Dedicated Server (EN)' excerpt: 'Erfahren Sie hier, wie Sie Ihren ESXi Server wirksam absichern' -updated: 2023-03-22 +updated: 2025-09-12 --- -> [!primary] -> Diese Übersetzung wurde durch unseren Partner SYSTRAN automatisch erstellt. In manchen Fällen können ungenaue Formulierungen verwendet worden sein, z.B. bei der Beschriftung von Schaltflächen oder technischen Details. Bitte ziehen Sie im Zweifelsfall die englische oder französische Fassung der Anleitung zu Rate. Möchten Sie mithelfen, diese Übersetzung zu verbessern? Dann nutzen Sie dazu bitte den Button "Beitragen" auf dieser Seite. -> - -## Ziel +## Objective -In dieser Anleitung erfahren Sie, wie Sie die Sicherheit Ihres ESXi Systems optimieren. +The purpose of this guide is to help you optimise security for your ESXi system. -Insbesondere wird erklärt, wie Sie: +In particular, this guide explains how to: -- Den Zugang zu ESXi auf eine bestimmte IP-Adresse oder einen bestimmten Netzwerkbereich beschränken. -- Dienste deaktivieren, um die Angriffsmöglichkeiten Ihres Servers zu verringern. +- Restrict access to your ESXi server to a specific IP address or network range. +- Disable services that increase your server's attack surface. -Wir behelfen uns dabei der nativen Funktionen von VMware, als auch der Optionen bei OVHcloud. +We will do this using the on-board features offered by VMware, as well as those offered by OVHcloud. > [!warning] > -> Kürzlich wurden ESXi Systeme Opfer von Angriffen über eine Sicherheitslücke, die über öffentliche Netzwerke ausgenutzt wurde. +> Recently, ESXi systems fell victim to a security flaw that malicious groups exploited very quickly across public networks. > -> Weitere Informationen zu diesem Angriff finden Sie in dieser [zusätzlichen FAQ (EN)](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). +> You can find more information on this attack in [an additional FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). > -### Bewährte Sicherheitspraktiken: +### Security best practices reminder -- Aktualisieren Sie Ihre ESXi Systeme regelmäßig. -- Beschränken Sie den Zugriff auf vertrauenswürdige IP-Adressen. -- Deaktivieren Sie Ports und nicht genutzte Dienste. -- Stellen Sie sicher, dass der Zugang zu Ihren Servern und Netzwerkgeräten mit sicheren Passwörtern eingeschränkt, kontrolliert und geschützt ist. -- Sichern Sie Ihre kritischen Daten auf externen Medien und Backup-Servern, die abgesichert und vom Internet isoliert sind. +- Update your ESXi systems regularly. +- Restrict access to trusted IP addresses only. +- Disable unused ports and services. +- Ensure access to your servers or network equipment is limited, controlled and protected with strong passwords. +- Back up your critical data to protected, isolated external disks and backup servers. **Optional**: -- Installieren Sie Protokollierungslösungen, um Ereignisse auf Ihren kritischen Servern und Netzwerkgeräten zu überwachen. -- Konfigurieren Sie Sicherheitspakete für die Erkennung unbefugter Zugriffe und Angriffe (IPS / NIDS) und die Überwachung der Netzwerktraffic-Bandbreite. +- Set up the necessary logging solutions to monitor events on your critical servers and network equipment. +- Set up security packs for malicious action detection, intrusion detection (IPS/NIDS) and network traffic bandwidth control. -## Voraussetzungen +## Requirements -- Sie haben Zugriff auf Ihr [OVHcloud Kundencenter](/links/manager). -- Sie verfügen über einen dedizierten Server mit ESXi installiert. -- Sie haben einen separaten Dienst, der mit unserer [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) kompatibel ist, sofern Sie diese Option zur Filterung verwenden möchten. +- Access to the [OVHcloud Control Panel](/links/manager) +- A dedicated server with the ESXi solution deployed +- An offer compatible with our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) feature, if you would like to use it for filtering -## In der praktischen Anwendung +## Instructions -### Nativer Einbruchsschutz +### Native intrusion protection -Hinweis zu Definition und Funktionsprinzip: +Reminder of its definition and operating principle: > [!primary] > -> Das ESXi System verfügt über einen Sicherheitsmechanismus, der mit dem Administratorkonto verbunden ist. -> Bei mehreren fehlgeschlagenen Zugriffsversuchen wird das Administratorkonto temporär gesperrt. -> Dieser Mechanismus schützt Ihr System und verhindert so unbefugte Verbindungen. +> The ESXi system includes a security mechanism linked to the administrator account. +> This is because, in the event of several incorrect access attempts, the administrator account is temporarily locked. +> This mechanism helps protect your system from malicious connection attempts. > [!warning] > -> Wenn dieser Schutz ausgelöst wurde und Sie sich sofort mit Ihrem ESXi verbinden möchten, müssen Sie das Administratorkonto manuell entsperren. +> If this system triggers and you want to log into your ESXi immediately, you will need to manually unlock the administrator account. > -> Dazu muss der ESXi Server über das OVHcloud Kundencenter [neu gestartet werden](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#neustart-ihres-dedicated-servers). +> To do this, you will need to [reboot](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restarting-your-dedicated-server) your ESXi server via the OVHcloud Control Panel. > -Sie können die Zugrifflogs über eine SSH-Verbindung in folgenden Dateien einsehen: +You can view the access log history in the following files via SSH: -- `/var/run/log/vobd.log` enthält die Logs, die für Überwachung und Problemlösung verwendet werden können: +- `/var/run/log/vobd.log` contains the logs that can be used for monitoring and troubleshooting: ``` 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. @@ -74,94 +70,104 @@ Sie können die Zugrifflogs über eine SSH-Verbindung in folgenden Dateien einse 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535867us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. ``` -- `/var/run/log/hostd.log` enthält die Logs des ESXi Hosts (Tasks, Zugang zum WEB-Interface, etc.): +- `/var/run/log/hostd.log` contains ESXi host logs (tasks, access to the web interface, etc.): -```output +``` 2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_do_authenticate: error [login:root][error code:2] 2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_sm_authenticate: failed [error code:2] 2023-02-21T08:44:19.712Z warning hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] Rejected password for user root from xxx.xxx.xxx.xxx 2023-02-21T08:44:19.712Z info hostd[2101004] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxui-d48c-26a4] Event 175 : Cannot login root@xxx.xxx.xxx.xxx ``` -Alle Informationen sind auch über das Web-Interface verfügbar. Klicken Sie auf `Host`{.action} und gehen Sie in den Bereich `Monitor`{.action} Klicken Sie dann auf `Logs`{.action}. +All this information is also available through the web administration interface. Click the `Host`{.action} menu and navigate to the `Monitor`{.action} section, and then click `Logs`{.action}. ![interface](images/gui_logs_.png){.thumbnail} -### Die Network Firewall +### The Network Firewall solution > [!primary] > -> Zur Erinnerung: Regeln der Network Firewall werden innerhalb des OVHcloud Netzwerks nicht berücksichtigt. Die konfigurierten Regeln haben daher keine Auswirkungen auf die Verbindungen aus dem internen Netzwerk. +> As a reminder, the Network Firewall is not taken into account within the OVHcloud network. As a result, the configured rules do not affect connections from this internal network. > -Wir empfehlen, unsere Network Firewall Filterlösung zu [aktivieren und zu verwenden](/pages/bare_metal_cloud/dedicated_servers/firewall_network). -Mit dieser Lösung können Sie die legitimen Zugänge, die Sie über Ihr ESXi System eingerichtet haben, problemlos verwalten. +You can enable and use our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) filtering solution. +This solution will allow you to easily manage legitimate access, in addition to the access you have set up through your ESXi system. -Sie vermeiden es auch, Ihren Administrator-Account im Falle eines Angriffs unbeabsichtigt zu sperren. +It will also prevent you from unexpectedly locking your administrator account in the event of an attack. -Es wird daher empfohlen, die legitimen Zugänge wie folgt zu filtern: +It is recommended that you filter legitimate access in this way: -- Regel 1 (Priority 0) erlaubt es externen vertrauenswürdigen Netzwerken, Zugang zu Ihrem ESXi System zu erhalten. -- Regel 2 (Priority 1) blockiert alles weitere. +- Rule 1 (Priority 0) allows trusted external networks to access your ESXi system. +- Rule 2 (Priority 1) blocks everything else. ![Network_Firewall](images/firewall_network_.png){.thumbnail} -### Filterung unter ESXi +### Filtering in ESXi > [!primary] > -> Sie haben auch die Möglichkeit, die Zugriffe auf Ihr ESXi System über die integrierte Firewall zu filtern. -> Sie können zusätzlich ungenutzte Dienste deaktivieren. +> You can also filter access to your ESXi system with the built-in firewall. +> You can also disable unnecessary services, depending on your usage. > > [!warning] > -> Die Deaktivierung von **SSH** und **SLP** wird dringend empfohlen. -> Wenn Sie den SSH-Dienst weiterhin verwenden, minimieren Sie dessen Verwendung und die Zugriffe. -> Das gilt auch für den **Shell**-Zugang. -> Lassen Sie nur das absolut Notwendige aktiviert. +> We strongly advise disabling **SSH** and **SLP** services. +> If you still use the SSH service, restrict its use and access as much as possible. +> This also applies to **shell** access. +> Prioritise only what is strictly necessary for each of your needs. + +#### Manipulation via the graphical interface -#### Manipulation über das grafische Interface +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> -**Dienste** +**Services** -Klicken Sie auf `Host`{.action} und gehen Sie in den Bereich `Manage`{.action}. Klicken Sie dann auf `Services`{.action}. +Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. -Finden Sie in der Liste den `TSM-SSH`-Dienst und klicken Sie mit der rechten Maustaste auf die Zeile. +In the list, find the `TSM-SSH` service and right-click on the associated line. -Beenden Sie den Dienst, indem Sie auf `Stop`{.action} klicken: +Stop the service by clicking `Stop`{.action}: ![services_ssh](images/stop_service.png){.thumbnail} -Wählen Sie die `Policy` aus und ändern Sie sie entsprechend dem angezeigten Beispiel. +Select the `Policy`, then edit it as shown in the example. -Wählen Sie die Option `Start and stop manually`{.action} , um zu vermeiden, dass der Dienst beim Start des Servers aktiv wird. +Choose the `Start and stop manually`{.action} option to prevent the service from being active when the server starts. ![services_ssh](images/ssh_disabled_.png){.thumbnail} -Verwenden Sie die gleichen Einstellungen für den Dienst `slpd`: +Apply the same settings for the `slpd` service: ![services_slp](images/slpd_.png){.thumbnail} -**Firewall-Regeln** +**Firewall rules** -Klicken Sie auf das Menü `Networking`{.action} und dann auf `Firewall rules`{.action}. Wählen Sie `Edit settings`{.action} für jeden der zu schützenden Dienste aus. +Click the `Networking`{.action} menu, then `Firewall rules`{.action}, and choose `Edit settings`{.action} for each service you want to protect: ![rules](images/firewall_web_.png){.thumbnail} -Bearbeiten Sie die Regel, um nur die IP-Adressen oder Netzwerke hinzuzufügen, die Zugriff auf Ihr ESXi System haben müssen. +Edit the rule to add only IP addresses or networks that need access to your ESXi system. -Beispiel, das ausschließlich Verbindungen über IP 192.168.1.10 erlaubt: +Example that only allows connections from IP 192.168.1.10: ![custom](images/custom_fw_rule.png){.thumbnail} -#### Manipulation via Shell +#### Shell manipulation + +**Services** -**Dienste** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> -Deaktivieren Sie unnötige Dienste: +Disable unnecessary services: -- SLP +- SLP Service ```bash /etc/init.d/slpd stop @@ -169,7 +175,7 @@ esxcli network firewall ruleset set -r CIMSLP -e 0 chkconfig slpd off ``` -- SSH +- SSH Service ```bash /etc/init.d/SSH stop @@ -177,7 +183,7 @@ esxcli network firewall ruleset set -r sshServer -e 0 chkconfig SSH off ``` -Überprüfen Sie alle aktiven Dienste beim Start: +Check all active services at startup: ```bash chkconfig --list | grep on @@ -185,39 +191,39 @@ chkconfig --list | grep on

-**Firewall-Regeln** +**Firewall rules** -Bestehende Firewall-Regeln anzeigen: +View existing firewall rules: ```bash esxcli network firewall ruleset list esxcli system account list ``` -> Erläuterungen zu den Änderungen/Anpassungen der Zugangsregeln: +> Explanations for changing/adapting access rules: > -> - `vSphereClient`: Dieser Dienst entspricht dem WEB-Administrationsbereich über Port 443 (HTTPS). -> - `SSHserver`: Dieser Dienst entspricht dem SSH-Zugang über Port 22. +> - The `vSphereClient` service: This service corresponds to the web administration interface on port 443 (HTTPS). +> - The `sshServer` service: This service corresponds to SSH access on port 22. -Beispiel mit dem Dienst `vSphereClient`: +Example with the vSphereClient service: ```bash esxcli network firewall ruleset list --ruleset-id vSphereClient ``` -Stellen Sie sicher, dass die Firewall-Regel aktiv ist: +Ensure that the firewall rule is active: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --enabled true ``` -Geben Sie die Liste der für diese Regel autorisierten IPs an: +Display the list of authorised IPs for this rule: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Ergebnis: +Result: ``` Ruleset Allowed IP Addresses @@ -225,25 +231,25 @@ Ruleset Allowed IP Addresses vSphereClient All ``` -Ändern Sie den Status des Tags, indem Sie diesen deaktivieren: +Change the status of the tag by disabling it: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --allowed-all false ``` -Erlauben Sie ausschließlich die legitime IP-Adresse 192.168.1.10: +Authorise only the legitimate IP address 192.168.1.10: ```bash esxcli network firewall ruleset allowedip add --ruleset-id vSphereClient --ip-address 192.168.1.10 ``` -Überprüfen Sie das Vorhandensein der Adresse in der Zugangsliste: +Check the access list for the address: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Ergebnis: +Result: ``` Ruleset Allowed IP Addresses @@ -253,15 +259,15 @@ vSphereClient 192.168.1.10

-Wenn Sie den SSH-Dienst trotzdem verwenden möchten, erklären wir Ihnen hier, wie Sie einen Zugang über SSH-Schlüssel einrichten. +If you still want to use the SSH service, we will explain here how to set up SSH key access. -Erzeugen Sie die Schlüssel auf dem Gerät, das sich mit dem ESXi Server verbinden soll. Der Algorithmus **ECDSA** mit 521 Bit ist für maximale Sicherheit zu bevorzugen: +Generate the keys on the machine that needs to connect to the ESXi server. The 521-bit **ECDSA** algorithm should be used for maximum security: > [!warning] -> Die Authentifizierung funktioniert mit einem Schlüsselpaar: einem öffentlichen und einem privaten Schlüssel. -> Geben Sie Ihren **privaten** Schlüssel unter keinen Umständen weiter. Er verbleibt auf dem System, auf dem er generiert wurde. +> Authentication works with a key pair: one public and one private. +> Do not share your **private** key, it must remain on the machine where it was generated. -Führen Sie folgenden Befehl aus: +Run the following command: ```bash ssh-keygen -t ecdsa -b 521 -C "key-ecdsa-esxi-host" -f /path-to-my-key/key-ecdsa @@ -272,14 +278,14 @@ Generating public/private ecdsa key pair. Enter file in which to save the key (/path-to-my-key/key-ecdsa_rsa): ``` -Geben Sie ein starkes Passwort ein: +Enter a strong password: ``` Enter passphrase (empty for no passphrase): Enter same passphrase again: ``` -Nur der öffentliche Schlüssel (key-ecdsa.pub) muss auf den Servern, mit denen Sie sich verbinden möchten, vorhanden sein. +Only the public key (key-ecdsa.pub) must be sent or stored on the machines you want to connect to. ``` Your identification has been saved in /path-to-my-key/key-ecdsa. @@ -288,14 +294,14 @@ The key fingerprint is: SHA256:******************************************* key-ecdsa-esxi-host ``` -Übertragen Sie den öffentlichen Schlüssel auf Ihren ESXi Host, damit dieser als vertrauenswürdig deklariert werden kann: +Transfer the public key to your ESXi host so that it can be declared as trusted: ```bash cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys-root/authorized_keys' ``` -## Weiterführende Informationen +## Go further -Weitere Informationen zu bewährten Sicherheitsverfahren finden Sie in [dieser Anleitung von VMware](https://core.vmware.com/security-configuration-guide). +You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Für den Austausch mit unserer User Community gehen Sie auf . +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-asia.md index 11f56823fa6..fa2fca1620c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-asia.md @@ -1,12 +1,9 @@ --- title: 'Manage and secure your ESXi dedicated server from the outset' excerpt: 'Discover the various ways you can effectively secure your ESXi dedicated server' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective The purpose of this guide is to help you optimise security for your ESXi system. @@ -122,6 +119,11 @@ It is recommended that you filter legitimate access in this way: #### Manipulation via the graphical interface +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + **Services** Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. @@ -158,6 +160,11 @@ Example that only allows connections from IP 192.168.1.10: **Services** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + Disable unnecessary services: - SLP Service @@ -297,4 +304,4 @@ cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys- You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-au.md index 11f56823fa6..fa2fca1620c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-au.md @@ -1,12 +1,9 @@ --- title: 'Manage and secure your ESXi dedicated server from the outset' excerpt: 'Discover the various ways you can effectively secure your ESXi dedicated server' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective The purpose of this guide is to help you optimise security for your ESXi system. @@ -122,6 +119,11 @@ It is recommended that you filter legitimate access in this way: #### Manipulation via the graphical interface +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + **Services** Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. @@ -158,6 +160,11 @@ Example that only allows connections from IP 192.168.1.10: **Services** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + Disable unnecessary services: - SLP Service @@ -297,4 +304,4 @@ cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys- You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ca.md index 11f56823fa6..fa2fca1620c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ca.md @@ -1,12 +1,9 @@ --- title: 'Manage and secure your ESXi dedicated server from the outset' excerpt: 'Discover the various ways you can effectively secure your ESXi dedicated server' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective The purpose of this guide is to help you optimise security for your ESXi system. @@ -122,6 +119,11 @@ It is recommended that you filter legitimate access in this way: #### Manipulation via the graphical interface +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + **Services** Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. @@ -158,6 +160,11 @@ Example that only allows connections from IP 192.168.1.10: **Services** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + Disable unnecessary services: - SLP Service @@ -297,4 +304,4 @@ cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys- You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md index e85bbae8243..fa2fca1620c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-gb.md @@ -1,7 +1,7 @@ --- title: 'Manage and secure your ESXi dedicated server from the outset' excerpt: 'Discover the various ways you can effectively secure your ESXi dedicated server' -updated: 2024-09-13 +updated: 2025-09-15 --- ## Objective diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ie.md index 11f56823fa6..fa2fca1620c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-ie.md @@ -1,12 +1,9 @@ --- title: 'Manage and secure your ESXi dedicated server from the outset' excerpt: 'Discover the various ways you can effectively secure your ESXi dedicated server' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective The purpose of this guide is to help you optimise security for your ESXi system. @@ -122,6 +119,11 @@ It is recommended that you filter legitimate access in this way: #### Manipulation via the graphical interface +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + **Services** Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. @@ -158,6 +160,11 @@ Example that only allows connections from IP 192.168.1.10: **Services** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + Disable unnecessary services: - SLP Service @@ -297,4 +304,4 @@ cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys- You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-sg.md index 11f56823fa6..fa2fca1620c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-sg.md @@ -1,12 +1,9 @@ --- title: 'Manage and secure your ESXi dedicated server from the outset' excerpt: 'Discover the various ways you can effectively secure your ESXi dedicated server' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective The purpose of this guide is to help you optimise security for your ESXi system. @@ -122,6 +119,11 @@ It is recommended that you filter legitimate access in this way: #### Manipulation via the graphical interface +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + **Services** Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. @@ -158,6 +160,11 @@ Example that only allows connections from IP 192.168.1.10: **Services** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + Disable unnecessary services: - SLP Service @@ -297,4 +304,4 @@ cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys- You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Join our [community of users](/links/community). \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-us.md new file mode 100644 index 00000000000..fa2fca1620c --- /dev/null +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.en-us.md @@ -0,0 +1,307 @@ +--- +title: 'Manage and secure your ESXi dedicated server from the outset' +excerpt: 'Discover the various ways you can effectively secure your ESXi dedicated server' +updated: 2025-09-15 +--- + +## Objective + +The purpose of this guide is to help you optimise security for your ESXi system. + +In particular, this guide explains how to: + +- Restrict access to your ESXi server to a specific IP address or network range. +- Disable services that increase your server's attack surface. + +We will do this using the on-board features offered by VMware, as well as those offered by OVHcloud. + +> [!warning] +> +> Recently, ESXi systems fell victim to a security flaw that malicious groups exploited very quickly across public networks. +> +> You can find more information on this attack in [an additional FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). +> + +### Security best practices reminder + +- Update your ESXi systems regularly. +- Restrict access to trusted IP addresses only. +- Disable unused ports and services. +- Ensure access to your servers or network equipment is limited, controlled and protected with strong passwords. +- Back up your critical data to protected, isolated external disks and backup servers. + +**Optional**: + +- Set up the necessary logging solutions to monitor events on your critical servers and network equipment. +- Set up security packs for malicious action detection, intrusion detection (IPS/NIDS) and network traffic bandwidth control. + +## Requirements + +- Access to the [OVHcloud Control Panel](/links/manager) +- A dedicated server with the ESXi solution deployed +- An offer compatible with our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) feature, if you would like to use it for filtering + +## Instructions + +### Native intrusion protection + +Reminder of its definition and operating principle: + +> [!primary] +> +> The ESXi system includes a security mechanism linked to the administrator account. +> This is because, in the event of several incorrect access attempts, the administrator account is temporarily locked. +> This mechanism helps protect your system from malicious connection attempts. + +> [!warning] +> +> If this system triggers and you want to log into your ESXi immediately, you will need to manually unlock the administrator account. +> +> To do this, you will need to [reboot](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restarting-your-dedicated-server) your ESXi server via the OVHcloud Control Panel. +> + +You can view the access log history in the following files via SSH: + +- `/var/run/log/vobd.log` contains the logs that can be used for monitoring and troubleshooting: + +``` +2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. +2023-02-13T16:22:22.897Z: [GenericCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. +2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535867us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. +``` + +- `/var/run/log/hostd.log` contains ESXi host logs (tasks, access to the web interface, etc.): + +``` +2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_do_authenticate: error [login:root][error code:2] +2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_sm_authenticate: failed [error code:2] +2023-02-21T08:44:19.712Z warning hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] Rejected password for user root from xxx.xxx.xxx.xxx +2023-02-21T08:44:19.712Z info hostd[2101004] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxui-d48c-26a4] Event 175 : Cannot login root@xxx.xxx.xxx.xxx +``` + +All this information is also available through the web administration interface. Click the `Host`{.action} menu and navigate to the `Monitor`{.action} section, and then click `Logs`{.action}. + +![interface](images/gui_logs_.png){.thumbnail} + +### The Network Firewall solution + +> [!primary] +> +> As a reminder, the Network Firewall is not taken into account within the OVHcloud network. As a result, the configured rules do not affect connections from this internal network. +> + +You can enable and use our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) filtering solution. +This solution will allow you to easily manage legitimate access, in addition to the access you have set up through your ESXi system. + +It will also prevent you from unexpectedly locking your administrator account in the event of an attack. + +It is recommended that you filter legitimate access in this way: + +- Rule 1 (Priority 0) allows trusted external networks to access your ESXi system. +- Rule 2 (Priority 1) blocks everything else. + +![Network_Firewall](images/firewall_network_.png){.thumbnail} + +### Filtering in ESXi + +> [!primary] +> +> You can also filter access to your ESXi system with the built-in firewall. +> You can also disable unnecessary services, depending on your usage. +> + +> [!warning] +> +> We strongly advise disabling **SSH** and **SLP** services. +> If you still use the SSH service, restrict its use and access as much as possible. +> This also applies to **shell** access. +> Prioritise only what is strictly necessary for each of your needs. + +#### Manipulation via the graphical interface + +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + +**Services** + +Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. + +In the list, find the `TSM-SSH` service and right-click on the associated line. + +Stop the service by clicking `Stop`{.action}: + +![services_ssh](images/stop_service.png){.thumbnail} + +Select the `Policy`, then edit it as shown in the example. + +Choose the `Start and stop manually`{.action} option to prevent the service from being active when the server starts. + +![services_ssh](images/ssh_disabled_.png){.thumbnail} + +Apply the same settings for the `slpd` service: + +![services_slp](images/slpd_.png){.thumbnail} + +**Firewall rules** + +Click the `Networking`{.action} menu, then `Firewall rules`{.action}, and choose `Edit settings`{.action} for each service you want to protect: + +![rules](images/firewall_web_.png){.thumbnail} + +Edit the rule to add only IP addresses or networks that need access to your ESXi system. + +Example that only allows connections from IP 192.168.1.10: + +![custom](images/custom_fw_rule.png){.thumbnail} + +#### Shell manipulation + +**Services** + +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + +Disable unnecessary services: + +- SLP Service + +```bash +/etc/init.d/slpd stop +esxcli network firewall ruleset set -r CIMSLP -e 0 +chkconfig slpd off +``` + +- SSH Service + +```bash +/etc/init.d/SSH stop +esxcli network firewall ruleset set -r sshServer -e 0 +chkconfig SSH off +``` + +Check all active services at startup: + +```bash +chkconfig --list | grep on +``` +
+
+ +**Firewall rules** + +View existing firewall rules: + +```bash +esxcli network firewall ruleset list +esxcli system account list +``` + +> Explanations for changing/adapting access rules: +> +> - The `vSphereClient` service: This service corresponds to the web administration interface on port 443 (HTTPS). +> - The `sshServer` service: This service corresponds to SSH access on port 22. + +Example with the vSphereClient service: + +```bash +esxcli network firewall ruleset list --ruleset-id vSphereClient +``` + +Ensure that the firewall rule is active: + +```bash +esxcli network firewall ruleset set --ruleset-id vSphereClient --enabled true +``` + +Display the list of authorised IPs for this rule: + +```bash +esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient +``` + +Result: + +``` +Ruleset Allowed IP Addresses +------------- -------------------- +vSphereClient All +``` + +Change the status of the tag by disabling it: + +```bash +esxcli network firewall ruleset set --ruleset-id vSphereClient --allowed-all false +``` + +Authorise only the legitimate IP address 192.168.1.10: + +```bash +esxcli network firewall ruleset allowedip add --ruleset-id vSphereClient --ip-address 192.168.1.10 +``` + +Check the access list for the address: + +```bash +esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient +``` + +Result: + +``` +Ruleset Allowed IP Addresses +------------- -------------------- +vSphereClient 192.168.1.10 +``` +
+
+ +If you still want to use the SSH service, we will explain here how to set up SSH key access. + +Generate the keys on the machine that needs to connect to the ESXi server. The 521-bit **ECDSA** algorithm should be used for maximum security: + +> [!warning] +> Authentication works with a key pair: one public and one private. +> Do not share your **private** key, it must remain on the machine where it was generated. + +Run the following command: + +```bash +ssh-keygen -t ecdsa -b 521 -C "key-ecdsa-esxi-host" -f /path-to-my-key/key-ecdsa +``` + +``` +Generating public/private ecdsa key pair. +Enter file in which to save the key (/path-to-my-key/key-ecdsa_rsa): +``` + +Enter a strong password: + +``` +Enter passphrase (empty for no passphrase): +Enter same passphrase again: +``` + +Only the public key (key-ecdsa.pub) must be sent or stored on the machines you want to connect to. + +``` +Your identification has been saved in /path-to-my-key/key-ecdsa. +Your public key has been saved in /path-to-my-key/key-ecdsa.pub. +The key fingerprint is: +SHA256:******************************************* key-ecdsa-esxi-host +``` + +Transfer the public key to your ESXi host so that it can be declared as trusted: + +```bash +cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys-root/authorized_keys' +``` + +## Go further + +You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). + +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-es.md index d82731d9b72..69263f85679 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-es.md @@ -1,75 +1,68 @@ --- -title: 'Mantener y proteger su servidor dedicado ESXi desde el primer inicio' +title: 'Mantener y proteger su servidor dedicado ESXi desde el primer inicio (EN)' excerpt: 'Cómo proteger eficazmente su servidor dedicado ESXi' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> El hipervisor ESXi ya no es compatible con OVHcloud. Más información en [esta página dedicada](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - -> [!primary] -> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página. -> +## Objective -## Objetivo +The purpose of this guide is to help you optimise security for your ESXi system. -Esta guía explica cómo mejorar la seguridad de su sistema ESXi. +In particular, this guide explains how to: -En particular, esta guía explica cómo: +- Restrict access to your ESXi server to a specific IP address or network range. +- Disable services that increase your server's attack surface. -- Limitar el acceso a su ESXi a una dirección IP o rango de red específico; -- Desactivar servicios que aumenten la superficie de ataque del servidor. - -Para ello, no solo nos basaremos en las funciones a bordo que ofrece VMware, sino también en las que ofrece OVHcloud. +We will do this using the on-board features offered by VMware, as well as those offered by OVHcloud. > [!warning] > -> Recientemente, los sistemas ESXi han sido víctimas de un fallo que grupos malintencionados han explotado muy rápidamente a través de las redes públicas. +> Recently, ESXi systems fell victim to a security flaw that malicious groups exploited very quickly across public networks. > -> Más información sobre el ataque en [una FAQ adicional (EN)](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). +> You can find more information on this attack in [an additional FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). > -### Recordatorio de las buenas prácticas de seguridad: +### Security best practices reminder -- Actualice regularmente sus sistemas ESXi. -- Restrice el acceso solo a las direcciones IP de confianza. -- Desactive los puertos y servicios no utilizados. -- Asegúrese de que los accesos a sus servidores o sus dispositivos de red sean limitados, controlados y protegidos con contraseñas sólidas. -- Guarde sus datos críticos en discos externos y servidores de backup protegidos y aislados de internet. +- Update your ESXi systems regularly. +- Restrict access to trusted IP addresses only. +- Disable unused ports and services. +- Ensure access to your servers or network equipment is limited, controlled and protected with strong passwords. +- Back up your critical data to protected, isolated external disks and backup servers. -**Opcional**: +**Optional**: -- Ponga en marcha las soluciones de registro necesarias para controlar los eventos acaecidos en sus servidores críticos y sus dispositivos de red. -- Cree packs de seguridad para la detección de acciones maliciosas, intrusiones (IPS/NIDS) y el control del ancho de banda del tráfico de red. +- Set up the necessary logging solutions to monitor events on your critical servers and network equipment. +- Set up security packs for malicious action detection, intrusion detection (IPS/NIDS) and network traffic bandwidth control. -## Requisitos +## Requirements -- Haber iniciado sesión en el [área de cliente de OVHcloud](/links/manager). -- Tener un servidor dedicado con la solución ESXi desplegada. -- Tener contratado un servicio compatible con nuestra funcionalidad de [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) si quiere utilizarlo para filtrar. +- Access to the [OVHcloud Control Panel](/links/manager) +- A dedicated server with the ESXi solution deployed +- An offer compatible with our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) feature, if you would like to use it for filtering -## Procedimiento +## Instructions -### Protección antiintrusión nativa +### Native intrusion protection -Recordatorio de su definición y su principio de funcionamiento: +Reminder of its definition and operating principle: > [!primary] > -> El sistema ESXi incluye un mecanismo de seguridad asociado a la cuenta de administrador. -> En efecto, en caso de varios intentos de acceso erróneos, la cuenta de administrador se bloqueará temporalmente. -> Este mecanismo permite proteger su sistema y así evitar los intentos de conexiones malintencionadas. +> The ESXi system includes a security mechanism linked to the administrator account. +> This is because, in the event of several incorrect access attempts, the administrator account is temporarily locked. +> This mechanism helps protect your system from malicious connection attempts. > [!warning] > -> Si se activa este sistema y desea conectarse a su ESXi inmediatamente, deberá desbloquear manualmente la cuenta de administrador. +> If this system triggers and you want to log into your ESXi immediately, you will need to manually unlock the administrator account. > -> Para ello, deberá [reiniciar](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#reinicio-del-servidor-dedicado) el servidor ESXi desde el área de cliente de OVHcloud. +> To do this, you will need to [reboot](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restarting-your-dedicated-server) your ESXi server via the OVHcloud Control Panel. > -Puede consultar el historial de los logs de acceso en los siguientes archivos desde un intérprete de órdenes SSH: +You can view the access log history in the following files via SSH: -- `/var/run/log/vobd.log` contiene los logs que pueden utilizarse para supervisar y resolver problemas: +- `/var/run/log/vobd.log` contains the logs that can be used for monitoring and troubleshooting: ``` 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. @@ -77,7 +70,7 @@ Puede consultar el historial de los logs de acceso en los siguientes archivos de 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535867us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. ``` -- `/var/run/log/hostd.log` contiene los logs del host ESXi (tareas, acceso a la interfaz web, etc.): +- `/var/run/log/hostd.log` contains ESXi host logs (tasks, access to the web interface, etc.): ``` 2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_do_authenticate: error [login:root][error code:2] @@ -86,85 +79,95 @@ Puede consultar el historial de los logs de acceso en los siguientes archivos de 2023-02-21T08:44:19.712Z info hostd[2101004] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxui-d48c-26a4] Event 175 : Cannot login root@xxx.xxx.xxx.xxx ``` -Toda esta información también está disponible en el panel de administración web. Haga clic en el menú `Host`{.action} y acceda a la sección `Monitor`{.action} y haga clic en `Logs`{.action}. +All this information is also available through the web administration interface. Click the `Host`{.action} menu and navigate to the `Monitor`{.action} section, and then click `Logs`{.action}. -![interfaz](images/gui_logs_.png){.thumbnail} +![interface](images/gui_logs_.png){.thumbnail} -### La solución Network Firewall +### The Network Firewall solution > [!primary] > -> Le recordamos que el Network Firewall no se aplica en la red de OVHcloud. Por lo tanto, las reglas configuradas no afectan a las conexiones procedentes de esta red interna. +> As a reminder, the Network Firewall is not taken into account within the OVHcloud network. As a result, the configured rules do not affect connections from this internal network. > -Le ofrecemos activar y utilizar nuestra solución de filtrado [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network). -Esta solución le permitirá gestionar fácilmente los accesos legítimos, además de los que haya configurado a través de su sistema ESXi. +You can enable and use our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) filtering solution. +This solution will allow you to easily manage legitimate access, in addition to the access you have set up through your ESXi system. -También evitará bloquear inesperadamente su cuenta de administrador en caso de ataque. +It will also prevent you from unexpectedly locking your administrator account in the event of an attack. -Se recomienda filtrar los accesos legítimos de esta manera: +It is recommended that you filter legitimate access in this way: -- La regla 1 (Priority 0) autoriza a las redes externas de confianza a acceder al sistema ESXi. -- La regla 2 (Priority 1) bloquea todo lo demás. +- Rule 1 (Priority 0) allows trusted external networks to access your ESXi system. +- Rule 2 (Priority 1) blocks everything else. ![Network_Firewall](images/firewall_network_.png){.thumbnail} -### Filtrado en ESXi +### Filtering in ESXi > [!primary] > -> También puede filtrar los accesos al sistema ESXi a través del firewall integrado. -> En función de su uso, también podrá desactivar los servicios innecesarios. +> You can also filter access to your ESXi system with the built-in firewall. +> You can also disable unnecessary services, depending on your usage. > > [!warning] > -> Es altamente recomendable desactivar los servicios **SSH** y **SLP**. -> Si, a pesar de todo, sigue utilizando el servicio SSH, limite al máximo su uso y sus accesos. -> Esto también se aplica a los accesos al **intérprete**. -> Preste especial atención a lo estrictamente necesario para cada una de sus necesidades. +> We strongly advise disabling **SSH** and **SLP** services. +> If you still use the SSH service, restrict its use and access as much as possible. +> This also applies to **shell** access. +> Prioritise only what is strictly necessary for each of your needs. -#### Manipulación a través de la interfaz gráfica +#### Manipulation via the graphical interface -**Servicios** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + +**Services** -Haga clic en el menú `Host`{.action} y acceda a la sección `Manage`{.action} y, seguidamente, haga clic en `Services`{.action}. +Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. -Encuentre en la lista el servicio `TSM-SSH` y haga clic derecho en la línea asociada. +In the list, find the `TSM-SSH` service and right-click on the associated line. -Para el servicio, haga clic en `Stop`{.action}. +Stop the service by clicking `Stop`{.action}: ![services_ssh](images/stop_service.png){.thumbnail} -Seleccione la `Policy` y edítela como en el ejemplo que se muestra. +Select the `Policy`, then edit it as shown in the example. -Seleccione la opción `Start and stop manually`{.action} para evitar que el servicio esté activo al iniciar el servidor. +Choose the `Start and stop manually`{.action} option to prevent the service from being active when the server starts. ![services_ssh](images/ssh_disabled_.png){.thumbnail} -Aplique los mismos parámetros para el servicio `slpd`. +Apply the same settings for the `slpd` service: ![services_slp](images/slpd_.png){.thumbnail} -**Reglas de cortafuegos** +**Firewall rules** -Haga clic en el menú `Networking`{.action}, luego en `Firewall Rules`{.action} y seleccione `Edit settings`{.action} para cada uno de los servicios que desea proteger: +Click the `Networking`{.action} menu, then `Firewall rules`{.action}, and choose `Edit settings`{.action} for each service you want to protect: -![rulas](images/firewall_web_.png){.thumbnail} +![rules](images/firewall_web_.png){.thumbnail} -Configure la regla para añadir únicamente las direcciones IP o las redes que deban tener acceso al sistema ESXi. +Edit the rule to add only IP addresses or networks that need access to your ESXi system. -Ejemplo que solo autoriza las conexiones desde la IP 192.168.1.10: +Example that only allows connections from IP 192.168.1.10: ![custom](images/custom_fw_rule.png){.thumbnail} -#### Manipulación a través del intérprete de órdenes +#### Shell manipulation + +**Services** -**Servicios** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> -Desactive los servicios innecesarios: +Disable unnecessary services: -- Servicio SLP +- SLP Service ```bash /etc/init.d/slpd stop @@ -172,7 +175,7 @@ esxcli network firewall ruleset set -r CIMSLP -e 0 chkconfig slpd off ``` -- Servicio SSH +- SSH Service ```bash /etc/init.d/SSH stop @@ -180,7 +183,7 @@ esxcli network firewall ruleset set -r sshServer -e 0 chkconfig SSH off ``` -Compruebe todos los servicios activos al arrancar: +Check all active services at startup: ```bash chkconfig --list | grep on @@ -188,39 +191,39 @@ chkconfig --list | grep on

-**Reglas de cortafuegos** +**Firewall rules** -Establezca las reglas de firewall existentes: +View existing firewall rules: ```bash esxcli network firewall ruleset list esxcli system account list ``` -> Explicaciones sobre los cambios/ajustes de las reglas de acceso: +> Explanations for changing/adapting access rules: > -> - Servicio `vSphereClient`: este servicio corresponde a la interfaz web de administración del puerto 443 (HTTPS). -> - Servicio `SSHServer`: este servicio corresponde a los accesos por SSH al puerto 22. +> - The `vSphereClient` service: This service corresponds to the web administration interface on port 443 (HTTPS). +> - The `sshServer` service: This service corresponds to SSH access on port 22. -Ejemplo de servicio vSphereClient: +Example with the vSphereClient service: ```bash esxcli network firewall ruleset list --ruleset-id vSphereClient ``` -Asegúrese de que la regla de cortafuegos esté activa: +Ensure that the firewall rule is active: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --enabled true ``` -Muestra la lista de direcciones IP autorizadas para esta regla: +Display the list of authorised IPs for this rule: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Resultado: +Result: ``` Ruleset Allowed IP Addresses @@ -228,25 +231,25 @@ Ruleset Allowed IP Addresses vSphereClient All ``` -Cambie el estado de la etiqueta desactivándola: +Change the status of the tag by disabling it: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --allowed-all false ``` -Autorice exclusivamente la dirección IP legítima 192.168.1.10: +Authorise only the legitimate IP address 192.168.1.10: ```bash esxcli network firewall ruleset allowedip add --ruleset-id vSphereClient --ip-address 192.168.1.10 ``` -Compruebe la presencia de la dirección en la lista de acceso: +Check the access list for the address: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Resultado: +Result: ``` Ruleset Allowed IP Addresses @@ -256,15 +259,15 @@ vSphereClient 192.168.1.10

-Si quiere utilizar el servicio SSH, le explicamos cómo configurar un acceso por llave SSH. +If you still want to use the SSH service, we will explain here how to set up SSH key access. -Genere las llaves en la máquina que desea conectarse al servidor ESXi. Para una seguridad máxima, debe privilegiar el algoritmo **ECDSA** de 521 bits: +Generate the keys on the machine that needs to connect to the ESXi server. The 521-bit **ECDSA** algorithm should be used for maximum security: > [!warning] -> La autenticación funciona con un par de claves: una pública y otra privada. -> No comparta en ningún caso su llave **privada**, esta debe permanecer en la máquina en la que se haya generado. +> Authentication works with a key pair: one public and one private. +> Do not share your **private** key, it must remain on the machine where it was generated. -Ejecute el siguiente comando: +Run the following command: ```bash ssh-keygen -t ecdsa -b 521 -C "key-ecdsa-esxi-host" -f /path-to-my-key/key-ecdsa @@ -275,14 +278,14 @@ Generating public/private ecdsa key pair. Enter file in which to save the key (/path-to-my-key/key-ecdsa_rsa): ``` -Introduzca una contraseña sólida: +Enter a strong password: ``` Enter passphrase (empty for no passphrase): Enter same passphrase again: ``` -En las máquinas a las que quiera conectarse, solo deberá introducir la llave pública (key-ecdsa.pub). +Only the public key (key-ecdsa.pub) must be sent or stored on the machines you want to connect to. ``` Your identification has been saved in /path-to-my-key/key-ecdsa. @@ -291,14 +294,14 @@ The key fingerprint is: SHA256:******************************************* key-ecdsa-esxi-host ``` -Transfiera la llave pública al host ESXi para que pueda ser declarada de confianza: +Transfer the public key to your ESXi host so that it can be declared as trusted: ```bash cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys-root/authorized_keys' ``` -## Más información +## Go further -Para más información sobre las buenas prácticas de seguridad, consulte [esta guía](https://core.vmware.com/security-configuration-guide) de VMware. +You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-us.md index d82731d9b72..69263f85679 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.es-us.md @@ -1,75 +1,68 @@ --- -title: 'Mantener y proteger su servidor dedicado ESXi desde el primer inicio' +title: 'Mantener y proteger su servidor dedicado ESXi desde el primer inicio (EN)' excerpt: 'Cómo proteger eficazmente su servidor dedicado ESXi' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> El hipervisor ESXi ya no es compatible con OVHcloud. Más información en [esta página dedicada](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - -> [!primary] -> Esta traducción ha sido generada de forma automática por nuestro partner SYSTRAN. En algunos casos puede contener términos imprecisos, como en las etiquetas de los botones o los detalles técnicos. En caso de duda, le recomendamos que consulte la versión inglesa o francesa de la guía. Si quiere ayudarnos a mejorar esta traducción, por favor, utilice el botón «Contribuir» de esta página. -> +## Objective -## Objetivo +The purpose of this guide is to help you optimise security for your ESXi system. -Esta guía explica cómo mejorar la seguridad de su sistema ESXi. +In particular, this guide explains how to: -En particular, esta guía explica cómo: +- Restrict access to your ESXi server to a specific IP address or network range. +- Disable services that increase your server's attack surface. -- Limitar el acceso a su ESXi a una dirección IP o rango de red específico; -- Desactivar servicios que aumenten la superficie de ataque del servidor. - -Para ello, no solo nos basaremos en las funciones a bordo que ofrece VMware, sino también en las que ofrece OVHcloud. +We will do this using the on-board features offered by VMware, as well as those offered by OVHcloud. > [!warning] > -> Recientemente, los sistemas ESXi han sido víctimas de un fallo que grupos malintencionados han explotado muy rápidamente a través de las redes públicas. +> Recently, ESXi systems fell victim to a security flaw that malicious groups exploited very quickly across public networks. > -> Más información sobre el ataque en [una FAQ adicional (EN)](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). +> You can find more information on this attack in [an additional FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). > -### Recordatorio de las buenas prácticas de seguridad: +### Security best practices reminder -- Actualice regularmente sus sistemas ESXi. -- Restrice el acceso solo a las direcciones IP de confianza. -- Desactive los puertos y servicios no utilizados. -- Asegúrese de que los accesos a sus servidores o sus dispositivos de red sean limitados, controlados y protegidos con contraseñas sólidas. -- Guarde sus datos críticos en discos externos y servidores de backup protegidos y aislados de internet. +- Update your ESXi systems regularly. +- Restrict access to trusted IP addresses only. +- Disable unused ports and services. +- Ensure access to your servers or network equipment is limited, controlled and protected with strong passwords. +- Back up your critical data to protected, isolated external disks and backup servers. -**Opcional**: +**Optional**: -- Ponga en marcha las soluciones de registro necesarias para controlar los eventos acaecidos en sus servidores críticos y sus dispositivos de red. -- Cree packs de seguridad para la detección de acciones maliciosas, intrusiones (IPS/NIDS) y el control del ancho de banda del tráfico de red. +- Set up the necessary logging solutions to monitor events on your critical servers and network equipment. +- Set up security packs for malicious action detection, intrusion detection (IPS/NIDS) and network traffic bandwidth control. -## Requisitos +## Requirements -- Haber iniciado sesión en el [área de cliente de OVHcloud](/links/manager). -- Tener un servidor dedicado con la solución ESXi desplegada. -- Tener contratado un servicio compatible con nuestra funcionalidad de [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) si quiere utilizarlo para filtrar. +- Access to the [OVHcloud Control Panel](/links/manager) +- A dedicated server with the ESXi solution deployed +- An offer compatible with our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) feature, if you would like to use it for filtering -## Procedimiento +## Instructions -### Protección antiintrusión nativa +### Native intrusion protection -Recordatorio de su definición y su principio de funcionamiento: +Reminder of its definition and operating principle: > [!primary] > -> El sistema ESXi incluye un mecanismo de seguridad asociado a la cuenta de administrador. -> En efecto, en caso de varios intentos de acceso erróneos, la cuenta de administrador se bloqueará temporalmente. -> Este mecanismo permite proteger su sistema y así evitar los intentos de conexiones malintencionadas. +> The ESXi system includes a security mechanism linked to the administrator account. +> This is because, in the event of several incorrect access attempts, the administrator account is temporarily locked. +> This mechanism helps protect your system from malicious connection attempts. > [!warning] > -> Si se activa este sistema y desea conectarse a su ESXi inmediatamente, deberá desbloquear manualmente la cuenta de administrador. +> If this system triggers and you want to log into your ESXi immediately, you will need to manually unlock the administrator account. > -> Para ello, deberá [reiniciar](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#reinicio-del-servidor-dedicado) el servidor ESXi desde el área de cliente de OVHcloud. +> To do this, you will need to [reboot](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restarting-your-dedicated-server) your ESXi server via the OVHcloud Control Panel. > -Puede consultar el historial de los logs de acceso en los siguientes archivos desde un intérprete de órdenes SSH: +You can view the access log history in the following files via SSH: -- `/var/run/log/vobd.log` contiene los logs que pueden utilizarse para supervisar y resolver problemas: +- `/var/run/log/vobd.log` contains the logs that can be used for monitoring and troubleshooting: ``` 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. @@ -77,7 +70,7 @@ Puede consultar el historial de los logs de acceso en los siguientes archivos de 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535867us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. ``` -- `/var/run/log/hostd.log` contiene los logs del host ESXi (tareas, acceso a la interfaz web, etc.): +- `/var/run/log/hostd.log` contains ESXi host logs (tasks, access to the web interface, etc.): ``` 2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_do_authenticate: error [login:root][error code:2] @@ -86,85 +79,95 @@ Puede consultar el historial de los logs de acceso en los siguientes archivos de 2023-02-21T08:44:19.712Z info hostd[2101004] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxui-d48c-26a4] Event 175 : Cannot login root@xxx.xxx.xxx.xxx ``` -Toda esta información también está disponible en el panel de administración web. Haga clic en el menú `Host`{.action} y acceda a la sección `Monitor`{.action} y haga clic en `Logs`{.action}. +All this information is also available through the web administration interface. Click the `Host`{.action} menu and navigate to the `Monitor`{.action} section, and then click `Logs`{.action}. -![interfaz](images/gui_logs_.png){.thumbnail} +![interface](images/gui_logs_.png){.thumbnail} -### La solución Network Firewall +### The Network Firewall solution > [!primary] > -> Le recordamos que el Network Firewall no se aplica en la red de OVHcloud. Por lo tanto, las reglas configuradas no afectan a las conexiones procedentes de esta red interna. +> As a reminder, the Network Firewall is not taken into account within the OVHcloud network. As a result, the configured rules do not affect connections from this internal network. > -Le ofrecemos activar y utilizar nuestra solución de filtrado [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network). -Esta solución le permitirá gestionar fácilmente los accesos legítimos, además de los que haya configurado a través de su sistema ESXi. +You can enable and use our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) filtering solution. +This solution will allow you to easily manage legitimate access, in addition to the access you have set up through your ESXi system. -También evitará bloquear inesperadamente su cuenta de administrador en caso de ataque. +It will also prevent you from unexpectedly locking your administrator account in the event of an attack. -Se recomienda filtrar los accesos legítimos de esta manera: +It is recommended that you filter legitimate access in this way: -- La regla 1 (Priority 0) autoriza a las redes externas de confianza a acceder al sistema ESXi. -- La regla 2 (Priority 1) bloquea todo lo demás. +- Rule 1 (Priority 0) allows trusted external networks to access your ESXi system. +- Rule 2 (Priority 1) blocks everything else. ![Network_Firewall](images/firewall_network_.png){.thumbnail} -### Filtrado en ESXi +### Filtering in ESXi > [!primary] > -> También puede filtrar los accesos al sistema ESXi a través del firewall integrado. -> En función de su uso, también podrá desactivar los servicios innecesarios. +> You can also filter access to your ESXi system with the built-in firewall. +> You can also disable unnecessary services, depending on your usage. > > [!warning] > -> Es altamente recomendable desactivar los servicios **SSH** y **SLP**. -> Si, a pesar de todo, sigue utilizando el servicio SSH, limite al máximo su uso y sus accesos. -> Esto también se aplica a los accesos al **intérprete**. -> Preste especial atención a lo estrictamente necesario para cada una de sus necesidades. +> We strongly advise disabling **SSH** and **SLP** services. +> If you still use the SSH service, restrict its use and access as much as possible. +> This also applies to **shell** access. +> Prioritise only what is strictly necessary for each of your needs. -#### Manipulación a través de la interfaz gráfica +#### Manipulation via the graphical interface -**Servicios** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + +**Services** -Haga clic en el menú `Host`{.action} y acceda a la sección `Manage`{.action} y, seguidamente, haga clic en `Services`{.action}. +Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. -Encuentre en la lista el servicio `TSM-SSH` y haga clic derecho en la línea asociada. +In the list, find the `TSM-SSH` service and right-click on the associated line. -Para el servicio, haga clic en `Stop`{.action}. +Stop the service by clicking `Stop`{.action}: ![services_ssh](images/stop_service.png){.thumbnail} -Seleccione la `Policy` y edítela como en el ejemplo que se muestra. +Select the `Policy`, then edit it as shown in the example. -Seleccione la opción `Start and stop manually`{.action} para evitar que el servicio esté activo al iniciar el servidor. +Choose the `Start and stop manually`{.action} option to prevent the service from being active when the server starts. ![services_ssh](images/ssh_disabled_.png){.thumbnail} -Aplique los mismos parámetros para el servicio `slpd`. +Apply the same settings for the `slpd` service: ![services_slp](images/slpd_.png){.thumbnail} -**Reglas de cortafuegos** +**Firewall rules** -Haga clic en el menú `Networking`{.action}, luego en `Firewall Rules`{.action} y seleccione `Edit settings`{.action} para cada uno de los servicios que desea proteger: +Click the `Networking`{.action} menu, then `Firewall rules`{.action}, and choose `Edit settings`{.action} for each service you want to protect: -![rulas](images/firewall_web_.png){.thumbnail} +![rules](images/firewall_web_.png){.thumbnail} -Configure la regla para añadir únicamente las direcciones IP o las redes que deban tener acceso al sistema ESXi. +Edit the rule to add only IP addresses or networks that need access to your ESXi system. -Ejemplo que solo autoriza las conexiones desde la IP 192.168.1.10: +Example that only allows connections from IP 192.168.1.10: ![custom](images/custom_fw_rule.png){.thumbnail} -#### Manipulación a través del intérprete de órdenes +#### Shell manipulation + +**Services** -**Servicios** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> -Desactive los servicios innecesarios: +Disable unnecessary services: -- Servicio SLP +- SLP Service ```bash /etc/init.d/slpd stop @@ -172,7 +175,7 @@ esxcli network firewall ruleset set -r CIMSLP -e 0 chkconfig slpd off ``` -- Servicio SSH +- SSH Service ```bash /etc/init.d/SSH stop @@ -180,7 +183,7 @@ esxcli network firewall ruleset set -r sshServer -e 0 chkconfig SSH off ``` -Compruebe todos los servicios activos al arrancar: +Check all active services at startup: ```bash chkconfig --list | grep on @@ -188,39 +191,39 @@ chkconfig --list | grep on

-**Reglas de cortafuegos** +**Firewall rules** -Establezca las reglas de firewall existentes: +View existing firewall rules: ```bash esxcli network firewall ruleset list esxcli system account list ``` -> Explicaciones sobre los cambios/ajustes de las reglas de acceso: +> Explanations for changing/adapting access rules: > -> - Servicio `vSphereClient`: este servicio corresponde a la interfaz web de administración del puerto 443 (HTTPS). -> - Servicio `SSHServer`: este servicio corresponde a los accesos por SSH al puerto 22. +> - The `vSphereClient` service: This service corresponds to the web administration interface on port 443 (HTTPS). +> - The `sshServer` service: This service corresponds to SSH access on port 22. -Ejemplo de servicio vSphereClient: +Example with the vSphereClient service: ```bash esxcli network firewall ruleset list --ruleset-id vSphereClient ``` -Asegúrese de que la regla de cortafuegos esté activa: +Ensure that the firewall rule is active: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --enabled true ``` -Muestra la lista de direcciones IP autorizadas para esta regla: +Display the list of authorised IPs for this rule: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Resultado: +Result: ``` Ruleset Allowed IP Addresses @@ -228,25 +231,25 @@ Ruleset Allowed IP Addresses vSphereClient All ``` -Cambie el estado de la etiqueta desactivándola: +Change the status of the tag by disabling it: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --allowed-all false ``` -Autorice exclusivamente la dirección IP legítima 192.168.1.10: +Authorise only the legitimate IP address 192.168.1.10: ```bash esxcli network firewall ruleset allowedip add --ruleset-id vSphereClient --ip-address 192.168.1.10 ``` -Compruebe la presencia de la dirección en la lista de acceso: +Check the access list for the address: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Resultado: +Result: ``` Ruleset Allowed IP Addresses @@ -256,15 +259,15 @@ vSphereClient 192.168.1.10

-Si quiere utilizar el servicio SSH, le explicamos cómo configurar un acceso por llave SSH. +If you still want to use the SSH service, we will explain here how to set up SSH key access. -Genere las llaves en la máquina que desea conectarse al servidor ESXi. Para una seguridad máxima, debe privilegiar el algoritmo **ECDSA** de 521 bits: +Generate the keys on the machine that needs to connect to the ESXi server. The 521-bit **ECDSA** algorithm should be used for maximum security: > [!warning] -> La autenticación funciona con un par de claves: una pública y otra privada. -> No comparta en ningún caso su llave **privada**, esta debe permanecer en la máquina en la que se haya generado. +> Authentication works with a key pair: one public and one private. +> Do not share your **private** key, it must remain on the machine where it was generated. -Ejecute el siguiente comando: +Run the following command: ```bash ssh-keygen -t ecdsa -b 521 -C "key-ecdsa-esxi-host" -f /path-to-my-key/key-ecdsa @@ -275,14 +278,14 @@ Generating public/private ecdsa key pair. Enter file in which to save the key (/path-to-my-key/key-ecdsa_rsa): ``` -Introduzca una contraseña sólida: +Enter a strong password: ``` Enter passphrase (empty for no passphrase): Enter same passphrase again: ``` -En las máquinas a las que quiera conectarse, solo deberá introducir la llave pública (key-ecdsa.pub). +Only the public key (key-ecdsa.pub) must be sent or stored on the machines you want to connect to. ``` Your identification has been saved in /path-to-my-key/key-ecdsa. @@ -291,14 +294,14 @@ The key fingerprint is: SHA256:******************************************* key-ecdsa-esxi-host ``` -Transfiera la llave pública al host ESXi para que pueda ser declarada de confianza: +Transfer the public key to your ESXi host so that it can be declared as trusted: ```bash cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys-root/authorized_keys' ``` -## Más información +## Go further -Para más información sobre las buenas prácticas de seguridad, consulte [esta guía](https://core.vmware.com/security-configuration-guide) de VMware. +You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Interactúe con nuestra comunidad de usuarios en . \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-ca.md index 387e7267943..5b41890851e 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-ca.md @@ -1,12 +1,9 @@ --- title: 'Maîtriser et sécuriser votre serveur dédié ESXi dès son premier démarrage' excerpt: 'Découvrez les différents moyens vous permettant de sécuriser efficacement votre serveur dédié ESXi' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> L'hyperviseur ESXi n'est plus supporté par OVHcloud. Retrouvez plus d'informations sur [cette page dédiée](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objectif Cette documentation a pour objectif de vous accompagner pour élaborer au mieux la sécurisation de votre système ESXi. @@ -120,8 +117,14 @@ Il est donc recommandé de filtrer les accès légitimes de cette manière : > Ceci est valable également pour les accès au **shell**. > Ne prévilégiez que le strict nécessaire pour chacun de vos besoins. + #### Manipulation via l'interface graphique +> [!primary] +> +> Dans ESXi 8.0 GA et les versions ultérieures, le service SLP est renforcé, désactivé par défaut et filtré par le pare-feu ESXi. Cela signifie que vous n’avez plus besoin de le désactiver manuellement. Vous trouverez plus d’informations dans [cet article officiel du blog VMware](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) + + **Services** Cliquez sur le menu `Host`{.action} et accédez à la section `Manage`{.action} puis cliquez sur `Services`{.action}. @@ -156,6 +159,11 @@ Exemple autorisant uniquement les connexions depuis l'IP 192.168.1.10 : #### Manipulation via le shell +> [!primary] +> +> Dans ESXi 8.0 GA et les versions ultérieures, le service SLP est renforcé, désactivé par défaut et filtré par le pare-feu ESXi. Cela signifie que vous n’avez plus besoin de le désactiver manuellement. Vous trouverez plus d’informations dans [cet article officiel du blog VMware](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) + + **Services** Désactivez les services inutiles : diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md index 609c6c00e7b..5b41890851e 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.fr-fr.md @@ -1,12 +1,9 @@ --- title: 'Maîtriser et sécuriser votre serveur dédié ESXi dès son premier démarrage' excerpt: 'Découvrez les différents moyens vous permettant de sécuriser efficacement votre serveur dédié ESXi' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> L'hyperviseur ESXi n'est plus supporté par OVHcloud. Retrouvez plus d'informations sur [cette page dédiée](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objectif Cette documentation a pour objectif de vous accompagner pour élaborer au mieux la sécurisation de votre système ESXi. diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.it-it.md index 3877f7f9eea..5fab639cda0 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.it-it.md @@ -1,75 +1,68 @@ --- -title: Controllare e proteggere il vostro server dedicato ESXi dal primo avvio +title: Controllare e proteggere il vostro server dedicato ESXi dal primo avvio (EN) excerpt: Scopri i diversi modi per proteggere efficacemente il tuo server dedicato ESXi -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> L'hypervisor ESXi non è più supportato da OVHcloud. Per maggiori informazioni, visita [questa pagina dedicata](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - -> [!primary] -> Questa traduzione è stata generata automaticamente dal nostro partner SYSTRAN. I contenuti potrebbero presentare imprecisioni, ad esempio la nomenclatura dei pulsanti o alcuni dettagli tecnici. In caso di dubbi consigliamo di fare riferimento alla versione inglese o francese della guida. Per aiutarci a migliorare questa traduzione, utilizza il pulsante "Contribuisci" di questa pagina. -> +## Objective -## Obiettivo +The purpose of this guide is to help you optimise security for your ESXi system. -Questa guida ti mostra come configurare al meglio la protezione del tuo sistema ESXi. +In particular, this guide explains how to: -In particolare, questa guida ti mostra come: +- Restrict access to your ESXi server to a specific IP address or network range. +- Disable services that increase your server's attack surface. -- limitare l'accesso al tuo ESXi a un indirizzo IP o a una gamma di rete specifica; -- disattivare servizi che aumentano la superficie di attacco del tuo server. - -Ci affideremo alle funzioni embedded offerte da VMware, ma anche a quelle offerte da OVHcloud. +We will do this using the on-board features offered by VMware, as well as those offered by OVHcloud. > [!warning] > -> Di recente, i sistemi ESXi sono stati vittime di una falla che gruppi malevoli hanno sfruttato molto rapidamente attraverso le reti pubbliche. +> Recently, ESXi systems fell victim to a security flaw that malicious groups exploited very quickly across public networks. > -> Per maggiori informazioni su questo attacco, consulta [le FAQ (EN)](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). +> You can find more information on this attack in [an additional FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). > -### Best practice di sicurezza: +### Security best practices reminder -- Aggiorna regolarmente i tuoi sistemi ESXi. -- Restringi l'accesso ai soli indirizzi IP di fiducia. -- Disattiva le porte e i servizi non utilizzati. -- Assicurati che gli accessi ai tuoi server o dispositivi di rete siano limitati, controllati e protetti con password robuste. -- Salva i tuoi dati critici in dischi esterni e server di backup protetti e isolati da Internet. +- Update your ESXi systems regularly. +- Restrict access to trusted IP addresses only. +- Disable unused ports and services. +- Ensure access to your servers or network equipment is limited, controlled and protected with strong passwords. +- Back up your critical data to protected, isolated external disks and backup servers. -**Opzionale**: +**Optional**: -- Implementa le soluzioni di giornalizzazione necessarie per monitorare gli eventi verificatisi sui tuoi server critici e sui tuoi dispositivi di rete. -- Imposta pack di sicurezza per rilevare azioni malevoli, intrusioni (IPS/NIDS) e per il controllo della banda passante di traffico di rete. +- Set up the necessary logging solutions to monitor events on your critical servers and network equipment. +- Set up security packs for malicious action detection, intrusion detection (IPS/NIDS) and network traffic bandwidth control. -## Prerequisiti +## Requirements -- Avere accesso allo [Spazio Cliente OVHcloud](/links/manager) -- Disporre di un server dedicato con ESXi attivo -- Disporre di un'offerta compatibile con la funzionalità [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) per eseguire il filtraggio +- Access to the [OVHcloud Control Panel](/links/manager) +- A dedicated server with the ESXi solution deployed +- An offer compatible with our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) feature, if you would like to use it for filtering -## Procedura +## Instructions -### Protezione anti-intrusione nativa +### Native intrusion protection -Richiamo della sua definizione e del suo principio di funzionamento: +Reminder of its definition and operating principle: > [!primary] > -> Il sistema ESXi dispone di un meccanismo di sicurezza legato all’account amministratore. -> In caso di più tentativi errati di accesso, l'account amministratore viene bloccato temporaneamente. -> Questo meccanismo permette di proteggere il tuo sistema ed evitare così i tentativi di connessione malevoli. +> The ESXi system includes a security mechanism linked to the administrator account. +> This is because, in the event of several incorrect access attempts, the administrator account is temporarily locked. +> This mechanism helps protect your system from malicious connection attempts. > [!warning] > -> Se il sistema si attiva e desideri connetterti al tuo ESXi immediatamente, sarà necessario sbloccare manualmente l'account amministratore. +> If this system triggers and you want to log into your ESXi immediately, you will need to manually unlock the administrator account. > -> Per effettuare questa operazione, è necessario [riavviare](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#riavvio-del-tuo-server-dedicato) il server ESXi attraverso lo Spazio Cliente OVHcloud. +> To do this, you will need to [reboot](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restarting-your-dedicated-server) your ESXi server via the OVHcloud Control Panel. > -È possibile consultare lo storico dei log di accesso in questi file a partire da uno shell SSH: +You can view the access log history in the following files via SSH: -- `/var/run/log/vobd.log` contiene i log che possono essere utilizzati per la supervisione e la risoluzione dei problemi: +- `/var/run/log/vobd.log` contains the logs that can be used for monitoring and troubleshooting: ``` 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. @@ -77,7 +70,7 @@ Richiamo della sua definizione e del suo principio di funzionamento: 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535867us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. ``` -- `/var/run/log/hostd.log` contiene i log dell'host ESXi (task, accesso all'interfaccia WEB, ecc...): +- `/var/run/log/hostd.log` contains ESXi host logs (tasks, access to the web interface, etc.): ``` 2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_do_authenticate: error [login:root][error code:2] @@ -86,85 +79,95 @@ Richiamo della sua definizione e del suo principio di funzionamento: 2023-02-21T08:44:19.712Z info hostd[2101004] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxui-d48c-26a4] Event 175 : Cannot login root@xxx.xxx.xxx.xxx ``` -Tutte queste informazioni sono disponibili anche attraverso l'interfaccia di amministrazione Web. Clicca sul menu `Host`{.action} e accedi alla sezione `Monitor`{.action}, poi clicca su `Logs`{.action}. +All this information is also available through the web administration interface. Click the `Host`{.action} menu and navigate to the `Monitor`{.action} section, and then click `Logs`{.action}. -![interfaccia](images/gui_logs_.png){.thumbnail} +![interface](images/gui_logs_.png){.thumbnail} -### La soluzione Network Firewall +### The Network Firewall solution > [!primary] > -> Ti ricordiamo che il Network Firewall non è incluso nella rete OVHcloud. Di conseguenza, le regole configurate non influiscono sulle connessioni provenienti da questa rete interna. +> As a reminder, the Network Firewall is not taken into account within the OVHcloud network. As a result, the configured rules do not affect connections from this internal network. > -Ti proponiamo di attivare e utilizzare la nostra soluzione di filtraggio [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network). -Questa soluzione permette di gestire facilmente gli accessi legittimi, in aggiunta a quelli impostati tramite il sistema ESXi. +You can enable and use our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) filtering solution. +This solution will allow you to easily manage legitimate access, in addition to the access you have set up through your ESXi system. -In caso di attacco, eviti anche di bloccare inaspettatamente il tuo account amministratore. +It will also prevent you from unexpectedly locking your administrator account in the event of an attack. -Ti consigliamo di filtrare gli accessi legittimi in questo modo: +It is recommended that you filter legitimate access in this way: -- La regola 1 (Priority 0) autorizza reti esterne di fiducia ad accedere al tuo sistema ESXi. -- La regola 2 (Priority 1) blocca tutto il resto. +- Rule 1 (Priority 0) allows trusted external networks to access your ESXi system. +- Rule 2 (Priority 1) blocks everything else. ![Network_Firewall](images/firewall_network_.png){.thumbnail} -### Filtro con ESXi +### Filtering in ESXi > [!primary] > -> Puoi filtrare gli accessi al tuo sistema ESXi grazie al firewall integrato. -> In base all'utilizzo, è possibile disattivare anche i servizi non necessari. +> You can also filter access to your ESXi system with the built-in firewall. +> You can also disable unnecessary services, depending on your usage. > > [!warning] > -> Ti consigliamo di disattivare i servizi **SSH** e **SLP**. -> Se, nonostante tutto, continui a utilizzare il servizio SSH, ne restringi al massimo l'utilizzo e gli accessi. -> Ciò vale anche per l'accesso allo **shell**. -> Prevedibili solo allo stretto necessario per ogni tua necessità. +> We strongly advise disabling **SSH** and **SLP** services. +> If you still use the SSH service, restrict its use and access as much as possible. +> This also applies to **shell** access. +> Prioritise only what is strictly necessary for each of your needs. -#### Manipolazione tramite l'interfaccia grafica +#### Manipulation via the graphical interface -**Servizi** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + +**Services** -Clicca sul menu `Host`{.action} e accedi alla sezione `Manage`{.action}, poi clicca su `Services`{.action}. +Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. -Trova nella lista il servizio `TSM-SSH` e clicca con il tasto destro sulla linea associata. +In the list, find the `TSM-SSH` service and right-click on the associated line. -Fermate il servizio cliccando su `Stop`{.action}: +Stop the service by clicking `Stop`{.action}: ![services_ssh](images/stop_service.png){.thumbnail} -Seleziona la `Policy` e modificala come nell'esempio presentato. +Select the `Policy`, then edit it as shown in the example. -Scegli l'opzione `Start and stop manually`{.action} per evitare che il servizio sia attivo all'avvio del server. +Choose the `Start and stop manually`{.action} option to prevent the service from being active when the server starts. ![services_ssh](images/ssh_disabled_.png){.thumbnail} -Applica gli stessi parametri per il servizio `slpd`: +Apply the same settings for the `slpd` service: ![services_slp](images/slpd_.png){.thumbnail} -**Regole del firewall** +**Firewall rules** -Clicca sul menu `Networking`{.action} e poi su `Firewall rules`{.action} e seleziona `Edit settings`{.action} per ciascuno dei servizi da proteggere: +Click the `Networking`{.action} menu, then `Firewall rules`{.action}, and choose `Edit settings`{.action} for each service you want to protect: -![rughe](images/firewall_web_.png){.thumbnail} +![rules](images/firewall_web_.png){.thumbnail} -Modifica la regola per aggiungere solo indirizzi IP o reti che devono avere accesso al tuo sistema ESXi. +Edit the rule to add only IP addresses or networks that need access to your ESXi system. -Esempio che autorizza solo le connessioni dall'IP 192.168.1.10: +Example that only allows connections from IP 192.168.1.10: ![custom](images/custom_fw_rule.png){.thumbnail} -#### Manipolazione tramite la shell +#### Shell manipulation + +**Services** -**Servizi** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> -Disattiva i servizi non necessari: +Disable unnecessary services: -- Servizio SLP +- SLP Service ```bash /etc/init.d/slpd stop @@ -172,7 +175,7 @@ esxcli network firewall ruleset set -r CIMSLP -e 0 chkconfig slpd off ``` -- Servizio SSH +- SSH Service ```bash /etc/init.d/SSH stop @@ -180,7 +183,7 @@ esxcli network firewall ruleset set -r sshServer -e 0 chkconfig SSH off ``` -Verifica tutti i servizi attivi all'avvio: +Check all active services at startup: ```bash chkconfig --list | grep on @@ -188,39 +191,39 @@ chkconfig --list | grep on

-**Regole del firewall** +**Firewall rules** -Visualizza le regole del firewall esistenti: +View existing firewall rules: ```bash esxcli network firewall ruleset list esxcli system account list ``` -> Spiegazioni sulle modifiche/modifiche della regola di accesso: +> Explanations for changing/adapting access rules: > -> - Il servizio `vSphereClient`: questo servizio corrisponde all'interfaccia WEB di amministrazione sulla porta 443 (HTTPS). -> - Il servizio `sshServer`: questo servizio corrisponde agli accessi in SSH sulla porta 22. +> - The `vSphereClient` service: This service corresponds to the web administration interface on port 443 (HTTPS). +> - The `sshServer` service: This service corresponds to SSH access on port 22. -Esempio con il servizio vSphereClient: +Example with the vSphereClient service: ```bash esxcli network firewall ruleset list --ruleset-id vSphereClient ``` -Assicurati che la regola del firewall sia attiva: +Ensure that the firewall rule is active: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --enabled true ``` -Visualizza la lista degli IP autorizzati per questa regola: +Display the list of authorised IPs for this rule: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Risultato: +Result: ``` Ruleset Allowed IP Addresses @@ -228,25 +231,25 @@ Ruleset Allowed IP Addresses vSphereClient All ``` -Modifica lo stato del tag disattivandolo: +Change the status of the tag by disabling it: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --allowed-all false ``` -Autorizza esclusivamente l'indirizzo IP legittimo 192.168.1.10: +Authorise only the legitimate IP address 192.168.1.10: ```bash esxcli network firewall ruleset allowedip add --ruleset-id vSphereClient --ip-address 192.168.1.10 ``` -Verifica la presenza dell'indirizzo nella lista di accesso: +Check the access list for the address: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Risultato: +Result: ``` Ruleset Allowed IP Addresses @@ -256,15 +259,15 @@ vSphereClient 192.168.1.10

-Per utilizzare comunque il servizio SSH, spieghiamo come configurare un accesso tramite chiave SSH. +If you still want to use the SSH service, we will explain here how to set up SSH key access. -Genera le chiavi sulla macchina che deve connettersi al server ESXi, l'algoritmo **ECDSA** su 521 bit è da privilegiare per una sicurezza massima: +Generate the keys on the machine that needs to connect to the ESXi server. The 521-bit **ECDSA** algorithm should be used for maximum security: > [!warning] -> L'autenticazione funziona con una coppia di chiavi: una pubblica amministrazione e un'altra privata. -> Non condividere la tua chiave **privata**, questa deve restare sulla macchina in cui è stata generata. +> Authentication works with a key pair: one public and one private. +> Do not share your **private** key, it must remain on the machine where it was generated. -Esegui questo comando: +Run the following command: ```bash ssh-keygen -t ecdsa -b 521 -C "key-ecdsa-esxi-host" -f /path-to-my-key/key-ecdsa @@ -275,14 +278,14 @@ Generating public/private ecdsa key pair. Enter file in which to save the key (/path-to-my-key/key-ecdsa_rsa): ``` -Inserisci una password solida: +Enter a strong password: ``` Enter passphrase (empty for no passphrase): Enter same passphrase again: ``` -Solo la chiave pubblica (key-ecdsa.pub) dovrà essere comunicata o depositata sulle macchine alle quali vuoi connetterti. +Only the public key (key-ecdsa.pub) must be sent or stored on the machines you want to connect to. ``` Your identification has been saved in /path-to-my-key/key-ecdsa. @@ -291,14 +294,14 @@ The key fingerprint is: SHA256:******************************************* key-ecdsa-esxi-host ``` -Trasferisci la chiave pubblica verso il tuo host ESXi affinché possa essere dichiarata come affidabile: +Transfer the public key to your ESXi host so that it can be declared as trusted: ```bash cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys-root/authorized_keys' ``` -## Per saperne di più +## Go further -Per maggiori informazioni sulle best practice di sicurezza, consulta la [guida](https://core.vmware.com/security-configuration-guide) VMware. +You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Contatta la nostra Community di utenti all’indirizzo . \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pl-pl.md index eb74112ba6c..3c1d0dfae8d 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pl-pl.md @@ -1,75 +1,68 @@ --- -title: 'Zarządzanie serwerem dedykowanym ESXi i jego bezpieczeństwo po pierwszym uruchomieniu' +title: 'Zarządzanie serwerem dedykowanym ESXi i jego bezpieczeństwo po pierwszym uruchomieniu (EN)' excerpt: 'Poznaj sposoby skutecznego zabezpieczenia serwera dedykowanego ESXi' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> Hypervisor ESXi nie jest już wspierany przez OVHcloud. Więcej informacji na temat [tej strony dedykowanej](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - -> [!primary] -> Tłumaczenie zostało wygenerowane automatycznie przez system naszego partnera SYSTRAN. W niektórych przypadkach mogą wystąpić nieprecyzyjne sformułowania, na przykład w tłumaczeniu nazw przycisków lub szczegółów technicznych. W przypadku jakichkolwiek wątpliwości zalecamy zapoznanie się z angielską/francuską wersją przewodnika. Jeśli chcesz przyczynić się do ulepszenia tłumaczenia, kliknij przycisk "Zgłóś propozycję modyfikacji" na tej stronie. -> +## Objective -## Wprowadzenie +The purpose of this guide is to help you optimise security for your ESXi system. -Niniejszy przewodnik pomoże Ci w jak najlepszym opracowaniu zabezpieczeń systemu ESXi. +In particular, this guide explains how to: -W szczególności niniejszy przewodnik wyjaśnia, jak: +- Restrict access to your ESXi server to a specific IP address or network range. +- Disable services that increase your server's attack surface. -- Ograniczenie dostępu do ESXi do określonego adresu IP lub zakresu sieci; -- Wyłącz usługi zwiększające powierzchnię ataku serwera. - -W tym celu skorzystamy z pokładowych funkcji oferowanych przez VMware, ale również przez funkcje oferowane przez OVHcloud. +We will do this using the on-board features offered by VMware, as well as those offered by OVHcloud. > [!warning] > -> Niedawno systemy ESXi padły ofiarą luki, którą złośliwe grupy bardzo szybko wykorzystywały w sieciach publicznych. +> Recently, ESXi systems fell victim to a security flaw that malicious groups exploited very quickly across public networks. > -> Więcej informacji na temat tego ataku można znaleźć w [uzupełniającym FAQ (EN)](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). +> You can find more information on this attack in [an additional FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). > -### Przypomnienie dobrych praktyk w zakresie bezpieczeństwa: +### Security best practices reminder -- Regularnie aktualizuj swoje systemy ESXi. -- Ogranicz dostęp tylko do zaufanych adresów IP. -- Wyłącz porty i niewykorzystane usługi. -- Upewnij się, że dostęp do Twoich serwerów lub urządzeń sieciowych jest ograniczony, kontrolowany i chroniony za pomocą mocnych haseł. -- Przechowuj krytyczne dane na zewnętrznych dyskach oraz na serwerach backup, które są chronione i odizolowane od Internetu. +- Update your ESXi systems regularly. +- Restrict access to trusted IP addresses only. +- Disable unused ports and services. +- Ensure access to your servers or network equipment is limited, controlled and protected with strong passwords. +- Back up your critical data to protected, isolated external disks and backup servers. -**Opcjonalnie**: +**Optional**: -- Wdrażaj rozwiązania dziennikarskie niezbędne do monitorowania wydarzeń na serwerach krytycznych oraz na sprzęcie sieciowym. -- Zbuduj pakiety bezpieczeństwa do wykrywania złośliwych operacji, włamań (IPS / NIDS) oraz do kontroli przepustowości ruchu sieciowego. +- Set up the necessary logging solutions to monitor events on your critical servers and network equipment. +- Set up security packs for malicious action detection, intrusion detection (IPS/NIDS) and network traffic bandwidth control. -## Wymagania początkowe +## Requirements -- Dostęp do [panelu klienta OVHcloud](/links/manager). -- Posiadanie serwera dedykowanego z zainstalowanym rozwiązaniem ESXi -- Wykupienie usługi kompatybilnej z naszą funkcjonalnością [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network), jeśli chcesz korzystać z niej do filtrowania. +- Access to the [OVHcloud Control Panel](/links/manager) +- A dedicated server with the ESXi solution deployed +- An offer compatible with our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) feature, if you would like to use it for filtering -## W praktyce +## Instructions -### Ochrona przed włamaniami +### Native intrusion protection -Przypomnienie jej definicji i zasady działania: +Reminder of its definition and operating principle: > [!primary] > -> System ESXi posiada mechanizm bezpieczeństwa powiązany z rachunkiem administratora. -> W przypadku kilku prób błędnego dostępu konto administratora jest tymczasowo zablokowane. -> Mechanizm ten pozwala na zabezpieczenie Twojego systemu i zapobiega próbom złośliwego połączenia. +> The ESXi system includes a security mechanism linked to the administrator account. +> This is because, in the event of several incorrect access attempts, the administrator account is temporarily locked. +> This mechanism helps protect your system from malicious connection attempts. > [!warning] > -> Jeśli system się uruchomi i chcesz natychmiast zalogować się do ESXi, należy ręcznie odblokować konto administratora. +> If this system triggers and you want to log into your ESXi immediately, you will need to manually unlock the administrator account. > -> W tym celu konieczne będzie [zrestartowanie](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restart-serwera-dedykowanego) serwera ESXi w Panelu klienta OVHcloud. +> To do this, you will need to [reboot](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restarting-your-dedicated-server) your ESXi server via the OVHcloud Control Panel. > -Historię logów dostępu można sprawdzić w następujących plikach z powłoki SSH: +You can view the access log history in the following files via SSH: -- `/var/run/log/vobd.log` zawiera logi, które mogą być używane do monitorowania i rozwiązywania problemów: +- `/var/run/log/vobd.log` contains the logs that can be used for monitoring and troubleshooting: ``` 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. @@ -77,7 +70,7 @@ Historię logów dostępu można sprawdzić w następujących plikach z powłoki 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535867us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. ``` -- `/var/run/log/hostd.log` zawiera logi hosta ESXi (zadania, dostęp do interfejsu WEB, itp.): +- `/var/run/log/hostd.log` contains ESXi host logs (tasks, access to the web interface, etc.): ``` 2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_do_authenticate: error [login:root][error code:2] @@ -86,85 +79,95 @@ Historię logów dostępu można sprawdzić w następujących plikach z powłoki 2023-02-21T08:44:19.712Z info hostd[2101004] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxui-d48c-26a4] Event 175 : Cannot login root@xxx.xxx.xxx.xxx ``` -Wszystkie te informacje są również dostępne w interfejsie administracyjnym. Kliknij menu `Host`{.action} i przejdź do sekcji `Monitor`{.action}, a następnie kliknij `Logs`{.action}. +All this information is also available through the web administration interface. Click the `Host`{.action} menu and navigate to the `Monitor`{.action} section, and then click `Logs`{.action}. -![interfejs](images/gui_logs_.png){.thumbnail} +![interface](images/gui_logs_.png){.thumbnail} -### Rozwiązanie Network Firewall +### The Network Firewall solution > [!primary] > -> Przypominamy, że Network Firewall nie jest brany pod uwagę w ramach sieci OVHcloud. W związku z tym skonfigurowane reguły nie wpływają na połączenia pochodzące z tej sieci wewnętrznej. +> As a reminder, the Network Firewall is not taken into account within the OVHcloud network. As a result, the configured rules do not affect connections from this internal network. > -Proponujemy aktywację i korzystanie z naszego rozwiązania filtrowania [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network). -Dzięki temu będziesz mógł w prosty sposób zarządzać zgodnymi z prawem dostępami, oprócz tych, które wprowadzisz za pośrednictwem systemu ESXi. +You can enable and use our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) filtering solution. +This solution will allow you to easily manage legitimate access, in addition to the access you have set up through your ESXi system. -Dzięki temu unikniesz niespodziewanego zablokowania konta administratora w przypadku ataku. +It will also prevent you from unexpectedly locking your administrator account in the event of an attack. -Zaleca się zatem filtrowanie legalnych dostępów w ten sposób: +It is recommended that you filter legitimate access in this way: -- Reguła 1 (Priority 0) umożliwia dostęp do systemu ESXi przez zaufane sieci zewnętrzne. -- Reguła 2 (Priority 1) blokuje całą resztę. +- Rule 1 (Priority 0) allows trusted external networks to access your ESXi system. +- Rule 2 (Priority 1) blocks everything else. ![Network_Firewall](images/firewall_network_.png){.thumbnail} -### Filtrowanie w ESXi +### Filtering in ESXi > [!primary] > -> Możesz również filtrować dostęp do systemu ESXi za pomocą wbudowanej zapory sieciowej. -> Będziesz mógł również wyłączyć niepotrzebne usługi w zależności od ich zastosowania. +> You can also filter access to your ESXi system with the built-in firewall. +> You can also disable unnecessary services, depending on your usage. > > [!warning] > -> Zaleca się wyłączenie usług **SSH** i **SLP**. -> Jeśli mimo wszystko nadal korzystasz z usługi SSH, ogranicz jej wykorzystanie i dostęp. -> Dotyczy to również dostępu do **shell**. -> Nie zalecaj, aby wszystko, co jest konieczne dla każdego z Twoich potrzeb. +> We strongly advise disabling **SSH** and **SLP** services. +> If you still use the SSH service, restrict its use and access as much as possible. +> This also applies to **shell** access. +> Prioritise only what is strictly necessary for each of your needs. -#### Operacja w interfejsie graficznym +#### Manipulation via the graphical interface -**Usługi** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + +**Services** -Kliknij menu `Host`{.action} i przejdź do sekcji `Manage`{.action}, a następnie kliknij `Services`{.action}. +Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. -Znajdź na liście usługę `TSM-SSH` i kliknij prawym przyciskiem myszy na wybranej linii. +In the list, find the `TSM-SSH` service and right-click on the associated line. -Zatrzymaj usługę, klikając `Stop`{.action}: +Stop the service by clicking `Stop`{.action}: -![usługi_ssh](images/stop_service.png){.thumbnail} +![services_ssh](images/stop_service.png){.thumbnail} -Wybierz `Policy` i zmień ją, jak pokazano na przykładzie. +Select the `Policy`, then edit it as shown in the example. -Wybierz opcję `Start and stop manually`{.action}, aby zapobiec aktywacji usługi podczas uruchamiania serwera. +Choose the `Start and stop manually`{.action} option to prevent the service from being active when the server starts. -![usługi_ssh](images/ssh_disabled_.png){.thumbnail} +![services_ssh](images/ssh_disabled_.png){.thumbnail} -Zastosuj te same parametry dla usługi `slpd`: +Apply the same settings for the `slpd` service: -![usługi_slp](images/slpd_.png){.thumbnail} +![services_slp](images/slpd_.png){.thumbnail} -**Reguły zapory ogniowej** +**Firewall rules** -Kliknij menu `Networking`{.action}, następnie `Firewall rules`{.action} i wybierz `Edit settings`{.action} dla każdej z usług, które chcesz chronić: +Click the `Networking`{.action} menu, then `Firewall rules`{.action}, and choose `Edit settings`{.action} for each service you want to protect: -![rule](images/firewall_web_.png){.thumbnail} +![rules](images/firewall_web_.png){.thumbnail} -Edytuj regułę, aby dodać tylko adresy IP lub sieci, które muszą mieć dostęp do Twojego systemu ESXi. +Edit the rule to add only IP addresses or networks that need access to your ESXi system. -Przykład zezwalający wyłącznie na połączenia z IP 192.168.1.10: +Example that only allows connections from IP 192.168.1.10: ![custom](images/custom_fw_rule.png){.thumbnail} -#### Manipulacja przez powłokę +#### Shell manipulation + +**Services** -**Usługi** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> -Wyłącz niepotrzebne usługi: +Disable unnecessary services: -- Usługa SLP +- SLP Service ```bash /etc/init.d/slpd stop @@ -172,7 +175,7 @@ esxcli network firewall ruleset set -r CIMSLP -e 0 chkconfig slpd off ``` -- Usługa SSH +- SSH Service ```bash /etc/init.d/SSH stop @@ -180,7 +183,7 @@ esxcli network firewall ruleset set -r sshServer -e 0 chkconfig SSH off ``` -Sprawdź wszystkie usługi aktywne w trakcie uruchamiania: +Check all active services at startup: ```bash chkconfig --list | grep on @@ -188,39 +191,39 @@ chkconfig --list | grep on

-**Reguły zapory ogniowej** +**Firewall rules** -Wyświetl istniejące reguły zapory sieciowej: +View existing firewall rules: ```bash esxcli network firewall ruleset list esxcli system account list ``` -> Wyjaśnienia dotyczące zmian/dostosowania reguły dostępu: +> Explanations for changing/adapting access rules: > -> - Usługa `vSphereClient`: usługa ta odpowiada interfejsowi webowemu administracyjnemu na porcie 443 (HTTPS). -> - Usługa `sshServer`: usługa ta odpowiada dostępowi przez SSH na porcie 22. +> - The `vSphereClient` service: This service corresponds to the web administration interface on port 443 (HTTPS). +> - The `sshServer` service: This service corresponds to SSH access on port 22. -Przykład usługi vSphereClient: +Example with the vSphereClient service: ```bash esxcli network firewall ruleset list --ruleset-id vSphereClient ``` -Upewnij się, czy reguła zapory jest aktywna: +Ensure that the firewall rule is active: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --enabled true ``` -Wyświetl listę adresów IP upoważnionych dla tej reguły: +Display the list of authorised IPs for this rule: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Wynik: +Result: ``` Ruleset Allowed IP Addresses @@ -228,25 +231,25 @@ Ruleset Allowed IP Addresses vSphereClient All ``` -Zmień status tagu poprzez jego wyłączenie: +Change the status of the tag by disabling it: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --allowed-all false ``` -Zezwalaj wyłącznie na poprawny adres IP 192.168.1.10: +Authorise only the legitimate IP address 192.168.1.10: ```bash esxcli network firewall ruleset allowedip add --ruleset-id vSphereClient --ip-address 192.168.1.10 ``` -Sprawdź obecność adresu na liście dostępowej: +Check the access list for the address: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Wynik: +Result: ``` Ruleset Allowed IP Addresses @@ -256,15 +259,15 @@ vSphereClient 192.168.1.10

-Jeśli nadal chcesz korzystać z usługi SSH, wyjaśnimy, jak wdrożyć dostęp za pomocą klucza SSH. +If you still want to use the SSH service, we will explain here how to set up SSH key access. -Wygeneruj klucze na maszynie, która ma być połączona z serwerem ESXi, 521-bitowy algorytm **ECDSA** to bezpieczeństwo priorytetowe: +Generate the keys on the machine that needs to connect to the ESXi server. The 521-bit **ECDSA** algorithm should be used for maximum security: > [!warning] -> Uwierzytelnianie działa z parą kluczy: jedna publiczna i inna prywatna. -> W żadnym wypadku nie udostępniaj **prywatnego** klucza, który musi pozostać na maszynie, na której został wygenerowany. +> Authentication works with a key pair: one public and one private. +> Do not share your **private** key, it must remain on the machine where it was generated. -Wprowadź następujące polecenie: +Run the following command: ```bash ssh-keygen -t ecdsa -b 521 -C "key-ecdsa-esxi-host" -f /path-to-my-key/key-ecdsa @@ -275,14 +278,14 @@ Generating public/private ecdsa key pair. Enter file in which to save the key (/path-to-my-key/key-ecdsa_rsa): ``` -Wpisz silne hasło: +Enter a strong password: ``` Enter passphrase (empty for no passphrase): Enter same passphrase again: ``` -Na maszynach, do których chcesz się zalogować, należy podać lub przesłać tylko klucz publiczny (key-ecdsa.pub). +Only the public key (key-ecdsa.pub) must be sent or stored on the machines you want to connect to. ``` Your identification has been saved in /path-to-my-key/key-ecdsa. @@ -291,14 +294,14 @@ The key fingerprint is: SHA256:******************************************* key-ecdsa-esxi-host ``` -Przenieś klucz publiczny do hosta ESXi, aby mógł zostać uznany za bezpieczny: +Transfer the public key to your ESXi host so that it can be declared as trusted: ```bash cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys-root/authorized_keys' ``` -## Sprawdź również +## Go further -Więcej informacji na temat dobrych praktyk bezpieczeństwa znajdziesz w [tym przewodniku](https://core.vmware.com/security-configuration-guide) zaproponowanym przez VMware. +You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Dołącz do społeczności naszych użytkowników na stronie . \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pt-pt.md index 1a1ce4b049a..c37cb4c03d2 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-hardening/guide.pt-pt.md @@ -1,75 +1,68 @@ --- -title: 'Controle e proteja o seu servidor dedicado ESXi desde o seu primeiro começo' +title: 'Controle e proteja o seu servidor dedicado ESXi desde o seu primeiro começo (EN)' excerpt: 'Descubra os diferentes meios que lhe permitem proteger eficazmente o seu servidor dedicado ESXi' -updated: 2024-09-13 +updated: 2025-09-15 --- -> [!warning] -> O hipervisor ESXi já não é suportado pela OVHcloud. Encontre mais informações em [esta página dedicada](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - -> [!primary] -> Esta tradução foi automaticamente gerada pelo nosso parceiro SYSTRAN. Em certos casos, poderão ocorrer formulações imprecisas, como por exemplo nomes de botões ou detalhes técnicos. Recomendamos que consulte a versão inglesa ou francesa do manual, caso tenha alguma dúvida. Se nos quiser ajudar a melhorar esta tradução, clique em "Contribuir" nesta página. -> +## Objective -## Objetivo +The purpose of this guide is to help you optimise security for your ESXi system. -Este manual tem como objetivo acompanhá-lo no desenvolvimento da segurança do seu sistema ESXi. +In particular, this guide explains how to: -Em particular, este guia explica como: +- Restrict access to your ESXi server to a specific IP address or network range. +- Disable services that increase your server's attack surface. -- limitar o acesso ao seu ESXi a um endereço IP ou a uma gama de rede específica; -- desativar serviços que aumentem a superfície de ataque do seu servidor. - -Para isso, utilizaremos as funções de bordo propostas pela VMware, mas também as oferecidas pela OVHcloud. +We will do this using the on-board features offered by VMware, as well as those offered by OVHcloud. > [!warning] > -> Recentemente, os sistemas ESXi foram vítimas de uma falha que grupos maliciosos exploraram muito rapidamente através das redes públicas. +> Recently, ESXi systems fell victim to a security flaw that malicious groups exploited very quickly across public networks. > -> Para mais informações sobre este ataque, consulte [a FAQ (EN)](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). +> You can find more information on this attack in [an additional FAQ](/pages/bare_metal_cloud/dedicated_servers/faq-esxi). > -### Lembrete das boas práticas de segurança: +### Security best practices reminder -- Atualize regularmente os seus sistemas ESXi. -- Restrinja o acesso apenas aos endereços IP de confiança. -- Desative as portas e os serviços não utilizados. -- Certifique-se de que os acessos aos seus servidores ou equipamentos de rede são limitados, controlados e protegidos com palavras-passe robustas. -- Guarde os seus dados críticos em discos externos e servidores de backup protegidos e isolados da Internet. +- Update your ESXi systems regularly. +- Restrict access to trusted IP addresses only. +- Disable unused ports and services. +- Ensure access to your servers or network equipment is limited, controlled and protected with strong passwords. +- Back up your critical data to protected, isolated external disks and backup servers. -**Opcional**: +**Optional**: -- Implemente as soluções de registo necessárias para controlar os acontecimentos ocorridos nos seus servidores críticos e nos seus equipamentos de rede. -- Implemente packs de segurança para a deteção de ações maliciosas, intrusões (IPS / NIDS) e para o controlo da largura de banda do tráfego de rede. +- Set up the necessary logging solutions to monitor events on your critical servers and network equipment. +- Set up security packs for malicious action detection, intrusion detection (IPS/NIDS) and network traffic bandwidth control. -## Requisitos +## Requirements -- Ter acesso à [Área de Cliente OVHcloud](/links/manager). -- Ter um servidor dedicado com a solução ESXi implementada. -- Ter uma oferta compatível com a nossa funcionalidade [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) se pretender utilizá-la para efetuar a filtragem. +- Access to the [OVHcloud Control Panel](/links/manager) +- A dedicated server with the ESXi solution deployed +- An offer compatible with our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) feature, if you would like to use it for filtering -## Instruções +## Instructions -### A proteção anti-intrusão nativa +### Native intrusion protection -Lembrete da sua definição e do seu princípio de funcionamento: +Reminder of its definition and operating principle: > [!primary] > -> O sistema ESXi está a instalar um mecanismo de segurança associado à conta de administrador. -> Com efeito, em caso de várias tentativas de acesso erradas, a conta administrador está temporariamente bloqueada. -> Este mecanismo permite proteger o seu sistema e, assim, evitar as tentativas de ligações maliciosas. +> The ESXi system includes a security mechanism linked to the administrator account. +> This is because, in the event of several incorrect access attempts, the administrator account is temporarily locked. +> This mechanism helps protect your system from malicious connection attempts. > [!warning] > -> Se este sistema for ativado e pretender conectar-se ao seu ESXi imediatamente, terá de desbloquear manualmente a conta de administrador. +> If this system triggers and you want to log into your ESXi immediately, you will need to manually unlock the administrator account. > -> Para isso, será necessário [reiniciar](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#reinicializacao-do-seu-servidor-dedicado) o seu servidor ESXi através da Área de Cliente OVHcloud. +> To do this, you will need to [reboot](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server#restarting-your-dedicated-server) your ESXi server via the OVHcloud Control Panel. > -Pode consultar o histórico dos logs de acesso nos seguintes ficheiros a partir de uma shell SSH: +You can view the access log history in the following files via SSH: -- `/var/run/log/vobd.log` contém os logs que podem ser utilizados para a supervisão e resolução de problemas: +- `/var/run/log/vobd.log` contains the logs that can be used for monitoring and troubleshooting: ``` 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535559us: [vob.user.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. @@ -77,7 +70,7 @@ Pode consultar o histórico dos logs de acesso nos seguintes ficheiros a partir 2023-02-13T16:22:22.897Z: [UserLevelCorrelator] 410535867us: [esx.audit.account.locked] Remote access for ESXi local user account 'root' has been locked for 900 seconds after 6 failed login attempts. ``` -- `/var/run/log/hostd.log` contém os logs do host ESXi (tarefas, acesso à interface WEB, etc.): +- `/var/run/log/hostd.log` contains ESXi host logs (tasks, access to the web interface, etc.): ``` 2023-02-21T08:44:19.711Z error hostd[2101004] [Originator@6876 sub=Default opID=esxui-d48c-26a4] [module:pam_lsass]pam_do_authenticate: error [login:root][error code:2] @@ -86,85 +79,95 @@ Pode consultar o histórico dos logs de acesso nos seguintes ficheiros a partir 2023-02-21T08:44:19.712Z info hostd[2101004] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=esxui-d48c-26a4] Event 175 : Cannot login root@xxx.xxx.xxx.xxx ``` -Todas estas informações estão igualmente disponíveis através da interface de administração web. Clique no menu `Host`{.action} e aceda à secção `Monitor`{.action} e clique em `Logs`{.action}. +All this information is also available through the web administration interface. Click the `Host`{.action} menu and navigate to the `Monitor`{.action} section, and then click `Logs`{.action}. ![interface](images/gui_logs_.png){.thumbnail} -### A solução Network Firewall +### The Network Firewall solution > [!primary] > -> Relembramos que a Network Firewall não é tida em conta na rede OVHcloud. Por conseguinte, as regras configuradas não afetam as ligações provenientes desta rede interna. +> As a reminder, the Network Firewall is not taken into account within the OVHcloud network. As a result, the configured rules do not affect connections from this internal network. > -Propomos-lhe que ative e utilize a nossa solução de filtragem [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network). -Esta solução permitir-lhe-á gerir facilmente os acessos legítimos, em complemento dos que terá implementado através do seu sistema ESXi. +You can enable and use our [Network Firewall](/pages/bare_metal_cloud/dedicated_servers/firewall_network) filtering solution. +This solution will allow you to easily manage legitimate access, in addition to the access you have set up through your ESXi system. -Também evitará bloquear inesperadamente a sua conta de administrador em caso de ataque. +It will also prevent you from unexpectedly locking your administrator account in the event of an attack. -Por conseguinte, recomenda - se que os acessos legítimos sejam filtrados desta forma: +It is recommended that you filter legitimate access in this way: -- A regra 1 (Priority 0) permite o acesso de redes externas de confiança ao seu sistema ESXi. -- A regra 2 (Priority 1) bloqueia tudo o resto. +- Rule 1 (Priority 0) allows trusted external networks to access your ESXi system. +- Rule 2 (Priority 1) blocks everything else. ![Network_Firewall](images/firewall_network_.png){.thumbnail} -### A filtragem sob ESXi +### Filtering in ESXi > [!primary] > -> Também pode filtrar os acessos ao seu sistema ESXi graças à firewall integrada. -> Também poderá desativar os serviços inúteis, em função da sua utilização. +> You can also filter access to your ESXi system with the built-in firewall. +> You can also disable unnecessary services, depending on your usage. > > [!warning] > -> A desativação dos serviços **SSH** e **SLP** é fortemente aconselhada. -> Se, apesar de tudo, continuar a utilizar o serviço SSH, restrinja ao máximo a sua utilização e os seus acessos. -> O mesmo se aplica aos acessos ao **shell**. -> Preveja apenas o estritamente necessário para cada uma das suas necessidades. +> We strongly advise disabling **SSH** and **SLP** services. +> If you still use the SSH service, restrict its use and access as much as possible. +> This also applies to **shell** access. +> Prioritise only what is strictly necessary for each of your needs. -#### Manipulação através da interface gráfica +#### Manipulation via the graphical interface -**Serviços** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> + +**Services** -Clique no menu `Host`{.action} e aceda à secção `Manage`{.action} e clique em `Serviços`{.action}. +Click the `Host`{.action} menu and navigate to the `Manage`{.action} section, then click `Services`{.action}. -Encontre na lista o serviço `TSM-SSH` e faça um clique direito na linha associada. +In the list, find the `TSM-SSH` service and right-click on the associated line. -Parem o serviço ao clicar em `Stop`{.action}: +Stop the service by clicking `Stop`{.action}: -![serviços_ssh](images/stop_service.png){.thumbnail} +![services_ssh](images/stop_service.png){.thumbnail} -Selecione a `Policy` e altere-a conforme indicado no exemplo apresentado. +Select the `Policy`, then edit it as shown in the example. -Escolha a opção `Start and stop manually`{.action} para evitar que o serviço esteja ativo no arranque do servidor. +Choose the `Start and stop manually`{.action} option to prevent the service from being active when the server starts. -![serviços_ssh](images/ssh_disabled_.png){.thumbnail} +![services_ssh](images/ssh_disabled_.png){.thumbnail} -Aplicar os mesmos parâmetros para o serviço `slpd`: +Apply the same settings for the `slpd` service: -![serviços_slp](images/slpd_.png){.thumbnail} +![services_slp](images/slpd_.png){.thumbnail} -**Regras da firewall** +**Firewall rules** -Clique no menu `Networking`{.action} e, a seguir, na `Firewall rules`{.action} e selecione `Edit settings`{.action} para cada um dos serviços a proteger: +Click the `Networking`{.action} menu, then `Firewall rules`{.action}, and choose `Edit settings`{.action} for each service you want to protect: -![blocos](images/firewall_web_.png){.thumbnail} +![rules](images/firewall_web_.png){.thumbnail} -Editar a regra para adicionar apenas os endereços IP ou as redes que devem ter acesso ao seu sistema ESXi. +Edit the rule to add only IP addresses or networks that need access to your ESXi system. -Exemplo que autoriza apenas ligações a partir do IP 192.168.1.10: +Example that only allows connections from IP 192.168.1.10: ![custom](images/custom_fw_rule.png){.thumbnail} -#### Manipulação através do shell +#### Shell manipulation + +**Services** -**Serviços** +> [!primary] +> +> In ESXi 8.0 GA and newer, the SLP service is hardened, disabled by default, and filtered by the ESXi firewall. This means that you no longer have to disable it manually. You can find more information on [this official VMware blog post](https://blogs.vmware.com/security/2023/04/vmware-response-to-cve-2023-29552-reflective-denial-of-service-dos-amplification-vulnerability-in-slp.html) +> -Desative os serviços inúteis: +Disable unnecessary services: -- Serviço SLP +- SLP Service ```bash /etc/init.d/slpd stop @@ -172,7 +175,7 @@ esxcli network firewall ruleset set -r CIMSLP -e 0 chkconfig slpd off ``` -- Serviço SSH +- SSH Service ```bash /etc/init.d/SSH stop @@ -180,7 +183,7 @@ esxcli network firewall ruleset set -r sshServer -e 0 chkconfig SSH off ``` -Verifique todos os serviços ativos no arranque: +Check all active services at startup: ```bash chkconfig --list | grep on @@ -188,39 +191,39 @@ chkconfig --list | grep on

-**Regras da firewall** +**Firewall rules** -Indique as regras de firewall existentes: +View existing firewall rules: ```bash esxcli network firewall ruleset list esxcli system account list ``` -> Explicações sobre as alterações/ajustamentos da regra de acesso: +> Explanations for changing/adapting access rules: > -> - O serviço `vSphere Client`: este serviço corresponde à interface WEB de administração na porta 443 (HTTPS). -> - O serviço `sshServer`: este serviço corresponde aos acessos em SSH na porta 22. +> - The `vSphereClient` service: This service corresponds to the web administration interface on port 443 (HTTPS). +> - The `sshServer` service: This service corresponds to SSH access on port 22. -Exemplo com o serviço vSphere Client: +Example with the vSphereClient service: ```bash esxcli network firewall ruleset list --ruleset-id vSphereClient ``` -Certifique-se de que a regra da firewall está ativa: +Ensure that the firewall rule is active: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --enabled true ``` -Afixar a lista dos IP autorizados para esta regra: +Display the list of authorised IPs for this rule: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Resultado: +Result: ``` Ruleset Allowed IP Addresses @@ -228,25 +231,25 @@ Ruleset Allowed IP Addresses vSphereClient All ``` -Altere o estado da tag desativando-a: +Change the status of the tag by disabling it: ```bash esxcli network firewall ruleset set --ruleset-id vSphereClient --allowed-all false ``` -Autorize apenas o endereço IP legítimo 192.168.1.10: +Authorise only the legitimate IP address 192.168.1.10: ```bash esxcli network firewall ruleset allowedip add --ruleset-id vSphereClient --ip-address 192.168.1.10 ``` -Verifique a presença do endereço na lista de acesso: +Check the access list for the address: ```bash esxcli network firewall ruleset allowedip list --ruleset-id vSphereClient ``` -Resultado: +Result: ``` Ruleset Allowed IP Addresses @@ -256,15 +259,15 @@ vSphereClient 192.168.1.10

-Se pretender utilizar o serviço SSH, explicamos-lhe como implementar um acesso com chave SSH. +If you still want to use the SSH service, we will explain here how to set up SSH key access. -Gerar as chaves na máquina que deve ligar-se ao servidor ESXi, o algoritmo **ECDSA** em 521 bits deve ser privilegiado para uma segurança máxima: +Generate the keys on the machine that needs to connect to the ESXi server. The 521-bit **ECDSA** algorithm should be used for maximum security: > [!warning] -> A autenticação funciona com um par de chaves: uma pública e outra privada. -> Não partilhe de forma alguma a sua chave **privada**, ela deve permanecer na máquina onde foi gerada. +> Authentication works with a key pair: one public and one private. +> Do not share your **private** key, it must remain on the machine where it was generated. -Execute o seguinte comando: +Run the following command: ```bash ssh-keygen -t ecdsa -b 521 -C "key-ecdsa-esxi-host" -f /path-to-my-key/key-ecdsa @@ -275,14 +278,14 @@ Generating public/private ecdsa key pair. Enter file in which to save the key (/path-to-my-key/key-ecdsa_rsa): ``` -Introduza uma palavra-passe robusta: +Enter a strong password: ``` Enter passphrase (empty for no passphrase): Enter same passphrase again: ``` -Apenas a chave pública (key-ecdsa.pub) deverá ser comunicada ou colocada nas máquinas às quais deseja ligar-se. +Only the public key (key-ecdsa.pub) must be sent or stored on the machines you want to connect to. ``` Your identification has been saved in /path-to-my-key/key-ecdsa. @@ -291,14 +294,14 @@ The key fingerprint is: SHA256:******************************************* key-ecdsa-esxi-host ``` -Transfira a chave pública para o seu host ESXi para que possa ser declarada como estando de confiança: +Transfer the public key to your ESXi host so that it can be declared as trusted: ```bash cat /path-to-my-key/key-ecdsa.pub | ssh root@esxi-host-ip 'cat >> /etc/ssh/keys-root/authorized_keys' ``` -## Saiba mais +## Go further -Para mais informações sobre as boas práticas de segurança, consulte [este manual](https://core.vmware.com/security-configuration-guide) da VMware. +You can find even more details on security best practices in [this VMware suggested guide](https://core.vmware.com/security-configuration-guide). -Fale com a nossa comunidade de utilizadores em . \ No newline at end of file +Join our [community of users](/links/community). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.de-de.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.de-de.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-asia.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-asia.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-au.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-au.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ca.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ca.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md index c84bd75ff4f..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-gb.md @@ -1,5 +1,5 @@ --- -title: How to install VMware ESXi 8 on an dedicated server +title: How to install VMware ESXi 8 on a dedicated server excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image updated: 2025-09-15 --- @@ -17,7 +17,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Requirements - A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -26,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ie.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-ie.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-sg.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-sg.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-us.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.en-us.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-es.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-es.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-us.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.es-us.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-ca.md index 8fe16083411..92afdc0983f 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.fr-ca.md @@ -1,27 +1,24 @@ --- -title: "Serveurs Dédiés - Partitionnement d'ESXi" -excerpt: "Utilisez l'espace client OVHcloud ou l'API OVHcloud pour personnaliser la taille de la partition système d'ESXi" -updated: 2025-04-29 +title: "Installer VMware ESXi 8 sur un serveur dédié" +excerpt: "Découvrez comment installer et configurer VMware ESXi 8 sur un serveur dédié en utilisant un template fourni par OVHcloud" +updated: 2025-09-15 --- -> [!warning] -> L'hyperviseur ESXi n'est plus supporté par OVHcloud. Retrouvez plus d'informations sur [cette page dédiée](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objectif -Avec les [serveurs dédiés OVHcloud](/links/bare-metal/bare-metal), vous pouvez [personnaliser le partitionnement](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). Cela vous donne des possibilités de configuration assez vastes lors de l'installation du système d'exploitation. ESXi ne le permet pas à cause de ses spécificités car il s'agit d'un système propriétaire UNIX avec un installateur propriétaire. Par conséquent, OVHcloud est dépendant de l'éditeur pour l'installation de l'OS. Depuis ESXi 7.0, il est possible de choisir entre 4 schémas de partitionnement prédéfinis par l'éditeur. - -**Cet article a pour objectif de vous montrer comment choisir un schéma de partitionnement dans l'[espace client OVHcloud](/links/manager) ou l'[API OVHcloud](/links/api).** - > [!primary] > -> ESXi 7.0 est souvent utilisé comme exemple sur cette page, mais la documentation est valable pour les versions 7.0 et ultérieures d'ESXi. +> Depuis le 15 septembre 2025, OVHcloud propose un template d'installation ESXi 8 pour ses serveurs dédiés. > +Avec les [serveurs dédiés OVHcloud](/links/bare-metal/bare-metal), vous pouvez [personnaliser le partitionnement](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). Cela vous donne des possibilités de configuration assez vastes lors de l'installation du système d'exploitation. ESXi ne le permet pas à cause de ses spécificités car il s'agit d'un système propriétaire UNIX avec un installateur propriétaire. Par conséquent, les installations ESXi d'OVHcloud sont conformes à la configuration définie par l'éditeur du logiciel. Depuis ESXi 7.0, il est possible de choisir entre 4 schémas de partitionnement prédéfinis. + +Ce guide a pour objectif de vous montrer comment installer ESXi 8 et sélectionner un schéma de partitionnement dans l'[espace client OVHcloud](/links/manager) ou via l'[API OVHcloud](/links/api). + ## Prérequis -- Un [serveur dédié](/links/bare-metal/bare-metal) dans votre compte OVHcloud, **prêt à être installé/réinstallé**. -- Avoir accès à l'[espace client OVHcloud](/links/manager) et/ou à l'[API OVHcloud](/links/api). +- Un [serveur dédié](/links/bare-metal/bare-metal) **prêt à être installé/réinstallé** dans votre compte OVHcloud, compatible avec les [exigences matérielles d'ESXi 8](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-hardware-requirements-upgrade.html) +- Avoir accès à l'[espace client OVHcloud](/links/manager) et/ou à l'[API OVHcloud](/links/api) > [!alert] > @@ -30,44 +27,45 @@ Avec les [serveurs dédiés OVHcloud](/links/bare-metal/bare-metal), vous pouvez ## En pratique -ESXi 7.0 introduit une [option d'amorçage permettant de configurer la taille de la partition système ESXi](https://kb.vmware.com/s/article/81166). Cette fonctionnalité a été introduite par l'éditeur car l'augmentation de la taille de la partition système pouvait poser problème, en particulier sur les machines où les disques sont de petite taille. OVHcloud propose désormais cette fonctionnalité qui est disponible aussi bien depuis l'[espace client OVHcloud](https://www.ovh.com/manager/#/dedicated/configuration) que via l'[API OVHcloud](/links/api). +ESXi 7.0 et les versions ultérieures ont introduit une [option d'amorçage permettant de configurer la taille des partitions système d'ESXi](https://kb.vmware.com/s/article/81166). Cette fonctionnalité a été introduite par l'éditeur car l'augmentation de la taille de la partition système pouvait poser problème, en particulier sur les machines avec de petits disques. OVHcloud a inclus cette fonctionnalité qui est disponible aussi bien depuis l'[espace client OVHcloud](https://www.ovh.com/manager/#/dedicated/configuration) que via l'[API OVHcloud](/links/api). -Malgré le fait que votre serveur ait plusieurs disques, l'installation d'ESXi n'est possible que sur le premier disque de la grappe de disques sélectionnée pour l'installation (voir « [API OVHcloud et installation d'un OS - Grappes de disques](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group) » ), les autres disques pouvant être configurés par la suite par l'utilisateur pour être utilisés pour stocker les machines virtuelles (voir « [Configuration du stockage d'un serveur HGR-STOR-2](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) » ). +Même si votre serveur dispose de plusieurs disques, l'installation d'ESXi utilise uniquement le premier disque du groupe de disques ciblé (voir « [API OVHcloud et installation d'un OS - Grappes de disques](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group) »). Les autres disques peuvent être configurés par la suite pour être utilisés pour les machines virtuelles (voir « [Comment ajouter un datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) »). -4 valeurs sont possibles : +Il existe 4 valeurs différentes : |Valeur|Taille Système¹|Datastore³| |---|---|---| -|`default`|130 Gio|Tout l'epace restant²| -|`min`|32 Gio|Tout l'epace restant²| -|`small`|64 Gio|Tout l'epace restant²| +|`default`|130 Gio|Tout l'espace restant²| +|`min`|32 Gio|Tout l'espace restant²| +|`small`|64 Gio|Tout l'espace restant²| |`max`|Tout l'espace disponible²|❌⁴| -¹ Seul le premier disque de la grappe de disques sélectionnée pour l'installation de l'OS.
-² Espace disque sur lequel l'OS va être installé.
-³ Un datastore est une partition de disque (parfois aussi appelée « container ») qu'ESXi va utiliser pour stocker ses machines virtuelles. Retrouvez plus de détails sur [cette documentation VMware (EN)](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-5EE84941-366D-4D37-8B7B-767D08928888.html).
-⁴ Le client pourra toujours [ajouter un datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) par la suite, mais uniquement sur les autres disques.
+¹ Sur le premier disque du groupe de disques ciblé pour l'installation de l'OS.
+² Espace sur le disque sur lequel l'OS sera installé.
+³ Un datastore est une partition de disque (parfois aussi appelée « conteneur ») qu'ESXi va utiliser pour stocker les machines virtuelles. [Plus de détails](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-5EE84941-366D-4D37-8B7B-767D08928888.html).
+⁴ Les clients peuvent toujours [ajouter un datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore) par la suite sur les autres disques. -Comme vous pouvez le constater, aucun datastore n'est créé sur le premier disque lors de l'utilisation du schéma `max`. +Comme vous pouvez le constater, aucun datastore n'est créé sur le premier disque avec le schéma de partitionnement `max`. > [!primary] > > Le saviez-vous ? +> > Les solutions [VMware on OVHcloud](/links/hosted-private-cloud/vmware) sont basées sur des installations ESXi avec le schéma de partitionnement `small`. > ### Comment sélectionner le schéma de partitionnement ? -Comme vous pouvez le deviner, si le schéma n'est pas spécifié, le schéma de partitionnement `default` sera alors utilisé. +Le schéma de partitionnement `default` sera utilisé sauf si un autre est sélectionné. #### Via l'espace client OVHcloud > [!primary] > -> Cette procédure est très similaire à celle [des autres OS](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server), à l'exception qu'il n'est pas possible de sélectionner `Personnaliser la configuration des partitions`{.action} et qu'il y a une liste déroulante permettant de sélectionner le schéma de partitionnment à la quatrième et dernière étape. +> La procédure est très similaire [aux autres systèmes d'exploitation](/pages/bare_metal_cloud/dedicated_servers/getting-started-with-dedicated-server), à l'exception que vous ne pouvez pas cocher la case `Personnaliser la configuration des partitions`{.action} et qu'il y a une liste déroulante pour choisir le schéma de partitionnement à la quatrième et dernière étape. > -Dans l'[espace client OVHcloud](/links/manager), sous l'onglet `Informations générales`{.action}, cliquez sur `...`{.action} en face du système d'exploitation puis cliquez sur `Installer`{.action}. +Connectez-vous à l'[espace client OVHcloud](/links/manager). Depuis l'onglet `Informations générales`{.action}, cliquez sur le bouton `...`{.action} à côté du système d'exploitation, puis cliquez sur `Installer`{.action}. ![Bouton Réinstaller](images/reinstalling-your-server-00.png){.thumbnail} @@ -80,28 +78,29 @@ Ensuite, choisissez `Virtualisation`{.action}, `UNIX`{.action} et sélectionnez > [!primary] > -> Comme vous pouvez le constater, vous ne pouvez pas cocher l'option `Personnaliser la configuration des partitions`{.action}, comme expliqué ci-dessus. +> L'option `Personnaliser la configuration des partitions`{.action} n'est pas disponible, pour les raisons expliquées ci-dessus. > -Choisissez la grappe de disques sur laquelle vous souhaitez qu'ESXi soit installé. Notez que seul le premier disque de la grappe va être utilisé pour installer le système d'exploitation. Retrouvez plus d'information dans [ce guide](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group). +Choisissez le groupe de disques sur lequel vous souhaitez qu'ESXi soit installé. Notez que seul le premier disque de ce groupe sera utilisé pour installer l'OS. Retrouvez plus d'informations dans [ce guide](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group). Cliquez sur `Suivant`{.action} pour continuer. -![Choix d'ESXi comme OS à installer](images/reinstalling-your-server-02.png){.thumbnail} +![Choix d'ESXi](images/reinstalling-your-server-02.png){.thumbnail} -Dans la liste déroulante `Schéma de partitionnement`{.action}, sélectionnez le schéma de partitionnement désiré. L'aperçu est mis à jour dès que vous basculez vers un autre schéma de partitionnement, de telle sorte que vous puissiez avoir une idée de la configuration sur votre serveur dédié. +Dans la liste déroulante `Schéma de partitionnement`{.action}, sélectionnez le schéma de partitionnement désiré. L'aperçu est mis à jour dès que vous sélectionnez un autre schéma de partitionnement, de telle sorte que vous puissiez avoir une idée de la configuration sur votre serveur dédié. -Complétez les autres détails et cliquez sur `Confirmer`{.action} afin de démarrer l'installation d'ESXi sur votre serveur dédié. +Remplissez les autres détails et cliquez sur `Confirmer`{.action} pour lancer l'installation d'ESXi sur votre serveur dédié. > [!primary] > -> Le champ `Nombre de disques partitionnés`{.action} est grisé et sa valeur est de 1 même si votre serveur dispose de plusieurs disques sur la grappe choisie, comme expliqué ci-dessus. +> Le champ `Nombre de disques partitionnés`{.action} est grisé et sa valeur est de 1, même si votre serveur dispose de plus d'un disque sur le groupe de disques ciblé pour l'installation de l'OS, comme expliqué ci-dessus. +> -![Choix du schéma de partitionnement](images/esxi-custom-scheme-00.png){.thumbnail} +![Sélection du schéma de partitionnement](images/esxi-custom-scheme-00.png){.thumbnail} #### Via l'API OVHcloud -Lorsque vous lancez une installation d'OS, vous pouvez fournir une option `partitionSchemeName` afin de spécifier le schéma de partitionnement qui sera utilisé : +Lorsque vous lancez une installation d'OS, le client peut éventuellement fournir un `partitionSchemeName` afin de spécifier le schéma de partitionnement à utiliser : > [!api] > @@ -112,14 +111,14 @@ Exemple de requête : ```json { - "operatingSystem": "esxi70_64", - "storage": [ - { - "partitioning": { - "schemeName": "small" - } - } - ] +    "operatingSystem": "esxi80_64", +    "storage": [ +        { +            "partitioning": { +                "schemeName": "small" +            } +        } +    ] } ``` @@ -130,7 +129,7 @@ Pour lister les différents schémas de partitionnement d'un template OS OVHclou > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -Exemple de retour pour `esxi70_64` : +Exemple de retour pour `esxi80_64` : ```json [ @@ -148,6 +147,17 @@ Afin d'obtenir les détails du schéma de partitionnement de manière dynamique, > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +Exemple de retour pour `default`: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + Vous pouvez utiliser l'appel API suivant afin d'obtenir le détail de chaque partition : > [!api] @@ -155,6 +165,23 @@ Vous pouvez utiliser l'appel API suivant afin d'obtenir le détail de chaque par > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +Exemple de retour pour `/bootbank`: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Aller plus loin [Option d'amorçage permettant de configurer la taille de la partition système ESXi [EN]](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.it-it.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.it-it.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pl-pl.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pl-pl.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pt-pt.md index 310ffe6f662..f49b95c2388 100644 --- a/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/esxi-partitioning/guide.pt-pt.md @@ -1,26 +1,23 @@ --- -title: Dedicated Servers - ESXi Partitioning -excerpt: Use the OVHcloud Control Panel or the OVHcloud API to customise ESXi system partitions -updated: 2025-04-29 +title: How to install VMware ESXi 8 on a dedicated server +excerpt: Find out how to install and configure VMware ESXi 8 on a dedicated server using an OVHcloud provided image +updated: 2025-09-15 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective -With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
-OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to select a partitioning layout in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) or via the [OVHcloud API](/links/api). - > [!primary] > -> ESXi 7.0 is often used as an example but this documentation is valid for any further versions of ESXi as well. +> Since September 15, 2025, OVHcloud provides an ESXi 8 installation template for its dedicated servers. > +With [OVHcloud dedicated servers](/links/bare-metal/bare-metal), you can freely [configure partitioning](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh). This gives customers a wide range of options when installing an operating system. ESXi is an exception because it is a UNIX-based, proprietary system with a proprietary installer.
+OVHcloud installations of ESXi are therefore compliant with the configuration set by the software publisher. Since ESXi 7.0, it is possible to choose between 4 different predefined partitioning layouts. This guide will show you how to install ESXi 8 and select a partitioning layout in the [OVHcloud Control Panel](/links/manager) or via the [OVHcloud API](/links/api). + ## Requirements -- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with ESXi -- Access to the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and/or the [OVHcloud API](/links/api) +- A [dedicated server](/links/bare-metal/bare-metal) **ready to be installed/reinstalled** in your OVHcloud account that is compatible with [ESXi 8 hardware requirements](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/esxi-upgrade-8-0/upgrading-esxi-hosts-upgrade/esxi-requirements-upgrade/esxi-hardware-requirements-upgrade.html) +- Access to the [OVHcloud Control Panel](/links/manager) and/or the [OVHcloud API](/links/api) > [!alert] > @@ -29,7 +26,7 @@ OVHcloud installations of ESXi are therefore compliant with the configuration se ## Instructions -ESXi 7.0 introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](https://ovh.com/manager/#/dedicated/configuration) and the [OVHcloud API](/links/api). +ESXi 7.0 and later versions introduced a [boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) because the increased size of the system partition could cause issues, especially on systems with small disks. OVHcloud includes this feature in the [OVHcloud Control Panel](/links/manager) and the [OVHcloud API](/links/api). Even with multiple disks available on a server, the ESXi OS installation uses only the first disk of the targeted disk group (see [OVHcloud API and OS Installation - Disk Groups](/pages/bare_metal_cloud/dedicated_servers/partitioning_ovh#disk-group)). Other disks may be configured afterwards to be used for virtual machines (see [How to add a datastore](/pages/bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration#add-datastore)). @@ -113,7 +110,7 @@ Example of payload: ```json { - "operatingSystem": "esxi70_64", + "operatingSystem": "esxi80_64", "storage": [ { "partitioning": { @@ -131,7 +128,7 @@ To list the different available partitioning schemes for an OVHcloud template, y > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme > -For example, for `esxi70_64` it will return: +For example, using the template name `esxi80_64` will return: ```json [ @@ -149,6 +146,17 @@ In order to get the details of the partitioning scheme dynamically, you can use > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition > +For example, using the scheme name `default` will return: + +```json +[ + "/scratch", + "/bootbank", + "/altbootbank", + "/vmfs/volumes/datastore1" +] +``` + You can use the following API call to get the details for each partition: > [!api] @@ -156,6 +164,23 @@ You can use the following API call to get the details for each partition: > @api {v1} /dedicated/installationTemplate GET /dedicated/installationTemplate/{templateName}/partitionScheme/{schemeName}/partition/{mountpoint} > +For example, using the mountpoint `/bootbank` will return: + +```json +{ + "order": 2, + "filesystem": "fat16", + "mountpoint": "/bootbank", + "size": { + "value": 4095, + "unit": "MB" + }, + "raid": "0", + "type": "primary", + "volumeName": "" +} +``` + ## Go further [Boot option to configure the size of ESXi system partitions](https://kb.vmware.com/s/article/81166) diff --git a/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.en-gb.md index ae7521a6aa6..0266704694d 100644 --- a/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.en-gb.md @@ -4,9 +4,6 @@ excerpt: "Find the most frequently asked questions about the wave of attacks tar updated: 2024-09-13 --- -> [!warning] -> The ESXi hypervisor is no longer supported by OVHcloud. Find more information on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objective Following a major event on pre-7.0 U3i ESXi servers on February 3rd 2023, a wave of attacks is currently underway on these servers. diff --git a/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.fr-fr.md index 3aef2b172ce..9aec38f2c08 100644 --- a/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/faq-esxi/guide.fr-fr.md @@ -4,9 +4,6 @@ excerpt: "Retrouvez les questions les plus fréquemment posées sur la vague d'a updated: 2024-09-13 --- -> [!warning] -> L'hyperviseur ESXi n'est plus supporté par OVHcloud. Retrouvez plus d'informations sur [cette page dédiée](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). - ## Objectif Suite à un événement majeur survenu sur des serveurs ESXi de version antérieure à la 7.0 U3i le 03 février 2023, une vague d'attaques est actuellement en cours sur ce type de serveurs. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.de-de.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.de-de.md index 115462c3f24..be4c2efd288 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.de-de.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.de-de.md @@ -122,11 +122,6 @@ Sie können nun Ihre VM starten und zu den nächsten Schritten, abhängig vom in #### VMware ESXi -> [!warning] -> -> Der ESXi Hypervisor wird von OVHcloud nicht mehr unterstützt. Weitere Informationen finden Sie auf [dieser Seite](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > Die folgenden Anweisungen gelten für einen virtuellen Rechner, der zuvor mit einem bereits installierten Betriebssystem erstellt wurde. Wenn Sie keine VM erstellt haben, lesen Sie die Anleitung [Eine virtuelle Maschine im VMware Host-Client erstellen](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) (EN) auf der VMware-Seite. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-asia.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-asia.md index 97ef6f5b325..8886753b916 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-asia.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-asia.md @@ -124,11 +124,6 @@ Now you can start the VM and proceed with the [configuration steps](#configurati #### VMware ESXi -> [!warning] -> -> The ESXi hypervisor is no longer supported by OVHcloud. More information can be found on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-au.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-au.md index fe3401a720d..33ab5e3555c 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-au.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-au.md @@ -124,11 +124,6 @@ Now you can start the VM and proceed with the [configuration steps](#configurati #### VMware ESXi -> [!warning] -> -> The ESXi hypervisor is no longer supported by OVHcloud. More information can be found on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ca.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ca.md index d05a79028cb..fcbe99112aa 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ca.md @@ -124,11 +124,6 @@ Now you can start the VM and proceed with the [configuration steps](#configurati #### VMware ESXi -> [!warning] -> -> The ESXi hypervisor is no longer supported by OVHcloud. More information can be found on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-gb.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-gb.md index e0816aeef20..a08e02d396e 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-gb.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-gb.md @@ -124,11 +124,6 @@ Now you can start the VM and proceed with the [configuration steps](#configurati #### VMware ESXi -> [!warning] -> -> The ESXi hypervisor is no longer supported by OVHcloud. More information can be found on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ie.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ie.md index 72fd06c24a0..fce279afee8 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ie.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-ie.md @@ -124,11 +124,6 @@ Now you can start the VM and proceed with the [configuration steps](#configurati #### VMware ESXi -> [!warning] -> -> The ESXi hypervisor is no longer supported by OVHcloud. More information can be found on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-sg.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-sg.md index 076b2e6e5d0..8979d5aea30 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-sg.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-sg.md @@ -124,11 +124,6 @@ Now you can start the VM and proceed with the [configuration steps](#configurati #### VMware ESXi -> [!warning] -> -> The ESXi hypervisor is no longer supported by OVHcloud. More information can be found on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-us.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-us.md index 6cbcb03e33d..4f45e739ac1 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.en-us.md @@ -124,11 +124,6 @@ Now you can start the VM and proceed with the [configuration steps](#configurati #### VMware ESXi -> [!warning] -> -> The ESXi hypervisor is no longer supported by OVHcloud. More information can be found on [this dedicated page](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > The following instructions apply to a previously created VM with an OS already installed. If you have not created a VM, please review the guide [Create a Virtual Machine in the VMware Host Client](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) on the VMware page. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-es.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-es.md index 9a04cebf842..70f7cc1e432 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-es.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-es.md @@ -125,11 +125,6 @@ Una vez iniciado el VPS, podrá pasar a las siguientes etapas, en función del s #### VMware ESXi -> [!warning] -> -> El hipervisor ESXi ya no es compatible con OVHcloud. Más información en [esta página dedicada](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > Las siguientes instrucciones se aplican a una máquina virtual creada anteriormente con un sistema operativo instalado. Si no ha creado ninguna MV, consulte la guía [Crear una máquina virtual en el cliente host de VMware](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) (EN) en la página VMware. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-us.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-us.md index 2519fe7733f..3bb3d4e5453 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-us.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.es-us.md @@ -125,11 +125,6 @@ Una vez iniciado el VPS, podrá pasar a las siguientes etapas, en función del s #### VMware ESXi -> [!warning] -> -> El hipervisor ESXi ya no es compatible con OVHcloud. Más información en [esta página dedicada](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > Las siguientes instrucciones se aplican a una máquina virtual creada anteriormente con un sistema operativo instalado. Si no ha creado ninguna MV, consulte la guía [Crear una máquina virtual en el cliente host de VMware](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) (EN) en la página VMware. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-ca.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-ca.md index f2665332e62..88684db68f0 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-ca.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-ca.md @@ -123,11 +123,6 @@ Vous pouvez maintenant démarrer votre machine virtuelle et passer aux étapes s #### VMware ESXi -> [!warning] -> -> L'hyperviseur ESXi n'est plus supporté par OVHcloud. Retrouvez plus d'informations sur [cette page dédiée](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > Les instructions suivantes s'appliquent à une machine virtuelle créée précédemment avec un système d'exploitation déjà installé. Si vous n'avez pas créé de VM, consultez le guide [Créer une machine virtuelle dans le client hôte VMware](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) (EN) sur la page VMware. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-fr.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-fr.md index 31224e77238..8448da85a08 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-fr.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.fr-fr.md @@ -123,11 +123,6 @@ Vous pouvez maintenant démarrer votre machine virtuelle et passer aux étapes s #### VMware ESXi -> [!warning] -> -> L'hyperviseur ESXi n'est plus supporté par OVHcloud. Retrouvez plus d'informations sur [cette page dédiée](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > Les instructions suivantes s'appliquent à une machine virtuelle créée précédemment avec un système d'exploitation déjà installé. Si vous n'avez pas créé de VM, consultez le guide [Créer une machine virtuelle dans le client hôte VMware](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) (EN) sur la page VMware. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.it-it.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.it-it.md index f770fe71860..1b461e6e3ee 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.it-it.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.it-it.md @@ -124,11 +124,6 @@ A questo punto puoi avviare la tua macchina virtuale e passare agli step success #### VMware ESXi -> [!warning] -> -> L'hypervisor ESXi non è più supportato da OVHcloud. Per maggiori informazioni, visita [questa pagina dedicata](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > Le istruzioni seguenti sono valide per le macchine virtuali create in precedenza con un sistema operativo preinstallato. Se non hai creato una VM, consulta la guida [Creare una macchina virtuale nel client host VMware](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) (EN) sulla pagina VMware. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pl-pl.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pl-pl.md index f148e82ff13..9a1a353d2a2 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pl-pl.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pl-pl.md @@ -124,11 +124,6 @@ Teraz możesz uruchomić wirtualną maszynę i przejść do kolejnych etapów, w #### VMware ESXi -> [!warning] -> -> Hypervisor ESXi nie jest już wspierany przez OVHcloud. Więcej informacji na temat [tej strony dedykowanej](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > Poniższe instrukcje dotyczą utworzonej wcześniej maszyny wirtualnej z zainstalowanym systemem operacyjnym. Jeśli nie posiadasz wirtualnej maszyny, zapoznaj się z przewodnikiem [Tworzenie maszyny wirtualnej w kliencie hosta VMware](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID--F968-4983-A230-.html) na stronie VMware. diff --git a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pt-pt.md b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pt-pt.md index 24eaa9891da..714e6cff849 100644 --- a/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pt-pt.md +++ b/pages/bare_metal_cloud/dedicated_servers/network_bridging/guide.pt-pt.md @@ -127,11 +127,6 @@ Pode desde já iniciar a sua máquina virtual e passar às etapas seguintes, em #### VMware ESXi -> [!warning] -> -> O hipervisor ESXi já não é suportado pela OVHcloud. Encontre mais informações em [esta página dedicada](/pages/bare_metal_cloud/dedicated_servers/esxi-end-of-support). -> - > [!warning] > > As seguintes instruções aplicam-se a uma máquina virtual criada anteriormente com um sistema operativo já instalado. Se não criou nenhuma VM, consulte o guia [Criar uma máquina virtual no cliente host VMware](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.hostclient.doc/GUID-77AB6625-F968-4983-A230-A020C0A70326.html) (EN) na página VMware. diff --git a/pages/index.md b/pages/index.md index ede7f48a9cc..f0ae8724795 100644 --- a/pages/index.md +++ b/pages/index.md @@ -169,7 +169,6 @@ + [Managing Intel SGX on an Infrastructure server](bare_metal_cloud/dedicated_servers/sgx-enable-and-use) + [Uninstalling the RTM v2 monitoring system](bare_metal_cloud/dedicated_servers/rtm-uninstall) + [Configure a custom iPXE script to boot your server from the OVHcloud API](bare_metal_cloud/dedicated_servers/ipxe-scripts) - + [VMware ESXi on OVHcloud Dedicated Servers - End of Support](bare_metal_cloud/dedicated_servers/esxi-end-of-support) + [Server Backup and Restore](bare-metal-cloud-dedicated-servers-backup-restore) + [Preparing a Bare Metal Server backup with Veeam Enterprise](bare_metal_cloud/dedicated_servers/veeam-enterprise-server-backup-preparation) + [Backing up a Bare Metal Linux Server with Veeam Enterprise](bare_metal_cloud/dedicated_servers/veeam-enterprise-server-backup-linux) @@ -214,7 +213,7 @@ + [Hot-swapping a disk on a server with a software RAID configuration](bare_metal_cloud/dedicated_servers/hotswap_raid_soft) + [Configuring MegaRAID for RAID Level 0](bare_metal_cloud/dedicated_servers/megaraid_config) + [Configuring the storage on a HGR-STOR-2 server](bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration) - + [Dedicated Servers - ESXi Partitioning](bare_metal_cloud/dedicated_servers/esxi-partitioning) + + [How to install VMware ESXi 8 on a dedicated server](bare_metal_cloud/dedicated_servers/esxi-partitioning) + [Dedicated Servers - Upgrading your SSD Solidigm D7-P5520 firmware](bare_metal_cloud/dedicated_servers/solidigm_d7-p5520_fw_update) + [Advance Dedicated Servers - Upgrading your Samsung NVMe PM9A1 firmware](bare_metal_cloud/dedicated_servers/samsung-nvme-fw-upgrade) + [High Grade Dedicated Servers - Upgrading your SSD SAS Western Digital SS300 firmware](bare_metal_cloud/dedicated_servers/wd-sas-fw-upgrade) From dd3ccd1e396ac518007e62619d01d1190935be5c Mon Sep 17 00:00:00 2001 From: Yoann Cosse Date: Fri, 12 Sep 2025 16:44:23 +0200 Subject: [PATCH 3/3] Moving ESXi installation guide in the index --- pages/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/index.md b/pages/index.md index f0ae8724795..2cf8105c3f2 100644 --- a/pages/index.md +++ b/pages/index.md @@ -169,6 +169,7 @@ + [Managing Intel SGX on an Infrastructure server](bare_metal_cloud/dedicated_servers/sgx-enable-and-use) + [Uninstalling the RTM v2 monitoring system](bare_metal_cloud/dedicated_servers/rtm-uninstall) + [Configure a custom iPXE script to boot your server from the OVHcloud API](bare_metal_cloud/dedicated_servers/ipxe-scripts) + + [How to install VMware ESXi 8 on a dedicated server](bare_metal_cloud/dedicated_servers/esxi-partitioning) + [Server Backup and Restore](bare-metal-cloud-dedicated-servers-backup-restore) + [Preparing a Bare Metal Server backup with Veeam Enterprise](bare_metal_cloud/dedicated_servers/veeam-enterprise-server-backup-preparation) + [Backing up a Bare Metal Linux Server with Veeam Enterprise](bare_metal_cloud/dedicated_servers/veeam-enterprise-server-backup-linux) @@ -213,7 +214,6 @@ + [Hot-swapping a disk on a server with a software RAID configuration](bare_metal_cloud/dedicated_servers/hotswap_raid_soft) + [Configuring MegaRAID for RAID Level 0](bare_metal_cloud/dedicated_servers/megaraid_config) + [Configuring the storage on a HGR-STOR-2 server](bare_metal_cloud/dedicated_servers/hgrstor2_system_configuration) - + [How to install VMware ESXi 8 on a dedicated server](bare_metal_cloud/dedicated_servers/esxi-partitioning) + [Dedicated Servers - Upgrading your SSD Solidigm D7-P5520 firmware](bare_metal_cloud/dedicated_servers/solidigm_d7-p5520_fw_update) + [Advance Dedicated Servers - Upgrading your Samsung NVMe PM9A1 firmware](bare_metal_cloud/dedicated_servers/samsung-nvme-fw-upgrade) + [High Grade Dedicated Servers - Upgrading your SSD SAS Western Digital SS300 firmware](bare_metal_cloud/dedicated_servers/wd-sas-fw-upgrade)