ibm storage insights: security guide - ibm - united states · 2018-06-12 · the data collector...

IBM Storage Insights

Security GuideSC27-8774-02

IBM

Note:Before using this information and the product it supports, read the information in “Notices” onpage 37.

This edition applies to the current version of IBM Storage Insights (product number 5725-U02) and to allsubsequent versions until otherwise indicated in new editions.

This edition replaces SC27-8774-01.

© Copyright IBM Corporation 2018.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

About this guide . . . . . . . . . . . vWho should read this guide . . . . . . . . . v

Chapter 1. Summary . . . . . . . . . 1

Chapter 2. What is the data collector . . 3

Chapter 3. How is the metadataprotected . . . . . . . . . . . . . . 5

Chapter 4. What types of metadata arecollected . . . . . . . . . . . . . . 7

Chapter 5. How long is the metadatakept . . . . . . . . . . . . . . . . 9

Chapter 6. Who can access themetadata . . . . . . . . . . . . . . 11Metadata access controls and authorization . . . . 11Metadata access for resolving issues . . . . . . 12IBM Support access for troubleshooting your tickets 12Metadata access for quality improvements . . . . 12Data backup and restore . . . . . . . . . . 12Requesting the deletion of personal information . . 13

Chapter 7. Asset, capacity, andconfiguration metadata. . . . . . . . 15Block storage system metadata . . . . . . . . 15

Block volumes metadata . . . . . . . . . . 16Block pools metadata . . . . . . . . . . . 17I/O groups, nodes, and ports metadata . . . . . 17Disks and managed disks metadata . . . . . . 18File storage system metadata . . . . . . . . 18File system metadata . . . . . . . . . . . 19Fileset metadata . . . . . . . . . . . . . 19File shares metadata . . . . . . . . . . . 19File system pools metadata . . . . . . . . . 20Network shared disks metadata . . . . . . . 20File nodes metadata . . . . . . . . . . . 21Object storage systems metadata . . . . . . . 21Groups metadata . . . . . . . . . . . . 22Servers metadata . . . . . . . . . . . . 24

Chapter 8. Performance metadata . . . 25Performance metadata for storage systems that runIBM Spectrum Virtualize . . . . . . . . . . 25Performance metadata for DS8000 . . . . . . . 29Performance metadata for XIV, IBM SpectrumAccelerate, IBM FlashSystem A9000, and IBMFlashSystem A9000R . . . . . . . . . . . 31Performance metadata for IBM Spectrum Scale . . 32Performance metadata for EMC VMAX and VNX . 33

Notices . . . . . . . . . . . . . . 37Privacy policy considerations . . . . . . . . 39Trademarks . . . . . . . . . . . . . . 39

Index . . . . . . . . . . . . . . . 41

© Copyright IBM Corp. 2018 iii

||

||

iv IBM Storage Insights: Security Guide

About this guide

In IBM® Storage Insights Pro and IBM Storage Insights, detecting and resolvingissues in a storage environment has never been easier. It combines cognitivestorage management capabilities with a simplified yet robust IBM supportexperience to help you spend less time troubleshooting storage problems and moretime planning for your future storage needs.

Who should read this guideThis publication is intended for administrators or IT professionals who deploy IBMStorage Insights Pro or IBM Storage Insights and want to learn more about securityand data collection.

Administrators should be familiar with the following topics:v General procedures for installing software on Microsoft Windows, AIX®, Linux.v Storage area network (SAN) concepts.v Storage resources and management concepts.

© Copyright IBM Corp. 2018 v

vi IBM Storage Insights: Security Guide

Chapter 1. Summary

The concerns that customers might have about deploying a data collectoron-premises and processing and storing metadata off-premises are discussed.

IBM Storage Insights Pro and IBM Storage Insights are cloud service offerings thatuse a light-weight application that is called the data collector to collect and sendasset, configuration, capacity, and performance metadata for analysis to an IBMCloud data center and for presentation in the GUI.

Important: The security policies for collecting, sending, accessing, protecting, andstoring metadata for IBM Storage Insights Pro and IBM Storage Insights areidentical.

The key differences between both cloud service offerings lie in the exclusivefeatures that IBM Storage Insights Pro provides to its subscribers, such as capacityplanning analysis, reclamation analysis, and tiering analysis, and in the access tothe metadata that is presented in the GUI for the cloud service offerings. In IBMStorage Insights Pro, subscribers have access to all of the metadata in the GUI,whereas in IBM Storage Insights, users have access to key capacity andperformance metadata in the GUI, and IBM Support has read-only access to the setof metadata that they need to troubleshoot and close support tickets.

To discuss the security concerns that customers might have, the followingquestions are answered:v What is the data collector?v How is the metadata protected?v What types of metadata are collected?v How long is the metadata kept?v Who can access the metadata that is collected?

Lists of the asset, capacity, and configuration metadata and the performancemetadata that is collected and stored about your storage systems are also provided.Related reference:Chapter 7, “Asset, capacity, and configuration metadata,” on page 15The data collector collects and stores asset, capacity, and configuration metadatafor block, file, and object storage systems and their resources. A list of thesupported storage systems is provided.Chapter 8, “Performance metadata,” on page 25The data collector collects and stores performance metadata for IBM block storagesystems and non-IBM block storage systems and it collects and stores file systemand node performance metadata for IBM Spectrum Scale™ storage systems.

© Copyright IBM Corp. 2018 1

2 IBM Storage Insights: Security Guide

Chapter 2. What is the data collector

The data collector is the application that collects and delivers the metadata that isanalyzed and presented in the GUI.

The data collector is a light-weight application that is installed on a server in yourdata center. It sends the metadata that is collected about your storage systems,such as asset, configuration, capacity, and performance metadata, from your datacenter to your instance of IBM Storage Insights Pro or IBM Storage Insights, whichis in an IBM Cloud data center.

Important: Outbound metadata is sent by the data collector to a single, uniqueaddress, which is the IBM host name and port of your instance. This means thatwhen you configure your firewall to send the metadata, you open a single path toa well-defined and secure endpoint.

In a matter of minutes, you can install the data collector and when you add thestorage systems that you want to monitor, you get the capacity and performanceinsights that you need to monitor your data center. Because the metadata that IBM


Support needs to investigate and close tickets is also collected, you can also uploadlogs automatically when you create or update tickets and IBM Support can accessand investigate the metadata to resolve any issues that you might have.

Supported operating systems: Data collectors can be installed on servers that runAIX, Linux, or Windows operating systems. The server on which you install thedata collector must have a minimum of 1 GB RAM and 1 GB of free disk space.

Security certification: IBM Storage Insights, based on regular audits, has ISO/IEC27001 Information Security Management certification.

Key security characteristics

To ensure that metadata is collected securely, the data collector has the followingcharacteristics:

In-built securityCommunication with other entities, such as storage systems in the localdata center and the IBM Storage Insights service in the IBM Cloud datacenter are initiated solely by the data collector. The data collector does notprovide any remote APIs that might be used to interact with the datacollector.

One-way communicationThe data collector sends metadata out of your network to your instance ofIBM Storage Insights Pro or IBM Storage Insights. Communication isoutbound only; the data collector can't receive data from the internet orany other entity in your network.

Secure transmissionAll communication between the data collector and IBM Storage InsightsPro or IBM Storage Insights in the IBM Cloud data center uses encryptionbased on HTTPS.

The communication that the data collector initiates with the server where itis installed, and the communication between the server and IBM StorageInsights Pro GUI or IBM Storage Insights GUI uses HTTPS connections.HTTPS connections are signed by DigiCert Inc., which uses TLS 1.2 with128-bit keys.

Tip: Because HTTPS connections are used, the data collector can run onany computer that can access the internet over an outbound TCPconnection to port 443. Port 443 is the standard port for HTTPSconnections.


https://www.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=KUJ12445USEN

https://www.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=KUJ12445USEN

Chapter 3. How is the metadata protected

End-to end protection is provided for the metadata that is collected, delivered, andstored for your instance of IBM Storage Insights Pro or IBM Storage Insights in theIBM Cloud data center.

Metadata collection, delivery, and storage in the cloud

To transform the metadata into insights and present them in IBM Storage InsightsPro or IBM Storage Insights, the data collector forwards metadata packages foranalysis and storage to an IBM Cloud data center.

To keep the metadata package safe on its journey to the cloud, the data collectoruses Hypertext Transfer Protocol Secure (HTTPS), which encrypts the metadataand sends the metadata package through a secure channel to the IBM Cloud datacenter.

At the gateway, or reverse proxy gateway, the metadata package gets instructionsto deliver the package to your instance of IBM Storage Insights Pro or IBM StorageInsights.

When the metadata package is delivered, the metadata is decrypted, analyzed, andstored.

From your data center to the internet

HTTPS connections are used to compress and encrypt the metadata that iscollected about your storage systems and sent to your IBM Cloud data center.


As part of the onboarding process, you are provided with a host name and portnumber for your instance of IBM Storage Insights Pro or IBM Storage Insights. Tosecure the outbound communication between the data collector and IBM StorageInsights Pro or IBM Storage Insights, a Secure Sockets Layer (SSL) certificate isused.

To send the metadata, your firewall must be configured to allow outboundcommunication on HTTPS port 443 using TCP to the address of your instance.

At the IBM Cloud data center

IBM Storage Insights Pro and IBM Storage Insights are hosted in IBM Cloud datacenters, which comply with high physical, technical, and organizational securitystandards.

Physical protection

The data centers are rigorously controlled and onsite security is providedround the clock. Access to server-rooms is limited to certified employeesand security controls are vetted by third-party auditors.

See https://www.ibm.com/cloud-computing/bluemix/data-centers andhttps://www.ibm.com/cloud-computing/bluemix/trust-security-privacy.

Technical security

Each instance of IBM Storage Insights Pro or IBM Storage Insights isisolated from other instances of IBM Storage Insights Pro or IBM StorageInsights at the compute and at the storage layer.

Note: Dedicated SAN disks are used for each instance.

Each instance also uses its own database, which stores only data for thatinstance. The database is encrypted separately using native IBM DB2®

encryption with a strong cryptographic algorithm, AES 256-bit encryption.

See https://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.sec.doc/doc/c0061758.html.

On a day-to-day basis, the following security software and services areused:v Mantes Endpoint Protection to protect against malwarev IBM Bigfix® to comply with security and regulatory requirementsv IBM Security QRadar® SIEM to store and monitor system and

application logs

Organizational security

Access to the infrastructure and instances for IBM Storage Insights Pro andIBM Storage Insights, is controlled:v By restricting access to the members of the DevOps team and cloud

service infrastructure teams who qualify as privileged users.v By conducting regular system health and vulnerability scans at the

source code level and on the running instances.v By conducting regular penetration tests. External companies conduct the

penetration tests.

GDPR: IBM Storage Insights can assist you in meeting the requirements of the EUGeneral Data Protection Regulation.


||

https://www.ibm.com/cloud-computing/bluemix/data-centers

https://www.ibm.com/cloud-computing/bluemix/trust-security-privacy

https://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.sec.doc/doc/c0061758.html

https://www.ibm.com/support/knowledgecenter/SSEPGG_10.5.0/com.ibm.db2.luw.admin.sec.doc/doc/c0061758.html

Chapter 4. What types of metadata are collected

Asset, capacity, configuration, and performance metadata are collected and storedfor the storage systems that are monitored. Diagnostic data is also collected intolog packages and added to support tickets.

Metadata about the configuration and operations of storage resources is collected,and not the actual data that is stored on the storage systems or their resources.

The metadata that is collected is used:v To provide and improve servicesv To analyze and get insights into storage usage and performancev To generate charts and present data in the GUIv To upload logs automatically when support tickets are created or updatedv To enable IBM Support to investigate and close the issues that you might

encounter

The types of the metadata that are collected and stored are as follows:

Asset metadataName, model, firmware, and type of storage system.

Configuration metadataName and number of the resources that are associated with the storagesystem such as the number of disks, pools, and volumes.

Capacity metadataStorage usage values such as total volume capacity, unassigned volumespace, pool capacity, used pool space, and raw disk capacity.

Performance metadataPerformance metrics, such as read and write data rates, I/O rates, andresponse times.

Relationships metadataIn IBM Storage Insights Pro, metadata is collected to represent generalgroups, applications, and departments that are created to show storageusage and performance metadata.

Server metadataIn IBM Storage Insights Pro, asset and capacity metadata is collected aboutthe servers that are added for monitoring.

Data collector metadataTo monitor the performance of the data collector and resolve datacollection issues, the name of the server that hosts the data collector, thestatus of the data collector, and when the data collector was last run iscollected.

To get the metadata, the information that is used to connect to the storage systemsthat are monitored is also collected and stored. The information is stored in thedatabase that was created for your instance of IBM Storage Insights Pro or IBMStorage Insights and passwords are encrypted before they are stored in thedatabase.


||

IBM Support ticket and diagnostic log packages

When IBM Storage Insights Pro or IBM Storage Insights collects a diagnostic logpackage from your storage system, it transfers the package to IBM Support usingHTTPS. The log package is put where IBM Support needs it to be.

When users create tickets in IBM Storage Insights Pro or IBM Storage Insights, theyprovide a name, an email address and a phone number so that IBM Support cancontact them. The contact details are not stored by IBM.

IBM Storage Insights Pro and IBM Storage Insights collect and upload thediagnostic data that is collected for IBM block storage systems to IBM EnhancedCustomer Data Repository (ECuRep).

What is ECuRep: ECuRep is an IBM strategic worldwide Post Sales TechnicalSupport solution for client diagnostic data transmission, storing, and analysis.

The diagnostic data package is uploaded to ECuRep using HTTPS.

IBM Storage Insights Pro or IBM Storage Insights doesn't process the diagnosticdata packages, which might contain data other than the capacity and performancemetadata that is collected about the storage systems, such as the ID of the userwho completed an operation.


|||

||

|

Chapter 5. How long is the metadata kept

Information is provided about the retention periods for asset, capacity andconfiguration metadata and for performance metadata.

When you add storage systems, asset, configuration, capacity, and performancemetadata is collected about the storage systems.

IBM Storage Insights Pro: Metadata is collected and retained for the followingpurposes:v To detect changes in storage usage so that capacity can be plannedv To detect and troubleshoot performance issuesv To analyze capacity trends and predict future storage usage such as when pool

capacity will be depletedv To analyze volume activity to identify the volumes that can be reclaimedv To analyze tiering so that recommendations can be provided for volume

placementv To automatically upload logs when users open or update support ticketsv To provide IBM Support with the metadata that they need to investigate and

close open ticketsv To analyze to identify improvements to the servicev To analyze your storage so that recommendations can be provided

IBM Storage Insights: Metadata is collected and retained for the followingpurposes:v To analyze and present key storage usage metadatav To analyze and present key performance metadatav To automatically upload logs when users open or update support ticketsv To provide IBM Support with the metadata that they need to investigate and

close open ticketsv To analyze to identify improvements to the servicev To analyze your storage so that recommendations can be provided

As the metadata is collected, the aggregation level of the metadata changes. Forasset, configuration, and capacity metadata, over a 24-month period, theaggregation levels of the metadata change from daily, to weekly, to monthly basedon the age of the metadata. For performance metadata, over a 52-week period, theaggregation levels change from sample, to hourly, to daily based on the age of theperformance metadata. In effect, a more granular view of new metadata isprovided and a less granular view of aged metadata is provided.

The following table lists the aggregation levels for asset, configuration, andcapacity metadata based on the age of the data that is collected:

Table 1. Asset, configuration, and capacity metadata

Aggregation level Metadata age

Daily 12 weeks

Weekly 24 weeks


|

|

|

|

Table 1. Asset, configuration, and capacity metadata (continued)


Monthly 24 months

The following table lists the aggregation levels for performance metadata based onthe age of the data that is collected:

Table 2. Performance metadata


Sample 2 weeks

Hourly 4 weeks

Daily 52 weeks

Based on the collection date, metadata is retained for up to two years.

How long are diagnostic data packages kept

Typically, diagnostic data is automatically deleted from IBM Enhanced CustomerData Repository (ECuRep) 30 days after the ticket is closed. For information about

