RE: [802.1] MSTP MIB
[email protected] (Alex Ruzin) Fri, 22 Jul 2005 11:43:30 +0200
| Newsgroups | gmane.ietf.bridge |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPart_000_0039_01C58EB2.9541FDA0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Paul, Would you like to upload attached revision of the most recent draft of MST MIB to the 802.1 web-site, please? - I fixed the previous one (as far as I could) to satisfy 'smilint' checker. Thanks, Alex -----Original Message----- From: IEEE 802.1 [mailto:[email protected]]On Behalf Of Alex Ruzin Sent: Friday, July 22, 2005 8:47 AM To: [email protected] Subject: Re: [802.1] MSTP MIB David, Thank you, I'll try to use tools from you pointed. Nevertheless I believe on current stage we should concentrate our efforts on the structure of the MIB and on the set of objects to be managed. With respect, Alex -----Original Message----- From: IEEE 802.1 [mailto:[email protected]]On Behalf Of David B Harrington Sent: Thursday, July 21, 2005 6:13 PM To: [email protected] Subject: [802.1] MSTP MIB Hi Alex and all, The mib module in this document is not in good SMIv2 format, but rather seems to be a combination of SMIv1 syntax and SMIv2 syntax. There are better tools available for reviewing SMIv2 syntax. Please see http://www.ops.ietf.org/mib-review-tools.html for some suggestions. Smilint reported the following problems in the syntax of this MIB module. It would be helpful to get these fixed in the initial revision so the tools used by other 802.1 reviewers will not have problems with the MIB. --- This is an automatically generated mail message in response to a mail message you (or someone else who used your address) sent to <[email protected]>. If you want to learn more about this mail service, send a mail message with the "Subject: help" to <[email protected]>. The program smilint 0.4.3, as of Thu Jun 23 10:41:27 2005 has been used to process your request as follows: smilint -m -s -e -l 6 MSTP-MIB MSTP-MIB:24: [3] {revision-missing} revision for last update is missing MSTP-MIB:24: [2] {bad-identifier-case} `XXX' should start with a lower case letter MSTP-MIB:24: [2] {object-identifier-not-prefix} Object identifier element `XXX' name only allowed as first element MSTP-MIB:46: [5] {integer-misuse} warning: use Integer32 instead of INTEGER in SMIv2 MSTP-MIB:60: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:70: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:91: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:93: [2] {invalid-format} invalid format specification `d' MSTP-MIB:109: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:110: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:117: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:118: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:125: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:126: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:133: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:134: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:141: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:142: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:149: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:150: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:156: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:157: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:158: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:165: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:166: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:173: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:174: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:207: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:230: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:231: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:242: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:242: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:243: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:252: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:253: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:264: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:264: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:265: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:277: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:278: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:283: [1] {oid-registered} identifier `mstpGenCfgIdDigest' registers object identifier already registered by `mstpGenCfgIdRevLevel' MSTP-MIB:262: [6] {previous-definition} info: previous definition of `mstpGenCfgIdRevLevel' MSTP-MIB:289: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:290: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:297: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:297: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:298: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:306: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:307: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:315: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:316: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:328: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:329: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:390: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:392: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:403: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:404: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:422: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:444: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:453: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:507: [2] {sequence-type-mismatch} type of `mstpPortRxCfgBpduCounter' in sequence and object type definition do not match MSTP-MIB:515: [2] {sequence-type-mismatch} type of `mstpPortRxRstBpduCounter' in sequence and object type definition do not match MSTP-MIB:523: [2] {sequence-type-mismatch} type of `mstpPortRxMstBpduCounter' in sequence and object type definition do not match MSTP-MIB:531: [2] {sequence-type-mismatch} type of `mstpPortTxTcnBpduCounter' in sequence and object type definition do not match MSTP-MIB:539: [2] {sequence-type-mismatch} type of `mstpPortTxCfgBpduCounter' in sequence and object type definition do not match MSTP-MIB:547: [2] {sequence-type-mismatch} type of `mstpPortTxRstBpduCounter' in sequence and object type definition do not match MSTP-MIB:555: [2] {sequence-type-mismatch} type of `mstpPortTxMstBpduCounter' in sequence and object type definition do not match MSTP-MIB:569: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:578: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:587: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:593: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:595: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:603: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:611: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:635: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:643: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:647: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:658: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:665: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:667: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:676: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:684: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:692: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:699: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:700: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:708: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:716: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:748: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:749: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:756: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead MSTP-MIB:757: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:773: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:775: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:778: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:779: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:781: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:786: [2] {status-invalid-smiv2} invalid status `mandatory' in SMIv2 MIB MSTP-MIB:807: [5] {named-numbers-ascending} warning: named numbers not in ascending order MSTP-MIB:842: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:858: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:881: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:890: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:900: [2] {basetype-not-imported} SMIv2 base type `Integer32' must be imported from SNMPv2-SMI MSTP-MIB:910: [2] {macro-not-imported} macro `NOTIFICATION-TYPE' has not been imported from module `SNMPv2-SMI' MSTP-MIB:924: [2] {macro-not-imported} macro `NOTIFICATION-TYPE' has not been imported from module `SNMPv2-SMI' MSTP-MIB:940: [2] {macro-not-imported} macro `NOTIFICATION-TYPE' has not been imported from module `SNMPv2-SMI' MSTP-MIB:313: [5] {index-element-accessible} warning: index element `mstpPortIndex' of row `mstpPortEntry' should be not-accessible in SMIv2 MIB MSTP-MIB:754: [5] {index-element-accessible} warning: index element `mstpXstPortIndex' of row `mstpXstPortEntry' should be not-accessible in SMIv2 MIB MSTP-MIB:910: [3] {notification-object-access} object `mstpXstId' of notification `mstpNewRootBridge' must not be `not-accessible' MSTP-MIB:924: [3] {notification-object-access} object `mstpXstId' of notification `mstpNewRootPort' must not be `not-accessible' MSTP-MIB:940: [3] {notification-object-access} object `mstpXstId' of notification `mstpTopologyChange' must not be `not-accessible' MSTP-MIB:107: [4] {group-membership} warning: node `mstpGenBridgeMaxAge' must be contained in at least one conformance group MSTP-MIB:115: [4] {group-membership} warning: node `mstpGenBridgeHelloTime' must be contained in at least one conformance group MSTP-MIB:123: [4] {group-membership} warning: node `mstpGenBridgeForwardDelay' must be contained in at least one conformance group MSTP-MIB:131: [4] {group-membership} warning: node `mstpGenMaxAge' must be contained in at least one conformance group MSTP-MIB:139: [4] {group-membership} warning: node `mstpGenHelloTime' must be contained in at least one conformance group MSTP-MIB:147: [4] {group-membership} warning: node `mstpGenForwardDelay' must be contained in at least one conformance group MSTP-MIB:155: [4] {group-membership} warning: node `mstpGenMaxHops' must be contained in at least one conformance group MSTP-MIB:163: [4] {group-membership} warning: node `mstpGenHoldTime' must be contained in at least one conformance group MSTP-MIB:171: [4] {group-membership} warning: node `mstpGenMigrateTime' must be contained in at least one conformance group MSTP-MIB:179: [4] {group-membership} warning: node `mstpGenPathCostDefault' must be contained in at least one conformance group MSTP-MIB:197: [4] {group-membership} warning: node `mstpGenCapable' must be contained in at least one conformance group MSTP-MIB:222: [4] {group-membership} warning: node `mstpGenForceVersion' must be contained in at least one conformance group MSTP-MIB:240: [4] {group-membership} warning: node `mstpGenCfgIdFmtSel' must be contained in at least one conformance group MSTP-MIB:250: [4] {group-membership} warning: node `mstpGenCfgIdName' must be contained in at least one conformance group MSTP-MIB:262: [4] {group-membership} warning: node `mstpGenCfgIdRevLevel' must be contained in at least one conformance group MSTP-MIB:275: [4] {group-membership} warning: node `mstpGenCfgIdDigest' must be contained in at least one conformance group MSTP-MIB:287: [4] {group-membership} warning: node `mstpGenReginalRoot' must be contained in at least one conformance group MSTP-MIB:295: [4] {group-membership} warning: node `mstpGenExternalRootCost' must be contained in at least one conformance group MSTP-MIB:349: [4] {group-membership} warning: node `mstpPortIndex' must be contained in at least one conformance group MSTP-MIB:361: [4] {group-membership} warning: node `mstpPortAdminMACEnable' must be contained in at least one conformance group MSTP-MIB:370: [4] {group-membership} warning: node `mstpPortOperMACEnable' must be contained in at least one conformance group MSTP-MIB:379: [4] {group-membership} warning: node `mstpPortUpTime' must be contained in at least one conformance group MSTP-MIB:389: [4] {group-membership} warning: node `mstpPortAdminExternalPathCost' must be contained in at least one conformance group MSTP-MIB:401: [4] {group-membership} warning: node `mstpPortOperExternalPathCost' must be contained in at least one conformance group MSTP-MIB:410: [4] {group-membership} warning: node `mstpPortAdminEdge' must be contained in at least one conformance group MSTP-MIB:419: [4] {group-membership} warning: node `mstpPortOperEdge' must be contained in at least one conformance group MSTP-MIB:428: [4] {group-membership} warning: node `mstpPortAutoEdge' must be contained in at least one conformance group MSTP-MIB:437: [4] {group-membership} warning: node `mstpPortAdminPointToPoint' must be contained in at least one conformance group MSTP-MIB:450: [4] {group-membership} warning: node `mstpPortOperPointToPoint' must be contained in at least one conformance group MSTP-MIB:459: [4] {group-membership} warning: node `mstpPortHelloTime' must be contained in at least one conformance group MSTP-MIB:468: [4] {group-membership} warning: node `mstpPortAdminNonStp' must be contained in at least one conformance group MSTP-MIB:481: [4] {group-membership} warning: node `mstpPortProtocolMigration' must be contained in at least one conformance group MSTP-MIB:493: [4] {group-membership} warning: node `mstpPortRxTcnBpduCounter' must be contained in at least one conformance group MSTP-MIB:501: [4] {group-membership} warning: node `mstpPortRxCfgBpduCounter' must be contained in at least one conformance group MSTP-MIB:509: [4] {group-membership} warning: node `mstpPortRxRstBpduCounter' must be contained in at least one conformance group MSTP-MIB:517: [4] {group-membership} warning: node `mstpPortRxMstBpduCounter' must be contained in at least one conformance group MSTP-MIB:525: [4] {group-membership} warning: node `mstpPortTxTcnBpduCounter' must be contained in at least one conformance group MSTP-MIB:533: [4] {group-membership} warning: node `mstpPortTxCfgBpduCounter' must be contained in at least one conformance group MSTP-MIB:541: [4] {group-membership} warning: node `mstpPortTxRstBpduCounter' must be contained in at least one conformance group MSTP-MIB:549: [4] {group-membership} warning: node `mstpPortTxMstBpduCounter' must be contained in at least one conformance group MSTP-MIB:600: [4] {group-membership} warning: node `mstpMapVlanMin' must be contained in at least one conformance group MSTP-MIB:608: [4] {group-membership} warning: node `mstpMapVlanMax' must be contained in at least one conformance group MSTP-MIB:616: [4] {group-membership} warning: node `mstpMapRowStatus' must be contained in at least one conformance group MSTP-MIB:664: [4] {group-membership} warning: node `mstpXstBridgePriority' must be contained in at least one conformance group MSTP-MIB:673: [4] {group-membership} warning: node `mstpXstBridgeId' must be contained in at least one conformance group MSTP-MIB:681: [4] {group-membership} warning: node `mstpXstDesignatedRoot' must be contained in at least one conformance group MSTP-MIB:689: [4] {group-membership} warning: node `mstpXstDesignatedBridge' must be contained in at least one conformance group MSTP-MIB:697: [4] {group-membership} warning: node `mstpXstInternalRootCost' must be contained in at least one conformance group MSTP-MIB:705: [4] {group-membership} warning: node `mstpXstRootPort' must be contained in at least one conformance group MSTP-MIB:713: [4] {group-membership} warning: node `mstpXstMasterPort' must be contained in at least one conformance group MSTP-MIB:721: [4] {group-membership} warning: node `mstpXstTimeSinceTopologyChange' must be contained in at least one conformance group MSTP-MIB:729: [4] {group-membership} warning: node `mstpXstTopologyChangesCount' must be contained in at least one conformance group MSTP-MIB:737: [4] {group-membership} warning: node `mstpXstTopologyChangeFlag' must be contained in at least one conformance group MSTP-MIB:791: [4] {group-membership} warning: node `mstpXstPortIndex' must be contained in at least one conformance group MSTP-MIB:800: [4] {group-membership} warning: node `mstpXstPortState' must be contained in at least one conformance group MSTP-MIB:815: [4] {group-membership} warning: node `mstpXstPortRole' must be contained in at least one conformance group MSTP-MIB:832: [4] {group-membership} warning: node `mstpXstPortDesignatedRoot' must be contained in at least one conformance group MSTP-MIB:840: [4] {group-membership} warning: node `mstpXstPortExternalRootCost' must be contained in at least one conformance group MSTP-MIB:848: [4] {group-membership} warning: node `mstpXstPortRegionalBridge' must be contained in at least one conformance group MSTP-MIB:856: [4] {group-membership} warning: node `mstpXstPortInternalRootCost' must be contained in at least one conformance group MSTP-MIB:864: [4] {group-membership} warning: node `mstpXstPortDesignatedBridge' must be contained in at least one conformance group MSTP-MIB:872: [4] {group-membership} warning: node `mstpXstPortDesignatedPort' must be contained in at least one conformance group MSTP-MIB:880: [4] {group-membership} warning: node `mstpXstPortPriority' must be contained in at least one conformance group MSTP-MIB:889: [4] {group-membership} warning: node `mstpXstPortAdminInternalPathCost' must be contained in at least one conformance group MSTP-MIB:898: [4] {group-membership} warning: node `mstpXstPortOperInternalPathCost' must be contained in at least one conformance group MSTP-MIB:910: [4] {group-membership} warning: notification `mstpNewRootBridge' must be contained in at least one conformance group MSTP-MIB:924: [4] {group-membership} warning: notification `mstpNewRootPort' must be contained in at least one conformance group MSTP-MIB:940: [4] {group-membership} warning: notification `mstpTopologyChange' must be contained in at least one conformance group MSTP-MIB:807: [2] {enum-number-redefinition} redefinition of number `1' in number enumeration MSTP-MIB:7: [5] {import-unused} warning: identifier `mib-2' imported from module `RFC1213-MIB' is never used MSTP-MIB:7: [5] {obsolete-import} warning: identifier `mib-2' should be imported from `SNMPv2-SMI' instead of `RFC1213-MIB' --- David Harrington [email protected] IEEE 802.1 list: When forwarding, PLEASE DELETE this footer & list-related header items. http://www.ieee802.org/1/email-pages/pwdqq705.html **************************************************************************** ****************************************** The information contained in this e-mail message and its attachments is privileged and confidential, and is protected from unauthorized use or dissemination or by intellectual property rights. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify MRV immediately by telephone, or by e-mail and delete the message from your computer. Thank you! **************************************************************************** ******************************** IEEE 802.1 list: When forwarding, PLEASE DELETE this footer & list-related header items. http://www.ieee802.org/1/email-pages/pwdqq705.html **************************************************************************** ****************************************** The information contained in this e-mail message and its attachments is privileged and confidential, and is protected from unauthorized use or dissemination or by intellectual property rights. The information is intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify MRV immediately by telephone, or by e-mail and delete the message from your computer. Thank you! **************************************************************************** ******************************** ------=_NextPart_000_0039_01C58EB2.9541FDA0 Content-Type: text/plain; name="ruzin-mstp-mib-03.txt" Content-Disposition: attachment; filename="ruzin-mstp-mib-03.txt" Content-Transfer-Encoding: quoted-printable ruzin-mstp-mib-03.txt Network Working Group Alex = Rozin, IEEE 802.1 Interworking Task Group MRV = International Request for Comments: ???? David = Fattura, Category: Internet Draft (rev. 02) Enterasys = Networks Sumeshwar = Malhotra, Bhaskar = S, Anand = Goenka, Motorola, = Inc Definitions of Managed Objects for Bridges with Multiple Spanning Tree Protocol Status of this Memo This document is an Internet-Draft and is subject to all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/1id-abstracts.html The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines a MIB module for managing the Multiple Spanning Tree capability defined by the IEEE Std 802.1s amendment to IEEE Std 802.1D-1998 for bridging between Local Area Network (LAN) = segments. <<T.B.D: to replace all references from IEEE Std 802.1s to IEEE Std 802.1Q>> This memo gives a MIB module for managing the MSTP protocol in a = manner that is compliant to SMIv2 [RFC2578]. Table of Contents 1 The SNMP Management Framework ................................ =20 2 Overview ..................................................... =20 2.1 Scope ...................................................... =20 3 Structure of MSTP-MIB......................................... =20 4 Relation to Original Bridge MIB............................... =20 5 Definition for MSTP-MIB ...................................... =20 6 Acknowledgments .............................................. =20 7 Security consideration ....................................... =20 8 References ................................................... =20 9 Authors' Addresses ........................................... =20 10 Full Copyright .............................................. =20 1. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 2. Overview A common device present in many networks is the Bridge. This device is used to connect Local Area Network segments below the network layer. These devices are often known as 'layer 2 switches'. There are two major modes defined for this bridging: Source-Route and transparent. Management of Source-Route bridging is not discussed=20 in this document. MSTP is defined by IEEE Std 802.1s. MST is defined as one or more logical topologies on a common physical interface. Typically one or more VLANs are mapped to a logical topology. 2.1. Scope This MIB includes a comprehensive set of managed objects which attempts to match the set defined in IEEE Std 802.1s. 3. Structure of MSTP-MIB This MIB contains 6 parts: mstpTraps, mstpGen, mstpPortTable, mstpMapTable, mstpXstTable and mstpXstPortTable: 1. mstpTraps help to get information about changes in MSTP active topology asynchronous notifications. Conditions and parameters seem = to be clear, while may be discussed. 2. mstpGen. This group is dedicated to manage Bridge Protocol Entity, described in 12.8.1.1 and 12.8.1.3. In a certain sense this group = reflects CIST, but without objects, that may be managed in mstpXstTable, see = below. 3. mstpPortTable allows to manage physical ports, as it is described = in 1.8.2.1., 1.80.2.3., 1.8.2.5 and 12.8.2.7. In a certain sense this = group reflects CIST ports, but without objects, that may be managed in = mstpXstPortTable, see below. 4. mstpMapTable serves for MSTI List management. It allows to = build/delete instances and to map FIDs/VIDs (12.12). Actually, this table = reflects MST Configuration Table in format, that is defined in 13.7 item 4). It must be admitted that I "grabbed" the idea of ranges in this = table from malhotra-mstpmib-01.txt 5. mstpXstTable reflects instances - both CIST and MSTIs (12.8.1.2 and = 12.8.1.4). It contains objects, common for these both types of instances, for = example, mstpXstBridgePriority. 6. mstpXstPortTable is dedicated to manage ports inside instances - = both CIST and MSTIs (12.8.2.2., 12.8.2.4 and 12.8.2.6). It contains objects, = describing port and common for these both types of instances, for example, mstpXstPortState or mstpXstPortPriority. Note, that this table has mstpXstPortInternalRootCost, while mstpPortAdminExternalPathCost = belongs to mstpPortTable. Important, that the index mstpXstId in mstpXstTable and = mstpXstPortXstId in mstpXstPortTable have type MstiOrCistInstanceIndex : "value of zero" corresponds to CIST. Now, I'd like to mention in passing objects, that are not defined in = .1s Let us begin from less questionable. 1. mstpPortAutoEdge. It came from new .1d 917.13.3) and I don't expect many objections here :) 2. mstpXstPortRole. The exploitation of MSTP shows, that managers of complicated networks want to know reasons of ports states assignations. So, they concerned with ports roles. In my opinion, = this object is important not only debug purposes. 3. The similar destination have so called BpduCounters. Let's say, = when a port stops to be RootPort, a manager may see, that receive = BpduCounters on this port do not rise. He may trace bridges and select a point = of failure. And what is more, I'd define an object = mstpXstPortRxMstBpduCounter to count MSTI Configuration Messages. Sure, all these counters are = optional: if an agent cannot provide for them it must return zero. 4. mstpGenCapable. A manager has to know, what version of STP the = bridge supplies. If it supplies a number of versions (see = mstpGenForceVersion), the eldest one must be returned. 5. mstpGenForceVersion. If the bridge can supply a number of versions = of STP (let's say, it has a number of corresponding engines) a manager may = want to enable one of them (and of course to disable all others) he may = use with this object. This object also show which engine is currently = enabled. 6. The value forceNonStp(0) of object mstpGenForceVersion. I remember = a few of dispute both in IETF and in IEEE : what is STP disabled into = a bridge. I know and share a position of IEEE, that there may not be bridge = with STP disabled, nevertheless... The term "Spanning Tree Protocol Emulation" here means, that a = bridge is transparent for received BPDUs (does flooding: transmits from all = ports, without tags and without VLAN participation) and processes Topology Change = bit: does appropriate FDB flushing. 7. mstpPortAdminNonStp. Certain port may be configured as a port, that = does not participate in any STP operations: a) it discards all BDPUs, b) = does not send BPDUs and c) is always in forwarding state. This option may help to = termination point of STP domain. 8. mstpXstMasterPort. Servers the same purposes as mstpXstPortRole and BpduCounters. On the other hand, is not less helpful than = mstpXstRootPort; furthermore it may help to indicate fallacious instance mapping = (when a manager expects bridges in the same region, this object must be = zero). 9. Both mstpXstRootPort and mstpXstMasterPort have type = PortIndexOrZero. Brief structure of the MIB (result of "snmptranslate -Tp"): +--mstp(XXX) | +--mstpTraps(0) | | | +--mstpNewRootBridge(1) | +--mstpNewRootPort(2) | +--mstpTopologyChange(3) | +--mstpGen(10) | | | +-- -RW- INTEGER mstpGenBridgeMaxAge(2) | | Textual Convention: Timeout | | Range: 600..4000 | +-- -RW- INTEGER mstpGenBridgeHelloTime(3) | | Textual Convention: Timeout | +-- -RW- INTEGER mstpGenBridgeForwardDelay(4) | | Textual Convention: Timeout | +-- -R-- INTEGER mstpGenMaxAge(8) | | Textual Convention: Timeout | +-- -R-- INTEGER mstpGenHelloTime(9) | | Textual Convention: Timeout | +-- -R-- INTEGER mstpGenForwardDelay(10) | | Textual Convention: Timeout | +-- -RW- Integer32 mstpGenMaxHops(14) | | Range: 4..30 | +-- -RW- INTEGER mstpGenHoldTime(15) | | Textual Convention: Timeout | | Range: 100..1000 | +-- -RW- INTEGER mstpGenMigrateTime(16) | | Textual Convention: Timeout | | Range: 100..1000 | +-- -RW- EnumVal mstpGenPathCostDefault(18) | | Values: pathCostDefault8021d1998(1), = pathCostDefault8021t2001(2) | +-- -R-- EnumVal mstpGenCapable(19) | | Values: nonStp(0), dot1d1998(1), dot1w(2), dot1d2004(3), = dot1s(4), dot1q(5), unknown(6) | +-- -RW- EnumVal mstpGenForceVersion(20) | | Values: forceNonStp(0), forceLegacyDot1d(1), = forceDot1w(2), autoDot1s(3), unknown(4) | +-- -RW- Integer32 mstpGenCfgIdFmtSel(30) | +-- -RW- String mstpGenCfgIdName(31) | | Textual Convention: DisplayString | | Size: 32 | +-- -RW- Integer32 mstpGenCfgIdRevLevel(32) | +-- -R-- String mstpGenCfgIdDigest(33) | | Size: 16 | +-- -R-- String mstpGenReginalRoot(36) | | Textual Convention: BridgeId | | Size: 8 | +-- -R-- Integer32 mstpGenExternalRootCost(37) | +--mstpPortTable(11) | | | +--mstpPortEntry(1) | | Index: mstpPortIndex | | | +-- ---- Integer32 mstpPortIndex(1) | | Textual Convention: PortIndex | | Range: 1..4094 | +-- -RW- EnumVal mstpPortAdminMACEnable(2) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -R-- EnumVal mstpPortOperMACEnable(3) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -R-- TimeTicks mstpPortUpTime(4) | +-- -RW- Integer32 mstpPortAdminExternalPathCost(5) | | Range: 0..200000000 | +-- -R-- Integer32 mstpPortOperExternalPathCost(6) | +-- -RW- EnumVal mstpPortAdminEdge(7) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -R-- EnumVal mstpPortOperEdge(8) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -RW- EnumVal mstpPortAutoEdge(9) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -RW- EnumVal mstpPortAdminPointToPoint(10) | | Values: forceTrue(0), forceFalse(1), auto(2) | +-- -R-- EnumVal mstpPortOperPointToPoint(11) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -RW- INTEGER mstpPortHelloTime(12) | | Textual Convention: Timeout | +-- -RW- EnumVal mstpPortAdminNonStp(13) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -RW- EnumVal mstpPortProtocolMigration(14) | | Textual Convention: TruthValue | | Values: true(1), false(2) | +-- -R-- Counter mstpPortRxTcnBpduCounter(15) | | Textual Convention: BpduCounter | +-- -R-- Counter mstpPortRxCfgBpduCounter(16) | | Textual Convention: BpduCounter | +-- -R-- Counter mstpPortRxRstBpduCounter(17) | | Textual Convention: BpduCounter | +-- -R-- Counter mstpPortRxMstBpduCounter(18) | | Textual Convention: BpduCounter | +-- -R-- Counter mstpPortTxTcnBpduCounter(19) | | Textual Convention: BpduCounter | +-- -R-- Counter mstpPortTxCfgBpduCounter(20) | | Textual Convention: BpduCounter | +-- -R-- Counter mstpPortTxRstBpduCounter(21) | | Textual Convention: BpduCounter | +-- -R-- Counter mstpPortTxMstBpduCounter(22) | Textual Convention: BpduCounter | +--mstpMapTable(12) | | | +--mstpMapEntry(1) | | Index: mstpMapMSTiID, mstpMapVlanRangeIndex | | | +-- ---- Integer32 mstpMapMSTiID(1) | | Textual Convention: MstiInstanceIndex | | Range: 1..64 | +-- ---- Integer32 mstpMapVlanRangeIndex(2) | | Range: 1..4094 | +-- CR-- Integer32 mstpMapVlanMin(3) | | Textual Convention: VlanId | | Range: 1..2147483647 | +-- CR-- Integer32 mstpMapVlanMax(4) | | Textual Convention: VlanId | | Range: 1..2147483647 | +-- CR-- EnumVal mstpMapRowStatus(9) | Textual Convention: RowStatus | Values: active(1), notInService(2), notReady(3), = createAndGo(4), createAndWait(5), destroy(6) | +--mstpXstTable(13) | | | +--mstpXstEntry(1) | | Index: mstpXstId | | | +-- -R-- Integer32 mstpXstId(1) | | Textual Convention: MstiOrCistInstanceIndex | | Range: 0..64 | +-- -RW- Integer32 mstpXstBridgePriority(2) | | Range: 0..61440 | +-- -R-- String mstpXstBridgeId(3) | | Textual Convention: BridgeId | | Size: 8 | +-- -R-- String mstpXstDesignatedRoot(4) | | Textual Convention: BridgeId | | Size: 8 | +-- -R-- String mstpXstDesignatedBridge(5) | | Textual Convention: BridgeId | | Size: 8 | +-- -R-- Integer32 mstpXstInternalRootCost(6) | +-- -R-- Integer32 mstpXstRootPort(7) | | Textual Convention: PortIndexOrZero | | Range: 0..2147483647 | +-- -R-- Integer32 mstpXstMasterPort(8) | | Textual Convention: PortIndexOrZero | | Range: 0..2147483647 | +-- -R-- TimeTicks mstpXstTimeSinceTopologyChange(11) | +-- -R-- Counter mstpXstTopologyChangesCount(12) | +-- -R-- EnumVal mstpXstTopologyChangeFlag(13) | Textual Convention: TruthValue | Values: true(1), false(2) | +--mstpXstPortTable(14) | +--mstpXstPortEntry(1) | Index: mstpXstPortXstId, mstpXstPortIndex | +-- ---- Integer32 mstpXstPortXstId(1) | Textual Convention: MstiOrCistInstanceIndex | Range: 0..64 +-- -R-- Integer32 mstpXstPortIndex(2) | Textual Convention: PortIndex | Range: 1..4094 +-- -R-- EnumVal mstpXstPortState(3) | Values: disabled(0), discarding(1), learning(2), = forwarding(3), unknown(4) +-- -R-- EnumVal mstpXstPortRole(4) | Values: disabled(1), alternate(2), backup(3), root(4), = designated(5), master(6), nonStp(7), unknown(8) +-- -R-- String mstpXstPortDesignatedRoot(6) | Textual Convention: BridgeId | Size: 8 +-- -R-- Integer32 mstpXstPortExternalRootCost(7) +-- -R-- String mstpXstPortRegionalBridge(8) | Textual Convention: BridgeId | Size: 8 +-- -R-- Integer32 mstpXstPortInternalRootCost(9) +-- -R-- String mstpXstPortDesignatedBridge(10) | Textual Convention: BridgeId | Size: 8 +-- -R-- String mstpXstPortDesignatedPort(14) | Textual Convention: PortId | Size: 2 +-- -RW- Integer32 mstpXstPortPriority(15) | Range: 0..255 +-- -RW- Integer32 mstpXstPortAdminInternalPathCost(16) | Range: 0..200000000 +-- -R-- Integer32 mstpXstPortOperInternalPathCost(17) MSTP-MIB DEFINITIONS ::=3D BEGIN -- draft ! IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, mib-2, Counter32, = TimeTicks, Integer32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, DisplayString, TruthValue FROM SNMPv2-TC VlanId FROM Q-BRIDGE-MIB=20 Timeout, BridgeId, dot1dBridge FROM BRIDGE-MIB; mstp MODULE-IDENTITY LAST-UPDATED "200507070000Z" ORGANIZATION "MRV Communications, Inc." CONTACT-INFO "Alex Rozin MRV Communication, Inc http://www.mrv.com Email: [email protected]" DESCRIPTION "The MIB module for managing devices that support Multiple & Rapid Spanning Trees Protocol and algorith. It is dedicated to reflect IEEE Std 802.1s" REVISION "200507070000Z" -- 07 Jul 2005 DESCRIPTION "'smilib' tested." ::=3D { dot1dBridge XXX } -- to be selected or moved into other = place of the tree =20 -- -- Textual Conventions -- -- VlanId ::=3D TEXTUAL-CONVENTION -- DISPLAY-HINT "d" -- STATUS current -- DESCRIPTION -- "." -- SYNTAX Integer32 (1..2147483647) =20 PortIndex ::=3D TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "A unique value, greater than zero, for each Port in the managed Bridge. The value for each PortIndex remain constant at least from one re-initialization of the entity's network management system to the next re-initialization." SYNTAX Integer32 (1..4094) PortIndexOrZero ::=3D TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "This textual convention is an extension of the PortIndex convention. The latter defines a greater than zero value used to identify a Port in the managed = Bridge. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined = as part of the description of any object which uses this = syntax. Examples of the usage of zero might include situations where Port was unknown, or when none or all Ports need to be = referenced." SYNTAX Integer32 (0..2147483647) MstiInstanceIndex ::=3D TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "A unique value, greater than zero, for each Multiple = Spanning Tree Instance (MSTI) in the managed Bridge. The value for each MstiInstanceIndex remains constant for = the instance. The " SYNTAX Integer32 (1..64) BpduCounter ::=3D TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "An optional counter of received or transmitted Bridge = Protocol Data Units of different types on/from a Port. If the agent = does not support these counter, it returns the value 0. These = counters are reset when the protocol starts to operate and when the value = of mstpPortOperMACEnable changes from false(2) to true(1)." SYNTAX Counter32 MstiOrCistInstanceIndex ::=3D TEXTUAL-CONVENTION DISPLAY-HINT "d" STATUS current DESCRIPTION "This textual convention is an extension of the MstiInstanceIndex convention. This extension permits the additional value of zero, which means Common and Internal Spanning Tree (CIST)." SYNTAX Integer32 (0..64) PortId ::=3D TEXTUAL-CONVENTION DISPLAY-HINT "2x:2d" STATUS current DESCRIPTION "The Port Identifier of the Port, the unique Port identifier comprising two parts, the Port Number and the Port Priority field (13.24.8 of IEEE Std 802.1s, 8.5.5.1 and 17.18.16 of IEEE Std 802.1D, 1998 Edition)." SYNTAX OCTET STRING (SIZE (2)) mstpGen OBJECT IDENTIFIER ::=3D { mstp 10 } -- mstpGen group reflects configurations/statuses -- the Bridge as a unit mstpGenBridgeMaxAge OBJECT-TYPE SYNTAX Timeout (600..4000) MAX-ACCESS read-write STATUS current DESCRIPTION "12.8.1.3.a)" ::=3D { mstpGen 2 } mstpGenBridgeHelloTime OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-write STATUS current DESCRIPTION "12.8.1.3.b)" ::=3D { mstpGen 3 } mstpGenBridgeForwardDelay OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-write STATUS current DESCRIPTION "12.8.1.3.c)" ::=3D { mstpGen 4 } mstpGenMaxAge OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-only STATUS current DESCRIPTION "12.8.1.3.a)" ::=3D { mstpGen 8 } mstpGenHelloTime OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-only STATUS current DESCRIPTION "12.8.1.3.b)" ::=3D { mstpGen 9 } mstpGenForwardDelay OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-only STATUS current DESCRIPTION "12.8.1.3.c)" ::=3D { mstpGen 10 } mstpGenMaxHops OBJECT-TYPE SYNTAX Integer32 (4..30) MAX-ACCESS read-write STATUS current DESCRIPTION "13.22.f)" ::=3D { mstpGen 14 } mstpGenHoldTime OBJECT-TYPE SYNTAX Timeout (100..1000) MAX-ACCESS read-write STATUS current DESCRIPTION "." ::=3D { mstpGen 15 } mstpGenMigrateTime OBJECT-TYPE SYNTAX Timeout (100..1000) MAX-ACCESS read-write STATUS current DESCRIPTION "13.22.d)" ::=3D { mstpGen 16 } mstpGenPathCostDefault OBJECT-TYPE SYNTAX INTEGER { pathCostDefault8021d1998(1), pathCostDefault8021t2001(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "(Copied from draft-ietf-bridge-rstpmib-02.txt). The version of the Spanning Tree default Path Costs = that are to be used by this Bridge. A value of = pathCostDefault8021d1998(1) uses the 16-bit default Path Costs from IEEE Std. = 802.1D-1998. A value of pathCostDefault8021t2001(2) uses the = 32-bit default Path Costs from IEEE Std. 802.1t." REFERENCE "IEEE Std 802.1D & 802.1t Table 8-5" ::=3D { mstpGen 18 } mstpGenCapable OBJECT-TYPE SYNTAX INTEGER { nonStp(0), dot1d1998(1), dot1w(2), dot1d2004(3), dot1s(4), dot1q(5), unknown(6) } MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of wheter the Bridge supports 'maximum' level Spanning Tree Protocol. The value nonStp(0) indicates, the Bridge doesn't support any Spanning Tree Protocol. The value 'dot1d1998(1)' indicates the Spanning Tree = Protocol specified in EEE 802.1D-1998, 'dot1w(2)' indicates = the Rapid Spanning Tree Protocol specified in IEEE Std 802.1w, 'dot1d2004' indicates IEEE Std 802.1D-2004 and 'dot1s(4) means MSTP IEEE Std 802.1s." ::=3D { mstpGen 19 } mstpGenForceVersion OBJECT-TYPE SYNTAX INTEGER { forceNonStp(0), forceLegacyDot1d(1), forceDot1w(2), autoDot1s(3), unknown(4) } MAX-ACCESS read-write STATUS current DESCRIPTION "The value forceNonStp(0) indicates, the Spanning Tree = Protocol is disabled on the Bridge (or the Spanning Tree = Protocol Emulation operates). Other possible values are = described in IEEE Std 802.1s clause 12.8.1.3.e)" DEFVAL { autoDot1s } ::=3D { mstpGen 20 } mstpGenCfgIdFmtSel OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "Configuration Identificator Format Selector." REFERENCE "12.12.3.4.2.a)" ::=3D { mstpGen 30 } mstpGenCfgIdName OBJECT-TYPE SYNTAX DisplayString (SIZE (32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The configuration name that identifies the MST region and is used as one of the inputs in the=20 computation of the MST Configuration Identifier." REFERENCE "12.12.3.4.2.b)" ::=3D { mstpGen 31 } mstpGenCfgIdRevLevel OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-write STATUS current DESCRIPTION "This object identifies the MST revision that=20 identifies the MST region and is used as one of the inputs in the computation of the MST=20 configuration Identifier." REFERENCE "12.12.3.4.2.c)" ::=3D { mstpGen 32 } mstpGenCfgIdDigest OBJECT-TYPE SYNTAX OCTET STRING(SIZE(16)) MAX-ACCESS read-only STATUS current DESCRIPTION "Configuration Digest." REFERENCE "12.12.3.3.3.a.4" ::=3D { mstpGen 33 } mstpGenReginalRoot OBJECT-TYPE SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "... of CIST." ::=3D { mstpGen 36 } mstpGenExternalRootCost OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "... of CIST." ::=3D { mstpGen 37 } mstpPortTable OBJECT-TYPE SYNTAX SEQUENCE OF MstpPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A table that contains generic information about every port that is associated with this bridge." ::=3D { mstp 11 } mstpPortEntry OBJECT-TYPE SYNTAX MstpPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of information for each port of the bridge." INDEX { mstpPortIndex } ::=3D { mstpPortTable 1 } MstpPortEntry ::=3D SEQUENCE { mstpPortIndex PortIndex, mstpPortAdminMACEnable TruthValue, mstpPortOperMACEnable TruthValue, mstpPortUpTime TimeTicks, mstpPortAdminExternalPathCost Integer32, mstpPortOperExternalPathCost Integer32, mstpPortAdminEdge TruthValue, mstpPortOperEdge TruthValue, mstpPortAutoEdge TruthValue, mstpPortAdminPointToPoint INTEGER, mstpPortOperPointToPoint TruthValue, mstpPortHelloTime Timeout, mstpPortAdminNonStp TruthValue, mstpPortProtocolMigration TruthValue, -- mcheck mstpPortRxTcnBpduCounter BpduCounter, mstpPortRxCfgBpduCounter BpduCounter, mstpPortRxRstBpduCounter BpduCounter, mstpPortRxMstBpduCounter BpduCounter, mstpPortTxTcnBpduCounter BpduCounter, mstpPortTxCfgBpduCounter BpduCounter, mstpPortTxRstBpduCounter BpduCounter, mstpPortTxMstBpduCounter BpduCounter } mstpPortIndex OBJECT-TYPE SYNTAX PortIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "A unique value, greater than zero, for = each Port. The value for each interface sub-layer must remain constant at least from one = re-initialization of the entity's network management = system to the next re- initialization." ::=3D { mstpPortEntry 1 } mstpPortAdminMACEnable OBJECT-TYPE=20 SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause = 12.8.2.5.2" ::=3D { mstpPortEntry 2 } mstpPortOperMACEnable OBJECT-TYPE=20 SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause = 12.8.2.5.2" ::=3D { mstpPortEntry 3 } mstpPortUpTime OBJECT-TYPE=20 SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The value of sysUpTime at the time when = the Port has been enabled by = mstpPortAdminMACEnable or linked last time." ::=3D { mstpPortEntry 4 } mstpPortAdminExternalPathCost OBJECT-TYPE SYNTAX Integer32 (0..200000000) MAX-ACCESS read-write STATUS current DESCRIPTION "The administrative value of the = External Port Cost parameter. The value 0 means, that Port Cost will = be selected automatically in correspondence with = the speed of the attached LAN." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 5 } mstpPortOperExternalPathCost OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 6 } mstpPortAdminEdge OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 7 } mstpPortOperEdge OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 8 } mstpPortAutoEdge OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "(From IEEE Std 8021D). Optional." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 9 } mstpPortAdminPointToPoint OBJECT-TYPE SYNTAX INTEGER { forceTrue(0), forceFalse(1), auto(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 10 } mstpPortOperPointToPoint OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 11 } mstpPortHelloTime OBJECT-TYPE SYNTAX Timeout MAX-ACCESS read-write STATUS current DESCRIPTION "." REFERENCE "IEEE Std 802.1s Clause " ::=3D { mstpPortEntry 12 } mstpPortAdminNonStp OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Ports with this object set to true(1) = do not participate in any STP computation; they are always = in Forwarding state, do not send BPDU and all received on = these Ports BPDU must be discarded. Such Ports are used to = define the STP termination point of the LAN." REFERENCE "." ::=3D { mstpPortEntry 13 } mstpPortProtocolMigration OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "Reflects 'mcheck' - 'Force BPDU = Migration Check' management operation, which is executes, when this = object is being set to true(1). The value false(2) in SET = operation has to be ignored. The operation GET must always = return value false(2)." REFERENCE "IEEE Std 802.1s Clause = 12.8.2.7" ::=3D { mstpPortEntry 14 } mstpPortRxTcnBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Received Topology Change Notification = (TCN) Messages." ::=3D { mstpPortEntry 15 } mstpPortRxCfgBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Received Configuration BPDUs (IEEE Std = 802.1d-1998)." ::=3D { mstpPortEntry 16 } mstpPortRxRstBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Received RST BPDUs IEEE Std = 802.1w-2001." ::=3D { mstpPortEntry 17 } mstpPortRxMstBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Received MST BPDUs IEEE Std 802.1s." ::=3D { mstpPortEntry 18 } mstpPortTxTcnBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Transmitted Topology Change = Notification (TCN) Messages." ::=3D { mstpPortEntry 19 } mstpPortTxCfgBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Transmitted Configuration BPDUs (IEEE = Std 802.1d-1998)." ::=3D { mstpPortEntry 20 } mstpPortTxRstBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Transmitted RST BPDUs IEEE Std = 802.1w-2001." ::=3D { mstpPortEntry 21 } mstpPortTxMstBpduCounter OBJECT-TYPE SYNTAX BpduCounter MAX-ACCESS read-only STATUS current DESCRIPTION "Transmitted MST BPDUs IEEE Std 802.1s." ::=3D { mstpPortEntry 22 } = =20 mstpMapTable OBJECT-TYPE SYNTAX SEQUENCE OF MstpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "MST Configuration table (VID=3D>MSTID translation): = allocates each and every possible VLAN to CST or a specific = MSTI." ::=3D { mstp 12 } mstpMapEntry OBJECT-TYPE SYNTAX MstpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "MST Configuration table (VID=3D>MSTID translation): = allocates each and every possible VLAN to CST or a specific = MSTI." INDEX { mstpMapMSTiID, mstpMapVlanRangeIndex } ::=3D { mstpMapTable 1 } MstpMapEntry ::=3D SEQUENCE { mstpMapMSTiID MstiInstanceIndex, mstpMapVlanRangeIndex Integer32, mstpMapVlanMin VlanId, mstpMapVlanMax VlanId, mstpMapRowStatus RowStatus } mstpMapMSTiID OBJECT-TYPE SYNTAX MstiInstanceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "." ::=3D { mstpMapEntry 1 } mstpMapVlanRangeIndex OBJECT-TYPE SYNTAX Integer32 (1..4094) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Signifies the index to the VLAN range entry in = the table." ::=3D { mstpMapEntry 2 } mstpMapVlanMin OBJECT-TYPE SYNTAX VlanId MAX-ACCESS read-create STATUS current DESCRIPTION "." ::=3D { mstpMapEntry 3 } mstpMapVlanMax OBJECT-TYPE SYNTAX VlanId MAX-ACCESS read-create STATUS current DESCRIPTION "." ::=3D { mstpMapEntry 4 } mstpMapRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "The status of the row as per SNMP-v2." ::=3D { mstpMapEntry 9 } mstpXstTable OBJECT-TYPE SYNTAX SEQUENCE OF MstpXstEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "." ::=3D { mstp 13 } mstpXstEntry OBJECT-TYPE SYNTAX MstpXstEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "." INDEX { mstpXstId } ::=3D { mstpXstTable 1 } MstpXstEntry ::=3D SEQUENCE { mstpXstId MstiOrCistInstanceIndex, mstpXstBridgePriority Integer32, mstpXstBridgeId BridgeId, mstpXstDesignatedRoot BridgeId, mstpXstDesignatedBridge BridgeId, mstpXstInternalRootCost Integer32, mstpXstRootPort PortIndexOrZero, mstpXstMasterPort PortIndexOrZero, mstpXstTimeSinceTopologyChange TimeTicks, mstpXstTopologyChangesCount Counter32, mstpXstTopologyChangeFlag TruthValue } mstpXstId OBJECT-TYPE SYNTAX MstiOrCistInstanceIndex MAX-ACCESS read-only STATUS current DESCRIPTION "0 means CIST." ::=3D { mstpXstEntry 1 } mstpXstBridgePriority OBJECT-TYPE SYNTAX Integer32 (0..61440) MAX-ACCESS read-write STATUS current DESCRIPTION "Bridge priority, in steps of 4096." DEFVAL { 32768 } ::=3D { mstpXstEntry 2 } mstpXstBridgeId OBJECT-TYPE SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 3 } mstpXstDesignatedRoot OBJECT-TYPE SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 4 } mstpXstDesignatedBridge OBJECT-TYPE SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 5 } mstpXstInternalRootCost OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 6 } mstpXstRootPort OBJECT-TYPE SYNTAX PortIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 7 } mstpXstMasterPort OBJECT-TYPE SYNTAX PortIndexOrZero MAX-ACCESS read-only STATUS current DESCRIPTION "Non zero value may not be in CIST." ::=3D { mstpXstEntry 8 } mstpXstTimeSinceTopologyChange OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 11 } mstpXstTopologyChangesCount OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 12 } mstpXstTopologyChangeFlag OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstEntry 13 } mstpXstPortTable OBJECT-TYPE SYNTAX SEQUENCE OF MstpXstPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "." ::=3D { mstp 14 } mstpXstPortEntry OBJECT-TYPE SYNTAX MstpXstPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "." REFERENCE "." INDEX { mstpXstPortXstId, mstpXstPortIndex } ::=3D { mstpXstPortTable 1 } MstpXstPortEntry ::=3D SEQUENCE { mstpXstPortXstId = MstiOrCistInstanceIndex, mstpXstPortIndex PortIndex, mstpXstPortState INTEGER,=20 mstpXstPortRole INTEGER,=20 mstpXstPortDesignatedRoot BridgeId, mstpXstPortExternalRootCost Integer32, mstpXstPortRegionalBridge BridgeId, mstpXstPortInternalRootCost Integer32, mstpXstPortDesignatedBridge BridgeId, mstpXstPortDesignatedPort PortId, mstpXstPortPriority Integer32, mstpXstPortAdminInternalPathCost Integer32, mstpXstPortOperInternalPathCost Integer32 } mstpXstPortXstId OBJECT-TYPE SYNTAX MstiOrCistInstanceIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "0 means CIST." ::=3D { mstpXstPortEntry 1 } mstpXstPortIndex OBJECT-TYPE SYNTAX PortIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The value of mstpPortIndex of the = Port in mstpPortTable." ::=3D { mstpXstPortEntry 2 } mstpXstPortState OBJECT-TYPE=20 SYNTAX INTEGER { disabled(0), discarding(1), learning(2), forwarding(3), unknown(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 3 } mstpXstPortRole OBJECT-TYPE=20 SYNTAX INTEGER { disabled(1), alternate(2), backup(3), =20 root(4), designated(5), master(6), nonStp(7), unknown(8) } MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 4 } mstpXstPortDesignatedRoot OBJECT-TYPE=20 SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 6 } mstpXstPortExternalRootCost OBJECT-TYPE=20 SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 7 } mstpXstPortRegionalBridge OBJECT-TYPE=20 SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 8 } mstpXstPortInternalRootCost OBJECT-TYPE=20 SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 9 } mstpXstPortDesignatedBridge OBJECT-TYPE=20 SYNTAX BridgeId MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 10 } mstpXstPortDesignatedPort OBJECT-TYPE=20 SYNTAX PortId MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 14 } mstpXstPortPriority OBJECT-TYPE=20 SYNTAX Integer32 (0..255) MAX-ACCESS read-write STATUS current DESCRIPTION "Port priority, in steps of 16." DEFVAL { 128 } ::=3D { mstpXstPortEntry 15 } mstpXstPortAdminInternalPathCost OBJECT-TYPE=20 SYNTAX Integer32 (0..200000000) MAX-ACCESS read-write STATUS current DESCRIPTION "The value 0 means, that the cost = will be selected automatically." ::=3D { mstpXstPortEntry 16 } mstpXstPortOperInternalPathCost OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "." ::=3D { mstpXstPortEntry 17 } -- Traps mstpTraps OBJECT IDENTIFIER ::=3D { mstp 0 } mstpNewRootBridge NOTIFICATION-TYPE OBJECTS { mstpXstId } STATUS current DESCRIPTION "The mstpNewRootBridge trap indicates that the sending agent has become the new root of the Spanning Tree in the CIST or in any MSTI; the trap is sent by a bridge soon after its election as the new root, e.g., upon expiration of the Topology Change Timer immediately subsequent to its election. Implementation of this trap is optional." ::=3D { mstpTraps 1 } mstpNewRootPort NOTIFICATION-TYPE OBJECTS { mstpXstId, mstpXstPortIndex } STATUS current DESCRIPTION "The mstpNewRootPort trap indicates that the sending agent has changed the root Port of the Spanning Tree in the CIST or in any MSTI. If the instance has become a root one, the sending value of the parameter mstpXstPortIndex is equal to zero. The trap is sent by a bridge soon after its election as the new root Port, e.g., upon expiration of the Topology Change Timer immediately subsequent to its election. Implementation of this trap is optional." ::=3D { mstpTraps 2 } mstpTopologyChange NOTIFICATION-TYPE OBJECTS { mstpXstId, mstpXstPortIndex, mstpXstPortState } STATUS current DESCRIPTION "A mstpTopologyChange trap is sent by a bridge when any of its configured ports n any instance (CIST or MSTI) transitions from the Learning state to the Forwarding state, or from the Forwarding state to the Blocking state. The trap is not sent if a mstpNewRootBridge trap is sent for the same transition. Implementation of this trap is optional." ::=3D { mstpTraps 3 } -- ------------------------------------------------------------- -- mstp - Conformance Information -- ------------------------------------------------------------- --- T.B.D. -- ------------------------------------------------------------- -- Units of conformance -- ------------------------------------------------------------- --- T.B.D. -- ------------------------------------------------------------- -- Compliance statements -- ------------------------------------------------------------- --- T.B.D. END 4. Relation to Original Bridge MIB =20 The interpretation of all the existing groups in the original Bridge = MIB [BRIDGEMIB] remains unchanged. In addition to the objects in the = original=20 Bridge MIB [BRIDGEMIB], this document adds mstp group with the = following=20 OID to manage the Multiple Spanning Tree Protocol: dot1dBridge XXX 5. Acknowledgments This document was produced on behalf of the Bridge MIB Working Group in the Operations and Management area of the Internet Engineering Task Force. 6. Security Considerations Security Issues are not discussed in this memo. 7. References [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for Describing SNMP Management Frameworks, RFC 2571, April 1999. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Structure of Management Information Version 2 (SMIv2), STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Textual Conventions for SMIv2, STD 58, RFC 2579, April 1999. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2), RFC 1905, January 1996. [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. McCloghrie, "Definitions of Managed Objects for Bridges", RFC 1493, July 1993. [RFC2674] Bell, E., Smith, A., Langille, P., Rijhsinghani, A., McCloghrie, A., "Definitions of Managed Objects for Bridges with Traffic Classes, Multicast Filtering and Virtual LAN Extensions", RFC 2674, August 1999. [802.1d] IEEE Std 802.1d-1998, "IEEE Standard for Information = technology Telecommunications and information exchange between systems Local and metropolitan area networks - Common = Specifications Part 3: Media Access Control (MAC) Bridges". [802.1w] IEEE Std 802.1w-2001, "(Amendment to IEEE Standard 802.1D) = IEEE Standard for Information technology - Telecommunications = and information exchange between systems - Local and metropolitan area networks--Common Specifications - Part 3: Media Access Control (MAC) Bridges: Rapid Reconfiguation". [802.1s] IEEE Std 802.1s-2002, "(Amendment to IEEE Standard 802.1Q) = IEEE Standard for Local and metropolitan area networks-Virtual Bridged Local Area Networks-Amendment 3: Multiple Spanning=20 Trees. 8. Authors' Addresses T.B.D. 9. Full Copyright Copyright (C) The Internet Society (date). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, = copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ------=_NextPart_000_0039_01C58EB2.9541FDA0 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bridge-mib mailing list [email protected] https://www1.ietf.org/mailman/listinfo/bridge-mib ------=_NextPart_000_0039_01C58EB2.9541FDA0--