[Top] [All Lists]

RE: MLM on Solaris 2.7

To: nv-l@lists.tivoli.com
Subject: RE: MLM on Solaris 2.7
From: "Joel A. Gerber" <joel.gerber@usaa.com>
Date: Fri, 8 Sep 2000 08:42:36 -0500

We have several MLM servers on Solaris 2.7, and midmand is working OK, but
there ARE definitely problems with SNMP.  We seem to be having the
"opposite" problems as you, though.  SNMP to midmand is working fine, but
the mibiisa and dmi sub-agents are having problems.  Additionally, when the
server is rebooted, the snmpdx agent has problems initializing, but if we
restart it, then everything is fine with midmand.

I'm not sure about smconfig using a different port to communicate with
midmand.  I always thought that it used the standard SNMP port, but I've
never verified it.

If you give me some specific configuration files that you are interested in
seeing, I'll see if I can send those to you.

Joel Gerber - I/T Networking Professional - USAA Information Technology Co.
- San Antonio, TX
* (210)913-4231         * mailto:Joel.Gerber@USAA.com   "

-----Original Message-----
From:   Chris Cowan [SMTP:chris.cowan@2nd-wave.com]
Sent:   Wednesday, September 06, 2000 10:08
To:     nv-l@tkg.com
Subject:        [NV-L] MLM on Solaris 2.7

Has anyone gotten an MLM to work successfully on Solaris 2.7?

I have been doing some experimentation in my lab, and had no problems with
using MLM on either NT or Windows 2000.   It was absolutely painless.   SNMP
queries and smconfig show the tables populated exactly as I expected.

On Solaris I can't seem the midmand subagent to communicate properly.  The
symptoms I've noticed are:

- I'm unable to query any of the MLM MIB objects in either RO or RW mode,
under any circumstances.  I have no problems seeing the MIB-2 or Sun

- I've only been able to use smconfig against a Solaris MLM, when the dmi
subagent is stopped, and ony after I've made updates to both
/etc/snmp/conf/snmpd.conf and midmand.acl
Otherwise, smconfig complains about not be able to connect to a NetView
agent.  (This also brings up the realization that smconfig uses something
other than SNMP to communicate to the agent, perhaps port 1668).

- When snmpwalk public .
returns the correct result, I still seem to be having problems.

I'm fairly convinced that the problem lies somewhere in the *.conf, *.acl,
and *.reg files all located in /etc/snmp/conf, and the midmand is not
properly connected the snmpdx daemon.
I just can't seem to find the right combination.

Anyone seen this, or know what the problem is?   Actually, if someone could
post a configuration that does not use the default community names, I would


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

Archive operated by Skills 1st Ltd

See also: The NetView Web