Chapter 1. Release Notes for NetApp ONTAP Connector Pack

- Cisco UCS Director

- Connector Packs

- NetApp ONTAP Connector Pack

- New and Changed Features in Release 6.6.0.1

- Open Bugs

- Resolved Bugs

- Communications, Services, and Additional Information

Cisco UCS Director

Cisco UCS Director delivers unified, highly secure management for supported compute, network, storage, and virtualization platforms and for the industry's leading converged infrastructure solutions, which are based on the Cisco Unified Computing System (Cisco UCS) and Cisco Nexus platforms. Cisco UCS Director extends the unification of computing and network layers through Cisco UCS to provide data center administrators with comprehensive visibility and management capabilities for compute, network, storage, and virtualization. For more information, see Cisco UCS Director on Cisco.com.

- Revision History

Revision History

Release

Date

Description

6.6.0.1

August 22, 2018

Created for Release 6.6.0.1.

Connector Packs

Connector packs help you perform connector level upgrade in Cisco UCS Director without impacting other connectors and without having to upgrade the entire software version. After claiming Cisco UCS Director in Cisco Intersight, as a system administrator, you can view information on new versions of connector packs that are available for upgrade. The top header pane of the user interface displays a Download icon indicating that new connector pack versions are available. You can select and upgrade the connector packs in Cisco UCS Director.

NetApp ONTAP Connector Pack

Cisco UCS Director supports the NetApp storage infrastructure. Cisco UCS Director provides auto-discovery, monitoring, and complete visibility for all NetApp filer components, such as nodes, SVMs, IPspaces, aggregates, and SnapMirrors. The NetApp ONTAP connector pack provides features and defect fixes for NetApp storage infrastructure. Using the connector pack, you can upgrade to the latest version of NetApp ONTAP connector pack.

- Upgrading Connector Packs

- Viewing Connector Pack Upgrade Information

Upgrading Connector Packs

Before you begin

- You must have system administrator privileges in Cisco UCS Director.

- Cisco UCS Director has been claimed in Cisco Intersight. For information on claiming a device, see the integrated guided walkthrough titled Learn How to Claim a Device available within the Online Help menu in the Cisco Intersight user interface.

- Cisco UCS Director is successfully connected to Cisco Intersight.

- Take a snapshot of Cisco UCS Director before you initiate the upgrade.

Procedure

Step 1

On the header, click New Upgrades Available.

The Available System Upgrades screen appears and will display all available connector packs for upgrade along with version information. Upon login, if you clicked Yes to the pop-up message, then the very same upgrade screen appears.

Note

The New Upgrades Available icon is visible on the header only when new versions of the current running connector packs are available for upgrade.

Step 2

Check the check box of a connector pack from the list.

You can check the check boxes of multiple connector packs.

Step 3

Click Upgrade.

Step 4

In the Confirm Upgrade dialog box, click Yes.

After you confirm that the connector version must be upgraded, the validation process is initiated. If the validation process completes successfully, the upgrade process is initiated and the System Upgrade Status screen displays the upgrade status. After the upgrade process is successful, the Logout option is enabled.

Step 5

Click Logout.

While upgrading a base platform pack that includes changes to all infrastructure components, all Cisco UCS Director services are restarted. As a result, after clicking Logout, the screen could appear to be unresponsive for a few minutes. After all the services are restarted, and the upgrade process is complete, you can login to Cisco UCS Director .

What to do next

You can view the upgrade reports by choosing Administration > System > System Updates. From this screen, you can double-click on a report, and view additional details on the upgrade process. For more information, see Viewing Connector Pack Upgrade Information.

Viewing Connector Pack Upgrade Information

Procedure

Step 1

Choose Administration > System.

Step 2

On the System page, click System Updates.

Information such as upgrade request ID, user that initiated the upgrade, upgrade start time and end time, and the upgrade status are displayed.

Step 3

Select a connector pack and choose View Details to view details such as connector pack name, upgraded version, and prior version.

Step 4

Click State History to view the various states of the connector pack upgrade process. For example, upgrade request received, upgrade process initiated or upgrade process completed.

Step 5

Click Stages to view the entire lifecycle of the connector pack upgrade request.

New and Changed Features in Release 6.6.0.1

