The below requirements are needed on the host that executes this module.
- A physical or virtual clustered Data ONTAP system. The modules support Data ONTAP 9.1 and onward
- Ansible 2.6
- Python2 netapp-lib (2017.10.30) or later. Install using ‘pip install netapp-lib’
- Python3 netapp-lib (2018.11.13) or later. Install using ‘pip install netapp-lib’
- To enable http on the cluster you must run the following commands ‘set -privilege advanced;’ ‘system services web modify -http-enabled true;’
| Parameter | Choices/Defaults | Comments | |
|---|---|---|---|
| hostname string / required | |||
| http_port | Override the default port (80 or 443) with this port | ||
| https boolean |
| Enable and disable https | |
| license_codes - | |||
| license_names | List of license-names to delete. | ||
| base - | |||
| cdmi | CDMI License | ||
| cifs - | |||
| fcp | FCP License | ||
| flexclone - | |||
| iscsi | iSCSI License | ||
| nfs - | |||
| snaplock | SnapLock License | ||
| snapmanagersuite - | |||
| snapmirror | SnapMirror License | ||
| snapprotectapps - | |||
| snaprestore | SnapRestore License | ||
| snapvault - | |||
| v_storageattach | Virtual Attached Storage License | ||
| ontapi integer | |||
| password | Password for the specified user. | ||
| remove_expired |
| Remove licenses that have expired in the cluster. | |
| remove_unused boolean |
| Remove licenses that have no controller affiliation in the cluster. | |
| serial_number - | Serial number of the node associated with the license. This parameter is used primarily when removing license for a specific service. | ||
| state - |
| Whether the specified license should exist or not. | |
| use_rest string |
| REST API if supported by the target system for all the resources and attributes the module requires. Otherwise will revert to ZAPI. Never -- will always use the ZAPI | |
| username | This can be a Cluster-scoped or SVM-scoped account, depending on whether a Cluster-level or SVM-level API is required. For more information, please read the documentation https://mysupport.netapp.com/NOW/download/software/nmsdk/9.4/. | ||
| validate_certs |
| If set to no, the SSL certificates will not be validated.This should only set to False used on personally controlled sites using self-signed certificates. | |
. Search – Search by serial number. Also includes recent serial number searches. Profile – Place to update your personal details including location, phone number, and other information. Please note, while the skill is displayed, you cannot update this field. Please speak to your manager to make any changes. NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein.
- Licenses for the non-ESX build (Serial Number ) Use these licenses with the VMware Workstation, VMware Player, and VMware Fusion build. Feature License Code Description.
- NetApp Software Products and License Keys are available for immediate download. Please refer to the 'Access Key' and 'Sales Order #' as part of the documentation included in the actual shipment.
Note
- The modules prefixed with na_ontap are built to support the ONTAP storage platform.
- This module is not guaranteed to have a backwards compatible interface. [preview]
- This module is maintained by an Ansible Partner. [certified]
Authors¶
- NetApp Ansible Team (@carchi8py) <ng-ansibleteam@netapp.com>
Hint
If you notice any issues in this documentation, you can edit this document to improve it.
Answer
This article provides an overview of Data ONTAP 8.2 and 8.3 licensing, and provides links to additional, more detailed reference materials. This article covers the following topics:
- Data ONTAP 8.2 and 8.3 License Enforcement Model
- Data ONTAP 8.2 and 8.3 License Keys
- Situations that require new license keys
- Additional Resources
Data ONTAP 8.2 and 8.3 License Enforcement Model
License Serial Keygen
No license keys are required to enable Data ONTAP itself, but license keys are required to enable value-add features (such as protocols, SnapMirror, etc.). All license entitlements are sold per controller, for the life of the controller, and for the original 'sold to' customer. HA-pairs and clustered ONTAP implementations require uniform software entitlement on all the controllers (i.e., each controller must be entitled to use the features that are enabled in the pair or cluster).
The same license keys are used for both Data ONTAP 8.2 and 8.3 7-Mode and clustered Data ONTAP 8.2 and 8.3.
A Cluster Base Key is required to create a cluster, but value-add features are enabled by installing the controller-specific license keys within the cluster. It only takes a single license key to enable a feature across a cluster; however, it is a best practice to install all license keys for all nodes in the cluster to avoid any potential issues (e.g., appearing to be non-compliant with the ONTAP license terms). Also remember that NetApp's licensing policy requires that all the nodes in a cluster be entitled for any feature enabled within the cluster. This is called Uniform Software Entitlement.
Data ONTAP 8.2 and 8.3 License Keys
Data ONTAP 8.2 and 8.3 license keys are node-locked to the controller serial number for which they are purchased, and they will only work on that controller. Data ONTAP 8.2 and 8.3 license keys are 28 characters long, easily recognized when compared to Data ONTAP 8.1 license keys which are shorter.
Note: Node-locked license keys mean some situations might require new license keys. See the Situations that might require new license keys section.
If you require new license keys for a HW Replacement scenario (Controller or Motherboard replacements), contact CSS.
The Data ONTAP 8.2 and 8.3 Evaluation ('Eval') License Keys have explicit expiration dates. An Eval key is typically issued for a 90 day period. To extend a software evaluation after an Eval key expires, obtain and install a new Eval key. Work with a NetApp representative to obtain Eval license keys.
Situations that might require new license keys
Because of the changes in license key formats across Data ONTAP versions and modes, there are some situations where new license keys might be required. While NetApp is working to make license key generation self-service as soon as possible, current policies require a valid support case to provide new license keys for Data ONTAP versions other than the version originally purchased.
Three points to remember:
- Any clean installation of Data ONTAP requires version-appropriate license keys for the Data ONTAP version and mode being deployed
- New license keys are not required to upgrade from Data ONTAP 8.1 to Data ONTAP 8.2 or 8.3, unless point # 1 applies.
- Data ONTAP 8.2 and 8.3 node-locked license keys must be changed if a controller serial number change is detected.
For Data ONTAP 8.2 and 8.3 7-mode HA-Pairs that experience a failover, Data ONTAP will automatically enable a 90 day grace period on any replacement controller (when installed) for all the features licensed on the failed controller. A Software Entitlement Transfer (from the old controller to the new controller) must be completed with Support Services in order to obtain new license keys. The new license keys must be installed before the 90 day grace period expires.
To understand if a specific scenario requires new license keys or not, see KB: When should Data ONTAP License Keys be replaced?
Additional Information
Related Links:
Keygen
Netapp License Keygen App
- NetApp University Course: What’s New in Data ONTAP 8.2 Licensing
- NetApp University Course: ONTAP License Key Replacement Scenarios
- NetApp University Course: Technical Overview of Licensing in Data ONTAP 8.2