Security Server Health Test
In an Omnissa Horizon environment, the security server secures remote connections to virtual desktops and applications. Security servers are specifically designed to handle secure external access while protecting the internal network infrastructure. If the security server is not responding or if the SSL/TLS certificate of the security server is not valid, then, users may not be authenticated and hence remote connections could not be established. To overcome such authentication issues, it is essential to monitor the security server round the clock. The Security Server Health test helps in this aspect!
This test auto-discovers the security servers in the target Omnissa Horizon Cluster/Pod environment and for each security server, this test reports the current status. This test also reports further information on the SSL/TLS certificate of the security server such as if the certificate is valid and if the certificate is the default certificate. Using this test, administrators can easily identify the expiry date/time of the SSL/TLS certificate.
Target of the test : An Omnissa Horizon Cluster/Pod
Agent deploying the test : A remote agent
Outputs of the test : One set of results for each security server configured on the Omnissa Horizon Cluster/Pod being monitored
| Parameter | Description |
|---|---|
|
Test Period |
How often should the test be executed. |
|
Host |
The host for which the test is to be configured. |
|
Port |
Refers to the port used by the target Omnissa Horizon Cluster/Pod. By default, this is set to NULL. |
|
Connection Server Name |
By default, this test connects to every Horizon Connection Server configured in the Omnissa Horizon Cluster/Pod remotely and collects the required metrics. For this, it is necessary to specify valid credentials of the Horizon Connection Servers. To help administrators provide these credentials quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the encircled '+' icon that appears alongside this parameter in the test configuration page. To know how to use this special page, refer to Configuring the Omnissa Horizon Connection Servers for Monitoring. |
|
User Name, Password and Confirm Password |
By default, this test uses Omnissa Restful APIs to collect the required metrics from the target Omnissa Horizon Cluster/Pod. For this, the eG agent should be configured with read-only user privileges that will allow the agent to communicate with the Horizon Connection Server in a particular domain and extract statistics. Therefore, specify the credentials of the user who is authorized to access the Horizon Connection Server against the User Name, Password and Confirm Password text boxes. |
|
Domain Name |
Specify the name of the domain to which the Horizon Connection Server belongs to. |
|
DD Frequency |
Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD Frequency. |
|
Detailed Diagnosis |
To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:
|
| Measurement | Description | Measurement Unit | Interpretation | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
|
Status |
Indicates the current status of this security server. |
|
The values that this measure can take and its corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the above-mentioned Measure Values to indicate the current status of each security server. However, the graph of this measure will represent the same using the numeric equivalents only i.e., 1 to 3. The detailed diagnosis of this measure lists the Version and the Build number of the security server. |
||||||||
|
Is this the default certificate? |
Indicates whether/not the SSL/TLS certificate of this security server the default certificate. |
|
The values that this measure can take and its corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the above-mentioned Measure Values to indicate SSL/TLS certificate of this security server the default certificate. However, the graph of this measure will represent the same using the numeric equivalents only i.e., 0 or 1. |
||||||||
|
Is the certificate valid? |
Indicates whether/not the SSL/TLS certificate of this security server is valid. |
|
The values that this measure can take and its corresponding numeric values are discussed in the table below:
Note: By default, this measure reports the above-mentioned Measure Values to indicate whether/not the SSL/TLS certificate of this security server is valid. However, the graph of this measure will represent the same using the numeric equivalents only i.e., 0 or 1. The detailed diagnosis of this measure lists the message that offers further information on the validity of the SSL/TLS certificate. |
||||||||
|
TLS certificate expiry days |
Indicates the number of days that are left for the SSL/TLS certificate of this security server to expire. |
Number |
The detailed diagnosis of this measure lists the start time and end time of the SSL/TLS certificate. |
