NetBackup IT Analytics Data Collector Installation Guide for Fabric Manager

Last Published:
Product(s): NetBackup IT Analytics (11.1)
  1. Fabric Manager Data Collection overview
    1.  
      Introduction
    2.  
      Fabric Manager: Collection of SAN switch data
    3.  
      Switch zone alias collection
  2. Pre-Installation setup for Brocade switch
    1.  
      Pre-Installation setup for Brocade switch
    2.  
      Prerequisites for adding Data Collectors (Brocade switch)
    3.  
      Upgrade troubleshooting: Brocade BNA SMI-S (CIM) server and Java 11
    4.  
      Supported switches
    5.  
      Brocade switches: Default ports and firewall considerations
    6.  
      Installation overview (Brocade switch)
    7.  
      Brocade switch Data Collector policy
  3. Pre-Installation setup for Cisco switch
    1.  
      Pre-Installation setup for Cisco switch
    2.  
      Prerequisites for adding Data Collectors (Cisco switch)
    3.  
      Upgrade troubleshooting: Cisco DCNM SMI-S (CIM) server and Java 11
    4.  
      Cisco switches: Default ports and firewall considerations
    5.  
      Installation overview (Cisco switch)
    6.  
      Cisco switch Data Collection policy
    7.  
      Before you start Cisco switch Data Collection
  4. Pre-Installation setup for Brocade Zone alias
    1.  
      Pre-Installation setup for Brocade zone alias
    2.  
      Prerequisites for adding Data Collectors (Brocade zone alias)
    3.  
      Brocade switches: Default ports and firewall considerations
    4.  
      Installation overview (Brocade zone alias)
    5.  
      Brocade zone alias Data Collector policy
  5. Pre-Installation setup Cisco Zone alias
    1.  
      Pre-Installation setup Cisco zone alias
    2.  
      Prerequisites for adding Data Collectors (Cisco zone alias)
    3.  
      Cisco switches: Default ports and firewall considerations
    4.  
      Installation overview (Cisco Zone Alias)
    5.  
      Cisco zone alias Data Collector policy
  6. Installing the Data Collector software
    1.  
      Introduction
    2.  
      Installing the WMI Proxy service (Windows host resources only)
    3.  
      Testing WMI connectivity
    4.  
      Considerations to install Data Collector on non-English systems
    5.  
      Install Data Collector Software on Windows
    6.  
      Install Data Collector software on Linux
    7.  
      Deploy Data Collector in native Kubernetes environment
    8.  
      Configure Data Collector manually for Veritas NetBackup
  7. Validating Data Collection
    1.  
      Validation methods
    2.  
      Data Collectors: Vendor-Specific validation methods
    3. Working with on-demand Data Collection
      1.  
        View real-time logging during an on-demand collection
    4.  
      Using the CLI check install utility
    5.  
      List Data Collector configurations
  8. Uninstalling the Data Collector
    1.  
      Uninstall the Data Collector on Linux
    2.  
      Uninstall the Data Collector on Windows
  9. Manually starting the Data Collector
    1.  
      Introduction
  10. Appendix A. Firewall configuration: Default ports
    1.  
      Firewall configuration: Default ports

Cisco zone alias Data Collector policy

  • Before adding the policy: A Data Collector must exist in the Portal, to which you will add Data Collector Policies.

    For specific prerequisites and supported configurations for a specific vendor, see the Certified Configurations Guide.

  • After adding the policy: For some policies, collections can be run on-demand using the Run button on the Collector Administration page action bar. The Run button is only displayed if the policy vendor is supported.

    On-demand collection allows you to select which probes and devices to run collection against. This action collects data the same as a scheduled run, plus logging information for troubleshooting purposes. For probe descriptions, refer to the policy.

To add the policy

  1. Select Admin > Data Collection > Collector Administration. Currently configured Portal Data Collectors are displayed.
  2. Search for a Collector if required.
  3. Select a Data Collector from the list.
  4. Click Add Policy, and then select the vendor-specific entry in the menu.
  5. Specify Data Collector properties.
  6. Add or select the parameters. Mandatory parameters are denoted by an asterisk (*):

    Field

    Description

    Sample Value

    Collector Domain

    The domain of the collector to which the host alias policy is being added. This is a read-only field. By default, the domain for a new policy will be the same as the domain for the collector. This field is set when you add a collector.

    yourdomain

    Policy Domain

    The Collector Domain is the domain that was supplied during the Data Collector installation process. The Policy Domain is the domain of the policy that is being configured for the Data Collector. The Policy Domain must be set to the same value as the Collector Domain.

    The domain identifies the top level of your host group hierarchy. All newly discovered hosts are added to the root host group associated with the Policy Domain.

    Typically, only one Policy Domain will be available in the drop-down list. If you are a Managed Services Provider, each of your customers will have a unique domain with its own host group hierarchy.

    192.1.1.1

    Cisco Switch IP Addresses*

    Enter the IP address of the Cisco switch. A comma-separated list of addresses may be entered for multiple switches that have the same credentials.

    User ID

    Use the User ID and passcode for accessing the Cisco switch. This typically would be an administrator privilege, but must be a minimum privilege of a view-only user. Credentials are not mandatory because depending on the version of the Cisco switch software, a user ID and password may not be required.

    Administrator

    Password

    Password associated with the user ID. Credentials are not mandatory because depending on the version of the Cisco switch software, a user ID and password may not be required.

    Note:

    The password is encrypted prior to saving in the database and is never visible in any part of the application.

    Password1

    Zone Details

    Click the clock icon to create a schedule. Every Minute, Hourly, Daily, Weekly, and Monthly schedules may be created. Advanced use of native CRON strings is also available.

    Examples of CRON expressions:

    */30 * * * * means every 30 minutes

    */20 9-18 * * * means every 20 minutes between the hours of 9am and 6pm

    */10 * * * 1-5 means every 10 minutes Mon - Fri.

    Note:

    Explicit schedules set for a Collector policy are relative to the time on the Collector server. Schedules with frequencies are relative to the time that the Data Collector was restarted.

    Notes

    Enter or edit notes for your data collector policy. The maximum number of characters is 1024. Policy notes are retained along with the policy information for the specific vendor and displayed on the Collector Administration page as a column making them searchable as well.

    Test Connection

    Test Connection initiates a Data Collector process that attempts to connect to switches using the IP addresses and credentials supplied in the policy. Credentials are not mandatory because depending on the version of the Cisco switch software, a user ID and password may not be required. This validation process returns either a success message or a list of specific connection errors.

    Several factors affect the response time of this validation request, causing some requests to take longer than others. For example, there could be a delay when connecting to the switch. Likewise, there could be a delay when getting the response, due to other processing threads running on the Data Collector. Test Connection requires that Agent Services are running.