BN-LOG-MESSAGE-MIB
File:
BN-LOG-MESSAGE-MIB.mib (34186 bytes)
Imported modules
Imported symbols
Defined Types
BnLogMsgBufferEntry |
|
SEQUENCE |
|
|
|
|
bnLogMsgBufferMsgIndex |
Integer32 |
|
|
bnLogMsgBufferMsgOrig |
Integer32 |
|
|
bnLogMsgBufferMsgTime |
TimeTicks |
|
|
bnLogMsgBufferMsgSrc |
INTEGER |
|
|
bnLogMsgBufferMsgCode |
Integer32 |
|
|
bnLogMsgBufferMsgString |
DisplayString |
|
|
bnLogMsgBufferMsgParam1 |
Integer32 |
|
|
bnLogMsgBufferMsgParam2 |
Integer32 |
|
|
bnLogMsgBufferMsgParam3 |
Integer32 |
|
|
bnLogMsgBufferMsgUtcTime |
DateAndTime |
|
|
bnLogMsgBufferMsgType |
INTEGER |
|
BnLogMsgRemoteServerEntry |
|
SEQUENCE |
|
|
|
|
bnLogMsgRemoteServerAddressType |
InetAddressType |
|
|
bnLogMsgRemoteServerAddress |
InetAddress |
|
|
bnLogMsgRemoteServerEnabled |
TruthValue |
|
|
bnLogMsgRemoteServerSaveTargets |
INTEGER |
|
|
bnLogMsgRemoteServerRowStatus |
RowStatus |
|
|
bnLogMsgRemoteServerStandardSaveTargets |
INTEGER |
|
Defined Values
bnLogMsgMIB |
1.3.6.1.4.1.45.1.6.16.1 |
The management information definitions for the
Bay Networks log message facility. |
MODULE-IDENTITY |
|
|
|
bnLogMsgBufferOperaton |
1.3.6.1.4.1.45.1.6.16.1.1.1 |
The decision to store or discard generated log
messages is determined by the value of this object.
Specifying on(1) causes log messages to be stored
in the log message buffer facility according to the
parameters specified by related management objects
in this module. Specifying off(2) discontinues log
message accumulation. Previously collected log
messages remained stored in the buffer facility
until they are manually cleared or the system is
reset. Resets do not clear log messages that have
been saved in non-volatile storage.
Note that this object does not affect operation
of the remote syslog facility, it only determines
whether log messages are stored locally. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
on(1), off(2) |
|
bnLogMsgBufferMaxSize |
1.3.6.1.4.1.45.1.6.16.1.1.2 |
This object determines the overall size of the log
message buffer facilities. Changing the value of this
object causes all messages currently being stored in
the buffer to be lost. Note that attempts to set this
object to a larger value (e.g., msgBufferSizeSmall(50)
to msgBufferSizeLarge(200)) may be rejected due to
current resource utiliztion within the running system.
Note that this object only applies to the buffering
capabilities that are volatile. Messages that are
classified as volatile are lost upon system
reinitialization. This object has no affect on
non-volatile message logging capacity. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgBufferSizeSmall(50), msgBufferSizeMedium(100), msgBufferSizeLarge(200), msgBufferSizeVeryLarge(400) |
|
bnLogMsgBufferCurSize |
1.3.6.1.4.1.45.1.6.16.1.1.3 |
The current number of log messages in the volatile
portion of the system log message facility. Messages
that are classified as volatile are lost upon system
reinitialization. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
0..200 |
|
bnLogMsgBufferFullAction |
1.3.6.1.4.1.45.1.6.16.1.1.4 |
The amount of buffer space allocated for log messages,
as determined by the object bnLogMsgBufferMaxSize, is
finite and thus only a limited amount of log messages
may be saved on the device. This object specifies the
action to take when this space is exhausted. Selecting
overwrite(1) will cause previous messages to be over-
written. Messages are overwritten based on FIFO.
Specifying latch(2) causes no more messages to be
saved until this object is changed to overwrite(1) or
until the buffer space is made available through some
other means (e.g., clearing the buffer).
Note that this object only pertains to messages that
are maintained in volatile storage. Messages that are
saved in non-volatile storage are never overwritten.
They must be cleared manually using the object
bnLogMsgBufferClearTargets. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
overwrite(1), latch(2) |
|
bnLogMsgBufferSaveTargets |
1.3.6.1.4.1.45.1.6.16.1.1.5 |
This object determines the type of log messages that
will be saved in the log message buffer facilities.
Messages are classified based on their type
Selecting a type of msgTypeCritical(1), msgTypeSerious(2),
or msgTypeInformational(3), causes all log messages that
have an associated value less than or equal to the type
value specified to be saved when the log message is
entered into the system. For example, specifying
the value msgTypeCritical(1) causes only messages
classified as 'critical' to be saved to non-volatile
storage. Specifying msgTypeSerious(2) causes 'critical'
and 'serious' messages to be saved.
Specifying a value of msgTypeNone(4) means no log messages
will be stored in volatile memory. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeCritical(1), msgTypeSerious(2), msgTypeInformational(3), msgTypeNone(4) |
|
bnLogMsgBufferClearTargets |
1.3.6.1.4.1.45.1.6.16.1.1.6 |
This object determines the type of log messages that
will be deleted from the log message buffer facilities
when the action object bnLogMsgBufferClearMsgs is set.
Messages are classified based on their type. Specifying
msgTypeAllVolatile(4) causes all messages in volatile
storage to be deleted. Specifying msgTypeNonVolatile(5)
causes all messages, including those in non-volatile
storage, to be discarded. |
Status: deprecated |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeCritical(1), msgTypeSerious(2), msgTypeInformational(3), msgTypeAllVolatile(4), msgTypeNonVolatile(5) |
|
bnLogMsgBufferClearMsgs |
1.3.6.1.4.1.45.1.6.16.1.1.7 |
Setting this object to clearMsgs(1) causes messages
currently saved in the log message buffer facilities
to be deleted. The type of entries to be deleted is
determined by the bnLogMsgBufferClearTargets object.
This object always returns the value savingMsgs(2)
upon retrieval. |
Status: deprecated |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
clearMsgs(1), savingMsgs(2) |
|
bnLogMsgBufferNonVolCurSize |
1.3.6.1.4.1.45.1.6.16.1.1.8 |
The current number of log messages that are present
in the non-volatile portion of the system log message
facility. Messages that are classified as non-
volatile are saved across system reinitializations. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
0..50 |
|
bnLogMsgBufferNonVolSaveTargets |
1.3.6.1.4.1.45.1.6.16.1.1.9 |
This object determines the type of log messages that
will be saved to non-volatile storage when they occur.
Messages are classified based on their type. Selecting
a type value causes all log messages that have an
associated value less than or equal to the type
value specified to be saved when the log message is
entered into the system. For example, specifying
the value msgTypeCritical(1) causes only messages
classified as 'critical' to be saved to non-volatile
storage. Specifying msgTypeSerious(2) causes 'critical'
and 'serious' messages to be saved. Specifying
msgTypeNone(4) causes no messages to be saved.
Note that non-volatile storage space is quite limited
in many systems such that the user should exercise
caution when specifying the type of log messages that
are to be saved in non-volatile storage. Messages are
no longer saved in non-volatile storage when this
space is exhausted. A log message is automatically
generated to alert the user of this situation. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeCritical(1), msgTypeSerious(2), msgTypeInformational(3), msgTypeNone(4) |
|
bnLogMsgBufferEntry |
1.3.6.1.4.1.45.1.6.16.1.1.10.1 |
Information on a particular event as described by
a log message and related information. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
BnLogMsgBufferEntry |
|
|
bnLogMsgBufferMsgIndex |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.1 |
The arbitrary integer index assigned to the log
message upon entry into the message facility. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
Integer32 |
0..2147483647 |
|
bnLogMsgBufferMsgOrig |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.2 |
The originator of the log message. Typically, this
value represents the slot or unit on which this
message originated. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
Integer32 |
0..2147483647 |
|
bnLogMsgBufferMsgTime |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.3 |
The time (in hundredths of a second) between system
initialization and the time this log message was
entered into the system. This object is the second
component in an index into this table to support
retrieving messages ordered by time of occurrence. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
TimeTicks |
|
|
bnLogMsgBufferMsgSrc |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.4 |
The message source indicates whether this message
was loaded from non-volatile storage at system
initialization or whether the message has been
generated since this time. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgSrcRunning(1), msgSrcNonVol(2) |
|
bnLogMsgBufferMsgCode |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.5 |
The message code indicating the originator of and
the reason why a log message has been generated.
This code, coupled with the log message parameters
that are associated with the message, should provide
a thorough understanding of the log message. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
bnLogMsgBufferMsgString |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.6 |
A printable string indicating the originator of and
the reason why a log message has been generated.
This string, coupled with the log message parameters
that are associated with the message, should provide
a thorough understanding of the log message. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DisplayString |
|
|
bnLogMsgBufferMsgParam1 |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.7 |
A parameter that is used to convey additional
information about a particular occurrence that
has initiated the generation of a log message.
The value of this is object is pertinent only
under the context of additional information in
the log entry (i.e., bnLogMsgBufferMsgCode). |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
bnLogMsgBufferMsgParam2 |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.8 |
A parameter that is used to convey additional
information about a particular occurrence that
has initiated the generation of a log message.
The value of this is object is pertinent only
under the context of additional information in
the log entry (i.e., bnLogMsgBufferMsgCode). |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
bnLogMsgBufferMsgParam3 |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.9 |
A parameter that is used to convey additional
information about a particular occurrence that
has initiated the generation of a log message.
The value of this is object is pertinent only
under the context of additional information in
the log entry (i.e., bnLogMsgBufferMsgCode). |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
Integer32 |
|
|
bnLogMsgBufferMsgUtcTime |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.10 |
Contains the system's local value of UTC (Universal
Coordinated Time) when the log entry was created. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
DateAndTime |
|
|
bnLogMsgBufferMsgType |
1.3.6.1.4.1.45.1.6.16.1.1.10.1.11 |
The message type indicates whether this message
is classified as 'critical', 'serious' or
'informational'. |
Status: current |
Access: read-only |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeCritical(1), msgTypeSerious(2), msgTypeInformational(3), msgTypeNone(4) |
|
bnLogMsgRemoteSyslogEnabled |
1.3.6.1.4.1.45.1.6.16.1.1.11 |
This object controls whether remote logging of
log messages using the remote syslog facility
is enabled. The value of this object may not
be true(2) if the value of the remote syslog
address object is 0.0.0.0. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
TruthValue |
|
|
bnLogMsgRemoteSyslogAddress |
1.3.6.1.4.1.45.1.6.16.1.1.12 |
The IP address to which log messages are sent
using the remote syslog facility. If the value
of this object is 0.0.0.0, the refer to the values
of bnLogMsgRemoteSyslogInetAddressType and
bnLogMsgRemoteSyslogInetAddress. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
IpAddress |
|
|
bnLogMsgRemoteSyslogSaveTargets |
1.3.6.1.4.1.45.1.6.16.1.1.13 |
This object determines the type of log messages that
will be sent to a remote syslog server when they occur.
Messages are classified based on their type. Selecting
a type value causes all log messages that have an
associated value less than or equal to the type
value specified to be sent when the log message is
entered into the system. For example, specifying
the value msgTypeCritical(1) causes only messages
classified as 'critical' to be sent to the remote
syslog server. Specifying msgTypeSerious(2) causes
'critical' and 'serious' messages to be sent.
Specifying msgTypeNone(4) means that no log messages
will be sent to the remote syslog server. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeCritical(1), msgTypeSerious(2), msgTypeInformational(3), msgTypeNone(4) |
|
bnLogMsgClearMessageBuffers |
1.3.6.1.4.1.45.1.6.16.1.1.14 |
Setting this objects causes messages currently saved in
the log message buffer facilities to be deleted. All
messages of types matching the specified bits will be
deleted. For example, a Set on this object containing bits
volSerious(2) and nonVolCritical(4) will delete all
'serious' messages from volatile storage, and all 'critical'
messages from non-volatile storage.
The none(0) value doesn't have any effect at read and write operations.
It have been introduced to correct the BITS syntax declaration. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
BITS |
none(0), volCritical(1), volSerious(2), volInformational(3), nonVolCritical(4), nonVolSerious(5), nonVolInformational(6) |
|
bnLogMsgRemoteSyslogInetAddressType |
1.3.6.1.4.1.45.1.6.16.1.1.15 |
The type of the IP address contained in the object
bnLogMsgRemoteSyslogInetAddress. Together, these two
objects specify the IP address to which log messages
are sent using the remote syslog facility. The value
of this object may not be unknown(0) if the value
of bnLogMsgRemoteSyslogEnabled is true(2). |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
InetAddressType |
|
|
bnLogMsgRemoteSyslogSecondaryInetAddressType |
1.3.6.1.4.1.45.1.6.16.1.1.17 |
The type of the IP address contained in the object
bnLogMsgRemoteSyslogSecondaryInetAddress. Together, these two objects
specify a second IP address to which log messages are sent using the
remote syslog facility. If the value of this object is unknown(0),
then messages are not sent to this address. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
InetAddressType |
|
|
bnLogMsgRemoteServerEntry |
1.3.6.1.4.1.45.1.6.16.1.1.19.1 |
A remote logging server address. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
BnLogMsgRemoteServerEntry |
|
|
bnLogMsgRemoteServerAddressType |
1.3.6.1.4.1.45.1.6.16.1.1.19.1.1 |
The type of address represented by this entry. The value of this
object indicates the format of the value of the corresponding instance
of bnLogMsgRemoteServerAddress. Currently only the values ipv4(1)
and ipv6(2) are allowed for this object. |
Status: current |
Access: not-accessible |
OBJECT-TYPE |
|
|
|
|
InetAddressType |
|
|
bnLogMsgRemoteServerSaveTargets |
1.3.6.1.4.1.45.1.6.16.1.1.19.1.4 |
This object determines the type of log messages that
will be sent to a remote syslog server when they occur.
Messages are classified based on their type. Selecting
a type value causes all log messages that have an
associated value less than or equal to the type
value specified to be sent when the log message is
entered into the system. For example, specifying
the value msgTypeCritical(1) causes only messages
classified as 'critical' to be sent to the remote
syslog server. Specifying msgTypeSerious(2) causes
'critical' and 'serious' messages to be sent.
Specifying msgTypeNone(4) means that no log messages
will be sent to the remote syslog server. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeCritical(1), msgTypeSerious(2), msgTypeInformational(3), msgTypeNone(4) |
|
bnLogMsgRemoteServerStandardSaveTargets |
1.3.6.1.4.1.45.1.6.16.1.1.19.1.6 |
This object determines the type of log messages that
will be sent to a remote syslog server when they occur.
Messages are classified based on their type. Selecting
a type value causes all log messages that have an
associated value less than or equal to the type
value specified to be sent when the log message is
entered into the system. |
Status: current |
Access: read-create |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeEmergency(0), msgTypeAlert(1), msgTypeCritical(2), msgTypeError(3), msgTypeSerious(4), msgTypeNotice(5), msgTypeInformational(6), msgTypeDebug(7), msgTypeNone(8) |
|
bnLogMsgRemoteSyslogFacility |
1.3.6.1.4.1.45.1.6.16.1.1.20 |
The facility against which remote logging is done. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
fltKernel(1), fltUserLevel(2), fltMailSystem(3), fltDaemon(4), fltSecAuthor(5), fltMsgGenInt(6), fltLinePrinter(7), fltNetNews(8), fltUUCP(9), fltClockDaemon(10), fltSecAuthor2(11), fltFTPDaemon(12), fltNTP(13), fltLogAudit(14), fltLogAlert(15), fltClockDaemon2(16), fltLocal0(17), fltLocal1(18), fltLocal2(19), fltLocal3(20), fltLocal4(21), fltLocal5(22), fltLocal6(23), fltLocal7(24), fltNone(25) |
|
bnLogMsgRemoteSyslogStandardSaveTargets |
1.3.6.1.4.1.45.1.6.16.1.1.21 |
This object determines the type of log messages that
will be sent to a remote syslog server when they occur.
Messages are classified based on their type. Selecting
a type value causes all log messages that have an
associated value less than or equal to the type
value specified to be sent when the log message is
entered into the system. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
msgTypeEmergency(0), msgTypeAlert(1), msgTypeCritical(2), msgTypeError(3), msgTypeSerious(4), msgTypeNotice(5), msgTypeInformational(6), msgTypeDebug(7), msgTypeNone(8) |
|
bnLogMsgRemoteSyslogPrimaryTcpPort |
1.3.6.1.4.1.45.1.6.16.1.1.22 |
Specifies the TCP port to use with the primary address
for sending syslog messages to the host. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
601 | 1024..65535 |
|
bnLogMsgRemoteSyslogSecondaryTcpPort |
1.3.6.1.4.1.45.1.6.16.1.1.23 |
Specifies the TCP port to use with the secondary address
for sending syslog messages to the host. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
Integer32 |
601 | 1024..65535 |
|
bnLogMsgRemoteSyslogPrimaryConnectionType |
1.3.6.1.4.1.45.1.6.16.1.1.24 |
Specifies the primary connection type (TCP/UDP) to be used
to send syslog messages to the host. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
connectionTypeUDP(1), connectionTypeTCP(2), connectionTypeTCPSecure(3) |
|
bnLogMsgRemoteSyslogSecondaryConnectionType |
1.3.6.1.4.1.45.1.6.16.1.1.25 |
Specifies the secondary connection type (TCP/UDP) to be used
to send syslog messages to the host. |
Status: current |
Access: read-write |
OBJECT-TYPE |
|
|
|
|
INTEGER |
connectionTypeUDP(1), connectionTypeTCP(2), connectionTypeTCPSecure(3) |
|
bnLogMsgBufferFull |
1.3.6.1.4.1.45.1.6.16.1.2.0.1 |
A bnLogMsgBufferFull trap is sent when either
the volatile log message buffer space or the
non-volatile log message buffer space is exhausted.
An agent will generate this trap only once when
it is determined that the buffer facilities are
exhausted. This trap will not be sent again until
the message storage facilities are cleared via the
bnLogMsgBufferClearMsgs object. Note that, for
example, clearing only the volatile storage space
when the non-volatile space is full will result in
another trap being generated when the non-volatile
space is next found to be full (e.g., when the next
log message to be saved in non-volatile storage is
generated). |
Status: current |
Access: read-write |
NOTIFICATION-TYPE |
|
|
|