the retention of data in ECuRep, see the IBM Knowledge Center for IBMSpectrum Control™ (http://www.ibm.com/de/support/ecurep/terms.html).Related tasks:“Requesting the deletion of personal information” on page 13To delete the minimal personal information that was stored to provide you withmonitoring and support services for your storage systems, you can submit arequest to IBM Support.


|

||

||

Chapter 6. Who can access the metadata

Information is provided about access to the metadata that is collected and stored.

Access to the metadata that is collected and stored for your instance of IBMStorage Insights Pro or IBM Storage Insights is restricted:v To the DevOps and cloud service infrastructure teams who are responsible for

the maintenance and day-to-day operation of your instancev To IBM Support for investigating and closing support tickets and for

downloading support logs to investigate issues

Note: IBM Support has read-only access to the metadata that is collected aboutblock storage systems and their internal resources.

To access the metadata in the IBM Cloud network and ensure that the connectionis secure, DevOps and cloud service infrastructure teams use a secure virtualprivate network (VPN) connection. Access to instances is only permitted fromprivileged user workstations, which must meet the strict security controls of IBMSecurity policies for production servers.

The access to metadata for DevOps and cloud service infrastructure teams isrestricted:v To the infrastructure for the cloud servicev To the operating systemv To add-on services such as agentsv To middleware components

Metadata access controls and authorizationAccess controls and authorization checks are enforced for SaaS infrastructurecomponents and services.

An approval process is used to authorize access to the following infrastructuralelements and services:v The networkv The operating systemv The middleware componentsv The applicationv Administrative services

The following change management processes are adhered to for managing changesto the production environment:v Changes to the production environment must be recorded and must be

approved by the change advisory boardv All support activities must be tracked in the IBM Support Portal for cloud

servicesv All operational and maintenance activities must be tracked by the internal

ticketing system


Metadata access for resolving issuesTo investigate and resolve issues, access is required to metadata and instances ofIBM Storage Insights Pro or IBM Storage Insights.

To find the causes of issues, investigations are undertaken that might requireaccess to the metadata that is collected and stored, or access to infrastructuralelements, or both. For example, the DevOps team or IBM Support, might need tomonitor instances of the application to determine the cause of interruptions inservice, or to investigate interruptions in the collection of metadata. To resolvesuch issues, it might be necessary:v To analyze the configuration of the instancev To analyze log filesv To analyze the metadata that was collected

To thoroughly investigate some issues, it might also be necessary to package themetadata and transfer it to a secure IBM system so that the development team cancomplete the investigation.

IBM Support access for troubleshooting your tickets

To investigate the hardware and software tickets that users open, IBM Support hasread-only access to the metadata that is collected.

When users create tickets, IBM might need to access the metadata that is collectedfor IBM Storage Insights Pro or IBM Storage Insights.

To close tickets, IBM Support has read-only access to the asset, configuration,capacity, and performance metadata that is collected for the IBM block storagesystems and their internal storage resources. If streaming diagnostic metadata isinsufficient to troubleshoot your issue, IBM Support might need to collect a logpackage from your storage. In this case, IBM Support can attach the log package toan open ticket and submit the log package to IBM Enhanced Customer DataRepository (ECuRep).

Metadata access for quality improvementsAnonymized metadata is used to improve the quality of service and to enhance theproduct offering.

A subset of the metadata from all of the instances is aggregated and condensed forfurther analysis. The data that is used is anonymized:v It does not include instance-specific metadatav It does not include customer-specific metadata such as IP addresses

For example, the aggregated metadata contains such information as the number ofdifferent types of storage systems or the number of different firmware levels forthe storage systems that are monitored. The aggregated metadata might containGUI and usage metrics, but it doesn't contain the names, the serial numbers, or theIP addresses of the storage systems.

Data backup and restoreTo restore instances, regular backups of the data are made automatically.


|

||

|||||||

Backups are made daily, which means that recovery point objective (RPO) is oneday, and the recovery time objective (RTO) is between 1.5 and 2 days.

Backups are stored both locally, in the same data center, and remotely. The latestbackup of the instance is stored in a remote data center, whereas the five previousbackups are stored in the local data center.

Requesting the deletion of personal informationTo delete the minimal personal information that was stored to provide you withmonitoring and support services for your storage systems, you can submit arequest to IBM Support.

If you cancel your subscription for IBM Storage Insights Pro or decide that you nolonger want to monitor your storage environment with IBM Storage Insights, youcan request that the minimal personal information is deleted.1. Go to IBM Support.2. Sign in.3. Click Go to my cases.4. Create a new case and request the deletion of your personal information.

Chapter 6. Who can access the metadata 13

|

|||

|||

|

|

|

|

https://www.ibm.com/mysupport/

Chapter 7. Asset, capacity, and configuration metadata

The data collector collects and stores asset, capacity, and configuration metadatafor block, file, and object storage systems and their resources. A list of thesupported storage systems is provided.

Asset, capacity, and configuration, metadata is collected and stored for thefollowing IBM block storage systems and non-IBM block storage systems whenthey are added for monitoring.

Table 3. Asset, capacity, and configuration metadata by storage systemStorage System IBM Storage Insights Pro IBM Storage InsightsDS8000® Yes YesEMC VMAX Yes NoEMC VNX Yes NoFlashSystem 840 Yes YesFlashSystem 900 Yes YesFlashSystem A9000 Yes YesFlashSystem A9000R Yes YesFlashSystem V840 Yes YesFlashSystem V9000 Yes YesIBM Spectrum Accelerate™ Yes YesSAN Volume Controller Yes YesStorwize® V3500 Yes YesStorwize V3700 Yes YesStorwize V5000 Yes YesStorwize V7000 Yes YesStorwize V7000 Unified Yes YesXIV® Yes Yes

In IBM Storage Insights Pro, asset, capacity, and configuration metadata is collectedfor the following file, object, and software-defined storage systems when they areadded for monitoring:v EMC VNXv EMC VNXev IBM Cloud Object Storagev IBM SONASv IBM Spectrum Scalev Storwize V7000 Unified

Block storage system metadataView the list of the asset, configuration, and capacity metadata for block storagesystems.

Depending on the type of storage system, and the features that the storage systemsupports, some or all of the following metadata is collected and stored:

Table 4. Storage system asset, capacity, and configuration metadataData name Data nameAssigned Volume Space (GiB) Pools


Table 4. Storage system asset, capacity, and configuration metadata (continued)Data name Data nameAvailable Pool Space (GiB) PortsAvailable Pool Space (GiB) Raw Disk Capacity (GiB)Compressed Read Cache (GiB)Compression Savings (%) Remote RelationshipsCustom Tag 1 2, 3 Serial NumberData Deduplication Savings (%) Shortfall (%)Data Collection Time ZoneData Reduction Savings (%)Disks Total Volume Capacity (GiB)Effective Capacity (%) Turbo PerformanceFirmware TypeFlashCopy Unassigned Volume Space (GiB)IP Address Used Pool Space (GiB)Location Used Space (GiB)Managed Disks VDisk MirrorsModel VendorName Virtual Allocation (%)Physical Allocation (%) VolumesPhysical Allocation (%) Write Cache (GiB)Pool Capacity (GiB) Write Cache (GiB)

Block volumes metadataView the list of the asset, capacity, and configuration metadata for volumes.

Depending on the type of storage system, and the features that the storage systemsupports, some or all of the following metadata is collected and stored for blockstorage volumes.

Table 5. Volume asset, capacity, and configuration metadataData name Data nameAllocated Space (GiB) Physical Allocation (%)Auto Expand PoolCapacity (GiB) RAID LevelCompression Savings (%) Shortfall (%)Copies SSD Capacity (GiB)Copy Relationship Storage SystemEasy Tier Storage VirtualizerEnterprise HDD Capacity (GiB) TargetFast Write State Thin ProvisionedFormatted Tier Distribution (%)Grain Size (KiB) Unallocated Space (GiB)Hosts Unique IDI/O Group Unused Space (GiB)ID Used Allocated Space (%)Last Data Collection Used Space (GiB)Mirror Virtual Allocation (%)Name Virtualizer Disk TypeNearline HDD Capacity (GiB) Virtualizer DiskNode Warning Level (%)


Block pools metadataView the list of the asset, capacity, and configuration metadata for block storagepools.

Depending on the type of storage system, and the features that the storage systemsupports, some or all of the following metadata is collected and stored for storagepools:

Table 6. Pool asset, capacity and configuration metadataData name Data nameActivity Nearline HDD Capacity (GiB)Allocated Space (GiB) Owner NameAssigned Volume Space (GiB) Physical Allocation (%)Available Pool Space (GiB) RAID LevelAvailable Repository Space (GiB) Rank GroupAvailable Soft Space (GiB) Repository Capacity (GiB)Back-end Storage Disk Type Shortfall (%)Back-end Storage Disks Soft Space (GiB)Back-end Storage RAID Level Solid StateBack-end Storage System Type SSD Available Space (GiB)Capacity (GiB) SSD Capacity (GiB)Compression Savings (%) Storage SystemCustom Tag 1,2 , 3 Tier

Tier Distribution (%)Easy Tier Total Volume Capacity (GiB)EncryptionEncryption Group Unallocatable Volume Space (GiB)Enterprise HDD Available Space (GiB) Unallocated Volume Space (GiB)Enterprise HDD Capacity (GiB) Unassigned Volume Space (GiB)Extent Size (MiB) Unused Space (GiB)Format Used Space (GiB)Last Data Collection Virtual Allocation (%)LSS or LCU VolumesManaged Disks Zero CapacityNameNearline HDD Available Space (GiB)

I/O groups, nodes, and ports metadataView the lists of the asset, capacity, and configuration metadata for I/O groups,nodes, and ports.

Depending on the type of storage system, and the features that the storage systemsupports, some or all of the following metadata is collected and stored for I/Ogroups, nodes, and ports:

Table 7. I/O groups asset, capacity, and configuration metadataData name Data nameCompression

NameNodesTotal FlashCopy Memory (MiB)Total Mirroring Memory (MiB)

Total Remote Copy Memory (MiB)Used FlashCopy Memory (MiB)Used Mirroring Memory (MiB)Used Remote Copy Memory (MiB)Volumes

Chapter 7. Asset, capacity, and configuration metadata 17

Table 8. Nodes asset, capacity and, configuration metadataData name Data nameCompressionConfiguration node

FC PortsI/O GroupIP address

ModelNamePanel nameSerial numberSpare nodesWWN

Table 9. Ports asset, capacity, and configuration metadataData name Data nameName WWPNSpeed (Gbps)

Disks and managed disks metadataView the lists of the asset, capacity, and configuration metadata for disks andmanaged disks.

Depending on the type of storage system, and the features that the storage systemsupports, some or all of the following metadata is collected and stored for disksand managed disks:

Table 10. Disks asset, capacity, and configuration metadataData name Data nameCapacity (GB)Capacity (GiB)ClassFirmware

ModelName

Serial number

SpareSpeed (RPM)StatusVendor

Table 11. Managed disks (MDisks) asset, capacity, and configuration metadataData name Data nameActive Quorum ModeAvailable Space (GiB) NameBack-end Storage System PoolCapacity (GiB) RAID LevelClass Storage SystemEasy Tier Volumes

File storage system metadataView the list of the asset, configuration, and capacity metadata for file storagesystems.

Depending on the type of file storage system, and the features that the file storagesystem supports, some or all of the following metadata is collected and stored:

Restriction: Applies only to IBM Storage Insights Pro.

Table 12. Storage system asset, capacity, and configuration metadataData name Data nameAvailable File System Space (GiB) Model


|

Table 12. Storage system asset, capacity, and configuration metadata (continued)Data name Data nameCluster NameCustom Tag 1, 2, 3 Raw Disk Capacity (GiB)Data Collection Serial NumberDisks Total File System Capacity (GiB)External Pool Used Space (GiB) TypeFile System Capacity (%) Used File System Space (GiBIP Address VendorLocation Version

File system metadataView the list of the asset, configuration, and capacity metadata for file systems.



Table 13. File system asset, capacity, and configuration metadataData name Data nameAvailable Inodes NSDsAvailable Space (GiB) PathCapacity (%) Physical Capacity (GiB)Cluster PoolsCustom Tag 1, 2, 3 Storage SystemFile System Type Total Capacity (GiB)Filesets Used InodesLast Probe Time Used Inodes (%)Maximum Inodes Used Space (GiB)Name

Fileset metadataView the list of the asset, configuration, and capacity metadata for filesets.

Depending on the type of file storage system, and the features that the file storagesystem supports, some or all of the following metadata is collected and stored.


Table 14. Fileset asset, capacity, and configuration metadataData name Data nameCache Role NameComment PathFile System StateHome System Name Used Space (GiB)

File shares metadataView the list of the asset, configuration, and capacity metadata for file shares.


Depending on the type of file storage system, and the features that the file storagesystem supports, some or all of the following metadata is collected and stored.


Table 15. File shares asset, capacity, and configuration metadataData name Data nameCluster Shared ServersDiscovered Time StateName Storage SystemPath TicketProtocols

File system pools metadataView the list of the asset, configuration, and capacity metadata for file systempools.



Table 16. File system pools asset, capacity, and configuration metadataData name Data nameAvailable Space (GiB) Inactive Used Space (GiB)Capacity (%) NameCluster Storage SystemExternal Used Space (GiB) Total Capacity (GiB)File System Used Space (GiB)Inactive Used Space (%)

Network shared disks metadataView the list of the asset, configuration, and capacity metadata for network shareddisks.

Depending on the type of file storage system, and the features that the file storagesystem supports, some or all of the following metadata is collected and storedabout network shared disks:


Table 17. Network shared disks asset, capacity, and configuration metadataData name Data nameAvailable Space (GiB) NameCluster PoolCorrelated Storage Volume Probe TimeCustom Tag 1, 2, 3 Storage SystemDisk Capacity (%) Total Disk Capacity (GiB)Failure Group TypeFile System Used Space (GiB)ID


File nodes metadataView the list of the asset, configuration, and capacity metadata for file nodes.

Depending on the type of file storage system, and the features that the file storagesystem supports, some or all of the following metadata is collected and storedabout file nodes.


Table 18. File nodes asset, capacity, and configuration metadataData name Data nameCache Gateway Node RoleCluster Serial numberIP Address Storage SystemName Version

Object storage systems metadataView the lists of the asset, configuration, and capacity metadata for object storagesystems and their internal resources.

Some or all of the following metadata is collected and stored for object storagesystems and their internal storage resources such as:v Access poolsv Accesser nodesv Storage poolsv Slicestor nodesv Sitesv Vaults


Table 19. Storage system asset, capacity, and configuration metadataData name Data nameAccess pools NameAvailable Space (GiB) ObjectsCapacity (%) Total Capacity (GiB)Containers TypeCustom Tag 1, 2, 3 Used Space (GiB)Data Collection VaultsIP Address VendorLocation Version

Table 20. Access pools asset, capacity, and configuration metadataData name Data nameMirrors VaultsName SiteProtocol

Table 21. Accesser nodes asset, capacity, and configuration metadataData name Data nameAccess Pool Serial Number


Table 21. Accesser nodes asset, capacity, and configuration metadata (continued)Data name Data nameIP Address SiteModel Software VersionName

Table 22. Storage pools asset, capacity, and configuration metadataData name Data nameCapacity (%) Storage PoolsName Total Capacity (GiB)Sets Used Space (GiB)Site Vaults

Table 23. Slicestor nodes asset, capacity, and configuration metadataData name Data nameAvailable Space (GiB) Set IDCapacity (%) SiteDrives Software VersionIP Address Storage PoolModel Total Capacity (GiB)Name Used Space (GiB)Serial Number

Table 24. Sites asset, capacity, and configuration metadataData name Data nameAccess Nodes Slicestor NodesAccessibility Total Capacity (GiB)Available Space (GiB) Used Space (GiB)Capacity (%) VaultsName

Table 25. Vaults asset, capacity, and configuration metadataData name Data nameAccess Pools SitesAccessibility Soft Quota (GiB)Creation Date Space Quota (%)Hard Quota (GiB) Storage PoolIDA Storage SystemMirror Used Space (GiB)Name

Groups metadataView the lists of the asset, configuration, and capacity metadata for general groups,applications, and departments.

The metadata that is associated with the general groups, applications, anddepartments such as volumes is also collected and stored as are the filterdefinitions that are created so that you can see the capacity and performancemetadata for each type of group in one place.



Table 26. General groups asset, capacity, and configuration metadataData name Data nameName Subgroups

Table 27. Applications asset, capacity, and configuration metadataData name Data nameBlock Capacity (GiB) ServersCustom Tag 1, 2, 3 SubtypeDepartments TypeFile Capacity (GiB) VaultsName VolumesObject Capacity (GiB)

Table 28. Accesses nodes asset, capacity, and configuration metadataData name Data nameAccess Pool Serial NumberIP Address SiteModel Software VersionName

Table 29. Storage pools asset, capacity, and configuration metadataData name Data nameCapacity (%) Storage PoolsName Total Capacity (GiB)Sets Used Space (GiB)Site Vaults

Table 30. Slicestor nodes asset, capacity, and configuration metadataData name Data nameAvailable Space (GiB) Set IDCapacity (%) SiteDrives Software VersionIP Address Storage PoolModel Total Capacity (GiB)Name Used Space (GiB)Serial Number

Table 31. Sites asset, capacity, and configuration metadataData name Data nameAccess Nodes Slicestor NodesAccessibility Total Capacity (GiB)Available Space (GiB) Used Space (GiB)Capacity (%) VaultsName

Table 32. Vaults asset, capacity, and configuration metadataData name Data nameAccess Pools SitesAccessibility Soft Quota (GiB)Creation Date Space Quota (%)Hard Quota (GiB) Storage PoolIDA Storage SystemMirror Used Space (GiB)


Table 32. Vaults asset, capacity, and configuration metadata (continued)Data name Data nameName

Servers metadataView the list of the asset, capacity and configuration metadata for servers.

Metadata is collected about servers, their disks and controllers, and the relatedstorage resources, such as the volumes that they use.

Table 33. Servers asset, capacity, and configuration metadataData name Data nameAllocated SAN Space (GiB) LocationAssigned SAN Space (GiB) NameCustom Tag 1, 2, 3 OS TypeDomain Name Total Disk Space (GiB)IP Address

Table 34. Controllers metadataData name Data nameAssociated Disks NameHBA WWN Type

Table 35. Disks metadataData name Data nameCapacity (GiB) PathsCapacity (GB) Serial NumberName Vendor


Chapter 8. Performance metadata

The data collector collects and stores performance metadata for IBM block storagesystems and non-IBM block storage systems and it collects and stores file systemand node performance metadata for IBM Spectrum Scale storage systems.

Performance metadata is collected and stored for the following IBM block storagesystems and non-IBM block storage systems when they are added for monitoring:

Table 36. Block performance metadata by storage systemStorage System IBM Storage Insights Pro IBM Storage InsightsDS8000 Yes YesEMC VMAX Yes NoEMC VNX Yes NoFlashSystem 840 Yes YesFlashSystem 900 Yes YesFlashSystem A9000 Yes YesFlashSystem A9000R Yes YesFlashSystem V840 Yes YesFlashSystem V9000 Yes YesIBM Spectrum Accelerate Yes YesSAN Volume Controller Yes YesStorwize V3500 Yes YesStorwize V3700 Yes YesStorwize V5000 Yes YesStorwize V7000 Yes YesStorwize V7000 Unified Yes YesXIV Yes Yes

Node and file system performance metadata is also collected and stored for IBMSpectrum Scale storage systems.

Restriction: Applies to IBM Storage Insights Pro.

Performance metadata for storage systems that run IBM SpectrumVirtualize

View the lists of the performance metadata for SAN Volume Controller, Storwize,FlashSystem V840, FlashSystem V9000 storage systems, the IBM SpectrumVirtualize™ software-only solution, and other resources that run IBM SpectrumVirtualize.

Volume metrics

Table 37. Key volume performance metadataName NameData Rate (Read) Overall I/O Rate (Total)Data Rate (Write) Pool Activity ScoreData Rate (Total) Response Time (Read)Overall I/O Rate (Read) Response Time (Write)Overall Host Attributed Response TimePercentage

Response Time (Overall)


||

Table 37. Key volume performance metadata (continued)Name NameOverall I/O Rate (Read) Volume UtilizationOverall I/O Rate (Write) Write Cache Delay

Table 38. Volume I/O rate performance metadataName NameTransfer Rate (Cache-to-Disk) Write-Cache Delay I/O RateTransfer Rate (Disk-to-Cache)

Table 39. Volume cache hit percentage metadataName NameOverall I/O Cache Hits (Read) Overall I/O Cache Hits (Total)Overall I/O Cache Hits (Write)

Table 40. Volume response time performance metadataName NamePeak Response Time (Read) Peak Response Time (Write)

Table 41. Volume remote mirror performance metadataName NameGlobal Mirror (Overlapping Write I/O Rate) Global Mirror (Secondary Write Lag)Global Mirror (Overlapping WritePercentage)

Global Mirror (Write I/O Rate)

Table 42. Volume cache performance metadataName NameCache Hits (Dirty Writes) Response Time (Stage)Cache Hits (Read) Transfer Rates (Cache-to-Disk)Cache Hits (Total) Transfer Rates (Disk-to-Cache)Cache Hits (Write) Write Delay Percentage (Flush-through)I/O Rate (Destage) Write Delay Percentage (Total Delay)I/O Rate (Read) Write Delay Percentage (Write-through)I/O Rate (Total) Write Delay Rate (Flush-through)I/O Rate (Write) Write Delay Rate (Total Delay)Response Time (Destage) Write Delay Rate (Write-through)

Table 43. Volume copy cache performance metadataName NameCache Hits (Dirty Writes) Response Time (Prestage)Cache Hits (Read-ahead) Response Time (Stage)Cache Hits (Read) Transfer Rates (Cache-to-Disk)Cache Hits (Total) Transfer Rates (Disk-to-Cache)Cache Hits (Write) Write Delay Percentage (Flush-through)I/O Rate (Destage) Write Delay Percentage (Total Delay)I/O Rate (Prestage) Write Delay Percentage (Write-through)I/O Rate (Stage) Write Delay Rate (Flush-through)I/O Rate (Total) Write Delay Rate (Total Delay)I/O Rate (Write) Write Delay Rate (Write-through)Response Time (Destage) Response Time (Stage)


Table 44. Volumes compression performance metadataName NameCompressed Volumes (Data Rate) Uncompressed Volumes (Data Rate)Compressed Volumes (I/O Rate) Uncompressed Volumes (I/O Rate)Compressed Volumes (Response Time) Uncompressed Volumes (Response Time)

Table 45. Volumes miscellaneous performance metadataName NameCache to Host Transfer Response Time Transfer Size (Write)Non-Preferred Node Usage Percentage Transfer Size (Overall)Transfer Size (Read) Unaligned Write I/O Rate

Table 46. Volume legacy performance metadataName NameWrite-Cache Percentages (Flush-through) Write-Cache I/O Rate (Overflow)Write-Cache Percentages (Write-through) Write-Cache I/O Rate (Write-through)Write-Cache Percentages (Overflow) Dirty Write Percentage of Cache HitsWrite-Cache I/O Rate (Flush-through)

Disks

Table 47. Key metadataName NameData Rate (Read) I/O Rate (Total)Data Rate (Write) Response Time (Read)Data Rate (Total) Response Time (Write)I/O Rate (Read) Response Time (Overall)I/O Rate (Write)

Table 48. Response time performance metadataName NamePeak Back-end Queue Time (Read) Queue Time (Overall)Peak Back-end Queue Time (Write) Queue Time (Read)Peak Back-end Response Time (Read) Queue Time (Write)Peak Back-end Response Time (Write)

Table 49. Miscellaneous performance metadataName NameTransfer Size (Read) Cache Destage (In-Flight I/O)Transfer Size (Write) Cache Destage (Target I/O)Transfer Size (Overall)

Ports

Table 50. Key metadataName NameI/O Rate (Receive) Data Rate (Receive)I/O Rate (Send) Data Rate (Send)I/O Rate (Total) Data Rate (Total)

Table 51. I/O rates metadataName NamePort-to-Disk I/O Rate (Receive) Port-to-Local Node I/O Rate (Receive)

Chapter 8. Performance metadata 27

|||||||||||

Table 51. I/O rates metadata (continued)Name NamePort-to-Disk I/O Rate (Send) Port-to-Local Node I/O Rate (Send)Port-to-Disk I/O Rate (Total) Port-to-Local Node I/O Rate (Total)Port-to-Host I/O Rate (Receive) Port-to-Remote Node I/O Rate (Receive)Port-to-Host I/O Rate (Send) Port-to-Remote Node I/O Rate (Send)Port-to-Disk I/O Rate (Receive) Port-to-Remote Node I/O Rate (Total)Port-to-Host I/O Rate (Total)

Table 52. Data rate performance metadataName NamePort-to-Disk Data Rate (Receive) Port-to-Local Node Data Rate (Receive)Port-to-Disk Data Rate (Send) Port-to-Local Node Data Rate (Send)Port-to-Disk Data Rate (Total) Port-to-Local Node Data Rate (Total)Port-to-Host Data Rate (Receive) Port-to-Remote Node Data Rate (Receive)Port-to-Host Data Rate (Send) Port-to-Remote Node Data Rate (Send)Port-to-Host Data Rate (Total) Port-to-Remote Node Data Rate (Total)

Table 53. Response time performance metadataName NamePort-to-Local Node Response Time (Receive) Port-to-Remote Node Response Time

(Receive)Port-to-Local Node Response Time (Send) Port-to-Remote Node Response Time (Send)Port-to-Local Node Response Time (Overall) Port-to-Remote Node Response Time

(Overall)Port-to-Remote Node Response Time(Overall)

Table 54. Error rate performance metadataName NameCRC Error Rate Link Errors (Sync Loss)Link Errors (Invalid Link Transmission Rate) Port Congestion IndexLink Errors (Invalid Transmission Word Rate) Port Protocol Errors (Port Send Delay Time)Link Errors (Link Failures) Port Protocol Errors (Port Send Delay I/O

Percentage)Link Errors (Primitive Sequence ProtocolError Rate)

Port Protocol Errors (Zero Buffer CreditPercentage)

Link Errors (Signal Loss) Port Protocol Errors (Zero Buffer CreditTimer)

Table 55. Miscellaneous port performance metadataName NamePort-to-Local Node Queue Time (Receive) Port-to-Remote Node Queue Time (Receive)Port-to-Local Node Queue Time (Send) Port-to-Remote Node Queue Time (Send)Port-to-Local Node Queue Time (Overall) Port-to-Remote Node Queue Time (Overall)

Nodes

Table 56. Nodes performance metadataName NameCPU Utilization (System CPU) Compression CPU Utilization (Core 1 to Core

8)CPU Utilization (Compression CPU) Node Utilization by NodeSystem CPU Utilization (Core 1 to Core 8)


Performance metadata for DS8000View the lists of performance metadata for DS8000 storage systems.

Volume metadata

Table 57. Key volume performance metadataName NameCache Holding Time Pool Activity ScoreData Rate (Read) Response Time (Read)Data Rate (Write) Response Time (Write)Data Rate (Total) Response Time (Overall)Overall I/O Rate (Read) Volume UtilizationOverall I/O Rate (Write) Write-Cache Delay PercentageOverall I/O Rate (Total)

Table 58. Volume I/O rates metadataName NameAverage Transfer Rate (Cache-to-Disk) Normal I/O Rate (Total)Average Transfer Rate (Disk-to-Cache) PPRC Transfer RateHigh Performance FICON® (Read) Record Mode Read I/O RateHigh Performance FICON (Write) Sequential I/O Rate (Read)High Performance FICON (Total) Sequential I/O Rate (Write)Normal I/O Rate (Read) Sequential I/O Rate (Total)Normal I/O Rate (Write) Write-Cache Delay I/O Rate

Table 59. Volume cache hit metadataName NameNormal I/O Cache Hits (Read) Overall I/O Cache Hits (Total)Normal I/O Cache Hits (Write) Record Mode Read Cache Hit PercentageNormal I/O Cache Hits (Total) Sequential I/O Cache Hits (Read)Overall I/O Cache Hits (Read) Sequential I/O Cache Hits (Write)Overall I/O Cache Hits (Write) Sequential I/O Cache Hits (Total)

Table 60. Average transfer size, HPF I/O, and miscellaneous metadataName NameAverage Transfer Size (Read) HPF I/O PercentageAverage Transfer Size (Write) Sequential I/O PercentageAverage Transfer Size (Overall)

Disk metadata

Table 61. Key disk metadataName NameData Rate (Read) I/O Rate (Write)Data Rate (Write) I/O Rate (Total)Data Rate (Total) Response Time (Read)Disk Utilization Percentage Response Time (Write)I/O Rate (Read) Response Time (Overall)

Table 62. Transfer size metadataName NameAverage Transfer Size (Read) Average Transfer Size (Overall)Average Transfer Size (Write)


Port metadata

Table 63. Key port metadataName NameBandwidth (Receive) I/O Rate (Total)Bandwidth (Send) Port Utilization (Receive)Bandwidth (Overall) Port Utilization (Send)Data Rate (Receive) Port Utilization (Overall)Data Rate (Send) Response Time (Receive)Data Rate (Total) Response Time (Send)I/O Rate (Receive) Response Time (Overall)I/O Rate (Send)

Table 64. Port I/O rate metadataName NameFICON I/O Rate (Send) FCP I/O Rate (Send)FICON I/O Rate (Receive) FCP I/O Rate (Receive)FICON I/O Rate (Total) FCP I/O Rate (Total)

Table 65. Port data rates metadataName NameFICON Data Rate (Send) FCP Data Rate (Send)FICON Data Rate (Receive) FCP Data Rate (Receive)FICON Data Rate (Total) FCP Data Rate (Total)

Table 66. Port response times metadataName NameFICON Response Time (Send) FCP Response Time (Send)FICON Response Time (Receive) FCP Response Time (Receive)FICON Response Time (Overall) FCP Response Time (Overall)

Table 67. Error rate metadataName NameFrame Errors (CRC Errors) Overload Errors (I/O Busy Rate)Frame Errors (Error Frame) Overload Errors (I/O Overrun Percentage)Frame Errors (Invalid Relative Offset Rate) Overload Errors (I/O Overrun Rate)Link Errors (Invalid Link Transmission) Port Protocol Errors (Credit Recovery Link

Resets)Link Errors (Invalid Transmission Words) Port Protocol Errors (Duplicate Frames)Link Errors (Link Failures) Port Protocol Errors (Link Reset Received)Link Errors (Primitive Sequence ProtocolError Rate)

Port Protocol Errors (Link Reset Transmitted)

Link Errors (Sequence Timeouts) Port Protocol Errors (Out of Order ACK)Link Errors (Signal Loss) Port Protocol Errors (Out of Order Data)Link Errors (Sync Loss) Zero Receive Buffer Credit PercentageOverload Errors (Extreme I/O ConcurrencyPercentage)

Zero Send Buffer Credit Percentage

Overload Errors (I/O Busy Percentage)

Table 68. Remote mirror metadataName NamePPRC Data Rate (Receive) PPRC I/O Rate (Total)


Table 68. Remote mirror metadata (continued)Name NamePPRC Data Rate (Send) PPRC Response Time (Receive)PPRC Data Rate (Total)PPRC I/O Rate (Receive) PPRC Response Time (Send)PPRC I/O Rate (Send)

Table 69. Transfer size metadataName NameAverage Transfer Size (Receive) Average Transfer Size (Overall)Average Transfer Size (Send)

Performance metadata for XIV, IBM Spectrum Accelerate, IBMFlashSystem A9000, and IBM FlashSystem A9000R

View the lists of performance metadata for XIV systems, IBM Spectrum Accelerate,IBM FlashSystem A9000, and IBM FlashSystem A9000R.

Volume metadata

Table 70. Key volume performance metadataName NameData Rate (Read) Overall I/O Rate (Total)Data Rate (Write) Response Time (Read)Data Rate (Total) Response Time (Write)Overall I/O Rate (Read) Response Time (Overall)Overall I/O Rate (Write)

Table 71. Cache hit performance metadataName NameData Cache Hits (Read) Overall I/O Cache Hits (Write)Data Cache Hits (Write) Overall I/O Cache Hits (Total)Data Cache Hits (Overall) SSD Read Cache Hits (I/O)Overall I/O Cache Hits (Read) SSD Read Cache Hits (Data)

Table 72. Response time performance metadataName NameCache Hit Response Time (Read) Response Time by Transfer Size (Small)Cache Hit Response Time (Write) Response Time by Transfer Size (Medium)Cache Hit Response Time (Overall) Response Time by Transfer Size (Large)Cache Miss Response Time (Read) Response Time by Transfer Size (Very Large)Cache Miss Response Time (Write) SSD Read Cache Hit Response TimeCache Miss Response Time (Overall)

Table 73. Miscellaneous performance metadataName NameAverage Transfer Size (Read) I/O Transfer Size (Small)Average Transfer Size (Write) I/O Transfer Size (Medium)Average Transfer Size (Overall) I/O Transfer Size (Large)Data Transfer Size (Small) I/O Transfer Size (Very Large)Data Transfer Size (Medium) Pool Activity ScoreData Transfer Size (Large) Volume UtilizationData Transfer Size (Very Large)


Port performance metadata

Table 74. I/O rate performance metadataName NameI/O Rate (Send) I/O Rate (Total)I/O Rate (Receive)

Table 75. Data rate performance metadataName NameData Rate (Send) Data Rate (Total)Data Rate (Receive)

Table 76. Response time performance metadataName NameResponse Time (Send) Response Time (Overall)Response Time (Receive)

Table 77. Miscellaneous performance metadataName NameBandwidth (Send) Bandwidth (Overall)Bandwidth (Receive)

Performance metadata for IBM Spectrum ScaleView the lists of performance metadata for IBM Spectrum Scale storage systems.

Overview

The performance metadata that is collected and stored is divided into thesecategories:v “Node performance metadata”v “File system performance metadata”

Node performance metadata

You can view the following metadata for each GPFS™ cluster node:

Table 78. Metadata for nodes

Name Name

CPU Utilization (User) Memory Used (Total)CPU Utilization (System) I/O Rate (Read)CPU Utilization (Total) I/O Rate (Write)Memory Used (Cache and Buffer) I/O Rate (Total)Memory Used

File system performance metadata

You can view file system metadata for the following resources:v File systemsv IBM Spectrum Scale storage systems


Tip: For a storage system, the metadata consists of summary values for all thefile systems on the storage system.

Table 79. Metadata for file systems

Name Name

Data Rate (Read) I/O Rate (Total)Data Rate (Write) Maximum I/O Rate (Read)Data Rate (Total) Maximum I/O Rate (Write)Maximum Data Rate (Read) Maximum I/O Rate (Total)Maximum Data Rate (Write) Response Time (Read)Maximum Data Rate (Total) Response Time (Write)I/O Rate (Read) Response Time (Overall)I/O Rate (Write)

Performance metadata for EMC VMAX and VNXView the lists of performance metadata for EMC VMAX and VNX storage systems.

Lists of the performance metadata are provided in the following sections:v “VMAX storage systems”v “VNX storage systems” on page 34

Restriction: For EMC, performance metadata is available only for block storagesystems.

VMAX storage systems

The following performance metadata is available for VMAX resources:v “Volume metadata”v “Disk metadata” on page 34v “Port metadata” on page 34

Volume metadata

Volume performance metadata is divided into the following categories:v Key volume metadatav Cache hit metadatav Transfer size metadata

Table 80. Key volume metadataName NameOverall I/O Rate (Read) Response Time (Overall)Overall I/O Rate (Write) Volume UtilizationOverall I/O Rate (Total) Normal I/O Rate (Read)Data Rate (Read) Normal I/O Rate (Write)Data Rate (Write) Normal I/O Rate (Total)Data Rate (Total) Sequential I/O Rate (Read)Response Time (Read) Sequential I/O Rate (Write)Response Time (Write) Sequential I/O Rate (Total)


Table 81. Cache hit performance metadataName NameNormal I/O Cache Hits (Read) Sequential I/O Cache Hits (Total)Normal I/O Cache Hits (Write) Overall I/O Cache Hits (Read)Normal I/O Cache Hits (Total) Overall I/O Cache Hits (Write)Sequential I/O Cache Hits (Read) Overall I/O Cache Hits (Total)Sequential I/O Cache Hits (Write)

Table 82. Transfer size performance metadataName NameAverage Transfer Size (Read) Average Transfer Size (Overall)Average Transfer Size (Write)

Disk metadata

Disk performance metadata for VMAX block storage systems are divided into thefollowing categories:v Key disk metadatav Transfer size metadata

Table 83. Key disk performance metadataName NameI/O Rate (Read) Data Rate (Write)I/O Rate (Write) Data Rate (Total)I/O Rate (Total) Response Time (Overall)Data Rate (Read) Disk Utilization Percentage

Table 84. Transfer size performance metadataName NameTransfer Size (Read) Transfer Size (Overall)Transfer Size (Write)

Port metadata

Table 85. Port performance metadataName NameI/O Rate (Total) Response Time (Overall)Data Rate (Total) Transfer Size (Overall)

VNX storage systems

The following performance metadata is available for VNX resources:v Volume metadatav Disk metadatav Port metadata

Volume performance metadata

Volume performance metadata is divided into the following categories:v Key volume metadatav Transfer size metadata


Table 86. Key volume performance metadataName NameOverall I/O Rate (Read) Data Rate (Read)Overall I/O Rate (Write) Data Rate (Write)Overall I/O Rate (Total) Data Rate (Total)

Table 87. Transfer size performance metadataName NameAverage Transfer Size (Read) Average Transfer Size (Overall)Average Transfer Size (Write)

Disk metadata

Disk performance metadata for VNX storage systems is divided into the followingcategories:v Key disk metadatav Transfer size metadata

Table 88. Key disk performance metadataName NameI/O Rate (Read) Data Rate (Read)I/O Rate (Write) Data Rate (Write)I/O Rate (Total) Data Rate (Total)

Table 89. Transfer size performance metadataName NameTransfer Size (Read) Transfer Size (Overall)Transfer Size (Write)

Port performance metadata

Table 90. Port performance metadataName NameI/O Rate (Total) Transfer Size (Overall)Data Rate (Total)


Notices

This information was developed for products and services offered in the U.S.A.This material may be available from IBM in other languages. However, you may berequired to own a copy of the product or product version in that language in orderto access it.

IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not grant youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

For license inquiries regarding double-byte character set (DBCS) information,contact the IBM Intellectual Property Department in your country or sendinquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.


Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.S.A

Such information may be available, subject to appropriate terms and conditions,including in some cases, payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurements may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE: This information contains sample application programs insource language, which illustrate programming techniques on various operatingplatforms. You may copy, modify, and distribute these sample programs in anyform without payment to IBM, for the purposes of developing, using, marketing ordistributing application programs conforming to the application programming


interface for the operating platform for which the sample programs are written.These examples have not been thoroughly tested under all conditions. IBM,therefore, cannot guarantee or imply reliability, serviceability, or function of theseprograms. The sample programs are provided "AS IS", without warranty of anykind. IBM shall not be liable for any damages arising out of your use of the sampleprograms.

If you are viewing this information softcopy, the photographs and colorillustrations may not appear.

Privacy policy considerationsIBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user, or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

This Software Offering does not use cookies or other technologies to collectpersonally identifiable information.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, see IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details in thesection entitled “Cookies, Web Beacons and Other Technologies,” and the “IBMSoftware Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.

Trademarks

IBM, the IBM logo, and ibm.com® are trademarks or registered trademarks ofInternational Business Machines Corporation, registered in many jurisdictionsworldwide. Other product and service names might be trademarks of IBM or othercompanies. A current list of IBM trademarks is available on the Web at "Copyrightand trademark information" at http://www.ibm.com/legal/copytrade.shtml.

Intel, Intel logo, Intel Xeon, and Pentium are trademarks or registered trademarksof Intel Corporation or its subsidiaries in the United States and other countries.

Java™ and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Notices 39

http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

http://www.ibm.com/legal/copytrade.shtml

Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation inthe United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and othercountries.


Index

Aaccess controls 11Access, IBM Support 12aggregation of asset and capacity

metadata 9aggregation of performance metadata 9asset metadata 7authorization 11

Bbackups 13

Ccloud service infrastructure teams access

to metadata 11configuration metadata 7connection details data 7controllers metadata 24

Ddata collector 3DevOps access to metadata 11diagnostic data packages 7disks metadata 24

EECuRep 7, 12

Ffirewall 3

IIBM Spectrum Scale

file systems, view performancemetrics 32

nodes, view performance metrics 32IBM Support 12IBM Support access to metadata 11IEPD 7

Mmetadata access 11metadata access authorization 11metadata access controls 11metadata aggregation levels 9metadata backups 13metadata collected for storage

systems 15metadata collection 5metadata delivery 5

metadata encryption 5metadata for quality improvements 12metadata retention periods 9metadata storage 5metadata types 7minimum installation requirements 3

Oorganizational security 5

Pperformance metadata 7performance metrics

IBM Spectrum Scale 32personal data,

delete 13personal information,

delete 13physical protection 5PI,

delete 13

Qquality of service improvements 12

Rresolve issues 12

Ssecurity certification 3servers metadata 24service interruptions 12support tickets 7Support, access 12supported operating systems 3supported storage systems 15

Ttechnical security 5ticket data 7trademarks 39


IBM®

Product Number: 5725-U02

Printed in USA

SC27-8774-02

ibm storage insights: security guide - ibm - united states · 2018-06-12 · the data collector...

Documents