Remount volumes after changing the vendor from LSI to NETAPP

Contributors NetAppZacharyWambold netapp-jolieg

If your controller upgrade results in changing the vendor ID from LSI to NETAPP, follow the appropriate procedure for your host type:

Remount volumes on an AIX host

After you replace the controllers, you might observe that the host shows the new volumes on the storage array, but also shows the original volumes as failed.

Step

If failed volumes appear, run the cfgmgr command.

Remount volumes on a VMware host

After you replace the controllers, you might observe the following conditions:

  • VMware shows new paths for the volumes on the storage array, but also shows the original paths as dead paths.

  • The hosts still list the volumes on the storage array as having LSI vendor IDs. This might occur when the volumes were claimed by the LSI rule at the start and so continue to use the same LSI rule when the volumes come back on line.

  • The Display Name does not reflect the change from LSI to NetApp. This might occur because the display name became free test after initial discovery. In this case, you can change the Display Name manually.

Steps
  1. Perform a rescan on each host.

  2. Halt all host I/O operations to this subsystem.

  3. Reclaim the volumes under NetApp rule.

    1. Run the esxcli storage core device list command. Check the output from the command to identify volumes whose names have the form aa.xxxx.

    2. Run the command do esxcli storage core claiming reclaim -d naa.xxxxx to change the LSI vendor ID to NetApp.

Remount volumes on a Windows host

After you replace the controllers, you must remount volumes on a Windows host to enable attached hosts to perform I/O operations with the volumes located on the upgraded storage array.

Steps
  1. In the Device Manager, select Show Hidden Devices.

  2. For each NETAPP SCSI Disk Device listed in the Device Manager, right-click on the entry, and select Uninstall.

    If Windows displays a dialog box with a message indicating that you should reboot the host, finish uninstalling all of the volumes before you scan for hardware and reboot.

  3. Right-click in the Device Manager, and then select Scan for Hardware Changes.

  4. Reboot the host.