Installing and Configuring ftlSNMP
Simple Network Management Using Net-SNMP and ftlSNMP
8-5
The
snmpd.conf
File
C A U T I O N
C A U T I O N
!
Use SNMPv3 when the manager and master agent are
separated on a public network.
The following is an example only. Failure to use SNMPv3 when communicating over
a public network is a server and network security risk.
SNMP V3 includes true authentication and encryption. The three authentication
models are NoAuthnoPriv, authNoPriv, and authPriv. Note that you must have
auth
status for encryption.
An SNMP engine identifier takes the first IP address as the default that identifies the
agent in the device. Each device must have a user login account for the device.
SNMPv3 also has concepts of groups, views, and privileges for access control. These
are referred to as the view-based access control model (VACM) and user-based
security model (USM).
You
must
keep the following two lines in the
snmpd.conf
file for the master agent to
function properly:
master agentx
agentxTimeout 60
ftlSNMP requires agentX services.
To avoid timeouts when the subagents are running under abnormal system stress (for
example, 80% CPU usage and disks heavily stressed), raise the value of
agentxTimeout
. If a timeout occurs, there will be a short delay while the subagents
reinitialize their communications.
The
ftlsubagent.conf
and
ftltrapsubagent.conf
Files
These files require no editing for default operation, but you may want to adjust logging.
You can change the trace level from
off
to
brief
or
verbose
as desired, or as
suggested by NECAM to aid in diagnosing any problems. Debugging information will
be logged.
These files contain the following configuration lines:
sraTraceLevel off
sraTraceLog /var/opt/ft/log/ftlsubagents.log
