Hi Team,
I am looking for script to collect "Triggered Alarms" from 4 VC's in a single report. We are using ESXi 4.1 Ver in all VC's.
Is it possible to collect all Triggered Alarms from 4 VC's in a sigle report and automatically through mail with Excel report.
Thank You,
Regards,
Srinivasu
Hi Guys,
I have a VM with guest Windows server 2008R2 on ESXi 5.5. I am using a Netbackup to backup these VMs. while running the backup for this VM, the backup fails and when i check in the vCenter Server, the below error observed.
An error occurred while taking a snapshot: msg.snapshot.error-QUIESCINGERROR.
An error occurred while saving the snapshot: msg.snapshot.error-QUIESCINGERROR.
Please assist at the earliest.
regards
VK
We recently updated our vSphere Server 5.5 to 6.0 and the NetApp VSC Plugin from 5.0 to 6.0.
Now the Plugin won't show up in the WebClient as it did before the upgrade.
Has anyone the same issue? Is there a solution for it?
The backup jobs defined before the upgrade are running.
Thanks
I am attempting to access vSphere API method CreateVvolDatastore in list of Managed Object "HostDatastoreSystem" methods.
New CreateVvolDatastore method should be available in HostDatastoreSystem since vSphere API 6.0:
However method CreateVvolDatastore not showing up as an option. Note latest vijava pom.xml dependency entry is version 5.1:
<dependency>
<groupId>com.vmware</groupId>
<artifactId>vijava</artifactId>
<version>5.1</version>
</dependency>
Can anyone please advise how to successfully find / interface with vSphere 6.0 API class HostDatastoreSystem, method CreateVvolDatastore() ?
Is there any vijava SDK jar available containing this new method?
Thanks,
Elaine
In this environment I am required to have vcenter with several nics. I have quite a few esx hosts working fine but I have two that I am having problems with.
vcenter is running windows 2008R2 on a MSSQL
Problem:
my vcenter ip addresses are 10.10.0.5 and 192.168.200.20
Host A need to connect to vcenter on 10.10.0.5
I join Host A and instead in vpxa.cfg and vpx.hosts table it lists the vcenter address as 192.168.200.20
Host B is on the 192.168.200.x subnet as 192.168.200.123
Host B tries to connect to vcenter on 10.10.0.5
192.168.200.x is NAT'd through 10.10.0.20
Host B connects to vcenter with a serverIP of 10.10.0.20 instead of 192.168.200.123 and while it stays connected you cannot clone or deploy templates to it.
Does anyone know why Vcenter would present the wrong IP address?
I am considering upgrading from 5.1 U2 (Vcenter) hosts are U3 to 5.5 U2. When I installed SSO in 5.1 I chose a multisite installation.
I was considering using Linked mode but have since decide not to. Can I change to a basic SSO install when doing an upgrade or will I need do a fresh install to accomplish this?
Hi,
I am putting together a VCenter 6 Design currently with two VCenters and two external PSCs (one in each datacentre) load balanced using F5 GSLB. The PSCs VMCA component will be a subordinate of my client's internal Microsoft PKI. SO my questions are:
1. Do any certificates issued by the VMCA get replicated between the PSC nodes? If we have a primary datacentre failure, can I be certain that any certificates are also stored in the second PSC VECS? DOes it actually matter if the certificate is already on the host?
2. Are certificates checked against a CRL for revocation? Does the VMCA perform the CRL checking or is this done by the PKI?
3. What order does the install and certificate configuration happen? I am assuming;
Install PSC1
Configure PSC1 to be a subordinate of PKI
Install PSC2
Configure PSC2 to be a subordinate of PKI also
Configure Load balancing
Install VCenters using GSLB of PSCs.
Thanks all in advance
DNS server maps host name 192.168.1.206 to address(es) ; <<>> DiG 9.9.2-P2 <<>> 192.168.1.206 +short,;; global options: +cmd,;; connection timed out; no servers could be reached which seems to be not local ip address.
Please either update appliance /etc/hosts file to properly access DNS servers or update appliance DNS servers with the proper host name mapping. To check if DNS has record about local host name, please execute `dig 192.168.1.206 +short` locally on the appliance.
The windows host and VCSA 5.5 is in same port group.
No geteway,DNS,Firewall.
I can log into the VCSA on the windows host.
I am testing vSphere 5.5 in our lab and I am experiencing some issues with vCenter Server or SSO. After a fresh install all works about fine, I can add AD authentication to SSO and AD login works to vSphere Client. I was having issues with vCenter Orchestator login so I rebooted vCenter Server VM. After a Windows reboot vCenter Server is no longer starting, it tries to start but SSO fails and vCenter Server process shuts down. Below is a snippet from vpxd.log with relevant output.
Domain Controller is Windows Server 2012.
vCenter Server and SSO is on Windows Server 2008 R2.
2013-09-28T12:49:09.679+03:00 [04988 info 'dbdbPortgroup'] [VpxdInvtDVPortGroup::PreLoadDvpgConfig] loaded [0] dvpg config objects
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] Solution user set to: vCenterServer_2013.09.26_125138
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] VC's ServiceId in LookupService: Default-First-Site:b0f86720-9fa6-42b5-aaf4-26d700d6152a
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] STS URI set to: https://vCenter.vclass.local:7444/sts/STSService/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] Admin URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] Groupcheck URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][SsoFactory_CreateFacade]'] VC SSL certificate location: C:\ProgramData\VMware\VMware VirtualCenter\ssl\rui.crt
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][CreateSsoFacade]'] [CreateUserDirectory] STS URI set to: https://vCenter.vclass.local:7444/sts/STSService/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][CreateSsoFacade]'] [CreateUserDirectory] Admin URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.685+03:00 [04988 info '[SSO][CreateSsoFacade]'] [CreateUserDirectory] Groupcheck URI set to: https://vCenter.vclass.local:7444/sso-adminserver/sdk/vsphere.local
2013-09-28T12:49:09.737+03:00 [04988 warning 'Default'] Closing Response processing in unexpected state: 3
2013-09-28T12:49:09.740+03:00 [04988 error '[SSO][SsoFactory_CreateFacade]'] Unable to create SSO facade: Invalid response code: 404 Not Found.
2013-09-28T12:49:09.741+03:00 [04988 error 'vpxdvpxdMain'] [Vpxd::ServerApp::Init] Init failed: Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)
--> Backtrace:
--> backtrace[00] rip 000000018018cd7a
--> backtrace[01] rip 0000000180106c48
--> backtrace[02] rip 000000018010803e
--> backtrace[03] rip 00000001800907f8
--> backtrace[04] rip 00000000003f5bac
--> backtrace[05] rip 0000000000416722
--> backtrace[06] rip 000000014075dd5a
--> backtrace[07] rip 00000001407578bc
--> backtrace[08] rip 000000014098800b
--> backtrace[09] rip 000007feff17a82d
--> backtrace[10] rip 0000000076ef652d
--> backtrace[11] rip 000000007712c541
-->
2013-09-28T12:49:09.742+03:00 [04988 warning 'VpxProfiler'] ServerApp::Init [TotalTime] took 3520 ms
2013-09-28T12:49:09.742+03:00 [04988 error 'Default'] Failed to intialize VMware VirtualCenter. Shutting down...
Yes...I'm being paranoid! No, I can't find a concise answer anywhere.
We have VCenter 5.5, a distributed switch, 3 port groups, 5 datastores, SSO, ESXi 5.5 hosts, and of course many VM's.
What, if anything, will stop working if I physically shut off the vcenter server?
I'd like the answer to be "nothing", but if that's the answer then there would not really be a need for vcenter in the first place...
| The SSL protocol 3.0 design error, uses nondeterministic CBC padding, which makes it easier for man-in-the-middle attacks (POODLE) Additional information: (CVE-2014-3566) | An unauthorised user who can take a man-in-the-middle (MitM) position can exploit this vulnerability and gain access to encrypted communication between a client and server. | It is recommended to disable SSLv3 support to avoid this vulnerability. |
How can I check openssh version on ESXi machines?
I have got some issues with its versions
| Authenticated users can exploit this vulnerability to obtain usernames and other sensitive information. | It’s recommended to upgrade to OpenSSH 6.8 or later, available from the OpenSSH Web site - "http://www.openssh.com/". |
When selecting a VM to migrate the option to migrate is greyed out. In fact, Power On, Migrate, Revert to Current Snapshot are greyed out. I would like to migrate this VM to another host and datastore.
ESXi version 5.1.0 build 1021289
VMware vCenter Server, 5.1.0 build 947673
I've migrated 154 VMs and out of the 154 VMs migrated approximately a dozen VMs would not allow for live migrations(migrate... option greyed out). I could not identify any commonality between the dozen VMs that did not allow for live migrations.
I really need to migrate this VM in a live state if at all possible.
When vCenter checks to see if a VM is a valid candidate to migrate, what does it check for because the migrate option is NOT grey for about a second before it becomes greyed out?
After a recent upgrade to vCenter 5.5.0 update 2e, I am unable to use the web client to clone VMs. Each time i try to clone I get this error when the client is doing a compatibility check:
Error occurred while calculating compatibility: com.vmware.vim.vmomi.core.exception.MarshallException: com.ctc.wstx.exc.WstxIOException: Invalid white space character (0x1) in text to output (in xml 1.1, could output as a character entity)
Anyone seen this before? I have researched the forum and googled for this particular error but did not find anything about it.
Hi
I have 5 hosts, 3 hosts and the VCenter are in the same subnet and they are connected to VCenter. 2 of the hosts can't connect to the VCenter are on different subnet. It was working yesterday. Nothing was changed on the network. I already restart the Management Agents but still can't connect to the VCenter.
Thanks.
I have VCSA 6.0 installed but the VPXD does not initialize. Is there a specific log file that I can look at to determine why it is not initializing.
I've got couple of VMware docs, but my OS is windows 2012 server,any helpp is appreciated.
VMware KB: Installing vCenter Server does not complete with Windows Server 2008
environment :
windows 2012 R2
Esxi 5.5 update 2
Status log file.
==========
-----------------
Operation "Create standalone instance VMwareVCMSDS" failed:
Action: Create Standalone Instance
Action: Creation of standalone instance
Action: Create Instance
Problem: Creation of instance VMwareVCMSDS failed: The wizard could not access the registry.
Error code: 0x800706fd
The trust relationship between this workstation and the primary domain failed.
-----------------
Recovering from failed Operation "Create standalone instance VMwareVCMSDS"
-----------------
Recovery successful
-----------------
Execution error.
[2015-04-30 08:28:26,214 com.vmware.vim.jointool] Failed to find instance config at: "C:\ProgramData\VMware\VMware VirtualCenter\instance.cfg", assuming defaults
[2015-04-30 08:28:26,216 com.vmware.vim.jointool] Storage directory not found in instance.cfg.
[2015-04-30 08:28:26,436 com.vmware.vim.jointool] Initializing DB datasource from: vcdb with dsn: VMware vCenter as user:
[2015-04-30 08:28:26,467 com.vmware.vim.common.vdb.VdbConfig] Config name=vcdb
[2015-04-30 08:28:26,467 com.vmware.vim.common.vdb.VdbConfig] Property file=C:\ProgramData\VMware\VMware VirtualCenter\vcdb.properties
[2015-04-30 08:28:26,467 com.vmware.vim.common.vdb.VdbConfig] Loaded url from props=<not set>
[2015-04-30 08:28:26,468 com.vmware.vim.common.vdb.VdbConfig] Overrides=
[2015-04-30 08:28:26,468 com.vmware.vim.common.vdb.VdbConfig] prop:password
[2015-04-30 08:28:26,468 com.vmware.vim.common.vdb.VdbConfig] prop:dsn
[2015-04-30 08:28:26,468 com.vmware.vim.common.vdb.VdbConfig] prop:username
[2015-04-30 08:28:27,830 com.vmware.vim.jointool] DB datasource initialized.
[2015-04-30 08:28:27,830 com.vmware.vim.jointool] JoinTool started
[2015-04-30 08:28:27,831 com.vmware.vim.jointool] Storage directory for LDAP instance: C:\ProgramData\VMware\VMware VirtualCenter\\VMwareVCMSDS
[2015-04-30 08:28:27,832 com.vmware.vim.jointool] Operation Mode: initialize
[2015-04-30 08:28:27,851 com.vmware.vim.jointool] Creating directory services instance VMwareVCMSDS
[2015-04-30 08:28:27,851 com.vmware.vim.jointool] LDAP port = 389
[2015-04-30 08:28:27,851 com.vmware.vim.jointool] Base DN = dc=virtualcenter,dc=vmware,dc=int
[2015-04-30 08:28:27,851 com.vmware.vim.jointool] Storage dir = C:\ProgramData\VMware\VMware VirtualCenter\VMwareVCMSDS
[2015-04-30 08:28:28,658 com.vmware.vim.jointool] Operation "Create standalone instance VMwareVCMSDS" failed: : Action: Create Standalone Instance
Action: Creation of standalone instance
Action: Create Instance
Problem: Creation of instance VMwareVCMSDS failed: The wizard could not access the registry.
Error code: 0x800706fd
The trust relationship between this workstation and the primary domain failed.
[2015-04-30 08:28:28,659 com.vmware.vim.jointool] Recovering from failed Operation "Create standalone instance VMwareVCMSDS"
[2015-04-30 08:28:28,660 com.vmware.vim.jointool] Recovery successful
[2015-04-30 08:28:28,661 com.vmware.vim.jointool] Execution error.
Is the SYSLOG Collector in vSphere 6 discontinued?
Up to vSphere vCenter Server 5.5 there was an option under vSphere Support Tools to "Install vSphere Syslog Collector".
From the install screen of vSPhere 6 vCenter Server there is not an option to "Install vSphere Syslog Collector".
I know you can redirect the logs from ESXi hosts and vCenter Server to a Syslog host and I know there is a still a Syslog Service, but do you have to install a thrid party Syslog Server now and redirect the logs to that? The vSphere documentation is not very clear.
regards
I have vSphere 6.0 running in my lab as a trial right now and my evaluation is about to run out, before that happens i am going to test out building a SQL DB cluster for vCenter 6.0. I have built out MSFC's for previous versions of vCenter 5.1 and 5.5 and had very a lot of success with enhanced resiliency and it created a very stable environment and had maybe 5-7 seconds of vCenter not being able to write when the DB's fail over to the standby server, but vCenter was unaffected which is pretty impressive. Considering that vSphere 6.0 was just released not that long ago I wanted to get this out there and see if anyone had done this yet or had any good suggestions or reference's and if anything this could spark up a good discussion!
I will post up the results of the build and all the testing.
Thanks
Hi,
Today I've found out that for one of my templates some of the actions are grayed out. I can successfully deploy vm from this template, however I can't convert it to vm, nor rename it, nor remove it from inventory, nor delete it from disk. There are no on-going actions for this template currently. How can I find out why those actions are grayed out (my other templates are just fine, hasn't got those actions grayed out)?
