NetApp and OpenStack

1. NetApp OpenStack site
https://netapp.github.io/openstack/

2. Continuous Operations with OpenStack’s File-Share Service (Manila)
https://www.youtube.com/watch?v=Mvhx1gRgUUI

3. NetApp - Jumpstart Your Production OpenStack
https://www.youtube.com/watch?v=5YZPHc2y7XY

New features and Enhancements of NetApp OnTap 9

Primary ONTAP Features

1. Leading enterprise-class data services • Unified management across flash, disk, and cloud, as well as SAN and NAS protocols
2. High performance for all-flash solutions • Nondisruptive operations
3. Scaling up to 24-nodes
4. Storage efficiency and inline data reduction 
5. NetApp Integrated Data Protection 
6. NetApp OnCommand® management software

 New Features: ONTAP 9 

1. Simplified AFF deployments in <10 li="" microsoft="" minutes="" racle="" server="" sql="" vdi="" vmware="">
2. Up to 60% more IOPS than with ONTAP 8.3.1 
3. ONTAP Select (for SDS) and ONTAP Cloud 
4. Support for 15TB SSD 
5. Inline data compaction works with compression and deduplication for greater data reduction
6. SnapLock® software for data compliance 
7. RAID-TEC triple-parity protection 
8. Headroom for visibility of performance capacity 
9. MetroCluster enhancements (lower TCO,  8-node NAS configurations) 
10. Onboard key manager 
11. Inline deduplication and compression 
12. MetroCluster 2-node solutions and improved distance (300km), performance, and deployment
13. Storage virtual machine disaster recovery  
14. Foreign LUN import enhancements

References:

1. NetApp ONTAP 9 Datasheet

Resolving downed Interface Group on NetApp Cluster-Mode

netapp-cluster1::*> network port show
Auto-Negot  Duplex     Speed (Mbps)
Node   Port   Role         Link   MTU Admin/Oper  Admin/Oper Admin/Oper
------ ------ ------------ ---- ----- ----------- ---------- ------------
netapp-cluster1-01
a0a    data         down  1500  true/-     auto/-      auto/-
e0a    data         up    1500  true/true  full/full   auto/1000
e0b    data         up    1500  true/true  full/full   auto/1000
e0c    data         up    1500  true/true  full/full   auto/100
e0d    data         up    1500  true/true  full/full   auto/1000

2. If you have a LIF that should be on that node; do the following: The purpose is to let another node within the cluster to be the home-node for the data and mgmt while you up and down the interface group

netapp-cluster1::*> net int modify -vserver vs_StorageVNode11  -lif vs_StorageVNode11_data1 -home-node netapp-cluster1-02 -home-port a0a
netapp-cluster1::*> net int modify -vserver vs_StorageVNode11  -lif vs_StorageVNode11_mgmt1 -home-node netapp-cluster1-02 -home-port a0a
net int revert *

3. Remove the Interface Group from the -port e0c and down and up the e0c port

netapp-cluster1::*> ifgrp remove-port -node netapp-cluster1-01 -ifgrp a0a -port e0c
netapp-cluster1::*> net port modify -node netapp-cluster1-01 -port e0c -up-admin false
netapp-cluster1::*> net port modify -node netapp-cluster1-01 -port e0c -up-admin true
netapp-cluster1::*> net port show -node netapp-cluster1-01 -port a0a,e0c

Once If e0c shows up and at auto/1000, add the interface and return the interface group back to netap-cluster-01

netapp-cluster1::*> ifgrp add-port -node netapp-cluster1-01 -ifgrp a0a -port e0c
netapp-cluster1::*> net port show -node netapp-cluster1-01 -port a0a
netapp-cluster1::*> net int modify -vserver vs_StorageVNode11 -lif vs_StorageVNode11_data1 -home-node netapp-cluster1-01 -home-port a0a
netapp-cluster1::*> net int modify -vserver vs_StorageVNode11 -lif vs_StorageVNode11_mgmt1 -home-node netapp-cluster1-01 -home-port a0a
netapp-cluster1::*> net int revert *

Node, port and Lif Information for NetApp

Useful References

1. How to determine the node, port, or lif to which a client should be connected
   https://kb.netapp.com/support/index?page=content&id=1013873&locale=en_US&access=s
   
2. How to determine why a lif is on a certain port or node
   https://kb.netapp.com/support/index?page=content&id=1013874&locale=en_US&access=s
   
3. Enabling and reverting LIFs to home ports
   https://library.netapp.com/ecmdocs/ECMP1636041/html/GUID-7865FB3E-F57B-4976-803D-A87F2F760342.html

Enabling Predictive Cache Statistics (PCS) for Data OnTap 8.2p

* node1 is the controller currently primary to the aggregate/vol/LUN.

Step 1: Enable PCS

node1::> node run –node node1
node1::> options flexscale.enable on
node1::>options flexscale.enable
flexscale.enable pcs  you should see this
node1::>options flexscale.pcs_size 330GB  based on 3 x 200GB SSD RAID4

Step 2: Allow the representative workload to run and Run your workload

Step 3: Collect data throughout the process

node1::>stats show -p flexscale-access

NetApp recommends issuing this command through an SSH connection and logging the output throughout the observation period because you want to capture and observe the peak performance of the system and the cache. This output can also be easily imported into spreadsheet software, graphed, and so on. This process initially provides information on the “cold” state of the emulated cache. That is, no data is in the cache at the start of the test, and the cache is filled as the workload runs. The best time to observe the emulated cache is once it is filled, or “warmed”, as this will be the point when it enters a steady state. Filling the emulated cache can take a considerable amount of time and depends greatly on the workload. References:

1. Introduction to Predictive Cache Statistics
2. Clustered_Data_ONTAP_82_System_Administration

NetApp Visual Storage Console (VSC)5.0 Plugin for VCentre 5.5

VSC 5.0 is a major change that includes a new look and seamless integration with the VMware vSphere Web Client. New features in this release include support for the following:

• The VMware vSphere Web Client
• VASA Provider for clustered Data ONTAP®
• SnapVault integration as a backup job option for clustered Data ONTAP
• Adding a virtual machine or datastore to an existing backup job
• Numerous bug fixes

VSC 5.0 discontinues support for the following:

• vCenter 5.1 and earlier
• VMware Desktop client
• 32-bit Windows installations
• mbralign
• Single File Restore
• Datastore Remote Replication
• Flash Accel

To download, see  http://mysupport.netapp.com/NOW/download/software/vsc_win/5.0/

NetApp SteelStore Cloud Integrated Storage Appliance

Taken from NetApp SteelStore

Quick Overview

Use the NetApp® SteelStore™ cloud integrated storage appliance to leverage public and private cloud as part of your backup and archive strategy.

Features (from the website) includes

• Integrates with all leading backup solutions and all major public and private cloud providers.
• Offers complete, end-to-end security for data at rest and in flight using FIPS 140-2 certified encryption.
• Uses efficient, variable-length inline deduplication and compression, reducing storage costs up to 90%.
• Delivers fast, intelligent local backup and recovery based on local storage.
• Vaults older versions to the cloud, allowing for rapid restores with offsite protection.
• Supports policy-based data lifecycle management.
• Scales to an effective capacity of 28PB per appliance.

Technical Specification

How to do setup auto-support for NetApp DataOnTap

This is taken from Data ONTAP 8.1 System Administration Guide for Cluster-Mode Guide Page 142. See attached for the document How to setup AutoSupport (pdf)

Data OnTap 7-Mode to Cluster-Mode Command Map

If you have been using Data OnTap 7-Mode but if you need the equivalent for Cluster-Mode. Do look at this pdf for the mapping. You will find it very useful.

For more information, do take a look at Data OnTap 7-Mode to Cluster-Mode Command Map

Tracking NetApp Cluster-Mode Performance

To track NetApp Storage on Cluster Performance, do use the statistics "statistics show-periodic"

netapp-cluster1::> statistics show-periodic
cluster:summary: cluster.cluster: 9/9/2014 09:33:29
cpu    total                   data     data     data cluster  cluster  cluster     disk     disk
busy      ops  nfs-ops cifs-ops busy     recv     sent    busy     recv     sent     read    write
---- -------- -------- -------- ---- -------- -------- ------- -------- -------- -------- --------
5%      303      303        0   2%   4.86MB    223KB      0%   1.16MB   1.17MB    685KB    571KB
5%      312      312        0   3%   8.27MB    359KB      0%   1.11MB   1001KB    679KB   39.4KB
8%      300      300        0   2%   7.29MB    495KB      0%   2.87MB   3.30MB   2.66MB   59.1KB
6%      158      158        0   1%   3.53MB    168KB      0%   2.16MB   1.51MB   2.71MB   11.1MB
5%      184      184        0   2%   4.48MB   1.22MB      0%   1.99MB   1.97MB   1.21MB   10.9MB
5%      213      213        0   1%   2.82MB    222KB      0%    902KB    749KB    240KB    671KB
3%      144      144        0   1%   2.32MB    762KB      0%    559KB    685KB   96.6KB   15.8KB
4%      199      199        0   1%   3.73MB    881KB      0%    796KB    715KB    390KB   39.6KB
7%      164      164        0   1%   4.49MB    365KB      0%   2.34MB   2.43MB   2.52MB   8.33MB
7%      115      115        0   2%   4.07MB    154KB      0%   1.23MB   1.25MB   2.41MB   9.80MB
3%      224      224        0   1%   2.72MB    163KB      0%   1.80MB    721KB    407KB    996KB
4%      220      220        0   1%   4.38MB   1.32MB      0%    451KB   1.54MB    199KB    110KB
5%      124      124        0   1%   2.97MB    157KB      0%    315KB    273KB    251KB   15.8KB
7%      153      153        0   0%   1.76MB    139KB      0%    220KB    268KB   2.54MB   1.28MB
4%      120      120        0   0%   1.30MB   80.4KB      0%    417KB    325KB   2.86MB   13.9MB
cluster:summary: cluster.cluster: 9/9/2014 09:34:01
cpu    total                   data     data     data cluster  cluster  cluster     disk     disk
busy      ops  nfs-ops cifs-ops busy     recv     sent    busy     recv     sent     read    write
---- -------- -------- -------- ---- -------- -------- ------- -------- -------- -------- --------
Minimums:
3%      115      115        0   0%   1.30MB   80.4KB      0%    220KB    268KB   96.6KB   15.8KB
Averages for 15 samples:
5%      195      195        0   1%   3.93MB    451KB      0%   1.22MB   1.19MB   1.32MB   3.84MB
Maximums:
8%      312      312        0   3%   8.27MB   1.32MB      0%   2.87MB   3.30MB   2.86MB   13.9MB

