2016-10-20 01:06 AM - edited 2016-10-20 01:21 AM
OCI 7.2.3 shipped today. We are optimistic that in month or two, this release will be blessed with GA status, so if you are on OCI 7.1.x or earlier, you ought to install 7.2.3 in a lab and start testing for an upgrade.
OCI 7.2.3 introduces a new NFS traffic capability for our Perform customers - while OCI knows the IOP workload of all Ontap flexvols, OCI historically hasn't been able to tell you what client is driving that load, for flexvols with more than one client. The new Ethernet Monitoring Unit , or EMU, capability allows OCI to analyze your NFS ethernet traffic.
Our WebUI landing pages have been enhanced to improve usability in storage virtualization environments - if a Volume is a Virtual Volume in OCI speak, as in being presented by a storage virtualizer and sitting on 3rd party volumes, you will now see an icon to indicate the volume is virtual, and there is a new table on the landing page showing the back end volumes to allow for you to quickly understand what the back end volumes' performance looks like. Likewise, if a Volume is a Back end Volume, an icon will indicate as such, and there is a different table to show all the virtual volumes that map to this back end volume. As always, for OCI to understand the storage virtualization relationships, you need to discover both the storage virtualizer and back end storage arrays with datasources.
OCI 7.2.3 has Data Source Service Pack 4 built in. SP4 officially promotes a handful of datasources we have been shipping out of beta status, along with bug fixes and new enhancements like HNAS qtree support, and Openstack + KVM latency support. All OCI 7.2[0-2] environments should install the SP4 to keep their data source code up to date.
Release notes https://library.netapp.com/ecm/ecm_get_file/ECMLP2572612
2016-10-20 08:57 PM
Here is an example of the enhanced storage virtualization capabilites in our WebUI from our demo database running on OCI 7.2.3
The volume icon may show a V or B to indicate a virtual volume (as on this vSeries virtualizer), or a backend volume if it is behind a virtualizer.
If we scroll down, a new table showing the backend or virtual volumes that relate to this virtual volume, or backend volume respectively