Check out the .acl files in the /etc/snmp/conf directory. You may need to
fix up community strings int he mgragentd.acl or the snmpdx.acl daemon. I
had this problem earlier and Paul Stroud educated me. I believe the
mgragentd guy is the one  that makes "isManager" true.

-----Original Message-----
From: James Shanks [mailto:SHANKS AT us.tivoli DOT com]
Sent: Wednesday, September 05, 2001 6:48 AM
To: IBM NetView Discussion
Subject: Re: [NV-L] What test is used to set isManager


I cannot give you details, but (as is typical for Sun)  your Solaris
systems are not responding to SNMP correctly.
If mgragentd is not active or the SNMP query which should be responded to
by him does not work, then the system will not be identified as a NetView
system.

James Shanks
Level 3 Support
Tivoli NetView for UNIX and NT
Please note that my new id is jshanks AT us.ibm DOT com



"Cowan, Chris" <Chris.Cowan AT 2ndwaveinc DOT com>@tkg.com on 09/04/2001 
05:59:36
PM

Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>

Sent by:  owner-nv-l AT tkg DOT com


To:   "IBM NetView Discussion (E-mail)" <nv-l AT tkg DOT com>
cc:
Subject:  [NV-L] What test is used to set isManager





I've been trying to implement a backup manager, and have run into a
problem.

It seems that the isManager field is not being reliably set during
discoveries.   All my present systems, are running on Solaris.  The systems
in question are running other SNMP products, as well.   Forcing a demand
poll does not seem to fix the problem.

Anyway, my first basic question is what test does Netmon (or whatever)
conduct against a Node, in order to set the "isManager" field?