Hi Les,
The configuration of the SNMP agent in Solaris is a little bit different.
You nedd to use, in the case of MLM, the snmpdx as the agent, and two
subagents: mibiisa (or another free avalaible) for the mib-2 tree, and the
midmand for the MLM configurations tree.
There is a good paper called
SNMP Agents for Solaris and their Integration with
NetView and Mid Level Managers
Jane Curry, Skills 1st Limited
jane.curry@skills-1st.co.uk
that explains how to configure this agents.
I cant remember where I´ve got it. But if you cannot find it, I can send you a
copy. It is small.
There is just a error in the paper. You have to specify the option Port=XXX in
all the registration files, and not just in snmpdx.reg file, like show the
paper.
Regards,
--
Helder Luiz Garcia
Engenheiro de Sistemas
http://www.vanguard-it.com.br
-----Mensagem original-----
De: lesdickert@att.net [mailto:lesdickert@att.net]
Enviada em: terça-feira, 5 de fevereiro de 2002 12:01
Para: nv-l@lists.tivoli.com
Assunto: [nv-l] MLM configuration setup problem
Trying to set up NetView MLM on a Windows 2000
Server. Installed it fine from the NetView 7.1
CD and the log files verify that it is running.
However, when I try to configure it from a NetView 6.0.2
running on a Sparc station I have trouble. I can
demand poll the Windows 2000 server fine, but when
I run Tools->MLM Configuration Application, I get
messages along the lines of:
"TME 10 NetView agent(s) not found.
Community name could be invalid..."
Using a Sniffer, I discovered that the MLM Configuration
Application is doing 3 SNMPGETs to the MLM:
SNMPGET OID Reply from MLM
--------------- ----------------------
ibm.6.12.1.1.3.0 - returns fine from MLM
ibm.6.12.1.10.1.3.0 - no such MIB variable
ibm.6.60.1.1.1.3.0 - no such MIB variable
I Checked the MIB files on both servers for the second
two MIBs and they aren't there. I don't know why
the MLM Configuration Application is doing an SNMPGET
to retrieve MIB values for MIBs that are not in the
MIB files.
Anyone have any idea what is wrong or what I have
done wrong?
TIA,
Les Dickert
-------------------------------------------------------------------
Este e-mail foi enviado pelo site da Nlink: http://www.nlink.com.br
|