Thanks to everyone that helped me out on this one.  All of your suggestions
were very helpful and I have added many of those to my
"little-book-of-everything" for future reference.

But what I did was read the ACS/LS manual under troubleshooting, which I
quickly realized was the wrong place to be...this was a communication
problem from the Linux media server to the ACS server as many of you so
aptly pointed out.  So when I started focusing my engergies on that, I read
in one of the NBU manuals that the CSI_HOSTNAME environmnet variable needed
to be set for the communication to work properly....SO...here's what I did.

Since the CSI_HOSTNAME environment variable wasn't getting set properly.  I
put the following in the S77netbackup script in /etc/rc2.d

TPCONFIG=/usr/openv/volmgr/bin/tpconfig
CSI_HOSTNAME=`$TPCONFIG -data | grep robot | awk '{print $9}'`
export CSI_HOSTNAME

That worked like a CHAMP!
This works great for ONE robot in the environment.


David

<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
Backup Storage Consultant
DataStaff, Inc.
http://www.datastaff.com
312 683 1144
---------------------------------------

-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Brian Blake
Sent: Friday, January 24, 2003 3:23 AM
To: David A. Chapa; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Linux Media Server with STK ACS/LS


Check the ACSLS server's acsss_event.log. It should be in
/export/home/ACSSS/log/acsss_event.log, I believe. See if you're getting any
errors from the ACSLS server trying to communicate back to the NBU server.

Also log into the ACSLS server as the user acsss (or as root and su - to
acsss) and run cmd_proc. Do a "query server" to make sure the ACSLM is
online and ready to go. You can also leave this cmd_proc window up and then
try robtest from the Linux box and see if any errors show up in the upper
section of the cmd_proc window. Oh yeah, make sure to set the terminal to
vt100 or similar as cmd_proc is a curses-based interface.

It's probably a network communication thing between the ACSLS server and the
Linux box... The ACS API (which NBU and any other backup software will tie
into their robotic daemons) is all TCP/IP based.

B-

On 1/23/03 4:03 PM, "David A. Chapa" <david AT datastaff DOT com> wrote:

> I'm getting an ACS STATUS 72 when trying to enter robtest.
>
> I configured my media server's "robot" as ACS, pointed it to the ACS/LS
> server,
> everything seemed happy when I did that.
>
> Then I configured one drive (9840), brought it up and the drive never went
to
> ACS control, but stayed at AVR and robtest wouldn't come up but timed out
with
> that 72 error from ACS.
>
> ideas?
>
> Thoughts?
>
> David
>
> PS...RedHat Linux 7.x, NBU 4.5MP3
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>

--
Brian Blake
Professional Services Organization
VERITAS Software
brian.blake AT veritas DOT com


_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu