Re: IBM i and SNMP -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: IBM i and SNMP
From: Marc Rauzier <marc.rauzier@xxxxxxxxx>
Date: Tue, 19 Apr 2016 22:27:16 +0200
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Le 19/04/2016 21:54, Rob Berendt a écrit :

3.1.4. Default or Guessable SNMP community names: public (snmp-read-0001)
Description:

If you don't use an snmp manager, the best option is not to start snmp service.
Otherwise, usually changing the community name, through CHGSNMPA command, to someting else than "public" is enough to comply with security scans issues.

Marc

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: IBM i and SNMP , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.