New Articles and Resources articles in Virtualization

SAN Info PowerShell Script

mcgue — Sat, 14 Nov 2020 00:11:51 GMT

Purpose

Performs a variety of checks against an ONTAP SAN based system and returns the results in an Excel spreadsheet. Following are the checks involved.

Compare the initiators defined in each igroup against the actual logged in initiators on each node.
Show total number of initiators per LIF.
Gather FCP adapter details that might have a best practice impact.
Compare selective LUN mapping reporting-nodes against the hosting HA pair, other nodes in the cluster, and nodes no longer in the cluster.

Requirements

NetApp PowerShell Toolki - https://mysupport.netapp.com/site/tools/tool-eula/powershell-toolkit
ImportExcel Module - https://github.com/dfinke/ImportExcel
ONTAP 9.x cluster

Script Information

Save script as SANInfo.ps1
Learn more about the script with the following:
get-help .\SANInfo.ps1 -Detailed
The script only performs read operations against the cluster to collect data.

How to force vCenter to reload VSC/VASA GUI flash data for vSphere Web Client

RajeshPanda — Sun, 14 Apr 2019 17:24:20 GMT

When Virtual Storage Console (VSC) and VASA Provider are registered to vCenter, UI (user interface) extensions are pulled to vSphere. These UI extensions represent the framework that VSC and VASA Provider use to display data.

When new versions of VSC or VASA Provider are released they may be bundled with new UI extensions. During the upgrade process, VSC does not have the ability to delete the old UI extensions off of the vCenter server. These files must be removed manually. If old UI extensions are not removed then a conflict may arise which can cause display issues with the plugin.

During a upgrade of VSC or VASA Provider, it is highly recommended that the old UI extensions be removed.

RBAC User Creator tool for VSC, VASA Provider and Storage Replication Adapter 7.0 for VMware vSphere

ashruthi — Thu, 03 Aug 2017 13:43:17 GMT

Introduction

The RBAC User Creator for ONTAP® tool is a C# application that enables you to create RBAC users within ONTAP.
The list of privileges created are stored in an XML (ontapPrivs.xml) file. The XML file enables you to gather the following information:

1. You can verify the privileges of the new user created by RBAC User Creator tool.
2. You can add privileges or products later without the need to recompile the application.

The RBAC User Creator tool is a framework where all the products and the privileges for those products are listed in the XML file. You can easily add support for another product or product version by updating the information in the XML file.

RBAC User Creator tool for Virtual Storage Console, VASA Provider, and Storage Replication Adapter 7.0

This article describes how to use the RBAC User Creator tool for Virtual Storage Console, VASA Provider, and Storage Replication Adapter 7.0 for VMware vSphere. You can use the tool to create users for the below functionalities:

1. Virtual Storage Console
2. Virtual Storage Console and VASA Provider
3. Virtual Storage Console and Storage Replication Adapter
4. Virtual Storage Console, VASA Provider and Storage Replication Adapter

Please note that VSC, VASA Provider, and SRA 7.0 supports ONTAP versions 9.0 onwards only.

Once you have downloaded and installed the RBAC User Creator tool from the ToolChest, you will need to perform the below steps to provide support for VSC, VASA Provider and SRA 7.0.

Step 1: Replace XML for VSC, VASA Provider and SRA 7.0 support

To enable support for VSC, VASA Provider and SRA 7.0, please perform the following:

1. Download and keep a copy of the ontapPrivs.xml file (attached below).
2. Access the install directory of the RBAC User Creator tool.
This information is provided during installation. For example:- The default path would be: C:\Program Files (x86)\NetApp\RBAC User Creator
3. Replace the existing ontapPrivs.xml file with the downloaded .xml file.
4. Restart the RBAC User Creator tool.

You can start using the RBAC User Creator tool to create new roles and users.

Step 2: Setting up user names and privileges

You can create ONTAP user names with the privileges required for VSC, VASA Provider and SRA.

1. Enter the name of the admin user and IP of the storage system for which you want to create the user.
2. Click LOGIN .
The tool determines the controller type.
3. As the storage system is running ONTAP, the list of SVMs are displayed.
RBAC User Creator supports creating users on the Cluster-Admin SVM as well as on Data SVMs. Select the appropriate SVM from the drop-down list.
4. Select the product and product version depending on your requirements.
• For 7.0, you must select product as “VSC, VASA Provider and SRA”.
• If you wish to use only VSC, you must select product version as “VSC 7.0”.
• If you wish to use VASA Provider along with VSC, then you must select the product version as “VSC and VASA Provider 7.0”.
• If you wish to use SRA along with VSC, then you must select the product version as “VSC and SRA 7.0”.
• If you wish to use all three, VSC, VASA Provider and SRA, then you must select the product version as “VSC, VASA Provider and SRA 7.0”.
5. Select all the ONTAP privilege roles that apply.
RBAC User Creator tool merges all the privileges from the selected roles and combines them in a sorted list.
6. Enter a name for the role, user, and password, and then click Submit.
NOTE: RBAC User Creator requires admin storage credentials for creating new user names.

Step 3: Adding storage systems

1. Log in into your VSC, VASA Provider and SRA plugin from the vCenter.
2. Add the storage system using the new username and password.

Known issues

While providing a role name, do not provide any names that begin with “vsadmin”. This will prevent creating any new roles or users.

Downloading and using RBAC User Creator

Refer to the following link for details regarding download and usage of RBAC User Creator tool:
How to use the RBAC User Creator for ONTAP

Resources

Download RBAC User Creator for ONTAP

How to Use RBAC User Creator tool for Storage Replication Adapter 4.0

ashruthi — Tue, 31 Jan 2017 15:55:27 GMT

Introduction

The RBAC User Creator for ONTAP® tool is a C# application that enables you to create RBAC usernames within ONTAP. You can use the RBAC User Creator tool to create users in both 7-mode and ONTAP environments.

The list of privileges created are stored in an XML (ontapPrivs.xml) file. The XML file enables you to gather the following information:

1. You can verify the privileges of the new user created by RBAC User Creator tool.
2. You can add privileges or products later without the need to recompile the application.

RBAC User Creator tool for Storage Replication Adapter 4.0

The RBAC User Creator tool is enhanced to allow creating new roles and users required for Storage Replication Adapter (SRA) 4.0 by adding additional information in the XML file.

Please note that Storage Replication Adapter (SRA) 4.0 supports ONTAP versions 8.3.2 onwards only.

