If your existing 22.09.X virtual appliance has Internet connectivity, you can upgrade the appliance online.
Prerequisites
-
The prerequisites listed in Prerequisites for a Omnissa Access Online Upgrade are verified.
-
Verify that the virtual appliance is powered on and functioning.
-
For Omnissa Access 23.09, the Mobile SSO CertProxy configuration page UI was redesigned. If you enabled the VA-Configuration > Mobile SSO > Android SSO cert proxy settings in your environment, during the upgrade, you are asked to update the following CertProxy settings.
-
Number of load balancers. Enter the number of load balancers that are between the CertProxy service and the Omnissa Access instance or enter 0 if a load balancer is not used.
-
Client IP load balancer header name (Remote IP source). This is the source used to obtain the CertProxy instance IP from the HTTP request. The value can be X-forwarded-For header orX-Real-Ip header. If the number of load balancers is 0, Remote IP source is automatically set to Request remote address.
-
The allowlist of CertProxy instance IP addresses to accept authentication requests from. The current IP addresses configuration is pre-populated. You can make changes or click Enter to keep the current configuration. To change the allowlist, enter IP addresses of CertProxy instances separated by a semicolon, either in CIDR format, subnet format delimited by a space, or as a single IP.
Important: If the number of load balancers is 0 and the CertProxy destination is set to localhost, you must add the localhost IP to the list of IP addresses in the allowlist. This is usually 127.0.0.1.
-
Procedure
-
Log in to the existing Omnissa Access virtual appliance as the root user.
-
Run the following
updatemgr.hzncommand./usr/local/horizon/update/updatemgr.hzn updateinstaller -
Run the following command to check that an online upgrade exists.
/usr/local/horizon/update/updatemgr.hzn check -
Run the following command to update the appliance.
/usr/local/horizon/update/updatemgr.hzn update-
If the CertProxy service is enabled, the following settings must be updated.
-
Please provide number of load balancers between CertProxy and Access instance:Note: If you do not use a load balancer, enter
0as the value. When you enter 0, the next CertProxy question does not display. -
Please provide client IP load balancer header name (x-forwarded-for/x-real-ip): -
Please provide list of CertProxy instance IP addresses, separated by a semicolon, either in CIDR format, subnet format delimited by a space, or as a single IP:Important: If the number of load balancers is 0 and the CertProxy destination is set to localhost, you must add the localhost IP to the list of IP addresses in the allowlist. This is usually 127.0.0.1.
-
-
When asked
Would like to execute script /usr/local/horizon/update/reindexingIndices.hzn?, enter y when you upgrade the first node in a cluster. When you upgrade the other nodes in the cluster, enter n.For a single node upgrade, the setting is y by default.
-
-
Run the
updatemgr.hzn checkcommand again to verify that a newer update does not exist./usr/local/horizon/update/updatemgr.hzn check -
Restart the virtual appliance.
reboot -
Check the version of the upgraded appliance.
vamicli version --applianceThe new version is displayed.
-
After you upgrade all the nodes in your Omnissa Access deployment, use the diagnostics dashboard to monitor system information health.
-
Log in to the Omnissa Access console.
-
Select Monitor > Resiliency to open the diagnostics dashboard.
-
If your deployment consists of more than one Omnissa Access appliance, select the appliance you want to monitor.
-
Check the status of the various services.
For example, to check the health of the OpenSearch service, review the Integrated Components section and confirm that the values for the OpenSearch items are as expected. Therefore, the value for OpenSearch - Health is Green, the information about the cluster nodes is accurate.
-
Results
The upgrade is complete.
For tasks that might need to be performed after the upgrade to 23.09, see Post-upgrade Configuration of Omnissa Access.
Cette page vous a-t-elle été utile ?