OID reference
1.3.6.1.4.1.629.10.11.3.2.1
Compliance statement for agents that provide full support for BFD-MIB. Such devices can then be monitored and also be configured using this MIB module.
Identification
{1 3 6 1 4 1 629 10 11 3 2 1}
The displayed source records contain one distinct definition. Compare its source records.
bfdModuleFullCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance statement for agents that provide full
support for BFD-MIB. Such devices can
then be monitored and also be configured using
this MIB module."
MODULE -- This module.
MANDATORY-GROUPS {
bfdSessionGroup
-- bfdSessionPerfGroup,
-- bfdSessionPerfHCGroup,
-- bfdNotificationGroup
}
-- GROUP bfdSessionPerfHCGroup
-- DESCRIPTION
-- "This group is mandatory for those bfdPerfTable
-- entries for which any of the objects
-- bfdSessPerfPktInHC or bfdSessPerfPktOutHC
-- wraps around too quickly
-- based on the criteria specified in RFC 2863 for
-- high-capacity counters."
-- GROUP bfdNotificationGroup
-- DESCRIPTION
-- "This group is only mandatory for those
-- implementations which can efficiently implement
-- the notifications contained in this group."
OBJECT bfdSessAddrType
SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) }
DESCRIPTION
"Only unknown(0), ipv4(1) and ipv6(2) support
is required."
OBJECT bfdSessAddr
SYNTAX InetAddress (SIZE(0|4|16))
DESCRIPTION
"An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes."
::= { bfdCompliances 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Compliance statement for agents that provide full support for BFD-MIB. Such devices can then be monitored and also be configured using this MIB module.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: bfdModuleFullCompliance
{
"smi_kind": "MODULE-COMPLIANCE",
"definition": [
"bfdModuleFullCompliance",
"MODULE-COMPLIANCE",
"STATUS",
"current",
"DESCRIPTION",
"\"Compliance statement for agents that provide full support for BFD-MIB. Such devices can then be monitored and also be configured using this MIB module.\"",
"MODULE",
"MANDATORY-GROUPS",
"{",
"bfdSessionGroup",
"}",
"OBJECT",
"bfdSessAddrType",
"SYNTAX",
"InetAddressType",
"{",
"unknown",
"(",
"0",
")",
",",
"ipv4",
"(",
"1",
")",
",",
"ipv6",
"(",
"2",
")",
"}",
"DESCRIPTION",
"\"Only unknown(0), ipv4(1) and ipv6(2) support is required.\"",
"OBJECT",
"bfdSessAddr",
"SYNTAX",
"InetAddress",
"(",
"SIZE",
"(",
"0",
"|",
"4",
"|",
"16",
")",
")",
"DESCRIPTION",
"\"An implementation is only required to support unknown(0), ipv4(1) and ipv6(2) sizes.\"",
"::=",
"{",
"bfdCompliances",
"1",
"}"
],
"syntax_tree": [
[
"Status",
"current"
],
[
"DESCRIPTION",
"Compliance statement for agents that provide full support for BFD-MIB. Such devices can then be monitored and also be configured using this MIB module."
],
null,
[
"ComplianceModules",
[
[
null,
[
"bfdSessionGroup"
]
]
]
]
]
}Vendor MIB copy from the Observium Community archive.
Module: DC-BFD-STUB-MIB
See published definition above
{'IF-MIB': ['InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'enterprises', 'Unsigned32', 'Gauge32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP'], 'DC-MASTER-TC': ['AdminStatus', 'NpgOperStatus', 'NumericIndex', 'EntityProcType', 'InterfaceScope'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType']}Related source files and packages:
Registration