It has been our practice to set DHCP reservations rather than setting static IP's on the NICs assigned to the management network.  But that will change after today's issues.  I have two physical NICs assigned to the vSwitch that contains the Management vKernel adapters.  vmnic2 and vmnic4 are those adapters.  The MAC address for vmnic2 is what we used to set the DHCP reservation.  At 11:13am this morning, vmnic4 decided it wanted to grab the IP address, but since no reservation was made for that NIC, it grabbed a random IP address.

How does ESXi6 determine which NIC is to request an IP address, and why would it just randomly change?

I've asked VMware support on using reservations, and they said it was fine.  But regardless, each host will be configured for static in the near future.

Thanks!

Marty Bouillon

All seems to work fine so far.

How do I change the default gateway on a VMkernel network adapter?

I created a VMkernel network adapter using this code:

New-VMHostNetworkAdapter -VMHost $vmHost -PortGroup "vMotion" -VirtualSwitch $virtualSwitch -IP 10.202.5.101 -SubnetMask 255.255.255.0 -VMotionEnabled:$true -Mtu 9000

It was created with the wrong default gateway of 10.202.1.1 rather than the correct default gateway of 10.202.5.1.

How do I set the default gateway to 10.202.5.1?

I can make the changes in the GUI:

But I cannot figure out how to make the change in PowerShell 6, PowerCLI 10.

Any help would be greatly appreciated.

Thanks!

-Chris

Hi everyone,

Presented with a new server running esxi5.0 and I'm unable to execute any updates successfully. What has worked for me time n time again with other systems is failing and this time I'm not sure as to the actual issue or how to resolve it.

Command I'm executing (in maintenance mode) :

-

esxcli software profile update -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-5.5.0-20150204001-standard

It errors with the following :

[VibFormatError]

VIB 'esx-base-6.7.0-0.14.8941472' has invalid payload:

Please refer to the log file for more details.

It seems to run fine, until its depotcollection. Here is the last section of the log,

2018-06-29T11:31:43Z esxupdate: DepotCollection: DEBUG: Downloading metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-5.0.0-metadata.zip

2018-06-29T11:31:43Z esxupdate: downloader: DEBUG: Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-5.0.0-metadata.zip to /tmp/tmpVG5B4S...

2018-06-29T11:31:45Z esxupdate: DepotCollection: DEBUG: Downloading metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-5.1.0-metadata.zip

2018-06-29T11:31:45Z esxupdate: downloader: DEBUG: Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-5.1.0-metadata.zip to /tmp/tmp8vKNHl...

2018-06-29T11:31:46Z esxupdate: DepotCollection: DEBUG: Downloading metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-5.5.0-metadata.zip

2018-06-29T11:31:46Z esxupdate: downloader: DEBUG: Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-5.5.0-metadata.zip to /tmp/tmpg0SWDW...

2018-06-29T11:31:47Z esxupdate: DepotCollection: DEBUG: Downloading metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.0.0-metadata.zip

2018-06-29T11:31:47Z esxupdate: downloader: DEBUG: Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.0.0-metadata.zip to /tmp/tmpK_UBcw...

2018-06-29T11:31:49Z esxupdate: DepotCollection: DEBUG: Downloading metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.5.0-metadata.zip

2018-06-29T11:31:49Z esxupdate: downloader: DEBUG: Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.5.0-metadata.zip to /tmp/tmp_ABXkK...

2018-06-29T11:31:50Z esxupdate: DepotCollection: DEBUG: Downloading metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.7.0-metadata.zip

2018-06-29T11:31:50Z esxupdate: downloader: DEBUG: Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.7.0-metadata.zip to /tmp/tmpTTKJQ2...

2018-06-29T11:31:51Z esxupdate: DepotCollection: INFO: Error parsing metadata.zip from https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/esx/vmw/vmw-ESXi-6.7.0-metadata.zip: (None, "VIB 'esx-base-6.7.0-0.14.8941472' has invalid payload: ")

