Hypercom 1101 User Manual
IN-tact 1101 Software Configuration Guide
91
Chapter 8: SNMP Traps
Overview
The IN-tact 1101 SNMP agent is capable of sending out traps (asynchronous notifications) to the
configured SNMP manager IP addresses. SNMP manager addressing is configured on the
System Setup > Management screen. See page 24 for details on configuring this option. Each
trap includes the following fields:
configured SNMP manager IP addresses. SNMP manager addressing is configured on the
System Setup > Management screen. See page 24 for details on configuring this option. Each
trap includes the following fields:
Field
Description
enterprise
Identifies the subsystem that generated the trap. The value is taken from
sysObjectID in the system group (MIB-II).
sysObjectID in the system group (MIB-II).
agent-addr
The IP address of the object generating the trap.
generic-trap
One of the predefined trap types:
•
coldStart (0): The sending entry is reinitializing itself so that the agent’s
configuration or the protocol-entity implementation may be altered.
Typically, this is an unexpected restart due to a crash or major fault.
configuration or the protocol-entity implementation may be altered.
Typically, this is an unexpected restart due to a crash or major fault.
•
warmStart (1): The sending entity is reinitializing itself so that neither the
agent’s configuration nor the protocol-entity implementation is altered.
Typically, this is a routine restart.
agent’s configuration nor the protocol-entity implementation is altered.
Typically, this is a routine restart.
•
linkDown (2): Signals a failure in one of the agent’s communication links.
•
linkUp (3): Signals that one of the agent’s communication links has come
up.
up.
•
authenticationFailure (4): Signals that the sending entity has received a
protocol message that failed authentication.
protocol message that failed authentication.
•
egpNeighborLoss (5): Signals that an EGP neighbor for which the sending
protocol entity was an EGP peer has been marked down and the peer
relationship no longer exists.
protocol entity was an EGP peer has been marked down and the peer
relationship no longer exists.
•
enterpriseSpecific (6): Signifies that the sending entity recognizes that
some enterprise-specific event has occurred. The specific-trap field
indicates the type of trap.
some enterprise-specific event has occurred. The specific-trap field
indicates the type of trap.
specific-trap
A code that more specifically indicates the nature of the trap.