Import translated manuals from JM CVS Repository.

[linuxjm/jm.git] / manual / ucd-snmp / draft / man5 / snmpd.conf.5

.\"
.\" Japanese Version Copyright (c) 2002 Yuichi SATO
.\"         all rights reserved.
.\" Translated Mon May  6 20:59:37 JST 2002
.\"         by Yuichi SATO <ysato@h4.dion.ne.jp>
.\"
.TH SNMPD.CONF 5 "28 Aug 2001"
.ds )H U.C. Davis, ECE Dept.
.ds ]W V4.2.4
.UC 4
.\"O .SH NAME
.SH ̾Á°
.\"O /usr/share/snmp/snmpd.conf - configuration file for the ucd-snmp SNMP agent.
/usr/share/snmp/snmpd.conf - ucd-snmp SNMP ¥¨¡¼¥¸¥§¥ó¥È¤ÎÀßÄê¥Õ¥¡¥¤¥ë
.\"O .SH DESCRIPTION
.SH ÀâÌÀ
.\"O .B snmpd.conf
.\"O is the configuration file which defines how the ucd-smnp SNMP agent
.\"O operates.  These files may contain any of the directives found in the
.\"O DIRECTIVES section below.  This file is not required for the agent to
.\"O operate and report mib entries.
.B snmpd.conf
¤Ï ucd-smnp SNMP ¥¨¡¼¥¸¥§¥ó¥È¤ÎÁàºîË¡¤òÄêµÁ¤¹¤ëÀßÄê¥Õ¥¡¥¤¥ë¤Ç¤¢¤ë¡£
¤³¤Î¥Õ¥¡¥¤¥ë¤Ï²¼µ­¤Î¡Ö¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡×¥»¥¯¥·¥ç¥ó¤Ë¤¢¤ë
Ǥ°Õ¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò´Þ¤à¤³¤È¤¬¤Ç¤­¤ë¡£
¥¨¡¼¥¸¥§¥ó¥È¤¬ mib ¥¨¥ó¥È¥ê¤òÁàºî¤·¤¿¤êɽ¼¨¤·¤¿¤ê¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
¤³¤Î¥Õ¥¡¥¤¥ë¤ÏɬÍפʤ¤¡£
.\"O .SH PLEASE READ FIRST
.SH ºÇ½é¤Ë¤ªÆɤߤ¯¤À¤µ¤¤
.\"O First, make sure you have read the snmp_config(5) manual page that
.\"O describes how the ucd-snmp configuration files operate, where they
.\"O are located and how they all work together.
ºÇ½é¤Ë man ¥Ú¡¼¥¸ snmp_config(5) ¤òÆɤó¤Ç¤ª¤¯¤³¤È¡£
¤³¤³¤Ë¤Ï ucd-snmp ¥Õ¥¡¥¤¥ë¤ÎÁàºîË¡¡¦¾ì½ê¡¦
¸ß¤¤¤Ë¤É¤Î¤è¤¦¤ËÆ°ºî¤¹¤ë¤«¤¬½ñ¤«¤ì¤Æ¤¤¤ë¡£
.PP
.\"O Also, you might consider looking into the
.\"O .I snmpconf
.\"O application (perl script) which can help you build a snmpd.conf file
.\"O by prompting you for information.  You should try it.  Really.  Go
.\"O ahead.  Right now.  Run:
¤µ¤é¤Ë¡¢
.I snmpconf
¥¢¥×¥ê¥±¡¼¥·¥ç¥ó (perl ¥¹¥¯¥ê¥×¥È) ¤Ë¤¶¤Ã¤ÈÌܤòÄ̤¹¤Î¤â¤è¤¤¤«¤â¤·¤ì¤Ê¤¤¡£
¤³¤Î¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ï¥æ¡¼¥¶¡¼¤Ë¾ðÊó¤òÄ󼨤·¤Æ
snmpd.conf ¥Õ¥¡¥¤¥ë¤ÎºîÀ®¤ò½õ¤±¤Æ¤¯¤ì¤ë¡£
»î¤·¤Æ¤ß¤Ê¤µ¤¤¡£ËÜÅö¤Ë¡£¤µ¤¢¡¢º£¤¹¤°¤Ë¡£
.RS
.IP "snmpconf -g basic_setup"
.RE
.PP
.\"O to get you started.
¤Ç»Ï¤á¤é¤ì¤Þ¤¹¡£
.\"O .SH EXTENSIBLE-MIB
.SH ³ÈÄ¥²Äǽ MIB
.PP
.\"O The ucd-snmp SNMP agent reports much of its information through
.\"O queries to the 1.3.6.1.4.1.2021 section of the mib tree.  Every mib in
.\"O this section has the following table entries in it.
ucd-snmp SNMP ¥¨¡¼¥¸¥§¥ó¥È¤Ï¡¢
mib ¥Ä¥ê¡¼¤Î 1.3.6.1.4.1.2021 ¥»¥¯¥·¥ç¥ó¤ËÂФ·¤Æ¥¯¥§¥ê¡¼¤ò¹Ô¤¤¡¢
¿¤¯¤Î¾ðÊó¤òɽ¼¨¤¹¤ë¡£
¤³¤Î¥»¥¯¥·¥ç¥ó¤Î³Æ mib ¤Ë¤Ï°Ê²¼¤Î¥Æ¡¼¥Ö¥ë¥¨¥ó¥È¥ê¤¬¤¢¤ë¡£
.IP ".1 -- index"
.\"O This is the table's index numbers for each of the DIRECTIVES listed below.
°Ê²¼¤Ë¥ê¥¹¥È¤µ¤ì¤¿¡Ö¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¡×¤ËÂФ¹¤ë¥Æ¡¼¥Ö¥ë¤Î¥¤¥ó¥Ç¥Ã¥¯¥¹Èֹ档
.IP ".2 -- name"
.\"O The name of the given table entry.  This should be unique, but is not
.\"O required to be.
»ØÄꤵ¤ì¤¿¥Æ¡¼¥Ö¥ë¥¨¥ó¥È¥ê¤Î̾Á°¡£
¤³¤ì¤Ï¾¤È½Å¤Ê¤é¤Ê¤¤Êý¤¬Îɤ¤¤¬¡¢½Å¤Ê¤Ã¤Æ¤â¹½¤ï¤Ê¤¤¡£
.IP ".100 -- errorFlag"
.\"O This is a flag returning either the integer value 1 or 0 if an error
.\"O is detected for this table entry.
¤³¤Î¥Æ¡¼¥Ö¥ë¥¨¥ó¥È¥ê¤Ë¥¨¥é¡¼¤¬¸«¤Ä¤«¤Ã¤¿¾ì¹ç¤Ë¡¢
À°¿ô 1 ¤Þ¤¿¤Ï 0 ¤òÊÖ¤¹¥Õ¥é¥°¡£
.IP ".101 -- errorMsg"
.\"O This is a DISPLAY-STRING describing any error triggering the errorFlag above.
¾åµ­¤Î errorFlag ¤ò°ú¤­µ¯¤³¤¹¥¨¥é¡¼¤òÀâÌÀ¤¹¤ë¡Öɽ¼¨Ê¸»úÎó¡×¡£
.\"sato: DISPLAY-STRING ¤ËÂбþ¤¹¤ëÌõ¸ì¤Ï¤¢¤ë¤Î¤«¤Ê¡©
.IP ".102 -- errorFix"
.\"O If this entry is SNMPset to the integer value of 1 AND the errorFlag
.\"O defined above is indeed a 1, a program or script will get executed
.\"O with the table entry name from above as the argument.  The program to
.\"O be executed is configured in the config.h file at compile time.
¤³¤Î¥¨¥ó¥È¥ê¤¬ SNMPset ¤«¤éÀ°¿ô 1 ¤Ç¡¢
¤«¤Ä¾å¤ÇÄêµÁ¤µ¤ì¤Æ¤¤¤ë errorFlag ¤¬ 1 ¤Î¾ì¹ç¡¢
¾åµ­¤Î¥Æ¡¼¥Ö¥ë¥¨¥ó¥È¥ê̾¤ò°ú¤­¿ô¤È¤·¤Æ
¥×¥í¥°¥é¥à¤ä¥¹¥¯¥ê¥×¥È¤¬¼Â¹Ô¤µ¤ì¤ë¡£
.\"sato: 1 ¹ÔÌܤΠSNMPset to the integer value of 1 ¤¬¤è¤¯¤ï¤«¤é¤Ê¤¤¡£
¼Â¹Ô¤µ¤ì¤ë¥×¥í¥°¥é¥à¤Ï¥³¥ó¥Ñ¥¤¥ë»þ¤Ë config.h ¥Õ¥¡¥¤¥ë¤ÇÀßÄꤵ¤ì¤ë¡£
.\"O .SS Directives
.SS ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
.IP "proc NAME"
.IP "proc NAME MAX"
.IP "proc NAME MAX MIN"
.IP
.\"O Checks to see if the NAME'd processes are running on the agent's
.\"O machine.  An error flag (1) and a description message are then passed
.\"O to the 1.3.6.1.4.1.2021.2.1.100 and
.\"O 1.3.6.1.4.1.2021.2.1.101 mib columns (respectively) if the
.\"O NAME'd program is not found in the process table as reported by "/bin/ps -e".
NAME ¤È¤¤¤¦Ì¾Á°¤Î¥×¥í¥»¥¹¤¬
¥¨¡¼¥¸¥§¥ó¥È¤Î¥Þ¥·¥ó¤Ç²ÔƯ¤·¤Æ¤¤¤ë¤«¤ò¥Á¥§¥Ã¥¯¤¹¤ë¡£
NAME ¤È¤¤¤¦Ì¾Á°¤Î¥×¥í¥°¥é¥à¤¬
"/bin/ps -e" ¤Çɽ¼¨¤µ¤ì¤ë¥×¥í¥»¥¹¥Æ¡¼¥Ö¥ë¤Ë¤Ê¤¤¾ì¹ç¡¢
¥¨¥é¡¼¥Õ¥é¥° (1) ¤ÈÀâÌÀ¤Î¥á¥Ã¥»¡¼¥¸¤¬
mib ¥³¥é¥à¤Î 1.3.6.1.4.1.2021.2.1.100 ¤È
1.3.6.1.4.1.2021.2.1.101 ¤Ë (¤½¤ì¤¾¤ì) ÅϤµ¤ì¤ë¡£
.IP
.\"O If MAX and MIN are not specified, MAX is assumed to be 
.\"O .B infinity
.\"O and MIN is assumed to be 1.
MAX ¤È MIN ¤¬»ØÄꤵ¤ì¤Ê¤¤¾ì¹ç¡¢MAX ¤Ï
.B infinity
(̵¸ÂÂç) ¤Ç MIN ¤Ï 1 ¤Ç¤¢¤ë¤È²¾Äꤵ¤ì¤ë¡£
.IP
.\"O If MAX is specified but MIN is not specified, MIN is assumed to be 0.
MAX ¤Ï»ØÄꤵ¤ì¤Æ¤¤¤ë¤¬¡¢MIN ¤Ï»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
MIN ¤Ï 0 ¤Ç¤¢¤ë¤È²¾Äꤵ¤ì¤ë¡£
.IP "procfix NAME PROG ARGS"
.\"O This registers a command that knows how to fix errors with the given
.\"O process NAME.  When 1.3.6.1.4.1.2021.2.1.102 for a given
.\"O NAMEd program is set to the integer value of 1, this command will be
.\"O called.  It defaults to a compiled value set using the PROCFIXCMD
.\"O definition in the config.h file.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢NAME ¤Ç»ØÄꤵ¤ì¤¿¥×¥í¥»¥¹¤ÇȯÀ¸¤·¤¿¥¨¥é¡¼¤ò
½¤Àµ¤¹¤ë¤¿¤á¤Î¥³¥Þ¥ó¥É¤òÅÐÏ¿¤¹¤ë¡£
NAME ¤Ç»ØÄꤵ¤ì¤¿¥×¥í¥°¥é¥à¤ËÂФ·¤Æ 1.3.6.1.4.1.2021.2.1.102 ¤¬
À°¿ôÃÍ 1 ¤ËÀßÄꤵ¤ì¤¿¾ì¹ç¡¢¤³¤Î¥³¥Þ¥ó¥É¤¬¸Æ¤Ó½Ð¤µ¤ì¤ë¡£
¸Æ¤Ó½Ð¤µ¤ì¤ë¥×¥í¥°¥é¥à¤Î¥Ç¥Õ¥©¥ë¥È¤Ï¡¢¥³¥ó¥Ñ¥¤¥ë»þ¤ÎÃͤǤ¢¤ê¡¢
config.h ¥Õ¥¡¥¤¥ë¤Î PROCFIXCMD ¤ÇÄêµÁ¤µ¤ì¤ë¡£
.IP "exec NAME PROG ARGS"
.IP "exec MIBNUM NAME PROG ARGS"
.IP
.\"O If MIBNUM is not specified, the agent executes the named PROG with
.\"O arguments of ARGS and returns the exit status and the first line of
.\"O the STDOUT output of the PROG program to queries of the
.\"O 1.3.6.1.4.1.2021.8.1.100 and
.\"O 1.3.6.1.4.1.2021.8.1.101 mib columns (respectively).  All
.\"O STDOUT output beyond the first line is silently truncated.
MIBNUM ¤¬»ØÄꤵ¤ì¤Ê¤¤¾ì¹ç¡¢
¥¨¡¼¥¸¥§¥ó¥È¤Ï PROG ¤È¤¤¤¦Ì¾Á°¤Î¥×¥í¥°¥é¥à¤ò°ú¤­¿ô ARGS ¤òÉÕ¤±¤Æ¼Â¹Ô¤·¡¢
¥×¥í¥°¥é¥à PROG ¤Î½ªÎ»¥¹¥Æ¡¼¥¿¥¹¤Èɸ½à½ÐÎϤΠ1 ¹ÔÌܤòÊÖ¤¹¡£
¤³¤ì¤é¤Ï¤½¤ì¤¾¤ì mib ¥³¥é¥à¤Î 1.3.6.1.4.1.2021.8.1.100 ¤È
1.3.6.1.4.1.2021.8.1.101 ¤ÎÃͤò¥¯¥§¥ê¡¼¤·¤¿¤â¤Î¤Ç¤¢¤ë¡£
ɸ½à½ÐÎϤΠ1 ¹ÔÌܰʹߤϰÅÌÛ¤ÎÆâ¤Ë¾Êά¤µ¤ì¤ë¡£
.IP
.\"O If MIBNUM is specified, it acts as above but returns the exit status
.\"O to MIBNUM.100.0 and the entire STDOUT output to the table
.\"O MIBNUM.101 in a mib table.  In this case, the MIBNUM.101 mib
.\"O contains the entire STDOUT output, one mib table entry per line of
.\"O output (ie, the first line is output as MIBNUM.101.1, the second
.\"O at MIBNUM.101.2, etc...).
MIBNUM ¤¬»ØÄꤵ¤ì¤¿¾ì¹ç¤â¡¢¾å¤ÈƱ¤¸¤è¤¦¤ËÆ°ºî¤¹¤ë¤¬¡¢
½ªÎ»¥¹¥Æ¡¼¥¿¥¹¤ò MIBNUM.100.0 ¤ËÊÖ¤·¡¢
ɸ½à½ÐÎÏÁ´ÂΤò mib ¥Æ¡¼¥Ö¥ëÆâ¤Î¥Æ¡¼¥Ö¥ë MIBNUM.101 ¤ËÊÖ¤¹¡£
¤³¤Î¤È¤­ MIBNUM.101 mib ¤Ë¤Ïɸ½à½ÐÎϤؤνÐÎÏÁ´ÂΤ¬Æþ¤ê¡¢
1 ¤Ä¤Î mib ¥Æ¡¼¥Ö¥ë¥¨¥ó¥È¥ê¤Ë¤Ï½ÐÎϤΠ1 ¹Ôʬ¤¬Æþ¤ë
(¤Ä¤Þ¤ê¡¢½ÐÎϤÎÂè 1 ¹Ô¤Ï MIBNUM.101.1¡¢
Âè 2 ¹Ô¤Ï MIBNUM.101.2¡¢... ¤È¤Ê¤ë)¡£
.RS
.\"O .IP Note:
.IP Ãí°Õ:
.\"O The MIBNUM must be specified in dotted-integer notation and can
.\"O not be specified as ".iso.org.dod.internet..." (should instead
.\"O be .1.3.6.1...).
MIBNUM ¤Ï¥É¥Ã¥È¶èÀÚ¤ê¤ÎÀ°¿ôÃÍɽµ­¤Ç¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
(.1.3.6.1... ¤ÎÂå¤ï¤ê¤Ë) ".iso.org.dod.internet..." ¤Î¤è¤¦¤Ë
»ØÄꤹ¤ë¤³¤È¤Ï¤Ç¤­¤Ê¤¤¡£
.\"O .IP Note: 
.IP Ãí°Õ:
.\"O The agent caches the exit status and STDOUT of the executed program
.\"O for 30 seconds after the initial query.  This is to increase speed and
.\"O maintain consistency of information for consecutive table queries.
¥¨¡¼¥¸¥§¥ó¥È¤ÏºÇ½é¤Î¥¯¥§¥ê¡¼¤ò¹Ô¤Ã¤¿¸å¡¢
¼Â¹Ô¤·¤¿¥×¥í¥°¥é¥à¤Î½ªÎ»¥¹¥Æ¡¼¥¿¥¹¤Èɸ½à½ÐÎϤò 30 Éô֥­¥ã¥Ã¥·¥å¤¹¤ë¡£
¤³¤ì¤Ë¤è¤ê¤½¤Î¸å¤Î¥Æ¡¼¥Ö¥ë¤Î¥¯¥§¥ê¡¼¤Î¥¹¥Ô¡¼¥É¤¬¾å¤¬¤ê¡¢
¾ðÊó¤Î°ì´ÓÀ­¤¬´ÉÍý¤Ç¤­¤ë¡£
.\"O The cache can be flushed by a snmp-set request of integer(1) to
.\"O 1.3.6.1.4.1.2021.100.VERCLEARCACHE.
¤³¤Î¥­¥ã¥Ã¥·¥å¤Ï 1.3.6.1.4.1.2021.100.VERCLEARCACHE ¤ò
À°¿ô (1) ¤ËÀßÄꤹ¤ë snmp-set Í×µá¤Ë¤è¤ê¾Ãµî¤µ¤ì¤ë¡£
.RE
.IP "execfix NAME PROG ARGS"
.\"O This registers a command that knows how to fix errors with the given
.\"O exec or sh NAME.  When 1.3.6.1.4.1.2021.8.1.102 for a
.\"O given NAMEd entry is set to the integer value of 1, this command will
.\"O be called.  It defaults to a compiled value set using the EXECFIXCMD
.\"O definition in the config.h file.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï NAME ¤Ç»ØÄꤵ¤ì¤¿
¼Â¹Ô¥×¥í¥°¥é¥à¤Þ¤¿¤Ï¥·¥§¥ë¥¹¥¯¥ê¥×¥È¤ÇȯÀ¸¤·¤¿
¥¨¥é¡¼¤ò½¤Àµ¤¹¤ë¤¿¤á¤Î¥³¥Þ¥ó¥É¤òÅÐÏ¿¤¹¤ë¡£
NAME ¤Ç»ØÄꤷ¤¿¥¨¥ó¥È¥ê¤ËÂФ·¤Æ
1.3.6.1.4.1.2021.8.1.102 ¤¬À°¿ôÃÍ 1 ¤ËÀßÄꤵ¤ì¤ë¤È¡¢
¤³¤Î¥³¥Þ¥ó¥É¤¬¸Æ¤Ó½Ð¤µ¤ì¤ë¡£
¸Æ¤Ó½Ð¤µ¤ì¤ë¥×¥í¥°¥é¥à¤Î¥Ç¥Õ¥©¥ë¥È¤Ï¡¢¥³¥ó¥Ñ¥¤¥ë»þ¤ÎÃͤǤ¢¤ê¡¢
config.h ¥Õ¥¡¥¤¥ë¤Î EXECFIXCMD ¤ÇÄêµÁ¤µ¤ì¤ë¡£
.IP "disk PATH"
.IP "disk PATH [ MINSPACE | MINPERCENT% ]"
.IP
.\"O Checks the named disks mounted at PATH for available disk space.  If
.\"O the disk space is less than MINSPACE (kB) if specified or less than
.\"O MINPERCENT (%) if a % sign is specified, or DEFDISKMINIMUMSPACE (kB)
.\"O if not specified, the associated entry in the
.\"O 1.3.6.1.4.1.2021.9.1.100 mib table will be set to (1) and
.\"O a descriptive error message will be returned to queries of
.\"O 1.3.6.1.4.1.2021.9.1.101.
PATH ¤Ë¥Þ¥¦¥ó¥È¤µ¤ì¤¿¥Ç¥£¥¹¥¯¤Î»ÈÍѲÄǽ¤Ê¥Ç¥£¥¹¥¯ÍÆÎ̤ò¥Á¥§¥Ã¥¯¤¹¤ë¡£
¥Ç¥£¥¹¥¯ÍÆÎ̤¬ MINSPACE (kB) ¤è¤ê¾¯¤Ê¤¤¾ì¹ç¡¢
¤Þ¤¿¤Ï % µ­¹æ¤ò»ØÄꤷ¤Æ MINPERCENT (%) ¤è¤ê¾¯¤Ê¤¤¾ì¹ç¡¢
¤Þ¤¿¤Ï DEFDISKMINIMUMSPACE (kB) ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
1.3.6.1.4.1.2021.9.1.100 mib ¥Æ¡¼¥Ö¥ë¤Î´ØÏ¢¤¹¤ë¥¨¥ó¥È¥ê¤¬ (1) ¤ËÀßÄꤵ¤ì¡¢
¥¨¥é¡¼¤òÀâÌÀ¤¹¤ë¥á¥Ã¥»¡¼¥¸¤¬
1.3.6.1.4.1.2021.9.1.101 ¤Î¥¯¥§¥ê¡¼¤Ë¤è¤Ã¤ÆÊÖ¤µ¤ì¤ë¡£
.IP "load MAX1"
.IP "load MAX1 MAX5"
.IP "load MAX1 MAX5 MAX15"
.IP
.\"O Checks the load average of the machine and returns an error flag (1),
.\"O and an text-string error message
.\"O to queries of 1.3.6.1.4.1.2021.10.1.100 and
.\"O 1.3.6.1.4.1.2021.10.1.101 (respectively) when the
.\"O 1-minute, 5-minute, or 15-minute averages exceed the associated
.\"O maximum values.  If any of the MAX1, MAX5, or MAX15 values are
.\"O unspecified, they default to a value of DEFMAXLOADAVE.
¥Þ¥·¥ó¤ÎÊ¿¶ÑÉé²Ù¤ò¥Á¥§¥Ã¥¯¤·¡¢
1 ʬ´Ö¡¦5 ʬ´Ö¡¦15 ʬ´Ö¤ÎÊ¿¶Ñ¤¬¤½¤ì¤¾¤ì¤ÎºÇÂçÃͤòĶ¤¨¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢
1.3.6.1.4.1.2021.10.1.100 ¤È 1.3.6.1.4.1.2021.10.1.101 ¤ò¥¯¥§¥ê¡¼¤·¤Æ¡¢
¥¨¥é¡¼¥Õ¥é¥° (1) ¤È¥Æ¥­¥¹¥Èʸ»úÎó¤Î¥¨¥é¡¼¥á¥Ã¥»¡¼¥¸¤òÊÖ¤¹¡£
MAX1, MAX5, MAX15 ¤ÎÃͤΤ¦¤Á»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¤â¤Î¤Ï¡¢
¥Ç¥Õ¥©¥ë¥È¤Î DEFMAXLOADAVE ¤Ë¤Ê¤ë¡£
.IP "file FILE [MAXSIZE]"
.\"O Monitors file sizes and makes sure they don't grow beyond a certain
.\"O size (in kilobytes).  MAXSIZE defaults to infinite if not specified,
.\"O and only monitors the size without reporting errors about it.
¥Õ¥¡¥¤¥ë¥µ¥¤¥º¤ò´Æ»ë¤·¡¢(¥­¥í¥Ð¥¤¥È¤Ç) »ØÄꤵ¤ì¤¿¥µ¥¤¥º¤ò
Ķ¤¨¤Æ¤Ê¤¤¤«¤ò¥Á¥§¥Ã¥¯¤¹¤ë¡£
MAXSIZE ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ï̵¸ÂÂç¤Ë¤Ê¤ê¡¢
¥¨¥é¡¼¤òÊó¹ð¤»¤º¤Ë¥µ¥¤¥º¤Î¤ß¤ò´Æ»ë¤¹¤ë¡£
.\"O .SS "Errors"
.SS ¥¨¥é¡¼
.PP
.\"O Any errors in obtaining the above information are reported via the
.\"O 1.3.6.1.4.1.2021.101.1.100 flag and the
.\"O 1.3.6.1.4.1.2021.101.1.101 text-string description.
¾åµ­¤Î¾ðÊó¤ò¼èÆÀ¤¹¤ë¤¿¤á¤Î¥¨¥é¡¼¤Ï¡¢
1.3.6.1.4.1.2021.101.1.100 ¥Õ¥é¥°¤È
1.3.6.1.4.1.2021.101.1.101 ¥Æ¥­¥¹¥Èʸ»úÎó¤ò¥¯¥§¥ê¡¼¤·¤Æɽ¼¨¤µ¤ì¤ë¡£
.\"O .SH AGENTX SUB-AGENTS
.SH AGENTX ¥µ¥Ö¥¨¡¼¥¸¥§¥ó¥È
.\"O To enable AgentX support in the snmp master agent, put the following
.\"O line in your snmpd.conf file:
.\"O .IP "master agentx"
.\"O Note that this support is still experimental, and should not be used
.\"O on production systems.  See README.agentx for details.
snmp ¥Þ¥¹¥¿¡¼¥¨¡¼¥¸¥§¥ó¥È¤Ç AgentX ¥µ¥Ý¡¼¥È¤òÍ­¸ú¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
snmpd.conf ¥Õ¥¡¥¤¥ë¤Ë°Ê²¼¤Î¤è¤¦¤Ê¹Ô¤ò½ñ¤­¹þ¤á¤Ð¤è¤¤:
.IP "master agentx"
¤³¤Î¥µ¥Ý¡¼¥È¤Ï¤Þ¤À¼Â¸³Åª¤Ê¤â¤Î¤Ç¡¢À½ÉÊÈǤΥ·¥¹¥Æ¥à¤Ç¤Ï»ÈÍѤ¹¤Ù¤­¤Ç¤Ï¤Ê¤¤¡£
¾ÜºÙ¤Ï README.agentx ¤ò»²¾È¤¹¤ë¤³¤È¡£
.\"O .SH SMUX SUB-AGENTS
.SH SMUX ¥µ¥Ö¥¨¡¼¥¸¥§¥ó¥È
.\"O To enable and SMUX based sub-agent, such as
.\"O .IR gated ,
.\"O use the
.\"O .I smuxpeer
.\"O configuration entry
.I gated
¤Î¤è¤¦¤Ê SMUX ¥Ù¡¼¥¹¤Î¥µ¥Ö¥¨¡¼¥¸¥§¥ó¥È¤òÍ­¸ú¤Ë¤¹¤ë¤¿¤á¤Ë¤Ï¡¢
°Ê²¼¤Î¤è¤¦¤Ë
.I smuxpeer
ÀßÄꥨ¥ó¥È¥ê¤ò»È¤¨¤Ð¤è¤¤:
.IP "smuxpeer OID PASS"
.\"O For 
.\"O .I gated
.\"O a sensible entry might be
.\"O .I smuxpeer .1.3.6.1.4.1.4.1.3 secret
.\"Osato: 
.\"Osato: sensible ¤Î°ÕÌ£¤Ï¡Ö¼ÂºÝ¤Î¡×¤Ç¤¤¤¤¤«¤Ê¡©
.\"Osato: 
.I gated
¤Ë¤Ä¤¤¤Æ¤Î¼ÂºÝ¤Î¥¨¥ó¥È¥ê¤Ï
.I smuxpeer .1.3.6.1.4.1.4.1.3 secret
¤Î¤è¤¦¤Ë¤Ê¤ë¡£
.\"O .SH DYNAMICALLY LOADABLE MODULES
.SH ưŪÆɤ߹þ¤ß²Äǽ¥â¥¸¥å¡¼¥ë
.\"O If the agent is built with support for the UCD-DLMOD-MIB it is capable
.\"O of loading agent MIB modules dynamically at startup through
.\"O the \fIdlmod\fR directive and during runtime through use of the UCD-DLMOD-MIB.
.\"O The following directive loads the shared object module file PATH which
.\"O uses the module name prefix NAME.
¥¨¡¼¥¸¥§¥ó¥È¤¬ UCD-DLMOD-MIB ¤Î¥µ¥Ý¡¼¥È¤òÁȤ߹þ¤ó¤Ç¤¤¤ë¾ì¹ç¡¢
¥¨¡¼¥¸¥§¥ó¥È MIB ¥â¥¸¥å¡¼¥ë¤ò
µ¯Æ°»þ¤Ë \fIdlmod\fR ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò»È¤Ã¤ÆưŪ¤Ë¥í¡¼¥É¤·¤¿¤ê¡¢
¼Â¹ÔÃæ¤Ë UCD-DLMOD-MIB ¤ò»È¤Ã¤ÆưŪ¤Ë¥í¡¼¥É¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
°Ê²¼¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥â¥¸¥å¡¼¥ë̾¥×¥ì¥Õ¥£¥Ã¥¯¥¹¤¬ NAME ¤Ç¤¢¤ë
¶¦Í­¥ª¥Ö¥¸¥§¥¯¥È¥â¥¸¥å¡¼¥ë¥Õ¥¡¥¤¥ë PATH ¤ò¥í¡¼¥É¤¹¤ë¡£
.IP "dlmod NAME PATH"
.IP
.\"O .SH ACCESS CONTROL
.SH ¥¢¥¯¥»¥¹À©¸æ
.\"O snmpd supports the View-Based Access Control Model (vacm)
.\"O as defined in RFC 2275.
.\"O To this end, it recognizes the following keywords in the configuration
.\"O file: \fIcom2sec\fR, \fIgroup\fR, \fIaccess\fR, and \fIview\fR as well 
.\"O as some easier-to-use wrapper directives: \fIrocommunity\fR,
.\"O \fIrwcommunity\fR, \fIrouser\fR, \fIrwuser\fR.
snmpd ¤Ï RFC 2275 ¤Çµ¬Äꤵ¤ì¤Æ¤¤¤ë
View-Based Access Control Model (vacm) ¤ò¥µ¥Ý¡¼¥È¤·¤Æ¤¤¤ë¡£
¤³¤Î¤¿¤á¡¢snmpd ¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤Ë¤¢¤ë
\fIcom2sec\fR, \fIgroup\fR, \fIaccess\fR, \fIview\fR 
¤È¤¤¤¦¥­¡¼¥ï¡¼¥É¤òǧ¼±¤¹¤ë¡£
¤Þ¤¿´Êñ¤Ë»ÈÍѤ¹¤ë¤¿¤á¤Î¥é¥Ã¥Ñ¡¼¥Ç¥£¥ì¥¯¥Æ¥£¥Ö
\fIrocommunity\fR, \fIrwcommunity\fR, 
\fIrouser\fR, \fIrwuser\fR ¤âǧ¼±¤¹¤ë¡£
.IP "rocommunity COMMUNITY [SOURCE] [OID]"
.IP "rwcommunity COMMUNITY [SOURCE] [OID]"
.\"O These create read-only and read-write communities that can be used to
.\"O access the agent.  They are a quick method of using the following
.\"O \fIcom2sec\fR, \fIgroup\fR, \fIaccess\fR, and \fIview\fR directive lines.  They are
.\"O not as efficient either, as groups aren't created so the tables are
.\"O possibly larger.  In other words: don't use these if you have complex
.\"O situations to set up.
¤³¤ì¤é¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÏÆɤ߹þ¤ß¤·¤«¤Ç¤­¤Ê¤¤¥³¥ß¥å¥Ë¥Æ¥£¤È
Æɤ߽ñ¤­¤Ç¤­¤ë¥³¥ß¥å¥Ë¥Æ¥£¤òºîÀ®¤·¡¢
¥¨¡¼¥¸¥§¥ó¥È¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤¿¤á¤Ë»ÈÍѤ¹¤ë¡£
¤³¤ì¤é¤Ï°Ê²¼¤Î \fIcom2sec\fR, \fIgroup\fR, 
\fIaccess\fR, \fIview\fR ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¹Ô¤ò´Êñ¤Ë»È¤¦¤¿¤á¤ÎÊýË¡¤Ç¤¢¤ë¡£
¤³¤ì¤é¤Ï¸úΨŪ¤Ç¤Ï¤Ê¤¯¡¢¥°¥ë¡¼¥×¤¬ºîÀ®¤µ¤ì¤Ê¤¤¤¿¤á¤Ë
¥Æ¡¼¥Ö¥ë¤¬´öʬÂ礭¤¯¤Ê¤ë¡£
¸À¤¤´¹¤¨¤ì¤Ð¡¢Ê£»¨¤Ê¾õÂÖ¤òÀßÄꤹ¤ë¾ì¹ç¤Ë¤Ï»ÈÍѤ·¤Æ¤Ï¤Ê¤é¤Ê¤¤¡¢
¤È¤¤¤¦¤³¤È¤Ç¤¢¤ë¡£
.IP
.\"O The format of the SOURCE is token is described in the \fIcom2sec\fR
.\"O directive section below.  The OID token restricts access for that
.\"O community to everything below that given OID.
SOURCE ¤Î¥Õ¥©¡¼¥Þ¥Ã¥È¤Ï¡¢°Ê²¼¤Î \fIcom2sec\fR ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¥»¥¯¥·¥ç¥ó¤Ç
ÀâÌÀ¤µ¤ì¤Æ¤¤¤ë¥È¡¼¥¯¥ó¤ÈƱ¤¸¤Ç¤¢¤ë¡£
OID ¥È¡¼¥¯¥ó¤Ï¡¢¥³¥ß¥å¥Ë¥Æ¥£¤Î¥¢¥¯¥»¥¹¤ò¡¢
»ØÄꤵ¤ì¤¿ OID °Ê²¼¤Î¤â¤Î¤À¤±¤ËÀ©¸Â¤¹¤ë¡£
.IP "rouser USER [noauth|auth|priv] [OID]"
.IP "rwuser USER [noauth|auth|priv] [OID]"
.\"O Creates a SNMPv3 USM user in the VACM access configuration tables.
.\"O Again, its more efficient (and powerful) to use the combined
.\"O \fIcom2sec\fR, \fIgroup\fR, \fIaccess\fR, and \fIview\fR directives instead.
SNMPv3 USM ¥æ¡¼¥¶¡¼¤ò VACM ¥¢¥¯¥»¥¹ÀßÄê¥Æ¡¼¥Ö¥ë¤ËºîÀ®¤¹¤ë¡£
¤³¤ì¤â¤Þ¤¿¡¢\fIcom2sec\fR, \fIgroup\fR, \fIaccess\fR, \fIview\fR 
¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÁȤ߹ç¤ï¤»¤Æ»ÈÍѤ·¤¿Êý¤¬¸úΨŪ (¤«¤Ä¶¯ÎÏ) ¤Ç¤¢¤ë¡£
.IP
.\"O The minimum level of authentication and privacy the user must use is
.\"O specified by the first token (which defaults to "auth").  The OID
.\"O parameter restricts access for that user to everything below the given 
.\"O OID.
¥æ¡¼¥¶¡¼¤¬»ÈÍѤ·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤Ç§¾Ú¤È¥×¥é¥¤¥Ð¥·¡¼¤ÎºÇÄã¥ì¥Ù¥ë¤ò
ºÇ½é¤Î¥È¡¼¥¯¥ó¤Ç»ØÄꤹ¤ë (¥Ç¥Õ¥©¥ë¥È¤Ï "auth" ¤Ç¤¢¤ë)¡£
OID ¥Ñ¥é¥á¡¼¥¿¤Ï¡¢¤½¤Î¥æ¡¼¥¶¡¼¤Î¥¢¥¯¥»¥¹¤ò¡¢
»ØÄꤵ¤ì¤¿ OID °Ê²¼¤Î¤â¤Î¤À¤±¤ËÀ©¸Â¤¹¤ë¡£
.IP "com2sec NAME SOURCE COMMUNITY"
.\"O This directive specifies the mapping from a source/community pair to
.\"O a security name. SOURCE can be a hostname, a subnet, or the word
.\"O \fI"default"\fR.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥½¡¼¥¹ (SOURCE) ¤È¥³¥ß¥å¥Ë¥Æ¥£ (COMMUNITY) ¤Î¥Ú¥¢¤«¤é
¥»¥­¥å¥ê¥Æ¥£Ì¾ (NAME) ¤Ø¤Î¥Þ¥Ã¥Ô¥ó¥°¤ò»ØÄꤹ¤ë¡£
SOURCE ¤Ï¥Û¥¹¥È̾¡¦¥µ¥Ö¥Í¥Ã¥È¡¦\fI"default"\fR ¤Ç¤¢¤ë¡£
.\"O A subnet can be specified as IP/MASK or IP/BITS.
.\"O The first source/community combination that matches the incoming packet
.\"O is selected.
¥µ¥Ö¥Í¥Ã¥È¤Ï IP/MASK ¤Þ¤¿¤Ï IP/BITS ¤Ç»ØÄê¤Ç¤­¤ë¡£
Æþ¤Ã¤Æ¤¯¤ë¥Ñ¥±¥Ã¥È¤Ë¥Þ¥Ã¥Á¤¹¤ë¥½¡¼¥¹¤È¥³¥ß¥å¥Ë¥Æ¥£¤ÎÁȤ߹ç¤ï¤»¤¬ÁªÂò¤µ¤ì¤ë¡£
.IP "group NAME MODEL SECURITY"
.\"O This directive defines the mapping from securitymodel/securityname to group.
.\"O MODEL is one of \fIv1\fR, \fIv2c\fR, or \fIusm\fR.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥»¥­¥å¥ê¥Æ¥£¥â¥Ç¥ë (MODEL) ¤È
¥»¥­¥å¥ê¥Æ¥£Ì¾ (SECURITY) ¤Î¥Ú¥¢¤«¤é
¥°¥ë¡¼¥×̾ (NAME) ¤Ø¤Î¥Þ¥Ã¥Ô¥ó¥°¤òÄêµÁ¤¹¤ë¡£
MODEL ¤Ï \fIv1\fR, \fIv2c\fR, \fIusm\fR ¤Î¤¤¤º¤ì¤« 1 ¤Ä¤Ç¤¢¤ë¡£
.IP "access NAME CONTEXT MODEL LEVEL PREFX READ WRITE NOTIFY"
.\"O The access directive maps from group/security model/security level to
.\"O a view. 
.\"O MODEL is one of \fIany\fR, \fIv1\fR, \fIv2c\fR, or \fIusm\fR.
.\"O LEVEL is one of \fInoauth\fR, \fIauth\fR, or \fIpriv\fR.
access ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¥°¥ë¡¼¥×¥»¥­¥å¥ê¥Æ¥£¤È
¥â¥Ç¥ë¥»¥­¥å¥ê¥Æ¥£¤Î¥ì¥Ù¥ë¤ò¡¢¤¢¤ë¥Ó¥å¡¼ (view) ¤Ë¥Þ¥Ã¥×¤¹¤ë¡£
MODEL ¤Ï \fIany\fR, \fIv1\fR, \fIv2c\fR, \fIusm\fR ¤Î¤¤¤º¤ì¤« 1 ¤Ä¤Ç¤¢¤ë¡£
LEVEL ¤Ï \fInoauth\fR, \fIauth\fR, \fIpriv\fR ¤Î¤¤¤º¤ì¤« 1 ¤Ä¤Ç¤¢¤ë¡£
.\"O PREFX specifies how CONTEXT should be matched against the context of
.\"O the incoming pdu, either \fIexact\fR or \fIprefix\fR.
.\"O READ, WRITE and NOTIFY specifies the view to be used for the corresponding 
.\"O access.
.\"O For v1 or v2c access, LEVEL will be noauth, and CONTEXT will be empty.
PREFX ¤ÏÆþ¤Ã¤Æ¤¯¤ë pdu ¤ÎÆâÍƤËÂФ¹¤ë
CONTEXT ¤Î¥Þ¥Ã¥Á¤ÎÊýË¡¤ò»ØÄꤹ¤ë¤â¤Î¤Ç¡¢
\fIexact\fR ¤Þ¤¿¤Ï \fIprefix\fR ¤Ç¤¢¤ë¡£
READ, WRITE, NOTIFY ¤Ï¥Ó¥å¡¼¤ËÂбþ¤¹¤ë¥¢¥¯¥»¥¹ÊýË¡¤ò»ØÄꤹ¤ë¤Î¤Ë»È¤ï¤ì¤ë¡£
v1 ¤Þ¤¿¤Ï v2c ¤Î¥¢¥¯¥»¥¹¤Ç¤Ï¡¢LEVEL ¤Ï noauth¡¢
CONTEXT ¤Ï¶õʸ»úÎó¤Ç¤¢¤ë¡£
.IP "view NAME TYPE SUBTREE [MASK]"
.\"O The defines the named view. TYPE is either \fIincluded\fR or \fIexcluded\fR.
.\"O MASK is a list of hex octets, separated by '.' or ':'.  The MASK
.\"O defaults to "ff" if not specified.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï»ØÄꤷ¤¿Ì¾Á°¤Î¥Ó¥å¡¼ (view) ¤òÄêµÁ¤¹¤ë¡£
TYPE ¤Ï \fIincluded\fR ¤Þ¤¿¤Ï \fIexcluded\fR ¤Ç¤¢¤ë¡£
MASK ¤Ï 16 ¿Ê¿ô¤Çɽ¤·¤¿ 8 ¥Ó¥Ã¥È¤ò
\&'.' ¤Þ¤¿¤Ï ':' ¤Ç¶èÀڤäƥꥹ¥È¤Ë¤·¤¿¤â¤Î¤Ç¤¢¤ë¡£
MASK ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¤Î¥Ç¥Õ¥©¥ë¥È¤Ï "ff" ¤Ç¤¢¤ë¡£
.IP
.\"O The reason for the mask is, that it allows you to control access to
.\"O one row in a table, in a relatively simple way. As an example, as an ISP
.\"O you might consider giving each customer access to his or her own interface:
¥Þ¥¹¥¯¤ò»ÈÍѤ¹¤ëÍýͳ¤Ï¡¢Èæ³ÓŪ´Êñ¤Ë
¥Æ¡¼¥Ö¥ë¤Î 1 ¤Ä¤Î¹Ô (row) ¤Ø¤Î¥¢¥¯¥»¥¹¤òÀ©¸æ¤¹¤ë¤³¤È¤Ë¤¢¤ë¡£
Î㤨¤Ð¡¢ISP ¤Ç¤Ï¤½¤ì¤¾¤ì¤Î¸ÜµÒ¤ËÂФ·¤Æ
¸ÜµÒ¤´¤È¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë¥¢¥¯¥»¥¹¤µ¤»¤¿¤¤¤È¹Í¤¨¤ë¤«¤â¤·¤ì¤Ê¤¤:
.IP
.nf
view cust1 included interfaces.ifTable.ifEntry.ifIndex.1 ff.a0
view cust2 included interfaces.ifTable.ifEntry.ifIndex.2 ff.a0
.IP
.\"O (interfaces.ifTable.ifEntry.ifIndex.1 == .1.3.6.1.2.1.2.2.1.1.1,
.\"O ff.a0 == 11111111.10100000. which nicely covers up and including
.\"O the row index, but lets the user vary the field of the row)
(interfaces.ifTable.ifEntry.ifIndex.1 == .1.3.6.1.2.1.2.2.1.1.1 ¤Ç
ff.a0 == 11111111.10100000 ¤Ç¤¢¤ë¡£
¤³¤ì¤Ï¹Ô¥¤¥ó¥Ç¥Ã¥¯¥¹¤ò¤¦¤Þ¤¤¶ñ¹ç¤¤¤Ë¥«¥Ð¡¼¤·¤Æ´Þ¤ó¤Ç¤¤¤ë¤¬¡¢
¹Ô¥Õ¥£¡¼¥ë¥É¤ÎÊѹ¹¤ò¥æ¡¼¥¶¡¼¤Ëµö²Ä¤·¤Æ¤¤¤ë¡£)
.\"O .IP "VACM Examples:"
.IP "VACM ¤ÎÎã:"
.nf
#       sec.name  source          community
com2sec local     localhost       private
com2sec mynet     10.10.10.0/24   public
com2sec public    default         public

