Capacity Manager Configurations > Supported Storage Arrays and Access Requirements
  
Version 10.3.00P13
Supported Storage Arrays and Access Requirements
This section contains the following topics:
• IBM Arrays: Modify Profile
• Creating a NetApp User with API Privileges
• Creating a NetApp Cluster-Mode User with API Privileges
• Port Performance Metrics
• EMC Isilon Metrics
• NetApp Cluster-Mode Metrics
• EMC Symmetrix Enhanced Performance Metrics
Capacity Manager currently supports the storage management products and storage arrays listed below. In general, any storage array that the device manager or command-line interface supports should work with Capacity Manager. For specific prerequisites and configuration requirements, see the specific Data Collector information.
Capacity Chargebacks can be configured for block storage only; file-based storage is not supported for Array Capacity Chargeback.
Data Collectors require the following privileges to access APIs and underlying details:
• On Linux, root privileges for SSH and Telnet
• On Windows, administrator privileges for WMI.
Table 1 Storage Array Data Collection Prerequisites
Vendor
Arrays/NAS
Dev Mgr/API/CLI
Access Requirements
Ports
Notes
Dell
Compellent
v6.4, 6.5, 6.5.1
Enterprise Manager,
v6.2.2.8 and v14.2.2.6 for SMI-S provider and DB
• SMI-S Provider User ID.
• Enterprise Manager IP address.
• Enterprise Manager DB IP address.
5988 SMI-S over http
5989 SMI-S over https
1433 DB
No installations required on the Data Collector server.
Dell EMC
Unity
330/300F, 400/400F, 500/500F, 600/600F, 350F, 450F, 550F and 650F
• Read-only credentials (username and password) are required to connect to DELL EMC Unity storage array using REST API.
REST API version 4.3.0 on Port 443 or 8443
 
EMC
Elastic Cloud Storage (ECS)
3.x
• User must belong to Management Users with System Monitor privilege
REST API on Port 80 or 4443
 
EMC
VNX (Block), CLARiiON
 
Naviseccli, Navicli, v7.30, 7.31, 7.32
• IP address/hostname
• Customize: <ip address>:<port>
• View-only user ID & pwd for CLARiiON NaviSuite
Defaults:
443, 2163, 6389, 6390, 6391, 6392
• NaviSecCLI must be installed on the Data Collector server.
• Enable statistics logging on the VNX system to collect LUN performance data.
• A low security level for certificates is required. Ensure this setting by using the following command:
naviseccli security -certificate -setLevel low
EMC
VNX (File), Celerra
 
v7.0.40.1, 7.0.50.2, 7.0.52, 7.1.56
• XML API v2 access allowed must be enabled for Client Access.
• XML API server must be running.
• Read-only user (Operator role).
Defaults:
443, 2163, 6389,6390, 6391,6392
No installations required on the Data Collector server.
EMC
Data Domain
5.0, 5.1, 5.2, 5.4, 5.5, 5.6, 5.7, 6.0, 6.1, 6.2, 71
 
Port 22 (SSH)
 
 
EMC
Isilon
Isilon OneFS 6.5, 7.0, 7.1, 7.1.1, 7.2, 8.0
• Access to a single, externally addressable node in the cluster via SSH.
• Root access required (for certain isi commands).
22
• A sudo user, specific to this data collection, can be used for root-level access.
 
