How to rename Qtree in NetApp

To rename qtree in NetApp filers, we can follow below procedure.

• 1st make sure your volumes is in R/W state. If volume is snapmirrored and is in R/O mode... execute below procedure .

1. Quiesce snapmirror (snapmirror quiesce -S sourcefiler:/vol/vol1/qtree1 destfiler:/vol/vol1/qt1)
2. Break snapmirror  (snapmirror break destfile:/vol/vol1/qt1)
3. Now you can rename qtree, but not with ADMIN mode, we can do only in ADVANCED mode.
4. priv set advanced
5. qtree rename old qtree path  new atree path (qtree rename /vol/vol1/qt1 vol/vol1/qt2)
6. Once you rename qtree, make sure you also change share names.
7. Then you can resync snapmirror with source filer (snapmirror resync)

If qtrees belongs to volumes which are in specific vfilers, just add "vfiler run vfilername" before executing commands.

EMC SYMCLI commands.

For our convince let's assume Array SID as "000001234" 

symcfg

• symcfg list - A brief description of the all connected Symmetrix boxes.
• symcfg -sid 1234 remove - Remove the array 1234 from symcfg list.
• symcfg -sid 1234 list -lockn all - List all the external locks held in Symmetrix array 1234.
• symcfg -sid 1234 -lockn 15 release -force - Release the lock 15 held on array 1234 .
• symcfg -sid 1234 list -v - Displays detailed information about the Symmetrix Array 1234.
• symcfg -sid 1234 -dir 4a -p 0 list -addr -avail - List the LUN information / availability of lun ids on port 4a0 in array 1234 .
• symcfg -sid 1234 list -rdfg all - List details about all the rdf groups in array.
• symcfg -sid 1234 list -rdfg 3 - List details about rdf group 3 .
• symcfg -sid 1234 list -rdfg all -dynamic - List details about all the dynamic rdf groups in array .
• symcfg -sid 1234 list -rdfg all -static - List details about all the static rdf groups in array .
• symcfg -sid 1234 list -ra all - List all RA ports with details like rdfg number , remote array sid and online status.
• symcfg discover - Scans all the devices in hosts looking for new symmetrix devices and rebuilds the symmetrix configuration database .

symdev

• symdev -sid 1234 list - List all devices in symmetrix 1234.
• symdev -sid 1234 list -noport - List the devices which are not mapped to any ports.
• symdev -sid 1234 list -noport -meta - List all unmapped meta devices .
• symdev -sid 1234 list -dynamic - List all devices whose dyn_rdf attribute set .
• symdev -sid 1234 list -hotspare - Checks whether hotspare invoked in the array .
• symdev -sid 1234 show ABC - show the detailed information about devioce ABC.
• symdev -sid 1234 write_disable ABC -SA all - Write disable the device ABC from through all directors.
• symdev -sid 1234 not_ready ABC -SA all - Not ready the device ABC from through all directors.

symmaskdb

• symmaskdb -sid 1234 -dev ABC list assign - List the masking details of the dev ABC .
• symmaskdb -sid 1234 -wwn xxxxxxx list devs - List the devices masked to given wwn number .
• symmaskdb -sid 1234 -awwn hba_alias list devs - List the devices masked to given alias hba name .

symmask

• symmask list hba - List HBA details of the host.
• symmask -sid 1234 -dir 4a -p 0 list logins - List out wwns logged through port 4a0 .
• symmask -sid 1234 list logins -wwn xxx - Check whether wwn xxx logged in to any of the FAs on array 1234.
• symmask -sid 1234 refresh - Refresh the VCM Data Base after a masking and unmasking operation.
• symmask -sid 1234 -wwn xxxx -dir 4a -p 0 add devs ABC,ABD - Mask the devices ABC and ABD to given wwn in 1234 arrray .
• symmask -sid 1234 -wwn xxxx -dir 4a -p 0 remove devs ABC,ABD - Unmask the devices ABC and ABD from given wwn in 1234 arrray .

symdg

• symdg -sid 1234 list - List device groups which include the devices from array 1234.
• symdg create mydg -type rdf1 - Create device group mydg of rdf1 type .
• symdg show mydg - Shows members/details of mydg.
• symdg rename mydg yourdg - Renames the mydg to yourdg.
• symdg delete mydg -force - Delete device group mydg.

symld

• symld -g mydg -sid 1234 add dev ABC DEV006 - Add the RDF device ABC to device group mydg as DEV006
• symld -g mydg remove DEV006 - Remove DEV006 form device group mydg.

symrdf

• symrdf -sid 1234 -rdfg 3 -type rdf1 -file rdf.txt -g mydg createpair -establish - Establish the SRDF relation between the devices given in the file rdf.txt from array 1234(R1) and remote box according to the rdf group . This command start sync between R1 and R2, and also add these devices after creating the device group mydg.
• symrdf -sid 1234 -rdfg 3 -file rdf.txt query - Query the Devices by using device pair file.
• symrdf -g mydg set mode acp_disk - Set synching mode to Adaptive Copy.
• symrdf -g mydg query - Query device group.
• symrdf -g mydg split - Split the srdf pair for devices given in mydg.
• symrdf -sid 1234 -rdfg 3 -file rdf.txt deletepair.txt -force - Delete the srdf pairing between R1/R2 and return them to stanadard.

symdisk

• symdisk -sid 1234 list -hotspare - List Hotspares configured in the array.
• symdisk -sid 1234 list -by_diskgroup - Displays all the disks in array by disk groups.
• symdisk -sid 1234 list -diskg_group 1 - Displays all the disks in disk group 1.

Windows 2003 Hosts cannot see EMC VMAX Storage - Troubleshooting

Windows 2003 Hosts cannot see EMC VMAX Storage - What are some troubleshooting tips from the storage side that can be done? Should Windows flags be checked along with WWN's?

Please follow below steps 

1) Check the HBA are configured properly at host end 

2) Check Proper WWNs are used in zoning and ports are logging fine. 

3) Check the IG(Initiator Group ) has been created with right WWNs 

4) SPC2 and OS2007 flags should enabled at Initiator (or) IG level(by default the   VMAX FA are enabled with these flags .) 

5) Check the Devices are in Ready (or) Read_Write state
5) Recheck Masking View again with proper (IG,SG and zoned Port_group ) are used.

***
Check the server hba zoning and logged in status in the VMAX array. Use
the below command 
symaccess -sid xxx list logins -wwn < wwn no>



***
There should be no more than 255 LUNs because Windows cant' see LUNs on target 255

NetApp Undedup Procedure

•   Confirm the available space on each volume using the command “df –g <volname>” 
•   Confirm the dedupe savings on each volume using the command “df –s <volname>” and/or “sis status /vol/<volname>”.
•  Confirm that the volume’s current utilization can accommodate the additional data blocks.
•   Pause snapmirror jobs by entering the “#” in the snapmirror.conf file on the destination system.
•  Resize both prod and COB volumes according to dedup savings.
•  Disable dedupe (ASIS) on each volume using the command sis off /vol/<volname>
•  Enter privileged command mode using the command “priv set diag”
•  Begin the process of un-deduping each volume using the command “sis undo /vol/<volname>”
•  Monitor processor utilization with the command “sis status /vol/<volname>.
•  Repeat for additional volumes.
•  Confirm that dedupe has been removed by comparing the output of df –g before and after the undedupe process.
•  Confirm that dedupe has been disabled by running the command “sis status”.
•  Confirm volume utilization by running the “df –g <volname>” command.
•  To stop undedup “sis stop /vol/path”.

Maximum NDMP sessions for Data ONTAP 8.x

Considerations when using NDMP

You have to take into account a list of considerations when starting the NDMP service on your

storage system.

• Data ONTAP supports a maximum of 16 concurrent backups, restores, or both on a local tape

drive.

This includes backups initiated by NDMP as well as by the storage system’s dump, restore, and

smtape commands.

However, a storage system supports a maximum of 32 dump or restore sessions and 32 smtape

sessions.

• NDMP supports a maximum of 128 concurrent sessions on NearStore and 40 on other systems.

The following table defines the maximum number of NDMP sessions for storage systems running Data ONTAP 8.x:

Platform	Max QSM/SV	Max QSM/SV	Max NDMP sessions	Max NDMP sessions
	(with NearStore)	(no NearStore)	(with NearStore)	(no NearStore)
==========	============	===========	===============	===============
FAS2040	160	64	232	136
FAS2240	120	64	192	136
FAS3040	160	64	232	136
FAS3070	320	64	392	136
FAS3140	160	64	232	136
FAS3160	320	64	392	136
FAS3170	384	64	456	136
FAS3210	120	64	192	136
FAS3240	320	64	392	136
FAS3270	320	64	392	136
FAS6030	384	96	456	168
FAS6040	384	96	456	168
FAS6070	512	128	584	200
FAS6080	512	128	584	200
FAS6210	512	128	584	200
FAS6240	512	128	584	200
FAS6280	512	128	584	200

NetApp basic Volume and Vfiler commands

Here are the commands for Volume and Vfiler level

vol create Volume1 aggr1 680g vol options  Volume1  guarantee none vfiler add vfiler1 /vol/Volume1 vfiler run vfiler1 cifs shares -add Volume1  /vol/Volume1 vfiler run   vfiler1  cifs access -delete Volume1  everyone vfiler run  vfiler1  cifs access  Volume1  FOL\GOOGLE_MT Read vfiler run  vfiler1  cifs access  Volume1   FOL\GOOGLE_CA_SAs Full Control exportfs -p rw=server40-boot.n........................root.net /vol/Volume1 vfiler run vfiler1 exportfs -p rw=server40.............root.net /vol/Volume1  qtree security /vol/ Volume1/ unix  qtree security /vol/Volume1/qtree1 unix  cifs terminate  -V Volume1 exportfs -u /vol/Volume1 useradmin domainuser add user1 -g administrator

CF\VIF Failover test - NetApp Filers.

Usually for a new Filers we will be testing CF\VIF takeover test  before getting that BOX to Production...now here let's see procedure.


CF Takeover:


1. Login to Netapp CLI using your Login credentials.
2. Turn off SNMP and Autosupport before do this 
      --> options snmp.enable off
      --> options autosupport.enable off
3. Before starting the test make sure "Takeover NODE is UP"
      --> cf status
4. Now we need to run takeover command
     --> cf takeover
5. While the node is trying to do takeover - try to ping other node...finally it will be giving alert that "Takeover is sucess"
6. Check the status by 
     --> cf monitor
7. Once the node is ready to giveback 
       --> cf status (tells us if node is ready to giveback or not)
       --> cf giveback
8. Then check the "cf status" node should show as UP
9. ON -  SNMP and Autosupport
      --> options snmp.enable on
      --> options autosupport.enable on
10. To get the LOGS go to /etc/messages - and get the Failover logs.




VIF Failover:


1. See the status of interface 
    --> ifgrp status
2. If above cmd shows 1 - up and 1- down, note the name of non-active(which dhows down) interface and test it
3. ifgrp favor e2a
4. go to /etc/messages to collect the Failover logs.