Disk Arrays
cancel
Showing results for 
Search instead for 
Did you mean: 

Secure path 3.0B HP-UX + EVA5000

Secure path 3.0B HP-UX + EVA5000

Hi All,

I have questions on secure path 3.0B on HP-UX 11i. Installation Secure path + all required path's are executed without errors.
At attempt to add WWNN EVA environment, I receive the answer:
"No LUNs have been presented to Secure Path."

Whereas ioscan shows:
ctl 70 0/0/10/1/0.2.11.0.0.0.0 sctl CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
/dev/rscsi/c33t0d0
disk 276 0/0/10/1/0.2.11.0.0.0.1 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
/dev/dsk/c33t0d1 /dev/rdsk/c33t0d1
disk 283 0/0/10/1/0.2.11.0.0.0.2 sdisk CLAIMED DEVICE COMPAQ HSV110 (C)COMPAQ
/dev/dsk/c33t0d2 /dev/rdsk/c33t0d2

Pls. how to solve this problem?
4 REPLIES
Uwe Zessin
Honored Contributor

Re: Secure path 3.0B HP-UX + EVA5000

Are you sure you have installed all required patches? - See the Secure Path documentation for details.

I've seen a similar problem in a single-path configuration. HP-UX could not properly identify the EVA LUNs, so it created a device entry, but reported the disk's size as 0. Upgrading HP-UX fixed this.
.

Re: Secure path 3.0B HP-UX + EVA5000

Yes of course, before installation Secure Path, have preliminary established all required fix's.

Probably Secure Path does not work with this version VCS?
- Secure Path v.3.0D (P/N T3550A);
- EVA 5000 VCS v 3.020;

In technical specifications Secure Path v 3.0E It is told:
"Storage Controller Software EVA5000, EVA3000 solutions: Supports VCS v2.0, v3.0, v3.014.
Also is not present that about v3.020?

Alzhy
Honored Contributor

Re: Secure path 3.0B HP-UX + EVA5000

Yermek,

What version of SecurePath are you ACTUALLY using?

SecurePath 3.0D/E are what is certified for VXS 3.014/3.020.. SecurePath 3.0B as what you claimed is an old buggy release. Upgrade to 3.0D or 3.0E if this is the case.. Also, if the Array was newly added - you need to have at least a presentation LUN and reboot the system.

Hakuna Matata.

Re: Secure path 3.0B HP-UX + EVA5000

Dear All,

I am sorry for anxiety, the problem is fixed. By us has been installed Secure Path v.3D using "swinstall" instead of "install.sh".
Have inattentively read through in documentation "Note:"