nv-l

Using public as community name in spite of...

2001-02-05 16:40:05
Subject: Using public as community name in spite of...
From: Jane Curry <jane.curry AT skills-1st.co DOT uk>
To: nv-l AT lists.tivoli DOT com
Date: Mon, 05 Feb 2001 21:40:05 +0000
We are struggling with NetView 6.0.1 on NT to prevent it using public as
a community name.  ovsnmp.conf has a few specific node/community names
(none using public) and a default that is NOT public.  We have entirely
removed communityNames.conf.   In spite of this, we find nodes being
sent SNMP packets with public - and when the SNMP GET is successful, the
node is automatically added to ovsnmp.conf with public.

WE DON'T HAVE CONTROL OVER THESE DEVICES SO SUGGESTING CHANGING THE
AGENT CUSTOMISATION IS NOT VALID, but we really, really, don't want to
get SNMP answers out of them.

An earlier append suggested that following this process, including the
complete removal of communityNames.conf, solved the problem - but
perhaps that scenario was Unix rather than NT??

2 questions:
1) Does anyone else see this problem and have a solution?  We are
working on using the "I" flag in oid_to_type - not sure yet whether it
is going to suffice
2) Does anyone know if this is fixed in 6.0.2 which James said had gone
to manufacturing last week  (Hint - James - if you have time, I'd love a
list of bug fixes in 6.0.2.....)

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


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