Hi

I've been having trouble with the VDP Appliance in Version 6.1. Its a fresh install, running on a Windows vCenter 6.0.0 Build 3018524 and using a Buffalo TeraStation NAS as backup destination.

The problem starts when I try any kind of backup job. Before that everything works as intended. Creating jobs, managing the appliance etc. Once I start a backup job the appliance kind of freezes. In the web client it wont load any data

Sometimes in runs into the error that the time snyc. isnt working properly. Although I have checked vCenter Server, the hosts and the appliance. They're all configured with the proper ntp server and syncing properly. The VDP appliance is also showing the correct time. Restartet the tools services aswell.

At some point the Web Client looses the connection to the appliance.

Connecting over SSH to the appliance sometimes runs into timeouts aswell. Restarting the VDP appliance takes about 20-30 minutes.

UPDATE:

After literally a hour I was able to connect back into the appliance within the the web client. My test backup job started gradually counting up to 38% (Its 20GB small and really shouldnt take a hour to backup). After a few minutes it disconnected again.. the task stopping at 38%.

One thing to note: The VDPs virtual install disk is running on the same datastore as where its backing up to. Could this be the problem im having? I cant really any other problems within the config.

David

Hello,

It was very exciting moment when version 12.0 was released - so many improvements and OpenGL 3.0 support looked very impressing and promising. Unfortunately initial enthusiasm went away as soon as it turned out that entire virtual machine would crash when OpenGL is in use.

The application (kind of Map/Gis tool) I run in host (which happens to be x64 Windows Server 2012 R2) requires OpenGL 2.1 as minimum. Considering requirements application it worked quite well on VMWare 7.x (tools 9.3). Most of the application functions were working well and just a few did not. Those functions which did not _never_ crashed a virtual machine (the also never crashed the application) - they just did nothing - as never used. I hoped that things can only get better with an update to VMWare 12. Better OpenGL support (3 version) and lot of improvements.

Actually things got much worse. Some functions which used to work well before upgrade now are not working at all. The worst news, however, is the fact that entire virtual machine goes down when some of the application functions are used (functions which worked well before). This is what happens when thing go wrong:

My Environment:

Host OS: Windows 7 Professional (x64)

Host Graphics: Radeon R390 (checked with several drivers - currently latest stable version installed)

Guest OS: Windows Server 2012 R2 (x64)

VMPlayer 12.0.0, 12.0.1, 12.1.0 (latest VMWare Tools installed in each case)

Considering the situation I would like to ask two questions:

