 cOS Stream 4.00.05 SNMP Trap Reference Guide
|
Next |
|---|
| cOS Stream 4.00.05 SNMP Trap Reference Guide
|
Next |
|---|
![[Note]](images/note.png) |
Note: This document is also available in other formats |
|---|---|
|
A PDF version of this document along with all current and older documentation in PDF format can be found at https://my.clavister.com. It is also available as a single HTML page. |
The Clavister cOS Stream supports both proprietary and standard SNMPv2c traps. This guide is a reference for all supported SNMP traps. It is designed to be a valuable information source for both management and troubleshooting.
The main part of this guide lists the individual SNMP traps that are supported. This chapter explains how the traps are grouped and how to interpret the information presented for each.
The guide is divided into two major sections:
Clavister cOS Stream proprietary traps
This section lists the Clavister proprietary trap notifications supported by the Clavister cOS Stream. Proprietary traps may include several parameters controlled by Clavister.
Each individual trap is then grouped into a specific trap category that mirrors subsystems.
The trap MIB file is supplied with the Clavister cOS Stream and has the filename CLAVISTER-STREAM-TRAPS.mib. This can be downloaded using SCP from the system's top-level directory.
Supported Standard MIB traps
This section describes standard MIB traps files and individual trap notifications from those MIBs that are supported by the Clavister cOS Stream.
It is divided into one section per standard MIB that is at least partially supported. Subsections then list the traps from that MIB that are supported, grouped by category. Each category represents a system area.
The supported standard MIBs files are not supplied by Clavister but are available from third parties. The traps listed are those supported by the Clavister cOS Stream and may not include all the trap notifications present in a specifc MIB.
SNMP Trap Structure
SNMP traps are linked to specific log events, and are triggered if the log event is triggered. Each trap identified in this document always identifies its associated log. For completness, the administrator should use this reference guide in conjunction with the separate Log Reference Guide. The following information is provided for each specific trap message:Traps belong to categories, where each category maps to a specific subsystem or event group. A trap can belong to only one category.
In this guide, categories are listed as sections, where each section includes the traps for that category.
The MIB identifier for the trap. Each MIB name is unique.
The MIB OID is a string of digits which uniquely identifies the trap. This entry also has information on the MIB file that is used to identify the value with a trap receiving agent. For standard trap OIDs, information about the reference RFC number is also included.
Used only for standard traps. Identifies the parameters that are sent within the trap PDU, as defined in the reference RFC. Parameter names are consistent with names on the MIB.
This field identifies the log ID of the event responsible for triggering the trap.
A brief explanation of the event that took place.
The name of the parameters that are included in this trap. If a parameter is specified within square brackets (for example, [username]), then the parameter is optional and may or may not be included in the trap. Some parameters are only sent for enterprise traps.
A detailed explanation of the event.
Note that this information is only featured in this reference guide, and is never included in the SNMP trap itself.
1 to 3 words separated by "_" describing what action the system will take, if any. If the trap is purely informative, this is set to "None".
A short string describing the selected system action. Some actions are self explanatory.
If applicable, this will give a short explanation of what measures the administrator might take to address the triggered event.
