2012-05-21 08:45 AM
Recently upgrade a FAS6210 array to ONTAP 8.1 GA. Client has several volumes 16TB +, so this was a big need for them.
Aggregates are 64-bit so dedupe limitation for this platform is 70 TB (max volume size).
When I go to enable deduplication on any of these volumes (and even some that are much smaller), I receive the message "Operation Not Configured." This error occurs in both System Manager and the CLI.
I know that deduplication is no longer a "licensed feature" and is built into the ONTAP core, but is there an option someplace that I'm missing?
I have a case open that's awaiting escalation but reaching out everyone here as well
2012-05-24 10:39 PM
I ran into this error as well using the DataOnTAP PowerShell cmdlets. I was attempting to set the SIS settings before enabling SIS on the volume. Now, the command I run is this:
get-NaVol x | enable-NaSIS | Set-NaSIS -schedule auto | Start-NaSIS
Hope that helps.
2012-05-25 08:40 AM
Thanks for the input. Unfortunately, I get the same error as I've been getting all along...
PS C:\WINDOWS\system32\WindowsPowerShell> get-NaVol vol_atldata02_litigation_rep | enable-NaSIS | Set-NaSIS -schedule auto | Start-NaSIS
Enable-NaSis : Operation is not configured
At line:1 char:54
+ get-NaVol vol_atldata02_litigation_rep | enable-NaSIS <<<< | Set-NaSIS -schedule aut
o | Start-NaSIS
+ CategoryInfo : InvalidOperation: (10.101.252.80:NaController) [Enable-N
+ FullyQualifiedErrorId : SisEnableFailed,DataONTAP.PowerShell.SDK.Cmdlets.Sis.Ena
2012-06-06 01:25 PM
thanks for the suggestion, but this did not work for me.
I've had a case open with NetApp support since the issue started and still have no resolution. I have a feeling this one may go to the ONTAP team.
We shall see.
2013-01-26 01:15 PM
just a guess, I think SIS needs a nearstore license to work?
Have you tried to enable nearstore feature if it's "off" at the moment? >options licensed_feature.nearstore_option.enable
2013-01-28 01:05 PM
Problem solved... a failover for the controller helped to restore the a-sis feature. Yes, Iwas lucky, since I have an HA configuration that allowed me to failover to the second node.
Anyway, NetApp is aware of this issue: http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=625801