Simulator Discussions

I can't use snaplock feature even I add the snaplock license

hongboy
3,929 Views

Simulator ver: 8.2.1RC1

license: VSIM Licenses: 8.2.1RC1 licenses 7-Mode

http://support.netapp.com/NOW/download/tools/simulator/ontap/8.2.1RC1/7Mode_licenses_8.2.1RC1.txt

Issue : After I add the VSIM Licenses [ 8.2.1RC1 licenses 7-Mode ] to DataOntap. I run the command “snaplock clock initialize”, but the error said requires a snaplock or snaplock enterprise license.

FilerF> license

Serial Number: 4082367-72-5

Owner: FilerF

Package Type    Description           Expiration

----------------- ------- --------------------- --------------------

NFS license NFS License           -

CIFS license CIFS License          -

iSCSI license iSCSI License         -

FCP license FCP License           -

FlexClone license FlexClone License     -

SnapVault license SnapVault License     -

SnapLock license SnapLock Compliance License -

SnapLock_Enterprise license SnapLock Enterprise License -

FilerF> snaplock clock initialize

Secure clock initialization requires a snaplock or snaplock enterprise license.

FilerF>

Could you please give some advice to me?

Best Regards

Hongbo

1 ACCEPTED SOLUTION

shatfield
3,929 Views

I think you missed a step:

vsim821custom> options licensed_feature.snaplock_enterprise.enable on

vsim821custom> date 0917

Sat Apr 19 09:17:00 PDT 2014

vsim821custom> Sat Apr 19 09:17:00 PDT [vsim821custom:telnet_0:info]: Time changed (via "date") to Sat Apr 19 09:17:00 PDT 2014

Sat Apr 19 09:17:00 PDT [vsim821custom:wafl.date.changed.notice:notice]: The date or time used by the system has changed. A discrepancy between system date or time and Snapshot copy schedule can result in missing or delayed scheduled Snapshot copies. 

vsim821custom> date

Sat Apr 19 09:17:08 PDT 2014

vsim821custom> snaplock clock initialize  

*** WARNING: YOU ARE INITIALIZING THE SECURE COMPLIANCE CLOCK ***

You are about to initialize the secure Compliance Clock of this

system to the current value of the system clock. This procedure

can be performed ONLY ONCE on this system so you should ensure

that the system time is set correctly before proceeding.

The current local system time is: Sat Apr 19 09:17:14 PDT 2014

Is the current local system time correct? y

Are you REALLY sure you want initialize the Compliance Clock? y

vsim821custom> Sat Apr 19 09:17:23 PDT [vsim821custom:snaplock.sys.compclock.set:info]: The compliance clock time of the system has been set to 'Sat Apr 19 09:17:14 PDT 2014' due to the reason 'initialized by administrator'.

View solution in original post

4 REPLIES 4

SANJESHUF
3,929 Views

As per my knowledge SnapLock is not supported in any Data ONTAP 8.0.x release. So even if you have license you cant use the feature .

hongboy
3,929 Views

Thank you verymuch

shatfield
3,930 Views

I think you missed a step:

vsim821custom> options licensed_feature.snaplock_enterprise.enable on

vsim821custom> date 0917

Sat Apr 19 09:17:00 PDT 2014

vsim821custom> Sat Apr 19 09:17:00 PDT [vsim821custom:telnet_0:info]: Time changed (via "date") to Sat Apr 19 09:17:00 PDT 2014

Sat Apr 19 09:17:00 PDT [vsim821custom:wafl.date.changed.notice:notice]: The date or time used by the system has changed. A discrepancy between system date or time and Snapshot copy schedule can result in missing or delayed scheduled Snapshot copies. 

vsim821custom> date

Sat Apr 19 09:17:08 PDT 2014

vsim821custom> snaplock clock initialize  

*** WARNING: YOU ARE INITIALIZING THE SECURE COMPLIANCE CLOCK ***

You are about to initialize the secure Compliance Clock of this

system to the current value of the system clock. This procedure

can be performed ONLY ONCE on this system so you should ensure

that the system time is set correctly before proceeding.

The current local system time is: Sat Apr 19 09:17:14 PDT 2014

Is the current local system time correct? y

Are you REALLY sure you want initialize the Compliance Clock? y

vsim821custom> Sat Apr 19 09:17:23 PDT [vsim821custom:snaplock.sys.compclock.set:info]: The compliance clock time of the system has been set to 'Sat Apr 19 09:17:14 PDT 2014' due to the reason 'initialized by administrator'.

hongboy
3,929 Views

Thank you verymuch.

Now I can use it.

filerE> license add EXGDWMLWOZNBBGABGAAAAAAAAAAA

license add: successfully added license key "EXGDWMLWOZNBBGABGAAAAAAAAAAA".

filerE> options licensed_feature.snaplock_enterprise.enable on

filerE> snaplock clock initialize

*** WARNING: YOU ARE INITIALIZING THE SECURE COMPLIANCE CLOCK ***

You are about to initialize the secure Compliance Clock of this

system to the current value of the system clock. This procedure

can be performed ONLY ONCE on this system so you should ensure

that the system time is set correctly before proceeding.

The current local system time is: Mon Apr 21 10:02:26 GMT 2014

Is the current local system time correct?

Public