Appendix A: Upgrading the HySecure Cluster
This section describes the detailed process of applying this service pack on the HySecure Cluster, having three nodes (Active Config, Standby Config and Access server):
To upgrade the HySecure cluster, follow these main steps:
-
Upgrade the HySecure Access Server node
-
Upgrade the HySecure Standby Config node
-
Upgrade the HySecure Active Config node
Upgrading the HySecure Access Server Node
-
Connect to the HySecure Access Server node as a Security Officer (SO).
Note
Do not connect using a Virtual IP Address; ensure to use the actual IP of the real node.
-
Navigate to Settings > Cluster > Manage.
-
Select Enable Maintenance mode to apply the service pack.
-
Navigate to the Firmware upgrade section under the Settings > General Settings.
-
Select the option Hotfix or Service pack from the Select upgrade file type, and upload the upgrade file.
-
Uploading the service pack may take 15 minutes or more (Depending on the network bandwidth between the PC and the Gateway).
-
Once the service pack file is uploaded and the upgrade is initiated, a message will be displayed on the Management Console.
-
After the service pack is successfully applied, a message regarding this will be displayed on the Management Console.
-
Navigate to the Firmware Upgrade section under Settings > General Settings. Click View Logs to check the service pack installation logs.
Upgrading the HySecure Standby Config Node
-
Connect to the HySecure cluster manager standby node as the Security Officer (SO).
Note
Do not connect using a Virtual IP Address; ensure to use the actual IP address of the Standby node.
-
Navigate to Settings > Cluster > Manage.
-
Select Enable Maintenance mode to apply the service pack to the server.
-
Navigate to the Firmware upgrade section under Settings > General Settings.
-
Select the option Hotfix or Service pack from the Select upgrade file type, and upload the upgrade file.
-
Uploading the service pack may take 15 minutes or more (Depending on the network bandwidth between the PC and the Gateway).
-
Once the service pack file is uploaded and the upgrade begins, a message regarding this update will be displayed on the Management Console.
-
After the service pack is successfully applied, a message regarding this will be displayed on the Management Console.
-
Navigate to the Firmware upgrade section under Settings > General Settings. Click View Logs to check the service pack installation logs.
Upgrading the HySecure Active Config Node
- Connect to the HySecure cluster manager active node as the Security Officer (SO).
!!!note Do not connect using a Virtual IP Address; ensure to use the actual IP address of the Active node.
-
Navigate to Settings > Cluster > Manage.
-
Select Enable Maintenance mode.
-
Navigate to the Firmware upgrade section under Settings > General Settings.
-
Select the option Service pack from the Select upgrade file type, and upload the upgrade file.
-
Uploading the service pack may take 15 minutes or more (Depending on the network bandwidth between the PC and the Gateway).
-
Once the service pack file is uploaded and the upgrade begins, a message regarding this update will be displayed on the Management Console.
-
After the service pack is successfully applied, a message regarding this will be displayed on the Management Console.
-
Navigate to the Firmware upgrade section under Settings > General Settings. Click View Logs to check the service pack installation logs.
Disabling Maintenance Mode in the Active Config Node
-
Connect to the Active node as the Security Officer (SO).
-
Navigate to Settings > Cluster > Manage and click Disable Maintenance Mode.
Disabling Maintenance Mode in the Standby Config Node
-
Connect to the Standby node as the Security Officer (SO).
-
Navigate to Settings > Cluster > Manage and click Disable Maintenance mode.
Disabling Maintenance Mode in the Access Server Node
-
Connect to the Real node as the Security Officer (SO).
-
Navigate to Settings > Cluster > Manage and click Disable Maintenance mode.
Note
When performing any maintenance, ensure to use the actual IP addresses of the respective node.