Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Getting started
- Managing network settings for instances
- 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 user account in the Flex Appliance Console
- Managing open sessions
- Removing user or service accounts 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
- Managing multifactor authentication
- Using Flex Appliance Console accounts for API automation
- 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
- Changing the BIOS password
- Locating the node serial number
- Remote replication
- About remote replication
- Pairing appliances for remote replication
- Creating a replica
- Managing remote replication
- Remote replication best practices
- Monitoring remote replication
- Editing the replication network
- Repairing a lost connection between paired appliances
- Pausing and resuming replication
- Resolving discrepancies between an active and a replica instance
- Changing the replication role of an instance
- Unlinking active and replica instances
- Forgetting a paired appliance
- Appliance security
- Monitoring the appliance
- Registering an appliance
- Configuring alerts
- Viewing performance metrics
- 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
- Reconfiguring the appliance network
- Changing DNS or Hosts file settings
- Shutting down the appliance
- Performing a factory reset
- Performing a reimage
- Recovering storage data after a factory reset or a reimage
- Performing a storage reset
- Removing a node
- Viewing or resetting the storage shelf order on a Veritas 52xx Appliance
- Troubleshooting guidelines
Flex Appliance 6.0 release content
The following list contains the known issues that were fixed and that are now included in this release of Flex Appliance:
During a factory reset, error messages similar to the following may have displayed before the node was restarted:
err: Cannot open Packages using index using db5 - Permission denied (13)
err: Cannot open Packages in database /var/lib/rpm
When you restarted the appliance, a failed "Clear state" task sometimes displayed in the Activity Monitor, indicating that the network interface was down.
On a multi-node appliance, an issue could occur if you removed a node while that node was powered off. If the node came back online before you had restarted the appliance, the removed node was added back to the appliance.
When you ran the following commands, messages that included the text avc: denied and comm='iptables' or comm='ip6tables' may have appeared in the logs at
/var/log/audit/audit.log:setup configure-console
system restart
system appliance-recover
systemctl restart system-hostnamed
hostnamectl
The support data-collect command may have shown the following error:
"*** Error in `qaucli': double free or corruption"
When you created a new application instance, the Application instances section of the System topology page may have shown the instance status as Deleted while the creation was in progress.