Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Flex Appliance 3.0 new features, enhancements, and changes
- Flex Appliance 3.1 new features, enhancements, and changes
- Flex Appliance 3.2 new features, enhancements, and changes
- Flex Appliance 3.3 new features, enhancements, and changes
- Supported upgrade and update paths to this release
- Operational notes
- Flex Appliance 3.0 release content
- Flex Appliance 3.1 release content
- Flex Appliance 3.2 release content
- Flex Appliance 3.3 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
- 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
- Editing a remote user domain in the Flex Appliance Console
- Importing a remote user or user group to the Flex Appliance Console
- Managing single sign-on (SSO)
- Managing identity providers (IDPs)
- Importing a single sign-on user or user group to the Flex Appliance Console
- Managing user authentication with smart cards or digital certificates
- Changing a local user password in the Flex Appliance Console
- Expiring local user passwords in the Flex Appliance Console
- Unlocking a local user account in the Flex Appliance Console
- Removing users from the Flex Appliance Console
- Changing the password policy
- 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 updates
- Appliance security
- Monitoring the appliance
- Registering an appliance
- Configuring alerts
- Monitoring the appliance from the System Health Insights portal
- Viewing the hardware status
- Viewing hardware faults
- Viewing system data
- Clearing the hardware status
- Forwarding logs
- Providing access for external monitoring
- Revoking access for external monitoring
- Reconfiguring the appliance
- Troubleshooting guidelines
Flex Appliance 3.2 release content
The following list contains the known issues that were fixed and that are included in the Flex Appliance 3.2 release:
A known issue could occur when you tried to delete an application instance on a multi-node appliance. The following error message displayed in the Activity Monitor:
"Failed to delete instance. Check /var/log/nodeworker/worker.log and VCS logs for more details."
Performing a power cycle from the Veritas Remote Management Interface caused system downtime.
If you added a node to the appliance and did not use DNS, you needed to restart the infrastructure services after you added the hostname resolution information for the new node to the appliance Hosts file.
If you did not use DNS and you configured email alerts or configured Call Home with a proxy server, the alert tests failed, and alerts were not sent.
If you configured a Fibre Channel port in target mode and then changed it to initiator mode, a message should have appeared that advised you to rescan the ports. However, the message did not appear.
If you tried to remove a node that crashed or was no longer working, the removal failed with the following message:
"Unable to remove node because an appliance update is in progress or pending. Complete the update, then commit or roll back. If any of these operations did not complete successfully, you must resolve the errors before you can remove a node."
If you had a multi-node appliance and updated one of the nodes but had not updated the other node, the following message appeared on the Flex Appliance Console:
"V-492-100-505: Internal server error occurred"