HP 3000 Manuals HP 3000 Manuals
SNMPSAMP and SNMPCONF
The SNNP/XL product is shipped with a skeleton configuration file,
SNMPSAMP.NET.SYS. When the system is started, SNMP is automatically
launched. The first time this is done, the product copies the SNMPSAMP
file to the SNMPCONF file and initializes the configuration from the new
SNMPCONF file. This file contains the configuration information for the
HP SNMP/XL subsystem. Initially, SNMPSAMP looks like this:
# File Name: SNMPSAMP.NET.SYS
#
# $Revision: 5.1.1.2 $
#
# snmp/xl reads this configuration information from this file upon
# execution.
#
# When the SNMP/XL subsystem starts up, if the file SNMPCONF.NET.SYS
does not
# exist, this file SNMPSAMP.NET.SYS, is copied to SNMPCONF.NET.SYS
so that the
# SNMP/XL subsystem may successfully start.
#
# Enter appropriate values after the following keywords.
#
# agent-community-name:
# trap-dest:
# location:
# contact:
#
# agent-community-name: enter community name for the snmp agent. The
# agent will respond to any SNMP requests using this community name.
# If a community name is not entered, the agent will respond to get
# requests using any community name.
#
# example: to restrict the agent to only respond to get requests
# using the community name "secret," enter:
#
# agent-community-name: secret
#
# trap-dest: enter the system name where traps will be sent. This
system
# name is usually the hostname or IP address of the management station.
#
# example: to send the traps to system names "manager1," and
# "15.2.113.223," enter:
#
# trap-dest: manager1
# trap-dest: 15.2.113.223
#
# location: enter the physical location of the agent/system.
#
# example: if the agent is on the first floor near the west elevator,
enter:
#
# location: 1st Floor near west elevator
#
# contact: enter the person responsible for this agent, together
with
# information on how to contact this person.
#
# example: if Bob Jones is responsible for this agent, and his
# phone number is 555-2000, enter
#
# contact: Bob Jones (Phone 555-2000)
#
##
agent-community-name: # enter a community name
trap-dest: # enter a system name where traps will be sent
location: # enter location of agent
contact: # enter contact person and how to contact this
person
The SNMPCONF file should be the primary configuration file. This file
can be modified with any standard editor and reloaded via the
UPDATECONFIG command described in chapter 3. You should add the
agent-community-name, trap-dests, location, and contact information to
this file.
NOTE It is recommended that you modify these parameters in a consistent
manner with the SNMP network management station and applications.
For example, both the agent and manager should have the same
agent-community-name. The IP address of the trap-dest should be
that of the management station.
If you do not add any information to this skeleton file before starting
up the SNMP agent, then the agent-community-name, trap-dests, location,
and contact remain unconfigured. This means that:
* The agent-community-name is NULL. No inbound packets are excluded
on the basis of community name.
* The location and contact is NULL. An attempt to retrieve the MIB
object for location or contact results in an SNMP response being
returned, indicating that they are NULL.
* No traps are sent from this agent as long as no
trap-destinationsare configured.
If you want to add any new information to the configuration file, once
the product has been started, you must edit the SNMPCONF file and execute
the command SNMPCONTROL UPDATECONFIG. Or, you can shut down the product,
edit the SNMPCONF file, and restart the product so that the new SNMPCONF
file is read.