Skip to main content

Verifying licenses on the replaced nodes

You must install new licenses for the replacement nodes if the impaired nodes were using ONTAP features that require a standard (node-locked) license. For features with standard licenses, each node in the cluster should have its own key for the feature.

About this task

Until you install license keys, features requiring standard licenses continue to be available to the replacement node. However, if the impaired node was the only node in the cluster with a license for the feature, no configuration changes to the feature are allowed. Also, using unlicensed features on the node might put you out of compliance with your license agreement, so you should install the replacement license key or keys on the replacement node as soon as possible.

The licenses keys must be in the 28-character format.

You have a 90-day grace period in which to install the license keys. After the grace period, all old licenses are invalidated. After a valid license key is installed, you have 24 hours to install all of the keys before the grace period ends.

Note
If all nodes at a site have been replaced, license keys must be installed on the replacement node or nodes prior to switchback.
  1. Identify the licenses on the node: license show

    Example

    The following example displays the information about licenses in the system:

    cluster_B::>  license show
             (system license show)

    Serial Number: 1-80-00050
    Owner: site1-01
    Package           Type       Description             Expiration
    -------          -------     -------------           -----------
    Base             license     Cluster Base License        -
    NFS              site        NFS License                 -
    CIFS             site        CIFS License                -
    iSCSI            site        iSCSI License               -  
    FCP              site        FCP License                 -
    FlexClone        site        FlexClone License           -

    6 entries were displayed.
  2. Verify that the licenses are good for the node after switchback: metrocluster check license show

    Example

    The following example displays the licenses that are good for the node:

    cluster_B::> metrocluster check license show

    Cluster           Check                             Result             
    -------           -------                           -------------       
    Cluster_B         negotiated-switchover-ready       not-applicable
    NFS               switchback-ready                  not-applicable    
    CIFS              job-schedules                     ok
    iSCSI             licenses                          ok
    FCP               periodic-check-enabled            ok


  3. If you need new license keys, obtain replacement license keys on the Lenovo Support Site in the My Support section under Software licenses.
    Note
    The new license keys that you require are automatically generated and sent to the email address on file. If you fail to receive the email with the license keys within 30 days, you should contact technical support.
  4. Install each license key: system license add -license-code license-key, license-key...
  5. Remove the old licenses, if desired:
    1. Check for unused licenses: license clean-up -unused -simulate
    2. If the list looks correct, remove the unused licenses: license clean-up -unused