> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/productos/servers-2/details/technical-specs.md).

# Características Técnicas

Las especificaciones de un servidor de Plenit: cómputo, almacenamiento, hardware, virtualización y red física

Las especificaciones de un servidor de Plenit. Para decidir qué tamaño necesitas, ve a [Dimensiona tu servidor](/productos/servers/concepts/size-cpu-ram-disk.md) en Conceptos.

### Cómputo

|            |                             |
| ---------- | --------------------------- |
| vCPU       | Hasta 32                    |
| RAM        | Hasta 128 GB                |
| Procesador | Intel Xeon Scalable         |
| Escalado   | En caliente, sin reinstalar |

### Almacenamiento

|                  |                                              |
| ---------------- | -------------------------------------------- |
| Tecnología       | NVMe · NetApp All-Flash (ONTAP)              |
| Disco de sistema | Desde 60 GB                                  |
| Discos de datos  | Adicionales, cada uno con copia de seguridad |
| Redimensionado   | Ampliación en caliente                       |

La reducción de un disco es más delicada que la ampliación; el procedimiento está en How-to.

### Hardware

|              |                         |
| ------------ | ----------------------- |
| Servidores   | Dell                    |
| Procesador   | Intel Xeon Scalable     |
| Memoria      | DDR5 ECC                |
| Redundancia  | Clúster N+1             |
| Alimentación | Doble fuente (PSU)      |
| Red del host | Enlaces agregados (LAG) |

Si un host del clúster falla, sus máquinas virtuales se reinician en otro host disponible. Esta es la resiliencia de la infraestructura física; el diseño de alta disponibilidad por zonas lo defines tú (lo verás en Conceptos cuando esté disponible).

### Virtualización

|              |                   |
| ------------ | ----------------- |
| Hipervisor   | KVM               |
| Orquestación | Apache CloudStack |

### Red física

|                       |            |
| --------------------- | ---------- |
| Arquitectura          | Spine-leaf |
| Virtualización de red | VXLAN      |

### Dónde seguir

* Para regiones y zonas: [Regiones y zonas de disponibilidad](/productos/servers/details/regions-and-availability-zones.md).
* Para el compromiso de disponibilidad: [Disponibilidad del servicio](/productos/servers/details/service-availability.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.plenit.com/productos/servers-2/details/technical-specs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.