Migrating to NetApp ONTAP Using the 7-Mode …Migrating to NetApp ONTAP Using the 7-Mode Transition Tool Copy-Free Transition 2 © 2017 NetApp, Inc. All rights reserved. NetApp Proprietary

Migrating to NetApp ONTAP Usingthe 7-Mode Transition Tool Copy-FreeTransition

January 2017 | SL10256 Version 3.0

Migrating to NetApp ONTAP Using the 7-Mode Transition Tool Copy-Free Transition2 © 2017 NetApp, Inc. All rights reserved. NetApp Proprietary

TABLE OF CONTENTS

1 Introduction...................................................................................................................................... 3

2 Lab Environment............................................................................................................................. 4

3 Lab Activities................................................................................................................................... 6

3.1 Pre-Transition Setup..................................................................................................................6

3.2 Collect & Assess Exercise..................................................................................................... 11

3.3 Create a Transition Project.....................................................................................................17

3.4 Perform Cutover Exercise...................................................................................................... 37

3.5 Volume Re-host Exercise........................................................................................................72

4 References......................................................................................................................................89

5 Version History.............................................................................................................................. 90


1 IntroductionThe 7-Mode Transition Tool enables you to analyze your 7-Mode controllers, hosts, switches, and applicationsto assess their readiness for transition to clustered ONTAP. After assessment is complete you can then usethe 7_mode Transition Tool to plan your transition and implement it using either a copy-based or a copy-freetransition methodology.

A copy-based transition uses SnapMirror technology to copy 7-Mode volumes and configurations from DataONTAP 7G and 7-Mode to ONTAP. In a copy-based transition you migrate data off of a 7-Mode controller ingroups of one or more volumes at a time, meaning you can keep your 7-Mode controller in operation servingsome volumes while other volumes are in the process of migration and yet others have completed migration. Fora copy-based transition to be possible, the 7-Mode source controllers and disks must operate in parallel with thecluster-mode destination controllers, and both source and destination cluster must have enough disks available tosupport their own copies of the migrated data. The overall duration of the transition is longer as you must copy thedata from the source to the destination through SnapMirror, but the actual disruption of services is relatively shortbecause no hardware reconfiguration is necessary during cutover.

A copy-free transition uses disk shelf movement to migrate data from the 7-Mode source controllers to the cluster-mode destination controllers. In a copy-free transition, you disconnect all the disk shelves from the 7-Mode HApair and connect them to an HA pair in the destination cluster. A copy-free transition enables the re-use of the7-Mode disk shelves on the cluster-mode destination, thereby reducing hardware costs, but you also have tomigrate all the volumes on the source cluster at one time as part of the disk shelf moves. The overall duration ofa copy-free transition is generally shorter than a corresponding copy-based transition, as there is no need to copydata over the network from the source to the destination controllers. But the actual cutover is more disruptive andlonger-lasting that a copy-based transition due to all the required hardware reconfiguration involved in disk shelfmoves and recabling.

1 Lab ObjectivesIn this lab you will use the 7-Mode Transition Tool to analyze a 7-Mode environment running CIFS, NFS, andiSCSI for transition to clustered ONTAP, and then migrate that environment to clustered ONTAP by performinga Copy-Free Transition. You will also learn what is involved in migrating Windows and Linux clients to use thetransitioned storage services from their new clustered ONTAP destination.

This lab utilizes NetApp simulators as both the 7-Mode source controllers, and as the cluster-mode destinationcontrollers. The simulators use virtual disks rather than physical disks, and so shelf moves and shelf recabling arenot covered in this lab. But the lab still provides a very authentic copy-free transition experience using the 7-ModeTransition Tool.

1 Prerequisites• A basic understanding of NetApp Data ONTAP (7-Mode)• A basic understanding of NetApp Clustered Data ONTAP


2 Lab EnvironmentThe following figure contains a diagram of the environment for this lab.

Figure 2-1:

All of the servers and storage controllers presented in this lab are virtual devices, and the networks thatinterconnect them are exclusive to your lab session. While we encourage you to follow the demonstration stepsoutlined in this lab guide, you are free to deviate from this guide and experiment with other ONTAP features thatinterest you.

While the virtual storage controllers (vsims) used in this lab offer nearly all of the same functionality as physicalstorage controllers, they are not capable of providing the same performance as a physical controller, which is whythese labs are not suitable for performance testing.

Table 1 provides a list of the servers and storage controller nodes in the lab, along with their IP addresses.

Hostname OperatingSystem Role/Function IP address User ID Password

fas01 Data ONTAP 8.2.3 7-Mode Node 1 192.168.0.121 root Netapp1!

fas02 Data ONTAP 8.2.3 7-Mode Node 2 192.168.0.122 root Netapp1!


Hostname OperatingSystem Role/Function IP address User ID Password

cluster1clustered DataONTAP 8.3.2

clustered DataONTAP

192.168.0.101 adminNetapp1!

jumphostMicrosoft WindowsServer 2012 R2(64-bit)

CIFS & iSCSI client 192.168.0.5 DEMO\Administrator Netapp1!

rhel1Red Hat EnterpriseLinux 6.8 (64-bit)

NFS client 192.168.0.61 rootNetapp1!


3 Lab ActivitiesThe lab is broken out into various sections. Sections 2 and 5 can be skipped if desired, but all sections haveinterdependencies and must be executed in sequence.

1. Pre-Transition Setup.2. Collect & Assess a 7-Mode environment for transition.3. Create a Transition Project.4. Perform a Transition Cutover.5. Rehost volumes to other SVMs Post-Transition.

3.1 Pre-Transition SetupBefore you launch the 7-Mode, take a moment to familiarize yourself with the storage services that the 7-Modecontrollers are providing to Jumphost, and then launch the 7-Mode Transition Tool.

1. On the taskbar of Jumphost, launch Windows Explorer.

1

Figure 3-1:

Windows Explorer opens.

2. In Windows Explorer, click This PC.3. Observe that there are four 5 GB LUNs mapped on Jumphost as the L:, M:, N:, and O: drives,

respectively. Lun1 and lun2 are hosted on fas01, lun3 and lun4 are hosted on fas02. There is also a \\192.168.0.121\vol1 share from fas01 mounted as the P: drive.