2018-06-29T11:31:51Z esxupdate: root: ERROR: Traceback (most recent call last):

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 435, in <module>

2018-06-29T11:31:51Z esxupdate: root: ERROR:     main()

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 428, in main

2018-06-29T11:31:51Z esxupdate: root: ERROR:     ret = CMDTABLE[command](options)

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/usr/lib/vmware/esxcli-software", line 198, in ProfileUpdateCmd

2018-06-29T11:31:51Z esxupdate: root: ERROR:     allowDowngrades=opts.downgrade)

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/Transaction.py", line 574, in InstallVibsFromProfile

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/Transaction.py", line 460, in GetProfileFromSources

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/Transaction.py", line 105, in ParseDepots

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/DepotCollection.py", line 227, in ConnectDepots

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/DepotCollection.py", line 414, in ParseMetadata

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/Metadata.py", line 82, in ReadMetadataZip

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/VibCollection.py", line 120, in AddVibFromXml

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/Vib.py", line 792, in FromXml

2018-06-29T11:31:51Z esxupdate: root: ERROR:   File "/build/mts/release/bora-469512/bora/build/esx/release/python-2.6-lib-zip-stage/469512/visor/pylib/python2.6/site-packages/vmware/esximage/Vib.py", line 1382, in _XmlToKwargs

2018-06-29T11:31:51Z esxupdate: root: ERROR: VibFormatError: (None, "VIB 'esx-base-6.7.0-0.14.8941472' has invalid payload: ")

Any help greatly appreciated, I'm a bit stuck for ideas here.

I have one host in a NSX cluster that is causing the whole cluster to bounce between Ready and Not Ready on the NSX Dashboard. We are running NSX-V 6.3 When I check the status of each host in the cluster it says there is a Communication Channel Issue, only for the one host. Eventually it 'clears' on it's own only to repeat the same actions over again. I always check to ensure the NSX VIBs are present on the host. This cluster is not new to NSX has been running 6 months or more. The behavior has been occurring in last couple months. I have set up alerts in Log Insight as shown in Enable the Alerts for NSX for vSphere  but nothing is being indicated as a problem. I do see some entries in netcpa.log on host about cannot allocate memory but does not seem related to this. Any one else experienced this? How did you troubleshoot and finally address? Thanks.

any idea how I can copy a folder with  bash scripts to a local DS and execute on the esxi host?

Hello All,

I have a Linux VM that was created using the VMware Converter from P2V. The linux guest boots up just fine, and everything seems to be working except for Bridged networking. Even though I have bridged networking selected, it still appeared to be using the NAT setting anyway, given the IP Address the VM currently has.

I had noticed that there were no vmnet# adapters showing in the Win10 host. So I uninstalled VMware Player 14.1.1, then I downloaded the newest Player version 14.1.2 from vmware.com. After the install I am seeing 2 "new" network adapters in the Windows host. However, it still appears to have the same result.

I have Bridged Networking and Replicate Physical Network State enabled for the VM but the Virtual Machine is getting an IP Address from VMnet8, shown in the outputs below:

     *I tried it without Replicate Physical network state as well, with same result...

Linux Guest shows:

# ifconfig -a

eth0      Link encap:Ethernet  HWaddr 00:0C:29:XX:XX:XX 

         inet addr:192.168.122.128 Bcast:192.168.122.255  Mask:255.255.255.0

          inet6 addr: fe80::20c:29ff:fe2b:945/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:1058 errors:0 dropped:0 overruns:0 frame:0

          TX packets:932 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:102194 (99.7 Kb)  TX bytes:91653 (89.5 Kb)

          Interrupt:18 Base address:0x2000

 

 

lo        Link encap:Local Loopback 

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:16436  Metric:1

          RX packets:18 errors:0 dropped:0 overruns:0 frame:0

          TX packets:18 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:1272 (1.2 Kb)  TX bytes:1272 (1.2 Kb)

 

Windows 10 Host shows:

Ethernet adapter VMware Network Adapter VMnet1:

 

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet1

   Physical Address. . . . . . . . . : 00-50-56-XX-XX-XX

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::c45b:6183:a1a3:d2c6%54(Preferred)

   IPv4 Address. . . . . . . . . . . : 192.168.130.1(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : Friday, June 29, 2018 5:45:36 PM

   Lease Expires . . . . . . . . . . : Friday, June 29, 2018 6:30:36 PM

   Default Gateway . . . . . . . . . :

   DHCP Server . . . . . . . . . . . : 192.168.130.254

   DHCPv6 IAID . . . . . . . . . . . : 905990230

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-CA-90-87-54-E1-AD-4C-97-1E

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

                                       fec0:0:0:ffff::2%1

                                       fec0:0:0:ffff::3%1

   NetBIOS over Tcpip. . . . . . . . : Enabled

 

Ethernet adapter VMware Network Adapter VMnet8:

 

   Connection-specific DNS Suffix  . :

   Description . . . . . . . . . . . : VMware Virtual Ethernet Adapter for VMnet8

   Physical Address. . . . . . . . . : 00-50-56-XX-XX-XX

   DHCP Enabled. . . . . . . . . . . : Yes

   Autoconfiguration Enabled . . . . : Yes

   Link-local IPv6 Address . . . . . : fe80::3153:4901:e4a8:4df5%56(Preferred)

  IPv4 Address. . . . . . . . . . . : 192.168.122.1(Preferred)

   Subnet Mask . . . . . . . . . . . : 255.255.255.0

   Lease Obtained. . . . . . . . . . : Friday, June 29, 2018 5:45:39 PM

   Lease Expires . . . . . . . . . . : Friday, June 29, 2018 6:30:39 PM

   Default Gateway . . . . . . . . . :

   DHCP Server . . . . . . . . . . . : 192.168.122.254

   DHCPv6 IAID . . . . . . . . . . . : 939544662

   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-21-CA-90-87-54-E1-AD-4C-97-1E

   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

                                       fec0:0:0:ffff::2%1

                                       fec0:0:0:ffff::3%1

   Primary WINS Server . . . . . . . : 192.168.122.2

   NetBIOS over Tcpip. . . . . . . . : Enabled

Any ideas what could be happening here?

From the Linux guest, if I telnet to one of our switches, and then check who is connected to the switch via telnet, I can see the IP Address of my Win 10 host. So it appears to be using NAT, whether or not I've selected NAT or Bridged.

Thanks in Advance,

Matt

I need to create multiple VM's....how do I go about renaming them so I can keep them straight?

Jim

This guide describes steps to configure and test Azure Active Directory as a federation Identity Provider (IDP) and VMware Identity Manager as a Federation Service Provider (SP).

Assumptions:

Following assumptions are made for this guide:

• A SaaS tenant of VMware Identity Manager
• Azure Active Directory (AD) Premium subscription

Prerequisites:

• At least one test user account in Azure AD Premium
• At least one corresponding test user account in VMware Identity Manager

Configure Azure AD

VMware Identity Manager can federate with Azure AD as a custom application in the app gallery.

Sign into the Azure management portal using your Azure Active Directory administrator account, and browse to:

Active Directory > [Your Directory] > Applications section, select Add, and then Add an application from the gallery.

In the app gallery, add an unlisted app using the Custom category on the left. Enter a name for your VMware Identity Manager app.

Select Configure Single Sign-On.

Select Microsoft Azure AD Single Sign-On

The Configure App Setting screen requires SP metadata informaiton from your VMware Identity Manager tenant.

The Identity Manager SP metadata is available at https://[your_tenant].vmwareidentity.com/SAAS/API/1.0/GET/metadata/sp.xml.

Open https://[your_tenant].vmwareidentity.com/SAAS/API/1.0/GET/metadata/sp.xml in a web browser.

Copy following SP metadata values from VMware Identity Manager to Azure AD configuration Wizard:

• EntityID = IDENTIFIER
• HTTP-POST Assertion Consumer Service URL =REPLY URL

Click Next arrow.

Click Download Metadata (XML) to download Azure AD IDP metadata. This will be used when configuring SP federation connection in VMware Identity Manager.

Click Next arrow.

Complete the configuration wizard.

Assign App to user

Assign the newly created/federated "VMware Identity Manager" to a test user account.

Click Assign accounts.

Select a user and assign

At this stage we have configured IDP connection in Azure AD and assigned the VMware Identity Manager app to a user. Now we need to configure the VMware SP connection.

Configure VMware Identity Manager SP connection

Log into you VMware Identity Manager tenant as admin user and navigate to:

Identity & Access Management > Identity Providers > Add Identity Provider > Create Third Party IDP

Give a name to this Identity Provider (e.g. Azure AD).

Azure AD Identity Provider metadata file was downloaded in one of the steps above. Open this file in a text editor and copy/paste Azure AD IDP Metadata into Identity Provider Metadata(URL or XML) text box and press Process IdP Metadata button. There should be no error messages.

Under Name ID format mapping from SAML Response, add two mapping as below:

Under Users, select the user store for your test user(s)

Under Network, select All Ranges

Under Authentication Methods, select “urn:oasis:names:tc:SAML:2.0:ac:classes:Password”.

Also name the authentication method (e.g. AzureAD-Password)

Click Add button at the bottom of the page to save the SP connection configuration. The following screenshots depict all settings.

Under Identity & Access Management > Policies, select default_access_policy_set

Under Policy Rules, select Device Type Web Browser (note: feel free to try out other device types as well)

Under Edit Policy Rule, select the newly created Azure AD Authentication Method (e.g. AzureAD-Password).

Save changes.

Let's Test Now

Make sure you have a user account in VMware Identity Manager that maps to a user account in Azure AD.

Two user authentication flows can be tested:

• IDP initiated authentication
  To test this flow goto:
  http://myapps.microsoft.com and login with your test user account and click on the VMware Identity Manager app icon.
  Here's a video of this authentication flow:
  
  
  

• SP initiated authentication
  To test this flow, goto:
  https://[your_tenant].vmwareidentity.com.
  Here's video of this authentication flow:
  
  
  
  
  
  

Hello All,

Working with VCO and trying to get all cluster that are part of a datacenter due to my cluster names are not unique across all my vcenter i have connected to orchestrator. What would be the best approach to accomplish this?

I have installed vSphere Replication Appliance 6.5.0.1104 Build 4633956, configured it and connect it to vsphere server. In vSphere Web Client  version 6.5.0 the only task with error is:

"The name 'Cannot replicate VM configuration to the remote site.' already exists.", but the VR icon just not appear.

And, in task list, i can see that theVR plugin was successfuly installed: The deployment of plug-in vSphere Replication 6.5.0.654633957 is successful. Log in again to view the interface of the plug-in.

Am i missing anything?

Installed VMWare Workstation on a fresh Linux PC but am unable to open any VMs. I am able to create VMs as can be seen by the 'Windows 7 x64' folder on the desktop. When I click 'Open a Virtual Machine' I get an open file dialog and can select a file but nothing happens.

Anyone have any solutions or suggestions?

Edit: Forgot to mention I have a SSD full of VMs that work on my Windows PC but not on the Linux PC.

Also, I just clicked on the 'Workstation' button at the top not realizing there are two forums for Pro and Player. Could someone move this for me?

Hello, Im trying to run 144 hz on a my guest and can't seem to manage to do it, is that even possible? if yes, how? My specs are:

i5 3470 3.6 ghz(oc)

gtx 770 4 gb

12 gb ram

host - windows 7 64 bit

guest - ubuntu 18.04

Thanks for the help.

When utilizing Relay Servers, there are two ways the files can be sent from the Workspace ONE UEM console to the Relay Server: Push and Pull.

On a Push configuration, the files are sent to the Relay Server via an FTP connection (FTPS and SFTP are also supported). That means that SaaS users would need a public DNS to make the Relay Server available, so the Workspace ONE UEM server can open a connection to send over the files.

As an alternative, a Pull Service may be installed on the Relay Server. In this scenario, the Pull Service will regularly check the console server for files to download and, when there’s something available, it would download this content and place it on FTP home directory. Since the Pull Service is the component that opens a connection (HTTPS) to the Workspace ONE UEM console, there’s no need for it to be public.

Note that the Pull Service is only responsible for downloading files from the Workspace ONE UEM environment. The Relay Server still needs an FTP service running, so the devices can reach out to it to download packages.

Below is a diagram of how this communication would look like:

When installing the Pull Service, you will need both the Installer and the Configuration File (PullServiceInstaller.config). The Configuration File looks like the following:

<?xml version="1.0"?>

<PullConfiguration>

    <libraryPath>C:\FTP_Home\</libraryPath>

    <endPointAddress>https://<Console Server URL>/contentpull</endPointAddress>

</PullConfiguration>

Make sure you adjust the libraryPath and the endPointAddress accordingly before running the installer.

Outbound Proxy

In some cases, your internal network might need an outbound proxy, so the Relay Server can communicate to the SaaS environment. As the Pull Service installer does not give us an option to configure an outbound proxy, I got around this by doing the following:

1. After installing the Pull Service, the installation folder will have a file called AirWatch.Services.PullService.exe.config. This file will look like this:

<?xml version="1.0"?>

<configuration>

  <appSettings>

    (…)

  </appSettings>

  (…)

</configuration>

2. Between <configuration> and <appSettings>, add the following:

<system.net>

    <defaultProxy enabled="true" useDefaultCredentials="true">

        <proxy usesystemdefault="true" proxyaddress="http://<proxy_address>:<port>"/>

    </defaultProxy>

</system.net>

Note: Adjust the XML values accordingly.

3. Restart the Pull Service.

Troubleshooting

If you need to troubleshoot the Pull Service, a Log file is created on the folder where the Pull Service is installed. This log will indicate if files are being downloaded, if there’s any connectivity issues, etc.

The links below point to the documentation on how to install the Pull Relay Service:

Configure a Relay Server: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/9.5/vmware-airwatch-guides-95/GUID-AW95-ConfigureRelayServer.html

Create a Windows-Based Pull Service Relay Server: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/9.5/vmware-airwatch-guides-95/GUID-AW95-CreateWindowsPullRelayServer.html

Create a Linux-Based Pull Service Relay Server: https://docs.vmware.com/en/VMware-Workspace-ONE-UEM/9.5/vmware-airwatch-guides-95/GUID-AW95-CreateLinuxPullRelayServer.html

--

The postings on this site are my own and do not represent VMware’s positions, strategies or opinions.

Hi guys,

I'm estimating performance of a flash storage array in VM environment, using vdbench as test tool.

Can anybody share me a Parmfile of vdbench for typical VM workload?

Maybe included as follows:

IO size and distribution, R/W ratio, random ratio, dedup/compress ratio...

Thanks a lot.

We're seeing an error on our VSAN cluster after upgrading from 6.5 to 6.7. Error is "Unexpected VMware Update Manager (VUM)baseline creation failure. Please check vSAN and VUM logs for details", we've reset the VUM database and checked the logs but nothing sticks out.

Has anyone seen (and resolved) something similar?

my website：www.ultrahardmaterial.com

What can I do to improve

I've upgraded to 6.7 and after listening to the latest VMware Webcast - What’s New with vRealize Operations 6.7. Your Path to Self-Driving Data Center Operations. it sounds like I should be able to edit the default cost settings that are held in the database from the GUI.

I've looked through my admin tab but can't see anywhere this is possible.  Has anybody else been able to edit default costs?

upgrade vcenter 5.1 to 6.0 while  error ：

[SSL: SSL_NEGATIVE_LENGTH] dh key too small (_ssl.c:661)' while validating ssl certificate

瑙ｅ喅鏂规: Make sure that the sso service is started before continuing"