HI,
we do something similar with TME10/Netview for AIX since some month and it
works fine.
Here is some of the configuration stuff: ( ADSM Server is on level 3.1.2.20
)
herfried
herfried
--------------------------- config stuff
-----------------------------------
-----------------------------------
1.Modify server options file, dsmserv.opt, to specify the SNMP communication 
method.
1.Modify server options file, dsmserv.opt, to specify the SNMP communication 
method.

e.g:
commmethod                  snmp

         snmpheartbeatinterval    5
         snmpmessagecategory      severity

2.Install, configure, and start the SNMP agent as described in the 
documentation for that agent. The SNMP agent must support the DPI Version 2.0
standard. For
     example, the AIX SystemView agent is configured by customizing the file 
/etc/snmpd.conf. A default configuration might look like this:

     logging    file=/var/snmp/snmpd.log  enabled
     logging    size=0  level=0
     community  public
     community  private 127.0.0.1   255.255.255.255 readWrite
     community  system  127.0.0.1   255.255.255.255 readWrite  1.17.2
     view       1.17.2 system enterprises view
     trap       public  * snmp_manager_ip_adr *   1.2.3 fe
     snmpd      maxpacket=16000 smuxtimeout=60


     where * snmp_manager_ip_adr * is the IP address of the system running the 
SNMP management application.

3.Start ADSM SNMP subagent through the dsmsnmp executable.

4.Start the ADSM server to begin communication through the configured TCP/IP 
port with the subagent.

5.Begin event logging for the SNMP receiver and enable individual events or 
event severities to be reported to SNMP. For example, issue the following
commands:

     begin eventlogging snmp
     enable event snmp all

6.Define the ADSM SNMP MIB values for the SNMP manager to help format and 
display the ADSM SNMP MIB variables and messages. The
   ADSMSERV.MIB file ships with the ADSM server and must be loaded by the SNMP 
manager. For example, when you run NetView for OS/2 as an SNMP
   manager, the ADSMSERV.MIB file is copied to the \ netview_path\SNMP_MIB 
directory and then loaded through the following command:

     [C:\] loadmib -load adsmserv.mib
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
And now some hints  from our TME10 Netview implementation:
And now some hints  from our TME10 Netview implementation:

ad 6) you will use the "Load Mib"  from your OpenView Mgmt. Station
ad 5) enable evant snmp all is not realy good, but fine for testing

There is a mib2trap script that creates a shell script out of the mib 
definition file. If you run this script it adds the traps to trapd.conf, but in
our case we had to change the enterprise in this genarated script, cause it was 
wrong.
We always got "trap with unknown format" in the Netviews event log. ( You see 
the right enterprise there ). And the traps also were set up to LOG
only, so if the traps where ok then, we saw no errors and also no traps in the
event log. You have to change theire attitude in Openview Trap Custom.






"Jones, Bernard" <bernard_jones AT MERCK DOT COM>@VM.MARIST.EDU> on 28.02.2000
15:34:22

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:  SNMP Monitoring and Reporting


Hello All:

        Anyone out there have experience in using SNMP monitoring to manage
ADSM from a central repository like HPOpenView ??  I want to put a process
in place where specific ADSM error messages are routed to an HPOpenView
monitor
in our operations area.  Once this is established, I can have the
operations
staff
handle "tape related" ADSM error during the overnight shift to ensure clean
backups.
Any info would be appreciated...

Thanks,
Bernard A. Jones
Manager Storage Administration
(201) 703 - 7009