Network Appliance

Upgrading NetApp ONTAP 8.0.1 P7 to 8.1.2 P4

2015-08-18T04:22:00.000-07:00

1 Introduction

1.1 Overview

This document explains the step by step process of Data ONTAP 8.0.1 P7 to 8.1.2 P4 upgrade method for active/ active Configuration.
This non-disruptive active/active upgrade procedure ensures high storage system availability
This process is very important in the present environment where we don’t have any downtime available.

1.2 Purpose

This document explains the step by step process of Data ONTAP 8.0.1 P7 to 8.1.2 P4 upgrade method for active/ active Configuration.
This non-disruptive active/active upgrade procedure ensures high storage system availability.

2. Procedure & Prerequisite

1. Check if the FAS series supports the DATA ONTAP version.

2. Use Upgrade Advisor to understand the requirements for the upgrade and to generate an
upgrade plan.

3. Check compatibility in the NetApp Interoperability Matrix (IMT) tool.

4. If SnapMirror is being used, check the Data ONTAP version on destination storage system. The
destination storage system should have the same or higher version of DATA ONTAP.

5. Check if there is Raid4 aggregate, upgrade will disruptive for respective aggregate.

6. Check if the volumes have at least 1 MB of free space to accommodate the changes(inode changes).

7. Check for any failed disk and replace them before the activity and make sure there is no hardware error.

8. Make sure you have connectivity to SP direct serial connection while planning the activity.

9. If you use de-duplication technology, ensure that your system includes no more than 100 deduplicated volumes and that no de-duplication operations are active during the Data ONTAP
Upgrade.

10. Make sure that there is no SnapMirror sessions running/active or scheduled to run during the
activity.

11. CIFS needs downtime while upgrade.

12. Check the disk firmware

Firmware will be update in the background so that clients are not impacted by the firmware update process. if we enabled the below command

> options raid.background_disk_fw_update.enable on

Paste the proper disk firmware in /etc/disk_fw/ , later it will update.

Refer this link for more information:

http://support.netapp.com/NOW/download/tools/diskfw/

13. Check the disk shelves’ firmware

Paste the proper disk shelf firmware in /etc/shelf_fw / and if its FC disk shelf paste the ACP firmware in /etc/acpp_fw/, else no need of ACP firmware.

> set mode priv advanced
*> storage download shelf
*> storage download ACP

Refer this link for more information:

http://support.netapp.com/NOW/download/tools/diskshelf/

14. To disable automatic giveback for activity in active/active (if enabled)

> options cf.giveback.auto.enable off

Because in this activity, first filer B will be upgraded to 8.1.2 P4 but Partner filer A should be old version 8.0.1 P7, so that cf giveback won't work.

3. Pro Ensure that you have checked the following before you perform the upgrade:

Step 1: Make a back up /etc/rc and /etc/hosts

Backup /etc/rc and /etc/hosts files on both nodes.
Capture output of fcadmin config command.

Step 2: Software Download

Log in to the support.netapp.com site. Select Download tab
Select Software Download
Go to Products, Data ONTAP and select the Filer type (Ex: FAS****) Select Go,
http://mysupport.netapp.com/NOW/cgi-bin/software/

Select the Data ONTAP 7.3.2 and Download it desktop or laptop
If you don’t find the Specific version 7.3.2 in the list of software’s.
In the below software list we have options to Select To access a specific software

To download...	Click...
Data ONTAP 8.1.2
Data ONTAP 8.1.2P4

Step 3: Copy Software onto the filer

Get access to share vol0 in cifs.
Open the share in windows and copy the Data ONTAP 8.1.2p4 in /etc/software directory.
Unzip the software file in the share.

Step 4: Install 7.3.2 system file on both the filers.

Filer1> software install filer_name

Step 5: Verify primary kernel is at 7.3.2

Filer1> version -b
Filer2> version -b

Once download is completed you need to reboot the filers to use the new ONTAP.

Step 6: Takeover Process by Filer 1

From filer1, enter the following commands:

Filer1> cf takeover

Now filerB started reboot.
While booting press Ctrl+c to LOADER prompt and update the motherboard firmware.

LOADER> update_flash
LOADER> bye

Step 7: Giveback Process

Filer1> cf giveback

while upgrade we need downtime for cifs only
After giveback is completed, verify Filer 2 is at ONTAP 8.1.2p4

Step 8: Complete maintenance checklist on Filer 2

Maintenance Checklist
Verify all Aggregates online

Filer 2> aggr status

Verify all volumes online

Filer 2> vol status

Verify CIFS is operational

Filer 2> cifs domaininfo

Filer 2> cifs sessions –t

Filer 2> cifs stat

Follow the same to upgrade steps for filer1

****************************THANK YOU*************************

Please write your valuable comments, about my blog-spot.

Checking Netapp filer after a panic

2014-09-17T03:20:00.000-07:00

Checking Netapp filer after a panic

If suppose filer suddenly rebooted due to some hardware issues, causing a failover in a clustered pair.
if you would like to check the filer hardware status before you perform a giveback
These steps won't affected the other node of the cluster..

Please follow the bellow steps..

Steps :

1. login as naroot with root passwd

2. Type system console

3. It prompt for halt : type y

4. Now system will reboot.

5. Now it will prompt with LOADER-A> , there type boot_ontap

6. If you got above image please press Ctrl-C

7. Next following by the boot menu options

8. Select maintance mode boot ( option 5 ) and please never select options 4.

9. Next you will a warning message like "Continue to boot?" there please select "Y"

After some time you will enter into maintenance mode prompt .
Prompt looks like " *> "
Type "aggr status" to check

Check FC disks are online/shown using fcadmin device_map command.
Check SAS disks are in online using this sasadmin command.
if you want check other commands if needed.

10. To Exit maintenance mode type "halt"

11. Again it prompt in LOADER-A> there type boot_ontap

12. we have to wait utill below message.

Now it will be disconnected from RLM connection.

Please write your valuable comments, about my blogspot.

Snapmirror Transfer Error

2014-01-29T22:54:00.003-08:00

Transfer aborted : cannot connect to source filer.

src> wrfile snapmirror.allow
1.1.1.1 # secondary filer ip
filer_name # secondary filer name
Press CTRL-C to exit and save the file

Now start initialize the snapmirror relation ship..

Note : This command will create file in this path \\filer_name\C$\etc\snapmirror.allow

Snapmirror primary configuration of VSM & QSM

Snapmirror Secondary configuration of VSM & QSM

Snapmirror schedule configuration

what is Netapp raid group and how its working..?

2013-07-04T03:56:00.001-07:00

These are type of disks in filler

DISK TYPE	RAID-DP	RAID4
ATA/BSAS/SATA Maximum	16	7
FC/SAS Maximum	28	14
ATA/BSAS/SATA Default	14	4
FC/SAS Default	16	7
ATA/BSAS/SATA Minimum	3	2
FC/SAS Minimum	3	2

Only Example for RAID DP:

> aggr creare aggr1 –t raid_dp –r 7 17

-t : for selecting raid type (raid4 or raid DP)

-r : for select (how many disk want to be in one raid group)

17 meant for : 17 disk for aggr1

Consider you are using SATA Disk with RAID DP,

In SATA Disk

16 disks is the maximum in one raid group,

7 disks is default in one raid group and

3 Disks is Minimum to create NETAPP Raid group.

This is the recommended in Netapp.

After this command executed 3 raid groups will be created cause we mentioned ( –r 7 in command)so it will take 7 disk for one raid group(rg).

17 disk - 7 disk = 10 disk -----> rg0
10 -7 = 3 -----> rg1

3- 3 = 0 -----> rg2 (here we having 3 balance disks its less than 7 disks, so it will calculate accordingly and create another raid group as rg2 with 3 disks, cause In RAID DP minimum is 3 disk )

Another example in RAID DP If balance disk is 3 disk means i will create another raid group that already i explained above, If suppose its less than 3 disks remains means, two disk or one disk, That balance disk will moved to spare disks.

Only Example for RAID4 :

> aggr creare aggr1 –t raid4 –r 5 16

-t : for selecting raid type (raid4 or raid DP)

-r : for select (how many disk want to be in one raid group)

16 meant for : 16 disk for aggr1

Consider you are using SATA Disk with RAID 4,

In SATA Disk

16 disks is the maximum in one raid group,

4 disks is default in one raid group and

2 Disks is Minimum to create NETAPP Raid group.

This is the recommended in Netapp.

After this command executed 3 raid groups will be created cause we mentioned ( –r 5 in command)so it will take 5 disk for one raid group(rg).

16 disk - 5 disk = 11 disk -----> rg0
11 -5 = 6 -----> rg1

6- 5 = 1 -----> rg2

Its less than 5 disks, so that balance 1 disk will moved to spare disks.

So in this example aggr1 having 15 disk..

If Any Question please feel free to ask...

32 bit aggregate to 64 bit aggregate Migration

2013-07-04T03:39:00.000-07:00

32 bit aggregate to 64 bit aggregate Migration