1. Is the VMWare Team aware that a problem exists (I could not find any notes addressing kind of issues I'm experiencing and describing here). Do they have a fix on the roadmap? And if they are aware could someone please redirect me the place where I can find more information related to the problem?

2. If they are not aware what is the best way to let them know about the problem?

For those who are willing to help I can provide additional info (log file or other remnants of virtual machine crash) or perform some extra test scenarios. As you can see I'm using Player here but I have a strong feeling that Workstation would experience exactly the same problem.

--

Mark

hi,

I am having a strange problem.

when i am copying a file to another server from esxi console i am having a slow speed but when i am copying a same file from a virtual mahine on a same host i am getting a different speed.

All the underlying network is same. my management and VLAN settings are same. my management (esxi management console ) are using same NICS even.

why is this difference...

The Dynamic Types plug-in available with vRealize Orchestrator gives considerable flexibility to what you wish to offer "as a Service" via vRealize Automation. Christophe has released a Dynamic Types plug-in generator package that helps simplify the creation of a Dynamic Types plug-in for HTTP-REST services. He's also provided an NSX-v Dynamic Types plug-in using this technology. The plug-in attached here is intended to help map database tables to vRO so that you may easily request table records as a service.

NOTE/WARNING: This package was developed and tested with a Microsoft SQL Server. As such, the query in the action "com.vmware.coe.sql.getTableColumnNames" is likely to only work with a SQL Server. If you are using PostgreSQL, MySQL, or Oracle, you will likely need to modify the first line of this action to reflect the proper syntax of retrieving a record.

This is my first Dynamic Types plug-in generator package so please do provide feedback

The package was developed for use with a series of articles on my blog. As I work through the series, I'll add links here:

1. SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 1
2. SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 2
3. SQL Plug-in + DynamicTypes = Simple CMDB for vCAC - Part 3

What does the attached package do?

The package attached here will quickly build out an inventory based on a SQL Plug-in Database Table

General Instructions are below: (For more detailed instructions, please view the articles linked above)

1. Import the package to your vRO server
2. Have one or more Databases setup in the SQL plug-in
3. Run the "1 - Define Plug-in Namespace and DB" workflow
4. Run the "2 - Define a Type and its parent folder" workflow
5. Refresh your vRO Inventory and confirm the table you mapped now shows as a folder under your namespace and records in that table show as inventory items (See screenshot above as example)

Note: This package was developed and tested with vCO 5.5.2.1 and vCAC 6.1. Please notify me of any issues under vRO 6.0 and vRA 6.2 using the comments here.

This Package is now available on FlowGrab.com as "dynamictypes-dbplugingenerator" !

As customers begin moving to the cloud, their first two considerations are networking and security. “How do I connect my data centers to the cloud?” “How do I connect various cloud data centers/zones/regions to each other?” “How do I secure applications in the cloud?” “Can I use my existing firewalls/vulnerability scanners/intrusion detection/compliance/configuration management tools or should I use something different?”

Speaking from a vCloud Air perspective, our implementation of hybrid networking achieves much more than the others: vCloud Air is built with NSX as the core network stack. NSX is not an add-on running in a separate layer on top of something else; NSX IS the network for vCloud Air. It provides very real benefits for us as a cloud operator as well as you as a cloud consumer. You don’t have to worry about who to call for support – you call us – and we don’t have to worry about incompatibilities between NSX and a different lower level networking stack because there is no lower level stack.

To learn more, just visit the vCloud Air blog: Hybrid Networking is Available NOW: Why wait for (Windows) 2016 and a New (Azure) Stack? - VMware vCloud Air Blog - VMwa…

Companies of all sizes are adopting DevOps to get faster delivery of new features and capabilities, while also getting faster resolution to problems that arise. Yet one of the more challenging aspects for new organizations adopting DevOps is setting up the tool chain to support Continuous Integration. With multiple tools involved in an end-to-end workflow, it can be difficult to get past the planning stages to the point where organizations see tangible results.

To learn more, just visit the vCloud Air blog: Jumpstart DevOps with vCloud Air - VMware vCloud Air Blog - VMware Blogs

Our VDI run Teradici audio drivers, we use Jabra headsets .

Audio and microphone work with view desktop when accessed via Horizon client on windows 7 , and teradici Zero clients.

We have been trialling Chromebooks ,   Audio and Microphone work when using the PCoIp client app , but if we run the Horizon client , all we get is Audio, the microphone picks up no sound ?

The chromebook must be supporting usb passthrough for the PCoIp app to work, so unsure why the Horizon 6 view client is having issues . Would have expected either both to work, or neither.

Its noted the horoizon client on the google webstore is only 3.5.0 , though is dated Sept 2015

Any help much appreciated

In a blueprint there's a setting that determines how long a VM will live as an expired VM before it's fully decommissioned.  Since we're using ASD now we're using a few master blueprints for everything and all of the customization is happening in the vRO.  I haven't been able to figure out a way to overwrite that value on a per VM level.  Ideally I'd like to change that time to destroy setting to something much shorter for TST and Sandbox VMs.  Has anyone looked at this before?  Thanks for any info,

Hi,

is there anybody who has HP DL360/DL380 with P440ar and vSAN 6.1?

I have install custom HPE ISO 6.0 U1 (build 307316) and there is hpsa driver version 6.0.0.144-1 BUT on vSAN compatibility matrix is driver hpsa.5.5.0.106-1. vSAN healthcheck shows warning aganist HCL but it works fine.

thank you for your replies.

Joseph Zach

Currently I have one Standard vSwitch with one vmk for NFS storage for my datastores. The vmk is using two vmnic physical adapters which are configured in an etherchannel across two Cisco switches in a stack and the vSwitch teaming and failover is configured to load balance the route based on IP hash and both adapters are active. The vmk is assigned to my NFS VLAN ID. All is operating in a two host cluster.

All of my physical adapters are populated and I need to add ISCSI for SAN storage to compliment the existing NAS storage.

My questions are:

1) Can I add a second vmk to the vSwitch mentioned above and IP it and assign it to an ISCSI VLAN ID?

2) Should I run NFS and ISCSI on different VLANs, but utilizing the same two physical adapters that I am already using for NFS storage for my current datastores?

3) From my research it looks like for Load Balancing/Failover NFS and ISCSI should be configured differently. ISCSI more of an active/passive configuration where the vSwitch setting are being overwritten and forcing one vmnic to be active and a secondary to be passive, even to the point of using two separate vmks for ISCSI.

Any insight anyone could pass along would be greatly appreciated.

