Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Release notes
- Flex Appliance 4.0 new features, enhancements, and changes
- Flex Appliance 4.1 new features, enhancements, and changes
- Flex Appliance 4.2 new features, enhancements, and changes
- Supported update paths to this release
- Operational notes
- Flex Appliance 4.0 release content
- Flex Appliance 4.1 release content
- Flex Appliance 4.2 release content
- Getting started
- Managing network settings for instances
- Managing users
- Overview of the Flex Appliance default users
- Managing Flex Appliance Console users and tenants
- Adding a tenant
- Editing a tenant
- Removing a tenant
- Adding a local user to the Flex Appliance Console
- Connecting a remote user domain to the Flex Appliance Console
- Editing a remote user domain in the Flex Appliance Console
- Importing a remote user or user group to the Flex Appliance Console
- Managing single sign-on (SSO)
- Managing identity providers (IDPs)
- Importing a single sign-on user or user group to the Flex Appliance Console
- Managing user authentication with smart cards or digital certificates
- Changing a local user password in the Flex Appliance Console
- Expiring local user passwords in the Flex Appliance Console
- Unlocking a user account in the Flex Appliance Console
- Removing users from the Flex Appliance Console
- Changing the password policy
- Changing the hostadmin user password in the Flex Appliance Shell
- Changing the sysadmin user password in the Veritas Remote Management Interface
- Managing multifactor authentication
- Using Flex Appliance
- Managing the repository
- Creating application instances
- Managing application instances from Flex Appliance and NetBackup
- Managing application instances from Flex Appliance
- Resizing instance storage
- Editing instance network settings
- Assigning Fibre Channel ports to an instance
- Unassigning Fibre Channel ports from an instance
- Managing application add-ons on instances
- Viewing instance performance metrics
- Clearing a configuration error status on an application instance
- Deleting an application instance
- Upgrading application instances
- Updating an application instance to a newer revision
- About Flex Appliance updates
- Remote replication
- About remote replication
- Pairing appliances for remote replication
- Creating a replica
- Managing remote replication
- Remote replication best practices
- Monitoring remote replication
- Editing the replication network
- Repairing a lost connection between paired appliances
- Pausing and resuming replication
- Resolving discrepancies between an active and a replica instance
- Changing the replication role of an instance
- Unlinking active and replica instances
- Forgetting a paired appliance
- Appliance security
- Monitoring the appliance
- Registering an appliance
- Configuring alerts
- Monitoring the appliance from the System Health Insights portal
- Viewing the hardware status
- Viewing hardware faults
- Viewing system data
- Clearing the hardware status
- Forwarding logs
- Providing access for external monitoring
- Revoking access for external monitoring
- Reconfiguring the appliance
- Reconfiguring the appliance network
- Changing DNS or Hosts file settings
- Shutting down the appliance
- Performing a factory reset
- Performing a reimage
- Recovering storage data after a factory reset or a reimage
- Performing a storage reset
- Removing a node
- Viewing or resetting the storage shelf order on a Veritas 52xx Appliance
- Troubleshooting guidelines
Operational notes
This topic explains important aspects of Flex Appliance 4.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 4.x software:
After a new installation or an upgrade to version 4.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.0.0.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.
If you have a multi-node appliance with remote replication configured, and a replication error occurs, you may receive a separate alert for the same issue on each node. In addition, if the system is down on one of the nodes when the issue is resolved, you may not receive an email to notify you of the fix until that node is back online.
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 or 10.0.0.1, you must install an EEB on the instance.
You can find the EEBs at the following locations:
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.
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.
When the rsyslogs service starts, messages that include the text avc: denied and comm="(rsyslogd)" may appear in the logs at
/var/log/audit/audit.log. The rsyslog service starts when the appliance starts up or when another service that uses it restarts.The messages look similar to the following:
node=localhost.localdomain type=AVC msg=audit(1700916265.786:623): avc: denied { mounton } for pid=57833 comm="(rsyslogd)"
These messages can be ignored.
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 issue is fixed in version 4.2.
On earlier versions, this task displays in error and can be ignored. It has no impact on the generation of the log package.
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.
This issue is fixed in version 4.2.
To work around this issue on an earlier version, you must also enter a new size. Once the unit has updated, you can change the size back to the previous value if needed.
If you change the threshold for high disk usage alerts, the Flex Appliance Shell lets you set the warning threshold up to 93%. However, the critical threshold that cannot be changed is 90%.
This issue is fixed in version 4.1.
On version 4.0, do not set the warning threshold above 89%.
If a remote replication alert is not resolved before you forget the paired appliance, the alert remains in the alert summary.
This issue is fixed in version 4.1.
To clear the alert on version 4.0, refer to the following article: How to clear an unresolved remote replication alert after forgetting an appliance
If you try to create a replica instance, but the appliance with the active instance does not have enough storage space, the replica creation fails but does not include the reason for the failure.
This issue is fixed in version 4.1.
If you experience an undefined failure when you try to create a replica on version 4.0, you can check the logs for more information. To do so, run the support shell command in the Flex Appliance Shell and then run the following commands:
vi /var/log/nodeworker/inframodule.log
vi /var/log/nodeworker/worker.log
Check the logs for the following message:
V-492-101-102: Not enough space; request size of <requested space> MiB is greater than remaining space of <available space> MiB. The log volume and the internal data volumes are included in space calculations.