User guide

Relationship of Logs and Traps with Device Interfaces Log Formats
1-9
Log Reference for SBx3100 and iMAP Series Switches (Overview of Logs / Alarms System)
2.5 Relationship of Logs and Traps with Device Interfaces
Since there are multiple ways to report a device status as well as multiple interfaces to display them, the follow-
ing summarizes how they are related:
Traps are produced and associated with:
• Standard (RFC-based) MIBs
• Allied Telesis products
All traps produce logs, and these logs have associated log messages, reason codes, and severities.
Some logs, on the other hand, do not have an associated trap. These are usually for status or update informa-
tion.
The SYSLOG (System Log Events) application on the AlliedView NMS shows the logs as produced by the Allied
Telesis devices and can be controlled to show only some or all log categories. The Syslog viewer, therefore, is a
way to view all logs produced by the devices on the AlliedView NMS, while the Alarm view is a graphical way to
view all log messages that have a severity and need to be viewed immediately.
2.6 CARD and PORT Logs (Information, Degrading and Failing Conditions)
The two most common logs for card and port logs are CARD023, CARD005, PORT013, and PORT003 logs.
• CARD023 logs are intended to indicate INFO conditions that do not affect state, such as file corruption,
database upgrade, multicast stream limit, and inconsistent load.
• CARD005 covers all failing and degrading conditions.
Note: Both of those logs generate the same SNMP trap.
• PORT003 logs are for degrading conditions, and PORT013 is informational only.
3 Log Formats
The Allied Telesis product produces management logs that provide information about all changes that occur. Fig-
ure 1-3 shows an example log.