Hi there

i have been making lots of vmware project for the last 10 years, i do have prepared a project documentation  for handling the project to the customer but i am not really satisfied what i had done .

Is there a method or a tool in vmware environment for documantating the environment (i do mean the vmware environment)

For example ,when i do a project with netapp storage , i do use netapp-docs after the setup ,and create a huge document which i deliver it to the customer.

if so please lead me to it

thanks a lot

Every time I try to boot up my virtual machine (OSX Yosemite) I get an error message :

VMware Player unrecoverable error: (vcpu-0)

vcpu-0:VERIFY vmcore/vmm/main/physMem_monitor.c:1123

A log file is available in "C:\Users\FF\Documents\Virtual Machines\OS X 10.10\vmware.log".

You can request support.

To collect data to submit to VMware technical support, run "vm-support".

We will respond on the basis of your support entitlement.

I'm unsure why I'm getting this error - any help much apprecated!

Hello Community,

I've a problem to connect a vm from itself on it's erxternal IP trough a vse.

I've in my webapplication a link to a vhost an the same vm. The vm resolv this name to the external IP of itself and get a connection refused. If i use the internal IP of the vm, than all it's ok.

NAT and firwall rules are ok, from outside, there are no problems to connect the vm.

Is there a way to connect a vm itself by external IP?

Thanks

Markus

So got vROps up and running for about 2 years and have some great data from it.  We are starting to roll out the EPO Agent to all of our VM's because as we all know, what the HyperVisor thinks the VM is using and what the VM thinks it's using as far as resources (RAM, CPU) most often are different.  So my conundrum is, having all this data, how can I create a dashboard that can display both HyperVisor metrics and GuestOS metrics together on the same scorecard after picking a VM from a object list? 

The main issue I'm seeing is that the EPO agent object and the GuestOS object don't automatically relate to the Virtual Machine object, which makes it tough to use all the data together in one cohesive manner.

I guess that brings another question; how does vROps use the GuestOS metrics in it's analytics of the VM?  or can it even do that?

I'm attempting to update our VCSA's from 6.0 U3a to 6.0 U3b using vSphere Update Manager but I'm receiving the error:

I have attempted to apply the .zip file directly from the download site but again, there's a problem with the package:

This environment is in a secure zone - the vSphere Hardening Guide has been applied to all components - so I'm guessing that this is the cause as it will not accept invalid signed packages.

Can anyone help with a fix on how to apply an invalid signed package from VMware within a hardened environment?

Should this be flagged for VMware to have the update signed correctly?

Any info would help.

Thanks

Andy

I've got several workflows that call several actions.

In an effort to make the logging a little bit better, I'm wondering if there's a way to know the name of the action from within the action itself.

so for example, i have an action

com.anoop.library.GetVMUuid

within the script, can i do something like

System.log($this + ": VM UUID is " + uuid);

is that possible? or are there alternatives?

thanks.

When I use Vcentrer converter standalone 6 to convert server 2008 I am getting the following error.

"Unable to find the system volume, reconfiguration is not possible"

Anyone run into to this problem and find a solution?

Attached is the log file along with BCDedit result and source server Disks.

Below is error we seen in logs.

ot an error getting MNTAPI OS information

2017-03-03T07:05:15.200+01:00 error vmware-converter-worker[03708] [Originator@6876 sub=task-12] [BaseDiskSetComputer::AnalyzeErrorAndThrow] Error occurred when opening disk set, MNTAPI_ERROR = 176 MNTAPI errorType = 0, errorCode = 11

2017-03-03T07:05:15.200+01:00 warning vmware-converter-worker[03708] [Originator@6876 sub=task-12] [PopulateDetailedOsInfo] Failed to get MNTAPI OS version information

Any help would be much appreciated

We have production machines that run three shifts seven days a week.  Up until now we have had the forcibly disconnect setting set so that they never disconnect.  After upgrading to Horizon 6 they now disconnect approx. every 20 hours even when set to Never in Global Settings.  Is there a work around that anyone here is aware of?

