EndRun Tempus LX GPS, User Manual

Page: 82 / 116

T e m p u s L X G P S U s e r M a n u a l 70
A P P E N D I X C
71 T e m p u s L X G P S U s e r M a n u a l
S I M P L E N E T W O R K M A N A G E M E N T P R O T O C O L ( S N M P )
give you the flavor of the configuration but definitely not the full scope of possibilities. To access
your Tempus LX via v3 of SNMP, you will have to configure two files:
/etc/snmpd.conf
/boot/net-snmp/snmpd.conf
The first file contains static configuration parameters that the agent uses to control access and to de-
termine where to send notifications/traps. Other aspects of the agent’s operation are also configurable
in this file, but you should not need to modify those. To use the SNMPv3 capabilities of the Tempus
LX, you must first set up user information and access limits for those users in
/etc/snmpd.conf.
Un-
comment and edit these two lines to define your v3 users and their access parameters:
rwuser root priv .1
rouser ntpuser auth .1.3.6.1.4.1.13827
The first line defines a SNMPv3 read-write user
root
whose minimum security level will be authenti-
cated and encrypted for privacy (choices are noauth, auth and priv), and who will have read-write ac-
cess to the entire
iso(1)
branch of the SMI object tree. The second line defines a SNMPv3 read-only
user ntpuser whose minimum security level will be authenticated but not encrypted, and who will
have read-only access to the entire
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).endRun-
TechnologiesMIB(13827) branch of the SMI object tree. After adding the user lines to /etc/
snmpd.conf
, copy it to the
/boot/etc
directory using
cp –p
.
The second file is located on the non-volatile FLASH disk and is used by the SNMP agent to store
“persistent data” that may be dynamic in nature. This may include the values of the MIB-II variables
sysLocation, sysContact and sysName as well as any configured SNMPv3 user crypto keys. In order
to use SNMPv3, you must configure user keys in this file for each SNMPv3 user that you have set up
in /etc/snmpd.conf . To do this, you must add lines to /boot/net-snmp/snmpd.conf like these for each
user:
createUser root MD5 endrun_1 DES endrun_1
createUser ntpuser SHA Tempus_0
The first line will cause the agent,
snmpd
to create a user root who may be authenticated via Mes-
sage Digest Algorithm 5 (MD5) with password
endrun_1
and may use the Data Encryption Standard
(DES) to encrypt the session data with passphrase endrun_1 . The second line will cause a user nt-
puser
to be created who may be authenticated using the Secure Hash Algorithm (SHA) with password
Tempus_0 . Passwords and passphrases must have a minimum of 8 characters, or you will not be able
to be authenticated.
IMPORTANT
You must kill the
snmpd
process prior to editing, /boot/net-snmp/snmpd.conf . Otherwise, the secret
key creation may not complete properly. Issue the command
ps -e
to have the operating system dis-
play the list of running processes. Look for the PID of the
snmpd
process and issue the kill command to
stop it. For example, if the PID listed for the
snmpd
process is 53, then you would issue this command:
kill 53
. You can verify that the process was terminated by re-issuing the
ps -e
command.
After re-booting, the agent will read the
/boot/net-snmp/snmpd.conf
configuration file and compute