FSC-LOG3-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
45
Objects
Active
Status
5
Dependencies
Imported Objects
Objects
45 total| Object Name |
|---|
sni OBJECT IDENTIFIER .1.3.6.1.4.1.231 |
sniProductMibs OBJECT IDENTIFIER .1.3.6.1.4.1.231.2 |
fscLog3MIB OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46 |
log3Objects OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.1 |
log3Config OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.1.1 |
log3ConfigSubAgentVersionVersion of SNMP Agentro SnmpAdminString (SNMP-FRAMEWORK-MIB) .1.3.6.1.4.1.231.2.46.1.1.1 |
log3ConfigNotifyOperScopeSet 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.ro Enumeration .1.3.6.1.4.1.231.2.46.1.1.2 |
log3ConfigNotifyAdminScopeThe desired Scope of Information supplied by the subagentrw Enumeration .1.3.6.1.4.1.231.2.46.1.1.3 |
log3ConfigGlobalEntryLimitThe maximum number of notification entries. A value of 0 means no limitrw GlobalEntryLimit .1.3.6.1.4.1.231.2.46.1.1.4 |
log3Stats OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.1.2 |
log3StatsCurrentThe number of event posted by the agent.ro Counter .1.3.6.1.4.1.231.2.46.1.2.1 |
log3StatsMemoryThe memory in bytes used by the agent, to hold event informations.ro Gauge32 .1.3.6.1.4.1.231.2.46.1.2.2 |
log3StatsReceivedThe number of event received by the agent.ro Counter .1.3.6.1.4.1.231.2.46.1.2.3 |
log3Event OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.1.3 |
log3EventTableThe table of events. SEQUENCE OF Log3EventEntry .1.3.6.1.4.1.231.2.46.1.3.1 |
log3EventEntrylog3 event data Log3EventEntry .1.3.6.1.4.1.231.2.46.1.3.1.1 |
log3EventIndexThe 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.ro Gauge .1.3.6.1.4.1.231.2.46.1.3.1.1.1 |
log3EventComponentNumberA Number which uniquely identify a log3 Component.
The Numbers are assigned by log3 number authority
at FSC.ro Gauge .1.3.6.1.4.1.231.2.46.1.3.1.1.2 |
log3EventModuleNameA 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.3 |
log3EventObjectIDA string which describe the modules object, which send
log3 informations.
E.g. printer1.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.4 |
log3EventErrorNumberA integer which describes the error code.ro Gauge .1.3.6.1.4.1.231.2.46.1.3.1.1.5 |
log3EventErrorWeightA 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.ro Enumeration .1.3.6.1.4.1.231.2.46.1.3.1.1.6 |
log3EventProcessIdThe system OS process ID.ro ProcessID .1.3.6.1.4.1.231.2.46.1.3.1.1.7 |
log3EventReleaseVersionComponents release and version number.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.8 |
log3EventSystemNameEvent 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.9 |
log3EventNodeNamelog3 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.10 |
log3EventFirstTimeTime, where event first occurred.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.11 |
log3EventSequencea 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.ro Counter16 .1.3.6.1.4.1.231.2.46.1.3.1.1.12 |
log3EventRepeatsIf a event keep going and no other event happens meanwhile,
the event will be counted.ro Counter16 .1.3.6.1.4.1.231.2.46.1.3.1.1.13 |
log3EventLastTimeTime, where event last occurred.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.14 |
log3EventUserIDThe host OS UserID.ro UserID .1.3.6.1.4.1.231.2.46.1.3.1.1.15 |
log3EventUserNameThe user who log the event.
This is the UserID, decoded by the host OS.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.16 |
log3EventGroupIDThe host OS GroupID.ro GroupID .1.3.6.1.4.1.231.2.46.1.3.1.1.17 |
log3EventGroupNameThe group, where the user belong to.
This is the log3GroupID, decoded by the host OS.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.231.2.46.1.3.1.1.18 |
log3EventMessageTextThis is the message, which the component will log.
This message describe in detail what was happen. The component
is responsible for the text content.ro MessageString .1.3.6.1.4.1.231.2.46.1.3.1.1.19 |
log3Notifications OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.2 |
log3Traps OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.2.0 |
log3Conformance OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3 |
log3Compliances OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3.1 |
log3Compliance OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3.1.1 |
log3Groups OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3.2 |
log3ConfigGroup OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3.2.1 |
log3StatsGroup OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3.2.2 |
log3EventGroup OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3.2.3 |
log3NoticeGroup OBJECT IDENTIFIER .1.3.6.1.4.1.231.2.46.3.2.4 |