Re: [nv-l] Sun snmp daemon and netview

[Michael Webb <mlwebb@us.ibm.com>]

I have not read Jane’s document, but here are some suggestions for querying Sun machines.

First, I usually comment out the managers line in the snmpd.conf file (or modify it to add your NV machine to the list so that the NV machine can query the Sun machine).

Second, the Solaris agent has an added security feature in its SNMP agent. It will trim your available MIB if you get the community string wrong more than 3 times, which this type of discovery will happen when using communityNames.conf with multiple strings in it.

This can be avoided by adding “-f 0” to the end of the command line that starts snmpd in the init.snmpdx script. You can find the script in the /etc/init.d directory. After you have made the change, restart the agents as follows:

/etc/init.d/init.dmi stop
/etc/init.d/init.snmpdx stop
/etc/init.d/init.snmpdx start
/etc/init.d/init.dmi start

Regards,

Michael Webb, IBM Tivoli
Q1CA Distributed NetView / ITSA SVT
Email: mlwebb@us.ibm.com
Ext: (919) 224-1410, T/L: 687-1410

Jane Curry <jane.curry@skills-1st.co.uk>

Jane Curry <jane.curry@skills-1st.co.uk> Sent by: owner-nv-l@lists.us.ibm.com 03/19/2004 11:48 AM Please respond to nv-l

To: nv-l@lists.us.ibm.com cc: Subject: Re: [nv-l] Sun snmp daemon and netview

I shiver whenever I have to work with the Sun SNMP agent again!  There 
are so many bits you have to configure, none of which is well 
documented.  I wrote a Tivoli Field Guide a couple of years back on this 
topic - you can get it at 
http://www-1.ibm.com/support/entdocview.wss?uid=swg27002148

One of the things that can happen is that someone changes some community 
name customisation and you end up with access to the base snmpdx agent 
but, on Solaris, it is the mibiisa agent that answers all MIB-2 queries.

Cheers,
Jane

Qureshi, Fawad wrote:

> NV 7.1.3 / AIX 5.1
>
>  
>
> Has anyone experienced any problems using Sun's snmp daemon and 
> Netview? Especially with community names?
>
>  
>
> We have several Sun servers that we have been monitoring fine till few 
> days back. These servers do not respond to snmpwalk or any snmp 
> queries anymore. SNMP times out. Possible cause could be incorrect 
> community name, but I have checked and all looks correct on both 
> sides. I am able nmdemandpoll, TCP/SNMP connectivity etc. just fine, 
> except SNMP requests time out.
>
>  
>
> I have done xnmsnmpconf -resolve and result is correct. Forcing 
> community name with snmpwalk -c still results in time out due to bad 
> community.
>
>  
>
> "Bad Community name" alerts are also being logged in Sun's syslog files.
>
>  
>
> I have seen this before as well, and always with Sun servers. Any 
> ideas? Thanks.
>
>  
>
> **Cheers **
>
> ** **
>
> **Fawad Qureshi**
>
>  
>

-- 
Tivoli Certified Consultant & Instructor
Skills 1st Limited, 2 Cedar Chase, Taplow, Bucks, SL6 0EU, UK
Tel: +44 (0)1628 782565
Copyright (c) 2004 Jane Curry <jane.curry@skills-1st.co.uk>.  All rights reserved.