How to remove the unused extension from vCenter 7

Hi, Today I will show you how we can remove the unused extension from VMware vCenter.

First of all, Where is the extenstion?

Please go to this address:

https://vCenter IP address → Administration → Solution → Client Plugins

I want delete this plugin from my vCenter.

1- go to the below address

https://vCenter IP address/mob

2- Enter your vCenter username and password

3- In the Properties Section, Click on Content

4- On the next page, click on ExtensionManager

5- Find your extension name. For example, I searched for the HPE plugin

Copy the extension name

6- Go to the Methods section under the page and find and click on UnregisterExtension

7- Paste or write your extension that you want to delete here and click on Invoke Method.

Finish 🙂

How we can change vCenter’s (VCSA) name or IP address

Hi, Today I plan to change vCenter7’s hostname, domain name and IP address.

Note:

Please take a backup from your vCenter and unregistered your plugins (such as monitoring, backup) from vCenter server.

Make sure that the new FQDN/Hostname is resolvable to the IP address (DNS A records). Make sure that the resolution works in both directions.

First, Connect to vCenter VAMI interface, The address is :

https://your_vCenter_ip_address or FQDN :5480/

Then go to Networking> end click Edit

In this wizard will select a network adapter that you would like to edit.

On the next screen, we can change the hostname, IP address and a DNS setting.

On this screen, we just need to fill in our Single Sign-On (SSO) credentials.

On this screen, select the checkbox, if you have made a backup of your vCenter Server and unregistered extensions.

Network update in progress

Process Completed.

Finish 🙂

How to set a proxy for ESXi 6.7?

Hi, If you set a proxy for your vCenter version 6.7.0.46000 , and it is not working, this post is fit for you.

Today I configured a proxy from UI for vCenter version 6.7.0.46000, but it is not working.

1- login to VAMI.

Https://vcenter-ip-address:5480

Login as a root user.

2- Networking –> Proxy Settings

{This configured not working}.

What is a solution?

It has a trick.

3- Login to VAMI with SSH client like putty.

4- vi this file

/etc/wgetrc

5- Put your proxy address in this file

# You can set the default proxies for Wget to use for http, https, and ftp.
# They will override the value in the environment.
https_proxy = https://proxy_address:port/
http_proxy = http://proxy_address:port/

Finish 🙂

ESXi 7 System Storage Changes

Overview

We’ve reviewed and changed the lay-out for ESXi system storage partitions on its boot device. This is done to be more flexible, and to support other VMware, and 3rd party solutions. Prior to vSphere 7, the ESXi system storage lay-out had several limitations. The partition sizes were fixed and the partition numbers were static, limiting partition management. This effectively restricts the support for large modules, debugging functionality and possible third-party components.

That is why we changed the ESXi system storage partition layout. We have increased the boot bank sizes, and consolidated the system partitions and made them expandable. This article details these changes introduced with vSphere 7 and how that reflects on the boot media requirements to run vSphere 7.

The partition sizes in vSphere 6.x are fixed, with an exception for the scratch partition and the optional VMFS datastore. These are created depending on the used boot media and its capacity.

Consolidated Partition Layout in vSphere 7

To overcome the challenges presented by using this configuration, the boot partitions in vSphere 7 are consolidated.

The ESXi 7 System Storage lay-out only consists of four partitions.

  • System boot
    • Stores boot loader and EFI modules.
    • Type: FAT16
  • Boot-banks (x2)
    • System space to store ESXi boot modules
    • Type: FAT16
  • ESX-OSData
    • Acts as the unified location to store extra (nonboot) modules, system configuration and state, and system virtual machines
    • Type: VMFS-L
    • Should be created on high-endurance storage devices

The OSData partition is divided into two high-level categories of data called ROM-data and RAM-data. Frequently written data, for example, logs, VMFS global traces, vSAN EPD and traces, and live databases are referred to as RAM-data. ROM-data is data written infrequently, for example, VMtools ISOs, configurations, and core dumps.

