Quantcast
Channel: VMware Communities: Message List
Viewing all 226966 articles
Browse latest View live
↧

Early Access: Design and Deployment of VMware Skyline within the VMware Validated Design for SDDC

August 25, 2018, 7:15 am
$
0
0

As many of you may know, this Early Access sub-community provides you an opportunity to download and discuss pre-released design materials for the VMware Validated Designs. We want you discover the latest content that is in development and learn about the potential directions in these designs.

 

I'm please to share the work that we recently completed, Design and Deployment of VMware Skyline within the VMware Validated Design for SDDC. This early access material covers the architecture and design elements, plus deployment guidance, for adding Skyline Collector 1.4 to the VMware Validated Design and is applicable to single-region, dual-region, and multi-availability zones.

 

VMware Skyline is a technology for proactive support. VMware Skyline uses automation to securely collect data and perform environment-specific analytics on configuration, feature, and performance data. The resulting information improves visibility in your environment. As a result, VMware and your organization interact without extensive time and investment by support administrators. As a result, proactive, predictive, and prescriptive recommendations by VMware improve the stability and reliability of the environment. In addition, reactive support issues can be resolved more quickly.

 

Got feedback?

 

We want to hear from you. So dive into this latest early access content and share your feedback directly with our solutions architects and product managers!

↧
Search

Re: VM+vdisks limitation for migrate

August 25, 2018, 7:24 am
$
0
0

what does this mean

 

Concurrent vMotion operations per VMFS volumes   128

 

vMotion operations per host (10 Gb/s network)      8

 

vMotion operations per datastore          128

 

Storage vMotion operations per host          2

 

Storage vMotion operations per datastore     8

↧
↧

Re: Unable to run virtual machines after the upgrade to 6.7

August 25, 2018, 7:35 am
$
0
0

In the vSphere web client

Actions > Compatibility > Upgrade VM Compatibility....

How old is this VM that it has the HW version set so low??

Here is a document talking about the hardware version upgrade: VMware Knowledge Base

Before you upgrade the virtual hardware:

  1. Create a backup or snapshot of the virtual machine. For more information, see:

  2. Upgrade VMware Tools. On Microsoft Windows virtual machines, if you upgrade the virtual hardware before you upgrade VMware Tools, the virtual machine might lose its network settings.
  3. Verify that all .vmdk files are available to the ESXi/ESX hosts on a VMFS 3, VMFS 5, or NFS datastore.
  4. Verify that the virtual machines are stored on VMFS 3, VMFS 5 or NFS datastores.
  5. Determine the version of the virtual hardware by selecting the virtual machine from the vSphere Client or vSphere Web Client and clicking the Summary tab. The VM Version label in the Compatibility field displays the virtual hardware version

Please consider marking this answer "correct" or "helpful" if you think your question have been answered correctly.

↧

Re: Unable to run virtual machines after the upgrade to 6.7

August 25, 2018, 7:44 am
$
0
0

Upgrading a white-box can always be a hit, or miss.

Anyway, please follow the upgrade steps again until step 4, but replace the command with the one below, and post the output.

esxcli software profile install -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml -p ESXi-6.7.0-20180804001-standard --ok-to-remove --dry-run

Note: This command will not modify anything (--dry-run), but will show what's left over from the old installation.

 

André

↧

Re: SCP between 4.1 and 6.7 no matching KexAlgo

August 25, 2018, 7:50 am
↧
↧

Esxi Time

August 25, 2018, 8:49 am
$
0
0

hello everybody,

 

Using latest Esxi. But VMMachines time is not properly correct though I made those correct many times!

 

Do I have to make it correct from Esxi?

 

Thanks in Advance

 

redhot4400

↧

Re: Esxi Time

August 25, 2018, 9:03 am
$
0
0

Yes, you need to set the time properly within ESXi or use an NTP server as the source of clock sync.

↧

Re: VM+vdisks limitation for migrate

August 25, 2018, 9:21 am
$
0
0

At any given point of time, these many respective tasks can run at the maximum per object. For example, for a 10 GB vMotion network only 8 concurrent vMotion operations per host will be possible. The 9th one will be queued (though, on the client it says it has started) and the data copy will start only when one of the initial 8 tasks is completed.

 

Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered.

 

Cheers,

Supreet

↧
Search

Re: Esxi Time

August 25, 2018, 9:26 am
↧
↧

Re: Data Integrity Errors Creating Package via CloudClient - vRA 7.2 Environment

August 25, 2018, 9:50 am
$
0
0

I tried version 4.2 and got the same error.

↧

Re: Esxi Time

August 25, 2018, 10:04 am
↧

Re: Esxi Time

August 25, 2018, 10:07 am
$
0
0

Hello diegodco31,

 

Thanks for your nice reply with screenshot.

 

I checked it in this way, the time is alright. But problem is with VMs, they keep changing time.

 

Thanks in Advance

 

redhot4400

↧

Re:XaaS provisioning request - no item in the "Items" tab

August 25, 2018, 10:14 am
$
0
0

it seems as if everyone who works with dynamicTypes will read this sooner or later. i have checked unhappyvra´s statement and this looks like the right answer.if i use the findForType method my deployed item does NOT show up in VRA. if i use the DynamicTypesManager.getObject method the deployed item DOES show up in vra. for those who are new to DynamicTypes, you have to bind the result of the DynamicTypesManager.getObject method to an out variable that represents the DynamicTypes Type you use. The following is a scriptable task that sets outitem to the result of the DynamicTypesManager.getObject method. outitem represents the DynamicTypes Type testItem in the namespace test.

