Status in source: current.
Names: fsMIFsIpContextDebug
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMIFsIpContextDebug",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Enables the tracing in the selected submodule in IP. A 32 bit integer is used to store the Tracing level in the specified module. Different Tracing Levels - BIT 0 - Initialisation and Shutdown Trace. BIT 1 - Management trace. BIT 2 - Data path trace. BIT 3 - Control Plane trace. BIT 4 - Packet Dump. BIT 5 - OS Resource trace. BIT 6 - All Failure trace (All failures including Packet Validation) BIT 7 - Buffer Trace. Different submodule Tracing - BIT 16 - Tracing in IP module. BIT 17 - Tracing in ICMP submodule. BIT 19 - Tracing in RIP submodule. BIT 20 - Tracing in ARP submodule. BIT 21 - Tracing in BOOTP submodule. BIT 22 - Tracing in UDP submodule. The remaining bits are used.The combination of levels and submodules are allowed i.e. Tracing can be allowed at all failure and data path level in All submodules by setting the BIT appropriately. For Example, setting the debug valut to 0b00000000000000010000000001000000 will enable all failure trace prints in IP module.\"",
"::=",
"{",
"fsMIFsIpGlobalEntry",
"13",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Enables the tracing in the selected submodule in IP. A 32 bit integer is used to store the Tracing level in the specified module. Different Tracing Levels - BIT 0 - Initialisation and Shutdown Trace. BIT 1 - Management trace. BIT 2 - Data path trace. BIT 3 - Control Plane trace. BIT 4 - Packet Dump. BIT 5 - OS Resource trace. BIT 6 - All Failure trace (All failures including Packet Validation) BIT 7 - Buffer Trace. Different submodule Tracing - BIT 16 - Tracing in IP module. BIT 17 - Tracing in ICMP submodule. BIT 19 - Tracing in RIP submodule. BIT 20 - Tracing in ARP submodule. BIT 21 - Tracing in BOOTP submodule. BIT 22 - Tracing in UDP submodule. The remaining bits are used.The combination of levels and submodules are allowed i.e. Tracing can be allowed at all failure and data path level in All submodules by setting the BIT appropriately. For Example, setting the debug valut to 0b00000000000000010000000001000000 will enable all failure trace prints in IP module."
],
null,
null,
null,
null
]
}
- 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: ARICENT-MIFS-IP-MIB
See published definition above
Module imports
{'SNMPv2-TC': ['DisplayString', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'IpAddress', 'Counter32', 'Integer32', 'enterprises'], 'ARICENT-MISTD-IPVX-MIB': ['fsMIStdIpContextId']}
Related source files and packages:
- Belden, GarrettCom and Hirschmann IT official standalone MIBs
· Publisher's source file: fsmpip.mib
Module: ARICENT-MIFS-IP-MIB
Same published definition
Module imports
{'SNMPv2-TC': ['DisplayString', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'IpAddress', 'Counter32', 'Integer32', 'enterprises'], 'ARICENT-MISTD-IPVX-MIB': ['fsMIStdIpContextId']}
Related source files and packages: