Chatta subito con l'assistenza
Chat con il supporto

Foglight for VMware Horizon View 5.8.3 - User Guide

Manage desktops in virtual environments Interact with Foglight for VMware Horizon View dashboards Reference

Add Host Agents

This workflow allows you to add Infrastructure (IC) agents to monitor your VMware Horizon View environment. An IC agent collects data such as CPU, disk, memory, services, and other network metrics for the VMware Horizon View components in your environment. This data appears on the Details tab of the VMware View Environment dashboard.

The Add Host Agents wizard appears, showing the Select Agent Manager Host page. The information listed on this page is from the Agent Host dashboard (Administration > Agents > Agent Hosts).
The Select Server(s) page appears. This page lists the terminal servers, security servers, and connection servers that are in the VMware View infrastructure.
The Credential Verification - Windows page appears. Credentials are security data that provide the Infrastructure agents with the permission to monitor system resources, such as a host or a range of hosts.
Do not configure a credential. Select this option if you want to configure the credential for this resource at a later time. Local credentials for Windows® and UNIX® are set up by default when Foglight for Infrastructure is installed. Click Next and continue with Step 7.
Add host(s) to a new credential. Select this option if you want to add the host to a new credential. This option is suitable if none of the existing credentials have the connection details needed to access the new host. Click Next and continue with Step 5.
Add host(s) to an existing credential. Select this option if you want to add the host to an existing credential. This option is suitable if an existing credential has the security data needed to access the new host, but you need to edit its resource mappings to include this host. Click Next and continue with Step 6.
a
On the Credential Type page that appears, select the credential type from the available options.
b
Click Next.
The Credential Properties page appears. The level of required information depends on the selected credential type. For example, the User Name and Password type needs a user name and a password, while the Challenge Response type needs a user name along with a question/response pair.
c
On the Credential Properties page, type the required properties, and click Next.
The Credential Name and Lockbox page appears.
d
On the Credential Name and Lockbox page, provide a name to identify the credential, and select a lockbox in which you want to keep the credential. A lockbox can be used to group credentials for access and/or security. In smaller Foglight installations, using the default System lockbox should be sufficient.
Click Next.
The Resource Mapping page appears.
e
On the Resource Mapping page, indicate which hosts you want to associate with this credential. You can either select the host that you are about to start monitoring, all monitored hosts, or hosts whose name contains a specific text string.
Click Next.
The Policies page appears.
f
Optional. On the Policies page, define one or more policies for this credential. A policy defines the number of times a credential can be used, the number of allowed authentication failures, the time range during which the credential is valid, or the length of time the credential data can be cached on the client. For example, you can specify the number of times the credential can be used, or the time period during which it can be used. For complete information about the available credential policies, see the Foglight Administration and Configuration Help.
Click Next.
The Summary page appears.
a
On the Credential page that appears, select an existing credential to contain this host.
b
Click Next.
The Resource Mapping page appears.
c
On the Resource Mapping page, indicate which hosts you want to associate with this credential. You can either select the host that you are about to start monitoring, all monitored hosts, or hosts whose name contains a specific text string.
Click Next.
The Summary page appears.
7
On the Summary page that appears, review the information provided about the host and the monitoring agent.
8
Click Finish.
The new host is added to the Hosts dashboard after a short delay. The monitoring agent is created.
If the operation is successful, the Result For Agent(s) Creation dialog box appears. Review the information and close the dialog box.
The agent instance created to monitor the new host appear on the Administration > Agents > Agent Status dashboard.

Managing certificates

In order to successfully make use of the Foglight commands in your monitoring environment, review the syntax conventions before getting started. The syntax conventions are as follows:

<foglight_home> is a placeholder that represents the path to the Foglight Management Server installation.
<foglight_agent_mgr_home> is a placeholder that represents the path to the Foglight Agent Manager installation. This can be the location of the Foglight Agent Manager installation on a monitored host, or the home directory of the Foglight Agent Manager that comes embedded with the Foglight Management Server. For example:

Foglight Evolve agents use Foglight Agent Manager (FglAM) to manage certificates for SSL encryption connection.

All the certificate-related command line options require that FglAM be up and running.

bin/fglam --add-certificate "user alias 1"=/path/to/certificate/file

The alias is required and is used in the list and delete operations to refer to the certificate. It can be anything.

bin/fglam --list-certificates

Print out a list of certificates and the aliases that refer to them.

Refer to the example output below:

Remove a certificate referred to by an alias.

bin/fglam --delete-certificate "user alias 1"

Use the keytool utility shipped with Foglight to create, import, or export certificates. This utility can be found at: <foglight_home>\jre\bin\keytool.

The KeyStore Foglight used in FIPS-compliant mode is located at: <Foglight_home>/config/security/trust.fips.keystore (default password: nitrogen)

Use the keytool command in FMS JRE located in <foglight>/jre/bin.

keytool -import -trustcacerts -alias "<alias>" -file "<certificate path>" -keystore "<Foglight_home>/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "<Foglight_home>/server/core/bc-fips.jar" -storepass nitrogen

<alias>: The alias is required and is used in the list and delete operations to refer to the certificate. It can be anything.
<Foglight_home>: The folder path where Foglight is installed.
<certificate path>: Your custom certificate path.

keytool -list -keystore "<Foglight_home>/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "<Foglight_home>/server/core/bc-fips.jar" -storepass nitrogen

Prints out a list of certificates and the aliases that refer to them.

Refer to the example output below:

Remove a certificate referred to by an alias.

keytool -delete -alias <alias> -keystore "<Foglight_home>/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "<Foglight_home>/server/core/bc-fips.jar" -storepass nitrogen

C:\Quest\Foglight\jre\bin>keytool -import -trustcacerts -alias "Evolve-Test" -file "D:/Evolve-test.crt" -keystore "C:/Quest/Foglight/config/security/trust.fips.keystore" -deststoretype BCFKS -provider org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider -providerpath "C:/Quest/Foglight/server/core/bc-fips.jar" -storepass nitrogen

Owner: CN=CA, DC=ca, DC=local

Issuer: CN=CA, DC=ca, DC=local

Serial number: xxxx

Valid from: Sun Jan 06 23:07:06 CST 2019 until: Wed Apr 06 23:07:06 CST 2022

Certificate fingerprints:

...

 

Extensions:

...

Trust this certificate? [no]: yes

Certificate was added to keystore

Use the VMware View Environment dashboard

A typical VMware View environment contains a combination of physical and virtual components. A physical component can be a Connection Server, Terminal server, or a user desktop. You can view the overall state of all VMware View components on the VMware View Environment dashboard.

3
On the navigation panel, under Dashboards, choose VMware View.
The Details and Administration tabs are available for selection.

For more information, see these topics:

Details tab

The Details tab contains the Details view and the Quick View. Selecting an object type and its alarm state in the Details view shows the summary information for your selection in the Quick View. For more information about the data appearing on this dashboard, see Explore the VMware View Environment Details tab.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione