Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Getting started
- Managing network settings
- Managing users
- Managing Flex Appliance Console users and tenants
- Using Flex Appliance
- Managing the repository
- Managing application instances from Flex Appliance
- Upgrading application instances
- About Flex Appliance updates
- Appliance security
- Monitoring the appliance
- Configuring alerts
- Viewing the hardware status
- Reconfiguring the appliance
- Troubleshooting guidelines
Flex Appliance 3.0 release content
The following list contains the known issues that were fixed and that are now included in this release of Flex Appliance:
When you upgraded and committed to the upgraded version, the Flex Appliance Console showed an error displaying the node information for a couple minutes after the commit. The error resolved on its own once all services were online.
When you created an instance or configured a proxy server for Call Home, an issue could occur with the file uploads if you uploaded a file with incorrect data. If you edited the file to correct the issue and then attempted to upload it again, the upload still failed.
If you upgraded the appliance and then rolled back, an issue could occur that caused the Flex Appliance Console to be unable to load.
On a multi-node appliance, if a node was restarted while the other node was off, the Flex Appliance Console failed to load.
When you created an instance, if you entered the IP address before you selected a network interface, the IP address field displayed the following error message:
"IP address does not belong to the selected network's subnet."
This message still displayed after you selected the network interface that corresponded to the IP address.
If you created a bond with a bond name that was all numbers, you could no longer create any additional bonds on the appliance.