Data ONTAP 7-Mode 8.1 and later

Identify 32-bit aggregates and run a check to see if the volumes are sufficient:

filerA> priv set advanced
filerA*> aggr status

Perform the upgrade with add disks:

filerA> priv set advanced
filerA*> aggr status

filerA*> aggr add aggr1 -64bit-upgrade normal 12 ( 12 is number of disks)

Perform the upgrade with-out add disks::

filerA> priv set advanced
filerA*> aggr status

filerA*> aggr 64bit-upgrade status aggr1 -all

Another way to 32 to 64 bit

If there is any existing aggregate in 32bit.
just create one aggregate with 64 bit
Create one the Volume in the 64 bit aggregate.
Then migrate all the old volume to the new Volume through NDMP protocol.

Fas > aggr create aggr2 -b 64 15(No of disks)

Fas > aggr status aggr2

Fas > vol create vol2 aggr2 100g

Fas > ndmpd on

Fas > ndmpd –l 0 –f /vol/vol1 /vol/vol2

Please write your valuable comments, about my blogspot.

BMC - RLM - SP

2013-06-18T05:07:00.003-07:00

BMC - RLM - SP is console port to connect the filer,
BMC - RLM - SP is a separate device in the FAS chassis.
It has it's own IP and is independent of the FAS so it keeps running any time.
BMC - RLM - SP is connects to the motherboard and install separately.When a FAS fails over BMC - RLM - SP keeps working locally.
These provide remote support like remote access, monitoring and troubleshooting.

Before FAS 2xxx they called BMC

FAS 2xxx to FAS 30xx / 31xx they called RLM

After FAS 3240 and 3270 they named SP (service processor)

BMC : Baseboard Management Controller

RLM : Remote Lan Module

SP : Service Processor

RLM - Remote Lan Module

Please write your valuable comments, About this Blogspot.

CIFS Oplocks - Opportunistic Locks

2013-06-04T04:59:00.000-07:00

CIFS Oplocks - Opportunistic Locks

CIFS Oplocks

CIFS oplocks reduce network traffic and increase the storage performance.
Its working like caching of read-ahead, write-behind, and lock information.
you can enable/disable CIFS oplocks for the individual volume or qtree.
In the database application we should turn off the CIFS oplocks
when you handling critical data and can't afford the data loss.
Otherwise, you can on CIFS oplocks options.

Enabling/Disabling for entire storage

> cifs.oplocks.enable on
> cifs.oplocks.enable off

Enabling/Disabling for qtrees qtree oplocks /vol/vol2/proj enable

> qtree oplocks /vol/vol1/qtree enable
> qtree oplocks /vol/vol1/qtree disable

Please write your valuable comments, About this Blogspot.

remove hidden folder in pen drive

2012-10-01T23:15:00.001-07:00

If your file are hidden in pen drive

1. Open MY COMPUTER and see the Drive letter for pen drive. here assume it is "G" Drive

2. Click on "Start" -->Run --> type command "cmd" and press Enter.

i. cd g: - press Enter.

ii. attrib -h -r -s /s /d *.* - press Enter.

iii. wait for some time that command to execute.

Now un-plug the drive and insert again, your hidden file will we visible normally.

Please write your valuable comments, About this Blogspot.

Steps creating VFiler

2012-09-20T22:14:00.000-07:00

Steps creating VFiler
The following conditions must be met before you can create a vFiler unit :

• You must create at least one unit of storage (qtrees, volumes - traditional or flexible) before creating vfiler

• The storage unit that contains vFiler unit configuration information must be writable volume. It must not be a read-only file system.

sysntax: vfiler create <vfiler name> -i <ip address> <Volume or Qtree path>

Below red colors are input to configure vfiler.

3070-1> vfiler create vfiler_name -i 10.100.201.120 -i /vol/vol1

Tue Nov 9 03:03:39 GMT [Vfiler_name@useradmin.added.deleted:info]: The role 'compliance' has been added.

Tue Nov 9 03:03:39 GMT [Vfiler_name@export.file.backup.notDone:warning]: Could not read from file /etc/exports.

Tue Nov 9 03:03:39 GMT [Vfiler_name@export.file.missing:warning]: Could not open '/etc/exports' for reading.

The etc configuration directory for vfiler "Vfiler_name" is /vol/vol1/etc.

Tue Nov 9 03:03:39 GMT [Vfiler_name@cmds.vfiler.info:notice]: vFiler unit Vfiler_name initialized.

Setting up vfiler Vfiler_name

Configure vfiler IP address 10.100.201.120? [y]: y

Interface to assign this address to {e0a, e0b, e0c, e0d}: e0b

Netmask to use: [255.255.255.0]:

Configure vfiler IP address 10.100.201.121? [y]: y

Interface to assign this address to {e0a, e0b, e0c, e0d}: e0c

Netmask to use: [255.255.255.0]:

The administration host is given root access to the filer's

/etc files for system administration. To allow /etc root access

to all NFS clients enter RETURN below.

Please enter the name or IP address of the administration host: 10.100.200.9 (Base netapp filer ip)

Do you want to run DNS resolver? [n]:

Do you want to run NIS client? [n]:

e0b: flags=0x2f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

inet 10.100.201.77 netmask 0xffffff00 broadcast 10.100.201.255

ether 00:a0:98:0d:20:be (auto-1000t-fd-up) flowcontrol full

e0c: flags=0x2f4c867<UP,BROADCAST,RUNNING,MULTICAST,TCPCKSUM> mtu 1500

inet 10.100.201.67 netmask 0xffffff00 broadcast 10.100.201.255

ether 00:a0:98:0d:20:bd (auto-1000t-fd-up) flowcontrol full

Tue Nov 9 03:04:39 GMT [Vfiler_name@useradmin.added.deleted:info]: The user 'root' has been added.

Default password for root on vfiler Vfiler_name is "".

New password:

Retype new password:

Tue Nov 9 03:04:47 GMT [Vfiler_name@passwd.changed:info]: passwd for user 'root' changed.

Do you want to setup CIFS? [y]:

This process will enable CIFS access to the filer from a Windows(R) system.

Use "?" for help at any prompt and Ctrl-C to exit without committing changes.

Your filer does not have WINS configured and is visible only to

clients on the same subnet.

Do you want to make the system visible via WINS? [n]:

A filer can be configured for multiprotocol access, or as an NTFS-only

filer. Since multiple protocols are currently licensed on this filer,

we recommend that you configure this filer as a multiprotocol filer

(1) Multiprotocol filer

(2) NTFS-only filer

Selection (1-2)? [1]: 1

CIFS requires local /etc/passwd and /etc/group files and default files

will be created. The default passwd file contains entries for 'root',

'pcuser', and 'nobody'.

Enter the password for the root user []:

Retype the password:

The default name for this CIFS server is 'VFILER_NAME'.

Would you like to change this name? [n]: n

Data ONTAP CIFS services support four styles of user authentication.

Choose the one from the list below that best suits your situation.

(1) Active Directory domain authentication (Active Directory domains only)

(2) Windows NT 4 domain authentication (Windows NT or Active Directory domains)

(3) Windows Workgroup authentication using the filer's local user accounts

(4) /etc/passwd and/or NIS/LDAP authentication

Selection (1-4)? [1]: 3

What is the name of the Workgroup? [WORKGROUP]:

CIFS - Starting SMB protocol...

It is recommended that you create the local administrator account

(VFILER_NAME\administrator) for this filer.

Do you want to create the VFILER_NAME\administrator account? [y]:

Enter the new password for VFILER_NAME\administrator:

Retype the password:

Welcome to the WORKGROUP Windows(R) workgroup

Tue Nov 9 03:05:09 GMT [vfiler_name@passwd.changed:info]: passwd for user 'root' changed.

Tue Nov 9 03:05:19 GMT [vfiler_name@cifs.startup.local.succeeded:info]: CIFS: CIFS local server is running.

3070-1> vfiler status

vfiler0 running
vifiler_name running

Note : vfiler0 is the default (once we enable the license default will create)

Steps creating VFiler DR(disaster recovery)

VFILER COMMANDS

Vfiler

Please write your valuable comments, About This Blogspot.

Enable Security tab in windows 2003

2012-09-05T00:22:00.002-07:00

1. For windows 2003 server

Click Start --> run

Regsvr32 rshx32.dll

2. For windows 2003 server

Start--> run
Type regedit
Locate the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Exchange\EXAdmin
On the Edit menu, click Add Value, and then add the following registry value: Value Name: ShowSecurityPage. Data Type: REG_DWORD Radix: Binary Value: 1
Quit Registry Editor.

Please write your valuable comments, about my BlogSpot.

VFILER COMMANDS

2012-09-02T05:55:00.000-07:00

TO CREATE A VFILER UNIT:

> vfiler create <vfiler name> -i <ip address> <Volume or Qtree path>

Fas2050> vfiler create vfiler1 -i 10.10.x.x /vol/vol1

After command executed vfiler1 is installed in volume1
vfiler install is same like ONTAP installation.

TO GO TO A VFILER CLI:

> vfiler context <vfiler name>

Fas2050> vfiler context vfiler1

This is the command to enter in vfiler unit.

TO GO TO NON DEFAULT VFILER UNIT:

> vfiler context <vfiler0>

Fas2050> vfiler context vfiler0

Vfiler0 is the main filer
If this command is execute vfiler come to Physical filer(FAS2050)

TO RENAME A VFILER:

> vfiler rename <old name> <new name>

Fas2050> vfiler rename old_vfiler1 to new_vfiler

TO DESTROY A VFILER:

> vfiler stop <vfiler name> and then vfiler destroy <vfiler name>

we cannot destroy vfiler directly

Fas2050> vfiler stop vfiler1

Fas2050> vfiler destroy viler1

TO CONFIGURE DISASTER RECOVERY FOR A VFILER:

> vfiler dr configure –l <remote_login:remote_passwd>

TO ADD RESOURCES TO A VFILER:

Resources is nothing, its is another volume or qtree
if we need to increase vfiler space, we can add another volume or qtree

> vfiler add <vfiler name> -I <ip address> <path>

Fas2050>

TO REMOVE RESOURCES FROM A VFILER:

if added more than enough volume or qtree means,
we can remove resources from vfiler

> vfiler remove <vfiler name> -I <ip address> <path>

TO MIGRATE A VFILER:

> vfiler migrate start –l <remote_login:remote_passwd>
remote_vfiler@remote_filer

Fas2050>

TO MOVE RESOURCES FROM ONE VFILER TO OTHER IS:

> vfiler move <vfiler_from> <vfiler_to> -I <ip address> <path>

Fas2050>

To START A VFILER:

> vfiler start <vfiler name>

Fas2050> vfiler start vfiler1

TO STOP A VFILER:

> vfiler stop <vfiler name>

Fas2050> vfiler stop vfiler1

TO CHECK THE STATUS OF A VFILER:

> vfiler status

Fas2050> vfiler status

TO RUN A COMMAND ON A VFILER:

> vfiler run <vfiler name> command

Fas2050>

TO ALLOW USE OF A PROTOCOL ON A VFILER:

Using vfiler allow command, we can allow need protocols

> vfiler allow <vfiler name> <proto=cifs| nfs| rsh| iscsi| ftp
| http>

Fas2050> viler allow vfiler1 cifs

TO DISALLOW USE OF A PROTOCOL ON A VFILER:

Using vfiler disallow command, we can remove unwanted protocols.

> vfiler disallow <vfiler name> <proto=cifs| nfs| rsh| iscsi| ftp
| http>

Fas2050> viler disallow vfiler1 cifs

TO SET NUMBER OF VFILER UNIT:

Maximum of 65 vfiler unit and 65th is viler0 for one filer.
we can limit vfiler unit creation for the physical filer
if we limited vfiler means we cannot create more than limited value

> vfiler limit <number>

Fas2050> vfiler limit 15

LICENSING THE VILER:

> license add <Multistore license>

Fas2050> license add xxxxxxxxxxxxx

VFILER COMMANDS

VFILER

Please write your valuable comments, about my blogspot.

Vfiler

2012-09-01T02:30:00.000-07:00

MultiStore

MultiStore is a software product you can use optionally.
MultiStore enables you to partition the storage and network resources of a single storage system so that it appears as multiple storage systems on the network.
Each "storage system" created as a result of the partitioning is called a vFiler unit.
A vFiler unit, using the resources assigned, delivers file services to its clients as a storage system does.The storage resource assigned to a vFiler unit can be one or more qtrees or volumes. The network resource assigned can be one or more base IP addresses or IP aliases associated with network interfaces.
You can add or remove resources at any time.
we don't need additional license for the vfiler unit, we can use physical filer license to vfiler unit.

Reasons for using MultiStore

MultiStore has many features that you can use for your provisioning needs.

To consolidate multiple servers to one storage system.
To use the storage system to host data for multiple customers, such as clients of a service provider or different organizations within an enterprise.
To use the SnapMirror technology for migrating data from one storage system to another
transparently.

Some limitations of MultiStore

You can have a maximum of 65 vFiler units on a storage system. You can create 64 vFiler units on a storage system. The 65th vFiler unit is vfiler0, which is created automatically when MultiStore is licensed on the storage system.
In an active/active configuration, you can create up to 64 vFiler units on each node of the active/active configuration, for a maximum of 130 vFilers in the active/active configuration.
Only Ethernet interfaces are supported for vFiler units
Only the NFS, CIFS, iSCSI, HTTP, and FTP protocols are supported for the vFiler units. However, protocols not supported on vFiler units are supported on vfiler0, the default vFiler unit.

VFILER COMMANDS

Steps creating VFiler and Dr

Please write your valuable comments, About this Blogspot.

NetApp Maxfiles

2012-08-31T00:11:00.001-07:00

Maxfiles

Using maxfiles command we can increase the number of inodes in the respective volume, so that we create additional files.
We may not decrease the inode value because you might not be able to run WAFL_check.
One file is one inodes

The below examples show how to inodes increase:

STEP :1

fas3070> aggr create aggr1 10
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.24 Shelf 1 Bay 8 [NETAPP VD-100MB 0042] S/N [50125907] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.36 Shelf 2 Bay 4 [NETAPP VD-100MB 0042] S/N [50130017] to aggregate aggr1 has completed successfully
Creation of an aggregate with 10 disks has completed.
fas3070> Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.22 Shelf 1 Bay 6 [NETAPP VD-100MB 0042] S/N [50125906] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.35 Shelf 2 Bay 3 [NETAPP VD-100MB 0042] S/N [50130016] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.21 Shelf 1 Bay 5 [NETAPP VD-100MB 0042] S/N [50125905] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.34 Shelf 2 Bay 2 [NETAPP VD-100MB 0042] S/N [50130015] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.20 Shelf 1 Bay 4 [NETAPP VD-100MB 0042] S/N [50125904] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.33 Shelf 2 Bay 1 [NETAPP VD-100MB 0042] S/N [50130014] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.19 Shelf 1 Bay 3 [NETAPP VD-100MB 0042] S/N [50125903] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:16 GMT [raid.vol.disk.add.done:notice]: Addition of Disk /aggr1/plex0/rg0/v4.32 Shelf 2 Bay 0 [NETAPP VD-100MB 0042] S/N [50125913] to aggregate aggr1 has completed successfully
Fri Aug 31 06:29:17 GMT [wafl.vol.add:notice]: Aggregate aggr1 has been added to the system.
fas3070> Fri Aug 31 06:29:20 GMT [nbt.nbns.registrationComplete:info]: NBT: All CIFS name registrations have completed for the local server.

STEP:2

CREATE THE NEW VOLUME FOR 100MB

fas3070>
fas3070> vol create vol1 aggr1 1.2g
Creation of volume 'vol1' with size 1.2g on containing aggregate
'aggr1' has completed.
fas3070>

STEP:3

CHECK THE VOL1 & VOL1 INODE VALUE

fas3070> maxfiles
Volume vol0: maximum number of files is currently 19990 (6096 used)
Volume vol1: maximum number of files is currently 322,122547 (52870 used)
fas3070>

STEP:4

NOW THE CHECK THE USED AND FREE INODE OF VOL1

fas3070> df -i /vol/vol1

Filesystem iused ifree %iused Mounted on

/vol/vol0 52870 322,122547 97% /vol/vol0

fas3070>

STEP:5

INCREASING THE INODE VAULE 3033 TO 5000

fas3070> maxfiles vol1 422,122547
The new maximum number of files specified is more than twice as big as it needs to be, based on current usage patterns. Increasing the maximum number of files consumes disk space, and the number can never
be decreased. Configuring a large number of inodes can also result in less available memory after an upgrade, which means you might not be able to run WAFL_check.

The new maximum number of files will be rounded to 422,122540.

Are you sure you want to increase the maximum number of files? y
fas3070>

fas3070> maxfiles
Volume vol0: maximum number of files is currently 19990 (6154 used).
Volume vol1: maximum number of files is currently 422,122540 (52870used).
fas3070>

NOW THE INODE VALUE IS 4988 AT MAXIMUM OF VOLUME1

FINISHED

Please write your valuable comments, about my blogspot.

All General Commands

2012-08-20T22:06:00.001-07:00

General Commands

setup (Re-Run initial setup)
halt (Reboots controller into bootrom)
reboot (Reboots controller back to Data Ontap)
sysconfig -a (System configuration and information)
java netapp.cmds.jsh (limited freebsd cli)
storage show disk (show physical information about disks)
passwd (Change password for logged in user)
sasadmin shelf (shows a graphical layout of your shelves with occupied disk slots)
options trusted.hosts x.x.x.x or x.x.x.x/nn (hosts that are allowed telnet, http, https and ssh admin access. x.x.x.x = ip address, /nn is network bits)
options trusted.hosts * (Allows all hosts to the above command)
sysstat -s 5 (Displays operating statistics every 5 seconds i.e. CPU, NFS, CIFS, NET, DISK, etc)
options autologout.console.enable on (Turns on autologout for the console)
options autologout.console.timeout 300 (300 second autologout for the console)
options autologout.telnet.enable on (Turns on autologout for telnet)
options autologout.telnet.timeout 300 (300 second autologout for the console)

Diagnostics

Press DEL at boot up during memory test followed by boot_diags and select all (Diagnostic tests for a new install)
priv set diags (Enter diagnostics CLI mode from the Ontap CLI)
priv set (Return to normal CLI mode from diagnostics mode)

Software

software list (Lists software in the /etc/software directory)
software get http://x.x.x.x/8.0_e_image.zip 8.0_e_image.zip (Copy software from http to software directory)
software delete (Deletes software in the /etc/software directory)
software update 8.0_e_image.zip -r (Install software. The -r prevents it rebooting afterwards)

Baseboard Management Controller BMC

bmc status (shows the status of the BMC remote management interface)
bmc setup (BMC remote management interface setup)

Service Port SP

sp status (shows the status of the SP remote management interface)
sp setup (SP remote management setup)

ACP (Alternate Control Path)

options acp.enabled on (Turns on ACP)
storage show acp -a (show ACP status)

Root Volume

If you have a 32-bit root volume that you wish to convert to 64-bit, the best way I found is to snapmirror the root volume to a 64-bit aggregate, break the snapmirror, set the new root volume as root, and either failover and failback the filer, or reboot.

Aggregates

aggr create aggregate_name (Creates an Aggregate)
aggr destroy aggregate_name (removes an Aggregate)
aggr offline aggregate_name (takes an Aggregate offline)
aggr online aggregate_name (bring an Aggregate online)
aggr options aggregate_name root (makes an Aggregate root|Only use if your Root Aggregate is damanged)
aggr status (shows status of all aggregates)
aggr status aggregate_name (show status of a specific Aggregate)
aggr status -r aggr0 (shows the root volume on aggr0 and the disk layout)
aggr status -s aggr0 (shows spare disks on aggr0)
aggr status -v aggr0 (MUST BE DONE IN PRIV SET DIAG MODE. Shows more detailed information of the aggregate status)
aggr show_space aggregate_name (shows specific aggregate space information)
aggr options aggregate_name nosnap=on (Disable snapshot autocreation)
aggr options aggregate_name raidsize=x (x being the number of drives in the RAID)
aggr scrub status -v (MUST BE DONE IN PRIV SET DIAG MODE. Shows scrub status of the aggregate)
aggr scrub resume (MUST BE DONE IN PRIV SET DIAG MODE. Resumes a susepended scrub)
aggr scrub suspend (MUST BE DONE IN PRIV SET DIAG MODE. Suspends a current scrub process)
aggr scrub start (MUST BE DONE IN PRIV SET DIAG MODE. Starts a new scrub process)
snap reserve -A aggregate_name 0 (Set Aggregate snap reserve to 0% or any number you enter)
snap list -A aggregate_name (Lists snapshots on specified aggregate)
snap delete -A aggregate_name (Deletes a snapshot on a specified aggregate)
snap sched -A aggregate_name x x x@x,x,x (Creates a snapshot shedule in weeks days hours@time ie 0 2 1@9 means no weekly snaps, 2 daily, 1 hourly @ 9am)

Volumes

vol create volume_name (Creates a volume)
vol autosize volume_name (Shows autosize settings for a given volume)
vol autosize volume_name on|off (Turns Volume autosize on or off)
vol options volume_name (Lists volume options)
vol size volume_name + size k|m|g|t (increase volume size by KB, MB, GB or TB)
vol status -f (lists broken or failed disks)
vol scrub status -v (Shows the scrubbing status of volumes)
vol options nosnapdir on|off (enables or disables snapshot visibility from the volume or LUN level)

Qtree’s

qtree create /vol/volume_name/qtree_name (Create a qtree within a volume)
qtree security /vol/volume_name/qtree_name unix|ntfs|mixed (Change security settings of a qtree)
qtree stats qtree_name (Shows CIFS or NFS ops/sec for a given qtree)
qtree status (Displays all your Qtree’s)

Snapshots

snap create volume_name snapshot_name (create a snapshot)
snap list volume_name (List snapshots for a volume)
snap delete volume_name snapshot_name (delete a snapshot on a volume)
snap delete -a volume_name (Deletes all snapshots for a volume)
snap autodelete volume_name show (Shows snapshot autodelete settings for a volume)
snap restore -s snapshot_name volume_name (Restores a snapshot on the specified volume name)
snap sched volume_name weeks days hours@time (Creates a snapshot schedule on a volume i.e. snap sched volume 4 5 1@07 Weekly Snapshots are created at midnight on each Sunday, Daily snapshots are created each day except Sunday at midnight)
snap delta volume_name (Shows delta changes between snapshots for a given volume)
snap reserve volume_name (Shows the snap reserve for a given volume)
snap reclaimable volume_name snapshot_name (Shows the amount of space reclaimable if you remove this snapshot from the volume)
options cifs.show_snapshot on (Allows snapshot directory to be browse-able via CIFS)
options nfs.hide_snapshot off (Allows snapshot directory to be visible via NFS)

SnapMirror

options snapmirror.enable on (turns on SnapMirror. Replace on with off to toggle)
rdfile /etc/snapmirror.allow (Performed on the Source Filer. You should see you destination filers in this file.)
wrfile /etc/snapmirror.allow (Performed on the Source Filer. Overwrites the file with the specified destination filer name and ip address)
vol restrict volume_name (Performed on the Destination. Makes the destination volume read only which must be done for volume based replication. Don’t use for Qtree based replication)
snapmirror initialize -S srcfiler:source_volume dstfiler:destination_volume (Performed on the destination. This is for full volume mirror. For example snapmirror initialize -S filer1:vol1 filer2:vol2)
snapmirror initialize -S srcfiler:/vol/vol1/qtree dstfiler:/vol/vol1/qtree (Performed on the destination. Performs the same as the command above but for Qtree’s only)
snapmirror initialize -S srcfiler/vol/vol1/- dstfiler:/vol/vol1/qtree (Performed on the destination. Performs volume to qtree replication. Includes all luns, exports on the source volume)
snapmirror status (Shows the status of snapmirror and replicated volumes or qtree’s)
snapmirror status -l (Shows much more detail that the command above, i.e. snapshot name, bytes transferred, progress, etc)
snapmirror quiesce volume_name (Performed on Destination. Pauses the SnapMirror Replication. If you are removing the snapmirror relationship this is the first step.)
snapmirror break volume_name (Performed on Destination. Breaks or disengages the SnapMirror Replication. If you are removing the snapmirror relationship this is the second step followed by deleting the snapshot)
snapmirror resync volume_name (Performed on Destination. When data is out of date, for example working off DR site and wanting to resync back to primary, only performed when SnapMirror relationship is broken)
snapmirror update -S srcfiler:volume_name dstfiler:volume_name (Performed on Destination. Forces a new snapshot on the source and performs a replication, only if an initial replication baseline has been already done)
snapmirror release volume_name dstfiler:volume_name (Performed on Destination. Removes a snapmirror destination)
/etc/snapmirror.conf (edit or wrfile this file on the destination filer or vfiler to enter in a snapmirror schedule. i.e. srcfiler:vol1 dstfiler:vol1 – 15 * * * This will replicate every 15 minutes. Each * represents a value. Starting from right to left you have day of week, month, day of month, hour minute. Minute 0-59, hours 0-23, day-of-month 1-31, day-of-week 0 for Sunday – 6 Saturday) Each value can only be a number.)
/vol/vfiler_vol/etc/snapmirror.conf (read or write this file for snapmirror configurations on a vfiler. vfiler_vol being the first volume with the /etc in the vfiler)
“priv set diag” followed by “snapmirror break -h ” followed by “priv set”. (If for some reason you snapmirror relationship has been orphaned, meaning it doesn’t exist in snapmirror status on the source but does exist on the destination, you can use these three commands to force the destination to become read/write. You can then do “snap list” and find the baseline snapshot for the destination. Followed by snap delete of the baseline snapshot. This will remove the snapmirror relationship if all else fails. Lastly don’t forget to remove the entry from snapmirror.conf)

Cluster

cf enable (enable cluster)
cf disable (disable cluster)
cf takeover (take over resources from other controller)
cf giveback (give back controller resources after a take over)

vFiler – Multistore

