VMware Communities: Message List

If on vRA 7.4, make sure you've applied the latest available hotfix here.

Thanks for the reply; so i just need to adjust the offset to make the time same.

Did you not read what was written? No, you cannot install Mac OS on your hardware because it isn't official Apple hardware. That's all there is to say about that.

add ESXi servers DNS name in dns server or host file.

Thanks. Sure I will check that with the production deploymentand on my test bed where I was trying it.

It doesn't mean, i cannot istall any Mac os in my VMware.

My PC is Acer i5 7th Gen. So if i want to install the mac Os in my VM. what should i do ?

Thanks & Regards

Malith

Connecting to the vSphere ESXi Web Client (https://esxi_fqdn.com/ui/#/login) fails.
We see the following entry:

503 Service Unavailable (Failed to connect to endpoint: [N7Vmacore4Http16LocalServiceSpecE:0x05683530] _serverNamespace = / action = Allow _port = 8309)

I am getting the same error trying to set either of the following vCenter 6.7 U1 alarms. The alarms names are identical except for the case on the A/a of alarm.

Name: vSAN health alarm 'Network adapter is VMware certified'

Description: Default alarm to monitor changes for the health test 'Network adapter is VMware certified'

Name:vSAN Health Alarm 'Network adapter is VMware certified'

Description: Default alarm to monitor changes for the online health test 'Network adapter is VMware certified'

The command

Get-AlarmAction -ActionType SendEmail | New-AlarmActionTrigger -StartStatus "Yellow" -EndStatus "Red" -Repeat | Out-Null

Error given for both is:

New-AlarmActionTrigger : 08/12/2018 14:18:53 New-AlarmActionTrigger A specified parameter was not correct:

At C:\Users\Administrator\OneDrive\My PowerShell\VMware\Set vCenter Alarms\Set-vCenterAlarmEmails.ps1:96 char:101

+ ... SendEmail | New-AlarmActionTrigger -StartStatus "Yellow" -EndStatus " ...

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

+ CategoryInfo : NotSpecified: (:) [New-AlarmActionTrigger], InvalidArgument

+ FullyQualifiedErrorId : Client20_AlarmServiceImpl_NewAlarmActionTrigger_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Alarm.NewAlarmActionTrigger

I am using:

PSVersion 5.1.14409.1018

VMware.PowerCLI 11.0.0.10380590

vCenter 6.7 U1 vCenter Appliance 6.7 U1 (6.7.0.20000)

Any ideas

Thanks

What version of ESXi and what version of esx-ui?

Hi community members, I have the same subject problem. I've attached the folder snapshot and log files, kindly help me out.

Hi All,

I have a doubt about VSAN RAID controller queue depth & write cache.

1) We are using Dell PERC H710 RAID controller. Is there any recommended queue depth available to this H710 controller ? By default it is 64. May i know what is the recommended value to reset the queue depth? It is 256 or more ?

2) Do we need to disable write cache from this RAID controller ? i have not seen any options to disable. Is this must ?

Thanks you in advance.

Manivel Rajarathinam.

The h710 controller is not supported on current releases of vsan.

What release are you running?

I would recommend a h330 hba since it's well supported

You need to start with an alarm definition.
Something like this

Get-AlarmDefinition-Name'MyAlarm'|

Get-AlarmAction-ActionTypeSendEmail|

New-AlarmActionTrigger-StartStatusYellow-EndStatusRed-Repeat

ESXi 6.5.

Client version: 1.21.0

Update your host client to the latest on the Fling site and try again.

A server error occurred

400 an error occured while processing the authentication response from the Vcenter Single sign-on server.

details: com.vmware.vim.vmomi.client.expection.SslException:

com.vmware.vim.vmome.core.exception.CertificateValidationException: Server certificate chain not verified.

https://docs.vmware.com/en/Unified-Access-Gateway/3.3.1/com.vmware.uag-331-deploy-config.doc/GUID-1B8665A2-485E-4471-954E-56DB9BA540E9.html did you try to follow these steps?

This is usually due to the security restrictions about identified developers of Mac OS X applications, to solve it just go to System Preferences > Security & Privacy and verify if VMWare is allowed to run and there is no mentioning of a blocked application.

regards

Greetings,

I have verified your finding. Looks like an error in the documentation.

Please use the "Feedback" link at the very bottom right of the Release Notes document to report your finding.

Answer "No" to the question "Did you enjoy your experience on docs.vmware.com?" (although you might have enjoyed it anyway :-)) and you will have the option to enter a more detailed message.

Thanks

Andreas

Hi all,

Recently we upgraded our 5.5 vCenter to 6.5 vCenter and the installation got failed. The appliance was deployed successfully. vCenter server appliance looks healthy and all its content seems fine. But, we are unable to login to the vCenter from any browser. We have tried rebooting the VCSA and restart its core services by SSH. But the issue persists.

We had a three ESXi hosts cluster with a SAN attached to it. We powered off the vCenter 5.5 server VM and took a snapshot backup of it prior to the 6.5 upgrade.

Now, we only have three ESXi hosts and VMs running on them without a vCenter management.

Below are the doubts we have:

Can we power on the 5.5 vCenter server appliance and revert it back to the snapshot which we took prior to the 6.5 upgrade? if so, would it take the IP address back, which was exported to the new 6.5 appliance during the migration process?

If not, can we do a fresh installation of 6.5 vCenter server appliance and attach the ESXI hosts to it ? If so, are there any dependencies (vCenter settings, Network settings, ESXi hosts Licensing, vCenter Licensing) we need to be aware of ?

Latest Images