Sunday, September 27, 2015

Netapp SnapDrive Applicaiton Installation in windows



Netapp snapdrive automate storage provisioning tasks. Back up and restore business-critical data in seconds with integrated NetApp Snapshot technology. Add more storage as needed to your physical and virtual environments and eliminate the need to preallocate storage resources based on forecasted demand.

SnapDrive:

  • Provides continuous data access across frameworks
  • Enables server administrators to self-manage data
  • Improves efficiency by automating provisioning
  • Leverages the advanced capabilities of the NetApp clustered Data ONTAP operating system
  • Enhances data reliability through rapid file system- and application-consistent backup and restore functions and disaster recovery
SnapDrive can be used in multiple platform such as Linux, Unix, AIX and windows platforms Now we are going to see the installation of snapdrive in windows

Prerequisites:

  • Windows Operating system 2008, 2008-R2 and 2012 is required
  • .Net frame work 3.5 OR 4.0 is required
  • Install DSM 4.0 OR above
  • Windows Hotfixes are required before you install the SnapDrive For windows 2012 install – HotFix 2859162. If it is 2008 and 2008-R2 install Hotfixes 2522766, 2528357, 2494016, 2520235, 2531907, 974930
  • Install PowerShell 2.0 Or above
  • Install Netapp windows host utilities kit 6.0.2 or above
  • Create service account with required privileges to execute commands in Filers

Additional licenses you can enable on your storage system

  • iSCSI, Fibre Channel, Fibre Channel over Ethernet, or Virtual Fibre Channel
  • SnapRestore (required for restore operations)
  • SnapMirror
  • FlexClone (required for persistent mount operations)
  • SnapVault
  • MultiStore
  • SnapManager products

Now download the SnapDrive application from Netapp Support site, Double click on setup file



double click on the setup file
Click Next

  • Storage system licensing enables you to execute SnapDrive operations only on a storage system that has the SnapDrive license installed.
  • Host-side licensing enables you to execute SnapDrive on any SnapDrive instance on your host system.
select the option as you license permits Click Next



Provide your user name and organization details and Click Next


If the server you are installing SnapDrive on is a virtual machine which is part of Vmware vCenter and you wish to use the Fiber Channel HBA’s or iSCSI initiators from the ESX hosts, click Enable VirtualCenter or ESX Server Settings and enter in the IP address, user name (with admin rights on vcenter) and password. If the server you’re installing SnapDrive on is a physical machine, don’t Enable VirtualCenter integration and just Click Next.

 here you have to provide your SERVICE ACCOUNT details and password. Then Click Next



Enter the details of your Netapp filer Click Next

Provide details and Click Next


If you dont want to specify the protocol then Click Next
click Next


Click Install

Click Finish

Your Installation of SnapDrive application is Done..!!



Wednesday, September 23, 2015

NSCA examp pratice paper


1.If you change the setting for the option cifs.neg_buf_size, you need to terminate CIFS on the

storage appliance and do a restart for the changes to take effect.


A.True

B.False


Correct:A

2.If the client is a CIFS client, locks are __________.

A.advisory

B.mandatory

C.ordered

D.optional

Correct:B

3.To view per client NFS statistics on the storage appliance, options nfs.per_client_stats.enable

must be turned on.

A.True

B.False

Correct:A

4.Three methods of creating a LUN are: *lun setup *lun map *FilerView

A.True

B.False

Correct:A

5.Applications, such as databases, running on NAS or iSCSI or FC SAN must be

__________________. A.prepared for snapshots by flushing buffers to disk and momentarily suspending activity.

B.disconnected from their storage resources during the snapshot.

C.using dynamic multipathing during a backup.

D.mirrored with a host-based volume manager to be backed-up.

Correct:A

6.To export volumes and directories automatically on reboot, include them in the /etc/exports file.

A.True

B.False

Correct:A

7.Using the output below, a co-worker determined that these are type "Solaris" LUNs. What would

your determination be? lun show -m LUN pathMapped to LUN ID

--------------------------------------------------- /vol/vol1/lun0 solaris-igroup0 0 /vol/vol1/lun1 solaris-igroup1


0 /vol/vol1/qtree1/lun2 solaris-igroup2 0 /vol/vol1/qtree1/lun3 solaris-igroup3 0

A.These are type "Solaris" LUNs.

B.These are NFS LUNs, but the exact OS cannot be determined.

