Hands-On MultiStore Advanced Lab Guide ONTAP 8.1 7-Mode

MultiStore Hands -On Advanced Labs Data ONTAP 8.
1 7-Mode
Scott Gelb, Insight Integrated Systems
TABLE OF CONTENTS 1 2 3 4 5 LAB I NFO RMATIO N ......................................................................................................................... 3 VFILER MANAGEMENT ................................................................................................................... 8 DATAMO TIO N FOR V FILER........................................................................................................... 18 VFILER MIGRATE (CLI ) ................................................................................................................. 41 VFILER DR ..................................................................................................................................... 43
5.1 5.2 5.3 5.4 CONFIGUR ING VFILER DR W ITH THE ONCOMM AND 5 NMC PLU GIN .............................................................................43 ACTIVAT E A DR VF ILER ...................................................................................................................................................................52 RESYNC A DR VF ILER .......................................................................................................................................................................54 VFIL ER DR U SIN G EXISTIN G SN APM IRROR .............................................................................................................................56
6 7 8 9
MOVING THE VFILE R ROO T VOLUME.......................................................................................... 57 SNAPMIRROR BE TWEEN VFI LER UNI TS ..................................................................................... 58 APPENDIX A LAB CO NFIGURATION FOR REFERE NCE ........................................................... 60 APPENDIX B CRE ATE A V FILER WI TH SYS TEM MANAGER 2.0 .............................................. 69
10 APPENDIX C CRE ATE A V FILER WI TH PROVISIO NING MANAGE R ........................................ 77 11 APPENDIX D - VFILE R MIGRATE WI TH NO DATA COPY ........................................................... 102 12 APPENDIX E - HO W TO MOVE EXIS TING VFI LER0 TO A VFILER ............................................. 103
LIST OF TABLES Table 1) Internal Lab IP Addresse s .......................................................................................................... 3 Table 2) Data ONTAP Simulator Lab Configuration.................................................................................. 4 Table 3) Data ONTAP Simulator vFiler Units............................................................................................ 5
LIST OF FIGURES Figure 1) Data ONTAP Simulator and vFiler Unit Layout .......................................................................... 6 Figure 2) FlexClone Between vFiler Units .............................................................................................. 15 Figure 3) Move A Clone Source Between vFiler Units ............................................................................ 16 Figure 4) Add and Remove Volumes From vFiler Units .......................................................................... 16 Figure 5) DataMotion for vFiler Diagram................................................................................................. 18 Figure 6) vFiler DR Diagram .................................................................................................................. 43 Figure 7) vFiler DR Resync Diagram ...................................................................................................... 54 Figure 8) SnapMirror Using The vFiler Network...................................................................................... 58 Figure 9) SnapMirror Using vFiler0 Loopback ........................................................................................ 59 Figure 10) vFiler Migrate No Copy Diagram ......................................................................................... 102
CR-3-133 Hands-On MultiStore Advanced Lab Guide
LAB INFORMATION
This lab is pre-configured with Data ONTAP simulators th at represent two physical FAS Controllers, as well as three vFiler units. See Appendix A for a reference on how the lab was configured.
All Passwords are netapp123: Windows NetApp and Linux LAB\Administrator : netapp123 root : netapp123
Table 1) Internal Lab IP Addresses
System Windows Server 2008 R2
IP Address 192.168.150.11
Notes RDP Jumphost, lab.local domain, CIFS shares and iSCSI LUNs OnCommand 5 and NFS mounts Data ONTAP Simulator Data ONTAP Simulator vFiler unit for vFiler migrate vFiler unit for vFiler DR vFiler unit for DataMotion
CentOS 6 Linux FAS6280 FAS3270 vfiler1 vfiler2 vfiler3
192.168.150.31 192.168.150.210 192.168.150.211 192.168.150.221 192.168.150.222 192.168.150.223
The Windows jumphost is the machine that has access to all resources: System Manager 2.0R1 PuTTY for SSH access (all sessions are preconfigured) NetApp Management Console 3.1 OnCommand 5 Console shortcut
Table 2) Data ONTAP Simulator Lab Configuration
Data ONTAP Simulators (v filer0) user passw d IP Subnet GW IPSpace dns domainname dns serv er Admin Host rootv ol CIFS CIFS Netbios Name CIFS Admin CIFS Admin Passw d CIFS Share NFS Export root
FAS6280 root
FAS3270
netapp123 192.168.150.210 (e0a) 255.255.255.0 192.168.150.2 default-ipspace lab.local 192.168.150.11 192.168.150.31 root domain fas6280 administrator netapp123 C$ /vol/root
netapp123 192.168.150.211 (e0a) 255.255.255.0 192.168.150.2 default-ipspace lab.local 192.168.150.11 192.168.150.31 root domain fas3270 administrator netapp123 C$ /vol/root
Table 3) Data ONTAP Simulator vFiler Units
v Filer Units user passw d IP Subnet GW IPspace DNS domain DNS serv er Admin Host rootv ol nasv ol sanv ol CIFS CIFS Netbios Name CIFS Admin CIFS Admin Passw d CIFS Share NFS Export iSCSI LUN root
v filer1 root
v filer2 root netapp123
v filer3
netapp123 192.168.150.220 (e0b) 255.255.255.0 192.168.150.2 ipspace1 lab.local 192.168.150.11 192.168.150.31 vfiler1_root vfiler1_nas vfiler1_san domain vfiler1
netapp123 192.168.150.221 (e0b) 255.255.255.0 192.168.150.2 ipspace1 lab.local 192.168.150.11 192.168.150.31 vfiler2_root vfiler2_nas vfiler2_san domain vfiler2
192.168.150.222 (e0b) 255.255.255.0 192.168.150.2 ipspace1 lab.local 192.168.150.11 192.168.150.31 vfiler3_dmotion_root vfiler3_dmotion_root vfiler3_dmotion_root domain vfiler3
administrator netapp123
vfiler1_nas /vol/vfiler1_nas
vfiler2_nas /vol/vfiler2_nas
vfiler3_root/nas /vol/vfiler3_root/nas
/vol/vfiler1_san/vfiler1_lun1 /vol/vfiler2_san/vfiler2_lun1 /vol/vfiler3_dmotion_root/vfiler3_lun1
At the beginning of this lab, all vFiler units reside on the Data ONTAP Simulator representing a FAS6280.
Figure 1) Data ONTAP Simulator and vFiler Unit Layout
FAS6280 vfiler0 vfiler1 vfiler2 vfiler3
FAS3270 vfiler0
The Windows Server 2008R2 desktop is pictured below. On the desktop you will see a number of icons that have been placed there for your use in the lab: Icons Column 1 top to bottom System Manager 2.0R1 NetApp Management Console (NMC 3.1) OnCommand 5 Console (new DFM) Data Fabric Manager Console (legacy DFM)
Icons Column 2 top to bottom vFiler Shares (shortcuts to all vFiler CIFS shares and iSCSI drives) Putty
2
1.
VFILER MANAGEMENT
Double Click the PuTTY icon, select the session for FAS3270 (vfiler0), and login as as root : netapp123
2.
Create a test vFiler unit using the CLI. The initial command is show below - you can copy and past the command directly into the PuTTY window to avoid spelling mistakes. Continue following the output of the command and provide answers where indicated in bold.
vfiler create test -s ipspace1 -i 192.168.150.223 /vol/vfiler1_root /vol/vfiler1_nas /vol/vfiler1_san Configure vfiler IP address 192.168.150.223? [y]: y Interface to assign this address to {e0b}: e0b Netmask to use: [255.255.255. 0]: 255.255.255.0 Please enter the name or IP address of the administration host: 192.168.150.31 Do you want to run DNS resolver? [n]: y Please enter DNS domain name []: lab.local Please enter the IP address for first nameserver []: 192.168.150.11 Do you want another nameserver? [n]: n Do you want to run NIS client? [n]: n Default password for root on vfiler test is "". New password: netapp123 Retype new password: netapp123 Do you want to setup CIFS? [y]: y Do you want to make the system visible via WINS? [n]: n (1) Multiprotocol filer (2) NTFS-only filer Selection (1-2)? [1]: 1 Enter the password for the root user []: netapp123 Retype the password: netapp123 The default name for this CIFS server is 'TEST'. 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 Di rectory 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? [lab.local]: lab.local Enter the name of the Windows user [Administrator@LAB.LOCAL]: Password for Administrator@LAB.LOCAL: netapp123 (1) CN=computers (2) OU=Domain Controllers (3) None of the above Selection (1-3)? [1]: 1 Do you want to create the TEST\administrator account? [y]: y Enter the new password for TEST \administrator: netapp123
3.
Show the vFiler status. The -r option will show you network and volume details for each vfiler. The -a option will show you more details. Try all three!
vfiler status vfiler status -r vfiler status -a
4.
Rename your vFiler:

vfiler rename test fas3270_vfiler1 vfiler status
5.
Change the vFiler l imit (max vfilers on the system): NOTE: to increase this value, you must reboot for it to take effect. Limits are based on memory. The Data ONTAP Simulator is limited to a maximum of 11 and defaults to 3. This lab is preset to a maximum of 4. vFiler Limits FAS Controllers with <1GB RAM FAS Controllers with >=1GB RAM FAS Controllers with >=2GB RAM
vfiler limit vfiler limit 5 vfiler limit
11 max vFiler units 26 max vFiler units 65 max vFiler units
Here we change the vfiler limit in this lab to a maximum of 5.
6.
Allow and disallow protocols per vFiler unit. You can show all protocols, which by default are all enabled. However, the protocol must be licensed on vfiler0 in order for the vFiler unit to use it.
vfiler status -a
Disallow rsh, ftp and http:

vfiler disallow fas3270_vfiler1 proto=rsh pro to=ftp proto=http vfiler status -a # confirm
Allow ftp:
vfiler allow fas3270_vfiler1 proto=ftp vfiler status -a # confirm
7.
Using vFiler run and vFiler context to run commands in a vFiler. Using the vfiler context command will take you into a command menu just for that specific vfiler. Notice that the command prompt changes after you execute this command.
vfiler context fas3270_vfiler1 fas3270_vfiler1@fas3270> vol status
Use the same command to return to the mai n context of vfiler0.

fas3270_vfiler1@fas3270> vfiler context vfiler0
From the command shell, you can also run a command directly to a vfiler without switching context:
vfiler run fas3270_vfiler1 vol status
You can use this same method to run a command against all vFiler units from vfiler0. Notice how vfiler0 sees ALL volumes and fas3270_vfiler1 only sees its own volumes.
vfiler run * vol status
If you use qtrees, you can see which volumes and qtrees are owned by which vFiler unit:
qtree status -v
10
8.
Interactive and non-interactive ssh directly to the vFiler unit. Data ONTAP 8.1 7-Mode adds a fully interactive secure shell to vFiler units. In addition, the former non-interactive secure shell is also available. To use either of these shells, you first nee d to set up ssh on the vFiler unit. Hit enter for all defaults in the command output.
vfiler run fas3270_vfiler1 secureadmin setup ssh
To test the newly configured secure shell, d ouble-click the PuTTY icon and select the Linux session, authenticating as root : netapp123 NOTE: Ignore the Access Denied message after entering the root login id.
How to use interactive ssh login to a vfiler. Answer yes to the fingerprint question and use the netapp123 password. Note that the vol status only shows volumes accessible to vfiler1.
[root@ ~]# ssh -l root 192.168.150.223 fas3270_vfiler1@fas3270> vol status fas3270_vfiler1@fas3270> exit
How to use non-interactive ssh login to the same vfiler. Again, use the same netapp123 password.
[root@ ~]# ssh -l root 192.168.150.223 vol status
11
9.
Stop and start a vFiler unit. NOTE: All vFiler units are started on system boot, even if they were stopped prior to boot. The vfiler stop command is not persistent across reboots. You can set a loader environment variable to disable all vFiler network connectivity at boot by running setenv no -vfiler-ips? true at a boot loader prompt. You COULD also put vfiler stop vfilername in the /etc/rc file, but the vfi ler would run for a short while after boot.
vfiler stop fas3270_vfiler1 vfiler start fas3270_vfiler1
10. Destroy a vFiler unit. When this command is issued, all the volumes assigned to the vFiler unit are reassigned to vfiler0, including the vFiler root volume that contains all of the configuration for the vFiler unit.
vfiler stop fas3270_vfiler1 vfiler destroy fas3270_vfiler1 vfiler status -a
11. Recreate the vFiler unit you just destroyed. As long as the root volume is preserved, you can recreate the vfiler unit. If the data volumes were destroyed, they can be recreated using the same volume names.
vfiler create fas3270_vfiler1 -r /vol/vfiler1_root -b fas3270_vfiler1
NOTE: We didnt specify the oth er 2 volumes that were in the vFiler unit, but they are added back from the root volume configuration. You will see the .223 address is not configured after the -r to recreate so an ifconfig is needed to rebind to e0b (below).
vfiler status -a
To reconfigure the network interface:

ifconfig e0b 192.168.150.223 netmask 255.255.255.0 up vfiler status -a
12
12. Create another vFiler unit (fas3270_vfiler2):

vfiler create fas3270_vfiler2 -s ipspace1 -i 192.168.150.224 /vol/vfiler2_root /vol/vfiler2_nas /vol/vfiler2_san Configure vfiler IP address 192.168.150.224? [y]: y Interface to assign this address to {e0b}: e0b Netmask to use: [255.255.255.0]: 255.255.255.0 Please enter the name or IP address of the administration host: 192.168.150.31 Do you want to run DNS resolver? [n]: y Please enter DNS domain name []: lab.local Please enter the IP address for first nameserver []: 192.168.150.11 Do you want another nameserver? [n]: n Do you want to run NIS client? [n]: n Default password for root on vfiler test is "". New password: netapp123 Retype new password: netapp123 Do you want to setup CIFS? [y]: y Do you want to make the system visible via WINS? [n]: n (1) Multiprotocol filer (2) NTFS-only filer Selection (1-2)? [1]: 1 Enter the password for the root user []: netapp123 Retype the password: netapp123 The default name for this CIFS server is 'fas3270_vfiler2'. 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]: 1 What is the name of the Active Directory domain? [lab .local]: lab.local Enter the name of the Windows user [Administrator@LAB.LOCAL]: Password for Administrator@LAB.LOCAL: netapp123 (1) CN=computers (2) OU=Domain Controllers (3) None of the above Selection (1-3)? [1]: 1 Do you want to create the FAS3270_VFILER2\administrator account? [y]: y Enter the new password for FAS3270_VFILER2 \administrator: netapp123
13. Using config dump to save settings including cifs shares and other configuration settings for every vFiler unit on the system:
vfiler run * config dump -f -v dump1.txt
Check the vfiler0 dump file at \\192.168.150.211\c$\etc\configs Check the vfiler1 dump file at \\192.168.150.223\c$\vol\vfiler1_root\etc\configs Check the vfiler2 dump file at \\192.168.150.224\c$\vol\vfiler2_root\etc\configs
13
14. Using FlexShare to prioritize volumes in vFiler units. FlexShare allows you to set priority of access to volumes on the NetApp storage system. It has 5 grades of priority from VeryLow to VeryHigh. With this functionality you can control priority of access to vFiler units by setting one vFiler units volumes to low and another to high. Show no priority set yet:
priority show priority show volume -v
Enable FlexCache priority:

priority on priority set io_concurrency=512 # enable priority defaults # disable disk controls
Set very high priority on fas3270_vfiler1_nas volume and very low p riority to fas3270_vfiler2_nas volume
priority set volume vfiler1_nas level=VeryHigh system=VeryHigh priority set volume vfiler2_nas level=VeryLow system=VeryLow
Show priority is set:

