Čítačka správ

Backing & Restoring NSX-T L2 VPN Autonomous Client Config

VMware Documents - Pi, 04/17/2020 - 08:01

This document talks about backing & restoring NSX-T L2 VPN autonomous client configuration.



We assume you have a working NSX-T L2 VPN Autonomous Client with vlans extended to VMC SDDC.




To backup the configuration, login to VPN client via UI and navigate to backup/restore tab. Click on backup post entering pass phrase. It will take close to a minute and you will prompted to save backup.tar file.





Taking an assumption, the L2 VPN VM has crashed and you do not have Image backup. We need to deploy new L2 VPN and restore the configuration.

We need to make sure the old L2 VM is powered off and the new VM has correct vNic mappings



Login to the L2 VPN client via UI and click on backup/restore tab. Browse the config file, enter the credentials and hit the restore button. It will ~one minute to restore the config.

You should see a similar screenshot like below.



The connectivity should be back to Cloud VM's (on extended networks) from OnPrem.

If the new L2 VPN VM has a different management IP as compared to old L2 VPN VM ; then post reboot new L2 VPN VM will fall back to management IP as old client.

Kategórie: VMware

Traffic steering to paloalto. Do I need DFW at all?

VMware Community - Št, 04/16/2020 - 00:04



Our company has purchased Paloalto VM-Series ELA licenses to be deployed for microsegmentation. So we don't have any restriction on number of VM Firewalls or the size of them.


My boss wants to steer all the traffice to VM series firewalls and not use NSX DFW at all, considering two thing, having one single place to manage the traffic and firewall rules. and second because I am the only one with a little bit knowledge of NSX (VCP-NV) and the rest of the team only know PAN he wants to reduce the cost of education and relying only on one resource.


I know that when you vmotion a vm the current sessions won't be managed with the VMseries on the new host and they will continue to pass traffic until the session is ended, like a big file transfer or replication.


I also know that VRNI which we own as well makes life so easy by detecting traffic flows and suggesting security policies.


Other than the above is there any other reason we shouldn't steer all the traffic to VM series? and leave the NSX DFW to allow everything?



Kategórie: VMware

VMware.Vim Clone_VM 'The operation is not allowed in the current state.'

VMware Community - St, 04/15/2020 - 23:18

My team is developing an application that needs to clone existing templates in our vSphere environment. We're using VMware.Vim in a C# application to do this. We're replacing an already existing implementation that uses PowerShell.

Below is the code that is throwing the error. We are eventually going to load balance based on memory usage, but currently we are selecting the host by random. That's why there is some extra code with collecting all of the hosts and then picking one.

When it gets to CloneVM_Task, an exception with the message 'The operation is not allowed in the current state.' is thrown. The exception doesn't give me much to work with and I can't find any useful logs in vSphere. vSphere just says "An error prevented the virtual machine from being cloned" in the events log. We're using version 6.7. I'm new to VMWare, so any help is appreciated. The documentation, or the organization of the documentation, is lacking, to say the least.

I hope this is the right forum for this question. It's hard to navigate these forums. 