Once you have downloaded and installed the RBAC User Creator tool from the ToolChest, you will need to perform the below steps to provide support for SRA 4.0.

Step 1: Replace XML for SRA 4.0 support

To enable support for SRA 4.0, please perform the following:

You can start using the RBAC User Creator tool to create new roles and users.

Step 2: Setting up user names and privileges

You can create ONTAP user names with all the privileges required for SRA.

1. Enter the name of the root or admin user and IP of the storage system for which you want to create the user.
2. Click LOGIN .
The tool determines the controller type.
3. As the storage system is running ONTAP, the list of SVMs are displayed.
RBAC User Creator supports creating users on the Cluster-Admin SVM as well as on Data SVMs. Select the appropriate SVM from the drop-down list.
4. Select the product and product version.
For SRA 4.0, you must select product as “SRA for VMware SRM” and product version as “SRA 4.0 for VMware SRM”.
5. Select the ONTAP privilege role as “NAS/SAN Role”.
RBAC User Creator tool merges all the privileges from the selected roles and combines them in a sorted list.
6. Enter a name for the role , user, and password, and then click Submit.
NOTE: RBAC User Creator requires root or admin storage credentials for creating new user names.

Step 3: Adding storage systems

1. Log in into your SRA 4.0 system.
2. Add the storage system using the new username and password.

Known issues

While providing a role name, do not provide any names that begin with “vsadmin”. This will prevent creating any new roles or users.

Downloading and using RBAC User Creator

Refer to the following link for details regarding download and usage of RBAC User Creator tool:

How to use the RBAC User Creator for ONTAP

Resources

Download RBAC User Creator for ONTAP

How to Check Data ONTAP 8.3.2 Upgrade Requirements Using a PowerShell Script

mcgue — Tue, 25 Apr 2017 15:08:23 GMT

Introduction:

This script checks a specified cluster for the items in the "Steps for preparing for a major upgrade" section. The items that are covered are the ones that can be addressed prior to the actual software image update. These are outlined roughly on pages 31-54 in the guide. Based upon the output of the script you can make the necessary adjustments in the cluster to ensure a successful upgrade.

Step 1: Configure PowerShell Environment

.NET Framework 4.5 or greater installed which is available here.
PowerShell 4.0 or later installed (must be installed after .NET Framework 4.5 or later is installed) which is available here.
NetApp PowerShell Toolkit 3.2.1 installed which is available for download here.

Step 2: Download and Prepare to Run Script

Save the attached file with a ".ps1" extension. Current version 2.5 was uploaded on April 12, 2017.
Start Windows PowerShell with the "Run as Administrator" option.
Execution policy set appropriately to run scripts within PowerShell (currently this script is unsigned).
More help on these requirements can be found here.

Step 3: Run Script (See Details Below)

Find more information about the script by issuing the following in PowerShell:
get-help .\83UpgradeCheck.ps1 -full
Syntax:
.\83UpgradeCheck.ps1 [-HyperV] [-FCP] [-ISCSI] [-NoHyperV] [-NoFCP] [-NoISCSI]
[[-Cluster] <String>] [[-Username] <String>] [[-Password] <String>] [[-RunSection] <String[]>] [[-SkipSection] <String[]>] [[-Outpu
tFile] <String>] [-PostCheck] [-ShowVersion] [<CommonParameters>]
Here is a brief explanation of the optional parameters, see above get-help output for more detail:
HyperV: Cluster has Hyper-V over SMB in use
FCP: Cluster has FCP in use
ISCSI: Cluster has ISCSI in use
NoHyperV: Cluster does not have Hyper-V over SMB in use
NoFCP: Cluster does not have FCP in use
NoISCSI: Cluster does not have ISCSI in use
Cluster: Specify the cluster management LIF used for connection
Username: Specify the username to connect to the cluster
Password: Password to connect to the cluster (note - this is in clear text)
RunSection: One or more specific sections of the script to run
SkipSection: One or more specific sections of the script to skip
OutputFile: A file name to write the output of the script results
PostCheck: To run after 8.3.2 upgrade checks
ShowVersion: Show the version of the script
The script output is color coded as follows:
Purple - Section headers, tells you what is being checked
Red - The check failed
Green - The check succeeded
Yellow - User interaction is needed
Blue - At the completion of the script shows count of errors and warnings

Resources:

Clustered Data ONTAP 8.3.2 Upgrade outlined in several major sections can be found here.

Charts from OpenStack Manila Presentation at OpenStack Summit in Paris

rcallawa — Wed, 03 Dec 2014 16:48:11 GMT

Here are the charts for the presentation “Understanding OpenStack Manila File Share Service” that was presented in Paris at the OpenStack Summit in November of 2014. If you’d like to watch a recording of the presentation, check it out here out on YouTube.

Uncovering NetApp SnapManager 2.1 for Hyper-V for Windows

vinith — Tue, 02 Dec 2014 14:59:25 GMT

This blog posts provides insight into NetApp’s SnapManager for Hyper-V and highlights key features in our newly released SnapManager for Hyper-V 2.1.

SnapManager for Hyper-V provides a solution for data protection, backup and recovery for Microsoft® Hyper-V virtual machines (VMs) running on Data ONTAP® with NetApp storage systems. You can perform application-consistent and crash-consistent dataset backups according to protection policies set by your backup administrator. You can also restore VMs from these backups. Reporting features enable you to monitor the status of and get detailed information about your backup and restore jobs.

NetApp SnapManager for Hyper-V (SMHV) addresses the resource utilization problem typically found in virtual environments by leveraging NetApp Snapshot technology. Using this technology reduces the CPU and network load on the host platforms and drastically reduces the time required for backups to complete. SMHV can be quickly installed and configured for use in Hyper-V environments, saving valuable time during backups, allowing quick and efficient restorations, and reducing administrative overhead.

Backups, restores, and disaster recovery (DR) can place a demanding overhead on Hyper-V virtual infrastructure. NetApp SMHV simplifies and automates the backup process by leveraging the underlying NetApp Snapshot and Snap Restore® and rapid, granular restore and recovery of VMs and their associated datasets.

New features in SMHV 2.1

Support for clustered Data ONTAP 8.3 & MetroCluster

Clustered Data ONTAP 8.3 enhances availability and performance for business-critical applications, simplifies upgrades, deployments and transitions, increases efficiency for entry systems, provides more granular data management for server virtualization, delivers greater SAN scaling and manageability, offers CIFS and NFS enhancements and improves performance of flash storage.