priority show priority show volume -v
Create 2 CIFS shares for testing: You could also use NFS or create LUNs with iSCSI, then apply priority to those volumes. vfiler run fas3270_vfiler1 cifs shares -add vfiler1_nas /vol/vfiler1_nas vfiler run fas3270_vfiler2 cifs shares -add vfiler2_nas /vol/vfiler2_nas Open CIFS shares (administrator | netapp01) in a Windows Explorer window: \\192.168.150.223\vfiler1_nas \\192.168.150.224\vfiler2_nas Begin the copy process take a large file or directory and copy to each share (copy something from the C: drive) Start a copy of the large directory or file to vfiler2_nas first (low priority) then to vfiler1_nas soon after (high priority) and the vfiler1_nas copy will run faster. This test doesnt show exact throughput (not using a metric other t han watching), however it shows how FlexShare works. Turn off priority:
priority off
NOTE: On a system with FlashCache cards, you can selectively cache volumes AND enable priority on those volumes. What this means in a multi -tenant architecture is that you can cache and give high FlexShare priority to certain tenant volumes, and turn off cache and give lower priority to other tenant volumes.
14
15. FlexClone a vFiler volume and add that clone to another vfiler unit. This is very useful in a test/dev environment, or moving data from test to production. Another use case here would be taking internal production data and sharing it out on a vfiler that is in a DMZ. These commands all need to be run from vfiler0:
snap create vfiler2_nas clone_snap vol clone create vfiler2_nas_clone -s none -b vfiler2_nas vfiler run * vol status vfiler status -a vfiler add fas3270_vfiler1 /vol/vfiler2_nas_clone vfiler status -a clone_snap
Figure 2) FlexClone Between vFiler Units
vfiler2_nas_clone
FAS3270
fas3270_vfiler1 fas3270_vfiler2
clone_snap
vfiler2_nas
15
16. Move the source of the cloned volume from one vfiler to another.
vfiler move fas3270_vfiler2 fas3270_vfiler1 /vol/vfiler2_nas
This command may fail because the volume is a CIFS share. If so, delete the share and rerun the command.
vfiler run fas3270_vfiler2 cifs shares -delete vfiler2_nas vfiler move fas3270_vfiler2 fas3270_vfiler1 /vol/vfiler2_nas vfiler status -a
Figure 3) Move A Clone Source Between vFiler Units
vfiler2_nas_clone
FAS3270
fas3270_vfiler1 fas3270_vfiler2
clone_snap
vfiler2_nas
17. Remove a volume from vfiler1 and it is reassigned back to vfiler0. You can then add the volume back to vfiler2. This achieves the same object as vfiler move but here you see the remove and add functions.
vfiler vfiler vfiler vfiler vfiler vfiler remove fas3270_vfiler1 /vol/vfiler2_nas_clone run * vol status status -a add fas3270_vfiler2 /vol/vfiler2_nas_clone run * vol status status -a
Figure 4) Add and Remove Volumes From vFiler Units
FAS3270
remove add
vfiler2_nas_clone
fas3270_vfiler1
vFiler0
fas3270_vfiler2
16
18. Destroy vfiler1 and add all its resources to vfiler2 (both network and volumes):
vfiler stop fas3270_vfiler1 vfiler destroy fas3270_vfiler1 vfiler add fas3270_vfiler2 -i 192.168.150.223 /vol/vfiler1_san /vol/vfiler1_nas /vol/vfiler2_nas vfiler status -a
19. Remove an IP and volume from vfiler2:

vfiler remove fas3270_vfiler2 -i 192.168.150.223 vfiler remove fas3270_vfiler2 /vol/vfiler1_san vfiler status -a
20. Stop and destroy vfiler2 and destroy the clone volume for the next labs:
vfiler stop fas3270_vfiler2 vfiler destroy fas3270_vfiler2 vfiler status -a vol offline vfiler2_nas_clone vol destroy vfiler2_nas_clone
17
DATAMOTION FOR VFILER
DataMotion for vFiler in Data ONTAP 8.1 contains a number of enhancements. vFilers can now be nondisruptively moved between any type of controller and any type of disk. This lab will walk you through performing a complete DataMotion for vFiler operation.
Figure 5) DataMotion for vFiler Diagram
FAS6280
vfiler3
Data Motion Migrate
FAS3270
vfiler3
1.
To begin this lab, open several SSH sessions. Double-click the PuTTY icon and login to the FAS6280 (vfiler0), FAS3270 (vfiler0), and Linux sessions, authenticating as root : netapp123. You should already have two of these sessions open. Display your access to the NAS (CIFS and NFS) and SAN (iSCSI) connections on vfiler3 . In the Linux PuTTY window, check the nfs mount:
[root@ ~]# ls -l /root/vfiler3 total 0 -rw-r--r-- 1 root root 12 Sep 30 01:17 test_vfiler3.txt
2.
18
On the Windows machine, double-click vFiler Shares then click into each of the 3 vFiler shortcuts and confirm access to vfiler3_C$, vfiler3_nas and vfiler3_san .
19
20
3.
To get started with the DataMotion for vFiler process, double -click the NetApp Management Console (NMC) on the Windows 2008 Desktop. Enter the pa ssword netapp123 then click Connect.
4.
Click on the Hosts pane on the left.
21
5.
Click on v Filer Units and select v filer3 in the window. Click the Start migration button.
22
6.
Click Next.
23
7.
Select Online migration and click Next.
NOTE: Online migration is the key to DataMotion for vFiler. This method of migration allows vFiler units to be moved non-disruptively between NetApp storage systems with a maximum pause in I/O of 120 seconds. Offline migration will migrate vFiler units disruptively. The vFiler unit will be stopped and there is an undetermined amount of time for the pause in I/O while data cutover occurs.
24
8.
Select fas3270 and click Next.
25
9.
Click Next (take defaults we only have one aggregate on each Simulator).
26
10. Click Edit.
27
11. Select e0b for the network interface and click Update , then click Next.
28
12. Click Next (no SnapMirror throttle).
29
13. Click Next. We wont cutover now so you can see how to do this manually.
30
14. Click Next on the information screen.
31
15. Click Finish.
16. You will be able to watch the status of the job as it progresses.
32
17. When the Status is shown as Started, cutover required , click the Cut ov er button. You can also run Update to resync the mirrors if a long period has passed. The cutover process will take a while to begin, but once the cutover has begun, the pause in I/O from clients will not exceed 120 seconds.
33
18. The migration cutover wizard starts. Click Next.
34
19. Click Next.
35
20. Leave the defaults (All static routes radio button and Store the migrated routes checkbox) and click Next.
36
21. Click Next.
37
22. Click Finish.
23. You will be able to watch the cutover job as it completes.
38
24. When the job window closes, the Migration Status is Migrated, Cleanup Required .
25. To see all jobs, click on the Data pane and select Jobs .
39
26. After this process you can again verify that after vfiler3 moved from the FAS6280 to the FAS3270 there is no outage to the data. Display your access to the NAS (CIFS and NFS) and SAN (iSCSI) connections on vfiler3. In the Linux PuTTY window, check the nfs mount:
On the Windows machine, double-click vFiler Shares then click into each of the 3 vFiler shortcuts and confirm access to vfiler3_C$, vfiler3_nas and vfiler3_san .
27. If you want to try some additional functionality, try the Rollback function in the NMC. This moves vfiler3 back to the FAS6280. The Clean Up operations removes all the original source volumes, SnapMirror configuration, Snapshots, and vfiler configuration from the FAS6280.
40
VFILER MIGRATE (CLI)
In the previous section you migrated a vFiler unit nondisrupti vely using the Online Migration capability of Provisioning Manager. Here we will show you how to perform the same migration using the v filer migrate CLI command. If you recall, Provisioning Manager also has an Offline Migration capability. This is the same capability that you can manage from the CLI. Both the Offline Migration and the CLI vfiler migrate command use Asynchronous SnapMirror for mirroring and cutover of data. This means that the cutover may take an unknown amount of time based on the load of the system, and the cutover can not happen during a guaranteed time. Both of these methods are disruptive. In this lab we will migrate vfiler1 from the FAS6280 simulator to the FAS3270. In this lab environment, the NFS and iSCSI clients will not see an outa ge because there is no load on the system and very little data in the volumes being mirrored. If you leave a CIFS window open to the vfiler1 CIFS share, you will notice a disconnection. NOTE: The snapmirror.conf file on the 3270 will update every 3 minutes by default (you would change this for a production migration). Volumes must be the same name on the source and target systems. IPSpace names must be the same name on source and target systems (they were pre-created for these labs). The mirrors run from vfiler0 (physical controller) and not to the vFiler units directly. For information on how to move vFiler units between controllers in the same HA pair, using vfiler migrate (-m nocopy), see Appendix D. 1. 2. To begin a vfiler migrate process, first show the sta tus:
fas3270> vfiler status -a
Then youll execute the migrate start command. Note that we are executing this command from the destination system, not from the source, so we have to provide a login and password for the source system.
fas3270> vfiler migrate start -c secure -l root:netapp123 vfiler1@fas6280
3. 4.
When prompted, answer y to keep the same .220 IP address. Enter e0b for the interface, and use 255.255.255.0 for the subnet. Now you can show the status of the migration. Wait until SnapMirror status shows as Idle for all three volumes.
fas3270> vfiler migrate status vfiler1@fas6280 fas3270> snapmirror status
5.
Once the SnapMirror status shows as idle, you can complete the migration. When you enter this command, the vFiler unit on the source system is stopped. A final incremental SnapMirror update is processed, and the vFiler unit is then started on the destination system.
fas3270> vfiler migrate complete -c secure -l root:netapp123 vfiler1@fas6280
6.
You can now see that the vfiler unit has been moved:
fas3270> vfiler status -a fas6280> vfiler status -a # vfiler1 running on the 3270 # vfiler1 is gone on the 6280
7.
As with the previous DataMotion for vFiler session, you can confirm that CIFS, NFS and iSCSI access continues for vfiler1 even though it has moved physical controllers. NFS (Linux)
CIFS (access from vFiler Shares on desktop)

\\192.168.150.220\vfiler1_nas
41
iSCSI (access from vFiler Shares on desktop)

X:\
42
VFILER DR
A new plugin is available for the NetApp Management Console (NMC) that allows you to configure and activate vFiler DR relationships. This lab will show you how to use the plugin to configure a new vFiler DR relationship. You will then use the CLI to simula te an outage and activate the DR vFiler, and resync it with the source site.
5.1
CONFIGURING VFILER DR WITH THE ONCOMMAND 5 NMC PLUGIN

** The equivalent CLI to the GUI below ** fas3270> vfiler dr configure -u -c secure -l root:netapp123 vfiler2@fas6280
Figure 6) vFiler DR Diagram
FAS6280
vfiler2
FAS3270
SnapMirror async to D.R. site
vfiler2
D.R.
1.
Double Click the NetApp Management Console (NMC) on the Windows 2008 Desktop. Enter the password netapp123 then click Connect.
43
Click on the Hosts pane on the left.
44
2.
Click v Filer DR Units and select v filer2 . Click the Protect button.
45
3.
Click Next.
4.
Click Next as there is only one storage system in the list.
46
5.
Click Next, as we are keeping the same IP and interface settings.
6.
Click next to use the default protection values. The destination volumes have been precreated as part of the lab. In a real -world scenario you would need to create these.
47
7.
Click Next to use the same DNS and NIS setti ngs.
8.
Click Next. If you needed to specify alternate source or destination IP addresses, you could do that here (for example, if you have a specific network for SnapMirror replication).
48
9.
Enter the appropriate credentials for the source system (root : netapp123 ), and check the Use secure command channel , then click Next.
49
10. Click Finish.
50
11. Once the DR relationship has been defined, you can view it both in the NMC as well as the CLI. NOTE: The NMC refreshes DR relationships slowly, so it may take several minutes for the Protection Role to show as DR Backup.
12. You can also show the vfiler status using the CLI:
fas3270> vfiler status vfiler0 vfiler3 vfiler2 running running stopped, DR backup
51
5.2
ACTIVATE A DR VFILER
The elegance of vFiler DR is that it breaks all mirrors automatically, and it also contains the shares, exports, iSCSI mappings, IP addresses, and other settings from the source vFiler unit. Without vFiler DR, you would have to manually break mirrors, and recreate all of the configuration manually at the DR destination site. Note: You could activate from the vFiler DR plugin in the NMC above, but we will show via CLI. Here you will shut down vfiler2 on the FAS6280 system, to simulate a disaster at the source site. The destination vfiler2 will be activated on the FAS3270 system. 1. 2. 3. First, you will simulate a disaster on the source system:
fas6280> vfiler stop vfiler2
Next, activate the DR vFiler on the destination system:

fas3270> vfiler dr activate vfiler2@fas6280
Display the vFiler status on each system. Obviously in a real disaster you may not be able to see that the vfiler on the source system is stopped, but this is a valid use case for DR testing.
fas6280> vfiler status -a fas3270> vfiler status -a
4.
As with the previous sessions, you can confirm that CIFS, NFS and iSCSI access continues for vfiler2 even though it has moved physical controllers. NFS (Linux)
CIFS (access from vFiler Shares on desktop)

\\192.168.150.221\vfiler2_nas
iSCSI (access from vFiler Shares on desktop)

Y:\
52
53
5.3
RESYNC A DR VFILER
Now that youve simulated a disaster and seen how to bring up a DR vFiler at a destination site, youll want to know how to resync the destination site with the source once the disaster is over. Note: You could resync from the vFiler DR plugin in the NMC above, but we will show via CLI. In this section you will perform a vFiler DR resync back to the FAS6280 system, failover the DR vfiler, and resync again back to the destination. This will return vfiler2 back to the source system in the same state it was before we simulated a disaster above.
Figure 7) vFiler DR Resync Diagram
FAS6280
1. SnapMirror
vfiler2
Resync D.R.
FAS3270
2. SnapMirror
Resync D.R. 3. Stop D.R. vFiler
vfiler2
Start Prod vFiler
D.R.
4.
1.
To resync the running DR vfiler2 back to the source production site:

fas6280> vfiler dr resync -c secure -l root:netapp123 vfiler2@fas3270 fas6280> vfiler dr status vfiler2@fas3270 fas6280> snapmirror status fas6280> vfiler status -a
2.
Once the SnapMirror status in step 1 shows as Idle , you can then stop the DR vFiler and activate it again on the source production site. NOTE: Make certain you issue the commands on the correct simulators.
fas3270> vfiler stop vfiler2 fas6280> vfiler dr activate vfiler2@fas3270 fas3270> vfiler status -a fas6280> vfiler status -a
3.
Now, in order to restore the DR relationship so that the DR vFiler on the FAS3270 returns to the correct state of Stopped, DR Backup , you will need to again resync the relationship.
fas3270> vfiler dr resync -c secure -l root:netapp123 vfiler2@fas6280 fas3270> vfiler dr status vfiler2@fas6280 fas3270> snapmirror status fas3270> vfiler status -a
54
4.
Finally, you can release the SnapMirror rel ationships which are left over from the resync of the original source volumes:
fas3270> snapmirror release vfiler2_root fas6280:vfiler2_root fas3270> snapmirror release vfiler2_san fas3270> snapmirror release vfiler2_nas fas6280:vfiler2_san fas6280:vfiler2_nas
55
5.4
VFILER DR USING EXISTING SNAPMIRROR
A new option (-u) was introduced in Data ONTAP 7.3.5 and Data ONTAP 8.1 7 -mode to allow creation of a vFiler DR relationship using an existing SnapMirror relationship. This means that if you have existing SnapMirror relationships between two storage controllers, you can use them to initialize a vFiler DR relationship. All volume mirrors must be initialized prior to using this option. 1. Here, we will delete the existing DR relationship for vfiler2 on the FAS62 80, use the volumes to create new initialized SnapMirror relationships with the FAS3270, and then use those relationships to create a new DR vfiler. This simulates a situation where you already have mirrored volumes and do not wish to perform a new baselin e.
fas3270> fas3270> fas3270> fas3270> fas3270> fas3270> fas3270> fas3270> vfiler dr delete vfiler2@fas6280 vol restrict vfiler2_root vol restrict vfiler2_nas vol restrict vfiler2_san snapmirror initialize -S fas6280:vfiler2_root vfiler2_root snapmirror initialize -S fas6280:vfiler2_nas vfiler2_nas snapmirror initialize -S fas6280:vfiler2_san vfiler2_san snapmirror status
2.
Once the SnapMirror status shows Idle , you can create the vFiler DR relationship using the -u option:
fas3270> vfiler dr configure -u -c secure -l root:netapp123 vfiler2@fas6280
When prompted, use the same IP address. Enter e0b as the interface, and 255.255.255.0 for the subnet mask. Answer N to use the same DNS settings. 3. You can now check the status and you will see that the vFiler DR relationship has been created.
fas3270> snapmirror status fas3270> vfiler status
4.
NOTE: When using the -u command, the vFiler DR configure process will change th e existing settings in /etc/snapmirror.conf to every 3 minutes. In a production scenario you will want to change these settings back to an interval of your choosing.
CLEANUP Stop the DR vFiler on the FAS6280 and activate the vFiler unit on the FAS3270:
fas6280> vfiler stop vfiler2 fas6280> vfiler status -a fas3270> vfiler dr activate vfiler2@fas6280 fas3270> vfiler status -a
56
MOVING THE VFILER ROOT VOLUME
To move the root volume into a different aggregate, the vfiler must be stopped, destroyed and recreated using the same root volume name. T he new root must be renamed to the old root name. NOTE: You can rename any vFiler volume (including root) with v ol renameold new at any time, however to actually move the root volume requires that we destroy and recreate the vFiler using the same name of the root volume before/after the move to another aggregate. The procedure below will move the vfiler1_root volume to newroot (which will become vfiler1_root) 1. Create anew root volume, restrict it, and vol copy the existing root to the newroot:
fas3270> vol create newroot -s none aggr0 20m fas3270> vol restrict newroot fas3270> vol copy start -S vfiler1_root newroot
2.
Stop and destroy the vfiler:

fas3270> vfiler stop vfiler1 fas3270> vfiler destroy vfiler1
3.
Rename volumes so the newroot is the same name as oldroot

fas3270> vol rename vfiler1_root oldroot fas3270> vol rename newroot vfiler1_root
4.
Online the new root volume and recreate the vfiler:

fas3270> vol online vfiler1_root fas3270> vfiler create vfiler1 -r /vol/vfiler1_root
5.
NOTE: The e0b interface will not be configured and needs to be configured. You will need to ifconfig the interface. You will also need to update the rc file in a production environment.
fas3270> vfiler status -a fas3270> ifconfig e0b alias 192.168.150.220 fas3270> vfiler status -a
57
SNAPMIRROR BETWEEN VFILER UNITS
Here we show two methods of mirroring between vfiler units on the same physical controller, one using the vfiler network, and the other using physical filer loopback address(vfiler0). The advantage of mirroring from a vfiler is if the vfiler moves, then the mirror follows. If you are mirroring from vfiler0, mirrors need to be resynced when moved to a new target controller. The advantage in mirroring from vfiler0 is if there is a DMZ or no network route between vFiler units, you can still replicate data. NOTE: If you run snapmirror from the vFiler, the logs are in /etc/log/snapmirror of the vFiler, not vfiler0. Logs reside wherever the mirror runs (on both source and target ). NOTE: If you plan on using snapmirror multipathing, that is only supported in vfiler0 and not in individual vfilers. This is also required for snapmirror compression, so using vfiler0 for mirrors is most useful in these environments.
Figure 8) SnapMirror Using The vFiler Network
FAS3270
vfiler1
vfiler1_source
SnapMirror
192.168.150/24
vfiler2
vfiler2_dest:RO
SNAPMIRROR USING THE VFILER NETWORK 1. Confirm you can ping both vfilers:
fas3270> ping 192.168.150.220 fas3270> ping 192.168.150.221
2.
Next, create the volumes you want to mirror and add them to both vFiler units.
fas3270> vol create vfiler1_source -s none aggr0 20m fas3270> vfiler add vfiler1 /vol/vfiler1_source fas3270> vol create vfiler2_dest -s none aggr0 20m fas3270> vfiler add vfiler2 /vol/vfiler2_dest
3.
Now you can turn on SnapMirror and mirror the volumes.

fas3270> vfiler run * snapmirror on fas3270> vfiler run * options snapmirror.access * fas3270> vfiler run vfiler2 vol restrict vfiler2_dest fas3270> vfiler run vfiler2 snapmirror initialize 192.168.150.220:vfiler1_source vfiler2_dest fas3270> vfiler run vfiler2 snapmirror status -S
58
SNAPMIRROR USING THE VFILER0 LOOPBACK In this method, you do not use any externally connected network interfaces to carry the SnapMirror replication traffic. This means that you can mirror traffic betwee n two vFiler units that do not have any network connection. This is a good way to replicate data from production to a DMZ.
Figure 9) SnapMirror Using vFiler0 Loopback
vFiler0
vfiler1
vfiler1_source2
FAS3270
SnapMirror
Loopback
DMZ IPSpace
vfiler2
vfiler2_dest2:RO
1.
As above, create the volumes you want to mirror and add them to both vFiler units.
fas3270> vol create vfiler1_source2 -s none aggr0 20m fas3270> vfiler add vfiler1 /vol/vfiler1_source 2 fas3270> vol create vfiler2_dest2 -s none aggr0 20m fas3270> vfiler add vfiler2 /vol/vfiler2_dest 2
2.
This time when you initialize the SnapMirror, note that the command has no IP source or destination address.
fas3270> vol restrict vfiler2_dest2 fas3270> snapmirror initialize -S vfiler1_source2 vfiler2_dest2 fas3270> snapmirror status
59
APPENDIX A LAB CONFIGURATION FOR REFERENCE
BASIC LAB CONFIGURATION # username # password # e0a root netapp123 192.168.150.nnn/24 fas6280 nnn=210 fas3270 nnn=211 vfiler1 nnn=220 vfiler2 nnn=221 vfiler3 nnn=222 # gateway # dns domainname # dns server # cifs setup # cifs administrator # cifs password # timezone # language # admin host 192.168.150.2 lab.local 192.168.150.11 multiprotocol; lab.local domain lab\administrator:netapp123 administrator netapp123 GMT C.UTF-8 192.168.150.31
IPS 192.168.150.2 192.168.150.11 192.168.150.31 192.168.150.210-229 gateway Windows 2008 host (RDP landing) CentOS 6 host#1 VSIM and vFilers login: login: login: administrator : netapp123 root : netapp123 root : netapp123
CHANGE VM SETTINGS Change description (VMware) for each VSIM to "vsim_8.1-7mode node1, node2" for each of the 2 nodes 6280, 3270 Change all 4 interfaces e0a/e0b/e0c/e0d to NAT (from custom and bridged) Change (disconnect) both serial ports under settings | other devices so no serial port conf licts DO NOT Change from 2 CPU, 2048MB RAM (required for VSIM)
CHANGESERIAL NUMBERS (SO NO DUPLICATION IN ONCOMMAND) Change serial# of each VSIM for System Manager and Operations Manager - Default SYSID = 123454321
CTRL-C at the boot timer to get to SIMLOADER
60
There are two boot variables and one (bootarg.nvram.sysid) takes precedent in setting the UID's. If you're looking to avoid UID conflicts, the best thing to do is set bootarg.nvram.sysid and SYS_SERIAL_NUM to the same value, and do this prior to first boot and initializing the disks. That prevents having to go through maintenance mode to reassign the disks. Other UID's may also be fixed and harder to change after the first complete boot.
Also, the system ID format is a 10-digit number. The last two digits of the number need to be unique within the C-Mode cluster for the disk UID's to be unique. So one way to manage the values is to use the first 8 digits to represent the cluster, and the last two digits to represent the node. For example: 1111111101, 1111111102, ..., 2222222201, 2222222202, etc. To set the values, you'll need to enter: SIMLOADER> set bootarg.nvram.sysid 1111111101 SIMLOADER> set SYS_SERIAL_NUM 1111111101 SIMLOADER> boot #use 01,02 for each of the 2 nodes 6280, 3270 #use 01,02 for each of the 2 nodes 6280, 3270 #"Y" to system override sysid
CTRL-C Boot Maintenance Mode - you must run option 4 after changing sysids
Option (4) Clean configuration and initialize all disks.
ADD DISKS (SIM HACK FROM MIROSLAV)
The default simulator comes with 28 simulated disks of 1GB each. It is possible to increase the simulated disk count to 56 simulated disks. Any disk files above the first 56 are ignored. The following procedures will provide step-by-step instructions for doubling the disk coun t to 56 disks and maki ng the disks available for use. unlock the diag user and assign it a password:
priv set advanced useradmin diaguser unlock useradmin diaguser password # netapp123
log in to the system shell using the diag user account:
systemshell login: diag password: netapp123
Add the directory with the simulator disk tools to the path:
setenv PATH "${PATH}:/sim/bin"
61
echo $PATH
Go to the simulated devices directory:
cd /sim/dev ls ,disks/
At this point you will see a number of files which represent the simulated disks. Notice that these files start with "v0." and "v1.". That means the di sk are attached to adapters 0 and 1, and if you count the disk files you'll see that there are 14 of them on each adapter. This is similar to the DS14 shelf topology with each shelf attached to its own adapter. We will now add two more sets of 14 disks to the currently unused adapters 2 and 3:
makedisks.main -h sudo makedisks.main -n 14 -t 23 -a 2 sudo makedisks.main -n 14 -t 23 -a 3 ls ,disks/
*** NOTE: Type 23 for 1GB disks and 8.1 added 2 and 4GB disk types w ith types 30 -33 (30-31 for SAS 520 Blocks per sector, 32-33 for SATA 512 w ith less usable)
30 31 32 33
NETAPP__ VD-2000MB-FZ-520 2097,512,000 B 2159,272,960 B NETAPP__ VD-4000MB-FZ-520 4194,304,000 B 4289,192,960 B NETAPP__ VD-2000MB-FZ-ATA 2097,512,000 B 2391,810,048 B NETAPP__ VD-4000MB-FZ-ATA 4194,304,000 B 4751,106,048 B
Yes Yes Yes Yes
520 520 512 512
The first invocation of the command prints usage information. The remaining two commands tell the simulated disk creation tool to create 14 additional disk (" -n 14") of type 23 ("-t 23") on adapters 2 and 3 (e.g., "-a 2"). Data ONTAP 8.0.1 supports simulated disks 1GB or smaller. Even if you see larger disks listed in the usage i nformation, please resist the temptation to add them to the simulator. It will only cause Data ONTAP to panic on boot and force you to recreate the simulator from scratch.
Now we're done with the system shell. We need to reverse some of the earlier steps and reboot the simulator so that it sees the new disks: exit useradmin diaguser lock priv set admin reboot
62
After the reboot complete, log back in and take ownership of all the new disks: disk show -n disk assign all disk show -v
You should now see 56 disks of 1GB each listed in the simulator. The new disks should be listed as already zeroed and ready to use inside an aggregate. CONFIGURATION FOR BOTH 6280 AND 3270 NODES
disk assign all aggr create aggr1 -r 25 50 options autosupport.enable off vol rename vol0 root license add # add license keys options security.passwd.rules.history 0 options httpd.enable on options httpd.admin.enable on options tls.enable on options ndmpd.enable on options snapmirror.enable on options snapmirror.access * options timed.servers 192.168.150.11 options timed.enable on admin host is 192.168.150.31 cifs setup (for all vfiler0 and vfilers) - keep names fas6280, fas3270, vfiler1, vfiler2, vfiler3 n 1 netapp123 1 netapp123 no wins multiprotocol root password domain lab.local local administrator netapp123 # non root disks change to the vsim # Configuration for Both 6280 and 3270 nodes
options licensed_feature.flexcache_nfs.enable on options licensed_feature.iscsi.enable on options licensed_feature.multistore.enable on options licensed_feature.nearstore_option.enable on vfiler limit 4 reboot vol create vfiler1_root -s none aggr1 20m vol create vfiler1_nas vol create vfiler1_san vol create vfiler2_nas vol create vfiler2_san -s none aggr1 400m -s none aggr1 400m -s none aggr1 400m -s none aggr1 400m
vol create vfiler2_root -s none aggr1 20m
63
vol create vfiler3_dmotion_root aggr1 10g autocreate from dmotion options autologout.telnet.enable off options autologout.console.timeout 180 options autologout.telnet.timeout 180 ipspace create ipspace1 ipspace assign ipspace1 e0b ipspace list
# 6280 only.
Not 3270.
3270 will
CONFIGURE VFILERS ON FAS6280 v filer1

fas6280> vfiler create vfiler1 -s ipspace1 -i 192.168.150.220 /vol/vfiler1_root /vol/vfiler1_nas /vol/vfiler1_san Setting up vfiler vfiler1 Configure vfiler IP address 192.168.150.220? [y]: Interface to assign this address to: e0b Admin host 192.168.150.31 Dns lab.local, 192.168.150.11 nameserver vfiler run vfiler1 cifs shares -add vfiler1_nas /vol/vfiler1_nas vfiler run vfiler1 cifs shares vfiler run vfiler1 options snapmirror.enable on vfiler run vfiler1 options snapmirror.access * vfiler run vfiler1 secureadmin setup ssh vfiler run vfiler1 secureadmin enable ssh vfiler run vfiler1 exportfs -av vfiler run vfiler1 igroup create -i -t windows vfiler1_iscsi vfiler run vfiler1 igroup add vfiler1_iscsi iqn.199105.com.microsoft:win2k8r2.lab.local vfiler run vfiler1 lun create -o noreserve -s 32m -t windows /vol/vfiler1_san/vfiler1_lun1 vfiler run vfiler1 lun map /vol/vfiler1_san/vfiler1_lun1 vfiler1_iscsi # enter all all defaults
v filer2
fas6280> vfiler create vfiler2 -s ipspace1 -i 192.168.150.221 /vol/vfiler2_root /vol/vfiler2_nas /vol/vfiler2_san Setting up vfiler vfiler2 Configure vfiler IP address 192.168.150.221? [y]: Interface to assign this address to: e0b Admin host 192.168.150.31 Dns lab.local, 192.168.150.11 nameserver vfiler run vfiler2 cifs shares -add vfiler2_nas /vol/vfiler2_nas vfiler run vfiler2 cifs shares vfiler run vfiler2 secureadmin setup ssh vfiler run vfiler2 secureadmin enable ssh # enter all all defaults
64
vfiler run vfiler2 exportfs -av vfiler run vfiler2 igroup create -i -t windows vfiler2_iscsi vfiler run vfiler2 igroup add vfiler2_iscsi iqn.199105.com.microsoft:win2k8r2.lab.local vfiler run vfiler2 lun create -o noreserve -s 32m -t windows /vol/vfiler2_san/vfiler2_lun1 vfiler run vfiler2 lun map /vol/vfiler2_san/vfiler2_lun1 vfiler2_iscsi
65
v filer3
fas6280> vfiler create vfiler3 -s ipspace1 -i 192.168.150.222 /vol/vfiler3_dmotion_root Setting up vfiler vfiler3 Configure vfiler IP address 192.168.150.222? [y]: Interface to assign this address to: e0b Admin host 192.168.150.31 Dns lab.local, 192.168.150.11 nameserver vfiler run vfiler3 cifs shares -add vfiler3_root /vol/vfiler3_dmotion_root vfiler run vfiler3 cifs shares vfiler run vfiler3 secureadmin setup ssh vfiler run vfiler3 secureadmin enable ssh vfiler run vfiler3 exportfs -av vfiler run vfiler3 igroup create -i -t windows vfiler3_iscsi vfiler run vfiler3 igroup add vfiler3_iscsi iqn.199105.com.microsoft:win2k8r2.lab.local vfiler run vfiler3 lun create -o noreserve -s 32m -t windows /vol/vfiler3_dmotion_root/vfiler3_lun1 vfiler run vfiler3 lun map /vol/vfiler3_dmotion_root/vfiler3_lun1 vfiler3_iscsi # enter all all defaults
Edit /etc/rc and enter manually the line below to add a default route in the IPSpace:
fas6280> vfiler run vfiler1 route add default 192.168.150.2 1
SETTINGS TO CHANGE FOR ALL VFILER UNITS

vfiler run * options security.passwd.rules.history 0 vfiler run * options httpd.admin.enable on vfiler run * options tls.enable on vfiler run * options ndmpd.enable on vfiler run * options snapmirror.enable on vfiler run * options snapmirror.access * vfiler run * options iscsi.ip_based_tpgroup on # data motion requirement
OTHER CONFIGURATION Make Windows 2008 (or other) DNS entries for all 5 systems (2 vfiler0, 3 vfiler) Setup iSCSI Create 11 desktop shortcuts (2 physical, 3 per vfiler) C$, vfiler_nas, vfiler_san (shortcut to x:, y:, z:) drives. Write a file to each NAS share and iSCSI LUN. Install Linux, disable firewall , disable screen saver mkdir /root/vfiler1 /root/vfiler2 /root/vfiler3
Add NFS mounts in the linux machines /etc/fstab for /root/vfiler1 /root/vfiler2 /root/vfiler3
vfiler1:/vol/vfiler1_nas
/root/vfiler1 nfs rsize=32768,wsiz e= 32768,timeo=600,intr
66
vfiler2:/vol/vfiler2_nas vfiler3:/vol/vfiler3_dmotion _root/n as
/root/vfiler2 nfs rsize=32768,wsiz e= 32768,timeo=600,intr /root/vfiler3 nfs rsize=32768,wsiz e= 32768,timeo=600,intr
Install all nfs packages to get around wrong fs type errors system administration add/remove software Do a software update on linux
Disable SE Linux setenforce 0 # realtime disable
vi /etc/selinux/config change SELINUX=enforcing to to SELINUX=disabled
SOFTWARE INSTALLATIO N Install Java, Perl, Adobe Flash, System Manager 2.0R1, NetApp Management Console (NMC), and the vFiler DR plugin for the NMC on the Windows host and add the two simulators (6280, 3270) to System Manager. Install OnCommand 5.0 on the Linux host: ./occore-setup-5-0-linux-x64.sh -o
dfm plugin add filerconfig_Linux64.zip
Download the 8.1RC1 64-bit plugin from NOW:

https://now.netapp.com/NOW/download/software/ontap/8.1RC1/dfm_plug -in.shtml dfm service list dfm vfiler add all # make sure all are started. dfm option set vFilerMonInterval=1min
dfm ssl serv er setup dfm options set httpsEnabled=on dfm options list httpsEnabled dfm serv ice stop http dfm serv ice start http dfm option set serv erHTTPEnabled=Enabled
JAVA Install http://java.com download sudo su cd /usr/java chmod a+x jre-6u29-linux-x64-rpm.bin ./ jre-6u29-linux-x64-rpm.bin # install java -version # test java version
67
cd /usr/lib/mozilla/plugins ln -s /usr/java/latest/lib/amd64/libnpjp2.so browser http://www.java.com/en/download/help/testvm.xml Authenticate NMC to the controllers root and ndmp # required to work in Mozilla # test java
http://localhost:8080/dfm/w elcome http://localhost:8080/start.html http://localhost:8443/dfm/w elcome http://localhost:8443/start.html
# # # #
http http to NEW OnCommand5 dashboard https https to NEW OnCommand5 dashboard
68
9 APPENDIX B CREATE A VFILER WITH SYSTEM MANAGER 2.0

1. Open System Manager 2.0 from the icon on the Windows desktop. Select the FAS3270 and click the Login button.
2.
Click on v Filer units .
69
3.
Click on Create .
70
4.
Click Next.
5.
Fill in the details below (vfilername: test, browse for existing vfiler1_root volume) and click Next.
71
6.
Fill in the networking details. Enter ipspace1 for the IPSpace, 192.168.150.223 for the IP address, 255.255.255.0 for the netmask, e0b for the interface, and click Next.
7.
Click on 3 protocols (all but RSH) and click Next.
72
8.
Enter the admin host 192.168.150.31 and the password netapp123 and click Next.
9.
Click Next.
73
10. Click Finish.
11. Add 2 more volumes. Select the test vFiler unit and click Edit.
74
12. Select the Storage tab and click the Add button.
13. Click the elipse ... and add the volumes v filer1_nas and v filer1_san, then click Sav e .
75
14. Select the DNS tab, enter lab.local and 192.168.150.11 , then click Sav e and Close .
76
10
APPENDIX C CREATE A VFILER WITH PROVISIONING MANAGER
NOTE: You will need to add a vfiler default route by adding a route add default statement in the vfiler0 /etc/rc file. Steps required to create a vFiler unit using Provisioning Manager: Create a resource pool Create a vFiler template Create a vFiler unit Create a provisioning policy Create a dataset and assign storage
CREATE A RESOURCE POOL 1. Open the NetApp Management Console (NMC) and select the Hosts Pane Storage Systems , click the Details tab on the bottom, then click on the FAS3270 . Confirm that all licenses you need are installed.
77
2.
From the navigation pane, click Data > Resource Pools . Click the Add button to start the setup wizard.
78
3.
Click Next.
79
4.
Enter test in General Properties then click Next.
80
5.
Click on the fas3270 and click the > arrow to add to the resource pool , and click Next.
81
6.
Leave the Resource pool label blank and click Next.
82
7.
Confirm Space Thresholds (increate thresholds per below) and click Next.
83
8.
Click Finish.
84
9.
You can now see your created Resource Pool.
85
CREATE A VFILER TEMPLATE 1. From the navigation pane, select Policies > v Filer Templates . Click the Add button to start the setup wizard.
86
2.
Click Next.
87
3.
Enter test and click Next.
88
4.
Add DNS settings. Enter lab.local for the domtain name and 192.168.150.11 for a name server. Click on Add then click Next.
89
5.
For CIFS Settings, select MultiProtocol , Activ e Directory and click Next.
6.
Click Finish. You can now see your created vFiler Template.
90
CREATE A VFILER UNIT
1.
From the navigation pane, select Hosts > v Filer Units . Click the Add button to start the setup wizard.
91
2. Click Next.
92
3. Enter test for the name, ipspace1 as the IPSpace. Select NFS , CIFS and iSCSI, then click Next.
93
4. Select fas3270 and click Next.
94
5. Click Next.
6. Click Add to enter IP bindings. Enter the IP, netmask, e0b (which will be part ipspace1 from prior setting) and click Add.
95
7. Click Next.
96
8. Select the vfiler template test, enter the domain password (netapp123 ), and click Next.
97
9. Enter the password netapp123 and click Next.
98
10. Click Next.
99
11. Click Finish.
100
ADDITIONAL TASKS OUT OF SCOPE OF THIS EXAMPLE Create a provisioning policy: Create a dataset and assign storage: Policies Prov isioning Data Datasets
101
11
APPENDIX D - VFILER MIGRATE WITH NO DATA COPY
For Reference Only this is not possible in the simulator hands-on lab. SnapMover was previously a separate license and product name. In Data ONTAP 7.3.2 and Data ONTAP 8.0 and later, the SnapMover license and product name have been discontinued. The functionality has been included with the MultiStore license. This functionality can not be demonstrated in a simulator since we dont have software disk ownership, but see below for more information. The major requirement is that the vFiler owns ALL volumes in ALL aggregates used by that vFiler. For FAS controllers, it only works between 2 cluster nod es since both can see the disks at the same time. The vfiler migrate command is issued only once to do the migration since no data mirroring is done, just vfiler stop, disk reassign, and vfiler start. The command to use is:
vfiler migrate -m nocopy
Figure 10) vFiler Migrate No Copy Diagram
FAS
MultiStore POC Example vFiler migrate with SnapMover

ONE Step, ONE Command Migration
Disks/LUNs reassign to different physical node

No Data is Migrated
A to B
FAS6080> vFiler migrate -m nocopy vFiler1@fas6280
Requirements
V-Series
- SnapMover license (included with MultiStore) - Disks/LUNs are under software disk ownership - Disks/LUNs are connected to source/dest nodes
3rd Party DISK (V-series LUNs) lun1,lun2,lun3,lun4,lun5
102
12
APPENDIX E - HOW TO MOVE EXISTING VFILER0 TO A VFILER
It is possible to migrate an existing physical controller to a vFiler unit. There are many considerations to plan for moving a physical controller into a vFiler. There will be downtime to migrate to a vFiler, but if you plan (and pre-write commands or scripts) for all the considerations below, the downtime can be short. In many cases you may take vfiler0 and create more than one vFiler, and that can be extrapolated from the list below. There are a lot of small things to migrate from vfiler0 into the vFiler and these considerations also apply when migrating from one physical controller to another physical controller. Below is a checklist of topics without ONTAP commands (anyone doing this work should know the commands or where to find them). A pre-written plan to execute on-site is the key to success when migrating to a vFiler from a physical controller. A vFiler needs its own small root volume Create a root volume for the vFiler iSCSI Nodename and LUN Mappings Rename the vfiler0 iscsi nodename and reassign the iscsi nodename on the vFiler to match former vfiler0 for no client change (you can leave it different but need to make changes on the clients if you do). Create iGroups in the vFiler Map LUNs to iGroups Hostname Need a new hostname (either for vfiler0 or vFiler depending on which keeps the original hostname). For no host change, often vfiler0 is renamed and the vFiler assumes the name of vfiler0. IPSpaces Do you need to create a separate network from the default -ipspace? IP and Interface, DNS, NIS, LDAP You need a new IP (often put a new management IP on vfiler0 and move existing interfaces on vfiler0 to the vFiler). Domain Membership, FilerSID, Recreate shares and exports We need to rejoin the domain from vFiler using the same netbios name we had in vfiler0, then rejoin with vfiler0 with a new netbios name. Typically vfiler0 rejoins the domain with a new name to free the computer account first. SnapMirror Relationships Need to manually setup additional volumes and then create the dr vf iler manually ,then resync it. Use vfiler0 for the relationship, so this typically involves a new IP address since the new vFiler typically assumes the physical filer address and you have a new hostname and IP for vfiler0 which will be the source of the mirror for vfiler dr. You could use the vfiler IP for snapmirror, but not if using vfiler dr. If Operations Manager use vfiler0 for relationships and update snapmirror.access. NDMP Backups If any backups are set to run against vfiler0 and its ip changes, change the backup software to authenticate to vfiler0s new IP/name. NDMP works for copying but does not work for backup to tape from a vFiler. NDMP backups for the data will need to reauthenticate to vfiler0. SnapVault Relationships Operations Manager uses vfiler0 (hosting filer) for SnapVault relationships. Modify / restart vaults from vFiler0 between source and target instead of direct vfiler to vfiler. Set snapvault.access and ndmpd.preferred_interfaces on vfiler0.
103
VSCAN If any vscanners are set to run against vfiler0 and its ip changes, change the vscan software to authenticate to vfiler0s new I P/name. Unless you want to vscan from the vFiler (most often vscan is centralized for all vFilers at vfiler0). Netbios Aliasing If any netbios aliases are used by vfiler0, they need to be moved to the vFiler. NOTE: this might be an issue if you leave resources on vfiler0 that also need the alias. The same alias cant be in more than o ne filer (virtual or physical). If all resources move to the vFiler, we can move it from vfiler0, but if not, users may be impacted. AutoHome directories If any autohome directories are setup for any volumes moving from vfiler0 to the vFiler, they must be removed from vfiler0 and setup again in the vFiler. Local User Accounts Create local user accounts in vfiler0 in the vFiler. There is a method to export and import registry entries for users. Local Groups Check for local groups from the w indow s mmc and/or /etc/lclgroups.cfg. Make entries in the new vfiler for any groups needed in the vfiler. Domain User Accounts Always check to see if domain user accounts are used in vfile r0 so they can be added to the vFiler. SNMP Match SNMP settings if any snmp monitors are used (OpsManager, etc.) Quotas If any quotas are set on volumes moving from vfiler0 to the vFiler, the /etc/quotas entries need to be removed from /etc/quotas on vfile r0 and created in /etc/quotas on the vFiler, then quota on volname in the vFiler for the volume. User Mappings Copy usermap.cfg entries needed in vfiler1 from vfiler0 (modify / copy / delete as needed for each vfiler) CIFS, NFS, iSCSI Options List all options from vfiler0 and match on the vFiler Fpolicy settings Need to run fpolicy setup in the vFiler Widelinks /etc/symlink.translations (move from the physical controller to the vFiler). SSH, RSH setup Both of these need to be enabled and configured in the vFiler. Volume Names Volume names must be the same on the source and destination for migrate, dr and data motion.
104
2011 NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consent of NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Go further, faster, xxx, and xxx are trademarks or registered trademarks of NetApp, Inc. in the United States and/or other countries. <<Insert third -party trademark notices here.>> All other brands or products are trademarks or registered trademarks of their respective holders and sh ould be treated as such.nTRXXX-XX CR-3-133 Hands-On MultiStore Advanced Lab Guide

Hands-On MultiStore Advanced Lab Guide ONTAP 8.1 7-Mode

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Hands-On MultiStore Advanced Lab Guide ONTAP 8.1 7-Mode

Uploaded by

Copyright:

Available Formats

MultiStore Hands -On Advanced Labs Data ONTAP 8.

Scott Gelb, Insight Integrated Systems

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Table 1) Internal Lab IP Addresses

System Windows Server 2008 R2

CentOS 6 Linux FAS6280 FAS3270 vfiler1 vfiler2 vfiler3

192.168.150.31 192.168.150.210 192.168.150.211 192.168.150.221 192.168.150.222 192.168.150.223

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Table 2) Data ONTAP Simulator Lab Configuration

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Table 3) Data ONTAP Simulator vFiler Units

v filer2 root netapp123

/vol/vfiler1_san/vfiler1_lun1 /vol/vfiler2_san/vfiler2_lun1 /vol/vfiler3_dmotion_root/vfiler3_lun1

CR-3-133 Hands-On MultiStore Advanced Lab Guide

FAS6280 vfiler0 vfiler1 vfiler2 vfiler3

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Rename your vFiler:

CR-3-133 Hands-On MultiStore Advanced Lab Guide

11 max vFiler units 26 max vFiler units 65 max vFiler units

Here we change the vfiler limit in this lab to a maximum of 5.

Disallow rsh, ftp and http:

Use the same command to return to the mai n context of vfiler0.

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

To reconfigure the network interface:

CR-3-133 Hands-On MultiStore Advanced Lab Guide

12. Create another vFiler unit (fas3270_vfiler2):

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Enable FlexCache priority:

Show priority is set:

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Figure 2) FlexClone Between vFiler Units

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Figure 3) Move A Clone Source Between vFiler Units

Figure 4) Add and Remove Volumes From vFiler Units

CR-3-133 Hands-On MultiStore Advanced Lab Guide

19. Remove an IP and volume from vfiler2:

CR-3-133 Hands-On MultiStore Advanced Lab Guide

DATAMOTION FOR VFILER

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Click on the Hosts pane on the left.

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Select Online migration and click Next.

CR-3-133 Hands-On MultiStore Advanced Lab Guide

Select fas3270 and click Next.

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

10. Click Edit.

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

12. Click Next (no SnapMirror throttle).

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide

14. Click Next on the information screen.

CR-3-133 Hands-On MultiStore Advanced Lab Guide

15. Click Finish.

CR-3-133 Hands-On MultiStore Advanced Lab Guide

CR-3-133 Hands-On MultiStore Advanced Lab Guide