SUMMARY: snmpd.conf configuration - two pollers in same community?
From: Reed, Judith (jreed_at_navisite.com)
Date: 03/23/04
- Previous message: jhamlin_at_bhe.com: "Output from "cp" command"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 23 Mar 2004 10:50:20 -0500 To: tru64-unix-managers@ornl.gov
Greetings. I'd asked what the correct entries were for snmpd.conf to
allow redundant (unique) servers to both poll a tru64 v5.1a system using
the same community. I noted that adding two strings of the form:
community community_string ip#1 read
community community_string ip#2 read
actually works, but snmpd complains about it on startup.
I only rec'd one reply, from Dr. Blynn - thanks to him.
He said (in part):
"I get the distinct impression from the reference page that there
is supposed to be a one-to-one mapping between the community name and
a single IP address. But then, other than replacing the "public" name
with others that have restrictions, it's unclear to me from reading
the man page what use there is. It even looks like you could use the
IP address itself as the community name... If it's working, maybe you
should just ignore the warning message.. "
We've decided to do just that for now - ignore the warning msg. However,
situation may escalate when we want to allow pollers from multiple
datacenters to poll each server from same community to provide extensive
redundancy, so I may be revisiting the situation at some point soon!
Thanks,
Judith Reed
jreed@navisite.com
Service delivery manager, Syracuse Data Center
315-453-2912 x5835
- Previous message: jhamlin_at_bhe.com: "Output from "cp" command"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