Thank you

Bare with me as I'm new to this stuff.

I do have a quite a bit of programming experience and can learn quickly, but I am just new-ish to VMware, its ecosystem, terminology, etc.

We have an idea for an ESXCLI plugin/namespace, but it's going to require a dependency on a specific python library.

This python library in turn has some OS-level dependencies like OpenSSL and SWIG.

I know that ESXi will wipe anything on it's filesystem not in /scratch or not installed from a .vib.

So I'm guessing we're going to have to create a .vib to get these dependencies on the host.

ESXi comes with openssl, but not swig (i believe), and I even think its python installation has been altered by VMware and possibly missing some standard library modules.

My question is, how do I go about getting these missing dependencies on the host? I imagine I have to get any missing build tools on the host too, so that the missing dependencies can get compiled for ESXi.

As you can tell I am pretty lost getting started on all of this.

Any help would be greatly appreciated!

Hi there,

I am planning to develop a vcenter plugin that is hopefully able to support as many vSphere versions as possible. So far, I know that using the web client SDK, I should be able to support vSphere-5.1,5.5 and 6.0. 

But on the other hand, each vSphere version has its matching SDK version. If my objective is to share as much code as possible and support all 3 vSphere versions (5.1, 5.5 and 6.0), what is my best strategy?

Assuming vSphere is backward compatible, can I assume a plugin developed using the SDK-5.1 is able to run smoothly on vSphere-5.5 and 6.0? Or  should I best start at the SDK-6.0 instead?

I am not sure there would be a positive answer to either of my question above. I have a feeling that I probably have to write some version specific code for each of the version that I support. But the kind of functionalities I am trying to achieve is mostly focused on server extension instead of UI and I don't think they are that different from 5.1 to 6.0. I hope I can find a way to share most if not all of my code across the different versions. Is there any best practice or advice for doing this?

Thank you very much,

Shi

Hi,

I have a problem when expanding datastores in 5.0.U1, U2, U3 versions. When large disk cabin, ESXi recognizes the new size, but in "Properties" Datastorage the button "Increase" this is disabled:

I have opened a case with vmware and was told that is a workaround for versions 5.0.X and 5.1.x and  in the 5.5.x version is corrected. He sent me this link: VMware KB:    Cannot grow VMFS datastore, the Increase button is disabled  but I can not apply because it involves service stop.

I found this KB VMware KB:    Growing or expanding a VMFS volume or datastore  and following the steps sometimes allows me to do the expansion, I enable the "Increase", but  many times the button  not working, continues disabled.

I found thisl post "Scripted resize of VMFS datastores" but the script fails me, I can not make it work.

The script is this:

$ds = Get-Datastore -Name "Volume05"
$dsscsi = get-datastore $ds | get-scsilun
$dscanonical = $dsscsi.CanonicalName
$esx = Get-View $ds.ExtensionData.Host[0].Key
$storSys = Get-View $esx.ConfigManager.StorageSystem
$dsSys = Get-View $esx.ConfigManager.DatastoreSystem
$vmfsPath = $ds.ExtensionData.Host[0].MountInfo.Path
$storSys.RescanAllHba()
$extent = $dsSys.QueryVmfsDatastoreExpandOptions($ds.ExtensionData.MoRef)
$spec = New-Object VMware.Vim.HostScsiDiskPartition
$spec.diskName = $dscanonical
$spec.partition = "1"
if($extent.Count -ne 0){  $storsys.ExpandVmfsExtent($vmfspath,$spec)
}

The error I get is:

Excepción al llamar a "ExpandVmfsExtent" con los argumentos "2": "A specified parameter was not correct.
"
En E:\Resize_VMFS_01.ps1: 15 Carácter: 3
+   $storsys.ExpandVmfsExtent($vmfspath,$spec)
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException    + FullyQualifiedErrorId : VimException

Please can someone help me?

Regards

Daniel

I'm building a script to query the vSphere API for various critical performance metrics for CPU, MEM, Network and Disk performance metrics from vCenter.  

I'll then use this data to set various thresholds to generate alerts and also graph performance.

My question is - should I query the API using the PerformanceManager methods or simply grab the "quick stats" data objects?

Here is what I found in this vSphere documentation: vSphere Documentation Center

"You can obtain near real-time summary information about performance or utilization without using the PerformanceManager methods. vSphere servers maintain “quick stats” data objects for hosts (HostListSummaryQuickStats), virtual machines (VirtualMachineQuickStats), and resource pools (ResourcePoolQuickStats). For more information about these objects, see the vSphere API Reference."