C.Not enough information is given here. Run the lun show -v command to get the information requested.

D.Not enough information is given here. Run the lun map command to get the information requested.

Correct:C

8.Which one of the following will enable "symlink_strict_security"?

A.options cifs.symlink_strict_security on

B.cifs shares -change -symlink_strict_security

C.options symlink_strict_security=true 2 / 4

D.options symlink_strict_security=on

Correct:B

9.To configure a storage system as a member of an active directory, the time on the storage system must be synchronized with the time on the Domain Controller.

A.True

B.False

Correct:A

10.The writeable snapshot that is created for a LUN clone depends on ___________.

A.mirroring.

B.the snapshot taken at the time the clone was created.

C.exclusive access to the volume.

D.the data in the original LUN not changing.

Correct:B

11.Which command is the most appropriate for troubleshooting a multiprotocol authentication problem?

A.wcc

B.rdfile /etc/rc

C.priv set advanced

D.sysstat 1

Correct:A

12.A quota target can be defined as _______________.

A.the maximum amount of disk space in a volume.

B.the maximum number of files in a disk.

C.a user, group, or qtree to which a quota is applied.

D.a specific disk space threshold.

Correct:C

13.Which three are used for creating LUNs on the storage appliance? (Choose 3)

A.lun create

B.lun setup

C.FilerView

D.lun config

Correct:A B C

14.What is the outcome of this command? lun create -b /vol/vol2/.snapshot/testsnap/lun0

/vol/vol2/lun0.clone


A.It creates a duplicate of the clone process of lun0.

B.It creates a clone of the writeable snapshot of lun0.

C.It creates a writeable snapshot of lun0.

D.It creates a snapshot "testsnap" of vol2.

Correct:C

15.Which security method encrypts the data?

A.IPSec

B.CHAP

C.LUN masking

D.Header and Data Digests 3 / 4

Correct:A

16.____________ is the default cfmode for new installations of Data ONTAP 7.2.

A.single image

B.mixed

C.partner

D.dual fabric

Correct:A

17.Which command would you use to verify that the iSCSI service is running?

A.license add iSCSI

B.iscsi service

C.iscsi status

D.iscsi protocol

Correct:C

18.If you believe you have a FC SAN performance problem, which NetApp utility or command would gather both your Solaris host and storage appliance data for analysis?

A.poststat

B.perfstat

C.prestat

D.sio_ntap.exe

Correct:B

19.What is the definition of the cifs setup command?

A.It displays the mount point of all shared directories.

B.It displays the names of all mounted directories on the storage system.

C.It displays the prompts for CIFS configuration information.

D.It displays a list of the users on the storage system.

Correct:C

20.UNIX allow file access based on __________.

A.GID or UID and UNIX permissions.

B.NT ACLs and UNIX permissions.

C.NT ACLs and SID.

D.GID or UID and ACLs.

Correct:A



Please provide your valuable comments ... Is this useful..!!

Sunday, September 20, 2015

Netapp Cluster Mode commands cheat sheet - Netapp Notes by ARK

MISC

set -privilege advanced (Enter into privilege mode)
set -privilege diagnostic (Enter into diagnostic mode)
set -privilege admin (Enter into admin mode)
system timeout modify 30 (Sets system timeout to 30 minutes)
system node run – node local sysconfig -a (Run sysconfig on the local node)
The symbol ! means other than in clustered ontap i.e. storage aggregate show -state !online (show all aggregates that are not online)
node run -node -command sysstat -c 10 -x 3 (Running the sysstat performance tool with cluster mode)
system node image show (Show the running Data Ontap versions and which is the default boot)
dashboard performance show (Shows a summary of cluster performance including interconnect traffic)
node run * environment shelf (Shows information about the Shelves Connected including Model Number)

DIAGNOSTICS USER CLUSTERED ONTAP

security login unlock -username diag (Unlock the diag user)
security login password -username diag (Set a password for the diag user)
security login show -username diag (Show the diag user)

SYSTEM CONFIGURATION BACKUPS FOR CLUSTERED ONTAP

system configuration backup create -backup-name node1-backup -node node1 (Create a cluster backup from node1)
system configuration backup create -backup-name node1-backup -node node1 -backup-type node (Create a node backup of node1)
system configuration backup upload -node node1 -backup node1.7z -destination ftp://username:password@ftp.server.com (Uploads a backup file to ftp)

