Olicom-MIB: View SNMP OID List / Download MIB

A string containing the hardware product id.

A string containing the hardware version.

A string containing the ECO update level.

A string containing the hardware serial number.

A sequence of hardware options, each a string describing the appropriate option present.

The option number for this option.

A string describing this option.

A string containing the software product id. Recommended format is as follows: the string consists of fixed and optional part. Fixed part contains device's symbol (eg.'CF8711' for the CrossFire 8711 FE switch). This fixed part cannot contain any whitespace characters. The optional part contains additional description, it must begin with a space character as delimiter.

A string containing the software version. Recommended format is as follows: the string consists of fixed and optional part. Fixed part contains software version as 4 numbers separated by dot characters (eg. '1.0.0.20'). This fixed part must use only digit and dot characters. The optional part contains additional description, it must begin with a space character as delimiter.

A string containing the ECO update level.

A sequence of software options, each a string describing the appropriate option present.

The option number for this option.

A string describing this option.

A sequence of MIBs supported by this device.

The number for this MIB description entry.

The unique OBJECT IDENTIFIER for this MIB description entry. Olicom specific MIBs have OBJECT IDENTIFIERs that are defined as { ocmibs N }. (See ocmibs section).

A string describing this MIB description entry.

This table contains the product IDs and addtional information for the additional files included in a multichunk file.

An entry in the infoXtraSwTable.

The entry number in the infoXtraSwTable.

From the file header: The target for the SW image.

From the file header: The SW product ID.

From the file header: The SW version.

From the file header: The SW ECO level.

From the file header: The SW serial number.

From the file header: A bitmask of SW options.

This table describes all the HW modules in a system with multiple modules.

A list of information objects for a HW module.

The module index of this module. This is a unique index identifying a hardware module in the switching system. The planar board of a switch box is considered a module. Any expansion boards (slots) are assigned the subsequent moduleIndexes.

A string containing the modules product id (eg. from EEPROM)

A string containing the modules version (eg. from EEPROM)

A string containing the modules serial no (eg. from EEPROM)

A string containing the modules bootprom version. An empty string, if no bootprom is present on this module.

This table describes all the SW images in the system.

A list of information objects for SW image.

The module index of the module on which the SW image reside.

The SW image number, relative to the HW module.

A string containing the SW images product id. An empty string, if this image is not present or corrupted.

A string containing the SW images version. An empty string, if this image is not present or corrupted.

The time when the software image was downloaded to the device. This is measured in seconds since 00:00:00 on 1 January 1970 (i.e. UNIX standard time).

This variable controls in which form MAC addresses will be represented. The default is canonical form for ethernet products and non-cannonical for tokenring products. Setting this variable controls the representation for syntax's: PhysAddress, MacAddress and MacAddressString. Setting this variable will enforce a reboot. Enumeration: 'non-canonical': 2, 'canonical': 1.

This variable controls whether the device will send rhwo packets on UDP port 513. The packets include information about pseudo-users logged in. For the Olicom Bridge products, these are: Olicom Bridge Manager (user: obrimg) or the (IBM) Lan Network Manager (users: control, altern, observ). The tty information describes the management link. If this object it disabled, it overrides the value of inetIPAddressEnableRwho. Enumeration: 'disabled': 2, 'enabled': 1.

This variable control whether the device will process RIP (Routing Information Protocol) packets on UDP port 520 to update the IP routing table. The device will not announce any routes, it will only participate as a passive host. Refer to Unix documentation of either routed or gated daemons, or Internet RFC document 1058. If this object it disabled, it overrides the value of inetIPAddressEnableRIP. Enumeration: 'disabled': 2, 'enabled': 1.

The maximum number of community entries allowed in inetCommunityTable.

A list of entries for each community which is authorized to access the agent. The maximum number of entries is given by inetCommunityMaxEntries.

A community entry containing objects pertaining to a network manager which is authorized to access the agent.

The entry number in the community table for this community.

The community name used by the management station to access the agent. An empty community name means that any request regardless of it's community name will be accepted.

