Veritas Flex Appliance Getting Started and Administration Guide

The following list contains the notes and the known issues that apply for the Flex Appliance 2.1 software:

• When you upgrade and commit to version 2.1, the Flex Appliance Console shows an error displaying the node information for a couple minutes after the commit. The error resolves on its own once all services are online. If you see node errors, wait a couple minutes and check again.

• During an instance upgrade, an issue can occur that causes the following error to display in the Activity Monitor:

  "Create snapshot failed with error exec: Stdout already set"

  This issue is fixed in the 2.1.1 update. If you encounter this issue in version 2.1, retry the upgrade. If the problem persists, restart all nodes on the appliance and try again.

• When you create an instance or configure a proxy server for Call Home, an issue can occur with the file uploads if you upload a file with incorrect data. If you edit the file to correct the issue and then attempt to upload it again, the upload still fails.

  This issue is fixed in the 2.1.1 update. If you encounter this issue in version 2.1, exit the operation and start it again.

• The set alerts hardware-threshold command was added this release to set threshold values for alerts. However, alerts are not currently sent for the metrics that can be set with this command.

• The support data-collect command may show the following error:

  "*** Error in `qaucli': double free or corruption"

  This error can be safely disregarded. The command still generates a DataCollect package.

• During an instance upgrade on a Veritas 5150 Appliance, the upgrade precheck may fail with the following error message:

  "V-492-101-102: Not enough space; request size of 256000 MB is greater than remaining space of <available space> MB. The log volume and the internal data volumes are included in space calculations."

  If you encounter this issue, resize one or more of your application instances to make sure that there is 250 GB of available storage space. Then retry the upgrade.

• During a firmware upgrade, an issue can occur with the storage shelf controller that causes an upgrade failure message to appear. If you see a failure message, it may have appeared in error, and the upgrade may still have worked. Run the following command to confirm the firmware version:

  show hardware-health primaryshelf component=controller

• If you upgrade to version 2.1 and then roll back, an issue can occur that causes the Flex Appliance Console to be unable to load. If you encounter this issue, restart all appliance nodes and then try again to access the console.

  Warning:

  If you have a multi-node appliance, do not restart both nodes at the same time.

• For this release, while an update is in progress, do not perform any other operations in the Flex Appliance Shell or the Flex Appliance Console.

• If you change the BIOS date and time on a Veritas 5250 Appliance after initial configuration, you can no longer access the Flex Appliance Console.

  This issue is fixed in the 2.1.1 update. If you encounter this issue in version 2.1, change the BIOS date and time back to what it was before.

• When you create a bond, do not give it a bond name that is all numbers. If you do so, you can no longer create any additional bonds on the appliance.

  If you were not aware of this limitation and have already created a bond name that is all numbers, contact Technical Support for assistance. Ask your representative to reference article 100050464.

• Accelerator backups on Flex Appliance application instances fail if there is not enough space for the logs. For example, the logs for NDMP backups could require up to a Terabyte of storage space.

  On a primary server instance, the logs are stored in the same location as the NetBackup catalogs. To resolve this issue on a primary server instance, resize the NetBackup catalog and make sure to allocate enough storage for the Accelerator logs as well.

  On a media server instance, the logs are stored in the /mnt/nblogs directory, which has a default size of 250 GB. This directory cannot currently be resized through the Flex Appliance Console.

  On version 2.1.1, you can resize the directory with the PUT /instances/<instance-id>/volumes API. See the Flex Management Server API documentation on Veritas SORT for details.

  If you are on version 2.1, contact Veritas Support and ask your representative to reference article 100049971 to resize the directory.

• Due to an underlying performance issue, the monitoring and alerting feature for the ROC Temperature (RAID on Chip for RAID Adapters) is disabled in this release for the Veritas 5250 Appliance. This feature will be reinstated and available for 5250 models in a future software release.

• When you install application add-ons on an instance, the Flex Appliance Console lets you select different versions of the same OST plug-in. However, this configuration is not supported, and if you select more than one version of the same plug-in, the Install add-ons page shows duplicate entries. Only install one version of each OST plug-in on an instance. If you need to change the version of an OST plug-in that is already installed, first uninstall it, and then install the new version.

• If the host0 or host1 port is not connected to the appliance node during initial configuration, the following error message appears that does not provide complete information:

  "Network card for <interface name> is missing. Make sure that all network interfaces are connected to the appliance."

  If you encounter this message, verify that all ports are connected according to the initial configuration guidelines. See Initial configuration guidelines and checklist. Then restart the node to continue the configuration.

• When you create a new application instance, the Application instances section of the System topology page may show the instance status as Partially Deleted while the creation is in progress. The Partially Deleted status displays in error and can be safely ignored. You can track the instance creation progress from the Activity Monitor, and the instance status changes to Online when the instance creation has completed successfully.

• If you have a tenant whose name or location contains special characters when you upgrade to version 2.1, tenant operations fail after the upgrade. To resolve this issue, edit the tenant name and location so that they do not have special characters.

• The following error message may display in the Flex Appliance Shell during an upgrade or a factory reset:

  dracut:Failed to install module bnx2

  This message displays in error and can be safely disregarded.

• If you have a multi-node appliance and one of the nodes is turned off for any reason, do not restart the other node until they are both online. If a node is restarted while the other node is off, the Flex Appliance Console fails to load.

  If you encounter this scenario, contact Veritas Technical Support and ask your representative to reference articles 100046118 and 100051413.

• When you create an instance, if you enter the IP address before you select a network interface, the IP address field displays the following error message:

  "IP address does not belong to the selected network's subnet."

  This message still displays after you select the network interface that corresponds to the IP address. To clear the message, click inside the IP address field and then click or tab outside of it.

• After some operations in the Flex Appliance Shell, an "Operation successfully" message may display even if a failure occurred. Read all of the messages that display at the end of each task to make sure that no further action is required.