Luis Freixas – Luis Knowledge Base

15 de marzo de 2025

Installing Nutanix CE in Supermicro E300-9D

After some time trying and playing around with the Nutanix CE in Nested mode in my lab,
I finally put my hands into a little monster able to handle a Single Node Cluster, My Supermicro E300-9D!

Im going to show you the process of Installation, cluster (Single node) creation, in future posts, we will continue seeing new stuff, step by step.

Let’s get started:

First of all, as we already know, lets download the Nutanix CE from the community portal, to do so, you must be registered, and after installation, you will need your restoration to make it work properly.

after downloading the CE ISO, lets boot from the ISO and get started…

Now is time to add some data,
I havee 3 disks, Boot, CVM and Data, choose the ones you would like to use, and then,
configure the IP Details as shown,
You need 1 IP for the AHV Host, One for the CVM, gateway and subnet mask.

after few minutes, done!
Now, is time to remove the boot media, answer with a Y, and continue…

Now, after the first boot of the server,
we are going to ssh to the AHV host, with the IP we setup earlier
username: root
password: nutanix/4u

then, from the AHV host, we are going to ssh to the CVM to the IP we also setup earlier,
in this case
username: nutanix
password: nutanix/4u

Now, we are into the CVM via ssh, its time to create the Cluster,
in this case, Single node cluster
the command I used is the following:

cluster -s <CVM IP> —-redundancy_factor_1 —-dns_server 1.1.1.1 create

Now, the cluster has been created successfully, lets see the server console.

Now, lets connect to the web UI to continue working on our new cluster

to connect, we will use the CVM IP Address and the port 9440

Default username: admin
Default password: nutanix/4u

Now, is time to change the admin password

Here is an important step, we need to provide our Nutanix Community credentials, as we created them before to download the ISO, if you don’t have any, its time to create an account, 😉

Done!

Here is our beautiful WebUI of our Nutanix CE Single Node Cluster!!

I hope you like it,

this setup is in a physical server,
Supermicro E300-9D, 128GB RAM, 3 SSD disks.

In the next entry, initial config and run.

cheers!

4 de marzo de 2025

OOTBI New Release 1.6

I recently wrote an entry about updating our OOTBI cluster
https://lfconsulting.org/updating-our-ootbi-cluster

Now, Object First has launched a new release of OOTBI, 1.6.63.10886

These are the new features described in the release:

The update process, as shown before, is super straightforward and allows you to update and reboot your cluster in a few clicks without any stress or «fancy» steps, guides, or troubleshooting.

The feature I was looking forward to getting, and finally is here, is the user’s roles,
I’m super excited about these:

we will continue testing the new features, and describe them in the future.

cheers.

21 de febrero de 2025

Updating our OOTBI Cluster

Hi, it’s been a journey, with the OOTBI topics here:

https://lfconsulting.org/object-first-ootbi
https://lfconsulting.org/object-first-ootbi-primer-arranque-y-configuracion
https://lfconsulting.org/object-first-ootbi-pasos-finales-para-estar-ready
https://lfconsulting.org/deploying-a-object-first-ootbi-vsa-lab
https://lfconsulting.org/expanding-our-object-first-ootbi-cluster-adding-nodes-and-vbr-space

Now, is time to update our cluster,
One of the most important reasons to implement OOTBI, is the ability to get updates, improvements and upgrades straight away, keeping yourself in the important task of protecting the Infrastructure and data,
Object First has you covered with the Tech and Updates.

Let’s follow up the process witha few screenshots and thoughts:

When it’s time for an update, our console will tell us, also, at any time, we can check it in the settings menu as well.

Let’s login to our web GUI, and check the events and alerts, as you can see, the system is telling us that an update is available:

We go to the menu under settings. Cluster Update and the system checks for the latest updates

The Update cluster button becomes purple, and you can see the available update, let’s hit the button and proceed

IMPORTANT!

Let’s Install!

And done!
Now our cluster is up to date!

I hope you like it

as you can see, the process is super simple and straight forward,
and this is the main pilars of this technology, easy to use and maintain.

see you in the next one!

cheers!

27 de noviembre de 202427 de noviembre de 2024

Expanding our Object First OOTBI Cluster – adding nodes and VBR space

Hi, in a previous entry, we saw how to deploy and get up to work an OOTBI Virtual Appliance,
https://lfconsulting.org/deploying-a-object-first-ootbi-vsa-lab

We will add an extra node to the «Single Node Cluster» to become a multi-node one.

The steps are straightforward, let’s see them via screenshots with comments:

First of all, we need to deploy the OOTBI VSA which will be added to the cluster,
follow the guide from the previous entry, ending after the deployment (don’t create the Cluster again).

updating…
After the update, you will be pushed to the initial menu, go over it again, and the data (NIC config) will remain, just go forward and continue

OK, now, add your OOTBI CLUSTER IP ADDRESS,
The one we used/created in the previous entry, and the objectfirst user password we created.

Now you see the first two options blurry, and the cluster endpoint IP Address (Bottom left) is the same as the previous cluster.

IMPORTANT

Now, that our Cluster setup is done, we need to update the information in our VBR to get the space and the cluster working fine.
In the picture below you can see that the S3 bucket from the cluster remains at 1TB.

If we do the rescan repository it will give us an error like so.

Please Right click into the Repo, and re-run the setup wizard,
next, next, finish.

The thing that will happen is that, when extending the cluster, the certificate has changed, so now the VBR needs to grab it again from our OOTBI Cluster to work properly.

Running and ending the setup (properties) wizard again to update the certificate

Boom!
As you can see, after the re-config, the VBR sees 2TB of Storage, so the cluster has been updated!

Following the guide, I will add one more node, so we will have a 3TB Cluster!
Follow the same steps from before, and now, we will see the 3 Nodes and the 3TB storage!

IMPORTANT
Once again, run the setup (properties) wizard for the Repo once again to get the certificate updated!

In the picture, you can see the wizard updating the cert and the bucket now shows 3TB Free instead of 2TB.

cheers!

25 de noviembre de 2024

Deploying Veeam Data Platform on the Lab – Recovery Orchestrator

I want to share with you all my initial setup of a small Lab for the Veeam Data Platform
which is installing VBR + VONE + Recovery Orchestrator.

In my case, I don’t have too many resources, so, for lab proposes, all three roles will be deployed in the same machine

The wizard takes care of installing the tools, just asking you the necessary things to get it done.

As you will see, installing the Orchestrator, includes the VBR and VONE.

If you haven’t downloaded the Veeam data platform, please do…
This is the virtual specs for the VM where VDP is installed on my lab:

Let’s follow up on the screenshots and the comments on the installation.

Here ends the installation.

Now, let’s take a look into the consoles, with very high level / initial configuration:

VBR – We already know how it looks, Showing you adding a Job from a Hyper-V VM.
Initial setup with Backup config, etc…

Veeam One

Recovery Orchestrator Web

Lets add our VBR server, so Veeam One can start collecting info from it,
also, lets add from our infra our Hypervisors, to get more details and monitoring.

In the next entry, we will add an ESXI host to the Recovery Orchestrator and start setting up a recovery plan (a super simple, lab test).

cheers.

11 de noviembre de 202412 de noviembre de 2024

Deploying a Object First OOTBI VSA (Lab)

Luckily I have the opportunity to have access to a VSA OOTBI for my Lab,
So I would like to share the deployment and initial steps to get it up and running in my Vsphere lab with y’all.