LOGS

To look at the logs within clustered ontap you must log in as the diag user to a specific node
set -privilege advanced
systemshell -node
username: diag
password:
cd /mroot/etc/mlog
cat command-history.log | grep volume (searches the command-history.log file for the keyword volume)
exit (exits out of diag mode)

SERVICE PROCESSOR

system node image get -package http://webserver/306-02765_A0_SP_3.0.1P1_SP_FW.zip -replace-package true (Copies the firmware file from the webserver into the mroot directory on the node)
system node service-processor image update -node node1 -package 306-02765_A0_SP_3.0.1P1_SP_FW.zip -update-type differential (Installs the firmware package to node1)
system node service-processor show (Show the service processor firmware levels of each node in the cluster)
system node service-processor image update-progress show (Shows the progress of a firmware update on the Service Processor)

CLUSTER

set -privilege advanced (required to be in advanced mode for the below commands)
cluster statistics show (shows statistics of the cluster – CPU, NFS, CIFS, FCP, Cluster Interconnect Traffic)
cluster ring show -unitname vldb (check if volume location database is in quorum)
cluster ring show -unitname mgmt (check if management application is in quorum)
cluster ring show -unitname vifmgr (check if virtual interface manager is in quorum)
cluster ring show -unitname bcomd (check if san management daemon is in quorum)
cluster unjoin (must be run in priv -set admin, disjoins a cluster node. Must also remove its cluster HA partner)
debug vreport show (must be run in priv -set diag, shows WAFL and VLDB consistency)
event log show -messagename scsiblade.* (show that cluster is in quorum)

NODES

system node rename -node -newname
system node reboot -node NODENAME -reason ENTER REASON (Reboot node with a given reason. NOTE: check ha policy)

FLASH CACHE

system node run -node * options flexscale.enable on (Enabling Flash Cache on each node)
system node run -node * options flexscale.lopri_blocks on (Enabling Flash Cache on each node)
system node run -node * options flexscale.normal_data_blocks on (Enabling Flash Cache on each node)
node run NODENAME stats show -p flexscale (fashcache configuration)
node run NODENAME stats show -p flexscale-access (display flash cache statistics)
 FLASH POOL
storage aggregate modify -hybrid-enabled true (Change the AGGR to hybrid)
storage aggregate add-disks -disktype SSD (Add SSD disks to AGGR to begin creating a flash pool)
priority hybrid-cache set volume1 read-cache=none write-cache=none (Within node shell and diag mode disable read and write cache on volume1)

FAIL-OVER

storage failover takeover -bynode (Initiate a failover)
storage failover giveback -bynode (Initiate a giveback)
storage failover modify -node -enabled true (Enabling failover on one of the nodes enables it on the other)
storage failover show (Shows failover status)
storage failover modify -node -auto-giveback false (Disables auto giveback on this ha node)
storage failover modify -node -auto-giveback enable (Enables auto giveback on this ha node)
aggregate show -node NODENAME -fields ha-policy (show SFO HA Policy for aggregate)

AGGREGATES

aggr create -aggregate -diskcount -raidtype raid_dp -maxraidsize 18 (Create an AGGR with X amount of disks, raid_dp and raidgroup size 18)
aggr offline | online (Make the aggr offline or online)
aggr rename -aggregate -newname
aggr relocation start -node node01 -destination node02 -aggregate-list aggr1 (Relocate aggr1 from node01 to node02)
aggr relocation show (Shows the status of an aggregate relocation job)
aggr show -space (Show used and used% for volume foot prints and aggregate metadata)
aggregate show (show all aggregates size, used% and state)
aggregate add-disks -aggregate -diskcount (Adds a number of disks to the aggregate)
reallocate measure -vserver vmware -path /vol/datastore1 -once true (Test to see if the volume datastore1 needs to be reallocated or not)
reallocate start -vserver vmware -path /vol/datastore1 -force true -once true (Run reallocate on the volume datastore1 within the vmware vserver)

DISKS

storage disk assign -disk 0a.00.1 -owner (Assign a specific disk to a node) OR
storage disk assign -count -owner (Assign unallocated disks to a node)
storage disk show -ownership (Show disk ownership to nodes)
storage disk show -state broken | copy | maintenance | partner | percent | reconstructing | removed | spare | unfail |zeroing (Show the state of a disk)
storage disk modify -disk NODE1:4c.10.0 -owner NODE1 -force-owner true (Force the change of ownership of a disk)
storage disk removeowner -disk NODE1:4c.10.0 -force true (Remove ownership of a drive)
storage disk set-led -disk Node1:4c.10.0 -action blink -time 5 (Blink the led of disk 4c.10.0 for 5 minutes. Use the blinkoff action to turn it off)

VSERVER

vserver setup (Runs the clustered ontap vserver setup wizard)
vserver create -vserver -rootvolume (Creates a new vserver)
vserver show (Shows all vservers in the system)
vserver show -vserver (Show information on a specific vserver)

VOLUMES

volume create -vserver -volume -aggregate -size 100GB -junction-path /eng/p7/source (Creates a Volume within a vserver)
volume move -vserver -volume -destination-aggregate -foreground true (Moves a Volume to a different aggregate with high priority)
volume move -vserver -volume -destination-aggregate -cutover-action wait (Moves a Volume to a different aggregate with low priority but does not cutover)
volume move trigger-cutover -vserver -volume (Trigger a cutover of a volume move in waiting state)
volume move show (shows all volume moves currently active or waiting. NOTE: You can only do 8 volume moves at one time, more than 8 and they get queued)
system node run – node vol size 400g (resize volume_name to 400GB) OR
volume size -volume -new-size 400g (resize volume_name to 400GB)
volume modify -vserver -filesys-size-fixed false -volume (Turn off fixed file sizing on volumes)

LUNS

lun show -vserver (Shows all luns belonging to this specific vserver)
lun modify -vserver -space-allocation enabled -path (Turns on space allocation so you can run lun reclaims via VAAI)
lun geometry -vserver path /vol/vol1/lun1 (Displays the lun geometry)

NFS

vserver modify -4.1 -pnfs enabled (Enable pNFS. NOTE: Cannot coexist with NFSv4)

FCP

storage show adapter (Show Physical FCP adapters)
fcp adapter modify -node NODENAME -adapter 0e -state down (Take port 0e offline)
node run fcpadmin config (Shows the config of the adapters – Initiator or Target)
node run -t target 0a (Changes port 0a from initiator or target – You must reboot the node)

CIFS

vserver cifs create -vserver -cifs-server -domain (Enable Cifs)
vserver cifs share create -share-name root -path / (Create a CIFS share called root)
vserver cifs share show
vserver cifs show

SMB

vserver cifs options modify -vserver -smb2-enabled true (Enable SMB2.0 and 2.1)

SNAPSHOTS

volume snapshot create -vserver vserver1 -volume vol1 -snapshot snapshot1 (Create a snapshot on vserver1, vol1 called snapshot1)
volume snapshot restore -vserver vserver1 -volume vol1 -snapshot snapshot1 (Restore a snapshot on vserver1, vol1 called snapshot1)
volume snapshot show -vserver vserver1 -volume vol1 (Show snapshots on vserver1 vol1)

DP MIRRORS AND SNAPMIRRORS

volume create -vserver -volume vol10_mirror -aggregate -type DP (Create a destinaion Snapmirror Volume)
snapmirror create -vserver -source-path sysadmincluster://vserver1/vol10 -destination -path sysadmincluster://vserver1/vol10_mirror -type DP (Create a snapmirror relationship for sysadmincluster)
snapmirror initialize -source-path sysadmincluster://vserver1/vol10 -destination-path sysadmincluster://vserver1/vol10_mirror -type DP -foreground true (Initialize the snapmirror example)
snapmirror update -source-path vserver1:vol10 -destination-path vserver2:vol10_mirror -throttle 1000 (Snapmirror update and throttle to 1000KB/sec)
snapmirror modify -source-path vserver1:vol10 -destination-path vserver2:vol10_mirror -throttle 2000 (Change the snapmirror throttle to 2000)
snapmirror restore -source-path vserver1:vol10 -destination-path vserver2:vol10_mirror (Restore a snapmirror from destination to source)
snapmirror show (show snapmirror relationships and status)
NOTE: You can create snapmirror relationships between 2 different clusters by creating a peer relationship

SNAPVAULT

snapmirror create -source-path vserver1:vol5 -destination-path vserver2:vol5_archive -type XDP -schedule 5min -policy backup-vspolicy (Create snapvault relationship with 5 min schedule using backup-vspolicy)
NOTE: Type DP (asynchronous), LS (load-sharing mirror), XDP (backup vault, snapvault), TDP (transition), RST (transient restore)

NETWORK INTERFACE

network interface show (show network interfaces)
network port show (Shows the status and information on current network ports)
network port modify -node * -port -mtu 9000 (Enable Jumbo Frames on interface vif_name>
network port modify -node * -port -flowcontrol-admin none (Disables Flow Control on  port data_port_name)
network interface revert * (revert all network interfaces to their home port)

INTERFACE GROUPS

ifgrp create -node -ifgrp -distr-func ip -mode multimode (Create an interface group called vif_name on node_name)
network port ifgrp add-port -node -ifgrp -port (Add a port to vif_name)
net int failover-groups create -failover-group data__fg -node -port (Create a failover group – Complete on both nodes)
ifgrp show (Shows the status and information on current interface groups)
net int failover-groups show (Show Failover Group Status and information)

ROUTING GROUPS

network interface show-routing-group (show routing groups for all vservers)
network routing-groups show -vserver vserver1 (show routing groups for vserver1)
network routing-groups route create -vserver vserver1 -routing-group 10.1.1.0/24 -destination 0.0.0.0/0 -gateway 10.1.1.1 (Creates a default route on vserver1)
ping -lif-owner vserver1 -lif data1 -destination www.google.com (ping www.google.com via vserver1 using the data1 port)

DNS

services dns show (show DNS)

UNIX

vserver services unix-user show
vserver services unix-user create -vserver vserver1 -user root -id 0 -primary-gid 0 (Create a unix user called root)
vserver name-mapping create -vserver vserver1 -direction win-unix -position 1 -pattern (.+) -replacement root (Create a name mapping from windows to unix)
vserver name-mapping create -vserver vserver1 -direction unix-win -position 1 -pattern (.+) -replacement sysadmin011 (Create a name mapping from unix to windows)
vserver name-mapping show (Show name-mappings)

NIS

vserver services nis-domain create -vserver vserver1 -domain vmlab.local -active true -servers 10.10.10.1 (Create nis-domain called vmlab.local pointing to 10.10.10.1)
vserver modify -vserver vserver1 -ns-switch nis-file (Name Service Switch referencing a file)
vserver services nis-domain show

NTP

system services ntp server create -node -server (Adds an NTP server to node_name)
system services ntp config modify -enabled true (Enable ntp)
system node date modify -timezone (Sets timezone for Area/Location Timezone. i.e. Australia/Sydney)
node date show (Show date on all nodes)

DATE AND TIME

timezone -timezone Australia/Sydney (Sets the timezone for Sydney. Type ? after -timezone for a list)
date 201307090830 (Sets date for yyyymmddhhmm)
date -node (Displays the date and time for the node)

CONVERGED NETWORK ADAPTERS (FAS 8000)

ucadmin show -node NODENAME (Show CNA ports on specific node)
ucadmin -node NODENAME -adapter 0e -mode cna (Change adapter 0e from FC to CNA. NOTE: A reboot of the node is required)

PERFORMANCE

show-periodic -object volume -instance volumename -node node1 -vserver vserver1 -counter total_ops|avg_latency|read_ops|read_latency (Show the specific counters for a volume)
statistics show-periodic 0object nfsv3 -instance vserver1 -counter nfsv3_ops|nfsv3_read_ops|nfsv3_write_ops|read_avg_latency|write_avg_latency (Shows the specific nfsv3 counters for a vserver)
sysstat -x 1 (Shows counters for CPU, NFS, CIFS, FCP, WAFL)

Disclaimer:

All the tutorials included on this site are performed in a lab environment to simulate a real world production scenario. As everything is done to provide the most accurate steps to date, we take no responsibility if you implement any of these steps in a production environment.

Please provide your valuable comments ...

Could Not Complete Giveback Because of Non-CA Locks on Volume – Netapp C Mode


Error: Could Not Complete Giveback Because of Non-CA Locks on Volume


I came across this error (Could Not Complete Giveback Because of Non-Ca Locks on Volume) during a failover and give back on a HA pair. Performing the manual failover was fine and all aggregates failed over correctly, however on the failback the root volumes were successful but some SFO aggregates contained an error.

First up I saw the basic error during a giveback using the command:


ArkClus::> storage failover show

I then went to look into the logs by typing:

ArkClus::> log show (the newest logs are always at the top of the list)

These are the exact messages from the log:


5/28/2015 21:47:21  NODE1        ERROR         sfo.giveback.failed: Giveback of aggregate aggr1 failed due to Giveback was vetoed..

5/28/2015 21:47:21  NODE1        ERROR         sfo.sendhome.subsystemAbort: The giveback operation of ‘aggr1’ was aborted by ‘lock_manager’.

5/28/2015 21:47:21  NODE1        ERROR         lmgr.gb.nonCA.locks.exist: Could not complete giveback because of non-CA locks on volume volume1@vserver:2345673-5898-11e3-83fb-123478563412.


The volume named volume1 appeared to have a locked cifs session and was preventing the aggregate to failback.
Non-CA Locks on Volume Fix

There are 3 options to fix this:

  •     Wait and then try to perform the give back again
  •     Disable cifs on the vserver to remove the lock
  •     Use the option -override-vetoes true. Take not that using this option might drop the cifs sessions momentarily until the aggregate has failed back. 

The full command would be:

ArkClus::> failover giveback -ofnode node1 -orverride-vetoes true
Monitor the giveback with the command:

ArkClus::> storage failover giveback

Once the failback is successful, lastly check that the cluster ring is all in sync:

ArkClus::> set diag

ArkClus::*> cluster ring show

Please provide your valuable comments ....

 

Saturday, September 19, 2015

Cluster Mode Basic commands - Top Commands - Netapp Notes by ARK


In this article we are going to see basic commands of Netapp Cluster mode cd, top, up, set, redo and man usage explanation.

CD Command Usage and Explanation

The cd command changes the current working directory of the command prompt to the
directory you specify. Using this command with value “….” will change the directory path to the mentioned value.




cd "storage aggregate"

if you observe above screenshot i have changed the directory path to “volume snapshot”. Using this command we can change the directory path any level directly.

TOP and UP Command usage and Explanation

The top command changes the current working directory of the command prompt to the
top-level command directory


The UP command will change the current directory to up one level, if you mention (..) it will go two level up in hierarchy.

SET Command usage and explanation

using set command you can change the privilege level of access.

admin – Used for routine system management commands advanced – Used for infrequent, dangerous, or complicated commands diagnostic – Used for detailed diagnostic commands that are used only by support
personnel

set -privilege advanced
set -privilege admin



REDO and MAN Command Usage and Explanation

 

redo command will execute the previously executed command without typing total command


 man command will give the command usage and its options with details



 Please provide your valuable comments below ..............

 

Thursday, September 17, 2015

Configuring Netapp Cluster Node - Netapp Notes by ARK


Yet your home using an Netapp Simulator you can build your own Netapp environment to practice as a live environment. 

in order to build Netapp lab environment Download Simulator .

Booting the DataONTAP Simulator 1st Node

Open the simulator vSphere client console, press Ctrl-C for the Boot Menu when displayed on the screen.

 Once the boot menu is loaded, select  Opt 4 ” Clean configuration and initialize all disks.”
 



At the zero disk, reset config and install a new file system prompt, type “yes” or “y” and press Enter.  Confirm the selection and press enter. 

The simulator VM restarts and will continue the initialization process.
 


Do not interrupt this process as it might result in corruption of the simulator disks.
Creating the Cluster

  
At the “Welcome to the cluster setup wizard” screen you will be prompted to create or join a cluster.  Since this is the first node in the cluster type create and press enter.
 


When prompted “Do you intend for this node to be used as a single node cluster”, continue with the default no and press enter.
 


Allow the cluster network to use network switches and press enter. 

When creating the cluster interfaces (e0a & e0b) you have the option of keeping the system defaults or changing the network defaults during the cluster configuration.
 


Once the cluster interfaces are created, enter the name of your cluster & license key(s). 

Create a cluster admin password.

Enter the required network information for the cluster management interface


Enter the required network information for the node management interface

Cluster creation is now complete

 

To validate your cluster setup via CLI, log in and run “cluster show.” 
 

Stay tune for Next steps, How we can add other node to the cluster.





Thanks for visiting the Site... Please do comment your feedback about this article



Tuesday, September 15, 2015

How to join Netapp Filer to domain - Netapp Notes by ARK

Why we have to join Netapp filer to Active  Directory

  1.  Adding removing users to Netapp filer made easy
  2.  Configuring and providing access to CIFS shares
  3.  Integrating with your windows server will provide you an handy to automate regular jobs
  4.  single sign on will simplify your login using active directory
The process itself is very simple but there are a couple of things to keep in mind regarding the time so i thought it would be nice to share them.

Before starting, here’s a bit of background on why clock is very important: Active Directory authentication is based on a protocol called Kerberos, which use a ticketing system to grant access, the system time is very important if ticket is waiting for more then specified time it will expires and authentication will fail. 

Verify the date and time before going to join the Netapp filer to domain. 

 ARK> date
Tue Sep 15 02:03:49 PDT 2015

if you time is not in sync with the LDAP Server then make change using date command

ARK>date 201509150254
Warning: syncing time to an external time source which will eventually override the time set by the date command.


201509150254 which is (YYYYMMDDhhmm)

And then we need to configure the NTP server to keep the time in sync with the Domain Controllers:

ARK> options timed.enable off
ARK> options timed.proto ntp
ARK> options timed.servers
ARK> options timed.max_skew 5m
ARK> options timed.enable on


Now you can join the Netapp filer to domain using cifs setup command

ARK> cifs setup             
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)? [2]: 2
        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 []:
#Enter your root password
Retype the password:
#Enter your root password
The default name for this CIFS server is 'ARK'.
Would you like to change this name? [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]: 1
What is the name of the Active Directory domain? [arkit.co.in]: arkit.co.in
        In order to create an Active Directory machine account for the filer,
        you must supply the name and password of a Windows account with
        sufficient privileges to add computers to the arkit.co.in domain.
Enter the name of the Windows user [Administrator@arkit.co.in]: Administrator@arkit.co.in
Password for Administrator@arkit.co.in:
CIFS - Logged in as Administrator@arkit.co.in.
        The user that you specified has permission to create the filer's
        machine account in several (2) containers. Please choose where you
        would like this account to be created.

(1) CN=computers
(2) OU=Domain Controllers
(3) None of the above


Selection (1-3)? [1]: 1
CIFS - Starting SMB protocol...
        It is highly recommended that you create the local administrator
        account (ARKadministrator) for this filer. This account allows
        access to CIFS from Windows when domain controllers are not
        accessible.

Do you want to create the ARKadministrator account? [y]:
Enter the new password for ARKadministrator:

Retype the password:
        Currently the user "ARKadministrator" and members of the group
        "HANDS-ONDomain Admins" have permission to administer CIFS on this
        filer. You may specify an additional user or group to be added to the
        filer's "BUILTINAdministrators" group, thus giving them
        administrative privileges as well.

