I have a NB 4.5FP4 master on Solaris 9, silo is STK PowderHorn with 9940A
drives. These messages just happened this evening and I can't figure out why
it started or how to correct it. All my backups are in full swing so
stopping/restarting NB is not an option at this point. I have redirected a
few failed backups to another media server/library so backups can hobble
until day shift arrives to continue problem, but I am stuck for a long time
with what is currently happening, which is several things.  First  question
is, this error just started after giving a batch of scratch pool tapes to
the group that runs the mainframe/silos. When I attempted to run an
inventory, I get this message from the java gui,

robot inventory failed:  Unable to initialize robot (204)

bpps -a on master shows:
MM Processes
------------
    root   789     1  0   Dec 12 ?        0:30 vmd -v
    root 27480 27309  0 01:07:40 ?        0:00 acsd -v
    root 27492 27309  0 01:07:42 ?        0:00 tldd -v
    root  4489 27480  0 02:34:20 ?        0:00 acsd -v
    root 27499 27309  0 01:07:44 ?        0:00 avrd -v
    root 27309     1  0 01:07:34 ?        0:01 ltid
    root   939     1  0   Dec 12 ?        0:00 acssel -s 13740
    root   977     1  0   Dec 12 ?        0:03 acsssi 13741
    root 27519   789  0 01:07:54 ?        0:00 rdevmi -sockfd 6 -r -verbose

this is the part I am not sure of. The mainframe controls the robot arm,
which has 2 ip addresses. One address resolves to dns name syp, other ip
resolves to dns name syt. Both are suppose to be active at all times, per
mainframe group. Both ip's/hostnames are in local hosts file on master.
What I am unsure of is, on the master, in the vm.conf the device host has
only one line for the robot, which is:
DEVICE_HOST = syp  
Should there be another entry for syt?

any help would be greatly appreciated! Many thanks.


-Dwayne

Dwayne J. Brzozowski
Department of Veterans Affairs
Night Shift Supervisor-Unix Group
Austin Automation center
dwayne.brzozowski AT mail.va DOT gov