The problem turned out to be in the HOSTS.NET.SYS file.

I will need to do more research next week to figure out what exactly is
going on here and why the AutoRAID could not handle it.

We have both a general network and a private network configured to the
HP3000 in HOSTS.NET.SYS. The particular system is named "ipmc".
HOSTS.NET.SYS has lines for both the private network (in "ipmcp" the "p" at
the end of the node name is a convention we use to indicate the Private
network) (actual IP addresses replaced with "#" in the email for security):

10.#.#.#            ipmcp

and later in the file we have the entry for the general network (no "p" at
the end of the name):

199.###.###.###    ipmc


As soon as HP changed the "10.#.#.# ipmcp" entry to "10.#.#.# ipmc", the ARM
commands started working.

I am going to have to look at NMCONFIG and talk to some network experts to
figure out why the AutoRAID is insisting on the general network node name
"ipmc" yet going after the wrong IP address. We would in fact want it to use
the private network node name "ipmcp". The private network is intended for
critical machine to machine communications. I think the  AutoRAID would fall
into this category. I don't think I want it competing with user downloads
etc. over the general network.

But that is all for next week. Have a good weekend everyone.

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *