Description
Use these instructions to download and upgrade the Access Appliance from version 7.4.2 to 7.4.2.100. For complete upgrade details, see the Veritas Access Appliance Upgrade Guide.
Product dependencies
Run the software self-test on each of the appliance nodes to verify the status of the appliance software components. Ensure that you run a self-test on each of the appliance nodes that you want to upgrade. The self-test must complete with a PASS status. For detailed instruction on how to run a self-test, refer to the Access Appliance Upgrade Guide.
Before you upgrade
EEB (Etrack 3985885)
If the Emergency Engineering Binary (EEB) to resolve security vulnerabilities for Veritas InfoScale (Etrack 3985885) is installed on Access Appliance version 7.4.2, complete the following steps:
- Uninstall the EEB (Etrack 3985885) from Access Appliance version 7.4.2.
- Upgrade the Access Appliance from version 7.4.2 to 7.4.2.100.
- Install the EEB (Etrack 3985885) again after upgrading the appliance to version 7.4.2.100.
Verify the MaxStartups attribute in the sshd configuration file
Ensure that the MaxStartups attribute in the OpenSSH Daemon (sshd) configuration file (etc/ssh/sshd_config) is set to a value that is greater than the number of service groups running on the system.
A rolling upgrade to version 7.4.2.100 might fail with the following message displayed in /log/upgrade_upgrade_log_7.4.2.*_yyyy_mm_dd if the MaxStartups attribute of sshd is set to a value that is smaller than the number of service groups running on the system:upgrade.upgrade_comm.py - DEBUG - Return value is: 255. Output is: ssh_exchange_identification: Connection closed by remote host
During an upgrade, when switching the services between the nodes, the system tries to retrieve the status of the service groups from the other node using the SSH daemon. The MaxStartups attribute defines the maximum number of concurrent unauthenticated connections to the SSH daemon. If the value of this attribute is less than the number of service groups, the SSH daemon blocks the additional connections and is unable to retrieve the status of all the service groups, which results in an upgrade failure.
To verify that the MaxStartups attribute is set to a value that is greater than the number of service groups running on the system:
1. Check the number of service groups in the cluster:
a. Open an SSH session and log on to the appliance as an administrator using the Access Appliance shell menu.
The Main_Menu view is displayed
b. To open an interactive shell menu, in the Access Appliance shell menu, enter the following command
Support > Maintenance
c. Enter the password for the Maintenance user account.
d. In the command shell, run the following command:
hagrp -list Enabled=1 | cut -f 1 | uniq | wc -l
2. Check the value configured for the MaxStartups attribute. In the command shell, run the cat /etc/ssh/sshd_config | grep MaxStartups command.
3. Update the MaxStartups attribute if its value is less than the number of service groups running on both the nodes:
a. Open the etc/ssh/sshd_config file.
b. Set the MaxStartups attribute to value that is greater than the number of service groups.
c. Restart the sshd service by running the following command
systemctl restart sshd
For example, if the value of the MaxStartups is set to 25 and the number of service groups is 36, update the value of MaxStartups to a value that is greater than 36.
About the Veritas Access 3340 Appliance upgrade
Veritas Access 3340 Appliance supports the following upgrade methods:
- Rolling upgrade: Use this method if the Veritas Access 3340 Appliance is configured and the
- Node-by-node upgrade: Use this method if the appliance nodes are in factory state.
Note: The appliance nodes that are in the Not in Access cluster state cannot be upgraded. You can reset a node to the default factory settings, and then upgrade the node.
Downloading the appliance software release updates
Appliance software updates can be downloaded by using the Access Appliance shell menu or manually through a share. Updates must be downloaded to the appliance before you start the upgrade.
- For a rolling upgrade, download the software upgrade package to one of the nodes in the cluster.
-
Downloading software updates directly to an Access 3340 appliance node using the Access Appliance shell menu
Use this procedure to download the VRTSaccess-app-update-7.4.2.1-1.x86_64.rpm to the appliance node:
1. Open an SSH session and log on to the appliance as an administrator using the Access Appliance shell menu.
The Main_Menu view is displayed.
2. To determine if a software update is available from the Veritas Support website, enter the following command:
Main_Menu > Manage > Software > List AvailablePatch
The software release update that is available for installation is displayed. Note the name of the software release update package. For example, VRTSaccess-app-update-7.4.2.1-1.x86_64.rpm
3. To download the available software update, enter the following command:
Main_Menu > Manage > Software > Download update_name
where update_name is the name of the software release update package.
For example:
Main_Menu > Manage > Software > Download VRTSaccess-app-update-7.4.2.1-1.x86_64.rpm
4. To verify that the software update has downloaded successfully, enter the following command:
Main_Menu > Manage > Software > List Downloaded
The downloaded software update is validated and details such as the patch name, size, and version are displayed.
Downloading software updates to an Access 3340 appliance node using a client share
Use this procedure to download the software release update to an appliance node using a CIFS or an NFS share. The software update file is split into three tar files, which you need to download from the Veritas SORT website (See "Download links for Access Appliance software updates").
1. If not already done so, open an SSH session and log on to the appliance as an administrator using the Access Appliance Shell Menu.
2. To open an NFS or a CIFS share, enter the following command:
Main_Menu > Manage > Software > Share Open
Note: If you experience a 'time-out' or 'denied' error when mounting the NFS share on your client computer, refer to the Veritas Access 7.3.2 Release Notes (SORT website) for details about how to bring the NFS server online.
3. Mount the appliance share directory as follows:
For a Linux NFS share:
mkdir -p /mount/Node_management_IP
mount Node_management_IP:/inst/patch/incoming /mount/Node_management_IP
where Node_management_IP is the IP address that is assigned to eth1 of each node.
For a Windows CIFS share:\\Node_management_IP\incoming_patches
where Node_management_IP is the IP address that is assigned to eth1 of each node.
Note: Use the appliance admin user credentials to map a share directory for CIFS.
4. Download the upgrade package files and the MD5 and SHA1 checksums.
- Release updates: Refer the links in attachments section to download the split tar files form the Veritas SORT website.
- MD5 and SHA1 checksums: Refer the links in attachments section to download a text file that contains the MD5 and SHA1 checksums.
Verify that the downloaded MD5 or SHA1 checksums match those in the file on the Veritas SORT website.
5. Use the following command to merge and extract the release update .rpm files:
copy /b VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.1of3+VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.2of3+VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.3of3 VRTSaccess-app-N-7.4.2.1-1.x86_64.tar
Note: Enter this command as a single string. Ensure that the only space in the name is after .3of3.
Use the Windows WinRAR utilities to extract the contents of the VRTSaccess-app-N-7.4.2.1-1.x86_64.tar file.
The resulting files are:
VRTSaccess-app-update-7.4.2.1-1.x86_64.rpm
update.rpm.md5_checksum
update.rpm.sha1_checksum
For Linux:
cat VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.1of3 VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.2of3 VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.3of3 | tar xvf -
The resulting files are:
VRTSaccess-app-update-7.4.2.1-1.x86_64.rpm
update.rpm.md5_checksum
update.rpm.sha1_checksum
6. Run one of the following commands to compute the checksum of the rpm file:
md5sum VRTSaccess-app-update-7.4.2.1-1.x86_64.rpm
sha1sum VRTSaccess-app-update-7.4.2.1-1.x86_64.rpm
7. Copy this release update to the mounted share.
Note: To avoid any issues, ensure that you do not run commands on the appliance nodes when you copy the update.
8. Unmount the shared directory after copying the update.
9. Close the NFS and the CIFS shares by using the command:
Main_Menu > Manage > Software > Share Close
10. List the downloaded files by using the command:
Main_Menu > Manage > Software > List Downloaded
The downloaded update is validated and details such as the patch name, size, and version are displayed.
Upgrading Access 3340 Appliance version 7.4.2 to 7.4.2.100
- For a rolling upgrade, install the software update on the node where you downloaded the upgrade package.
- For a node-by-node upgrade, install the software update on each node that you want to upgrade.
To install the downloaded software release update, complete the following steps:
1. Connect to the Intelligent Platform Management Interface (IPMI) console of the node where you downloaded the software update package.
Note: Veritas recommends that you log in using the Access Appliance Shell Menu from the IPMI console instead of an SSH session. The IPMI console is also known as the Veritas Remote Management Console. For details about how to access and use the Veritas Remote Management Console, refer to the Veritas Access Appliance Initial Configuration Guide.
2. Log in to the Access Appliance Shell Menu.
3. To install the software release update, run the following command:
Main_Menu > Manage > Software > Install patch_name
where patch_name is the name of the software release update that you want to install.
A summary of the upgrade changes is displayed and you are prompted for confirmation. Review the details and type yes to continue.
4. Monitor the preflight check and check if any Check failed messages are displayed. After the preflight check completes, you have the following options:
- If Check failed messages are not displayed and the preflight check completes successfully, the Pre-flight check finished successfully message is displayed and you are prompted to continue to the next step.
- If a Check failed message is displayed, the upgrade cannot continue. You must resolve the reported failures, and then install the update again (see step 3) so that the preflight check can verify that the failures have been resolved. For information about how to resolve the reported issues, refer to the technical articles corresponding to the displayed UMI codes (V-409-xxx-xxxx).
5. When the following message is displayed and you are promoted for confirmation, type yes to continue:
This software update requires a reboot of the appliance after the installation process completes. Do you want to continue? (yes/no)
6. To check the upgrade status, run the following command:
Main_Menu > Manage > Software > UpgradeStatus
The details about the completed tasks and the completion status are displayed.
If the upgrade fails at any point in time, error messages and the details about possible solutions are displayed and a rollback operation is initiated automatically. After the rollback is completed successfully, the Completed the rollback operation. Run the 'Support> Test Software' command to verify if all the services are up. message is displayed.
If the software update is installed successfully, the following message is displayed:
This appliance node is not in upgrade state.
To ensure that the appliance is upgraded successfully, run the Main_Menu > Appliance > Status command and verify the Access version and the appliance version.
Download links for Access Appliance software updates
Click the following links to download the Access Appliance software version 7.4.2.100 updates:
VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.1of3
VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.2of3
VRTSaccess-app-N-7.4.2.1-1.x86_64-tar-split.3of3
Access_Appliance_Release_7421_MD5_SHA1.txt
References
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.