idnits 2.17.1 draft-ietf-vgmib-repeater-dev-01.txt: ** The Abstract section seems to be numbered 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-16) 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 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 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: ---------------------------------------------------------------------------- == Line 1877 has weird spacing: '... object to 'n...' -- 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 (December 18, 1995) is 10347 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '3' is defined on line 2298, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 2304, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Obsolete normative reference: RFC 1442 (ref. '2') (Obsoleted by RFC 1902) ** Obsolete normative reference: RFC 1443 (ref. '3') (Obsoleted by RFC 1903) ** Obsolete normative reference: RFC 1444 (ref. '4') (Obsoleted by RFC 1904) -- Possible downref: Non-RFC (?) normative reference: ref. '6' Summary: 12 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft IEEE 802.12 Repeater MIB December 18 1995 4 Definitions of Managed Objects for IEEE 802.12 Repeater Devices 6 December 18, 1995 8 John Flick 10 Hewlett Packard Company 11 8000 Foothills Blvd. M/S 5556 12 Roseville, CA 95747-5556 14 johnf@hprnd.rose.hp.com 16 18 Status of this Memo 20 This document is an Internet-Draft. Internet-Drafts are working 21 documents of the Internet Engineering Task Force (IETF), its areas, 22 and its working groups. Note that other groups may also distribute 23 working documents as Internet-Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as ``work in progress.'' 30 To learn the current status of any Internet-Draft, please check the 31 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 32 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 33 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 34 ftp.isi.edu (US West Coast). 36 1. Abstract 38 This memo defines an experimental portion of the Management 39 Information Base (MIB) for use with network management protocols in 40 TCP/IP-based internets. In particular, it defines objects for 41 managing network repeaters based on IEEE 802.12. 43 2. Object Definitions 45 Management information is viewed as a collection of managed objects, 46 residing in a virtual information store, termed the Management 47 Information Base (MIB). Collections of related objects are defined 48 in MIB modules. MIB modules are written using a subset of Abstract 49 Syntax Notation One (ASN.1) [1] termed the Structure of Management 50 Information (SMI) [2]. In particular, each object type is named by 51 an OBJECT IDENTIFIER, an administratively assigned name. The object 52 type together with an object instance serves to uniquely identify a 53 specific instantiation of the object. For human convenience, we 54 often use a textual string, termed the descriptor, to refer to the 55 object type. 57 3. Overview 59 Instances of these object types represent attributes of an IEEE 60 802.12 repeater, as defined by Section 12, "RMAC Protocol" in IEEE 61 Standard 802.12-1995 [6]. 63 The definitions presented here are based on Section 13, "Layer 64 management functions and services", and Annex C, "GDMO Specifications 65 for Demand Priority Managed Objects" of IEEE Standard 802.12-1995 66 [6]. Implementors of these MIB objects should note that the IEEE 67 document explicitly describes (in the form of Pascal pseudocode) 68 when, where, and how various repeater attributes are measured. The 69 IEEE document also describes the effects of repeater actions that may 70 be invoked by manipulating instances of the MIB objects defined here. 72 The counters in this document are defined to be the same as those 73 counters in IEEE Standard 802.12-1995, with the intention that the 74 same instrumentation can be used to implement both the IEEE and IETF 75 management standards. 77 3.1. MAC Addresses 79 All representations of MAC addresses in this MIB module are in 80 "canonical" order defined by 802.1a, i.e., as if it were transmitted 81 least significant bit first. This is true even if the repeater is 82 operating in token ring framing mode, which requires MAC addresses to 83 be transmitted most significant bit first. 85 3.2. IEEE 802.12 Training Frames 87 Training frames are special MAC frames that are used only during link 88 initialization. Training frames are initially constructed by the 89 device at the lower end of a link. The training frame format is as 90 follows: 92 +----+----+------------+--------------+----------+-----+ 93 | DA | SA | Req Config | Allow Config | Data | FCS | 94 +----+----+------------+--------------+----------+-----+ 96 DA = destination address (six octets) 97 SA = source address (six octets) 98 Req Config = requested configuration (2 octets) 99 Allow Config = allowed configuration (2 octets) 100 Data = data (594 to 675 octets) 101 FCS = frame check sequence (4 octets) 103 Training frames are always sent with a null destination address. To 104 pass training, an end node must use its source address in the source 105 address field of the training frame. A repeater may use a non-null 106 source address if it has one, or it may use a null source address. 108 The requested configuration field allows the device at the lower end 109 of a link to inform the device at the upper end of the link about 110 itself and to request configuration options. The training response 111 frame from the device at the upper end of the link contains the 112 requestor's requested configuration from the training request frame. 113 The currently defined format of the requested configuration field as 114 defined in the IEEE Standard 802.12-1995 standard is shown below. 115 Please refer to the most current version of the IEEE document for a 116 more up to date description of this field. In particular, the 117 reserved bits may be used in later versions of the standard. 119 First Octet: Second Octet: 121 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 122 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 123 |v|v|v|r|r|r|r|r| |r|r|r|F|F|P|P|R| 124 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 126 vvv: The version of the 802.12 training protocol with which 127 the training initiator is compliant. The current version 128 is 100. 129 r: Reserved bits (set to zero) 130 FF: 00 = frameType88023 131 01 = frameType88025 132 10 = reserved 133 11 = frameTypeEither 134 PP: 00 = singleAddressMode 135 01 = promiscuousMode 136 10 = reserved 137 11 = reserved 138 R: 0 = the training initiator is an end node 139 1 = the training initiator is a repeater 141 The allowed configuration field allows the training responder to 142 respond with the allowed configuration. The training initiator sets 143 the contents of this field to all zero bits. The training responder 144 sets the allowed configuration field as follows: 146 First Octet: Second Octet: 148 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 149 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 150 |v|v|v|D|C|N|r|r| |r|r|r|F|F|P|P|R| 151 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 153 vvv: The version of the 802.12 training protocol with which 154 the training responder is compliant. The current version 155 is 100. 156 D: 0 = No duplicate address has been detected. 157 1 = Duplicate address has been detected 158 C: 0 = The requested configuration is compatible with the 159 network. 160 1 = The requested configuration is not compatible with 161 the network. In this case, the FF, PP, and R bits 162 indicate the configuration that would be allowed. 163 N: 0 = Access will be allowed, providing the configuration 164 is compatible (C = 0). 165 1 = Access is not granted because of security 166 restrictions 167 r: Reserved bits (set to zero) 168 FF: 00 = frameType88023 will be used 169 01 = frameType88025 will be used 170 10 = reserved 171 11 = reserved 172 PP: 00 = singleAddressMode 173 01 = promiscuousMode 174 10 = reserved 175 11 = reserved 176 R: 0 = Requested access as an end node is allowed 177 1 = Requested access as a repeater is allowed 179 Again, note that the most recent version of the IEEE 802.12 standard 180 should be consulted for the most up to date definition of the 181 requested configuration and allowed configuration fields. 183 The data field contains between 594 and 675 octets and is filled in 184 by the training initiator. The first 55 octets may be used for 185 vendor specific protocol information. The remaining octets are all 186 zeros. The length of the training frame combined with the 187 requirement that 24 consecutive training frames be received without 188 error to complete training ensures that marginal links will not 189 complete training. 191 3.3. Structure of the MIB 193 Objects in this MIB are arranged into MIB groups. Each MIB group is 194 organized as a set of related objects. 196 3.3.1. The Basic Group Definitions 198 This group contains the objects which are applicable to all 199 repeaters. It contains status, parameter and control objects for 200 each repeater within the managed system, for the port groups within 201 the system, and for the individual ports themselves. 203 3.3.2. The Monitor Group Definitions 205 This group contains monitoring statistics for each repeater within 206 the system and for individual ports. 208 3.3.3. The Address Tracking Group Definitions 210 This group contains objects for tracking the MAC addresses of the 211 DTEs attached to the ports within the system. 213 3.4. Relationship to other MIBs 215 It is assumed that a repeater implementing this MIB will also 216 implement (at least) the 'system' group defined in MIB-II [5]. 218 3.4.1. Relationship to the 'system' group 220 In MIB-II, the 'system' group is defined as being mandatory for all 221 systems such that each managed entity contains one instance of each 222 object in the 'system' group. Thus, those objects apply to the 223 entity even if the entity's sole functionality is management of 224 repeaters. 226 3.4.2. Relationship to the 'interfaces' group 228 In MIB-II, the 'interfaces' group is defined as being mandatory for 229 all systems and contains information on an entity's interfaces, where 230 each interface is thought of as being attached to a the Internet 231 suite of protocols.) 232 This MIB uses the notion of ports on a repeater. The concept of a 233 MIB-II interface has NO specific relationship to a repeater's port. 234 Therefore, the 'interfaces' group applies only to the one (or more) 235 network interfaces on which the entity managing the repeater sends 236 and receives management protocol operations, and does not apply to 237 the repeater's ports. 239 3.5. Mapping of IEEE 802.12 Managed Objects 241 IEEE 802.12 Managed Object Corresponding SNMP Object 243 oRepeater 244 .aCurrentFramingType vgRptrInfoCurrentFramingType 245 .aDesiredFramingType vgRptrInfoDesiredFramingType 246 .aFramingCapability vgRptrInfoFramingCapability 247 .aGroupMap 248 .aMACAddress vgRptrInfoMACAddress 249 .aRepeaterGroupCapacity 250 .aRepeaterHealthData 251 .aRepeaterHealthState vgRptrInfoOperStatus 252 .aRepeaterHealthText 253 .aRepeaterID vgRptrInfoIndex 254 .aRepeaterSearchAddress vgRptrAddrSearchAddress 255 .aRepeaterSearchGroup vgRptrAddrSearchGroup 256 .aRepeaterSearchPort vgRptrAddrSearchPort 257 .aRepeaterSearchState vgRptrAddrSearchState 258 .aRMACVersion vgRptrInfoTrainingVersion 259 .acExecuteNonDisruptiveSelfTest 260 .acRepeaterSearchAddress vgRptrAddrSearchAddress 261 .acResetRepeater vgRptrInfoReset 262 .nGroupMapChange vgRptrGroupChange 263 .nRepeaterHealth vgRptrHealth 264 .nRepeaterReset vgRptrResetEvent 266 oGroup 267 .aGroupCablesBundled vgRptrGroupCablesBundled 268 .aGroupID vgRptrGroupIndex 269 .aGroupPortCapacity vgRptrGroupPortCapacity 270 .aPortMap 271 .nPortMapChange 273 oPort 274 .aAllowableTrainingType vgRptrPortAllowedTrainType 275 .aBroadcastFramesReceived vgRptrPortBroadcastFrames 276 .aCentralMgmtDetectedDupAddr vgRptrMgrDetectedDupAddress 277 .aDataErrorFramesReceived vgRptrPortDataErrorFrames 278 .aHighPriorityFramesReceived vgRptrPortHighPriorityFrames 279 .aHighPriorityOctetsReceived vgRptrPortHighPriorityOctets or 280 vgRptrPortHCHighPriorityOctets 281 .aIPMFramesReceived vgRptrPortIPMFrames 282 .aLastTrainedAddress vgRptrAddrLastTrainedAddress 283 .aLastTrainingConfig vgRptrPortLastTrainConfig 284 .aLocalRptrDetectedDupAddr vgRptrRptrDetectedDupAddress 285 .aMediaType 286 Tranceiver MIB issue 287 .aMulticastFramesReceived vgRptrPortMulticastFrames 288 .aNormalPriorityFramesReceived vgRptrPortNormPriorityFrames 289 .aNormalPriorityOctetsReceived vgRptrPortNormPriorityOctets or 290 vgRptrPortHCNormPriorityOctets 291 .aNullAddressedFramesReceived vgRptrPortNullAddressedFrames 292 .aOctetsInUnreadableFramesRcvd vgRptrPortUnreadableOctets or 293 vgRptrPortHCUnreadableOctets 294 .aOversizeFramesReceived vgRptrPortOversizeFrames 295 .aPortAdministrativeState vgRptrPortAdminStatus 296 .aPortID vgRptrPortIndex 297 .aPortStatus vgRptrPortStatus 298 .aPortType vgRptrPortType 299 .aPriorityEnable vgRptrPortPriorityEnable 300 .aPriorityPromotions vgRptrPortPriorityPromotions 301 .aReadableFramesReceived vgRptrPortReadableFrames 302 .aReadableOctetsReceived vgRptrPortReadableOctets or 303 vgRptrPortHCReadableOctets 304 .aSupportedCascadeMode vgRptrPortSupportedCascadeMode 305 .aSupportedPromiscMode vgRptrPortSupportedPromiscMode 306 .aTrainedAddressChanges vgRptrAddrTrainedAddressChanges 307 .aTrainingResult vgRptrPortTrainingResult 308 .aTransitionsIntoTraining vgRptrPortTransitionToTrainings 309 .acPortAdministrativeControl vgRptrPortAdminStatus 311 4. Definitions 313 DOT12-RPTR-MIB DEFINITIONS ::= BEGIN 315 IMPORTS 316 experimental, Integer32, Counter32, Counter64, 317 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE 318 FROM SNMPv2-SMI 319 DisplayString, MacAddress, TruthValue, TimeStamp, 320 TestAndIncr 321 FROM SNMPv2-TC 322 MODULE-COMPLIANCE, OBJECT-GROUP 323 FROM SNMPv2-CONF 324 OwnerString 325 FROM IF-MIB; 327 vgRptrMIB MODULE-IDENTITY 328 LAST-UPDATED "9512152252Z" 329 ORGANIZATION "IETF 100VG-AnyLAN Working Group" 330 CONTACT-INFO 331 " John Flick 333 Postal: Hewlett Packard Company 334 8000 Foothills Blvd. M/S 5556 335 Roseville, CA 95747-5556 336 Tel: +1 916 785 4018 337 Fax: +1 916 785 3583 339 E-mail: johnf@hprnd.rose.hp.com" 340 DESCRIPTION 341 "This MIB module describes objects for managing 342 IEEE 802.12 repeaters." 343 ::= { experimental 64 } 345 vgRptrObjects OBJECT IDENTIFIER ::= { vgRptrMIB 1 } 347 vgRptrBasic OBJECT IDENTIFIER ::= { vgRptrObjects 1 } 348 vgRptrBasicRptr OBJECT IDENTIFIER ::= { vgRptrBasic 1 } 350 -- Note: { vgRptrBasicRptr 1 } to { vgRptrBasicRptr 10 } 351 -- were used in an earlier version of this draft for 352 -- repeater-wide scalar objects. With the change in the 353 -- model to allow multiple repeaters, they have been moved 354 -- into the following table. This table should be moved 355 -- to { vgRptrBasicRptr 1 } when this draft is published 356 -- as an RFC. 358 vgRptrInfoTable OBJECT-TYPE 359 SYNTAX SEQUENCE OF VgRptrInfoEntry 360 MAX-ACCESS not-accessible 361 STATUS current 362 DESCRIPTION 363 "A table of information about each non-trivial 364 802.12 repeater in the managed system." 365 ::= { vgRptrBasicRptr 11 } 367 vgRptrInfoEntry OBJECT-TYPE 368 SYNTAX VgRptrInfoEntry 369 MAX-ACCESS not-accessible 370 STATUS current 371 DESCRIPTION 372 "An entry in the table, containing information 373 about a single, non-trivial repeater." 374 INDEX { vgRptrInfoIndex } 375 ::= { vgRptrInfoTable 1 } 377 VgRptrInfoEntry ::= 378 SEQUENCE { 379 vgRptrInfoIndex Integer32, 380 vgRptrInfoMACAddress MacAddress, 381 vgRptrInfoCurrentFramingType INTEGER, 382 vgRptrInfoDesiredFramingType INTEGER, 383 vgRptrInfoFramingCapability INTEGER, 384 vgRptrInfoTrainingVersion INTEGER, 385 vgRptrInfoOperStatus INTEGER, 386 vgRptrInfoReset INTEGER, 387 vgRptrInfoLastChange TimeStamp 388 } 390 vgRptrInfoIndex OBJECT-TYPE 391 SYNTAX Integer32 (1..2147483647) 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "A unique identifier for the repeater for which 396 this entry contains information. The numbering 397 scheme for repeaters is implementation specific." 398 REFERENCE 399 "IEEE Standard 802.12-1995, 13.2.4.2.1, 400 aRepeaterID." 401 ::= { vgRptrInfoEntry 1 } 403 vgRptrInfoMACAddress OBJECT-TYPE 404 SYNTAX MacAddress 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "The MAC address used by the repeater when it 409 initiates training on the uplink port. Repeaters 410 are allowed to train with an assigned MAC address 411 or a null (all zeroes) MAC address." 412 REFERENCE 413 "IEEE Standard 802.12-1995, 13.2.4.2.1, 414 aMACAddress." 415 ::= { vgRptrInfoEntry 2 } 417 vgRptrInfoCurrentFramingType OBJECT-TYPE 418 SYNTAX INTEGER { 419 frameType88023(1), 420 frameType88025(2) 421 } 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "The type of framing (802.3 or 802.5) currently 426 in use by the repeater." 427 REFERENCE 428 "IEEE Standard 802.12-1995, 13.2.4.2.1, 429 aCurrentFramingType." 430 ::= { vgRptrInfoEntry 3 } 432 vgRptrInfoDesiredFramingType OBJECT-TYPE 433 SYNTAX INTEGER { 434 frameType88023(1), 435 frameType88025(2) 436 } 437 MAX-ACCESS read-write 438 STATUS current 439 DESCRIPTION 440 "The type of framing which will be used by the 441 repeater after the next time it is reset. The 442 value of this object should be preserved across 443 repeater resets and power failures" 444 REFERENCE 445 "IEEE Standard 802.12-1995, 13.2.4.2.1, 446 aDesiredFramingType." 447 ::= { vgRptrInfoEntry 4 } 449 vgRptrInfoFramingCapability OBJECT-TYPE 450 SYNTAX INTEGER { 451 frameType88023(1), 452 frameType88025(2), 453 frameTypeEither(3) 455 } 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION 459 "The type of framing this repeater is capable of 460 supporting." 461 REFERENCE 462 "IEEE Standard 802.12-1995, 13.2.4.2.1, 463 aFramingCapability." 464 ::= { vgRptrInfoEntry 5 } 466 vgRptrInfoTrainingVersion OBJECT-TYPE 467 SYNTAX INTEGER (0..7) 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The highest version bits (vvv bits) supported by 472 the repeater during training." 473 REFERENCE 474 "IEEE Standard 802.12-1995, 13.2.4.2.1, 475 aRMACVersion." 476 ::= { vgRptrInfoEntry 6 } 478 vgRptrInfoOperStatus OBJECT-TYPE 479 SYNTAX INTEGER { 480 ok(2), 481 generalFailure(6) 482 } 483 MAX-ACCESS read-only 484 STATUS current 485 DESCRIPTION 486 "The vgRptrInfoOperStatus object indicates the 487 operational state of the repeater." 488 REFERENCE 489 "IEEE Standard 802.12-1995, 13.2.4.2.1, 490 aRepeaterHealthState." 491 ::= { vgRptrInfoEntry 7 } 493 vgRptrInfoReset OBJECT-TYPE 494 SYNTAX INTEGER { 495 noReset(1), 496 reset(2) 497 } 498 MAX-ACCESS read-write 499 STATUS current 500 DESCRIPTION 501 "Setting this object to reset(2) causes the 502 repeater to transition to its initial state as 503 specified in clause 12 [IEEE Std 802.12]. 505 Setting this object to noReset(1) has no effect. 506 The agent will always return the value noReset(1) 507 when this object is read. 509 After receiving a request to set this variable to 510 reset(2), the agent is allowed to delay the reset 511 for a short period. For example, the implementor 512 may choose to delay the reset long enough to 513 allow the SNMP response to be transmitted. In 514 any event, the SNMP response must be transmitted. 516 This action does not reset the management 517 counters defined in this document nor does it 518 affect the vgRptrPortAdminStatus parameters. 519 Included in this action is the execution of a 520 disruptive Self-Test with the following 521 characteristics: 523 1) The nature of the tests is not specified. 524 2) The test resets the repeater but without 525 affecting configurable management 526 information about the repeater. 527 3) Packets received during the test may or 528 may not be transferred. 529 4) The test does not interfere with 530 management functions. 532 After performing this self-test, the agent will 533 update the repeater health information (including 534 vgRptrInfoOperStatus), and send a 535 vgRptrResetEvent." 536 REFERENCE 537 "IEEE Standard 802.12-1995, 13.2.4.2.2, 538 acResetRepeater." 539 ::= { vgRptrInfoEntry 8 } 541 vgRptrInfoLastChange OBJECT-TYPE 542 SYNTAX TimeStamp 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "The value of sysUpTime when any of the following 547 conditions occurred: 549 1) agent cold- or warm-started; 550 2) this instance of repeater was created 551 (such as when a device or module was 552 added to the system); 553 3) a change in the value of 554 vgRptrInfoOperStatus; 555 4) ports were added or removed as members of 556 the repeater; or 557 5) any of the counters associated with this 558 repeater had a discontinuity." 559 ::= { vgRptrInfoEntry 9 } 561 vgRptrBasicGroup OBJECT IDENTIFIER ::= { vgRptrBasic 2 } 563 vgRptrBasicGroupTable OBJECT-TYPE 564 SYNTAX SEQUENCE OF VgRptrBasicGroupEntry 565 MAX-ACCESS not-accessible 566 STATUS current 567 DESCRIPTION 568 "A table containing information about groups of 569 ports." 570 ::= { vgRptrBasicGroup 1 } 572 vgRptrBasicGroupEntry OBJECT-TYPE 573 SYNTAX VgRptrBasicGroupEntry 574 MAX-ACCESS not-accessible 575 STATUS current 576 DESCRIPTION 577 "An entry in the vgRptrBasicGroupTable, containing 578 information about a single group of ports." 579 INDEX { vgRptrGroupIndex } 580 ::= { vgRptrBasicGroupTable 1 } 582 VgRptrBasicGroupEntry ::= 583 SEQUENCE { 584 vgRptrGroupIndex Integer32, 585 vgRptrGroupDescr DisplayString, 586 vgRptrGroupObjectID OBJECT IDENTIFIER, 587 vgRptrGroupOperStatus INTEGER, 588 vgRptrGroupLastOperStatusChange TimeStamp, 589 vgRptrGroupPortCapacity Integer32, 590 vgRptrGroupCablesBundled INTEGER 591 } 593 vgRptrGroupIndex OBJECT-TYPE 594 SYNTAX Integer32 (1..2146483647) 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "This object identifies the group within the 599 system for which this entry contains information. 600 The numbering scheme for groups is implementation 601 specific." 602 REFERENCE 603 "IEEE Standard 802.12-1995, 13.2.4.4.1, 604 aGroupID." 605 ::= { vgRptrBasicGroupEntry 1 } 607 vgRptrGroupDescr OBJECT-TYPE 608 SYNTAX DisplayString (SIZE (0..255)) 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "A textual description of the group. This value 613 should include the full name and version 614 identification of the group's hardware type and 615 indicate how the group is differentiated from 616 other types of groups in the system. 'Plug-in 617 Module, Rev A' or 'Barney Rubble 100BaseVG 4-port 618 socket Version 2.1' are examples of valid group 619 descriptions. 621 It is mandatory that this only contain printable 622 ASCII characters." 623 ::= { vgRptrBasicGroupEntry 2 } 625 vgRptrGroupObjectID OBJECT-TYPE 626 SYNTAX OBJECT IDENTIFIER 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "The vendor's authoritative identification of the 631 group. This value may be allocated within the 632 SMI enterprises subtree (1.3.6.1.4.1) and 633 provides a straight-forward and unambiguous means 634 for determining what kind of group is being 635 managed. 637 For example, this object could take the value 638 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, 639 Inc.' was assigned the subtree 1.3.6.1.4.1.4242, 640 and had assigned the identifier 641 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 642 6-Port Plug-in Module.'" 643 ::= { vgRptrBasicGroupEntry 3 } 645 vgRptrGroupOperStatus OBJECT-TYPE 646 SYNTAX INTEGER { 647 other(1), 648 operational(2), 649 malfunctioning(3), 650 notPresent(4), 651 underTest(5), 652 resetInProgress(6) 653 } 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "An object that indicates the operational status 658 of the group. 660 A status of notPresent(4) indicates that the 661 group is temporarily or permanently physically 662 and/or logically not a part of the system. It 663 is an implementation-specific matter as to 664 whether the agent effectively removes notPresent 665 entries from the table. 667 A status of operational(2) indicates that the 668 group is functioning, and a status of 669 malfunctioning(3) indicates that the group is 670 malfunctioning in some way." 671 ::= { vgRptrBasicGroupEntry 4 } 673 vgRptrGroupLastOperStatusChange OBJECT-TYPE 674 SYNTAX TimeStamp 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "An object that contains the value of sysUpTime 679 at the time that the value of the 680 vgRptrGroupOperStatus object for this group last 681 changed. 683 A value of zero indicates that the group's 684 operational status has not changed since the 685 agent last restarted." 686 ::= { vgRptrBasicGroupEntry 5 } 688 vgRptrGroupPortCapacity OBJECT-TYPE 689 SYNTAX Integer32 (1..2146483647) 690 MAX-ACCESS read-only 691 STATUS current 692 DESCRIPTION 693 "The vgRptrGroupPortCapacity is the number of 694 ports that can be contained within the group. 696 Valid range is 1-2147483647. Within each group, 697 the ports are uniquely numbered in the range from 698 1 to vgRptrGroupPortCapacity. 700 Some ports may not be present in the system, in 701 which case the actual number of ports present will 702 be less than the value of vgRptrGroupPortCapacity. 703 The number of ports present is never greater than 704 the value of vgRptrGroupPortCapacity. 706 Note: In practice, this will generally be the 707 number of ports on a module, card, or board, and 708 the port numbers will correspond to numbers marked 709 on the physical embodiment." 710 REFERENCE 711 "IEEE Standard 802.12-1995, 13.2.4.4.1, 712 aGroupPortCapacity." 713 ::= { vgRptrBasicGroupEntry 6 } 715 vgRptrGroupCablesBundled OBJECT-TYPE 716 SYNTAX INTEGER { 717 someCablesBundled(1), 718 noCablesBundled(2) 719 } 720 MAX-ACCESS read-write 721 STATUS current 722 DESCRIPTION 723 "This configuration flag is used to select either 724 bundled or unbundled cabling. When this flag is 725 'someCablesBundled(1)' and the port is not 726 promiscuous or cascaded, frames received from 727 ports on this group and destined to go out 728 multiple ports on this group will be buffered 729 completely before being repeated out ports on 730 this group. When this flag is 731 'noCablesBundled(2)' or the port is promiscuous 732 or cascaded, these frames will be repeated out 733 ports on this group as the frame is being 734 received. 736 Note that the value 'someCablesBundled(1)' will 737 work in the vast majority of all installations, 738 regardless of whether or not any cables are 739 physically in a bundle, since promiscuous and 740 cascaded ports automatically avoid the store and 741 forward. The main situation in which 742 'noCablesBundled(2)' is beneficial is when there 743 is a large amount of multicast traffic and the 744 cables are not in a bundle. The value of this 745 object should be preserved across repeater resets 746 and power failures." 747 REFERENCE 748 "IEEE Standard 802.12-1995, 13.2.4.4.1, 749 aGroupCablesBundled." 750 ::= { vgRptrBasicGroupEntry 7 } 752 vgRptrBasicPort OBJECT IDENTIFIER ::= { vgRptrBasic 3 } 754 vgRptrBasicPortTable OBJECT-TYPE 755 SYNTAX SEQUENCE OF VgRptrBasicPortEntry 756 MAX-ACCESS not-accessible 757 STATUS current 758 DESCRIPTION 759 "A table containing configuration and status 760 information about 802.12 repeater ports in the 761 system. The number of entries is independent of 762 the number of repeaters in the managed system." 763 ::= { vgRptrBasicPort 1 } 765 vgRptrBasicPortEntry OBJECT-TYPE 766 SYNTAX VgRptrBasicPortEntry 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION 770 "An entry in the vgRptrBasicPortTable, containing 771 information about a single port." 772 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 773 ::= { vgRptrBasicPortTable 1 } 775 VgRptrBasicPortEntry ::= 776 SEQUENCE { 777 vgRptrPortIndex Integer32, 778 vgRptrPortType INTEGER, 779 vgRptrPortAdminStatus INTEGER, 780 vgRptrPortOperStatus INTEGER, 781 vgRptrPortSupportedPromiscMode INTEGER, 782 vgRptrPortSupportedCascadeMode INTEGER, 783 vgRptrPortAllowedTrainType INTEGER, 784 vgRptrPortLastTrainConfig OCTET STRING, 785 vgRptrPortTrainingResult OCTET STRING, 786 vgRptrPortPriorityEnable TruthValue, 787 vgRptrPortRptrInfoIndex Integer32 788 } 790 vgRptrPortIndex OBJECT-TYPE 791 SYNTAX Integer32 (1..2147483647) 792 MAX-ACCESS not-accessible 793 STATUS current 794 DESCRIPTION 795 "This object identifies the port within the group 796 for which this entry contains information. This 797 identifies the port independently from the 798 repeater it may be attached to. The numbering 799 scheme for ports is implementation specific; 800 however, this value can never be greater than 801 vgRptrGroupPortCapacity for the associated group." 802 REFERENCE 803 "IEEE Standard 802.12-1995, 13.2.4.5.1, 804 aPortID." 805 ::= { vgRptrBasicPortEntry 1 } 807 vgRptrPortType OBJECT-TYPE 808 SYNTAX INTEGER { 809 cascadeExternal(1), 810 cascadeInternal(2), 811 localExternal(3), 812 localInternal(4) 813 } 814 MAX-ACCESS read-only 815 STATUS current 816 DESCRIPTION 817 "Describes the type of port. One of the 818 following: 820 cascadeExternal - Port is an uplink with 821 physical connections which 822 are externally visible 823 cascadeInternal - Port is an uplink with 824 physical connections which 825 are not externally visible, 826 such as a connection to an 827 internal backplane in a 828 chassis 829 localExternal - Port is a downlink or local 830 port with externally 831 visible connections 832 localInternal - Port is a downlink or local 833 port with connections which 834 are not externally visible, 835 such as a connection to an 836 internal agent 838 'internal' is used to identify ports which place 839 traffic into the repeater, but do not have any 840 external connections. Note that both DTE and 841 cascaded repeater downlinks are considered 842 'local' ports." 843 REFERENCE 844 "IEEE Standard 802.12-1995, 13.2.4.5.1, 845 aPortType." 846 ::= { vgRptrBasicPortEntry 2 } 848 vgRptrPortAdminStatus OBJECT-TYPE 849 SYNTAX INTEGER { 850 enabled(1), 851 disabled(2) 852 } 853 MAX-ACCESS read-write 854 STATUS current 855 DESCRIPTION 856 "Port enable/disable function. Enabling a 857 disabled port will cause training to be 858 initiated. Setting this object to disabled(2) 859 disables the port. 861 A disabled port neither transmits nor receives. 862 Once disabled, a port must be explicitly enabled 863 to restore operation. A port which is disabled 864 when power is lost or when a reset is exerted 865 shall remain disabled when normal operation 866 resumes." 867 REFERENCE 868 "IEEE Standard 802.12-1995, 13.2.4.5.1, 869 aPortAdministrativeState." 870 ::= { vgRptrBasicPortEntry 3 } 872 vgRptrPortOperStatus OBJECT-TYPE 873 SYNTAX INTEGER { 874 active(1), 875 inactive(2), 876 training(3) 877 } 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "Current status for the port as specified by the 882 PORT_META_STATE in the port process module of 883 clause 12 [IEEE Std 802.12]. 885 During initialization or any link warning 886 conditions, vgRptrPortStatus will be 887 'inactive(2)'. 889 When Training_Up is received by the repeater on a 890 local port (or when Training_Down is received on 891 a cascade port), vgRptrPortStatus will change to 892 'training(3)' and vgRptrTrainingResult can be 893 monitored to see the detailed status regarding 894 training. 896 When 24 consecutive good FCS packets are received 897 and the configuration bits are OK, 898 vgRptrPortStatus will change to 'active(1)'. 900 A disabled port shall have a port status of 901 'inactive(2)'." 902 REFERENCE 903 "IEEE Standard 802.12, 13.2.4.5.1, 904 aPortStatus." 905 ::= { vgRptrBasicPortEntry 4 } 907 vgRptrPortSupportedPromiscMode OBJECT-TYPE 908 SYNTAX INTEGER { 909 singleModeOnly(1), 910 singleOrPromiscMode(2), 911 promiscModeOnly(3) 912 } 913 MAX-ACCESS read-only 914 STATUS current 915 DESCRIPTION 916 "This object describes whether the port hardware 917 is capable of supporting promiscuous mode, single 918 address mode (i.e., repeater filters unicasts not 919 addressed to the end station attached to this 920 port), or both. A port for which vgRptrPortType 921 is equal to 'cascadeInternal' or 'cascadeExternal' 922 will always have a value of 'promiscModeOnly' for 923 this object." 924 REFERENCE 925 "IEEE Standard 802.12-1995, 13.2.4.5.1, 926 aSupportedPromiscMode." 927 ::= { vgRptrBasicPortEntry 5 } 929 vgRptrPortSupportedCascadeMode OBJECT-TYPE 930 SYNTAX INTEGER { 931 endNodesOnly(1), 932 endNodesOrRepeaters(2), 933 cascadePort(3) 934 } 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "This object describes whether the port hardware 939 is capable of supporting cascaded repeaters, end 940 nodes, or both. A port for which vgRptrPortType 941 is equal to 'cascadeInternal' or 942 'cascadeExternal' will always have a value of 943 'cascadePort' for this object." 944 REFERENCE 945 "IEEE Standard 802.12-1995, 13.2.4.5.1, 946 aSupportedCascadeMode." 947 ::= { vgRptrBasicPortEntry 6 } 949 vgRptrPortAllowedTrainType OBJECT-TYPE 950 SYNTAX INTEGER { 951 allowEndNodesOnly(1), 952 allowPromiscuousEndNodes(2), 953 allowEndNodesOrRepeaters(3), 954 allowAnything(4) 955 } 956 MAX-ACCESS read-write 957 STATUS current 958 DESCRIPTION 959 "This security object is set by the network 960 manager to configure what type of device is 961 permitted to connect to the port. One of the 962 following values: 964 allowEndNodesOnly - only non- 965 promiscuous end 966 nodes permitted. 967 allowPromiscuousEndNodes - promiscuous or 968 non-promiscuous 969 end nodes 970 permitted 971 allowEndNodesOrRepeaters - repeaters or non- 972 promiscuous end 973 nodes permitted 974 allowAnything - repeaters, 975 promiscuous or 976 non-promiscuous 977 end nodes 978 permitted 980 For a port for which vgRptrPortType is equal to 981 'cascadeInternal' or 'cascadeExternal', the 982 corresponding instance of this object may not be 983 set to 'allowEndNodesOnly' or 984 'allowPromiscuousEndNodes'. 986 The agent must reject a SET of this object if the 987 value includes no capabilities that are 988 supported by this port's hardware, as defined by 989 the values of the corresponding instances of 990 vgRptrPortSupportedPromiscMode and 991 vgRptrPortSupportedCascadeMode. 993 Note that vgRptrPortSupportPromiscMode and 994 vgRptrPortSupportedCascadeMode represent what the 995 port hardware is capable of supporting. 996 vgRptrPortAllowedTrainType is used for setting an 997 administrative policy for a port. The actual set 998 of training configurations that will be allowed 999 to succeed on a port is the intersection of what 1000 the hardware will support and what is 1001 administratively allowed. The above requirement 1002 on what values may be set to this object says that 1003 the intersection of what is supported and what is 1004 allowed must be non-empty. In other words, it 1005 must not result in a situation in which nothing 1006 would be allowed to train on that port. However, 1007 a value can be set to this object as long as the 1008 combination of this object and what is supported 1009 by the hardware would still leave at least one 1010 configuration that could successfully train on the 1011 port." 1012 REFERENCE 1013 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1014 aAllowableTrainingType." 1015 ::= { vgRptrBasicPortEntry 7 } 1017 vgRptrPortLastTrainConfig OBJECT-TYPE 1018 SYNTAX OCTET STRING (SIZE(2)) 1019 MAX-ACCESS read-only 1020 STATUS current 1021 DESCRIPTION 1022 "This 16 bit field contains the requested 1023 configuration field from the most recent 1024 error-free training request frame sent by the end 1025 node connected to the port. For cascade ports, 1026 this object contains the responder's allowed 1027 configuration field from the most recent 1028 error-free training response frame received in 1029 response to training initiated by this repeater. 1030 The format of the current version of this field is 1031 described in section 3.2. Please refer to the 1032 most recent version of the IEEE 802.12 standard 1033 for the most up-to-date definition of the format 1034 of this object." 1035 REFERENCE 1036 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1037 aLastTrainingConfig." 1038 ::= { vgRptrBasicPortEntry 8 } 1040 vgRptrPortTrainingResult OBJECT-TYPE 1041 SYNTAX OCTET STRING (SIZE(3)) 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "This 18 bit field is used to indicate the result 1046 of training. It contains two bits which indicate 1047 if error-free training frames have been received, 1048 and it also contains the 16 bits of the allowed 1049 configuration field from the most recent 1050 error-free training response frame on the port. 1052 First Octet: Second and Third Octets: 1053 7 6 5 4 3 2 1 0 1054 +-+-+-+-+-+-+-+-+-----------------------------+ 1055 |0|0|0|0|0|0|V|G| allowed configuration field | 1056 +-+-+-+-+-+-+-+-+-----------------------------+ 1058 V: Valid: set when at least one error-free 1059 training frame has been received. 1060 Indicates the 16 training configuration 1061 bits in vgRptrPortLastTrainConfig and 1062 vgRptrPortTrainingResult contain valid 1063 information. This bit is cleared when 1064 vgRptrPortStatus transitions to the 1065 'inactive' or 'training' state. 1066 G: LinkGood: indicates the link hardware is 1067 OK. Set if 24 consecutive error-free 1068 training packets have been received. 1069 Cleared when a training packet with 1070 errors is received, or when 1071 vgRptrPortStatus transitions to the 1072 'inactive' or 'training' state. 1074 The format of the current version of the allowed 1075 configuration field is described in section 3.2. 1076 Please refer to the most recent version of the 1077 IEEE 802.12 standard for the most up-to-date 1078 definition of the format of this field. 1080 If the port is in training, a management station 1081 can examine this object to see if any training 1082 packets have been passed successfully. If there 1083 have been any good training packets, the Valid 1084 bit will be set and the management station can 1085 examine the allowed configuration field to see if 1086 there is a duplicate address, configuration, or 1087 security problem. 1089 Note that on a repeater local port, this repeater 1090 generates the training response bits, while on 1091 a cascade port, the higher level repeater 1092 originated the training response bits." 1093 REFERENCE 1094 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1095 aTrainingResult." 1096 ::= { vgRptrBasicPortEntry 9 } 1098 vgRptrPortPriorityEnable OBJECT-TYPE 1099 SYNTAX TruthValue 1100 MAX-ACCESS read-write 1101 STATUS current 1102 DESCRIPTION 1103 "A configuration flag used to determine whether 1104 the repeater will service high priority requests 1105 received on the port as high priority or normal 1106 priority. When 'false', high priority requests 1107 on this port will be serviced as normal priority. 1108 The value of this object should be preserved 1109 across repeater resets and power failures. 1111 The setting of this object has no effect on a 1112 cascade port. Also note that the setting of this 1113 object has no effect on a port connected to a 1114 cascaded repeater. In both of these cases, this 1115 setting is treated as always 'true'. The value 1116 'false' only has an effect when the port is a 1117 localInternal or localExternal port connected to 1118 an end node." 1119 REFERENCE 1120 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1121 aPriorityEnable." 1122 ::= { vgRptrBasicPortEntry 10 } 1124 vgRptrPortRptrInfoIndex OBJECT-TYPE 1125 SYNTAX Integer32 (0..2147483647) 1126 MAX-ACCESS read-only 1127 STATUS current 1128 DESCRIPTION 1129 "This object identifies the repeater that this 1130 port is currently mapped to. The repeater 1131 identified by a particular value of this object 1132 is the same as that identified by the same value 1133 of vgRptrInfoIndex. A value of zero indicates 1134 that this port is not currently mapped to any 1135 repeater." 1136 ::= { vgRptrBasicPortEntry 11 } 1138 vgRptrMonitor OBJECT IDENTIFIER ::= { vgRptrObjects 2 } 1140 vgRptrMonRepeater OBJECT IDENTIFIER ::= { vgRptrMonitor 1 } 1142 vgRptrMonitorTable OBJECT-TYPE 1143 SYNTAX SEQUENCE OF VgRptrMonitorEntry 1144 MAX-ACCESS not-accessible 1145 STATUS current 1146 DESCRIPTION 1147 "A table of performance and error statistics for 1148 each repeater in the system. The instance of the 1149 vgRptrInfoLastChange associated with a repeater 1150 is used to indicate possible discontinuities of 1151 the counters in this table that are associated 1152 with the same repeater." 1153 ::= { vgRptrMonRepeater 1 } 1155 vgRptrMonitorEntry OBJECT-TYPE 1156 SYNTAX VgRptrMonitorEntry 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "An entry in the table, containing statistics 1161 for a single repeater." 1162 INDEX { vgRptrInfoIndex } 1163 ::= { vgRptrMonitorTable 1 } 1165 VgRptrMonitorEntry ::= 1166 SEQUENCE { 1167 vgRptrMonTotalReadableFrames Counter32, 1168 vgRptrMonTotalReadableOctets Counter32, 1169 vgRptrMonTotalErrors Counter32, 1170 vgRptrMonHCTotalReadableOctets Counter64 1171 } 1173 vgRptrMonTotalReadableFrames OBJECT-TYPE 1174 SYNTAX Counter32 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION 1178 "The total number of good frames of valid frame 1179 length that have been received on all ports in 1180 this repeater. If an implementation cannot 1181 obtain a count of frames as seen by the repeater 1182 itself, this counter may be implemented as the 1183 summation of the values of the 1184 vgRptrPortReadableFrames counters for all of the 1185 ports in this repeater." 1186 ::= { vgRptrMonitorEntry 1 } 1188 vgRptrMonTotalReadableOctets OBJECT-TYPE 1189 SYNTAX Counter32 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "The total number of octets contained in good 1194 frames that have been received on all ports in 1195 this repeater. If an implementation cannot 1196 obtain a count of octets as seen by the repeater 1197 itself, this counter may be implemented as the 1198 summation of the values of the 1199 vgRptrPortReadableOctets counters for all of the 1200 ports in this repeater. 1202 Note that this counter will roll over very 1203 quickly. It is provided for backward 1204 compatibility for Network Management protocols 1205 that do not support 64 bit counters (e.g. SNMP 1206 version 1)." 1207 ::= { vgRptrMonitorEntry 2 } 1209 vgRptrMonTotalErrors OBJECT-TYPE 1210 SYNTAX Counter32 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "The total number of errors which have occurred on 1215 all of the ports in this repeater. If an 1216 implementation cannot obtain a count of these 1217 errors as seen by the repeater itself, this 1218 counter may be implemented as the summation of the 1219 values of the vgRptrPortIPMFrames, 1220 vgRptrPortOversizeFrames, and 1221 vgRptrPortDataErrorFrames counters for all of the 1222 ports in this repeater." 1223 ::= { vgRptrMonitorEntry 3 } 1225 vgRptrMonHCTotalReadableOctets OBJECT-TYPE 1226 SYNTAX Counter64 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "The total number of octets contained in good 1231 frames that have been received on all ports in 1232 this repeater. If an implementation cannot 1233 obtain a count of octets as seen by the repeater 1234 itself, this counter may be implemented as the 1235 summation of the values of the 1236 vgRptrPortHCReadableOctets counters for all of the 1237 ports in this repeater. 1239 This counter is a 64 bit version of 1240 vgRptrMonTotalOctets. It should be used by 1241 Network Management protocols which support 64 bit 1242 counters (e.g. SNMPv2)." 1243 ::= { vgRptrMonitorEntry 4 } 1245 vgRptrMonGroup OBJECT IDENTIFIER ::= { vgRptrMonitor 2 } 1246 -- Currently unused 1248 vgRptrMonPort OBJECT IDENTIFIER ::= { vgRptrMonitor 3 } 1250 vgRptrMonPortTable OBJECT-TYPE 1251 SYNTAX SEQUENCE OF VgRptrMonPortEntry 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "A table of performance and error statistics for 1256 the ports. The columnar object 1257 vgRptrPortLastChange is used to indicate possible 1258 discontinuities of counter type columnar objects 1259 in this table." 1260 ::= { vgRptrMonPort 1 } 1262 vgRptrMonPortEntry OBJECT-TYPE 1263 SYNTAX VgRptrMonPortEntry 1264 MAX-ACCESS not-accessible 1265 STATUS current 1266 DESCRIPTION 1267 "An entry in the vgRptrMonPortTable, containing 1268 performance and error statistics for a single 1269 port." 1270 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 1271 ::= { vgRptrMonPortTable 1 } 1273 VgRptrMonPortEntry ::= 1274 SEQUENCE { 1275 vgRptrPortReadableFrames Counter32, 1276 vgRptrPortReadableOctets Counter32, 1277 vgRptrPortUnreadableOctets Counter32, 1278 vgRptrPortHighPriorityFrames Counter32, 1279 vgRptrPortHighPriorityOctets Counter32, 1280 vgRptrPortNormPriorityFrames Counter32, 1281 vgRptrPortNormPriorityOctets Counter32, 1282 vgRptrPortBroadcastFrames Counter32, 1283 vgRptrPortMulticastFrames Counter32, 1284 vgRptrPortNullAddressedFrames Counter32, 1285 vgRptrPortIPMFrames Counter32, 1286 vgRptrPortOversizeFrames Counter32, 1287 vgRptrPortDataErrorFrames Counter32, 1288 vgRptrPortPriorityPromotions Counter32, 1289 vgRptrPortTransitionToTrainings Counter32, 1290 vgRptrPortHCReadableOctets Counter64, 1291 vgRptrPortHCUnreadableOctets Counter64, 1292 vgRptrPortHCHighPriorityOctets Counter64, 1293 vgRptrPortHCNormPriorityOctets Counter64, 1294 vgRptrPortLastChange TimeStamp 1295 } 1297 vgRptrPortReadableFrames OBJECT-TYPE 1298 SYNTAX Counter32 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "This object is the number of good frames of 1303 valid frame length that have been received on 1304 this port. This counter is incremented by one 1305 for each frame received on the port which is not 1306 counted by any of the following error counters: 1307 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1308 vgRptrPortNullAddressedFrames, or 1309 vgRptrPortDataErrorFrames." 1310 REFERENCE 1311 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1312 aReadableFramesReceived." 1313 ::= { vgRptrMonPortEntry 1 } 1315 vgRptrPortReadableOctets OBJECT-TYPE 1316 SYNTAX Counter32 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "This object is a count of the number of octets 1321 contained in good frames that have been received 1322 on this port. This counter is incremented by 1323 OctetCount for each frame received on this port 1324 which has been determined to be a readable frame 1325 (i.e. each frame counted by 1326 vgRptrPortReadableFrames). 1328 Note that this counter will roll over very 1329 quickly. It is provided for backward 1330 compatibility for Network Management protocols 1331 that do not support 64 bit counters (e.g. SNMP 1332 version 1)." 1333 REFERENCE 1334 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1335 aReadableOctetsReceived." 1336 ::= { vgRptrMonPortEntry 2 } 1338 vgRptrPortUnreadableOctets OBJECT-TYPE 1339 SYNTAX Counter32 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "This object is a count of the number of octets 1344 contained in invalid frames that have been 1345 received on this port. This counter is 1346 incremented by OctetCount for each frame received 1347 on this port which is counted by 1348 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1349 vgRptrPortNullAddressedFrames, or 1350 vgRptrPortDataErrorFrames. This counter can be 1351 combined with vgRptrPortReadableOctets to 1352 calculate network utilization. 1354 Note that this counter will roll over very 1355 quickly. It is provided for backward 1356 compatibility for Network Management protocols 1357 that do not support 64 bit counters (e.g. SNMP 1358 version 1)." 1359 REFERENCE 1360 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1361 aOctetsInUnreadableFramesRcvd." 1362 ::= { vgRptrMonPortEntry 3 } 1364 vgRptrPortHighPriorityFrames OBJECT-TYPE 1365 SYNTAX Counter32 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "This object is a count of high priority frames 1370 that have been received on this port. This 1371 counter is incremented by one for each high 1372 priority frame received on this port. This 1373 counter includes both good and bad high priority 1374 frames, as well as high priority training frames. 1375 This counter does not include normal priority 1376 frames which were priority promoted." 1377 REFERENCE 1378 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1379 aHighPriorityFramesReceived." 1380 ::= { vgRptrMonPortEntry 4 } 1382 vgRptrPortHighPriorityOctets OBJECT-TYPE 1383 SYNTAX Counter32 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "This object is a count of the number of octets 1388 contained in high priority frames that have been 1389 received on this port. This counter is 1390 incremented by OctetCount for each frame received 1391 on this port which is counted by 1392 vgRptrPortHighPriorityFrames. 1394 Note that this counter will roll over very 1395 quickly. It is provided for backward 1396 compatibility for Network Management protocols 1397 that do not support 64 bit counters (e.g. SNMP 1398 version 1)." 1399 REFERENCE 1400 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1401 aHighPriorityOctetsReceived." 1402 ::= { vgRptrMonPortEntry 5 } 1404 vgRptrPortNormPriorityFrames OBJECT-TYPE 1405 SYNTAX Counter32 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "This object is a count of normal priority frames 1410 that have been received on this port. This 1411 counter is incremented by one for each normal 1412 priority frame received on this port. This 1413 counter includes both good and bad normal 1414 priority frames, as well as normal priority 1415 training frames and normal priority frames which 1416 were priority promoted." 1418 REFERENCE 1419 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1420 aNormalPriorityFramesReceived." 1421 ::= { vgRptrMonPortEntry 6 } 1423 vgRptrPortNormPriorityOctets OBJECT-TYPE 1424 SYNTAX Counter32 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "This object is a count of the number of octets 1429 contained in normal priority frames that have 1430 been received on this port. This counter is 1431 incremented by OctetCount for each frame received 1432 on this port which is counted by 1433 vgRptrPortNormPriorityFrames. 1435 Note that this counter will roll over very 1436 quickly. It is provided for backward 1437 compatibility for Network Management protocols 1438 that do not support 64 bit counters (e.g. SNMP 1439 version 1)." 1440 REFERENCE 1441 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1442 aNormalPriorityOctetsReceived." 1443 ::= { vgRptrMonPortEntry 7 } 1445 vgRptrPortBroadcastFrames OBJECT-TYPE 1446 SYNTAX Counter32 1447 MAX-ACCESS read-only 1448 STATUS current 1449 DESCRIPTION 1450 "This object is a count of broadcast packets that 1451 have been received on this port. This counter is 1452 incremented by one for each readable frame 1453 received on this port whose destination MAC 1454 address is the broadcast address. Frames 1455 counted by this counter are also counted by 1456 vgRptrPortReadableFrames." 1457 REFERENCE 1458 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1459 aBroadcastFramesReceived." 1460 ::= { vgRptrMonPortEntry 8 } 1462 vgRptrPortMulticastFrames OBJECT-TYPE 1463 SYNTAX Counter32 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "This object is a count of multicast packets that 1468 have been received on this port. This counter is 1469 incremented by one for each readable frame 1470 received on this port whose destination MAC 1471 address has the group address bit set, but is not 1472 the broadcast address. Frames counted by this 1473 counter are also counted by 1474 vgRptrPortReadableFrames, but not by 1475 vgRptrPortBroadcastFrames. Note that when 1476 value of the instance vgRptrInfoCurrentFramingType 1477 for the repeater that this port is associated 1478 with is equal to 'frameType88025', this count 1479 includes packets addressed to functional 1480 addresses." 1481 REFERENCE 1482 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1483 aMulticastFramesReceived." 1484 ::= { vgRptrMonPortEntry 9 } 1486 vgRptrPortNullAddressedFrames OBJECT-TYPE 1487 SYNTAX Counter32 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "This object is a count of null addressed packets 1492 that have been received on this port. This 1493 counter is incremented by one for each frame 1494 received on this port with a destination MAC 1495 address consisting of all zero bits. Both void 1496 and training frames are included in this 1497 counter." 1498 REFERENCE 1499 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1500 aNullAddressedFramesReceived." 1501 ::= { vgRptrMonPortEntry 10 } 1503 vgRptrPortIPMFrames OBJECT-TYPE 1504 SYNTAX Counter32 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "This object is a count of the number of frames 1509 that have been received on this port with an 1510 invalid packet marker and no PMI errors. A 1511 repeater will write an invalid packet marker to 1512 the end of a frame containing errors as it is 1513 forwarded through the repeater to the other 1514 ports. This counter is incremented by one for 1515 each frame received on this port which has had an 1516 invalid packet marker added to the end of the 1517 frame. 1519 This counter indicates problems with remote cable 1520 segments, as opposed to problems with cables 1521 directly attached to this repeater." 1522 REFERENCE 1523 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1524 aIPMFramesReceived." 1525 ::= { vgRptrMonPortEntry 11 } 1527 vgRptrPortOversizeFrames OBJECT-TYPE 1528 SYNTAX Counter32 1529 MAX-ACCESS read-only 1530 STATUS current 1531 DESCRIPTION 1532 "This object is a count of oversize frames 1533 received on this port. This counter is 1534 incremented by one for each frame received on 1535 this port whose OctetCount is larger than the 1536 maximum legal frame size. 1538 The frame size which causes this counter to 1539 increment is dependent on the current value of 1540 vgRptrInfoCurrentFramingType for the repeater that 1541 the port is associated with. When 1542 vgRptrInfoCurrentFramingType is equal to 1543 frameType88023 this counter will increment for 1544 frames that are 1519 octets or larger. When 1545 vgRptrInfoCurrentFramingType is equal to 1546 frameType88025 this counter will increment for 1547 frames that are 4521 octets or larger." 1548 REFERENCE 1549 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1550 aOversizeFramesReceived." 1551 ::= { vgRptrMonPortEntry 12 } 1553 vgRptrPortDataErrorFrames OBJECT-TYPE 1554 SYNTAX Counter32 1555 MAX-ACCESS read-only 1556 STATUS current 1557 DESCRIPTION 1558 "This object is a count of errored frames 1559 received on this port. This counter is 1560 incremented by one for each frame received on 1561 this port with any of the following errors: bad 1562 FCS (with no IPM), PMI errors (excluding frames 1563 with an IPM error as the only PMI error), or 1564 undersize (with no IPM). Does not include 1565 packets counted by vgRptrPortIPMFrames, 1566 vgRptrPortOversizeFrames, or 1567 vgRptrPortNullAddressedFrames. 1569 This counter indicates problems with the cable 1570 directly attached to this repeater, while 1571 vgRptrPortIPMFrames indicates problems with remote 1572 cables attached to other repeaters." 1573 REFERENCE 1574 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1575 aDataErrorFramesReceived." 1576 ::= { vgRptrMonPortEntry 13 } 1578 vgRptrPortPriorityPromotions OBJECT-TYPE 1579 SYNTAX Counter32 1580 MAX-ACCESS read-only 1581 STATUS current 1582 DESCRIPTION 1583 "This counter is incremented by one each time the 1584 priority promotion timer has expired on this port 1585 and a normal priority frame is priority 1586 promoted." 1587 REFERENCE 1588 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1589 aPriorityPromotions." 1590 ::= { vgRptrMonPortEntry 14 } 1592 vgRptrPortTransitionToTrainings OBJECT-TYPE 1593 SYNTAX Counter32 1594 MAX-ACCESS read-only 1595 STATUS current 1596 DESCRIPTION 1597 "This counter is incremented by one each time the 1598 vgRptrPortStatus object for this port transitions 1599 into the 'training' state." 1600 REFERENCE 1601 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1602 aTransitionsIntoTraining." 1603 ::= { vgRptrMonPortEntry 15 } 1605 vgRptrPortHCReadableOctets OBJECT-TYPE 1606 SYNTAX Counter64 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "This object is a count of the number of octets 1611 contained in good frames that have been received 1612 on this port. This counter is incremented by 1613 OctetCount for each frame received on this port 1614 which has been determined to be a readable frame 1615 (i.e. each frame counted by 1616 vgRptrPortReadableFrames). 1618 This counter is a 64 bit version of 1619 vgRptrPortReadableOctets. It should be used by 1620 Network Management protocols which support 64 bit 1621 counters (e.g. SNMPv2)." 1622 REFERENCE 1623 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1624 aReadableOctetsReceived." 1625 ::= { vgRptrMonPortEntry 16 } 1627 vgRptrPortHCUnreadableOctets OBJECT-TYPE 1628 SYNTAX Counter64 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "This object is a count of the number of octets 1633 contained in invalid frames that have been 1634 received on this port. This counter is 1635 incremented by OctetCount for each frame received 1636 on this port which is counted by 1637 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1638 vgRptrPortNullAddressedFrames, or 1639 vgRptrPortDataErrorFrames. This counter can be 1640 combined with vgRptrPortHCReadableOctets to 1641 calculate network utilization. 1643 This counter is a 64 bit version of 1644 vgRptrPortUnreadableOctets. It should be used by 1645 Network Management protocols which support 64 bit 1646 counters (e.g. SNMPv2)." 1647 REFERENCE 1648 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1649 aOctetsInUnreadableFramesRcvd." 1650 ::= { vgRptrMonPortEntry 17 } 1652 vgRptrPortHCHighPriorityOctets OBJECT-TYPE 1653 SYNTAX Counter64 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "This object is a count of the number of octets 1658 contained in high priority frames that have been 1659 received on this port. This counter is 1660 incremented by OctetCount for each frame received 1661 on this port which is counted by 1662 vgRptrPortHighPriorityFrames. 1664 This counter is a 64 bit version of 1665 vgRptrPortHighPriorityOctets. It should be used 1666 by Network Management protocols which support 64 1667 bit counters (e.g. SNMPv2)." 1668 REFERENCE 1669 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1670 aHighPriorityOctetsReceived." 1671 ::= { vgRptrMonPortEntry 18 } 1673 vgRptrPortHCNormPriorityOctets OBJECT-TYPE 1674 SYNTAX Counter64 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "This object is a count of the number of octets 1679 contained in normal priority frames that have 1680 been received on this port. This counter is 1681 incremented by OctetCount for each frame received 1682 on this port which is counted by 1683 vgRptrPortNormPriorityFrames. 1685 This counter is a 64 bit version of 1686 vgRptrPortNormPriorityOctets. It should be used 1687 by Network Management protocols which support 64 1688 bit counters (e.g. SNMPv2)." 1689 REFERENCE 1690 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1691 aNormalPriorityOctetsReceived." 1692 ::= { vgRptrMonPortEntry 19 } 1694 vgRptrPortLastChange OBJECT-TYPE 1695 SYNTAX TimeStamp 1696 MAX-ACCESS read-only 1697 STATUS current 1698 DESCRIPTION 1699 "The value of sysUpTime when the last of the 1700 following occurred: 1701 1) the agent cold- or warm-started; 1702 2) the row for the port was created 1703 (such as when a device or module was 1704 added to the system); or 1705 3) any condition that would cause one of 1706 the counters for the row to experience 1707 a discontinuity." 1708 ::= { vgRptrMonPortEntry 20 } 1710 vgRptrAddrTrack OBJECT IDENTIFIER ::= { vgRptrObjects 3 } 1712 vgRptrAddrTrackRptr 1713 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 1 } 1715 vgRptrAddrSearch 1716 OBJECT IDENTIFIER ::= { vgRptrAddrTrackRptr 1 } 1718 -- Note: { vgRptrAddrSearch 1 } to { vgRptrAddrSearch 4 } 1719 -- were used in an earlier version of this draft for 1720 -- repeater-wide scalar objects. With the change in the 1721 -- model to allow multiple repeaters, they have been moved 1722 -- into the following table. This table should be moved to 1723 -- { vgRptrAddrSearch 1 } when this draft is published as 1724 -- an RFC. 1726 vgRptrAddrSearchTable OBJECT-TYPE 1727 SYNTAX SEQUENCE OF VgRptrAddrSearchEntry 1728 MAX-ACCESS not-accessible 1729 STATUS current 1730 DESCRIPTION 1731 "This table contains one entry per repeater in the 1732 system. It defines objects which allow a network 1733 management application to instruct an agent to 1734 watch for a given MAC address and report which 1735 port it was seen on. Only one address search can 1736 be in progress on each repeater at any one time. 1737 Before starting an address search, a management 1738 application should obtain 'ownership' of the entry 1739 in vgRptrAddrSearchTable for the repeater that is 1740 to perform the search. This is accomplished with 1741 the vgRptrAddrSearchLock and 1742 vgRptrAddrSearchStatus as follows: 1744 try_again: 1745 get(vgRptrAddrSearchLock, 1746 vgRptrAddrSearchStatus) 1747 while (vgRptrAddrSearchStatus != notInUse) 1748 { 1749 /* Wait for objects to be available */ 1750 short delay 1751 get(vgRptrAddrSearchLock, 1752 vgRptrAddrSearchStatus) 1754 } 1756 /* Try to claim map objects */ 1757 lock_value = vgRptrAddrSearchLock 1758 if ( set(vgRptrAddrSearchLock = lock_value, 1759 vgRptrAddrSearchStatus = inUse, 1760 vgRptrAddrSearchOwner = 'my-address') 1761 == FAILURE) 1762 /* Another manager got the lock */ 1763 goto try_again 1765 /* I have the lock */ 1766 set(vgRptrAddrSearchAddress = ) 1768 wait for vgRptrAddrSearchState to change from 1769 none 1771 if (vgRptrAddrASearchState == single) 1772 get (vgRptrAddrSearchGroup, 1773 vgRptrAddrSearchPort) 1775 /* release the lock, making sure not to 1776 overwrite anyone else's lock */ 1777 set (vgRptrAddrSearchLock = lock_value+1, 1778 vgRptrAddrSearchStatus = notInUse, 1779 vgRptrAddrSearchOwner = '') 1781 A management station first retrieves the values of 1782 the appropriate instances of the 1783 vgRptrAddrSearchLock and vgRptrAddrSearchStatus 1784 objects, periodically repeating the retrieval if 1785 necessary, until the value of 1786 vgRptrAddrSearchStatus is 'notInUse'. The 1787 management station then tries to set the same 1788 instance of the vgRptrAddrSearchLock object to the 1789 value it just retrieved, the same instance of the 1790 vgRptrAddrSearchStatus object to 'inUse', and the 1791 corresponding instance of vgRptrAddrSearchOwner to 1792 a value indicating itself. If the set operation 1793 succeeds, then the management station has obtained 1794 ownership of the vgRptrAddrSearchEntry, and the 1795 value of vgRptrAddrSearchLock is incremented by 1796 the agent (as per the semantics of TestAndIncr). 1797 Failure of the set operation indicates that some 1798 other manager has obtained ownership of the 1799 vgRptrAddrSearchEntry. 1801 Once ownership is obtained, the management station 1802 can proceed with the search operation. Note that 1803 the agent will reset vgRptrAddrSearchStatus to 1804 'notInUse' if it has been in the 'inUse' state 1805 for an abnormally long period of time, to prevent 1806 a misbehaving manager from permanently locking the 1807 entry. It is suggested that this timeout period 1808 be between one and five minutes. 1810 When the management station has completed its 1811 search operation, it should free the entry by 1812 setting the instance of the vgRptrAddrSearchLock 1813 object to the previous value + 1, the instance of 1814 the vgRptrAddrSearchStatus to 'notInUse', and the 1815 instance of vgRptrAddrSearchOwner to a zero length 1816 string. This is done to prevent overwriting 1817 another station's lock." 1818 ::= { vgRptrAddrSearch 5 } 1820 vgRptrAddrSearchEntry OBJECT-TYPE 1821 SYNTAX VgRptrAddrSearchEntry 1822 MAX-ACCESS not-accessible 1823 STATUS current 1824 DESCRIPTION 1825 "An entry containing objects for invoking an 1826 address search on a repeater." 1827 INDEX { vgRptrInfoIndex } 1828 ::= { vgRptrAddrSearchTable 1 } 1830 VgRptrAddrSearchEntry ::= 1831 SEQUENCE { 1832 vgRptrAddrSearchLock TestAndIncr, 1833 vgRptrAddrSearchStatus INTEGER, 1834 vgRptrAddrSearchAddress MacAddress, 1835 vgRptrAddrSearchState INTEGER, 1836 vgRptrAddrSearchGroup Integer32, 1837 vgRptrAddrSearchPort Integer32, 1838 vgRptrAddrSearchOwner OwnerString 1839 } 1841 vgRptrAddrSearchLock OBJECT-TYPE 1842 SYNTAX TestAndIncr 1843 MAX-ACCESS read-write 1844 STATUS current 1845 DESCRIPTION 1846 "This object is used by a management station as an 1847 advisory lock for this vgRptrAddrSearchEntry." 1848 ::= { vgRptrAddrSearchEntry 1 } 1850 vgRptrAddrSearchStatus OBJECT-TYPE 1851 SYNTAX INTEGER { 1852 notInUse(1), 1853 inUse(2) 1854 } 1855 MAX-ACCESS read-write 1856 STATUS current 1857 DESCRIPTION 1858 "This object is used to indicate that some 1859 management station is currently using this 1860 vgRptrAddrSearchEntry. Cooperating managers 1861 should set this object to 'notInUse' when they are 1862 finished using this entry. The agent will 1863 automatically set the value of this object to 1864 'notInUse' if it has been set to 'inUse' for an 1865 unusually long period of time." 1866 ::= { vgRptrAddrSearchEntry 2 } 1868 vgRptrAddrSearchAddress OBJECT-TYPE 1869 SYNTAX MacAddress 1870 MAX-ACCESS read-write 1871 STATUS current 1872 DESCRIPTION 1873 "This object is used to search for a specified MAC 1874 address. When this object is set, an address 1875 search begins. This automatically sets the 1876 corresponding instance of the 1877 vgRptrAddrSearchState object to 'none' and the 1878 corresponding instances of the 1879 vgRptrAddrSearchGroup and vgRptrAddrSearchPort 1880 objects to 0. 1882 When a valid frame is received by this repeater 1883 with a source MAC address which matches the 1884 current value of vgRptrAddrSearchAddress, the 1885 agent will update the corresponding instances of 1886 vgRptrAddrSearchState, vgRptrAddrSearchGroup and 1887 vgRptrAddrSearchPort to reflect the current status 1888 of the search, and the group and port on which 1889 the frame was seen." 1890 ::= { vgRptrAddrSearchEntry 3 } 1892 vgRptrAddrSearchState OBJECT-TYPE 1893 SYNTAX INTEGER { 1894 none(1), 1895 single(2), 1896 multiple(3) 1897 } 1899 MAX-ACCESS read-only 1900 STATUS current 1901 DESCRIPTION 1902 "The current state of the MAC address search on 1903 this repeater. This object is initialized to 1904 'none' when the corresponding instance of 1905 vgRptrAddrSearchAddress is set. If the agent 1906 detects the address on exactly one port, it will 1907 set this object to 'single', and set the 1908 corresponding instances of vgRptrAddrSearchGroup 1909 and vgRptrAddrSearchPort to reflect the group and 1910 port on which the address was heard. If the agent 1911 detects the address on more than one port, it will 1912 set this object to 'multiple'." 1913 ::= { vgRptrAddrSearchEntry 4 } 1915 vgRptrAddrSearchGroup OBJECT-TYPE 1916 SYNTAX Integer32 (0..2147483647) 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "The group from which an error-free frame whose 1921 source address is equal to the corresponding 1922 instance of vgRptrAddrSearchAddress has been 1923 received. The value of this object is undefined 1924 when the corresponding instance of 1925 vgRptrAddrSearchState is equal to 'none' or 1926 'multiple'." 1927 ::= { vgRptrAddrSearchEntry 5 } 1929 vgRptrAddrSearchPort OBJECT-TYPE 1930 SYNTAX Integer32 (0..2147483647) 1931 MAX-ACCESS read-only 1932 STATUS current 1933 DESCRIPTION 1934 "The port from which an error-free frame whose 1935 source address is equal to the corresponding 1936 instance of vgRptrAddrSearchAddress has been 1937 received. The value of this object is undefined 1938 when the corresponding instance of 1939 vgRptrAddrSearchState is equal to 'none' or 1940 'multiple'." 1941 ::= { vgRptrAddrSearchEntry 6 } 1943 vgRptrAddrSearchOwner OBJECT-TYPE 1944 SYNTAX OwnerString 1945 MAX-ACCESS read-write 1946 STATUS current 1947 DESCRIPTION 1948 "The entity which currently has 'ownership' of 1949 this vgRptrAddrSearchEntry." 1950 ::= { vgRptrAddrSearchEntry 7 } 1952 vgRptrAddrTrackGroup 1953 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 2 } 1954 -- Currently unused 1956 vgRptrAddrTrackPort 1957 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 3 } 1959 vgRptrAddrTrackTable OBJECT-TYPE 1960 SYNTAX SEQUENCE OF VgRptrAddrTrackEntry 1961 MAX-ACCESS not-accessible 1962 STATUS current 1963 DESCRIPTION 1964 "Table of address mapping information about the 1965 ports." 1966 ::= { vgRptrAddrTrackPort 1 } 1968 vgRptrAddrTrackEntry OBJECT-TYPE 1969 SYNTAX VgRptrAddrTrackEntry 1970 MAX-ACCESS not-accessible 1971 STATUS current 1972 DESCRIPTION 1973 "An entry in the table, containing address mapping 1974 information about a single port." 1975 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 1976 ::= { vgRptrAddrTrackTable 1 } 1978 VgRptrAddrTrackEntry ::= 1979 SEQUENCE { 1980 vgRptrAddrLastTrainedAddress OCTET STRING, 1981 vgRptrAddrTrainedAddrChanges Counter32, 1982 vgRptrRptrDetectedDupAddress TruthValue, 1983 vgRptrMgrDetectedDupAddress TruthValue 1984 } 1986 vgRptrAddrLastTrainedAddress OBJECT-TYPE 1987 SYNTAX OCTET STRING (SIZE(0 | 6)) 1988 MAX-ACCESS read-only 1989 STATUS current 1990 DESCRIPTION 1991 "This object is the MAC address of the last 1992 station which succeeded in training on this port. 1994 A cascaded repeater may train using the null 1995 address. If no stations have succeeded in 1996 training on this port since the agent began 1997 monitoring the port activity, the agent shall 1998 return a string of length zero." 1999 REFERENCE 2000 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2001 aLastTrainedAddress." 2002 ::= { vgRptrAddrTrackEntry 1 } 2004 vgRptrAddrTrainedAddrChanges OBJECT-TYPE 2005 SYNTAX Counter32 2006 MAX-ACCESS read-only 2007 STATUS current 2008 DESCRIPTION 2009 "This counter is incremented by one for each time 2010 that the vgRptrAddrLastTrainedAddress object for 2011 this port changes." 2012 REFERENCE 2013 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2014 aTrainedAddressChanges." 2015 ::= { vgRptrAddrTrackEntry 2 } 2017 vgRptrRptrDetectedDupAddress OBJECT-TYPE 2018 SYNTAX TruthValue 2019 MAX-ACCESS read-only 2020 STATUS current 2021 DESCRIPTION 2022 "This object is used to indicate that the 2023 repeater detected an error-free training frame on 2024 this port with a source MAC address which matches 2025 the value of vgRptrAddrLastTrainedAddress of 2026 another active port in the same repeater. This is 2027 reset to 'false' when an error-free training frame 2028 is received with a source MAC address which does 2029 not match vgRptrAddrLastTrainedAddress of another 2030 port which is active in the same repeater. For 2031 the cascade port, this object will be 'true' if 2032 the 'D' bit in the most recently received 2033 error-free training response frame was set." 2034 REFERENCE 2035 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2036 aLocalRptrDetectedDupAddr." 2037 ::= { vgRptrAddrTrackEntry 3 } 2039 vgRptrMgrDetectedDupAddress OBJECT-TYPE 2040 SYNTAX TruthValue 2041 MAX-ACCESS read-write 2042 STATUS current 2043 DESCRIPTION 2044 "This object can be set by a management station 2045 when it detects that there is a duplicate MAC 2046 address. This object is OR'd with 2047 vgRptrRptrDetectedDupAddress to form the value of 2048 the 'D' bit in training response frames on this 2049 port. 2051 The purpose of this object is to provide a means 2052 for network management software to inform an end 2053 station that it is using a duplicate station 2054 address. Setting this object does not affect the 2055 current state of the link; the end station will 2056 not be informed of the duplicate address until it 2057 retrains for some reason. Note that regardless 2058 of its station address, the end station will not 2059 be able to train successfully until the network 2060 management software has set this object back to 2061 'false'. Although this object exists on 2062 cascade ports, it does not perform any function 2063 since this repeater is the initiator of training 2064 on a cascade port." 2065 REFERENCE 2066 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2067 aCentralMgmtDetectedDupAddr." 2068 ::= { vgRptrAddrTrackEntry 4 } 2070 vgRptrTraps OBJECT IDENTIFIER ::= { vgRptrMIB 2 } 2071 vgRptrTrapPrefix OBJECT IDENTIFIER ::= { vgRptrTraps 0 } 2073 vgRptrHealth NOTIFICATION-TYPE 2074 OBJECTS { vgRptrInfoOperStatus } 2075 STATUS current 2076 DESCRIPTION 2077 "A vgRptrHealth trap conveys information related 2078 to the operational state of a repeater. This trap 2079 is sent when the value of an instance of 2080 vgRptrInfoOperStatus changes. The vgRptrHealth 2081 trap is not sent as a result of powering up a 2082 repeater. 2084 The vgRptrHealth trap must contain the instance of 2085 the vgRptrInfoOperStatus object associated with 2086 the affected repeater. 2088 The agent must throttle the generation of 2089 consecutive vgRptrHealth traps so that there is at 2090 least a five-second gap between traps of this 2091 type. When traps are throttled, they are dropped, 2092 not queued for sending at a future time. (Note 2093 that 'generating' a trap means sending to all 2094 configured recipients.)" 2095 REFERENCE 2096 "IEEE 802.12, Layer Management, 13.2.4.2.3, 2097 nRepeaterHealth." 2098 ::= { vgRptrTrapPrefix 1 } 2100 vgRptrGroupChange NOTIFICATION-TYPE 2101 OBJECTS { vgRptrGroupIndex } 2102 STATUS current 2103 DESCRIPTION 2104 "This trap is sent when a change occurs in the 2105 group structure of a repeater system. This occurs 2106 only when a group is physically removed from or 2107 added to a repeater system. The vgRptrGroupChange 2108 trap is not sent when powering up a repeater. 2110 The varBind list contains the identifier of the 2111 group that was removed or added. 2113 The agent must throttle the generation of 2114 consecutive vgRptrGroupChange traps so that there 2115 is at least a five-second gap between traps of 2116 this type. When traps are throttled, they are 2117 dropped, not queued for sending at a future time. 2118 (Note that 'generating' a trap means sending to 2119 all configured recipients.)" 2120 REFERENCE 2121 "IEEE 802.12, Layer Management, 13.2.4.2.3, 2122 nGroupMapChange." 2123 ::= { vgRptrTrapPrefix 2 } 2125 vgRptrResetEvent NOTIFICATION-TYPE 2126 OBJECTS { vgRptrInfoOperStatus } 2127 STATUS current 2128 DESCRIPTION 2129 "A vgRptrResetEvent trap conveys information 2130 related to the operational state of a repeater. 2131 This trap is sent on completion of a repeater 2132 reset action. A repeater reset action is defined 2133 as a transition to its initial state as specified 2134 in clause 12 [IEEE Std 802.12] when triggered by 2135 a management command. 2137 The vgRptrResetEvent trap is not sent when the 2138 agent restarts and sends an SNMP coldStart or 2139 warmStart trap. 2141 The vgRptrResetEvent trap must contain the 2142 instance of the vgRptrInfoOperStatus object 2143 associated with the affected repeater. 2145 The agent must throttle the generation of 2146 consecutive vgRptrResetEvent traps so that there 2147 is at least a five-second gap between traps of 2148 this type. When traps are throttled, they are 2149 dropped, not queued for sending at a future time. 2150 (Note that 'generating' a trap means sending to 2151 all configured recipients.)" 2152 REFERENCE 2153 "IEEE 802.12, Layer Management, 13.2.4.2.3, 2154 nRepeaterReset." 2155 ::= { vgRptrTrapPrefix 3 } 2157 -- conformance information 2159 vgRptrConformance OBJECT IDENTIFIER ::= { vgRptrMIB 3 } 2161 vgRptrCompliances 2162 OBJECT IDENTIFIER ::= { vgRptrConformance 1 } 2164 vgRptrGroups OBJECT IDENTIFIER ::= { vgRptrConformance 2 } 2166 -- compliance statements 2168 vgRptrCompliance MODULE-COMPLIANCE 2169 STATUS current 2170 DESCRIPTION 2171 "The compliance statement for managed 802.12 2172 repeaters." 2174 MODULE -- this module 2175 MANDATORY-GROUPS { vgRptrConfigGroup } 2177 GROUP vgRptrStatsGroup 2178 DESCRIPTION 2179 "This group is optional. It is appropriate 2180 for all agents that have the necessary 2181 instrumentation." 2183 GROUP vgRptrAddrGroup 2184 DESCRIPTION 2185 "This group is optional. It is appropriate 2186 for all agents that have the necessary 2187 instrumentation." 2188 ::= { vgRptrCompliances 1 } 2190 -- units of conformance 2192 vgRptrConfigGroup OBJECT-GROUP 2193 OBJECTS { 2194 vgRptrInfoMACAddress, 2195 vgRptrInfoCurrentFramingType, 2196 vgRptrInfoDesiredFramingType, 2197 vgRptrInfoFramingCapability, 2198 vgRptrInfoTrainingVersion, 2199 vgRptrInfoOperStatus, 2200 vgRptrInfoReset, 2201 vgRptrInfoLastChange, 2202 vgRptrGroupDescr, 2203 vgRptrGroupObjectID, 2204 vgRptrGroupOperStatus, 2205 vgRptrGroupLastOperStatusChange, 2206 vgRptrGroupPortCapacity, 2207 vgRptrGroupCablesBundled, 2208 vgRptrPortType, 2209 vgRptrPortAdminStatus, 2210 vgRptrPortOperStatus, 2211 vgRptrPortSupportedPromiscMode, 2212 vgRptrPortSupportedCascadeMode, 2213 vgRptrPortAllowedTrainType, 2214 vgRptrPortLastTrainConfig, 2215 vgRptrPortTrainingResult, 2216 vgRptrPortPriorityEnable, 2217 vgRptrPortRptrInfoIndex 2218 } 2219 STATUS current 2220 DESCRIPTION 2221 "A collection of objects for managing the status 2222 and configuration of IEEE 802.12 repeaters." 2223 ::= { vgRptrGroups 1 } 2225 vgRptrStatsGroup OBJECT-GROUP 2226 OBJECTS { 2227 vgRptrMonTotalFrames, 2228 vgRptrMonTotalOctets, 2229 vgRptrMonTotalErrors, 2230 vgRptrMonHCTotalOctets, 2231 vgRptrPortReadableFrames, 2232 vgRptrPortReadableOctets, 2233 vgRptrPortUnreadableOctets, 2234 vgRptrPortHighPriorityFrames, 2235 vgRptrPortHighPriorityOctets, 2236 vgRptrPortNormPriorityFrames, 2237 vgRptrPortNormPriorityOctets, 2238 vgRptrPortBroadcastFrames, 2239 vgRptrPortMulticastFrames, 2240 vgRptrPortNullAddressedFrames, 2241 vgRptrPortIPMFrames, 2242 vgRptrPortOversizeFrames, 2243 vgRptrPortDataErrorFrames, 2244 vgRptrPortPriorityPromotions, 2245 vgRptrPortTransitionToTrainings, 2246 vgRptrPortHCReadableOctets, 2247 vgRptrPortHCUnreadableOctets, 2248 vgRptrPortHCHighPriorityOctets, 2249 vgRptrPortHCNormPriorityOctets, 2250 vgRptrPortLastChange 2251 } 2252 STATUS current 2253 DESCRIPTION 2254 "A collection of objects for providing statistics 2255 for IEEE 802.12 repeaters." 2256 ::= { vgRptrGroups 2 } 2258 vgRptrAddrGroup OBJECT-GROUP 2259 OBJECTS { 2260 vgRptrAddrSearchLock, 2261 vgRptrAddrSearchStatus, 2262 vgRptrAddrSearchAddress, 2263 vgRptrAddrSearchState, 2264 vgRptrAddrSearchGroup, 2265 vgRptrAddrSearchPort, 2266 vgRptrAddrSearchOwner, 2267 vgRptrAddrLastTrainedAddress, 2268 vgRptrAddrTrainedAddrChanges, 2269 vgRptrRptrDetectedDupAddress, 2270 vgRptrMgrDetectedDupAddress 2271 } 2272 STATUS current 2273 DESCRIPTION 2274 "A collection of objects for tracking addresses 2275 on IEEE 802.12 repeaters." 2276 ::= { vgRptrGroups 3 } 2278 END 2280 5. Acknowledgements 2282 This document was produced by the IETF 100VG-AnyLAN Working Group. 2283 It is based on the work of IEEE 802.12. 2285 6. References 2287 [1] Information processing systems - Open Systems Interconnection - 2288 Specification of Abstract Syntax Notation One (ASN.1), 2289 International Organization for Standardization. International 2290 Standard 8824 (December, 1987). 2292 [2] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 2293 of Management Information for version 2 of the Simple Network 2294 Management Protocol (SNMPv2)", RFC 1442, SNMP Research, Inc., 2295 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 2296 University, April 1993. 2298 [3] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 2299 Conventions for version 2 of the Simple Network Management 2300 Protocol (SNMPv2)", RFC 1443, SNMP Research, Inc., Hughes LAN 2301 Systems, Dover Beach Consulting, Inc., Carnegie Mellon 2302 University, April 1993. 2304 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2305 "Conformance Statements for version 2 of the Simple Network 2306 Management Protocol (SNMPv2)", RFC 1444, SNMP Research, Inc., 2307 Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 2308 University, April 1993. 2310 [5] McCloghrie, K., and M. Rose, "Management Information Base for 2311 Network Management of TCP/IP-based internets - MIB-II", STD 17, 2312 RFC 1213, Hughes LAN Systems, Performance Systems International, 2313 March 1991. 2315 [6] IEEE, "Demand Priority Access Method, Physical Layer and Repeater 2316 Specifications for 100 Mb/s Operation", IEEE Standard 2317 802.12-1995" 2319 7. Security Considerations 2321 Security issues are not discussed in this memo. 2323 8. Author's Address 2324 John Flick 2325 Hewlett Packard Company 2326 8000 Foothills Blvd. M/S 5556 2327 Roseville, CA 95747-5556 2329 Phone: +1 916 785 4018 2330 Email: johnf@hprnd.rose.hp.com 2332 Table of Contents 2334 1. Abstract ................................................... 2 2335 2. Object Definitions ......................................... 2 2336 3. Overview ................................................... 3 2337 3.1. MAC Addresses ............................................ 3 2338 3.2. IEEE 802.12 Training Frames .............................. 4 2339 3.3. Structure of the MIB ..................................... 7 2340 3.3.1. The Basic Group Definitions ............................ 7 2341 3.3.2. The Monitor Group Definitions .......................... 7 2342 3.3.3. The Address Tracking Group Definitions ................. 7 2343 3.4. Relationship to other MIBs ............................... 7 2344 3.4.1. Relationship to the 'system' group ..................... 7 2345 3.4.2. Relationship to the 'interfaces' group ................. 7 2346 3.5. Mapping of IEEE 802.12 Managed Objects ................... 8 2347 4. Definitions ................................................ 10 2348 5. Acknowledgements ........................................... 51 2349 6. References ................................................. 51 2350 7. Security Considerations .................................... 51 2351 8. Author's Address ........................................... 51