Veritas Flex Appliance Getting Started and Administration Guide
- Product overview
- Getting started
- Modifying settings
- Managing users
- Using Flex Appliance
- Managing applications and upgrade packages in the repository
- Creating application instances
- Managing application instances
- Monitoring the appliance
- About AutoSupport and Call Home
- Monitoring the hardware from the Flex Appliance Shell
- Reconfiguring the appliance
- Troubleshooting guidelines
This topic explains important aspects of Flex Appliance 1.1 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 1.1 software:
If you run the system self-test on an appliance that has not been configured yet, you may see the following error messages:
Error: Failed services found! - ' UNIT LOAD ACTIVE SUB DESCRIPTION' - \u25cf gab.service loaded failed failed VERITAS Group Membership and Atomic Broadcast(GAB) - \u25cf llt.service loaded failed failed VERITAS Low Latency Transport (LLT) - \u25cf vxfen.service loaded failed failed VERITAS I/O Fencing (VxFEN)
These messages can be safely disregarded. Proceed with the initial configuration, and they should not display again when the configuration is complete.
When multiple NetBackup application instances are running on a Flex appliance with a high number of MSDP backup jobs, the backups can fail due to memory allocation errors. The Activity Monitor in the NetBackup Administration Console shows job failures with status codes 83, 89, 11, and 27.
If you plan to run multiple MSDP instances on the appliance with a high number of backup jobs or if you encounter this issue, contact Veritas Technical Support to implement a workaround. Ask your representative to reference article 100044080.
When you create an instance, the new instance displays on the System Topology page after step 3 of the creation process, as seen from the Activity Monitor. If the instance creation fails during step 4, an error appears on the Activity Monitor, but the System Topology page shows the instance with an ONLINE status. If you encounter this issue, you can refer to the error message to fix the instance failure, or you can delete the instance from the System Topology page and try again.
When you create a media server instance with MSDP storage, you must tune the NetBackup parameters after you create the storage servers, and you may need to resize the MSDP storage partition. Make sure that you follow all of the steps that are listed in this document for creating a media server instance.
The System Topology page shows the full storage capacity of the appliance storage shelves. However, not all of the storage is available for use. You can see the usable storage capacity when you create or resize an instance. Navigate to the Application instances section on the System Topology page to manage your instances.
If you run any of the show hardware-health commands in the Flex Appliance Shell immediately after starting or restarting the appliance, you may see the following error message:
Unable to retrieve hardware information.
If you see this error, wait a few minutes and try again. This issue also applies during initial configuration, after you run the setup configure-network command.
The Flex Appliance Shell does not currently support changing the host network settings after initial configuration has been completed. If you need to change the DNS server IP address after initial configuration, contact Veritas Technical Support and ask your representative to reference article 100042306. If you need to change any of the other host network settings, you must perform a factory reset and then restart the initial configuration process.
If an application instance restarts due to a relocation or a storage resize, the NetBackup services may not start again when the instance does. If you encounter this issue, perform one of the following steps:
Sign in to the Flex Appliance Console and navigate to the System topology page. Use the Application instances section to stop the instance and then restart it.
Open an SSH session to the instance and log in as the appadmin user. Run the following command:
sudo systemctl start netbackup
IP forwarding is enabled in the Flex Appliance kernel by design; it is used to facilitate network communication between application instances and external networks.
The Flex Appliance Console does not display correctly in a web browser with low resolution. Some of the text fields can appear merged because the contents do not fit on the page. If you encounter this issue, use the zoom feature of your browser to zoom out until all of the fields are readable.
After a factory reset, the password for the root user account does not revert to the default password. This issue affects the initial configuration procedure if it is performed after a factory reset. If you encounter this issue, use the previous root user password when prompted during configuration. If you do not know the previous password, contact Veritas Technical Support for assistance resetting the password. Ask your representative to reference article 100043625.
An issue can occur that causes all Flex Appliance Shell users to be unable to log in through SSH. If you cannot open an SSH session to the node as any user, contact Veritas Technical Support and ask your representative to reference article 100043656.
If you restart a node, the node becomes available for login through SSH before the restart is fully completed. To avoid configuration issues, wait until the restart has fully completed and the Flex Appliance Shell displays the login screen before you log back in to the node.
If you relocate an instance, the task details that display in the Activity Monitor may include a string of garbled text. You can safely disregard this text.
If the VLAN tags do not match between the nodes of a multi-node appliance, the following error appears when you attempt to relocate an instance:
Failed to clear the fault on <network_interface> on <node_hostname>. Check /log/hostagent.log and VCS logs for more details.
However, these logs do not include any additional details. If you encounter this issue, check the VLAN tags on the appliance from the Settings > Network page. Verify that all of the VLAN tags have been added on both nodes.
If you resize the storage on an instance to a smaller amount, the process can take an extended amount of time to complete. The amount of time depends on how much storage needs to be resized and the overall workload on the appliance.
If the storage reduction takes longer than an hour, the Activity Monitor times out, and the resize status shows as Failed. However, the resize operation continues running in the background, and if it completes after the time-out, the status changes to Successful.
If you see a Failed status after an hour, do not restart the resize operation. Monitor the status, and if it has not changed to Successful within 12 hours, contact Veritas Technical Support for assistance. Ask your representative to reference article 100044047.
The following list contains the notes and the known issues that apply for the Veritas 5340 Appliance hardware:
On a Veritas 5340 Appliance, a receive transmission (RX) error message appears for 10GbE ports in Slot 8. These ports experience a 20% backup performance degradation in comparison to the 10GbE ports in other slots, which are not affected.