Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Adding probes to Analyzer probe server

Start collecting information about your system resources by adding probes to the Analyzer probe server.

Adding Hitachi Enterprise Storage probe

The Hitachi Enterprise Storage probe collects data about the following Hitachi Enterprise storage systems: VSP, VSP F series, VSP G series, VSP 5000 series, and HUS VM. This procedure presumes you are using the RAID Agent bundled with Analyzer server. The procedure is the same for using Tuning Manager - Agent for RAID.

The Hitachi Enterprise Storage probe collects all performance data and specific configuration data from the RAID Agent using the REST API.

Additional configuration data not collected from the RAID Agent is available from Hitachi Configuration Manager (preferred) or Hitachi Device Manager. (You are prompted with this option when adding the Hitachi Enterprise Storage probe.)

NoteWhen you add the Hitachi Enterprise Storage probe, the following message might be displayed:
Some required opcodes are turned off by default on RAID Agent. Ensure that these are enabled to collect the related metrics.
Before proceeding further, refer to product user documentation.

Ignore this message as this setting is automatically enabled on RAID Agent in Ops Center Analyzer.

Procedure

  1. On the Analyzer probe home page, click Add Probe.

  2. In the Add Probe window, from the Probes list, select Hitachi Enterprise Storage.

  3. In the Provide RAID Agent Details section, provide the following details, and then click Next:

    • Probe Name: The probe name must be unique and contain a minimum 4 to maximum100 alphanumeric characters, and no special characters other than hyphen and underscore.
    • Connection Type: Choose HTTP or HTTPS.
    • RAID Agent IP Address: IP address of the machine on which the RAID Agent is installed.
    • RAID Agent Host name: Host name of the machine on which the RAID Agent is installed. The host name must match the machine host name (case-sensitive). Specify the host name that is returned when you run the uname -n command on the RAID Agent server. Do not use localhost.
    • RAID Agent Port: Port number used by the RAID Agent on the RAID Agent host. The default port number is:

      24221-HTTP

    • Storage System Serial number: Serial number of the storage system configured on the RAID Agent.
    • Storage System Instance: Storage instance name (alias) used to add the storage system to the RAID Agent.
    • Enable real time data collection: Select this check box to collect real-time data that can be used for alerts, reports, and the REST API.
      NoteEnabling the real-time data collection increases the load on the Analyzer detail view server.
  4. In the Configure RAID Agent Collection Interval window, specify the collection intervals as follows and then click Next:

    • Collection interval for PLC (Pool Configuration): 60
    • Collection interval for VVC (V-VOL status of Dynamic Provisioning): 60
    • Collection interval for LDSX (LDEV Summary Extra): 300 (only if the Access Type is 2 or 4)
    Note
    • The data collection interval for each record must match the data collection interval set in RAID Agent or in Tuning Manager - Agent for RAID.
    • The data collection interval for each record must also match the data collection interval set on the storage system. If these intervals do not match, the performance charts might not display properly (the graphs might not be continuous).
    • If you are using RAID Agent, use the collection_config command to verify the setting for the data collection interval, and specify a value that is the same as the displayed data collection interval.
    • For the data collection interval of records that are not displayed by using the collection_config command, use the default setting (without change).
  5. Select the Collect additional configuration metrics check box, and select the option to use for collecting the additional configuration metrics:

    NoteIf you do not want to collect additional configuration data, click Next and skip the rest of this procedure.
  6. In the Validation window, click Next, and then click OK.

  7. In the Status window, in Action, click Start to start collecting data.

    NoteIf you change the storage system configuration after you add a Hitachi Enterprise Storage probe, the old information displays until the status is updated.

Collecting additional configuration metrics

The Hitachi Enterprise Storage probe provides an option to collect additional configuration metrics not available from the RAID Agent. These additional metrics can be collected using the Hitachi Configuration Manager (preferred) or Hitachi Device Manager. This is optional; you can skip it if you do not want to collect these metrics. Refer to Hitachi Ops Center Analyzer Detail View Metrics Reference Guide for the list of additional configuration metrics.

Collecting additional configuration metrics with Hitachi Configuration Manager

The Hitachi Configuration Manager collects additional configuration metrics from the following storage systems: VSP 5000 series AFA, VSP 5000 series hybrid, VSP F400, VSP F600, VSP F800, VSP F1500, VSP G200, VSP G400, VSP G600, VSP G800, VSP G1000, and VSP G1500.

Before you begin

Verify the following:

  • User credentials used to connect to the storage systems have one of the following roles:
    • Security Administrator (view only) or greater
    • Storage Administrator (view only) with access to all Resource Groups
  • The Hitachi Configuration Manager server is configured for fcConnectionMode (in-band). (Using in-band communication mode, the Hitachi Configuration Manager server communicates with the storage system through the command device.) If you are using another communication mode, then change the mode to in-band before configuring the Hitachi Configuration Manager server in the Hitachi Enterprise Storage probe. (Multiple communication mode with lanConnectionMode is not supported.)
  • User Authentication is enabled on the command device.

Procedure

  1. Select the Collect additional configuration metrics check box, and then select the Hitachi Configuration Manager option.

  2. In the Hitachi Configuration Manager Details section, provide the following details and click Next:

    • Connection Type Choose HTTP or HTTPS.
    • Host IP Address or Host name of the Hitachi Configuration Manager server.
    • Port Port number of the Hitachi Configuration Manager server. The default port numbers are:

      23450-HTTP

      23451-HTTPS

    • Username/Password User name and password of the storage system specified in the Provide RAID Agent Details section.
  3. In the Validation window, click Next, and then click OK.

  4. In the Status window, in Action, click Start to start collecting data.

    Notes:
    • The Hitachi Configuration Manager server supports only 30 storage system instances.
    • It is recommended that the Hitachi Configuration Manager server that is configured in the Analyzer probe is not used by any other external application because it might affect the Hitachi Enterprise Storage probe data collection.

Collecting additional configuration metrics with Hitachi Device Manager

The Hitachi Device Manager collects additional configuration metrics related to the Hitachi storage systems.

Before you begin

  • Configure Hitachi Device Manager with all required storage devices.
  • Ensure that Hitachi Device Manager:
    • is capable of querying the storage capacity and host information.
    • has read-only privileges (at minimum).
    • is a member of the ViewGroup user group.
    • is version 7.5 or later.

Procedure

  1. Select the Collect additional configuration metrics check box, and then select the Hitachi Device Manager option.

  2. In the Hitachi Device Manager Details section, provide the following details and click Next:

    • Connection Type: Choose HTTP or HTTPS.

    • Host: IP address or host name of the Hitachi Device Manager server.

    • Port: Port number of the Hitachi Device Manager server. The default port numbers are:

      2001-HTTP

      2443-HTTPS

    • Username/Password: User name and password for Hitachi Device Manager. (This user must be added in the ViewGroup user group of Hitachi Device Manager.)

  3. In the Validation window, click Next, and then click OK.

  4. In the Status window, in Action, click Start to start collecting data.

Switching from Hitachi Device Manager to Hitachi Configuration Manager

You can change the option to collect additional configuration metrics used by the Hitachi Enterprise Storage probe from Hitachi Device Manager to Hitachi Configuration Manager and vice versa.

  1. Log on to the Analyzer probe.

  2. In the Action column, stop the probe if it is running, and then click Edit.

  3. In the Edit Hitachi Enterprise Storage Probe window, select the collection option.

Adding Hitachi Adaptable Modular Storage (AMS) probe

The AMS probe collects data from AMS and HUS storage systems.

Procedure

  1. On the Analyzer probe home page, click Add Probe.

  2. In the Add Probe window, from the Probes list, select Hitachi AMS.

  3. In the Add Hitachi AMS Probe section, provide the following details, then click Next:

    • Hitachi AMS Probe Name: Name of the HUS100 storage system for which the probe is added. (This must not be the same as the storage name that is defined in your environment.) After you add the probe, it is identified with this name in the Analyzer probe.

    • Controller 0 IP address and Controller 1 IP address: IP addresses of Controller 0 and Controller 1.

    • User name and Password: User name and password of the user with read-only permissions.

      Note

      If user authentication for the HUS100 storage system is disabled, then you must type a dummy user name and password because these two fields are mandatory for adding the AMS probe.

  4. In the Validation window, click Next, and then click OK.

  5. In the Status window, in Action, click Start to start collecting data.

Adding Hitachi NAS probe

Hitachi NAS probe collects configuration and performance data for the Hitachi NAS platform. There are two types of Hitachi NAS configurations: External SMU and Internal SMU. The Hitachi NAS probe collects configuration data using REST API, and performance data using RUSC CLI.

Hitachi NAS probe supports the Hitachi NAS server configured as a cluster, single node cluster, and a standalone (non-clustered) server.

NoteThe Analyzer probe supports the REST API v4 and v7 of the target Hitachi NAS storage system. If you are using the REST API v7, then make sure that following criteria are met: VSP G/F/Nx00 with NAS OS 13.5 or higher and HNAS 4000 series with NAS OS 13.5 or higher.

The following diagram illustrates the data collection flow.

GUID-46BF66ED-B006-4A84-9B9E-505C919DC736-low.png

Configuration metrics that are not collected using REST API and are required for reporting in the UI are collected using CLI.

Before you begin

  • External SMU
    • To collect the performance data, make sure that the user has SMU CLI access.
    • To collect the configuration data, a login with a role of supervisor is required to execute REST API calls.

      A valid Enterprise Virtual Server (EVS) IP address with admin services type (called an Admin EVS IP address) is required to execute REST API calls. The Hitachi NAS probe obtains this information based on the SMU details that you provide when adding the Hitachi NAS probe.

  • Internal SMU
    • A user with a role of supervisor is required to collect the performance and configuration data.
    • To collect the configuration data, make sure that the REST API server is installed on one of the controllers.
    • The controller and the REST API server must use the same login with a role of supervisor.

Procedure

  1. On the Analyzer probe home page, click Add Probe.

  2. In the Add Probe window, from the Probes list, select Hitachi NAS.

  3. On the Add Hitachi NAS Probe window, in the Provide SMU details section, provide the following details, then click Next:

    • IP address The IP address of the Hitachi NAS System Management Unit (SMU).
    • User name and Password User credentials of the SMU user.
  4. In the Validation window, click Next.

  5. Based on the SMU IP address, the Provide REST API server details or Provide controller details window opens.

    • External SMU: The Provide REST API server details window lists all the Hitachi NAS servers managed by the SMU. Select the Hitachi NAS server and Admin EVS IP address, and enter the REST API server details. Click Next.
      NoteYou can select multiple Hitachi NAS servers; each is added as an individual probe in the Analyzer probe. (The probe is added as an SMU-Hitachi NAS server combination.)
    • Internal SMU: The Provide controller details window lists all the controllers managed by the SMU. Type the username and password of the controller that you want to add. (The default port is 8444 and cannot be changed.)
      NoteYou can select multiple controllers, and a single probe is added for multiple controllers. (The probe is added as an SMU-Controller combination.) If you provide the details of one controller, then the configuration data is collected from all controllers managed by the SMU. However, to collect the performance data you must provide the details of each controller from which you want to collect the performance data.
  6. In the Validation window, click Next, then click OK.

  7. In the Status window, in Action, click Start to start collecting data.

Adding VMware probe

VMware probe collects data from the VMware vCenter server and standalone VMware ESXi host.

  1. From the Analyzer probe server home page, click Add Probe.

  2. In the Add Probe window, from the Probes drop-down list, select VMware.

  3. In the Add VMware Probe section, provide the following details, then click Next:

    • vCenter Server: Host name or IP address of the VMware vCenter Server Appliance or VMware ESXi host IP address.

    • User name: Any user with access to VMware vCenter Server (read-only privileges are sufficient). Ensure that the user has access to all the ESXi hosts (within the VMware vCenter Server) that you want to monitor.

    • Password: Password associated with the user name.

  4. In the Validation window, click Next.

    NoteIf you have entered the standalone VMware ESXi host details, skip to step 6.
  5. In the Choose Hosts for Data Collection window, select the hosts that you want to monitor.

    NoteWhen a new host is added to the VMware vCenter server, the probe begins collecting data automatically. To override this setting, clear Include hosts that are added in the future.

    You can also add the hosts using the Import CSV option, which allows you to add a large number of hosts with a flexibility of adding only those hosts that you want to monitor. For example, if you have 100 hosts in a vCenter server and out of these you want to monitor 60, you can specify these hosts in the CSV file and import it to the probe.

    1. Select the Select hosts for data collection using csv file import option.

    2. Ensure the CSV file is in a specific format. Download a sample file by clicking the Export option.

    3. Edit the CSV file details offline based on your requirements. In the CSV file, you can add only those hosts that you want to monitor or type No for each host that you do not want to monitor.

    4. Import the CSV file by clicking the Import option. The imported hosts are listed in the Select hosts for data collection section.

    5. Track the status of the hosts in the Uploaded Host CSV Record Status window. To view the status, click the Details option. Refer to Viewing the host CSV file import status for more information.

  6. Click Next, and then click OK.

  7. In the Status window, in Action, click Start to start collecting data.

Adding Brocade FC Switch (BNA) probe

Brocade FC Switch (BNA) probe collects configuration and performance data about the brocade switches from Brocade Network Advisor using REST API. Brocade Network Advisor manages the entire Brocade IP address and SAN portfolio for unified network visibility and control.

Before you begin

  • The user must have Area of Responsibility as All Fabrics and at least one role: SAN Discovery setup or Performance with read-only permissions.
  • Brocade Network Advisor Professional plus or Brocade Network Advisor Enterprise must be installed.
    NoteDo not use both the Brocade FC Switch (BNA) probe and Brocade FC Switch (CLI) probe to collect data for the same switch.

Procedure

  1. From the Analyzer probe server home page, click Add Probe.

  2. In the Add Probe window, from the Probes drop-down list, select Brocade FC Switch (BNA).

  3. In the Add Brocade FC Switch (BNA) Probe window, type the following details, and then click Next:

    • BNA IP address: IP address of Brocade Network Advisor
    • BNA Port: Port number of the Brocade Network Advisor
    • Protocol: Select HTTP or HTTPS

      The default ports are:

      80 (HTTP)

      443 (HTTPS)

    • Username and Password: User name and password of the Brocade Network Advisor
  4. In the Validation window, click Next.

  5. In the Choose switches for data collection window, select the switches that you want to monitor.

    NoteWhen a new switch is added to Brocade Network Advisor, the probe begins collecting data automatically. To override this setting, clear Include Switches that are added in the future.

    You can also add the switches using the Import CSV option, which allows you to add a large number of switches with a flexibility of adding only those switches that you want to monitor. For example, if you have 100 switches and out of these you want to monitor 60, you can specify these switches in the CSV file and import it to the probe.

    1. Select the Select switches for data collection using csv file import option.

    2. Ensure that the CSV file is in a specific format. Download a sample file by clicking the Export option.

    3. Edit the CSV file details offline based on your requirements. In the CSV file, you can add only those switches that you want to monitor or type No for each switch that you do not want to monitor.

    4. Import the CSV file by clicking the Import option. The imported switches are listed in the Select switches for data collection section.

    5. Track the status of the switches in the Uploaded Switch CSV Record Status window. To view the status click the Details option. Refer to Viewing the host CSV file import status for more information.

  6. Click Next, and then click OK.

  7. In the Status window, in Action, click Start to begin collecting data.

Adding Cisco FC Switch (DCNM) probe

The Cisco FC Switch (DCNM) probe collects data from the Cisco Data Center Network Manager using Web Services APIs.

NoteDo not use both the Cisco FC Switch (DCNM) and Cisco FC Switch (CLI) probe to collect data for the same switch.

Procedure

  1. From the Analyzer probe server home page, click Add Probe.

  2. In the Add Probe window, from the Probes drop-down list, select Cisco FC Switch (DCNM).

  3. In the Add Cisco FC Switch (DCNM) Probe window, type the following details and click Next:

    • Cisco FC Switch (DCNM) IP Address: IP address of DCNM.

    • DCNM Web service Port: The port number to access web service on the DCNM server.

      Note In some environments, the port number is optional.
    • Protocol : Select HTTP or HTTPS.

      The default ports are:

      80 - HTTP

      443 - HTTPS

    • Username and password of DCNM. The user must have access to the DCNM web client.

  4. In the Validation window, click Next.

  5. In the Choose switches for data collection window, select the switch that you want to monitor.

    NoteWhen a new switch is added to the Cisco Data Center Network Manager, the probe begins collecting data automatically. To override this setting, clear Include Switches that are added in the future.

    You can also add the switches using the Import CSV option, which allows you to add a large number of switches with a flexibility of adding only those switches that you want to monitor. For example, if you have 100 switches and out of these you want to monitor 60, you can specify these switches in the CSV file and import it to the probe.

    1. Select the Select switches for data collection using csv file import option.

    2. Ensure that the CSV file is in a specific format. Download a sample file by clicking the Export option.

    3. Edit the CSV file details offline based on your requirements. In the CSV file, you can add only those switches that you want to monitor or type No for each switch that you do not want to monitor.

    4. Import the CSV file by clicking the Import option. The imported switches are listed in the Select switches for data collection section.

    5. Track the status of the switches in the Uploaded Switch CSV Record Status window. To view the status click the Details option. Refer to Viewing the host CSV file import status for more information.

  6. Click Next, and then click OK.

  7. In the Status window, under Action, click Start to start collecting data.

Adding Cisco FC Switch (CLI) probe

Cisco FC Switch (CLI) probe collects the performance and configuration data using the CLI commands from Cisco SAN switches.

NoteDo not use both the Cisco FC Switch (DCNM) and Cisco FC Switch (CLI) probe to collect data for the same switch.

Procedure

  1. On the Analyzer probe home page, click Add Probe.

  2. In the Add Probe window, from the Probes menu, select Cisco FC Switch (CLI).

  3. In the Add Switch Details section, select any of the following options to add the target switches:

    • Select Add Device, type the following details, and then click Add Switch:
      • Data Center: Name of the data center; you can enter any name.
        NoteThe switch is displayed under this data center in the Analyzer detail view Resources tree.
      • Start IP Address and End IP Address: Range of the IP address from which to start collecting data. This scans all the switch IP addresses in that range.
        NoteIf you have entered a range for addresses, the username and password must be the same for all switches.
      • User Name: User name with the network-operator role (at minimum)
      • Password: Password of the user
      • SSH Port: The port number (default: 22)
    • Upload CSV: You can add the range of switch IP addresses with different credentials and group the switches based on the data center. While adding multiple data centers, make sure that each has a unique name. The switches are shown under the respective data center in the Analyzer detail view Resources tree.
      • Select Upload CSV to upload the switch details in a CSV file, and then click Import CSV.

        The CSV file must be in a specific format. You can download a sample file by clicking Download Sample CSV File.

    • Upload Encrypted CSV: The upload encrypted CSV works similar to the upload CSV option. However, it is useful when you want to provide the switch details, including login credentials, that must be kept confidential.
      • Select Upload Encrypted CSV to upload details in an encrypted CSV file, and then click Import CSV.

        The Encrypted CSV file must be in a specific format. You can download the sample file by clicking Download Sample CSV File. Refer to Encrypting the CSV file for more information.

      • Encrypted Random Key: Select an encrypted random key.
      • Upload Encrypted CSV: Upload an encrypted CSV.

    Scroll down to view the list of switches. You can also add more switches or delete a switch before adding the probe.

  4. To add more Cisco SAN switch IP addresses, click Add More.

  5. Click Next.

    The system scans the switch IP addresses and adds the valid switches to the system.

  6. In the Switch Validation window, click Next, and then OK.

    Each valid switch IP address is added as an individual probe.
  7. In the Status window, in Action, click Start to start collecting data.

