draft-ietf-bridge-rstpmib-01.txt   draft-ietf-bridge-rstpmib-02.txt 
Internet Draft E. Bell Internet Draft V. Ngai
Expires January 2001 3Com Corp. Expires August 2002 Enterasys Networks
draft-ietf-bridge-rstpmib-01.txt V. Ngai draft-ietf-bridge-rstpmib-02.txt E. Bell
Enterasys Networks 3Com Corp.
November 2001 March 2002
Definitions of Managed Objects for Bridges with Rapid Spanning Tree Definitions of Managed Objects for Bridges
Protocol and VLAN Classification Extensions with Rapid Spanning Tree Protocol
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions This document is an Internet-Draft and is subject to all provisions
of Section 10 of RFC2026. Internet-Drafts are working documents of of Section 10 of RFC2026. Internet-Drafts are working documents of
the Internet Engineering Task Force (IETF), its areas, and its the Internet Engineering Task Force (IETF), its areas, and its
working groups. Note that other groups may also distribute working working groups. Note that other groups may also distribute working
documents as Internet-Drafts. documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
skipping to change at page 1, line 39 skipping to change at page 1, line 39
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP based internets. for use with network management protocols in TCP/IP based internets.
In particular, it defines three MIB modules for managing the new In particular, it defines a MIB module for managing the Rapid
capabilities of MAC bridges defined by the IEEE P802.1t [802.1t], Spanning Tree capability defined by the IEEE P802.1t [802.1t] and
P802.1u [802.1u], P802.1v [802.1v] and P802.1w [802.1w] amendments to P802.1w [802.1w] amendments to IEEE Std 802.1D-1998 for bridging
IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) between Local Area Network (LAN) segments.
segments. One MIB module defines objects for managing Rapid Spanning
Tree Protocol, one for controlling Restricted VLAN Registration, and
one for VLAN Classification.
Provisions are made for support of transparent bridging. Provisions Provisions are made for support of transparent bridging. Provisions
are also made so that these objects apply to bridges connected by are also made so that these objects apply to bridges connected by
subnetworks other than LAN segments. This memo also includes several subnetworks other than LAN segments. This memo also includes a MIB
MIB modules in a manner that is compliant to SMIv2 [RFC2578]. module in a manner that is compliant to SMIv2 [RFC2578].
This memo supplements RFC 1493 [BRIDGEMIB] and RFC 2674 [Q-BRIDGE- This memo supplements RFC 1493 [BRIDGEMIB] and RFC 2674 [Q-BRIDGE-
MIB]. MIB].
Table of Contents Table of Contents
1 The SNMP Management Framework ................................ 3 1 The SNMP Management Framework ................................ 3
2 Overview ..................................................... 4 2 Overview ..................................................... 4
2.1 Scope ...................................................... 4 2.1 Scope ...................................................... 4
3 Structure of MIBs ............................................ 4 3 Structure of MIBs ............................................ 4
3.1 Structure of RSTP-MIB ...................................... 5 3.1 Structure of RSTP-MIB ...................................... 4
3.2 Structure of U-BRIDGE-MIB .................................. 5 3.4 Relationship to Other MIBs ................................. 5
3.3 Structure of V-BRIDGE-MIB .................................. 6 3.4.1 Relationship to Original Bridge MIB ...................... 5
3.3.1 The dot1vProtocol Group .................................. 6 3.4.1.1 The dot1dBase Group .................................... 5
3.4 Relationship to Other MIBs ................................. 6 3.4.1.2 The dot1dStp Group ..................................... 5
3.4.1 Relationship to Original Bridge MIB ...................... 6 3.4.1.3 The dot1dTp Group ...................................... 6
3.4.1.1 The dot1dBase Group .................................... 6 3.4.1.4 The dot1dStatic Group .................................. 6
3.4.1.2 The dot1dStp Group ..................................... 7 4 Definition for RSTP-MIB ...................................... 7
3.4.1.3 The dot1dTp Group ...................................... 7 5 Acknowledgments .............................................. 13
3.4.1.4 The dot1dStatic Group .................................. 8 6 Security consideration ....................................... 13
3.4.2 Relation to the P-BRIDGE-MIB module defined in RFC2674 ... 8 7 References ................................................... 14
3.4.3 Relation to the Q-BRDIGE-MIB module defined in RFC2674 ... 8 8 Authors' Addresses ........................................... 16
4 Definition for RSTP-MIB ...................................... 8 9 Full Copyright ............................................... 17
5 Definition for U-BRIDGE-MIB .................................. 14
6 Definition for V-BRIDGE-MIB .................................. 20
7 Acknowledgments .............................................. 25
8 Security consideration ....................................... 25
9 References ................................................... 26
10 Authors' Addresses .......................................... 28
11 Full Copyright .............................................. 29
1. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
skipping to change at page 4, line 9 skipping to change at page 4, line 9
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
2. Overview 2. Overview
A common device present in many networks in the Bridge. This device A common device present in many networks is the Bridge. This device
is used to connect Local Area Network segments below the network is used to connect Local Area Network segments below the network
layer. These devices are often known as 'layer 2 switches'. layer. These devices are often known as 'layer 2 switches'.
There are two major modes defined for this bridging: Source-Route and There are two major modes defined for this bridging: Source-Route and
transparent. Source-Route bridging is described by IEEE 802.5 transparent. Source-Route bridging is described by IEEE 802.5
[802.5] and is not discussed further in this document. [802.5] and is not discussed further in this document.
The transparent method of bridging is defined by IEEE 802.1D-1998 The transparent method of bridging is defined by IEEE 802.1D-1998
[802.1D] Managed objects for that original specification of [802.1D] Managed objects for that original specification of
transparent bridging were defined in RFC 1493 [BRIDGEMIB]. transparent bridging were defined in RFC 1493 [BRIDGEMIB].
2.1. Scope 2.1. Scope
This MIB includes a comprehensive set of managed objects which This MIB includes a comprehensive set of managed objects which
attempts to match the set defined in IEEE P802.1t [802.1t], P802.1u attempts to match the set defined in IEEE P802.1t [802.1t] and
[802.1u], P802.1v [802.1v] and P802.1w [802.1w]. P802.1w [802.1w].
3. Structure of MIBs 3. Structure of MIBs
This document defines additional objects, on top of those existing in This document defines additional managed objects for Rapid Spanning
the original BRIDGE-MIB module defined in [BRIDGEMIB]: that MIB Tree Protocol defined by IEEE P802.1t and IEEE P802.1w, on top of
module is to be maintained unchanged for backwards compatibility. those existing in the original BRIDGE-MIB module defined in
Section 3.4.3 of the present document contains some recommendations [BRIDGEMIB]: that MIB module is to be maintained unchanged for
regarding usage of objects in the original bridge MIB by devices backwards compatibility. Section 3.4.1 of the present document
implementing the enhancements defined here. contains some recommendations regarding usage of objects in the
original bridge MIB by devices implementing the enhancements defined
Three MIB modules are defined here: here.
(1) Managed objects for an extended bridge MIB module RSTP-MIB for
Rapid Spanning Tree Protocol defined by IEEE P802.1t and IEEE
P802.1w.
(2) Managed Objects for an extended virtual bridge MIB module U-
BRIDGE-MIB for Restricted VLAN Registration control
enhancement defined by IEEE P802.1u.
(3) Managed Objects for an extended bridge MIB module V-BRIDGE-MIB
for VLAN classification by Protocol and Port enhancement
defined by IEEE P802.1v.
3.1. Structure of RSTP-MIB 3.1. Structure of RSTP-MIB
Objects in this MIB are defined as an addition to the dot1dStp group Objects in this MIB are defined as an addition to the dot1dStp group
in the original bridge MIB [BRIDGE-MIB]. The overall structure is in the original bridge MIB [BRIDGE-MIB]. The overall structure is
shown below: shown below:
Bridge MIB Name IEEE P802.1t(t) or 802.1w(w) Bridge MIB Name IEEE P802.1t(t) or 802.1w(w)
Reference Reference
skipping to change at page 5, line 25 skipping to change at page 5, line 19
dot1dStpVersion (w) 17.6.1 ForceVersion dot1dStpVersion (w) 17.6.1 ForceVersion
dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount dot1dStpTxHoldCount (w) 17.16.6 TxHoldCount
dot1dStpPathCostDefault dot1dStpPathCostDefault
dot1dStpExtPortTable dot1dStpExtPortTable
dot1dStpPortProtocolMigration (w) 17.18.10 mcheck dot1dStpPortProtocolMigration (w) 17.18.10 mcheck
dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort dot1dStpPortAdminEdgePort (t) 18.3.3 adminEdgePort
dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort dot1dStpPortOperEdgePort (t) 18.3.4 operEdgePort
dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC dot1dStpPortAdminPointToPoint (w) 6.4.3 adminPointToPointMAC
dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC dot1dStpPortOperPointToPoint (w) 6.4.3 operPointToPointMAC
3.2. Structure of U-BRIDGE-MIB
Objects in this MIB are defined as an addition to the dot1qVlan group
in the Virtual Bridge MIB [Q-BRIDGE-MIB]. The overall structure is
shown below:
Virtual Bridge MIB Name IEEE P802.1u(u) or
P802.1t(t) Reference
dot1dGmrp
dot1dExtPortGmrpTable
dot1dPortRestrictedGroupRegistration
(t) 10.3.2.3 Restricted
Group Registration
dot1qVlan
dot1qExtPortVlanTable
dot1qPortRestrictedVlanRegistration
(u) 11.2.3.2.3 Restricted
VLAN Registration
gmrpFailure (t) 14.10.1.2 GMRP failure
notification
gvrpFailure (t) 12.10.1.6 GVRP failure
notification
3.3. Structure of V-BRIDGE-MIB
Objects in this MIB are arranged in a single group which is organized
as a set of related objects. The overall structure and assignment of
objects to the group is shown below:
Bridge MIB Name IEEE P802.1v Reference
dot1vProtocol
dot1vProtocolGroupTable 8.6.4 Protocol Group Database,
8.6.2 Protocol Template
dot1vProtocolTemplateFrameType
dot1vProtocolTemplateProtocolValue
dot1vProtocolGroupId 8.6.3 Protocol Group Identifier
dot1vProtocolPortTable 8.4.4 VID Set for each Port
dot1vProtocolPortGroupId
dot1vProtocolGroupVid
3.3.1. The dot1vProtocol Group
This group contains objects that describe the bridge's state with
respect VLAN classification by Protocol and Port. If VLAN
classification is not supported, this group will not be implemented.
3.4. Relationship to Other MIBs 3.4. Relationship to Other MIBs
As described above, some IEEE 802.1D management objects have not been As described above, some IEEE 802.1D management objects have not been
included in this MIB because they overlap with objects in other MIBs included in this MIB because they overlap with objects in other MIBs
applicable to a bridge implementing this MIB. In particular, it is applicable to a bridge implementing this MIB. In particular, it is
assumed that a bridge implementing this MIB will implement the assumed that a bridge implementing this MIB will implement the
original bridge MIB [BRIDGEMIB]. If the U-BRIDGE-MIB and V-BRIDGE- original bridge MIB [BRIDGEMIB].
MIB modules are implemented, a bridge will also implement the P-
BRIDGE-MIB and the Q-BRIDGE-MIB modules defined in RFC 2674
[RFC2674].
3.4.1. Relation to Original Bridge MIB 3.4.1. Relation to Original Bridge MIB
This section defines how objects in the original bridge MIB module This section defines how objects in the original bridge MIB module
[BRIDGEMIB] should be represented for devices which implement all the [BRIDGEMIB] should be represented for devices which implement all the
MIB modules described in this memo. Some of the old objects are less MIB modules described in this memo. Some of the old objects are less
useful in such devices but must still be implemented for reasons of useful in such devices but must still be implemented for reasons of
backwards compatibility. backwards compatibility.
3.4.1.1. The dot1dBase Group 3.4.1.1. The dot1dBase Group
skipping to change at page 8, line 11 skipping to change at page 7, line 5
This group contains objects that describe the entity's state with This group contains objects that describe the entity's state with
respect to transparent bridging. Interpretation for this group is respect to transparent bridging. Interpretation for this group is
unchanged. unchanged.
3.4.1.4. The dot1dStatic Group 3.4.1.4. The dot1dStatic Group
This group contains objects that describe the entity's state with This group contains objects that describe the entity's state with
respect to destination-address filtering. Interpretation for this respect to destination-address filtering. Interpretation for this
group is unchanged. group is unchanged.
3.4.2. Relation to the P-BRIDGE-MIB module defined in RFC 2674
The P-BRIDGE-MIB module contains managed objects for the traffic
class and multicast filtering enhancements defined by IEEE 802.1D-
1998 [802.1D]. Interpretation for all groups defined in this module
is unchanged.
3.4.3. Relation to the Q-BRIDGE-MIB module defined in RFC 2674
The Q-BRIDGE-MIB module contains managed objects for the Virtual LAN
bridging enhancements defined by IEEE 802.1Q-1998 [802.1Q].
Interpretation for all groups defined in this module is unchanged.
4. Definitions for RSTP-MIB 4. Definitions for RSTP-MIB
RSTP-MIB DEFINITIONS ::= BEGIN RSTP-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- MIB for IEEE 802.1w Rapid Spanning Tree Protocol -- MIB for IEEE 802.1w Rapid Spanning Tree Protocol
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
skipping to change at page 14, line 5 skipping to change at page 13, line 5
} }
GROUP rstpDefaultPathCostGroup GROUP rstpDefaultPathCostGroup
DESCRIPTION DESCRIPTION
"Support for this group is mandatory only if "Support for this group is mandatory only if
both 16-bit and 32-bit Path Costs are supported." both 16-bit and 32-bit Path Costs are supported."
::= { rstpCompliances 1 } ::= { rstpCompliances 1 }
END END
5. Definitions for U-BRIDGE-MIB 5. Acknowledgments
U-BRIDGE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI
TruthValue, MacAddress
FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
dot1dBridge, dot1dBasePort, dot1dBasePortEntry
FROM BRIDGE-MIB
dot1qPvid, dot1qVlan
FROM Q-BRIDGE-MIB
dot1dGmrp
FROM P-BRIDGE-MIB;
uBridgeMIB MODULE-IDENTITY
LAST-UPDATED "200111160000Z"
ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO
"Email: Bridge-mib@ietf.org"
DESCRIPTION
"The Bridge MIB Extension module for managing devices
that allow control over dynamic VLAN registration through
Restricted VLAN Registration as defined by IEEE 802.1u."
REVISION "200111160000Z"
DESCRIPTION
"Draft 1"
::= { dot1dBridge 12 }
dot1dExtPortGmrpTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dExtPortGmrpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing per port Restricted Group Registration
control information."
::= { dot1dGmrp 2 }
dot1dExtPortGmrpEntry OBJECT-TYPE
SYNTAX Dot1dExtPortGmrpEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information controlling Group Registration for a port
on the device. This is indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry }
::= { dot1dExtPortGmrpTable 1 }
Dot1dExtPortGmrpEntry ::=
SEQUENCE {
dot1dPortRestrictedGroupRegistration
TruthValue,
dot1dPortLastGroupFailed
MacAddress,
dot1dPortGmrpFailingReason
INTEGER
}
dot1dPortRestrictedGroupRegistration OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The state of Restricted Group Registration on this port.
If the value of this control is true(1), then creation
of a new dynamic entry is permitted only if there is a
Static Filtering Entry for the VLAN concerned, in which
the Registrar Administrative Control value is Normal
Registration."
REFERENCE
"IEEE 802.1t clause 10.3.2.3, 14.10.1.3."
DEFVAL { false }
::= { dot1dExtPortGmrpEntry 1 }
dot1dPortLastGroupFailed OBJECT-TYPE
SYNTAX MacAddress
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The MAC address of the Group GMRP failed to register
on this port. This object is accessible only through
gmrpFailure notification."
REFERENCE
"IEEE 802.1t clause 14.10.1.2.3a."
::= { dot1dExtPortGmrpEntry 2 }
dot1dPortGmrpFailingReason OBJECT-TYPE
SYNTAX INTEGER {
lackOfResources(1),
registrationRestricted(2)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The reason for the last registration failure on this
port. The value 'lackofResources(1)' indicates that
GMRP failed due to lack of resources in the Filtering
Database for the creation of a Group Registration
Entry. The value 'registrationRestricted(2)'
indicates that GMRP failed because dynamic group is
restricted. This object is accessible only through
gmrpFailure notification."
REFERENCE
"IEEE 802.1t clause 14.10.1.2.3c."
::= { dot1dExtPortGmrpEntry 3 }
dot1qExtPortVlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qExtPortVlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table containing per port Restricted VLAN Registration
control information."
::= { dot1qVlan 11 }
dot1qExtPortVlanEntry OBJECT-TYPE
SYNTAX Dot1qExtPortVlanEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information controlling VLAN Registration for a port
on the device. This is indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry }
::= { dot1qExtPortVlanTable 1 }
Dot1qExtPortVlanEntry ::=
SEQUENCE {
dot1qPortRestrictedVlanRegistration
TruthValue,
dot1qPortGvrpFailingReason
INTEGER
}
dot1qPortRestrictedVlanRegistration OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The state of Restricted VLAN Registration on this port.
If the value of this control is true(1), then creation
of a new dynamic VLAN entry is permitted only if there
is a Static VLAN Registration Entry for the VLAN concerned,
in which the Registrar Administrative Control value for
this port is Normal Registration."
REFERENCE
"IEEE 802.1u clause 11.2.3.2.3, 12.10.1.7."
DEFVAL { false }
::= { dot1qExtPortVlanEntry 1 }
dot1qPortGvrpFailingReason OBJECT-TYPE
SYNTAX INTEGER {
lackOfResources(1),
registrationRestricted(2),
unsupportedVID(3)
}
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The reason for the last registration failure on this
port. The value 'lackofResources(1)' indicates that
GVRP failed due to lack of resources in the Filtering
Database for the creation of a VLAN Registration
Entry. The value 'registrationRestricted(2)' indicates
that GVRP failed because dynamic VLAN registration is
restricted. And the value 'unsupportedVID(3)'
indicates that a registration request for an
unsupported VID is received."
REFERENCE
"IEEE 802.1u clause 12.10.1.6.3c."
::= { dot1qExtPortVlanEntry 2 }
gmrpFailure NOTIFICATION-TYPE
OBJECTS { dot1dPortLastGroupFailed,
dot1dBasePort,
dot1dPortGmrpFailingReason }
STATUS current
DESCRIPTION
"The trap that is generated when there is a GMRP
failure. dot1dPortLastGroupFailed indicates the
MAC address of the Group that has failed to be
registered, dot1dBasePort indicates the port on
which the registration is received, and
dot1dPortGmrpFailingReason indicates the reason for
the failure."
REFERENCE
"IEEE 802.1t 14.10.1.2."
::= { dot1dBridge 0 3 }
gvrpFailure NOTIFICATION-TYPE
OBJECTS { dot1qPvid,
dot1dBasePort,
dot1qPortGvrpFailingReason }
STATUS current
DESCRIPTION
"The trap that is generated when there is a GVRP
failure. dot1qPvid indicates the VID of he VLAN
that GVRP has failed to register, dot1dBasePort
indicates the port on which the registration is
received, and dot1qPortGvrpFailingReason indicates
the reason for the failure."
REFERENCE
"IEEE 802.1t 12.10.1.6."
::= { dot1dBridge 0 4 }
uBridgeConformance OBJECT IDENTIFIER ::= { uBridgeMIB 1 }
uBridgeGroups OBJECT IDENTIFIER ::= { uBridgeConformance 1 }
uBridgeCompliances OBJECT IDENTIFIER ::= { uBridgeConformance 2 }
uBridgePortVlanGroup OBJECT-GROUP
OBJECTS {
dot1qPortRestrictedVlanRegistration,
dot1qPortGvrpFailingReason
}
STATUS current
DESCRIPTION
"Per-port Restricted VLAN Registration Control parameter"
::= { uBridgeGroups 1 }
uBridgePortGmrpGroup OBJECT-GROUP
OBJECTS {
dot1dPortRestrictedGroupRegistration,
dot1dPortLastGroupFailed,
dot1dPortGmrpFailingReason
}
STATUS current
DESCRIPTION
"Per-port Restricted Group Registration Control parameter"
::= { uBridgeGroups 2 }
uBridgeTrapGroup NOTIFICATION-GROUP
NOTIFICATIONS {
gmrpFailure,
gvrpFailure
}
STATUS current
DESCRIPTION
"GMRP and GVRP notifications"
::= { uBridgeGroups 3 }
uBridgeCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for device support of bridging
services."
MODULE
GROUP uBridgePortVlanGroup
DESCRIPTION
"Support for this object group is optional."
GROUP uBridgePortGmrpGroup
DESCRIPTION
"Support for this object group is optional."
GROUP uBridgeTrapGroup
DESCRIPTION
"Support for this notification group is optional."
::= { uBridgeCompliances 1 }
END
6. Definitions for V-BRIDGE-MIB
V-BRIDGE-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
dot1dBridge, dot1dBasePort
FROM BRIDGE-MIB;
vBridgeMIB MODULE-IDENTITY
LAST-UPDATED "200106300000Z"
ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO
"Email: Bridge-mib@ietf.org"
DESCRIPTION
"The Bridge MIB Extension module for managing devices
that support VLAN Classification by Protocol and Port
defined in IEEE 802.1v."
REVISION "200106300000Z"
DESCRIPTION
"Draft 0"
::= { dot1dBridge 13 }
vBridgeMIBObjects OBJECT IDENTIFIER ::= { vBridgeMIB 1 }
dot1vProtocol OBJECT IDENTIFIER ::= { vBridgeMIBObjects 1 }
dot1vProtocolGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1vProtocolGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains mappings from Protocol
Templates to Protocol Group Identifiers used for
Port-and-Protocol-based VLAN Classification."
REFERENCE
"IEEE 802.1v clause 8.6.4"
::= { dot1vProtocol 1 }
dot1vProtocolGroupEntry OBJECT-TYPE
SYNTAX Dot1vProtocolGroupEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A mapping from a Protocol Template to a Protocol
Group Identifier."
INDEX { dot1vProtocolTemplateFrameType,
dot1vProtocolTemplateProtocolValue }
::= { dot1vProtocolGroupTable 1 }
Dot1vProtocolGroupEntry ::=
SEQUENCE {
dot1vProtocolTemplateFrameType
INTEGER,
dot1vProtocolTemplateProtocolValue
OCTET STRING,
dot1vProtocolGroupId
INTEGER
}
dot1vProtocolTemplateFrameType OBJECT-TYPE
SYNTAX INTEGER {
ethernet (1),
rfc1042 (2),
snap8021H (3),
snapOther (4),
llcOther (5)
}
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The data-link encapsulation format or the
'detagged_frame_type' in a Protocol Template."
REFERENCE
"IEEE 802.1v clause 8.6.2"
::= { dot1vProtocolGroupEntry 1 }
dot1vProtocolTemplateProtocolValue OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2 | 5))
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The identification of the protocol above the data-link
layer in a Protocol Template. Depending on the
frame type, the octet string will have one of the
following values:
For 'ethernet', 'rfc1042' and 'snap8021H',
this is the 16-bit (2-octet) IEEE 802.3 Type Field.
For 'snapOther',
this is the 40-bit (5-octet) PID.
For 'llcOther',
this is the 2-octet IEEE 802.2 LSAP pair:
first octet for DSAP and second octet for SSAP."
REFERENCE
"IEEE 802.1v clause 8.6.2"
::= { dot1vProtocolGroupEntry 2 }
dot1vProtocolGroupId OBJECT-TYPE
SYNTAX INTEGER (0..2147483647)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Represents a group of protocols that are associated
together when assigning a VID to a frame."
REFERENCE
"IEEE 802.1v clause 8.6.3, 12.10.2.1"
::= { dot1vProtocolGroupEntry 3 }
dot1vProtocolPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1vProtocolPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A table that contains VID sets used for
Port-and-Protocol-based VLAN Classification."
REFERENCE
"IEEE 802.1v clause 8.4.4"
::= { dot1vProtocol 2 }
dot1vProtocolPortEntry OBJECT-TYPE
SYNTAX Dot1vProtocolPortEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A VID set for a port."
INDEX { dot1dBasePort,
dot1vProtocolPortGroupId }
::= { dot1vProtocolPortTable 1 }
Dot1vProtocolPortEntry ::=
SEQUENCE {
dot1vProtocolPortGroupId
INTEGER,
dot1vProtocolPortGroupVid
INTEGER
}
dot1vProtocolPortGroupId OBJECT-TYPE
SYNTAX INTEGER (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Designates a group of protocols in the Protocol
Group Database."
REFERENCE
"IEEE 802.1v clause 8.6.3, 12.10.1.2"
::= { dot1vProtocolPortEntry 1 }
dot1vProtocolPortGroupVid OBJECT-TYPE
SYNTAX INTEGER (1..4094)
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The VID associated with a group of protocols for
each port."
REFERENCE
"IEEE 802.1v clause 8.4.4, 12.10.1.2"
::= { dot1vProtocolPortEntry 2 }
vBridgeConformance OBJECT IDENTIFIER ::= { vBridgeMIB 2 }
vBridgeGroups OBJECT IDENTIFIER ::= { vBridgeConformance 1 }
vBridgeCompliances OBJECT IDENTIFIER ::= { vBridgeConformance 2 }
vBridgeDeviceGroup OBJECT-GROUP
OBJECTS {
dot1vProtocolGroupId
}
STATUS current
DESCRIPTION
"VLAN classification information for the bridge."
::= { vBridgeGroups 1 }
vBridgePortGroup OBJECT-GROUP
OBJECTS {
dot1vProtocolPortGroupVid
}
STATUS current
DESCRIPTION
"VLAN classification information for individual ports."
::= { vBridgeGroups 2 }
vBridgeCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for device support of bridging
services."
MODULE
MANDATORY-GROUPS {
vBridgeDeviceGroup,
vBridgePortGroup
}
::= { vBridgeCompliances 1 }
END
7. Acknowledgments
This document was produced on behalf of the Bridge MIB Working Group This document was produced on behalf of the Bridge MIB Working Group
in the Operations and Management area of the Internet Engineering in the Operations and Management area of the Internet Engineering
Task Force. Task Force.
The authors wish to thank the members of the Bridge MIB Working Group The authors wish to thank the members of the Bridge MIB Working Group
and Anders SW Christensen in particular for their comments and for their comments and suggestions which improved this effort.
suggestions which improved this effort.
8. Security Considerations 6. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
SNMPv1 by itself is not a secure environment. Even if the network SNMPv1 by itself is not a secure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and control as to who on the secure network is allowed to access and
GET/SET (read/change/create/delete) the objects in this MIB. GET/SET (read/change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model [USM] and the View-based Access of the User-based Security Model [USM] and the View-based Access
Control Model [VACM] is recommended. Control Model [VACM] is recommended.
9. References 7. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture
for Describing SNMP Management Frameworks, RFC 2571, April for Describing SNMP Management Frameworks, RFC 2571, April
1999. 1999.
[RFC1155] Rose, M., and K. McCloghrie, Structure and Identification [RFC1155] Rose, M., and K. McCloghrie, Structure and Identification
of Management Information for TCP/IP-based Internets, STD of Management Information for TCP/IP-based Internets, STD
16, RFC 1155, May 1990. 16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD [RFC1212] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD
skipping to change at page 27, line 33 skipping to change at page 15, line 33
Extensions", RFC 2674, August 1999. Extensions", RFC 2674, August 1999.
[802.1D] "Information technology - Telecommunications and [802.1D] "Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Common specifications - Part metropolitan area networks - Common specifications - Part
3: Media Access Control (MAC) Bridges: Revision. This is 3: Media Access Control (MAC) Bridges: Revision. This is
a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k- a revision of ISO/IEC 10038: 1993, 802.1j-1992 and 802.6k-
1992. It incorporates P802.11c, P802.1p and P802.12e." 1992. It incorporates P802.11c, P802.1p and P802.12e."
ISO/IEC 15802-3: 1998. ISO/IEC 15802-3: 1998.
[802.1Q] ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and
Metropolitan Area Networks: Virtual Bridged Local Area
Networks", 1998.
[BRIDGEMIB] Decker, E., Langille, P., Rijsinghani, A. and K. [BRIDGEMIB] Decker, E., Langille, P., Rijsinghani, A. and K.
McCloghrie, "Definitions of Managed Objects for Bridges", McCloghrie, "Definitions of Managed Objects for Bridges",
RFC 1493, July 1993. RFC 1493, July 1993.
[802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE [802.1t] IEEE 802.1t-2001, "(Amendment to IEEE Standard 802.1D) IEEE
Standard for Information technology - Telecommunications Standard for Information technology - Telecommunications
and information exchange between systems - Local and and information exchange between systems - Local and
metropolitan area networks - Common specifications - Part metropolitan area networks - Common specifications - Part
3: Media Access Control (MAC) Bridges: Technical and 3: Media Access Control (MAC) Bridges: Technical and
Editorial Corrections". Editorial Corrections".
[802.1u] IEEE 802.1u-2001, "(Amendment to IEEE Standard 802.1Q) IEEE
Standard for Local and metropolitan area networks - Virtual
Bridged Local Area Networks - Amendment 1: Technical and
editorial corrections".
[802.1v] IEEE 802.1v-2001, "(Amendment to IEEE Standard 802.1Q) IEEE
Standards for Local and Metropolitan Area Networks: Virtual
Bridged Local Area Networks--Amendment 2: VLAN
Classification by Protocol and Port".
[802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE [802.1w] IEEE 802.1w-2001, "(Amendment to IEEE Standard 802.1D) IEEE
Standard for Information technology--Telecommunications and Standard for Information technology--Telecommunications and
information exchange between systems--Local and information exchange between systems--Local and
metropolitan area networks--Common Specifications--Part 3: metropolitan area networks--Common Specifications--Part 3:
Media Access Control (MAC) Bridges: Rapid Reconfiguation". Media Access Control (MAC) Bridges: Rapid Reconfiguation".
10. Authors' Addresses 9. Authors' Addresses
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
eCom Centre, Boundary Way eCom Centre, Boundary Way
Hemel Hempstead Hemel Hempstead
Herts. HP2 7YU Herts. HP2 7YU
UK UK
Phone: +44 1442 438025 Phone: +44 1442 438025
Email: Les_Bell@3Com.com Email: Les_Bell@3Com.com
Vivian Ngai Vivian Ngai
Enterasys Networks Enterasys Networks
2691 South Decker Lake Lane 2691 South Decker Lake Lane
Salt Lake City, UT 84119 Salt Lake City, UT 84119
USA
Phone: +1 801-887-9802 Phone: +1 801-887-9802
Fax: +1 801-972-5789 Fax: +1 801-972-5789
Email: vngai@enterasys.com Email: vngai@enterasys.com
11. Full Copyright 9. Full Copyright
Copyright (C) The Internet Society (date). All Rights Reserved. Copyright (C) The Internet Society (date). All Rights Reserved.
This document and translations of it may be copied and furnished This document and translations of it may be copied and furnished
to others, and derivative works that comment on or otherwise to others, and derivative works that comment on or otherwise
explain it or assist in its implementation may be prepared, copied, explain it or assist in its implementation may be prepared, copied,
published and distributed, in whole or in part, without published and distributed, in whole or in part, without
restriction of any kind, provided that the above copyright notice restriction of any kind, provided that the above copyright notice
and this paragraph are included on all such copies and derivative and this paragraph are included on all such copies and derivative
works. However, this document itself may not be modified in any works. However, this document itself may not be modified in any
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/