APSYSLOG-MIB

All MIBs › APSYSLOG-MIB

Organization: Acme Packet, Inc

Last Updated: 2000-06-21

Category: Telephony and VoIP, Vendor: Acme Packet

Description: Acme Packet SBC syslog facility configuration and remote logging server management.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is APSYSLOG-MIB?

APSYSLOG-MIB is a proprietary Acme Packet SBC module for configuring and monitoring the device's syslog subsystem, including remote logging severity thresholds and message history. It exposes counters for notifications sent and enabled, the configured maximum severity level, counts of ignored and dropped messages, and a bounded history table of recent syslog messages with their source and severity. This is a software-health monitoring module in the sense that it reveals whether the logging pipeline itself is healthy: a rising apSyslogMsgDrops or apSyslogMsgIgnores count indicates the device is losing diagnostic messages, which could mask other faults. It is a self-contained vendor module that complements, rather than replaces, the standard SNMP notification framework used for its own apSyslogNotificationsSent/Enabled objects. It is deployed on Acme Packet SBCs wherever centralized syslog collection and message-history auditing are required. Engineers can download the APSYSLOG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in APSYSLOG-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Acme Packet Session Border Controller (SBC)

Monitoring Examples

An operator would poll apSyslogNotificationsSent and apSyslogNotificationsEnabled to confirm syslog-based SNMP notifications are active, and watch apSyslogMsgDrops and apSyslogMsgIgnores for signs the device is discarding log messages faster than expected. The apSyslogHistoryTable, indexed by apSyslogHistIndex with apSyslogHistFrom and apSyslogHistLevel fields, lets an admin review recent high-severity messages up to apSyslogHistTableMaxLength entries. A sustained increase in apSyslogMsgDrops alongside apSyslogHistMsgsFlushed would indicate the local history buffer is overflowing and messages are being lost before collection.

What Can Be Monitored

syslog messages sent/dropped/ignored
configured maximum log severity level
syslog message history
history buffer flush/overflow counts

Imported Objects

From ACMEPACKET-SMI

acmepacketMgmt

OBJECT-IDENTITY

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using apSyslogNotificationsSent OID:

Select an Acme Packet Session Border Controller (SBC) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type apSyslogNotificationsSent into the Find box to locate it in the OID tree, then select it and click OK. The number of apSyslogMessageGenerated notifications that have been sent. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in notifications), since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
apSyslogModule	1.3.6.1.4.1.9148.3.1			The syslog MIB for Acme Packet
apSyslogMIBObjects	1.3.6.1.4.1.9148.3.1.1
apSyslogBasic	1.3.6.1.4.1.9148.3.1.1.1
C32 apSyslogNotificationsSentEx	1.3.6.1.4.1.9148.3.1.1.1.1	Counter32	read-only	The 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.
T/F apSyslogNotificationsEnabled	1.3.6.1.4.1.9148.3.1.1.1.2	TruthValue	read-write	Indicates 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.
SYS apSyslogMaxLevel	1.3.6.1.4.1.9148.3.1.1.1.3	SyslogLevel	read-write	Indicates 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).
C32 apSyslogMsgIgnores	1.3.6.1.4.1.9148.3.1.1.1.4	Counter32	read-only	The 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.
C32 apSyslogMsgDrops	1.3.6.1.4.1.9148.3.1.1.1.5	Counter32	read-only	The 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.
apSyslogHistory	1.3.6.1.4.1.9148.3.1.1.2
I32 apSyslogHistTableMaxLength	1.3.6.1.4.1.9148.3.1.1.2.1	Integer32	read-write	The 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.
C32 apSyslogHistMsgsFlushed	1.3.6.1.4.1.9148.3.1.1.2.2	Counter32	read-only	The 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.
apSyslogHistoryTable	1.3.6.1.4.1.9148.3.1.1.2.3		not-accessible	A table of syslog messages generated by this device. All 'interesting' syslog messages (i.e. Log-Level <= apSyslogMaxLevel) are entered into this table.
apSyslogHistoryEntry	1.3.6.1.4.1.9148.3.1.1.2.3.1		not-accessible	A syslog message that was previously generated by this device. Each entry is indexed by a message index.
I32 apSyslogHistIndex	1.3.6.1.4.1.9148.3.1.1.2.3.1.1	Integer32	read-only	A monotonically increasing integer for the sole purpose of indexing messages. When it reaches the maximum value the agent wraps the value back to 1.
STR apSyslogHistFrom	1.3.6.1.4.1.9148.3.1.1.2.3.1.2	DisplayString	read-only	The process name and host of the sending client. For example: 'anyclient@sr.acme.com'.
SYS apSyslogHistLevel	1.3.6.1.4.1.9148.3.1.1.2.3.1.3	SyslogLevel	read-only	The Log-Level of the message.
STR apSyslogHistType	1.3.6.1.4.1.9148.3.1.1.2.3.1.4	DisplayString	read-only	A textual identification for the Log-Type, which categorizes the log message.
STR apSyslogHistContent	1.3.6.1.4.1.9148.3.1.1.2.3.1.5	DisplayString	read-only	The text of the message. If the text of the message exceeds 255 bytes, the message will be truncated to 255 bytes.
TIM apSyslogHistTimestamp	1.3.6.1.4.1.9148.3.1.1.2.3.1.6	TimeStamp	read-only	The value of sysUpTime when this message was generated.
apSyslogMIBNotificationPrefix	1.3.6.1.4.1.9148.3.1.2
apSyslogMIBNotifications	1.3.6.1.4.1.9148.3.1.2.0
NTF apSyslogMessageGenerated	1.3.6.1.4.1.9148.3.1.2.0.1			When 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.
apSyslogMIBConformance	1.3.6.1.4.1.9148.3.1.3
apSyslogMIBCompliances	1.3.6.1.4.1.9148.3.1.3.1
apSyslogMIBGroups	1.3.6.1.4.1.9148.3.1.3.2
apSyslogGroup	1.3.6.1.4.1.9148.3.1.3.2.1			A collection of objects providing the syslog MIB capability.
apSyslogNotificationsGroup	1.3.6.1.4.1.9148.3.1.3.2.2			A collection of notifications describing license violation.

RFC description

Collects and manages syslog messages from Acme Packet Session Routers and Media Routers.

Start monitoring Acme Packet Session Border Controller (SBC) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download APSYSLOG-MIB