NetApp Data ONTAP ETL v4.0 for BMC Capacity Optimization · NetApp Data ONTAP ETL for BMC Capacity Optimization is a connector specifically designed to interact ... Select a NetApp

User Documentation May 2014

NetApp Data ONTAP ETL forBMC Capacity Optimization

Version 4.0

Table of Contents 2

NetApp Data ONTAP ETL for BMC Capacity Optimization

Version 4.0

Table of Contents...........................................................................................................................6Supported Platforms and Versions

...........................................................................................................................7Getting the Installation Package

...........................................................................................................................10Installing the ETL for BCO

...........................................................................................................................13Restarting the Scheduler Service

...........................................................................................................................14Configuring the ETL for BCO

...........................................................................................................................16Customizing Volumes / Shares Monitoring

...........................................................................................................................20Setting the Collect Frequency

...........................................................................................................................22Running the Extractor Service Task

...........................................................................................................................28STOCONT Dataset Performance Metrics for BCO

...........................................................................................................................29STOGLB Dataset Performance Metrics for BCO

...........................................................................................................................33STOPRM Dataset Performance Metrics for BCO

...........................................................................................................................34STOSSW Dataset Performance Metrics for BCO

...........................................................................................................................36SYSCNF Dataset Performance Metrics for BCO

...........................................................................................................................37SYSDSK Dataset Performance Metrics for BCO

...........................................................................................................................38SYSGLB Dataset Performance Metrics for BCO

Overview

4


Version 4.0

NetApp Data ONTAP ETL for BMC Capacity Optimization is a connector specifically designed for BMCCapacity Optimization and can be defined as an ETL Service, named Sentry Software Integration forBCO – NetApp Data ONTAP Extractor Service, that continuously polls and collects data from the NetAppFilers. Once an ETL Service is started, it runs continuously on BMC Capacity Optimization. Once properlyconfigured, the Sentry Software Integration for BCO – NetApp Data ONTAP Extractor Service taskcollects all the metrics required for performing critical capacity optimization tasks, such as: analysis,trending, simulation and analytic modeling.

NetApp Data ONTAP ETL for BMC Capacity Optimization A rchitecture Diagram

Getting Started

6Supported Platforms and Versions


Version 4.0

Supported Platforms and Versions

Supported NetApp Storage FilersNetApp Data ONTAP ETL for BMC Capacity Optimization supports:

In 7-mode (traditional mode): All NetApp storage filers with Data ONTAP 7.3.1 or higher.

In C-mode (cluster mode): All NetApp storage filers with Data ONTAP 8.1 or higher.

Supported Versions of BMC Capacity Optimization

NetApp Data ONTAP ETL for BMC Capacity Optimization v4.0 natively requires BMC CapacityOptimization v9.5 or higher.

7Getting the Installation Package


Version 4.0

Getting the Installation Package

The installation package for NetApp Data ONTAP ETL for BMC Capacity Optimization can be downloadedfrom the BMC Electronic Product Distribution site or directly from the Sentry Software Web site:

NetApp-Data-ONTAP-ETL-for-BCO-4.0.00.zip

The file can be saved on any server accessible via the BCO Console.

Before you can install NetApp Data ONTAP ETL for BMC Capacity Optimization you must have previouslyinstalled and configured BMC Capacity Optimization. Please refer to the documentation provided by BMCfor further information about the BMC Capacity Optimization installation and configuration procedures.

http://www.sentrysoftware.com/Products/

Integrating the ETL for BCO

9


Version 4.0

NetApp Data ONTAP ETL for BMC Capacity Optimization is a connector specifically designed to interactwith the BMC Capacity Optimization (BCO) environment. It relies on the BCO interface and features forintegrating, managing and processing the performance metrics of your NetApp systems.

Before installing, make sure that all the prerequisite operations have been properly completed (refer tothe Getting Started chapter).

10Installing NetApp Data ONTAP ETL for BMCCapacity Optimization


Version 4.0

Installing NetApp Data ONTAP ETLfor BMC Capacity OptimizationThis section provides the step-by-step procedure to upload NetApp Data ONTAP ETL for BMC CapacityOptimization into the BCO Console. The upload procedure is quick and easy, as it relies on the Uploadpatch or additional package mechanism accessible in the BCO Console under the sectionAdministration >System >Maintenance.

Uploading NetApp Data ONTAP ETL for BMC CapacityOptimization into the BCO Console

To upload NetApp Data ONTAP ETL for BMC Capacity Optimization into the BCO Console:

1. Access the BCO Console.

2. In the Administration tab, click System > Maintenance.

Verify the installation status of the already uploaded packages. If their status is "READY" or"RUNNING", wait for the installation to complete before proceeding.

At the bottom of the Maintenance page, locate the Upload patch or additional package filesection:



Version 4.0

Click Browse.

Locate and select the file NetApp-Data-ONTAP-ETL-for-BCO-4.0.00.zip designed for BMCCapacity Optimization v9.5

Click Upload.

3. Read the Overview and click Next to continue.

4. Read and accept the End User License Agreement.

5. Select the server on which the operation must be executed; that is the server on which the packagewill be saved. Click Proceed to continue.

6. A successful installation will result in a green line in the Additional Packages table.



Version 4.0

In case of unsuccessful outcome (e.g. a yellow WARNING line), click the icon to inspect the deployment log.

7. Manually restart the scheduler service to complete the installation.

13Restarting the Scheduler Service


Version 4.0

Restarting the Scheduler Service

A manual restart of the scheduler service is required to complete installation of NetApp Data ONTAP ETLfor BMC Capacity Optimization:

1. Open a shell command (SSH) on all the scheduler hosts and connect as cpit user

2. Navigate to the BCO home directory[cpit@bco ~]$ cd /opt/bmc/BCO

3. Execute the BCO script to restart the scheduler service[cpit@bco BCO]$ ./cpit restart scheduler

14Configuring the ETL for BCO


Version 4.0

Configuring the ETL for BCO

This chapter details every steps required to configure an ETL Service and add it as an ETL taskresponsible for extracting capacity and performance metrics on NetApp storage systems from theNetApp Data ONTAP API and feeding it into the BMC Capacity Optimization Data Warehouse.

To configure the ETL:

1. Access the configuration window:

In the Administration tab, click ETL & System Tasks > ETL tasks.

Press the Add button, and select Add ETL.

2. Expand the Run configuration menu:

3. From the ETL module pull-down list, select Sentry Software Integration for BCO – NetAppData ONTAP Extractor Service.

4. Click the Edit button to add all the available datasets:

In the Available datasets list, select the datasets to be added.

Click .

Click Apply.

5. Expand the Lookup sharing menu and select:

15Configuring the ETL for BCO


Version 4.0

PRIVATE if only this ETL will extract data from the specified resources.

SHARED to avoid duplicates if several ETLs extract data from the same resources. You'll thenhave to specify the ETL with which this ETL will share the information.

6. Expand the Object relationship menu to indicate the Domain tree the imported entities willpopulate:

choosing new Domain displays the domain default name: Sentry Software Integration forBCO – NetApp Data ONTAP Extractor Service. The default name is editable.

choosing existing Domain allows you to select a specific domain.

7. Expand the Connection settings menu:

Enter the hostname of the NetApp Filer in Cluster Mode or the IP address of the first controllerin 7-Mode.

Indicate the port number used by the NetApp Data ONTAP API (default: 443).

Enter the username and password to connect to the NetApp Data ONTAP API This username isset with the mandatory administrator's rights. If you wish to use a different username, make sureit has administrator's rights. For detailed information about the rights management, refer to theNetApp Data ONTAP API documentation).

Select a NetApp Data ONTAP Mode (7-Mode or Cluster-Mode).

If in 7-mode, enter the partner hostname or IP address of the second controller of yourNetApp Filer.

Select the Transport Protocol used by the NetApp Data ONTAP API (for HTTP, the default portis 80; for HTTPS the default port is 443).

8. Click Save.

16Customizing Volumes / Shares Monitoring


Version 4.0

Customizing Volumes / SharesMonitoringDiscovering volumes and/or shares and collecting their performance metrics are resource-intensiveactions that can create extra workload on the system. To reduce the system resource consumption,administrators can disable or enable the volumes and/or shares monitoring at will and fine-tune thecreation of volume and/or share entities into the BCO environment

Disabling volumes and/or shares monitoring

Disabling the monitoring of volumes and/or shares suspends the discovery of all volumes and/or sharesuntil the volumes and/or shares monitoring is re-enabled. Thus, volumes and/or shares capacity andperformance metrics are not collected. While the system resource consumption is therefore significantlyreduced, valuable metrics are no longer displayed in the console. Additionally, when data is no longercollected, the calculation of other sources metrics may be impacted (refer to the Fine-tuning entitiesmanagement section for detailed information).

To disable the monitoring of volumes and/or shares:

1. Edit the NetApp Data ONTAP ETL for BMC Capacity Optimization Run Configuration.

2. Expand the ETL additional settings menu.

Disabling Volum es and Shares Monitoring

3. From the Disable Volumes Monitoring and Disable Shares Monitoring pull-down lists, selectYes.

4. Click Save.

The table below lists the datasets and their respective metrics that are no longer collected andtherefore not displayed in the console when the volumes monitoring is disabled:



Version 4.0

Volume (NetApp LUN)

Dataset Metrics

STOGLB 7-Mode and Cluster-Mode:

ST_OVERSUBSCRIBED_CAPACITY (Storage Oversubscribed Capacity)

ST_POOL_SUBSCRIBED_CAPACITY (Pool Subscribed Capacity)

ST_POOL_SUBSCRIBED_CAPACITY_PCT (Pool Subscribed Capacity Percentage)

ST_SYSTEM_SUBSCRIBED_CAPACITY (Storage Subscribed Capacity)

The table below lists the datasets and their respective metrics that are no longer collected andtherefore not displayed in the console when the shares monitoring is disabled:

Share (NetApp Volume)

Dataset Metrics

STOGLB 7-Mode and Cluster-Mode:

ST_AVAILABLE_CAPACITY (Storage Available Capacity)

ST_AVAILABLE_IN_STORAGE_POOLS (Available Capacity in Storage Pools)

ST_CONSUMED_CAPACITY (Storage Consumed Capacity)

ST_CONSUMED_CAPACITY_PCT (Storage Consumed Capacity Percentage)

ST_OVERSUBSCRIBED_CAPACITY (Storage Oversubscribed Capacity)

ST_SYSTEM_SUBSCRIBED_CAPACITY (Storage Subscribed Capacity)

Cluster-Mode only:

ST_POOL_SUBSCRIBED_CAPACITY (Pool Subscribed Capacity)

ST_POOL_SUBSCRIBED_CAPACITY_PCT (Pool Subscribed Capacity Percentage)

Fine-tuning entities management

ETL Services manages data in two successive phases: the collect and the loading. Administrators cancombine these tasks in order to adapt the amount of data to process with the workload that theirsystem can handle. This typically depends on the database capacity and the server performance.

VolumeMonitoring

ShareMonitoring

ImportEntities

Result

No (enabled) No (enabled) Checked All volumes and/or shares are discovered and their metricsare collected and processed.

Volumes-related metrics and/or shares-related metrics aresaved in the database, processed and loaded in theconsole.

Use this configuration if your system is powerful enough tomanage all the volumes and/or shares to monitor.



Version 4.0

VolumeMonitoring

ShareMonitoring

ImportEntities

Result

No (enabled) No (enabled) Unchecked All volumes and/or shares are discovered and their metricsare collected and processed.

Volumes-related metrics and/or shares-related metrics arenot loaded in the console.

Use this configuration if you wish to collect and processvolume-related metrics and/or share-related metrics withoutloading this information in the console. The collected data willhowever be used to calculate metrics for other sources, whenrequired. This will reduce the resource consumption of yoursystem.

Yes (disabled) Yes (disabled) N/A Volumes and/or shares are not discovered.

Volumes-related metrics and/or shares-related metrics arenot loaded in the console.

Use this configuration if you want to prevent the discovery ofvolumes and/or shares and do not need to collect, save orprocess their data. Note that the calculation of metrics forother sources may be impacted (see reference guide).

Enabling volumes and/or shares monitoring

Enabling the monitoring of volumes and/or shares resumes the discovery of all volumes and/or shares.Thus, volumes and/or shares capacity and performance metrics are properly collected. According to thenumber of volumes and/or shares to monitor, the system resource consumption may be significantlyimpacted.

To enable the monitoring of volumes and/or shares:

1. Edit the NetApp Data ONTAP ETL for BMC Capacity Optimization Run Configuration.

2. Expand the Run Configuration menu to verify that the STOGLB, OBJREL and STOPRM (for sharesonly) datasets are selected.

3. Expand the ETL additional settings menu.

Enabling Volum es and Shares Monitoring



Version 4.0

4. From the Disable Volumes Monitoring and Disable Shares Monitoring pull-down list, selectNo.

5. Check the Volume and Share boxes to make the volume and share entities appear in the Domaintree.

Please note that creating entities for additional object classes may have a deep impact on theperformance of the application.

6. Click Save.

20Setting the Collect Frequency


Version 4.0

Setting the Collect Frequency

The collect frequency is the rate at which data is collected. The collect frequency is set to 15 minutes bydefault but can be modified to better suit your needs.

To set the collect frequency:

1. Edit the NetApp Data ONTAP ETL for BMC Capacity Optimization Run Configuration:

In the Administration tab, click ETL & System Tasks > ETL tasks.

Click the link Sentry Software Integration for BCO – NetApp Data ONTAP ExtractorService.

Click the Stop button to stop the service execution; then click the Edit button available in theRun configurations section.

21Setting the Collect Frequency


Version 4.0

2. Click the link provided at the bottom of the page You can manually edit ETL properties fromthis page to display a list of editable options.

3. Locate the service.period option, and enter the number of milliseconds corresponding to thefrequency at which data will be collected.

22Running Sentry Software Integration for BCO – NetApp Data ONTAP Extractor Service Task


Version 4.0

Running Sentry SoftwareIntegration for BCO – NetApp DataONTAP Extractor Service TaskThe Sentry Software Integration for BCO – NetApp Data ONTAP Extractor Service task canbe run manually to retrieve performance metrics.

The steps listed in this section are not mandatory and are required only if the ETLs are not already scheduled forexecution.

To run the Sentry Software Integration for BCO – NetApp Data ONTAP Extractor Servicetask:

1. Access the BCO Console

2. In the Administration tab, select ETL & System Tasks > ETL Tasks.

3. Click to execute the Sentry Software Integration for BCO – NetApp Data ONTAPExtractor Service ETL task.

When the execution is complete, the value of the Status column in the ETL tasks table changes fromWaiting to Ended.

Generating Log Files

24


Version 4.0

The Sentry Software support team may ask you to provide log files to better diagnose the nature of aproblem when you need help on a specific matter. These log files can be obtained by executing the LogGrabber from the BCO console:

1. Access the BCO Console.

2. In the Administration tab, click System > Maintenance.

3. Open the Maintenance Activities tab.

4. Click to execute the Log Grabber.

5. Click Next.

25


Version 4.0

6. Select the host for which you wish to obtain logs and click Proceed to execute the Log Grabber.

7. Refresh the Maintenance Activities page to check the request status.

8. When the request status is "ENDED", click to view the deployment log.

