Monday, March 30, 2015

Adding Disks to the Aggregate / Expanding the Aggregate

EXPANDING THE AGGREGATE / ADDING THE DISKS TO AGGREGATE

To add the disks to the aggregate, verify the UN-assigned disks first using below command.

Filer> disk show -n
  DISK       OWNER                  POOL   SERIAL NUMBER
------------ -------------          -----  -------------
3c.03.16     Not Owned              NONE   6SL9229GNK
3c.03.22     Not Owned              NONE   6SLN5261G8L
3c.03.8      Not Owned              NONE   6SL0N5261A3Q
3c.03.23     Not Owned              NONE   6SR7260000N03E
3c.03.9      Not Owned              NONE   6SL9260UVL
3c.03.20     Not Owned              NONE   6SLN5260YN3
3c.03.13     Not Owned              NONE   6SL9T9P1CC6
3c.03.19     Not Owned              NONE   6SL20000N5260QUY
3c.03.15     Not Owned              NONE   6SL9TBNG0YKA

Then Assign the disks to a pool using below command

Filer> disk assign  3c.03.16 3c.03.23
Mon Mar 30 21:58:21 PDT [Filer: diskown.changingOwner:info]: changing ownership for disk 3c.03.16 (S/N 6SL9R52N5219B9) from unowned (ID -1) to Filer (ID 15749567)
 Mon Mar 30 21:58:21 PDT [Filer: diskown.changingOwner:info]: changing ownership for disk 3c.03.23 (S/N 6SL9RN2619B9) from unowned (ID -1) to Filer (ID 15749567)

then verify the spare disks using below command

Filer>aggr status -s

before adding disks to the aggregate run below command 

Filer> df -Ah
then Add the spare disks to Aggregate

Filer> aggr add AGGR0 -d  3c.03.16 3c.03.23

Then verify the Aggregate space using 
Filer> df -Ah

Now you can able to see the Aggregate space is increased.

After completion of adding the disks to the aggregate you have to do re-allocation process for all the volumes which will spread the spindles across the aggregate, so you will get good performance.

Filer>reallocate start -o -p -f /vol/vol_name


Thursday, March 5, 2015

Updating DATA ONTAP Version

http://netappnotesark.blogspot.in/2015/08/index_12.html


You need to have a Administrator access to the filer,

Before upgrading Data ONTAP, monitor CPU and disk utilization for 30 seconds by entering
the following command at the console of each storage controller:
sysstat -c 10 -x 3

The values in the CPU and Disk Utilization columns are strongly recommended not to exceed 50%
for all ten measurements reported. Ensure that no additional load is added to the storage
system until the upgrade completes.

Ensure all SnapDrive for Windows clients are running one of the supported versions.

Download the DATA ONTAP version from http://mysupport.netapp.com/NOW/cgi-bin/software/ and select your Netapp filer Model click on Go!

 NOTE : If you are performing a Data ONTAP NDU (or backout), you must perform this
step on both nodes before performing the takeover and giveback steps.

Filer1> options autosupport.doit "Starting_Update ONTAP Version"

 Backup /etc/hosts and /etc/rc files from Netapp filer before upgrading.

copy the system image file to the /etc/software directory on the node, from windows/Linux box as administrator.

Filer1> software update 814P1_q_image.zip -r

  OR

Filer1> software update 814P7_q_image.exe -r

Filer1> cifs terminate

CIFS local server is shutting down...

CIFS local server has shut down...

Filer1>  cf disable
Filer1>  cf status
Cluster disabled.

Filer1> snapmirror off
Filer1> reboot

Now Login using your RLM (Remote LAN Management).

login as: naroot
naroot@192.168.1.2's password:
RLM Filer1> system console

It will show you the status. If it structured yet  LOAD_ONTAP> 

LOAD_ONTAP> boot_ontap

it will ask you for the boot menu. 

enter 1 for normal boot

LOAD_ONTAP>1

Data ONTAP (Filer1)
login:
Data ONTAP (Filer1)
login: root
Password:
Filer1> version (it should show new version)
Filer1> cf enable
Filer1> cifs stat
Filer1> cifs restart
Filer1> snapmirror resume <your destination here>
Filer1> options autosupport.doit "Finised_Upgradation <Version>"

YOUR DATA ONTAP Version is successfully upgraded to New version. 

THANKS.......