255-700-025
A-9
PacketStar
™
Access Concentrator 60 User Guide
, Issue 1
Release 6.3.0
Appendix A SNMP Trap Messages
Viewing SNMP Trap Messages
Table A-2 on page A-9 provides information about the SNMP enterprise-
specific trap messages, including the following:
•
Enterprise-specific trap name
•
Type of event that caused the message: a system, module, interface, or
connection event
•
System indicator for the trap message
•
The MIB objects associated with the trap message
•
Description of the trap message indicating what happened.
The system indicators for the trap messages are defined as follows:
System Indicator for
the Trap (Column 3 in
Table A-2)
Definition
• System Response
(“Response” in
Table A-2)
A system-supplied reply to a command a user enters,
usually indicating the success or failure of a requested
action.
• System Informa-
tion
(“Info” in
Table A-2)
A system-supplied informational message indicating
the completion of a particular process (for example, a
maintenance function).
• Minor Problem
(“Minor” in
Table A-2)
A notification of a problem that does not affect ser-
vice or function of a component of the Access Con-
centrator system (for example, the failure of a
redundant power supply module).
• Major Problem
(“Major” in
Table A-2)
A notification of a problem that affects service of
function of a component of the Access Concentrator
system (for example, failure of a DS1/T1 module).
• Critical Problem
(“Critical” in
Table A-2)
A notification of a problem that affects functioning of
the whole Access Concentrator system (for example,
failure of a nonredundant Stratum 3–4 module).
Critical notifications indicate that all traffic flow
through the system has ceased.
Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names
Enterprise-Specific
Trap Name
Event Type
for the Trap
System Indica-
tor for the
Trap
MIB Object Name
Trap Description
aal2TrunkConfig
ReqFailNotify
Connec-
tion
Response
aal2TrunkConfigIf
aal2TrunkConfigVpi
aal2TrunkConfigVci
pvcFailureReasonCode
The PVC VCC aal2
trunk could not be
setup.