The IP address of the management station authorized to access the agent. A value of 0.0.0.0 allows every IP node to use the community name.

Controls the access rights of the management station. Enumeration: 'readWrite': 2, 'readOnly': 1.

Setting this object to a non zero value, deletes the entry for this community entry.

The IPX address of the management station authorized to access the agent. A value of all zeroes allows every IPX node to use the community name.

This variable defines which transport protocols should be expected to deliver requests for this community. If the bit-value 0x01 is set, UDP/IP is used and the inetCommunityIPAddress variable contains the source address. If the bit-value 0x02 is set, IPX is used and the inetCommunityIPXAddress variable will be used. If the bit-value 0x04 is set, MAC is used and the inetCommunityMACAddress varial will be used. All three bit-values can be set, in which case all source addresses will be allowed.

The MAC address of the management station authorized to access the agent. A value of 000000000000 allows every MAC node to use the community name.

The maximum number of network manager entries allowed in inetTrapTable.

A list of trap entries for each network manager which receives traps from the agent. The maximum number of entries is given by trapMaxEntries.

A trap entry containing objects pertaining to a network manager which receives traps from the agent.

The community name used in traps sent to the management station.

The IP address of the management station to receive traps. Note a value of zero or resetting inetTrapTransportProtocols bit value 0x01 disables IP based traps from the entry However inetTrapDelete should be used to delete entries as it resets all parameters to default settings.

NOTE: This field has been replaced by the controlTrapTable. Bitmask of disabled traps from product-specific network management agents. Each octet within the value of this object specifies a set of eight traps, with the first octet specifying traps 1 through 8, the second octet specifying traps 9 through 16, etc. Within each octet, the least significant bit represents the lowest numbered trap, and the most significant bit represents the highest numbered trap. Thus, each trap of the device is represented by a single bit within the value of this object. If that bit has a value of `0' then that trap is included in the set of traps; the trap is not included if its bit has a value of `1'. The bits corresponds to the TRAP numbers found in the the product specific MIBs.

Setting this object to a non-zero value, deletes the entry for the trap destination.

The UDP port on the management station to receive traps. If set to 0 (zero) the default value 162 is used.

All entries in the inetTrapTable have a unique index, denoted by this variable.

The IPX address of the management station to receive traps. Note a value of zero or resetting inetTrapTransportProtocols bit value 0x02 disables IPX based traps from the entry However inetTrapDelete should be used to delete entries as it resets all parameters to default settings.

This variable defines which transport protocols should be used to deliver TRAPs for this trap destination. If the bit-value 0x01 is set, UDP/IP is use and the inetTrapDestIPAddress variable contains the destination address (together with the inetTrapDestUDPPort variable), and if the bit-value 0x02 is set, IPX is used and the inetTrapDestIPXAddress variable will be used. Both bit-values can be set, in which case the traps will be set to both destinations.

This variable controls the encapsulation method used when delivering TRAPs via the UDP/IP protocol. NOTE: On TokenRing devices only snap(3) works. ON EtherNet devices only ethernet(1) and snap(3) works. Enumeration: 'snap': 3, 'ethernet': 1, 'ieee8022': 2.

This variable controls the encapsulation method used when delivering TRAPs via the IPX protocol. NOTE: On TokenRing devices only ieee8022(2) and snap(3) works. Enumeration: 'snap': 3, 'ethernet': 1, 'ieee8022': 2.

This variable controls the default encapsulation method used by this device, when transmitting via the UDP/IP protocol. This default encapsulation method is only used when there is no other way to know which encapsulation method the receiving host understands. NOTE: On TokenRing devices only snap(3) works. ON EtherNet devices only ethernet(1) and snap(3) works. Enumeration: 'snap': 3, 'ethernet': 1, 'ieee8022': 2.

This variable controls the default encapsulation method used by this device, when transmitting via the IPX protocol. This default encapsulation method is only used when there is no other way to know which encapsulation method the receiving host understands. NOTE: On TokenRing devices only ieee8022(2) and snap(3) works. Enumeration: 'snap': 3, 'ethernet': 1, 'ieee8022': 2.