EMC
Symmetrix
Solutions Enabler (Symcli), v7.1.3, 7.2, 7.3, 7.4, 7.5, 7.6.1, 7.6.2, 8.0, 8.1
Unisphere 8.3
No User ID & pwd required.
2707
5480
Data Collector must be installed on the server that manages the Symmetrix arrays.
Symcli uses Fibre Channel (FC) to communicate; Data Collector must be installed on a server connected via FC to the Symmetrix array, by a switch, if necessary.
Sample command: symcfg list -v
Unisphere 8.3 is used for Performance collection.
EMC
VPLEX
5.3, 5.4
User ID & pwd for the VPLEX storage system.
https TCP 443
The VPLEX storage system should be reachable by the Data Collector server.
EMC
XtremIO
Management Server 3.0.x, 4.0.x
X2 (V6.0.x)
Read-only user ID & pwd
80
REST API
Hitachi
Hitachi Content Platform (HCP)
HCP Version 7.2.x.x, HCP Mib Version 7.2
Read-only user ID & pwd (Local User/AD User). Refer to the HCP-specific data collector information for all permissions.
SNMP:161
REST API: https 9090
SNMP v2/v3
REST API
Hitachi
Virtual Storage Platform (VSP)
Hitachi Universal Storage Platform V
Hitachi Unified Storage (HUS) Model 100 Series (DF850)
TagmaStore AMS, USP, WMS, Network Storage Controller
Lightning 9900 V Series
Thunder 9500 V Series
HP Command View Advanced Edition
Hitachi Device Manager (HDvM), 5.5, 6.0, 6.1, 6.2, 6.3. 6.4, 7.0, 7.1.1, 7.2, 7.3, 7.4, 7.6, 8.0, 8.4, 8.5
Hitachi Dynamic Tiering (HDT) starting with
HDvM v7.1; Valid only if your HDvM is managing VSP arrays running HDT.
 
• Name of Device Manager server.
• Admin User ID & pwd of Device Manager.
• For 7.1.1 thru 7.4, the User ID configured to access HDvM must have view permissions to HRpM and HTSM.
• Use the Admin username for accessing the Hitachi Infrastructure Analytics Advisor.
ensure port 2001 is open
For the HIAA probe: 22015 is used for HTTP and 22016 is used for HTTPS.
XML API calls over HTTP
 
HP XP arrays are treated as Hitachi Block Storage
Hitachi
Hitachi Tuning Manager (for performance data collection)
Hitachi Tuning Manager (HTnM) versions 7.2, 7.3, 7.4, 8.1
Supported on Windows only.
N/A
Data Collector must be installed on the host where Tuning Manager is installed.
Single Data Collector policy must be used to collect both capacity data from the Device Manager server and performance data from the Tuning Manager server.
Hitachi
(HNAS)
BlueArc
NAS
HUS (File Module)
Hitachi NAS CLI
HNAS versions 10.x and 11.x
• Hitachi NAS Admin EVS addresses separated by commas.
• The location of the SiliconServer Control (SSC) CLI. For example:
Linux: /usr/bin/ssc
Windows: c:\program files\ssc
• Create a user with supervisor privileges for accessing the Hitachi NAS.
 
 
 
N/A
To collect block storage that is shared with HNAS, create a separate data collector policy for the relevant supported vendor storage; for example, Hitachi Storage.
 
HP
3PAR
InForm 2.3.1, 3.1.1, 3.1.2, 3.2.2, 3.3.1
• Comma-separated list of IP addresses or host names of the HP 3PAR servers from which to collect data.
• User ID & Password must be the same for all servers listed in the Server Address field.
ssh: 22 for CLI
Uses CLI collection via ssh
HP
EVA
v8400, 6400, 6100, 4400
• Server name or IP address of the HP EVA management server.
• SSSU user name & password.
2372
HP Storage System Scripting Utility (SSSU) must be installed on the Data Collector server.
HP
StorageWorks XP
 
Hitachi Device Manager (HDvM), 5.5, 6.0, 6.1, 6.2, 6.3. 6.4, 7.0, 7.1.1, 7.2, 7.3, 7.4, 7.6, 8.0
HP Command View Advanced Edition (CLI/SMI-S enabled)
Hitachi Dynamic Tiering (HDT) starting with HDvM v7.1; Valid only if HDvM is managing VSP arrays running HDT.
• Name of Device Manager server
• Admin user ID & password of Device Manager.
• For 7.1.1 & 7.2, user ID configured to access HDvM must have view permissions to HRpM & HTSM.
Ensure port 2001 is open
XML API calls over HTTP.
 
For HP Command View Advanced Edition, HP XP arrays are treated as Hitachi Block Storage.
 
HPE
Nimble Storage
5.0.7.100-607338-opt
REST API Reference Version 5.0.1.0
Storage System Addresses
5392
 
