Migrating from management node 10.x to version 11.x

If you have a management node at version 10.x, you cannot upgrade from 10.x to 11.x. You can instead use this migration procedure to copy over the configuration from 10.x to a newly deployed 11.1 management node. If your management node is currently at 11.0 or higher, you should skip this procedure. You need management node 11.0 or 11.1 and the latest HealthTools to upgrade Element software from 10.3 + through 11.x.


  1. From the VMware vSphere interface, deploy the management node 11.1 OVA and power it on.
  2. Open the management node VM console, which brings up the terminal user interface (TUI). Use the TUI to create a new administrator ID and assign a password.
  3. In the management node TUI, log in to the management node with the new ID and password and validate that it works.
  4. From the vCenter or management node TUI, get the management node 11.1 IP address and browse to the IP address on port 9443 to open the management node UI.
    https://<mNode 11.1 IP address>:9443
  5. In vSphere, select NetApp Element Configuration > mNode Settings. In older versions, the top-level menu is NetApp SolidFire Configuration.
  6. Click Actions > Clear.
  7. To confirm, click Yes. The mNode Status field should report Not Configured.
    Note: When you go to the mNode Settings tab for the first time, the mNode Status field might display as Not Configured instead of the expected UP; you might not be able to choose Actions > Clear. Refresh the browser. The mNode Status field will eventually display UP.
  8. Log out of vSphere.
  9. In a web browser, open the management node registration utility (https://<mNode 11.1 IP address>:9443) and select QoSSIOC Service Management.
  10. Set the new QoSSIOC password.
    Note: The default password is solidfire. This password is required to set the new password.
  11. Click the vCenter Plug-in Registration tab.
  12. Select Update Plug-in.
  13. Enter required values. When you are finished, click UPDATE.
  14. Log in to vSphere and select NetApp Element Configuration > mNode Settings.
  15. Click Actions > Configure.
  16. Provide the management node IP address, management node user ID (the user name is admin), password that you set on the QoSSIOC Service Management tab of the registration utility, and vCenter user ID and password.
    In vSphere, the mNode Settings tab should display the mNode Status as UP, which indicates management node 11.1 is registered to vCenter.
  17. From the management node registration utility (https://<mNode 11.1 IP address>:9443), restart the SIOC service from QoSSIOC Service Management.
  18. Wait for one minute and check the NetApp Element Configuration > mNode Settings tab. This should display the mNode Status as UP.
    If status is DOWN, check the permissions for /sf/packages/sioc/app.properties. The file should have read, write, and execute permissions for the file owner. The correct permissions should appear as follows: -rwx------
  19. After the SIOC process starts and vCenter displays mNode Status as UP, check the logs for the sf-hci-nma service on the management node. There should be no error messages.
  20. (For management node 11.1 only) SSH into the management node version 11.1 with root privileges and start the NMA service with the following commands:
    # systemctl enable /sf/packages/nma/systemd/sf-hci-nma.service
    # systemctl start sf-hci-nma
  21. Perform actions from vCenter to remove a drive, add a drive or reboot nodes. This triggers storage alerts which should be reported in vCenter. If this is working, NMA system alerts are functioning as expected.
  22. If ONTAP Select is configured in vCenter, configure ONTAP Select alerts in NMA by copying the .ots.properties file from the previous management node to the management node version 11.1 /sf/packages/nma/conf/.ots.properties file, and restart the NMA service using the following command: systemctl restart sf-hci-nma.
  23. Verify that ONTAP Select is working by viewing the logs with the following command: journalctl -f | grep -i ots.
  24. Configure AIQ by doing the following:
    1. SSH in to the management node version 11.1 and go to the /sf/packages/collector directory.
    2. Run the following command:
      sudo ./manage-collector.py --set-username netapp --set-password --set-mvip <MVIP>
    3. Enter the management node UI password when prompted.
    4. Run the following commands:
      ./manage-collector.py --get-all
      sudo systemctl restart sfcollector
    5. Verify sfcollector logs to confirm it is working.
  25. In vSphere, the NetApp Element Configuration > mNode Settings tab should display the mNode Status as UP
  26. Verify NMA is reporting system alerts and ONTAP Select alerts.
  27. If everything is working as expected, shut down and delete management node 10.x VM.