testItem2= Server.findForType("DynamicTypes:test.testItem", "testFolder" + "/" + "testItem");
System.log("testItem2 : " + testItem2);
System.log("testItem2.id: " + testItem2.id);
testItem = DynamicTypesManager.getObject("test", "testItem", testItem2.id);
System.log("testItem2.id: " + testItem.id);
item=testItem;
outItem=testItem;
System.log ("testItem2 :" + testItem2);
System.log ("outItem :" + outItem);
System.log ("item :" + item);

 

 

 

 

finally a few links that helped me:

a good overview:   https://www.vcoteam.info/articles/learn-vco/281-enabling-vcloud-

a detailed implementation:   https://www.vcoteam.info/articles/learn-vco/323-how-to-create-a-microsoft-dns-dynamic-types-plug-in.html

 

t.

↧
↧

Re: Esxi Time

August 25, 2018, 10:17 am
$
0
0

See if you are synchronizing with the esxi.

↧

Re: Esxi Time

August 25, 2018, 10:22 am
$
0
0

Run this command (windows). Check your ntp server is the esxi.

>net time

↧
Search

Re: Unable to run virtual machines after the upgrade to 6.7

August 25, 2018, 10:57 am
$
0
0

In the vSphere web client

Actions > Compatibility > Upgrade VM Compatibility....

 

Have a look at one of my screenshots above. This is unfortunately not an option, because the "Actions" button is grayed out.

 

How old is this VM that it has the HW version set so low??

I do not remember that. It was installed when ESXi 5.1 was the newest version, so most likely 2013. I have subsequently updated to ESXi 6.0 (through USB installation) without any problems whatsoever. I was also using the native Windows vSphere client app until today. Right now I have updated to 6.7 and problems appeared.

 

Here is a document talking about the hardware version upgrade: VMware Knowledge Base

Have a look at one of my screenshots above. This is unfortunately not an option, because the "Compatibility" button is grayed out.

 

Thank you.

↧

Re: Unable to run virtual machines after the upgrade to 6.7

August 25, 2018, 11:00 am
$
0
0
Anyway, please follow the upgrade steps again until step 4, but replace the command with the one below, and post the output.

Thanks, here is the output:

https://paste.ee/p/0ZVnN

 

Btw. some of those "VIBs Removed" may possibly be my test attempts that I have installed to make it work. I am just mentioning it so that we will not stuck on them while thinking that this is the actual problem (e.g. xAHCI from front.de, locker tools).

↧
↧

Re: Unable to run virtual machines after the upgrade to 6.7

August 25, 2018, 11:13 am
$
0
0

What about vmfs not being upgraded issue? Perhaps I should do that manually using SSH command.

 

[root@ESXi:~] esxcli storage vmfs upgrade -l Datastore

Cannot find VMFS volume with label Datastore

[root@ESXi:~] esxcli storage core path list

sata.vmhba64-sata.0:0-naa.50014ee6567fa232

   UID: sata.vmhba64-sata.0:0-naa.50014ee6567fa232

   Runtime Name: vmhba64:C0:T0:L0

   Device: naa.50014ee6567fa232

   Device Display Name: Local ATA Disk (naa.50014ee6567fa232)

   Adapter: vmhba64

   Channel: 0

   Target: 0

   LUN: 0

   Plugin: NMP

   State: active

   Transport: sata

   Adapter Identifier: sata.vmhba64

   Target Identifier: sata.0:0

   Adapter Transport Details: Unavailable or path is unclaimed

   Target Transport Details: Unavailable or path is unclaimed

   Maximum IO Size: 32768

 

 

sata.vmhba0-sata.0:0-naa.50014ee260e467d1

   UID: sata.vmhba0-sata.0:0-naa.50014ee260e467d1

   Runtime Name: vmhba0:C0:T0:L0

   Device: naa.50014ee260e467d1

   Device Display Name: Local ATA Disk (naa.50014ee260e467d1)

   Adapter: vmhba0

   Channel: 0

   Target: 0

   LUN: 0

   Plugin: NMP

   State: active

   Transport: sata

   Adapter Identifier: sata.vmhba0

   Target Identifier: sata.0:0

   Adapter Transport Details: Unavailable or path is unclaimed

   Target Transport Details: Unavailable or path is unclaimed

   Maximum IO Size: 32768

 

 

sata.vmhba1-sata.0:0-naa.5000c5004f06c948

   UID: sata.vmhba1-sata.0:0-naa.5000c5004f06c948

   Runtime Name: vmhba1:C0:T0:L0

   Device: naa.5000c5004f06c948

   Device Display Name: Local ATA Disk (naa.5000c5004f06c948)

   Adapter: vmhba1

   Channel: 0

   Target: 0

   LUN: 0

   Plugin: NMP

   State: active

   Transport: sata

   Adapter Identifier: sata.vmhba1

   Target Identifier: sata.0:0

   Adapter Transport Details: Unavailable or path is unclaimed

   Target Transport Details: Unavailable or path is unclaimed

   Maximum IO Size: 32768

 

Here is the core devices list command output:

https://paste.ee/p/6ipB2

↧

Re: Unable to enumerate all disks

August 25, 2018, 11:21 am
$
0
0

Thank you for all of your help!!!!!!!

↧

Re: Unable to run virtual machines after the upgrade to 6.7

August 25, 2018, 11:27 am
$
0
0

There's no need to upgrade VMFS. As a side note, an upgrade from VMFS5 to VMFS6 - if you plan to do this at a later time - is no inplace upgrade. You'll have to reformat the datastores.

The vmkernel.log that you've posted contains entries for the 3 disks as being detected as sanpshot LUNs.

Please run

esxcli storage vmfs snapshot list

and if the LUNs show up, you may be able to mount the datastores from the command line by following the steps in https://kb.vmware.com/s/article/1011387

 

André

↧
Viewing all 226966 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>