9. Click to download the deployment log.

Reference Guide

27


Version 4.0

This section provides detailed information on the performance metrics collected by the SentrySoftware Integration for BCO – NetApp Data ONTAP Extractor Service from the NetApp Filersand made available in the BCO Console.

The performance metrics are available in the following datasets:

STOCONT Dataset Performance Metrics

STOGLB Dataset Performance Metrics

STOPRM Dataset Performance Metrics

STOSSW Dataset Performance Metrics

SYSCNF Dataset Performance Metrics

SYSDSK Dataset Performance Metrics

SYSGLB Dataset Performance Metrics

For additional information about datasets management, refer to BMC Capacity Optimization documentation.

28[108] STOCONT Dataset Performance Metricsfor BCO


Version 4.0

[108] STOCONT DatasetPerformance Metrics for BCOMetrics are presented in table, where each column represents a particular variable, and each rowcorresponds to a given member of the STOCONT dataset.

Metric Unit Name Description Value Type

BYCONT_PORT_NUM N/A Number ofavailableports bycontroller

Number of available ports by controller. Thesubobject specifies the controller name.

Configurationdata (string)

BYCONT_PROCESSOR_UTIL PCT Processorutilization bycontroller

Processor utilization by controller. Thesubobject specifies the controller name.

Percentagecounter

BYCONT_RESPONSE_TIME MILLIS Responsetime bycontroller

Response time by controller. The subobjectspecifies the controller name.

Elapsed time

BYCONT_TRANSFER_RATE BYTE/S Transferrate bycontroller

Transfer rate by controller. The subobjectspecifies the controller name.

A frequency, inevents/sec

Additional Columns

Column Name Unit Name Description

CONTNM N/A

Storagecontrollername Storage controller name.

DS_SYSNM N/A

System namein theDatasource The name of the system as in the Datasource (for lookup).

DURATION S Duration Duration of the sample.

SYSNM N/A System nameThe name of the system proposed for identification in BMC CapacityOptimization; if absent, the DS_SYSNM is used.

SYSTYPENM N/A Object type Object type name.

TS N/A Timestamp Start timestamp of the sample [YYYY-MM-DD HH:MI:SS].

For detailed information about datasets, refer to the BMC Capacity Optimization documentation.

https://docs.bmc.com/docs/display/public/bcmco90/Home

29[30] STOGLB Dataset Performance Metrics forBCO


Version 4.0

[30] STOGLB Dataset PerformanceMetrics for BCOMetrics are presented in a table, where each column represents a particular variable, and each rowcorresponds to a given member of the STOGLB dataset.

Metric Entity Unit Name Description Value Type

ST_AGGREGATE_AVAILABLE StorageAggregate

N/A StorageAggregateAvailable

Storage Aggregate Available Configurationdata (string)

ST_AGGREGATE_SIZE StorageAggregate

BYTES StorageAggregateSize

Storage Aggregate Size Configurationdata (string)

ST_AGGREGATE_TYPE StorageAggregate

N/A StorageAggregateType

Storage Aggregate Type Configurationdata (string)

ST_AGGREGATE_USED StorageAggregate

BYTES StorageAggregateUsed Size

Storage Aggregate Used Size Positiveaccumulationcounter

ST_AVAILABLE_CAPACITY² Storage AreaNetworkStorage -AggregateStorage -Share

BYTES AvailableCapacity

Capacity not consumed (forstorage systems: unused rawspace plus available capacity instorage pools)

Negativeaccumulationcounter

ST_AVAILABLE_CAPACITY_PCT

Storage -AggregateStorage -Share

PCT AvailableCapacityPercentage

Percentage of the storagecapacity that is not consumed

Percentagecounter

ST_AVAILABLE_FOR_STORAGE_POOLS

Storage AreaNetwork

BYTES AvailableCapacity forStoragePools

Raw space available forstorage pool creation


ST_AVAILABLE_IN_STORAGE_POOLS²

Storage AreaNetwork

BYTES AvailableCapacity inStoragePools

Sum of space not consumed inall storage pools


ST_CAPACITY Storage AreaNetworkStorage -AggregateStorage -Share

BYTES StorageCapacity

Total capacity (for storagesystems: unused raw spaceplus sum of the capacity for allstorage pools)

Genericcounter,absolute value

ST_CONFIG_SIZE Storage -AggregateStorage -Share

BYTES StorageConfiguredSpace

Overall size of the component(for a storage system, thisvalue is the sum of the raw sizeof all disks; for a storage poolthis value is the external size)




Version 4.0


ST_CONSUMED_CAPACITY² Storage AreaNetworkStorage -AggregateStorage -Share

BYTES StorageConsumedCapacity

Actually consumed capacity Genericcounter,absolute value

ST_CONSUMED_CAPACITY_PCT²

Storage AreaNetworkStorage -AggregateStorage -Share

PCT StorageConsumedCapacityPercentage

Percentage of capacity actuallyconsumed

Percentagecounter

ST_DEVICECOUNT Storage AreaNetwork

QTY StorageDevicesNumber

Number of storage devices Configurationdata (string)

ST_FILER StorageAggregate,Storage Filer

N/A StorageFiler

Storage Filer Configurationdata (string)

ST_LUN_SIZE Storage -Volume

BYTES Storage LUNSize

Storage LUN Size Configurationdata (string)

ST_MICROCODE Storage AreaNetwork

N/A Microcodeversion

Software microcode version Configurationdata (string)

ST_OVERSUBSCRIBED_CAPACITY¹ ²

Storage AreaNetworkStorage -Aggregate

BYTES StorageOversubscribedCapacity

Storage subscribed capacityexceeding the actual capacityof the component


ST_POOL_DEV_COUNT Storage -Aggregate

N/A Pool devicescount

Pool devices count Configurationdata (string)

ST_POOL_RAID_LEVEL StorageAggregate

N/A Pool RAIDLevel

RAID level of the storage pool Configurationdata (string)

ST_POOL_SUBSCRIBED_CAPACITY¹ ²

Storage -Aggregate

BYTES PoolSubscribedCapacity

Sum of the host visible capacityfor all volumes in the storagepool. Can be greater than theactual capacity of the storagepool for over-subscribed thinpools.


ST_POOL_SUBSCRIBED_CAPACITY_PCT¹ ²

Storage -Aggregate

PCT PoolSubscribedCapacityPercentage

Subscribed capacity, inpercentage of the capacity ofthe storage pool. Can exceed100% for thin pools, thereforecalled oversubscribed

Percentagecounter

ST_POOL_TYPE Storage -Aggregate

N/A Array PoolType

Type of the pool Configurationdata (string)

ST_SID Storage AreaNetwork

N/A StorageDeviceUniqueIdentifier

Unique identifier of the storagedevice




Version 4.0


ST_SIZE Storage AreaNetwork

BYTES Storage Size Sum of the host visible capacityfor all volumes in the storagepool. Can be greater than theactual capacity of the storagepool for over-subscribed thinpools


ST_STATUS StorageAggregate

N/A StorageStatusInformation

Storage Status Information Configurationdata (string)

ST_SYSTEM_BANDWIDTH Storage AreaNetwork

BYTE/S SystemBandwidth

Bandwidth available in storagesystem


ST_SYSTEM_BANDWIDTH_UTIL

Storage AreaNetwork

PCT SystemBandwidthUtilization

Bandwidth consumed instorage system

Percentagecounter

ST_SYSTEM_MODEL Storage AreaNetwork

N/A StorageArray Model

Model of the system Configurationdata (string)

ST_SYSTEM_PORT_NUM Storage AreaNetwork

N/A StorageArray PortNumber

Total number of ports Configurationdata (string)

ST_SYSTEM_SUBSCRIBED_CAPACITY¹ ²

Storage AreaNetwork

BYTES StorageSubscribedCapacity

Sum of the host visible capacityfor all volumes. Can be greaterthan the actual capacity of thestorage system with over-subscribed thin pools


ST_SYSTEM_TRANSFER_BYTE_RATE

Storage AreaNetwork

BYTE/S SystemTransferByte Rate

Total data traffic (in and out,read and write)


ST_SYSTEM_VENDOR Storage AreaNetwork

N/A Vendor Vendor Configurationdata (string)

ST_TYPE Storage -Filer

N/A Box Type Box Type Configurationdata (string)

ST_VOLUME Storage -Volume

N/A StorageVolume

Storage Volume Configurationdata (string)

ST_VOLUME_CONSUMED_CAPACITY

Storage -Volume

BYTES VolumeConsumedCapacity

Amount of capacity that hasbeen actually consumed by thehost (for thin volumes, thisvalue will typically be less thanthe host visible capacity; fortraditional volumes this valuealways equals the host visiblecapacity)

Positiveaccumulationcounter

ST_VOLUME_CONSUMED_CAPACITY_PCT

Storage -Volume

PCT VolumeConsumedCapacityPercentage

Percentage of the volumesubscribed capacity that hasbeen actually consumed by thehost. Will be typically less than100% for thin volumes. Will beexactly 100% for all traditionalvolumes

Percentagecounter

ST_VOLUME_HOST_VISIBLE_CAPACITY

Storage -Volume

BYTES Host VolumeVisibleCapacity

Amount of capacity that hasbeen subscribed and can be"seen" by the host




Version 4.0


ST_VOLUME_MAPPED Storage -Volume

N/A VolumeMapped

Whether the LUN is mapped toat least one host


ST_VOLUME_SNAPSHOT_RESERVE_SIZE

Storage -Share

BYTES StorageVolumeSnapshotReserveSize

Storage Volume SnapshotReserve Size


ST_VOLUME_SNAPSHOT_RESERVE_USED

Storage -Share

BYTES StorageVolumeSnapshotReserveUsed

Storage Volume SnapshotReserve Used


ST_VOLUME_SPACE_GUARANTEE

Storage -Share

N/A StorageVolumeSpaceGuarantee

Storage Volume SpaceGuarantee


ST_VOLUME_STATE Storage -Share

N/A StorageVolumeState

Storage Volume State Configurationdata (string)

ST_VOLUME_TRANSFER_BYTE_RATE

Storage -Volume

BYTE/S VolumeTransferByte Rate

Data traffic (read and write) onthe volume


ST_VOLUME_TYPE Storage -Share

N/A StorageVolumeType

