BN-LOG-MESSAGE-MIB
AI MIB Summary
The BN-LOG-MESSAGE-MIB enables monitoring and retrieval of system log entries and event messages from Bay Networks networking hardware via SNMP. It provides structured access to historical and real-time log data for troubleshooting device operations and security auditing.
The management information definitions for the Bay Networks log message facility.
Main OID:
bnLogMsgMIB.1.3.6.1.4.1.45.1.6.16.1
50
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
50 total| Object Name |
|---|
bnLogMsgMIBThe management information definitions for the Bay Networks log message facility. MODULE-IDENTITY .1.3.6.1.4.1.45.1.6.16.1 |
bnLogMsgMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.45.1.6.16.1.1 |
bnLogMsgBufferOperatonThe 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.1 |
bnLogMsgBufferMaxSizeThis 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.2 |
bnLogMsgBufferCurSizeThe 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.ro Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.3 |
bnLogMsgBufferFullActionThe 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.4 |
bnLogMsgBufferSaveTargetsThis 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.5 |
bnLogMsgBufferClearTargetsThis 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.rwdeprecated Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.6 |
bnLogMsgBufferClearMsgsSetting 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.rwdeprecated Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.7 |
bnLogMsgBufferNonVolCurSizeThe 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.ro Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.8 |
bnLogMsgBufferNonVolSaveTargetsThis 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.9 |
bnLogMsgBufferTableLocally held information about log messages. SEQUENCE OF BnLogMsgBufferEntry .1.3.6.1.4.1.45.1.6.16.1.1.10 |
bnLogMsgBufferEntryInformation on a particular event as described by a log message and related information. BnLogMsgBufferEntry .1.3.6.1.4.1.45.1.6.16.1.1.10.1 |
bnLogMsgBufferMsgIndexThe arbitrary integer index assigned to the log message upon entry into the message facility. Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.10.1.1 |
bnLogMsgBufferMsgOrigThe originator of the log message. Typically, this value represents the slot or unit on which this message originated. Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.10.1.2 |
bnLogMsgBufferMsgTimeThe 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. TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.45.1.6.16.1.1.10.1.3 |
bnLogMsgBufferMsgSrcThe 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.ro Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.10.1.4 |
bnLogMsgBufferMsgCodeThe 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.ro Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.10.1.5 |
bnLogMsgBufferMsgStringA 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.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.45.1.6.16.1.1.10.1.6 |
bnLogMsgBufferMsgParam1A 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).ro Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.10.1.7 |
bnLogMsgBufferMsgParam2A 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).ro Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.10.1.8 |
bnLogMsgBufferMsgParam3A 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).ro Integer32 .1.3.6.1.4.1.45.1.6.16.1.1.10.1.9 |
bnLogMsgBufferMsgUtcTimeContains the system's local value of UTC (Universal Coordinated Time) when the log entry was created.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.45.1.6.16.1.1.10.1.10 |
bnLogMsgBufferMsgTypeThe message type indicates whether this message is classified as 'critical', 'serious' or 'informational'.ro Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.10.1.11 |
bnLogMsgRemoteSyslogEnabledThis 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.45.1.6.16.1.1.11 |
bnLogMsgRemoteSyslogAddressThe 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.rw IpAddress .1.3.6.1.4.1.45.1.6.16.1.1.12 |
bnLogMsgRemoteSyslogSaveTargetsThis 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.13 |
bnLogMsgClearMessageBuffersSetting 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.rw Bits .1.3.6.1.4.1.45.1.6.16.1.1.14 |
bnLogMsgRemoteSyslogInetAddressTypeThe 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).rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.45.1.6.16.1.1.15 |
bnLogMsgRemoteSyslogInetAddressThe IP address to which log messages are sent using the remote syslog facility.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.45.1.6.16.1.1.16 |
bnLogMsgRemoteSyslogSecondaryInetAddressTypeThe 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.rw InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.45.1.6.16.1.1.17 |
bnLogMsgRemoteSyslogSecondaryInetAddressThe IP address to which log messages are sent using the remote syslog facility.rw InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.45.1.6.16.1.1.18 |
bnLogMsgRemoteServerTableA table of remote logging server addresses. SEQUENCE OF BnLogMsgRemoteServerEntry .1.3.6.1.4.1.45.1.6.16.1.1.19 |
bnLogMsgRemoteServerEntryA remote logging server address. BnLogMsgRemoteServerEntry .1.3.6.1.4.1.45.1.6.16.1.1.19.1 |
bnLogMsgRemoteServerAddressTypeThe 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. InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.45.1.6.16.1.1.19.1.1 |
bnLogMsgRemoteServerAddressThe address represented by this entry. InetAddress .1.3.6.1.4.1.45.1.6.16.1.1.19.1.2 |
bnLogMsgRemoteServerEnabledIndicates whether this server is enabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.45.1.6.16.1.1.19.1.3 |
bnLogMsgRemoteServerSaveTargetsThis 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.19.1.4 |
bnLogMsgRemoteServerRowStatusThis object is used to create/delete entries in this table.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.45.1.6.16.1.1.19.1.5 |
bnLogMsgRemoteServerStandardSaveTargetsThis 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.19.1.6 |
bnLogMsgRemoteSyslogFacilityThe facility against which remote logging is done.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.20 |
bnLogMsgRemoteSyslogStandardSaveTargetsThis 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.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.21 |
bnLogMsgRemoteSyslogPrimaryTcpPortSpecifies the TCP port to use with the primary address for sending syslog messages to the host.rw Integer32 (601|1024..65535) .1.3.6.1.4.1.45.1.6.16.1.1.22 |
bnLogMsgRemoteSyslogSecondaryTcpPortSpecifies the TCP port to use with the secondary address for sending syslog messages to the host.rw Integer32 (601|1024..65535) .1.3.6.1.4.1.45.1.6.16.1.1.23 |
bnLogMsgRemoteSyslogPrimaryConnectionTypeSpecifies the primary connection type (TCP/UDP) to be used to send syslog messages to the host.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.24 |
bnLogMsgRemoteSyslogSecondaryConnectionTypeSpecifies the secondary connection type (TCP/UDP) to be used to send syslog messages to the host.rw Enumeration .1.3.6.1.4.1.45.1.6.16.1.1.25 |
bnLogMsgMIBTraps OBJECT IDENTIFIER .1.3.6.1.4.1.45.1.6.16.1.2 |
bnLogMsgMIBTrapPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.45.1.6.16.1.2.0 |
bnLogMsgBufferFullA 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). NOTIFICATION-TYPE .1.3.6.1.4.1.45.1.6.16.1.2.0.1 |
bnLogMsgMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.45.1.6.16.1.3 |