public async void CreateVirtualMachineAsync(NewVMRequest newVMRequest){    var appliance = await _applianceService.GetAppliance(newVMRequest.Appliance);     var vimClient = new VimClientImpl    {        IgnoreServerCertificateErrors = true, ServiceUrl = appliance.ServiceUrl    };    vimClient.Login(appliance.User, appliance.Password);     var datacenter = GetDatacenter(vimClient);     var hostCollection = GetListOfHosts(vimClient, datacenter);     var randomHost = PickRandomHost(hostCollection);     var sourceVm = GetSelectedVm(vimClient, newVMRequest);     if (sourceVm == null)    {        _logger.LogDebug($"Could not find virtual machine {newVMRequest.Source} to use for template");        _logger.LogError($"Could not find virtual machine {newVMRequest.Source} to use for template", null);        return;    }     var selectedStore = ConnectToDataStore(vimClient);     var cluster = GetCluster(vimClient);     var mySpec = CreateCloneSpec(selectedStore, randomHost, cluster, sourceVm);     vimClient.WaitForTask(sourceVm.CloneVM_Task(sourceVm.Parent, newVMRequest.Name, mySpec));     vimClient.Disconnect();}private VirtualMachineCloneSpec CreateCloneSpec(Datastore selectedStore, ManagedObjectReference randomHost, ClusterComputeResource cluster, VirtualMachine sourceVm){    var mySpec =  new VirtualMachineCloneSpec    {        Location = new VirtualMachineRelocateSpec        {            Datastore = selectedStore.MoRef,            Transform = VirtualMachineRelocateTransformation.sparse,            Host = randomHost,            Pool = cluster.ResourcePool        },        Config = new VirtualMachineConfigSpec()    };     var networkDevice = new VirtualDevice();    foreach (var vDevice in sourceVm.Config.Hardware.Device)    {        if (vDevice.DeviceInfo.Label.Contains("Network"))        {            networkDevice = vDevice;        }    }     var devSpec = new VirtualDeviceConfigSpec    {        Device = networkDevice, FileOperation = VirtualDeviceConfigSpecFileOperation.create     };    mySpec.Config.DeviceChange = new[] { devSpec };     return mySpec;}private Datacenter GetDatacenter(VimClient vimClient){    var entities = vimClient.FindEntityViews(typeof(Datacenter), null, null, null);    return (Datacenter)entities.First();}private List<ManagedObjectReference> GetListOfHosts(VimClient vimClient, Datacenter datacenter){    var hostCollection = new List<ManagedObjectReference>();    var hostFolderMoRef = datacenter.HostFolder;    var hostFolder = (Folder)vimClient.GetView(hostFolderMoRef, null);    var childEntityMoRefs = hostFolder.ChildEntity;    foreach (var childEntityMoRef in childEntityMoRefs)    {        var thisCluster = (ClusterComputeResource)vimClient.GetView(childEntityMoRef, null);        var clusterHostMoRefs = thisCluster.Host;        foreach (var clusterHostMoRef in clusterHostMoRefs)        {            var hostSystem = (HostSystem)vimClient.GetView(clusterHostMoRef, null);            hostCollection.Add(hostSystem.MoRef);        }    }     return hostCollection;}private ManagedObjectReference PickRandomHost(List<ManagedObjectReference> hostCollection){    var rand = new Random();    return hostCollection[rand.Next(0, hostCollection.Count)];}private VirtualMachine GetSelectedVm(VimClient vimClient, NewVMRequest newVMRequest){    var filter = new NameValueCollection    {        {"name", newVMRequest.Source},        {"Config.Template", newVMRequest.UseTemplate.ToString().ToLower()}    };    var entityViews = vimClient.FindEntityViews(typeof(VMware.Vim.VirtualMachine), null, filter, null);     if (entityViews.Count == 0)    {        return null;    }    return (VirtualMachine)vimClient.FindEntityViews(typeof(VMware.Vim.VirtualMachine), null, filter, null).First();}private Datastore ConnectToDataStore(VimClient vimClient){       var myDs = vimClient.FindEntityView(typeof(Datastore), null, null /*dsFilter*/, null);    return (Datastore)myDs;}private ClusterComputeResource GetCluster(VimClient vimClient){    var appClusters = vimClient.FindEntityViews(typeof(ClusterComputeResource), null, null, null);    return (ClusterComputeResource)appClusters?.FirstOrDefault();}
Kategórie: VMware

Migrate Skyline from My VMware to VMware Cloud Services

VMware Documents - St, 04/15/2020 - 20:07

A large majority of customer's today access Skyline through VMware Cloud Services. VMware Cloud Services allows customers to have complete control over who can access Skyline Advisor, as well as organize data in a way that makes the most sense for their business, organization, or team. However, some of our earliest of adopters of Skyline did so before Skyline Advisor was available on VMware Cloud Services. These customers access Skyline Advisor through My VMware.


VMware will be disabling access to Skyline Advisor through My VMware in the near future. This article will assist customers who still access Skyline Advisor through My VMware in migrating their Skyline implementation to Cloud Services.


At a high-level, what's involved with migrating from My VMware to VMware Cloud Services?


  • You will create a Cloud Services Organization on VMware Cloud Services.
  • You will associate your support entitlement with this Cloud Services Organization. This is performed automatically, based upon the support entitlement's associated the My VMware account used to create the Cloud Services Organization.
  • You will migrate your Skyline Collectors from My VMware, to this Cloud Services Organization. This again, is performed automatically.
  • Within this Cloud Services Organization, the Skyline Advisor service will be available to you.


