Ontap Upgrade 8.1.2 to 8.2P5. NFS License Database issue-Critical

by on ‎2014-01-30 01:28 PM
Labels:

We ran into this nasty issue while doing an Ontap Upgrade which lead to a downtime for us.

Ontap Upgrade from 8.1.2 to 8.2P5. Followed Upgrade Advisor and Software upgrade was done. Did a cftakeover and things looked good.

When we did a cfgiveback after 4-5 minutes once the Filer was ready for a giveback the process started and we started seeing..

exportfs [Line 9007]: NFS not licensed; local volume /vol/UAT_NFS1_persist/jqtree1 not exported

exportfs [Line 9008]: NFS not licensed; local volume /vol/UAT_NFS9_temp/qtree2 not exported

exportfs [Line 9009]: NFS not licensed; local volume /vol/UAT_NFS9_persist/qtree3 not exported

exportfs [Line 9010]: NFS not licensed; local volume /vol/UAT_NFS9_persist/tqtree4 not exported

Got error : 192 from export_add_entry

exportfs [Line 9011]: volume is offline, /vol/UAT_NFS11_temp/sqtree4 not exported

Got error : 192 from export_add_entry

exportfs [Line 9012]: volume is offline, /vol/UAT_NFS11_temp/qtree5 not exported

exportfs [Line 9014]: NFS not licensed; local volume /vol/UAT_VMDK17_swap not exported

exportfs [Line 9015]: NFS not licensed; local volume /vol/UAT_NFS7_persist/qtree6 not exported

exportfs [Line 9016]: NFS not licensed; local volume /vol/UAT_NFS7_temp/qtree7 not exported

exportfs [Line 9023]: NFS not licensed; local volume /vol/UAT_NFS7_temp/qtree8 not exported

Got error : 192 from export_add_entry

exportfs [Line 9024]: volume is offline, /vol/UAT_NFS11_persist/qtree9 not exported

and so on.. once it was up. we saw this.

filera> license

License database is not available at this time.

filera> license

License database is not available at this time.

filera> license

License database is not available at this time.

filera> license

License database is not available at this time.

filera> license show

License database is not available at this time.

Netapp Support was called up and  escalated. Comes out to be the License DB takes 2-5 minutes to come up and this can happen.

WORKAROUND

1.) priv set diag 

2.) registry set nfs.persistent.enable on

3.) check the setting nfs.persistent.enable with the following command:

     registry get nfs.persistent.enable

4.) Please confirm that the option is set to on

5.) If it is set to on, please continue with the upgrade


1 of 2 people found this article helpful.
Did you find this article helpful? Yes No
7 Comments (7 New)
Hide Comments
Comments
aborzenkov
on ‎2014-01-30 09:01 PM

Wow! You mean - 5 minutes after boot? Is it true for every boot or just one time event after update?

AMANSINGH13
on ‎2014-01-30 09:19 PM

Since its change in Licensing from 8.1.x to 8.2, its one time thing and that entry gets added automatically with upgrade. So 2-5 minutes is when you do cf giveback.

WillFulmer
on ‎2014-03-23 08:14 PM

Just experienced this myself.

One node was set to nfs.persistent.enable=off.


wnorthmtitsd
on ‎2014-04-21 08:01 AM

Since I see no nfs.persistent.enable  in 8.1 this is something that needs to be done after the takeover/giveback ??

thanks

JGPSHNTAP
on ‎2014-08-26 06:03 AM

Does this affect controllers that are already at 8.2.1 out of the box?

Amandeep
on ‎2017-03-30 10:18 AM

@wnorthmtitsdbefore upgrade

Amandeep
on ‎2017-03-30 10:19 AM

@JGPSHNTAP  out of box 8.2.1 are fine

Warning!

This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.

In accordance to our Code of Conduct and Community Terms of Use DO NOT post or attach the following:

  • Software files (compressed or uncompressed)
  • Files that require an End User License Agreement (EULA)
  • Confidential information
  • Personal data you do not want publicly available
  • Another’s personally identifiable information
  • Copyrighted materials without the permission of the copyright owner

Files and content that do not abide by the Community Terms of Use or Code of Conduct will be removed. Continued non-compliance may result in NetApp Community account restrictions or termination.