This table contains IP addressing information for each interface.

This number corresponds to the interface number, ifIndex, in ifTable from MIB-II.

This is the IP address associated with the interface.

This is the IP netmask associated with the interface. Note: Setting the netmask for one interface may change the netmask for other interfaces.

This is the IP default gateway associated with the interface. Note: Setting the default gateway for one interface may change the default gateway for other interfaces.

This variable controls whether the device will send rhwo packets on UDP port 513 on the specified interface. The packets include information about pseudo-users logged in. This object has effect only if inetEnableRwho has the value 'enabled'. Enumeration: 'disabled': 2, 'enabled': 1.

This variable control whether the device will process RIP (Routing Information Protocol) packets on UDP port 520 on the specified interface to update the IP routing table. The device will not announce any routes, it will only participate as a passive host. Refer to Unix documentation of either routed or gated daemons, or Internet RFC document 1058. This object has effect only if inetEnableRIP has the value 'enabled'. Enumeration: 'disabled': 2, 'enabled': 1.

This variable controls the IP encapsulation method used on the specified interface. Choosing media-default(4) selects SNAP encapsulation on TokenRing interfaces and Ethernet encapsulation on Ethernet interfaces. NOTE: On TokenRing interfaces only snap(3) and media-default(4) works. Enumeration: 'snap': 3, 'ethernet': 1, 'media-default': 4.

The baud rate used by a SLIP connection. Enumeration: 'b9600': 4, 'b1200': 1, 'b2400': 2, 'b38400': 6, 'b19200': 5, 'b4800': 3.

The transmission parity used by a SLIP connection. Enumeration: 'even': 2, 'none': 1, 'odd': 3.

The number of stop bits used by a SLIP connection. Enumeration: 'two': 2, 'one': 1.

A string sent to the modem to initialize it prior to establishing a SLIP connection.

Enable or disable compression of the SLIP headers. Enumeration: 'yes': 1, 'no': 2.

Maximum Transmit Unit size, that is, the maximum size of a PDU transmitted on a SLIP connection.

Maximum Receive Unit size, that is, the maximum acceptable size of a PDU received on a SLIP connection.

This object controls whether the Olicom Out-Of-Band Management Callback sub-system should be active (enabled) or not. Enumeration: 'disabled': 1, 'enabled': 2.

A string containing the telephone number to be used by the callback sub-system. This string will be sent `as is' to the modem connected to the OBM communication port.

This object controls whether the Olicom Out-Of-Band Management Callout sub-system should be active (enabled) or not. Enumeration: 'disabled': 1, 'enabled': 2.

A string containing the telephone number to be used by the callout sub-system. This string will be sent `as is' to the modem connected to the OBM communication port.

Writing any value other than zero to this variable causes the device program to restart.

This variable contains the number of times, any part of the configuration has been changed by any of the management systems controlling this device. See the managementTable.

This table contains an entry for each enterprise-specific TRAP this device is capable of sending. The only writable field in the table is the controlTrapGeneration field, which controls the generation is that particular TRAP. All other fields are used as indices.

A controlTrapTableEntry entry contains objects pertaining to one particular enterprise-specific TRAP.

This variable corresponds to the inetTrapIndex variable in the inetTrapTable.

This variable identifies the MIB in which this TRAP is defined. The variable is the index of the entry in infoSoftwareMIBsTable that defines the MIB in question.

This variable describes in which TRAP in the MIB subtree this TRAP is.

This variable describes the TRAP. This corresponds to the description field in the MIB text for this TRAP.

This variable controls whether this TRAP never(1) is generated or is always(2) generated. Enumeration: 'always': 2, 'never': 1.

This variable defines which protocol should be used for downloading configuration and program code. Notice that a specific Olicom product will typically support only one or two of the listed protocols. Enumeration: 'bootp-tftp': 3, 'olicom-rpl': 4, 'ibm-hlm': 2, 'ibm-rpl': 1, 'olicom-remote-software-update': 5.

