idnits 2.17.1 draft-ietf-vgmib-repeater-dev-03.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-20) 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 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. ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 366 has weird spacing: '...DupAddr vgR...' == Line 368 has weird spacing: '...eceived vgR...' == Line 369 has weird spacing: '...eceived vgR...' == Line 379 has weird spacing: '...eceived vgRpt...' == Line 380 has weird spacing: '...eceived vgRpt...' == (3 more instances...) -- 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 (February 18, 1997) is 9923 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Obsolete normative reference: RFC 1902 (ref. '2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '3') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '4') (Obsoleted by RFC 2580) -- Possible downref: Non-RFC (?) normative reference: ref. '6' ** Downref: Normative reference to an Informational RFC: RFC 1988 (ref. '8') -- Possible downref: Non-RFC (?) normative reference: ref. '9' Summary: 14 errors (**), 0 flaws (~~), 8 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 February 18 1997 4 Definitions of Managed Objects for IEEE 802.12 Repeater Devices 6 February 18, 1997 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. Introduction 38 This memo defines a portion of the Management Information Base (MIB) 39 for use with network management protocols in TCP/IP-based internets. 40 In particular, it defines objects for managing network repeaters 41 based on IEEE 802.12. 43 2. The SNMP Network Management Framework 45 The SNMP Network Management Framework consists of several components. 46 For the purpose of this specification, the applicable components of 47 the Framework are the SMI and related documents [2, 3, 4], which 48 define the mechanisms used for describing and naming objects for the 49 purpose of management. 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, termed 57 the Management Information Base (MIB). Objects in the MIB are 58 defined using the subset of Abstract Syntax Notation One (ASN.1) [1] 59 defined in the SMI [2]. In particular, each object type is named by 60 an OBJECT IDENTIFIER, an administratively assigned name. The object 61 type together with an object instance serves to uniquely identify a 62 specific instantiation of the object. For human convenience, we 63 often use a textual string, termed the descriptor, to refer to the 64 object type. 66 3. Overview 68 Instances of these object types represent attributes of an IEEE 69 802.12 repeater, as defined by Section 12, "RMAC Protocol" in IEEE 70 Standard 802.12-1995 [6]. 72 The definitions presented here are based on Section 13, "Layer 73 management functions and services", and Annex C, "GDMO Specifications 74 for Demand Priority Managed Objects" of IEEE Standard 802.12-1995 75 [6]. 77 Implementors of these MIB objects should note that the IEEE document 78 explicitly describes (in the form of Pascal pseudocode) when, where, 79 and how various repeater attributes are measured. The IEEE document 80 also describes the effects of repeater actions that may be invoked by 81 manipulating instances of the MIB objects defined here. 83 The counters in this document are defined to be the same as those 84 counters in IEEE Standard 802.12-1995, with the intention that the 85 same instrumentation can be used to implement both the IEEE and IETF 86 management standards. 88 3.1. MAC Addresses 90 All representations of MAC addresses in this MIB module are in 91 "canonical" order defined by 802.1a, i.e., as if it were transmitted 92 least significant bit first. This is true even if the repeater is 93 operating in token ring framing mode, which requires MAC addresses to 94 be transmitted most significant bit first. 96 3.2. Master Mode and Slave Mode 98 In an IEEE 802.12 network, "master" devices act as network 99 controllers to decide when to grant requesting end-nodes permission 100 to transmit. These master devices may be repeaters, or other active 101 controller devices such as switches. 103 Devices which do not act as network controllers, such as end-nodes or 104 passive switches, are considered to be operating in "slave" mode. 106 An 802.12 repeater always acts in "master" mode on its local ports, 107 which may connect to end nodes, switch or other device ports acting 108 in "slave" mode, or lower-level repeaters in a cascade. It acts in 109 "slave" mode on cascade ports, which may connect to an upper-level 110 repeater in a cascade, or to switch or other device ports operating 111 in "master" mode. 113 3.3. IEEE 802.12 Training Frames 115 Training frames are special MAC frames that are used only during link 116 initialization. Training frames are initially constructed by the 117 device at the "lower" end of a link, which is the slave mode device 118 for the link. The training frame format is as follows: 120 +----+----+------------+--------------+----------+-----+ 121 | DA | SA | Req Config | Allow Config | Data | FCS | 122 +----+----+------------+--------------+----------+-----+ 124 DA = destination address (six octets) 125 SA = source address (six octets) 126 Req Config = requested configuration (2 octets) 127 Allow Config = allowed configuration (2 octets) 128 Data = data (594 to 675 octets) 129 FCS = frame check sequence (4 octets) 131 Training frames are always sent with a null destination address. To 132 pass training, an end node must use its source address in the source 133 address field of the training frame. A repeater may use a non-null 134 source address if it has one, or it may use a null source address. 136 The requested configuration field allows the slave mode device to 137 inform the master mode device about itself and to request 138 configuration options. The training response frame from the master 139 mode device contains the slave mode device's requested configuration 140 from the training request frame. The currently defined format of the 141 requested configuration field as defined in the IEEE Standard 142 802.12-1995 standard is shown below. Please refer to the most 143 current version of the IEEE document for a more up to date 144 description of this field. In particular, the reserved bits may be 145 used in later versions of the standard. 147 First Octet: Second Octet: 149 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 150 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 151 |v|v|v|r|r|r|r|r| |r|r|r|F|F|P|P|R| 152 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 154 vvv: The version of the 802.12 training protocol with which 155 the training initiator is compliant. The current version 156 is 100. Note that because of the different bit ordering 157 used in IEEE and IETF documents, this value corresponds 158 to version 1. 159 r: Reserved bits (set to zero) 160 FF: 00 = frameType88023 161 01 = frameType88025 162 10 = reserved 163 11 = frameTypeEither 164 PP: 00 = singleAddressMode 165 01 = promiscuousMode 166 10 = reserved 167 11 = reserved 168 R: 0 = the training initiator is an end node 169 1 = the training initiator is a repeater 171 The allowed configuration field allows the master mode device to 172 respond with the allowed configuration. The slave mode device sets 173 the contents of this field to all zero bits. The master mode device 174 sets the allowed configuration field as follows: 176 First Octet: Second Octet: 178 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 179 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 180 |v|v|v|D|C|N|r|r| |r|r|r|F|F|P|P|R| 181 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 183 vvv: The version of the 802.12 training protocol with which 184 the training responder is compliant. The current version 185 is 100. Note that because of the different bit ordering 186 used in IEEE and IETF documents, this value corresponds 187 to version 1. 188 D: 0 = No duplicate address has been detected. 189 1 = Duplicate address has been detected. 190 C: 0 = The requested configuration is compatible with the 191 network and the attached port. 192 1 = The requested configuration is not compatible with 193 the network and/or the attached port. In this case, 194 the FF, PP, and R bits indicate a configuration that 195 would be allowed. 196 N: 0 = Access will be allowed, providing the configuration 197 is compatible (C = 0). 198 1 = Access is not granted because of security 199 restrictions. 200 r: Reserved bits (set to zero). 201 FF: 00 = frameType88023 will be used. 202 01 = frameType88025 will be used. 203 10 = reserved 204 11 = reserved 205 PP: 00 = singleAddressMode 206 01 = promiscuousMode 207 10 = reserved 208 11 = reserved 209 R: 0 = Requested access as an end node is allowed. 210 1 = Requested access as a repeater is allowed. 212 Again, note that the most recent version of the IEEE 802.12 standard 213 should be consulted for the most up to date definition of the 214 requested configuration and allowed configuration fields. 216 The data field contains between 594 and 675 octets and is filled in 217 by the training initiator. The first 55 octets may be used for 218 vendor specific protocol information. The remaining octets are all 219 zeros. The length of the training frame combined with the 220 requirement that 24 consecutive training frames be exchanged without 221 error to complete training ensures that marginal links will not 222 complete training. 224 3.4. Structure of the MIB 226 Objects in this MIB are arranged into packages, each of which 227 contains a set of related objects within a broad functional category. 228 Objects within a package are generally defined under the same OID 229 subtree. These packages are intended for organizational convenience 230 ONLY, and have no relation to the conformance groups defined later in 231 the document. 233 3.4.1. Basic Definitions 235 The basic definitions include objects for managing the basic status 236 and control parameters for each repeater within the managed system, 237 for the port groups within the managed system, and for the individual 238 ports themselves. 240 3.4.2. Monitor Definitions 242 The monitor definitions include monitoring statistics for each 243 repeater within the system and for individual ports. 245 3.4.3. Address Tracking Definitions 247 This collection includes objects for tracking the MAC addresses of 248 the DTEs attached to the ports within the system. 250 Note that this MIB also includes by reference a collection of objects 251 from the 802.3 Repeater MIB which may be used for mapping the 252 topology of a network. These definitions are based on a technology 253 which has been patented by Hewlett-Packard Company (HP). HP has 254 granted rights to this technology to implementors of this MIB. See 255 [8] and [9] for details. 257 3.5. Relationship to other MIBs 259 3.5.1. Relationship to MIB-II 261 It is assumed that a repeater implementing this MIB will also 262 implement (at least) the 'system' group defined in MIB-II [5]. 264 3.5.1.1. Relationship to the 'system' group 266 In MIB-II, the 'system' group is defined as being mandatory for all 267 systems such that each managed entity contains one instance of each 268 object in the 'system' group. Thus, those objects apply to the 269 entity even if the entity's sole functionality is management of 270 repeaters. 272 3.5.1.2. Relationship to the 'interfaces' group 274 In MIB-II, the 'interfaces' group is defined as being mandatory for 275 all systems and contains information on an entity's interfaces, where 276 each interface is thought of as being attached to a 'subnetwork'. 277 (Note that this term is not to be confused with 'subnet' which refers 278 to an addressing partitioning scheme used in the Internet suite of 279 protocols.) 281 This Repeater MIB uses the notion of ports on a repeater. The 282 concept of a MIB-II interface has NO specific relationship to a 283 repeater's port. Therefore, the 'interfaces' group applies only to 284 the one (or more) network interfaces on which the entity managing the 285 repeater sends and receives management protocol operations, and does 286 not apply to the repeater's ports. 288 This is consistent with the physical-layer nature of a repeater. An 289 802.12 repeater has an RMAC implementation, which acts as the 290 repeater end of the Demand Priority Access Method, but does not 291 contain a DTE MAC implementation, and does not pass packets up to 292 higher-level protocol entities for processing. 294 (When a network management entity is observing a repeater, it may 295 appear as though the repeater is passing packets to a higher-level 296 protocol entity. However, this is only a means of implementing 297 management, and this passing of management information is not part of 298 the repeater functionality.) 300 3.5.2. Relationship to the 802.3 Repeater MIB 302 An IEEE 802.12 repeater can be configured to operate in either 303 ethernet or token ring framing mode. This only affects the frame 304 format and address bit order of the frames on the wire. An 802.12 305 network does not use the media access protocol for either ethernet or 306 token ring. Instead, IEEE 802.12 defines its own media access 307 protocol, the Demand Priority Access Method (DPAM). 309 There is an existing standards-track MIB module for instrumenting 310 IEEE 802.3 repeaters [7]. That MIB module is designed to instrument 311 the operation of the repeater in a network implementing the 802.3 312 media access protocol. Therefore, much of that MIB does not apply to 313 802.12 repeaters. 315 However, the 802.3 Repeater MIB also contains a collection of objects 316 that may be used to map the topology of a network. These objects are 317 contained in a separable OBJECT-GROUP, are not 802.3-specific, and 318 are considered useful for 802.12 repeaters. In addition, the layer 319 management clause of the IEEE 802.12 specification includes similar 320 functionality. Therefore, vendors of agents for 802.12 repeaters are 321 encouraged to implement the snmpRptrGrpRptrAddrSearch OBJECT-GROUP 322 defined in the 802.3 Repeater MIB. 324 3.6. Mapping of IEEE 802.12 Managed Objects 326 IEEE 802.12 Managed Object Corresponding SNMP Object 328 oRepeater 329 .aCurrentFramingType vgRptrInfoCurrentFramingType 330 .aDesiredFramingType vgRptrInfoDesiredFramingType 331 .aFramingCapability vgRptrInfoFramingCapability 332 .aGroupMap 333 .aMACAddress vgRptrInfoMACAddress 334 .aRepeaterGroupCapacity 335 .aRepeaterHealthData 336 .aRepeaterHealthState vgRptrInfoOperStatus 337 .aRepeaterHealthText 338 .aRepeaterID vgRptrInfoIndex 339 .aRepeaterSearchAddress SNMP-REPEATER-MIB - 340 rptrAddrSearchAddress 341 .aRepeaterSearchGroup SNMP-REPEATER-MIB - 342 rptrAddrSearchGroup 343 .aRepeaterSearchPort SNMP-REPEATER-MIB - 344 rptrAddrSearchPort 345 .aRepeaterSearchState SNMP-REPEATER-MIB - 346 rptrAddrSearchState 347 .aRMACVersion vgRptrInfoTrainingVersion 348 .acExecuteNonDisruptiveSelfTest 349 .acRepeaterSearchAddress SNMP-REPEATER-MIB - 350 rptrAddrSearchAddress 351 .acResetRepeater vgRptrInfoReset 352 .nGroupMapChange 353 .nRepeaterHealth vgRptrHealth 354 .nRepeaterReset vgRptrResetEvent 356 oGroup 357 .aGroupCablesBundled vgRptrGroupCablesBundled 358 .aGroupID vgRptrGroupIndex 359 .aGroupPortCapacity vgRptrGroupPortCapacity 360 .aPortMap 361 .nPortMapChange 363 oPort 364 .aAllowableTrainingType vgRptrPortAllowedTrainType 365 .aBroadcastFramesReceived vgRptrPortBroadcastFrames 366 .aCentralMgmtDetectedDupAddr vgRptrMgrDetectedDupAddress 367 .aDataErrorFramesReceived vgRptrPortDataErrorFrames 368 .aHighPriorityFramesReceived vgRptrPortHighPriorityFrames 369 .aHighPriorityOctetsReceived vgRptrPortHCHighPriorityOctets, or 370 vgRptrPortL32HighPriorityOctets and 371 vgRptrPortU32HighPriorityOctets 372 .aIPMFramesReceived vgRptrPortIPMFrames 373 .aLastTrainedAddress vgRptrAddrLastTrainedAddress 374 .aLastTrainingConfig vgRptrPortLastTrainConfig 375 .aLocalRptrDetectedDupAddr vgRptrRptrDetectedDupAddress 376 .aMediaType 377 Tranceiver MIB issue 378 .aMulticastFramesReceived vgRptrPortMulticastFrames 379 .aNormalPriorityFramesReceived vgRptrPortNormPriorityFrames 380 .aNormalPriorityOctetsReceived vgRptrPortHCNormPriorityOctets, or 381 vgRptrPortL32NormPriorityOctets and 382 vgRptrPortU32NormPriorityOctets 383 .aNullAddressedFramesReceived vgRptrPortNullAddressedFrames 384 .aOctetsInUnreadableFramesRcvd vgRptrPortHCUnreadableOctets, or 385 vgRptrPortL32UnreadableOctets and 386 vgRptrPortU32UnreadableOctets 387 .aOversizeFramesReceived vgRptrPortOversizeFrames 388 .aPortAdministrativeState vgRptrPortAdminStatus 389 .aPortID vgRptrPortIndex 390 .aPortStatus vgRptrPortOperStatus 391 .aPortType vgRptrPortType 392 .aPriorityEnable vgRptrPortPriorityEnable 393 .aPriorityPromotions vgRptrPortPriorityPromotions 394 .aReadableFramesReceived vgRptrPortReadableFrames 395 .aReadableOctetsReceived vgRptrPortHCReadableOctets, or 396 vgRptrPortL32ReadableOctets and 397 vgRptrPortU32ReadableOctets 398 .aSupportedCascadeMode vgRptrPortSupportedCascadeMode 399 .aSupportedPromiscMode vgRptrPortSupportedPromiscMode 400 .aTrainedAddressChanges vgRptrAddrTrainedAddressChanges 401 .aTrainingResult vgRptrPortTrainingResult 402 .aTransitionsIntoTraining vgRptrPortTransitionToTrainings 403 .acPortAdministrativeControl vgRptrPortAdminStatus 405 4. Definitions 407 DOT12-RPTR-MIB DEFINITIONS ::= BEGIN 409 IMPORTS 410 -- NOTE TO RFC EDITOR: When this document is published as 411 -- an RFC, change 'experimental' to 'mib-2' in the 412 -- following import, and delete this comment. 413 experimental, Integer32, Counter32, Counter64, 414 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE 415 FROM SNMPv2-SMI 416 MacAddress, TruthValue, TimeStamp 417 FROM SNMPv2-TC 418 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 419 FROM SNMPv2-CONF; 421 vgRptrMIB MODULE-IDENTITY 422 LAST-UPDATED "9702182114Z" -- February 18, 1997 423 ORGANIZATION "IETF 100VG-AnyLAN Working Group" 424 CONTACT-INFO 425 "WG E-mail: vgmib@hprnd.rose.hp.com 427 Chair: Jeffrey Johnson 428 Postal: cisco Systems, Inc. 429 170 W.Tasman Drive 430 San Jose, CA 94015 431 Tel: +1 408 526 7789 432 E-mail: jjohnson@cisco.com 434 Editor: John Flick 435 Postal: Hewlett Packard Company 436 8000 Foothills Blvd. M/S 5556 437 Roseville, CA 95747-5556 438 Tel: +1 916 785 4018 439 Fax: +1 916 785 3583 440 E-mail: johnf@hprnd.rose.hp.com" 441 DESCRIPTION 442 "This MIB module describes objects for managing 443 IEEE 802.12 repeaters." 444 ::= { experimental 64 } 445 -- NOTE TO RFC EDITOR: When this document is published as 446 -- an RFC, change '{ experimental 64 }' to '{ mib-2 XX }', 447 -- where XX is assigned by IANA, and delete this comment. 449 vgRptrObjects OBJECT IDENTIFIER ::= { vgRptrMIB 1 } 451 vgRptrBasic OBJECT IDENTIFIER ::= { vgRptrObjects 1 } 452 vgRptrBasicRptr OBJECT IDENTIFIER ::= { vgRptrBasic 1 } 454 vgRptrInfoTable OBJECT-TYPE 455 SYNTAX SEQUENCE OF VgRptrInfoEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "A table of information about each non-trivial 460 802.12 repeater in the managed system." 461 ::= { vgRptrBasicRptr 1 } 463 vgRptrInfoEntry OBJECT-TYPE 464 SYNTAX VgRptrInfoEntry 465 MAX-ACCESS not-accessible 466 STATUS current 467 DESCRIPTION 468 "An entry in the table, containing information 469 about a single, non-trivial repeater." 470 INDEX { vgRptrInfoIndex } 471 ::= { vgRptrInfoTable 1 } 473 VgRptrInfoEntry ::= 474 SEQUENCE { 475 vgRptrInfoIndex Integer32, 476 vgRptrInfoMACAddress MacAddress, 477 vgRptrInfoCurrentFramingType INTEGER, 478 vgRptrInfoDesiredFramingType INTEGER, 479 vgRptrInfoFramingCapability INTEGER, 480 vgRptrInfoTrainingVersion INTEGER, 481 vgRptrInfoOperStatus INTEGER, 482 vgRptrInfoReset INTEGER, 483 vgRptrInfoLastChange TimeStamp 484 } 486 vgRptrInfoIndex OBJECT-TYPE 487 SYNTAX Integer32 (1..2147483647) 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "A unique identifier for the repeater for which 492 this entry contains information. The numbering 493 scheme for repeaters is implementation specific." 494 REFERENCE 495 "IEEE Standard 802.12-1995, 13.2.4.2.1, 496 aRepeaterID." 497 ::= { vgRptrInfoEntry 1 } 499 vgRptrInfoMACAddress OBJECT-TYPE 500 SYNTAX MacAddress 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The MAC address used by the repeater when it 505 initiates training on the uplink port. Repeaters 506 are allowed to train with an assigned MAC address 507 or a null (all zeroes) MAC address." 508 REFERENCE 509 "IEEE Standard 802.12-1995, 13.2.4.2.1, 510 aMACAddress." 511 ::= { vgRptrInfoEntry 2 } 513 vgRptrInfoCurrentFramingType OBJECT-TYPE 514 SYNTAX INTEGER { 515 frameType88023(1), 516 frameType88025(2) 517 } 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The type of framing (802.3 or 802.5) currently 522 in use by the repeater." 523 REFERENCE 524 "IEEE Standard 802.12-1995, 13.2.4.2.1, 525 aCurrentFramingType." 526 ::= { vgRptrInfoEntry 3 } 528 vgRptrInfoDesiredFramingType OBJECT-TYPE 529 SYNTAX INTEGER { 530 frameType88023(1), 531 frameType88025(2) 532 } 533 MAX-ACCESS read-write 534 STATUS current 535 DESCRIPTION 536 "The type of framing which will be used by the 537 repeater after the next time it is reset. The 538 value of this object should be preserved across 539 repeater resets and power failures" 540 REFERENCE 541 "IEEE Standard 802.12-1995, 13.2.4.2.1, 542 aDesiredFramingType." 543 ::= { vgRptrInfoEntry 4 } 545 vgRptrInfoFramingCapability OBJECT-TYPE 546 SYNTAX INTEGER { 547 frameType88023(1), 548 frameType88025(2), 549 frameTypeEither(3) 550 } 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "The type of framing this repeater is capable of 555 supporting." 556 REFERENCE 557 "IEEE Standard 802.12-1995, 13.2.4.2.1, 558 aFramingCapability." 559 ::= { vgRptrInfoEntry 5 } 561 vgRptrInfoTrainingVersion OBJECT-TYPE 562 SYNTAX INTEGER (0..7) 563 MAX-ACCESS read-only 564 STATUS current 565 DESCRIPTION 566 "The highest version bits (vvv bits) supported by 567 the repeater during training." 568 REFERENCE 569 "IEEE Standard 802.12-1995, 13.2.4.2.1, 570 aRMACVersion." 571 ::= { vgRptrInfoEntry 6 } 573 vgRptrInfoOperStatus OBJECT-TYPE 574 SYNTAX INTEGER { 575 other(1), 576 ok(2), 577 generalFailure(3) 578 } 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "The vgRptrInfoOperStatus object indicates the 583 operational state of the repeater." 584 REFERENCE 585 "IEEE Standard 802.12-1995, 13.2.4.2.1, 586 aRepeaterHealthState." 587 ::= { vgRptrInfoEntry 7 } 589 vgRptrInfoReset OBJECT-TYPE 590 SYNTAX INTEGER { 591 noReset(1), 592 reset(2) 593 } 594 MAX-ACCESS read-write 595 STATUS current 596 DESCRIPTION 597 "Setting this object to reset(2) causes the 598 repeater to transition to its initial state as 599 specified in clause 12 [IEEE Std 802.12]. 601 Setting this object to noReset(1) has no effect. 602 The agent will always return the value noReset(1) 603 when this object is read. 605 After receiving a request to set this variable to 606 reset(2), the agent is allowed to delay the reset 607 for a short period. For example, the implementor 608 may choose to delay the reset long enough to 609 allow the SNMP response to be transmitted. In 610 any event, the SNMP response must be transmitted. 612 This action does not reset the management 613 counters defined in this document nor does it 614 affect the vgRptrPortAdminStatus parameters. 615 Included in this action is the execution of a 616 disruptive Self-Test with the following 617 characteristics: 619 1) The nature of the tests is not specified. 620 2) The test resets the repeater but without 621 affecting configurable management 622 information about the repeater. 623 3) Packets received during the test may or 624 may not be transferred. 625 4) The test does not interfere with 626 management functions. 628 After performing this self-test, the agent will 629 update the repeater health information (including 630 vgRptrInfoOperStatus), and send a 631 vgRptrResetEvent." 632 REFERENCE 633 "IEEE Standard 802.12-1995, 13.2.4.2.2, 634 acResetRepeater." 635 ::= { vgRptrInfoEntry 8 } 637 vgRptrInfoLastChange OBJECT-TYPE 638 SYNTAX TimeStamp 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "The value of sysUpTime when any of the following 643 conditions occurred: 645 1) agent cold- or warm-started; 646 2) this instance of repeater was created 647 (such as when a device or module was 648 added to the system); 649 3) a change in the value of 650 vgRptrInfoOperStatus; 651 4) ports were added or removed as members of 652 the repeater; or 653 5) any of the counters associated with this 654 repeater had a discontinuity." 655 ::= { vgRptrInfoEntry 9 } 657 vgRptrBasicGroup OBJECT IDENTIFIER ::= { vgRptrBasic 2 } 659 vgRptrBasicGroupTable OBJECT-TYPE 660 SYNTAX SEQUENCE OF VgRptrBasicGroupEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "A table containing information about groups of 665 ports." 666 ::= { vgRptrBasicGroup 1 } 668 vgRptrBasicGroupEntry OBJECT-TYPE 669 SYNTAX VgRptrBasicGroupEntry 670 MAX-ACCESS not-accessible 671 STATUS current 672 DESCRIPTION 673 "An entry in the vgRptrBasicGroupTable, containing 674 information about a single group of ports." 675 INDEX { vgRptrGroupIndex } 676 ::= { vgRptrBasicGroupTable 1 } 678 VgRptrBasicGroupEntry ::= 679 SEQUENCE { 680 vgRptrGroupIndex Integer32, 681 vgRptrGroupObjectID OBJECT IDENTIFIER, 682 vgRptrGroupOperStatus INTEGER, 683 vgRptrGroupPortCapacity Integer32, 684 vgRptrGroupCablesBundled INTEGER 685 } 687 vgRptrGroupIndex OBJECT-TYPE 688 SYNTAX Integer32 (1..2146483647) 689 MAX-ACCESS not-accessible 690 STATUS current 691 DESCRIPTION 692 "This object identifies the group within the 693 system for which this entry contains information. 694 The numbering scheme for groups is implementation 695 specific." 696 REFERENCE 697 "IEEE Standard 802.12-1995, 13.2.4.4.1, 698 aGroupID." 699 ::= { vgRptrBasicGroupEntry 1 } 701 vgRptrGroupObjectID OBJECT-TYPE 702 SYNTAX OBJECT IDENTIFIER 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "The vendor's authoritative identification of the 707 group. This value may be allocated within the 708 SMI enterprises subtree (1.3.6.1.4.1) and 709 provides a straight-forward and unambiguous means 710 for determining what kind of group is being 711 managed. 713 For example, this object could take the value 714 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, 715 Inc.' was assigned the subtree 1.3.6.1.4.1.4242, 716 and had assigned the identifier 717 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 718 6-Port Plug-in Module.'" 719 ::= { vgRptrBasicGroupEntry 2 } 721 vgRptrGroupOperStatus OBJECT-TYPE 722 SYNTAX INTEGER { 723 other(1), 724 operational(2), 725 malfunctioning(3), 726 notPresent(4), 727 underTest(5), 728 resetInProgress(6) 729 } 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "An object that indicates the operational status 734 of the group. 736 A status of notPresent(4) indicates that the 737 group is temporarily or permanently physically 738 and/or logically not a part of the system. It 739 is an implementation-specific matter as to 740 whether the agent effectively removes notPresent 741 entries from the table. 743 A status of operational(2) indicates that the 744 group is functioning, and a status of 745 malfunctioning(3) indicates that the group is 746 malfunctioning in some way." 747 ::= { vgRptrBasicGroupEntry 3 } 749 vgRptrGroupPortCapacity OBJECT-TYPE 750 SYNTAX Integer32 (1..2146483647) 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "The vgRptrGroupPortCapacity is the number of 755 ports that can be contained within the group. 756 Valid range is 1-2147483647. Within each group, 757 the ports are uniquely numbered in the range from 758 1 to vgRptrGroupPortCapacity. 760 Some ports may not be present in the system, in 761 which case the actual number of ports present will 762 be less than the value of vgRptrGroupPortCapacity. 763 The number of ports present is never greater than 764 the value of vgRptrGroupPortCapacity. 766 Note: In practice, this will generally be the 767 number of ports on a module, card, or board, and 768 the port numbers will correspond to numbers marked 769 on the physical embodiment." 770 REFERENCE 771 "IEEE Standard 802.12-1995, 13.2.4.4.1, 772 aGroupPortCapacity." 773 ::= { vgRptrBasicGroupEntry 4 } 775 vgRptrGroupCablesBundled OBJECT-TYPE 776 SYNTAX INTEGER { 777 someCablesBundled(1), 778 noCablesBundled(2) 779 } 780 MAX-ACCESS read-write 781 STATUS current 782 DESCRIPTION 783 "This object is used to indicate whether there are 784 any four-pair UTP links connected to this group 785 that are contained in a cable bundle with multiple 786 four-pair groups (e.g. a 25-pair bundle). Bundled 787 cable may only be used for repeater-to-end node 788 links where the end node is not in promiscuous 789 mode. 791 When a broadcast or multicast packet is received 792 from a port on this group that is not a 793 promiscuous or cascaded port, the packet will be 794 buffered completely before being repeated if 795 this object is set to 'someCablesBundled(1)'. 796 When this object is equal to 'noCablesBundled(2)', 797 all packets received from ports on this group will 798 be repeated as the frame is being received. 800 Note that the value 'someCablesBundled(1)' will 801 work in the vast majority of all installations, 802 regardless of whether or not any cables are 803 physically in a bundle, since packets received 804 from promiscuous and cascaded ports automatically 805 avoid the store and forward. The main situation 806 in which 'noCablesBundled(2)' is beneficial is 807 when there is a large amount of multicast traffic 808 and the cables are not in a bundle. The value of 809 this object should be preserved across repeater 810 resets and power failures." 811 REFERENCE 812 "IEEE Standard 802.12-1995, 13.2.4.4.1, 813 aGroupCablesBundled." 814 ::= { vgRptrBasicGroupEntry 5 } 816 vgRptrBasicPort OBJECT IDENTIFIER ::= { vgRptrBasic 3 } 818 vgRptrBasicPortTable OBJECT-TYPE 819 SYNTAX SEQUENCE OF VgRptrBasicPortEntry 820 MAX-ACCESS not-accessible 821 STATUS current 822 DESCRIPTION 823 "A table containing configuration and status 824 information about 802.12 repeater ports in the 825 system. The number of entries is independent of 826 the number of repeaters in the managed system." 827 ::= { vgRptrBasicPort 1 } 829 vgRptrBasicPortEntry OBJECT-TYPE 830 SYNTAX VgRptrBasicPortEntry 831 MAX-ACCESS not-accessible 832 STATUS current 833 DESCRIPTION 834 "An entry in the vgRptrBasicPortTable, containing 835 information about a single port." 836 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 837 ::= { vgRptrBasicPortTable 1 } 839 VgRptrBasicPortEntry ::= 840 SEQUENCE { 841 vgRptrPortIndex Integer32, 842 vgRptrPortType INTEGER, 843 vgRptrPortAdminStatus INTEGER, 844 vgRptrPortOperStatus INTEGER, 845 vgRptrPortSupportedPromiscMode INTEGER, 846 vgRptrPortSupportedCascadeMode INTEGER, 847 vgRptrPortAllowedTrainType INTEGER, 848 vgRptrPortLastTrainConfig OCTET STRING, 849 vgRptrPortTrainingResult OCTET STRING, 850 vgRptrPortPriorityEnable TruthValue, 851 vgRptrPortRptrInfoIndex Integer32 852 } 854 vgRptrPortIndex OBJECT-TYPE 855 SYNTAX Integer32 (1..2147483647) 856 MAX-ACCESS not-accessible 857 STATUS current 858 DESCRIPTION 859 "This object identifies the port within the group 860 for which this entry contains information. This 861 identifies the port independently from the 862 repeater it may be attached to. The numbering 863 scheme for ports is implementation specific; 864 however, this value can never be greater than 865 vgRptrGroupPortCapacity for the associated group." 866 REFERENCE 867 "IEEE Standard 802.12-1995, 13.2.4.5.1, 868 aPortID." 869 ::= { vgRptrBasicPortEntry 1 } 871 vgRptrPortType OBJECT-TYPE 872 SYNTAX INTEGER { 873 cascadeExternal(1), 874 cascadeInternal(2), 875 localExternal(3), 876 localInternal(4) 877 } 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "Describes the type of port. One of the 882 following: 884 cascadeExternal - Port is an uplink with 885 physical connections which 886 are externally visible 887 cascadeInternal - Port is an uplink with 888 physical connections which 889 are not externally visible, 890 such as a connection to an 891 internal backplane in a 892 chassis 893 localExternal - Port is a downlink or local 894 port with externally 895 visible connections 896 localInternal - Port is a downlink or local 897 port with connections which 898 are not externally visible, 899 such as a connection to an 900 internal agent 902 'internal' is used to identify ports which place 903 traffic into the repeater, but do not have any 904 external connections. Note that both DTE and 905 cascaded repeater downlinks are considered 906 'local' ports." 907 REFERENCE 908 "IEEE Standard 802.12-1995, 13.2.4.5.1, 909 aPortType." 910 ::= { vgRptrBasicPortEntry 2 } 912 vgRptrPortAdminStatus OBJECT-TYPE 913 SYNTAX INTEGER { 914 enabled(1), 915 disabled(2) 916 } 917 MAX-ACCESS read-write 918 STATUS current 919 DESCRIPTION 920 "Port enable/disable function. Enabling a 921 disabled port will cause training to be 922 initiated by the training initiator (the slave 923 mode device) on the link. Setting this object to 924 disabled(2) disables the port. 926 A disabled port neither transmits nor receives. 927 Once disabled, a port must be explicitly enabled 928 to restore operation. A port which is disabled 929 when power is lost or when a reset is exerted 930 shall remain disabled when normal operation 931 resumes." 932 REFERENCE 933 "IEEE Standard 802.12-1995, 13.2.4.5.1, 934 aPortAdministrativeState." 935 ::= { vgRptrBasicPortEntry 3 } 937 vgRptrPortOperStatus OBJECT-TYPE 938 SYNTAX INTEGER { 939 active(1), 940 inactive(2), 941 training(3) 942 } 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "Current status for the port as specified by the 947 PORT_META_STATE in the port process module of 948 clause 12 [IEEE Std 802.12]. 950 During initialization or any link warning 951 conditions, vgRptrPortStatus will be 952 'inactive(2)'. 954 When Training_Up is received by the repeater on a 955 local port (or when Training_Down is received on 956 a cascade port), vgRptrPortStatus will change to 957 'training(3)' and vgRptrTrainingResult can be 958 monitored to see the detailed status regarding 959 training. 961 When 24 consecutive good FCS packets are exchanged 962 and the configuration bits are OK, 963 vgRptrPortStatus will change to 'active(1)'. 965 A disabled port shall have a port status of 966 'inactive(2)'." 967 REFERENCE 968 "IEEE Standard 802.12, 13.2.4.5.1, 969 aPortStatus." 970 ::= { vgRptrBasicPortEntry 4 } 972 vgRptrPortSupportedPromiscMode OBJECT-TYPE 973 SYNTAX INTEGER { 974 singleModeOnly(1), 975 singleOrPromiscMode(2), 976 promiscModeOnly(3) 977 } 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "This object describes whether the port hardware 982 is capable of supporting promiscuous mode, single 983 address mode (i.e., repeater filters unicasts not 984 addressed to the end station attached to this 985 port), or both. A port for which vgRptrPortType 986 is equal to 'cascadeInternal' or 'cascadeExternal' 987 will always have a value of 'promiscModeOnly' for 988 this object." 989 REFERENCE 990 "IEEE Standard 802.12-1995, 13.2.4.5.1, 991 aSupportedPromiscMode." 992 ::= { vgRptrBasicPortEntry 5 } 994 vgRptrPortSupportedCascadeMode OBJECT-TYPE 995 SYNTAX INTEGER { 996 endNodesOnly(1), 997 endNodesOrRepeaters(2), 998 cascadePort(3) 999 } 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "This object describes whether the port hardware 1004 is capable of supporting cascaded repeaters, end 1005 nodes, or both. A port for which vgRptrPortType 1006 is equal to 'cascadeInternal' or 1007 'cascadeExternal' will always have a value of 1008 'cascadePort' for this object." 1009 REFERENCE 1010 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1011 aSupportedCascadeMode." 1012 ::= { vgRptrBasicPortEntry 6 } 1014 vgRptrPortAllowedTrainType OBJECT-TYPE 1015 SYNTAX INTEGER { 1016 allowEndNodesOnly(1), 1017 allowPromiscuousEndNodes(2), 1018 allowEndNodesOrRepeaters(3), 1019 allowAnything(4) 1020 } 1021 MAX-ACCESS read-write 1022 STATUS current 1023 DESCRIPTION 1024 "This security object is set by the network 1025 manager to configure what type of device is 1026 permitted to connect to the port. One of the 1027 following values: 1029 allowEndNodesOnly - only non- 1030 promiscuous end 1031 nodes permitted. 1032 allowPromiscuousEndNodes - promiscuous or 1033 non-promiscuous 1034 end nodes 1035 permitted 1036 allowEndNodesOrRepeaters - repeaters or non- 1037 promiscuous end 1038 nodes permitted 1039 allowAnything - repeaters, 1040 promiscuous or 1041 non-promiscuous 1042 end nodes 1043 permitted 1045 For a port for which vgRptrPortType is equal to 1046 'cascadeInternal' or 'cascadeExternal', the 1047 corresponding instance of this object may not be 1048 set to 'allowEndNodesOnly' or 1049 'allowPromiscuousEndNodes'. 1051 The agent must reject a SET of this object if the 1052 value includes no capabilities that are 1053 supported by this port's hardware, as defined by 1054 the values of the corresponding instances of 1055 vgRptrPortSupportedPromiscMode and 1056 vgRptrPortSupportedCascadeMode. 1058 Note that vgRptrPortSupportPromiscMode and 1059 vgRptrPortSupportedCascadeMode represent what the 1060 port hardware is capable of supporting. 1061 vgRptrPortAllowedTrainType is used for setting an 1062 administrative policy for a port. The actual set 1063 of training configurations that will be allowed 1064 to succeed on a port is the intersection of what 1065 the hardware will support and what is 1066 administratively allowed. The above requirement 1067 on what values may be set to this object says that 1068 the intersection of what is supported and what is 1069 allowed must be non-empty. In other words, it 1070 must not result in a situation in which nothing 1071 would be allowed to train on that port. However, 1072 a value can be set to this object as long as the 1073 combination of this object and what is supported 1074 by the hardware would still leave at least one 1075 configuration that could successfully train on the 1076 port." 1078 REFERENCE 1079 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1080 aAllowableTrainingType." 1081 ::= { vgRptrBasicPortEntry 7 } 1083 vgRptrPortLastTrainConfig OBJECT-TYPE 1084 SYNTAX OCTET STRING (SIZE(2)) 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "This object is a 16 bit field. For local ports, 1089 this object contains the requested configuration 1090 field from the most recent error-free training 1091 request frame sent by the device connected to 1092 the port. For cascade ports, this object contains 1093 the responder's allowed configuration field from 1094 the most recent error-free training response frame 1095 received in response to training initiated by this 1096 repeater. The format of the current version of 1097 this field is described in section 3.2. Please 1098 refer to the most recent version of the IEEE 1099 802.12 standard for the most up-to-date definition 1100 of the format of this object." 1101 REFERENCE 1102 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1103 aLastTrainingConfig." 1104 ::= { vgRptrBasicPortEntry 8 } 1106 vgRptrPortTrainingResult OBJECT-TYPE 1107 SYNTAX OCTET STRING (SIZE(3)) 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "This 18 bit field is used to indicate the result 1112 of training. It contains two bits which indicate 1113 if error-free training frames have been received, 1114 and it also contains the 16 bits of the allowed 1115 configuration field from the most recent 1116 error-free training response frame on the port. 1118 First Octet: Second and Third Octets: 1119 7 6 5 4 3 2 1 0 1120 +-+-+-+-+-+-+-+-+-----------------------------+ 1121 |0|0|0|0|0|0|V|G| allowed configuration field | 1122 +-+-+-+-+-+-+-+-+-----------------------------+ 1124 V: Valid: set when at least one error-free 1125 training frame has been received. 1127 Indicates the 16 training configuration 1128 bits in vgRptrPortLastTrainConfig and 1129 vgRptrPortTrainingResult contain valid 1130 information. This bit is cleared when 1131 vgRptrPortStatus transitions to the 1132 'inactive' or 'training' state. 1133 G: LinkGood: indicates the link hardware is 1134 OK. Set if 24 consecutive error-free 1135 training packets have been exchanged. 1136 Cleared when a training packet with 1137 errors is received, or when 1138 vgRptrPortStatus transitions to the 1139 'inactive' or 'training' state. 1141 The format of the current version of the allowed 1142 configuration field is described in section 3.2. 1143 Please refer to the most recent version of the 1144 IEEE 802.12 standard for the most up-to-date 1145 definition of the format of this field. 1147 If the port is in training, a management station 1148 can examine this object to see if any training 1149 packets have been passed successfully. If there 1150 have been any good training packets, the Valid 1151 bit will be set and the management station can 1152 examine the allowed configuration field to see if 1153 there is a duplicate address, configuration, or 1154 security problem. 1156 Note that on a repeater local port, this repeater 1157 generates the training response bits, while on 1158 a cascade port, the device at the upper end of 1159 the link originated the training response bits." 1160 REFERENCE 1161 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1162 aTrainingResult." 1163 ::= { vgRptrBasicPortEntry 9 } 1165 vgRptrPortPriorityEnable OBJECT-TYPE 1166 SYNTAX TruthValue 1167 MAX-ACCESS read-write 1168 STATUS current 1169 DESCRIPTION 1170 "A configuration flag used to determine whether 1171 the repeater will service high priority requests 1172 received on the port as high priority or normal 1173 priority. When 'false', high priority requests 1174 on this port will be serviced as normal priority. 1176 The value of this object should be preserved 1177 across repeater resets and power failures. 1179 The setting of this object has no effect on a 1180 cascade port. Also note that the setting of this 1181 object has no effect on a port connected to a 1182 cascaded repeater. In both of these cases, this 1183 setting is treated as always 'true'. The value 1184 'false' only has an effect when the port is a 1185 localInternal or localExternal port connected to 1186 an end node." 1187 REFERENCE 1188 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1189 aPriorityEnable." 1190 ::= { vgRptrBasicPortEntry 10 } 1192 vgRptrPortRptrInfoIndex OBJECT-TYPE 1193 SYNTAX Integer32 (0..2147483647) 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION 1197 "This object identifies the repeater that this 1198 port is currently mapped to. The repeater 1199 identified by a particular value of this object 1200 is the same as that identified by the same value 1201 of vgRptrInfoIndex. A value of zero indicates 1202 that this port is not currently mapped to any 1203 repeater." 1204 ::= { vgRptrBasicPortEntry 11 } 1206 vgRptrMonitor OBJECT IDENTIFIER ::= { vgRptrObjects 2 } 1208 vgRptrMonRepeater OBJECT IDENTIFIER ::= { vgRptrMonitor 1 } 1210 vgRptrMonitorTable OBJECT-TYPE 1211 SYNTAX SEQUENCE OF VgRptrMonitorEntry 1212 MAX-ACCESS not-accessible 1213 STATUS current 1214 DESCRIPTION 1215 "A table of performance and error statistics for 1216 each repeater in the system. The instance of the 1217 vgRptrInfoLastChange associated with a repeater 1218 is used to indicate possible discontinuities of 1219 the counters in this table that are associated 1220 with the same repeater." 1221 ::= { vgRptrMonRepeater 1 } 1223 vgRptrMonitorEntry OBJECT-TYPE 1224 SYNTAX VgRptrMonitorEntry 1225 MAX-ACCESS not-accessible 1226 STATUS current 1227 DESCRIPTION 1228 "An entry in the table, containing statistics 1229 for a single repeater." 1230 INDEX { vgRptrInfoIndex } 1231 ::= { vgRptrMonitorTable 1 } 1233 VgRptrMonitorEntry ::= 1234 SEQUENCE { 1235 vgRptrMonTotalReadableFrames Counter32, 1236 vgRptrMonL32TotalReadableOctets Counter32, 1237 vgRptrMonU32TotalReadableOctets Counter32, 1238 vgRptrMonHCTotalReadableOctets Counter64, 1239 vgRptrMonTotalErrors Counter32 1240 } 1242 vgRptrMonTotalReadableFrames OBJECT-TYPE 1243 SYNTAX Counter32 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "The total number of good frames of valid frame 1248 length that have been received on all ports in 1249 this repeater. If an implementation cannot 1250 obtain a count of frames as seen by the repeater 1251 itself, this counter may be implemented as the 1252 summation of the values of the 1253 vgRptrPortReadableFrames counters for all of the 1254 ports in this repeater. 1256 This counter may experience a discontinuity when 1257 the value of the corresponding instance of 1258 vgRptrInfoLastChange changes." 1259 ::= { vgRptrMonitorEntry 1 } 1261 vgRptrMonL32TotalReadableOctets OBJECT-TYPE 1262 SYNTAX Counter32 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "The total number of octets contained in good 1267 frames that have been received on all ports in 1268 this repeater. If an implementation cannot 1269 obtain a count of octets as seen by the repeater 1270 itself, this counter may be implemented as the 1271 summation of the values of the 1272 vgRptrPortL32ReadableOctets counters for all of 1273 the ports in this repeater. 1275 Note that this counter can roll over very 1276 quickly. A management station is advised to 1277 also poll the vgRptrU32TotalReadableOctets 1278 object, or to use the 64-bit counter defined by 1279 vgRptrMonHCTotalReadableOctets instead of the 1280 two 32-bit counters. 1282 This two-counter mechanism is provided for those 1283 network management protocols that do not support 1284 64-bit counters (e.g. SNMPv1). Note that 1285 retrieval of these two counters in the same PDU 1286 is NOT guaranteed to be atomic. 1288 This counter may experience a discontinuity when 1289 the value of the corresponding instance of 1290 vgRptrInfoLastChange changes." 1291 ::= { vgRptrMonitorEntry 2 } 1293 vgRptrMonU32TotalReadableOctets OBJECT-TYPE 1294 SYNTAX Counter32 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "The total number of octets contained in good 1299 frames that have been received on all ports in 1300 this repeater, modulo 2**32. That is, it 1301 contains the upper 32 bits of a 64-bit counter, 1302 of which the lower 32 bits are contained in the 1303 corresponding instance of 1304 vgRptrL32MonTotalReadableOctets. If an 1305 implementation cannot obtain a count of octets 1306 as seen by the repeater itself, this counter may 1307 be implemented as the summation of the values of 1308 the vgRptrL32PortReadableOctets counters combined 1309 with the corresponding 1310 vgRptrPortU32ReadableOctets counters for all of 1311 the ports in this repeater. 1313 This two-counter mechanism is provided for those 1314 network management protocols that do not support 1315 64-bit counters (e.g. SNMPv1). Note that 1316 retrieval of these two counters in the same PDU 1317 is NOT guaranteed to be atomic. 1319 This counter may experience a discontinuity when 1320 the value of the corresponding instance of 1321 vgRptrInfoLastChange changes." 1322 ::= { vgRptrMonitorEntry 3 } 1324 vgRptrMonHCTotalReadableOctets OBJECT-TYPE 1325 SYNTAX Counter64 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "The total number of octets contained in good 1330 frames that have been received on all ports in 1331 this repeater. If an implementation cannot 1332 obtain a count of octets as seen by the repeater 1333 itself, this counter may be implemented as the 1334 summation of the values of the 1335 vgRptrPortHCReadableOctets counters for all of the 1336 ports in this repeater. 1338 This counter is a 64 bit version of 1339 vgRptrL32MonTotalOctets and 1340 vgRptrU32MonTotalOctets. It should be used by 1341 Network Management protocols which support 64 bit 1342 counters (e.g. SNMPv2). 1344 This counter may experience a discontinuity when 1345 the value of the corresponding instance of 1346 vgRptrInfoLastChange changes." 1347 ::= { vgRptrMonitorEntry 4 } 1349 vgRptrMonTotalErrors OBJECT-TYPE 1350 SYNTAX Counter32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The total number of errors which have occurred on 1355 all of the ports in this repeater. If an 1356 implementation cannot obtain a count of these 1357 errors as seen by the repeater itself, this 1358 counter may be implemented as the summation of the 1359 values of the vgRptrPortIPMFrames, 1360 vgRptrPortOversizeFrames, and 1361 vgRptrPortDataErrorFrames counters for all of the 1362 ports in this repeater. 1364 This counter may experience a discontinuity when 1365 the value of the corresponding instance of 1366 vgRptrInfoLastChange changes." 1368 ::= { vgRptrMonitorEntry 5 } 1370 vgRptrMonGroup OBJECT IDENTIFIER ::= { vgRptrMonitor 2 } 1371 -- Currently unused 1373 vgRptrMonPort OBJECT IDENTIFIER ::= { vgRptrMonitor 3 } 1375 vgRptrMonPortTable OBJECT-TYPE 1376 SYNTAX SEQUENCE OF VgRptrMonPortEntry 1377 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1380 "A table of performance and error statistics for 1381 the ports. The columnar object 1382 vgRptrPortLastChange is used to indicate possible 1383 discontinuities of counter type columnar objects 1384 in this table." 1385 ::= { vgRptrMonPort 1 } 1387 vgRptrMonPortEntry OBJECT-TYPE 1388 SYNTAX VgRptrMonPortEntry 1389 MAX-ACCESS not-accessible 1390 STATUS current 1391 DESCRIPTION 1392 "An entry in the vgRptrMonPortTable, containing 1393 performance and error statistics for a single 1394 port." 1395 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 1396 ::= { vgRptrMonPortTable 1 } 1398 VgRptrMonPortEntry ::= 1399 SEQUENCE { 1400 vgRptrPortReadableFrames Counter32, 1401 vgRptrPortL32ReadableOctets Counter32, 1402 vgRptrPortU32ReadableOctets Counter32, 1403 vgRptrPortHCReadableOctets Counter64, 1404 vgRptrPortL32UnreadableOctets Counter32, 1405 vgRptrPortU32UnreadableOctets Counter32, 1406 vgRptrPortHCUnreadableOctets Counter64, 1407 vgRptrPortHighPriorityFrames Counter32, 1408 vgRptrPortL32HighPriorityOctets Counter32, 1409 vgRptrPortU32HighPriorityOctets Counter32, 1410 vgRptrPortHCHighPriorityOctets Counter64, 1411 vgRptrPortNormPriorityFrames Counter32, 1412 vgRptrPortL32NormPriorityOctets Counter32, 1413 vgRptrPortU32NormPriorityOctets Counter32, 1414 vgRptrPortHCNormPriorityOctets Counter64, 1415 vgRptrPortBroadcastFrames Counter32, 1416 vgRptrPortMulticastFrames Counter32, 1417 vgRptrPortNullAddressedFrames Counter32, 1418 vgRptrPortIPMFrames Counter32, 1419 vgRptrPortOversizeFrames Counter32, 1420 vgRptrPortDataErrorFrames Counter32, 1421 vgRptrPortPriorityPromotions Counter32, 1422 vgRptrPortTransitionToTrainings Counter32, 1423 vgRptrPortLastChange TimeStamp 1424 } 1426 vgRptrPortReadableFrames OBJECT-TYPE 1427 SYNTAX Counter32 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "This object is the number of good frames of 1432 valid frame length that have been received on 1433 this port. This counter is incremented by one 1434 for each frame received on the port which is not 1435 counted by any of the following error counters: 1436 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1437 vgRptrPortNullAddressedFrames, or 1438 vgRptrPortDataErrorFrames. 1440 This counter may experience a discontinuity when 1441 the value of the corresponding instance of 1442 vgRptrPortLastChange changes." 1443 REFERENCE 1444 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1445 aReadableFramesReceived." 1446 ::= { vgRptrMonPortEntry 1 } 1448 vgRptrPortL32ReadableOctets OBJECT-TYPE 1449 SYNTAX Counter32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "This object is a count of the number of octets 1454 contained in good frames that have been received 1455 on this port. This counter is incremented by 1456 OctetCount for each frame received on this port 1457 which has been determined to be a readable frame 1458 (i.e. each frame counted by 1459 vgRptrPortReadableFrames). 1461 Note that this counter can roll over very 1462 quickly. A management station is advised to 1463 also poll the vgRptrPortU32ReadableOctets object, 1464 or to use the 64-bit counter defined by 1465 vgRptrPortHCReadableOctets instead of the two 1466 32-bit counters. 1468 This two-counter mechanism is provided for those 1469 network management protocols that do not support 1470 64-bit counters (e.g. SNMPv1). Note that 1471 retrieval of these two counters in the same PDU 1472 is NOT guaranteed to be atomic. 1474 This counter may experience a discontinuity when 1475 the value of the corresponding instance of 1476 vgRptrPortLastChange changes." 1477 REFERENCE 1478 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1479 aReadableOctetsReceived." 1480 ::= { vgRptrMonPortEntry 2 } 1482 vgRptrPortU32ReadableOctets OBJECT-TYPE 1483 SYNTAX Counter32 1484 MAX-ACCESS read-only 1485 STATUS current 1486 DESCRIPTION 1487 "This object is a count of the number of octets 1488 contained in good frames that have been received 1489 on this port, modulo 2**32. That is, it contains 1490 the upper 32 bits of a 64-bit counter, of which 1491 the lower 32 bits are contained in the 1492 corresponding instance of the 1493 vgRptrPortL32ReadableOctets object. 1495 This two-counter mechanism is provided for those 1496 network management protocols that do not support 1497 64-bit counters (e.g. SNMPv1). Note that 1498 retrieval of these two counters in the same PDU 1499 is NOT guaranteed to be atomic. 1501 This counter may experience a discontinuity when 1502 the value of the corresponding instance of 1503 vgRptrPortLastChange changes." 1504 REFERENCE 1505 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1506 aReadableOctetsReceived." 1507 ::= { vgRptrMonPortEntry 3 } 1509 vgRptrPortHCReadableOctets OBJECT-TYPE 1510 SYNTAX Counter64 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "This object is a count of the number of octets 1515 contained in good frames that have been received 1516 on this port. This counter is incremented by 1517 OctetCount for each frame received on this port 1518 which has been determined to be a readable frame 1519 (i.e. each frame counted by 1520 vgRptrPortReadableFrames). 1522 This counter is a 64 bit version of 1523 vgRptrPortL32ReadableOctets and 1524 vgRptrPortU32ReadableOctets. It should be used by 1525 Network Management protocols which support 64 bit 1526 counters (e.g. SNMPv2). 1528 This counter may experience a discontinuity when 1529 the value of the corresponding instance of 1530 vgRptrPortLastChange changes." 1531 REFERENCE 1532 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1533 aReadableOctetsReceived." 1534 ::= { vgRptrMonPortEntry 4 } 1536 vgRptrPortL32UnreadableOctets OBJECT-TYPE 1537 SYNTAX Counter32 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "This object is a count of the number of octets 1542 contained in invalid frames that have been 1543 received on this port. This counter is 1544 incremented by OctetCount for each frame received 1545 on this port which is counted by 1546 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1547 vgRptrPortNullAddressedFrames, or 1548 vgRptrPortDataErrorFrames. This counter can be 1549 combined with vgRptrPortL32ReadableOctets to 1550 calculate network utilization. 1552 Note that this counter can roll over very 1553 quickly. A management station is advised to 1554 also poll the vgRptrPortU32UnreadableOctets 1555 object, or to use the 64-bit counter defined by 1556 vgRptrPortHCUnreadableOctets instead of the two 1557 32-bit counters. 1559 This two-counter mechanism is provided for those 1560 network management protocols that do not support 1561 64-bit counters (e.g. SNMPv1). Note that 1562 retrieval of these two counters in the same PDU 1563 is NOT guaranteed to be atomic. 1565 This counter may experience a discontinuity when 1566 the value of the corresponding instance of 1567 vgRptrPortLastChange changes." 1568 REFERENCE 1569 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1570 aOctetsInUnreadableFramesRcvd." 1571 ::= { vgRptrMonPortEntry 5 } 1573 vgRptrPortU32UnreadableOctets OBJECT-TYPE 1574 SYNTAX Counter32 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1578 "This object is a count of the number of octets 1579 contained in invalid frames that have been 1580 received on this port, modulo 2**32. That is, it 1581 contains the upper 32 bits of a 64-bit counter, 1582 of which lower 32 bits are contained in the 1583 corresponding instance of the 1584 vgRptrPortL32UnreadableOctets object. 1586 This two-counter mechanism is provided for those 1587 network management protocols that do not support 1588 64-bit counters (e.g. SNMPv1). Note that 1589 retrieval of these two counters in the same PDU 1590 is NOT guaranteed to be atomic. 1592 This counter may experience a discontinuity when 1593 the value of the corresponding instance of 1594 vgRptrPortLastChange changes." 1595 REFERENCE 1596 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1597 aOctetsInUnreadableFramesRcvd." 1598 ::= { vgRptrMonPortEntry 6 } 1600 vgRptrPortHCUnreadableOctets OBJECT-TYPE 1601 SYNTAX Counter64 1602 MAX-ACCESS read-only 1603 STATUS current 1604 DESCRIPTION 1605 "This object is a count of the number of octets 1606 contained in invalid frames that have been 1607 received on this port. This counter is 1608 incremented by OctetCount for each frame received 1609 on this port which is counted by 1610 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1611 vgRptrPortNullAddressedFrames, or 1612 vgRptrPortDataErrorFrames. This counter can be 1613 combined with vgRptrPortHCReadableOctets to 1614 calculate network utilization. 1616 This counter is a 64 bit version of 1617 vgRptrPortL32UnreadableOctets and 1618 vgRptrPortU32UnReadableOctets. It should be used 1619 by Network Management protocols which support 64 1620 bit counters (e.g. SNMPv2). 1622 This counter may experience a discontinuity when 1623 the value of the corresponding instance of 1624 vgRptrPortLastChange changes." 1625 REFERENCE 1626 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1627 aOctetsInUnreadableFramesRcvd." 1628 ::= { vgRptrMonPortEntry 7 } 1630 vgRptrPortHighPriorityFrames OBJECT-TYPE 1631 SYNTAX Counter32 1632 MAX-ACCESS read-only 1633 STATUS current 1634 DESCRIPTION 1635 "This object is a count of high priority frames 1636 that have been received on this port. This 1637 counter is incremented by one for each high 1638 priority frame received on this port. This 1639 counter includes both good and bad high priority 1640 frames, as well as high priority training frames. 1641 This counter does not include normal priority 1642 frames which were priority promoted. 1644 This counter may experience a discontinuity when 1645 the value of the corresponding instance of 1646 vgRptrPortLastChange changes." 1647 REFERENCE 1648 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1649 aHighPriorityFramesReceived." 1650 ::= { vgRptrMonPortEntry 8 } 1652 vgRptrPortL32HighPriorityOctets OBJECT-TYPE 1653 SYNTAX Counter32 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 Note that this counter can roll over very 1665 quickly. A management station is advised to 1666 also poll the vgRptrPortU32HighPriorityOctets 1667 object, or to use the 64-bit counter defined by 1668 vgRptrPortHCHighPriorityOctets instead of the two 1669 32-bit counters. 1671 This two-counter mechanism is provided for those 1672 network management protocols that do not support 1673 64-bit counters (e.g. SNMPv1). Note that 1674 retrieval of these two counters in the same PDU 1675 is NOT guaranteed to be atomic. 1677 This counter may experience a discontinuity when 1678 the value of the corresponding instance of 1679 vgRptrPortLastChange changes." 1680 REFERENCE 1681 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1682 aHighPriorityOctetsReceived." 1683 ::= { vgRptrMonPortEntry 9 } 1685 vgRptrPortU32HighPriorityOctets OBJECT-TYPE 1686 SYNTAX Counter32 1687 MAX-ACCESS read-only 1688 STATUS current 1689 DESCRIPTION 1690 "This object is a count of the number of octets 1691 contained in high priority frames that have been 1692 received on this port, modulo 2**32. That is, it 1693 contains the upper 32 bits of a 64-bit counter, 1694 of which lower 32 bits are contained in the 1695 corresponding instance of the 1696 vgRptrPortL32HighPriorityOctets object. 1698 This two-counter mechanism is provided for those 1699 network management protocols that do not support 1700 64-bit counters (e.g. SNMPv1). Note that 1701 retrieval of these two counters in the same PDU 1702 is NOT guaranteed to be atomic. 1704 This counter may experience a discontinuity when 1705 the value of the corresponding instance of 1706 vgRptrPortLastChange changes." 1707 REFERENCE 1708 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1709 aHighPriorityOctetsReceived." 1710 ::= { vgRptrMonPortEntry 10 } 1712 vgRptrPortHCHighPriorityOctets OBJECT-TYPE 1713 SYNTAX Counter64 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "This object is a count of the number of octets 1718 contained in high priority frames that have been 1719 received on this port. This counter is 1720 incremented by OctetCount for each frame received 1721 on this port which is counted by 1722 vgRptrPortHighPriorityFrames. 1724 This counter is a 64 bit version of 1725 vgRptrPortL32HighPriorityOctets and 1726 vgRptrPortU32HighPriorityOctets. It should be 1727 used by Network Management protocols which support 1728 64 bit counters (e.g. SNMPv2). 1730 This counter may experience a discontinuity when 1731 the value of the corresponding instance of 1732 vgRptrPortLastChange changes." 1733 REFERENCE 1734 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1735 aHighPriorityOctetsReceived." 1736 ::= { vgRptrMonPortEntry 11 } 1738 vgRptrPortNormPriorityFrames OBJECT-TYPE 1739 SYNTAX Counter32 1740 MAX-ACCESS read-only 1741 STATUS current 1742 DESCRIPTION 1743 "This object is a count of normal priority frames 1744 that have been received on this port. This 1745 counter is incremented by one for each normal 1746 priority frame received on this port. This 1747 counter includes both good and bad normal 1748 priority frames, as well as normal priority 1749 training frames and normal priority frames which 1750 were priority promoted. 1752 This counter may experience a discontinuity when 1753 the value of the corresponding instance of 1754 vgRptrPortLastChange changes." 1755 REFERENCE 1756 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1757 aNormalPriorityFramesReceived." 1758 ::= { vgRptrMonPortEntry 12 } 1760 vgRptrPortL32NormPriorityOctets OBJECT-TYPE 1761 SYNTAX Counter32 1762 MAX-ACCESS read-only 1763 STATUS current 1764 DESCRIPTION 1765 "This object is a count of the number of octets 1766 contained in normal priority frames that have 1767 been received on this port. This counter is 1768 incremented by OctetCount for each frame received 1769 on this port which is counted by 1770 vgRptrPortNormPriorityFrames. 1772 Note that this counter can roll over very 1773 quickly. A management station is advised to 1774 also poll the vgRptrPortU32NormPriorityOctets 1775 object, or to use the 64-bit counter defined by 1776 vgRptrPortHCNormPriorityOctets instead of the two 1777 32-bit counters. 1779 This two-counter mechanism is provided for those 1780 network management protocols that do not support 1781 64-bit counters (e.g. SNMPv1). Note that 1782 retrieval of these two counters in the same PDU 1783 is NOT guaranteed to be atomic. 1785 This counter may experience a discontinuity when 1786 the value of the corresponding instance of 1787 vgRptrPortLastChange changes." 1788 REFERENCE 1789 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1790 aNormalPriorityOctetsReceived." 1791 ::= { vgRptrMonPortEntry 13 } 1793 vgRptrPortU32NormPriorityOctets OBJECT-TYPE 1794 SYNTAX Counter32 1795 MAX-ACCESS read-only 1796 STATUS current 1797 DESCRIPTION 1798 "This object is a count of the number of octets 1799 contained in normal priority frames that have 1800 been received on this port, modulo 2**32. That 1801 is, it contains the upper 32 bits of a 64-bit 1802 counter, of which lower 32 bits are contained in 1803 the corresponding instance of the 1804 vgRptrPortL32NormPriorityOctets object. 1806 This two-counter mechanism is provided for those 1807 network management protocols that do not support 1808 64-bit counters (e.g. SNMPv1). Note that 1809 retrieval of these two counters in the same PDU 1810 is NOT guaranteed to be atomic. 1812 This counter may experience a discontinuity when 1813 the value of the corresponding instance of 1814 vgRptrPortLastChange changes." 1815 REFERENCE 1816 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1817 aNormalPriorityOctetsReceived." 1818 ::= { vgRptrMonPortEntry 14 } 1820 vgRptrPortHCNormPriorityOctets OBJECT-TYPE 1821 SYNTAX Counter64 1822 MAX-ACCESS read-only 1823 STATUS current 1824 DESCRIPTION 1825 "This object is a count of the number of octets 1826 contained in normal priority frames that have 1827 been received on this port. This counter is 1828 incremented by OctetCount for each frame received 1829 on this port which is counted by 1830 vgRptrPortNormPriorityFrames. 1832 This counter is a 64 bit version of 1833 vgRptrPortL32NormPriorityOctets and 1834 vgRptrPortU32NormPriorityOctets. It should be 1835 used by Network Management protocols which support 1836 64 bit counters (e.g. SNMPv2). 1838 This counter may experience a discontinuity when 1839 the value of the corresponding instance of 1840 vgRptrPortLastChange changes." 1841 REFERENCE 1842 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1843 aNormalPriorityOctetsReceived." 1844 ::= { vgRptrMonPortEntry 15 } 1846 vgRptrPortBroadcastFrames OBJECT-TYPE 1847 SYNTAX Counter32 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "This object is a count of broadcast packets that 1852 have been received on this port. This counter is 1853 incremented by one for each readable frame 1854 received on this port whose destination MAC 1855 address is the broadcast address. Frames 1856 counted by this counter are also counted by 1857 vgRptrPortReadableFrames. 1859 This counter may experience a discontinuity when 1860 the value of the corresponding instance of 1861 vgRptrPortLastChange changes." 1862 REFERENCE 1863 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1864 aBroadcastFramesReceived." 1865 ::= { vgRptrMonPortEntry 16 } 1867 vgRptrPortMulticastFrames OBJECT-TYPE 1868 SYNTAX Counter32 1869 MAX-ACCESS read-only 1870 STATUS current 1871 DESCRIPTION 1872 "This object is a count of multicast packets that 1873 have been received on this port. This counter is 1874 incremented by one for each readable frame 1875 received on this port whose destination MAC 1876 address has the group address bit set, but is not 1877 the broadcast address. Frames counted by this 1878 counter are also counted by 1879 vgRptrPortReadableFrames, but not by 1880 vgRptrPortBroadcastFrames. Note that when the 1881 value of the instance vgRptrInfoCurrentFramingType 1882 for the repeater that this port is associated 1883 with is equal to 'frameType88025', this count 1884 includes packets addressed to functional 1885 addresses. 1887 This counter may experience a discontinuity when 1888 the value of the corresponding instance of 1889 vgRptrPortLastChange changes." 1890 REFERENCE 1891 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1892 aMulticastFramesReceived." 1893 ::= { vgRptrMonPortEntry 17 } 1895 vgRptrPortNullAddressedFrames OBJECT-TYPE 1896 SYNTAX Counter32 1897 MAX-ACCESS read-only 1898 STATUS current 1899 DESCRIPTION 1900 "This object is a count of null addressed packets 1901 that have been received on this port. This 1902 counter is incremented by one for each frame 1903 received on this port with a destination MAC 1904 address consisting of all zero bits. Both void 1905 and training frames are included in this 1906 counter. 1908 This counter may experience a discontinuity when 1909 the value of the corresponding instance of 1910 vgRptrPortLastChange changes." 1911 REFERENCE 1912 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1913 aNullAddressedFramesReceived." 1914 ::= { vgRptrMonPortEntry 18 } 1916 vgRptrPortIPMFrames OBJECT-TYPE 1917 SYNTAX Counter32 1918 MAX-ACCESS read-only 1919 STATUS current 1920 DESCRIPTION 1921 "This object is a count of the number of frames 1922 that have been received on this port with an 1923 invalid packet marker and no PMI errors. A 1924 repeater will write an invalid packet marker to 1925 the end of a frame containing errors as it is 1926 forwarded through the repeater to the other 1927 ports. This counter is incremented by one for 1928 each frame received on this port which has had an 1929 invalid packet marker added to the end of the 1930 frame. 1932 This counter indicates problems occurring in the 1933 domain of other repeaters, as opposed to problems 1934 with cables or devices directly attached to this 1935 repeater. 1937 This counter may experience a discontinuity when 1938 the value of the corresponding instance of 1939 vgRptrPortLastChange changes." 1940 REFERENCE 1941 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1942 aIPMFramesReceived." 1943 ::= { vgRptrMonPortEntry 19 } 1945 vgRptrPortOversizeFrames OBJECT-TYPE 1946 SYNTAX Counter32 1947 MAX-ACCESS read-only 1948 STATUS current 1949 DESCRIPTION 1950 "This object is a count of oversize frames 1951 received on this port. This counter is 1952 incremented by one for each frame received on 1953 this port whose OctetCount is larger than the 1954 maximum legal frame size. 1956 The frame size which causes this counter to 1957 increment is dependent on the current value of 1958 vgRptrInfoCurrentFramingType for the repeater that 1959 the port is associated with. When 1960 vgRptrInfoCurrentFramingType is equal to 1961 frameType88023 this counter will increment for 1962 frames that are 1519 octets or larger. When 1963 vgRptrInfoCurrentFramingType is equal to 1964 frameType88025 this counter will increment for 1965 frames that are 4521 octets or larger. 1967 This counter may experience a discontinuity when 1968 the value of the corresponding instance of 1969 vgRptrPortLastChange changes." 1970 REFERENCE 1971 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1972 aOversizeFramesReceived." 1973 ::= { vgRptrMonPortEntry 20 } 1975 vgRptrPortDataErrorFrames OBJECT-TYPE 1976 SYNTAX Counter32 1977 MAX-ACCESS read-only 1978 STATUS current 1979 DESCRIPTION 1980 "This object is a count of errored frames 1981 received on this port. This counter is 1982 incremented by one for each frame received on 1983 this port with any of the following errors: bad 1984 FCS (with no IPM), PMI errors (excluding frames 1985 with an IPM error as the only PMI error), or 1986 undersize (with no IPM). Does not include 1987 packets counted by vgRptrPortIPMFrames, 1988 vgRptrPortOversizeFrames, or 1989 vgRptrPortNullAddressedFrames. 1991 This counter indicates problems with cables or 1992 devices directly connected to this repeater, while 1993 vgRptrPortIPMFrames indicates problems occurring 1994 in the domain of other repeaters. 1996 This counter may experience a discontinuity when 1997 the value of the corresponding instance of 1998 vgRptrPortLastChange changes." 1999 REFERENCE 2000 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2001 aDataErrorFramesReceived." 2002 ::= { vgRptrMonPortEntry 21 } 2004 vgRptrPortPriorityPromotions OBJECT-TYPE 2005 SYNTAX Counter32 2006 MAX-ACCESS read-only 2007 STATUS current 2008 DESCRIPTION 2009 "This counter is incremented by one each time the 2010 priority promotion timer has expired on this port 2011 and a normal priority frame is priority 2012 promoted. 2014 This counter may experience a discontinuity when 2015 the value of the corresponding instance of 2016 vgRptrPortLastChange changes." 2017 REFERENCE 2018 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2019 aPriorityPromotions." 2020 ::= { vgRptrMonPortEntry 22 } 2022 vgRptrPortTransitionToTrainings OBJECT-TYPE 2023 SYNTAX Counter32 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "This counter is incremented by one each time the 2028 vgRptrPortStatus object for this port transitions 2029 into the 'training' state. 2031 This counter may experience a discontinuity when 2032 the value of the corresponding instance of 2033 vgRptrPortLastChange changes." 2034 REFERENCE 2035 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2036 aTransitionsIntoTraining." 2037 ::= { vgRptrMonPortEntry 23 } 2039 vgRptrPortLastChange OBJECT-TYPE 2040 SYNTAX TimeStamp 2041 MAX-ACCESS read-only 2042 STATUS current 2043 DESCRIPTION 2044 "The value of sysUpTime when the last of the 2045 following occurred: 2046 1) the agent cold- or warm-started; 2047 2) the row for the port was created 2048 (such as when a device or module was 2049 added to the system); or 2050 3) any condition that would cause one of 2051 the counters for the row to experience 2052 a discontinuity." 2053 ::= { vgRptrMonPortEntry 24 } 2055 vgRptrAddrTrack OBJECT IDENTIFIER ::= { vgRptrObjects 3 } 2057 vgRptrAddrTrackRptr 2058 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 1 } 2059 -- Currently unused 2061 vgRptrAddrTrackGroup 2062 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 2 } 2063 -- Currently unused 2065 vgRptrAddrTrackPort 2066 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 3 } 2068 vgRptrAddrTrackTable OBJECT-TYPE 2069 SYNTAX SEQUENCE OF VgRptrAddrTrackEntry 2070 MAX-ACCESS not-accessible 2071 STATUS current 2072 DESCRIPTION 2073 "Table of address mapping information about the 2074 ports." 2075 ::= { vgRptrAddrTrackPort 1 } 2077 vgRptrAddrTrackEntry OBJECT-TYPE 2078 SYNTAX VgRptrAddrTrackEntry 2079 MAX-ACCESS not-accessible 2080 STATUS current 2081 DESCRIPTION 2082 "An entry in the table, containing address mapping 2083 information about a single port." 2084 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 2085 ::= { vgRptrAddrTrackTable 1 } 2087 VgRptrAddrTrackEntry ::= 2088 SEQUENCE { 2089 vgRptrAddrLastTrainedAddress OCTET STRING, 2090 vgRptrAddrTrainedAddrChanges Counter32, 2091 vgRptrRptrDetectedDupAddress TruthValue, 2092 vgRptrMgrDetectedDupAddress TruthValue 2093 } 2095 vgRptrAddrLastTrainedAddress OBJECT-TYPE 2096 SYNTAX OCTET STRING (SIZE(0 | 6)) 2097 MAX-ACCESS read-only 2098 STATUS current 2099 DESCRIPTION 2100 "This object is the MAC address of the last 2101 station which succeeded in training on this port. 2102 A cascaded repeater may train using the null 2103 address. If no stations have succeeded in 2104 training on this port since the agent began 2105 monitoring the port activity, the agent shall 2106 return a string of length zero." 2107 REFERENCE 2108 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2109 aLastTrainedAddress." 2110 ::= { vgRptrAddrTrackEntry 1 } 2112 vgRptrAddrTrainedAddrChanges OBJECT-TYPE 2113 SYNTAX Counter32 2114 MAX-ACCESS read-only 2115 STATUS current 2116 DESCRIPTION 2117 "This counter is incremented by one for each time 2118 that the vgRptrAddrLastTrainedAddress object for 2119 this port changes." 2120 REFERENCE 2121 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2122 aTrainedAddressChanges." 2123 ::= { vgRptrAddrTrackEntry 2 } 2125 vgRptrRptrDetectedDupAddress OBJECT-TYPE 2126 SYNTAX TruthValue 2127 MAX-ACCESS read-only 2128 STATUS current 2129 DESCRIPTION 2130 "This object is used to indicate that the 2131 repeater detected an error-free training frame on 2132 this port with a non-null source MAC address which 2133 matches the value of vgRptrAddrLastTrainedAddress 2134 of another active port in the same repeater. This 2135 is reset to 'false' when an error-free training 2136 frame is received with a non-null source MAC 2137 address which does not match 2138 vgRptrAddrLastTrainedAddress of another port which 2139 is active in the same repeater. 2141 For the cascade port, this object will be 'true' 2142 if the 'D' bit in the most recently received 2143 error-free training response frame was set, 2144 indicating the device at the other end of the link 2145 believes that this repeater's cascade port is 2146 using a duplicate address. This may be because 2147 the device at the other end of the link detected a 2148 duplicate address itself, or, if the other device 2149 is also a repeater, it could be because 2150 vgRptrMgrDetectedDupAddress was set to 'true' on 2151 the port that this repeater's cascade port is 2152 connected to." 2153 REFERENCE 2154 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2155 aLocalRptrDetectedDupAddr." 2156 ::= { vgRptrAddrTrackEntry 3 } 2158 vgRptrMgrDetectedDupAddress OBJECT-TYPE 2159 SYNTAX TruthValue 2160 MAX-ACCESS read-write 2161 STATUS current 2162 DESCRIPTION 2163 "This object can be set by a management station 2164 when it detects that there is a duplicate MAC 2165 address. This object is OR'd with 2166 vgRptrRptrDetectedDupAddress to form the value of 2167 the 'D' bit in training response frames on this 2168 port. 2170 The purpose of this object is to provide a means 2171 for network management software to inform an end 2172 station that it is using a duplicate station 2173 address. Setting this object does not affect the 2174 current state of the link; the end station will 2175 not be informed of the duplicate address until it 2176 retrains for some reason. Note that regardless 2177 of its station address, the end station will not 2178 be able to train successfully until the network 2179 management software has set this object back to 2180 'false'. Although this object exists on 2181 cascade ports, it does not perform any function 2182 since this repeater is the initiator of training 2183 on a cascade port." 2184 REFERENCE 2185 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2186 aCentralMgmtDetectedDupAddr." 2187 ::= { vgRptrAddrTrackEntry 4 } 2189 vgRptrTraps OBJECT IDENTIFIER ::= { vgRptrMIB 2 } 2190 vgRptrTrapPrefix OBJECT IDENTIFIER ::= { vgRptrTraps 0 } 2192 vgRptrHealth NOTIFICATION-TYPE 2193 OBJECTS { vgRptrInfoOperStatus } 2194 STATUS current 2195 DESCRIPTION 2196 "A vgRptrHealth trap conveys information related 2197 to the operational state of a repeater. This trap 2198 is sent when the value of an instance of 2199 vgRptrInfoOperStatus changes. The vgRptrHealth 2200 trap is not sent as a result of powering up a 2201 repeater. 2203 The vgRptrHealth trap must contain the instance of 2204 the vgRptrInfoOperStatus object associated with 2205 the affected repeater. 2207 The agent must throttle the generation of 2208 consecutive vgRptrHealth traps so that there is at 2209 least a five-second gap between traps of this 2210 type. When traps are throttled, they are dropped, 2211 not queued for sending at a future time. (Note 2212 that 'generating' a trap means sending to all 2213 configured recipients.)" 2214 REFERENCE 2215 "IEEE 802.12, Layer Management, 13.2.4.2.3, 2216 nRepeaterHealth." 2217 ::= { vgRptrTrapPrefix 1 } 2219 vgRptrResetEvent NOTIFICATION-TYPE 2220 OBJECTS { vgRptrInfoOperStatus } 2221 STATUS current 2222 DESCRIPTION 2223 "A vgRptrResetEvent trap conveys information 2224 related to the operational state of a repeater. 2225 This trap is sent on completion of a repeater 2226 reset action. A repeater reset action is defined 2227 as a transition to its initial state as specified 2228 in clause 12 [IEEE Std 802.12] when triggered by 2229 a management command. 2231 The vgRptrResetEvent trap is not sent when the 2232 agent restarts and sends an SNMP coldStart or 2233 warmStart trap. 2235 The vgRptrResetEvent trap must contain the 2236 instance of the vgRptrInfoOperStatus object 2237 associated with the affected repeater. 2239 The agent must throttle the generation of 2240 consecutive vgRptrResetEvent traps so that there 2241 is at least a five-second gap between traps of 2242 this type. When traps are throttled, they are 2243 dropped, not queued for sending at a future time. 2244 (Note that 'generating' a trap means sending to 2245 all configured recipients.)" 2246 REFERENCE 2247 "IEEE 802.12, Layer Management, 13.2.4.2.3, 2248 nRepeaterReset." 2249 ::= { vgRptrTrapPrefix 2 } 2251 -- conformance information 2253 vgRptrConformance OBJECT IDENTIFIER ::= { vgRptrMIB 3 } 2255 vgRptrCompliances 2256 OBJECT IDENTIFIER ::= { vgRptrConformance 1 } 2258 vgRptrGroups OBJECT IDENTIFIER ::= { vgRptrConformance 2 } 2260 -- compliance statements 2262 vgRptrCompliance MODULE-COMPLIANCE 2263 STATUS current 2264 DESCRIPTION 2265 "The compliance statement for managed 802.12 2266 repeaters." 2268 MODULE -- this module 2269 MANDATORY-GROUPS { vgRptrConfigGroup, 2270 vgRptrNotificationsGroup } 2272 GROUP vgRptrStatsGroup 2273 DESCRIPTION 2274 "Implementation of this optional group is 2275 recommended for systems which have the 2276 instrumentation to do performance monitoring." 2278 GROUP vgRptrAddrGroup 2279 DESCRIPTION 2280 "Implementation of this optional group is 2281 recommended for all systems which have the 2282 necessary instrumentation to track the last 2283 trained MAC address attached to a repeater 2284 port." 2286 MODULE SNMP-REPEATER-MIB 2287 GROUP snmpRptrGrpRptrAddrSearch 2288 DESCRIPTION 2289 "Implementation of this group is recommended 2290 for systems which have the necessary 2291 instrumentation to search all incoming data 2292 streams for a particular source MAC address." 2293 ::= { vgRptrCompliances 1 } 2295 -- units of conformance 2297 vgRptrConfigGroup OBJECT-GROUP 2298 OBJECTS { 2299 vgRptrInfoMACAddress, 2300 vgRptrInfoCurrentFramingType, 2301 vgRptrInfoDesiredFramingType, 2302 vgRptrInfoFramingCapability, 2303 vgRptrInfoTrainingVersion, 2304 vgRptrInfoOperStatus, 2305 vgRptrInfoReset, 2306 vgRptrInfoLastChange, 2307 vgRptrGroupObjectID, 2308 vgRptrGroupOperStatus, 2309 vgRptrGroupPortCapacity, 2310 vgRptrGroupCablesBundled, 2311 vgRptrPortType, 2312 vgRptrPortAdminStatus, 2313 vgRptrPortOperStatus, 2314 vgRptrPortSupportedPromiscMode, 2315 vgRptrPortSupportedCascadeMode, 2316 vgRptrPortAllowedTrainType, 2317 vgRptrPortLastTrainConfig, 2318 vgRptrPortTrainingResult, 2319 vgRptrPortPriorityEnable, 2320 vgRptrPortRptrInfoIndex 2321 } 2322 STATUS current 2323 DESCRIPTION 2324 "A collection of objects for managing the status 2325 and configuration of IEEE 802.12 repeaters." 2326 ::= { vgRptrGroups 1 } 2328 vgRptrStatsGroup OBJECT-GROUP 2329 OBJECTS { 2330 vgRptrMonTotalReadableFrames, 2331 vgRptrMonL32TotalReadableOctets, 2332 vgRptrMonU32TotalReadableOctets, 2333 vgRptrMonHCTotalReadableOctets, 2334 vgRptrMonTotalErrors, 2335 vgRptrPortReadableFrames, 2336 vgRptrPortL32ReadableOctets, 2337 vgRptrPortU32ReadableOctets, 2338 vgRptrPortHCReadableOctets, 2339 vgRptrPortL32UnreadableOctets, 2340 vgRptrPortU32UnreadableOctets, 2341 vgRptrPortHCUnreadableOctets, 2342 vgRptrPortHighPriorityFrames, 2343 vgRptrPortL32HighPriorityOctets, 2344 vgRptrPortU32HighPriorityOctets, 2345 vgRptrPortHCHighPriorityOctets, 2346 vgRptrPortNormPriorityFrames, 2347 vgRptrPortL32NormPriorityOctets, 2348 vgRptrPortU32NormPriorityOctets, 2349 vgRptrPortHCNormPriorityOctets, 2350 vgRptrPortBroadcastFrames, 2351 vgRptrPortMulticastFrames, 2352 vgRptrPortNullAddressedFrames, 2353 vgRptrPortIPMFrames, 2354 vgRptrPortOversizeFrames, 2355 vgRptrPortDataErrorFrames, 2356 vgRptrPortPriorityPromotions, 2357 vgRptrPortTransitionToTrainings, 2358 vgRptrPortLastChange 2359 } 2360 STATUS current 2361 DESCRIPTION 2362 "A collection of objects for providing statistics 2363 for IEEE 802.12 repeaters." 2364 ::= { vgRptrGroups 2 } 2366 vgRptrAddrGroup OBJECT-GROUP 2367 OBJECTS { 2368 vgRptrAddrLastTrainedAddress, 2369 vgRptrAddrTrainedAddrChanges, 2370 vgRptrRptrDetectedDupAddress, 2371 vgRptrMgrDetectedDupAddress 2372 } 2373 STATUS current 2374 DESCRIPTION 2375 "A collection of objects for tracking addresses 2376 on IEEE 802.12 repeaters." 2377 ::= { vgRptrGroups 3 } 2379 vgRptrNotificationsGroup NOTIFICATION-GROUP 2380 NOTIFICATIONS { 2381 vgRptrHealth, 2382 vgRptrResetEvent 2383 } 2384 STATUS current 2385 DESCRIPTION 2386 "A collection of notifications used to indicate 2387 802.12 repeater general status changes." 2388 ::= { vgRptrGroups 4 } 2390 END 2392 5. Acknowledgements 2394 This document was produced by the IETF 100VG-AnyLAN Working Group, 2395 whose efforts were greatly advanced by the contributions of the 2396 following people: 2398 Paul Chefurka 2399 Bob Faulk 2400 Jeff Johnson 2401 Karen Kimball 2402 David Lapp 2403 Jason Spofford 2404 Kaj Tesink 2406 This document is based on the work of IEEE 802.12. 2408 6. References 2410 [1] Information processing systems - Open Systems Interconnection - 2411 Specification of Abstract Syntax Notation One (ASN.1), 2412 International Organization for Standardization. International 2413 Standard 8824 (December, 1987). 2415 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2416 S. Waldbusser, "Structure of Management Information for Version 2417 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2418 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach 2419 Consulting, Inc., International Network Services, January 1996. 2421 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2422 S. Waldbusser, "Textual Conventions for Version 2 of the Simple 2423 Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 2424 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2425 International Network Services, January 1996. 2427 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2428 S. Waldbusser, "Conformance Statements for Version 2 of the 2429 Simple Network Management Protocol (SNMPv2)", RFC 1904, SNMP 2430 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 2431 Inc., International Network Services, January 1996. 2433 [5] McCloghrie, K., and M. Rose, "Management Information Base for 2434 Network Management of TCP/IP-based internets - MIB-II", STD 17, 2435 RFC 1213, Hughes LAN Systems, Performance Systems International, 2436 March 1991. 2438 [6] IEEE, "Demand Priority Access Method, Physical Layer and 2439 Repeater Specifications for 100 Mb/s Operation", IEEE Standard 2440 802.12-1995" 2442 [7] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, 2443 "Definitions of Managed Objects for IEEE 802.3 Repeater 2444 Devices", RFC 2108, 3Com Corporation, Madge Networks (Israel) 2445 Ltd., Cisco Systems, Inc., February, 1997. 2447 [8] McAnally, G., Gilbert, D., and J. Flick, "Conditional Grant of 2448 Rights to Specific Hewlett-Packard Patents In Conjunction With 2449 the Internet Engineering Task Force's Internet-Standard 2450 Network Management Framework", RFC 1988, August 1996. 2452 [9] Hewlett-Packard Company, US Patents 5,293,635 and 5,421,024. 2454 7. Security Considerations 2456 Certain management information defined in this MIB may be considered 2457 sensitive in some network environments. Therefore, authentication of 2458 received SNMP requests and controlled access to management 2459 information should be employed in such environments. The method for 2460 this authentication is a function of the SNMP Administrative 2461 Framework, and has not been expanded by this MIB. 2463 Several objects in the vgRptrConfigGroup allow write access. Setting 2464 these objects can have a serious effect on the operation of the 2465 network, including modifying the framing type of the network, 2466 resetting the repeater, enabling and disabling individual ports, and 2467 modifying the allowed capabilities of end stations attached to each 2468 port. It is recommended that implementers seriously consider whether 2469 set operations should be allowed without providing, at a minimum, 2470 authentication of request origin. 2472 One particular object in this MIB, vgRptrPortAllowedTrainType, is 2473 considered significant for providing operational security in an 2474 802.12 network. It is recommended that network administrators 2475 configure this object to the 'allowEndNodesOnly' value on all ports 2476 except ports which the administrator knows are attached to cascaded 2477 repeaters or devices which require promiscuous receive capability 2478 (bridges, switches, RMON probes, etc.). This will prevent 2479 unauthorized users from extending the network (by attaching cascaded 2480 repeaters or bridges) without the administrator's knowledge, and will 2481 prevent unauthorized end nodes from listening promiscuously to 2482 network traffic. 2484 8. Author's Address 2486 John Flick 2487 Hewlett Packard Company 2488 8000 Foothills Blvd. M/S 5556 2489 Roseville, CA 95747-5556 2491 Phone: +1 916 785 4018 2492 Email: johnf@hprnd.rose.hp.com 2494 Table of Contents 2496 1. Introduction ............................................... 2 2497 2. The SNMP Network Management Framework ...................... 2 2498 2.1. Object Definitions ....................................... 2 2499 3. Overview ................................................... 3 2500 3.1. MAC Addresses ............................................ 3 2501 3.2. Master Mode and Slave Mode ............................... 3 2502 3.3. IEEE 802.12 Training Frames .............................. 4 2503 3.4. Structure of the MIB ..................................... 7 2504 3.4.1. Basic Definitions ...................................... 7 2505 3.4.2. Monitor Definitions .................................... 7 2506 3.4.3. Address Tracking Definitions ........................... 7 2507 3.5. Relationship to other MIBs ............................... 7 2508 3.5.1. Relationship to MIB-II ................................. 7 2509 3.5.1.1. Relationship to the 'system' group ................... 8 2510 3.5.1.2. Relationship to the 'interfaces' group ............... 8 2511 3.5.2. Relationship to the 802.3 Repeater MIB ................. 8 2512 3.6. Mapping of IEEE 802.12 Managed Objects ................... 9 2513 4. Definitions ................................................ 12 2514 5. Acknowledgements ........................................... 53 2515 6. References ................................................. 53 2516 7. Security Considerations .................................... 54 2517 8. Author's Address ........................................... 55