Quick Check to identify broken disk for NetApp Ontall 8.2p2 Cluster mode

1. Identify the Cluster Nodes

My-NetApp-Cluster::> cluster show

Node                  Health  Eligibility
--------------------- ------- ------------
cluster1-01      true    true
cluster1-02      true    true
cluster1-03      true    true
cluster1-04      true    true
4 entries were displayed.

2. Check for Broken Disk

My-NetApp-Cluster::> run -node cluster1-01 vol status -f
RAID Disk Device   HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
--------- ------   ------------- ---- ---- ---- ----- --------------    --------------
failed   0a.00.12 0a    0   12  SA:A   -  BSAS  7200 1695466/3472315904 1695759/3472914816 
failed   0b.00.9  0b    0   9   SA:B   -  BSAS  7200 1695466/3472315904 1695759/3472914816 

3. Get System Information

My-NetApp-Cluster::> run -node cluster1-01 sysconfig -a
NetApp Release 8.2P2 Cluster-Mode: Sat Jul 20 20:31:47 PDT 2013
.....
.....
.....

Assigning ownership to disks for NetApp Storage

After replacing broken disks for NetApp Storage and if you want to manually assigned ownership back to the newly replaced but assigned disks, you can use the following command

1. Show Storage Ownership Information

My-NetApp-Cluster::> storage disk show -spare
Original Owner: acai-cluster1-01
  Checksum Compatibility: block
                                                            Usable Physical
    Disk            HA Shelf Bay Chan   Pool  Type    RPM     Size     Size Owner
    --------------- ------------ ---- ------ ----- ------ -------- -------- --------
    cluster1-01:0b.00.9
                    0b     0   9    B  Pool0  BSAS   7200   1.62TB   1.62TB cluster1-01
Original Owner: cluster1-02
  Checksum Compatibility: block
                                                            Usable Physical
    Disk            HA Shelf Bay Chan   Pool  Type    RPM     Size     Size Owner
    --------------- ------------ ---- ------ ----- ------ -------- -------- --------
    cluster1-02:0a.00.7
                    0a     0   7    B  Pool0  BSAS   7200   1.62TB   1.62TB cluster1-02
.....
.....

2. Display all unowned disks by entering the following command:

My-NetApp-Cluster::> storage disk show -container-type unassigned


                     Usable           Container
Disk                   Size Shelf Bay Type        Position   Aggregate Owner
---------------- ---------- ----- --- ----------- ---------- --------- --------
cluster1-01:0b.00.9
                     1.62TB     0   9 spare       present    -         cluster1-01
cluster1-02:0a.00.7
                     1.62TB     0   7 spare       present    -         cluster1-02

3. Assign each disk by entering the following command

My-NetApp-Cluster::> storage disk assign -disk cluster1-01:0b.00.9 -owner cluster1-01

Data ONTAP Cluster-Mode Vsim Tutorial

10 steps to a 2-node Data ONTAP 8.1.1 Cluster-Mode Vsim cluster. See https://www.youtube.com/watch?feature=player_embedded&v=prEf5J0wvi0

Multiprotocol Performance Test of VMware EX 3.5 on NetApp Storage Systems

This paper "Performance Report: Multiprotocol Performance Test of VMware® ESX 3.5 on NetApp Storage Systems" by NetApp and Vmware was written in 2008 is a interesting comparison with 3 protocols, FC, iSCSI and NFS. The variation between the protocols is about maximum 9%. With the advent of the new Vmmare VSphere, 10G with TOE etc, the performance gap may be close that in 2008.