Follow these steps to migrate from My VMware to VMware Cloud Services.




1. Open a web-browser, and go to https://skyline.vmware.com/get-started




2. Click on the Get Started button.


3. Log in to Cloud Services using your existing My VMware email address & password combination.


There are a couple of points regarding the My VMware account used to create your Cloud Services Organization. Use an account that has an active VMware support entitlement assigned to it. Skyline requires an active Production, or Premier Support contract. On that point, for customer's who have purchased Premier Support, be sure to use a My VMware account that is associated with your Premier Support contract.


Additionally, Skyline Advisor will display Support Requests opened under all EAs associated with the Cloud Services Organization. Therefore, use a My VMware account that is associated with all necessary EAs, for which a Support Request could be opened under.


See VMware KB 2011009 for more details regarding My VMware account information.


4. Click Create Your First Organization to create a Cloud Services Organization. If you are a member of an existing Cloud Services Organization, you can choose to migrate Skyline to an existing Cloud Services Organization. If this option is available to you, choose the Organization Name that you want to migrate Skyline to.



5. Enter the following details for your Cloud Services Organization:


Organization Name - Name your Organization something meaningful to both you, and VMware. This Organization name will be utilized by both you, as well as VMware, when assisting you with both proactive and reactive support.


The Address of your Organization.


During this step, your country currency, and possibly a Tax ID, will be displayed. I want to reiterate that there is no additional charge for Skyline, and the displaying of the country currency and Taxi ID is a construct of VMware Cloud Services. You can ignore both of these for the purposes of Skyline.



6. Within the Skyline Organization wizard, for Step 1 - Associate Support Entitlement; click Associate Support Entitlement. This will associate the highest tier of support entitlement for the logged-in My VMware user with your Cloud Services Organization. Click Proceed to Next Step.



7. You can skip Steps 2, 3, and 4, unless you need to deploy a new Skyline Collector.


8. For Step 5 - Manage existing Collectors; your already deployed Skyline Collectors should appear, with the Action to MIGRATE available to you. Click MIGRATE to migrate your Skyline Collectors from My VMware to your Cloud Services Organization. If your Skyline Collectors do not appear within Step 5 - Migrate existing Collectors, please start a discussion within the Skyline Community, and a Skyline team member will assist you with migrating your Collectors to Cloud Services.



9. At this point, as long as everything went as expected, the migration is complete, and you can begin accessing Skyline Advisor through Cloud Services, or directly by going to https://skyline.vmware.com/advisor.

Post-Migration Recommendations

Add additional individuals to your Cloud Services Organization, and to Skyline Advisor. This will allow additional individuals to view findings and recommendations, and use Log Assist for both transferring, and approving the transfer of support bundles to VMware GSS.


See the following resources for assistance with adding users to Cloud Services.

Kategórie: VMware

Upgrade failed: SQL Server Agent Jobs errors

VMware Documents - Ut, 04/14/2020 - 16:29

Upgrade failed: SQL Server Agent Jobs


If you are upgrading your Workspace ONE UEM and then installer fails with the below errors, it might be caused by the SQL Server Agent jobs.


In the installer logs you might see an error as shown below: "an error occurred while the batch was being executed":






To solve the problem, check the properties of all SQL Server Agent jobs, and make sure that the job owner is assigned to the SQL user that runs the installer.



Restore your DB from the Backup and re-run the installer.

Kategórie: VMware

CPU over commitment Report

VMware Community - Ut, 04/14/2020 - 07:02

Hi All,


I'm looking to convert the CPU over commitment report into CSV instead of table view format. Also, is it possible to get Memory over commitment as well ?



# Connect to vCenter using passthrough credentials

connect-viserver "vc.com";


# Get a list of hosts in a specific cluster (omit the get-cluster to get all hosts, and just use get-vmhost)

$hosts = get-cluster "MYCLUSTER" | get-vmhost;


# Define an empty table

$table = @();


# Loop through each host found

