draft-ietf-bridge-rstpmib-00.txt   draft-ietf-bridge-rstpmib-01.txt 
Internet Draft E. Bell Internet Draft E. Bell
Expires January 2001 3Com Corp. Expires January 2001 3Com Corp.
draft-ietf-bridge-rstpmib-00.txt V. Ngai draft-ietf-bridge-rstpmib-01.txt V. Ngai
Enterasys Networks Enterasys Networks
July 2001 November 2001
Definitions of Managed Objects for Bridges with Rapid Spanning Tree Definitions of Managed Objects for Bridges with Rapid Spanning Tree
Protocol and VLAN Classification Extensions Protocol and VLAN Classification Extensions
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
skipping to change at page 2, line 19 skipping to change at page 2, line 19
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 ...................................... 5
3.2 Structure of U-BRIDGE-MIB .................................. 5 3.2 Structure of U-BRIDGE-MIB .................................. 5
3.3 Structure of V-BRIDGE-MIB .................................. 5 3.3 Structure of V-BRIDGE-MIB .................................. 6
3.3.1 The dot1vProtocol Group .................................. 6 3.3.1 The dot1vProtocol Group .................................. 6
3.4 Relationship to Other MIBs ................................. 6 3.4 Relationship to Other MIBs ................................. 6
3.4.1 Relationship to Original Bridge MIB ...................... 6 3.4.1 Relationship to Original Bridge MIB ...................... 6
3.4.1.1 The dot1dBase Group .................................... 6 3.4.1.1 The dot1dBase Group .................................... 6
3.4.1.2 The dot1dStp Group ..................................... 6 3.4.1.2 The dot1dStp Group ..................................... 7
3.4.1.3 The dot1dTp Group ...................................... 7 3.4.1.3 The dot1dTp Group ...................................... 7
3.4.1.4 The dot1dStatic Group .................................. 7 3.4.1.4 The dot1dStatic Group .................................. 8
3.4.2 Relation to the Q-BRDIGE-MIB module defined in RFC2674 ... 7 3.4.2 Relation to the P-BRIDGE-MIB module defined in RFC2674 ... 8
3.4.2.1 The dot1qBase Group .................................... 7 3.4.3 Relation to the Q-BRDIGE-MIB module defined in RFC2674 ... 8
3.4.2.2 The dot1qTp Group ...................................... 7
3.4.2.3 The dot1qStatic Group .................................. 8
3.4.2.4 The dot1qVlan Group .................................... 8
4 Definition for RSTP-MIB ...................................... 8 4 Definition for RSTP-MIB ...................................... 8
5 Definition for U-BRIDGE-MIB .................................. 13 5 Definition for U-BRIDGE-MIB .................................. 14
6 Definition for V-BRIDGE-MIB .................................. 15 6 Definition for V-BRIDGE-MIB .................................. 20
7 Acknowledgments .............................................. 20 7 Acknowledgments .............................................. 25
8 Security consideration ....................................... 20 8 Security consideration ....................................... 25
9 References ................................................... 21 9 References ................................................... 26
10 Authors' Addresses .......................................... 23 10 Authors' Addresses .......................................... 28
11 Full Copyright .............................................. 24 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 5, line 16 skipping to change at page 5, line 16
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
dot1dStp dot1dStp
dot1dStpVersion (w) 17.6.1 ForceVersion dot1dStpVersion (w) 17.6.1 ForceVersion
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 3.2. Structure of U-BRIDGE-MIB
Objects in this MIB are defined as an addition to the dot1qVlan group 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 in the Virtual Bridge MIB [Q-BRIDGE-MIB]. The overall structure is
shown below: shown below:
Virtual Bridge MIB Name IEEE P802.1u Reference 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 dot1qVlan
dot1qExtPortVlanTable dot1qExtPortVlanTable
dot1qPortRestrictedRegistration 11.2.3.2.3 Restricted dot1qPortRestrictedVlanRegistration
(u) 11.2.3.2.3 Restricted
VLAN Registration 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 3.3. Structure of V-BRIDGE-MIB
Objects in this MIB are arranged in a single group which is organized 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 as a set of related objects. The overall structure and assignment of
objects to the group is shown below: objects to the group is shown below:
Bridge MIB Name IEEE P802.1v Reference Bridge MIB Name IEEE P802.1v Reference
dot1vProtocol dot1vProtocol
skipping to change at page 6, line 19 skipping to change at page 6, line 36
respect VLAN classification by Protocol and Port. If VLAN respect VLAN classification by Protocol and Port. If VLAN
classification is not supported, this group will not be implemented. 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]. If the U-BRIDGE-MIB and V-BRIDGE-
MIB modules are implemented, a bridge will also implement the Q- MIB modules are implemented, a bridge will also implement the P-
BRIDGE-MIB module defined in RFC 2674 [QBRIDGEMIB]. 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 7, line 36 skipping to change at page 8, line 11
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 Q-BRIDGE-MIB module defined in RFC 2674 3.4.2. Relation to the P-BRIDGE-MIB module defined in RFC 2674
This section defines how objects in the Q-BRIDGE-MIB module
[QBRIDGEMIB] should be represented for devices which implement the
U-BRIDGE-MIB and V-BRIDGE-MIB module described in this memo.
3.4.2.1. The dot1qBase Group
This mandatory group contains the objects which are applicable to all
bridges implementing IEEE 802.1Q virtual LANs.
3.4.2.2. The dot1qTp Group
This group contains objects that control the operation and report the
status of transparent bridging.
3.4.2.3. The dot1qStatic Group
This group contains objects that control static configuration The P-BRIDGE-MIB module contains managed objects for the traffic
information for transparent bridging. 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.2.4. The dot1qVlan Group 3.4.3. Relation to the Q-BRIDGE-MIB module defined in RFC 2674
This group contains objects that control configuration and report The Q-BRIDGE-MIB module contains managed objects for the Virtual LAN
status of the Virtual LANs known to a bridge. 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
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dStp, dot1dStpPortEntry dot1dBridge, dot1dStp, dot1dStpPortEntry
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
rstpMIB MODULE-IDENTITY rstpMIB MODULE-IDENTITY
LAST-UPDATED "200107130000Z" LAST-UPDATED "200111160000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org" "Email: Bridge-mib@ietf.org"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing devices "The Bridge MIB Extension module for managing devices
that support the Rapid Spanning Tree Protocol defined that support the Rapid Spanning Tree Protocol defined
by IEEE 802.1w." by IEEE 802.1w."
REVISION "200107130000Z" REVISION "200111160000Z"
DESCRIPTION DESCRIPTION
"Draft 0" "Draft 1"
::= { dot1dBridge 11 } ::= { dot1dBridge 11 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Addition to the dot1dStp group -- Addition to the dot1dStp group
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1dStpVersion OBJECT-TYPE dot1dStpVersion OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stpCompatible(0), stpCompatible(0),
rstp(2) rstp(2)
skipping to change at page 9, line 22 skipping to change at page 9, line 31
indicates the Spanning Tree Protocol specified in indicates the Spanning Tree Protocol specified in
IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning IEEE 802.1D and 'rstp(2)' indicates the Rapid Spanning
Tree Protocol specified in IEEE 802.1w. New value may Tree Protocol specified in IEEE 802.1w. New value may
be defined as future versions of the protocol become be defined as future versions of the protocol become
available." available."
REFERENCE REFERENCE
"IEEE 802.1w clause 14.8.1, 17.12, 17.16.1" "IEEE 802.1w clause 14.8.1, 17.12, 17.16.1"
DEFVAL { rstp } DEFVAL { rstp }
::= { dot1dStp 16 } ::= { dot1dStp 16 }
dot1dStpTxHoldCount OBJECT-TYPE
SYNTAX INTEGER (1..10)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value used by the Port Transmit state machine to limit
the maximum transmission rate."
REFERENCE
"IEEE 802.1w clause 17.16.6"
DEFVAL { 3 }
::= { dot1dStp 17 }
dot1dStpPathCostDefault OBJECT-TYPE dot1dStpPathCostDefault OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
stp8021d1998(1), stp8021d1998(1),
stp8021t2001(2) stp8021t2001(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The version of the Spanning Tree default Path Costs that "The version of the Spanning Tree default Path Costs that
are to be used by this Bridge. A value of 8021d1998(1) are to be used by this Bridge. A value of 8021d1998(1)
uses the 16-bit default Path Costs from IEEE Std. 802.1D-1998. uses the 16-bit default Path Costs from IEEE Std. 802.1D-1998.
A value of stp8021t2001(2) uses the 32-bit default Path A value of stp8021t2001(2) uses the 32-bit default Path
Costs from IEEE Std. 802.1t." Costs from IEEE Std. 802.1t."
REFERENCE REFERENCE
"IEEE 802.1D & 802.1t Table 8-5" "IEEE 802.1D & 802.1t Table 8-5"
::= { dot1dStp 17 } ::= { dot1dStp 18 }
dot1dStpExtPortTable OBJECT-TYPE dot1dStpExtPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1dStpExtPortEntry SYNTAX SEQUENCE OF Dot1dStpExtPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table that contains port-specific Rapid Spanning Tree "A table that contains port-specific Rapid Spanning Tree
information." information."
::= { dot1dStp 18 } ::= { dot1dStp 19 }
dot1dStpExtPortEntry OBJECT-TYPE dot1dStpExtPortEntry OBJECT-TYPE
SYNTAX Dot1dStpExtPortEntry SYNTAX Dot1dStpExtPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of Rapid Spanning Tree information maintained by "A list of Rapid Spanning Tree information maintained by
each port." each port."
AUGMENTS { dot1dStpPortEntry } AUGMENTS { dot1dStpPortEntry }
::= { dot1dStpExtPortTable 1 } ::= { dot1dStpExtPortTable 1 }
skipping to change at page 12, line 21 skipping to change at page 12, line 41
rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 } rstpGroups OBJECT IDENTIFIER ::= { rstpConformance 1 }
rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 } rstpCompliances OBJECT IDENTIFIER ::= { rstpConformance 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Units of conformance -- Units of conformance
-- ------------------------------------------------------------- -- -------------------------------------------------------------
rstpBridgeGroup OBJECT-GROUP rstpBridgeGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dStpVersion dot1dStpVersion,
dot1dStpTxHoldCount
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Rapid Spanning Tree information for the bridge." "Rapid Spanning Tree information for the bridge."
::= { rstpGroups 1 } ::= { rstpGroups 1 }
rstpDefaultPathCostGroup OBJECT-GROUP rstpDefaultPathCostGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1dStpPathCostDefault dot1dStpPathCostDefault
} }
skipping to change at page 13, line 16 skipping to change at page 13, line 38
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for device support of bridging "The compliance statement for device support of bridging
services." services."
MODULE MODULE
MANDATORY-GROUPS { MANDATORY-GROUPS {
rstpBridgeGroup, rstpBridgeGroup,
rstpPortGroup rstpPortGroup
} }
GROUP rstpDefaultPathCostGroup
DESCRIPTION
"Support for this group is mandatory only if
both 16-bit and 32-bit Path Costs are supported."
::= { rstpCompliances 1 } ::= { rstpCompliances 1 }
END END
5. Definitions for U-BRIDGE-MIB 5. Definitions for U-BRIDGE-MIB
U-BRIDGE-MIB DEFINITIONS ::= BEGIN U-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- MIB for IEEE 802.1u Restricted Group Registration -- MIB for IEEE 802.1u Restricted Group Registration
-- ------------------------------------------------------------- -- -------------------------------------------------------------
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue TruthValue, MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dBasePortEntry dot1dBridge, dot1dBasePort, dot1dBasePortEntry
FROM BRIDGE-MIB FROM BRIDGE-MIB
dot1qPortVlanEntry dot1qPvid, dot1qVlan
FROM Q-BRIDGE-MIB; FROM Q-BRIDGE-MIB
dot1dGmrp
FROM P-BRIDGE-MIB;
uBridgeMIB MODULE-IDENTITY uBridgeMIB MODULE-IDENTITY
LAST-UPDATED "200107130000Z" LAST-UPDATED "200111160000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org" "Email: Bridge-mib@ietf.org"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing devices "The Bridge MIB Extension module for managing devices
that allow control over dynamic VLAN registration through that allow control over dynamic VLAN registration through
Restricted VLAN Registration as defined by IEEE 802.1u." Restricted VLAN Registration as defined by IEEE 802.1u."
REVISION "200107130000Z" REVISION "200111160000Z"
DESCRIPTION DESCRIPTION
"Draft 0" "Draft 1"
::= { dot1dBridge 12 } ::= { dot1dBridge 12 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Augmentation to the dot1dGmrpTable
-- -------------------------------------------------------------
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 }
-- -------------------------------------------------------------
-- Augmentation to the dot1qPortVlanTable -- Augmentation to the dot1qPortVlanTable
-- ------------------------------------------------------------- -- -------------------------------------------------------------
dot1qExtPortVlanTable OBJECT-TYPE dot1qExtPortVlanTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot1qExtPortVlanEntry SYNTAX SEQUENCE OF Dot1qExtPortVlanEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table containing per port Restricted VLAN Registration "A table containing per port Restricted VLAN Registration
control information." control information."
skipping to change at page 14, line 30 skipping to change at page 16, line 50
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information controlling VLAN Registration for a port "Information controlling VLAN Registration for a port
on the device. This is indexed by dot1dBasePort." on the device. This is indexed by dot1dBasePort."
AUGMENTS { dot1dBasePortEntry } AUGMENTS { dot1dBasePortEntry }
::= { dot1qExtPortVlanTable 1 } ::= { dot1qExtPortVlanTable 1 }
Dot1qExtPortVlanEntry ::= Dot1qExtPortVlanEntry ::=
SEQUENCE { SEQUENCE {
dot1qPortRestrictedRegistration dot1qPortRestrictedVlanRegistration
TruthValue TruthValue,
dot1qPortGvrpFailingReason
INTEGER
} }
dot1qPortRestrictedRegistration OBJECT-TYPE dot1qPortRestrictedVlanRegistration OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The state of Restricted Registration on this port. "The state of Restricted VLAN Registration on this port.
If the value of this control is true(1), then creation If the value of this control is true(1), then creation
of a new dynamic VLAN entry is permitted only if there of a new dynamic VLAN entry is permitted only if there
is a Static VLAN Registration Entry for the VLAN concerned, is a Static VLAN Registration Entry for the VLAN concerned,
in which the Registrar Administrative Control value for in which the Registrar Administrative Control value for
this port is Normal Registration." this port is Normal Registration."
REFERENCE REFERENCE
"IEEE 802.1u clause 11.2.3.2.3, 12.10.1.7." "IEEE 802.1u clause 11.2.3.2.3, 12.10.1.7."
DEFVAL { false } DEFVAL { false }
::= { dot1qExtPortVlanEntry 1 } ::= { 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 }
-- Traps for Registration Failures
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 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- uBridgeMIB - Conformance Information -- uBridgeMIB - Conformance Information
-- ------------------------------------------------------------- -- -------------------------------------------------------------
uBridgeConformance OBJECT IDENTIFIER ::= { uBridgeMIB 1 } uBridgeConformance OBJECT IDENTIFIER ::= { uBridgeMIB 1 }
uBridgeGroups OBJECT IDENTIFIER ::= { uBridgeConformance 1 } uBridgeGroups OBJECT IDENTIFIER ::= { uBridgeConformance 1 }
uBridgeCompliances OBJECT IDENTIFIER ::= { uBridgeConformance 2 } uBridgeCompliances OBJECT IDENTIFIER ::= { uBridgeConformance 2 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Units of conformance -- Units of conformance
-- ------------------------------------------------------------- -- -------------------------------------------------------------
uBridgePortGroup OBJECT-GROUP uBridgePortVlanGroup OBJECT-GROUP
OBJECTS { OBJECTS {
dot1qPortRestrictedRegistration dot1qPortRestrictedVlanRegistration,
dot1qPortGvrpFailingReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Per-port Restricted VLAN Registration Control parameter" "Per-port Restricted VLAN Registration Control parameter"
::= { uBridgeGroups 1 } ::= { 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 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- Compliance statements -- Compliance statements
-- ------------------------------------------------------------- -- -------------------------------------------------------------
uBridgeCompliance MODULE-COMPLIANCE uBridgeCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for device support of bridging "The compliance statement for device support of bridging
services." services."
MODULE MODULE
MANDATORY-GROUPS { GROUP uBridgePortVlanGroup
uBridgePortGroup 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 } ::= { uBridgeCompliances 1 }
END END
6. Definitions for V-BRIDGE-MIB 6. Definitions for V-BRIDGE-MIB
V-BRIDGE-MIB DEFINITIONS ::= BEGIN V-BRIDGE-MIB DEFINITIONS ::= BEGIN
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- MIB for IEEE 802.1v VLAN Classification by Protocol and Port -- MIB for IEEE 802.1v VLAN Classification by Protocol and Port
skipping to change at page 16, line 10 skipping to change at page 20, line 25
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE MODULE-IDENTITY, OBJECT-TYPE
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
dot1dBridge, dot1dBasePort dot1dBridge, dot1dBasePort
FROM BRIDGE-MIB; FROM BRIDGE-MIB;
vBridgeMIB MODULE-IDENTITY vBridgeMIB MODULE-IDENTITY
LAST-UPDATED "200107130000Z" LAST-UPDATED "200106300000Z"
ORGANIZATION "IETF Bridge MIB Working Group" ORGANIZATION "IETF Bridge MIB Working Group"
CONTACT-INFO CONTACT-INFO
"Email: Bridge-mib@ietf.org" "Email: Bridge-mib@ietf.org"
DESCRIPTION DESCRIPTION
"The Bridge MIB Extension module for managing devices "The Bridge MIB Extension module for managing devices
that support VLAN Classification by Protocol and Port that support VLAN Classification by Protocol and Port
defined in IEEE 802.1v." defined in IEEE 802.1v."
REVISION "200107130000Z" REVISION "200106300000Z"
DESCRIPTION DESCRIPTION
"Draft 0" "Draft 0"
::= { dot1dBridge 13 } ::= { dot1dBridge 13 }
vBridgeMIBObjects OBJECT IDENTIFIER ::= { vBridgeMIB 1 } vBridgeMIBObjects OBJECT IDENTIFIER ::= { vBridgeMIB 1 }
-- ------------------------------------------------------------- -- -------------------------------------------------------------
-- group in this MIB -- group in this MIB
-- ------------------------------------------------------------- -- -------------------------------------------------------------
skipping to change at page 22, line 24 skipping to change at page 27, line 20
RFC 2573, April 1999. RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP), RFC 2575, April 1999. Management Protocol (SNMP), RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
Introduction to Version 3 of the Internet-standard Network Introduction to Version 3 of the Internet-standard Network
Management Framework, RFC 2570, April 1999. Management Framework, RFC 2570, April 1999.
[RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and
McCloghrie, "Definitions of Managed Objects for Bridges
with Traffic Classes, Multicast Filtering and Virtual LAN
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 [802.1Q] ANSI/IEEE Standard 802.1Q, "IEEE Standards for Local and
Metropolitan Area Networks: Virtual Bridged Local Area Metropolitan Area Networks: Virtual Bridged Local Area
Networks", 1998. 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.
[QBRIDGEMIB] Bell, E., Smith, A., Langille, P., Rijhsinghani, A. and
McCloghrie, "Definitions of Managed Objects for Bridges
with Traffic Classes, Multicast Filtering and Virtual LAN
Extensions", RFC 2674, August 1999.
[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 [802.1u] IEEE 802.1u-2001, "(Amendment to IEEE Standard 802.1Q) IEEE
Standard for Local and metropolitan area networks - Virtual Standard for Local and metropolitan area networks - Virtual
Bridged Local Area Networks - Amendment 1: Technical and Bridged Local Area Networks - Amendment 1: Technical and
editorial corrections". editorial corrections".
[802.1v] IEEE 802.1v-2001, "(Amendment to IEEE Standard 802.1Q) IEEE [802.1v] IEEE 802.1v-2001, "(Amendment to IEEE Standard 802.1Q) IEEE
Standards for Local and Metropolitan Area Networks: Virtual Standards for Local and Metropolitan Area Networks: Virtual
Bridged Local Area Networks--Amendment 2: VLAN Bridged Local Area Networks--Amendment 2: VLAN
Classification by Protocol and Port". Classification by Protocol and Port".
[802.1w] IEEE 802.1w/D10, "(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 10. Authors' Addresses
Les Bell Les Bell
3Com Europe Limited 3Com Europe Limited
eCom Centre, Boundary Way eCom Centre, Boundary Way
 End of changes. 

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