Matt_B1's Posts

Really excited to use the script. Can someone post v2.1? The short URL in the original post doesn't work for me and the long URL LucD shared points to v2.0. I have tried the short URL with both m... See more...
Really excited to use the script. Can someone post v2.1? The short URL in the original post doesn't work for me and the long URL LucD shared points to v2.0. I have tried the short URL with both my corporate and home systems. I also checked the Nuvoli blog and didn't see it.
This sounds more like the issue I am having. My main issue is that we cable the 10GB ports only which are vmnic4 and vmnic5. Where is menu.cfg located? I tried adding it to my boot.cfg file of... See more...
This sounds more like the issue I am having. My main issue is that we cable the 10GB ports only which are vmnic4 and vmnic5. Where is menu.cfg located? I tried adding it to my boot.cfg file of the ESXi image but that resulted in the ESXi install not even loading. kernelopt=ks=http://<kickstart server>/esxi6.0/ks.cfg netdevice=vmnic4 The error was "No NIC found with name "vmnic4". I went into the console of the ESXi server and verified vmnic4 is one of the 6 NICs listed. Without the vmnic4 line, everything works up into when it tries to get an IP and then load the kickstart file.
Through each vCO upgrade, some workflows are left with a ? under Users/Groups to indicate a former permission.  How can I remove those?  When I select them, the option to remove it grayed out.  I... See more...
Through each vCO upgrade, some workflows are left with a ? under Users/Groups to indicate a former permission.  How can I remove those?  When I select them, the option to remove it grayed out.  I have logged in as adminstrator@vsphere.local and an administrative AD account that I set and run into this issue.  For these workflows, I can edit access rights and add whatever I need but it still doesn't allow me to edit or delete the workflows.  I also have this challenge at the root (administrator@<vCO name>) in the workflows view.  Anyone fixed this?
VMware support was able to figure this out.  For some reason, not all the workflows were available even though I deployed a new 6.0.3 appliance and imported the config from my previous 5.5 instan... See more...
VMware support was able to figure this out.  For some reason, not all the workflows were available even though I deployed a new 6.0.3 appliance and imported the config from my previous 5.5 instance.  So, we went into the Orchestrator Configuration webpage->Troubleshooting and clicked "Reset Current Version" for plug-ins.  Bounced it and the missing workflows were there.  Then, went back into Orchestrator Configuration webpage->vSphere Configuration under General and input the IP of our vCenter PSC and used administrator@vsphere.local.  The look up data worked, I checked most of the boxes, and was able to see vCenter in vCO afterwards.
I had a self-service portal running off vCO 5.5 that a bunch of users use.  I deployed a vCO 6.0.3 appliance VM and imported the config.  I finished the configuration and all radio buttons are gr... See more...
I had a self-service portal running off vCO 5.5 that a bunch of users use.  I deployed a vCO 6.0.3 appliance VM and imported the config.  I finished the configuration and all radio buttons are green in the port 8283 Configuration site.  When trying to add vCenter using the "Add a vCenter server instance" workflow, it fails immediately at the "Import a certificate" workflow with "ReferenceError: "CertificateChainValidator" is not defined."  I have imported the SSL cert of the vCenter and of the PSC under Network->SSL Trust Manager.   All certs are self-signed since SRM 6.0 would not work with CA signed certs on vCenter at the time we deployed SRM.  I have not touched the certs on vCO 6.0.3...trying to take the path of least resistance to keep vCenter and SRM running and get vCO back online.  I checked vCenter MOB and there are no vCO extensions.  How do I get vCO 6.0.3 properly registered with vCenter?  My vCenter is a VCSA and 6.0 build 2656761.
I plan to open a support ticket but want to make these errors visible to all.  For the errors, I have replaced names but left the important content.  We had several issues with ESXi v6.0, vCenter... See more...
I plan to open a support ticket but want to make these errors visible to all.  For the errors, I have replaced names but left the important content.  We had several issues with ESXi v6.0, vCenter 6.0, and SRM 6.0.  I recommend hold off on v6.0 products until VMware releases a U1 patch. #1 Permission related blocked SRM views and certain functions not executing When using SRM as any other user aside from administrator@vsphere.local, you run into permission related blocked views and certain functions not even initiating.  If you click around, you can sometimes get the view to populate.  In some situations, it is impossible to execute a recovery.  I have tried using AD accounts that are nested in groups with Administrator permission and even not nested.   If I log in as administrator@vsphere.local, there are no issues. #2 "Cannot unmount volume 'Datastore Name: datastore1 VMFS uuid: <id>' because file system is busy. Correct the problem and retry the operation." SRM fails to unmount the datastore from the protected site across all ESXi hosts.  The behavior is inconsistent in regards to which host it can't unmount from.  If I immediately rerun the recovery without making any changes, it will complete without issue.  I can also manually unmount the datastore without issue. #3 Recovered datastore 'datastore1' is not accessible to host 'host1'. Warns about the datastore not being acccessible on the recovery site during the recovery.   When I check the recovery cluster, the datastore is visible on all hosts.  I can simply rerun the recovery without any changes and it will work properly.
On 2 of my 5 VCSA 6.0 appliances, SNMP polls are not working.  VCSA is 6.0 build 2656761 on all.  The non-working ones are using an external PSC (another VCSA) which appears to be the only differ... See more...
On 2 of my 5 VCSA 6.0 appliances, SNMP polls are not working.  VCSA is 6.0 build 2656761 on all.  The non-working ones are using an external PSC (another VCSA) which appears to be the only difference.  Commands I used... *Community string replaced for this post Command> snmp.set --communities myCommunityString Command> snmp.enable When I use the Windows tool MIB walk with myCommunityString, it fails the test immediately.  It works fine on my other 3 VCSAs.  I have logged into the shell and verified snmpd service is running. Anyone know what is incorrect?
I have attached a zip of the recent vmware log files.  I did replace a few names with generic names but the log contents are there.
Has anyone else noticed this?  With all variables held identical, a v11 VM will have dramatically slower transfer times than a v10 VM.  Here are some details from our testing: - On a v11 guest, ... See more...
Has anyone else noticed this?  With all variables held identical, a v11 VM will have dramatically slower transfer times than a v10 VM.  Here are some details from our testing: - On a v11 guest, UNC to a Netapp share is a little slow to respond. Grab a 300MB file from the Netapp share and drag it to the desktop of the guest. The transfer popup would show little or no activity for a few minutes. Most times it would throw an error. Other times, it would transfer at 2-3mb/s. - Do the exact same activity on a guest on the same subnet and the transfer was almost instant. We were able to move that 300mb file from the v10 guest to the v11 guest with reasonable speed. Not almost instant like we would expect, but it would finish. - We ran the same tests with 4G ISOs and v10 guest were 240mb/s+ while the v11 would not even copy. - We tried between different ESXi hosts and within the same host with same results.
Yes, I always used the FQDN.  This issue was actually the result of having an incorrect vCenter topology.  The error resulted in us spending hours with support all around valid or self-signed cer... See more...
Yes, I always used the FQDN.  This issue was actually the result of having an incorrect vCenter topology.  The error resulted in us spending hours with support all around valid or self-signed certs.  In the end, I had to completely redeploy new VCSA 6.0 appliances and follow the 3rd recommend topology. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2108548 With this setup, it also links the vCenters and it seems to be much quicker than Linked Mode in previous versions.  I was able to pair the sites in SRM without issue.  FYI, I am using self-signed certs all around at the moment.  SRM is very finicky about trust with SSL certs so I won't try implementing valid SSL certs until I get some working failovers.
SRM 6.0 is a brand new install after the vCenters were online.  I accepted the certificate when I entered the vCenter info.
Both are new VCSA 6.0 installs.  During the VCSA 6.0 install, I did not change, modify, or do anything with SSL certs.
I have used the default self-signed certificates throughout the vCenter and SRM setup.  When going to pair the vCenters, I get "Server certificate chain not verified".  These are 2 new VCSA 6.0 V... See more...
I have used the default self-signed certificates throughout the vCenter and SRM setup.  When going to pair the vCenters, I get "Server certificate chain not verified".  These are 2 new VCSA 6.0 VMs (embedded PSCs for each) and 2 new Windows 2012 R2 servers to run SRM 6.0.  I can view the Site in each respective vCenter but can't pair them.  Does anyone have suggestions?  We have tried valid SSL certs before on our original 6.0 deployment and continuously run into these certificate chain not valid errors.
After various restarts, reinstalls, unregistering the SRM extension, and other testing, I was able to eventually see Site Recovery in the web client.  Unfortunately, I am not clear which exact ch... See more...
After various restarts, reinstalls, unregistering the SRM extension, and other testing, I was able to eventually see Site Recovery in the web client.  Unfortunately, I am not clear which exact change fixed the issue.
I have installed SRM 6.0 successfully.  However, I can't see the Site Recovery link in the left frame of the web client.  I can see the plug-in listed in the desktop client and I can see it as "c... See more...
I have installed SRM 6.0 successfully.  However, I can't see the Site Recovery link in the left frame of the web client.  I can see the plug-in listed in the desktop client and I can see it as "com.vmware.vcDr" in the MOB.  I don't have any 3rd party extensions listed that may interfere.  vCenter is VCSA 6.0, upgraded from a VCSA 5.5 appliance.  I have logged in with administrator@vsphere.local, my admin account, and the service account used during SRM install and no accounts can see "Site Recovery". The VMware Site Recovery Manager 5.8.x plugin is not visible in the vSphere Web Client when some third party Web Client plugins are installed (2110188) http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2110188
I have the same error on a Windows 2008 R2 box.  ODBC connection is fine with local SQL credentials.  There is no trailing white space in the name.  There is only one IP on our IPv4 configured NI... See more...
I have the same error on a Windows 2008 R2 box.  ODBC connection is fine with local SQL credentials.  There is no trailing white space in the name.  There is only one IP on our IPv4 configured NIC.  Forward and reverse DNS lookups are fine.  We are consistently getting this error.  For background, I was doing an upgrade from 5.5 to 6.0 and it hung on Installing VCSServiceManager and Starting VMware vCenter for 2 hours.  Tech support ended up killing the process and we are now doing an install (connecting to external DB, create new SSO domain).  Through every combination of launching as the service account, run as Admin, using local system...they all hit the 1603 error with VCSServiceManager.   What else have people done to get by this error?
I also have this issue but we carefully upgraded SSO, then Web Client, then Inventory Service, then vCenter without issue.  Is there a way to verify the service versions are in alignment?  I can ... See more...
I also have this issue but we carefully upgraded SSO, then Web Client, then Inventory Service, then vCenter without issue.  Is there a way to verify the service versions are in alignment?  I can see the SRM v5.8 extension in the thick client but can't enable it since it says "no client side download is needed".  I assume this is because SRM v5.8 is only valid in the web client. Edited: I found this KB.  My Inventory Service version is 5.5.0.1381 (5.5U2c?) and my SSO version is 5.5.0.43769 (matches 5.5U2d).  Unless someone suggests otherwise, I am going to upgrade to 5.5U2e that was just released in hopes that running through all the components again fixes the issue. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2057466
Took forever to finally find this fix.  We upgraded from ESXi 4.1 to 5.5 using the HP ISO through VUM.  This was done on HP DL360 G7s.  By following this KB to regenerate the certs, I could final... See more...
Took forever to finally find this fix.  We upgraded from ESXi 4.1 to 5.5 using the HP ISO through VUM.  This was done on HP DL360 G7s.  By following this KB to regenerate the certs, I could finally get the host reconnected in vCenter. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2076665
Any update on this?  We now have HP Gen9 (Generation 9) blades and I would love to get my PXE build setup working for these UEFI based blades.  I found this example but it doesn't have an ESXi en... See more...
Any update on this?  We now have HP Gen9 (Generation 9) blades and I would love to get my PXE build setup working for these UEFI based blades.  I found this example but it doesn't have an ESXi entry as an example. HP Blogs - Learn how to modify a Linux based PXE server to su... - The HP Blog Hub
A couple things worked for us in fixing the issue with vnetflt.sys: For non-ESXi v5.5 VMs, uninstalling VMware tools, reinstalling but using custom option and deselecting the vShield drivers. ... See more...
A couple things worked for us in fixing the issue with vnetflt.sys: For non-ESXi v5.5 VMs, uninstalling VMware tools, reinstalling but using custom option and deselecting the vShield drivers. For ESXi v5.5 VMs, upgrading the VM to virtual hardware version 10.