These steps provide details for assigning disk ownership and disk initialization and verification.
Note Typical best practices should be followed when determining the number of disks to assign to each controller head. You may choose to assign a disproportionate number of disks to a given storage controller in an HA pair, depending on the intended workload.
In this reference architecture, half the total number of disks in the environment is assigned to one controller and the remainder to its partner.
How to Access the Configuration Worksheet Configuration Guide
Comments Configuration
Worksheet https://library.netapp.com/ecm/ecm_get_file/ECMM1249829
Requires access to the NetApp Support site.
Detail Detail Value
Controller A MGMT IP Controller A netmask Controller A gateway
URL of the Data ONTAP boot software Controller B MGMT IP
Controller B netmask Controller B gateway
Controller A
1. Connect to the storage system console port. You should see a Loader-A prompt. However, if the storage system is in a reboot loop, Press Ctrl – C to exit the Autoboot loop when you see this message:
Starting AUTOBOOT press Ctrl-C to abort…
2. If the system is at the LOADER prompt, enter the following command to boot Data ONTAP:
autoboot
3. During system boot, press Ctrl – C when prompted for the Boot Menu:
Press Ctrl-C for Boot Menu…
Note If 8.1.2 is not the version of software being booted, proceed with the steps below to install new software. If 8.1.2 is the version being booted, then proceed with step 14, maintenance mode boot.
4. To install new software first select option 7.
7
5. Type y indicating yes to perform a nondisruptive upgrade.
y
6. Select e0M for the network port you want to use for the download.
e0M
7. Type y indicating yes to reboot now.
y
8. Enter the IP address, netmask, and default gateway for e0M in their respective places.
<<var_controller1_e0m_ip>> <<var_controller1_mask>>> <<var_controller1_mgmt_gateway>>. 9. Enter the URL where the software can be found.
Note This Web server must be pingable.
<<var_url_boot_software>>
10. Press Enter for the username, indicating no user name.
Enter
11. Type y indicating yes to set the newly installed software as the default to be used for subsequent reboots.
y
12. Type y indicating yes to reboot the node.
y
13. When you see “Press Ctrl-C for Boot Menu”, press:
Ctrl-C
14. To enter Maintenance mode boot, select option 5.
5
15. When you see the question “Continue to Boot?” type yes.
y
16. To verify the HA status of your environment, enter:
NetApp FAS3240A Deployment Procedure - Part 1
Note If either component is not in HA mode, use the ha-config modify command to put the components in HA mode.
17. To see how many disks are unowned, enter:
disk show -a
Note No disks should be owned in this list.
18. Assign disks.
disk assign –n <<var_#_of_disks>>
Note This reference architecture allocates half the disks to each controller. However, workload design could dictate different percentages.
19. Reboot the controller.
halt
20. At the LOADER-A prompt, enter:
autoboot
21. Press Ctrl – C for Boot Menu when prompted.
Ctrl-C
22. Select option 4 for Clean configuration and initialize all disks.
4
23. Enter y indicating yes to zero disks, reset config, and install a new file system.
y
24. Type y indicating yes to erase all the data on the disks.
y
Note The initialization and creation of the root volume can take 75 minutes or more to complete, depending on the number of disks attached. When initialization is complete, the storage system reboots. You can continue with the Controller B configuration while the disks for Controller A are zeroing.
Controller B
1. Connect to the storage system console port. You should see a Loader-A prompt. However if the storage system is in a reboot loop, Press Ctrl – C to exit the Autoboot loop when you see this message:
Starting AUTOBOOT press Ctrl-C to abort…
2. If the system is at the LOADER prompt, enter the following command to boot Data ONTAP:
autoboot
3. During system boot, press Ctrl – C when prompted for the Boot Menu:
Press Ctrl-C for Boot Menu…
Note If 8.1.2 is not the version of software being booted, proceed with the steps below to install new software. If 8.1.2 is the version being booted, then proceed with step 14, maintenance mode boot.
7
5. Type y indicating yes to perform a nondisruptive upgrade.
y
6. Select e0M for the network port you want to use for the download.
e0M
7. Type y indicating yes to reboot now.
y
8. Enter the IP address, netmask and default gateway for e0M in their respective places.
<<var_controller2_e0m_ip>> <<var_controller2_mask>>
<<var_controller2_mgmt_gateway>>. 9. Enter the URL where the software can be found.
Note This Web server must be pingable.
<<var_url_boot_software>>
10. Press Enter for the username, indicating no user name.
Enter
11. Type y indicating yes to set the newly installed software as the default to be used for subsequent reboots.
y
12. Type y indicating yes to reboot the node.
y
13. When you see “Press Ctrl-C for Boot Menu”, press:
Ctrl-C
14. To enter Maintenance mode boot, select option 5:
5
15. If you see the question “Continue to Boot?” type yes.
y
16. To verify the HA status of your environment, enter:
ha-config show
Note If either component is not in HA mode, use the ha-config modify command to put the components in HA mode.
17. To see how many disks are unowned, enter:
disk show -a
Note The remaining disks should be shown.
18. Assign disks by entering:
disk assign –n <<var_#_of_disks>>
Note This reference architecture allocates half the disks to each controller. However, workload design could dictate different percentages.
NetApp FAS3240A Deployment Procedure - Part 1
halt
20. At the LOADER prompt, enter:
autoboot
21. Press Ctrl – C for Boot Menu when prompted.
Ctrl-C
22. Select option 4 for a Clean configuration and initialize all disks.
4
23. Type y indicating yes to zero disks, reset config, and install a new file system.
y
24. Type y indicating yes to erase all the data on the disks.
y
Note The initialization and creation of the root volume can take 75 minutes or more to complete, depending on the number of disks attached. When initialization is complete, the storage system reboots.