That makes perfect sense now! The documentation in symon 1.6 doesnt tally
with SMC3.0.
I've been trying to learn how to work out my own implementation, but there
arent any books or references to troubleshooting or writing your own snmp
agents. mauro's essential snmp & Stallings' SNMP, SNMPv2,v3, RMON1&2 have
been useful in deriving a coherent overview.. but you really dont get to
know enough to troubleshoot mibs or snmp problems. Hopefully, I may get a
better idea how to write my own mib after going through "understanding snmp
mibs". But without smc or Symon, how would you grep for critical events then
if all not such events are logged?

regards, Veni

inveni@hotmail.com


"Mike Kirk" <primealert@gmail.com> wrote in message
news:f0bc53ee.0410130727.3d59407e@posting.google.c om...
> Veni,
>
> > From the documents from sun, it is implied that from Symon 1.6
> > http://docs.sun.com/db/doc/805-4829/6j4io2pah?a=view, we should have
> > the mibs for hardware component monitoring
>
> Ah, I see where you're coming from. SyMON 1.x and SyMON 2.x (renamed
> to "Sun Management Center" as of version 3) are totally seperate
> products. Essentially 1.x was scrapped when 2.x was codeveloped with a
> partner (where Halcyon comes in). 2.x onwards all use the same core
> infrastructure, so 2.x docs still have some relevance to the most
> current version (3.5.1). But 1.x docs have nothing to do with 2.x or
> higher.
>
> > I am wondering if it would simply be cleaner to implement an
> > snmp trap (for hardware component monitoring) using the generic tools on
> > sun & perl given that critical errors and failures should be readable
> > and grepped off some of the syslog or var/admin logs.
>
> Scripts and logs may well be enough for your environment, especially
> if you have a bunch of non-production and/or small systems to
> maintain. But SunMC hardware monitoring also uses C code/libraries to
> query hardware for things that otherwise don't show up in log files.
> Especially for larger systems (3/4/6800, 12/15/20/25k range).
>
> You also have to ask yourself how much work it will be to maintain
> your setup in the face of new Sun hardware and software (i.e. Solaris
> 10) given that the basic hardware monitoring in SunMC is free.
> Downloading a new version may be easier to do than hacking away at
> Perl, though not nearly as fun!
>
> Regards,
>
> Mike
>
> Note: I am an employee of Halcyon (www.HalcyonInc.com)