APSYSLOG-MIB
AI MIB Summary
The APSYSLOG-MIB enables SNMP-based retrieval of syslog event data and system log entries from Acme Packet session border controllers and media gateways. It facilitates the monitoring of critical operational events, including call session states, protocol errors, and device health alerts, by exposing these logs as standardized MIB objects for centralized logging and alarm correlation.
The syslog MIB for Acme Packet
Main OID:
apSyslogModule.1.3.6.1.4.1.9148.3.1
27
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
27 total| Object Name |
|---|
apSyslogModuleThe syslog MIB for Acme Packet MODULE-IDENTITY .1.3.6.1.4.1.9148.3.1 |
apSyslogMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.1 |
apSyslogBasic OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.1.1 |
apSyslogNotificationsSentThe number of apSyslogMessageGenerated notifications that have been sent. This number may include notifications that were prevented from being transmitted due to reasons such as resource limitations and/or non-connectivity. If one is receiving notifications, one can periodically poll this object to determine if any notifications were missed. If so, a poll of the apSyslogHistoryTable might be appropriate.ro Counter32 UNITS "notifications" .1.3.6.1.4.1.9148.3.1.1.1.1 |
apSyslogNotificationsEnabledIndicates whether apSyslogMessageGenerated notifications will or will not be sent when a syslog message is generated by the device. Disabling notifications does not prevent syslog messages from being added to the apSyslogHistoryTable.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9148.3.1.1.1.2 |
apSyslogMaxLevelIndicates which syslog severity levels will be processed. Any syslog message with a Log-level value greater than this value will be ignored by the agent. note: severity numeric values increase as their severity decreases, e.g. major(3) is more severe than debug(8).rw SyslogLevel .1.3.6.1.4.1.9148.3.1.1.1.3 |
apSyslogMsgIgnoresThe number of syslog messages which were ignored, means no need to send apSyslog apSyslogMessageGenerated notification. A message will be ignored if it has a Log-Level value greater than apSyslogMaxSeverity.ro Counter32 UNITS "messages" .1.3.6.1.4.1.9148.3.1.1.1.4 |
apSyslogMsgDropsThe number of syslog messages which could not be processed due to lack of system resources. Most likely this will occur at the same time that syslog messages are generated to indicate this lack of resources. Increases in this object's value may serve as an indication that system resource levels should be examined via other mib objects. A message that is dropped will not appear in the history table and no notification will be sent for this message.ro Counter32 UNITS "messages" .1.3.6.1.4.1.9148.3.1.1.1.5 |
apSyslogHistory OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.1.2 |
apSyslogHistTableMaxLengthThe upper limit on the number of entries that the apSyslogHistoryTable may contain. A value of 0 will prevent any history from being retained. When this table is full, the oldest entry will be deleted and a new one will be created.rw Integer32 .1.3.6.1.4.1.9148.3.1.1.2.1 |
apSyslogHistMsgsFlushedThe number of entries that have been removed from the apSyslogHistoryTable in order to make room for new entries. This object can be utilized to determine whether your polling frequency on the history table is fast enough and/or the size of your history table is large enough such that you are not missing messages.ro Counter32 UNITS "messages" .1.3.6.1.4.1.9148.3.1.1.2.2 |
apSyslogHistoryTableA table of syslog messages generated by this device. All 'interesting' syslog messages (i.e. Log-Level <= apSyslogMaxLevel) are entered into this table. SEQUENCE OF ApSyslogHistoryEntry .1.3.6.1.4.1.9148.3.1.1.2.3 |
apSyslogHistoryEntryA syslog message that was previously generated by this device. Each entry is indexed by a message index. ApSyslogHistoryEntry .1.3.6.1.4.1.9148.3.1.1.2.3.1 |
apSyslogHistIndexA monotonically increasing integer for the sole purpose of indexing messages. When it reaches the maximum value the agent wraps the value back to 1.ro Integer32 .1.3.6.1.4.1.9148.3.1.1.2.3.1.1 |
apSyslogHistFromThe process name and host of the sending client. For example: 'anyclient@sr.acme.com'.ro DisplayString .1.3.6.1.4.1.9148.3.1.1.2.3.1.2 |
apSyslogHistLevelThe Log-Level of the message.ro SyslogLevel .1.3.6.1.4.1.9148.3.1.1.2.3.1.3 |
apSyslogHistTypeA textual identification for the Log-Type, which categorizes the log message.ro DisplayString .1.3.6.1.4.1.9148.3.1.1.2.3.1.4 |
apSyslogHistContentThe text of the message. If the text of the message exceeds 255 bytes, the message will be truncated to 255 bytes.ro DisplayString .1.3.6.1.4.1.9148.3.1.1.2.3.1.5 |
apSyslogHistTimestampThe value of sysUpTime when this message was generated.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9148.3.1.1.2.3.1.6 |
apSyslogMIBNotificationPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.2 |
apSyslogMIBNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.2.0 |
apSyslogMessageGeneratedWhen a syslog message is generated by the device a apSyslogMessageGenerated notification is sent. The sending of these notifications can be enabled/disabled via the apSyslogNotificationsEnabled object. NOTIFICATION-TYPE .1.3.6.1.4.1.9148.3.1.2.0.1 |
apSyslogMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.3 |
apSyslogMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.3.1 |
apSyslogMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9148.3.1.3.2 |
apSyslogGroupA collection of objects providing the syslog MIB capability. Unknown .1.3.6.1.4.1.9148.3.1.3.2.1 |
apSyslogNotificationsGroupA collection of notifications describing license violation. Unknown .1.3.6.1.4.1.9148.3.1.3.2.2 |