Re: Clone cluster

June 7, 2018, 12:58 pm

≫ Next: Re: New TR Released: TR-4690 - Oracle Databases on ONTAP Select

≪ Previous: Re: Service Processor Card Security - TLS

$

0

0

Hi

 

i have not tested it. and i see no one replied yet - so i'll just share my approach to the task

 

I think that to be more version and platform compatible friendly, allow changes & re-deploy later in time and to document better the environment  . woulden't it be much nicer to just have a file with all the commands required for the configurations? i was thinking shell commands. but if you already have the configuration  you can use scripts to export and re-import certain configuration. here's a good examples:

https://github.com/DatacenterDudes/cDOT-CIFS-share-backup-restore

 

 

If you want to go one step further. (and i didin't try it) configuration management such ansible do it in more structured way and can maybe help you manage the rest of your environment (servers, computers) to be consistent. i think also on personal level - experience with Ansible is a big requirements today in the job market.

https://www.youtube.com/watch?v=pUwIXeQ3ofM

https://netapp.io/2018/05/05/ansible-support-receives-massively-expanded-ontap-modules/

 

Gidi

---

Re: New TR Released: TR-4690 - Oracle Databases on ONTAP Select

June 7, 2018, 2:13 pm

≫ Next: Re: Service Processor Card Security - TLS

≪ Previous: Re: Clone cluster

$

0

0

 

 

Hari -

 

Again - Thank you !

 

Given that I'm the lead instructor teaching our new Integrating Hybrid Cloud with the Data Fabric course, this is more great stuff to reference !

See also: https://www.fastlaneus.com/course/netapp-inthcdf

 

I hope this response has been helpful to you.

At your service,

Eugene E. Kashpureff, Sr.
Independent NetApp Consultant http://www.linkedin.com/in/eugenekashpureff
Senior NetApp Instructor, Fast Lane US http://www.fastlaneus.com/
(P.S. I appreciate 'kudos' on any helpful posts.)

Re: Service Processor Card Security - TLS

June 8, 2018, 12:53 am

≫ Next: Support date passed 2038.

≪ Previous: Re: New TR Released: TR-4690 - Oracle Databases on ONTAP Select

$

0

0

The current status is that there is no Ontap or SP firmware release avilable that will result in the SP card using TLS.1.2 only. The best you can achieve is TLS1.1 & 1.2. We asked NETAPP recently if a fix was pending and we are anticipating a reply shortly. I will post on here once I have an update. 

Support date passed 2038.

June 8, 2018, 5:44 am

≫ Next: Re: Reporting Nodes Added Automatically When Moving iSCSI-Based Volumes?

≪ Previous: Re: Service Processor Card Security - TLS

$

0

0

Hello,

 

We are a software company that allows our customers to store data on netApp. We have code that writes out files onto netAPP with retention period. We recently hit the issue of not being able to set retention passed 2038. We were testing against netApp 8.2. Intrestingly enough when a retention date passed 2038 was passed to netapp, and the file made read only, it automatically wraps it around. That behavior has been changed in 9.3, where it does not allow us to use date beyond 2038. So my questions are the following:

 

1. Should my code explicitly map date greater thatn 2038 to dates between 1970 and 2003?

2. Is the difference I mentioned between 8.2 and 9.3 correct?

3. If we have a customer that would like to retain files passed 2071, how do we do that?

 

 

Thank you for taking the time to read this and I await your response

 

Kaleb

Re: Reporting Nodes Added Automatically When Moving iSCSI-Based Volumes?

June 8, 2018, 6:44 am

≫ Next: Re: Host Utilities Kit 7.0 needed with MPIO DSM 4.1p1?

≪ Previous: Support date passed 2038.

$

0

0

This is the new behavior. As Volumes and LUNs are moved from their original location to a new one, the reporting nodes are updated to include the new HA-Pair to prevent an outage. Once the new locataion is settled it's recommended to remove the previous reporting nodes unless you still wish them to be reported during any ALUA query.

Re: Host Utilities Kit 7.0 needed with MPIO DSM 4.1p1?

June 8, 2018, 1:51 pm

≫ Next: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

≪ Previous: Re: Reporting Nodes Added Automatically When Moving iSCSI-Based Volumes?

$

0

0

Yeah the HUK 7.0 and 7.1 work fine.  They work with MPIO no prob and have a decent san_version utility.  The settings are set correctly.  Wish they'd bring back the DSM / Plugin for Windows compmgmt.   

schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

June 9, 2018, 4:19 am

≫ Next: Re: Access systemshell in 7 mode

≪ Previous: Re: Host Utilities Kit 7.0 needed with MPIO DSM 4.1p1?

$

0

0

Hello team,

 

 

 

Is it okay to schedule anything in systemshell crontab in NetApp ( 7 Mode :8.2.4P6)

 

I want to disable scan on a paritcular share at a fixed time daily

 

 

cifs shares change xyz -novscan (to be done at 16:00)

cifs shares change xyz -vscan (to be done at 16:30)

 

 

https://kb.netapp.com/app/answers/answer_view/a_id/1033705

 

 

 

 

Thanks in advance!

Re: Access systemshell in 7 mode

June 9, 2018, 4:16 am

≫ Next: Copy data to Snowball

≪ Previous: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

$

0

0

I got the answer: in KB :

 

https://kb.netapp.com/app/answers/answer_view/a_id/1033705

 

To enable the diag user in 7-Mode:

By default, the diag user is locked, and does not have a password.

View the current state of the diag user in 7-Mode by running the following command:

nqa-f3050-5> priv set advanced
nqa-f3050-5*> useradmin diaguser show
Name: diag
Info: Account for access to systemshell
Locked: yes

Perform the following steps to enable the diag user in 7-Mode:

nqa-f3050-5*> useradmin diaguser unlock

nqa-f3050-5*> useradmin diaguser show
Name: diag
Info: Account for access to systemshell
Locked: no

1. Provide a password to the diag user:
   nqa-f3050-5*> useradmin diaguser password
The password must be at least 8 characters long.
Please enter a new password:
Please enter it again:
   Now you can access the OS using the diag user account:
   nqa-f3050-5> priv set advanced
nqa-f3050-5*> systemshell

Data ONTAP/i386 (nqa-f3050-5) (ttyp0)
login: diag
Password:
%pwd
/var/home/diag
2. Run the exit command to return to the standard Data ONTAP 8 shell

---

Copy data to Snowball

June 10, 2018, 5:21 pm

≫ Next: Re: Copy data to Snowball

≪ Previous: Re: Access systemshell in 7 mode

$

0

0

Hello

I am trying to copy data from my Netapp to my windows. Would anyone know the correct commands to perform this action? My company is moving to the cloud so I'm trying to migrate everything to the snowball. Any suggestions on this would be greatly appreciated. If there is any documentation please send it to amagee@bluecanopy.com. Thanks!!

Re: Copy data to Snowball

June 10, 2018, 8:25 pm

≫ Next: Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

≪ Previous: Copy data to Snowball

$

0

0

Hi there,

 

Going to need a lot more information to help with this - what protocols, applications, operating systems, versions, and what is the expected functionality/how do you plan to use it once it comes off snowball into AWS?

Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

June 11, 2018, 12:51 am

≫ Next: FAS 2020 Config Questions

≪ Previous: Re: Copy data to Snowball

$

0

0

The shell is for NetApp engineering only. it's unsupported to do any operation under this shell without engineering approving or documenting it

From the article you linked to "is only to be used for diagnosing issues that are not resolvable using the filer shell.".

 

You should schedule this cron ob/sched job from a remote server to run the command via ssh, or via one of the other interfaces or SDK.

 

Gidi

 

FAS 2020 Config Questions

June 11, 2018, 1:36 am

≫ Next: Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

≪ Previous: Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

$

0

0

Gents

I have done a factory reset on my FAS 2020 old system and after that i have lost my FC and ISCSI licences.

 

Please advise is there anyway i can use this system ?

 

 

Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

June 11, 2018, 3:21 am

≫ Next: filesys-size-fixed changed

≪ Previous: FAS 2020 Config Questions

$

0

0

Okay. Thanks for the reply GidonMarcus

 

Can we use NetApp Workflow Automation for this.

 

My purpose is only to run a particular command at a fixed time..

filesys-size-fixed changed

June 11, 2018, 11:42 am

≫ Next: Re: FAS 2020 Config Questions

≪ Previous: Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

$

0

0

I have several volumes on a cluster that I changed to filesys-size-fixed false.    1 week later the autosupport shows that they are set back to true.  I found this because a volume became full because it was unable to autogrow.   

 

None of these volumes were ever the destination of a snapmirror.    the filer in question is running ontap 9.2p1 and is now part of a 4 node cluster. What are the possible causes of this setting being chnaged to true?  

Re: FAS 2020 Config Questions

June 11, 2018, 6:51 pm

≫ Next: Re: Can I transition Volume level DR -> SVM DR?

≪ Previous: filesys-size-fixed changed

$

0

0

Er, not really. 

 

If you are the original purchasor, you may be able to recover them by contacting our support center, but they are non-transferrable, so if you aren't, you won't be able to.

 

If you recover the license codes, it doesn't matter which license goes on which controller - that era of licenses are not locked to a specific serial number.

 

 

---

Re: Can I transition Volume level DR -> SVM DR?

June 11, 2018, 8:31 pm

≫ Next: Re: Support date passed 2038.

≪ Previous: Re: FAS 2020 Config Questions

$

0

0

Sorry to re-open this topic.

 

Has anyone experienced the issue in 9.3P3 or above ?

 

Seems from 9.3 the default DP replaced by XDP.  and i keep getting error message "Error: command failed: There are one or more volumes in this Vserver which do not have a volume-level SnapMirror relationship with volumes in Vserver "soure"."

 

 

snapmirror create -source-path soure: -destination-path dest: -type DP -throttle unlimited -policy DPDefault -schedule daily -identity-preserve true

vserver stop dest

 

snapmirror resync dest:

Error: command failed: There are one or more volumes in this Vserver which do not have a volume-level SnapMirror relationship with volumes in Vserver "soure".

 

 

 

Re: Support date passed 2038.

June 12, 2018, 2:27 am

≫ Next: Getting rid of old root disks...

≪ Previous: Re: Can I transition Volume level DR -> SVM DR?

$

0

0

Hi there,

 

I'm not sure of your familiarity, but this is going to be a problem with many unix based systems. Low precision time is a 32bit signed integer of the number of seconds since Jan 1, 1970. The date you've found in 2038 is the maximum value of this - https://en.wikipedia.org/wiki/Year_2038_problem

 

We are tracking this issue holistically, and have a number of BURTs open, including several specifically around snaplock and post 2038 dates, but there are also required compatibilities on client systems and NFS for full implementation. At this point we are aiming for support for dates to 2106, but under the advice in our now-archived TR-3738, a 2071 date was also mentioned. 

 

Because of the in-depth analysis required, the somewhat esoteric nature of this request, and the potential risks, I suggest opening a support case is probably the best way to obtain clear guidance here.

 

Sorry I can't be of more assistance.

Getting rid of old root disks...

June 12, 2018, 5:20 am

≫ Next: Re: Getting rid of old root disks...

≪ Previous: Re: Support date passed 2038.

$

0

0

I want to repurpose disks earlier used in a cluster. The disks are added to the cluster and are visible/appearing as unassigned disks. During the assignment of the disks to a node of the cluster, 6 disks are identified as being the old root-disks. Is there a way to get rid of the data on those disks.

 

netapp01::*> storage disk show -disk 3.*.*
Usable Disk Container Container
Disk Size Shelf Bay Type Type Name Owner
---------------- ---------- ----- --- ------- ----------- --------- --------
....
3.41.0 - 41 0 FSAS unassigned - -
3.41.1 - 41 1 FSAS unassigned - -

....

 

netapp01::*> storage disk assign -disk 3.41.0 -owner netapp01-07

 

After changing the ownership of the disk, the disk is identified not being a spare.

 

netapp01::*> storage disk show -disk 3.*.*
Usable Disk Container Container
Disk Size Shelf Bay Type Type Name Owner
---------------- ---------- ----- --- ------- ----------- --------- --------
...
3.41.0 3.63TB 41 0 FSAS aggregate n05root netapp01-07
3.41.1 - 41 1 FSAS unassigned - -

...

 

Is there a way to revert the disk as being a spare? I know it could be done by using maintenance mode. But then I have to reboot the node and as this is production I would like to find out if there are other ways.

 

 

Re: Getting rid of old root disks...

June 12, 2018, 5:40 am

≫ Next: Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

≪ Previous: Getting rid of old root disks...

$

0

0

Hi

 

have you seen this KB ? https://kb.netapp.com/app/answers/answer_view/a_id/1030491

the process got much simplified recently and not require loading to maint anymore (also for old versions)

 

G

Re: schedule vscan disable on particular cifs in NetApp 7-mode systemshell crontab

June 12, 2018, 5:47 am

≫ Next: Re: Getting rid of old root disks...

≪ Previous: Re: Getting rid of old root disks...

$

0

0

Hi

 

WFA don't have a scheduler. but you can trigger a wrokflow via restAPI call  to WFA, so you still need external scheduler.

if it was a system i maintain. i would have set dedicated local user on the 7-mode with right only to run the command you need and schedule the command run externaly

 

another question, why do you want to disable VSCAN? if there's some workload you don't want to get scan you can create a dedicated share for it (also for the same volume/qtree) and set it to -novscan.

 

G