The KLOE command server, cmdsrv, executes in every
KLOE DAQ node to:
- Receive and queue messages to DAQ processes in the
node
- Give local variables to remote clients
The command server is based on the Simple Network Management
Protocol.
Two versions exist:
1- A complete snmp daemon that implements the network and KLOE
related MIB variables. This version must be started
with superuser privilegge because the Kernel must be
open to extract information. It runs on HP-UX and Lynx
and uses the standard UDP port 161.
2- A reduced snmp daemon that implements only the KLOE
variables and will be used in particular on OSF/1.
It runs on HP-UX and Lynx. The OSF/1 version will
be tested when the KLOE Unidaq version on OSF/1 will be release.
It uses per default the port KLOE_SNMP_PORT defined in
$DAQSNMPSRC/apps/kloe_vars.h but it can be redefined setting
the KLOE_SNMP_PORT environment variable.
It is available now as package daqsnmp
version v0. It requires two files
$DAQSNMPBIN/'node'/snmpd.conf
$DAQSNMPBIN/'node'/snmp.agentinfo
that contains the first, system variables (public and private
communities, trap destinations, ...). The second one, created
using a touch command, is used by the system to maintains history
of the active snmp agents.
The command server can be activated by the command
$DAQSNMPBIN/cmdsrv &
In the same package general purpose utilities exist (ksnmpget, ksnmpwalk,
ksnmptest) to respctively:
- get information about a single variable
$DAQSNMPBIN/ksnmpget kloedaq public kprocesses.knumber.0
- get information about a tree of variables
$DAQSNMPBIN/ksnmpwalk kloedaq public kprocesses
- set or get a single variable
$DAQSNMPBIN/ksnmptest kloedaq public
........................
The UDP port used is defined by the KLOE_SNMP_PORT
variable. By assining the 161 port, the general SNMP daemon can be
interrogated.
Suggestions, comments or questions? Please contact:
Maria Lorenza Ferrer (ferrer@hpkloe01.lnf.infn.it)