4. Open the L: drive.


2

3

4

Figure 3-2:

5. The L: drive contains a single file named “lun1_file.txt” to provide some content for the LUN. Feel free toexamine the file's contents, and you are welcome to create any additional files in this LUN that you mightwant to include in the transition.

6. ClickThis PC again to navigate back to the list of mapped drives.

5

6

Figure 3-3:


7. Examine the contents of the M:, N:, and O: drives. If you like you can create additional files on thosedrives too.

8. Examine the contents of the \\192.168.0.121\vol1 share mounted as the P: drive, and note thatit includes a pre-created file named “vol1_file.txt”. If you want to add any extra files of your own to thisshare, add them now.

7

8

Figure 3-4:

Now it's time to start up the 7-Mode Transition Tool.

9. On the desktop of Jumphost, launch the NetApp 7-Mode Transition Tool 3.0.0 shortcut.

Caution: The arrangement of the shortcuts on your desktop may differ from the arrangement ofshortcuts shown in the following screenshot (and in other screenshots of the Jumphost desktoplater in this lab guide), but the needed shortcuts will all be present.


9

Figure 3-5:

10. Fill in the credentials as the username DEMO\Administrator with the password Netapp1!.11. Click Sign In.


10

11

Figure 3-6:

12. The 7-Mode Transition Tool displays the Home tab13. The buttons at the top of the window provide access to the various high-level aspects of the 7-Mode

Transition Tool's capabilities.

Attention: The 7-Mode Transition tool requires a minimum screen resolution of 1280x1024 orhigher. If your web browser is set to a size smaller than a 1280x1024 viewing area then you willmost likely not be able to see all the fields and controls in the tool, as the tool does not providescroll bars for most windows.


1213

Figure 3-7:

3.2 Collect & Assess ExerciseIn this exercise you will run an assessment against the lab's 7-Mode controllers and the clients that utilize itsstorage.

1. In the row of buttons at the top of the 7-Mode Transition Tool window, click Collect & Assess to openthe “Collect & Assess” tab.

2. On the menu bar above the system list pane, click Add Systems.


12

Figure 3-8:

The “Add System” window opens.

3. Populate the fields as follows to add the 7-Mode system fas01 to the system list.

• “Name/IP”: fas01• “Username”: root• “Password”: Netapp1!• “Type”: Data ONTAP Storage

4. Click Add.


3

4

Figure 3-9:

The “Add System” window closes, and focus returns to the 7-Mode Transition Tool browser window.5. Using the following data, repeat the procedure in steps 2 - 4 to add the 7-Mode system fas02 to the

system list.

• “Name/IP”: fas02• “Username”: root• “Password”: Netapp1!• “Type”: Data ONTAP Storage

6. Using the following data, repeat the procedure in steps 2 - 4 again to add the Linux system rhel1 to thesystem list.

• “Name/IP”: rhel1• “Username”: root• “Password”: Netapp1!• “Type”: Red Hat Enterprise Linux

7. Using the following data, repeat the procedure in steps 2 - 4 one last time to add the Windows hostjumphost (the host on which the 7MTT tool is installed) to the system list.

• “Name/IP”: localhost• “Username”: <enter a single space>• “Password”: <leave this field blank>• “Type”: Microsoft Windows

You should now see the four systems you just entered listed in the “Collect & Assess” pane.8. Select the checkboxes for all of the systems in the list.9. Click Create Transition Assessment Report.


8 9

Figure 3-10:

The “Create Transition Assessment Report” window opens.

10. Select a Data ONTAP target version of 8.3.2.

Note: This lab utilizes ONTAP 8.3.2 as the target, but the migration tool also supports ONTAP 9targets.

11. Click Generate Report.

10

11

Figure 3-11:

The “Create Transition Assessment Report” window closes, and focus returns to the “Collect & Assess”tab in the 7MTT browser window.

Scroll to the bottom of the window to monitor progress and wait for assessment to complete.


Attention: The tool reports that the assessment make take as long as 15 minutes to run, but inthis lab it should only take a couple of minutes.

12. Once the assessment completes, click the xls link that appears in the “Progress Monitor” pane todownload/view the Transition Assessment Workbook.

12

Figure 3-12:

The “Opening AssessmentWorkbook.xml” window opens.

13. Click OK to open the document.


13

Figure 3-13:

The “Opening AssessmentWorkbook.xml” window closes, and Microsoft Excel opens and displays theworkbook's “Data Collection Summary” tab. This page provide links to the various sub-reports availablein this workbook.

14. Click the Transition Feasibility (CFT) link (or alternately find and select the Transition Feasibility(CFT) tab at bottom of the spreadsheet window).

15. See if there are any blocking errors that would prevent a Copy-Free Transition. In this lab you will notsee any blocking errors listed on that page.

1415

Figure 3-14:

There are lots of other tabs you can review for additional messages, including:


• “Config PreCheck Summary” Tab. Check to see if any objects in use on your 7-Modesystems that have changed in clustered Data ONTAP are applicable to your environment. Ifso, refer to the associated corrective action.

• “SAN Hosts” Tab: Check for MPIO Assessment to see if driver is supported.• “SAN Host HBAs” Tab: Check for HBA assessment to see if driver is supported.

Understanding these reports in any detail is beyond the scope of this lab. For a transition performedoutside of this lab you should review these files and implement any remediation steps before attemptingto proceed with the transition.

16. Close Excel.

16

Figure 3-15:

The workbook closes and focus returns to the "Collect & Assess" page in the 7-Mode Transition Toolbrowser window.

17. Close the Collect and Assess tab.

17

Figure 3-16:

The browser displays the “7-Mode Transition Tool Home” tab.

3.3 Create a Transition ProjectA transition project describes the set of volumes and storage services you have on your 7-Mode controllers, andhow you want to map those elements to the cluster-mode controllers during the migration.

1. If you do not already have the 7-Mode Transition Tool running from the previous exercise, launch it fromthe desktop of Jumphost, and log in as the user DEMO\Administrator with the password Netapp1!, afterwhich the browser should be displaying the 7MTT Home tab.


2. Click Plan & Design.

1 2

Figure 3-17:

The “Plan Migration” window opens.

3. Select the Copy-Free Transition radio button.4. Click Start Planning.

3

4

Figure 3-18:

The “Plan Migration” window closes, and the “Prerequisite for Copy-Free Transition” window opens.5. Check the checkboxes in each confirmation section as follows:

• “Assessment”: check Discovered the Environment.• “Host and Application Remediation”: check Not Applicable.• “SAN FC Zoning”: check Not Applicable.

6. Click Continue.


5

6

Figure 3-19:

The “Prerequisite for Copy-Free Transition” window closes, and focus returns to the “7MTT” browserswindow, where a new (CFT) Untitled Project tab has opened.

7. If there are not already entries in the 7-Mode Controllers list for fas01 and fas02, or there is not alreadyan entry in the Clustered Data ONTAP Systems list for cluster1, then use the controls in the “EnterDevice Credentials” box to add these systems to their repective lists by using the following values::

• cluster1 Hostname: cluster1, Username: admin, Password: Netapp1!• fas01 Hostname: fas01, Username: root, Password: Netapp1!• fas02 Hostname: fas02, Username: root, Password: Netapp1!

8. Click Add after populating the device credentials fields for each of the systems listed in the precedingstep.

9. All 3 controllers now appear in their respective lists.10. On the far right side of the window, click Next. This launches the wizard for the Plan & Design process.


7

8

9

10

Figure 3-20:

The Plan & Design wizard advances to the “Select Source Systems” stage.

11. In the “Select 7-Mode HA pair” list select the checkbox for fas01/fas02.12. In the middle of the far right of the window, click Create Project.


11

12

Figure 3-21:

The “Project Details” window opens.13. Set the “Project Name” field to fas01_fas02.14. Click Save.


13

14

Figure 3-22:

The “Project Details” window closes, and the Plan & Design wizard now advances to the “Select Clusterand Map Nodes” stage. This is where you specify the target cluster, and how the disk shelves on the 7-Mode controllers will map to the nodes in the target cluster.

15. Note that the text in the former (CFT) Untitled Project tab has now been updated to reflect the projectname you just entered. It now displays (CFT) fas01_fas02.

16. In the “Select Target HA Pair Nodes” pane, check the checkbox next to cluster1-01/cluster1-02.17. In the “Source to Target Node Mapping” pane, make sure that the nodes map as follows:

• fas01 to cluster1-01• fas02 to cluster1-02

If the mapping is swapped in your lab then use the Swap Node Mapping button to correct the mappingto the desired state.

18. In the middle of the far right side of the page, click Save and Continue.


15

16

17

18

Figure 3-23:

The Plan & Design wizard advances to the “Map SVMs and Volumes” stage. This is where you willselect which SVM on the destination cluster will be the target of the copy operation for each 7-Modecontroller.

Note: Each 7-Mode source vFiler must map to a unique target SVM.

19. In the table headings, hover the mouse over the ? icon next to the “Junction Path Policy” columnheader to see a description of the avilable junction path policies. For this lab you will keep the defaultvalue of “Preserve 7-Mode Mount Paths”.

20. In the “Storage System/vFiler Unit” list, in the vfiler0 entry under fas01, set the “Select Target SVM”dropdown to svm_fas01.

21. Still in the fas01 vfiler0 row, click Save Mapping.


19

20 21

Figure 3-24:

The vfiler0 row expands to show all the volumes that are on vfiler0.22. Observe that the volume entries are now pre-fixed by green circles indicating that they are mapped to a

target. In this instance that target is svm_fas01.23. The target volume names default to the same names they have on fas01 vfiler0.24. If you wanted to edit the target volume names, you would need to use the “edit” icon to the right of each

entry. However, for this exercise the default names are sufficient, so leave them as is.25. Use the +/- icon to the left of fas01 vfiler0 to collapse the volume list.

2223

24

25

Figure 3-25:

26. The entry for fas01 vfiler0 also has a green circle, indicating this vfiler's volumes are mapped.27. Note that the button in the fas01 vfiler0 row has changed from “Save Mapping” to “Clear Mapping”,

giving you the ability to change the mapping if you needed to.28. In the vfiler0 entry for fas02, set the “Select Target SVM” dropdown to svm_fas02.29. Still in the fas02 vfiler0 row, click Save Mapping.


30. The fas02 vfiler0 entry expands to display the volume mappings.

2627

28 29

30

Figure 3-26:

31. In the middle of the far right of the window, click Next.


31

Figure 3-27:

The Plan & Design wizard advances to the “Configure Networking” stage. This is where you selectwhich IP addresses on the destination cluster will be used for the transition. You can choose to eithertransition the 7-Mode controller's existing LIFs (e.g., IP addresses), or you can create new LIFs withnew IPs.

For this lab you will be transitioning the 7-Mode controller's LIFs to the destination cluster32. Click Select 7-Mode LIF.


32

Figure 3-28:

The “Select 7-Mode LIF” window opens.

33. In the column header row, check the checkbox next to Storage System/vFiler Unit, which will causeall the rows in the table to be selected.

34. Change the target port for both vfiler0 entries to e0d.35. Click Save.

3334

35

Figure 3-29:

The “Select 7-Mode LIF” window closes, and focus returns to the “Configure Networking” stage of thePlan & Design wizard.

36. Click the Next button located in the middle of the far right side of the window.


36

Figure 3-30:

The Plan & Design wizard advances to the “Plan Configuration” stage. This is where you can furthercustomize the transition configuration, including but not limited to modifying NFS export rules, snapshotschedules, CIFS and NFS options, and so on.

37. Note that you can customize the available settings on a per-SVM basis.38. Although examining these settings in detail lies outside the scope of this lab, take a moment to review

the various customization settings available here. By default all the checkboxes are selected, which isacceptable for this lab exercise.

39. Click Save and go to Dashboard on the right side of the window.


3738

39

Figure 3-31:

The Plan & Design wizard terminates, and the 7-Mode Transition Tool switches over to the MigrationDashboard, which includes a graphic of the transition workflow at the top of the window. The dashboardis where the 7-Mode Transition Tool actually invokes migrations, but in this exercise you are going tofocus on just the precheck portion. A precheck runs an analysis of the source, and targets controllersinvolved in the current transition project, looking for configuration problems that might block thetransition.

40. Click Run Prechecks.


40

Figure 3-32:

A precheck operation status window opens, and tracks the progress of the various checks that the toolis running. Individual checks can return, in increasing order of severity, informational, warning, or errorstatus results, and in most cases the tool provides suggestions for remediating a found issue. Errorstatus results will block a transition completely. Warnings and informational message will not block atransition, but the issues they point out may produce undesireable transition results, and so you shouldreview them and consider whether you want to take corresponding action.

It is quite common for the tool to find issues at this stage that require remediation. The specific issuesthe tool will find can vary significantly from system to system, and in the interests of time this lab cannot cover all of the possibilities. However, this exercise is designed to generate an error to give you aflavor for what the experience is like.

41. The prechecks complete but return an overall operation status of “Failed”.42. The check type summary list indicates that an error occured during the SAN prechecks.43. Expand the SAN prechecks section.44. If necessary, scroll down to view the details of the specific WAFL check that failed.45. The “Message” column details the specific problem the tool found. In this example the tool indicates an

error because one of the target SVMs in the cluster does not have iSCSI LIFs configured for all nodes.46. The “Recommended Action” column presents a list of some potential remediation actions you might

take in response. In this exercise you will implement this recommended action to correct the problem,so please read the full recommendation.

47. Click the Cluster Nodes link.


41

42

43 4446

45

47

Figure 3-33:

The “Cluster Nodes” window opens, and displays a list of the cluster nodes that are affected by theissue.

48. In this case the svm_fas01 SVM does not have an iSCSI LIF on node cluster1-02.49. Click Close.

48

49

Figure 3-34:


The “Cluster Nodes” window closes, and focus returns to the “Precheck Operation Status” window.

Remediate this error by creating an iSCSI LIF for svm_fas01 on cluster1-02.50. On the taskbar of Jumphost, launch PuTTY.

50

Figure 3-35:

The “PuTTY Configuration” window opens.

51. Double-click the saved session profile for cluster1.

51

Figure 3-36:

A PuTTY session window open to cluster1.

52. Log in as the user admin, with the password Netapp1!.


53. Display a list of the LIFs for the svm_fas01 SVM.

cluster1::> network interface show -vserver svm_fas01 Logical Status Network Current Current IsVserver Interface Admin/Oper Address/Mask Node Port Home----------- ---------- ---------- ------------------ ------------- ------- ----svm_fas01 iscsi_lif1 up/up 192.168.0.125/24 cluster1-01 e0c true lif1 up/up 192.168.0.124/24 cluster1-01 e0c true2 entries were displayed.

cluster1::>

As indicated by the pre-check, there is only an iSCSI LIF for node cluster1-01.

54. Create a new iSCSI LIF named “iscsi_lif2” for the SVM on node cluster1-02. .

cluster1::> network interface create -vserver svm_fas01 -lif iscsi_lif2 -role data -data-protocol iscsi -home-node cluster1-02 -home-port e0c -address 192.168.0.126 -netmask-length 24

cluster1::>

55. View the LIF list again.

cluster1::> network interface show -vserver svm_fas01 Logical Status Network Current Current IsVserver Interface Admin/Oper Address/Mask Node Port Home----------- ---------- ---------- ------------------ ------------- ------- ----svm_fas01 iscsi_lif1 up/up 192.168.0.125/24 cluster1-01 e0c true iscsi_lif2 up/up 192.168.0.126/24 cluster1-02 e0c true lif1 up/up 192.168.0.124/24 cluster1-01 e0c true3 entries were displayed.

cluster1::

56. Exit the PuTTY session to fas01.

cluster1> exit

The PuTTY window closes.

57. Bring the 7-Mode Transition Tool browser window back into focus. The browser should still bedisplaying the “Precheck Operation Status” window.

58. Click Close.


58

Figure 3-37:

The “Precheck Operation Status” window closes, and focus returns to the “Migration Dashboard”.

59. Notice that the circle for Plan phase of the transition workflow is red, indicating an error.60. Click Run Prechecks.


59

60

Figure 3-38:

The precheck operation status window opens again.

61. This time the precheck completes with an operation status of “Successful (With warnings)”.62. Feel free to examine some of the warning messages the precheck generated, but this exercise does

not require you to act on any of these warnings.63. Click Close.


61

62

63

Figure 3-39:

The “Precheck Operation Status” windows closes, and focus returns to the “Migration Dashboard”.

64. The “Plan” phase of the transition workflow now shows a green circle.


64

Figure 3-40:

3.4 Perform Cutover ExerciseA cutover is the process to migrate your data and storage services from the 7-Mode source controllers to thecluster-mode destination controllers.

You should still be on the Migration Dashboard from the end of the preceding exercise. In this exercise you willinitiate the actual cutover.

1. Click Apply SVM Config.


1

Figure 3-41:

A “Confirmation” window opens.

Important: Read the contents of the “Confirmation” window as it contains important detailsregarding the cutover procedure.

2. Click Yes to continue with the operation.

2

Figure 3-42:

The “Confirmation” window closes, and the “Apply SVM Configuration Operation Status” window opensand runs the prechecks again.

Note: While it may seem redundant to run the prechecks again, in production environments asignificant amount of time may have passed between the creation of the project and the start ofthe cutover. Rerunning the prechecks evaluates any changes that may have been made to thesource or destination in the interim.


3. The prechecks run again, followed by collecting and applying configurations. This process will takeseveral minutes.

4. When the configuration applications complete, the “Operation Status” field changes to “Successful (Withwarnings)”.

5. Click Close.

3

4

5

Figure 3-43:

The “Apply SVM Configuration Operation Status” window closes, and focus returns to the MigrationDashboard.

6. The “SVM Provisioning” circle in the workflow graphic has now turned green, indicating success.7. Click Check Readiness

67

Figure 3-44:

The “Cutover Readiness Check Operation Status” window opens.


This is an optional step that re-runs the prechecks run. Once again, in a production environment asignificant period of time may have elapsed between the time you applied the SVM configuration andthe time you initiate the actual cutover. This test allows you to check for configuration changes that mayhave been applied to controllers in the interrim that might adversely affect the cutover.

8. The checks complete with the status of “Successful (With warnings).9. Click Close.

8

9

Figure 3-45:

The “Cutover Readiness Check Operation Status” window closes, and focus returns to the MigrationDashboard.

10. The “Check Readiness” button is still active to allow you to run it again if needed. It is a best practice torun through “Check Readiness” immediately before “Export & Halt”, even if this project has passed thistest at some prior point in time.

10

Figure 3-46:


Note: Before you initiate the cutover, you should disable client access to the LUNs, shares,and NFS volumes to avoid potential data loss or corruption that might otherwise occur, as thecutover is a disruptive process. This has to be done at the client because 7MTT requires that allprotocol services be running on the controllers so it can gather data.

11. On the desktop of Jumphost, launch Computer Management.

11

Figure 3-47:

The “Computer Management” MMC window opens.

12. Navigate to Computer Management (Local) > Storage > Disk Management.13. In the lower pane, right click on Disk1, and select Offline from the context menu.

Attention: Right-click in the box to the left of the partition graphic. If you right-click inside thepartition graphic then the resulting context menu will not contain an entry to offline the disk.


12

13

Figure 3-48:

Disk 1 now shows as offline in the MMC.

14. Repeat the procedure from step 13 to mark Disk2, Disk3, and Disk4 offline as well.15. Close the “Computer Management” MMC window.


14

15

Figure 3-49:

The “Computer Management” MMC window closes.

16. On the desktop of Jumphost, launch iSCSI Initiator.


16

Figure 3-50:

The “iSCSI Initiator Properties” window opens.

17. Select the Targets tab.18. In the “Discovered targets” list, select the first entry.19. Click Disconnect.


17

18

19

Figure 3-51:

The “Disconnect From All Sessions” window opens.

20. Click Yes.

20

Figure 3-52:

The Disconnect From All Sessions” window closes, and focus returns to the “iSCSI Initiator Properties”window.

21. The status of the first connection has changed to “Inactive”.


22. Repeat steps 18 - 20 for the second entry in the “Discovered Targets” list.23. The status of the both connections should now be “Inactive”.

21

22 23

Figure 3-53:

24. Click the Discovery tab.25. In the “Target portals” list, select the entry for fas01.26. Click Remove.


24

25

26

Figure 3-54:

27. Repeats steps 25 - 26 for fas02.28. The Target portals list is now empty.29. Click OK.


28

29

Figure 3-55:

The “iSCSI Initiator Properties” window closes.

30. From the taskbar of Jumphost, open Windows Explorer.


30

Figure 3-56:


31. Click This PC.32. In the right pane locate the P: drive, right-click on it and select Disconnect from the context menu.33. Close Windows Explorer.


31

32

33

Figure 3-57:

34. On the taskbar of Jumphost, launch PuTTY.


34

Figure 3-58:


35. In the “Saved Sessions” list, double-click the entry for rhel1.

35

Figure 3-59:

A PuTTY terminal session window opens for rhel1.

36. Log in as the username root, with the password Netapp1!.37. Display a list of the mounted filesystems.

[root@rhel1 ~]# dfFilesystem 1K-blocks Used Available Use% Mounted on/dev/mapper/vg_rhel1-lv_root 11746316 5322440 5820536 48% /


tmpfs 444476 76 444400 1% /dev/shm/dev/sda1 487652 75314 386738 17% /boot192.168.0.121:/vol/vol1 19922944 320 19922624 1% /mnt/vol1[root@rhel1 ~]#

38. Unmount /mnt/vol1.

[root@rhel1 ~]# umount /mnt/vol1[root@rhel1 ~]#

39. Verify that /mnt/vol1 is no longer mounted.

[root@rhel1 ~]# dfFilesystem 1K-blocks Used Available Use% Mounted on/dev/mapper/vg_rhel1-lv_root 11746316 5322440 5820536 48% /tmpfs 444476 76 444400 1% /dev/shm/dev/sda1 487652 75314 386738 17% /boot[root@rhel1 ~]#

40. Minimize the PuTTY session window to rhel1 so you can use it again later.41. Return to the 7-Mode Transition Tool browser window.42. Click Export & Halt.

42

Figure 3-60:

A “Confirmation” window opens, advising you what will happen during the cutover.

Important: Read the contents of the Confirmation window!

43. Check the Confirm that the client access is disconnected checkbox.44. Click Yes.


43

44

Figure 3-61:

The “Confirmation” window closes, and the “Export & Halt Operation Status” window opens.

45. When the “Export & Halt” operation completes, the Operation Status changes to “Successful (Withwarnings)” in green.

Note: The Export & Halt procedure executes very quickly because this lab uses simulators. Onphysical hardware this step requires more time to complete.

46. Click Close.


45

46

Figure 3-62:

The “Export & Halt Operation Status” window window closes, and focus returns to the MigrationDashboard.

47. The graphic for the transition workflow now shows a green circle for the Export phase.

47

Figure 3-63:

When transitioning physical controllers, this is the point where you would re-cable the 7-Modecontrollers' disk shelves over to the target node controllers. There is no physcial re-cabling necessaryfor the simulators used in this lab, but there are functionally equivalent configuration changes that needto be applied to them. Those changes are simluator-specific, and so are handled in this lab by a script.

48. On the desktop of Jumphost, launch the move_shelves.bat script.


48

Figure 3-64:

The move_shelves script window opens.

49. Read the script output and follow its instructions.50. The script takes 1-2 minutes to run, and if the script completes successfully then the script window

turns green. If the script window instead turns red, contact Hands-On Labs or Lab on Demand supportfor assistance.

51. If the script completes successfully then, with the script window in focus, click any key to acknowledgeand close the window.


49

5051

Figure 3-65:

The “move_shelves” window closes.

52. Return to the 7-Mode Transition Tool browser window, which should still be displaying the MigrationDashboard.

53. Click Verify Cabling.

53

Figure 3-66:


54. Read the contents of the window. You will not be downloading and installing the Config Advisor toolin this lab, as there is no cabling for it to check on the simulators, but if you are transitioning physicalcontrollers then you would want to follow the procedure described in the Confirmation window.

55. Click Yes.


54

55

Figure 3-67:

The “Confirmation” window closes, and the “Verify Cabling Operation Status” window opens.

56. Wait until the operation completes.

Note: Once again, this check completes very quickly because this lab is using simulators. Thischeck takes noticeably longer when physical controllers are involved.

57. Click Close.

56

57

Figure 3-68:

The “Verify Cabling Operation Status” window closes, and focus returns to the Migration Dashboard.

58. The graphic for the transition workflow now shows a green circle for the Cabling phase.59. Click Import.


58

59

Figure 3-69:


60. This is the stage where the 7-Mode system storage components will migrate over to the target nodesand will change over to formats compatible with clustered ONTAP. Read the information presented inthe Confirmation window for further details.

61. Click Yes.

60

61

Figure 3-70:

The “Confirmation” window closes, and the “Import Operation Status” window opens.

62. When the import operation completes, the status at the top of the window changes to “Successful” ingreen.

Attention: In this lab the import operation just takes a couple of minutes. In a productionenvironment (with more complex configuration and larger data sets) the import operation willtake noteably longer.

63. Click Close.


62

63

Figure 3-71:

The “Import Operation Status” window closes, and focus returns to the Migration Dashboard.

64. The transition workflow graphic now shows a green circle for the Import phase.

64

Figure 3-72:

At this point it's still possible to roll back the transition to the 7-Mode controllers (initiated with the “GoTo Rollback Dashboard” button, an activity that lies outside the scope of this lab), but once you committhe transition that will no longer be the case. So, this is a good time to go and check your clients forproper operation (i.e., before you initiate the Commit operation).



65

Figure 3-73:


66. Click the Discovery tab.67. Click Discover Portal....


66

67

Figure 3-74:

The “Discover Target Portal” window opens.

68. Set the “IP Address or DNS name” field to 192.168.0.125.

Note: Remember that 192.168.0.125 and 192.168.0.126 are the IP addresses of the iSCSI LIFson svm_fas01.

69. Click OK.

69

68

Figure 3-75:

The “Discover Target Portal” window closes, and focus returns to the “iSCSI Initiator Properties”window.

70. Click Discover Portal... again.


70

Figure 3-76:


71. Set the “IP address or DNS name” field to 192.168.0.135.

Note: 192.168.0.135 and 192.168.0.136 are the IP address of the iSCSI LIFs on svm_fas02.72. Click OK.

72

71

Figure 3-77:


73. The “Target portals” list contains entries for both of the addresses you just entered.


73

Figure 3-78:

74. Select the Targets tab.75. In the “Discovered targets” list, select the first list entry.76. Click Connect.


74

75

76

Figure 3-79:

The “Connect To Target” window opens.

77. Check Enable multi-path.78. Click OK.

77

78

Figure 3-80:


The “Connect To Target” window closes, and focus returns to the “iSCSI Initiator Properties” window.

79. Repeat steps 75 - 78 for the second entry in the “Discovered targets” list.80. Both entries in the “Discovered Targets” list now show as “Connected”.

79

80

Figure 3-81:

81. Select the Volumes and Devices tab.82. Click Auto Configure.83. The “Volume List” box is populate with entries for the L:, M:, N:, and O: drives.84. Click OK.


81

82

83

84

Figure 3-82:




85

Figure 3-83:


86. In Windows Explorer, click This PC.87. Verify that the L:, M:, N:, and O: drives are connected, and that the files that were present on this

drives when they were hosted on the 7-Mode controllers are still present.

86

87

Figure 3-84:

Now reconnect the CIFS share.88. With This PC still selected, navigate to Computer > Map Network Drive.


88

Figure 3-85:

The “Map Network Drive” window opens.

89. Set the fields in this window as follows:

• “Drive”: P:• “Folder”: \\192.168.0.121\vol1• “Reconnect at sign-in checkbox”: checked

90. Click Finish.


89

90

Figure 3-86:

A new Windows Explorer window opens that displays the contents of the newly mapped share.

91. Verify the folders contents match the files that were there while the share was still hosted on the 7-Mode controllers, including any custom files you may have created on your own.

92. Verify that the share is writable by creating a new text file named newfile.txt.93. Close both Windows Explorer windows.

91

92

93

Figure 3-87:


94. Bring the PuTTY session to rhel1 that you minimzed earlier back into focus. If that window is nolonger available, open a new PuTTY session to rhel1, and log in as the user root with the passwordNetapp1!.

95. Display a list of the mounted filesystems.

[root@rhel1 ~]# dfFilesystem 1K-blocks Used Available Use% Mounted on/dev/mapper/vg_rhel1-lv_root 11746316 5322472 5820504 48% /tmpfs 444476 76 444400 1% /dev/shm/dev/sda1 487652 75314 386738 17% /boot[root@rhel1 ~]#

96. Mount

[root@rhel1 ~]# mount -a[root@rhel1 ~]#

97. Re-display the list of mounted filesystems.

[root@rhel1 ~]# dfFilesystem 1K-blocks Used Available Use% Mounted on/dev/mapper/vg_rhel1-lv_root 11746316 5322472 5820504 48% /tmpfs 444476 76 444400 1% /dev/shm/dev/sda1 487652 75314 386738 17% /boot192.168.0.121:/vol/vol1 19922944 320 19922624 1% /mnt/vol1[root@rhel1 ~]#

98. Examine the directory you just mounted and verify that you can read and write files there.

[root@rhel1 ~]# cd /mnt/vol1[root@rhel1 vol1]# lsnewfile.txt vol1_file.txt[root@rhel1 vol1]# cat vol1_file.txtTest file on vol1.[root@rhel1 vol1]# touch nfsfile.txt[root@rhel1 vol1]# ls -altotal 12drwxr-xr-x 2 root root 4096 Sep 18 21:17 .drwxr-xr-x. 3 root root 4096 Sep 11 06:47 ..-rwxr-xr-x 1 root bin 0 Sep 18 21:12 newfile.txt-rw-r--r-- 1 root root 0 Sep 18 21:17 nfsfile.txtdrwxrwxrwx 8 root root 4096 Sep 18 20:00 .snapshot-rwxr-xr-x 1 root bin 20 Sep 5 00:29 vol1_file.txt[root@rhel1 vol1]#

This confirms that NFS access to vol1 is still working after the cutover, and that the mount is stillwriteable.

