OID reference
1.3.6.1.4.1.1991.3.3.1.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 1991 3 3 1 3 2 1}
Available source records contain 2 distinct definitions; some records may not include a 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 -- 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 INTEGER { unknown(0), ipv4(1), ipv6(2) }
-- 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 }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 INTEGER { unknown(0), ipv4(1), ipv6(2) }
-- 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)Netdisco MIB archive copies
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",
",",
"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",
"INTEGER",
"{",
"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",
"bfdSessionPerfGroup",
"bfdSessionPerfHCGroup",
"bfdNotificationGroup",
"bfdSessionPerfHCGroup",
"bfdNotificationGroup"
]
]
]
]
]
}Vendor MIB copy from the LibreNMS archive.
Module: FOUNDRY-BFD-STD-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'Counter64', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetPortNumber'], 'FOUNDRY-SN-ROOT-MIB': ['bfd']}Related source files and packages:
Same file in Observium Community.
Vendor MIB copy from the Netdisco archive.
Module: FOUNDRY-BFD-STD-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'StorageType', 'TimeStamp'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'Counter64', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddress', 'InetAddressType', 'InetPortNumber'], 'FOUNDRY-SN-ROOT-MIB': ['bfd']}Related source files and packages:
Registration