ONTAP Discussions

Failed to add license on FAS3220 since license grace period active.

Steven_Huang
410 Views

Hi, here's a multi-path HA system with 2 FAS3220 (NetApp Release 8.2P4 7-Mode), both of them with permanent licenses.

 

Around half year ago, we replaced the malfunction controller (netapp2) with the controller without license (SN: aaaaaaaaaaaa) and active grace period.

Now we replace netapp2 again since grace period was expired and we can't access to the disks owned by it.

The new installed netapp2 with permanent licenses(SN: bbbbbbbbbbbb), but it shows warning below once we checking license.

 

Warning: License grace period active. Showing entries associated with the original system serial number

Original Serial Number: aaaaaaaaaaaa (1st replaced netapp2 without license)

Owner: Netapp2

No license are installed

 

We've check sysconfig, the serial number was updated as bbbbbbbbbbbb(2nd replaced netapp2 with licenses), netapp2 was ready for giveback and we did it.

Then we tried to add license "license add [License Key]" but failed since serial number is not belong to the node.

 

We totally have no clue about what to do next, any suggestions are welcome and appreciated🙂.

1 ACCEPTED SOLUTION

liu
317 Views

I hope this helps

This warning reports after the first correct license has been added and will repeat within that 24-hour window to warn that all licenses must be upgraded to the serial number.

I think you look   New Ontap License add issues warning: License update grace period validation active, with time limit of 24 hours - NetApp Knowledge Base

View solution in original post

2 REPLIES 2

liu
318 Views

I hope this helps

This warning reports after the first correct license has been added and will repeat within that 24-hour window to warn that all licenses must be upgraded to the serial number.

I think you look   New Ontap License add issues warning: License update grace period validation active, with time limit of 24 hours - NetApp Knowledge Base

Steven_Huang
257 Views

Hi liu,

Thanks for your advice.

We've verify the correct license access key and add it successfully, now the system is working normally.

Public