99. Exit the PuTTY session to rhel1.

exit

100. Return to the 7-Mode Transition Tool browser window, which should still be open to the MigrationDashboard.

101. Click Commit.


101

Figure 3-88:

A “Warning” window opens.102. Read the information presented.103. Click Yes.

102

103

Figure 3-89:

The “Commit Operation Status” window opens.

104. When the Commit operation completes the Operation Status field displays “Successful” in green.105. Click Close.


104

105

Figure 3-90:

The “Commit Operation Status” window closes, and focus returns to the Migration Dashboard.106. The transition workflow graphic now displays a green circle for the Commit phase.107. Close the 7-Mode Transition Tool browser window.

106

107

Figure 3-91:

This completes this exercise.

3.5 Volume Re-host ExerciseDuring a copy-free transition you must migrate all the volumes on a source 7-Mode controller to the samedestination Storage Virtual Machine (SVM). However, once the transition is over it is possible to move thosevolumes to a different SVM.

In this exercise you will migrate LUN volumes you transitioned to svm_fas01 to a different SVM.



1

Figure 3-92:


2. Select the Targets tab.3. In the “Discovered targets” list, select the first entry.4. Click Disconnect.


2

3

4

Figure 3-93:

The “Disconnect From All Sessions” window opens.

5. Click Yes.

5

Figure 3-94:

The Disconnect From All Sessions” window closes, and focus returns to the “iSCSI Initiator Properties”window.

6. The status of the first connection has changed to “Inactive”.


7. Repeat steps 3 - 6 for the second entry in the discovered target list.8. The status of the both connections should now be “Inactive”.

6

7

8

Figure 3-95:

9. Click the Discovery tab.10. In the “Target portals” list, select the entry for 192.168.0.125.11. Click Remove.


9 10

11

Figure 3-96:

The “Remove Target Portal” window opens, warning that there are persistent bindings to the removedtarget portal.

12. Click OK to aknowledge the warning.

12

Figure 3-97:

The “Remove Target Portal” window closes, and focus returns to the “iSCSI Initiator Properties”window.

13. The entry for the 192.168.0.125 address no longer appears in the “Target portals” list.14. Repeats steps 10 - 13 for 192.168.0.135.15. The Target portals list is now empty.16. Click OK to close the “iSCSI Initiator Properties” window.


15

16

Figure 3-98:


17. On the taskbar of Jumphost, launch PuTTY.


17

Figure 3-99:


18. Select the “Saved Session” for cluster1.19. Click Open.

18

19

Figure 3-100:

A PuTTY terminal session opens for cluster1.20. Log in as the user admin, with the password Netapp1!.21. The command to rehost a volume requires advanced priviliges, so elevate the CLI session privilege

level.

cluster1::> set -priv advanced


Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.Do you want to continue? {y|n}: y

cluster1::*>

22. Issue the ONTAP CLI command to rehost san_vol1 to the svm_iscsi SVM.

Note: The rehost command is an advanced privilige level command, so you will first need toelevate the the CLI session privilege level.

cluster1::*> volume rehost -vserver svm_fas01 -volume san_vol1 -destination-vserver svm_iscsi -auto-remap-luns true

Warning: Rehosting a volume from one Vserver to another Vserver does not change the security information on that volume. If the security domains of the Vservers are not identical, unwanted access might be permitted, and desired access might be denied. An attempt to rehost a volume will disassociate the volume from all volume policies and policy rules. The volume must be reconfigured after a successful or unsuccessful rehost operation. See the "7-Mode Transition Tool 2.2 Copy-Free Transition Guide" for reconfiguration details.Do you want to continue? {y|n}: y[Job 277] Job is queued: Volume rehost operation on volume "san_vol1" on Vserver "svm_fas01" to destination Vserver "svm_iscsi" by administrator "admin"..Error: command failed: [Job 277] Job failed: Volume rehost pre-check failed for reasons: Cannot rehost volume "san_vol1" on Vserver "svm_fas01" because the volume is part of a junction path. Use the "volume show -vserver svm_fas01 -volume san_vol1 -fields junction-path" command to view a volume's junction path. Use the "volume unmount" command to remove the junction path.

cluster1::*>

The rehost job fails because the volumes are junctioned in the SVM's namespace even though theseSAN volumes are not accessed through NAS protocols.

23. View a list of the junction paths for all of the SVMs on cluster1.

cluster1::*> volume show -fields junction-pathvserver volume junction-path ----------- ------ ------------- cluster1-01 vol0 - cluster1-02 vol0 - svm_fas01 san_vol1 /vol/san_vol1 svm_fas01 san_vol2 /vol/san_vol2 svm_fas01 svm_fas01_root / svm_fas01 testvol1 /testvol1 svm_fas01 vol0 /vol/vol0 svm_fas01 vol1 /vol/vol1 svm_fas01 vol2 /vol/vol2 svm_fas02 san_vol3 /vol/san_vol3 svm_fas02 san_vol4 /vol/san_vol4 svm_fas02 svm_fas02_root / svm_fas02 testvol2 /testvol2 svm_fas02 vol0 /vol/vol0 svm_fas02 vol3 /vol/vol3 svm_fas02 vol4 /vol/vol4 svm_iscsi svm_iscsi_root / 17 entries were displayed.

cluster1::*>

Take a moment to examine the ouput and notice that not only is san_vol1 junctioned into svm_fas01'snamespace, but san_vol2 is too, and san_vol3 and san_vol4 are junctioned into svm_fas02'snamespace.

24. Remove each of these volumes from their repective namespace.

cluster1::*> volume unmount -vserver svm_fas01 -volume san_vol1cluster1::*> volume unmount -vserver svm_fas01 -volume san_vol2cluster1::*> volume unmount -vserver svm_fas02 -volume san_vol3cluster1::*> volume unmount -vserver svm_fas02 -volume san_vol4


cluster1::*>

25. Re-issue the ONTAP CLI command to rehost san_vol1 to the svm_iscsi SVM.


Warning: Rehosting a volume from one Vserver to another Vserver does not change the security information on that volume. If the security domains of the Vservers are not identical, unwanted access might be permitted, and desired access might be denied. An attempt to rehost a volume will disassociate the volume from all volume policies and policy rules. The volume must be reconfigured after a successful or unsuccessful rehost operation. See the "7-Mode Transition Tool 2.2 Copy-Free Transition Guide" for reconfiguration details.Do you want to continue? {y|n}: y[Job 278] Job is queued: Volume rehost operation on volume "san_vol1" on Vserver "svm_fas01" to destination Vserver "svm_iscsi" by administrator "admin".[Job 278] Job succeeded: Successful

Info: Volume is successfully rehosted on the target Vserver.Set the desired volume configuration - such as the export policy and QoS policy - on the target Vserver.

cluster1::*>

26. Re-host the remaining three volumes.








Warning: Rehosting a volume from one Vserver to another Vserver does not change the security information on that volume. If the security domains of the Vservers are not identical, unwanted access might be permitted, and desired access might be denied. An


attempt to rehost a volume will disassociate the volume from all volume policies and policy rules. The volume must be reconfigured after a successful or unsuccessful rehost operation. See the "7-Mode Transition Tool 2.2 Copy-Free Transition Guide" for reconfiguration details.Do you want to continue? {y|n}: y[Job 281] Job is queued: Volume rehost operation on volume "san_vol4" on Vserver "svm_fas02" to destination Vserver "svm_iscsi" by administrator "admin".[Job 281] Job succeeded: Successful


cluster1::*>

27. Return the CLI session privilege level to normal.

cluster1::*> set -priv admin

cluster1::>

28. Display a list of the volumes the belong to svm_iscsi.

cluster1::> volume show -vserver svm_iscsiVserver Volume Aggregate State Type Size Available Used%--------- ------------ ------------ ---------- ---- ---------- ---------- -----svm_iscsi san_vol1 fas01_aggr1 online RW 20GB 13.96GB 30%svm_iscsi san_vol2 fas01_aggr1 online RW 20GB 13.96GB 30%svm_iscsi san_vol3 fas02_aggr1 online RW 20GB 13.96GB 30%svm_iscsi san_vol4 fas02_aggr1 online RW 20GB 13.96GB 30%svm_iscsi svm_iscsi_root cluster1_01_aggr1 online RW 20MB 18.85MB 5%5 entries were displayed.

cluster1::>

29. Display a list of the LIFs that belong to svm_iscsi.

cluster1::> network interface show -vserver svm_iscsi Logical Status Network Current Current IsVserver Interface Admin/Oper Address/Mask Node Port Home----------- ---------- ---------- ------------------ ------------- ------- ----svm_iscsi iscsi_lif1 up/up 192.168.0.165/24 cluster1-01 e0c true iscsi_lif2 up/up 192.168.0.166/24 cluster1-02 e0c true2 entries were displayed.

cluster1::>

You will need these IP addresses later when you reconnect Jumphost's iSCSI initiator to the LUNs.

30. Close the CLI session to cluster1.

cluster1::> exit



31

Figure 3-101:


32. Click the Discovery tab.33. Click Discover Portal....


32

33

Figure 3-102:


34. Set the “IP Address or DNS name” field to 192.168.0.165.

Note: Remember that 192.168.0.165 and 192.168.0.166 are the IP addresses of the iSCSI LIFson svm_iscsi.

35. Click OK.

34

35

Figure 3-103:


36. The “Target portals” list contains an entry for the address you just entered.


36

Figure 3-104:

37. Select the Targets tab.38. In the “Discovered targets” list, select the only entry.39. Click Connect.


37

38

39

Figure 3-105:

The “Connect To Target” window opens.

40. Check Enable multi-path.41. Click OK.

40 41

Figure 3-106:


The “Connect To Target” window closes, and focus returns to the “iSCSI Initiator Properties” window.

42. The entry in the “Discovered Targets” list now show as “Connected”.

42

Figure 3-107:

43. Select the Volumes and Devices tab.44. Click Auto Configure.45. The “Volume List” box is populated with entries for the L:, M:, N:, and O: drives.46. Click OK.


43

44

45

46

Figure 3-108:




47

Figure 3-109:


48. In Windows Explorer, click This PC.49. Verify that the L:, M:, N:, and O: drives are connected, and that the expected files are still present.

48

49

Figure 3-110:

This completes the exercise.


4 ReferencesThe following references were used in writing this lab guide.

• 7MTT v3.0 Product Documentation• TR-4052: Successfully Transitioning to Clustered Data ONTAP

http://mysupport.netapp.com/documentation/docweb/index.html?productID=62304&language=en-US

http://www.netapp.com/us/media/tr-4052.pdf


5 Version History

Version Date Document Version History

Version 3.0 Sep 2016 Initial Release - Insight 2016

Refer to the Interoperability Matrix Tool (IMT) on the NetApp Support site to validate that the exactproduct and feature versions described in this document are supported for your specific environment.The NetApp IMT defines the product components and versions that can be used to constructconfigurations that are supported by NetApp. Specific results depend on each customer's installation inaccordance with published specifications.

NetApp provides no representations or warranties regarding the accuracy, reliability, or serviceability of anyinformation or recommendations provided in this publication, or with respect to any results that may be obtainedby the use of the information or observance of any recommendations provided herein. The information in thisdocument is distributed AS IS, and the use of this information or the implementation of any recommendations ortechniques herein is a customer’s responsibility and depends on the customer’s ability to evaluate and integratethem into the customer’s operational environment. This document and the information contained herein may beused solely in connection with the NetApp products discussed in this document.

Go further, faster®

© 2017NetApp, Inc. All rights reserved. No portions of this document may be reproduced without prior written consentof NetApp, Inc. Specifications are subject to change without notice. NetApp, the NetApp logo, Data ONTAP®,ONTAP®, OnCommand®, SANtricity®, FlexPod®, SnapCenter®, and SolidFire® are trademarks or registeredtrademarks of NetApp, Inc. in the United States and/or other countries. All other brands or products are trademarks orregistered trademarks of their respective holders and should be treated as such.

http://support.netapp.com/matrix/mtx/login.do

Documents

Migrating to NetApp ONTAP Using the 7-Mode …Migrating to NetApp ONTAP Using the 7-Mode Transition Tool Copy-Free Transition 2 © 2017 NetApp, Inc. All rights reserved. NetApp Proprietary