|
|
|
|
Description:
|
ieee8021BridgeCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for devices supporting
VLAN-unaware bridging services as defined in
IEEE Std 802.1Q. Such devices support
path cost values of 32-bits, and Bridge and port priority
values are more restricted than in IEEE Std 802.1D-1995.
Full support for the IEEE 802.1Q 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 delete
Bridge Ports."
|
|
|
|
Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved, Orange © 2024 |
