Trap Recipient; System Contact Information; Restarting The Master Agent; Configuring Dynamic Dns - Cisco Access Registrar 4.2 Installation And Configuration Manual

Configuring Dynamic DNS

Trap Recipient

The following example shows the default configuration that sets up trap recipients for SNMP versions
v1 and v2c.
Most sites use a single NMS, not two as shown below.
Note
# -----------------------------------------------------------------------------
trapcommunitytrapcom
trapsinkzubattrapcom162
trap2sinkponytatrapcom162
###############################################################################
Note
trapcommunity defines the default community string to be used when sending traps. This command
must appear prior to trapsink or trap2sink which use this community string.
trapsink and trap2sink are defined as follows:

System Contact Information

System contact information is provided in two variables through the snmpd.conf file, syslocation and
syscontact.
Look for the following lines in the snmpd.conf file:
###############################################################################
# System contact information
#
syslocation Your Location, A Building, 8th Floor
syscontact A. Person <someone@somewhere.org>

Restarting the Master Agent

You restart the CAR SNMP master agent by restarting the CAR server.
Configuring Dynamic DNS
Cisco AR supports the the Dynamic DNS protocol providing the ability to update DNS servers. The
dynamic DNS updates contain the hostname/IP Address mapping for sessions managed by Cisco AR.
Installing and Configuring Cisco Access Registrar, 4.2
4-16
trapsink is used in SNMP version 1; trap2sink is used in SNMP version 2.
trapsink hostname community
trap2sink hostname community
/opt/CSCOar/bin/arserver start
Chapter 4
port
port
Configuring Cisco Access Registrar 4.2
OL-17221-02