MetroCluster is the solution that provides continuous availability for critical applications for which you can never afford planned or unplanned downtime.

With highly virtualized infrastructures running hundreds of mission-critical applications, the enterprise would likely be severely affected if all of those applications became unavailable simultaneously. In that case, it is the infrastructure that is mission critical, requiring zero data loss and recovery within minutes rather than hours.

MetroCluster addresses the need to provide continuous data availability beyond the data center (or beyond the cluster). MetroCluster enables business continuity and continuous availability beyond the data center, protecting you from events that are beyond the control of the IT organization, such as natural disasters (fires, floods, hurricanes) and site impacting failures (network outage, power loss, unrecoverable corruption).

With MetroCluster, your organization remains up and running by leveraging the synchronously replicated copy at the secondary site. MetroCluster consists of two Data ONTAP clusters that synchronously replicate to each other.

The minimum configuration for MetroCluster is a disaster recovery group that consists of one HA pair at each site, for a total of four nodes (controllers). Each cluster is an active-active HA pair, so all nodes serve clients at all times. This solution can stretch across city-wide or metro-wide deployments up to a maximum distance of 200 km. This capability enables a level of availability that goes beyond the high-availability features of a local cluster, which makes MetroCluster a highly versatile solution.

MetroCluster is an active-active solution, meaning that all nodes in each cluster actively serve data to applications, and data can be read from both the primary and secondary clusters, a feature that can also improve read performance.

Some of the advantages of using a MetroCluster solution:-

Zero data loss—never lose a transaction.
Zero planned and unplanned downtime—whether caused by an IT event or by an external event, such as a hurricane, flood, or loss of communications.
Set-it-once simplicity—with no external devices or host-based configuration.
Zero change management—once it’s set up, all changes on one side are automatically replicated on the other side.
50% lower cost and complexity compared to other solutions—including host-based ones. This includes lower software acquisition cost and cost of ownership of the solution due to its easy-to-manage architecture—again, there are no external devices, capacity-based licenses, or ongoing configuration management. What makes the cost-efficiency story even stronger is the added benefit of storage efficiency and the integration with server virtualization.
Seamless integration with storage efficiency, backup (Snap Vault), DR (SnapMirror), and NDO and non-FAS storage (via Flex Array storage virtualization software)—since they are all built in to the Data ONTAP operating system.
Supports both SAN and NAS—simultaneously, which is noteworthy since most competitive solutions support only SAN protocols.
Hypervisor and application integration—Seamless integration for multiple hypervisor solutions as Hyper-V, VMware.

Support for the validation of virtual machines during the creation or modification of a dataset

The Validate Dataset check box is selected by default. SnapManager for Hyper-V checks for any configuration errors in all VMs during the creation or modification of a dataset. Once the VM’s in the dataset are validated, the below message shows up in validation page

Once an invalid configuration is deleted for virtual machines part of dataset the below error gets thrown.

Refer to the Best Practise Guide for SMHV 2.1 for integrated architecture and implementations of NetApp® SnapManager for Hyper-V.

I hope that you have enjoyed this blog entry and have found this information helpful.

Charts from Red Hat/NetApp Webinar: Deploying Red Hat Enterprise Linux OpenStack Platform 5 on NetApp Storage

rcallawa — Thu, 21 Aug 2014 17:25:34 GMT

Here are the charts from today's webinar!

Reference Architecture: Highly Available OpenStack Deployments Built on NetApp Storage Systems

rcallawa — Thu, 21 Aug 2014 00:13:58 GMT

This document describes the solution design for a highly available deployment of OpenStack built on NetApp® storage systems. It includes architectural considerations, technology choices, and best practices for leveraging the functional and nonfunctional capabilities of NetApp storage systems toward an OpenStack deployment that provides self-service infrastructure-as- a-service (IaaS) capabilities to end users. It is based on the Icehouse release of OpenStack (April 2014).

OnCommand Workflow Automation package for VMware vCenter Orchestrator version 2.2

mcleod — Fri, 07 Aug 2015 20:48:49 GMT

A new version of the OnCommand Workflow Automation package for VMware vCenter Orchestrator has been released. This package integrates WFA 2.2 with VMware's vCenter Orchestrator 5.5. Using this package, NetApp WFA workflows can execute natively within vCenter Orchestrator. In order to understand how to setup this package please refer to TR-4306: Building Automation and Orchestration for Software-Defined Storage with NetApp and VMware.

Supported WFA Builds:

WFA Version: 2.0.0.391.2 B11275, 2.1.0.70.32 B2178337, and 2.2.0.2.6 B2416155

Package Updates

2013-10-21 - Updated the Package to version 2.1 - Now supports VMware’s vCenter Orchestrator 5.1 and 5.5 and OnCommand Workflow Automation 2.0, 2.0.1 and 2.1

2014-01-13 - Updated the Package to version 2.1.1 - Moved to new location for download files. Also fixed a missing Action Script.

2014-07-17 - Updated the Package to version 2.2 - Updated package to support WFA 2.2 by adding a job status of “PLANNING” and to support VMware's vCenter Orchestrator 5.5.1

Closing Locked Files using PowerShell in cDOT

mbeattie — Sun, 08 Jun 2014 03:34:20 GMT

Hi,

Clustered Data ONTAP doesn't support closing locked CIFS files using the MMC yet (coming in a future release) ...but even then do you really want to waste your time clicking in a GUI just to close a locked file?

I'd posted a previous solution for closing locked files in 7-Mode using sysinternals psfile.exe here:

https://communities.netapp.com/thread/22165

Unfortunately psfile.exe doesn't behave well with cDOT and I required the same functionality in cDOT for closing locked CIFS files on a vserver...so I developed a work around solution in the interim (see code and example output below).

I'll be porting this into a WFA workflow and uploading to communities. Hope this helps

Matt

Example Output:

PS C:\Scripts\> .\CloseLockedFile.ps1 -FileSpec "\\vserver1\share1$\folder1\data\employees.accdb"
The Script "CloseLockedFile.ps1" Started Processing.
Imported Module "DataOnTap"
Please enter the password for user "vsadmin": *************
Connected to vserver "vserver1"
Enumerated the mount point for CIFS share "share1$" as "/volume1/qtree1"

NcController : vserver1
Value :
2 entries were acted on.

Executed Command: set advanced;vserver locks break -vserver vserver1 -volume volume1 -lif * -path /volume1/qtree1/folder1/data/employees.accdb
The Script "CloseLockedFile.ps1" Completed Successfully.

#'------------------------------------------------------------------------------