FYI, Blue Medora has made publicly available 4 distinct vROps environments that are online and available for anyone who might find it useful to connect them.  Details, including scenarios highlighted in each, are available below.  If you have questions regarding access or the content of these demos, please reach out to demosupport@bluemedora.com.

Demo Environment 1 Live Link

Resource Kinds: vSphere | Oracle Database | NetApp Storage | Cisco UCS | Cisco Nexus

vROps Version: 6.3

User Login / Password Info can be found here

Scenarios found in this environment:

1. Use a Single Tool for Database and Infrastructure Monitoring
2. Plan for Storage Capacity Growth with Projects
3. Monitor Your Entire Stack, from Database to Disk

Demo Environment 2 Live Link

Resource Kinds: vSphere | MySQL Adapter | MongoDB | EMC VNX Block | Dell EMC PowerEdge | Cisco Networking

vROps Version: 6.3

User Login / Password Info can be found here

Scenarios found in this environment:

1. Gain Deeper Insight into Network Performance
2. Monitor Infrastructure During Migration
3. Understand Storage Cache Monitoring for SAN Efficiency

Demo Environment 3 Live Link

Resource Kinds: vSphere | NetApp E-Series | Microsoft SQL Server | F5 BIG-IP | Dell EMC PowerEdge | Citrix XenDesktop | Cisco Networking

vROPs Version: 6.4

User Login / Password Info can be found here

Scenarios found in this environment:

1. Monitor Workload Utilization Across Key Components of the Citrix VDI Stack
2. Understand Average Login Performance
3. See Stress on the VDI Environment to Prevent User “Boot-Storms”

Demo Environment 4 Live Link

Resource Kinds: vSphere | PostgreSQL | Oracle DB | MSSQL | NetApp | Cisco UCS | Cisco Networking | Amazon Web Services | Amazon RDS | Amazon Aurora

vROps Version: 6.5

User Login / Password Info can be found here

Scenarios found in this environment:

1. Use a Single Tool to Monitor All Database Workloads
2. See Performance Across your MySQL Workloads, On-Premises and Cloud
3. Understand the Health of Your Infrastructure, No Matter its Location

After applied Windows Update (KB4012212) in Windows Server 2008 R2 x64 with the vCenter, the vSphere client does not connects to vCenter (localhost) with error message:

"An unknown connection error occurred. (The request failed due to an SSL error. (The request was aborted: Could not create SSL/TLS secure channel.))"

Any vSphere and web client from machines with the Windows Updates to fix SMBv1 vulnerability cannot connect to vCenter 5.1.0 (for e.g. build-880146).

The Web client is still working, but only in localhost.

dear all

Hi

i have added a vcenter to my log insight but now want add other vcenter to log insight but there is no option for do this i have attached pic from log insight

now how can add other to log insight ??

BR

According to this docdisk.totalReadLatency.average should be available for VMs but when I try it it tells me it does not exist:

Get-Stat -Entity 'MyVM' -Stat 'disk.totalReadLatency.average'                                                                                                              

Get-Stat : 3/9/2016 6:02:05 PM    Get-Stat        The metric counter "disk.totalreadlatency.average" doesn't exist for entity "MyVM".                                          

At line:1 char:1                                                                                                                                                                   

+ Get-Stat -Entity 'MyVM' -Stat 'disk.totalReadLatency.average'                                                                                                                

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                                                                                

    + CategoryInfo          : ResourceUnavailable: (disk.totalreadlatency.average:String) [Get-Stat], VimException                                                                 

    + FullyQualifiedErrorId : Client20_RuntimeDataServiceImpl_CheckUserMetrics_MetricDoesntExist,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetViStats

However this metric does exist for my ESXi host though.

I have a cross vCenter NSX 6.2.4 implementation using SRM 6.1, the issue I am having is the full name of the virtualwire in each vCenter is different (see below) the difference is the MoRef of the vDS.

in all examples I can find on-line, the full name of the virtual wire is identical, including the MoRef of the vDS.

