Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Flex Appliance 2.1 new features, enhancements, and changes
- Flex Appliance 2.1.1 new features, enhancements, and changes
- Flex Appliance 2.1.2 new features, enhancements, and changes
- Flex Appliance 2.1.3 new features, enhancements, and changes
- Flex Appliance 2.1.4 new features, enhancements, and changes
- Supported upgrade paths to this release
- Operational notes
- Flex Appliance 2.1 release content
- Flex Appliance 2.1.1 release content
- Flex Appliance 2.1.2 release content
- Flex Appliance 2.1.3 release content
- Flex Appliance 2.1.4 release content
- Getting started
- Initial configuration guidelines and checklist
- Performing the initial configuration
- Adding a node
- Accessing and using the Flex Appliance Shell
- Accessing and using the Flex Appliance Console
- Managing the appliance from the Appliance Management Console
- Setting the date and time for appliance nodes
- Common tasks in Flex Appliance
- Managing network settings
- Managing users
- Overview of the Flex Appliance default users
- Changing the password policy
- Managing Flex Appliance Console users and tenants
- Adding a tenant
- Editing a tenant
- Removing a tenant
- Adding a local user to the Flex Appliance Console
- Connecting a remote user domain to the Flex Appliance Console
- Importing a remote user or user group to the Flex Appliance Console
- Editing a remote user domain in the Flex Appliance Console
- Changing a local user password in the Flex Appliance Console
- Expiring local user passwords in the Flex Appliance Console
- Removing users from the Flex Appliance Console
- Managing user authentication with smart cards or digital certificates
- Changing the hostadmin user password in the Flex Appliance Shell
- Changing the sysadmin user password in the Veritas Remote Management Interface
- Using Flex Appliance
- Managing the repository
- Creating application instances
- Managing application instances from Flex Appliance and NetBackup
- Managing application instances from Flex Appliance
- Upgrading application instances
- Updating an application instance to a newer revision
- About Flex Appliance upgrades and updates
- Appliance security
- Monitoring the appliance
- Reconfiguring the appliance
- Troubleshooting guidelines
Updating the firmware
Use the following procedure to update the appliance firmware.
If you make any hardware changes after you install a firmware update, make sure that you install the update again for the new hardware.
To update the firmware
- On the Flex Appliance Console, click the Repository icon in the left-side navigation bar and navigate to the Appliance updates tab.
- Make sure that the update package you want to use is located in the repository. See Managing the repository.
- Navigate to System topology > Application instances to check the status of the application instances.
- Do one of the following:
If you have a single-node appliance, stop all running instances.
If you have a multi-node appliance, stop all running instances or select the node that you want to update first and relocate all of its instances to the other node.
- Return to the Appliance updates tab on the Repository page. Select the node that you want to update and click Update or Update and restart. If you already updated the firmware and want to update it again because of new hardware, the options are Update again or Update again and restart.
If the update requires a restart, you can monitor the restart progress from the Veritas Remote Management Interface. However, the interface briefly becomes unavailable during the update. To access the Veritas Remote Management Interface, refer to the initial configuration procedure. See Performing the initial configuration.
Warning:
Do not start any application instances while the update is in progress.
- When the update process is done, refresh your browser cache and sign back in to the Flex Appliance Console.
- If you have a multi-node appliance, stop or relocate all instances on the other node.
Then repeat the update on the other node.