vfiler limit (Performed on the host to see what the limit of vfilers is)
vfiler limit 16 (Performed on the host to change the limit of vfilers to 16 or any number you specify. Check the documentation for Memory Requirements before doing this)
vfiler status (Displays the status of the vfiler i.e. running or stopped)
vfiler status -r (On the host system. Shows which volumes are running on each vfiler)
vfiler rename old_vfiler_name new_vfiler_name (Renames a vfiler)
vfiler run vfiler_name setup (Runs the vfiler setup wizard)
vfiler run vfiler_name cifs setup (Runs the cifs setup wizard for a vfiler)
ipspace create ipspacename (Creates an ipspace – needed when 2 or more vfilers use the same network subnets)
ipspace list (Lists the available ipspace’s)
ipspace assign ipspacename interface_name (Assigns the interface to an ipspace.)
ipspace destroy ipspace_name (Removes/Deletes an ipspace)
vfiler create vfiler_name -s ipspace_name -i x.x.x.x /vol/volume_name or qtree_name (Creates a vfiler name with ip address x.x.x.x and assigns the volume or qtree to the vfiler. The -s is optional)

NOTE:

Creating a qtree as the base vfiler does not allow you to enable snapmirror. You must create the
base as a volume!

vfiler add vfiler_name -i x.x.x.x /vol/volume_name (Adds an ip address and additional volume (can be qtree) to an existing vfiler name)
vfiler remove vfiler_name -i x.x.x.x /vol/volume_name (Removes an IP address and volume from an existing vfiler)
vfiler destroy vfiler_name (Deletes/removes a vfiler)
vfiler rename vfiler_name_old vfiler_name_new (Renames a vfiler from old name to new name)
vfiler context vfiler_name (Changes CLI into the context of the vfiler name)
vfiler allow vfiler_name proto=cifs proto=nfs proto=iscsi (Allows the following protocols cifs, nfs and iscsi. Disallows rsh, ssh, ftp and http)
vfiler stop vfiler_name (Stops a vfiler instance)
vfiler start vfiler_name (Starts a vfiler instance)
vfiler run vfiler_name route add default x.x.x.x 1 (Adds a default route to a vfiler. Performed from vfiler0)
route add x.x.x.x/x x.x.x.x 1 (Adds a route in a vfiler)
To add extra vlans to a vfiler you must do the following:
Check the ip space that the vfiler is using by typing ipspace list
Create the vlan interface on the host i.e. vif0-360 for vlan 360
Assign the interface to the ip space of the vfiler i.e. ipspace assign ipspace_name vif0-360
Add the ip address you wish to use on the vlan interface to the vfiler i.e. vfiler add vfiler_name -i 192.168.1.1
Once the vfiler has this ip address in it’s config we can add it onto the interface i.e. ifconfig vif0-360 192.168.1.1 netmask 255.255.255.0

Autosupport

options autosupport.support.enable on (Turns Autosupport on)
options autosupport.support.enable off (Turns Autosupport off)
autosupport.doit “description” (creates an autosupport alert with a user defined description)

Hot Spares

Any functioning disk that is not assigned to an aggregate but is assigned to a controller functions as a hot spare disk
disk show
vol status -r (displays which disks are allocated as spare)

Disks

disk show (Show disk information)
disk show -n (Show unowned disks)
disk assign 0d.02.0 -s unowned (Changes ownership from owned to unowned or to other cluster member)
disk assign 0d.02.0 (assigns the disk to the controller you perform the command on)
options disk.auto_assign off (turns auto assign of unowned disks to controllers to off)
options disk.auto_assign on (turns auto assign of unowned disks to controllers to on)
storage show disk -p (displays primary, secondary port, shelf and bay in a metro cluster)

Luns

lun setup (runs the cli lun setup wizard)
lun create -s 10g -t windows_2008 -o noreserve /vol/vol1/lun1 (creates a lun of 10GB with type Windows 2008, sets no reservation and places it in the following volume or qtree)
lun offline lun_path (takes a lun offline)
lun online lun_path (brings a lun online)
lun show -v (Verbose listing of luns)
lun move /lun_path_source /lun_path_destination (Move lun from source to destination)
lun resize -f lun_path +|- new_size k|m|g|t (Resizes a lun by adding space (+) or subtracting space (-) Note: a lun can only ever grow 10x it’s original size)
lun map /vol/vol1/lun1 igroup_name (Maps lun1 to the igroup_name)
lun alignment show (MUST BE DONE IN PRIV SET DIAG MODE. Shows which luns are aligned and which are not)

Fiber FCP

fcadmin config -t taget 0a (Changes adapter from initiator to target)
fcadmin config (lists adapter state)
fcadmin start (Start the FCP service)
fcadmin stop (Stop the FCP service)
fcp show adapters (Displays adapter type, status, FC Nodename, FC Portname and slot number)
fcp nodename (Displays fiber channel nodename)
fcp show initiators (Show fiber channel initiators)
fcp wwpn-alias set alias_name (Set a fiber channel alias name for the controller)
fcp wwpn-alias remove -a alias_name (Remove a fiber channel alias name for the controller)
igroup show (Displays initiator groups with WWN’s)

iSCSI

iscsi start (Start the iscsi service)
iscsi stop (Stop the iscsi server)
iscsi status (Show whether iscsi server is running or not running)
iscsi interface show (Show which interfaces are enabled or disabled for iscsi)
iscsi interface enable interface_name (Enable an interface for iscsi)
iscsi interface disableinterface_name (Disable an interface for iscsi)
iscsi nodename (Display the controllers iscsi nodename)
igroup show (Displays iSCSI initiators)
igroup create -i -t vmware sqlcluster_igroup (Creates an Initiator Group called sqlcluster_igroup with OS type vmware)
igroup add sqlcluster_igroup iqn.1991-05.com.microsoft:sqlcluster1.vmlab.local (Assigns the following iscsi initiator to the sqlcluster_igroup. This can also be FCP addresses)

Cifs

cifs setup (cifs setup wizard)
cifs terminate (terminate the cifs service)
cifs restart (restarts cifs)
cifs shares (displays cifs shares)
cifs status (show status of cifs)
cifs lookup SID|name (Either displays the SID if you type in the name or name if you type in the SID)
cifs sessions (Show you current cifs sessions)
cifs sessions -s username (Shows the current session for a user)
cifs broadbast -v volume_name “message” (Broadcast a message to all users connected to volume_name)
cifs shares -add share_name /vol/volume_name/qtree_name (Create a cifs share on a specific volume or qtree)
cifs shares -delete share_name (Deletes a share name)
cifs shares share_name (Displays full path and permissions of the share)
cifs access share_name -g user_rights (Grants specific user rights to the share)
cifs access share_name user_name permission (Grants a specific permission to a user for a share. Permissions = Full Control, Change, Read, No Access)
cifs domain info (Lists information about the filers connected Windows Domain)
cifs testdc ip_address (Test a specific Windows Domain Controller for connectivity)
cifs prefdc (Displays configured preferred Windows Domain Controllers)
cifs prefdc add domain address_list (Adds a preferred dc for a specific domain i.e. cifs prefdc add netapplab.local 10.10.10.1)
cifs prefdc delete domain (Delete a preferred Windows Domain Controllers)
cifs gpresult (Displays which Windows Group Policies apply to this filer)
cifs gpupdate (Forces an update of Windows Group Policy)
cifs top (Performance data for cifs. cifs.per_client_stats.enable option must be on to use this feature)
vscan on (Turns virus scanning on)
vscan off (Turns virus scanning off)
vscan reset (Resets virus scanning)

NFS

nfs setup (Runs the NFS setup wizard)
/etc/export (Enter in your export information here and save the file. Then proceed with exportfs -a to update memory buffer)
exportfs (Displays current exports)
exportfs -p path (Adds exports to the /etc/exports file)
exportfs -uav (Unexports all current exports)
exportfs -u path (Unexports a specific export from memory)
exportfs -z path (Unexports a specific export and also removes it from /etc/exports)
exportfs -a (Updates memory buffer with contents in /etc/exports)
nfsstat -d (Displays NFS statistics)

HTTP Admin

options httpd.admin.enable on (Turns on http web admin, na_admin)
options httpd.admin.access host=x.x.x.x,x.x.x.x (Allows admin access for specific hosts separated by a comma)

SIS (Deduplication)

sis status (Show SIS status)
sis config (Show SIS config)
sis on /vol/vol1 (Turn on deduplication on vol1)
sis config -s mon-fri@23 /vol/vol1 (Configure deduplication to run every monday – Friday at 11pm on vol1)
sis start -s /vol/vol1 (Run deduplication manually on vol1)
sis status -l /vol/vol1 (Display deduplication status on vol1)
df -s vol1 (View space savings with deduplication)
sis stop /vol/vol1 (Stop deduplication on vol1)
sis off /vol/vol1 (Disables deduplication on vol1)

User Accounts

useradmin user add user_name -g group_name (Adds a user to a group)
useradmin user list (Lists current users)
useradmin user list user_name (List specific user information)
useradmin group list (Lists current groups)
useradmin group delete group_name (Deletes a specific group name)
useradmin group modify group_name -g new_group_name (Modify group name)
useradmin user delete user_name (Delete a specific user)
useradmin user modify user_name -g group_name (Adds a user to a group)
useradmin domain user add user_name -g group_name (Adds a Windows Domain user to a local group)
useradmin domain user list -g group_name (List Windows Domain users in a specific group)

DNS

dns flush (Flushes the DNS cache)
/etc/resolv.conf (edit this file to change your dns servers)

