NCR-CORESSTSYSTEMLOG-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NCR-CORESSTSYSTEMLOG-MIB

Category: Network Management

Description: Manages system event log monitoring and SNMP notification delivery for NCR CORESS installations.

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 NCR-CORESSTSYSTEMLOG-MIB?

NCR-CORESSTSYSTEMLOG-MIB is a vendor MIB for NCR's CORESS (self-service terminal/retail transaction) platform, used to expose the device's system event log as SNMP table entries and to drive corresponding trap notifications. It models each log record with fields for the originating device and service name, transaction code, structured/message data payloads, and a human-readable description. Its primary monitoring purpose is software/service status and fault visibility: it lets a monitoring system detect application or service-level errors, transaction failures, or operational events logged by the terminal's software stack, effectively turning local log entries into remotely pollable and trap-able SNMP data. No strong dependency on external standard MIBs is evident; it appears to be a self-contained event-log representation. It is typically deployed on NCR self-service and retail terminal systems (e.g., ATMs, kiosks, POS-adjacent equipment) for centralized event monitoring. Network engineers evaluating or troubleshooting this functionality can download the NCR-CORESSTSYSTEMLOG-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in NCR-CORESSTSYSTEMLOG-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

  • NCR self-service terminal
  • retail/transaction kiosk or ATM-adjacent device

Monitoring Examples

A monitoring system would poll sstDeviceLogTable/sstLogEntry indexed by sstLogIndex, reading sstLogServiceName, sstLogTCode, and sstLogDescription to identify which service raised an event and what it means. A spike in log entries with a particular sstLogTCode value or repeated sstLogDescription text pointing to a hardware or transaction fault would trigger alerting for that terminal. sstLogSData and sstLogMData carry supplemental structured/message data that can be inspected for diagnostic detail beyond the plain-text description.

What Can Be Monitored

  • system log entries by index
  • originating service name
  • transaction/event code
  • log message description
  • structured log data payload
Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
enterprises

From RFC1213-MIB

DisplayString

From RFC1253-MIB

TruthValue
OIDs

RFC description

NCR Core SST system event log management with device, service, and error tracking.

Start monitoring NCR self-service terminal / retail kiosk (system event log) 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 NCR-CORESSTSYSTEMLOG-MIB