Let`s get started, by login into our Vsphere console, and starting the new VM process, deploying a VM from OVA:

After finishing the deployment, it is time to open the remote console to continue the wizard from it,

As you can read from my previous entry, in Spanish:
https://lfconsulting.org/object-first-ootbi-primer-arranque-y-configuracion

As you already may read from previous entries, in Spanish Im afraid, let’s create the cluster
yes, single node cluster:

OK, IMPORTANT! apply the updates, and no worries, after so, we will need to start the wizard again, but the info is kept, 😉

After updating, lets call the wizard again, I will continue in the next new screen, the previous info is saved, so just next next….

Here is the deal, lets setup the cluster name and IP Address

Define a password for the «objectfirst» user

INFO: how to connect to the Web UI, model, and S/N

Telemetry, very important to notify support in case of any issue

DONE, now both, setup new cluster and Join are bold, so all set.

Now, I will show you how to quickly create an S3 Key and a Bucket and how they look when added to VBR!

Grab and keep secure the info, you ill need it to setup the Repo in VBR.

Now lets create the Bucket, S3 Bucket – Create a Bucket

Of course Enable Versioning, so the bucket will be Immutable

Here you can see the Bucket added into VBR, ready to be use!

Cheers.

5 de noviembre de 20246 de noviembre de 2024

LAB- Deploying VBR13 – on Linux – OVA!

I want to share my initial screenshots of the Linux-based Veeam Backup & Replication Server.
Tech Preview: VBR on Linux (v13)

Private technology preview for Veeam 100, for non-production use only.

Let’s get started:

As you may know, let’s deploy the OVA in our Vsphere Host:

As always, follow the wizard…

Select where the VM is going to be stored

Important, LAB, so, Thin Prov.

Detailed resume, no worries for the error, is ok! It’s just lab and non-production, remember?

Booting and great looking…

Easy step, to see the assigned IP address to the VM, quick look into the VM properties

Now, it is time to open your favorite browser, and call the URL from the VBR IP Address, for the web console

Boom!
Look at this console, beautifully colorful.
Looking forward to working from it, especially day-to-day operations you don’t need the «heavy console».

Now, with a Vsphere host Added and some VMs

Now, time to show the «Heavy» Client, I will paste the pics, due to the fact that the installation is so straightforward

Stay tuned for more news regarding this VBR13 Linux-based!

cheers.

10 de septiembre de 202410 de septiembre de 2024

Cisco Meraki –

Hi there:
I would like to share with you my experience and what Im testing right now in my Lab,
I’ve got lucky to be able to test some Cisco Meraki devices, and they are looking so good.

We’ve got a Switch, Sensor, Door/window Sensor, and a couple of cameras, here the names and link to the descriptions

Now some more pics of the devices, they are very good looking:

In the next entry, we will get started with the Meraki Console, and adding the devices to our plan and start playing with them.

cheers.

1 de septiembre de 20241 de septiembre de 2024

Actualización Veeam VBR V12 a 12.2

Hola
Os dejo unos sencillos pantallazos de como ha sido mi actualización en el Lab de Veeam VBR 12 a la ultima version, 12.2, a pantallazos.

Primero que todo, descargamos la ISO de la última version de la web.

Una vez la tenemos, comienza la actualización

Hasta aquí, todo bien, pero, como veis, me pide reiniciar, dado que ese componente C++ estaba sin actualizar, así que nada, reiniciar el VBR y volver a empezar con el upgrade, y ahora, continúa sin problemas…

temas de lab, no tenemos siempre todos los recursos que quisiéramos….

(el repo S3 OOTBI lo tengo apagado, ya que es un Appliance Físico, y hago pruebas y lo apago)

Listo! Actualizado a la ultima version, y funcionando!!

Saludos.

30 de agosto de 202430 de agosto de 2024

Crear Cluster Nutanix (CE) Community Edition 2.1

Hola, en esta entrega, os voy a mostrar como he creado en mi laboratorio, un ESXi 8, de manera Nested un cluster de Nutanix CE 2.1 de 3 Nodos, de la manera más sencilla.

Partimos por recordar que, para la descarga del software como la iniciación del cluster, debemos estar registrados en la comunidad de Nutanix.

Ahora, nos loqueamos y accedemos al siguiente enlace, en el cual, encontraremos los ficheros necesarios para la instalación, en mi caso, la ISO de CE 2.1.

Una vez descargado, lo subimos, como es mi caso, a nuestro ESXi para poder realizar las instalaciones.

vale, ahora, crearemos las maquinas virtuales que serán nuestros 3 Nodos,
os dejo la captura de las especificaciones de las 3 vms:

En la parte de configuración avanzada, le he añadido una linea, para que los discos duros virtuales tengan serial number:

En las máquinas virtuales: Edición – Opciones – Avanzado – Editar configuración- añadir parámetro

Ahora vamos a seguir con los pantallazos y explicaciones:

Otro detalle a recordar, la configuración de nuestro vSwitch en el cual corre nuestro lab, debe ser como la siguiente:
Habilitando modo promiscuo y transmisiones falsificadas, sino, nos fallará la red.

Booteamos CE en nuestras vms, e instalamos el sistema rellenando los parámetros que nos solicita, como veis, los discos aparecen con Serial Number 😉 en los 3 nodos:

Aceptamos el EULA y continuamos:

Ya los tenemos instalados, ahora, toca reiniciar el ultimo, esperar un poco, y realizar la magia de la creación del cluster, vamos:

Nos vamos a lograr via SSH en una de las CVMs, en las IPs, una de las que pusimos, y desde ella, vamos a orquestar la instalación, recordar que el usuario por defecto utilizado es nutanix , y el password nutanix/4u

Tengo preparado mi comando, os lo pego e intento explicar lo mejor que se:

cluster -s 192.168.101.21,192.168.101.22,192.168.101.23 --dns_servers=192.168.101.1,1.1.1.1 --cluster_name=NTX-LAB-1 --cluster_external_ip=192.168.101.20 create

Le vamos a decir que ceee un cluster llamado NTX-LAB-1 con IP externa 192.168.101.20 con los DNS mostrados, al cual van a pertenecer las 3 CVMs, acabadas en 21, 22 y 23.

Aqui vemos lo que va haciendo, ejecutando las tareas en los diferentes nodos y creando los servicios.

Tras un rato, vemos este resultado, el cluster se ha creado Successful!

Aquí podeis ver los 3 nodos corriendo, cada uno con 32GB de ram, su disco utilizado, etc.

Ahora, vamos a entrar a Prism, y terminar la configuración inicial para poder acceder a nuestro cluster, para ello, en un navegador, escribimos la IP de una de las CVMs o La IP externa del cluster configurada en el comando anterior:

nos pide cambiar la contraseña por defecto por una nuestra

Una vez realizado esto, como os dije, nos pedirá nuestras credenciales de acceso a la community de Nutanix, las proporcionamos, y seguimos.

Listo!
Ya estamos en nuestro cluster!

Detalle, esto es un laboratorio de pruebas y aprendizaje, por ello este cluster está en modo «Nested», y si, chupa bastantes recursos, así que tenerlo en cuenta,
32Gb de RAM y 4vCPU por nodo, el disco está en Thin Provisioning, pero aun y todo ocupa.

Ahora, toca comenzar a «tunearlo» un poco, para luego desplegar nuestra primera vm, etc.

Como primer cambio, me gusta siempre definir el NTP Server, para que desde un comienzo todo tenga la hora correcta: