Administrator Guide

Table Of Contents
CFG_SUBTASK_CONFIG_CONFLICT_TRAP: Configuration conflict is found during audit
CFG_SUBTASK_CONFIG_CONFLICT_CLEAR_: Configuration conflict is resolved
CLI_BATCH_CONFIG_IN_PROGRESS_TRAP: Batch configuration commit is in progress
CLI_BATCH_CONFIG_COMPLETE_TRAP: Batch configuration commit is success
entity
Enable entity change traps
Trap SNMPv2-MIB::sysUpTime.0 = Timeticks: (1487406) 4:07:54.06,
SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::mib-2.47.2.0.1,
SNMPv2-SMI::enterprises.6027.3.6.1.1.2.0 = INTEGER: 4
Trap SNMPv2-MIB::sysUpTime.0 = Timeticks: (1488564) 4:08:05.64,
SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::mib-2.47.2.0.1,
SNMPv2-SMI::enterprises.6027.3.6.1.1.2.0 = INTEGER: 5
Trap SNMPv2-MIB::sysUpTime.0 = Timeticks: (1489064) 4:08:10.64,
SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::mib-2.47.2.0.1,
SNMPv2-SMI::enterprises.6027.3.6.1.1.2.0 = INTEGER: 6
Trap SNMPv2-MIB::sysUpTime.0 = Timeticks: (1489568)
4:08:15.68,SNMPv2-MIB::snmpTrapOID.0 = OID: SNMPv2-SMI::mib-2.47.2.0.1,
SNMPv2-SMI::enterprises.6027.3.6.1.1.2.0 = INTEGER: 7
<cr>
SNMP Copy Config Command Completed
%SYSTEM-P:CP %SNMP-4-RMON_RISING_THRESHOLD: RMON rising threshold alarm from
SNMP OID <oid>
%SYSTEM-P:CP %SNMP-4-RMON_FALLING_THRESHOLD: RMON falling threshold alarm from
SNMP OID <oid>
%SYSTEM-P:CP %SNMP-4-RMON_HC_RISING_THRESHOLD: RMON high-capacity rising threshold
alarm from SNMP OID <oid>Copy config traps
FILEMGR_COPY_CONFIG_TRAP: Copy-config from running-config to startup-config succeeded
RMON traps
%SYSTEM-P:CP %SNMP-4-RMON_RISING_THRESHOLD: RMON rising threshold alarm from
SNMP OID
%SYSTEM-P:CP %SNMP-4-RMON_FALLING_THRESHOLD: RMON falling threshold alarm from
SNMP OID
%SYSTEM-P:CP %SNMP-4-RMON_HC_RISING_THRESHOLD: RMON high-capacity rising
threshold alarm from SNMP OID
Enabling an SNMP Agent to Notify Syslog Server
Failure
You can configure a network device to send an SNMP trap if an audit processing failure occurs due to loss of connectivity with
the syslog server.
If a connectivity failure occurs on a syslog server that is configured for reliable transmission, an SNMP trap is sent and a
message is displayed on the console.
The SNMP trap is sent only when a syslog connection fails and the time-interval between the last syslog notification and current
time is greater than or equal to 5 minutes. This restriction also applies to the console message.
NOTE: If a syslog server failure event is generated before the SNMP agent service starts, the SNMP trap is not sent.
To enable an SNMP agent to send a trap when the syslog server is not reachable, enter the following command:
CONFIGURATION MODE
snmp-server enable traps snmp syslog-unreachable
To enable an SNMP agent to send a trap when the syslog server resumes connectivity, enter the following command:
CONFIGURATION MODE
snmp-server enable traps snmp syslog-reachable
910
Simple Network Management Protocol (SNMP)