Video 10:

iSCSI Storage (StarWind)

In this video, we'll use StarWind, a software solution, to set up an iSCSI server
on Windows Server. The we follow these steps:
Install StarWind: We begin by installing StarWind on the Windows Server,
serving as the foundation for the iSCSI server.
Add StarWind Server: After installation, we add a StarWind server with the
address 127.0.0.1:3261, representing the local loopback interface and port.
Connect with Default Credentials: We connect to the StarWind server using
default login "root” and password “starwind" for a secure initial connection.
Add a Hard Disk: We add a hard disk to the iSCSI server, specifying type,
creation method, size, name, and target alias.
Allow Multiple Connections: We have to configure the iSCSI server to allow
multiple concurrent connections, enabling simultaneous resource access.
Change Startup Type: Lastly, we set the "Microsoft iSCSI Initiator Service"
startup type to Automatic for seamless iSCSI connection during system boot.
 Video 11:
iSCSI Datastore / VMware ESXi Client
In this video, we configure the ESXi Host to connect with an iSCSI server:
1. Enable Software iSCSI: Head to "Storage Adapters," select "Software
iSCSI," and enable the feature.
2. Add Dynamic Target: Add a dynamic target with the iSCSI server's IP
address and port 3260.
3. Rescan and Refresh: Rescan and refresh to ensure recognition of the
iSCSI storage.
4. Device Configuration: Navigate to the "Devices" tab, perform another
rescan and refresh to detect the iSCSI storage.
5. Create Datastore: Use the added disk to create a new datastore.
6. Verification : Verify the configuration using ESXi Shell commands:
 esxcli storage filesystem list: Check for the new filesystem.
 esxcli storage san iscsi list: Confirm iSCSI adapter status.
 esxcli iscsi session list: View active iSCSI sessions.
 Video 12:
iSCSI Datastore / vSphere vCenter
In this video, the process replicates the steps from a prior video, but with a
notable difference—now, the vCenter is employed for the configuration:
1. Add Software iSCSI Adapter: Begin by adding a software iSCSI adapter to
the specific host intended to connect to the iSCSI server. This adapter
facilitates the communication between the host and the iSCSI storage.
2. Add Dynamic Target: Once the software iSCSI adapter is added, proceed
to include a dynamic target within its configuration. This involves
specifying the necessary details, such as the IP address of the iSCSI
server.
3. Create Datastore: The final step involves creating a datastore directly
from the disk obtained through the iSCSI connection. This datastore
serves as a logical storage container within the vCenter environment.
 Video 13:
MS Server iSCSI Storage
In this video, we opt for Windows Server's Server Manager to build an iSCSI
server:
1. Add iSCSI Target Server Role: Begin by selecting "Add roles and features"
and choose the iSCSI target server role.
2. Create iSCSI Virtual Disk: Navigate to "Files and Storage Services" > iSCSI
> Create an iSCSI virtual disk. Specify location, name, and size.
3. Add Initiator for Access: Complete the process by adding a specific
initiator to access the virtual disk, allowing controlled access to the iSCSI
storage.
 Video 14:
iSCSI ESXi / Network Port Binding
In this video, we configure our ESXi host to connect to an iSCSI server in
another subnet. We follow similar steps as before, with a modification: adding
port binding. This requires assigning the ESXi host NICs in both subnets,
ensuring communication between the host and the iSCSI server in the
respective subnets.
Watch Videos For DEMO
Note: I had to make two videos because my PC lagged and the recording got
cut, also I have already made the configuration, but the recording got corrupted
and I had to do it again, that’s why there is 2 existing iSCSIs and Target is pre-
configured.
 Video 15:
iSCSI vCenter / Network Port Binding
In this video, the focus is on visually demonstrating port binding in the vCenter
Server. The purpose is to highlight that the same approach used in a previous
video, which involves configuring port binding, can also be executed directly
from the vCenter interface. This emphasizes the flexibility of managing and
configuring port binding settings through the centralized vCenter Server.
 Video 16:
NFS Storage / ESXi
In this video, we establish an NFS (Network File System) server on our Windows
Server:
1. Create Shared Folder: Begin by creating a folder to be shared.
2. Enable NFS in Server Manager: Utilize the Server Manager utility to
enable NFS.
3. Configure NFS Sharing: Access the NFS Sharing tab within the folder, then
proceed to Manage NFS Sharing > Share this folder, specifying share
permissions.
4. Create Datastore in vCenter: Navigate to vCenter to create a Datastore
using the configured NFS.
5. Verify Changes with esxcli: Confirm the changes using esxcli commands,
specifically esxcli storage filesystem list and esxcli storage nfs41 list.
 Video 17:
VM Templates / Customization
Specifications
In this video, the process of creating a VM template is demonstrated within the
vCenter environment. Starting by selecting a specific VM, the user initiates the
cloning process to generate a template, assigning it a name and determining
the storage location. Compute resources, such as the host (192.168.1.30), and
the designated storage device are specified. Notably, the examination of
template files reveals the use of .vmtx instead of the traditional .vmx extension.
Configuration of the template involves tailoring settings for different operating
systems, including Linux and Windows, covering details such as OS,
computer/domain, time zone, network, and DNS. To create a VM from the
template, we select "New VM from This Template," providing details such as
the VM name, compute resource, storage preferences, and customizable
options for OS policies or hardware attributes like RAM and CPU. The final step
involves running the newly created VM with the specified configurations.
 Video 18:
Migrate Storage Only (Local2Local)
In this video, we perform live storage migration of a running VM from one
host's datastore to another. In vCenter, the VM is selected, and the migration
option is chosen. Opting for a storage-only migration, the destination storage is
specified. Throughout the process, ICMP requests are sent to test VM
continuity, ensuring its operational status during the storage migration.
 Video 19:
Migrate Storage Only (Local2Shared)
In this video, a new software iSCSI adapter is configured to establish a
connection with a remote iSCSI server, allowing the creation of a corresponding
datastore. Following this, the video replicates a prior procedure, with the sole
distinction being the migration of the VM's storage to the newly established
remote storage originating from the iSCSI setup.
 Video 20:
Migrate Compute Ressource Only
This video introduces an alternative migration option: compute resource
migration between hosts. The first step is creating a VMkernel adapter for
vMotion on both hosts. Subsequently, the migration process unfolds, allowing
the selection of the target host, designation of destination networks, and the
establishment of vMotion priority.
 Video 21:
Migrate Compute Ressource & Storage
In this video, the focus is on the third migration option, a hybrid approach
involving both compute resource and storage migration. Enabled by the
vMotion service on both hosts, this method combines elements from the
previous two. The process involves specifying the target host for migration as
well as the storage destination.
 Video 22:
Migrate EVC CPU
This video highlights the use of EVC (Enhanced vMotion Compatibility) for
CPUs, allowing seamless migration across different CPU generations. When
attempting to migrate both storage and compute resources to a host with a
different CPU, an error is encountered due to varying hardware requirements.
To address this issue, the tutorial demonstrates how to navigate to the specific
VM and adjust the VMWare EVC settings, providing a solution for compatibility
during the migration process.
 Video 23:
vSphere Cluster Service vCLS
This video explores a vSphere Cluster, commencing with its creation within a
vCenter Data Center. The process includes adding a host to the cluster and
concurrently generating a lightweight virtual machine named vCLS. This virtual
machine plays a pivotal role in overseeing essential cluster services, including
vSphere DRS and vSphere HA. Notably, the number of these vCLS virtual
machines is limited to three, regardless of the quantity of hosts incorporated
into the cluster.
 Video 24:
vSphere High Availability HA Demo
This video provides a demonstration of vSphere HA. The process involves
configuring a cluster with added hosts, enabling HA through settings
modification, and verifying the running status of the vSphere High Availability
Agent on one of the hosts. Subsequently, the tutorial showcases the resilience
of vSphere HA by powering off a host (192.168.1.10) and observing the
seamless migration of a VM from the powered-off host to another
(192.168.1.20).