Filter
Top Products
5-5
Cisco Access Registrar 3.5 Concepts and Reference Guide
OL-2683-02
Chapter 5 Understanding SNMP
SNMP Traps
carOtherAccServerResponding
carOtherAccServerResponding signifies that an accounting server that had previously sent a not
responding message is now responding to requests from the Cisco AR server. This trap has three objects:
• radiusAccServerAddress—indicates the identity of the concerned server
• radiusAccClientServerPortNumber—indicates the port number of the concerned server
• carAccServerType—indicates the type of the concerned server
The index of these three objects identifies the entry in radiusAuthServerTable and arAccServerExtTable
which maintains the characteristics of the concerned server.
One should not rely on the reception of this notification as an indication that all is well with the network.
Several conditions, including the restart of the Cisco AR server, could result in either multiple
carOtherAccServerNotResponding notifications being sent or in a carOtherAccServerResponding
notification not being sent. The NMS can query the carAccServerRunningState in carAccServerExtTable
for the current running state of this server.
carAccountingLoggingFailure
carAccountingLoggingFailure signifies that this Cisco AR server cannot record accounting packets
locally. This trap has two objects:
• carNotifAcctLogErrorReason—indicates the reason packets cannot be recorded locally
• carNotifAcctLogErrorInterval—indicates how long to wait until another notification of this type
might be sent. A value of 0 (zero) indicates no time interval checking, meaning that no new
notification can be sent until the error condition is corrected.
Configuring Traps
Cisco Access Registrar’s SNMP implementation uses various configuration files to configure its
applications.
Directories Searched
Configuration files can be found and read from numerous places. By default, SNMP applications look
for configuration files in the following three directories (in the order listed):
1. /usr/local/share/snmp/snmp.conf
This directory contains common configuration for the agent and the application. Refer to man page
snmp.conf(5) for details.
2. /usr/local/share/snmp/snmpd.conf
3. /usr/local/share/snmp/snmp.local.conf
This directory configures the agent. Refer to man page snmp.conf(5) for details.
In each of these directories, an SNMP application looks for files with the extension .conf. The
application also looks for configuration files in default locations where a configuration file can exist for
any given configuration file type.