Storage Volume Type Configurationdata (string)

¹These metrics will be missing if volumes monitoring is disabled. ²These metrics will be missing if shares monitoring is disabled.

Additional Columns

ColumnName

Unit Name Description

DS_SYSNM N/A System name inthe datasource

The name of the system as in the Datasource (for lookup).

DURATION S Duration Duration of the sample (in seconds).

SYSNM N/A Storage name The name of the storage system.





33[47] STOPRM Dataset Performance Metrics forBCO


Version 4.0

[47] STOPRM Dataset PerformanceMetrics for BCOMetrics are presented in table, where each column represents a particular variable, and each rowcorresponds to a given member of the STOPRM dataset.


ST_NFS_RATE OP/S Storage NFS Rate Storage Array NFS operations/sec A frequency, inevents/sec

ST_ISCSI_RATE OP/S Storage iSCSI Rate Storage Array iSCSI operations/sec A frequency, inevents/sec

ST_HTTP_RATE OP/S Storage HTTP Rate Storage Array HTTP operations/sec A frequency, inevents/sec

ST_CIFS_RATE OP/S Storage CIFS Rate Storage Array CIFS operations/sec A frequency, inevents/sec

ST_FC_RATE OP/S Storage FCP Rate Total number of FCP operations/secperformed


ST_SAN_RATE OP/S Storage SAN Rate Total number of SAN operations/secperformed


Additional Columns

ColumnName





GOLEVELS N/A Grouping objectlevels

Levels for populating a grouping object, colon separated.

SYSNM N/A Storage name The name of the storage system.





34[55] STOSSW Dataset Performance Metrics forBCO


Version 4.0

[55] STOSSW Dataset PerformanceMetrics for BCOMetrics are presented in a table, where each column represents a particular variable, and each rowcorresponds to a given member of the STOSSW dataset.

Metrics Unit Name Description Val Type

BYPORT_ADDRESS N/A Storage switch portaddress

Storage switch port address. Configurationdata (string)

BYPORT_BANDWIDTH

BIT/S Bandwidth of thestorage switch port

Bandwidth of the storage switch port. Configurationdata (string)

BYPORT_BANDWIDTH_UTIL

BIT/S Bandwidth utilizationof the storage switchport

Bandwidth utilization of the storage switchport.

Percentagecounter

BYPORT_BYTE_RATE

BYTE/S Input/output trafficrate for the port

Input/output traffic rate for the port. A frequency, inevents/sec

BYPORT_CONTROLLER_NAME

N/A Storage switch portcontroller name

Storage switch port controller name. Configurationdata (string)

BYPORT_IN_BYTE_RATE

BYTE/S Incoming traffic ratefor the port

Incoming traffic rate for the port. A frequency, inevents/sec

BYPORT_IN_UTIL PCT Inbound Utilizationpercentage by port

Percentage of inbound utilization of the port. Percentagecounter

BYPORT_OUT_BYTE_RATE

BYTE/S Outcoming traffic ratefor the port

Outcoming traffic rate for the port Percentagecounter

BYPORT_OUT_UTIL

PCT Outbound Utilizationpercentage by port

Percentage of outbound utilization of the port. Percentagecounter

BYPORT_TYPE N/A Storage switch porttype

Storage switch port type. Configurationdata (string)

Additional Columns

ColumnName







LOCATIONNM

N/A Location name Physical location of the measured object; if absent, assumedUNKNOWN.

PORTNM N/A Storage switchport name

Storage switch port name.

35[55] STOSSW Dataset Performance Metrics forBCO


Version 4.0

ColumnName


SYSNM N/A System name The name of the system proposed for identification in BMC CapacityOptimization; if absent, the DS_SYSNM is used.





36[1] SYSCNF Dataset Performance Metrics forBCO


Version 4.0

[1] SYSCNF Dataset PerformanceMetrics for BCOMetrics are presented in table, where each column represents a particular variable, and each rowcorresponds to a given member of the SYSCNF dataset.


NET_IP_ADDRESSES

N/A System IP addresses The IP addresses of the system, separated bya ";".


Additional Columns

ColumnName Unit Name Description

DS_SYSNM N/ASystem name inthe datasource The name of the system as in the Datasource (for lookup).


LOCATIONNM N/A Location name

Physical location of the measured object; if absent, assumedUNKNOWN.

SYSNM N/A System nameThe name of the system proposed for identification in BMC CapacityOptimization; if absent, the DS_SYSNM is used.





37[4] SYSDSK Dataset Performance Metrics forBCO


Version 4.0

[4] SYSDSK Dataset PerformanceMetrics for BCOMetrics are presented in a table, where each column represents a particular variable, and each rowcorresponds to a given member of the SYSDSK dataset.

Metrics

Metrics Unit Name Description Val Type

BYDISK_MODEL N/A Model by Disk Model of the Disk. Configurationdata (string)

BYDISK_RESPONSE_TIME

S Disk Response Time The average time for I/O requests issued tothe device to be served. This includes the timespent by the requests in queue and the timespent servicing them.

Genericcounter,absolute value,weighted

BYDISK_RPM RPM Disk revolutions perminute

Disk revolutions per minute. Configurationdata (string)

