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 πŸ™‚

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 πŸ™‚

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 πŸ™‚

How Upgrade from VCSA 6.7 to 7.0

Hi, Today i decided upgrade my VCSA 6.7 to 7.0. First, I need to verify that my VCSA version in my environment that it supports upgrading to 7.0 or not.

For this purpose, I check it from Β Product Interoperability Matrix that can help me to find out a lot of information.

Then I downloaded VCSA 7.0 iso and run the installer.

I choose Upgarde.

1- Genral information.

Upgrading the appliance 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.

2- License agreement, Click on check box. Next

3- Enter source vCenter Serever IP and HTTPS port that you want upgrade and press the Connect to Source Button

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

4- This is where you will select the VCSA deployment target. You can choose a vCenter different from the one you are upgrading, or you can choose an ESXi host that is managed by the VCSA you are upgrading.  Once selected, click  NEXT

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

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

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

8- Configure your temprory network settings, NEXT

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

10-  Stage 1 of the deployment process is complete. Continue

1- The second stage completers the upgrade process by copying data from the source appliance to the deployed vCenter Server. NEXT

2- After the Pre-upgrade check is finished you will see warnings that you should look in to before you proceed.

3- Once you have fixed all the issues from the pre check or you accept the warnings shown you will need to select which data you want to migrate to the new VCSA. This is something that you have to make a decision on because it is based on what historical data you might want to keep.

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- Verify the settings then check the box if you have backed up your VCSA, NEXT

6- Don’t be alarmed! This is just a warning letting you know once the upgrade is complete the original VCSA will be shut down and the newly deployed VCSA will take over the network configuration.

7- This process took about 45 minutes for me.

8- The upgrade is now complete πŸ™‚

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

Finish πŸ™‚