NDMPD

ndmpd status (check status)
ndmpd on|off (turns ndmpd on or off)
ndmpd version (displays version information)
ndmpd version 4 (set ndmpd version to 4)
options ndmpd (Display ndmpd options)
Reading and Writing Files (Deduplication)

rdfile path/file (Reads a file)
wrfile path/file (Writes to a file. Warning this method overwrites the file. Make sure you copy out original contents if you wish to keep it. If you haven’t used this before try on the simulator.)
wrfile -a path/file (Writes to a file by appending the changes)

Logging

/etc/messages (All logging is for the system is stored here)

VIF

vif status (Displays the status of VIF interfaces)
vif create lacp vif0 ip e0a,e0b,e0c,e0d (Create a vif interface named VIF0 using lacp and a load balancing method of IP, bundled with interface e0a, e0b, e0c, e0d)
vif add vif0 e0a (Adds a down interface into an existing VIF)
vif destroy vif0 (deletes a VIF interface)

Network

vlan create vif0 10 (create a vlan on interface vif0. The interface will be vifo-10)
vlan delete vif0 10 (deletes the vlan interface vif0-10)
ifconfig vif0-10 x.x.x.x netmask x.x.x.x partner vif0-10 (Sets IP information on the interface named vif0-10 with a partner interface of vif0-10)
route add default 192.168.1.1 1 (Adds a default route of 192.168.1.1 with metric 1)

Performance

sysstat -x 1 (displays per second statistics for CPU, iSCSI, FCP, CIFS, NFS, Disk Util, etc)
sysstat -m 1 (displays per second statistics for each CPU)
sysstat -M 1 (MUST BE DONE IN PRIV SET DIAG MODE. Displays per second statictics for CPU’s, Kahuna, WAFL, etc)
statit b (MUST BE DONE IN PRIV SET DIAG MODE. Starts a performance snapshot)
statit e (MUST BE DONE IN PRIV SET DIAG MODE. Stops a performance snapshot and displays the stats on screen. TIP: Turn on logging in your terminal program before running this command)

Please write your valuable comments, about my blogspot.

Roles and Responsibilities in NetApp Storage Admin

2012-05-17T08:36:00.004-07:00

Roles and Responsibilities in NetApp Storage Admin

Select some important points

We are doing remote support.
Checking the storage critical Events.
Controlling & Monitoring Network Interface.
Checking the status of aggregate and volume usage using DFM.
Checking the ticketing tool and mails.
Configuring and troubleshooting SnapMirror Environment.
Performing Daily health check to monitor the usage of LUN, Aggregate and volume utilization.
Configuring H drive for the users in the environment.
Restoring the data using snap restore and CIFS shares.
Dealing with permissions (Adding/removing the security groups to the shares) for share folders in CIFS.
Configuring and troubleshooting SnapVault Environment.
Performed DR test for the environment.
Snapshot, lunclone, flexclone management.
Setting up and troubleshooting V-Filer Environment.
Lun management (LUN creation, LUN snapshots, Manual and automatic igroup management, LUN restore) using Snapdrive.
Setting up and troubleshooting NFS, CIFS, and SAN (FC and ISCSI) Environment.
Configuring windows ISCSI Boot LUN for the environment.
Ontap OS upgrade from 7.3.3 to 8.0 7 mode.
Storage remediation like HBA driver and firmware upgrade.
Adding disk shelf to the existing storage for standalone and High availability controllers. (involved in ontap upgrade documents team )
Assigning LUN’s (FC and ISCSI) to distributed server in various environments.
Resolving the hardware issues in co-ordination with Netapp.
Managing the reports using operations manager.
Working with qtree’s for efficient storage utilization for the users.
Performing Deduplication for the volumes.
Volume resize, aggregate disk add and lun resize
Alias, zoning configuration for the servers connected in FC environment in brocade switches.
Able to create/Expand aggregate, volume, Qtree for NAS environments, LUN’s, Igroups for SAN environments and also reclamation the LUN’s and SAN ports if any (De-commissioning projects).

Please write your valuable comments, about my blogspot.

Network Ports for NetApp

2012-05-09T23:41:00.000-07:00

Product/Source	Port	Protocol	Target	Direction
SnapDrive dfm integration	8088	http	DFM server	bi-directional
SnapDrive dfm integration - secure	8488	https	DFM server	bi-directional
snapdrive webservice	4094	http	filer/vfiler	bi-directional
snapdrive webservice - secure	4095	https	filer/vfiler	bi-directional
Snapdrive autosupport	25	TCP	SMTP server	one way
Snapdrive iscsi	3260	TCP	filer/vfiler	bi-directional
Snapdrive netbios RPC	137	TCP	filer/vfiler	bi-directional
	138	TCP	filer/vfiler	bi-directional
	139	TCP	filer/vfiler	bi-directional
	1512	TCP	filer/vfiler	bi-directional
Snapmanager for SQL	808	TCP	SQL server	bi-directional
Snapmanager for Exchange	808	TCP	SQL server	bi-directional
OSSV-ndmp	10000	TCP	DFM server	bi-directional
OSSV-snapvault	10566	TCP	filer/vfiler	bi-directional
Snapvault-ndmp	10000	TCP	DFM server	bi-directional
Snapvault-traffic	10566	TCP	filer/vfiler	bi-directional
Snapmirror Source	10566	TCP	filer/vfiler	bi-directional
" " " "	10569	TCP	filer/vfiler	bi-directional
Snapmirror Destination	10565	TCP	filer/vfiler	bi-directional
" " " "	10567	TCP	filer/vfiler	bi-directional
" " " "	10568	TCP	filer/vfiler	bi-directional
SMVI	8043	TCP	filer/vfiler	bi-directional

Please write your valuable comments, about my blogspot.

FlexClone

2012-05-02T01:19:00.000-07:00

FlexClone

Its license futures in NetApp.
Flexclone is used for testing purpose.
Flexclone need volume snapshot, using that snapshot we can clone that to new volume.
FlexClone volumes always exist in the same aggregate as parent volumes.
Clone is in writable copy and without using a lot of disk space. After split the clone that time only clone will take space from the Aggregate.

Commands :

To Create new clone

fas3070> vol clone create old_vol_name –b new_volume_name snapshot_name

To view clone status

fas3070>  vol status new_volume_name

To start a clone split:

fas3070> vol clone split start volname

To stop a clone split:

fas3070> vol clone split stop

To check the status of a clone split:

fas3070>  vol clone split status [volname]

To estimate the time of completion:

fas3070>  vol clone split estimate [volname]

Please write your valuable comments, about my Blogspot.

Comparison of vol copy, ndmpcopy and dump/restore

2012-05-01T00:32:00.002-07:00

Comparison of vol copy, ndmpcopy and dump/restore

Description	vol copy	Ndmp copy	Dump/restore
Uses Snapshot	Yes	Yes, but snapshot taken by ndmp is deleted after copy is completed	No
Requires rsh access	Yes	No	No
Destination needs to be restricted	Yes	No	Uses tape drive as destination
Requirements Similar Type of Volume	Trad to Trad and Flex to Flex copy only	Source and destination can be of either flex / Trad Vols	Source could be
Vol size requirement	Destination volume size should be equal or more capacity	No limitation on destination vol size	n/a
Directory level copy possible	No	Yes	Yes

Please write your valuable comments, about my blogspot.

NDMP Copy

2012-05-01T00:22:00.000-07:00

1 NDMP Copy

Transfers directory trees between filers using NDMP (Network Data management Protocol)

Ndmpcopy transfers data between filers/v-filers using the Network Data Management Protocol (NDMP) versions 3 and higher.
This process can be thought of as creating a dedicated data pipe between dump running on the source filer and restore running on the destination filer.

1.1 Pre-Requisite

Turn on ndmp by

Filer > ndmpd on

Ping the filers each other and make sure they are reachable

Make sure that the Data ONTAP release on the filers you are using for the copy support NDMP version 3 and/or higher.

Filer >ndmpd version

For filers running ONTAP version 7.X, change the ndmpd authentication type to challenge

Filer > options ndmpd.authtype challenge

1.2 How to run ndmpcopy command

From the filer use the following syntax to run the command.

Syntax:

ndmpcopy [options] source destination

Where, source and destination are of the form [filer:]path

Options:

-sa username:password This is used for authenticating at source filer

-da username:password This is used for authenticating at source filer

-st text | md5 Source filer authentication type

-dt text | md5 Destination filer authentication type

-l 0 | 1 | 2 Level 0,1 and 2 copy (default is 0)

-d Debug

-f Force flag

-h Help

Example:

Filer > ndmpcopy -sa root:password –da root:password /vol/vol_s 10.100.201.10:/vol/vol_d

In this example /vol/vol_s directory on the source filer is copied to /vol/vol_d on filer 10.100.201.10

-sa root:password option is specified to user is root and password is “password” for the source user authentication and –da for the same purpose at destination filer, Screen shot.

1.3 Problems Faced and Lessons Learnt

Initially filer was giving ndmp authentication error, this was fixed by specifying the username and password (-sa and -da) option.
NDMP can copy at qtree level, but can not copy individual sub directories
Snapshot backups are taken for copying the data and snapshot copy is deleted after transfer is over.
No need to restrict the destination volume for copy.
Also ONTAP version 7.x requires, ndmpd.authtype set to challenge

Please write your valuable comments, about my blogspot.

Vol Copy

2012-04-28T05:48:00.000-07:00

1. Vol Copy

volcopy is a NetApp ONTAP command that copies all data, including snapshots, from one volume to another.

1.1 Prerequisite

The source and destination volumes must either both flexible volumes or both traditional volumes.
The source volume must be online and the destination volume must be offline/restricted.
If data is copied between two filers, each filer must be defined as a trusted host of the other filer.That is, In the /etc/hosts file we need to give partner filer name and IP-address. if we did't mention properly it will display this error "Permission denied"
The usable disk space of the destination volume must be greater than or equal to the usable disk space of the source volume.

1.2 How to use the volcopy command

Make sure that the above mentioned pre-requisites are completed.

Syntax:

vol copy start [ -S | -s snapshot ] source destination

If the -S flag is used, the command copies all snapshots in the source volume to the destination volume.

To specify a particular snapshot to copy, use the -s flag followed by the name of the snapshot.

If neither the -S nor -s flag is used in the command, the filer automatically creates a distinctively-named snapshot at the time the vol copy start command is executed and copies only that snapshot to the destination volume.

The source and destination volumes must either both be traditional volumes or both be flexible volumes.

The vol copy command will abort if an attempt is made to copy between different volume types.

The source and destination volumes can be on the same filer or on different filers. If the source or destination volume is on a filer other than the one on which the vol copy start command was entered, specify the volume name in the filer_name:volume_name format.

Each volcopy start command generates two volume copy operations: one for reading data from the source volume and one for writing data to the destination volume. Each filer supports up to four simultaneous volume copy operations.

Example:

vol copy start [ -S | -s snapshot ] source destination

How to monitor the status of vol copy operation

Syntax:

vol copy status [operation_number]

Displays the progress of one or all active volume copy operations.

The operations are numbered from 0 through 3.If no operation_number is specified, then status for all active vol copy operations is provided.

1.3 Controlling the speed of Volcopy

Syntax:

vol copy throttle [ operation_number ] value

This command controls the performance of the volume copy operation. The value ranges from 10 (full speed) to 1 (one-tenth of full speed).The default value is maintained in the filer's vol.copy.throttle option and is set 10 (full speed) at the factory.The performance value can be applied to an operation specified by the operation_number parameter.

If an operation number is not specified, the command applies to all active volume copy operations.

Please write your valuable comments, about my blogspot.

Deduplication

2012-04-13T03:33:00.002-07:00

Deduplication

Deduplication in license future in netapp.
Deduplication in an elimination of redundant data in volume
Deduplication deletes the multiple same data (words) and make only the unique data is stored. So some repeated data deletion provide some space to storage
Deduplication find duplicate 4KB blocks anywhere in the volume and delete duplicate and stores a unique in 4KB.

License

Deduplication need two license

First nearstore_options license must installed
Second Asis license install.

Netapp Deduplication commands:

license add for sis

Enable Asis for volume

Before start Asis check the volume total spaces and free spaces

Start Asis for /vol/vol1

If your volume already contains data means, now you start the Asis

After you started the deduplication sis will added in volume

After Asis started check the saved spaces

This is default sis schedule for volume

We change the default sis schedule for the volume

We can off the sis process

Please write your valuable comments, about my blogspot.

HBA - HOST BUS ADAPTER

2012-02-28T01:54:00.001-08:00

HBA= HOST BUS ADAPTER

HBA is the device which is inserted in the server and storage mother board PCI slot.

Fibre channel(FC) cable connected in HBA ports.

HBA that interconnects with servers, switches and storage devices on the fabric switch.

