Veritas Flex Appliance Getting Started and Administration Guide

Last Published:
Product(s): Appliances (1.0)
Platform: 5340
  1. Product overview
    1.  
      Introduction to Veritas Flex Appliance
    2.  
      About the Flex Appliance documentation
    3.  
      Operational notes
  2. Getting started
    1.  
      Initial configuration guidelines and checklist
    2.  
      Performing the initial configuration
    3.  
      Adding a node
    4.  
      Accessing and using the Flex Appliance Shell
    5.  
      Accessing and using the Flex Appliance Console
    6.  
      Common tasks in Flex Appliance
  3. Modifying settings
    1.  
      Creating a network bond
    2.  
      Deleting a network bond
    3.  
      Configuring a network interface
    4.  
      Setting the date and time for appliance nodes
  4. Configuring Call Home
    1.  
      About AutoSupport and Call Home
    2.  
      Viewing Call Home information
    3.  
      Configuring Call Home settings
    4.  
      Deleting and disabling Call Home settings
  5. Managing users
    1.  
      Adding a tenant
    2.  
      Editing a tenant
    3.  
      Removing a tenant
    4.  
      Adding a user
    5.  
      Removing a local user
    6.  
      Changing the password for the admin user on the Flex Appliance Console
    7.  
      Changing a hostadmin user password
  6. Using Flex Appliance
    1. Managing applications and upgrade packages in the repository
      1.  
        Adding files to the repository
    2. Creating application instances
      1.  
        Creating a NetBackup master server instance
      2.  
        Creating a NetBackup media server instance
    3. Managing application instances
      1.  
        Viewing instance performance metrics
      2.  
        Running NetBackup commands on an application instance
      3.  
        Establishing trust with a NetBackup 7.7.3 master server instance
  7. Monitoring the appliance
    1.  
      Monitoring the hardware from the Flex Appliance Shell
    2.  
      Viewing node information
    3.  
      Viewing Primary Storage Shelf information
    4.  
      Viewing Expansion Storage Shelf information
    5.  
      Viewing hardware faults
    6.  
      Viewing system data
  8. Reconfiguring the appliance
    1.  
      Performing a factory reset
    2.  
      Performing a storage reset
    3.  
      Removing a node
  9. Troubleshooting guidelines
    1.  
      General troubleshooting steps
    2.  
      Gathering device logs on a Flex 5340 appliance

Operational notes

This topic explains important aspects of Flex Appliance 1.0 operations that may not be documented elsewhere in the documentation.

Software operational notes

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

  • When you run the setup configure-console command during initial configuration, a warning message appears with a series of hardware commands to run. You should not run those commands at that time. Instead, run them after you run the setup configure-console command and the operation is complete.

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

    See Creating a NetBackup 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.

  • The Username field on the Activity Monitor page of the Flex Appliance Console always displays the admin user.

  • 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 host network settings after initial configuration, contact Veritas Technical Support and ask your representative to reference article 100042306.

  • When you create an instance, the /etc/hosts field does not support comments or blank lines. If you include comments or blank lines, the instance creation fails with the following message:

    V-492-101-515: Internal server error. Create instance failed. Check /log/inframodules.log for more details.

    To resolve this issue, remove the comments and blank lines from the /etc/hosts field and try again.

  • If you configure an SMTP server with the set alerts email-smtp smtp_server= command before you add an alert email address, the following message displays:

    - [Warning] No recipients are configured to receive software notifications. Use 'Settings->Alerts->Email Software Add' command to configure the appropriate Email address.

    This message is incorrect. Use the set alerts email-hardware email_address= command to add a recipient for alert notifications.

  • Flex Appliance does not support restarting both nodes of a multi-node appliance at the same time. If you restart the nodes at the same time, the nodes may start back up in an ADMIN_WAIT state. If you experience this issue, contact Veritas Technical Support and ask your representative to reference article 100042364.

  • The system data-collect command gathers component data into a .zip file in the log/autosupport directory. While the command runs, a message regarding too many arguments may display. The data that is gathered and the .zip file that is generated are not adversely affected. You can disregard the message.

  • The show instance repository-images command is not supported in this release.

  • If you create an application instance and enter a hostname with a space in it, the instance creation fails. If you try again with the same hostname without the space, the instance creation may fail again with the following error:

    V-492-102-134: Application instance already exists with given hostname or IP Address

    If you experience this issue, use a different hostname or contact Veritas Technical Support and ask your representative to reference article 100042410.

  • If you create an instance with a short hostname that is longer than 18 characters, the instance creation fails. To avoid this issue, enter a hostname that is fewer than 18 characters in length.

  • If the appliance file system becomes full, the operation of all of your application instances can be affected, and backups can fail. You can monitor the available space in the file system from the Flex Appliance Shell. Log in as the hostadmin user and run the following command:

    /usr/bin/df -h /var/lib/docker

  • After you run the system data-collect command, the following message displays:

    All logs have been collected in /log/DataCollect.zip

    The Log files DataCollect-BQWT73700226-20180307020753.tar.gz collected from the appliance are sent to AutoSupport servers. The data transmission may complete in several minutes or longer due to file size, network status, appliance performance and other reasons

    This message is incorrect. The logs are actually in the following location and are not automatically sent to the AutoSupport servers.

    /log/autosupport/DataCollect.zip

    You can use an SCP tool to transfer the logs to another location.

  • An issue can occur that causes the appliance connection status to appear as Disconnected if you run the system hardware-health node nodecomponent=connection command in the Flex Appliance Shell. At the same time, the status of all of the other components including the storage shelves does not show any errors.

    If you experience this issue, contact Veritas Technical Support and ask your representative to reference article 100042513.

  • On a multi-node appliance, the Flex Appliance Console displays incorrect capacity information for application instances on the second node. To view the correct storage usage, log in to the instance and run the df command.

  • 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

Hardware operational notes

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.