This section provides an overview of the significant new and changed features in this release.

Support for Migrating LUNs

This release of Connector Pack provides an option to move a LUN from one volume to another within the same Storage Virtual Machine (SVM) without causing any disruption in data. You can execute the Migrate NetApp Cluster LUN workflow task to migrate LUNs..

Note

To view descriptions of these workflow tasks, see the Task Library that you can launch in the following ways:

- Choose Orchestration > Workflows in the user interface.

- Go to http://IP_address/app/cloudmgr/onlinedocs/cloupiaTaskLib.html where IP_address is the IP address of Cisco UCS Director.

Support for Enabling and Disabling Data Compression

This release of Connector Pack provides an option to enable and disable data compression within a volume to reduce the storage capacity. By checking the Enable Background Compression and Enable Inline Compression check boxes, you can enable background and inline compression of data respectively. You can also execute the Modify NetApp Cluster Flexible Volume Compression Status workflow task to enable and disable data compression within a volume.

Support for FlexGroup Volumes

This release of Connector Pack provides an option to create FlexGroup volumes. A FlexGroup volume is a scale-out Network Attached Storage (NAS) container that provides high performance along with automatic load distribution and scalability. A FlexGroup volume contains several constituents that automatically and transparently share the traffic.

Following are the workflow tasks introduced in this release to manage FlexGroup volumes:

- Create NetApp Cluster FlexGroup Volume

- Destroy NetApp Cluster FlexGroup Volume

Support for User and Group Quotas

This release of Connector Pack provides an option to create user quotas and group quotas on a volume or a QTree. A quota limits the amount of disk space and the number of files that a particular user or group can consume.

Following are the workflow tasks modified in this release to manage user and group quotas:

- Add NetApp Cluster Quota

- Delete NetApp Cluster Quota

- Modify NetApp Cluster Quota

Support for NetApp ONTAP Versions

This release of Connector Pack supports NetApp FAS (Clustered Data ONTAP) - Data-ONTAP 9.4 and Netapp AFF (ALL Flash FAS ONTAP) - Data-ONTAP 9.4.

Open Bugs

All open bugs for this release are available in the Cisco Bug Search Tool.

Bug ID

Headline

CSCvk63679

Create LIF task is not loading the protocol type when the SVM is selected in the user input.

CSCvi84102

Create,Delete,Abort,Release,Restore & Update Sanpvault API are missing in Netapp 7 Mode.

CSCvk03364

Options are not displayed properly - Organization-PhyscialSources - Localised setup.

CSCvk20052

Create Routing group route from SVM report through action is failing.

CSCvk21803

Volumes report is not getting updated after Move and Create Multi snapshots actions on volumes.

CSCvk42984

Some Special characters are not allowed in task names.

CSCvk45257

Resize NFS Datastore operation failed when we have multiple C mode accounts in different pods.

CSCvk63676

Modify LIF config task is not working as expected.

CSCvk70548

In Volume Resize operation current volume size is not shown correctly.

CSCvk72389

Netapp reports are showing empty and inventory task getting deleted(intermittent).

CSCvk73409

Create NetApp cluster FCP Service task need to update the document.

CSCvm00839

Unable to map datastore identity from Associate NFS Export as Datastore to VMware-ProvisionablankVM.

Resolved Bugs

All resolved bugs for this release are available in the Cisco Bug Search Tool.

Bug ID

Headline

CSCvj19000

Error message should not be displayed if initiator is already part of initiator group.

CSCvk42939

LUN inventory should be triggered when we move Volume to offline state (Action).

CSCvk16088

Unable to select Destination volume in Create-Netapp Snapmirror relation task.

CSCvj37168

SVM inventory is not running in Netapp C-Mode.

CSCvj37109

Aggregate inventory is not running in NetAPP C-Mode

Communications, Services, and Additional Information

- To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.

- To get the business impact you’re looking for with the technologies that matter, visit Cisco Services.

- To submit a service request, visit Cisco Support.

- To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit Cisco Marketplace.

- To obtain general networking, training, and certification titles, visit Cisco Press.

- To find warranty information for a specific product or product family, access Cisco Warranty Finder.

Cisco Bug Search Tool

Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1721R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.