Problem in initializing the EVA4000 through storage server

[Natesan_1]

Configuration:
EVA4000
XCS5020

Storage Server:
ProlientDL380
Qlogic FC card
Windows 2003 Enterprise edition
with SP1, JAVA 1.5.0.05 , IE 6 with SP1
Commandview EVA 4.0
Mcdata 24port SAN switch.


Problem in detail:

We are able to see the controller in Storage server devicemanager also we are able to see the storage too.

When we start initialize the storage it takes command after some time, it shows command failed.

Storage name was showing sysst2005191420 (looks like date and time stamp of the command requested for initiazing the storage).

After the above event, we are not able to see the storge configuration it shows still uninitialzed only.. no error message in management and controller event logs.

But Storage initialized with sysst2005191420 doesn't show any error in LCD display.

I have verifed prequesite for commandview installation on Storage server, all found to be ok.


I have tried unintialize thro front panel and uninstall & install the Command view EVA, then I could able to see the storage.

As soon as I start initiaze the storage above problem repeats

Thanks in advance for ur vaulable reply..

[Uwe Zessin]

Looks like the SmartStart process somehow screws up the adapter settings. I would re-run the Smart Component (device driver installation & parameter setup - cp######.exe) for the FCA.

[Natesan_1]

Zessin,

Thanks for ur timly reply.
Do we required to use latest version of Smart start?.I belive we have 7.2 version.
Did you every come across this issue.

Let me try your recommendation.

Once again Thanks for ur reply.

[Uwe Zessin · Accepted solution]

I have seen the problem on SmartStart 7.2, 7.3 & 7.4.

[Natesan_1]

Thanks for your timely help.

After deleting the FC QLogic driver and install directly using q005268.exe file(driver file) problem resolved.

[Natesan_1]

Hi Zessin,

Thanks for your timely help.

After deleting the FC QLogic driver and install directly using q005268.exe file(driver file) problem resolved.

[Natesan_1]

problem resolved after reinstalling the qlogic card driver manually.