So SRM is not automapping the networks as  it looks to match the whole vDS port-group name, not just the universal logical switch portion, I don't really want to have to map these networks manually as it should work fine with automapping.

Using storage policy protection groups,

Site 1, vCenter 1

vxw-dvs-102-universalwire-47-sid-900012-colin-test

Site 2, vCenter 2

vxw-dvs-63-universalwire-47-sid-900012-colin-test

vxw                                 -> VXLAN-VirtualWire to distinguish the port-group that it was created by NSX

dvs-22                           -> MoRef* of the vDS (check in mob: https://<vcenter>/mob/ )

universalwire-47           -> universal vwire id within NSX

sid-900012                   -> segment id what this wire is using (VXLAN VNI)

colin-test                      -> name of the logical switch

*A Managed Object Reference ID also known just as MoRef ID

Anyone seen this before?

I was able to do that when I used Microsoft vCenter, but I just installed VCSA and can't, see below details:

1. VCSA has domain name vcsa.rt.local (AD is rt.local), and VCSA joined AD domain successfully.

Verify: administration->system administration->nodes->vcsa.rt.local (node name)->Active Directory, "Join" grayed out "Leave" is active

2. SSO user and Identity source added successfully

Verify: Administration->SSO->Configuration, "rt.local" added as AD, ->Users and groups, we can see all the AD users from rt.local drop-down rt.local menu.

3. Assign permission successfully

Verify: Global Inventory list->Vcenter server->vcsa.rt.local(server name)->permissions, AD users (RT\nsxadmin) are add to here and gave Administrator Role

Based on document/my MS vcenter experience, I should be able to  nsxadmin@rt.local to log in, but I can't!

Any Idea?

We are running about 900  desktops over VDI, some times ( +/- each 6 months) we need to do a refresh because of a storage capability issue, first time we did the "refresh" and, we caused a problem, everybody were calling Service Desk TI Department for help, the reason, all locally installed printers disappear.

i would like to know if there is, at least a workaround for this issue, thanks.

if there is a solution, better.

What are the minimum requirements for vsphere 6.5 SQL db server and will 5 cal's be enough?

We have a vSphere 6.5 server, with 6 1gb ports and we want all the ports live and allow for the biggest data pipe. How do I ensure that all 6 are active and provide a theoretical 6Gb bandwidth?

New OS

Windows Server 2008 R2 Standard SP1 x64

Dot Net 3.5 feature installed

VCenter Server 6.5  (6.5.0-5318154)

2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: ParseStatusFile: STATUS: 6%: "Starting VMware Identity Management Service..."

2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: ParseStatusFile: Calling callback with 3 -> 6 "Starting VMware Identity Management Service..."

2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: Entering function: UpdatePkgMgrProgressFromStatusFile

2017-05-03 11:22:50.411-04:00| vcsInstUtil-5318154| I: ProcessMsiMsg: ACTIONDATA reporting "Starting VMware Identity Management Service..."

2017-05-03 11:22:50.473-04:00| vcsInstUtil-5318154| I: Leaving function: UpdatePkgMgrProgressFromStatusFile

2017-05-03 11:22:50.473-04:00| vcsInstUtil-5318154| I: Leaving function: ParseStatusFile

2017-05-03 11:22:53.051-04:00| vcsInstUtil-5318154| I: Entering function: ParseStatusFile

2017-05-03 11:22:53.051-04:00| vcsInstUtil-5318154| I: ParseStatusFile: curr error msg: "Encountered an internal error.

Traceback (most recent call last):

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 2024, in main

    vmidentityFB.boot()

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 348, in boot

    self.configureIdentityManager(self.__idmRetryCount, self.__idmRetryInterval)

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 532, in configureIdentityManager

    self.startIDMService()

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 1257, in startIDMService

    returnCode = self.startService(self.__idm_servicename,self.__idmRetryCount * self.__idmRetryInterval)

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 88, in startService

    return service_start(svc_name, wait_time)

  File "C:\Program Files\VMware\vCenter Server\python-modules\cis\utils.py", line 784, in service_start

    raise ServiceStartException(svc_name)

ServiceStartException: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "VMwareIdentityMgmtService"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'VMwareIdentityMgmtService'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

"

2017-05-03 11:22:53.051-04:00| vcsInstUtil-5318154| E: ParseStatusFile: Displaying error message for "VMware vCenter Server": "Encountered an internal error.

Traceback (most recent call last):

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 2024, in main

    vmidentityFB.boot()

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 348, in boot

    self.configureIdentityManager(self.__idmRetryCount, self.__idmRetryInterval)

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 532, in configureIdentityManager

    self.startIDMService()

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 1257, in startIDMService

    returnCode = self.startService(self.__idm_servicename,self.__idmRetryCount * self.__idmRetryInterval)

  File "C:\Program Files\VMware\vCenter Server\firstboot\vmidentity-firstboot.py", line 88, in startService

    return service_start(svc_name, wait_time)

  File "C:\Program Files\VMware\vCenter Server\python-modules\cis\utils.py", line 784, in service_start

    raise ServiceStartException(svc_name)

ServiceStartException: {

    "resolution": null,

    "detail": [

        {

            "args": [

                "VMwareIdentityMgmtService"

            ],

            "id": "install.ciscommon.service.failstart",

            "localized": "An error occurred while starting service 'VMwareIdentityMgmtService'",

            "translatable": "An error occurred while starting service '%(0)s'"

        }

    ],

    "componentKey": null,

    "problemId": null

}

This is an unrecoverable error, please retry install. If you run into this error again, please collect a support bundle and open a support request."

Hi all,

I want to share my experience so others don't fall into the same trap as me. I recently purchased a DL360 gen9 and updated the firmware using SPP 2016.04.0. This updated the firmware BIOS to v2.30 - so all good. I decided to move our RMS VM to the new host. After few days of running, i get the purple screen of death with the error message " cpu / world tried to re-acquire lock". I googled the error message and it appears to an issue with the ilo driver.

Opened a ticket with HPE and they suggested i update to the latest SPP 2017.04.0 - BIOS firmware updated 2.40 - so all good. Again, after a few days later the RMS VM crashes and i get the purple screen of death. Note:  VM is powered off and ESXi is offline. iLO still works. So each time it crashes i had to access the ilo and do a reset of the host. Not a good practice in my eyes.

Open a second ticket with HPE, this time the supported said " SPP 2017.04.0 update won't fix the issue with purple screen of death" - i was like....Grrrrrr. The SPP 2017.04.0 update doesn't update ilo driver.

These are the instructions to permanently fix and update iLO driver.

1. 1. Download ESXI offline bundle

http://vibsdepot.hpe.com/hpe/jan2017/esxi-650-bundles/

         Download Select the 2nd file  hpe-esxi6.5uX-bundle-2.6.2-2.zip 

1. 9.8M size

1. Power off any virtual machines that are running on the host and place the host into maintenance mode.
2. Enable SSH on the ESXi host
3. Use filezilla app and FTP the bundle zip file to the ESXi host. Make sure to transfer the bundle to the following directory /var/log of the host
4. SSH into ESXIi host
5. Install from ESXi host, with offline bundle on ESXi host:
   
   

software vib install -d /var/log/hpe-esxi6.5uX-bundle-2.6.2-2.zip

Install takes approx. 4-5min

6.  Reboot ESXi host from vSphere web client

7. Verify that the vibs on the bundle are installed on your ESXi host

esxcli software vib list

1. 1. The update of the hp-ilo driver should be 650.10.0.2-2 or later ( as you can see the ilo-driver is updated )
2. 2. Exit maintenance mode of the ESXI

VMware and HPE AAdvisory

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2148123


http://h20565.www2.hpe.com/hpsc/doc/public/display?docId=c05378386

Hi All,

Iam not able to download the below said patch, I need to patch for my project server ASAP, please let me know any issue on ESXi 6.0 Express Patch 7c

Note : ESXi 6.0 Express Patch 7a is available

Regards,

Venkat