BYDISK_SIZE BYTES Size by Disk Disk size (bytes). Configurationdata (string)

Additional Columns

ColumnName




DSKNM N/A Disk Name The name of the disk.




SYSNM N/A System name The name of the system proposed for identification in BMC CapacityOptimization; if absent, the DS_SYSNM is used.



WEIGHT N/A Weight The weight of the sample.



38[2] SYSGLB Dataset Performance Metrics forBCO


Version 4.0

[2] SYSGLB Dataset PerformanceMetrics for BCOMetrics are presented in table, where each column represents a particular variable, and each rowcorresponds to a given member of the SYSGLB dataset.


CPU_UTIL PCT CPU Utilizationpercentage

Percentage of time the CPU was not idleduring the interval.

Percentagecounter

Additional Columns

ColumnName Unit Name Description

DS_SYSNM N/ASystem name inthe datasource The name of the system as in the Datasource (for lookup).


GOLEVELS N/AGrouping objectlevels Levels for populating a grouping object, colon separated.

LOCATIONNM N/A Location Name

Physical location of the measured object; if absent, assumedUNKNOWN.

SYSNM N/A System nameThe name of the system proposed for identification in BMC CapacityOptimization; if absent, the DS_SYSGLB is used.





Index 39


Version 4.0

Index

- A -Add ETL 14

Additional components 10

Architecture 4

- B -BCO Console 10

- C -Columns

CONTNM 28, 36

Disk Name 37

DS_SYSNM 28, 29, 33, 34, 36, 37, 38

DSKNM 37

Duration 28, 29, 33, 34, 36, 37, 38

GOLEVELS 33, 34, 37, 38

Grouping object levels 33, 34, 37, 38

Host name 33

Location Name 34, 38

LOCATIONNM 34, 38

Object type 28, 29, 33, 34, 36, 37, 38

PORTNM 34

Storage controller name 28, 36

Storage name 29, 33

Storage switch port name 34

SYSNM 28, 29, 33, 34, 36, 37, 38

System name 28, 34, 36, 37, 38

System name in the datasource 28, 29, 33,34, 36, 37, 38

SYSTYPENM 28, 29, 33, 34, 36, 37, 38

Timestamp 28, 29, 33, 34, 36, 37, 38

TS 28, 29, 33, 34, 36, 37, 38

WEIGHT 37Configuration 14

Connection settings 14

Customizing

Shares 16

Volumes 16

- D -Dataset

STOCONT 28

STOGLB 29

STOPRM 33

STOSSW 34

SYSCNF 36

SYSDSK 37

SYSGLB 38Disabling

Shares Monitoring 16

Volumes Monitoring 16

- E -Enabling

Shares Monitoring 16

Volumes Monitoring 16ETL tasks 14

Execute 22

- I -Installation 10

- L -License Agreement 10

Lookup sharing 14

- O -Object relationships 14

Overview 4

- P -Performance Metrics

Array Cache 29

Array Pool Type 29

Attached Hosts Number 29

Available Capacity 29

Available Capacity for Storage Pools 29

Available Capacity in Storage Pools 29

Index 40


Version 4.0

Performance Metrics

Available Capacity Percentage 29

Bandwidth of the storage switch port 34

Bandwidth utilization of the storage switchport 34

Box Type 29

BYCONT_PORT_NUM 28

BYCONT_PROCESSOR_UTIL 28

BYCONT_RESPONSE_TIME 28

BYCONT_TRANSFER_RATE 28

BYDISK_MODEL 37

BYDISK_RESPONSE_TIME 37

BYDISK_RPM 37

BYDISK_SIZE 37

BYPORT_ADDRESS 34

BYPORT_BANDWIDTH 34

BYPORT_BANDWIDTH_UTIL 34

BYPORT_BYTE_RATE 34

BYPORT_CONTROLLER_NAME 34

BYPORT_IN_BYTE_RATE 34

BYPORT_IN_UTIL 34

BYPORT_OUT_BYTE_RATE 34

BYPORT_OUT_UTIL 34

BYPORT_TYPE 34

CPU_UTIL 38

Device Space 29

Inbound Utilization percentage by port 34

Incoming traffic rate for the port 34

Input/output traffic rate for the port 34

Microcode version 29

NET_IP_ADDRESSES 36

Number of available ports by controller 28

Outbound Utilization percentage by port 34

Outcoming traffic rate for the port 34

Pool devices count 29

Pool Oversubscription Situation 29

Pool RAID Level 29

Pool Subscribed Capacity 29

Pool Subscribed Capacity Percentage 29

Primary Allocated Usable Space 29

Processor utilization by controller 28

Response time by controller 28

ST_AVAILABLE_CAPACITY 29

ST_AVAILABLE_CAPACITY_PCT 29

ST_AVAILABLE_FOR_STORAGE_POOLS 29

ST_AVAILABLE_IN_STORAGE_POOLS 29

ST_CACHE 29

ST_CAPACITY 29

ST_CIFS_RATE 33

ST_CONFIG_SIZE 29

ST_CONSUMED_CAPACITY 29

ST_CONSUMED_CAPACITY_PCT 29

ST_DEVICE_TOTAL 29

ST_DEVICECOUNT 29

ST_FC_RATE 33

