Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Getting started
- Managing network settings for instances
- Managing users
- Managing Flex Appliance Console users and tenants
- Managing multifactor authentication
- Using Flex Appliance Console accounts for API automation
- Using Flex Appliance
- Managing the repository
- Managing application instances from Flex Appliance
- Managing application add-ons on instances
- Upgrading application instances
- About Flex Appliance updates
- Remote replication
- Managing remote replication
- Appliance security
- Monitoring the appliance
- Configuring alerts
- Viewing the hardware status
- Reconfiguring the appliance
- Troubleshooting guidelines
Operational notes
This topic explains important aspects of Flex Appliance 5.x operations that may not be documented elsewhere in the documentation.
The following list contains the notes and the known issues that apply for the Flex Appliance 5.x software:
When you edit the roles for a user and select a base role, some of the extended roles are grayed out. These extended roles are included as part of the selected base role.
During a factory reset, error messages similar to the following may display before the node is restarted:
err: Cannot open Packages using index using db5 - Permission denied (13)
err: Cannot open Packages in database /var/lib/rpm
These messages display in error and can be ignored.
If you shut down both nodes of a multi-node appliance after an update but before you have committed or rolled back, an issue can occur that causes the appliance to be in an unusable state.
This issue is fixed in version 5.1.
To avoid this issue on version 5.0, do not shut down both nodes until you have committed or rolled back. If you were not aware of this issue and have encountered it, contact Veritas Technical Support for assistance. Ask your representative to reference article 100068050.
If you generate a Data Collect log package with data masking enabled, the
private_map
file that is included uses the same key value for multiple entries.After a new installation or an upgrade to version 5.x, SAN client (Fibre Transport Media Server) backups do not work on NetBackup application instances earlier than version 10.3. To use SAN client on an earlier supported version, you must install an EEB. Versions earlier than 10.1.1 must be upgraded before you can install the EEB.
You can find the EEBs at the following locations:
Note:
Update the appliance before you upgrade the instance or install the EEB.
When you restart the appliance, the network interfaces temporarily go down and then come back up. Due to this behavior, a failed "Clear state" task sometimes displays in the Activity Monitor, indicating that the network interface is down. If you see this failed task, check the Network interfaces page. If the interface shows as UP, you can ignore the failed task.
To use universal shares on NetBackup 10.1, you must install an EEB on the instance.
You can find the EEB at the following location: Version 10.1
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 Deleted while the creation is in progress. The 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.