Skip to main content
Data Infrastructure Insights

Configuring the IBM SAN Volume Controller data collector

Contributors netapp-alavoie
PDFs

The IBM SAN Volume Controller (SVC) data collector collects inventory and performance data using SSH, supporting a variety of devices that run the SVC operating system.

The list of supported devices includes models such as the SVC, the v7000, the v5000, and the v3700. Refer to the Data Infrastructure Insights support matrix for supported models and firmware versions.

Terminology

Data Infrastructure Insights acquires the following inventory information from the IBM SVC data collector. For each asset type acquired by Data Infrastructure Insights, the most common terminology used for this asset is shown. When viewing or troubleshooting this data collector, keep the following terminology in mind:

Vendor/Model Term Data Infrastructure Insights Term

Drive

Disk

Cluster

Storage

Node

Storage Node

Mdisk Group

Storage Pool

Vdisk

Volume

Mdisk

Backend LUNs and paths

Note: These are common terminology mappings only and might not represent every case for this data collector.

Inventory Requirements

  • IP address of each SVC cluster

  • Port 22 available

  • Read-only user name and password

Performance Requirements

  • SVC Console, which is mandatory for any SVC cluster and required for the SVC discovery foundation package.

  • Credentials will require administrative access level only for copying performance files from cluster nodes to the config node.

  • Enable data collection by connecting to the SVC cluster by SSH and running: svctask startstats -interval 1

    Note: Alternatively, enable data collection using the SVC management user interface.

Configuration

Field Description

Cluster IP Addresses

IP addresses or fully-qualified domain names of the SVC storage

Inventory User Name

User name for the SVC CLI

Inventory Password

Password for the SVC CLI

Advanced configuration

Field Description

Inventory Poll Interval (min)

Interval between inventory polls. The default is 40 minutes.

Performance Poll Interval (sec)

Interval between performance polls. The default is 300 seconds.

To clean up dumped stats files

Select this checkbox to clean up dumped stats files

Troubleshooting

Some things to try if you encounter problems with this data collector:

Problem: Try this:

Error: "The command cannot be initiated because it was not run on the configuration node."

The command must be executed on the configuration node.

Some things to try if you encounter problems with this data collector:

Problem: Try this:

Error: "The command cannot be initiated because it was not run on the configuration node."

The command must be executed on the configuration node.

Additional information on this Data Collector may be found from the Support page or in the Data Collector Support Matrix.