Status in source: current.
Names: fsFmTraceOption
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsFmTraceOption",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This object is used to enable trace statements in Fault Management module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Reserved Bit 3 - Control plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - Function Entry traces Bit 17 - Function exit traces Bit 18 - Critical traces Bit 19 - Remote Loopback test Bit 20 - Fault Event trigger traces Bit 21 - Event reception traces Bit 22 - Variable request/response traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to remote loopback test and event trigger trace messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set, then user has to give the value 0x300.\"",
"DEFVAL",
"{",
"'",
"00040000",
"'",
"H",
"}",
"::=",
"{",
"fsFmSystem",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This object is used to enable trace statements in Fault Management module. A four byte integer is used for enabling the trace level. Each bit in the four byte integer represents a particular trace level. The mapping between the bit positions & the trace level is as follows: Bit 0 - Init and Shutdown traces Bit 1 - Management traces Bit 2 - Reserved Bit 3 - Control plane traces Bit 4 - Packet Dump traces Bit 5 - Traces related to all resources except buffers Bit 6 - All Failure traces Bit 7 - Buffer allocation/release traces Bit 16 - Function Entry traces Bit 17 - Function exit traces Bit 18 - Critical traces Bit 19 - Remote Loopback test Bit 20 - Fault Event trigger traces Bit 21 - Event reception traces Bit 22 - Variable request/response traces The remaining bits are unused. Combination of levels are also allowed. For example if the bits 19 and 20 are set, then the trace statement related to remote loopback test and event trigger trace messages will be printed. The user has to enter the corresponding integer value for the bits set. For example if bits 8 and 9 are to be set, then user has to give the value 0x300."
],
null,
null,
null,
[
"DEFVAL",
"'00040000'H"
]
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: FM-MIB
See published definition above
Module imports
{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32', 'Unsigned32']}
Related source files and packages:
- Belden, GarrettCom and Hirschmann IT official standalone MIBs
· Publisher's source file: fsfm.mib
Module: FM-MIB
Same published definition
Module imports
{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Integer32', 'Unsigned32']}
Related source files and packages: