FSC-LOG3-MIB

All MIBs › FSC-LOG3-MIB

Description: FSC-LOG3-MIB module

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 FSC-LOG3-MIB?

FSC-LOG3-MIB is a Fujitsu Siemens Computers (FSC/Siemens Nixdorf lineage, "sni" root) proprietary MIB module implementing a generic event-logging subsystem for FSC server and network hardware. It exposes an event log table capturing individual system events along with statistics on the log's current size, memory usage, and total events received, plus configuration objects controlling logging scope and retention limits. This MIB is squarely a software/hardware status-monitoring tool: it lets administrators track how many events have been logged, how full the log buffer is, and inspect individual log entries (including component and originating module) that typically record hardware faults, configuration changes, or subsystem errors as they occur. As part of the broader FSC/Siemens SNI enterprise MIB tree, it likely depends on companion FSC MIBs for identifying the specific hardware component or subsystem referenced by each log entry. It is typically deployed for centralized event/fault monitoring on Fujitsu Siemens/Fujitsu PRIMERGY-class servers and related network equipment. Network engineers evaluating or troubleshooting this functionality can download the FSC-LOG3-MIB file directly to load it into their MIB browser.

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

Fujitsu Siemens (FSC) PRIMERGY servers and related network hardware

Monitoring Examples

An administrator would poll log3StatsCurrent, log3StatsMemory, and log3StatsReceived to track how many log entries are currently stored, memory consumed by the log, and the total event count received, watching for a log nearing log3ConfigGlobalEntryLimit which could indicate an event storm. Walking log3EventTable/log3EventEntry, keyed by log3EventIndex, reveals individual events with log3EventComponentNumber and log3EventModuleName identifying which hardware component or software module raised the condition. log3ConfigNotifyOperScope and log3ConfigNotifyAdminScope would be checked to confirm which severity levels are configured to trigger SNMP notifications for real-time fault alerting.

What Can Be Monitored

event log entry count
log memory usage
total events received
individual event details (component/module)
notification scope configuration
global log entry limit

Imported Objects

From RFC1155-SMI

Counter
Gauge
enterprises

From RFC1213-MIB

mib-2

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

NOTIFICATION-GROUP

From SNMPv2-SMI

Counter64

From SNMPv2-TC

DateAndTime
DisplayString

How to Use in IPNetwork Monitor

Example using log3StatsCurrent OID:

Select a Fujitsu Siemens Computers (FSC)/Fujitsu PRIMERGY server/network hardware (event log) 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 log3StatsCurrent into the Find box to locate it in the OID tree, then select it and click OK. The number of event posted by the agent. 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, 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
sni	1.3.6.1.4.1.231
sniProductMibs	1.3.6.1.4.1.231.2
fscLog3MIB	1.3.6.1.4.1.231.2.46
log3Objects	1.3.6.1.4.1.231.2.46.1
log3Config	1.3.6.1.4.1.231.2.46.1.1
STR log3ConfigSubAgentVersion	1.3.6.1.4.1.231.2.46.1.1.1	SnmpAdminString	read-only	Version of SNMP Agent
INT log3ConfigNotifyOperScope	1.3.6.1.4.1.231.2.46.1.1.2	INTEGER	read-only	Set of Notifications sent by the subagent: - unknown: The Information cannot be supplied. - other: The Information does not correspond to the other enumerated values. - all: The subagent sends notifications for all events. - local: The subagent sends notifications for all events concerning a subset of systems including the local node. - no: The subagent sends no notifications.
INT log3ConfigNotifyAdminScope	1.3.6.1.4.1.231.2.46.1.1.3	INTEGER	read-write	The desired Scope of Information supplied by the subagent
GLO log3ConfigGlobalEntryLimit	1.3.6.1.4.1.231.2.46.1.1.4	GlobalEntryLimit	read-write	The maximum number of notification entries. A value of 0 means no limit
log3Stats	1.3.6.1.4.1.231.2.46.1.2
CTR log3StatsCurrentEx	1.3.6.1.4.1.231.2.46.1.2.1	Counter	read-only	The number of event posted by the agent.
G32 log3StatsMemory	1.3.6.1.4.1.231.2.46.1.2.2	Gauge32	read-only	The memory in bytes used by the agent, to hold event informations.
CTR log3StatsReceived	1.3.6.1.4.1.231.2.46.1.2.3	Counter	read-only	The number of event received by the agent.
log3Event	1.3.6.1.4.1.231.2.46.1.3
log3EventTable	1.3.6.1.4.1.231.2.46.1.3.1		not-accessible	The table of events.
log3EventEntry	1.3.6.1.4.1.231.2.46.1.3.1.1		not-accessible	log3 event data
GAU log3EventIndex	1.3.6.1.4.1.231.2.46.1.3.1.1.1	Gauge	read-only	The index into the event list. MAX-ACCESS is not set to not-accessible, that the agent can send the Index in Notifications. This maybe helpfull for SNMP managers.
GAU log3EventComponentNumber	1.3.6.1.4.1.231.2.46.1.3.1.1.2	Gauge	read-only	A Number which uniquely identify a log3 Component. The Numbers are assigned by log3 number authority at FSC.
STR log3EventModuleName	1.3.6.1.4.1.231.2.46.1.3.1.1.3	DisplayString	read-only	A string which describes the module, which send log3 informations. One module may have more then one object. E.g. spool module may have objects printer1 and printer2.
STR log3EventObjectID	1.3.6.1.4.1.231.2.46.1.3.1.1.4	DisplayString	read-only	A string which describe the modules object, which send log3 informations. E.g. printer1.
GAU log3EventErrorNumber	1.3.6.1.4.1.231.2.46.1.3.1.1.5	Gauge	read-only	A integer which describes the error code.
INT log3EventErrorWeight	1.3.6.1.4.1.231.2.46.1.3.1.1.6	INTEGER	read-only	A integer which describes the components error priority. Components should use syslog(3) priority. Compoments which use illegal priorities above debug(8) are mapped to other(9). A components error priority maybe FATAL, but this does not implies that the error is FATAL for the system.
PRO log3EventProcessId	1.3.6.1.4.1.231.2.46.1.3.1.1.7	ProcessID	read-only	The system OS process ID.
STR log3EventReleaseVersion	1.3.6.1.4.1.231.2.46.1.3.1.1.8	DisplayString	read-only	Components release and version number.
STR log3EventSystemName	1.3.6.1.4.1.231.2.46.1.3.1.1.9	DisplayString	read-only	Event reporting system name. If a system reports log3 events to a other system, which collect all log3 events, this is the name of the system, where the events occurred.
STR log3EventNodeName	1.3.6.1.4.1.231.2.46.1.3.1.1.10	DisplayString	read-only	log3 reporting system name. If a system reports log3 events to a other system, which collect all log3 events, this is the name of the system, which collect events from other systems.
DAT log3EventFirstTime	1.3.6.1.4.1.231.2.46.1.3.1.1.11	DateAndTime	read-only	Time, where event first occurred.
NUM log3EventSequence	1.3.6.1.4.1.231.2.46.1.3.1.1.12	Counter16	read-only	a log3 internal sequence number. This number could be used to find the sequence of events, if more then one events happens in one second. log3 is responsible to hold this counter consistent.
NUM log3EventRepeats	1.3.6.1.4.1.231.2.46.1.3.1.1.13	Counter16	read-only	If a event keep going and no other event happens meanwhile, the event will be counted.
DAT log3EventLastTime	1.3.6.1.4.1.231.2.46.1.3.1.1.14	DateAndTime	read-only	Time, where event last occurred.
USE log3EventUserID	1.3.6.1.4.1.231.2.46.1.3.1.1.15	UserID	read-only	The host OS UserID.
STR log3EventUserName	1.3.6.1.4.1.231.2.46.1.3.1.1.16	DisplayString	read-only	The user who log the event. This is the UserID, decoded by the host OS.
GRO log3EventGroupID	1.3.6.1.4.1.231.2.46.1.3.1.1.17	GroupID	read-only	The host OS GroupID.
STR log3EventGroupName	1.3.6.1.4.1.231.2.46.1.3.1.1.18	DisplayString	read-only	The group, where the user belong to. This is the log3GroupID, decoded by the host OS.
STR log3EventMessageText	1.3.6.1.4.1.231.2.46.1.3.1.1.19	MessageString	read-only	This is the message, which the component will log. This message describe in detail what was happen. The component is responsible for the text content.
log3Notifications	1.3.6.1.4.1.231.2.46.2
log3Traps	1.3.6.1.4.1.231.2.46.2.0
NTF log3EmergencyNotice	1.3.6.1.4.1.231.2.46.2.0.1			Information send to the management station.
NTF log3AlertNotice	1.3.6.1.4.1.231.2.46.2.0.2			Information send to the management station.
NTF log3CriticalNotice	1.3.6.1.4.1.231.2.46.2.0.3			Information send to the management station.
NTF log3ErrorNotice	1.3.6.1.4.1.231.2.46.2.0.4			Information send to the management station.
NTF log3WarningNotice	1.3.6.1.4.1.231.2.46.2.0.5			Information send to the management station.
NTF log3NoticeNotice	1.3.6.1.4.1.231.2.46.2.0.6			Information send to the management station.
NTF log3InformationalNotice	1.3.6.1.4.1.231.2.46.2.0.7			Information send to the management station.
NTF log3DebugNotice	1.3.6.1.4.1.231.2.46.2.0.8			Information send to the management station.
NTF log3OtherNotice	1.3.6.1.4.1.231.2.46.2.0.9			Information send to the management station.
log3Conformance	1.3.6.1.4.1.231.2.46.3
log3Compliances	1.3.6.1.4.1.231.2.46.3.1
log3Compliance	1.3.6.1.4.1.231.2.46.3.1.1
log3Groups	1.3.6.1.4.1.231.2.46.3.2
log3ConfigGroup	1.3.6.1.4.1.231.2.46.3.2.1
log3StatsGroup	1.3.6.1.4.1.231.2.46.3.2.2
log3EventGroup	1.3.6.1.4.1.231.2.46.3.2.3
log3NoticeGroup	1.3.6.1.4.1.231.2.46.3.2.4

RFC description

Provides SNMP agent version and logging configuration objects for Fujitsu Siemens servers.

Start monitoring Fujitsu Siemens Computers (FSC)/Fujitsu PRIMERGY server/network hardware (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 FSC-LOG3-MIB