Replies to This Discussion

Permalink Reply by Brock Johnson on August 14, 2013 at 10:57am

I am getting the same issue when I do a fresh install.  The system never comes out of Diagnostics.  I am also running this in a vSphere 5.1 environment.

Thanks

Brock

• ▶ Reply

Permalink Reply by Jerry Schmidt on August 14, 2013 at 1:47pm

Hello Harold and Brock,

Can you verify that the system requirements are being met as listed on page 4 of the Quantum DXi V1000 Quick Start Guide?

• ▶ Reply

Permalink Reply by Mark Thacker on August 16, 2013 at 11:33am

Hi Brock,

Did the system ever successfully work? I suspect that something has changed about your networking or underlying disk infrastructure post reboot.

Also, as a note, the DXi V-series products (V1000, V4000) do behave differently than do the physical DXis when it comes to networking. The DXi V-Series support DHCP and VLAN tagging on VMware. 

So, when we have seen this in the past, it has been either a disk has become corrupted (improper shutdown or the disk was moved during to a different data store and not properly updated so the VM could find it again. OR, we have seen this when the VMware virtual network configuration became corrupt or changed (for example, DHCP being incorrect, VLAN configuration being incorrect or the gateway for DHCP not being pingable by the DXi at boot).

If you connect to the http://dxi-ipaddress/ you should be able to at least get into the console to see the error messages.

If not, then you should be able to SSH into the system and login as "cliadmin" (same thing for default password - changeable by you). From there, you can use the "syscli" command to extract what error messages the system has. You don't need Root directly to at least determine what the problem is that the DXi is claiming.

The Command Line Guide (available from this site in the Resources section) has a complete description of what you can do as cliadmin on the system.

• ▶ Reply