It seems that the PerformanceManager method provides far more "Performance Providers" than the "quick stats" as summarized below:

PerformanceManager >> Performance Providers:

Cluster Services

    CPU

    Management Agent

    Memory

    Network

    Resource Scheduler

    Storage Capacity:

        Datastore / Virtual Machine

    Storage I/O:

        Datastore

        Disk

        Virtual Disk

        Storage Adapter

        Storage Path

    System

    Virtual Machine Operations

Quick Stats

         Hosts

         VMs

         Resource Pools

Anyone grappled with this question before?

Thank you!

Amir

Hi,

Running vRA v6.2.3 and vRO v6.03. The AD plugin (v2.03) is configured with three Active Directory in the same forest, for example corp.local, dev.corp.local and pre.corp.local. All three are registered with the AD plugin and can be browsed from vRO AD Plugin.

I have an 'AD description' vRO workflow which updates the virtual machines description in AD. This works fine for corp.local but when attempted with systems from the other domains it fails with a 'TypeError: Cannot call method "getAttribute" of null'

The relevant IN parameters are the description, the computers AD description vCACVm (vCAC:VirtualMachine) and computerAD (AD:ComputerAD).

The code as follows...

computerAD=ActiveDirectory.getComputerAD(vCACVm.virtualMachineName);

System.log("Old computer account description is :"+computerAD.getAttribute("description"));

System.log("Setting new description as :"+description);

computerAD.setAttribute("description",description);

I can't figure out what I'm missing?

Cheers

I'm building a script to query the vSphere API for various critical performance metrics for CPU, MEM, Network and Disk performance metrics from vCenter.  

I'll then use this data to set various thresholds to generate alerts and also graph performance.

My question is - should I query the API using the PerformanceManager methods or simply grab the "quick stats" data objects?

Here is what I found in this vSphere documentation: vSphere Documentation Center

"You can obtain near real-time summary information about performance or utilization without using the PerformanceManager methods. vSphere servers maintain “quick stats” data objects for hosts (HostListSummaryQuickStats), virtual machines (VirtualMachineQuickStats), and resource pools (ResourcePoolQuickStats). For more information about these objects, see the vSphere API Reference."

It seems that the PerformanceManager method provides far more "Performance Providers" than the "quick stats" as summarized below:

PerformanceManager >> Performance Providers:

Cluster Services

    CPU

    Management Agent

    Memory

    Network

    Resource Scheduler

    Storage Capacity:

        Datastore / Virtual Machine

    Storage I/O:

        Datastore

        Disk

        Virtual Disk

        Storage Adapter

        Storage Path

    System

    Virtual Machine Operations

Quick Stats

         Hosts

         VMs

         Resource Pools

Anyone grappled with this question before?

Thank you!

Amir

People,

I'm having some serious issue here after upgrading the HP Blade BL 465c G7 with Emulex NC551i Dual Port FlexFabric 10 Gb adapter.

The problem: After successful inline update from ESXi 5.1 Update 2 Patch 5 (2000251) into ESXi 5.1 Update 3 (2323236) the ESXi server cannot be pinged nor it can ping to outside network, therefore it failed to reconnect back to VCenter server.

Software/Firmware version:

Before the upgrade of the server the version are as follows:

~ # ethtool -i vmnic0

driver: be2net

version: 10.2.293.0

firmware-version: 4.9.416.2

bus-info: 0000:04:00.0

~ #

Since the version above doesn't work, I've managed to download VMW-ESX-5.1.0-be2net-10.2.477.20-offline_bundle-2541837.zip to upgrade the VMNic driver it into: 10.2.477.20 but still after the update and reboot the network is not ping-able.

Rollback:

I have also tried to perform rollback to the previous working ESXi server version 2000251 using Shift+R but the ESXi server still rebooting as 2323236 with no working network still.

Any other suggestion would be greatly appreciated without having to reconfigure the ESXi settings and Distributed Switch configuration from scratch.

Hi folks,

Sorry if this is a newbie question, but...

I have a 32-bit PC running XP, and I just bought a 64-bit PC running Windows 10.  The XP box contains a PCIe audio interface card, and I plan to remove that card from the old PC and insert it into the new PC.

Before removing the card, though, I'm going to create an image of the XP system (using vCenter Standalone 5.5), which I'll then run in Workstation Player as a guest on the new machine.

So here's my question: Will Workstation Player automatically associate the physical PCIe card in the new machine with the virtual PCIe card in the VM?

Thank you,

T.

Any word on when Mirage will support Office 2016?