#             sec.model  sec.name
group mygroup v1         mynet
group mygroup v2c        mynet
group mygroup usm        mynet
group local   v1         local
group local   v2c        local
group local   usm        local
group public  v1         public
group public  v2c        public
group public  usm        public

#           incl/excl subtree                          mask
view all    included  .1                               80
view system included  system                           fe
view mib2   included  .iso.org.dod.internet.mgmt.mib-2 fc

#              context sec.model sec.level prefix read   write notify
access mygroup ""      any       noauth    exact  mib2   none  none
access public  ""      any       noauth    exact  system none  none
access local   ""      any       noauth    exact  all    all   all
.\"O .IP "Default VACM model"
.IP "¥Ç¥Õ¥©¥ë¥È¤Î VACM ¥â¥Ç¥ë"
.\"O The default configuration of the agent, as shipped, is functionally
.\"O equivalent to the following entries:
ºÇ½é¤Î¾õÂ֤ǤΥ¨¡¼¥¸¥§¥ó¥È¤Î¥Ç¥Õ¥©¥ë¥È¤ÎÀßÄê¤Ï¡¢
µ¡Ç½Åª¤Ë¤Ï°Ê²¼¤Î¥¨¥ó¥È¥ê¤ÈÅù²Á¤Ç¤¢¤ë:
.nf
com2sec public  default public
group   public  v1      public
group   public  v2c     public
group   public  usm     public
view    all     included        .1
access  public  ""      any     noauth  exact   all     none    none
.\"O .SH SNMPv3 CONFIGURATION
.SH SNMPv3 ÀßÄê
.PP
.IP "engineID STRING"
.\"O The snmpd agent needs to be configured with an engineID to be able to
.\"O respond to SNMPv3 messages.  With this configuration file line, the
.\"O engineID will be configured from STRING.  The default value of the
.\"O engineID is configured with the first IP address found for the
.\"O hostname of the machine.
snmpd ¥¨¡¼¥¸¥§¥ó¥È¤¬ SNMPv3 ¥á¥Ã¥»¡¼¥¸¤Ë±þÅú¤¹¤ë¤¿¤á¤Ë¤Ï
engineID ¤òÀßÄꤹ¤ëɬÍפ¬¤¢¤ë¡£
ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¤³¤Î¹Ô¤¬¤¢¤ì¤Ð¡¢STRING ¤«¤é engineID ¤òÀßÄꤹ¤ë¡£
engineID ¤Î¥Ç¥Õ¥©¥ë¥ÈÃͤϡ¢¥Þ¥·¥ó¤Î¥Û¥¹¥È̾¤ËÂФ·¤Æ¸«¤Ä¤«¤ë
ºÇ½é¤Î IP ¥¢¥É¥ì¥¹¤ËÀßÄꤵ¤ì¤ë¡£
.IP "createUser username (MD5|SHA) authpassphrase [DES] [privpassphrase]"
.\"O This directive should be placed into the
.\"O "/var/ucd-snmp"/snmpd.conf file instead of the other normal
.\"O locations.  The reason is that the information is read from the file
.\"O and then the line is removed (eliminating the storage of the master
.\"O password for that user) and replaced with the key that is derived from 
.\"O it.  This key is a localized key, so that if it is stolen it can not
.\"O be used to access other agents.  If the password is stolen, however,
.\"O it can be.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢Â¾¤Î¾ì½ê¤Ë¤¢¤ëÄ̾ï¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤Ç¤Ï¤Ê¤¯¡¢
"/var/ucd-snmp"/snmpd.conf ¥Õ¥¡¥¤¥ë¤Ë½ñ¤¯¤Ù¤­¤Ç¤¢¤ë¡£
¤½¤ÎÍýͳ¤Ï¡¢¾ðÊ󤬤³¤Î¥Õ¥¡¥¤¥ë¤«¤éÆɤ߹þ¤Þ¤ì¤¿¸å¡¢
¤³¤Î¹Ô¤¬ºï½ü¤µ¤ì (¥æ¡¼¥¶¡¼¤Î¥Þ¥¹¥¿¡¼¥Ñ¥¹¥ï¡¼¥É¤Î³ÊǼ¾ì½ê¤«¤é¾Ãµî¤µ¤ì¤Æ)¡¢
¤³¤Î¹Ô¤«¤éÆÀ¤é¤ì¤ë¥­¡¼¤ËÃÖ¤­´¹¤¨¤é¤ì¤ë¤¿¤á¤Ç¤¢¤ë¡£
¤³¤Î¥­¡¼¤Ï¥í¡¼¥«¥ë¤Ê¥­¡¼¤Ç¤¢¤ê¡¢
Åð¤Þ¤ì¤¿¤È¤·¤Æ¤â¾¤Î¥¨¡¼¥¸¥§¥ó¥È¤Ë¥¢¥¯¥»¥¹¤¹¤ë¤Î¤Ë¤Ï»È¤¨¤Ê¤¤¡£
¤·¤«¤·¥Ñ¥¹¥ï¡¼¥É¤¬Åð¤Þ¤ì¤¿¾ì¹ç¤Ï¡¢Â¾¤Î¥¨¡¼¥¸¥§¥ó¥È¤Ë¥¢¥¯¥»¥¹¤Ç¤­¤ë¡£
.IP
.\"O MD5 and SHA are the authentication types to use, but you must have
.\"O built the package with openssl installed in order to use SHA.  The
.\"O only privacy protocol currently supported is DES.  If the privacy
.\"O passphrase is not specified, it is assumed to be the same as the
.\"O authentication passphrase.  Note that the users created will be
.\"O useless unless they are also added to the VACM access control tables
.\"O described above.
MD5 ¤È SHA ¤Ï»ÈÍѤµ¤ì¤ëǧ¾Ú¥¿¥¤¥×¤Ç¤¢¤ë¤¬¡¢
SHA ¤ò»ÈÍѤ¹¤ë¤¿¤á¤Ë¤Ï¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë openssl ¤ò»È¤Ã¤Æ
¥Ñ¥Ã¥±¡¼¥¸¤òºîÀ®¤·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
¸½ºß¤Î¤È¤³¤í¥×¥é¥¤¥Ð¥·¡¼¥×¥í¥È¥³¥ë¤¬¥µ¥Ý¡¼¥È¤µ¤ì¤Æ¤¤¤ë¤Î¤Ï DES ¤Î¤ß¤Ç¤¢¤ë¡£
¥×¥é¥¤¥Ð¥·¡¼¥Ñ¥¹¥Õ¥ì¡¼¥º¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
ǧ¾Ú¥Ñ¥¹¥Õ¥ì¡¼¥º¤ÈƱ¤¸¤Ç¤¢¤ë¤È²¾Äꤵ¤ì¤ë¡£
¾å¤ÇÀâÌÀ¤·¤¿ VACM ¥¢¥¯¥»¥¹À©¸æ¥Æ¡¼¥Ö¥ë¤ËÆþ¤ì¤Ê¤±¤ì¤Ð¡¢
ºîÀ®¤·¤¿¥æ¡¼¥¶¡¼¤Î»È¤¤Æ»¤¬¤Ê¤¤ÅÀ¤ËÃí°Õ¤¹¤ë¤³¤È¡£
.IP
.\"O Warning: the minimum pass phrase length is 8 characters.
·Ù¹ð: ¥Ñ¥¹¥Õ¥ì¡¼¥º¤Ï¾¯¤Ê¤¯¤È¤â 8 ʸ»ú¤Ç¤¢¤ë¡£
.IP
.\"O SNMPv3 users can be created at runtime using the
.\"O .I snmpusm
.\"O command.
.I snmpusm
¥³¥Þ¥ó¥É¤òÍѤ¤¤ì¤Ð¡¢¼Â¹ÔÃæ¤Ë SNMPv3 ¥æ¡¼¥¶¡¼¤òºîÀ®¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
.IP
.\"O .SH SETTING SYSTEM INFORMATION
.SH ¥·¥¹¥Æ¥à¾ðÊó¤ÎÀßÄê
.IP "syslocation STRING"
.IP "syscontact STRING"
.IP "sysname STRING"
.\"O Sets the system location, system contact or system name for the agent.
.\"O This information is reported in the 'system' group the mibII tree.
¥¨¡¼¥¸¥§¥ó¥È¤¬ÃÖ¤«¤ì¤Æ¤¤¤ë¥·¥¹¥Æ¥à¤Î¾ì½ê (location)¡¦
Ï¢ÍíÀè (contact)¡¦Ì¾Á° (name) ¤òÀßÄꤹ¤ë¡£
¤³¤Î¾ðÊó¤Ï mibII ¥Ä¥ê¡¼¤Î 'system' ¥°¥ë¡¼¥×¤ËÀßÄꤵ¤ì¤ë¡£
.\"O Ordinarily these objects (sysLocation.0, sysContact.0 and sysName.0)
.\"O are read-write.  However, specifying the value for one of these
.\"O objects by giving the appropriate token makes the corresponding object
.\"O read-only, and attempts to set the value of the object will result in
.\"O a notWritable error response.
Ä̾¤³¤ì¤é¤Î¥ª¥Ö¥¸¥§¥¯¥È (sysLocation.0, sysContact.0 and sysName.0) ¤Ï
Æɤ߽ñ¤­²Äǽ¤Ç¤¢¤ë¡£
¤¿¤À¤·¡¢¤³¤ì¤é¤Î¥ª¥Ö¥¸¥§¥¯¥È¤ÎÃͤËŬÀڤʥȡ¼¥¯¥ó¤òÉղ䷤ƻØÄꤹ¤ì¤Ð¡¢
¤½¤Î¥ª¥Ö¥¸¥§¥¯¥È¤òÆɤ߹þ¤ß¤Î¤ß¤Ë¤¹¤ë¤³¤È¤¬¤Ç¤­¡¢
¥ª¥Ö¥¸¥§¥¯¥È¤ÎÃͤòÀßÄꤷ¤è¤¦¤È¤·¤¿¤È¤­¤Ë
notWritable ¥¨¥é¡¼¥ì¥¹¥Ý¥ó¥¹¤òÊÖ¤¹¤è¤¦¤Ë¤Ç¤­¤ë¡£
.IP "sysservices NUMBER"
.\"O Sets the value of the system.sysServices.0 object.
.\"O For a host, a good value is 72.
system.sysServices.0 ¥ª¥Ö¥¸¥§¥¯¥È¤ÎÃͤòÀßÄꤹ¤ë¡£
¥Û¥¹¥È¤Î¾ì¹ç¤Ï¡¢72 ¤¬¤è¤¤¡£
.IP "agentaddress [(udp|tcp):]port[@address][,...]"
.\"O Makes the agent list on the specified list of sockets instead of the
.\"O default port, which is port 161.  Multiple ports can be separated by
.\"O commas.  Transports can be specified by prepending the port number
.\"O with the transport name ("udp" or "tcp") followed by a colon.
.\"O Finally, to bind to a particular interface, you can specify the
.\"O address you want it to bind with.
¥Ç¥Õ¥©¥ë¥È¤Î 161 È֥ݡ¼¥È¤Ç¤Ï¤Ê¤¯¡¢
»ØÄꤷ¤¿¥½¥±¥Ã¥È¤Î¥ê¥¹¥È¤Ç¥¨¡¼¥¸¥§¥ó¥È¤Î¥ê¥¹¥È¤òºîÀ®¤¹¤ë¡£
Ê£¿ô¤Î¥Ý¡¼¥È¤ò¥³¥ó¥Þ¤Ç¶èÀڤäƻØÄê¤Ç¤­¤ë¡£
¥È¥é¥ó¥¹¥Ý¡¼¥È̾ ("udp" ¤Þ¤¿¤Ï "tcp")¡¦¥³¥í¥ó¡¦¥Ý¡¼¥È̾¤Î¤è¤¦¤Ë¤·¤Æ¡¢
¥È¥é¥ó¥¹¥Ý¡¼¥È̾¤ò»ØÄê¤Ç¤­¤ë¡£
ÆÃÄê¤Î¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Ë¥Ð¥¤¥ó¥É¤¹¤ë¤¿¤á¤Ë¡¢
¥¢¥É¥ì¥¹¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
.\"O For example, specifying
.\"O .I "agentaddress 161,tcp:161,9161@localhost"
.\"O will make the agent listen on: udp port 161 for any address, tcp port
.\"O 161 for any address, and udp port 9161 on only the interface
.\"O associated with the localhost address.  Note that the 
.\"O .I "-T"
.\"O flag changes the default transport mapping to use (in the
.\"O above example, the default transport mapping is 
.\"O .I udp.
Î㤨¤Ð
.I "agentaddress 161,tcp:161,9161@localhost"
¤Î¤è¤¦¤Ë»ØÄꤹ¤ì¤Ð¡¢¥¨¡¼¥¸¥§¥ó¥È¤ËÂФ·¤Æ¡¢
Á´¤Æ¤Î¥¢¥É¥ì¥¹¤Î udp ¥Ý¡¼¥È 161¡¦Á´¤Æ¤Î¥¢¥É¥ì¥¹¤Î tcp ¥Ý¡¼¥È 161¡¦
localhost ¤Î¥¢¥É¥ì¥¹¤Ë´ØÏ¢¤Å¤±¤é¤ì¤¿
¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤Î udp ¥Ý¡¼¥È 9161 ¤ò´Æ»ë (listen) ¤µ¤»¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
.I "-T"
¥Õ¥é¥°¤òÍѤ¤¤ì¤Ð¡¢
»ÈÍѤ¹¤ë¥Ç¥Õ¥©¥ë¥È¤Î¥È¥é¥ó¥¹¥Ý¡¼¥È¥Þ¥Ã¥Ô¥ó¥°¤òÊѹ¹¤¹¤ë¤³¤È¤¬¤Ç¤­¤ë
(¾åµ­¤ÎÎã¤Ç¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Î¥È¥é¥ó¥¹¥Ý¡¼¥È¥Þ¥Ã¥Ô¥ó¥°¤Ï
.I udp
¤Ç¤¢¤ë)¡£
.IP "agentgroup groupid"
.\"O Change to this gid after opening port. The groupid may refer to a group
.\"O by name or a number if the group number starts with '#'. For example,
.\"O specifying
.\"O .I agentgroup snmp
.\"O will cause the agent to run as the snmp group or
.\"O .I agentgroup #10
.\"O will cause the agent to run as the group with groupid 10.
¥Ý¡¼¥È¤ò¥ª¡¼¥×¥ó¤·¤¿¸å¤Ç¡¢¥°¥ë¡¼¥× ID ¤ò»ØÄꤷ¤¿ÃͤËÊѹ¹¤¹¤ë¡£
groupid ¤Ï¥°¥ë¡¼¥×̾¤Þ¤¿¤Ï¥°¥ë¡¼¥×ÈÖ¹æ¤Ç¤¢¤ë¡£
¥°¥ë¡¼¥×ÈÖ¹æ¤Î¾ì¹ç¤Ï '#' ¤Ç»Ï¤á¤ë¡£
Î㤨¤Ð
.I agentgroup snmp
¤Î¾ì¹ç¤Ï¡¢¥¨¡¼¥¸¥§¥ó¥È¤ò snmp ¥°¥ë¡¼¥×¤ÇÆ°ºî¤µ¤»¤ë¡£
.I agentgroup #10
¤Î¾ì¹ç¤Ï¡¢¥¨¡¼¥¸¥§¥ó¥È¤ò¥°¥ë¡¼¥× ID 10 ÈÖ¤ÇÆ°ºî¤µ¤»¤ë¡£
.IP "agentuser uid"
.\"O Change to this uid after opening port. The userid may refer to a user
.\"O by name or a number if the user number starts with '#'. For example,
.\"O specifying
.\"O .I agentuser snmp
.\"O will cause the agent to run as the snmp user or
.\"O .I agentuser #10
.\"O will cause the agent to run as the user with userid 10.
¥Ý¡¼¥È¤ò¥ª¡¼¥×¥ó¤·¤¿¸å¤Ç¡¢¥æ¡¼¥¶¡¼ ID ¤ò»ØÄꤷ¤¿ÃͤËÊѹ¹¤¹¤ë¡£
userid ¤Ï¥æ¡¼¥¶¡¼Ì¾¤Þ¤¿¤Ï¥æ¡¼¥¶¡¼ÈÖ¹æ¤Ç¤¢¤ë¡£
¥æ¡¼¥¶¡¼ÈÖ¹æ¤Î¾ì¹ç¤Ï '#' ¤Ç»Ï¤á¤ë¡£
Î㤨¤Ð
.I agentuser snmp
¤Î¾ì¹ç¤Ï¡¢¥¨¡¼¥¸¥§¥ó¥È¤ò¥æ¡¼¥¶¡¼ snmp ¤ÇÆ°ºî¤µ¤»¤ë¡£
.I agentuser #10
¤Î¾ì¹ç¤Ï¡¢¥¨¡¼¥¸¥§¥ó¥È¤ò¥æ¡¼¥¶¡¼ ID 10 ÈÖ¤ÇÆ°ºî¤µ¤»¤ë¡£
.IP "interface NAME TYPE SPEED"
.\"O For interfaces where the agent fails to guess correctly on the type and
.\"O speed, this directive can supply additional information.
.\"O TYPE is a type value as given in the IANAifType-MIB.
¥¨¡¼¥¸¥§¥ó¥È¤¬¥¿¥¤¥×¤ä¥¹¥Ô¡¼¥É¤Î¿ä¬¤Ë¼ºÇÔ¤·¤¿¥¤¥ó¥¿¥Õ¥§¡¼¥¹¤ËÂФ·¤Æ¡¢
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ÇÄɲäξðÊó¤òÄ󶡤¹¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
TYPE ¤Ï IANAifType-MIB ¤Ç»ØÄꤵ¤ì¤ë¥¿¥¤¥×¤Ç¤¢¤ë¡£
.IP "ignoredisk STRING"
.\"O When scanning for available disk devices the agent might block in trying
.\"O to open all possible disk devices. This might lead to a timeout when
.\"O walking the device tree. Sometimes the next walk will run without timeout,
.\"O sometimes it will timeout every time you try it.
»ÈÍѲÄǽ¤Ê¥Ç¥£¥¹¥¯¥Ç¥Ð¥¤¥¹¤ò¥¹¥­¥ã¥ó¤¹¤ë¾ì¹ç¡¢
¥¨¡¼¥¸¥§¥ó¥È¤Ï»ÈÍѲÄǽ¤Ê¥Ç¥£¥¹¥¯¥Ç¥Ð¥¤¥¹¤ò¥ª¡¼¥×¥ó¤¹¤ë¤È¤­¤Ë
¥Ö¥í¥Ã¥¯¤ò¹Ô¤¦¤³¤È¤¬¤¢¤ë¡£
¤³¤ì¤Ë¤è¤Ã¤Æ¥Ç¥Ð¥¤¥¹¥Ä¥ê¡¼¤òé¤Ã¤Æ¤¤¤ë¤È¤­¤Ë¥¿¥¤¥à¥¢¥¦¥È¤¬µ¯¤ë¤«¤â¤·¤ì¤Ê¤¤¡£
¼¡¤Ëé¤Ã¤¿¤È¤­¤Ë¥¿¥¤¥à¥¢¥¦¥È¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Ê¤¤¤·¡¢
Ëè²ó¥¿¥¤¥à¥¢¥¦¥È¤Ë¤Ê¤ë¤«¤â¤·¤ì¤Ê¤¤¡£
.IP
.\"O If you experience such behaviour you might add this directive and give all
.\"O device names not to be checked (i.e. opened). You might have more than one
.\"O such directive in your configuration file stating all devices not to be
.\"O opened. You might also specify those devices using wildcards similar to
.\"O the syntax you can use in a bourne shell (see examples below).
¤³¤Î¤è¤¦¤Ê¸½¾Ý¤¬µ¯¤Ã¤¿¾ì¹ç¤Ï¡¢¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤òÄɲä·¡¢
¥Á¥§¥Ã¥¯¤·¤Ê¤¤ (¤Ä¤Þ¤ê¥ª¡¼¥×¥ó¤·¤Ê¤¤) Á´¤Æ¤Î¥Ç¥Ð¥¤¥¹¤ò»ØÄꤹ¤ë¡£
ÀßÄê¥Õ¥¡¥¤¥ë¤Ë¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤ò 1 ¤Ä°Ê¾å¤Î»ØÄꤷ¤Æ¡¢
¥ª¡¼¥×¥ó¤·¤Ê¤¤Á´¤Æ¤Î¥Ç¥Ð¥¤¥¹¤ò½ñ¤­¹þ¤à¡£
bourne ¥·¥§¥ë¤Îʸˡ¤Î»÷¤¿¥ï¥¤¥ë¥É¥«¡¼¥É¤ò»È¤Ã¤Æ¡¢
¥Ç¥Ð¥¤¥¹¤ò»ØÄꤹ¤ë¤³¤È¤â¤Ç¤­¤ë (²¼µ­¤ÎÎã¤ò»²¾È¤¹¤ë¤³¤È)¡£
.IP
.\"O .B Note:
.B Ãí°Õ:
.\"O For a list of devices scanned for every system please consult the sources
.\"O (host/hr_disk.c) and check for the Add_HR_Disk_entry() calls relevant for
.\"O your type of OS.
Á´¤Æ¤Î¥·¥¹¥Æ¥à¤Ç¥¹¥­¥ã¥ó¤µ¤ì¤ë¥Ç¥Ð¥¤¥¹¤Î¥ê¥¹¥È¤Ï¡¢
¥½¡¼¥¹ (host/hr_disk.c) ¤ò¸«¤Æ¡¢
OS ¥¿¥¤¥×¤ËÂбþ¤·¤¿ Add_HR_Disk_entry() ¥³¡¼¥ë¤ò¥Á¥§¥Ã¥¯¤¹¤ë¤³¤È¡£
.IP
.\"O Examples:
Îã:
.IP
ignoredisk /dev/rdsk/c0t2d0
.IP
.\"O This directive prevents the device /dev/rdsk/c0t2d0 from being scanned.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢
¥Ç¥Ð¥¤¥¹ /dev/rdsk/c0t2d0 ¤ò¥¹¥­¥ã¥ó¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¡£
.IP
ignoredisk /dev/rdsk/c0t[!6]d0
.IP
.\"O This directive prevents all devices /dev/rdsk/c0tXd0 except .../c0t6d0
.\"O from being scanned. For most systems similar is the following directive:
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï /dev/rdsk/c0t6d0 ¤ò½ü¤¯ /dev/rdsk/c0tXd0 ¤Î
Á´¤Æ¤Î¥Ç¥Ð¥¤¥¹¤ò¥¹¥­¥ã¥ó¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¡£ 
¿¤¯¤Î¥·¥¹¥Æ¥à¤ÇƱÍͤʥǥ£¥ì¥¯¥Æ¥£¥Ö¤È¤·¤Æ¤Ï°Ê²¼¤Î¤â¤Î¤¬¤¢¤ë:
.IP
ignoredisk /dev/rdsk/c0t[0-57-9a-f]d0
.IP
ignoredisk /dev/rdsk/c1*
.IP
.\"O This directive prevents all devices whose device names start with /dev/rdsk/c1
.\"O from being scanned.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢/dev/rdsk/c1 ¤Ç»Ï¤Þ¤ë̾Á°¤Î¥Ç¥Ð¥¤¥¹¤ò
Á´¤Æ¥¹¥­¥ã¥ó¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¡£
.IP
ignoredisk /dev/rdsk/c?t0d0
.IP
.\"O This directive prevents all devices /dev/rdsk/cXt0d0 ('X' might be any char)
.\"O from being scanned.
¤³¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ï¡¢¥Ç¥Ð¥¤¥¹ /dev/rdsk/cXt0d0 ('X' ¤ÏǤ°Õ¤Îʸ»ú) ¤ò
Á´¤Æ¥¹¥­¥ã¥ó¤µ¤»¤Ê¤¤¤è¤¦¤Ë¤¹¤ë¡£
.IP
.\"O You might use more than one such wildcard expression in any such directive.
¤É¤Î¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ë¤ª¤¤¤Æ¤â¡¢
¤³¤Î¤è¤¦¤Ê¥ï¥¤¥ë¥É¥«¡¼¥Éɽ¸½¤ò 2 ¤Ä°Ê¾å»È¤¦¤³¤È¤Ç¤­¤ë¡£
.IP "authtrapenable NUMBER"
.\"O Setting authtrapenable to 1 enables generation of authentication failure
.\"O traps.  The default value is disabled(2).  Ordinarily the corresponding
.\"O object (snmpEnableAuthenTraps.0) is read-write, but setting its value
.\"O via this token makes the object read-only, and attempts to set the
.\"O value of the object will result in a notWritable error response.
authtrapenable ¤ò 1 ¤ËÀßÄꤹ¤ë¤È¡¢
ǧ¾Ú¤Î¼ºÇÔ¤¬µ¯¤Ã¤¿¾ì¹ç¤Ë¥È¥é¥Ã¥×¤òÀ¸À®¤¹¤ë¡£
¥Ç¥Õ¥©¥ë¥È¤ÎÃÍ¤Ï disabled(2) ¤Ç¤¢¤ë¡£
Ä̾盧¤ì¤ËÂбþ¤¹¤ë¥ª¥Ö¥¸¥§¥¯¥È
(snmpEnableAuthenTraps.0) ¤ÏÆɤ߽ñ¤­²Äǽ¤Ç¤¢¤ë¤¬¡¢
¤³¤Î¥È¡¼¥¯¥ó¤ò»È¤Ã¤ÆÃͤòÀßÄꤹ¤ë¤ÈÆɤ߹þ¤ß¤À¤±¤Ë¤Ê¤ê¡¢
¥ª¥Ö¥¸¥§¥¯¥È¤ÎÃͤòÀßÄꤷ¤è¤¦¤È¤·¤¿¾ì¹ç¤Ë¤Ï
notWritable ¥¨¥é¡¼¥ì¥¹¥Ý¥ó¥¹¤òÊÖ¤¹¡£
.IP "trapcommunity STRING"
.\"O This defines the default community string to be used when sending traps.
.\"O Note that this command must be used prior to any of the following three
.\"O commands that are intended use this community string.
¤³¤Î¥³¥Þ¥ó¥É¤Ï¥È¥é¥Ã¥×¤òÁ÷¤ë¤È¤­¤Ë»È¤¦
¥Ç¥Õ¥©¥ë¥È¤Î¥³¥ß¥å¥Ë¥Æ¥£Ê¸»úÎó¤òÄêµÁ¤¹¤ë¡£
¤³¤Î¥³¥Þ¥ó¥É¤Ï¥³¥ß¥å¥Ë¥Æ¥£Ê¸»úÎó¤ò»È¤¦°Ê²¼¤Î 3 ¤Ä¤Î¥³¥Þ¥ó¥É¤è¤ê
Á°¤Ë»ÈÍѤ·¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤ÅÀ¤ËÃí°Õ¤¹¤ë¤³¤È¡£
.IP "trapsink HOST [COMMUNITY [PORT]]"
.IP "trap2sink HOST [COMMUNITY [PORT]]"
.IP "informsink HOST [COMMUNITY [PORT]]"
.\"O These commands define
.\"O the hosts to receive traps (and/or inform notifications). The
.\"O daemon sends a Cold Start trap when it starts up. If enabled, it also sends
.\"O traps on authentication failures.  Multiple \fItrapsink\fR, \fItrap2sink\fR
.\"O and \fIinformsink\fR lines may be specified to specify multiple destinations.
¤³¤ì¤é¤Î¥³¥Þ¥ó¥É¤Ï¥È¥é¥Ã¥×¤ò¼õ¿®¤¹¤ë (ÄÌÃΤòÁ÷¤ëÀè¤Î) ¥Û¥¹¥È¤òÄêµÁ¤¹¤ë¡£
¤³¤Î¥Ç¡¼¥â¥ó¤Ïµ¯Æ°»þ¤Ë Cold Start ¥È¥é¥Ã¥×¤òÁ÷¤ë¡£
Í­¸ú¤Ë¤Ê¤Ã¤Æ¤¤¤ë¾ì¹ç¤Ï¡¢Ç§¾Ú¤¬¼ºÇÔ¤·¤¿¤È¤­¤Ë¤â¥È¥é¥Ã¥×¤òÁ÷¤ë¡£
\fItrapsink\fR, \fItrap2sink\fR, \fIinformsink\fR ¹Ô¤òÊ£¿ô»ØÄꤹ¤ì¤Ð¡¢
Ê£¿ô¤ÎÁ÷¿®Àè¤ò»ØÄꤹ¤ë¤³¤È¤¬¤Ç¤­¤ë¡£
.\"O Use \fItrap2sink\fR to send SNMPv2 traps and \fIinformsink\fR to send
.\"O inform notifications.
.\"O If COMMUNITY is not specified, the string from a preceding \fItrapcommunity\fR
.\"O directive will be used. If PORT is not specified, the well known SNMP trap
.\"O port (162) will be used.
\fItrap2sink\fR ¤Ï SNMPv2 ¥È¥é¥Ã¥×¤òÁ÷¤ë¤Î¤Ë»È¤¦¡£
\fIinformsink\fR ¤ÏÄÌÃΤòȯ¹Ô¤¹¤ë¤Î¤Ë»È¤¦¡£
COMMUNITY ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
°ÊÁ°¤Ë \fItrapcommunity\fR ¥Ç¥£¥ì¥¯¥Æ¥£¥Ö¤Ç»ØÄꤷ¤¿Ê¸»úÎ󤬻Ȥï¤ì¤ë¡£
PORT ¤¬»ØÄꤵ¤ì¤Æ¤¤¤Ê¤¤¾ì¹ç¡¢
Îɤ¯ÃΤé¤ì¤Æ¤¤¤ë SNMP ¥È¥é¥Ã¥×¥Ý¡¼¥È (162) ¤¬»È¤ï¤ì¤ë¡£
.IP "trapsess [SNMPCMD_ARGS] HOST [COMMUNITY]"
.\"O This is a more generic trap configuration token that allows any type
.\"O of trap destination to be specified with any version of SNMP.  See the 
.\"O .I snmpcmd(1)
.\"O manual page for further details on the arguments that can be passed as
.\"O .I "SNMPCMD ARGS".
¤³¤ì¤Ï¤è¤ê´ðËÜŪ¤Ê¥È¥é¥Ã¥×ÀßÄê¥È¡¼¥¯¥ó¤Ç¡¢
Ǥ°Õ¤Î¥È¥é¥Ã¥×Á÷¿®À西¥¤¥×¤ÈǤ°Õ¤Î SNMP ¥Ð¡¼¥¸¥ç¥ó¤ò»ØÄê¤Ç¤­¤ë¡£
.I "SNMPCMD ARGS"
¤È¤·¤ÆÅϤµ¤ì¤ë°ú¤­¿ô¤Î¤è¤ê¾Ü¤·¤¤¾ðÊó¤Ï¡¢
.I snmpcmd(1)
¤Î man ¥Ú¡¼¥¸¤ò»²¾È¤¹¤ë¤³¤È¡£
.\"O In addition to the arguments listed there, the special argument
.\"O \fI-Ci\fR specifies that you want inform notifications to be used
.\"O instead of unacknowledged traps (this requires that you also specify a 
.\"O version number of v2c or v3 as well).
.\"Osato: 
.\"Osato: that you want ... to be used ¤ÎÌõ¤¬¼«¿®¤Ê¤·¡£
.\"Osato: 
¤³¤³¤Çµó¤²¤¿°ú¤­¿ô¤Ë²Ã¤¨¤Æ¡¢ÆÃÊ̤ʰú¤­¿ô \fI-Ci\fR ¤¬¤¢¤ê¡¢
unacknowledged ¥È¥é¥Ã¥×¤Ç¤Ï¤Ê¤¯ÄÌÃΤò»ÈÍѤ¹¤ë¤³¤È¤ò»ØÄꤹ¤ë¡£
(¤³¤Î°ú¤­¿ô¤ò»ØÄꤹ¤ë¤Ë¤Ï¡¢
¥Ð¡¼¥¸¥ç¥óÈÖ¹æ v2c ¤Þ¤¿¤Ï v3 ¤ò»ØÄꤹ¤ëɬÍפ¬¤¢¤ë)¡£
.\"O .SH "PROXY SUPPORT"
.SH ¥×¥í¥­¥·¤Î¥µ¥Ý¡¼¥È
.IP "proxy [SNMPCMD ARGS] HOST OID [REMOTEOID]"
.\"O .B Warning:
.B ·Ù¹ð:
.\"O This functionality is at beta level support.
¤³¤Îµ¡Ç½¤Ï¥µ¥Ý¡¼¥È¤Ï¦ÂÈǤǤ¢¤ë¡£
.IP
.\"O This token specifies that any incoming requests under OID should be
.\"O proxied on to HOST instead.  Optionally, relocate the local OID tree
.\"O to the new location at the REMOTEOID.  To authenticate to HOST you
.\"O should use the appropriate set of
.\"O .I "SNMPCMD ARGS."
.\"O See the snmpcmd man page for details.
¤³¤Î¥È¡¼¥¯¥ó¤Ï¼õ¿®¤·¤¿ OID °Ê²¼¤ÎǤ°Õ¤Î¥ê¥¯¥¨¥¹¥È¤ò HOST ¤ËÃæ·Ñ¤·¤ÆÅϤ¹¡£
Ä̾ï¤Ï¥í¡¼¥«¥ë¤Î OID ¥Ä¥ê¡¼¤ò¿·¤·¤¤  REMOTEOID ¤È¤¤¤¦¾ì½ê¤ËÊѹ¹¤¹¤ë¡£
HOST ¤Çǧ¾Ú¤µ¤ì¤ë¤¿¤á¤Ë¤Ï¡¢Å¬ÀÚ¤Ê
.I "SNMPCMD ARGS"
¤Î¥»¥Ã¥È¤ò»È¤ï¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤¡£
¾ÜºÙ¤Ï snmpcmd ¤Î man ¥Ú¡¼¥¸¤ò»²¾È¤¹¤ë¤³¤È¡£
.IP
.\"O Examples:
Îã:
.IP
proxy -v 1 -c public remotehost .1.3.6.1.4.1.2021
.IP
proxy -v 3 -l noAuthNoPriv -u user remotehost .1.3.6.1.3.10 .1.3.6.1.2.1.1
.\"O .SH "PASS-THROUGH CONTROL"
.SH ¥Ñ¥¹¥¹¥ë¡¼À©¸æ
.IP "pass MIBOID EXEC"
.\"O Passes entire control of MIBOID to the EXEC program.  The EXEC program
.\"O is called in one of the following three ways:
MIBOID ¤ÎÁ´À©¸æ¤ò EXEC ¥×¥í¥°¥é¥à¤ËÅϤ¹¡£
EXEC ¥×¥í¥°¥é¥à¤Ï°Ê²¼¤Î 3 ¤Ä¤Î¤¦¤Á¤Î 1 ¤Ä¤ÎÊýË¡¤Ç¸Æ¤Ó½Ð¤¹:
.RS
.IP "EXEC -g MIBOID"
.IP "EXEC -n MIBOID"
.IP
.\"O These call lines match to SNMP get and getnext requests.  It is
.\"O expected that the EXEC program will take the arguments passed to it
.\"O and return the appropriate response through it's stdout.  
¤³¤ì¤é¤Î¸Æ¤Ó½Ð¤·¤Ï SNMP get ¤È getnext ¥ê¥¯¥¨¥¹¥È¤Ë¥Þ¥Ã¥Á¤¹¤ë¡£
EXEC ¥×¥í¥°¥é¥à¤ÏÅϤµ¤ì¤¿°ú¤­¿ô¤ò¼õ¤±¼è¤ê¡¢
¥ì¥¹¥Ý¥ó¥¹¤òɸ½à½ÐÎϤËÊÖ¤¹¤È²¾Äꤵ¤ì¤Æ¤¤¤ë¡£
.IP
.\"O The first line of stdout should be the mib OID of the returning value.
ɸ½à½ÐÎϤΠ1 ¹ÔÌܤÏÊÖ¤êÃͤΠmib OID ¤Ç¤¢¤ë¡£
.\"O The second line should be the TYPE of value returned, where TYPE is
.\"O one of the text strings:
.\"O .B string, integer, unsigned, objectid, timeticks, ipaddress, counter, 
.\"O or
.\"O .B gauge.
2 ¹ÔÌܤÏÊÖ¤µ¤ì¤ëÃͤΠTYPE ¤Ç¤¢¤ë¡£
TYPE ¤Ï¥Æ¥­¥¹¥Èʸ»úÎó
.BR string ", " integer ", " unsigned ", " objectid ", "
.BR timeticks ", " ipaddress ", " counter ", " gauge
¤Î¤¦¤Á¤Î 1 ¤Ä¤Ç¤¢¤ë¡£
.\"O The third line of stdout should be the VALUE corresponding with the
.\"O returned TYPE.
ɸ½à½ÐÎϤΠ3 ¹ÔÌܤÏÊÖ¤µ¤ì¤¿ TYPE ¤ËÂбþ¤¹¤ë VALUE ¤Ç¤¢¤ë¡£
.IP
.\"O For instance, if a script was to return the value integer value "42"
.\"O when a request for .1.3.6.1.4.100 was requested, the script should
.\"O return the following 3 lines:
Î㤨¤Ð .1.3.6.1.4.100 ¤Ø¥ê¥¯¥¨¥¹¥È¤¬Á÷¤é¤ì¤¿¤È¤­¤Ë
¥¹¥¯¥ê¥×¥È¤¬À°¿ôÃÍ "42" ¤òÊÖ¤¹¾ì¹ç¡¢
¥¹¥¯¥ê¥×¥È¤Ï°Ê²¼¤Î 3 ¹Ô¤òÊÖ¤µ¤Ê¤±¤ì¤Ð¤Ê¤é¤Ê¤¤:
.br
.RS
  .1.3.6.1.4.100
