Veritas-bu

[Veritas-bu] Status of a robot from command line

2001-10-31 10:36:13
Subject: [Veritas-bu] Status of a robot from command line
From: David A. Chapa" <david AT xbpadm-commands DOT com (David A. Chapa)
Date: Wed, 31 Oct 2001 07:36:13 -0800 (PST)
in unix its in your syslog

solaris /var/adm/messages

nt is in your event log.

David

Quoting Pablo A Juarez <pjuarez AT tysons.tmac DOT com>:

> Good day to you all..
>
>       While reading this thread, I decided to run the 
vmoprcmd
> command, and I found that a drive was marked as down 
(which would
> explain the 196 errors I have been getting recently). 
I searched through
> all the logs and I couldn't find the reason why this 
drive was marked as
> down. Perhaps I am looking in the wrong places. Is 
there some sort of
> automatic process that would do such a thing, or 
would it require a
> manual change? Thanks for your help.
>
> Pablo Juarez
>
> -----Original Message-----
> From: Jason Ahrens [mailto:Jason.Ahrens AT telus DOT com]
> Sent: Monday, October 29, 2001 4:02 PM
> To: Veritas BU
> Subject: RE: [Veritas-bu] Status of a robot from 
command line
>
>
> I am using vmoprcmd to watch the status of the 
drives. Unfortunatly,
> that
> didn't help with the situation today where the robot 
malfunctioned, but
> the
> drives themselves were fine. The robot sat in 
an 'intervention required'
> state but it never set off alarms as the drives were 
still in an UP and
> OK
> state. I could have started feeding them tapes 
manually probably. When I
> was
> trying to do some diagnostics I saw 'robtest' spit 
back soem information
> about the robot (presumably gathered through tldtest) 
stating that
> manual
> intervention was required. I'd like to access this 
sense key data that
> robtest/tldtest returned. The difference is, I can't 
seem to duplicate
> it
> when the robot is working fine.
>
> Jason
>
> > -----Original Message-----
> > From: Larry Kingery 
[mailto:larry.kingery AT veritas DOT com]
> > Sent: October 29, 2001 15:56
> > To: Jason Ahrens
> > Cc: Veritas BU
> > Subject: Re: [Veritas-bu] Status of a robot from 
command line
> >
> >
> > $ vmoprcmd -d ds
> >
> > will show you the drive(s) status from the CLI.  If 
it's AVR, there's
> > probably something up with the robot.  Of course, 
it could just be
> > that someone has the door open or something, so 
you'd want to wait a
> > few minutes before paging someone (at least if that 
someone is you).
> >
> > HTH,
> > L
> _______________________________________________
> 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
> 



<><><><><><><><><><><><><><><><><><><><>
David A. Chapa
Consulting Manager
DataStaff, Inc.
847 413 1144
http://www.consulting.datastaff.com
---------------------------------------
http://www.xbpadm-commands.com
NBU-LSERV AT datastaff DOT com - Adv. Scripting

<Prev in Thread] Current Thread [Next in Thread>