Technical blog

Steps to create Virtual Network in Nutanix and Virtual Network Services flow Virtual

Virtual Networking allows you to create completely isolated virtual networks that are separated from the physical network. You can do multi-tenant network provisioning with overlapping IP addresses, self-service network provisioning, and IP address preservation. Best of all, these isolated virtual networks provide security by default.

Open Nutanix Console using cluster IP

Click on drop down -> Select Network

Once you click Network tab you will see list of the created network and Network assigned to which VMs.

How to create a Virtual Network in Nutanix.

To flow the traffic within the Nutanix infra or outside we need to create a Virtual network and assign it to VM.

Steps to create Virtual Network in Nutanix

Click on drop down & Select VM

Click on Network Config

Click on User VM Interfaces -> To create network interface for VM

Give network Name and & vLAN ID.

If you are creating virtual network in your Lab environment and you don’t have vLAN to configure then you can give vLAN ID 0

Click Save.

To assign the network interface for VM

Select VM and click -> click Update

Select Add New NIC

Drop down and select the NIC

Full network tutorial

https://www.nutanixbible.com/12c-book-of-network-services-flow-virtual-networking.html

Volume Group in Nutanix and Mount in Client iSCSI Initiator Step by Step

What is the Volume Group in Nutanix and How to create? And mount in client or Initiator machines

VGs enable you to separate the data vDisks from the VM's boot vDisk. This separation allows you to create a protection domain that consists only of the data vDisks for snapshots and cloning. In addition, VGs let you configure a cluster with shared-disk access across multiple VMs. Supported clustering applications include Oracle Real Application Cluster (RAC), IBM Spectrum Scale (formerly known as GPFS), Veritas InfoScale, and Red Hat Clustering. To attach the VG to multiple VMs when you use the aCLI, create it with a shared=true attribute. If you use Prism, answer yes when you attach the VG to a second VM. There are two ways to use Nutanix VGs: default VG and VGLB.

Note- : In short we are creating iSCSI disk, that we create in Windows server and allow the initiator to connect the disk and use it as a shared disk for MS Cluster.

Click Table -> Storage

Click Volume Group

Enter Volume Group Name

Description

Click Add New Disk

Drop down and select the Storage Container.

Give the size and click Add

Click Add New Client to allow access to connect this Volume group

Enter client machine IP or IQN

Click Add

You may add multiple clients IP or IQN to connect with VG and use disk as cluster disk.

Click Save

Go to Table -> Storage -> Table and Volume Goup to see newly created Volume Group

Select the Volume to see the summary

I have assigned two initiators

How to Map Volume in client machine

Open iSCSI Initiator

Enter iSCSI provider IP (Nutanix Server Cluster IP)

Click Quick Connect

Refresh the page

Go to Disk management to see mounted disk

Failed to install roles in Windows Server 2019 with error 0x80073701

ISSUE:

Failed to install IIS roles on one Windows Server 2019 with error 0x80073701.

TROUBLESHOOTING:

We ran the scripts sfc /scannow and DISM.exe /Online /Cleanup-Image /Restorehealth to check the system file integrity, from the output of which we noticed the corruptions related to patch KB5014669 and KB5014022.

2023-05-09 09:26:34, Info CBS =================================

2023-05-09 09:26:34, Info CBS Checking System Update Readiness.

2023-05-09 09:26:34, Info CBS

2023-05-09 09:26:34, Info CBS (p) CBS Catalog Missing (n) Package_5472_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10

2023-05-09 09:26:34, Info CBS Repair failed: Missing replacement mum/cat pair.

2023-05-09 09:26:34, Info CBS (p) CBS Catalog Missing (n) Package_5477_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10

2023-05-09 09:26:34, Info CBS Repair failed: Missing replacement mum/cat pair.

…

2023-05-09 09:26:34, Info CBS (w) CBS Package Index Package Missing 0x80070490 Package_2566_for_KB5014022~31bf3856ad364e35~amd64~~0.0.0.0 Package_2566_for_KB5014022~31bf3856ad364e35~amd64~~10.0.1.14

2023-05-09 09:26:34, Info CBS (w) CBS Package Index Package Missing 0x80070490 Package_2567_for_KB5014022~31bf3856ad364e35~amd64~~0.0.0.0 Package_2567_for_KB5014022~31bf3856ad364e35~amd64~~10.0.1.14

2. As I learned that we have deleted the reg keys for KB5014022 before, we suggested you restore the reg keys or reinstall the package to fix it.

From the CBS log, we noticed that the assembly missing issue is caused by package KB5014669, thus we suggested to remove all the related reg key with script remove-Item -path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\*KB5014669*".

2023-05-09 09:34:05, Error CSI 000068ef (F) STATUS_SXS_ASSEMBLY_MISSING #56773556# from CCSDirectTransaction::OperateEnding at index 0 of 1 operations, disposition 2[gle=0xd015000c]

2023-05-09 09:34:05, Error CSI 000068f0 (F) HRESULT_FROM_WIN32(ERROR_SXS_ASSEMBLY_MISSING) #56773398# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_PinDeployment(Flags = 0, a = be61d6ca2ab4dcc4eede90c05a096ade, version 10.0.17763.1790, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, cb = (null), s = (null), rid = 'Package_5931_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10.5014669-10806_neutral', rah = (null), manpath = (null), catpath = (null), ed = 0, disp = 0)[gle=0x80073701]

2023-05-09 09:34:05, Info CBS Failed to pin deployment while resolving Update: Package_5931_for_KB5014669~31bf3856ad364e35~amd64~~10.0.1.10.5014669-10806_neutral from file: (null) [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

2023-05-09 09:34:05, Info CBS Failed to bulk stage deployment manifest and pin deployment for package:Package_3995_for_KB5023702~31bf3856ad364e35~amd64~~10.0.1.10 [HRESULT = 0x80073701 - ERROR_SXS_ASSEMBLY_MISSING]

RESOLUTION:

1. Restore the reg key related to KB5014022 or re-install the patch KB5014022 to fix the corruption.

2. Remove the package KB5014669 by running remove-Item -path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\*KB5014669*" with powershell as admin.