Hi Rajeev Thanks for the input. I can confirm that none of my passwords have a single quote mark in them so I don't think this is relevant, thanks anyway!
I have a separate PSC and VCSA at version 6.5 U2. I have upgraded both to version 6.7 U2 from the ISO and am now trying to converge to one VM. I have mounted the VCSA ISO on the VCSA 6.7 VM as ...
See more...
I have a separate PSC and VCSA at version 6.5 U2. I have upgraded both to version 6.7 U2 from the ISO and am now trying to converge to one VM. I have mounted the VCSA ISO on the VCSA 6.7 VM as I don't have internet access from these machines. The converge process is started succesfully from the GUI but then fails. looking at the converge.log on the VCSA I see the first error is 'ERROR converge Unable to run ldapsearch' then it later says 'ERROR converge Failed to run white listed firstboot scripts' I have checked the converge_status.json file and it indicates firstboot stage 1 of 4 failed. All DNS is working correctly and I am unsure what to check next with this. It is a lab environment so I can try things out without affecting any prod systems. Any suggestions on how to resolve this? Thanks Chris
I am trying to get vCenter alarms to trigger upon certian events on a cluster made of Dell PowerEdge R730xd servers. We did a cable pull test on Friday and no alerts were raised for a PSU being ...
See more...
I am trying to get vCenter alarms to trigger upon certian events on a cluster made of Dell PowerEdge R730xd servers. We did a cable pull test on Friday and no alerts were raised for a PSU being down. When browsing the hardware status system event log I can see the Assert+ Power Supply Power Supply AC lost event, and I can also see this on the iDRAC but it is not alerting about this in vCenter. I have seen that the DELL customized ESXi image no longer includes any CIM extensions so I tried installing the OMSA VIB but this didn't seem to make any differnece. How can I get vCenter to see these errors? WE are using ESXi 6.0 U2
Running latest vCenter server and have deployed as an external PSC and 2 vCenter Servers. I have used the certificate manager to generate a new machine SSL and solution user CSRs for the PSC. T...
See more...
Running latest vCenter server and have deployed as an external PSC and 2 vCenter Servers. I have used the certificate manager to generate a new machine SSL and solution user CSRs for the PSC. These have been submitted to our internal CA and I have managed to install the machine SSL certificate so I am no longer getting a cert error when going to https://<machine FQDN>/psc. I have also tried to replace the solution user certificates but this doesn't seem to be working. I ensured the CSRs had different names (pscname-machine and pscname-webclient) and I can see this has been set succesfully within the certificates. The Certificate manager appears to replace the certificates but when browsing to https://<machine FQDN>:5480 it is still using the default certificate. I have also tried replacing the certificates through the web gui and although they appear to be updated the https://<machine FQDN>:5480 is still using the default cert. I have restarted the PSC and when logging in I can see that the solutoin user certificates it is using are the correct ones, but I am still getting the certificate error on logging in to https://<machine FQDN>:5480. How can I get this certificate to replace?
I am trying to install vCenter 6 with an external PSC and the database on a SQL 2014 cluster. The DSN has been set up correctly and testing passes ok. When running the installer it errors when ...
See more...
I am trying to install vCenter 6 with an external PSC and the database on a SQL 2014 cluster. The DSN has been set up correctly and testing passes ok. When running the installer it errors when trying to start the inventory service. Looking at the logs details that it cannot establish an SSL connection with the SQL server. I have found that this error can occur if an alias for the DB server is used to create the DSN so we have tried with the IP address but it is still not working. Trying to connect directly to the node hosting the SQL cluster role does not work. How can I get this to install?
I have had to do this a few times so will try to document the process I followed. If you have numerous datastores then make a note of which datastore the machine sits in. The next step is to un...
See more...
I have had to do this a few times so will try to document the process I followed. If you have numerous datastores then make a note of which datastore the machine sits in. The next step is to unregister the VM from vCenter / ESXi Then you need to enable SSH on your ESXi host Use Putty or something similar to connect to the ESXi host Run the following commands (in italics) cd /vmfs/volumes/<datastore name> ie if the datastore containing the VM is named datastore1 then you would run cd /vmfs/volumes/datastore1 Next run ls to check that the VM folder is there Rename the folder using mv <oldVMFoldername> <newVMFoldername> Change into the folder with cd <NewVMFoldername> Rename the nvram, vmsd, vmx and <VMname-xxxx.hlog> files by running mv again ie mv oldname.nvram newname.nvram mv oldname.vmsd newname.vmsd mv oldname.vmx newname.vmx mv oldname-1234.hlog newname-1234.hlog Rename the vmdk file with vmkfstools -E oldname.vmdk newname.vmdk Edit the vmx file with vi newname.vmx Change the references from oldname to newname within this file Register the VM with the ESXi server and it should power on ok This link gives more detail and other methods VMware KB: Renaming a virtual machine and its files in VMware ESXi and ESX
I don't think you will be able to change the names whilst the VM is running as the files will be in use. If you want to rename the VM files you will need to use vmkfstools to rename the disk fil...
See more...
I don't think you will be able to change the names whilst the VM is running as the files will be in use. If you want to rename the VM files you will need to use vmkfstools to rename the disk files and will need to modify the relevant files within the vmx file If you are just renaming the folder that contains the VM I think you will just need to unregister the VM, rename the folder then re-register
Hi thiruvas You will be able to enable EVC, however it will not be easy as you have 2 different baseline hosts in the cluster. The easiest way would be to create a new cluster, enable EVC and...
See more...
Hi thiruvas You will be able to enable EVC, however it will not be easy as you have 2 different baseline hosts in the cluster. The easiest way would be to create a new cluster, enable EVC and set it to Westmere generation, then move your existing hosts into the new cluster. EVC basically 'hides' the instructions of newer processors that are not available on the baseline processor that you select. If you have enough headroom you could remove the 3 Sandybridge processors from your current cluster, enable EVC which will then be set to Westmere and then add the 3 sandybridge hosts back into the cluster Also have a look here Enable EVC without downtime
You can create any number of Virtual NICs on the ESXi Server, on the pfsense box you can just add another vNIC and have it connected to your new vSwitch that would be for internal traffic with no...
See more...
You can create any number of Virtual NICs on the ESXi Server, on the pfsense box you can just add another vNIC and have it connected to your new vSwitch that would be for internal traffic with no physical NICs attached. Basically you will have an external vSwitch that is connected to the Physical NIC and the external vNIC of the pfsense would connect to that, then there will be another vSwitch for internal traffic that will contain the other vNIC from the pfsense and all your VMs will connect to this.
This may help with configuring, it is for VMware Workstation but you can use the same instructions for ESXi Home Lab with pfSense & VMware Workstation | OutsideSys
OK, it looks like your ESXi Server has a public IP address. You will need some kind of networking device to perform NAT if you want to use a private IP address internally on your server, maybe l...
See more...
OK, it looks like your ESXi Server has a public IP address. You will need some kind of networking device to perform NAT if you want to use a private IP address internally on your server, maybe look into pfsense. You can then configure this to supply DHCP addreses to your client machines. What you will need to do is connect your pfsense public interface to the vswitch connected to the physical NIC that is connected to the public network, and create another vSwitch for your private traffic, and connect the pfsense private interface to this vswitch. I'm afraid I don't know pfsense but can try to help
You will also need to set a valid IP address, Subnet Mask, Default Gateway and DNS Servers on the NIC within Windows unless you have a DHCP server that can provide these settings
I have a vCenter on one network, and the ESXi hosts I want to manage are on another network, these are separated by a firewall and I have port 902 opened on the firewall. I'm unable to connect m...
See more...
I have a vCenter on one network, and the ESXi hosts I want to manage are on another network, these are separated by a firewall and I have port 902 opened on the firewall. I'm unable to connect my vCenter to the ESXi hosts but I thought that this was the only port I needed to open - is anyone able to give me a definitive list of which ports need to be open for the communication to work please? I am having trouble interpreting the list here VMware KB: Required ports for vCenter Server Appliance 5.x It is the vCenter appliance that I am using Thanks
We have an install of vCenter 5.1 on a Windows 2012 R2 server which is a VM. If IPv6 is enabled on the NIC then access and tasks within vCenter are slow, if IPv6 is disabled then access and all ...
See more...
We have an install of vCenter 5.1 on a Windows 2012 R2 server which is a VM. If IPv6 is enabled on the NIC then access and tasks within vCenter are slow, if IPv6 is disabled then access and all tasks run fine. We need to have IPv6 enabled for support from MS so disabling is not an option. the reason we are using vCenter 5.1 is we are trialling DaaS which will not install on a 5.5 as of yet
