insf -e doesn't create device files

[Tim Killinger]

Both before and after I did a cold install of UX on our rp5450, insf -e does not create the device files for the 13 luns on our locally attached va7100. armdsp -i diplays the existing LUNS beautifully. A fresh install of commandview 1.06 on a fresh install of UX, the VA7100 is at HP16 (HP18 next week).

We had this exact problem before the cold install...

Any ideas?? Thanks in advance!!!

[David Navarro]

If you do an ioscan -e, can you see your LUN's?
If you can, devices are showing NOHW, UNCLAIMED ?

David.

[Eugeny Brychkov]

Actually here's only LUN 0 listed. I would recommend to:
- check host behavior table and/or default host behavior to be hpux;
- check VA security table (if security is turned on). Remember: if host's HBA is not listed in security table then it means that host will have no access to LUNs. But what about LUN 0 host sees? In usual configurations LUN 0 is assigned 'WC' access for all hosts, thus visible for everyone.
More information needed? Attach 'armdsp -a' output to your next reply
Eugeny

[Eugeny Brychkov]

Very good. Security is enabled. Run
armsecure -r -f sec_tbl.txt -p va7100
and look into sec_tbl.txt file contents. If you wish your hpux host to see, for example, LUN 5, you should insert a string
NODEWWN 50060b0000021b49 5 WC
with hosts's HBA WWN and download it back to VA using
armsecure -w -f sec_tbl.txt -p va7100
Eugeny
PS. is VA's security password

[Tim Killinger]

Eugeny,

That was it(security enabled) ! thanks so much!