Would you like to specify a user or group that can administer CIFS? [n]: n
Welcome to the arkit.co.in (ARK) Active Directory(R) domain.

CIFS local server is running.


Now you can integrate Netapp filer to your computer management by connecting to other computer

Please provide your valuable comments ...




Sunday, September 13, 2015

Know Storage limits - LUNs Volumes Aggregates RAID-Groups RAID-Size Disks FlexClone - Netapp Notes by ARK


RAID Groups
Maximum RAID Groups supported by Netapp is 150 per aggregate
Maximum RAID Groups supported by Netapp is 400 per System

RAID Group Size

RAID-DP 
Default size SATA/BSAS/FSAS/MSATA/ATA: 14, FC/SAS: 16, SSD: 23
Maximum size SATA/BSAS/FSAS/MSATA/ATA: 20, FC/SAS: 28, SSD: 28

RAID4
Default size SATA/BSAS/FSAS/MSATA/ATA: 7, FC/SAS/SSD: 8 
Maximum size SATA/BSAS/FSAS/MSATA/ATA: 7, FC/SAS/SSD: 14

RAID0
Default 8
Maximum 26

Aggregate Limitations
32 bit aggregate will support maximum of 16TB in size
64 bit Aggregate will support maximum of 100TB size

Volume Limitations
Flex Volumes 32bit 16TB
Flex Volumes 64bit 100TB
Maximum Qtrees for Volume is 4995
Maximum snapshots for volume is 255
FlexClone volumes maximum 499
Flexvol Volumes 200 per aggregate dependent on Netapp Hardware model

Please provide your valuable comments.....







Netapp Hardware Interview Questions and Answers - Netapp Notes by ARK

* Netapp Hardware Interview questions and answers *

1. What is NVRAM..?
Ans:- Non-volatile battery-backed memory (NVRAM) is used for write caching.

2. Do you know how data is written to the disk in Netapp.? Please explain..?
Ans:- As soon as the write to NVRAM is confirmed, the storage appliance acknowledges the write as completed to the client machine. At pre-determined triggers, this buffered write data is processed from storage device memory through the Write Anywhere File Layout (WAFL) and RAID layers and written to disk.

3. What is SP/RLM/BMC..?
Ans:- 
SP - Service processor
 SP monitors the system temperatures, voltages, currents, and fan speeds. When an environmental sensor has reached an abnormal condition, the SP logs the abnormal readings, notifies Data ONTAP of the issue, and sends alerts and 'down system' notifications as necessary through an AutoSupport message, regardless of whether the storage system can send AutoSupport messages

RLM - Remote LAN Module
The RLM provides remote node management capabilities, including remote access, monitoring, troubleshooting, logging, and alerting features

BMC -  Baseboard management console
The AutoSupport settings are used for sending the alerts through e-mail over the BMC LAN interface.

4. What is difference between FAS and V-Series..?
Ans:- 
FAS - Fibre attached Storage
V-Series - Virtualized  Series 

FAS is used in Single node and HA pair configuration
V-Series is used when want to virtualize with third party Storage system

5. What is difference between 7-mode and C-mode..?
Ans:- 
7-mode either single node Or two controllers clustered for HA. Single node will support for single namespace. One controller will work as a single node. 

C-mode either single controller "pair" Or multi controller "pairs" connected as a clustered. Each VServer will work as a single entity. It will support for multi namespaces 

 6. What is the maximum capacity of volume in 7-mode 32bit..?
Ans:- 16TB

7. How many disk types can Netapp support..?
Ans:-   FC, SAS, SSD, Near Line SAS and SATA

8. How to check your Netapp serial number..?
Ans:- sysconfig -a

9. how to determine that FC port is working an which mode..?
Ans:- using fcadmin command we can verify

10. How to verify whether all the disk shelfs for connected in redundant..?
Ans:- sysconfig -d and storage show disk  




Related Links

Interview Questions and Answers - Part-1

Interview Questions and Answers - Part-2 

 

if you have more questions please comment...

Saturday, September 12, 2015

Data ONTAP 8 Cabling - Single Node - HA Pair and Cluster Interconnect - Netapp Notes by ARK


In this article i am going to explain about the Netapp Storage Hardware single Node, HA Nodes and Cluster interconnect connectivity.
Netapp Hardware

1. SAS Ports:   

On board serial attached SCSI ports used to connect SAS Disk shelves. 0a and 0b port numbers

2. 10G Ports / FC Ports

These ports are used connect partner controller.
FC ports are used to connect FC disk shelves  

3. Ethernet 1G Data ports

These ports are used connect general data connectivity

 4. Ethernet Management Port / ACP Port

This port is used to connect for management. Service processor connectivity.  
When controller power is down used to connect alternate controller path

5. Power Supply

To connect power supply

6. Serial connectivity

When you want to connect to the controller terminal connection.


SAS Cable Connectivity

In above single node SAS connectivity diagram, We are connecting the SAS cabling with two stacks.

For stack one we have to connect SAS port A to first shelf IO module A. You can close the SAS stack1 by attaching the 5d SAS controller port to IO module of disk shelve last port.

In the same way as like stack1 we have to connect stack2 as shown in diagram. Each stack disk shelve number will be unique.

ACP Connectivity
Now connecting the ACP path using CAT6 Ethernet cables, as shown in above picture

Management Port connectivity
In a initialization faze we have to connect serial and management cable to configure the storage system, later you can disconnect serial console cable.
Single Node Cabling connectivity
It's looks like a messy when you look at the picture but in real single node connectivity we follow the same.

In above picture we are connecting Management port to Management network using Ethernet switch. We connected only single port to the managment network because if management port is not accessible still no matter storage system will service the data to the clients.

Data network we have connected 4 10G ports using two modules because this ports serves the data to the clients its may be CIFS, NFS and iSCSI traffic, if any port is down you should have a alternate path to the serve the continuous data to the clients.

i hope you understand the cabling for single node Netapp controller.

Coming up article is HA Pair connectivity and Cluster interconnect


Please provide your feedback about this article. Your feedback will help me to improve the content quality. Keeping an one line of comment will not cost you but it will help others.


Enter your email address:



Clustered Data ONTAP Administration Questions - Netapp Notes by ARK