All MIBs › NCR-CORESSTSWARELOG-MIB
Category: Network Management
Description: Defines software event log notifications and alert objects for NCR CORESS transaction processing platforms.
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-CORESSTSWARELOG-MIB?
NCR-CORESSTSWARELOG-MIB is an NCR enterprise MIB defining software event log notifications and alert objects for NCR CORESS transaction-processing/self-service (retail or ATM/POS-style) platforms. It exposes a software event log table capturing detailed diagnostic entries such as source name, process and thread name, DLL name, event ID, severity level, and reason text for each logged software event. Its monitoring emphasis is squarely on software/process health: it lets an operator track application-level faults, exceptions, or warnings emitted by specific processes, threads, or DLLs within the transaction-processing software stack, which is critical for detecting failing services or software regressions on the platform. It is a self-contained software-logging MIB likely paired with hardware-status MIBs for the same NCR CORESS platform in a full monitoring deployment. It is deployed on NCR CORESS retail/financial self-service transaction processing systems (e.g., point-of-sale or ATM-adjacent platforms) where software reliability is monitored via SNMP. Engineers can download the NCR-CORESSTSWARELOG-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in NCR-CORESSTSWARELOG-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 CORESS transaction processing / self-service platform
Monitoring Examples
An operator polls sstSWareLogTable/sstSWareLogEntry indexed by sstSWareLogIndex and sstSWareLogLineNumber, reading sstSWareLogSourceName, sstSWareLogProcName, and sstSWareLogThrdName alongside sstSWareLogLevel and sstSWareLogReason to pinpoint which process or thread logged a severe software error. Correlating repeated entries from the same sstSWareLogDLLName with the same sstSWareLogEventId would reveal a recurring software fault in a specific module, prompting a targeted patch or restart of that transaction-processing component.
What Can Be Monitored
- software event log entries
- event severity level
- source process/thread/DLL name
- event ID and reason text
- log line/index sequence
Imported Objects
From RFC-1212
| OBJECT-TYPE |
From RFC1155-SMI
| Counter | |
| enterprises |
From RFC1213-MIB
| DisplayString |
From RFC1253-MIB
| TruthValue |
OIDs
RFC description
Tracks software event logs with source, thread, and binary data information from NCR SST systems.
Start monitoring NCR CORESS self-service platforms 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.