ESXi 7 System Storage Sizes

Depending the boot media used and if its a fresh installation or upgrade, the capacity used for each partition varies. The only constant here is the system boot partition. If the boot media is larger than 128GB, a VMFS datastore is created automatically to use for storing virtual machine data.

For storage media such as USB or SD devices, the ESX-OSData partition is created on a high-endurance storage device such as an HDD or SSD. When a secondary high-endurance storage device is not available, VMFS-L Locker partition is created on USB or SD devices, but this partition is used only to store ROM-data. RAM-data is stored on a RAM disk.

ESXi 7 System Storage Contents

The sub-systems that require access to the ESXi partitions, access these partitions using the symbolic links. For example: /bootbank and /altbootbank symbolic links are used for accessing the active bootbank and alternative bootbank. The /var/core symbolic link is used to access the core-dumps.

Review the System Storage Lay-out

When examining the partition details in the vSphere Client, you’ll notice the partition lay-out as described in the previous chapters. Use this information to review your boot media capacity and the automatic sizing as configured by the ESXi installer.

A similar view can be found in the CLI of an ESXi host. You’ll notice the partitions being labeled as BOOTBANK1/2 and OSDATA.

You might notice the OSDATA partition being formatted as the Virtual Flash File System (VFFS). When the OSDATA partition is placed on a SDD or NVMe device, VMFS-L is labeled as VFSS.

Boot Media

vSphere supports a wide variety of boot media with a strong recommendation to use high-endurance storage media devices like HDD, SSD and NVMe, or boot from a SAN LUN. To install ESXi 7, these are the recommendations for choosing boot media:

  • 32GB for other boot devices like hard disks, or flash media like SSD or NVMe devices.
  • A boot device must not be shared between ESXi hosts.

Upgrading to from ESXi 6.x to ESXi 7.0 requires a boot device that is a minimum of 4 GB. Review the full vSphere ESXi hardware requirements here. As always, the VMware Compatibility Guide is the source of truth for supported hardware devices.

Legacy SD and USB devices are supported with some limitations listed below, more information in this FAQ.

  • To chose a proper SD or USB boot device, see Knowledge Base article 82515.You must provide an additional VMFS volume of at least 32 GB to store the ESX-OSData volume and required VMFS datastore. If the boot device is larger than 138 GB, the ESXi installer creates a VMFS volume automatically. Delete the VMFS datastore on USB and SD devices immediately after installation to prevent data corruption. For more information how to configure a persistent scratch partition, see Knowledge Base article 1033696.
  • If the VMware Tools partition is stored locally, you must redirect it to the RAM disk. For more information, see Knowledge Base article 83376.
  • You must use an SD flash device that is approved by the server vendor for the particular server model on which you want to install ESXi on an SD flash storage device.

Main Resource

https://core.vmware.com/resource/esxi-system-storage-changes

Import or Clone a Virtual Machine with Advanced Cross vCenter vMotion

Today, my boss told me we need to move 2 virtual machines from vCenter 6.7 to vCenter 7. And we need to move 1 virtual machine from vCenter 7 to vCenter 6.7. VMware has a solution for these scenarios.

Now, for vSphere 7.0 Update 3, the feature is further enhanced to support bulk clone operation! In addition, there are some quality improvements such as a new enhanced vCenter Server connection form and a new icon.

Prerequisites

  1. Obtain the credentials for the administrator account of the vCenter Server instance from which you want to import or clone virtual machines.
  2. Verify that the source vCenter Server instances are version 6.5 or later.
  3. Verify that the target vCenter Server instance is version 7.0 Update 1c or later if you want to import virtual machines to another vCenter Server instance.
  4. Verify that the target vCenter Server instance is version 7.0 Update 3 if you want to clone virtual machines to another vCenter Server instance.

Scenario1:

Import Workflow:

In order to clone several virtual workloads from another vCenter Server to the current one, right-click on the destination host/cluster and select the “Import VMs” action.

After that, enter the credentials of the source vCenter Server in the import connection form.

On the next screen, select the workloads that should be cloned.

When you complete the wizard, the workloads will be cloned to the destination vCenter Server.

Scenario2:

Export Workflow:

Select the virtual workloads that should be cloned to a foreign vCenter Server and click on “Migrate…”

On the next screen, make sure to select “Cross vCenter Server export” option.

Then, select the destination vCenter Server and, when you complete the wizard, all workloads will be cloned there.

With the enhancements to the XVM in vSphere 7.0 Update 3, users are able to perform a bulk workload clone operation between different vCenter Servers. This makes the feature more versatile and suits a variety of use cases, some of which are:

  1. Migrating/cloning VMs from an on-premise to a cloud (VMware Cloud) environment
  2. Quicker adoption of the new vSphere versions by migrating/cloning the workloads from the old vCenter Server

For a more detailed information of the usage and requirements, please see the official documentation.

Finish 🙂

Step by Step Enable vSAN 7.0 FileService

Hi, Today i decided enable vSAN 7.0 File Service.

vSAN file service allows a vSphere admin to provision a file share from their vSAN cluster. The file share can be accessed using NFS or SMB.

1- Click on your Cluster –> Configure TAB  –>  vSAN –> Services –> File service –> Enable

2- Checklist

The following information is needed to configure file service.

  • Static IP address, subnet masks and gateway for file servers
  • DNS name for each IP address or allow the system to do a reverse DNS lookup.

For SMB share and NFS share with Kerberos Security, the following information is needed.

  • AD domain, organizational unit (optional), and a user account with sufficient delegated permissions.

I configure DNS name for each IP address

3- You can download manually or automatically File service agent, i downlload it and Manually import it. Click Browse

Select your files and Next.

4- Enter your Domain informations.

5- Enter your Networking information.

It is important configure Security setting before add it to File Service.

Go to Ntework Tab –> Select your port group or create new port group –> Advanced –> Custumize default polices configuration

Promiscuous mode and Forged transmits –> Accept

6- Choose your distributed port group name and location

7- Enter your ips and DNS names

8- Click on Finish button

Finish 🙂

vSphere Cluster Services (vCLS) enhancements

Hi, Today i want to write about new feature of vCenter 7 Update 3, With vSphere 7.0 Update 3, vSphere admins can configure vCLS virtual machines to run on specific datastores by configuring the vCLS VMs datastore preference per cluster. Admins can also define compute policies to specify how the vSphere Distributed Resource Scheduler (DRS) should place vCLS agent virtual machines (vCLS VMs) and other groups of workload VMs. 

First of all, What is vSphere Cluster Services (vCLS) ?

vSphere Cluster Services (vCLS) is a new feature in vSphere 7.0 Update 1. This feature ensures cluster services such as vSphere DRS and vSphere HA are all available to maintain the resources and health of the workloads running in the clusters independent of the vCenter Server instance availability.

In vSphere 7.0 Update 1, VMware has released a platform/framework to facilitate them to run independently of the vCenter Server instance availability. In this release, vCenter Server is still required for running cluster services such as vSphere DRS, vSphere HA etc.

vCLS is a mandatory feature that is deployed on each vSphere cluster when vCenter Server is upgraded to Update 1 or when a fresh deployment of vSphere 7.0 Update 1. ESXi host can be of any older version that is compatible with vCenter server 7.0 Update 1.

Size of the vCLS VMs

vSphere Cluster Service VMs are very small VMs compared to workload VMs. Each consumes 1 vCPU and 128 MB of memory and about 500 MB of storage. Below table shows the specification of these VMs:
 

Memory 128 MB
Memory Reservation 100 MB
Swap Size 256 MB
CPU 1
CPU Reservation 100 MHz
Hard Disk 2 GB
Ethernet Adapter 0 (It is a No NIC VM)
VMDK Size -245 MB
Storage Space -480 MB

How can configure this new feature of vCenter:

Login to your vCenter Server.

Click on your Cluster name and select Configure tab and select vSphere Cluster Services –> Datastores

Click ADD

Select one or more DataStores in which you want vCLS VMs to be created.

Refrences:

https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-703-release-notes.html

https://kb.vmware.com/s/article/80472

Finish 🙂

How to assign license to the vCenter 7.0 Update3

Hi, After install vCenter 7.0 Update 3 in my last post, You need to assign license to your vCenter.

For this purpose, You need to buy a license from VMware company. 

Login to your vCenter Server, You see a warning on your screen. Click on Manage Your Licenses button.

Your vCenter license is on Evaluation License. CLick ADD

Enter your License Key

Enter your License Name, NEXT

Your License import in to the vCenter repositry, Now you need assign your License to an asset. Click on Assets tab and choose VCENTER SERVER SYSTEMS

Select your vCenter License and click OK.

Now, Refresh your page, The alert message disappears .

Finish 🙂

Step by Step install vCenter 7.0 update3

Hi, Today i want install vCenter 7.0 Update3.

You can find system prerequisites from this page .

I downloaded VCSA 7.0 iso from VMware.com and run the installer.

I choose Install.

1-Introduction

Note: The external Paltform Services Controller deployment has been deprecated.

Note: Installing the vCenter Server is a two stage process. The first stage involves deploying a new vCenter Server to the target ESXi host or a compute resource in the target vCenter Server. The second stage completes the setup of the deployed vCenter Server. Next

2- License agreement, Click on check box. Next

3- Specify the vCenter Server deployment target settings. The target is the ESXi host or vCenter Server will be deployed.

On this page, fill in all the blank fields, Next

Accept certificate warning and click  NEXT

4- Enter the new VM name for your VCSA 7.0 Update 3 and set the root password for it, NEXT

5- Select your deployment size, I choose Large. NEXT

6- Select datastore, you can select Thin or Thick disk mode, NEXT

7- Configure your temprory network settings, NEXT

10- The installer will begin deploying the new VCSA according to the settings you provided. Finish

1- The second stage process. NEXT

2- Set your Time and NTP servers and you can Enbaled or Disabled SSH access to vCenter Server.

3- You have two option2: 1-Create a new SS domain or 2-Join an existing SSO domain

4- You can now  join VMware Customer Experience Improvement Program. This basically allows VMware to collect certain sanitized data from your environment, which could help with future releases.

5-Install – Stage 2

6- This process took about 45 minutes for me.

9- Login to the VCSA by the FQDN or IP address and proceed.

Finish 🙂

Installing Management Pack from Operations Manager

Hi, Today i decided to monitor my EMC Unity with vRops. I need to install Dell EMC ESA for vROps.

Dell EMC Enterprise Storage Analytics provides preconfigured, customizable dashboards so users can optimally manage their storage environment:

1. Topology

2. Metrics

3. Overview

4. Create-Your-Own-Dashboard

You can find and download it from VMware Marketplace .

I downloaded this file.

dellemcenterprisestorageanalytics_6-1626968738565.pak

1- Login to your vRops, then go to Administarion –> Solutions –> Repository, Press the ADD button

2- Click on Browse

3- Select pakcage file that you downloaded it before.

4- Select Check box and press on UPDOAD button

5- Next

6- Select check box License Agreement and NEXT

7- Install Successful

8- You can see it in your Repositry, you must enter your storage username and password.

9- Enter a name for your account name, Your storage IP address and credential, Select your storage models from Connection Type, I select my Unity storage

10- You can add/delete more storage account in Other Accounts section

11- You can see your install result in Dashboard –> Dell EMC

Finish 🙂