.br
  integer
.br
  42
.RE
.IP
.\"O To indicate that the script is unable to comply with the request due
.\"O to an end-of-mib condition or an invalid request, simple exit and
.\"O return no output to stdout at all.  A snmp error will be generated
.\"O corresponding to the SNMP NO-SUCH-NAME response.
end-of-mib ¾ò·ï¤äÉÔÀµ¤Ê¥ê¥¯¥¨¥¹¤¬¸¶°ø¤Ç¡¢
¥¹¥¯¥ê¥×¥È¤¬±þÅú¤Ç¤­¤Ê¤¤¤³¤È¤òɽ¤¹¤Ë¤Ï¡¢
ñ½ã¤Ë exit ¤·¤Æɸ½à½ÐÎϤ˲¿¤âÊÖ¤µ¤Ê¤±¤ì¤Ð¤è¤¤¡£
SNMP NO-SUCH-NAME ¥ì¥¹¥Ý¥ó¥¹¤ËÂбþ¤¹¤ë snmp ¥¨¥é¡¼¤¬À¸À®¤µ¤ì¤ë¡£
.IP "EXEC -s MIBOID TYPE VALUE"
.IP 
.\"O For SNMP set requests, the above call method is used.  The TYPE passed
.\"O to the EXEC program is one of the text strings:
.\"O .B integer, counter, gauge, timeticks, ipaddress, objid,
.\"O or 
.\"O .B string,
.\"O indicating the type of value passed in the next argument.
SNMP set ¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ë¤Ë¤Ï¡¢¾å¤ÎÊýË¡¤òÍѤ¤¤ë¡£
EXEC ¥×¥í¥°¥é¥à¤ËÅϤµ¤ì¤ë TYPE ¤Ï¡¢¥Æ¥­¥¹¥Èʸ»úÎó
.BR integer ", " counter ", " gauge ", " timeticks ", " 
.BR ipaddress ", " objid ", " string
¤Î¤¦¤Á¤Î 1 ¤Ä¤Ç¤¢¤ë¡£
¤³¤ì¤é¤Ï¼¡¤Î°ú¤­¿ô¤ÇÅϤµ¤ì¤ë VALUE ¤Î¥¿¥¤¥×¤òɽ¤¹¡£
.IP
.\"O Return nothing to stdout, and the set will assumed to have been
.\"O successful.  Otherwise, return one of the following error strings to
.\"O signal an error:
.\"O .B not-writable, 
.\"O or 
.\"O .B wrong-type
.\"O and the appropriate error response will be generated instead.
ɸ½à½ÐÎϤ˲¿¤âÊÖ¤µ¤Ê¤«¤Ã¤¿¾ì¹ç¤Ï¡¢set ¤¬À®¸ù¤·¤¿¤â¤Î¤È²¾Äꤹ¤ë¡£
¤½¤ì°Ê³°¤Î¾ì¹ç¤È¤·¤Æ¤Ï¡¢¥¨¥é¡¼¤ò¼¨¤¹¤¿¤á¤Ë
.B not-writable
¤Þ¤¿¤Ï
.B wrong-type
¤Î¤¤¤º¤ì¤«¤Îʸ»úÎó¤òÊÖ¤¹¤³¤È¤¬¤¢¤ê¡¢
ŬÅö¤Ê¥¨¥é¡¼¥ì¥¹¥Ý¥ó¥¹¤¬À¸À®¤µ¤ì¤ë¡£
.RS
.\"O .IP Note:
.IP Ãí°Õ:
.\"O By default, the only community allowed to write (ie snmpset) to your
.\"O script will be the "private" community,or community #2 if defined
.\"O differently by the "community" token discussed above.  Which
.\"O communities are allowed write access are controlled by the RWRITE
.\"O definition in the snmplib/snmp_impl.h source file.
¥Ç¥Õ¥©¥ë¥È¤Ç¤Ï¡¢¥æ¡¼¥¶¡¼¤Î¥¹¥¯¥ê¥×¥È¤Ç
write (¤Ä¤Þ¤ê snmpset) ¤¬µö²Ä¤µ¤ì¤ë¥³¥ß¥å¥Ë¥Æ¥£¤Ï¡¢
"private" ¥³¥ß¥å¥Ë¥Æ¥£¤È
¾å¤ÇÀâÌÀ¤·¤¿ "community" ¥È¡¼¥¯¥ó¤ÇÊ̤ËÄêµÁ¤·¤¿
¥³¥ß¥å¥Ë¥Æ¥£ #2 ¤Î¤ß¤Ç¤¢¤ë¡£
¤É¤Î¥³¥ß¥å¥Ë¥Æ¥£¤Ë½ñ¤­¹þ¤ß¥¢¥¯¥»¥¹¤òµö²Ä¤¹¤ë¤«¤Ï¡¢
¥½¡¼¥¹¥Õ¥¡¥¤¥ë snmplib/snmp_impl.h ¤Î
RWRITE ÄêµÁ¤ÇÀ©¸æ¤Ç¤­¤ë¡£
.RE
.RE
.IP
.\"O Example (in snmpd.conf):
(snmpd.conf ¤Ë¤ª¤±¤ë) Îã:
.IP
pass .1.3.6.1.4.1.2021.255 /path/to/local/passtest
.RE
.IP "pass_persist MIBOID EXEC"
.\"O Passes entire control of MIBOID to the EXEC program.  
.\"O Similar to pass, but the EXEC program continues to run after the initial
.\"O request is answered.
MIBOID ¤ÎÁ´¤Æ¤ÎÀ©¸æ¤ò EXEC ¥×¥í¥°¥é¥à¤ËÅϤ¹¡£
pass ¤È»÷¤Æ¤¤¤ë¤¬¡¢EXEC ¥×¥í¥°¥é¥à¤Ï
ºÇ½é¤Î¥ê¥¯¥¨¥¹¥È¤ËÊÖÅú¤·¤¿¸å¤â²ÔƯ¤·Â³¤±¤ë¡£
.IP
.\"O Upon initialization, EXEC is passed the string "PING\\n" in stdin,
.\"O and it should respond by printing "PONG\\n" to stdout.
½é´ü²½¤ÎºÝ¤Ë¤Ï¡¢EXEC ¤ËÂФ·¤Æɸ½àÆþÎϤ«¤éʸ»úÎó "PING\\n" ¤¬ÅϤµ¤ì¡¢
ɸ½à½ÐÎÏ¤Ë "PONG\\n" ¤òɽ¼¨¤·¤ÆÊÖÅú¤¹¤ë¡£
.IP
.\"O For get and getnext requests, EXEC program is passed two lines,
.\"O the command (get or getnext) and the mib OID.  It should return
.\"O three lines, the mib OID, the TYPE of value returned,
.\"O the VALUE corresponding with the returned TYPE.
get ¤Þ¤¿¤Ï getnext ¥ê¥¯¥¨¥¹¥È¤òÁ÷¤ë¤Ë¤Ï¡¢
EXEC ¥×¥í¥°¥é¥à¤Ë¥³¥Þ¥ó¥É (get ¤Þ¤¿¤Ï getnext) ¤È
mib OID ¤È¤¤¤¦ 2 ¹Ô¤òÅϤ¹¡£
EXEC ¥×¥í¥°¥é¥à¤Ï¡¢mib OID¡¦ÊÖ¤µ¤ì¤ë VALUE ¤Î TYPE¡¦
ÊÖ¤µ¤ì¤¿ TYPE ¤ËÂбþ¤¹¤ë VALUE ¤È¤¤¤¦ 3 ¹Ô¤òÊÖ¤¹¡£
.IP
.\"O For example, if the value for .1.3.6.1.4.100 was requested, the following
.\"O 2 lines would be passed in to stdin:
Î㤨¤Ð¡¢.1.3.6.1.4.100 ¤ÎÃͤò¥ê¥¯¥¨¥¹¥È¤¹¤ë¾ì¹ç¤Ï¡¢
ɸ½àÆþÎϤ˰ʲ¼¤Î 2 ¹Ô¤òÅϤ¹¡£
.br
.RS
  get
