BN-LOG-MESSAGE-MIB

All MIBs › BN-LOG-MESSAGE-MIB

Organization: Nortel Networks

Last Updated: 2013-10-10

Category: Alarm and Event Management

Description: Manages system log message configuration and trap generation on Bay Networks routers.

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 BN-LOG-MESSAGE-MIB?

BN-LOG-MESSAGE-MIB is a vendor-specific enterprise MIB from Bay Networks (later absorbed into Nortel) for managing the router's internal system log message buffer and generating associated traps. It belongs to the system logging/event-management configuration category. Its monitoring relevance is software/system-health focused: it reports the log buffer's current and maximum size, its fill-action behavior (what happens when the buffer is full), and provides a table of individual buffered log messages, letting an operator review recent system events -- effectively a software status/event history feed captured directly on the router without needing external syslog collection. No explicit dependency on other MIBs is evident beyond the standard SNMPv2 trap/notification conventions it uses for bnLogMsgMIBTraps. It is deployed on legacy Bay Networks/Nortel routers and switches used in enterprise and carrier networks. Network engineers evaluating or troubleshooting this functionality can download the BN-LOG-MESSAGE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BN-LOG-MESSAGE-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

Bay Networks / Nortel router or switch

Monitoring Examples

An operator would check bnLogMsgBufferCurSize against bnLogMsgBufferMaxSize to see how full the in-memory log buffer is, and review bnLogMsgBufferFullAction to understand whether old messages get overwritten or logging stops when full. Walking bnLogMsgBufferTable/bnLogMsgBufferEntry indexed by bnLogMsgBufferMsgIndex retrieves individual buffered log messages for review, while bnLogMsgBufferNonVolCurSize shows how much of the non-volatile log store is used. Triggering bnLogMsgBufferClearMsgs and watching bnLogMsgBufferCurSize reset confirms the buffer-clear operation succeeded after a maintenance action.

What Can Be Monitored

log buffer current size
log buffer maximum size
buffer full action behavior
non-volatile log buffer usage
individual buffered log messages

Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From S5-ROOT-MIB

bnLogMsg

OBJECT-IDENTITY

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
TimeTicks

From SNMPv2-TC

DateAndTime
DisplayString
RowStatus
TruthValue

How to Use in IPNetwork Monitor

Example using bnLogMsgBufferCurSize OID:

Select a Bay Networks/Nortel routers and switch (legacy) 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 bnLogMsgBufferCurSize into the Find box to locate it in the OID tree, then select it and click OK. The current number of log messages in the volatile portion of the system log message facility. 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 an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
bnLogMsgMIB	1.3.6.1.4.1.45.1.6.16.1			The management information definitions for the Bay Networks log message facility.
bnLogMsgMIBObjects	1.3.6.1.4.1.45.1.6.16.1.1
INT bnLogMsgBufferOperaton	1.3.6.1.4.1.45.1.6.16.1.1.1	INTEGER	read-write	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.
INT bnLogMsgBufferMaxSize	1.3.6.1.4.1.45.1.6.16.1.1.2	INTEGER	read-write	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.
I32 bnLogMsgBufferCurSizeEx	1.3.6.1.4.1.45.1.6.16.1.1.3	Integer32	read-only	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.
INT bnLogMsgBufferFullAction	1.3.6.1.4.1.45.1.6.16.1.1.4	INTEGER	read-write	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.
INT bnLogMsgBufferSaveTargets	1.3.6.1.4.1.45.1.6.16.1.1.5	INTEGER	read-write	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.
INT bnLogMsgBufferClearTargets	1.3.6.1.4.1.45.1.6.16.1.1.6	INTEGER	read-write	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.
INT bnLogMsgBufferClearMsgs	1.3.6.1.4.1.45.1.6.16.1.1.7	INTEGER	read-write	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.
I32 bnLogMsgBufferNonVolCurSize	1.3.6.1.4.1.45.1.6.16.1.1.8	Integer32	read-only	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.
INT bnLogMsgBufferNonVolSaveTargets	1.3.6.1.4.1.45.1.6.16.1.1.9	INTEGER	read-write	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.
bnLogMsgBufferTable	1.3.6.1.4.1.45.1.6.16.1.1.10		not-accessible	Locally held information about log messages.
bnLogMsgBufferEntry	1.3.6.1.4.1.45.1.6.16.1.1.10.1		not-accessible	Information on a particular event as described by a log message and related information.
I32 bnLogMsgBufferMsgIndex	1.3.6.1.4.1.45.1.6.16.1.1.10.1.1	Integer32	not-accessible	The arbitrary integer index assigned to the log message upon entry into the message facility.
I32 bnLogMsgBufferMsgOrig	1.3.6.1.4.1.45.1.6.16.1.1.10.1.2	Integer32	not-accessible	The originator of the log message. Typically, this value represents the slot or unit on which this message originated.
TIK bnLogMsgBufferMsgTime	1.3.6.1.4.1.45.1.6.16.1.1.10.1.3	TimeTicks	not-accessible	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.
INT bnLogMsgBufferMsgSrc	1.3.6.1.4.1.45.1.6.16.1.1.10.1.4	INTEGER	read-only	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.
I32 bnLogMsgBufferMsgCode	1.3.6.1.4.1.45.1.6.16.1.1.10.1.5	Integer32	read-only	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.
STR bnLogMsgBufferMsgString	1.3.6.1.4.1.45.1.6.16.1.1.10.1.6	DisplayString	read-only	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.
I32 bnLogMsgBufferMsgParam1	1.3.6.1.4.1.45.1.6.16.1.1.10.1.7	Integer32	read-only	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).
I32 bnLogMsgBufferMsgParam2	1.3.6.1.4.1.45.1.6.16.1.1.10.1.8	Integer32	read-only	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).
I32 bnLogMsgBufferMsgParam3	1.3.6.1.4.1.45.1.6.16.1.1.10.1.9	Integer32	read-only	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).
DAT bnLogMsgBufferMsgUtcTime	1.3.6.1.4.1.45.1.6.16.1.1.10.1.10	DateAndTime	read-only	Contains the system's local value of UTC (Universal Coordinated Time) when the log entry was created.
INT bnLogMsgBufferMsgType	1.3.6.1.4.1.45.1.6.16.1.1.10.1.11	INTEGER	read-only	The message type indicates whether this message is classified as 'critical', 'serious' or 'informational'.
T/F bnLogMsgRemoteSyslogEnabled	1.3.6.1.4.1.45.1.6.16.1.1.11	TruthValue	read-write	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.
IP bnLogMsgRemoteSyslogAddress	1.3.6.1.4.1.45.1.6.16.1.1.12	IpAddress	read-write	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.
INT bnLogMsgRemoteSyslogSaveTargets	1.3.6.1.4.1.45.1.6.16.1.1.13	INTEGER	read-write	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.
BIT bnLogMsgClearMessageBuffers	1.3.6.1.4.1.45.1.6.16.1.1.14	Bits	read-write	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.
IPt bnLogMsgRemoteSyslogInetAddressType	1.3.6.1.4.1.45.1.6.16.1.1.15	InetAddressType	read-write	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).
IP bnLogMsgRemoteSyslogInetAddress	1.3.6.1.4.1.45.1.6.16.1.1.16	InetAddress	read-write	The IP address to which log messages are sent using the remote syslog facility.
IPt bnLogMsgRemoteSyslogSecondaryInetAddressType	1.3.6.1.4.1.45.1.6.16.1.1.17	InetAddressType	read-write	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.
IP bnLogMsgRemoteSyslogSecondaryInetAddress	1.3.6.1.4.1.45.1.6.16.1.1.18	InetAddress	read-write	The IP address to which log messages are sent using the remote syslog facility.
bnLogMsgRemoteServerTable	1.3.6.1.4.1.45.1.6.16.1.1.19		not-accessible	A table of remote logging server addresses.
bnLogMsgRemoteServerEntry	1.3.6.1.4.1.45.1.6.16.1.1.19.1		not-accessible	A remote logging server address.
IPt bnLogMsgRemoteServerAddressType	1.3.6.1.4.1.45.1.6.16.1.1.19.1.1	InetAddressType	not-accessible	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.
IP bnLogMsgRemoteServerAddress	1.3.6.1.4.1.45.1.6.16.1.1.19.1.2	InetAddress	not-accessible	The address represented by this entry.
T/F bnLogMsgRemoteServerEnabled	1.3.6.1.4.1.45.1.6.16.1.1.19.1.3	TruthValue	read-create	Indicates whether this server is enabled.
INT bnLogMsgRemoteServerSaveTargets	1.3.6.1.4.1.45.1.6.16.1.1.19.1.4	INTEGER	read-create	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.
ROW bnLogMsgRemoteServerRowStatus	1.3.6.1.4.1.45.1.6.16.1.1.19.1.5	RowStatus	read-create	This object is used to create/delete entries in this table.
INT bnLogMsgRemoteServerStandardSaveTargets	1.3.6.1.4.1.45.1.6.16.1.1.19.1.6	INTEGER	read-create	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.
INT bnLogMsgRemoteSyslogFacility	1.3.6.1.4.1.45.1.6.16.1.1.20	INTEGER	read-write	The facility against which remote logging is done.
INT bnLogMsgRemoteSyslogStandardSaveTargets	1.3.6.1.4.1.45.1.6.16.1.1.21	INTEGER	read-write	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.
I32 bnLogMsgRemoteSyslogPrimaryTcpPort	1.3.6.1.4.1.45.1.6.16.1.1.22	Integer32	read-write	Specifies the TCP port to use with the primary address for sending syslog messages to the host.
I32 bnLogMsgRemoteSyslogSecondaryTcpPort	1.3.6.1.4.1.45.1.6.16.1.1.23	Integer32	read-write	Specifies the TCP port to use with the secondary address for sending syslog messages to the host.
INT bnLogMsgRemoteSyslogPrimaryConnectionType	1.3.6.1.4.1.45.1.6.16.1.1.24	INTEGER	read-write	Specifies the primary connection type (TCP/UDP) to be used to send syslog messages to the host.
INT bnLogMsgRemoteSyslogSecondaryConnectionType	1.3.6.1.4.1.45.1.6.16.1.1.25	INTEGER	read-write	Specifies the secondary connection type (TCP/UDP) to be used to send syslog messages to the host.
bnLogMsgMIBTraps	1.3.6.1.4.1.45.1.6.16.1.2
bnLogMsgMIBTrapPrefix	1.3.6.1.4.1.45.1.6.16.1.2.0
NTF 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).
bnLogMsgMIBConformance	1.3.6.1.4.1.45.1.6.16.1.3

RFC description

Management information definitions for Bay Networks log message facility, supporting remote syslog, message buffering, and logging configuration.

Start monitoring Bay Networks/Nortel routers and switches (legacy) 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 BN-LOG-MESSAGE-MIB