In the Load protocols where it is relevant this variable contains the name of the file to be downloaded.

This object specifies the MAC address of the Load server used for download. Only used if the Load protocol defined by the controlLoadProtocol variable needs the MAC address of the an Load server.

This object specifies the IP address of the Load server used for download. Only used if the Load protocol defined by the controlLoadProtocol variable needs the IP address of the an Load server.

This object specifies the IPX address of the Load server used for download. Only used if the Load protocol defined by the controlLoadProtocol variable needs the IPX address of the an Load server.

Writing any value other than zero to this variable causes a download to start. While reading, it returns the current status of transmission or last transmission result. Enumeration: 'protocolFailure': 6, 'badFile': 8, 'completed': 5, 'notInitiated': 1, 'flashFailure': 7, 'inProgress': 3, 'starting': 2, 'finishing': 4.

The internal clock in the device. This is measured in seconds since 00:00:00 on 1 January 1970 (i.e. UNIX standard time).

This object specifies whether RMON probe is enabled or disabled. If the device does not support RMON only disabled is allowed. Setting this variable resets the CAU. Enumeration: 'disabled': 2, 'enabled': 1.

This object specifies whether changes to certain fundamental configuration parameters (as specified for the corresponding MIB variables) shall cause the device to restart automatically. The auto restart functionality is always enabled after restarting the bridge. NOTICE: In general, disabling this functionality is not recommended, since some changes may cause the device to behave erratically (which may be the reason why the device has to restart). However, for the initial configuration of the device (i.e. before it is operational, it is usually safe to postpone restarting the device until all configuration changes have been made. Enumeration: 'disabled': 2, 'enabled': 1.

This object controls the state of the SW images in systems where more than one image is present. In the OC-9100 the state of each image may be: empty(1) - no image is present, future1(2) - the image may be used later, futureTest(3) - the image will be used once on the next restart, future2(4) - the image may be used later, current1(5) - the image is in use now, past(6) - the image was previously used, current2(7) - the image is in use now, checksumError(8) - the image is faulty, erased(9) - the image has been erased. Because this information is stored in flash each state cannot be used arbitrarily. For example, the future state can only be used twice, namely as state future1 and future2. Normally, the state of a SW image progresses through numerically increasing states. In the OC-8500 and OC-8700 series the status word is stored in BBS RAM. This releases the constraints to the sequence of states, thus only a subset of the above is needed: empty(1) - no image is present, future1(2) - the image may be used later, futureTest(3) - the image will be used once on the next restart, current1(5) - the image is in use now, past(6) - the image was previously used, checksumError(8) - the image is faulty, erased(9) - the image has been erased. The value actually stored in this object is state1*256+state2, where state1 and state2 are the values of the two SW image states. Note that a number of combinations are illegal. For example, the value 6*256+6 (indicating two 'past' images) may not be written.

The total number of bytes in the configuration FLASH, or rather, in one of the two alternating sections.

The number of free bytes in the configuration FLASH.

Controls the state of the FLASH configuration. The states are as follows: normal default - The DEFAULT button has been activated. corrupted - The FLASH configuration has been corrupted, default configuration is used. temporary - A temporary update to the configuration has been initiated. testTemporary - A restart has been performed after a 'temporary' update. acceptTemporary - Setting this value in state 'temporary' or 'testTemporary' will force the state to 'normal' and will cause the configuration to be accepted. rejectTemporary - Setting this value in state 'temporary' or 'testTemporary' will cause the temporary configuration update to be aborted. rewrite - Setting this value will cause the FLASH to be rewritten, resulting in maximum free FLASH. Enumeration: 'temporary': 4, 'corrupted': 3, 'normal': 1, 'default': 2, 'rewrite': 8, 'testTemporary': 5, 'rejectTemporary': 7, 'acceptTemporary': 6.

Writing value n to this variable will cause device to restart after n seconds. Writing zero cancels the reboot. Writing new value when the reboot is already scheduled cancels previously scheduled action and schedules new reboot. While reading this variable shows time remaining to the reboot (0 if reboot is not scheduled).

Number of bytes transmitted so far. 0 if no transmission is currently in progress.

Length of the file being transmitted. 0 if no transmission is currently in progress or if the size is unknown.

The maximum number of simultaneous sessions this device is able to handle.

The unique identifier of the next free TFTP session. This index should be used for manipulating rows in controlTftpSessionTable.

This table makes it possible to control TFTP sessions performed by the built-in device TFTP client.

A list of configuration objects for the TFTP session.

The TFTP session index.

The status of this TFTP session entry. The following values are possible: 'active' - TFTP operation is in progress. Setting this object to this value starts the transmission. 'notInService' - The row is created but there is no TFTP transfer in progress. 'createAndWait' - the only way to create the session. If the operation is successful the status of the row should be 'notInService'. 'destroy' - destroys the row and frees the resources. This operation will fail when the row is 'active'. 'createAndGo' is illegal. Setting this object to this value will fail. 'notReady' is not used for this variable.

The direction of this session's transfer. Enumeration: 'download': 1, 'upload': 2.

The IP address of the TFTP server used for the transmission.

The name of the transferred file on the server side.

The name of the transferred file on the switch side. In case of upload switch may ignore this variable.

The status of the session or transmission result when the session was completed. The following values are possible: notInitiated(1) no transfer since this row creation starting(2) inProgress(3) finishing(4) completed(5) last transfer was completed successfully protocolFailure(6) transmission failed (e.g. TFTP error) flashFailure(7) writing to the flash failed badFile(8) the file transmitted was corrupted The download/upload cycle doesn't have to go through all of the states listed above. Enumeration: 'protocolFailure': 6, 'badFile': 8, 'completed': 5, 'notInitiated': 1, 'flashFailure': 7, 'inProgress': 3, 'starting': 2, 'finishing': 4.

Number of bytes transmitted so far. 0 if no transmission is currently in progress.

Length of the file being transmitted. 0 if no transmission is currently in progress or if the size is unknown.

The type of restart that will be performed after next reboot request. After any kind of reboot the value of this object should be soft(1) regardles of the previous value. Enumeration: 'default': 2, 'soft': 1.

This object controls whether the Olicom Out-Of-Band Management system should be active (enabled) or not. Enumeration: 'disabled': 1, 'enabled': 2.

A string containing the password needed to access the device through the OBM communication port. NOTE: Reading the password will return the string `********' - an attempt to set the password to that value will not modify the password.

This object controls the baudrate of the communication port used by the Out-of-Band Management system. The 'auto' means automatic UART speed sensing. Enumeration: 'b9600': 4, 'auto': 12, 'b1200': 1, 'b2400': 2, 'b38400': 6, 'b19200': 5, 'b460800': 10, 'b921600': 11, 'b115200': 8, 'b57600': 7, 'b4800': 3, 'b230400': 9.

This object controls the parity of the communication port used by the Out-of-Band Management system. Enumeration: 'even': 2, 'none': 1, 'odd': 3.

This object controls the number of stopbits of the communication port used by the Out-of-Band Management system. Enumeration: 'two': 2, 'one': 1.

A string containing the initialization string used to initialize the modem connected to the OBM communication port. This string will be sent `as is'.

This object controls whether the Olicom Out-Of-Band Management Callback sub-system should be active (enabled) or not. Enumeration: 'disabled': 1, 'enabled': 2.

A string containing the default phone number to be used by the callback sub-system. This string will be sent `as is' to the modem connected to the OBM communication port.

This object controls whether the Olicom Out-Of-Band Management Callout sub-system should be active (enabled) or not. Enumeration: 'disabled': 1, 'enabled': 2.

A string containing the telephone number to be used by the callout sub-system. This string will be sent `as is' to the modem connected to the OBM communication port.

This object controls which events will trigger the callout sub-system to try to establish a connection using the obmCalloutPhoneNumber. The value is a bitmask, representing the following possibilities: 0x01 : Fatal Error. (CAU/CAM/BRIDGE) 0x02 : Adapter Failure. (CAU) 0x02 : Start-up Failure. (BRIDGE) 0x04 : Fan Failure. (SWI) 0x04 : LAM Failure. (CAU/CAM) 0x08 : Main ring Wrap due to beacon. (CAU) 0x10 : HLM Connection Lost. (CAU/CAM) 0x10 : Temperature warning (SWI) 0x20 : Power System Failure (CAU) 0x40 : WAN link failure (BRIDGE) 0x40 : Port auto disabled (SWI)

This value denotes the number of times the callout sub-system will try to establish a connection using the obmCallbackPhoneNumber string. Used also for call-back.

This value denotes the number of minutes between unsuccesful attempts to establish a connection using the obmCalloutPhoneNumber string. Used also for call-back.

This object controls whether the Olicom Out-Of-Band Management delayed Recovery sub-system should be active (enabled) or not. On a bridge this is controlled by the configRestartOnError variable. Enumeration: 'disabled': 1, 'enabled': 2.

This object controls whether the Olicom Out-Of-Band Management can be accessed from telnet. Enumeration: 'disabled': 1, 'enabled': 2.

This value denotes the number of seconds the user must wait after 3 unsuccesfull attempts to enter the correct password. The default value is 60 sec.

This object controls whether the Olicom Out-Of-Band Management can be accessed via serial console or async PPP/SLIP or selected dynamically (serial or async PPP/SLIP) based on the incoming data type. Enumeration: 'autoSense': 1, 'serialConsole': 2, 'asyncPPP': 3.

This object controls value of inactivity timeout [min] which will be used to disconnect an idle user from the Out-of-Band Management system. The default value is 3 min. Value 0 disables this feature (infinite timeout)

This object controls if ATDP or ATDT will be sent to a modem while dialing from the Out-of-Band Management system. Enumeration: 'tone': 2, 'pulse': 1.

A string containing the password needed to read-access the device through the OBM communication port. NOTE: Reading the password will return the string `********' - an attempt to set the password to that value will not modify the password.

The status of Xon/Xoff flow control. Enumeration: 'disabled': 2, 'enabled': 1.

The status of RTS/CTS handshake. Enumeration: 'disabled': 2, 'enabled': 1.

Number of databits to be used by serial interface.

A list of entries for each management system the device supports. NOTE: The SNMP management system is always the first entry in the table.

A management entry contains objects pertaining to a network management system which is supported by this device.

The entry number in the management table for this management system.

A descriptive text for this management system (protocol).

This variable describes the current association between this device and this management system. Some systems are association oriented (e.g. CMIP) and can therefore have state associated(1) or not-associated(2), while other management systems are request/reply oriented (e.g. SNMP) and therefore always have the state na-association(3). Enumeration: 'not-associated': 2, 'associated': 1, 'na-association': 3.

This variable describes the relative priority of the management systems supported by this device. The associated management system with the highest managementPriority value (numerically) will be the ONLY system with write access to all management variables.

This table contains the history log for the last 10 SNMP managers which have accessed this device.

An entry in the managementSnmpAccessLogTable.

The number of this entry in the managementSnmpAccessLogTable.

The time at which the SNMP manager last accessed this device.

The IP Address of the SNMP manager.

Specifies the access rights of the SNMP manager. Enumeration: 'readWrite': 2, 'readOnly': 1.

Specifies the number of times the SNMP manager has accessed this device.

A detailed explanation of why the last SNMP operation failed. It is used by the management station when the SNMP error-status in the response does not fully explain the reason for the failure. For example, 'badValue' can be returned if the user has entered an improper value or if there are insufficient system resources to perform a requested action. The SNMP agent should return the failure explanation only if it is requested by the station that caused it. If no failure has occurred, the SNMP agent should return an empty string when a request for this object.

This variable contains the text that is displayed in the device's frontpanel display.

This variable controls whether the keyboard on the device's frontpanel will work. The value enabled(1) means all actions are permitted, status-only(2) means that all keyboard actions that change the device's configuration is denied, while disabled(3) means that all access is denied. Enumeration: 'disabled': 3, 'enabled': 1, 'status-only': 2.

This variable contains the errorcode that is displayed in the device's frontpanel display.

This variable contains the state of the error LED on this device's frontpanel. Enumeration: 'led-off': 2, 'led-on-steady': 3, 'led-unknown': 1, 'led-flashing': 4.

The display of the device is capable of showing different status displays with different counters. This variable determines which counter-display should be shown, when no other error-messages need to be displayed. The device may choose to ignore this value. The value 0 (zero) means default display of the device's choice.

Some devices have a front-panel keyboard. This variable may be used to remotely operate the front-panel keyboard. Enumeration: 'key-enter': 400, 'key-down': 402, 'key-left': 403, 'key-right': 404, 'key-up': 401.

This table is used to store history logs in the form of a number of display texts, including a corresponding time stamp.

This is an entry in the frontpanelDisplayLogTable.

The entry number in the frontpanelDisplayLogTable. In order to ensure that an SNMP GET-NEXT operation produces consistent results, it is recommended that entries be added to this table starting with a high index value; subsequent addtions to the table should happen with decreasing index values.

The time at which the entry was made.

The text string from the front panel display.

This table contains a number of error log entries from the managed device.

The number of the entry.

This variable describes the device's perception of the time when the error occurred.

This variable contains a description of the error that occurred in this device.

This variable contains additional information about the error.

This variable describes the device's conception of the calendar time when the error occurred. This is measured in seconds since 00:00:00 on 1 January 1970 (i.e. UNIX standard time).

This variable describes the device's conception of the calendar time when the error condition disappeared. This is measured in seconds since 00:00:00 on 1 January 1970 (i.e. UNIX standard time). A value of 0 (zero) indicates that the error condition has not disappeared.

This variable contains the category of the error log Enumeration: 'startup': 2, 'bootload': 1, 'operational': 3.

This variable contains the severity of the error log Enumeration: 'information': 1, 'notice': 2, 'alert': 6, 'warning': 3, 'critical': 5, 'error': 4, 'debug': 8, 'fatal': 9, 'panic': 7.

This variable contains the physical interface number of the error log, if the log is related to a certain physical interface. Otherwise it will have the value 0

This variable contains the virtual interface number of the error log, if the log is related to a certain virtual interface. Otherwise it will have the value 0

The current state of device's trace log area. Enumeration: 'erase-log': 4, 'log-empty': 1, 'save-log': 3, 'log-present': 2.

The current trace log mask. The interpretation of this variable is device specific.

The current trace log mask. The interpretation of this variable is device specific.

The current trace log mask. The interpretation of this variable is device specific.

The size of the trace log area (in bytes).

This table provides access to the device's trace log.

The number of this trace log area slice (each of size `errorlogTraceSliceSize').

The size of this slice of the trace log area.

The data in this slice of the trace log area.

This variable contains the severity level determining which error logs will be written to permanent storage. Any error log with severity higher than or equal to this severity level will be stored for retrieval, even after a reset

This table contains Token Ring configuration information for each interface.

This number corresponds to the interface number, ifIndex, in ifTable from MIB-II.

The burnt-in MAC address for this interface.

The locally administered MAC address for this interface. If locally address MAC addresses are not used, this entry is all zeroes.

Indicates if early token release is used on the interface. Enumeration: 'disabled': 2, 'enabled': 1.

This trap is sent when the device tries to place a OBM callback phonecall to phone number obmCallbackPhoneNumber. Even though the call might be repeated several times before a connection is established, only one trap is sent.

This trap is sent when the device tries to place a OBM callout phonecall to phone number obmCalloutPhoneNumber because it was triggered by the event(s) obmCalloutTriggerEvent. Even though the call might be repeated several times before a connection is established, only one trap is sent.