Encrypting the CSV file

Before uploading the CSV file you must encrypt it using the public key.

  1. Contact customer support for the public key.
  2. Log on to the Analyzer probe server through an SSH client (like putty) as a root user.
    Note
  3. Create the temporary folder in the /data folder and save the public key.
  4. Generate the random key using the following command:
    openssl rand -base64 32 > randomkey.bin
  5. Encrypt the random key by using the public key, using the following command:
    openssl rsautl -encrypt -inkey public-key.pem -pubin -in randomkey.bin -out randomkey.bin.enc
  6. Encrypt the CSV file by using the random key (not encrypted):
    openssl enc -aes-256-cbc -salt -in <name of the CVS file that you want to encrypt> -out <outputfilename.CSV> -pass file:./randomkey.bin

    For example, openssl enc -aes-256-cbc -salt -in BrocadeSANSwitchProbeSample.csv -out BrocadeSANSwitchProbeEncrypted.csv -pass file:./randomkey.bin

  7. Download the encrypted random file and encrypted CSV file to your local machine.
  8. Provide the encrypted random file and CSV file when adding the probe.

Adding Linux probe

The Linux probe collects performance and configuration data from individual machines running the Linux operating system.

Before you begin

  • The following packages must be installed on the virtual machine (or host) to be monitored:
    • sysstat
    • perl
    • zip
  • The following perl modules must be executable on the virtual machine or host to be monitored:
    File::Path, Getopt::Std, HTTP::Request::Common, IO::Select, IO::Handle, LWP::UserAgent, Time::HiRes 
  • The openssh-clients must be installed on the target machine or host.
  • Create an installation directory with read, write, and execute permissions on all target machines for the data collection scripts. (Installation directory names are restricted to alphanumeric, hypen, and underscore characters only.)
  • A user with read, write, and execute permissions for crontab must be present on each target machine.
  • Data for the following resources must be collected as the root user: Host Volume Group, Host Logical Volume, and Host Physical Volume.
  • The xinetd service must be running on the Analyzer probe server.
    Note The Linux probe does not collect multipath information.

Procedure

  1. On the Analyzer probe home page, click Add Probe.

  2. In the Add Probe window, from the Probes list, select Linux.

  3. In the Add Host Details section, type the following details, and then click Next:

    • HOST IP ADDRESS: The IP address of the target Linux host or machine.
    • USERNAME: A user on the target Linux host or machine.
    • PASSWORD: User password
    • INSTALLATION DIRECTORY: Location for the data collection scripts on the target Linux host or machine.
  4. To add multiple targets, click Add More or click Next to continue.

    The Host Validation section opens. The system validates the host IP address.

  5. Click Next.

    The Script Deployment section opens. The data collection scripts are deployed on the target host or machine.
  6. Click Next, and then click OK.

  7. In the Status window, in Action, click Start to start collecting data.

    When adding multiple targets, the Status window shows multiple probes. You must start each probe individually.

Viewing the host CSV file import status

The details link shows the following status of the imported CSV file.

The following figure shows an example status of an imported CSV file and the resources monitored:

GUID-64A96C0C-2946-4335-A663-146209213427-low.png

  • Valid: Total number of valid records (Monitored and Not monitored)
    • Monitored: The list of records from which the data is collected.
    • Not monitored: The list of records that are marked as No in the CSV file.
  • Invalid: Total number of invalid records that cannot be added.
    NoteYou can edit the invalid records and re-import the CSV file. To view the details of the invalid records, click View.
    • Bad Record: The list of records with incorrect values, which cannot be read by Analyzer probe server.
    • Unknown state: The list of records with incorrect monitored status in the CSV file. The monitored status in the CSV file must be either Yes or No.