Huawei
OceanStor Enterprise Storage
Huawei OceanStor DeviceManager REST APIs are used. OceanStor Model - 5300 V3, 5500 V3, 5600 V3, 5800 V3, 6800 V3, Storage versions - V300R003, V300R006.
• IP address of the storage array to be accessed
• User ID and password for the Huawei OceanStor storage system.
Huawei OceanStor Device Manager port that provides services. The port number is 8088.
 
IBM
6000 & 8000
(Enterprise arrays)
DSCLI 5.2.2.272
• User account on the array with monitor group privileges
1751
1750
1718
DSCLI must be installed on the Data Collector server. Location:
Linux: /opt/ibm/dscli
Windows: C:\Program Files\IBM\dscli
IBM
N Series
Data ONTAP, versions 7.2, 7.3, 8, 8.1 7-Mode and Cluster-Mode, 8.3P1 Cluster-Mode, 9
Use an existing NetApp user or create one with the necessary privileges to access the API:
login-http-admin
api-*
443
Typically, the root, admin user has all the capabilities, but it is not advisable to use root or admin passwords.
If api-* does not meet your security requirements, contact Support for a list of exact required api privileges.
IBM
SVC
v4.3.x, v5.1,
v6.1 - 6.4.
v7.4
Storwize V7000
FlashSystem V9000, 840/900
Performance data is collected only for SVC 6.x and 7.4, with an SMI-S version of 1.4 or above.
• Namespace: /root/ibm
• IP address or hostname of SVC master console (from which data will be collected).
• Super User ID & pwd for CIMOM. Super User ID refers to the user ID of the SVC master console server. The same user is used to execute CLI commands via ssh.
• Enable statistics collection via the SVC UI: Manage Clusters > Start Statistics Collection.
5988
5989
ssh: 22
SSPC (System Storage Productivity Center) with CIMOM agent is required OR embedded CIMOM for v5.1, v6.1 & v6.3.
Known issue: v5.1.08 does not provide vdisk data.
The data collector can run on any server that can access the SSPC server with CIMOM.
IBM
VIO
v1.5, v2.1, Hardware Management Console (HMC) Version 7
• IP Address/Hostname of LPAR Management Server of either HMC (Hardware Management Console) or IVM (Integrated Virtualization Manager).
• User name & password for LPAR Management Server. For HMC, user name should have at least HMCViewer permissions.
ssh: 22
telnet: 23
 
IBM
XIV, Model 2810/2812-A14 (Gen 2), Model 2810/2812-114 (Gen 3)
XIV Storage Manager, v10.1.x, v10.2.x
 
• XCLI must be installed on the Data Collector server.
• Read-only user credentials are sufficient for executing XCLI commands for data collection.
TCP 7778
 
 
INFINIDAT
InfiniBox
2.0, 2.2, 3.0.12.0 (F4000)
• user with read-only role
https: 443
 
LSI
LSI 1532, 1932, 3992, 3994, 6994, 6998, 7900
IBM Storage Manager CLI:
3K series: 02.70.G5.15 & above
4K/5K series: 10.10.G5.05 & above
6K/8K series: DSCLI 5.2.2.272 & above
• See the corresponding IBM Array requirements.
N/A
 
NetApp
FAS6000 Series, FAS3100 Series, FAS3000 Series, FAS2000 Series, V-Series
Data ONTAP, versions 7.2, 7.3, 8, 8.1, 8.2, 7-Mode and Cluster-Mode, 8.3P1 Cluster-Mode, 9
• Use an existing NetApp user or create one with the necessary privileges to access the API:
login-http-admin
api-*
Typically, the root, admin user has all the capabilities, but it is not advisable to use root or admin passwords.
TCP 80/443
Array performance data also can be collected via the ONTAP API.
If api-* does not meet your security requirements, contact Support for a detailed list of exact api privileges that are required.
NetApp
E-Series: E2600, E2700, E5400, E5500, EF560, E2800
SANtricity SMcli: 10.86, 11.30
 
TCP 2436
SMCLI must be installed on the Data Collector server. Location:
Linux: /opt/SM8/client/
Windows: C:\Program Files\SM8\client
This also applies to the IBM DS Series arrays.
OpenStack
OpenStack Swift (Juno10, TBC),
SwiftStack v2.2
 
• Keystone v2
• Proxy path for Swift configuration files must be specified.
• Controller credentials that have access to tenants/projects.
• Swift proxy server credentials with super-user privileges.
35357 for Keystone Admin
5000 for Keystone Public
22 for SSH
• If multiple proxies exist, APTARE IT Analytics uses only one. Capacity reports will reflect only one proxy.
• Configure the policy to use the address of the actual proxy server, not the server responsible for load balancing.
• Capacity data is collected from devices mapped to OpenStack nodes.
OpenStack
OpenStack Ceilometer
REST API
•  
8777
•  
Pure Storage
FlashArray
REST API
View-only User ID for the Pure Storage FlashArray storage system.
443
API calls for HTTPS
Sun
StorEdge 9900
Hitachi Device Manager (HDvM), 5.5, 6.0, 6.1, 6.2, 6.3. 6.4, 7.0, 7.1.1, 7.2, 7.3, 7.4, 7.6, 8.0
• Device Manager server name.
• Admin user ID & password of Device Manager.
2001
XML API calls over HTTP
IBM Arrays: Modify Profile
For the IBM Enterprise arrays (6000 & 8000 Series), the profile must be modified. Locate the profile file, typically in the /profile sub-directory and named dscli.profile. In this file, uncomment the Output Format property and set it to XML, as shown in the following example.
# Output format type for ls commands, which can take one of the following values:
# default: Default output
# xml : XML format
# delim : delimit columns using a character specified by "delim"
# stanza : Horizontal table format
# "format" is equivalent to option "-fmt default|xml|delim|stanza".
format: xml
Creating a NetApp User with API Privileges
Use an existing NetApp user or create one with the necessary privileges to access the application programming interface (API). This role and user is required for collection from NetApp-7 systems. Typically, the root, admin user has all the capabilities, but it is not advisable to use root or admin passwords.
To create a new user, with the required privileges, on a NetApp system, use the following Command Line Interface (CLI) steps. For the role command, do not include a space after the comma.
filer> useradmin role add apifarole -a login-http-admin,api-*
filer> useradmin group add apifagroup -r apifarole
filer> useradmin user add apifauser -g apifagroup
If api-* does not meet your security requirements, additional File Analytics privileges can be configured using the following steps:
filer> useradmin role add apifarole -a api-volume-list-info,api-nfs-exportfs-list-rules,api-cifs-share-list-iter-start,api-cifs-share-list-iter-next,api-cifs-share-list-iter-end,api-snapdiff-iter-start,api-snapdiff-iter-next,api-snapdiff-iter-end,login-http-admin,api-volume-options-list-info,api-snapshot-list-info,api-snapshot-delete,api-snapshot-create,api-nameservice-map-uid-to-user-name
filer> useradmin group add apifagroup -r apifarole
filer> useradmin user add apifauser -g apifagroup
Note: For the role command, do not include a space after the comma.
Creating a NetApp Cluster-Mode User with API Privileges
Data collection of NetApp Cluster-Mode requires a specific read-only role and user in order to collect data for a cluster.
To create a new user account with the required privileges, use the following Command Line Interface (CLI) steps. This set of commands creates a role as apt_readonly and then a user named apt_user with read-only access.
1. Create a read-only role using the following two commands.
security login role create -role apt_readonly -cmddirname DEFAULT -access readonly
security login role create -role apt_readonly -cmddirname security -access readonly
2. Create the read-only user using the following command. Once you have executed the create command, you will be prompted to enter a password for this user.
security login create -username apt_user -application ontapi -authmethod password -role apt_readonly
 
The resulting role and user login will look something like this:
Role Command/ Access
Vserver Name Directory Query Level
---------- ------------- --------- ------------------ --------
cluster1 apt_readonly DEFAULT readonly
cluster1 apt_readonly security readonly
 
 
cluster1::security login> show
Vserver: cluster1
Authentication Acct
UserName Application Method Role Name Locked
---------------- ----------- -------------- ---------------- ------
apt_user ontapi password apt_readonly no