Skip to main content
Version: Spectra Analyze 9.2.2

SNMP

SNMP Trap Thresholds

The Spectra Analyze appliance can receive notifications (traps) about important system events via the Simple Network Management Protocol (SNMP).

Traps used for monitoring the average system load, as well as memory and disk usage, are generated by the Distributed Management Event Management Information Base (MIB) (DISMAN-EVENT-MIB::mteTriggerFired). Traps related to Spectra Detect and classification queue sizes are generated by the tswQueueThreshold MIB.

To enable SNMP traps and configure the address of the trap sink server, adjust the values in the Administration ‣ Configuration ‣ SNMP dialog on the Spectra Analyze appliance. The dialog also allows setting thresholds for supported types of events, which are described in more detail below.

Average system load

This trap is sent if the average load of the local system exceeds specified values (1-minute, 5-minute and 15-minute averages). Values should be provided as percentages, which are recalculated into appropriate thresholds as reported with uptime or top commands.

The following examples show traps triggered by a high 1-minute, 5-minute and 15-minute system load average, respectively:

2018-01-26 14:35:54 <UNKNOWN> [UDP: [192.168.123.247]:60418->[192.168.123.17]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (13) 0:00:00.13
SNMPv2-MIB::snmpTrapOID.0 = OID:
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: laTable
DISMAN-EVENT-MIB::mteHotTargetName.0 = STRING:
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
DISMAN-EVENT-MIB::mteHotOID.0 = OID:
UCD-SNMP-MIB::laErrorFlag.1
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 1
UCD-SNMP-MIB::laNames.1 = STRING: Load-1
UCD-SNMP-MIB::laErrMessage.1 = STRING: 1 min Load Average too high (= 2.56)
2018-01-26 14:35:54 <UNKNOWN> [UDP: [192.168.123.247]:60418->[192.168.123.17]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (13) 0:00:00.13
SNMPv2-MIB::snmpTrapOID.0 = OID:
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: laTable
DISMAN-EVENT-MIB::mteHotTargetName.0 = STRING:
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
DISMAN-EVENT-MIB::mteHotOID.0 = OID:
UCD-SNMP-MIB::laErrorFlag.2
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 1
UCD-SNMP-MIB::laNames.2 = STRING: Load-5
UCD-SNMP-MIB::laErrMessage.2 = STRING: 5 min Load Average too high (= 2.00)
2018-01-26 14:35:54 <UNKNOWN> [UDP: [192.168.123.247]:60418->[192.168.123.17]:162]:
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (13) 0:00:00.13
SNMPv2-MIB::snmpTrapOID.0 = OID:
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: laTable
DISMAN-EVENT-MIB::mteHotTargetName.0 = STRING:
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
DISMAN-EVENT-MIB::mteHotOID.0 = OID:
UCD-SNMP-MIB::laErrorFlag.3
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 1
UCD-SNMP-MIB::laNames.3 = STRING: Load-15
UCD-SNMP-MIB::laErrMessage.3 = STRING: 15 min Load Average too high (= 2.05)

Used memory

This trap is sent if used memory on the local system exceeds the specified percentage. The default value is 80%. The following example shows an event triggered by memory usage that exceeded the configured trap threshold:

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (8) 0:00:00.08
SNMPv2-MIB::snmpTrapOID.0 = OID:
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: memoryFree
DISMAN-EVENT-MIB::mteHotTargetName.0 = STRING:
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
DISMAN-EVENT-MIB::mteHotOID.0 = OID:
UCD-SNMP-MIB::memTotalFree.0
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 2124816
UCD-SNMP-MIB::memTotalReal.0 = INTEGER: 16467096 kB

Used disk space

This trap is sent if used disk space on any of the mounted disks exceeds the specified percentage. The default value is 90%. The following example shows an event triggered by a disk with less than 10% of free disk space on the /boot partition:

DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (25) 0:00:00.25
SNMPv2-MIB::snmpTrapOID.0 = OID:
DISMAN-EVENT-MIB::mteTriggerFired
DISMAN-EVENT-MIB::mteHotTrigger.0 = STRING: dskTable
DISMAN-EVENT-MIB::mteHotTargetName.0 = STRING:
DISMAN-EVENT-MIB::mteHotContextName.0 = STRING:
DISMAN-EVENT-MIB::mteHotOID.0 = OID:
UCD-SNMP-MIB::dskErrorFlag.26
DISMAN-EVENT-MIB::mteHotValue.0 = INTEGER: 1
UCD-SNMP-MIB::dskPath.26 = STRING: /boot
UCD-SNMP-MIB::dskErrorMsg.26 = STRING: /boot: less than 10% free (= 8%)

Spectra Detect queue size

This trap is sent if the number of messages in any of the queues used for Spectra Detect communication exceeds the specified value. Since the check is performed once every minute, it is possible to have the peak message count in the queue higher than the threshold, if the duration of the peak was shorter than 1 minute.

Logged events have two values: name of the queue that triggered the event and the size of the queue at the moment the event was triggered.

Classifications queue size

This trap is sent if the number of messages in any of the queues used for classifications exceeds the specified value. Since the check is performed once every minute, it is possible to have the peak message count in the queue higher than the threshold, if the duration of the peak was shorter than 1 minute.

Logged events have two values: name of the queue that triggered the event and the size of the queue at the moment the event was triggered.

Spectra Analyze MIB Descriptions

MIB fileValueDescriptionUsage
RL-MIB.txta1000Device identifiernot displayed
RL-TCBASE-MIB.txttcbQueuesApiLongStateState for api_longrunning queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesApiLongConsNumber of consumers for api_longrunning queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesApiLongMsgNumber of messages for api_longrunning queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesApiReqsStateState for api_requests queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesApiReqsConsNumber of consumers for api_requests queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesApiReqsMsgNumber of messages for api_requests queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesCeleryStateState for celery queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesCeleryConsNumber of consumers for celery queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesCeleryMsgNumber of messages for celery queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesDefaultStateState for default queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesDefaultConsNumber of consumers for default queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesDefaultMsgNumber of messages for default queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiStateState for tasks.api queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiConsNumber of consumers for tasks.api queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiMsgNumber of messages for tasks.api queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiLongStateState for tasks.api.longrunning queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiLongConsNumber of consumers for tasks.api.longrunning queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiLongMsgNumber of messages for tasks.api.longrunning queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiReqStateState for tasks.api.requests queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiReqConsNumber of consumers for tasks.api.requests queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksApiReqMsgNumber of messages for tasks.api.requests queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksClassStateState for tasks.classification queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksClassConsNumber of consumers for tasks.classification queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksClassMsgNumber of messages for tasks.classification queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksDefaultStateState for tasks.default queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksDefaultConsNumber of consumers for tasks.default queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksDefaultMsgNumber of messages for tasks.default queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksTransferStateState for tasks.transfer queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksTransferConsNumber of consumers for tasks.transfer queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksTransferMsgNumber of messages for tasks.transfer queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksIntegrationsStateState for tasks.integrations queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksIntegrationsConsNumber of consumers for tasks.integrations queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTasksIntegrationsMsgNumber of messages for tasks.integrations queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTcbaseCollectorStateState for tcbase.collector queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTcbaseCollectorConsNumber of consumers for tcbase.collector queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesTcbaseCollectorMsgNumber of messages for tcbase.collector queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentErrorStateState for tiscale.hagent_error queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentErrorConsNumber of consumers for tiscale.hagent_error queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentErrorMsgNumber of messages for tiscale.hagent_error queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentInputStateState for tiscale.hagent_input queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentInputConsNumber of consumers for tiscale.hagent_input queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentInputMsgNumber of messages for tiscale.hagent_input queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentRetryStateState for tiscale.hagent_retry queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentRetryConsNumber of consumers for tiscale.hagent_retry queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueuesHagentRetryMsgNumber of messages for tiscale.hagent_retry queueSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueueNameQueue nameSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueueSizeQueue sizeSpectra Detect Manager > Spectra Analyze > Queues table
tcbQueueThresholdQueue size exceeded configured thresholdSpectra Detect Manager > Spectra Analyze > Queues table
redundancyTriggerFailover on HA systemnot displayed (Spectra Analyze > redundancy)
redundancyTriggerOkHA System resumed operationnot displayed (Spectra Analyze > redundancy)
SNMPv2-MIB.txtsysNameAn administratively-assigned name for this managed node. By convention, this is the node’s fully-qualified domain name. If the name is unknown, the value is the zero-length string.Spectra Detect Manager > Spectra Analyze > System table
sysUpTimeThe time (in hundredths of a second) since the network management portion of the system was last re-initialized.Spectra Detect Manager > Spectra Analyze > System table
sysContactThe textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.not displayed
sysLocationThe physical location of this node (e.g., ‘telephone closet, 3rd floor’). If the location is unknown, the value is the zero-length string.Spectra Detect Manager > Spectra Analyze > System table
sysDescrA textual description of the entity. This value should include the full name and version identification of the system’s hardware type, software operating-system, and networking software.Spectra Detect Manager > Spectra Analyze > System table
HOST-RESOURCES-MIB.txthrProcessorLoadThe average, over the last minute, of the percentage of time that this processor was not idle. Implementations may approximate this one minute smoothing period if necessary.Spectra Detect Manager > Spectra Analyze > CPU table
hrStorageTableA (conceptual) entry for one logical storage area on the host. As an example, an instance of the hrStorageType object might be named hrStorageType.3Spectra Detect Manager > Spectra Analyze > Storage table
hrStorageSizeThe size of the storage represented by this entry, in units of hrStorageAllocationUnits. This object is writable to allow remote configuration of the size of the storage area in those cases where such an operation makes sense and is possible on the underlying system. For example, the amount of main memory allocated to a buffer pool might be modified or the amount of disk space allocated to virtual memory might be modified.Spectra Detect Manager > Spectra Analyze > Storage table
hrStorageTypeThe type of storage represented by this entry.Spectra Detect Manager > Spectra Analyze > Storage table
hrStorageUsedThe amount of the storage represented by this entry that is allocated, in units of hrStorageAllocationUnits.Spectra Detect Manager > Spectra Analyze > Storage table
hrStorageDescrA description of the type and instance of the storage described by this entry.Spectra Detect Manager > Spectra Analyze > Storage table
hrStorageAllocationUnitsThe size, in bytes, of the data objects allocated from this pool. If this entry is monitoring sectors, blocks, buffers, or packets, for example, this number will commonly be greater than one. Otherwise this number will typically be one.Spectra Detect Manager > Spectra Analyze > Storage table
UCD-SNMP-MIB.txtmemoryMemory usage/watch reporting object.Spectra Detect Manager > Spectra Analyze > Memory table
memIndexBogus Index. This should always return the integer 0.Spectra Detect Manager > Spectra Analyze > Memory table
memBufferThe total amount of real or virtual memory currently allocated for use as memory buffers. This object will not be implemented on hosts where the underlying operating system does not explicitly identify memory as specifically reserved for this purpose.Spectra Detect Manager > Spectra Analyze > Memory table
memCachedThe total amount of real or virtual memory currently allocated for use as cached memory. This object will not be implemented on hosts where the underlying operating system does not explicitly identify memory as specifically reserved for this purpose.Spectra Detect Manager > Spectra Analyze > Memory table
memAvailRealThe amount of real/physical memory currently unused or available.Spectra Detect Manager > Spectra Analyze > Memory table
memAvailSwapThe amount of swap space currently unused or available.Spectra Detect Manager > Spectra Analyze > Memory table
memErrorNameBogus Name. This should always return the string ‘swap’.Spectra Detect Manager > Spectra Analyze > Memory table
memTotalRealThe total amount of real/physical memory installed on this host.Spectra Detect Manager > Spectra Analyze > Memory table
memTotalSwapThe total amount of swap space configured for this host.Spectra Detect Manager > Spectra Analyze > Memory table
IF-MIB.txtifTypeThe type of interface. Additional values for ifType are assigned by the Internet Assigned Numbers Authority (IANA), through updating the syntax of the IANAifType textual convention.Spectra Detect Manager > Spectra Analyze > Network table
ifSpeedAn estimate of the interface’s current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those where no accurate estimation can be made, this object should contain the nominal bandwidth. If the bandwidth of the interface is greater than the maximum value reportable by this object then this object should report its maximum value (4,294,967,295) and ifHighSpeed must be used to report the interace’s speed. For a sub-layer which has no concept of bandwidth, this object should be zero.Spectra Detect Manager > Spectra Analyze > Network table
ifInOctetsThe total number of octets received on the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.Spectra Detect Manager > Spectra Analyze > Network table
ifOutOctetsThe total number of octets transmitted out of the interface, including framing characters. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.”Spectra Detect Manager > Spectra Analyze > Network table
ifDescrA textual string containing information about the interface. This string should include the name of the manufacturer, the product name and the version of the interface hardware/software.Spectra Detect Manager > Spectra Analyze > Network table
ifPhysAddressThe interface’s address at its protocol sub-layer. For example, for an 802.x interface, this object normally contains a MAC address. The interface’s media-specific MIB must define the bit and byte ordering and the format of the value of this object. For interfaces which do not have such an address (e.g., a serial line), this object should contain an octet string of zero length.Spectra Detect Manager > Spectra Analyze > Network table
ifOperStatusThe current operational state of the interface. The testing(3) state indicates that no operational packets can be passed. If ifAdminStatus is down(2) then ifOperStatus should be down(2). If ifAdminStatus is changed to up(1) then ifOperStatus should change to up(1) if the interface is ready to transmit and receive network traffic; it should change to dormant(5) if the interface is waiting for external actions (such as a serial line waiting for an incoming connection); it should remain in the down(2) state if and only if there is a fault that prevents it from going to the up(1) state; it should remain in the notPresent(6) state if the interface has missing (typically, hardware) components.Spectra Detect Manager > Spectra Analyze > Network table
ifAdminStatusThe desired state of the interface. The testing(3) state indicates that no operational packets can be passed. When a managed system initializes, all interfaces start with ifAdminStatus in the down(2) state. As a result of either explicit management action or per configuration information retained by the managed system, ifAdminStatus is then changed to either the up(1) or testing(3) states (or remains in the down(2) state).Spectra Detect Manager > Spectra Analyze > Network table