|
Table Of Contents
File Reference
This chapter describes the following files, which are used in the Cisco Metro 1500 series environment.
• hosts
Note These files are examples and are sorted in alphabetical order:
hosts
Name
hosts-File that lists all hosts who are known to Windows 95/98/NT
Example
# Copyright (c) 1998 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP stack for
# Windows98
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host
# name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a `#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com
# source server
# 38.25.63.10 x.acme.com
# x client host
127.0.0.1 localhost
169.254.178.200 home.colt
169.254.178.41 home.christine christine
snmpd.conf
Name
snmpd.conf-Configuration file for cmu snmpd
Description
/etc/snmpd.conf is read on startup by snmpd. The file has two parts. The first part is related to the view, user, and community configuration for snmp v2-usec. The second part is for the Linux port and allows the setting of additional configuration items.
The Linux specific part consists of lines containing a key followed by a : and a value. Lines beginning with a # and empty lines are ignored. The recognized key and value pairs are shown in Table 7-1.
Example
This is an example snmpd.conf file:
## /etc/snmpd.conf:
##
## view configuration
##
## viewName OID included/excluded
##
## internet
view all .1.3.6.1 included
## internet
view mini .1.3.6.1 included
## for v1 public exclude exclude mib-2.ident.identInfo
## and mib-2.host.hrSWRun in the mini view:
view xmini .1.3.6.1 included
view xmini .1.3.6.1.2.1.24.1 excluded
view xmini .1.3.6.1.2.1.25.4 excluded
## system, snmp, usecAgent, usecStats
view semi .1.3.6.1.2.1.1 included
view semi .1.3.6.1.2.1.11 included
view semi .1.3.6.1.6.3.6.1.1 included
view semi .1.3.6.1.6.3.6.1.2 included
## snmp, usecAgent, usecStats
view semi .1.3.6.1.2.1.11 included
view semi .1.3.6.1.6.3.6.1.1 included
view semi .1.3.6.1.6.3.6.1.2 included
##
## user configuration
##
## noneRV noneWV authRV authWV userName[/authKey]
##
u s e r m i n i - a l l a l l p u b l ic/0x05a1483bb7a0b314cc5cf9d27aee2a89
##
## community configuration
##
## commName readV writeV
##
community public xmini -
community private mini mini
##
## now follows the specific section of the linux-port.
##
##
## port to use (default is 161):
##
# port: 161
##
## the entry of system.Contact and system.Location:
##
system contact: name
system location: location
## system name is per default determined from the
hostname:
# system name: chappell
##
## type and speed of interfaces:
##
interface: lo0 24 20000000
interface: eth0 6 10000000
interface: sl0 28 38400
interface: sl1 28 38400
interface: sl2 28 38400
interface: sl3 28 38400
interface: ppp0 23 38400
interface: ppp1 23 38400
interface: ppp2 23 38400
interface: ppp3 23 38400
## end of /etc/snmpd.conf
Bugs
There is currently no further documentation about the user-specific part.
snmptrapd.conf
Name
snmptrapd.conf-Configuration file for the event manager snmptrapd
Description
snmptrapd.conf is the configuration file for the event manager. It is located in /etc/. After starting snmptrapd, immediately after power up, the configuration file is read. snmptrapd.conf is modified by using an editor or by snmpconfig. Changes in snmptrapd.conf are only valid after restarting the event manager. Comment lines start with a #; tokens are space or tab. The first section describes the different event logging mechanisms: LogFlash is the keyword for the permanent log file, LogRAM for the temporary log file, and TrapSink for the external SNMP managers. In the second section, all known events are listed. You can define a priority for every event, 1 is high, 10 is low. An event is logged if it is of an equal or higher priority than the priority of the logging mechanism. Table 7-2 lists and describes snmptrapd.com keywords.
For example, by default the ColdStart has a priority of 1 which means "very high." This event is always logged. An event with priority 4 is only logged if the logging mechanism has priority 4, 5, or higher number.
Sections
Table 7-2 describes snmpdtrapd.com keywords.
Example
# Configuration File
# /etc/snmptrapd.conf
# last change: Mon Oct 26 19:44:36 1998
# This file is used to set the configuration for logging on
# Flash Disk, RAM Disk and external System via Traps
# Log Levels for Flash Disk and RAM Disk
LogFlash 1 1000
LogRAM 10 32768
# Trap Sink addresses
TrapSink 0 5 public 192.168.100.44
# Generic Traps
Generic 0 1 ColdStart
Generic 1 10 WarmStart
Generic 2 10 IFDown
Generic 3 10 IFUp
Generic 4 10 InvalidCommunity
Generic 5 10 EGPdown
# Enterprises Traps
Enterprise 1 4 passwordFail
Enterprise 2 4 switchWarning
Enterprise 3 4 switchLOS
Enterprise 4 4 switchErrorLock
Enterprise 5 4 switchBackupLineFail
Enterprise 6 4 switchChangedLine
Enterprise 7 4 snmpFail
Enterprise 8 4 chanFail
Enterprise 9 4 chanLasLocCurrOOR
Enterprise 10 4 chanLasRemCurrOOR
Enterprise 11 4 chanTempOOR
Enterprise 12 4 chanClockrecFail
Enterprise 13 4 chanCommunicationWar
Enterprise 14 4 chanRecremLOS
Enterprise 15 4 chanReclocLOS
Enterprise 16 4 fanFail
Enterprise 17 4 edfaFail
Enterprise 18 4 psFail
Enterprise 19 4 psOK
Enterprise 20 4 chanRecremNoLOS
Enterprise 21 4 chanReclocNoLOS
Enterprise 22 4 chanHardwareAdd
Enterprise 23 4 chanHardwareDel
Enterprise 24 4 chanClockrecNoFail
See Also
snmpconfig, RFC 1065, RFC 1066, RFC 1067
Bugs
Not all traps are supported.
Posted: Tue Apr 26 05:59:22 PDT 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.