No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

LUN Owning Not Refreshed After You Configure Failover Between VTL Servers and Restart Them

Publication Date:  2015-08-04 Views:  82 Downloads:  0
Issue Description
Product and version: VTL6000 V100R003

On the VTL Console, after you log in to two VTL servers and configure failover between them and rename them, the two servers fail to be restarted. An error message is displayed stating There are no available virtualized disks on the active server to be configured for quorum disk.

Figure 1 No virtual disk available to the active server


Handling Process
1.  Check whether LUNs on the active server belong to the original host.
  • If yes, go to 2.
  • If no, keep the application environment unchanged and seek technical support.
2.  Refresh the LUN owning.

     a. In the navigation tree of the VTL Console, choose Physical Resources > Fiber Channel Devices.
     b. Right-click the unrefreshed LUNs and choose Erase from the shortcut menu.
     c. In the navigation tree of the VTL Console, right-click Physical Resource and choose Rescan to scan for existing devices.

3.  Check whether LUNs on the active server belong to the new host.
  • If yes, the fault is rectified.
  • If no, keep the application environment unchanged and seek technical support.
Root Cause
Possible Causes:

The possible cause of this failure of this problem is that LUNs on the active server are unavailable.

On the VTL Console, check LUN owning and it is found that all LUNs belong to the original host.

Fault Diagnosis:

Figure 2 Troubleshooting flowchart


END