Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- 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 upgrades and updates
- Appliance security
- Monitoring the appliance
- Reconfiguring the appliance
- Troubleshooting guidelines
Flex Appliance 2.0 release content
The following list contains the known issues that were fixed and that are now included in this release of Flex Appliance.
The Flex Appliance Shell let you log in using the IP address that you set for the Flex Appliance Console even though logging in to the shell with the console IP address is not supported.
If you created a bond with a bond name that was all numbers, you could no longer create any additional bonds on the appliance.
If you edited the MTU value of a network interface, the change was not preserved if the node restarted.
If you removed a node from a multi-node appliance and then performed a factory reset on the node that you removed, the factory reset failed with the following error:
Installing VxOS (Note - May take up to 15 minutes) [FAILED] Task Name: Generating boot configuration Error: "AnsibleUndefinedVariable: 'kernel_map' is undefined"
If Call Home was enabled but was unable to communicate with the AutoSupport server due to a firewall, the set alerts email-smtp and delete alerts email-smtp commands took more than a minute to complete.
If more than one user edited the network of an instance from the Flex Appliance Console at the same time, the second user's changes overwrote the first user's changes.