Param(

[CmdletBinding()]

[Parameter(Position=0,

Mandatory=$True,

ValueFromPipeLine=$True,

ValueFromPipeLineByPropertyName=$True)]

[String]$FileSpec

)

<#'-----------------------------------------------------------------------------

'Script Name : CloseLockedFile.ps1

'Author : Matthew Beattie

'Email : mbeattie@netapp.com

'Created : 08/06/14

'Description : This script closes a locked file on a CIFS share on a

' : NetApp storage controller running Clustered Data ONTAP.

' : It accepts a FileSpec parameter containing the UNC Path of the

' : file to close.

'-----------------------------------------------------------------------------#>

#'Initialization Section.

#'------------------------------------------------------------------------------

[String]$scriptPath = Split-Path($MyInvocation.MyCommand.Path)

[String]$scriptSpec = $MyInvocation.MyCommand.Definition

[String]$scriptBaseName = (Get-Item $scriptSpec).BaseName

[String]$scriptName = (Get-Item $scriptSpec).Name

Write-Host "The Script ""$scriptName"" Started Processing."

#'------------------------------------------------------------------------------

#'Split the files UNC Path into variables.

#'------------------------------------------------------------------------------

[String]$modulename = "DataOnTap"

[Array]$elements = $fileSpec -Split [regex]::Escape("\")

[String]$hostName = $elements[2]

[String]$shareName = $elements[3]

[String]$fileName = $elements[$elements.Length -1]

[String]$folderPath = "/"

#'------------------------------------------------------------------------------

#'Import the Data ONTAP powershell module.

#'------------------------------------------------------------------------------

Try{

Import-Module $moduleName -ErrorAction Stop

Write-Host "Imported Module ""$moduleName"""

}Catch{

Write-Error "Failed Importing Module ""$moduleName"""

Break;

}

#'------------------------------------------------------------------------------

#'construct the folder path between the share and file name.

#'------------------------------------------------------------------------------

For($i=4; $i -lt ($elements.Count -1); $i++){

[String]$folderPath = $folderPath + $elements[$i] + "/"

}

#'------------------------------------------------------------------------------

#'Ensure the vserver is online and responding to ICMP requests.

#'------------------------------------------------------------------------------

If(-Not(Test-Connection -computername $hostName -count 1)){

Write-Warning "The vserver ""$hostName"" did not respond to an ICMP request"

Break;

}

#'------------------------------------------------------------------------------

#'Prompt for credentials to connect to the vserver.

#'------------------------------------------------------------------------------

[String]$username = "vsadmin"

[System.Security.SecureString]$password = `

Read-Host "Please enter the password for user ""$username""" -AsSecureString

[System.Management.Automation.PSCredential]$credentials = `

New-Object System.Management.Automation.PSCredential -ArgumentList $username, $password

#'------------------------------------------------------------------------------

#'Connect to the vserver.

#'------------------------------------------------------------------------------

Try{

Connect-NcController -Name $hostName -Credential $credentials -HTTPS -ErrorAction Stop | Out-Null

Write-Host "Connected to vserver ""$hostName"""

}Catch{

Write-Error "Failed connecting to vserver ""$hostName"""

Break;

}

#'------------------------------------------------------------------------------

#'Enumerate the mount point of the CIFS share matching the share name.

#'------------------------------------------------------------------------------

Try{

[String]$mountPoint = Get-NcCifsShare -Name $shareName -ErrorAction Stop | `

Select-Object -ExpandProperty Path

Write-Host "Enumerated the mount point for CIFS share ""$shareName"" as ""$mountPoint"""

}Catch{

Write-Error "Failed enumerating the CIFS share named ""$shareName"""

Break;

}

#'------------------------------------------------------------------------------

#'Set the command to close the locked CIFS file

#'------------------------------------------------------------------------------

[String]$volumeName = $mountPoint.Split("/")[1]

[String]$filePath = "$mountPoint$folderPath$fileName"

[String]$command = "set advanced;vserver locks break -vserver $hostName -volume $volumeName -lif * -path $filePath"

#'------------------------------------------------------------------------------

#'Invoke the command to close the CIFS locked files.

#'------------------------------------------------------------------------------

Try{

Invoke-NcSsh -Name $hostName -Command $command -Credential $credentials -ErrorAction Stop

Write-Host "Executed Command: $command"

}Catch{

Write-Error "Failed executing Command: $command"

Break;

}

Write-Host "The Script ""$scriptName"" Completed Successfully."

#'------------------------------------------------------------------------------

NetApp OpenStack Deployment and Operations Guide 3.0 (Icehouse)

rcallawa — Tue, 03 Jun 2014 14:56:07 GMT

The NetApp OpenStack Deployment and Operations Guide version 3.0. This version focuses on OpenStack Block Storage (Cinder), OpenStack Image (Glance), OpenStack Object Storage (Swift) and aspects of OpenStack Compute (Nova) deployment. As NetApp's File Share Service (the OpenStack Manila development project) is still under development and not yet integrated into OpenStack it is not covered in this version of the guide. This version applies to the Icehouse release of OpenStack and augments and expands upon the community documentation available at:

http://docs.openstack.org/icehouse/config-reference/content/netapp-volume-driver.html

Also note that an HTML version of this page is available at http://netapp.github.io/openstack-deploy-ops-guide/

Note: Please refer to prior versions of this document for Havana or prior.

Configure and Manage Storage Pools with Data ONTAP SMI-S Agent 5.1 on Windows Server 2012 and 2012 R2.

vinith — Thu, 22 May 2014 06:01:01 GMT

In this blogpost i would show how you can configure and manage storage pools with Data ONTAP SMI-S Agent 5.1 on Windows Server 2012 and 2012 R2. for more details on how to get started with Configuring Data ONTAP SMI-S agent with Windows Server 2012 / 2012 R2 check out my previous blogpost Getting started with Configuring Data ONTAP SMI-S Agent 5.1 on Windows Server 2012 and 2012 R2.

We would dig deep into the storage powershell cmdlets which come with the storage module and also see how these cmdlets integrate with the SMI-S agent to manage our NetApp Storage Array.

If i run a measure object on the list of cmdlets in the storage module, we would see that there are about 102 cmdlets.

gcm -Module storage | Measure-Object

Now lets look at the list of cmdlets which can be used to configure and manage storage pools, i can get the list of these cmdlets by filtering the output of the above one liner and check for the cmdlets which match the name pool.

gcm -Module storage | ?{$_.name -match "pool"}

Get-StoragePool gets me the list of all storage pools which exist on the NetApp controller.

So next let us explore the properties of one of these pool's, as you can see below this cmdlet gives us a detailed information regarding the pool.

Get-StoragePool aggr_SC2012 | fl *

To create a new storage pool we need to use the New-StoragePool cmdlet, the New-StoragePool cmdlet creates a new storage pool using a group of physical disks and a specific storage subsystem exposed by a storage provider.

New storage pools are created using the physical disks which are currently not part of any storage pool, these disks should have the canpool property set to true.

To get the list of physical disks use the Get-PhysicalDisk cmdlet.

Get-PhysicalDisk | ft -AutoSize

As you see in the figure above lot of these disks have the canpool property set to false, which means that they are already a part of a storage pool, now to get the list of disks which are free to pool, run the get-physicaldisk cmdlet with the canpool parameter set to true.

Get-PhysicalDisk -CanPool $true | ft -AutoSize

If i dig deep down into the characteristics of a NetApp Disk, im able to see that a detailed information regarding the disk type, serial number etc.

If i execute the Get-PhysicalDisk cmdlet it does not give me the storage subsystem to which its bounded, below you can see that when i execute this cmdlet it does not give me storage subsystem name.

So here's where we use powershell to create custom objects, the below script accomplishes this task.

$storagesubsystem = Get-StorageSubSystem
$volinfoarray = @()
foreach ($stor in $storagesubsystem)
{
$physicaldiskinfo = Get-StorageSubSystem $stor.FriendlyName | Get-PhysicalDisk 
foreach ($physicald in $physicaldiskinfo)
{
       $physicaldiskmodinfo = [pscustomobject][ordered] @{
            'Storage_SubSystem_Name' = $stor.FriendlyName;
            'CanPool' = $physicald.CanPool;
            'BusType' = $physicald.BusType;
            'HealthStatus' = $physicald.HealthStatus;
            'AllocatedSize'  = ([math]::Round([decimal]($physicald.AllocatedSize)/1gb,2));
            'Description'  = $physicald.Description;
            'DeviceId'  = $physicald.DeviceId;
            'Manufacturer'  = $physicald.Manufacturer;
            'Model' = $physicald.Model;
            'SerialNumber' = $physicald.SerialNumber;
            'Size' = $physicald.Size;
            'SpindleSpeed' = $physicald.SpindleSpeed
            }
            $volinfoarray += $physicaldiskmodinfo
}
}

Once i execute this scriptlet it gives me the details of the physical disks along with the storage subsystem to which it belongs.

Now if i look into the output of $volinfoarray, you would be able to see the storagesubsystem name listed.

Next if we filter the output more, i can get the list of disks which are free to be pooled.

$volinfoarray | ?{$_.canpool -match "True"}

Next let me create a storage pool using these free disks.

New-StoragePool -FriendlyName "LUN-1TB" -StorageSubSystemUniqueId (Get-StorageSubSystem -FriendlyName Jupiter).uniqueID -PhysicalDisks (Get-PhysicalDisk -CanPool $true)

As you can see in the figure above once i execute a Get-StoragePool cmdlet im able to see the new storage pool which was created.

Similarly you can use the Remove-StoragePool cmdlet to remove a storage pool, When a storage pool is created, it consumes one or more physical disks to create the pool, from which virtual disks are subsequently created. The removal of a

storage pool, which can only be performed after all virtual disks have first been removed ( which can be accomplished using the Remove-PhysicalDisk cmdlet) , destroys the storage pool, and returns the physical disks back to a non-pooled state, where they may be re-consumed.

PS C:\> Remove-StoragePool -FriendlyName "LUN-1TB"

To modify the properties of the specified storage pool, you can use the Set-StoragePool cmdlet. Below are examples from the cmdlet help.

Example 1: Change the friendly name

PS C:\>Set-StoragePool -FriendlyName StoragePool -NewFriendlyName StoragePool2

Example 2: Make a read-only storage pool writeable

PS C:\>Set-StoragePool -FriendlyName "Storage Pool 1" -IsReadOnly $False

Example 3: Set the default resiliency and provisioning settings

PS C:\>Set-StoragePool -FriendlyName "Storage Pool 1" -ResiliencySettingsNameDefault Mirror -ProvisioningTypeDefault Thin

If you upgrade your Windows Server 2012 infrastructure to Windows Server 2012 R2, storage pools hosted on that server continue to work, but new Storage Spaces functionality, such as storage tiers, is not available. This cmdlet enables new Storage Spaces functionality for a storage pool on a server that runs Windows Server 2012 R2. The Update-StoragePool cmdlet updates the metadata of a Windows Server® 2012 storage pool to a Windows Server® 2012 R2 storage pool.

Below are some examples from the cmdlet output.

Updates the metadata of a Windows Server 2012 R2 storage pool.

Example 1: Upgrade a storage pool by using a friendly name

PS C:\>Update-StoragePool -FriendlyName "Win8Pool32"

I hope that you have enjoyed this blog entry and have found this information helpful. In my next series of blog post i would be taking a deep dive into the powershell cmdlets which can be used to manage Virtual Disks.

Good Luck!

Thanks,

Vinith

Presentation for "NetApp Storage for OpenStack" at Juno Summit

esker — Fri, 16 May 2014 22:33:04 GMT

Session recording available here: http://youtu.be/v_q31iKwTLQ

Lab on Demand for NetApp employees / reselling partners

dlamotta — Thu, 15 May 2014 19:44:09 GMT

Great news for NetApp employees and for NetApp reselling partners! You can access a Lab on Demand (LoD) for the Virtual Storage Console for Apache CloudStack. The LoD is based on a Citrix CloudPlatform 4.3 setup running in RHEL 6.4. In addition, it contains clustered Data ONTAP running 8.2.1 with 2 Storage Virtual Machines, which showcase their power and use in a multi-tenant cloud environment.

We know you are bound to love this LoD! Please let us know what you think.

Video: Annotated Recorded Demo - VSC

dlamotta — Fri, 26 Sep 2014 15:50:08 GMT

This is a recorded video with annotations that was used for mini-theater presentations at Citrix Synergy 2014, as well as being played in a loop at one of the demo stations at the same event.

Use this if you want to see what the VSC looks and feels like!

Best of Synergy 2014 - Cloud: Virtual Storage Console for Apache CloudStack

dlamotta — Thu, 15 May 2014 18:31:07 GMT

We are proud to share that NetApp won the Best of Synergy 2014 in the cloud category with the Virtual Storage Console for Apache CloudStack. There were 4 categories (cloud, mobility, networking and virtualization), and winning was driven by attendee voting. You can find more details by pointing your browser to the URLs sbelow. Enjoy!

http://www.citrix.com/cms/ready/best-of-synergy-2014-winners/

http://blogs.citrix.com/2014/05/08/congratulations-to-the-citrix-best-of-synergy-2014-winners/

Technology Preview - what does it mean?

dlamotta — Thu, 15 May 2014 18:04:00 GMT

Releasing the Virtual Storage Console for Apache CloudStack as a Technology Preview means a few things, most importantly for you is the fact that it is not supported software.

NetApp does not provide any phone or web based technical support for this sofwtare. See the terms and conditions of this Tech Preview software in the EULA.

The VSC has gone through the full software development cycle, including dev/test and formal QA, but given that it is a Tech. Preview it also means use at your own risk. This community is here to provide best-effort help, and under no circumstances should it be considered anything beyond that in terms of support.

A Tech. Preview will allow us to gauge customer demand and interest, so this is your community as much as it is ours. Your feedback and interest in the Virtual Storage Console for Apache CloudStack will be the driving factor to invest resources and develop a roadmap for the software. In other words, if you tell us you'd like a certain feature that currently doesn't exist, or if you see that something is not working as expected, please post it on the community!

Cheers.

SYN232 - Citrix Synergy 2014

dlamotta — Thu, 15 May 2014 17:50:31 GMT

This is the slide deck for SYN232, which was co-presented at Citrix Synergy 2014 by David La Motta and Chris Rodriguez. It covers details of clustered Data ONTAP that are perfectly suited for life in the cloud; the presentation goes over the details of the VSC, including screenshots of the product.

Overview - VSC for Apache CloudStack

dlamotta — Thu, 15 May 2014 17:45:15 GMT

Virtual Storage Console (VSC) for Apache CloudStack is a plug-in that enables you to efficiently manage your NetApp storage from within Apache CloudStack (ACS) or Citrix CloudPlatform (powered by Apache CloudStack) (CCP).

VSC simplifies common storage tasks, saving time and eliminating complexities associated with storage management.

VSC provides the following benefits:

Simplifies and automates the provisioning, resizing, and destruction of storage by implementing the vendor neutral storage subsystem API available from ACS or CCP
Enables visibility into storage consumption, available space, and storage efficiency
Provides the ability to take virtual machine snapshots on a per-request basis when running VMware vSphere
Includes additional features not otherwise available on Citrix CloudPlatform, such as backing up the management server’s database
Leverages other NetApp storage efficiency technologies (such as FlexVol technology, FlexClone technology, and Snapshot technology)
Offloads the backup and recovery to the NetApp storage system, providing a significant performance increase on the virtual machine
Enhances data recovery and protection by providing multiple backup locations (primary storage and NetApp Snapshot copies)

Please review the Installation and Administration Guide for a complete description of what the VSC can do.

Software Requirements

dlamotta — Thu, 15 May 2014 17:32:00 GMT

Please make sure you meet the following software requirements for the Virtual Storage Console for Apache CloudStack:

The minimum supported version for Apache CloudStack (ACS) or Citrix CloudPlatform (CCP) is 4.3
The versions of clustered Data ONTAP supported by the VSC are 8.2 and 8.2.1. Please note that Data ONTAP operating in 7-mode is not supported
ACS or CCP should be installed on a Red Hat Enterprise Linux 6.4 or CentOS 6.4 server
The hypervisors currently supported are:
- VMware ESXi 5.1
- VMware ESXi 5.1 Update1
- VMware ESXi 5.5
- Citrix XenServer 6.1
- Citrix XenServer 6.2

Presentation for 'Manila: An OpenStack File Share Service' at Juno Summit

rcallawa — Thu, 15 May 2014 02:39:46 GMT

Demo available for download here

Session recording available @ https://www.youtube.com/watch?v=fR-X7jbG5QM

Presentation for 'Creating Differentiated Storage Offerings Using Cinder Volume Types' at Juno Summit

rcallawa — Thu, 15 May 2014 02:32:07 GMT

Demo available for download @ https://s3.amazonaws.com/netapp-openstack/cinder_volume_types_demo.mp4

Session recording available @ https://www.youtube.com/watch?v=LO6pQxEwlJ4

Accelerate Data ONTAP SMI-S Agent 5.1 discovery process in SCVMM 2012 R2 using PowerShell Scheduled Job.

vinith — Fri, 18 Apr 2014 04:04:55 GMT

SCVMM 2012 R2 polls "Windows Standard Storage management service" every 2 hours to update its Database, you can verify this behaviour by analyzing the "Reads Storage Provider" job in SCVMM Jobs pane.

We can see below that the Read-SCStorageProvider cmdlet retrieves updated information from the storage provider including array, pool,and logical unit information exposed by the SMI-S provider every two hours.

Now if you need to fasten up this pooling process, you can create a scheduled job using powershell scheduled jobs "PSScheduledjob" module and fasten up the discovery process. Copy paste the below snippet in PowerShell - "Run as Administrator Mode".

#You can create scheduled tasks very easily if you have PowerShell v3 and above .

# Creates a scheduled job immediately which runs every 10 minutes

$trigger = New-JobTrigger -Once -At (Get-Date) -RepetitionInterval (New-TimeSpan -Minutes 10) -RepetitionDuration ([TimeSpan]::MaxValue)

.DESCRIPTION

Following snippet runs the Read-SCStorageProvider cmdlet which retrieves updated information from the storage provider including array, pool,and logical unit information exposed by the SMI-S provider every 10 minutes

ipmo virtualmachinemanager

Get-SCStorageProvider | Read-SCStorageProvider

}

#After i Run this script on my elevated powershell prompt i was able to see the Job created in task scheduler under "TaskSchedulerLibrary\Microsoft\Windows\powershell\scheduledjobs"

Next wait for 10 minutes and verify that the job starts as scheduled every 10 minutes in SCVMM - Jobs pane.

I hope that you have enjoyed this blog entry and have found this information helpful.

Good Luck !

Thanks,

Vinith

Exporting VSC Alignment Scan reports

mbeattie — Sat, 15 Mar 2014 05:00:08 GMT

Hi,

I was recently asked if they is any way to export VSC alignment scan information via an API as there is no export function in the VSC GUI. The information is available in the logs but i wanted to export it via an API rather than parsing the log file.

As it took some time to find the solution I thought i'd share it (credit to Jeremy Maness for providing the API solution). An example of the log looks like this:

"C:\Program Files\NetApp\Virtual Storage Console\log\caster.log"

2014-03-14 13:58:12,690 (pool-3-thread-1) INFO [AlignmentScanManager] - Scanning datastores with the following morefs: [Datastore:datastore-144]

2014-03-14 13:58:12,690 (pool-3-thread-1) INFO [ControllerUtil] - logging level 6 to EMS: Scanning datastores with the following morefs: [Datastore:datastore-144]

2014-03-14 13:58:12,955 (pool-3-thread-1) INFO [ControllerUtil] - logging level 6 to EMS: Scanning datastores with the following morefs: [Datastore:datastore-144]

2014-03-14 13:58:13,455 (pool-3-thread-1) INFO [DatastoreUtil] - getDSVolumeQtreeName: testns01 does not have the address 192.168.100.23

2014-03-14 13:58:13,455 (pool-3-thread-1) INFO [DatastoreUtil] - getDSVolumeQtreeName: testnv01 has the ip address 192.168.100.23 on interface e0b

2014-03-14 13:58:13,455 (pool-3-thread-1) INFO [DatastoreUtil] - getDSVolumeQtreeName: /vol/vol2 replaced with /vol/vol2

2014-03-14 13:58:15,530 (pool-3-thread-1) INFO [DatastoreUtil] - getDSVolumeQtreeName: testnv01 has the ip address 192.168.100.23 on interface e0b

2014-03-14 13:58:15,530 (pool-3-thread-1) INFO [DatastoreUtil] - getDSVolumeQtreeName: /vol/vol2 replaced with /vol/vol2

2014-03-14 13:58:15,530 (pool-3-thread-1) ERROR [AlignmentScanManager] - Invalid suffix detected for an NFS-shimmed volume:

2014-03-14 13:58:15,842 (pool-3-thread-1) INFO [CasterPreferences] - default.option.scanthreads=4

2014-03-14 13:58:15,842 (pool-3-thread-1) INFO [CasterPreferences] - default.option.scantimeout_mins.vms=1440

2014-03-14 13:58:15,842 (pool-3-thread-1) INFO [CasterPreferences] - default.option.migratethreads=4

2014-03-14 13:58:15,889 (VMExaminer-testxp10-1394765895842) INFO [VMExaminerService] - Scanning virtual machine: testxp10 (5021e732-9bcc-f68d-8a64-1c99a4b50867)

2014-03-14 13:58:16,606 (VMExaminer-testxp10-1394765895842) INFO [VMExaminerService] - Cleaning up any remaining snapshots

2014-03-14 13:58:16,638 (VMExaminer-testxp10-1394765895842) INFO [VMExaminerService] - Finished scanning virtual machine: testxp10 (5021e732-9bcc-f68d-8a64-1c99a4b50867)

2014-03-14 13:58:16,669 (pool-3-thread-1) INFO [AlignmentScanManager] - AlignmentScanManager is done

2014-03-14 13:58:16,669 (pool-3-thread-1) INFO [AlignmentScanManager] - Scan initiation ended

Its possible to list of all virtual machines that have been scanned by parsing the log. EG:

C:\Program Files\NetApp\Virtual Storage Console\log>find /i "[VMExaminerService] - Finished scanning virtual machine:" caster.log

---------- CASTER.LOG

2014-03-14 13:58:16,638 (VMExaminer-testxp10-1394765895842) INFO [VMExaminerService] - Finished scanning virtual machine: testxp10 (5021e732-9bcc-f68d-8a64-1c99a4b50867)

A better approach is to use the "getAlignmentReport" API. Here is an example of how to invoke it using powershell:

#'------------------------------------------------------------------------------

Function Get-AlignmentReport{

.SYNOPSIS

Get-AlignmentReport retrieves an alignment status report from a previous alignment scan

.DESCRIPTION

Get-AlignmentReport retrieves an alignment status report from a previous alignment scan.

The alignment scan should be initiated through the VSC user interface.

.PARAMETER VscHostName

Specifies the hostname or IP address of the vCenter Server

.PARAMETER PortNumber

Specifies the VSC Port Number

.PARAMETER Credentials

Specifies the credential object to connect to VSC

.INPUTS

None. You cannot pipe objects to Get-AlignmentReport.

.OUTPUTS

A scannedVirtualMachine object for each virtual machine, containing the following properties:

alignmentStatus alignmentStatus (Enum: FUNCTIONALLY_ALIGNED, ACTUALLY_ALIGNED,

ONLINE_MIGRATION, OFFLINE_ALIGNMENT, OTHER)

alignmentStatusSpecified System.Boolean

datastoreName System.String

hosts System.String

instanceUuid System.String

moref System.String

name System.String

offset System.Int32

offsetSpecified System.Boolean

.EXAMPLE

C:\PS> Get-AlignmentReport -VscHostName "testvc01" -PortNumber 8143 -Credentials $credentials

.LINK

http://www.netapp.com/us/products/management-software/vsc/

[CmdletBinding()]

Param(

[Parameter(Position=0,

Mandatory=$True,

ValueFromPipeLine=$True,

ValueFromPipeLineByPropertyName=$True)]

[String]$VscHostName,

[Parameter(Position=1,

Mandatory=$True,

ValueFromPipeLine=$True,

ValueFromPipeLineByPropertyName=$True)]

[Int]$PortNumber,

[Parameter(Position=2,

Mandatory=$True,

ValueFromPipeLine=$True,

ValueFromPipeLineByPropertyName=$True)]

[System.Management.Automation.PSCredential]$Credentials

)

#'---------------------------------------------------------------------------

#'Bypass SSL certificate confirmation

#'---------------------------------------------------------------------------

[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$True}

#'---------------------------------------------------------------------------

#'Create a web service connection to VSC

#'---------------------------------------------------------------------------

[String]$uri = "https://$VscHostName`:$PortNumber/caster/public/api?wsdl"

Try{

[System.Web.Services.Protocols.SoapHttpClientProtocol]$connection = `

New-WebServiceProxy -uri $uri -Credential $Credentials -ErrorAction Stop

Write-Host "Connected to VSC on ""$uri"""

}Catch{

Write-Host ("Error """ + $Error[0] + """ Connecting to ""$uri""")

Break;

}

#'---------------------------------------------------------------------------

#'Enumerate the VSC namespace

#'---------------------------------------------------------------------------

[System.Object]$namespace = $connection.GetType().Namespace

#'---------------------------------------------------------------------------

#'Enumerate the VSC username and password from the Credential object

#'---------------------------------------------------------------------------

[String]$vscDomain = $Credentials.GetNetworkCredential().domain

[String]$vscUser = $Credentials.GetNetworkCredential().username

[String]$vscPassword = $Credentials.GetNetworkCredential().password

[String]$vscUsername = "$vscDomain\$vscUser"

#'---------------------------------------------------------------------------

#'Create a requestSpec object and set credentials.

#'---------------------------------------------------------------------------

[System.Object]$requestSpecType = ($namespace + '.requestSpec')

[System.Object]$requestSpec = New-Object ($requestSpecType)

[System.Object]$requestSpec.serviceUrl = "https://" + $vscHostName + "/sdk"

[System.Object]$requestSpec.vcUser = $vscUsername

[System.Object]$requestSpec.vcPassword = $vscPassword

#'---------------------------------------------------------------------------

#'Invoke the GetAlignmentReport API and return the results.

#'---------------------------------------------------------------------------

Try{

$results = $connection.getAlignmentReport($requestSpec)

}Catch{

Write-Host ("Error """ + $Error[0] + """ invoking the ""GetAlignmentReport"" Method")

Break;

}

Return $results;

}#End Function

#'------------------------------------------------------------------------------

#'Prompt for VSC credentials.

#'------------------------------------------------------------------------------

[String]$username = "testlab\administrator"

[System.Security.SecureString]$password = Read-Host "Please enter the password for user ""$username""" -AsSecureString

[System.Management.Automation.PSCredential]$Credentials = New-Object System.Management.Automation.PSCredential -ArgumentList $username, $password

#'------------------------------------------------------------------------------

#'Enumerate the VSC alignment report and display the results.

#'------------------------------------------------------------------------------

$results = Get-AlignmentReport -VscHostName "testvc01" -PortNumber 8143 -Credentials $Credentials

$results | Where-Object {$_.alignmentStatus -eq "ONLINE_MIGRATION"}

#'------------------------------------------------------------------------------

Example output:

PS C:\Scripts\PowerShell\Projects\VSC> .\GetAlignmentReport.ps1
Please enter the password for user "testlab\administrator": *************
Connected to VSC on "https://testvc01:8143/caster/public/api?wsdl"

alignmentStatus : ONLINE_MIGRATION

alignmentStatusSpecified : True

datastoreName : datastore1

instanceUuid : 5021e732-9bcc-f68d-8a64-1c99a4b50867

moref : VirtualMachine:vm-411

name : testxp10

offset : 7

offsetSpecified : True

GUI View:

Hope that helps

Cheers Matt

perf report -t output as object

markweber — Mon, 10 Feb 2014 16:12:04 GMT

just ran across "perf report -t" and wanted to be able to get the same format from powershell.

these are quick (and probably inefficient) functions that format the cpu_disk_util_matrix counter as a table like the output from "perf report -t"

cluster version returns a hash.

. .\get-naperfreport.ps1

Get-NaPerfReport -Controller <filer> | out-gridview

. .\get-ncperfreport.ps1

$results = Get-NcPerfReport -Controller <cluster>

$results.item("<node>") | out-gridview

7-mode:

Function Get-NaPerfReport{

[CmdletBinding()]

Param(

[Parameter(Mandatory=$False,

ValueFromPipeline=$true)]

[String]$Controller

)

Begin{

if($Controller){

connect-nacontroller $Controller > $null

}

$results = @()

}

Process{

$raw = (get-naperfdata perf -Counters cpu_disk_util_matrix).counters.Value

$matrix = $raw.split(',')

foreach($i in 0..9){

$cpulabel = "$($i*10) to $(($i+1)*10)% CPU"

$total = ($matrix[($i*10)..((($i+1)*10)-1)] | Measure-Object -sum).sum -as [int64]

$Prop=[ordered]@{

'CPU bucket' = $cpulabel

'10disk' = $matrix[(($i)*10)] -as [int64]

'20disk' = $matrix[(($i)*10)+1] -as [int64]

'30disk' = $matrix[(($i)*10)+2] -as [int64]

'40disk' = $matrix[(($i)*10)+3] -as [int64]

'50disk' = $matrix[(($i)*10)+4] -as [int64]

'60disk' = $matrix[(($i)*10)+5] -as [int64]

'70disk' = $matrix[(($i)*10)+6] -as [int64]

'80disk' = $matrix[(($i)*10)+7] -as [int64]

'90disk' = $matrix[(($i)*10)+8] -as [int64]

'100disk' = $matrix[(($i)*10)+9] -as [int64]

'total' = $total

}

$Obj=New-Object -TypeName PSObject -Property $Prop

$Results += $Obj

}

$prop=[ordered]@{}

$prop.'CPU bucket'="total"

$prop.'10disk'=($results.'10disk' | measure-object -sum).sum -as [int64]

$prop.'20disk'=($results.'20disk' | measure-object -sum).sum -as [int64]

$prop.'30disk'=($results.'30disk' | measure-object -sum).sum -as [int64]

$prop.'40disk'=($results.'40disk' | measure-object -sum).sum -as [int64]

$prop.'50disk'=($results.'50disk' | measure-object -sum).sum -as [int64]

$prop.'60disk'=($results.'60disk' | measure-object -sum).sum -as [int64]

$prop.'70disk'=($results.'70disk' | measure-object -sum).sum -as [int64]

$prop.'80disk'=($results.'80disk' | measure-object -sum).sum -as [int64]

$prop.'90disk'=($results.'90disk' | measure-object -sum).sum -as [int64]

$prop.'100disk'=($results.'100disk' | measure-object -sum).sum -as [int64]

$prop.'total'=($results.'total' | measure-object -sum).sum -as [int64]

$Obj=New-Object -TypeName PSObject -Property $Prop

$results += $Obj

}

End{

Write-Output $results

}

cDOT:

Function Get-NcPerfReport{

[CmdletBinding()]

Param(

[Parameter(Mandatory=$False,

ValueFromPipeline=$true)]

[String]$Controller

)

Begin{

if($Controller){

connect-nccontroller $Controller > $null

}

$results = @()

$hash = @{}

}

Process{

$raw = get-ncperfdata perf -Instance perf -Counter cpu_disk_util_matrix

foreach($r in $raw){

$results = @()

$node = $r.uuid.split(':')[0]

$matrix = $r.Counters.value.split(',')