idnits 2.17.1 draft-ietf-ifmib-tokenringmib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (23 June 1994) is 10893 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '3') ** Obsolete normative reference: RFC 1448 (ref. '4') (Obsoleted by RFC 1905) ** Obsolete normative reference: RFC 1443 (ref. '5') (Obsoleted by RFC 1903) ** Obsolete normative reference: RFC 1573 (ref. '6') (Obsoleted by RFC 2233) -- Possible downref: Non-RFC (?) normative reference: ref. '7' Summary: 15 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IEEE 802.5 MIB 3 23 June 1994 5 Keith McCloghrie & Eric B. Decker 6 cisco Systems, Inc. 8 10 Status of this Memo 12 This document is an Internet Draft. Internet Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its 14 Areas, and its Working Groups. Note that other groups may also 15 distribute working documents as Internet Drafts. 17 Internet Drafts are valid for a maximum of six months and may be 18 updated, replaced, or obsoleted by other documents at any time. 19 It is inappropriate to use Internet Drafts as reference material 20 or to cite them other than as a "work in progress". 22 Draft IEEE 802.5 MIB June 1994 24 1. Introduction 26 This memo defines a portion of the Management Information Base 27 (MIB) for use with network management protocols in the Internet 28 community. In particular, it describes managed objects used for 29 managing subnetworks which use the IEEE 802.5 Token Ring 30 technology described in 802.5 Token Ring Access Method and 31 Physical Layer Specifications, IEEE Standard 802.5-1989 [7]. This 32 memo is (proposed as) a replacement for RFC 1231. 34 2. The SNMPv2 Network Management Framework 36 The SNMPv2 Network Management Framework consists of four major 37 components. They are: 39 o RFC 1442 [1] which defines the SMI, the mechanisms used for 40 describing and naming objects for the purpose of management. 42 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 43 objects for the Internet suite of protocols. 45 o RFC 1445 [3] which defines the administrative and other 46 architectural aspects of the framework. 48 o RFC 1448 [4] which defines the protocol used for network 49 access to managed objects. 51 The Framework permits new objects to be defined for the purpose of 52 experimentation and evaluation. 54 2.1. Object Definitions 56 Managed objects are accessed via a virtual information store, 57 termed the Management Information Base or MIB. Objects in the MIB 58 are defined using the subset of Abstract Syntax Notation One 59 (ASN.1) defined in the SMI. In particular, each object type is 60 named by an OBJECT IDENTIFIER, an administratively assigned name. 61 The object type together with an object instance serves to 62 uniquely identify a specific instantiation of the object. For 63 human convenience, we often use a textual string, termed the 64 descriptor, to refer to the object type. 66 Draft IEEE 802.5 MIB June 1994 68 3. Changes from RFC 1231 70 This memo has the following differences from RFC 1231: 72 (1) This memo is formatted using the SNMPv2 SMI. 74 (2) The relationship of the "open" and "close" states of 75 dot5Commands to the value of ifAdminStatus has been 76 clarified. In particular, the setting of one affects the 77 value of the other. 79 (3) The relationship dot5RingSpeed and ifSpeed has been 80 clarified. In particular, ifSpeed indicates the current 81 ring-speed; dot5RingSpeed indicates the ring-speed at the 82 next insertion into the ring. If the interface doesn't 83 support changing ring-speed, then dot5RingSpeed can only be 84 set to its current value. When dot5RingSpeed has the value 85 'unknown(1)', the ring-speed is to be set to the ring's 86 actual ring-speed. 88 (4) Write-access to dot5ActMonParticipate is not required, and a 89 change to the value of dot5ActMonParticipate does not take 90 effect until the next Active Monitor election. 92 (5) Write-access to dot5Functional is not required. ,np A new 93 object, dot5LastBeaconSent has been defined to contain the 94 timestamp of the last beacon frame sent. 96 (6) The dot5TimerTable has been designated as obsolete. 98 (7) Text has been added describing the applicability of RFC 1573 99 [6] to 802.5 interfaces. 101 (8) Other minor editorial changes. 103 Draft IEEE 802.5 MIB June 1994 105 4. Overview 107 This memo defines three tables: the 802.5 Interface Table, which 108 contains state and parameter information which is specific to 109 802.5 interfaces, the 802.5 Statistics Table, which contains 802.5 110 interface statistics, and the 802.5 Timer Table, which contains 111 the values of 802.5-defined timers. A managed system will have one 112 entry in the 802.5 Interface Table and one entry in the 802.5 113 Statistics Table for each of its 802.5 interfaces. The 802.5 114 Timer Table is obsolete, but its definition has been retained in 115 this memo for backward compatibility. 117 This memo also defines OBJECT IDENTIFIERs, some to identify 118 interface tests for use with the ifTestTable [6], and some to 119 identify Token Ring interface Chip Sets. 121 4.1. MAC Addresses 123 All representations of MAC addresses in this MIB Module use the 124 MacAddress textual convention [5] for which the address is in the 125 "canonical" order defined by IEEE 802.1a, i.e., as if it were 126 transmitted least significant bit first, even though 802.5 127 requires MAC addresses to be transmitted most significant bit 128 first. 130 16-bit addresses, if needed, are represented by setting their 131 upper 4 octets to all zeros, i.e., AAFF would be represented as 132 00000000AAFF. 134 4.2. Relationship to RFC 1213 136 When this MIB module is used in conjunction with the "old" (i.e., 137 pre-RFC 1573) interfaces group, the relationship between an 802.5 138 interface and an interface in the context of the RFC 1213 is one- 139 to-one. That is, the value of an ifIndex object instance for an 140 802.5 interface can be directly used to identify corresponding 141 instances of the objects defined in this memo. 143 4.3. Relationship to RFC 1573 145 RFC 1573, the Interface MIB Evolution, requires that any MIB 146 module which is an adjunct of the Interface MIB, clarify specific 147 Draft IEEE 802.5 MIB June 1994 149 areas within the Interface MIB. These areas were intentionally 150 left vague in RFC 1573 to avoid over constraining the MIB module, 151 thereby precluding management of certain media-types. 153 Section 3.3 of RFC 1573 enumerates several areas which a media- 154 specific MIB module must clarify. Each of these areas is 155 addressed in a following subsection. The implementor is referred 156 to RFC 1573 in order to understand the general intent of these 157 areas. 159 4.3.1. Layering Model 161 For the typical usage of this IEEE 802.5 MIB module, there will be 162 no sub-layers "above" or "below" the 802.5 interface. However, 163 this MIB module does not preclude such layering. 165 4.3.2. Virtual Circuits 167 802.5 does not support virtual circuits. 169 4.3.3. ifTestTable 171 This MIB module defines two tests for 802.5 interfaces: Insertion 172 and Loopback. Implementation of these tests is not required. 174 4.3.4. ifRcvAddressTable 176 The ifRcvAddressTable is defined to contains all MAC addresses, 177 unicast, multicast and broadcast, for which an interface will 178 receive packets. For 802.5 interfaces, its use includes 179 functional addresses. The format of the address, contained in 180 ifRcvAddressAddress, is the same as for ifPhysAddress. 182 For functional addresses on a particular 802.5 interface, only one 183 ifRcvAddressTable entry is required. That entry is the one for 184 the address which has the functional address bit ANDed with the 185 bit mask of all functional addresses for which the interface will 186 accept frames. 188 Draft IEEE 802.5 MIB June 1994 190 4.3.5. ifPhysAddress 192 For an 802.5 interface, ifPhysAddress contains the interface's 193 IEEE MAC address, stored as an octet string of length 6, in IEEE 194 802.1a "canonical" order, i.e., the Group Bit is positioned as the 195 low-order bit (0x01) of the first octet. 197 4.3.6. ifType 199 The objects defined in this memo apply to each interface for which 200 the ifType has the value: 202 iso88025-tokenRing(9) 204 Draft IEEE 802.5 MIB June 1994 206 5. Definitions 208 TOKENRING-MIB DEFINITIONS ::= BEGIN 210 IMPORTS 211 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 212 experimental, 213 Counter32, Integer32 FROM SNMPv2-SMI 214 transmission FROM RFC1213-MIB 215 MacAddress,TimeStamp FROM SNMPv2-TC 216 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 218 dot5MIB MODULE-IDENTITY 219 LAST-UPDATED "9406231150Z" 220 ORGANIZATION "IETF Interfaces MIB Working Group" 221 CONTACT-INFO 222 "Keith McCloghrie 223 cisco Systems, Inc. 224 1525 O'Brien Dr. 225 Menlo Park, CA 94025 227 Phone: (415) 324-5260 228 EMail: kzm@cisco.com" 229 DESCRIPTION 230 "The MIB module for IEEE 802.5 Token Ring interfaces." 231 ::= { experimental 999 } 233 dot5 OBJECT IDENTIFIER ::= { transmission 9 } 234 Draft IEEE 802.5 MIB June 1994 236 -- The 802.5 Interface Table 238 -- This table contains state and parameter information which 239 -- is specific to 802.5 interfaces. It is mandatory that 240 -- systems having 802.5 interfaces implement this table in 241 -- addition to the ifTable (see RFCs 1213 and 1573). 243 dot5Table OBJECT-TYPE 244 SYNTAX SEQUENCE OF Dot5Entry 245 MAX-ACCESS not-accessible 246 STATUS current 247 DESCRIPTION 248 "This table contains Token Ring interface 249 parameters and state variables, one entry 250 per 802.5 interface." 251 ::= { dot5 1 } 253 dot5Entry OBJECT-TYPE 254 SYNTAX Dot5Entry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "A list of Token Ring status and parameter 259 values for an 802.5 interface." 260 INDEX { dot5IfIndex } 261 ::= { dot5Table 1 } 263 Dot5Entry ::= SEQUENCE { 264 dot5IfIndex Integer32, 265 dot5Commands INTEGER, 266 dot5RingStatus INTEGER, 267 dot5RingState INTEGER, 268 dot5RingOpenStatus INTEGER, 269 dot5RingSpeed INTEGER, 270 dot5UpStream MacAddress, 271 dot5ActMonParticipate INTEGER, 272 dot5Functional MacAddress, 273 dot5LastBeaconSent TimeStamp 274 } 276 dot5IfIndex OBJECT-TYPE 277 SYNTAX Integer32 278 MAX-ACCESS read-only 279 STATUS current 280 DESCRIPTION 282 Draft IEEE 802.5 MIB June 1994 284 "The value of this object identifies the 285 802.5 interface for which this entry 286 contains management information. The 287 value of this object for a particular 288 interface has the same value as the 289 ifIndex object, defined in MIB-II for 290 the same interface." 291 ::= { dot5Entry 1 } 293 dot5Commands OBJECT-TYPE 294 SYNTAX INTEGER { 295 noop(1), 296 open(2), 297 reset(3), 298 close(4) 299 } 300 MAX-ACCESS read-write 301 STATUS current 302 DESCRIPTION 303 "When this object is set to the value of 304 open(2), the station should go into the 305 open state. The progress and success of 306 the open is given by the values of the 307 objects dot5RingState and 308 dot5RingOpenStatus. 309 When this object is set to the value 310 of reset(3), then the station should do 311 a reset. On a reset, all MIB counters 312 should retain their values, if possible. 313 Other side affects are dependent on the 314 hardware chip set. 315 When this object is set to the value 316 of close(4), the station should go into 317 the stopped state by removing itself 318 from the ring. 319 Setting this object to a value of 320 noop(1) has no effect. 321 When read, this object always has a 322 value of noop(1). 323 The open(2) and close(4) values 324 correspond to the up(1) and down(2) values 325 of MIB-II's ifAdminStatus and ifOperStatus, 326 i.e., the setting of ifAdminStatus and 327 dot5Commands affects the values of both 328 dot5Commands and ifOperStatus." 330 Draft IEEE 802.5 MIB June 1994 332 ::= { dot5Entry 2 } 334 dot5RingStatus OBJECT-TYPE 335 SYNTAX INTEGER (0..262143) 336 MAX-ACCESS read-only 337 STATUS current 338 DESCRIPTION 339 "The current interface status which can 340 be used to diagnose fluctuating problems 341 that can occur on token rings, after a 342 station has successfully been added to 343 the ring. 344 Before an open is completed, this 345 object has the value for the 'no status' 346 condition. The dot5RingState and 347 dot5RingOpenStatus objects provide for 348 debugging problems when the station 349 can not even enter the ring. 350 The object's value is a sum of 351 values, one for each currently applicable 352 condition. The following values are 353 defined for various conditions: 355 0 = No Problems detected 356 32 = Ring Recovery 357 64 = Single Station 358 256 = Remove Received 359 512 = reserved 360 1024 = Auto-Removal Error 361 2048 = Lobe Wire Fault 362 4096 = Transmit Beacon 363 8192 = Soft Error 364 16384 = Hard Error 365 32768 = Signal Loss 366 131072 = no status, open not completed." 367 ::= { dot5Entry 3 } 369 dot5RingState OBJECT-TYPE 370 SYNTAX INTEGER { 371 opened(1), 372 closed(2), 373 opening(3), 374 closing(4), 375 openFailure(5), 376 ringFailure(6) 378 Draft IEEE 802.5 MIB June 1994 380 } 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 384 "The current interface state with respect 385 to entering or leaving the ring." 386 ::= { dot5Entry 4 } 388 dot5RingOpenStatus OBJECT-TYPE 389 SYNTAX INTEGER { 390 noOpen(1), -- no open attempted 391 badParam(2), 392 lobeFailed(3), 393 signalLoss(4), 394 insertionTimeout(5), 395 ringFailed(6), 396 beaconing(7), 397 duplicateMAC(8), 398 requestFailed(9), 399 removeReceived(10), 400 open(11) -- last open successful 401 } 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "This object indicates the success, or the 406 reason for failure, of the station's most 407 recent attempt to enter the ring." 408 ::= { dot5Entry 5 } 410 dot5RingSpeed OBJECT-TYPE 411 SYNTAX INTEGER { 412 unknown(1), 413 oneMegabit(2), 414 fourMegabit(3), 415 sixteenMegabit(4) 416 } 417 MAX-ACCESS read-write 418 STATUS current 419 DESCRIPTION 420 "The ring-speed at the next insertion into 421 the ring. Note that this may or may not be 422 different to the current ring-speed which is 423 given by MIB-II's ifSpeed. For interfaces 424 which do not support changing ring-speed, 426 Draft IEEE 802.5 MIB June 1994 428 dot5RingSpeed can only be set to its current 429 value. When dot5RingSpeed has the value 430 unknown(1), the ring's actual ring-speed is 431 to be used." 432 ::= { dot5Entry 6 } 434 dot5UpStream OBJECT-TYPE 435 SYNTAX MacAddress 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The MAC-address of the up stream neighbor 440 station in the ring." 441 ::= { dot5Entry 7 } 443 dot5ActMonParticipate OBJECT-TYPE 444 SYNTAX INTEGER { 445 true(1), 446 false(2) 447 } 448 MAX-ACCESS read-write 449 STATUS current 450 DESCRIPTION 451 "If this object has a value of true(1) then 452 this interface will participate in the 453 active monitor selection process. If the 454 value is false(2) then it will not. 455 Setting this object does not take effect 456 until the next Active Monitor election, and 457 might not take effect until the next time 458 the interface is opened." 459 ::= { dot5Entry 8 } 461 dot5Functional OBJECT-TYPE 462 SYNTAX MacAddress 463 MAX-ACCESS read-write 464 STATUS current 465 DESCRIPTION 466 "The bit mask of all Token Ring functional 467 addresses for which this interface will 468 accept frames." 469 ::= { dot5Entry 9 } 471 dot5LastBeaconSent OBJECT-TYPE 472 SYNTAX TimeStamp 474 Draft IEEE 802.5 MIB June 1994 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The value of MIB-II's sysUpTime object at which 480 the local system last transmitted a Beacon frame 481 on this interface." 482 ::= { dot5Entry 10 } 484 -- The 802.5 Statistics Table 486 -- This table contains statistics and error counter which are 487 -- specific to 802.5 interfaces. It is mandatory that systems 488 -- having 802.5 interfaces implement this table. 490 dot5StatsTable OBJECT-TYPE 491 SYNTAX SEQUENCE OF Dot5StatsEntry 492 MAX-ACCESS not-accessible 493 STATUS current 494 DESCRIPTION 495 "A table containing Token Ring statistics, 496 one entry per 802.5 interface. 497 All the statistics are defined using 498 the syntax Counter32 as 32-bit wrap around 499 counters. Thus, if an interface's 500 hardware maintains these statistics in 501 16-bit counters, then the agent must read 502 the hardware's counters frequently enough 503 to prevent loss of significance, in order 504 to maintain 32-bit counters in software." 505 ::= { dot5 2 } 507 dot5StatsEntry OBJECT-TYPE 508 SYNTAX Dot5StatsEntry 509 MAX-ACCESS not-accessible 510 STATUS current 511 DESCRIPTION 512 "An entry contains the 802.5 statistics 513 for a particular interface." 514 INDEX { dot5StatsIfIndex } 515 ::= { dot5StatsTable 1 } 517 Dot5StatsEntry ::= SEQUENCE { 518 dot5StatsIfIndex Integer32, 519 dot5StatsLineErrors Counter32, 521 Draft IEEE 802.5 MIB June 1994 523 dot5StatsBurstErrors Counter32, 524 dot5StatsACErrors Counter32, 525 dot5StatsAbortTransErrors Counter32, 526 dot5StatsInternalErrors Counter32, 527 dot5StatsLostFrameErrors Counter32, 528 dot5StatsReceiveCongestions Counter32, 529 dot5StatsFrameCopiedErrors Counter32, 530 dot5StatsTokenErrors Counter32, 531 dot5StatsSoftErrors Counter32, 532 dot5StatsHardErrors Counter32, 533 dot5StatsSignalLoss Counter32, 534 dot5StatsTransmitBeacons Counter32, 535 dot5StatsRecoverys Counter32, 536 dot5StatsLobeWires Counter32, 537 dot5StatsRemoves Counter32, 538 dot5StatsSingles Counter32, 539 dot5StatsFreqErrors Counter32 540 } 542 dot5StatsIfIndex OBJECT-TYPE 543 SYNTAX Integer32 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "The value of this object identifies the 548 802.5 interface for which this entry 549 contains management information. The 550 value of this object for a particular 551 interface has the same value as MIB-II's 552 ifIndex object for the same interface." 553 ::= { dot5StatsEntry 1 } 555 dot5StatsLineErrors OBJECT-TYPE 556 SYNTAX Counter32 557 MAX-ACCESS read-only 558 STATUS current 559 DESCRIPTION 560 "This counter is incremented when a frame 561 or token is copied or repeated by a 562 station, the E bit is zero in the frame 563 or token and one of the following 564 conditions exists: 1) there is a 565 non-data bit (J or K bit) between the SD 566 and the ED of the frame or token, or 568 Draft IEEE 802.5 MIB June 1994 570 2) there is an FCS error in the frame." 571 ::= { dot5StatsEntry 2 } 573 dot5StatsBurstErrors OBJECT-TYPE 574 SYNTAX Counter32 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "This counter is incremented when a station 579 detects the absence of transitions for five 580 half-bit timers (burst-five error)." 581 ::= { dot5StatsEntry 3 } 583 dot5StatsACErrors OBJECT-TYPE 584 SYNTAX Counter32 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "This counter is incremented when a station 589 receives an AMP or SMP frame in which A is 590 equal to C is equal to 0, and then receives 591 another SMP frame with A is equal to C is 592 equal to 0 without first receiving an AMP 593 frame. It denotes a station that cannot set 594 the AC bits properly." 595 ::= { dot5StatsEntry 4 } 597 dot5StatsAbortTransErrors OBJECT-TYPE 598 SYNTAX Counter32 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "This counter is incremented when a station 603 transmits an abort delimiter while 604 transmitting." 605 ::= { dot5StatsEntry 5 } 607 dot5StatsInternalErrors OBJECT-TYPE 608 SYNTAX Counter32 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "This counter is incremented when a station 613 recognizes an internal error." 614 ::= { dot5StatsEntry 6 } 616 Draft IEEE 802.5 MIB June 1994 618 dot5StatsLostFrameErrors OBJECT-TYPE 619 SYNTAX Counter32 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "This counter is incremented when a station 624 is transmitting and its TRR timer expires. 625 This condition denotes a condition where a 626 transmitting station in strip mode does not 627 receive the trailer of the frame before the 628 TRR timer goes off." 629 ::= { dot5StatsEntry 7 } 631 dot5StatsReceiveCongestions OBJECT-TYPE 632 SYNTAX Counter32 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "This counter is incremented when a station 637 recognizes a frame addressed to its 638 specific address, but has no available 639 buffer space indicating that the station 640 is congested." 641 ::= { dot5StatsEntry 8 } 643 dot5StatsFrameCopiedErrors OBJECT-TYPE 644 SYNTAX Counter32 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "This counter is incremented when a station 649 recognizes a frame addressed to its 650 specific address and detects that the FS 651 field A bits are set to 1 indicating a 652 possible line hit or duplicate address." 653 ::= { dot5StatsEntry 9 } 655 dot5StatsTokenErrors OBJECT-TYPE 656 SYNTAX Counter32 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "This counter is incremented when a station 661 acting as the active monitor recognizes an 662 error condition that needs a token 664 Draft IEEE 802.5 MIB June 1994 666 transmitted." 667 ::= { dot5StatsEntry 10 } 669 dot5StatsSoftErrors OBJECT-TYPE 670 SYNTAX Counter32 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The number of Soft Errors the interface 675 has detected. It directly corresponds to 676 the number of Report Error MAC frames 677 that this interface has transmitted. 678 Soft Errors are those which are 679 recoverable by the MAC layer protocols." 680 ::= { dot5StatsEntry 11 } 682 dot5StatsHardErrors OBJECT-TYPE 683 SYNTAX Counter32 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The number of times this interface has 688 detected an immediately recoverable 689 fatal error. It denotes the number of 690 times this interface is either 691 transmitting or receiving beacon MAC 692 frames." 693 ::= { dot5StatsEntry 12 } 695 dot5StatsSignalLoss OBJECT-TYPE 696 SYNTAX Counter32 697 MAX-ACCESS read-only 698 STATUS current 699 DESCRIPTION 700 "The number of times this interface has 701 detected the loss of signal condition from 702 the ring." 703 ::= { dot5StatsEntry 13 } 705 dot5StatsTransmitBeacons OBJECT-TYPE 706 SYNTAX Counter32 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The number of times this interface has 712 Draft IEEE 802.5 MIB June 1994 714 transmitted a beacon frame." 715 ::= { dot5StatsEntry 14 } 717 dot5StatsRecoverys OBJECT-TYPE 718 SYNTAX Counter32 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The number of Claim Token MAC frames 723 received or transmitted after the interface 724 has received a Ring Purge MAC frame. This 725 counter signifies the number of times the 726 ring has been purged and is being recovered 727 back into a normal operating state." 728 ::= { dot5StatsEntry 15 } 730 dot5StatsLobeWires OBJECT-TYPE 731 SYNTAX Counter32 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The number of times the interface has 736 detected an open or short circuit in the 737 lobe data path. The adapter will be closed 738 and dot5RingState will signify this 739 condition." 740 ::= { dot5StatsEntry 16 } 742 dot5StatsRemoves OBJECT-TYPE 743 SYNTAX Counter32 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The number of times the interface has 748 received a Remove Ring Station MAC frame 749 request. When this frame is received 750 the interface will enter the close state 751 and dot5RingState will signify this 752 condition." 753 ::= { dot5StatsEntry 17 } 755 dot5StatsSingles OBJECT-TYPE 756 SYNTAX Counter32 757 MAX-ACCESS read-only 758 STATUS current 760 Draft IEEE 802.5 MIB June 1994 762 DESCRIPTION 763 "The number of times the interface has 764 sensed that it is the only station on the 765 ring. This will happen if the interface 766 is the first one up on a ring, or if 767 there is a hardware problem." 768 ::= { dot5StatsEntry 18 } 770 dot5StatsFreqErrors OBJECT-TYPE 771 SYNTAX Counter32 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "The number of times the interface has 776 detected that the frequency of the 777 incoming signal differs from the expected 778 frequency by more than that specified by 779 the IEEE 802.5 standard." 780 ::= { dot5StatsEntry 19 } 782 -- The Timer Table 784 -- This group contains the values of timers for 802.5 785 -- interfaces. This table is obsolete, but its definition 786 -- is retained here for backwards compatibility. 788 dot5TimerTable OBJECT-TYPE 789 SYNTAX SEQUENCE OF Dot5TimerEntry 790 MAX-ACCESS not-accessible 791 STATUS obsolete 792 DESCRIPTION 793 "This table contains Token Ring interface 794 timer values, one entry per 802.5 795 interface." 796 ::= { dot5 5 } 798 dot5TimerEntry OBJECT-TYPE 799 SYNTAX Dot5TimerEntry 800 MAX-ACCESS not-accessible 801 STATUS obsolete 802 DESCRIPTION 803 "A list of Token Ring timer values for an 804 802.5 interface." 805 INDEX { dot5TimerIfIndex } 807 Draft IEEE 802.5 MIB June 1994 809 ::= { dot5TimerTable 1 } 811 Dot5TimerEntry ::= SEQUENCE { 812 dot5TimerIfIndex Integer32, 813 dot5TimerReturnRepeat Integer32, 814 dot5TimerHolding Integer32, 815 dot5TimerQueuePDU Integer32, 816 dot5TimerValidTransmit Integer32, 817 dot5TimerNoToken Integer32, 818 dot5TimerActiveMon Integer32, 819 dot5TimerStandbyMon Integer32, 820 dot5TimerErrorReport Integer32, 821 dot5TimerBeaconTransmit Integer32, 822 dot5TimerBeaconReceive Integer32 823 } 825 dot5TimerIfIndex OBJECT-TYPE 826 SYNTAX Integer32 827 MAX-ACCESS read-only 828 STATUS obsolete 829 DESCRIPTION 830 "The value of this object identifies the 831 802.5 interface for which this entry 832 contains timer values. The value of 833 this object for a particular interface 834 has the same value as MIB-II's ifIndex 835 object for the same interface." 836 ::= { dot5TimerEntry 1 } 838 dot5TimerReturnRepeat OBJECT-TYPE 839 SYNTAX Integer32 840 MAX-ACCESS read-only 841 STATUS obsolete 842 DESCRIPTION 843 "The time-out value used to ensure the 844 interface will return to Repeat State, in 845 units of 100 micro-seconds. The value 846 should be greater than the maximum ring 847 latency." 848 ::= { dot5TimerEntry 2 } 850 dot5TimerHolding OBJECT-TYPE 851 SYNTAX Integer32 852 MAX-ACCESS read-only 853 STATUS obsolete 855 Draft IEEE 802.5 MIB June 1994 857 DESCRIPTION 858 "Maximum period of time a station is 859 permitted to transmit frames after capturing 860 a token, in units of 100 micro-seconds." 861 ::= { dot5TimerEntry 3 } 863 dot5TimerQueuePDU OBJECT-TYPE 864 SYNTAX Integer32 865 MAX-ACCESS read-only 866 STATUS obsolete 867 DESCRIPTION 868 "The time-out value for enqueuing of an SMP 869 PDU after reception of an AMP or SMP 870 frame in which the A and C bits were 871 equal to 0, in units of 100 872 micro-seconds." 873 ::= { dot5TimerEntry 4 } 875 dot5TimerValidTransmit OBJECT-TYPE 876 SYNTAX Integer32 877 MAX-ACCESS read-only 878 STATUS obsolete 879 DESCRIPTION 880 "The time-out value used by the active 881 monitor to detect the absence of valid 882 transmissions, in units of 100 883 micro-seconds." 884 ::= { dot5TimerEntry 5 } 886 dot5TimerNoToken OBJECT-TYPE 887 SYNTAX Integer32 888 MAX-ACCESS read-only 889 STATUS obsolete 890 DESCRIPTION 891 "The time-out value used to recover from 892 various-related error situations. 893 If N is the maximum number of stations on 894 the ring, the value of this timer is 895 normally: 896 dot5TimerReturnRepeat + N*dot5TimerHolding." 897 ::= { dot5TimerEntry 6 } 899 dot5TimerActiveMon OBJECT-TYPE 900 SYNTAX Integer32 901 MAX-ACCESS read-only 903 Draft IEEE 802.5 MIB June 1994 905 STATUS obsolete 906 DESCRIPTION 907 "The time-out value used by the active 908 monitor to stimulate the enqueuing of an 909 AMP PDU for transmission, in units of 910 100 micro-seconds." 911 ::= { dot5TimerEntry 7 } 913 dot5TimerStandbyMon OBJECT-TYPE 914 SYNTAX Integer32 915 MAX-ACCESS read-only 916 STATUS obsolete 917 DESCRIPTION 918 "The time-out value used by the stand-by 919 monitors to ensure that there is an active 920 monitor on the ring and to detect a 921 continuous stream of tokens, in units of 922 100 micro-seconds." 923 ::= { dot5TimerEntry 8 } 925 dot5TimerErrorReport OBJECT-TYPE 926 SYNTAX Integer32 927 MAX-ACCESS read-only 928 STATUS obsolete 929 DESCRIPTION 930 "The time-out value which determines how 931 often a station shall send a Report Error 932 MAC frame to report its error counters, 933 in units of 100 micro-seconds." 934 ::= { dot5TimerEntry 9 } 936 dot5TimerBeaconTransmit OBJECT-TYPE 937 SYNTAX Integer32 938 MAX-ACCESS read-only 939 STATUS obsolete 940 DESCRIPTION 941 "The time-out value which determines how 942 long a station shall remain in the state 943 of transmitting Beacon frames before 944 entering the Bypass state, in units of 945 100 micro-seconds." 946 ::= { dot5TimerEntry 10 } 948 dot5TimerBeaconReceive OBJECT-TYPE 949 SYNTAX Integer32 951 Draft IEEE 802.5 MIB June 1994 953 MAX-ACCESS read-only 954 STATUS obsolete 955 DESCRIPTION 956 "The time-out value which determines how 957 long a station shall receive Beacon 958 frames from its downstream neighbor 959 before entering the Bypass state, in 960 units of 100 micro-seconds." 961 ::= { dot5TimerEntry 11 } 963 Draft IEEE 802.5 MIB June 1994 965 -- 802.5 Interface Tests 967 dot5Tests OBJECT IDENTIFIER ::= { dot5 3 } 969 -- RFC 1573 defines the ifTestTable, through which a 970 -- network manager can instruct an agent to test an interface 971 -- for various faults. A test to be performed is identified 972 -- as an OBJECT IDENTIFIER. 974 -- The Insert Function test 976 dot5TestInsertFunc OBJECT-IDENTITY 977 STATUS current 978 DESCRIPTION 979 "Invoking this test causes the station to test the insert 980 ring logic of the hardware if the station's lobe media 981 cable is connected to a wiring concentrator. Note that 982 this command inserts the station into the network, and 983 thus, could cause problems if the station is connected 984 to a operational network." 985 ::= { dot5Tests 1 } 987 -- The Full-Duplex Loop Back test 989 dot5TestFullDuplexLoopBack OBJECT-IDENTITY 990 STATUS current 991 DESCRIPTION 992 "Invoking this test on a 802.5 interface causes the 993 interface to check the path from memory through the 994 chip set's internal logic and back to memory, thus 995 checking the proper functioning of the systems's 996 interface to the chip set." 997 ::= { dot5Tests 2 } 999 Draft IEEE 802.5 MIB June 1994 1001 -- 802.5 Hardware Chip Sets 1003 -- RFC 1229 specified an object, ifExtnsChipSet, with the 1004 -- syntax of OBJECT IDENTIFIER, to identify the hardware 1005 -- chip set in use by an interface. RFC 1573 obsoletes 1006 -- the use of ifExtnsChipSet. However, the following 1007 -- definitions are retained for backwards compatibility. 1009 dot5ChipSets OBJECT IDENTIFIER ::= { dot5 4 } 1011 dot5ChipSetIBM16 OBJECT-IDENTITY 1012 STATUS current 1013 DESCRIPTION 1014 "IBM's 16/4 Mbs chip set." 1015 ::= { dot5ChipSets 1 } 1017 dot5ChipSetTItms380 OBJECT-IDENTITY 1018 STATUS current 1019 DESCRIPTION 1020 "Texas Instruments' TMS 380 4Mbs chip-set" 1021 ::= { dot5ChipSets 2 } 1023 dot5ChipSetTItms380c16 OBJECT-IDENTITY 1024 STATUS current 1025 DESCRIPTION 1026 "Texas Instruments' TMS 380C16 16/4 Mbs chip-set" 1027 ::= { dot5ChipSets 3 } 1029 Draft IEEE 802.5 MIB June 1994 1031 -- conformance information 1033 dot5Conformance OBJECT IDENTIFIER ::= { dot5MIB 2 } 1035 dot5Groups OBJECT IDENTIFIER ::= { dot5Conformance 1 } 1036 dot5Compliances OBJECT IDENTIFIER ::= { dot5Conformance 2 } 1038 -- compliance statements 1040 dot5Compliance MODULE-COMPLIANCE 1041 STATUS current 1042 DESCRIPTION 1043 "The compliance statement for SNMPv2 entities 1044 which implement the IEEE 802.5 MIB." 1046 MODULE -- this module 1047 MANDATORY-GROUPS { dot5StateGroup, dot5StatsGroup } 1049 OBJECT dot5ActMonParticipate 1050 MIN-ACCESS read-only 1051 DESCRIPTION 1052 "Write access is not required." 1054 OBJECT dot5Functional 1055 MIN-ACCESS read-only 1056 DESCRIPTION 1057 "Write access is not required." 1059 ::= { dot5Compliances 1 } 1061 Draft IEEE 802.5 MIB June 1994 1063 -- units of conformance 1065 dot5StateGroup OBJECT-GROUP 1066 OBJECTS { dot5Commands, dot5RingStatus, dot5RingState, 1067 dot5RingOpenStatus, dot5RingSpeed, dot5UpStream, 1068 dot5ActMonParticipate, dot5Functional, 1069 dot5LastBeaconSent 1070 } 1071 STATUS current 1072 DESCRIPTION 1073 "A collection of objects providing state information 1074 and parameters for IEEE 802.5 interfaces." 1075 ::= { dot5Groups 1 } 1077 dot5StatsGroup OBJECT-GROUP 1078 OBJECTS { dot5StatsLineErrors, dot5StatsBurstErrors, 1079 dot5StatsACErrors, dot5StatsAbortTransErrors, 1080 dot5StatsInternalErrors, dot5StatsLostFrameErrors, 1081 dot5StatsReceiveCongestions, 1082 dot5StatsFrameCopiedErrors, dot5StatsTokenErrors, 1083 dot5StatsSoftErrors, dot5StatsHardErrors, 1084 dot5StatsSignalLoss, dot5StatsTransmitBeacons, 1085 dot5StatsRecoverys, dot5StatsLobeWires, 1086 dot5StatsRemoves, dot5StatsSingles, 1087 dot5StatsFreqErrors 1088 } 1089 STATUS current 1090 DESCRIPTION 1091 "A collection of objects providing statistics for 1092 IEEE 802.5 interfaces." 1093 ::= { dot5Groups 2 } 1095 END 1096 Draft IEEE 802.5 MIB June 1994 1098 6. Acknowledgements 1100 The changes from RFC 1231 are the result of discussions on the 1101 IETF's snmp mailing-list and in the Interfaces MIB Working Group. 1103 7. References 1105 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1106 "Structure of Management Information for version 2 of the 1107 Simple Network Management Protocol (SNMPv2)", RFC 1442, SNMP 1108 Research,Inc., Hughes LAN Systems, Dover Beach Consulting, 1109 Inc., Carnegie Mellon University, April 1993. 1111 [2] McCloghrie, K., and M. Rose, Editors, "Management Information 1112 Base for Network Management of TCP/IP-based internets: MIB- 1113 II", STD 17, RFC 1213, Hughes LAN Systems, Performance 1114 Systems International, March 1991. 1116 [3] Galvin, J., and K. McCloghrie, "Administrative Model for 1117 version 2 of the Simple Network Management Protocol 1118 (SNMPv2)", RFC 1445, Trusted Information Systems, Hughes LAN 1119 Systems, April 1993. 1121 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1122 "Protocol Operations for version 2 of the Simple Network 1123 Management Protocol (SNMPv2)", RFC 1448, SNMP Research,Inc., 1124 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie 1125 Mellon University, April 1993. 1127 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1128 "Textual Conventions for version 2 of the Simple Network 1129 Management Protocol (SNMPv2)", RFC 1443, SNMP Research,Inc., 1130 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie 1131 Mellon University, April 1993. 1133 [6] McCloghrie, K., and F. Kastenholz, "Evolution of the 1134 Interfaces Group of MIB-II", RFC 1573, Hughes LAN Systems, 1135 FTP Software, Jan 1994 1137 [7] Institute of Electrical and Electronic Engineers, "Token Ring 1138 Access Method and Physical Layer Specifications", IEEE 1139 Standard 802.5-1989, 1989. 1141 Draft IEEE 802.5 MIB June 1994 1143 8. Security Considerations 1145 Security issues are not discussed in this memo. 1147 9. Author's Address 1149 Keith McCloghrie 1150 cisco Systems, Inc. 1151 1525 O'Brien Dr. 1152 Menlo Park, CA 94025 1153 Phone: (415) 324-5260 1154 EMail: kzm@cisco.com 1156 Eric B. Decker 1157 cisco Systems, Inc. 1158 1525 O'Brien Dr. 1159 Menlo Park, CA 94025 1160 Phone: (415) 688-8241 1161 EMail: cire@cisco.com 1163 Draft IEEE 802.5 MIB June 1994 1165 Table of Contents 1167 1 Introduction .............................................. 2 1168 2 The SNMPv2 Network Management Framework ................... 2 1169 2.1 Object Definitions ...................................... 2 1170 3 Changes from RFC 1231 ..................................... 3 1171 4 Overview .................................................. 4 1172 4.1 MAC Addresses ........................................... 4 1173 4.2 Relationship to RFC 1213 ................................ 4 1174 4.3 Relationship to RFC 1573 ................................ 4 1175 4.3.1 Layering Model ........................................ 5 1176 4.3.2 Virtual Circuits ...................................... 5 1177 4.3.3 ifTestTable ........................................... 5 1178 4.3.4 ifRcvAddressTable ..................................... 5 1179 4.3.5 ifPhysAddress ......................................... 6 1180 4.3.6 ifType ................................................ 6 1181 5 Definitions ............................................... 7 1182 6 Acknowledgements .......................................... 28 1183 7 References ................................................ 28 1184 8 Security Considerations ................................... 29 1185 9 Author's Address .......................................... 29