ST_HOSTCNT 29

ST_HTTP_RATE 33

ST_ISCSI_RATE 33

ST_MICROCODE 29

ST_NFS_RATE 33

ST_OVERSUBSCRIBED_CAPACITY 29

ST_POOL_DEV_COUNT 29

ST_POOL_OVERSUBSCRIPTION_SITUATION 29

ST_POOL_RAID_LEVEL 29

ST_POOL_SUBSCRIBED_CAPACITY 29

ST_POOL_SUBSCRIBED_CAPACITY_PCT 29

ST_POOL_TYPE 29

ST_PRIMARY_ALLOCATED 29

ST_SAN_RATE 33

ST_SID 29

ST_SIZE 29

ST_SYSTEM_BANDWIDTH 29

ST_SYSTEM_BANDWIDTH_UTIL 29

ST_SYSTEM_MODEL 29

ST_SYSTEM_PORT_NUM 29

ST_SYSTEM_SUBSCRIBED_CAPACITY 29

ST_SYSTEM_TRANSFER_BYTE_RATE 29

ST_SYSTEM_VENDOR 29

ST_THINDEV_COUNT 29

ST_THINPOOL_CONFIG_TOTAL 29

ST_THINPOOL_COUNT 29

ST_THINPOOL_FREE 29

ST_THINPOOL_USED 29

ST_TYPE 29

ST_VOLUME_CONSUMED_CAPACITY 29

ST_VOLUME_CONSUMED_CAPACITY_PCT 29

ST_VOLUME_HOST_VISIBLE_CAPACITY 29

ST_VOLUME_MAPPED 29

ST_VOLUME_RAID_LEVEL 29

ST_VOLUME_RESPONSE_TIME 29

ST_VOLUME_TIME_SINCE_LAST_ACTIVITY 29

ST_VOLUME_TRANSFER_BYTE_RATE 29

Storage Array Model 29

Storage Array Port Number 29

Storage Capacity 29

Index 41


Version 4.0

Performance Metrics

Storage CIFS Rate 33

Storage Configured Space 29

Storage Consumed Capacity 29

Storage Consumed Capacity Percentage 29

Storage Device Unique Identifier 29

Storage Devices Number 29

Storage FCP Rate 33

Storage HTTP Rate 33

Storage iSCSI Rate 33

Storage NFS Rate 33

Storage Oversubscribed Capacity 29

Storage SAN Rate 33

Storage Size 29

Storage Subscribed Capacity 29

Storage switch port address 34

Storage switch port controller name 34

Storage switch port type 34

System Bandwidth 29

System Bandwidth Utilization 29

System IP addresses 36

System Transfer Byte Rate 29

Thin devices count 29

Thin pool free space 29

Thin Pool Total capacity 29

Thin pool used space 29

Thin pools count 29

Transfer rate by controller 28

Vendor 29

Volume Consumed Capacity 29

VOLUME_EXTERNAL_ID 29Platforms

7-mode 6

cluster mode 6

c-mode 6

traditional mode 6

- R -Run configuration 14

- S -Shares

Customizing 16

Disabling 16

Enabling 16

Monitoring 16

STOCONT Dataset 28

STOGLB Dataset 29

STOPRM Dataset 33

STOSSW Dataset 34

Supported

Platforms 6

Versions 6SYSCNF Dataset 36

SYSDSK Dataset 37

SYSGLB Dataset 38

- T -Task properties 14

- U -Upload 10

- V -Versions

BMC Capacity Optimization 6Volumes

Customizing 16

Disabling 16

Enabling 16

Monitoring 16

About BMC® SoftwareBMC Software helps leading companies around the world put technology at theforefront of business transformation, improving the delivery and consumption ofdigital services. From mainframe to cloud to mobile, BMC delivers innovative ITmanagement solutions that have enabled more than 20,000 customers toleverage complex technology into extraordinary business performance—increasing their agility and exceeding anything they previously thought possible.

For more information about BMC Software, visit www.bmc.com.

About Sentry Software™Sentry Software, a strategic Technology Alliance Partner of BMC Software,provides comprehensive multi-platform monitoring solutions that enablemanagement of the hardware and software aspects of all servers and SANs andcovering up to 100 % of custom applications within the BMC ProactiveNetPerformance Management environment. Sentry Software also develops adaptersfor BMC Atrium Orchestrator that enables IT administrators to automate theexecution of common requests and tasks that occur in the daily course of IToperations. Combined with BMC’s servers and network automation tools, theadapters allow IT administrators to implement provisioning anddecommissioning workflows that cover all layers of their IT infrastructure. Finally,Sentry Software designs connectors that bring storage capacity metrics into BMCCapacity Optimization to ensure IT administrators that their storageinfrastructure is properly sized for their current and future needs.The combination of its monitoring, automation, and capacity optimizationcapabilities for IT infrastructures, makes Sentry Software a key-partner in thestorage management marketplace. For more information about Sentry Software,please visit www.sentrysoftware.com.

452596

http://www.sentrysoftware.com

Documents

NetApp Data ONTAP ETL v4.0 for BMC Capacity Optimization · NetApp Data ONTAP ETL for BMC Capacity Optimization is a connector specifically designed to interact ... Select a NetApp