After an external LUN recovers, if the remote LUN or eDevLUN corresponding to the external LUN on the local storage system is still faulty

If a local storage system has one of the following abnormalities after the external LUN mapped from a heterogeneous storage system becomes normal, manually scan the local storage system for LUNs:

• The local storage system cannot display information about the remote LUN corresponding to the external LUN.

• The remote LUN corresponding to the external LUN on the local storage system is still in the fault state.

• The eDevLUN is still in the faulty state.

Use one of the following methods to scan for LUNs:

• Start an automatic LUN scan on DeviceManager.

• In CLI, run the scan remote_lun command.

1. Log in to the DeviceManager for the local storage system.

2. Go to the Automatic LUN Scan dialog box.

   1. In the navigation bar, choose System > External Storage.

   2. Based on Name and ESN, select the remote device that corresponds to the heterogeneous storage system. In the lower function pane, click Scan for External LUN.

      The OK dialog box is displayed.

3. Click OK to start an automatic LUN scan.

   DeviceManager then scans for LUNs, and updates information about the remote LUN and eDevLUN, making the information consistent with information about the external LUN.

4. Click Close.