Thursday, May 25, 2023

vSAN ESA Raid 1

 vSAN ESA Raid 1

2 way mirror vm

The perf leg is a two way mirror

The cap leg is redundant and striped

3 way mirror vm

The perf leg is a three way mirror

The cap leg is redundant and striped

4 way mirror vm

The perf leg is a four way mirror

The cap leg is redundant and striped

vSAN ESA Raid 5 and Raid 6

 vSAN ESA RAID 5 and RAID 6 vms

Note: The layout of the cap leg varies depending on the number of hosts.

Raid 5 vm with 8 hosts

The perf leg is a two way mirror.

The cap leg is Raid 5

Raid 6 vm with 8 hosts

The perf leg is a three way mirror.

The cap leg is Raid 6

Monday, May 1, 2023

VCLS and Retreat Mode

Activating Retreat Mode

New as of vSphere 7.0U1

Step 1: Select the cluster that needs to go into retreat mode.

Step 2: Look at the url of the cluster and document the four digits that follow domain-c word

Step 3: Select your vCenter Server and go to Configure

Step 4: Add an advance setting called config.vcls.clusters.domain-c????.enabled 

Step 5: In the value column, Add the word False

          Step 6: Click on ADD and then click on SAVE 



This change will automatically shut down and then delete these virtual machines.

For more information:

Tuesday, November 30, 2021

vSAN object related commands

 vSAN is an object based file system. Although typically monitored via the vSphere Client, there are plenty of commands available to understand objects and their health. What follows are a few of these commands.

1. esxcli vsan debug object list.  This command displays all of the objects and components. It also displays information about the policies used, the state of the components, their location and vote count.

2. esxcli vsan debug object health summary get. Use this command to see how many objects are healthy or not.

3. esxcli vsan debug object overview. Another command that can be used to quickly view all of the objects, size, policy used and information about healthy components.

Friday, October 2, 2020

How to mount a Remote vSAN Datastore. HCI Mesh

 Step 1: Select the "client" vSAN cluster (the one that wants to mount the other's datastore) and click on Configure. In this setup, both vSAN clusters are managed by the same vCenter server as you can see and happen to be in the same Datacenter.

Step 2: Under vSAN, select Datastore Sharing like shown below. Notice that two clusters exist in this case and both are controlled by the same vCenter Server.


Step 4: Select the remote datastore and click on Next.

Step 5: Verify that everything looks good and click on Finish. Notice the two captures. One shows you why it may fail, the other one after fixing whatever may be incompatible with HCI Mesh.

Final Note: 

Verify that you can access both datastores from one cluster. Feel free to storage vMotion vms between the two datastores. Use commands like df -h or the gui to look at more information. According to Cormac Hogan, one cluster can mount up to 5 remote vSAN datastores. Be aware that HCI Mesh requires Enterprise or Enterprise + licenses.  

Useful YouTube video:

Thursday, September 24, 2020

How to Create a Basic Docker Container

 How to create a basic Docker container

Step 1: install docker in your pc, laptop or vm.

# sudo apt-get install

# sudo systemctl start docker

# sudo systemctl enable docker

Step 2: create a directory for testing purposes and access such folder

# mkdir Dockerfiles

# cd Dockerfiles

Step 3: Create a docker file and call it Dockerfile

# vi Dockerfile

# Specify the base image to use, gets downloaded automatically

FROM ubuntu

# Specify the maintainer and email address


RUN apt-get update

# Specify the command to run

CMD [#echo", "Hello guys...! from my first image"]

Step 4: Build your image and tag it

# sudo docker build -t myimage:1.0 .

    Sending build context to Docker daemon  2.048kB

    Step 1/4 : FROM ubuntu

     ---> bb0eaf4eee00

    Step 2/4 : MAINTAINER *** <***>

     ---> Using cache

     ---> 2c30cf6f43fb

    Step 3/4 : RUN apt-get update

     ---> Using cache

     ---> 832660e5cdc3

    Step 4/4 : CMD ["echo", "Hello guys...! from my first image"]

     ---> Using cache

     ---> 168e1047d6a4

    Successfully built 168e1047d6a4

    Successfully tagged myimage:1.0

Step 5: List the images available

$ sudo docker image list

REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

myimage             1.0                 b6f0f1350590        2 minutes ago       95.8MB

ubuntu              latest              bb0eaf4eee00        8 days ago          72.9MB

Step 6: Run the image for testing purposes

# sudo docker run image_id

    Hello guys...! from my first image

Final Note: 

You can pull more images to play with using sudo docker pull image_name