Secure Path steps after adding a new LUN from EVA

[Adam Garsha]

Are there any steps that need to be taken with spmgr after adding a new LUN to an HP-UX system?

It seems that Secure Path automatically noted the presence and set up paths after I had ioscan'ed and insf'd.

Secure Path did send some cryptic Email messages which I now understand are normal. Do I need to do anything special to maintain state between reboots?

The automatic arrangement of paths looks good to me.

The reason that I ask is I remember hearing about "spmgr update" and "recompiling the kernel"... some long time ago and I can't remember the reference and I see no "spmgr update" on the man page--so I am hoping that was an older Secure Path that needed this care and feeding.

I have:

CPQswsp A.3.0E.00F.00F HP StorageWorks Secure Path Device Driver

And these are the settings, I believe:

Load Balance: On
Auto-restore: On
Balance Policy: Round Robin
Path Verify: On
Verify Interval: 30
HBAs: td0 td1

[Dave Hutton]

I think it's prior to 3.0D you had to issue the spmgr update:
Run kmadmin -L swspData
config -M swspData -u
for changes to persist across reboots.


The newer versions you don't have to do it.

[John Payne_2]

Adam,

If this is a newly-connected-to-the-SAN machine, you have to set load balance, the policy you want, etc. (spmgr set -a, set -b, etc.) If you unpresent all luns from an array, these values will be reset also.

I generally set an alias for the lun, and have our SAN guy do the same. (I don't manage the EVA, just consume the space...) That way in the future, we can be clear as to what lun we are talking about. (spmgr alias)

As has been posted, 'spmgr update' is no longer necessary.

Once you do the ioscan & insf -e and you can see the LUN via spmgr, you should be good to go...

John