Cisco Cisco Access Registrar 3.5 - Manual (Page 48)

5-2
Cisco Access Registrar 3.5 Concepts and Reference Guide
OL-2683-02
Chapter 5 Understanding SNMP
SNMP Traps
RADIUS-AUTH-SERVER-MIB
The RADIUS-AUTH-SERVER-MIB describes the server side of the RADIUS authentication protocol.
The information contained in this MIB describes managed objects used for managing a RADIUS
authentication server.
RADIUS-ACC-CLIENT-MIB
The RADIUS-ACC-CLIENT-MIB describes the client side of the RADIUS accounting protocol. The
information contained in this MIB is useful when an Cisco AR server is used for accounting.
RADIUS-ACC-SERVER-MIB
The RADIUS-ACC-CLIENT-MIB describes the server side of the RADIUS accounting protocol. The
information contained in this MIB is useful when an Cisco AR server is used for accounting.
SNMP Traps
The traps supported by Access Registrar enable a standard SNMP management station to receive trap
messages from an Cisco AR server. These messages contain information indicating whether a server was
brought up or down, or that the proxied remote server is down or has come back online.
A trap is a network message of a specific format issued by an SNMP entity on behalf of a network
management agent application. A trap is used to provide the management station with an asynchronous
notification of an event.
When a trap is generated, a single copy of the trap is transmitted as a trap PDU to each destination
contained within a list of trap recipients.
The list of trap recipients is shared by all events and is determined at server initialization time along with
other trap configuration information. The list of trap recipients dictates where Cisco AR traps are
directed.
The configuration of any other SNMP agent on the host is ignored. By default, all traps are enabled but
no trap recipients are defined. By default, no trap is sent until trap recipients are defined.
Traps are configured using the command line interface (CLI). After configuring traps, the configuration
information is re initialized when a server reload or restart occurs.
When you configure traps, you must provide the following information:
• List of trap recipients (community string for each)
• Suppressing traps for any type of message
• Frequency of traps for any type of message