HPUX community[4]

community(4) community(4)
NAME
community - SNMP community name database
DESCRIPTION
The community file associates host names with SNMP community names.
The SNMP applications use this file to determine which SNMP community
name to use for SNMP requests.
SNMP community names are similar to passwords. The community name
sent with a request must match the community name expected by the
target SNMP node (agent). Some SNMP nodes support multiple levels of
access based on the community name (e.g., read-only versus read-
write). Since the capability of changing a remote node's
configuration may be sensitive, only store read-only SNMP community
names in this database. (See snmpd(1M).)
Each host has a single line with the following format.
hostname community proxy
hostname is the official host name (see hosts(4)). For aliases, enter
additional lines in the same format.
community is the SNMP community name used to access the hostname.
Separate the fields by blanks or tabs. Empty lines are ignored. A #
character indicates the beginning of a comment; characters from the #
character to the end of the line are ignored.
proxy is the offical host name (see hosts(4)) of the proxy. This
field is optional.
Use the default special name to indicate the community name used if a
hostname is not found in the database. This entry usually has the
value public.
EXAMPLES
Each line in the following community file has a preceding comment that
explains the entry.
# Community name for the testnode node is netman
testnode netman
# Community name for the monet node is painter
monet painter
# All SNMP requests for node renoir
# will be sent to node seurat using the community name
# proxy_comm
- 1 - Formatted: August 11, 1996
community(4) community(4)
renoir proxy_comm seurat
# Default community name is public
default public
AUTHOR
community was developed by HP.
FILES
/etc/community SNMP community names
SEE ALSO
snmpget(1), snmpnext(1), snmpset(1), snmptrap(1), snmpd(1M), hosts(4),
snmpd.conf(4), xnmintro(5).
RFC 1155, RFC 1156, RFC 1157, RFC 1158, RFC 1109.
- 2 - Formatted: August 11, 1996