ieee8021BridgeCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for devices supporting bridging
services as defined in 802.1D-2004. Such devices support
path cost values of 32-bits, and bridge and port priority
values are more restricted than in 802.1D-1995.
Full support for the 802.1D management objects requires
implementation of the objects listed in the systemGroup
from the SNMPv2-MIB [RFC3418], as well as the objects
listed in the ifGeneralInformationGroup from the
IF-MIB [RFC2863]."
MODULE SNMPv2-MIB -- The SNMPv2-MIB, RFC 3418
MANDATORY-GROUPS {
systemGroup
}
MODULE IF-MIB -- The interfaces MIB, RFC 2863
MANDATORY-GROUPS {
ifGeneralInformationGroup
}
MODULE
MANDATORY-GROUPS {
ieee8021BridgeBaseBridgeGroup,
ieee8021BridgeBasePortGroup
}
GROUP ieee8021BridgeCreatableBaseBridgeGroup
DESCRIPTION
"Implementation of this group is mandatory for
bridges that allow management systems to add and delete
bridge components. Provider Backbone Edge Bridges would
typically fall in this category."
GROUP ieee8021BridgeTpPortGroup
DESCRIPTION
"Implementation of this group is mandatory for
bridges that support the transparent bridging
mode. A transparent bridge will implement
this group."
GROUP ieee8021BridgeInternalLANGroup
DESCRIPTION
"Implementation of this group is optional. It can be supported
to provide control over the relationship between interfaces and
bridge ports where such relationships are more complex than a
simple 1-to-1 mapping."
GROUP ieee8021BridgeDot1dDynamicPortCreationGroup
DESCRIPTION
"Implementation of this group is optional. It can be supported
to provide the ability to dynamically create and deleted 802.1D
bridge ports."
View at oid-info.com
The compliance statement for devices supporting bridging
services as defined in 802.1D-2004. Such devices support
path cost values of 32-bits, and bridge and port priority
values are more restricted than in 802.1D-1995.
Full support for the 802.1D management objects requires
implementation of the objects listed in the systemGroup
from the SNMPv2-MIB [RFC3418], as well as the objects
listed in the ifGeneralInformationGroup from the
IF-MIB [RFC2863].
Parsed from file IEEE8021-BRIDGE-MIB.mib.txt
Company: None
Module: IEEE8021-BRIDGE-MIB
The compliance statement for devices supporting bridging
services as defined in 802.1D-2004. Such devices support
path cost values of 32-bits, and bridge and port priority
values are more restricted than in 802.1D-1995.
Full support for the 802.1D management objects requires
implementation of the objects listed in the systemGroup
from the SNMPv2-MIB [RFC3418], as well as the objects
listed in the ifGeneralInformationGroup from the
IF-MIB [RFC2863].
Automatically extracted from IEEE Management Information Bases (MIBs).
ieee8021BridgeCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for devices supporting bridging services as defined in 802.1D-2004. Such devices support path cost values of 32-bits, and bridge and port priority values are more restricted than in 802.1D-1995. Full support for the 802.1D management objects requires implementation of the objects listed in the systemGroup from the SNMPv2-MIB [RFC3418], as well as the objects listed in the ifGeneralInformationGroup from the IF-MIB [RFC2863]." MODULE SNMPv2-MIB MANDATORY-GROUPS { systemGroup } MODULE IF-MIB MANDATORY-GROUPS { ifGeneralInformationGroup } MODULE MANDATORY-GROUPS { ieee8021BridgeBaseBridgeGroup, ieee8021BridgeBasePortGroup } GROUP ieee8021BridgeCreatableBaseBridgeGroup DESCRIPTION "Implementation of this group is mandatory for bridges that allow management systems to add and delete bridge components. Provider Backbone Edge Bridges would typically fall in this category." GROUP ieee8021BridgeTpPortGroup DESCRIPTION "Implementation of this group is mandatory for bridges that support the transparent bridging mode. A transparent bridge will implement this group." GROUP ieee8021BridgeInternalLANGroup DESCRIPTION "Implementation of this group is optional. It can be supported to provide control over the relationship between interfaces and bridge ports where such relationships are more complex than a simple 1-to-1 mapping." GROUP ieee8021BridgeDot1dDynamicPortCreationGroup DESCRIPTION "Implementation of this group is optional. It can be supported to provide the ability to dynamically create and deleted 802.1D bridge ports." ::= { ieee8021BridgeCompliances 1 }
ieee8021BridgeCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for devices supporting bridging services as defined in 802.1D-2004. Such devices support path cost values of 32-bits, and bridge and port priority values are more restricted than in 802.1D-1995. Full support for the 802.1D management objects requires implementation of the objects listed in the systemGroup from the SNMPv2-MIB [RFC3418], as well as the objects listed in the ifGeneralInformationGroup from the IF-MIB [RFC2863]." MODULE SNMPv2-MIB MANDATORY-GROUPS { systemGroup } MODULE IF-MIB MANDATORY-GROUPS { ifGeneralInformationGroup } MODULE MANDATORY-GROUPS { ieee8021BridgeBaseBridgeGroup, ieee8021BridgeBasePortGroup } GROUP ieee8021BridgeCreatableBaseBridgeGroup DESCRIPTION "Implementation of this group is mandatory for bridges that allow management systems to add and delete bridge components. Provider Backbone Edge Bridges would typically fall in this category." GROUP ieee8021BridgeTpPortGroup DESCRIPTION "Implementation of this group is mandatory for bridges that support the transparent bridging mode. A transparent bridge will implement this group." GROUP ieee8021BridgeInternalLANGroup DESCRIPTION "Implementation of this group is optional. It can be supported to provide control over the relationship between interfaces and bridge ports where such relationships are more complex than a simple 1-to-1 mapping." GROUP ieee8021BridgeDot1dDynamicPortCreationGroup DESCRIPTION "Implementation of this group is optional. It can be supported to provide the ability to dynamically create and deleted 802.1D bridge ports." ::= { ieee8021BridgeCompliances 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.111.2.802.1.1.2.2.1.2 | ieee8021BridgePriorityAndMulticastFilteringCompliance | 0 | 0 | The compliance statement for device support of Priority and Multicast Filtering extended bridging services. |
| 1.3.111.2.802.1.1.2.2.1.3 | ieee8021BridgeCompliance1 | 0 | 0 | The compliance statement for devices supporting VLAN-unaware bridging services as defined in IEEE Std 802.1Q. Such devices suppo… |