With ALL events enabled, ANY admin command you send to TSM (like a Q DB)
will be logged in the event log, and therefore should be sent to your
SNMP receiver.

I have always had to stop and restart TSM AFTER you get dsmsnmp talking
for the msg forwarding to work.

Then in your TSM actlog you should see the msg "ANR4660 Connected to
SNMP subagent on port ......"
Wont' work until you get that happening.

Also, you will probably have to load the TSM mib into your SNMP
receiver.
Search on *.mib, you'll find it in the TSM server directories somewhere.

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: Tuesday, August 30, 2005 9:08 AM
To: [email protected]
Subject: More TSM /SNMP Questions


Ok, got SNMP running @ the OS, dsmsnmp is running and connects to os
SNMP.  
I've enabled all SNMP events in TSM, 

Dsmserv.opt
COMMmethod SNMP
SNMPSUBAGENT HOST 127.0.0.1 COMM public timeout 600
SNMPSUBAGENTHOST  127.0.0.1 
SNMPMESSAGECATEGORY SEVERITY

Then did the following on TSM
BEGIN EVENTLOGGING snmp 
Enable EVENTS snmp all

All I see in the snmpdv3.log  is the foillowing...  Is there a way to
force a snmp test trap?
08/30/05 07:42:36 AM -  s_agv123.c(1498): Dyn. Conf: Time to backup the
config file 1125405756
 08/30/05 07:42:36 AM -  s_dynfup.c(155): Dyn.Conf: dynUpdateConfigFile
invoked 
 08/30/05 07:42:36 AM -  s_dynfup.c(269): Dyn.Conf: Returning from
dynUpdateConfigFile : 0
 08/30/05 07:42:36 AM -  s_agv123.c(1517): Dyn. Conf: currentTime :
1125405756
 08/30/05 07:42:36 AM -  s_agv123.c(1519): Dyn. Conf: timeToBackup :
1125406056
 08/30/05 07:42:36 AM -  s_agv123.c(1521): Dyn. Conf: fileUpdTimeout :
300

Am I missing something?  Really appreciate the help!  Cant be this
hard... 

Reply via email to