Quantcast
Channel: VMware Communities: Message List
Viewing all 195043 articles
Browse latest View live

Re: Permissions problems with linked VCs after VCSA migration

$
0
0

We have moved things forward (using various machine account reset procedures, including this one: VMware Knowledge Base ) and now Site B is able to browse Site A. However it seems the root problem was with Site B as site A still can not browse this.

 

Site A now reports:

 

2020-09-14T16:03:32.473567+00:00 err vmdird  t@139750677653248: _VmDirFetchReplicationPage: error: 53 filter: 'uSNChanged>=90807' requested: 1000 received: 0 usn: 90806 utd: '765c1341-c05f-11e5-ae51-000c29865313:95793,'

 

Which isn't very interesting, however site B now says this:

 

2020-09-14T15:59:31.962756+00:00 err vmdird  t@140568298514176: VmDirSendLdapResult: Request (Search), Error (53), Message (Server in not in normal mode, not allowing outward replication.), (0) socket (ip.ip.ip.ip)

 

A bit more googling around led us to this command and output:

 

# /usr/lib/vmware-vmafd/bin/dir-cli state get

Enter password for administrator@vsphere.local:

Directory Server State: Failure (5)

 

There are a couple of articles around this but just attempting to change the state but this CLI output implies this is no longer available with the 6.7 VCSA:

 

# /usr/lib/vmware-vmafd/bin/dir-cli state set --state NORMAL
  Enter password for administrator@vsphere.local:
  dir-cli failed. Error 9001: Possible errors:
  LDAP error: Operations error
  Win Error: Operation failed with error ERROR_INVALID_FUNCTION (1)

 

and trying to follow other options to reset the password doesn't seem to work either:

 

# vcenter-restore -u administrator
  Please enter SSO Admin Password:
  Restore of embedded node is not supported via this script. Exiting.

 

This seemed to work as a script but didn't resolve the problem:

 

/usr/lib/vmware-vmafd/bin/dir-cli computer password-reset --login administrator --live-dc-hostname fbsshefvc.fletchers.corp --password XXXXXXX

 

It feels like we are at the root cause now though, there is a problem with the PSC or 'Directory Server' on Site B.


Re: SRM 8.2 virtual appliance wont take certificate.

$
0
0

Hi

 

Please try the following:

 

1. Upload the certificate chain to SRM appliance(Steps 1 to 6) -->  How to Set Up a Trusted Environment for the Site Recovery Manager Virtual Appliance

2. Convert certificate to PKCS#12 format --> VMware Knowledge Base

Note: openssl tool is available on SRM appliance by default. You can just run openssl instead of openssl.exe

 

3. Run steps 7 and later once you have the certificate in PKCS#12 format.--> How to Set Up a Trusted Environment for the Site Recovery Manager Virtual Appliance

 

Hope that helps

Re: Standby-Hosts exiting standby after VCSA-Reboot

Re: Heartbeat Wait Time

Re: get the number of vms for each esx

$
0
0

Sorry

i made a mistake,

I have no error but the result file returns me a value of 0 in the number of vms

 

for example  i have 2 esx, and the result is like the attached file

Re: VM Write Latency

$
0
0

the problem here indeed is that you are using 'benchmarking' tools which are not really designed for benchmarking distributed object storage systems. If you want to figure out what your cluster can do, then look at something like HCIBench instead. That will give you a better view.

 

In your case you are saying a performance impact simply because half of the IO will need to go across the network, and there's a cost to that. You compare it to RAID-0, which has no protection whatsoever.

Workstation Pro 15.5.2 MKS: Internal Error

$
0
0

Hi.. Had this issue for a while but finally have some time to look at resolving it. I Workstation Pro 15.5.2 installed but whenever I try to connect to an esxi 5.1 vm I get an MKS: Internal error and just a black screen. This just happens on Workstation Pro 15. It was fine on Workstation 12 and it also still connect fine using vsphere client console.

 

I've tried iincreasing  Remote.maxconnections option also removing /re-adding the guest. Restarting the host but issue remains.. As this was working fine with Workstation 12 it looks particular to Workstation 15.. any ideas how I can get the display console working correctly instead of this MKS internal error and the black screen?

 

Thanks

Re: APNS for Applications - Update for 2020/2021?


Re: STS Signing Certificate is expiring on Windows vCenter 6.0

$
0
0

C:\ProgramData\VMware\vCenterServer\cfg\sso\keys\newsts>"C:\Program Files\VMware

\vCenter Server\jre\bin\keytool.exe" -list -v -keystore root-trust.jks

输入密钥库口令:

密钥库类型: JKS

密钥库提供方: SUN

 

 

您的密钥库包含 2 个条目

 

 

别名: root-ca

创建日期: 2020-9-14

条目类型: trustedCertEntry

 

 

所有者: OU=VMware, O=scxt-vCenter, ST=California, C=US, DC=local, DC=vsphere, CN

=CA

发布者: OU=VMware, O=scxt-vCenter, ST=California, C=US, DC=local, DC=vsphere, CN

=CA

序列号: f885f49bec9a18e8

有效期为 Sun Sep 23 09:34:42 CST 2018 至 Wed Sep 20 09:34:42 CST 2028

证书指纹:

         MD5:  9E:9E:7C:AF:70:7F:DC:02:C3:AE:E0:40:2C:80:DE:FD

         SHA1: A7:27:C0:F8:9C:E6:A6:C0:25:DA:7F:E4:D8:0C:14:38:C7:0E:1A:A7

         SHA256: 38:9D:83:6B:51:10:44:43:71:70:3A:C6:B8:9A:BC:B0:32:66:55:6C:3D:

E4:C2:61:6C:FD:FF:40:45:AF:E2:AA

签名算法名称: SHA256withRSA

主体公共密钥算法: 2048 位 RSA 密钥

版本: 3

 

 

扩展:

 

 

#1: ObjectId: 2.5.29.19 Criticality=true

BasicConstraints:[

  CA:true

  PathLen:0

]

 

 

#2: ObjectId: 2.5.29.15 Criticality=true

KeyUsage [

  Key_CertSign

  Crl_Sign

]

 

 

#3: ObjectId: 2.5.29.17 Criticality=false

SubjectAlternativeName [

  RFC822Name: email@acme.com

  IPAddress: 127.0.0.1

]

 

 

#4: ObjectId: 2.5.29.14 Criticality=false

SubjectKeyIdentifier [

KeyIdentifier [

0000: B8 FF 79 34 6C A8 33 D7   F0 8D B0 EE 9C 7D E9 23  ..y4l.3........#

0010: 9E A0 A7 96                                        ....

]

]

 

 

 

 

 

 

*******************************************

*******************************************

 

 

 

 

别名: newstssigning

创建日期: 2020-9-14

条目类型: PrivateKeyEntry

证书链长度: 2

证书[1]:

所有者: OU=VMware, O=VMware, L=Palo Alto, ST=California, C=US, CN=CA

发布者: OU=VMware, O=scxt-vCenter, ST=California, C=US, DC=local, DC=vsphere, CN

=CA

序列号: df6477ab15b7445d

有效期为 Mon Sep 14 14:41:13 CST 2020 至 Wed Sep 14 14:41:13 CST 2022

证书指纹:

         MD5:  2F:E3:3F:98:DA:64:4F:28:1F:85:EB:5A:83:C9:5B:66

         SHA1: 78:AB:83:21:3D:3E:F0:6A:DF:C9:CC:4E:32:B3:9B:7F:FC:2C:E8:74

         SHA256: E7:EB:28:4C:AC:7E:9B:94:03:89:08:72:3C:46:D4:82:FB:C8:B0:4F:BC:

AB:3B:B5:6B:65:B2:7E:C7:26:DB:28

签名算法名称: SHA256withRSA

主体公共密钥算法: 2048 位 RSA 密钥

版本: 3

 

 

扩展:

 

 

#1: ObjectId: 2.5.29.35 Criticality=false

AuthorityKeyIdentifier [

KeyIdentifier [

0000: B8 FF 79 34 6C A8 33 D7   F0 8D B0 EE 9C 7D E9 23  ..y4l.3........#

0010: 9E A0 A7 96                                        ....

]

]

 

 

