In my line of work I get to play with a lot of NetApp FASs running Ontap from versions 8 up to 9.7. In that time I have complied a handy little list of console commands that I use often.
The following commands are mainly used when setting up (or re-purposing) aFAS (or AFF)
Configure config backup to FTP server
set -privilege advanced
system configuration backup settings modify -destination ftp://[FTP-IP] -username NETAPP
system configuration backup settings set-password
set -privilege admin
Manually run that config backup to FTP server
system configuration backup create -node [nodename] -backup-name [backup-name] -backup-type cluster
--- wait a couple on minutes ---
system configuration backup upload -node [nodename] -backup [backup-name].7z -destination ftp://[FTP-IP]
Change ownership of disks
Very handy if you want maximumise storage. Good luck finding this info out on the internet if you are not sure how to word the question.
set -privilege advanced
storage disk show
storage disk assign -force -data1 -owner [target-node] -disk [id]
storage disk assign -force -data2 -owner [target-node] -disk [id]
or
storage disk assign -force -owner [target-node] -disk [id]
set -privilege admin
Move cluster LIF to e0M port
Not best practice but I have been asked to do that in the past.
Network interface show
Network interface modify -vserver [cluster] -lif [lifname] -home-node <e0M> -home-port <e0M>
Create Service Processor
Configuring up the Service Processors is one of the the first things you should do.
system node service-processor network modify -node [node] -address-type IPv4 -enable true -ip-address [IP] -netmask [Mask] -gateway [Gateway]
Configure email alerting
event config modify -mail-server smtp.work.net -mail-from [fasname]@work.net
event notification destination create -name storage-alerts -email fas@work.net
event notification create -filter-name important-events -destinations storage-alerts
Increase inodes
If you have ever got an out of space error on a CIFs volume when you have plenty of space. Its iNodes you have really run out of.
I was advised by NetApp to keep adding 5 or 10% to the iNode maximum. When I asked why should I just not set it to something stupidly high I was told no, but one at NetApp seemed to know why.
volume show –vserver <vserver name> -volume <volume name> -fields files
volume modify –vserver <vserver name> -volume <volume name> -files <number of files>
re-ip node / cluster mgt
Handy when quickly re-purposing or moving a SAN. Needles to say (type) its best done from the service processor.
set -privilege advanced
network interface modify -vserver [vserver] -lif [LIFNAME] -home-node [HOMENODE] -home-port [PortName] -address [IPADDRESS] -netmask [NETMASK]
set -privilege admin
Change Default Gateway
Handy when quickly re-purposing or moving a SAN. Needles to say (type) its best done from the service processor.
route create -vserver [vserver] -destination 0.0.0.0/0 -gateway [GW]
route delete -vserver [vserver] -destination 0.0.0.0/0 -gateway [GW]
Rename lif
network interface rename -vserver [vServer] -lif [lif] -newname [new lif name]
Firewall
Did you know OnTap has a firewall? I didn’t for a very frustrating couple of days. Sometimes it will set a data LIF to a firewall policy of mgt, you will need to change it to data.
network interface show
network interface show -lif [lif] -fields firewall-policy
network interface modify -lif [lif] -firewall-policy data -vserver [vserver]