Do you use the UWP Horizon Client from the Windows Store?

This is a known issue of this Client.

VMware Horizon Client 5.2 for Windows 10 UWP Release Notes

I am not able to fetch the details what i want.

below is the code i am using

foreach($dc in (Get-Datacenter | where {$_.ExtensionData.triggeredAlarmState})){

`   $dc.ExtensionData.TriggeredAlarmState |

    Select @{N='vCenter';E={$vcenter = $dc.Uid.Split('@:')[1]; $vcenter}},

     @{N="Entity";E={Get-View $_.Entity -Server $vcenter | Select -ExpandProperty Name}},

     @{N="Alarm";E={Get-View $_.Alarm -Server $vcenter  | Select -ExpandProperty Info | Select -ExpandProperty Name}},

           Time,OverallStatus |

    Where-object{$_.Alarm -notmatch 'Virtual machine cpu usage' -and

                 $_.Alarm -notmatch 'Host IPMI System Event Log status*'}

}

Below is the Result i am getting

vCenter       : zakvcszone.southzone.sa

Entity        : zak_LUN01

Alarm         : Datastore usage on disk

Time          : 4/16/2020 8:04:49 AM

OverallStatus : yellow

I am looking to fetch the details with below values too.

Previous Status:

New Status:

Alarm Definition:

Current values for metric/state:

Description:

Event details:

when a vcenter alert trigger i am getting the below information as email, in fact would like to fetch the same detail via powercli

Target: zak99.southzone.sa

Previous Status: Green

New Status: Red

Alarm Definition:

([Event alarm expression: Lost Network Redundancy; Status = Red] OR [Event alarm expression: Restored uplink redundancy to portgroups; Status = Green] OR [Event alarm expression: Lost Network Redundancy on DVPorts; Status = Red] OR [Event alarm expression: Restored Network Redundancy to DVPorts; Status = Green])

Event details:

Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic4 is down. Affected portgroups:"Vmotion", "Mgmt".

I have been implementing/supporting  vSphere for over 10 years and Horizon for 5, VxRail for the last 2 years.  I thought during this lock down would be a good time to explore and study for VCP certification, especially since I am in between jobs. Then everything I read says it requires a $4250 class. Wow. I just wanted to verify that this is true, there is no way around this? You cannot just prove yourself via testing? I am not against attending a class, and would enjoy it, but I am not in a financial position to spend that money.

In order to get a VCP certificate, you must get training from a training center. VMware VCP certification cannot be obtained without training. Therefore, you will receive the Install Configure Manage or Optimize and Scale training and then take the exam.

Hello,

I am new to VMware vSphere ESXi. I have deployed ESXi on a server. After this, This uses Management network and has 2 uplink network adaptors. I have also enabled. the following on the vSwitch (saw on post that this could help). Assigned static ip address to this server.

Security policy

How to configure the new VM's network such that it is able to ping the ip address outside this ESXi host. Currently my DNS server outside of this VM is not reachable from this VM.

I have installed this VM so that I can use this as a client VM to trigger the installation of VCenter Server Appliance.

Since I am new to this VMware, I did not understand how to properly configure the network on this VM. I have configured with the static ip, gateway, DNS, subnet mask.

However,what is needed to make this VM reach outside of this Host ?

Any suggestions is much appreciated !

Thanks !

[root@clientVM1 lin64]# ./vcsa-deploy install /root/vcenter/config/embedded_vCSA_on_ESXi.json --accept-eula --no-esx-ssl-verify --no-ssl-certificate-verification --log-dir=/root/vcenter/log

Run the installer with "-v" or "--verbose" to log detailed information

Updating log file location, copying '/tmp/vcsaCliInstaller-2020-04-21-03-14-69v3uwr0/vcsa-cli-installer.log' to desired location as a backup: '/root/vcenter/log/workflow_1587438887538/vcsa-cli-installer.log.bak'

Consuming the installer build:15393115

Workflow log-dir /root/vcenter/log/workflow_1587438887538

=================================================== [START] Start executing Task: To validate CLI options at 03:14:47 ===================================================

Command line arguments verfied.

========= [SUCCEEDED] Successfully executed Task 'CLIOptionsValidationTask: Executing CLI optionsValidation task' in TaskFlow 'template_validation' at 03:14:47 =========

=========================================== [START] Start executing Task: To validate the syntax of the template. at 03:14:47 ===========================================

Template syntax validation for template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' succeeded.

Syntax validation for all templates succeeded.

======== [SUCCEEDED] Successfully executed Task 'SyntaxValidationTask: Executing Template Syntax Validation task' in TaskFlow 'template_validation' at 03:14:47 ========

[START] Start executing Task: To check the version of each template, and for each older template that supports CEIP, convert it to the latest template format, and save

it to the Template Blackboard at 03:14:47

CEIP is not enabled because the template key 'ceip_enabled' in section 'ceip', subsection 'settings' in template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' was

set to 'false'.

CEIP is not enabled because the template key 'ceip_enabled' in section 'ceip', subsection 'settings' in template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' was

set to 'false'.

CEIP is not enabled because the template key 'ceip_enabled' in section 'ceip', subsection 'settings' in template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' was

set to 'false'.

Template version processing for template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' succeeded.

Version processing for all templates succeeded.

======= [SUCCEEDED] Successfully executed Task 'VersionProcessingTask: Executing Template Version Processing task' in TaskFlow 'template_validation' at 03:14:47 =======

============= [START] Start executing Task: To validate the template structure against the rules specified by a corresponding template schema. at 03:14:47 =============

Template structure validation for template '/root/vcenter/config/embedded_vCSA_on_ESXi.json' succeeded.

Structure validation for all templates succeeded.

===== [SUCCEEDED] Successfully executed Task 'StructureValidationTask: Executing Template Structure Validation task' in TaskFlow 'template_validation' at 03:14:47 =====

[START] Start executing Task: To create a dependency graph for the provided templates, with an edge pairing two templates that are dependent on each other. Such graph

relationships will affect whether certain templates can be deployed in parallel, or must be deployed sequentially. at 03:14:48

Dependency processing for all templates succeeded.

==== [SUCCEEDED] Successfully executed Task 'DependencyProcessingTask: Executing Template Dependency Processing task' in TaskFlow 'template_validation' at 03:14:48 ====

=================================== [START] Start executing Task: Validate that requirements are met in the source VCSA. at 03:14:48 ===================================

InstallRequirementCollector: Reached gathering requirement

================ [SUCCEEDED] Successfully executed Task 'SrcRequirementTask: Running SrcRequirementTask' in TaskFlow 'embedded_vCSA_on_ESXi' at 03:14:48 ================

=================================================== [START] Start executing Task: Perform precheck tasks. at 03:14:49 ===================================================

============================ [START] Start executing Task: Verify that the provided credentials for the target ESXi/VC are valid at 03:14:49 ============================

The certificate of server '1.2.3.4' will not be verified because you have provided either the '--no-ssl-certificate-verification' or '--no-esx-ssl-verify' command

parameter, which disables verification for all certificates. Remove this parameter from the command line if you want server certificates to be verified.

============================ [SUCCEEDED] Successfully executed Task 'Running precheck: TargetCredentials' in TaskFlow 'install' at 03:14:49 ============================

============================== [START] Start executing Task: Verify the target host type matches the one given in the template at 03:14:49 ==============================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: TargetHostType' in TaskFlow 'install' at 03:14:49 ==============================

========================== [START] Start executing Task: Verify that the target ESXi or VC version meets the minimum requirements at 03:14:49 ==========================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: TargetVersion' in TaskFlow 'install' at 03:14:49 ==============================

================================ [START] Start executing Task: Validate that the OVA image has the required OVA properties. at 03:14:50 ================================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: OVAProperties.' in TaskFlow 'install' at 03:14:50 ==============================

====================================== [START] Start executing Task: Validate the provided ip/fqdn is available to use at 03:14:50 ======================================

Pinging IPv4 address 5.6.7.8

5.6.7.8 seems not in use.

Pinging IPv4 address vcenter1.esxi1.lab

Pinging IPv4 address vcenter1.esxi1.lab

Pinging IPv4 address vcenter1.esxi1.lab

5.6.7.8 seems not in use.

=============================== [SUCCEEDED] Successfully executed Task 'Running precheck: IpFqdnInUse' in TaskFlow 'install' at 03:15:34 ===============================

===================== [SUCCEEDED] Successfully executed Task 'Running precheck: LinkingTargetHostnameValidation' in TaskFlow 'install' at 03:15:35 =====================

========================================= [START] Start executing Task: Validate the target ESXi management status at 03:15:35 =========================================

=========================== [SUCCEEDED] Successfully executed Task 'Running precheck: ESXManagementStatus' in TaskFlow 'install' at 03:15:35 ===========================

============================== [START] Start executing Task: Precheck CPU, memory and datastore size requirements for a host. at 03:15:35 ==============================

=============================== [SUCCEEDED] Successfully executed Task 'Running precheck: HostConfigs' in TaskFlow 'install' at 03:15:37 ===============================

=============================== [START] Start executing Task: Validate the provided target appliance name is available to use at 03:15:37 ===============================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: ApplianceName' in TaskFlow 'install' at 03:15:37 ==============================

============================================================== [START] Start executing Task:  at 03:15:37 ==============================================================

============================================== [SUCCEEDED] Successfully executed Task '' in TaskFlow 'install' at 03:15:37 ==============================================

====================== [START] Start executing Task: Check whether the datastore's free space accommodate the VCSA's deployment option at 03:15:38 ======================

============================ [SUCCEEDED] Successfully executed Task 'Running precheck: TargetDsFreespace' in TaskFlow 'install' at 03:15:38 ============================

=========================== [START] Start executing Task: Verify the provided SSO info is valid by connecting to the STS service. at 03:15:38 ===========================

============================== [SUCCEEDED] Successfully executed Task 'Running precheck: SSOCredentials' in TaskFlow 'install' at 03:15:38 ==============================

============================= [START] Start executing Task: Verify that the provided external SSO (PSC)/Embedded info is valid at 03:15:38 =============================

=============================== [SUCCEEDED] Successfully executed Task 'Running precheck: SSOExternal' in TaskFlow 'install' at 03:15:38 ===============================

======================= [SUCCEEDED] Successfully executed Task 'PrecheckTask: Running prechecks.' in TaskFlow 'embedded_vCSA_on_ESXi' at 03:15:38 =======================

=========================== [START] Start executing Task: Invoke OVF Tool to deploy VCSA for installation, upgrade, and migration at 03:15:39 ===========================

OVF Tool: Opening OVA source: /mnt/cdrom/vcsa-cli-installer/lin64/../../vcsa/VMware-vCenter-Server-Appliance-7.0.0.10100-15934039_OVF10.ova

OVF Tool: The manifest validates

OVF Tool: The provided certificate is in valid period

OVF Tool: Source is signed but could not verify certificate (possibly self-signed)

OVF Tool: Certificate information:

OVF Tool:   CertIssuer:/C=US/ST=California/L=Palo Alto/O=VMware, Inc.

OVF Tool:   CertSubject:/C=US/ST=California/L=Palo Alto/O=VMware, Inc.

OVF Tool:   -----BEGIN CERTIFICATE-----

OVF Tool:   ... <DELETED> ...

OVF Tool:

OVF Tool:   -----END CERTIFICATE-----

OVF Tool: Opening VI target: vi://root@1.2.3.4:443/

OVF Tool: Deploying to VI: vi://root@1.2.3.4:443/

OVF Tool: Disk progress: 99%

OVF Tool: Transfer Completed

OVF Tool: Powering on VM: Embedded-vCenter-Server-Appliance

OVF Tool: Task progress: 0%

OVF Tool: Task Completed

OVF Tool: Waiting for IP address...

OVF Tool: Received IP address: 5.6.7.8

OVF Tool: Completed successfully

====================== [SUCCEEDED] Successfully executed Task 'Deploying vCenter Server Appliance' in TaskFlow 'embedded_vCSA_on_ESXi' at 03:21:31 ======================

================================= [START] Start executing Task: Monitor the entire VCSA deployment using appliance REST API at 03:21:31 =================================

Checking if the target VCSA is powered on and ready for operations...

Successfully verified that the target VCSA 'Embedded-vCenter-Server-Appliance' has been powered on and is now ready for operations

Checking if the target VCSA appliance API is available for query

The certificate of server '5.6.7.8' will not be verified because you have provided either the '--no-ssl-certificate-verification' or '--no-esx-ssl-verify' command

parameter, which disables verification for all certificates. Remove this parameter from the command line if you want server certificates to be verified.

Where ,

1.2.3.4 - ESXi host

5.6.7.8 - vCenter IP

clientVM1 is on the another server , a RHEL VM created, which has access to the DNS server. Reverse mapping of DNS is also done on the DNS server.

Can you reduce the amount of CPU on this virtual machine? The% RDY value is caused by an over-given CPU. If there are as many CPUs on the virtual machine that you don't need, you may experience this problem.

good! I am testing a scenario of 3 vsan nodes, 2 of them with storage and a single one with essentials plus and vsan standard licenses and I have two questions. Could I use the steched cluster and witness apliance option for this installation? Can I somehow use the node that now has no disks (boots via SD) as a witness? Thank you

berndweyand

Yes, unfortunately they are still on this old version and hardware. I'm quite new in this team and quite frankly there's a lot I would've done differently.

Ok, thanks! I'll look into that.

Kind regards,

Frida

Page 81: https://docs.vmware.com/en/VMware-vSphere/6.7/vsphere-esxi-vcenter-server-67-networking-guide.pdf?hWord=N4IghgNiBcIEYEsB…

IRIX201110141

Thanks for the detailed response!

Kind regards, Frida

Thank you both for reply.

a.p.Unfortunately I already tried to modifiy the UDID without success.

So, at this point, is there at least a way to backup/restore the Networking section?

If the server fails, I'll get a pain scratching my head to restore the whole network configuration

The default post-installation network configuration should usually give VMs network connectivity.

vSwitch0 will use a vmnic physical NIC port as an uplink, and on the vSwitch there will be a port group called VM Network that you can connect the network adapters of VMs to.

So as long as your VM can be on the same L2/L3 network as your management connection (at least to begin with) you should be good to go.

I suggest posting screenshots of your vSwitch setup (the parts I’ve mentioned above)

As I understand you have 3 nodes. It’s possible to use stretched cluster. The minimum number of hosts in a vSAN Stretched Cluster is 2 plus the vSAN Witness Host. Site 1 contains one physical ESXi host; Site 2 contains one physical ESXi host; Site 3 contains the vSAN Witness Host (virtual appliance or physical). The configuration is 1+1+1. This is commonly referred to as a 2 Node configuration. If both nodes in a 2 Node configuration are in the same site, the vSAN Witness Host can be in the same site , or in an alternate site. In configurations where the 2 Nodes are in alternate sites, the vSAN Witness Host must be in a third site. About witness appliance need storage to deploy the ova on local datastore where some storage also needed for witness components. So as I know witness appliance not installed on SD card.  If you using physical ESXi host as witness you can install this in SD card however, you need vsphere license and some storage capacity for witness components..

Hi,

How can I send only NSX-T Load Balancer Access Logs to Syslog? I can't see any Log Message IDs related to LB, so wonder if there is a way to only send messages related to LB. If not, which Log Message ID would include the LB access logs?

Thanks.

Hi all, has anyone experienced the Horizon agent going into a “Agent Unreachable” state on physical desktops?

We have desktop pools in our Horizon 7.10 environment that contain both virtual and physical machines.

Thanks in advance.

High “ready” and “co-stop” when only running a single VM indicates too many vCPUs.

No, it was only once so far.

Environment:

VMware ESXi, 6.7.0, 15160138

vCenter: 6.7.0.41000 build number: 14836122

We cannot remove one crashed VMware host from our datacenter. We do not have any clusters configured. We do have a vDS. Other hosts are working fine and in production. Remove from inventory is greyed out in vCenter.

The following action I already tried:

Disconnect the host (succesfully)

Remove host from vDS (succesfully)

Remove from inventory is greyed out

Used PowerCLI but came with this error:

Remove-VMHost : 21-4-2020 08:23:16      Remove-VMHost           The method is disabled by 'com.vmware.vcIntegrity'

At line:1 char:1

+ Remove-VMHost ESXVN0XX.FQDN

Any ideas?