#2: ObjectId: 2.5.29.15 Criticality=false

KeyUsage [

  DigitalSignature

  Non_repudiation

  Key_Encipherment

]

 

 

#3: ObjectId: 2.5.29.17 Criticality=false

SubjectAlternativeName [

  RFC822Name: dongjh@ahope.com.cn

  IPAddress: 10.44.221.29

  DNSName: scxt-vCenter

]

 

 

#4: ObjectId: 2.5.29.14 Criticality=false

SubjectKeyIdentifier [

KeyIdentifier [

0000: EC FC 60 86 DF 98 B2 15   D3 56 7A 7F BF 23 B4 25  ..`......Vz..#.%

0010: 7D E8 3C 89                                        ..<.

]

]

 

 

证书[2]:

所有者: OU=VMware, O=scxt-vCenter, ST=California, C=US, DC=local, DC=vsphere, CN

=CA

发布者: OU=VMware, O=scxt-vCenter, ST=California, C=US, DC=local, DC=vsphere, CN

=CA

序列号: f885f49bec9a18e8

有效期为 Sun Sep 23 09:34:42 CST 2018 至 Wed Sep 20 09:34:42 CST 2028

证书指纹:

         MD5:  9E:9E:7C:AF:70:7F:DC:02:C3:AE:E0:40:2C:80:DE:FD

         SHA1: A7:27:C0:F8:9C:E6:A6:C0:25:DA:7F:E4:D8:0C:14:38:C7:0E:1A:A7

         SHA256: 38:9D:83:6B:51:10:44:43:71:70:3A:C6:B8:9A:BC:B0:32:66:55:6C:3D:

E4:C2:61:6C:FD:FF:40:45:AF:E2:AA

签名算法名称: SHA256withRSA

主体公共密钥算法: 2048 位 RSA 密钥

版本: 3

 

 

扩展:

 

 

#1: ObjectId: 2.5.29.19 Criticality=true

BasicConstraints:[

  CA:true

  PathLen:0

]

 

 

#2: ObjectId: 2.5.29.15 Criticality=true

KeyUsage [

  Key_CertSign

  Crl_Sign

]

 

 

#3: ObjectId: 2.5.29.17 Criticality=false

SubjectAlternativeName [

  RFC822Name: email@acme.com

  IPAddress: 127.0.0.1

]

 

 

#4: ObjectId: 2.5.29.14 Criticality=false

SubjectKeyIdentifier [

KeyIdentifier [

0000: B8 FF 79 34 6C A8 33 D7   F0 8D B0 EE 9C 7D E9 23  ..y4l.3........#

0010: 9E A0 A7 96                                        ....

]

]

 

 

 

 

 

 

*******************************************

*******************************************

Deployment with subscription failed with timeout error

$
0
0

We have a blueprint to create VM on vSphere with a subscription to complete configuration on state "VMPSMasterWorkflow32.MachineProvisioned" phase PRE on vRA 7.6

We configured :

  • Timeout to 20160 minutes (14 days) on workflow subscription
  • Add this setting <addkey="Extensibility.VMPSMasterWorkflow32.MachineProvisioned.PRE.Timeout"value="14.00:00:00.0"/> in C:\Program Files (x86)\VMware\vCAC\Server\ManagerService.exe.config on Manager Service Service

 

A user request this blueprint. 72 hours after, the deployment fail with error "The following component requests failed: VMWindowsServer. Component Request [b70ff5e8-7b09-4676-8d02-e2523698cb71] terminated due to timeout". The workflow are still in waiting of a user interaction.

 

What's wrong

 

Thanks

Auto-start VM after power outage or reboot Workstation 16 Pro

$
0
0

Before Shared VMs were removed in Workstation 16, Shared VMs were the best option to auto-power on VMs.

 

I understand folks can add `vmrun` batch scripts or powershell scripts but almost all of these options require the user to log in first.

 

The scenario I would like to avoid is:

  • I am cities away from my PC
  • A power outage or reboot occurs

 

On startup, I am not logged in and my startup scripts will not run. I can create a Scheduled Task that runs on power on (not login), however, when I finally gain access to my physical PC and log in, the Workstation client cannot control or access the VMs (running in background with `nogui`).

 

I have tried to run the Scheduled Task with "runAs: my account", but Workstation STILL cannot control unless I kill the processes and restart them.

 

Any thoughts?

Re: "Unable to query vSphere health information" and "Unable to query vSAN health information" after certificate replacement - VCSA 6.7U2

$
0
0

Faced the same issue :

 

Virgo logs gave :

 

++++++

Caused by: com.vmware.vim.vmomi.client.exception.VlsiCertificateException: Server certificate chain is not trusted and thumbprint doesn't match

 

Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

++++++

 

Fixed the mismatch and the Skyline health was fine.

Re: Error "Unable to Connect to MKS" after upgrade to VMware Workstation 15.5.5

$
0
0

Wow, that's really atrocious!  The Shared VM's feature was pretty much *the only* thing I really cared about.  Our infrastructure is based on it.

 

Thank you for providing this text.  I was able to search it and found this link...

 

VMware Workstation 16 Pro Release Notes

 

I'm going right now to log into our company's financial software and put a block on vmware and red flag them to prevent us from spending any more money on vmware products going forward.  The red flag will contain the link above to make anyone looking to buy it aware.

 

I cannot allow people to buy vmware if the shared VM's are not working!

Re: Status of other host hardware objects error after upgrade to ESXi 6.7

$
0
0

I have similar on ProLiant DL380 Gen10 that is using the HPE Custom VMware ESXi 6.7 Image.

 

My Hardware Health sensors  have two areas of problems:

 

System Chassis 1 UID | Unknown state

and three entries for Memory

 

Memory Device 10 Mem_Stat_C01S11 | Alert state

Memory Device 18 Mem_Stat_C02S03 | Alert state

Memory Device 2 Mem_Stat_C01S03 | Alert state

 

Server is only using 2x32GB 2933MHz DIMM

 

Strange thing was that the System Chassis 1 UID issue was present after I upgraded from Esxi 6.5 to 6.7.

Also host was at iLO5 v2.16. I thought that iLO upgrade to latest might clear it.

Now host is at iLO5 v2.30 ... and additionally displaying Memory sensor issues.

When viewing under esxcli ipmi it shows Configuration Error.

System BIOS = U30 v2.36 07/16/2020

 

iLO5 IML and HPE Support have given the server a clean bill of health.

I also have updated ALL firmware for BIOS, NIC, SPS, Smart Array to latest I can find.

esxi hardware sensors alerts.png

 

Re: Ethernet problem with vmware 12.0.0 (16880131) and MacOS Big Sur 11 20A5364e

$
0
0

Apple is not releasing Big Sur tomorrow, just the iOS based platforms.


Re: ports to be open

Re: Mouse click not working Workstation Pro 14.1.1 build - 7528167

$
0
0

Still happens to me with Workstation PRO15.5.6 build-16341506.

Left click doesn't work but everything else works. Read through and tried all of the suggestions on this post and the only thing that works is a full power cycle of the VM.

Re: Auto-start VM after power outage or reboot Workstation 16 Pro

Re: vLCM - HPe HSM - Fetching of online depot URL failed

vapp not started

$
0
0

Hi all

 

In our vmware structure, there are 2 vcenter, namely management and edge-resource pool.

Management vcenter unfortunatly restarted.We have reactivated vcenter and VSAN and HA,NSX now look healthy.

But vms connected to Vapp cannot enter the start state.

 

Fail on below;

 

Unable to start vApp "testing2". - Platform config fault reported by vCenter Server. Platform Config fault occurred. An error occurred during host configuration. vCenter Server task (moref: task-11383) failed in vCenter Server 'EdgeResourcePod-vCenter' (36101bc6-481d-4110-9ba9-226cfe32f224). - An error occurred during host configuration.

 

image.png

 

vcloud-container-debug.log file in the /opt/vmware/vcloud-director/logs(logoutput file named) directory, but I could not find much detail.

 

I closed the admission control but the error occurred again.

Viewing all 195043 articles
Browse latest View live