The summary of the pro and cons as mentioned in the article is summarised at Multiprotocol Performance Test of VMware EX 3.5 on NetApp Storage Systems

Restoring a snapshot from Netapp from a newbie

I am a newbie to NetApp Storage solution. Creation and restoring Snapshot in Netapp could not be easier.

Basically, NetApp provides a very easy-to-recognise snapshot features. The Snapshot schedules are

1.  Weekly Snapshot copies are taken at 24:00 on Sunday, creating Snapshot copies called weekly.n, where n is an integer (weekly.0, weekly.1, weekly.2, and so on).
2. Nightly Snapshot copies are taken at 24:00 Monday through Saturday, creating Snapshot copies called nightly.n, where n is an integer (nightly.0, nightly.1, and so on).
3. Four hourly Snapshot copies are taken at 8 a.m., noon, 4 p.m., and 8 p.m., unless specified otherwise using the hourly Snapshot copy schedule in this window, creating Snapshot copies called hourly.n, where n is an integer (hourly.0, hourly.1, hourly.2, and so on).

You can easily select your snapshot schedule with some simple select and click.

If you make your snapshot directory visible, The snapshot content can be easily be seen from .shapshot directory of the NetApp volume.Restoration is very easy then. Assuming the NetApp volume is mounted as /home and you wish to recover nightly.0

# cp -avp /home/.snapshot/nightly.0/home/mysite/recover_my_folder /home/mysite/

that's it! I was quite amazed at the ease of the restoration of the lost folder.

How Cloud helped lift a nation

A nice write-up on how Cloud Computing using NetApp storage. This article and video shows how after the devastating earthquake and tsunami in Japan changes how the way a corporation - Softbank work.

1. A Disaster Can Teach Us What’s Possible
2. Video about Softbank

Best Practices for VMware vSphere 5 on NetApp Data ONTAP

This updated technical report Best Practices for Vmware vSphere 5 covers 3 main areas

1. How the new and updated technologies from VMware and NetApp enable you to virtualize demanding business-critical applications
2. The role of the best practice TR as it relates to the rest of the joint VMware and NetApp solutions documents in the NetApp technical library
3. How to enable coordinated and automated cross-domain operations where resources are consumed dynamically while complying with operational standards

 Interesting Extraction from the article


With VMware vSphere 5 you can deploy “monster VMs”—virtual machines configured with a maximum of 32 virtual CPUs and 1TB of memory. To put the new configurations of a “monster VM” in perspective, in vSphere 4.1 a virtual machine was limited to 8 virtual CPUs and 255GB of memory. The VMware engineering team has outdone itself in delivering such an increase in computing capacity.

NetApp has also enhanced the performance of the dedupe intelligence within the storage caches of its arrays. Dedupe-aware storage controller cache is unique to NetApp and is a feature that we developed and brought to market specifically for use with server virtualization. If you’re familiar with the performance benefits of VMware Transparent Page Sharing, then just imagine that technology in the cache of a storage array. NetApp is the only array that allows data cached from one VM to be accessed when servicing a subsequent request by another VM......

Interesting related technical report "NetApp Storage Best Practices for VMware vSphere" (pdf)

How to replace failed disk on N-Series Filer

I had 2 failed disk on 1 aggregate for my N-Series (N3600)  or NetApp FAS2050. I was really thankful that NetApp is RAID-6 with Dual Parity. Here are the steps that I took to quickly replace my failed disks.

Of course, I new that that the disks has failed as I see  amber lights on my failed disks. I verify with the Syslog Messages in my Filer and this confirmed the 2 disks have failed.

NetApp Filer has hot-swappable disks, so it is safe to pull out the failed disks. Do verify that the disks has failed though. One you have replaced the disks, it should automatically detect the correct controller. If it does not, you have to do the following

Controller-A> disk show -n

 DISK       OWNER               POOL
------     -------             ------
0a.76    Not Owned              NONE    

U should see that the disk are unowned. I'm assuming you are using the controller console you are assigning the disk to. Just type

Controller-A> disk assign 0a.76

At your syslog file, you should see the disk being rebuilt. If somehow it the N-Series Filer do not accept the command above, you have to unown the disk again and enter the right controller console and assign the disk again. To unown, use the following command

Controller-A> disk assign 0a.76 -s unowned -f

NetApp posts world-record SPEC SFS2008 NFS benchmark result

NetApp achieved over 1.5 million SPEC SFS2008 NFS operations per second with a 24-node cluster based on FAS6240 boxes running ONTAP 8 in Cluster Mode......For more information, see NetApp posts world-record SPEC SFS2008 NFS benchmark result