Command View version 1.09, does not work

[Peter te Focht]

I installed CV 1.09 on a ia64 machine, I see the management Lun, this lun is write/config for this machine, but with armdiscover it does not find a device. All dialdaemons and HA_start have been activated, what things can I do wrong ( Everything ???)
Cheers, Jan Poortman

[Patrick Wallek]

What type of array are you trying to see with this version of CommandView?

Which specific version of CommandView? CommandView for VA? CommandView for EVA?

[Peter te Focht]

Hi Patrick,

I'm trying to see a VA7410. With another machine, a PA-risk, it works, so I can mange the VA. However, this machine will be obsolete in the near future. So I had to install CV on a newer machine.

[Patrick Wallek · Accepted solution]

Did you download the CommandView version for Itanium? Or did you install the PA-RISC version of CommandView.

If you go here:
http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?lang=en&cc=us&prodNameId=443575&taskId=135&prodTypeId=12169&prodSeriesId=64112&submit.y=0&submit.x=0〈=en&cc=us

You can select the version of CV appropriate for you.

[Peter te Focht]

Installed the ia64-version, cvsdm_IA_11_23_v109.depot.
I think that should be the right one, I had no errors during the install.

[Torsten.]

You should use version 1.09.02:

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=443575&prodTypeId=18964&prodSeriesId=64112&swLang=13&taskId=135&swEnvOID=2080


See if this helps:

https://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=954693

[Peter te Focht]

Thanks Torsten,

I will try it today, I will inform the forum with the results.

[Peter te Focht]

I just installed v10902, but still the same message after armdiscover:"No devices found on host: local host"
May be something wrong with secure manager of the VA7410 ???

[Torsten.]

You need to check if you have access to LUN0.

If you go through the thread I posted above, you will find a lot of other things to check, like

/opt/sanmgr/hostagent/config/commIpAddr.txt
/opt/sanmgr/hostagent/config/access.dat

How about

# armdsp -i
# armtopology

[Peter te Focht]

Hello,

I checked everything you mentioned, also the kernelparameter, max_thread_proc, with 256.

In the attachment an overview of all the things I checked.
I have access via two ways to lun 0 of the VA.

[Torsten.]

Can you check the secure manager config and if this is even enabled?

[Torsten.]

Another point to check:

can you successfully resolve the hostname?

[Peter te Focht]

Name resolving is ok.
Secure manager status : enabled
Next Sunday I can reboot the machine. May be these modern boxes have the same behaviour as "Bill Gates-machines".
Tomorrow I'll be back, have a nice evening.
Jan

[Torsten.]

It's some time ago since I worked with this array family - so I forgot some things ...


Anyway, I assume you probably configured all kind of access based on hosts HBA WWN - new server = new WWN. So now you are not allowed to access something.

Since secure manager is enabled, you need to check the configuration.

[Peter te Focht]

Thanks for all hints. I will make a call for HP and hope that they have a solution. It could be possible that it has something to do with VA7410-firmware and the FC-adaptor on the server. This one is quiet new and the devicefiles are not named /dev/td0 or /dev/td1 anymore, but /dev/fclp0 and /dev/fclp1.