Veritas Flex Appliance Getting Started and Administration Guide

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

• Once you upgrade to version 3.x, SAN client (Fibre Transport Media Server) backups no longer work on NetBackup application instances earlier than version 10.1. To use SAN client on earlier versions, you must install an EEB on versions 10.0.0.1 and 9.1.0.1. Versions other than 10.0.0.1 and 9.1.0.1 do not have an EEB and must be upgraded before you can install the EEB.

  You can find the EEBs at the following locations:

  • Version 10.0.0.1

  • Version 9.1.0.1

  Veritas recommends that you install the EEB before you upgrade the appliance to version 3.x so that scheduled backups are not interrupted.

• Once you upgrade to version 3.x, universal shares no longer work on NetBackup application instances earlier than version 10.1.1. To use universal shares on earlier versions, you must install an EEB on versions 10.1, 10.0.0.1, and 9.1.0.1. Versions other than 10.1, 10.0.0.1, and 9.1.0.1 do not have an EEB and must be upgraded before you can install the EEB.

  You can find the EEBs at the following locations:

  • Version 10.1

  • Version 10.0.0.1

  • Version 9.1.0.1

  Veritas recommends that you install the EEB before you upgrade the appliance to version 3.x so that scheduled backups are not interrupted.

• NetBackup 10.3 is not supported on Flex Appliance 3.x.

• When you access the Flex Appliance Shell through the Veritas Remote Management Interface, do not enter alt+PrtScn while a command is running. If you do, the command fails, and it still may not work when you try to rerun it.

• When you create an instance, if you change the unit for a volume in the Storage section but do not enter a new size, the unit does not update. To work around this issue, you must also enter a new size. Once the unit has updated, you can change the size back to the previous value if needed.

• For this release, the audit log may include incorrect username or group name values for user identifiers (for example, UID and GUID). The log shows the values for the user IDs or group IDs on the appliance instead of the user IDs or group IDs on the application instance.

• If you generate a Data Collect log package and stay on the Activity Monitor page for more than 15 minutes, you may see a new task appear on the monitor page. The new task stops immediately with the following message:

  "A Data Collect operation is already in progress. Retry after the task is completed."

  This task displays in error and can be ignored. It has no impact on the generation of the log package.

• The Linux Ispci utility shows an incorrect model number for the SAS storage controller. You can see the correct model number with the hardware-health commands in the Flex Appliance Shell.

• If you make configuration changes on the appliance while an update is in progress, the update may fail. To avoid this issue, do not make configuration changes or run the system restart command until the update is fully complete. If you were not aware of this issue and have encountered it, rerun the update to resolve it.

• For this release, the Alt + s shortcut in the Flex Appliance Shell is not enabled.

• When you add a node to the appliance either during initial configuration or after, the system self-test command fails on the new node if you run it before you run setup add-node. The following error appears:

  "Hostagent must not be active on unconfigured appliance"

  If you see this error in this scenario, it can be ignored. Run setup add-node to finish adding the node and then run system self-test again.

• For this release, the Performance graphs on the Flex Appliance Console Home page show data only in the UTC time zone.

• On a multi-node appliance, an issue can occur if you remove a node while that node is powered off. If the node comes back online before you have restarted the appliance, the removed node is added back to the appliance. If you experience this issue, remove the node again and then immediately restart the appliance.

• When you run the following commands, messages that include the text avc: denied and comm='iptables' or comm='ip6tables' may appear in the logs at /var/log/audit/audit.log:

  • setup configure-console

  • system restart

  • system appliance-recover

  • systemctl restart system-hostnamed

  • hostnamectl

  The messages look similar to the following:

  node=localhost.localdomain type=AVC msg=audit(1668166429.323:16048): avc: denied { ioctl } for pid=612229 comm="iptables"

  These messages can be ignored.

• Alerts are not currently sent for the metrics that can be set with the set alerts hardware-threshold 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 Data Collect package.

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

  show hardware-health primaryshelf component=controller

• 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.

• 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 configure or change the configuration of a Call Home proxy server, the event does not display correctly in System Health Insights. The Severity column on the Events page shows as Unknown. You can ignore this status.

  This issue is fixed in version 3.3.

• A known issue can occur when you try to delete an application instance on a multi-node appliance. The following error message displays in the Activity Monitor:

  "Failed to delete instance. Check /var/log/nodeworker/worker.log and VCS logs for more details."

  This issue is fixed in version 3.2. To avoid this issue on earlier releases, relocate the instance to the other node before you delete it.

  If you were not aware of this issue and encounter it, contact Veritas Technical Support for assistance and ask your representative to reference article 100054665.

• Performing a power cycle from the Veritas Remote Management Interface can cause system downtime.

  This issue is fixed in version 3.2. If you need to restart the appliance on earlier releases, run the system restart command from the Flex Appliance Shell.

• For versions 3.0 and 3.1, if you add a node to the appliance and do not use DNS, you must perform the following steps after you add the hostname resolution information for the new node to the appliance Hosts file:

  • Log in to the Flex Appliance Shell from the preexisting node that was already part of the appliance.

  • Run the following command:

    system ha-service restart service=infra_svc node=<node hostname>

    Where <node hostname> is the hostname of the node that you are logged in to.

  Perform these steps after you run the system add-host command and before you run the setup add-node command. You do not need to perform these steps on version 3.2 and later.

• If you do not use DNS and you configure email alerts or configure Call Home with a proxy server, the alert tests fail, and alerts are not sent.

  This issue is fixed in version 3.2. To resolve this issue on earlier releases, perform the following steps after you configure the alerts:

  • Log in to the Flex Appliance Shell and run the following command:

    system add-host

  • Enter the required information for the SMTP server or the Call Home proxy server.

  • Run the following commands:

    system os-service restart service=autosupport

    system ha-server restart service=infra_svc node=<node hostname>

    Note:

    If you have a multi-node appliance, you must run these two commands on both nodes.

• If you configure a Fibre Channel port in target mode and then change it to initiator mode, a message should appear that advises you to rescan the ports. However, the message does not appear in versions 3.0 and 3.1. If you change a port from target mode to initiator mode, make sure that you rescan the ports after the change to discover all devices.

• If you try to remove a node that has crashed or is no longer working, the removal may fail 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."

  This issue is fixed in version 3.2. If you encounter this scenario on an earlier release, retry the remove node operation.

• If you have a multi-node appliance and update one of the nodes but have not updated the other node, the following message may appear on the Flex Appliance Console:

  "V-492-100-505: Internal server error occurred"

  This issue is resolved in version 3.2. On earlier versions, this message can be ignored. To remove the message, update the other node.