Problem installing OVSAM 3.1 Node Manager Agent on VMS Cluster

[David Harrold]

We have just purchased Storage Optimizer and Storage Node Manager for our SAN and we are in the installation phase of the project.

We are installing the agent on a 2 node VMS V7.3-1 cluster of DS20Es. The install works correctly on the first node, but it appears to need to be re-installed on the second node. When we try this, the installation fails with a file not found message.

Has anyone successfully installed and configured this agent on a cluster? If so, how did you do it?

Thanks,

Dave Harrold

[Martin P.J. Zinser]

Hello Dave,

I do not have experience with this specific agent, but if you can give us

a.)The message(s) that lead you to believe you need to re-install on the second node

b.)The error message during the installation indicating a missing file

I think the forum might be able to make some educated guesses.

Greetings, Martin

[David Harrold]

Hi Martin,

As far as the re-install, it is implied in the documentation that it needs to be installed on each node. All of the agent files are placed in SYS$SPECIFIC:[OPT] directory tree. There doesn't appear to be a cluster wide installation and a node specific configuration anywhere. I'm guessing I could backup the files from the first nodes directory to the next nodes and tweak a few files, but that just doesn't seem right.

The errors on the install from are below.
HNAY$> @ovmsinst
Archive: SYS$SYSDEVICE:[PRODUCTS.OVSAM]OVMS731.ZIP;1
creating: [.ovms]
inflating: [.ovms]hp-axpvms-v731_hpovsamcp-v0301--1.pcsi
inflating: [.ovms]hp-axpvms-v731_hpovsamhb-v0301--1.pcsi
inflating: [.ovms]hp-axpvms-v731_hpovsamda-v0301--1.pcsi
inflating: [.ovms]hp-axpvms-v731_hpovsamca-v0301--1.pcsi
inflating: [.ovms]hp-axpvms-v731_hpovsamha-v0301--1.pcsi
inflating: [.ovms]HP-AXPVMS-V73173_HPOVSAMJR-V0301--1.PCSI
inflating: [.ovms]hp-axpvms-v731_hpovsamsg-v0301--1.pcsi
inflating: ovms_local_uninstall.com
inflating: ovms_local_install.com
inflating: default_ovsam_install_list

%DELETE-I-FILDEL, SYS$SPECIFIC:[OPT.OVSAMLOCAL]TEMP.TXT;1 deleted (64 blocks)
CREATING THE SYS$SPECIFIC:[OPT.SANMGR.HOSTAGENT.CONFIG]ACCESS.DAT FILE ...
ENTER IP ADDRESS OF MANAGEMENT SERVER (Q FOR QUIT)
IP ADDRESS:: xxx.xxx.xxx.xxx
ADDING xxx.xxx.xxx.xxx TO NEW MANAGEMENT SERVER LIST
%PURGE-I-NOFILPURG, no files purged
CREATING THE SYS$SPECIFIC:[OPT.SANMGR.HOSTAGENT.CONFIG]COMMIPADDR.TXT FILE ...
ENTER IP ADDRESS OF THE LOCAL LAN INTERFACE USED TO
COMMUNICATE WITH THE OVSAM MANAGEMENTSERVER (Q TO QUIT)
IP ADDRESS:: xxx.xxx.xxx.xxx
%PURGE-I-NOFILPURG, no files purged
START INSTALL FOR COMPONENT: V73173_HPOVSAMJR


The following product has been selected:
HP AXPVMS V73173_HPOVSAMJR V3.1 Layered Product [Installed]

Do you want to continue? [YES]

Configuration phase starting ...

You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.

HP AXPVMS V73173_HPOVSAMJR V3.1: V73173_HPOVSAMJR

@(#) (c) 2003 Hewlett-Packard Company, All Rights Reserved.

Hewlett-Packard Company

* This product does not have any configuration options.

Execution phase starting ...

The following product will be installed to destination:
HP AXPVMS V73173_HPOVSAMJR V3.1 DISK$ENGSYSDISK:[VMS$COMMON.]

Portion done: 0%

%PCSI-E-OPENOUT, error opening DISK$ENGSYSDISK:[SYS1.][OPT.SANMGR.HOSTAGENT.CONF
IG.MANIFEST]HPOVSAMJR.IMF;* as output
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
%PCSI-E-OPFAILED, operation failed
Terminating is strongly recommended. Do you want to terminate? [YES]
%PCSI-E-CANCEL_WIP, termination resulted in an incomplete modification to the sy
stem
%PCSI-E-S_OPCAN, operation cancelled by request
%PCSIUI-E-ABORT, operation terminated due to an unrecoverable error condition
HNAY$>

[Martin P.J. Zinser]

Hello Dave,

ok, if they do install into sys$specific you do need a per node installation obviously.

The error message says

DISK$ENGSYSDISK:[SYS1.][OPT.SANMGR.HOSTAGENT.CONF
IG.MANIFEST]HPOVSAMJR.IMF;* as output
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file

specifically saying <> not found.

So one question, one conjecture:

1.) Is Disk$engsysdisk:[sys1] the sys$specific for the system you want to install on?

2.)Since PCSI "thinks" the product is already installed it might not have created the directories for you. Doing this manually might be a workaround for your problem. You should be able to copy the directory structure from the node that installed ok without danger of messing up data.

Greetings, Martin

[Willem Grooters]

My guess is that the installation procedure will find the application installed already, either in it's database or by files already existing, and then bypasses the installation and will _expect_ directories below SYS$SPECIFIC existing. In this case, it won't - so this error.

First, a wild guess: where is your PROD database of installed products located? Is this the same file for both systems?
Split this up to local files, you _may_ find the second installtion will succeed. (You'll have to de-install first, and re-install on both nodes. The default location you specified (VMS$COMMON) is ok, a second install will either place new files, overwrite them or just ignore these common files.

As for the installation procedure:
If the product is to be runnable in a clustered environment, the installation should be able to handle this -> HP should solve this.
If not, (which, deducted from it's name, is quite feasable) it is to be expected to err in a second installation.
Workaround might be to install is on another, preferably local, location.
Anyway, your PROD database of installed products will then need to be node-specific.

[David Harrold]

Well, finally I'm able to give an update.

Basically, the installation is bad. :-( PCSI is cluster wide, but the procedure assumes a single stand alone node.

My basic work around was to do as suggested and backup the directory tree from the installed node to the next node in the cluster and tweak the appropriate configuration files. (there are only 2 or three).

The other problem that I tripped over was file ownership. If the files in the directory tree aren't owned by the SYSTEM account, the agent will fail to run.

So, I now have the agent running on all nodes of my test and development clusters and I am working on the plan to roll it out to production.

Now, I'm just waiting for them to get a OVSAM performance agent for VMS, so we can see HBA statistics.

Thanks for everyone's help and suggestions.

Dave Harrold