>> MIB - Management Information Base
>> Table: trcBufTable - (.1.3.6.1.4.1.272.4.1.65.1.1.1)
Description: This object contains a trace buffer entry.
trcBufTable
OID | Name | Type | Access
.1 | Index | INTEGER | R
.2 | Device | DisplayString | R
.3 | Mode | ENUM | R
.4 | DataMode | ENUM | R
.5 | Size | INTEGER | R
.6 | DataSize | INTEGER | R
.7 | Date | Date | R
.8 | Descr | DisplayString | R
.9 | ID | Unsigned32 | R
.10 | Operation | ENUM | R
Index
Unique Index of the trace buffer
Device
The device representing this trace buffer Length: 0 to 255
Mode
Indicates operation mode of trace buffer: single-shot: just fill buffer up to maximum size continuous: ring buffer mode In single-shot mode every write attempt that would exceed buffer limits, causes the buffer to get closed for writing and the write attempt to fail (as any further attempts will). In continuous mode the buffer is filled up to the maximum size, and overwrite older data as new data gets written. Variable is meaningless as long as variable trcBufOperation is set to unused. Enumerations: single-shot (1) continuous (2)
DataMode
Indicates how trace buffer treats data written to it: In bytestream mode no structure is imposed on written data, buffer will get completely filled up if enough data is written. Data overwrite is done byte-by-byte. Mode message keeps the data structure in messages as passed down to the trace buffer and allows for reading them back in same portions as written. Mode message-per-session treats any data written to trace buffer between opening and closing it as one message. Variable is meaningless as long as variable trcBufOperation is set to unused. NOTE: modes message and message-per-session only reflect the last state; it depends on the application(s) writing to the trace buffer in which mode it is used, so this variable can toggle between these two states over time. Enumerations: bytestream (1) message (2) message-per-session (3)
Size
The maximum size of the trace buffer
DataSize
The current data size of the trace buffer
Date
Time and date of the buffer creation Range: 0 to -1
Descr
Optional descriptive information of the buffer's purpose. Length: 0 to 255
ID
Optional identificator for the buffer.
Operation
The current status of the trace buffer: unused: Device is free to be used idle : Device is parameterized but not open read : Device is open for reading write: Device is open for writing read-write: Device is open for reading and writing full: No more writing to buffer possible Value read-write would normally refer to two processes. Value full indicates that no more data can be written to buffer; it will remain unchanged until it gets deleted. Enumerations: unused (1) idle (2) read (3) write (4) closed (6)

MIB Reference to Software Version 10.2.12 generated on 2023/08/29. Provided by webmaster@bintec-elmeg.com Copyright ©2023 by bintec elmeg GmbH