FC HBA have (world wide port number WWPN and WWNN (world wide node name) like MAC address

Open Systems SnapVault

2012-02-28T01:46:00.002-08:00

Extend and enhance your data protection strategy.

Designed to safeguard open storage platforms faster and more cost effectively, Open Systems SnapVault® (OSSV) is your key to simplifying and extending NetApp® data protection strategies.

Open Systems SnapVault leverages the block-level incremental backup technology found in SnapVault to protect Windows®, Linux®, UNIX®, SQL Server®, and VMware® systems running on mixed storage.OSSV increases performance and enables more frequent data protection by moving and creating backups from changed data blocks, not entire changed files. And since only changed blocks are stored, less capacity is needed.

OSSV is particularly well suited for centralizing D2D backups from remote offices.

NetApp OSSV recently introduced support for Microsoft® SQL Server database backups. We also made OSSV available as a free download from our customer support site (formerly NOW®), to maximize the cost savings and backup efficiencies generated by your NetApp SnapVault systems.

For more information on the benefits of OSSV for efficient D2D backup of non-NetApp data, please read theOpen Systems SnapVault datasheet. For more information on how our core Snapshot® and replication technologies can protect NetApp data, please visit the SnapVault page. And to see how NetApp Syncsort Integrated Backup extends OSSV capabilities to more applications and recovery scenarios, please visit the NSBpage.

Please write your valuable comments, about my blogspot.

Netapp HR Question

2012-02-22T21:30:00.001-08:00

1. Tell me about yourself? Your work? Your designation & your responsibilities?

I am name from place, I have 3+ years experience in IT, I had completed (dgree name in college name ). I debuted to (your first company name) as system administrator from (month and year) to (month and year). And I got offer in (Second company name) as a storage admin from (month and year) to still now. And my current job profile is(say some important points)

2. Why did you leave your last job?

Why are you looking for a job change?

Speak positive think and never say major problem with management Team leader and co-workers with current organization.
Better say knowledge and career growth.
I don't have access for filler.

3. In what areas you would like to improve yourself?

Try to include improvement activities that relate to the job. A wide variety of activities can be mentioned as positive self-improvement. Have some good ones handy to mention

4. What do you know about this organization?

Please refer the respective company website, shares, top management before going to interview.

5. Do feel yourself successful roll in current job?

Please say yes and speak about the critical work you faced in your current job.

6. What experience do you have in this field?

Now you can speak about the position you applying for, if there is no reason to say means try close as you can , please don’t try to overcome.

7. What are your expectations in salary?

Can you tell me the range for this position? In most cases, the interviewer, taken off guard, will tell you. If not, say that it can depend on the details of the job.

8. Explain how you would be an asset to this organization?

It gives you a chance to highlight your best points as they relate to the position being discussed. Give a little advance thought to this relationship.

9. Why should we hire you?

Please do not compare with any other candidates in old company and new company to make impress interviewer

Please write your valuable comments, about my blogspot.

NetApp Interview Question

2012-02-22T06:33:00.001-08:00

NetApp Interview Question

How to improve the Netapp storage performance?

There is no direct answer for this question but we shall do it in several way.
If volume/lun present in ATA/SATA harddisk aggregate, then the volume can be migrated to FC/SAS disk aggregate.
For NFS/CIFS instead of accessing from single interface, multi mode vif can be configured to get better bandwidth and fault tolerance.
Always advised to keep aggr/vol utilization below 90%.
Avoid doing multiple volume backup in single point of time.
Aggr/volume/lun reallocation can be done to re–distribute the data to multiple disk for better striping performance.
Schedule scrubbing and deduplication scanning after business hours.
Avoid connecting different types of shelf in a same loop.
Avoid mixing up different speeds of disk and different types of disk in a same aggregate.
Always keep sufficient spare disk to replace incase of disk failure. Because reconstruction time will take more time and cause negative performance.
Keep the advised version of firmware/software which is recommended by netapp.
Better to have nearstore functionality to avoid backing up data from source filer.

Unable to map lun to solaris server, but solaris server side no issue. How to resolve the issue?

FROM STORAGE SIDE:

Verify iscsi/fcp license is added in storage
Verify iscsi/fcp session is logged in from server side
Verify luns are mapped to the corresponding igroup.
Verify whether correct host type is mentioned while creating igroup and lun
Verify whether correct iqn/wwpn number is added to igroup
Verify zoning is properly configured from switch side.

How to create the LUN for solaris server?

lun create –s size –t solaris /vol/vol1/lunname

How to create qtree and provide the security?

Qtree create /vol/vol1/qtreename
Qtree security /vol/vol1/qtree unix|ntfs|mixed

How to copy filer to filer?

ndmpcopy or snapmirror

How to resize the aggregate?

Aggr add agg(name) no.of.disk

How to increase the volume?

Traditional

Vol add vol(name) no.of.disk

Flexiable

Vol size vol(name) +60g

What is qtree?

Qtree are Logical partition of the volume

What is the default snap reserve in aggregate?

5%

What is snapshot?

Copy(read only) of active file system

What are the raid groups netapp supporting?, what is the difference between them?

Raid_dp(double parity,diagonal parity) ,raid4(striping&dedicated parity)

What are the protocols you are using?

Say some protocols like NFS, CIFS, ISCSI and FC

What is the difference between iscsi and fcp?

Iscsi-sending block through(tcp,ip)

Fcp-send through fibre medium

What is the iscsi port number your are using?

860 and 3260

What is the difference between ndmp copy and vol copy?

Ndmp copy –network data management protocol(used for tape backup)

Vol copy – is used to transfer volume to same or another aggr

http://netapplines.blogspot.in/2012/05/comparison-of-vol-copy-ndmpcopy-and.html

What is the difference between ONTAP 7 & 8?

In ONTAP 7 the individual aggregate is limited to maximum of 16 TB. Where ONTAP 8 supports the new 64 bit aggregate and hence the size of the individual aggregate extends to 100 TB.

What are the steps need to perform to configure SnapMirror?

The SnapMirror configuration process consists of the following four steps:

a. Install the SnapMirror license on the source and destination systems: license add <code>

b. On the source, specify the host name or IP address of the SnapMirror destination systems you wish to authorize to replicate this source system.

options snapmirror.access host=dst_hostname1,dst_hostname2

c. For each source volume or qtree to replicate, perform an initial baseline transfer. For volume SnapMirror,

restrict the destination volume first: vol restrict dst_vol

Then initialize the volume SnapMirror baseline, using the following syntax on the destination:

snapmirror initialize -S src_hostname:src_v

oldst_hostname:dst_vol

For a qtree SnapMirror baseline transfer, use the following syntax on the destination:

snapmirror initialize –S src_hostname:/vol/src_vol/src_qtree

dst_hostname:/vol/dst_vol/dst_qtree

d. After the initial transfer completes, set the SnapMirror mode of replication by creating the

/etc/snapmirror.conf file in the destination’s root volume.

For reference:

http://netapplines.blogspot.in/2012/01/snapmirror-schedule-configuration.html

http://netapplines.blogspot.in/2011/11/snapmirror-primary-conf.html

http://netapplines.blogspot.in/2011/11/snapmirror-secondary-conf.html

While doing baseline transfer you’re getting error message. What are the troubleshooting steps you’ll do?

Check both the hosts are reachable by running “ping” command
Check whether the TCP port 10566 & 10000 are open
Check whether the snapmirror license are installed in both and destination

Explain the different types of replication modes.

The SnapMirror Async mode replicates Snapshot copies from a source volume or qtree to a destination

volume or qtree. Incremental updates are based on a schedule or are performed manually using the

snapmirror update command. Async mode works with both volume SnapMirror and qtree SnapMirror.

SnapMirror Sync mode replicates writes from a source volume to a destination volume at the same time it is

written to the source volume. SnapMirror Sync is used in environments that have zero tolerance for data loss.

SnapMirror Semi-Sync provides a middle-ground solution that keeps the source and destination systems more

closely synchronized than Async mode, but with less impact on performance.

How do you configure multiple path in Snapmirror?

Add a connection name line in the snapmirror.conf file
/etc/snapmirror.conf
FAS1_conf = multi (FAS1-e0a,FAS2-e0a) (FAS1-e0b,FAS2-e0b)

Explain how De-Duplication works?

In the context of disk storage, deduplication refers to any algorithm that searches for duplicate data objects (for example, blocks, chunks, files) and discards those duplicates. When duplicate data is detected, it is not retained, but instead a “data pointer” is modified so that the storage system references an exact copy of the data object already stored on disk. This deduplication feature works well with datasets that have lots of duplicated date (for example, full backups).

http://netapplines.blogspot.in/2012/04/deduplication.html

What is the command used to see amount of space saved using deduplication?

df –s <volume name>

Command used to check progress and status of deduplication?

sis status

How do you setup Snapvault Snapshot schedule?

pri> snapvault snap sched vol1 sv_hourly 22@0-22

This schedule is for the home directories volume vol1
Creates hourly Snapshot copies, except 11:00 p.m.
Keeps nearly a full day of hourly copies

What is metadata?

Metadata is defined as data providing information about one or more aspects of the data,

1. Inode file
2. Used block bitmap file
3. Free block bitmap file

How do you shutdown filer through RLM?

telnet “rlm ip address”
RLM_Netapp> system power on

After creating LUN (iSCSI) & mapped the lun to particular igroup, the client not able to access the LUN. What are the trouble shooting steps you take?

Check whether IQN number specified is correct
Check whether the created LUN is in “restrict” mode
Check the iscsi status

In CIFS how do you check who is using most?

Cifs top

How to check cifs performance statistics

cifs stat

What do you do if a customer reports a particular CIFS share is responding slow?

Check the r/w using "cifs stat" & "sysstat -x 1".
If disk & cpu utilization is more then problem is with filer side only.
CPU utilization will be high if more disk r/w time, i.e.,during tapeback up & also during scrub activities.

what is the degraded mode? You have parity for failed disks then why the filer goes to degraded mode?

If the spare disk is not added within 24hours,then filer will be shutdown auomatically to avoid further disk failures and data loss.

Did you ever do ontap upgrade? From which version to which version and for what reason?

Yes i have done ontap upgrade from version 7.2.6.1 to 7.3.3 due to lot of bugs in old version.

How do you create a lun ?

lun create -s <lunsize> -t <host type> <lunpath>

Production Manager?

Production manager will do the planning,co-ordinating and controlling the process.

Performance Manager?

Performance manager will analyses the performance trends of application.systems and services.

How do you monitor the filers?

Using DFM(Data Fabric Manager) or also using SNMP you can monitor the filer.

What are the prerequisites for a cluster?

cluster interconnect cable should be connected.

shelf connect should be properly done for both the controllers

cluster license should be enabled on both the nodes

Interfaces should be properly configured for fail over

cluster should be enabled

What are the scenarios you have for a cluster failover?

If disk shelf power or shelf port is down, then failover will not happen. It cannot access the mail box disk. Mail box disk stores the cluster configuration data.

What is the diff bet cf takeover and cf force takeover?

If partner shelf power is off (metrco cluster), the forcetakover will work else normal takeover will work.

Please write your valuable comments, about my blogspot.

Network Appliance

Upgrading NetApp ONTAP 8.0.1 P7 to 8.1.2 P4

1 Introduction

1.1 Overview

1.2 Purpose

2. Procedure & Prerequisite

3. Pro Ensure that you have checked the following before you perform the upgrade:

Step 1: Make a back up /etc/rc and /etc/hosts

Step 2: Software Download

Step 3: Copy Software onto the filer

Step 4: Install 7.3.2 system file on both the filers.

Step 5: Verify primary kernel is at 7.3.2

Step 6: Takeover Process by Filer 1

Step 7: Giveback Process

Step 8: Complete maintenance checklist on Filer 2

Checking Netapp filer after a panic

Checking Netapp filer after a panic

Snapmirror Transfer Error

what is Netapp raid group and how its working..?

These are type of disks in filler

32 bit aggregate to 64 bit aggregate Migration

32 bit aggregate to 64 bit aggregate Migration

BMC - RLM - SP

CIFS Oplocks - Opportunistic Locks

CIFS Oplocks - Opportunistic Locks

CIFS Oplocks

remove hidden folder in pen drive

Steps creating VFiler

Related Topic

VFILER COMMANDS

Vfiler

Enable Security tab in windows 2003

VFILER COMMANDS

TO CREATE A VFILER UNIT:

TO DESTROY A VFILER:

TO CONFIGURE DISASTER RECOVERY FOR A VFILER:

TO REMOVE RESOURCES FROM A VFILER:

TO MIGRATE A VFILER:

TO MOVE RESOURCES FROM ONE VFILER TO OTHER IS:

To START A VFILER:

TO STOP A VFILER:

TO CHECK THE STATUS OF A VFILER:

TO RUN A COMMAND ON A VFILER:

TO ALLOW USE OF A PROTOCOL ON A VFILER:

TO DISALLOW USE OF A PROTOCOL ON A VFILER:

TO SET NUMBER OF VFILER UNIT:

LICENSING THE VILER:

Related Topic

VFILER COMMANDS

VFILER

Vfiler

Related Topic

VFILER COMMANDS

Steps creating VFiler and Dr

NetApp Maxfiles

FINISHED

All General Commands

General Commands

Roles and Responsibilities in NetApp Storage Admin

Roles and Responsibilities in NetApp Storage Admin

Select some important points

Network Ports for NetApp

FlexClone

FlexClone

Comparison of vol copy, ndmpcopy and dump/restore

Comparison of vol copy, ndmpcopy and dump/restore

Description

vol copy

Ndmp copy

Dump/restore

NDMP Copy

1 NDMP Copy

1.1 Pre-Requisite

1.2 How to run ndmpcopy command

1.3 Problems Faced and Lessons Learnt

Vol Copy

1. Vol Copy

1.1 Prerequisite

1.2 How to use the volcopy command

1.3 Controlling the speed of Volcopy