foreach ($vmhost in $hosts) {


    # Create an empty row

    $row = "" | select Hostname, LogicalCPUs, CPUsAssigned, Overcommited;


    # Get the number of vCPUs assigned

    $cpumeasure = $vmhost | get-vm | where {$_.powerstate -eq "poweredon"} | measure-object numcpu -sum;


    # Add the hostname to the row

    $row.Hostname = (($vmhost.name).split("."))[0];


    # Add the number of logical CPUs to the row

    $row.logicalcpus = $vmhost.numcpu * 2;


    # Add the number of allocated vCPUs to the row

    $row.cpusassigned = [int]$cpumeasure.sum;


    # Get the overcommitment level as a percentage

    $perc = [int](($cpumeasure.sum / $row.logicalcpus)*100);


    # Warn if overcommitted

    if ($perc -gt 100) {

        $row.Overcommited = "YES - " + $perc + "%";


    else {

        $row.Overcommited = "No";



# Add the current row to the table

$table = $table + $row;




# Display the table

$table | out-gridview;






Kategórie: VMware

Chrome OS Troubleshooting Guide

VMware Documents - Ut, 04/14/2020 - 03:18
Kategórie: VMware

Generating Support bundle for NSX-T L2 VPN Autonomous Client via command line

VMware Documents - Ut, 04/14/2020 - 02:27

This document talks about generating support bundle for NSX-T L2 VPN autonomous client via command line.



SSH to L2 appliance as root and switch over to admin



To generate log bundle run below command



To view the log bundle file, exit from admin prompt and navigate to below directory. You should see the log bundle. You can now connect to L2 VPN appliance via WINSCP and copy the file.

Kategórie: VMware

vra 8 - Default email notifications via email server

VMware Community - Pi, 04/10/2020 - 10:49

Do you have any information on default Email notification scenarios for vRA 8. Does it have all default email notifications as version 7 did, especially, request submitted/completed and machine is ready notifications.


Kategórie: VMware

Troubleshoot ESXI network with Shell

VMware Documents - St, 04/08/2020 - 05:54

Hi everyone


At this little article writes about what can do Virtualization(VMware) Admins when they docent have access to GUI configuration or in the worse situations, when ESXI Network can't work properly, for example you have one NIC for Management a ESXI Server and cause any unexpected failure, NIC can't up and VSPhere web client is unreachable, and when VCenter want to control and solve this problem, Operation see an BIG-Error about Management connection to the ESXI Server xxxx lost. Maybe first think any sysadmin can do it is change the Physical NIC assigned to Management PortGroup and everything can work properly again like before fault, but when ESXI joined to a VCenter and All of other physical ports assigned to VDS Switches as a UP-Link we can't get them back in the console and assign them to the any other switch or any management change to them. In fact it is a one of situation can be occurring and sysadmins need to configure ESXI network from shell, command-line, console.


If anyone have this situation and he/she don't know how to manage ESXI network via console, then he/she must reinstall ESXI, restore backup and so many other solution they need to restart host or change OS reconfigure it and in the end we have so many wast time.


In this little Article we try to show you how to configure ESXI Networking VSwitch via console and how to use [ esxcfg-vswitch ] command.

First, for you get access to your ESXI-Shell press ALT+F1 to prompt user and password, input a user like root user and confirm to access shell.

In the next step we need to see how is the Networking map, use the [esxcfg-vswitch -l] to view V-Switches configuration and diagram in the text mode, in my lab I have one ESXI and two UP-Link or physical link and I have this output:

Switch Name: vSwitch0(Default name of ESXI first standard vSwitch ) , in this situation we haven't VCenter and we don't see any other switches like Distributed Switches or any other standard vSwitch, if we created standard switch in the ESXI Networking, there name was here.


Ok, and the next field is 'Num Ports' its default switch port number its 2560, in the maximum standard switches port number in a host is 4096 and 1016 Active port.

used port from 128 port is 6. And some other info like MTU and Important section for this troubleshooting is Uplink section and we have two NIC "vmnic0 , vmnic1 ".ESXI Management network need one of this physical port to work properly.



In the next step we need to delete vmnic0 from vSwitch0:

esxcfg-vswitch -U vmnic0 vSwitch0


Now ESXI have only one vmnic1 as a Active Up-Link.



create another vSwitch , of course if you have Management network in the another Vswitch and it is a Standard vSwitch, you don't need create another vSwitch and scape this step :

esxcfg-vswith -a [VSwitchName]

(for example in this lab environment I create a vSwitch mng_svsw)

esxcfg-vswitch -l:

in the next step to access Management network or ping successfully Management IP address, we need to link vmnic0 to Which switch name that exist for management purpose:

esxcfg-vswitch -L vmnic0 mng_svsw

at the last step we assign vmnic0 to Switch mng_svsw as a Up-Link.

The Uplink added successfully, just if you have vLan configuration on your switches you can set vLan on the new switch and PortGroup:

esxcfg-vswitch [switchName] -v [VLan Number] -p [PortGroupName]Example:esxcfg-vswitch mng_svsw -v 200 -p Management


VLAN ID is 0.



After VLAN Assignment:




VLAN ID is 200 and if your physical port on the ethernet switch is in the VLAN 200, now you must can Ping or can connect to it.




Set esxcfg-vswitch [Switchname] -m [MTU] #set MTU for Switch for example enable Jumbo Frame and set 9000 Byte.

esxcfg-vswitch have some other parameter can be useful to have better troubleshoot, like:

esxcfg-vswitch -c [SwitchName] #Check switch sexist or not

esxcfg-vswitch -C [PortGroupName] #Check PortGroup exist or not

Kategórie: VMware

.vmdk file cannot be opened

VMware Documents - Ut, 04/07/2020 - 12:24



I have moved from Virtualbox to VMware. My problem right now is that I don't want to create a new VM but instead move the system from VB to VMware. The system is saved as a .vmdk file. Thing is that I can add a new hard disk but apparently not a .vmdk file. I got 2 of them: "name of Virtualbox system".vmdk and "name of Virtualbox system"-flat.vmdk. It accepts the normal .vmdk file but unfortunately not the -flat.vmdk. The "flat" file is needed because that is the real VM file (since it's 100GB and that's the actual size of my system)


I do hope that someone can help me out. Thanks in advance!

Kategórie: VMware

DNS resolution error during SRM site pairing

VMware Documents - Ut, 04/07/2020 - 07:13

During SRM Site pairing from OnPrem to VMC SDDC, below error might be seen


This document assumes that you have fresh deployment of OnPrem SRM and it has not been configured/paired with any site. If you have an existing configured/paired production/development/test OnPrem SRM instance, please contact support and do not proceed.

In the above screenshot you should have registered OnPrem vSphere Replication appliance as well however this document focuses on SRM DNS error.


Cloud SRM reaches out to OnPrem PSC and checks for OnPrem SRM url, to setup site pairing with.

If the OnPrem SRM is registered with hostname and not FQDN, above error might come up.


High level steps that we need to follow

  • Verify OnPrem SRM is registered with OnPrem PSC via hostname.
  • Unregister OnPrem SRM with OnPrem PSC
  • Change the OnPrem hostname to fqdn
  • Generate new self signed cert for OnPrem SRM
  • Register OnPrem SRM with OnPrem PSC via FQDN
  • Complete SRM site pairing operation





To verify if the OnPrem SRM is registered with hostname and not with FQDN ; navigate to OnPrem PSC by editing below url


Change the value field as below and click on Invoke method

Try to search via OnPrem SRM hostname, FQDN registration is not seen.







Now we need to unregister OnPrem SRM from PSC. Login to SRM VAMI page >> summary tab and click on unregister

Check all the options and click on unregister

When it completes, you should see similar screen







We now need to change OnPrem SRM hostname to FQDN. Navigate to networking tab on SRM VAMI portal and click edit >> enter FQDN and hit save.

You should see new hostname on portal.







To generate new self signed OnPrem SRM cert, navigate to access tab on SRM VAMI portal and click on cert change.

Make sure SRM FQDN is seen with FQDN and right IP. Enter the organization details and click on change

Post changing the default cert, we need to refresh the browser and accept new cert. On the browser we should now see cert with FQDN.






Let's proceed registering OnPrem SRM with PSC. Click on the summary tab on SRM VAMI portal and click on configure appliance.

Enter OnPrem PSC details and hit next. Enter the details for name/extension ; make sure that hostname comes as FQDN and finish the wizard

We can verify now if the SRM registration on PSC comes up with FQDN


SRM site pairing now should not return initial error message and would go through.

Kategórie: VMware

6 Reasons Why Customers Choose Horizon 7 on VMware Cloud on AWS

VMware Documents - Po, 04/06/2020 - 08:59

New Blog Published.


Many a times this questions is being asked by clients. Please refer to below blog for your perusal

6 Reasons Why Customers Choose Horizon 7 on VMware Cloud on AWS

Kategórie: VMware

Key Resources for Installing the Horizon Client

VMware Documents - Pi, 03/27/2020 - 15:04

Below are some important links for admins and end-users on installing the Horizon Client on various devices.


For Admins



For End-Users

Download the VMware Horizon Clients for Windows, Mac, iOS, Linux, Chrome and Android

Instructions for Installing the Horizon Client on Windows

Instructions for Installing the Horizon Client on Mac


After installing Horizon Client on your device and launching it, you will need to provide organization-specific information in order to connect to a remote desktop or application. This information (name of server and your organization credentials) can only be provided by your organization.

Kategórie: VMware

26 March 2020 release notes: What's New in VMware Learning Platform

VMware Documents - Pi, 03/27/2020 - 10:00
  • PDF Lab Manuals
    VMware Learning Platform now supports the PDF document format for student lab manuals. This feature enables content creators to use external authoring tools to develop lab manuals for use in VMware Learning Platform. In addition, it provides customers who have preexisting content an additional import option. Go to Lab Management > Lab Resources > Create Lab Resource.


  • Detailed Billing
    The new billing dashboard provides granular usage metering of on-demand service usage. This dashboard enables Tenant Administrators to optimize usage of the service to help control cost. The new billing dashboard is available in the Tenant Management module > Billing.


  • Lab Replication
    With replicas, a Tenant Administrator can easily and reliably replicate vApp Lab Templates within the same region or to other geographical regions throughout the cloud. This feature helps enable several key use cases including distributing templates for high availability, remote backups, and improving performance for students by providing labs in-region.


  • Create User during Entitlement Creation
    This functionality introduces the ability to create a user during the entitlement creation process, without the need for the user to register for or create an account in VMware Learning Platform. This feature can be useful in one-time lab use situations, or to provide a quick hands-on demo without having the user go through the standard registration process.


  • Class Self-Registration
    Instructors now have the capability to enable a class for student self-registration. This feature is advantageous in scenarios where an instructor may not have the student roster well in advance of a scheduled class. During class creation the instructor simply configures the number of seats the class is intended to support, and then provides their students with a self-registration URL. No account creation is required beforehand.

Remember to keep a lookout for the new Admin User Interface if you aren’t already using it, as the old UI will be deprecated within the next few weeks!

Reference link: What's New in VMware Learning Platform

Kategórie: VMware

kubuntu vm: no network after resume

VMware Community - So, 03/21/2020 - 12:02

vmware fusion 11.5.2, macOS 10.15.3, vm: kubuntu 19.10


Network is working fine in vm after booting. Problem is, whenever pausing and resuming I end up with a non working network. Can get back to working state by restarting the vm, but that's somewhat annoying. Any ideas how to fix this?


Screenshots show network working state and non-working state.

Kategórie: VMware


VMware Documents - Št, 03/19/2020 - 13:01
Kategórie: VMware

SourceHandle of NetBufferList is set to NULL by vmxnet3.sys, which causes abnormal behavior..

VMware Documents - Po, 03/16/2020 - 04:40

Please understand that my English is not good before starting...


I installed Windows 2019 server on VMWare Workstation.

And I found that there is an critical issue(maybe..?) where the network function is malfunctioning.


The cause is VMWare's vmxnet3.sys driver.



Look at the picture below..


The current state of the WFP layer is FWPM_LAYER_INBOUND_MAC_FRAME_ETHERNET.

The SourceHandle in NBL is NULL.


That is, the NIC information of the packet received from vmxnet3.sys cannot be obtained.


So I am requesting a review of the fix for this bug.



Kategórie: VMware

pdf manual support with VLP

VMware Documents - Pi, 03/13/2020 - 11:43

We are happy to introduce pdf manual support with VMware learning Platform. A manual in VLP can be created using screen-steps, Microsoft word import and a raw pdf.


Steps to enable pdf manual:

  1. Upload a pdf to lab resources in tenant admin
  2. Select the pdf resource in the lab (Make sure there is no manual attached to lab)
  3. Start the lab and the pdf will be rendered within the manual itself.


Kategórie: VMware
Syndikovať obsah