.br
  .1.3.6.1.4.100  
.RE
.IP
.\"O To return the value, say, 42, the script would write to stdout:
ÃÍ¡¢¤Ä¤Þ¤ê 42 ¤òÊÖ¤¹¤¿¤á¤Ë¡¢¥¹¥¯¥ê¥×¥È¤Ï°Ê²¼¤Î¤è¤¦¤Ê½ñ¤­½Ð¤·¤ò¹Ô¤¦:
.br
.RS
  .1.3.6.1.4.100
.br
  integer
.br
  42
.RE
.IP
.\"O To indicate that the script is unable to comply with the request due
.\"O to an end-of-mib condition or an invalid request, print "NONE\\n" to
.\"O stdout.
end-of-mib ¾ò·ï¤Þ¤¿¤ÏÉÔÀµ¤Ê¥ê¥¯¥¨¥¹¥È¤¬¸¶°ø¤Ç¡¢
¥¹¥¯¥ê¥×¥È¤¬¥ê¥¯¥¨¥¹¥È¤Ë±þÅú¤Ç¤­¤Ê¤¤¤³¤È¤òɽ¤¹¤Ë¤Ï¡¢
ɸ½à½ÐÎÏ¤Ë "NONE\\n" ¤ò½ñ¤­½Ð¤¹¡£
.IP
.\"O Example (in snmpd.conf):
(snmpd.conf ¤Ë¤ª¤±¤ë) Îã:
.IP
pass_persist .1.3.6.1.4.1.2021.255 /path/to/local/pass_persisttest
.RE
.\"O .SH "EXAMPLE"
.SH Îã
.\"O See the EXAMPLE.CONF file in the top level source directory for a more
.\"O detailed example of how the above information is used in real
.\"O examples.
¾åµ­¤Î¾ðÊ󤬼ºݤÎÎã¤Ç¤É¤Î¤è¤¦¤Ë»È¤ï¤ì¤Æ¤¤¤ë¤«¤Ë¤Ä¤¤¤Æ¤Ï¡¢
¥½¡¼¥¹¤Î¥È¥Ã¥×¥Ç¥£¥ì¥¯¥È¥ê¤Ë¤¢¤ë EXAMPLE.CONF ¥Õ¥¡¥¤¥ë¤ò»²¾È¤¹¤ë¤³¤È¡£
.\"O .SH "RE-READING snmpd.conf and snmpd.local.conf"
.SH snmpd.conf ¤È snmpd.local.conf ¤ÎºÆÆɤ߹þ¤ß
.\"O The ucd-snmp agent can be forced to re-read its configuration files.
.\"O It can be told to do so by one of two ways:
ucd-snmp ¥¨¡¼¥¸¥§¥ó¥È¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤òºÆÆɤ߹þ¤ß¤µ¤»¤ë¤³¤È¤¬²Äǽ¤Ç¤¢¤ë¡£
°Ê²¼¤Î 2 ¤Ä¤Î¤¦¤Á¤Î 1 ¤Ä¤ò¼Â¹Ô¤¹¤ì¤Ð¤è¤¤:
.IP 1.
.\"O An snmpset of integer(1) to UCD-SNMP-MIB::versionUpdateConfig.0
.\"O (.1.3.6.1.4.1.2021.100.11.0)
snmpset ¤Ç UCD-SNMP-MIB::versionUpdateConfig.0
(.1.3.6.1.4.1.2021.100.11.0) ¤òÀ°¿ô (1) ¤ËÀßÄꤹ¤ë¡£
.IP 2.
.\"O A "kill -HUP" signal sent to the snmpd agent process.
snmpd ¥¨¡¼¥¸¥§¥ó¥È¥×¥í¥»¥¹¤Ë "kill -HUP" ¥·¥°¥Ê¥ë¤òÁ÷¤ë¡£
.\"O .SH "FILES"
.SH ¥Õ¥¡¥¤¥ë
/usr/share/snmp/snmpd.conf
.\"O .SH "SEE ALSO"
.SH ´ØÏ¢¹àÌÜ
snmpconf(1), snmp.conf(5), snmp_config(5), snmpd(1), EXAMPLE.conf, read_config(3).
.\" Local Variables:
.\"  mode: nroff
.\" End: