Netbackup doesn't currently support drive serialization for ACS robot types, so 
the gui has no way of knowing where the drives
are in the robot. Tpconfig doesn't care because you have to tell it where the 
drives are anyway.

George

On Mon, 20 Oct 2003, Steve Mickeler wrote:

>
> Turns out when I used the GUI to configure my drives, it would always have
> the "Drive is under robotic control" section greyed out.
>
> Configure the drive via tpconfig and voila, it asks me if my drives are
> under robotic control, and allows me to configure them.
>
> So, why is the gui teasing me ?
>
>
> On Sat, 18 Oct 2003, Steve Mickeler wrote:
>
> >
> > Using NBU 4.5 - FP5
> >
> > I cant seem to get acsd started.
> >
> > It always quits with:
> >
> > Daemon terminating: No devices found on ACS(0)
> >
> > I can talk to the acsls server just fine via acstest if I manually start
> > acsssi
> >
> > /usr/openv/volmgr/bin/acstest -r acsls
> > SSI socket not specified... trying default (13741)
> > Server 0 with 138 free cells is in state "STATE_RUN"
> >
> > QUERY SERVER complete
> >
> > Enter acs commands (? returns help information)
> >
> > Any ideas ?
> > _______________________________________________
> > Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> >
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>