Also remember that on PENDING events that end up as MISSED because the TSM
server can't contact node _________ on (or is it at) IP address
____________
will trigger one of those messages right off the bat at the beginning of
its schedule window.
Depending on your amount of automation and monitoring you have available,
you might be able to trap that "can't contact" message from the TSM server
activity log and fire of an event through something else that will bounce
the scheduler process over on that client, which can just about cure
"missed" events within your environment.
:-)
Dwight E. Cook
Systems Management Integration Professional, Advanced
Integrated Storage Management
TSM Administration
(918) 835-3106 (local Tulsa OK)
(877) 625-4186
T/L 349-4361
"Hart, Charles"
<[EMAIL PROTECTED]
TRONIC.COM> To
Sent by: "ADSM: ADSM-L@VM.MARIST.EDU
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU> Re: SNMP and Client Backup Failures
07/15/2005 01:51
PM
Please respond to
"ADSM: Dist Stor
Manager"
Thank you! That's what I was hoping. The only client activity I want
to pas is the failures / misses as you mentioned below.
Have a great weekend!
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Prather, Wanda
Sent: Friday, July 15, 2005 1:49 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: SNMP and Client Backup Failures
Yes and no, depending on what you mean.
There isn't a TSM SNMP agent on the client end.
But, there are many ways to get good results, if you have an SNMP trap
receiver console (like Netview or Openview, for example).
- Remember that most TSM client errors are forwarded up to the TSM
server and logged in the activity log, just like server errors. So if
you have the TSM server forwarding events to an SNMP trap receiver, just
include those error messages in the list of messages TSM forwards to
Openview. For example:
07/14/2005 18:00:01 ANR2578W Schedule SCHD_WINCLIENT_INCR_AM in domain
PDOM_WINCLIENT for node SPDFAC1 has missed its
scheduled start up window.
If you include ANR2578W in the list of messages you forward from the TSM
server to Openview, this is what you see.
- Remember that you can query the TSM server using the TSM admin command
client (dsmadmc). And there is a trapgen.exe module that you can
invoke with parms to create your own traps. So, it is pretty easy to
write a perl or kornshell script that runs via cron, does "q event * * "
(or the equivalent in a SELECT), parse the output, formats a message
with the failed/missed node names, and sends it to Openview via trapgen.
Wanda Prather
"I/O, I/O, It's all about I/O" -(me)
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Hart, Charles
Sent: Friday, July 15, 2005 9:42 AM
To: ADSM-L@VM.MARIST.EDU
Subject: SNMP and Client Backup Failures
Is anyone using TSM's SNMP agent to trap client backup failures? I see
people are using snmp to monitor server errors but what about the
clients. Is this possible?
Regards,
Charles
