idnits 2.17.1 draft-ietf-vgmib-repeater-dev-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == 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 407 has weird spacing: '...DupAddr vgR...' == Line 409 has weird spacing: '...eceived vgR...' == Line 410 has weird spacing: '...eceived vgR...' == Line 418 has weird spacing: '...eceived vgRpt...' == Line 419 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 (May 19, 1997) is 9832 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: 12 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 May 19 1997 4 Definitions of Managed Objects for IEEE 802.12 Repeater Devices 6 May 19, 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 Abstract 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 1. 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 1.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 2. 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 2.1. Repeater Management Model 90 The model used in the design of this MIB allows for a managed system 91 to contain one or more managed 802.12 repeaters, and one or more 92 managed 802.12 repeater ports. 94 A repeater port may be thought of as a source of traffic into a 95 repeater in the system. The vgRptrBasicPortTable contains entries 96 for each physical repeater port in the managed system. An 97 implementor may choose to separate these ports into "groups". For 98 example, a group may be used to represent a field-replaceable unit, 99 so that the port numbering may match the numbering in the hardware 100 implementation. Note that this group mapping is recommended but 101 optional. An implementor may choose to put all of the system's ports 102 into a single group, or to divide the ports into groups that do not 103 match physical divisions. Each group within the system is uniquely 104 identified by a group number. Each port within a system is uniquely 105 identified by a combination of group number and port number. The 106 method of numbering groups and ports is implementation-specific. 107 Both groups and ports may be sparsely numbered. 109 In addition to the externally visible ports, some implementations may 110 have internal ports that are not obvious to the end-user but are 111 nevertheless sources of traffic into the repeater system. Examples 112 include internal management ports, through which an agent 113 communicates, and ports connecting to a backplane internal to the 114 implementation. It is the decision of the implementor to select the 115 appropriate group(s) in which to place internal ports. 117 Managed repeaters in the system are represented by entries in the 118 vgRptrInfoTable. There may be multiple repeaters in the managed 119 system. They are uniquely identified by a repeater number. The 120 method of numbering repeaters is implementation-specific. Each port 121 will either be associated with one of the repeaters, or isolated (a 122 so-called "trivial" repeater). The set of ports associated with a 123 single repeater will be in the same contention domain, and will be 124 participating in the same instance of the Demand Priority Access 125 Method protocol. The mapping of ports to repeaters may be static or 126 dynamic. A column in the vgRptrBasicPortTable, 127 vgRptrPortRptrInfoIndex, indicates the repeater that the port is 128 currently associated with. The method for assigning a port to a 129 repeater is implementation-specific. 131 2.2. MAC Addresses 133 All representations of MAC addresses in this MIB module are in 134 "canonical" order defined by 802.1a, i.e., as if it were transmitted 135 least significant bit first. This is true even if the repeater is 136 operating in token ring framing mode, which requires MAC addresses to 137 be transmitted most significant bit first. 139 2.3. Master Mode and Slave Mode 141 In an IEEE 802.12 network, "master" devices act as network 142 controllers to decide when to grant requesting end-nodes permission 143 to transmit. These master devices may be repeaters, or other active 144 controller devices such as switches. 146 Devices which do not act as network controllers, such as end-nodes or 147 passive switches, are considered to be operating in "slave" mode. 149 An 802.12 repeater always acts in "master" mode on its local ports, 150 which may connect to end nodes, switch or other device ports acting 151 in "slave" mode, or lower-level repeaters in a cascade. It acts in 152 "slave" mode on cascade ports, which may connect to an upper-level 153 repeater in a cascade, or to switch or other device ports operating 154 in "master" mode. 156 2.4. IEEE 802.12 Training Frames 158 Training frames are special MAC frames that are used only during link 159 initialization. Training frames are initially constructed by the 160 device at the "lower" end of a link, which is the slave mode device 161 for the link. The training frame format is as follows: 163 +----+----+------------+--------------+----------+-----+ 164 | DA | SA | Req Config | Allow Config | Data | FCS | 165 +----+----+------------+--------------+----------+-----+ 167 DA = destination address (six octets) 168 SA = source address (six octets) 169 Req Config = requested configuration (2 octets) 170 Allow Config = allowed configuration (2 octets) 171 Data = data (594 to 675 octets) 172 FCS = frame check sequence (4 octets) 174 Training frames are always sent with a null destination address. To 175 pass training, an end node must use its source address in the source 176 address field of the training frame. A repeater may use a non-null 177 source address if it has one, or it may use a null source address. 179 The requested configuration field allows the slave mode device to 180 inform the master mode device about itself and to request 181 configuration options. The training response frame from the master 182 mode device contains the slave mode device's requested configuration 183 from the training request frame. The currently defined format of the 184 requested configuration field as defined in the IEEE Standard 185 802.12-1995 standard is shown below. Please refer to the most 186 current version of the IEEE document for a more up to date 187 description of this field. In particular, the reserved bits may be 188 used in later versions of the standard. 190 First Octet: Second Octet: 192 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 193 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 194 |v|v|v|r|r|r|r|r| |r|r|r|F|F|P|P|R| 195 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 197 vvv: The version of the 802.12 training protocol with which 198 the training initiator is compliant. The current version 199 is 100. Note that because of the different bit ordering 200 used in IEEE and IETF documents, this value corresponds 201 to version 1. 202 r: Reserved bits (set to zero) 203 FF: 00 = frameType88023 204 01 = frameType88025 205 10 = reserved 206 11 = frameTypeEither 207 PP: 00 = singleAddressMode 208 01 = promiscuousMode 209 10 = reserved 210 11 = reserved 211 R: 0 = the training initiator is an end node 212 1 = the training initiator is a repeater 214 The allowed configuration field allows the master mode device to 215 respond with the allowed configuration. The slave mode device sets 216 the contents of this field to all zero bits. The master mode device 217 sets the allowed configuration field as follows: 219 First Octet: Second Octet: 221 7 6 5 4 3 2 1 0 7 6 5 4 3 2 1 0 222 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 223 |v|v|v|D|C|N|r|r| |r|r|r|F|F|P|P|R| 224 +-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+ 226 vvv: The version of the 802.12 training protocol with which 227 the training responder is compliant. The current version 228 is 100. Note that because of the different bit ordering 229 used in IEEE and IETF documents, this value corresponds 230 to version 1. 231 D: 0 = No duplicate address has been detected. 232 1 = Duplicate address has been detected. 233 C: 0 = The requested configuration is compatible with the 234 network and the attached port. 235 1 = The requested configuration is not compatible with 236 the network and/or the attached port. In this case, 237 the FF, PP, and R bits indicate a configuration that 238 would be allowed. 239 N: 0 = Access will be allowed, providing the configuration 240 is compatible (C = 0). 241 1 = Access is not granted because of security 242 restrictions. 243 r: Reserved bits (set to zero). 244 FF: 00 = frameType88023 will be used. 245 01 = frameType88025 will be used. 246 10 = reserved 247 11 = reserved 248 PP: 00 = singleAddressMode 249 01 = promiscuousMode 250 10 = reserved 251 11 = reserved 252 R: 0 = Requested access as an end node is allowed. 253 1 = Requested access as a repeater is allowed. 255 Again, note that the most recent version of the IEEE 802.12 standard 256 should be consulted for the most up to date definition of the 257 requested configuration and allowed configuration fields. 259 The data field contains between 594 and 675 octets and is filled in 260 by the training initiator. The first 55 octets may be used for 261 vendor specific protocol information. The remaining octets are all 262 zeros. The length of the training frame combined with the 263 requirement that 24 consecutive training frames be exchanged without 264 error to complete training ensures that marginal links will not 265 complete training. 267 2.5. Structure of the MIB 269 Objects in this MIB are arranged into OID subtrees, each of which 270 contains a set of related objects within a broad functional category. 271 These subtrees are intended for organizational convenience ONLY, and 272 have no relation to the conformance groups defined later in the 273 document. 275 2.5.1. Basic Definitions 277 The basic definitions include objects for managing the basic status 278 and control parameters for each repeater within the managed system, 279 for the port groups within the managed system, and for the individual 280 ports themselves. 282 2.5.2. Monitor Definitions 284 The monitor definitions include monitoring statistics for each 285 repeater within the system and for individual ports. 287 2.5.3. Address Tracking Definitions 289 This collection includes objects for tracking the MAC addresses of 290 the DTEs attached to the ports within the system. 292 Note that this MIB also includes by reference a collection of objects 293 from the 802.3 Repeater MIB which may be used for mapping the 294 topology of a network. These definitions are based on a technology 295 which has been patented by Hewlett-Packard Company (HP). HP has 296 granted rights to this technology to implementors of this MIB. See 297 [8] and [9] for details. 299 2.6. Relationship to other MIBs 301 2.6.1. Relationship to MIB-II 303 It is assumed that a repeater implementing this MIB will also 304 implement (at least) the 'system' group defined in MIB-II [5]. 306 2.6.1.1. Relationship to the 'system' group 308 In MIB-II, the 'system' group is defined as being mandatory for all 309 systems such that each managed entity contains one instance of each 310 object in the 'system' group. Thus, those objects apply to the 311 entity even if the entity's sole functionality is management of 312 repeaters. 314 Note that all of the managed repeaters (i.e. entries in the 315 vgRptrInfoTable) will normally exist within a single naming scope. 316 Therefore, there will normally only be a single instance of each of 317 the objects in the system group for the entire managed repeater 318 system regardless of how many managed repeaters there are in the 319 system. 321 2.6.1.2. Relationship to the 'interfaces' group 323 In MIB-II, the 'interfaces' group is defined as being mandatory for 324 all systems and contains information on an entity's interfaces, where 325 each interface is thought of as being attached to a 'subnetwork'. 326 (Note that this term is not to be confused with 'subnet' which refers 327 to an addressing partitioning scheme used in the Internet suite of 328 protocols.) 330 This Repeater MIB uses the notion of ports on a repeater. The 331 concept of a MIB-II interface has NO specific relationship to a 332 repeater's port. Therefore, the 'interfaces' group applies only to 333 the one (or more) network interfaces on which the entity managing the 334 repeater sends and receives management protocol operations, and does 335 not apply to the repeater's ports. 337 This is consistent with the physical-layer nature of a repeater. An 338 802.12 repeater has an RMAC implementation, which acts as the 339 repeater end of the Demand Priority Access Method, but does not 340 contain a DTE MAC implementation, and does not pass packets up to 341 higher-level protocol entities for processing. 343 (When a network management entity is observing a repeater, it may 344 appear as though the repeater is passing packets to a higher-level 345 protocol entity. However, this is only a means of implementing 346 management, and this passing of management information is not part of 347 the repeater functionality.) 349 2.6.2. Relationship to the 802.3 Repeater MIB 351 An IEEE 802.12 repeater can be configured to operate in either 352 ethernet or token ring framing mode. This only affects the frame 353 format and address bit order of the frames on the wire. An 802.12 354 network does not use the media access protocol for either ethernet or 355 token ring. Instead, IEEE 802.12 defines its own media access 356 protocol, the Demand Priority Access Method (DPAM). 358 There is an existing standards-track MIB module for instrumenting 359 IEEE 802.3 repeaters [7]. That MIB module is designed to instrument 360 the operation of the repeater in a network implementing the 802.3 361 media access protocol. Therefore, much of that MIB does not apply to 362 802.12 repeaters. 364 However, the 802.3 Repeater MIB also contains a collection of objects 365 that may be used to map the topology of a network. These objects are 366 contained in a separable OBJECT-GROUP, are not 802.3-specific, and 367 are considered useful for 802.12 repeaters. In addition, the layer 368 management clause of the IEEE 802.12 specification includes similar 369 functionality. Therefore, vendors of agents for 802.12 repeaters are 370 encouraged to implement the snmpRptrGrpRptrAddrSearch OBJECT-GROUP 371 defined in the 802.3 Repeater MIB. 373 2.7. Mapping of IEEE 802.12 Managed Objects 375 IEEE 802.12 Managed Object Corresponding SNMP Object 377 oRepeater 378 .aCurrentFramingType vgRptrInfoCurrentFramingType 379 .aDesiredFramingType vgRptrInfoDesiredFramingType 380 .aFramingCapability vgRptrInfoFramingCapability 381 .aMACAddress vgRptrInfoMACAddress 382 .aRepeaterHealthState vgRptrInfoOperStatus 383 .aRepeaterID vgRptrInfoIndex 384 .aRepeaterSearchAddress SNMP-REPEATER-MIB - 385 rptrAddrSearchAddress 386 .aRepeaterSearchGroup SNMP-REPEATER-MIB - 387 rptrAddrSearchGroup 388 .aRepeaterSearchPort SNMP-REPEATER-MIB - 389 rptrAddrSearchPort 390 .aRepeaterSearchState SNMP-REPEATER-MIB - 391 rptrAddrSearchState 392 .aRMACVersion vgRptrInfoTrainingVersion 393 .acRepeaterSearchAddress SNMP-REPEATER-MIB - 394 rptrAddrSearchAddress 395 .acResetRepeater vgRptrInfoReset 396 .nRepeaterHealth vgRptrHealth 397 .nRepeaterReset vgRptrResetEvent 399 oGroup 400 .aGroupCablesBundled vgRptrGroupCablesBundled 401 .aGroupID vgRptrGroupIndex 402 .aGroupPortCapacity vgRptrGroupPortCapacity 404 oPort 405 .aAllowableTrainingType vgRptrPortAllowedTrainType 406 .aBroadcastFramesReceived vgRptrPortBroadcastFrames 407 .aCentralMgmtDetectedDupAddr vgRptrMgrDetectedDupAddress 408 .aDataErrorFramesReceived vgRptrPortDataErrorFrames 409 .aHighPriorityFramesReceived vgRptrPortHighPriorityFrames 410 .aHighPriorityOctetsReceived vgRptrPortHCHighPriorityOctets, or 411 vgRptrPortHighPriorityOctets and 412 vgRptrPortHighPriOctetRollovers 413 .aIPMFramesReceived vgRptrPortIPMFrames 414 .aLastTrainedAddress vgRptrAddrLastTrainedAddress 415 .aLastTrainingConfig vgRptrPortLastTrainConfig 416 .aLocalRptrDetectedDupAddr vgRptrRptrDetectedDupAddress 417 .aMulticastFramesReceived vgRptrPortMulticastFrames 418 .aNormalPriorityFramesReceived vgRptrPortNormPriorityFrames 419 .aNormalPriorityOctetsReceived vgRptrPortHCNormPriorityOctets, or 420 vgRptrPortNormPriorityOctets and 421 vgRptrPortNormPriOctetRollovers 422 .aNullAddressedFramesReceived vgRptrPortNullAddressedFrames 423 .aOctetsInUnreadableFramesRcvd vgRptrPortHCUnreadableOctets, or 424 vgRptrPortUnreadableOctets and 425 vgRptrPortUnreadOctetRollovers 426 .aOversizeFramesReceived vgRptrPortOversizeFrames 427 .aPortAdministrativeState vgRptrPortAdminStatus 428 .aPortID vgRptrPortIndex 429 .aPortStatus vgRptrPortOperStatus 430 .aPortType vgRptrPortType 431 .aPriorityEnable vgRptrPortPriorityEnable 432 .aPriorityPromotions vgRptrPortPriorityPromotions 433 .aReadableFramesReceived vgRptrPortReadableFrames 434 .aReadableOctetsReceived vgRptrPortHCReadableOctets, or 435 vgRptrPortReadableOctets and 436 vgRptrPortReadOctetRollovers 437 .aSupportedCascadeMode vgRptrPortSupportedCascadeMode 438 .aSupportedPromiscMode vgRptrPortSupportedPromiscMode 439 .aTrainedAddressChanges vgRptrAddrTrainedAddressChanges 440 .aTrainingResult vgRptrPortTrainingResult 441 .aTransitionsIntoTraining vgRptrPortTransitionToTrainings 442 .acPortAdministrativeControl vgRptrPortAdminStatus 444 The following IEEE 802.12 managed objects have not been included in 445 the 802.12 Repeater MIB for the indicated reasons. 447 IEEE 802.12 Managed Object Disposition 449 oRepeater 450 .aGroupMap Can be determined by GetNext sweep 451 of vgRptrBasicGroupTable 453 .aRepeaterGroupCapacity Meaning is unclear in many 454 repeater implementations. For 455 example, some cards may have 456 daughter cards which make group 457 capacity change depending on the 458 cards installed. Meaning is also 459 unclear in a stackable 460 implementation. Also, since 461 groups are not required to be 462 numbered from 1..capacity, but may 463 be computed algorithmically or 464 related to Entity MIB indices, 465 this object was not considered 466 useful. 468 .aRepeaterHealthData Since the data is implementation 469 specific and non-interoperable, 470 it was not considered useful. 472 .aRepeaterHealthText Implementation experience with 473 similar object in 802.3 Rptr MIB 474 indicated it was not useful. 476 .acExecuteNonDisruptiveSelfTest Implementation experience with 477 similar object in 802.3 Rptr MIB 478 indicated it was not useful. 480 .nGroupMapChange Since aGroupMap was not included, 481 a notification of a change in that 482 object was not needed. 484 oGroup 485 .aPortMap Can be determined by GetNext sweep 486 of vgRptrBasicPortTable 487 .nPortMapChange Since aPortMap was not included, 488 a notification of a change in that 489 object was not needed. 491 oPort 492 .aMediaType This object is a function of the 493 Physical Media Dependent (PMD) 494 layer, which is defined 495 differently for each type of 496 network. For an 802.3 network, 497 .aMediaType corresponds to the PMD 498 definitions in the 802.3 MAU MIB. 499 For management of an 802.12 500 network, mapping of this object is 501 deferred to future work on an 502 802.12 PMD MIB which will include 503 both repeater and interface PMD 504 information and redundant link 505 support. 507 3. Definitions 509 DOT12-RPTR-MIB DEFINITIONS ::= BEGIN 511 IMPORTS 512 -- NOTE TO RFC EDITOR: When this document is published as 513 -- an RFC, change 'experimental' to 'mib-2' in the 514 -- following import, and delete this comment. 515 experimental, Integer32, Counter32, Counter64, 516 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE 517 FROM SNMPv2-SMI 518 MacAddress, TruthValue, TimeStamp 519 FROM SNMPv2-TC 520 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 521 FROM SNMPv2-CONF; 523 vgRptrMIB MODULE-IDENTITY 524 LAST-UPDATED "9705192256Z" -- May 19, 1997 525 ORGANIZATION "IETF 100VG-AnyLAN Working Group" 526 CONTACT-INFO 527 "WG E-mail: vgmib@hprnd.rose.hp.com 529 Chair: Jeff Johnson 530 Postal: RedBack Networks 531 2570 North First Street, Suite 410 532 San Jose, CA 95131 533 Tel: +1 408 571 2699 534 Fax: +1 408 571 2698 535 E-mail: jeff@redbacknetworks.com 537 Editor: John Flick 538 Postal: Hewlett Packard Company 539 8000 Foothills Blvd. M/S 5556 540 Roseville, CA 95747-5556 541 Tel: +1 916 785 4018 542 Fax: +1 916 785 3583 543 E-mail: johnf@hprnd.rose.hp.com" 544 DESCRIPTION 545 "This MIB module describes objects for managing 546 IEEE 802.12 repeaters." 547 ::= { experimental 64 } 548 -- NOTE TO RFC EDITOR: When this document is published as 549 -- an RFC, change '{ experimental 64 }' to '{ mib-2 XX }' 550 -- where XX is assigned by IANA, and delete this comment. 552 vgRptrObjects OBJECT IDENTIFIER ::= { vgRptrMIB 1 } 553 vgRptrBasic OBJECT IDENTIFIER ::= { vgRptrObjects 1 } 554 vgRptrBasicRptr OBJECT IDENTIFIER ::= { vgRptrBasic 1 } 556 vgRptrInfoTable OBJECT-TYPE 557 SYNTAX SEQUENCE OF VgRptrInfoEntry 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "A table of information about each 802.12 repeater 562 in the managed system." 563 ::= { vgRptrBasicRptr 1 } 565 vgRptrInfoEntry OBJECT-TYPE 566 SYNTAX VgRptrInfoEntry 567 MAX-ACCESS not-accessible 568 STATUS current 569 DESCRIPTION 570 "An entry in the table, containing information 571 about a single repeater." 572 INDEX { vgRptrInfoIndex } 573 ::= { vgRptrInfoTable 1 } 575 VgRptrInfoEntry ::= 576 SEQUENCE { 577 vgRptrInfoIndex Integer32, 578 vgRptrInfoMACAddress MacAddress, 579 vgRptrInfoCurrentFramingType INTEGER, 580 vgRptrInfoDesiredFramingType INTEGER, 581 vgRptrInfoFramingCapability INTEGER, 582 vgRptrInfoTrainingVersion INTEGER, 583 vgRptrInfoOperStatus INTEGER, 584 vgRptrInfoReset INTEGER, 585 vgRptrInfoLastChange TimeStamp 586 } 588 vgRptrInfoIndex OBJECT-TYPE 589 SYNTAX Integer32 (1..2147483647) 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "A unique identifier for the repeater for which 594 this entry contains information. The numbering 595 scheme for repeaters is implementation specific." 596 REFERENCE 597 "IEEE Standard 802.12-1995, 13.2.4.2.1, 598 aRepeaterID." 599 ::= { vgRptrInfoEntry 1 } 601 vgRptrInfoMACAddress OBJECT-TYPE 602 SYNTAX MacAddress 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "The MAC address used by the repeater when it 607 initiates training on the uplink port. Repeaters 608 are allowed to train with an assigned MAC address 609 or a null (all zeroes) MAC address." 610 REFERENCE 611 "IEEE Standard 802.12-1995, 13.2.4.2.1, 612 aMACAddress." 613 ::= { vgRptrInfoEntry 2 } 615 vgRptrInfoCurrentFramingType OBJECT-TYPE 616 SYNTAX INTEGER { 617 frameType88023(1), 618 frameType88025(2) 619 } 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "The type of framing (802.3 or 802.5) currently 624 in use by the repeater." 625 REFERENCE 626 "IEEE Standard 802.12-1995, 13.2.4.2.1, 627 aCurrentFramingType." 628 ::= { vgRptrInfoEntry 3 } 630 vgRptrInfoDesiredFramingType OBJECT-TYPE 631 SYNTAX INTEGER { 632 frameType88023(1), 633 frameType88025(2) 634 } 635 MAX-ACCESS read-write 636 STATUS current 637 DESCRIPTION 638 "The type of framing which will be used by the 639 repeater after the next time it is reset. 641 The value of this object should be preserved 642 across repeater resets and power failures." 643 REFERENCE 644 "IEEE Standard 802.12-1995, 13.2.4.2.1, 645 aDesiredFramingType." 646 ::= { vgRptrInfoEntry 4 } 648 vgRptrInfoFramingCapability OBJECT-TYPE 649 SYNTAX INTEGER { 650 frameType88023(1), 651 frameType88025(2), 652 frameTypeEither(3) 653 } 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "The type of framing this repeater is capable of 658 supporting." 659 REFERENCE 660 "IEEE Standard 802.12-1995, 13.2.4.2.1, 661 aFramingCapability." 662 ::= { vgRptrInfoEntry 5 } 664 vgRptrInfoTrainingVersion OBJECT-TYPE 665 SYNTAX INTEGER (0..7) 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The highest version bits (vvv bits) supported by 670 the repeater during training." 671 REFERENCE 672 "IEEE Standard 802.12-1995, 13.2.4.2.1, 673 aRMACVersion." 674 ::= { vgRptrInfoEntry 6 } 676 vgRptrInfoOperStatus OBJECT-TYPE 677 SYNTAX INTEGER { 678 other(1), 679 ok(2), 680 generalFailure(3) 681 } 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION 685 "The vgRptrInfoOperStatus object indicates the 686 operational state of the repeater." 687 REFERENCE 688 "IEEE Standard 802.12-1995, 13.2.4.2.1, 689 aRepeaterHealthState." 690 ::= { vgRptrInfoEntry 7 } 692 vgRptrInfoReset OBJECT-TYPE 693 SYNTAX INTEGER { 694 noReset(1), 695 reset(2) 696 } 698 MAX-ACCESS read-write 699 STATUS current 700 DESCRIPTION 701 "Setting this object to reset(2) causes the 702 repeater to transition to its initial state as 703 specified in clause 12 [IEEE Std 802.12]. 705 Setting this object to noReset(1) has no effect. 706 The agent will always return the value noReset(1) 707 when this object is read. 709 After receiving a request to set this variable to 710 reset(2), the agent is allowed to delay the reset 711 for a short period. For example, the implementor 712 may choose to delay the reset long enough to 713 allow the SNMP response to be transmitted. In 714 any event, the SNMP response must be transmitted. 716 This action does not reset the management 717 counters defined in this document nor does it 718 affect the vgRptrPortAdminStatus parameters. 719 Included in this action is the execution of a 720 disruptive Self-Test with the following 721 characteristics: 723 1) The nature of the tests is not specified. 724 2) The test resets the repeater but without 725 affecting configurable management 726 information about the repeater. 727 3) Packets received during the test may or 728 may not be transferred. 729 4) The test does not interfere with 730 management functions. 732 After performing this self-test, the agent will 733 update the repeater health information (including 734 vgRptrInfoOperStatus), and send a 735 vgRptrResetEvent." 736 REFERENCE 737 "IEEE Standard 802.12-1995, 13.2.4.2.2, 738 acResetRepeater." 739 ::= { vgRptrInfoEntry 8 } 741 vgRptrInfoLastChange OBJECT-TYPE 742 SYNTAX TimeStamp 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "The value of sysUpTime when any of the following 747 conditions occurred: 749 1) agent cold- or warm-started; 750 2) this instance of repeater was created 751 (such as when a device or module was 752 added to the system); 753 3) a change in the value of 754 vgRptrInfoOperStatus; 755 4) ports were added or removed as members of 756 the repeater; or 757 5) any of the counters associated with this 758 repeater had a discontinuity." 759 ::= { vgRptrInfoEntry 9 } 761 vgRptrBasicGroup OBJECT IDENTIFIER ::= { vgRptrBasic 2 } 763 vgRptrBasicGroupTable OBJECT-TYPE 764 SYNTAX SEQUENCE OF VgRptrBasicGroupEntry 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION 768 "A table containing information about groups of 769 ports." 770 ::= { vgRptrBasicGroup 1 } 772 vgRptrBasicGroupEntry OBJECT-TYPE 773 SYNTAX VgRptrBasicGroupEntry 774 MAX-ACCESS not-accessible 775 STATUS current 776 DESCRIPTION 777 "An entry in the vgRptrBasicGroupTable, containing 778 information about a single group of ports." 779 INDEX { vgRptrGroupIndex } 780 ::= { vgRptrBasicGroupTable 1 } 782 VgRptrBasicGroupEntry ::= 783 SEQUENCE { 784 vgRptrGroupIndex Integer32, 785 vgRptrGroupObjectID OBJECT IDENTIFIER, 786 vgRptrGroupOperStatus INTEGER, 787 vgRptrGroupPortCapacity Integer32, 788 vgRptrGroupCablesBundled INTEGER 789 } 791 vgRptrGroupIndex OBJECT-TYPE 792 SYNTAX Integer32 (1..2146483647) 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "This object identifies the group within the 797 system for which this entry contains information. 798 The numbering scheme for groups is implementation 799 specific." 800 REFERENCE 801 "IEEE Standard 802.12-1995, 13.2.4.4.1, 802 aGroupID." 803 ::= { vgRptrBasicGroupEntry 1 } 805 vgRptrGroupObjectID OBJECT-TYPE 806 SYNTAX OBJECT IDENTIFIER 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "The vendor's authoritative identification of the 811 group. This value may be allocated within the 812 SMI enterprises subtree (1.3.6.1.4.1) and 813 provides a straight-forward and unambiguous means 814 for determining what kind of group is being 815 managed. 817 For example, this object could take the value 818 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, 819 Inc.' was assigned the subtree 1.3.6.1.4.1.4242, 820 and had assigned the identifier 821 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 822 6-Port Plug-in Module.'" 823 ::= { vgRptrBasicGroupEntry 2 } 825 vgRptrGroupOperStatus OBJECT-TYPE 826 SYNTAX INTEGER { 827 other(1), 828 operational(2), 829 malfunctioning(3), 830 notPresent(4), 831 underTest(5), 832 resetInProgress(6) 833 } 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "An object that indicates the operational status 838 of the group. 840 A status of notPresent(4) indicates that the 841 group is temporarily or permanently physically 842 and/or logically not a part of the system. It 843 is an implementation-specific matter as to 844 whether the agent effectively removes notPresent 845 entries from the table. 847 A status of operational(2) indicates that the 848 group is functioning, and a status of 849 malfunctioning(3) indicates that the group is 850 malfunctioning in some way." 851 ::= { vgRptrBasicGroupEntry 3 } 853 vgRptrGroupPortCapacity OBJECT-TYPE 854 SYNTAX Integer32 (1..2146483647) 855 MAX-ACCESS read-only 856 STATUS current 857 DESCRIPTION 858 "The vgRptrGroupPortCapacity is the number of 859 ports that can be contained within the group. 860 Valid range is 1-2147483647. Within each group, 861 the ports are uniquely numbered in the range from 862 1 to vgRptrGroupPortCapacity. 864 Some ports may not be present in the system, in 865 which case the actual number of ports present will 866 be less than the value of vgRptrGroupPortCapacity. 867 The number of ports present is never greater than 868 the value of vgRptrGroupPortCapacity. 870 Note: In practice, this will generally be the 871 number of ports on a module, card, or board, and 872 the port numbers will correspond to numbers marked 873 on the physical embodiment." 874 REFERENCE 875 "IEEE Standard 802.12-1995, 13.2.4.4.1, 876 aGroupPortCapacity." 877 ::= { vgRptrBasicGroupEntry 4 } 879 vgRptrGroupCablesBundled OBJECT-TYPE 880 SYNTAX INTEGER { 881 someCablesBundled(1), 882 noCablesBundled(2) 883 } 884 MAX-ACCESS read-write 885 STATUS current 886 DESCRIPTION 887 "This object is used to indicate whether there are 888 any four-pair UTP links connected to this group 889 that are contained in a cable bundle with multiple 890 four-pair groups (e.g. a 25-pair bundle). Bundled 891 cable may only be used for repeater-to-end node 892 links where the end node is not in promiscuous 893 mode. 895 When a broadcast or multicast packet is received 896 from a port on this group that is not a 897 promiscuous or cascaded port, the packet will be 898 buffered completely before being repeated if 899 this object is set to 'someCablesBundled(1)'. 900 When this object is equal to 'noCablesBundled(2)', 901 all packets received from ports on this group will 902 be repeated as the frame is being received. 904 Note that the value 'someCablesBundled(1)' will 905 work in the vast majority of all installations, 906 regardless of whether or not any cables are 907 physically in a bundle, since packets received 908 from promiscuous and cascaded ports automatically 909 avoid the store and forward. The main situation 910 in which 'noCablesBundled(2)' is beneficial is 911 when there is a large amount of multicast traffic 912 and the cables are not in a bundle. 914 The value of this object should be preserved 915 across repeater resets and power failures." 916 REFERENCE 917 "IEEE Standard 802.12-1995, 13.2.4.4.1, 918 aGroupCablesBundled." 919 ::= { vgRptrBasicGroupEntry 5 } 921 vgRptrBasicPort OBJECT IDENTIFIER ::= { vgRptrBasic 3 } 923 vgRptrBasicPortTable OBJECT-TYPE 924 SYNTAX SEQUENCE OF VgRptrBasicPortEntry 925 MAX-ACCESS not-accessible 926 STATUS current 927 DESCRIPTION 928 "A table containing configuration and status 929 information about 802.12 repeater ports in the 930 system. The number of entries is independent of 931 the number of repeaters in the managed system." 932 ::= { vgRptrBasicPort 1 } 934 vgRptrBasicPortEntry OBJECT-TYPE 935 SYNTAX VgRptrBasicPortEntry 936 MAX-ACCESS not-accessible 937 STATUS current 938 DESCRIPTION 939 "An entry in the vgRptrBasicPortTable, containing 940 information about a single port." 941 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 942 ::= { vgRptrBasicPortTable 1 } 944 VgRptrBasicPortEntry ::= 945 SEQUENCE { 946 vgRptrPortIndex Integer32, 947 vgRptrPortType INTEGER, 948 vgRptrPortAdminStatus INTEGER, 949 vgRptrPortOperStatus INTEGER, 950 vgRptrPortSupportedPromiscMode INTEGER, 951 vgRptrPortSupportedCascadeMode INTEGER, 952 vgRptrPortAllowedTrainType INTEGER, 953 vgRptrPortLastTrainConfig OCTET STRING, 954 vgRptrPortTrainingResult OCTET STRING, 955 vgRptrPortPriorityEnable TruthValue, 956 vgRptrPortRptrInfoIndex Integer32 957 } 959 vgRptrPortIndex OBJECT-TYPE 960 SYNTAX Integer32 (1..2147483647) 961 MAX-ACCESS not-accessible 962 STATUS current 963 DESCRIPTION 964 "This object identifies the port within the group 965 for which this entry contains information. This 966 identifies the port independently from the 967 repeater it may be attached to. The numbering 968 scheme for ports is implementation specific; 969 however, this value can never be greater than 970 vgRptrGroupPortCapacity for the associated group." 971 REFERENCE 972 "IEEE Standard 802.12-1995, 13.2.4.5.1, 973 aPortID." 974 ::= { vgRptrBasicPortEntry 1 } 976 vgRptrPortType OBJECT-TYPE 977 SYNTAX INTEGER { 978 cascadeExternal(1), 979 cascadeInternal(2), 980 localExternal(3), 981 localInternal(4) 982 } 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "Describes the type of port. One of the 987 following: 989 cascadeExternal - Port is an uplink with 990 physical connections which 991 are externally visible 992 cascadeInternal - Port is an uplink with 993 physical connections which 994 are not externally visible, 995 such as a connection to an 996 internal backplane in a 997 chassis 998 localExternal - Port is a downlink or local 999 port with externally 1000 visible connections 1001 localInternal - Port is a downlink or local 1002 port with connections which 1003 are not externally visible, 1004 such as a connection to an 1005 internal agent 1007 'internal' is used to identify ports which place 1008 traffic into the repeater, but do not have any 1009 external connections. Note that both DTE and 1010 cascaded repeater downlinks are considered 1011 'local' ports." 1012 REFERENCE 1013 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1014 aPortType." 1015 ::= { vgRptrBasicPortEntry 2 } 1017 vgRptrPortAdminStatus OBJECT-TYPE 1018 SYNTAX INTEGER { 1019 enabled(1), 1020 disabled(2) 1021 } 1022 MAX-ACCESS read-write 1023 STATUS current 1024 DESCRIPTION 1025 "Port enable/disable function. Enabling a 1026 disabled port will cause training to be 1027 initiated by the training initiator (the slave 1028 mode device) on the link. Setting this object to 1029 disabled(2) disables the port. 1031 A disabled port neither transmits nor receives. 1032 Once disabled, a port must be explicitly enabled 1033 to restore operation. A port which is disabled 1034 when power is lost or when a reset is exerted 1035 shall remain disabled when normal operation 1036 resumes. 1038 The value of this object should be preserved 1039 across repeater resets and power failures." 1040 REFERENCE 1041 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1042 aPortAdministrativeState." 1043 ::= { vgRptrBasicPortEntry 3 } 1045 vgRptrPortOperStatus OBJECT-TYPE 1046 SYNTAX INTEGER { 1047 active(1), 1048 inactive(2), 1049 training(3) 1050 } 1051 MAX-ACCESS read-only 1052 STATUS current 1053 DESCRIPTION 1054 "Current status for the port as specified by the 1055 PORT_META_STATE in the port process module of 1056 clause 12 [IEEE Std 802.12]. 1058 During initialization or any link warning 1059 conditions, vgRptrPortStatus will be 1060 'inactive(2)'. 1062 When Training_Up is received by the repeater on a 1063 local port (or when Training_Down is received on 1064 a cascade port), vgRptrPortStatus will change to 1065 'training(3)' and vgRptrTrainingResult can be 1066 monitored to see the detailed status regarding 1067 training. 1069 When 24 consecutive good FCS packets are exchanged 1070 and the configuration bits are OK, 1071 vgRptrPortStatus will change to 'active(1)'. 1073 A disabled port shall have a port status of 1074 'inactive(2)'." 1075 REFERENCE 1076 "IEEE Standard 802.12, 13.2.4.5.1, 1077 aPortStatus." 1078 ::= { vgRptrBasicPortEntry 4 } 1080 vgRptrPortSupportedPromiscMode OBJECT-TYPE 1081 SYNTAX INTEGER { 1082 singleModeOnly(1), 1083 singleOrPromiscMode(2), 1084 promiscModeOnly(3) 1085 } 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "This object describes whether the port hardware 1090 is capable of supporting promiscuous mode, single 1091 address mode (i.e., repeater filters unicasts not 1092 addressed to the end station attached to this 1093 port), or both. A port for which vgRptrPortType 1094 is equal to 'cascadeInternal' or 'cascadeExternal' 1095 will always have a value of 'promiscModeOnly' for 1096 this object." 1097 REFERENCE 1098 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1099 aSupportedPromiscMode." 1100 ::= { vgRptrBasicPortEntry 5 } 1102 vgRptrPortSupportedCascadeMode OBJECT-TYPE 1103 SYNTAX INTEGER { 1104 endNodesOnly(1), 1105 endNodesOrRepeaters(2), 1106 cascadePort(3) 1107 } 1108 MAX-ACCESS read-only 1109 STATUS current 1110 DESCRIPTION 1111 "This object describes whether the port hardware 1112 is capable of supporting cascaded repeaters, end 1113 nodes, or both. A port for which vgRptrPortType 1114 is equal to 'cascadeInternal' or 1115 'cascadeExternal' will always have a value of 1116 'cascadePort' for this object." 1117 REFERENCE 1118 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1119 aSupportedCascadeMode." 1120 ::= { vgRptrBasicPortEntry 6 } 1122 vgRptrPortAllowedTrainType OBJECT-TYPE 1123 SYNTAX INTEGER { 1124 allowEndNodesOnly(1), 1125 allowPromiscuousEndNodes(2), 1126 allowEndNodesOrRepeaters(3), 1127 allowAnything(4) 1128 } 1129 MAX-ACCESS read-write 1130 STATUS current 1131 DESCRIPTION 1132 "This security object is set by the network 1133 manager to configure what type of device is 1134 permitted to connect to the port. One of the 1135 following values: 1137 allowEndNodesOnly - only non- 1138 promiscuous end 1139 nodes permitted. 1140 allowPromiscuousEndNodes - promiscuous or 1141 non-promiscuous 1142 end nodes 1143 permitted 1144 allowEndNodesOrRepeaters - repeaters or non- 1145 promiscuous end 1146 nodes permitted 1147 allowAnything - repeaters, 1148 promiscuous or 1149 non-promiscuous 1150 end nodes 1151 permitted 1153 For a port for which vgRptrPortType is equal to 1154 'cascadeInternal' or 'cascadeExternal', the 1155 corresponding instance of this object may not be 1156 set to 'allowEndNodesOnly' or 1157 'allowPromiscuousEndNodes'. 1159 The agent must reject a SET of this object if the 1160 value includes no capabilities that are 1161 supported by this port's hardware, as defined by 1162 the values of the corresponding instances of 1163 vgRptrPortSupportedPromiscMode and 1164 vgRptrPortSupportedCascadeMode. 1166 Note that vgRptrPortSupportPromiscMode and 1167 vgRptrPortSupportedCascadeMode represent what the 1168 port hardware is capable of supporting. 1169 vgRptrPortAllowedTrainType is used for setting an 1170 administrative policy for a port. The actual set 1171 of training configurations that will be allowed 1172 to succeed on a port is the intersection of what 1173 the hardware will support and what is 1174 administratively allowed. The above requirement 1175 on what values may be set to this object says that 1176 the intersection of what is supported and what is 1177 allowed must be non-empty. In other words, it 1178 must not result in a situation in which nothing 1179 would be allowed to train on that port. However, 1180 a value can be set to this object as long as the 1181 combination of this object and what is supported 1182 by the hardware would still leave at least one 1183 configuration that could successfully train on the 1184 port. 1186 The value of this object should be preserved 1187 across repeater resets and power failures." 1188 REFERENCE 1189 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1190 aAllowableTrainingType." 1191 ::= { vgRptrBasicPortEntry 7 } 1193 vgRptrPortLastTrainConfig OBJECT-TYPE 1194 SYNTAX OCTET STRING (SIZE(2)) 1195 MAX-ACCESS read-only 1196 STATUS current 1197 DESCRIPTION 1198 "This object is a 16 bit field. For local ports, 1199 this object contains the requested configuration 1200 field from the most recent error-free training 1201 request frame sent by the device connected to 1202 the port. For cascade ports, this object contains 1203 the responder's allowed configuration field from 1204 the most recent error-free training response frame 1205 received in response to training initiated by this 1206 repeater. The format of the current version of 1207 this field is described in section 3.2. Please 1208 refer to the most recent version of the IEEE 1209 802.12 standard for the most up-to-date definition 1210 of the format of this object." 1211 REFERENCE 1212 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1213 aLastTrainingConfig." 1214 ::= { vgRptrBasicPortEntry 8 } 1216 vgRptrPortTrainingResult OBJECT-TYPE 1217 SYNTAX OCTET STRING (SIZE(3)) 1218 MAX-ACCESS read-only 1219 STATUS current 1220 DESCRIPTION 1221 "This 18 bit field is used to indicate the result 1222 of training. It contains two bits which indicate 1223 if error-free training frames have been received, 1224 and it also contains the 16 bits of the allowed 1225 configuration field from the most recent 1226 error-free training response frame on the port. 1228 First Octet: Second and Third Octets: 1229 7 6 5 4 3 2 1 0 1230 +-+-+-+-+-+-+-+-+-----------------------------+ 1231 |0|0|0|0|0|0|V|G| allowed configuration field | 1232 +-+-+-+-+-+-+-+-+-----------------------------+ 1234 V: Valid: set when at least one error-free 1235 training frame has been received. 1236 Indicates the 16 training configuration 1237 bits in vgRptrPortLastTrainConfig and 1238 vgRptrPortTrainingResult contain valid 1239 information. This bit is cleared when 1240 vgRptrPortStatus transitions to the 1241 'inactive' or 'training' state. 1242 G: LinkGood: indicates the link hardware is 1243 OK. Set if 24 consecutive error-free 1244 training packets have been exchanged. 1245 Cleared when a training packet with 1246 errors is received, or when 1247 vgRptrPortStatus transitions to the 1248 'inactive' or 'training' state. 1250 The format of the current version of the allowed 1251 configuration field is described in section 3.2. 1252 Please refer to the most recent version of the 1253 IEEE 802.12 standard for the most up-to-date 1254 definition of the format of this field. 1256 If the port is in training, a management station 1257 can examine this object to see if any training 1258 packets have been passed successfully. If there 1259 have been any good training packets, the Valid 1260 bit will be set and the management station can 1261 examine the allowed configuration field to see if 1262 there is a duplicate address, configuration, or 1263 security problem. 1265 Note that on a repeater local port, this repeater 1266 generates the training response bits, while on 1267 a cascade port, the device at the upper end of 1268 the link originated the training response bits." 1269 REFERENCE 1270 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1271 aTrainingResult." 1272 ::= { vgRptrBasicPortEntry 9 } 1274 vgRptrPortPriorityEnable OBJECT-TYPE 1275 SYNTAX TruthValue 1276 MAX-ACCESS read-write 1277 STATUS current 1278 DESCRIPTION 1279 "A configuration flag used to determine whether 1280 the repeater will service high priority requests 1281 received on the port as high priority or normal 1282 priority. When 'false', high priority requests 1283 on this port will be serviced as normal priority. 1285 The setting of this object has no effect on a 1286 cascade port. Also note that the setting of this 1287 object has no effect on a port connected to a 1288 cascaded repeater. In both of these cases, this 1289 setting is treated as always 'true'. The value 1290 'false' only has an effect when the port is a 1291 localInternal or localExternal port connected to 1292 an end node. 1294 The value of this object should be preserved 1295 across repeater resets and power failures." 1296 REFERENCE 1297 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1298 aPriorityEnable." 1299 ::= { vgRptrBasicPortEntry 10 } 1301 vgRptrPortRptrInfoIndex OBJECT-TYPE 1302 SYNTAX Integer32 (0..2147483647) 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "This object identifies the repeater that this 1307 port is currently mapped to. The repeater 1308 identified by a particular value of this object 1309 is the same as that identified by the same value 1310 of vgRptrInfoIndex. A value of zero indicates 1311 that this port is not currently mapped to any 1312 repeater." 1313 ::= { vgRptrBasicPortEntry 11 } 1315 vgRptrMonitor OBJECT IDENTIFIER ::= { vgRptrObjects 2 } 1317 vgRptrMonRepeater OBJECT IDENTIFIER ::= { vgRptrMonitor 1 } 1319 vgRptrMonitorTable OBJECT-TYPE 1320 SYNTAX SEQUENCE OF VgRptrMonitorEntry 1321 MAX-ACCESS not-accessible 1322 STATUS current 1323 DESCRIPTION 1324 "A table of performance and error statistics for 1325 each repeater in the system. The instance of the 1326 vgRptrInfoLastChange associated with a repeater 1327 is used to indicate possible discontinuities of 1328 the counters in this table that are associated 1329 with the same repeater." 1330 ::= { vgRptrMonRepeater 1 } 1332 vgRptrMonitorEntry OBJECT-TYPE 1333 SYNTAX VgRptrMonitorEntry 1334 MAX-ACCESS not-accessible 1335 STATUS current 1336 DESCRIPTION 1337 "An entry in the table, containing statistics 1338 for a single repeater." 1339 INDEX { vgRptrInfoIndex } 1340 ::= { vgRptrMonitorTable 1 } 1342 VgRptrMonitorEntry ::= 1343 SEQUENCE { 1344 vgRptrMonTotalReadableFrames Counter32, 1345 vgRptrMonTotalReadableOctets Counter32, 1346 vgRptrMonReadableOctetRollovers Counter32, 1347 vgRptrMonHCTotalReadableOctets Counter64, 1348 vgRptrMonTotalErrors Counter32 1349 } 1351 vgRptrMonTotalReadableFrames OBJECT-TYPE 1352 SYNTAX Counter32 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "The total number of good frames of valid frame 1357 length that have been received on all ports in 1358 this repeater. If an implementation cannot 1359 obtain a count of frames as seen by the repeater 1360 itself, this counter may be implemented as the 1361 summation of the values of the 1362 vgRptrPortReadableFrames counters for all of the 1363 ports in this repeater. 1365 This counter may experience a discontinuity when 1366 the value of the corresponding instance of 1367 vgRptrInfoLastChange changes." 1368 ::= { vgRptrMonitorEntry 1 } 1370 vgRptrMonTotalReadableOctets OBJECT-TYPE 1371 SYNTAX Counter32 1372 MAX-ACCESS read-only 1373 STATUS current 1374 DESCRIPTION 1375 "The total number of octets contained in good 1376 frames that have been received on all ports in 1377 this repeater. If an implementation cannot 1378 obtain a count of octets as seen by the repeater 1379 itself, this counter may be implemented as the 1380 summation of the values of the 1381 vgRptrPortReadableOctets counters for all of the 1382 ports in this repeater. 1384 Note that this counter can roll over very 1385 quickly. A management station is advised to 1386 also poll the vgRptrReadableOctetRollovers 1387 object, or to use the 64-bit counter defined by 1388 vgRptrMonHCTotalReadableOctets instead of the 1389 two 32-bit counters. 1391 This two-counter mechanism is provided for those 1392 network management protocols that do not support 1393 64-bit counters (e.g. SNMPv1). Note that 1394 retrieval of these two counters in the same PDU 1395 is NOT guaranteed to be atomic. 1397 This counter may experience a discontinuity when 1398 the value of the corresponding instance of 1399 vgRptrInfoLastChange changes." 1400 ::= { vgRptrMonitorEntry 2 } 1402 vgRptrMonReadableOctetRollovers OBJECT-TYPE 1403 SYNTAX Counter32 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The total number of times that the associated 1408 instance of the vgRptrMonTotalReadableOctets 1409 counter has rolled over. 1411 This two-counter mechanism is provided for those 1412 network management protocols that do not support 1413 64-bit counters (e.g. SNMPv1). Note that 1414 retrieval of these two counters in the same PDU 1415 is NOT guaranteed to be atomic. 1417 This counter may experience a discontinuity when 1418 the value of the corresponding instance of 1419 vgRptrInfoLastChange changes." 1420 ::= { vgRptrMonitorEntry 3 } 1422 vgRptrMonHCTotalReadableOctets OBJECT-TYPE 1423 SYNTAX Counter64 1424 MAX-ACCESS read-only 1425 STATUS current 1426 DESCRIPTION 1427 "The total number of octets contained in good 1428 frames that have been received on all ports in 1429 this repeater. If an implementation cannot 1430 obtain a count of octets as seen by the repeater 1431 itself, this counter may be implemented as the 1432 summation of the values of the 1433 vgRptrPortHCReadableOctets counters for all of the 1434 ports in this repeater. 1436 This counter is a 64 bit version of 1437 vgRptrMonTotalReadableOctets. It should be used 1438 by Network Management protocols which support 64 1439 bit counters (e.g. SNMPv2). 1441 This counter may experience a discontinuity when 1442 the value of the corresponding instance of 1443 vgRptrInfoLastChange changes." 1444 ::= { vgRptrMonitorEntry 4 } 1446 vgRptrMonTotalErrors OBJECT-TYPE 1447 SYNTAX Counter32 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "The total number of errors which have occurred on 1452 all of the ports in this repeater. If an 1453 implementation cannot obtain a count of these 1454 errors as seen by the repeater itself, this 1455 counter may be implemented as the summation of the 1456 values of the vgRptrPortIPMFrames, 1457 vgRptrPortOversizeFrames, and 1458 vgRptrPortDataErrorFrames counters for all of the 1459 ports in this repeater. 1461 This counter may experience a discontinuity when 1462 the value of the corresponding instance of 1463 vgRptrInfoLastChange changes." 1464 ::= { vgRptrMonitorEntry 5 } 1466 vgRptrMonGroup OBJECT IDENTIFIER ::= { vgRptrMonitor 2 } 1467 -- Currently unused 1469 vgRptrMonPort OBJECT IDENTIFIER ::= { vgRptrMonitor 3 } 1471 vgRptrMonPortTable OBJECT-TYPE 1472 SYNTAX SEQUENCE OF VgRptrMonPortEntry 1473 MAX-ACCESS not-accessible 1474 STATUS current 1475 DESCRIPTION 1476 "A table of performance and error statistics for 1477 the ports. The columnar object 1478 vgRptrPortLastChange is used to indicate possible 1479 discontinuities of counter type columnar objects 1480 in this table." 1481 ::= { vgRptrMonPort 1 } 1483 vgRptrMonPortEntry OBJECT-TYPE 1484 SYNTAX VgRptrMonPortEntry 1485 MAX-ACCESS not-accessible 1486 STATUS current 1487 DESCRIPTION 1488 "An entry in the vgRptrMonPortTable, containing 1489 performance and error statistics for a single 1490 port." 1491 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 1492 ::= { vgRptrMonPortTable 1 } 1494 VgRptrMonPortEntry ::= 1495 SEQUENCE { 1496 vgRptrPortReadableFrames Counter32, 1497 vgRptrPortReadableOctets Counter32, 1498 vgRptrPortReadOctetRollovers Counter32, 1499 vgRptrPortHCReadableOctets Counter64, 1500 vgRptrPortUnreadableOctets Counter32, 1501 vgRptrPortUnreadOctetRollovers Counter32, 1502 vgRptrPortHCUnreadableOctets Counter64, 1503 vgRptrPortHighPriorityFrames Counter32, 1504 vgRptrPortHighPriorityOctets Counter32, 1505 vgRptrPortHighPriOctetRollovers Counter32, 1506 vgRptrPortHCHighPriorityOctets Counter64, 1507 vgRptrPortNormPriorityFrames Counter32, 1508 vgRptrPortNormPriorityOctets Counter32, 1509 vgRptrPortNormPriOctetRollovers Counter32, 1510 vgRptrPortHCNormPriorityOctets Counter64, 1511 vgRptrPortBroadcastFrames Counter32, 1512 vgRptrPortMulticastFrames Counter32, 1513 vgRptrPortNullAddressedFrames Counter32, 1514 vgRptrPortIPMFrames Counter32, 1515 vgRptrPortOversizeFrames Counter32, 1516 vgRptrPortDataErrorFrames Counter32, 1517 vgRptrPortPriorityPromotions Counter32, 1518 vgRptrPortTransitionToTrainings Counter32, 1519 vgRptrPortLastChange TimeStamp 1520 } 1522 vgRptrPortReadableFrames OBJECT-TYPE 1523 SYNTAX Counter32 1524 MAX-ACCESS read-only 1525 STATUS current 1526 DESCRIPTION 1527 "This object is the number of good frames of 1528 valid frame length that have been received on 1529 this port. This counter is incremented by one 1530 for each frame received on the port which is not 1531 counted by any of the following error counters: 1532 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1533 vgRptrPortNullAddressedFrames, or 1534 vgRptrPortDataErrorFrames. 1536 This counter may experience a discontinuity when 1537 the value of the corresponding instance of 1538 vgRptrPortLastChange changes." 1539 REFERENCE 1540 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1541 aReadableFramesReceived." 1542 ::= { vgRptrMonPortEntry 1 } 1544 vgRptrPortReadableOctets OBJECT-TYPE 1545 SYNTAX Counter32 1546 MAX-ACCESS read-only 1547 STATUS current 1548 DESCRIPTION 1549 "This object is a count of the number of octets 1550 contained in good frames that have been received 1551 on this port. This counter is incremented by 1552 OctetCount for each frame received on this port 1553 which has been determined to be a readable frame 1554 (i.e. each frame counted by 1555 vgRptrPortReadableFrames). 1557 Note that this counter can roll over very 1558 quickly. A management station is advised to 1559 also poll the vgRptrPortReadOctetRollovers 1560 object, or to use the 64-bit counter defined by 1561 vgRptrPortHCReadableOctets instead of the two 1562 32-bit counters. 1564 This two-counter mechanism is provided for those 1565 network management protocols that do not support 1566 64-bit counters (e.g. SNMPv1). Note that 1567 retrieval of these two counters in the same PDU 1568 is NOT guaranteed to be atomic. 1570 This counter may experience a discontinuity when 1571 the value of the corresponding instance of 1572 vgRptrPortLastChange changes." 1573 REFERENCE 1574 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1575 aReadableOctetsReceived." 1576 ::= { vgRptrMonPortEntry 2 } 1578 vgRptrPortReadOctetRollovers OBJECT-TYPE 1579 SYNTAX Counter32 1580 MAX-ACCESS read-only 1581 STATUS current 1582 DESCRIPTION 1583 "This object is a count of the number of times 1584 that the associated instance of the 1585 vgRptrPortReadableOctets counter has rolled over. 1587 This two-counter mechanism is provided for those 1588 network management protocols that do not support 1589 64-bit counters (e.g. SNMPv1). Note that 1590 retrieval of these two counters in the same PDU 1591 is NOT guaranteed to be atomic. 1593 This counter may experience a discontinuity when 1594 the value of the corresponding instance of 1595 vgRptrPortLastChange changes." 1596 REFERENCE 1597 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1598 aReadableOctetsReceived." 1599 ::= { vgRptrMonPortEntry 3 } 1601 vgRptrPortHCReadableOctets OBJECT-TYPE 1602 SYNTAX Counter64 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "This object is a count of the number of octets 1607 contained in good frames that have been received 1608 on this port. This counter is incremented by 1609 OctetCount for each frame received on this port 1610 which has been determined to be a readable frame 1611 (i.e. each frame counted by 1612 vgRptrPortReadableFrames). 1614 This counter is a 64 bit version of 1615 vgRptrPortReadableOctets. It should be used by 1616 Network Management protocols which support 64 bit 1617 counters (e.g. SNMPv2). 1619 This counter may experience a discontinuity when 1620 the value of the corresponding instance of 1621 vgRptrPortLastChange changes." 1622 REFERENCE 1623 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1624 aReadableOctetsReceived." 1625 ::= { vgRptrMonPortEntry 4 } 1627 vgRptrPortUnreadableOctets OBJECT-TYPE 1628 SYNTAX Counter32 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "This object is a count of the number of octets 1633 contained in invalid frames that have been 1634 received on this port. This counter is 1635 incremented by OctetCount for each frame received 1636 on this port which is counted by 1637 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1638 vgRptrPortNullAddressedFrames, or 1639 vgRptrPortDataErrorFrames. This counter can be 1640 combined with vgRptrPortReadableOctets to 1641 calculate network utilization. 1643 Note that this counter can roll over very 1644 quickly. A management station is advised to 1645 also poll the vgRptrPortUnreadOctetRollovers 1646 object, or to use the 64-bit counter defined by 1647 vgRptrPortHCUnreadableOctets instead of the two 1648 32-bit counters. 1650 This two-counter mechanism is provided for those 1651 network management protocols that do not support 1652 64-bit counters (e.g. SNMPv1). Note that 1653 retrieval of these two counters in the same PDU 1654 is NOT guaranteed to be atomic. 1656 This counter may experience a discontinuity when 1657 the value of the corresponding instance of 1658 vgRptrPortLastChange changes." 1659 REFERENCE 1660 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1661 aOctetsInUnreadableFramesRcvd." 1662 ::= { vgRptrMonPortEntry 5 } 1664 vgRptrPortUnreadOctetRollovers OBJECT-TYPE 1665 SYNTAX Counter32 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "This object is a count of the number of times 1670 that the associated instance of the 1671 vgRptrPortUnreadableOctets counter has rolled 1672 over. 1674 This two-counter mechanism is provided for those 1675 network management protocols that do not support 1676 64-bit counters (e.g. SNMPv1). Note that 1677 retrieval of these two counters in the same PDU 1678 is NOT guaranteed to be atomic. 1680 This counter may experience a discontinuity when 1681 the value of the corresponding instance of 1682 vgRptrPortLastChange changes." 1683 REFERENCE 1684 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1685 aOctetsInUnreadableFramesRcvd." 1686 ::= { vgRptrMonPortEntry 6 } 1688 vgRptrPortHCUnreadableOctets OBJECT-TYPE 1689 SYNTAX Counter64 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "This object is a count of the number of octets 1694 contained in invalid frames that have been 1695 received on this port. This counter is 1696 incremented by OctetCount for each frame received 1697 on this port which is counted by 1698 vgRptrPortIPMFrames, vgRptrPortOversizeFrames, 1699 vgRptrPortNullAddressedFrames, or 1700 vgRptrPortDataErrorFrames. This counter can be 1701 combined with vgRptrPortHCReadableOctets to 1702 calculate network utilization. 1704 This counter is a 64 bit version of 1705 vgRptrPortUnreadableOctets. It should be used 1706 by Network Management protocols which support 64 1707 bit counters (e.g. SNMPv2). 1709 This counter may experience a discontinuity when 1710 the value of the corresponding instance of 1711 vgRptrPortLastChange changes." 1712 REFERENCE 1713 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1714 aOctetsInUnreadableFramesRcvd." 1715 ::= { vgRptrMonPortEntry 7 } 1717 vgRptrPortHighPriorityFrames OBJECT-TYPE 1718 SYNTAX Counter32 1719 MAX-ACCESS read-only 1720 STATUS current 1721 DESCRIPTION 1722 "This object is a count of high priority frames 1723 that have been received on this port. This 1724 counter is incremented by one for each high 1725 priority frame received on this port. This 1726 counter includes both good and bad high priority 1727 frames, as well as high priority training frames. 1728 This counter does not include normal priority 1729 frames which were priority promoted. 1731 This counter may experience a discontinuity when 1732 the value of the corresponding instance of 1733 vgRptrPortLastChange changes." 1734 REFERENCE 1735 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1736 aHighPriorityFramesReceived." 1737 ::= { vgRptrMonPortEntry 8 } 1739 vgRptrPortHighPriorityOctets OBJECT-TYPE 1740 SYNTAX Counter32 1741 MAX-ACCESS read-only 1742 STATUS current 1743 DESCRIPTION 1744 "This object is a count of the number of octets 1745 contained in high priority frames that have been 1746 received on this port. This counter is 1747 incremented by OctetCount for each frame received 1748 on this port which is counted by 1749 vgRptrPortHighPriorityFrames. 1751 Note that this counter can roll over very 1752 quickly. A management station is advised to 1753 also poll the vgRptrPortHighPriOctetRollovers 1754 object, or to use the 64-bit counter defined by 1755 vgRptrPortHCHighPriorityOctets instead of the two 1756 32-bit counters. 1758 This two-counter mechanism is provided for those 1759 network management protocols that do not support 1760 64-bit counters (e.g. SNMPv1). Note that 1761 retrieval of these two counters in the same PDU 1762 is NOT guaranteed to be atomic. 1764 This counter may experience a discontinuity when 1765 the value of the corresponding instance of 1766 vgRptrPortLastChange changes." 1767 REFERENCE 1768 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1769 aHighPriorityOctetsReceived." 1770 ::= { vgRptrMonPortEntry 9 } 1772 vgRptrPortHighPriOctetRollovers OBJECT-TYPE 1773 SYNTAX Counter32 1774 MAX-ACCESS read-only 1775 STATUS current 1776 DESCRIPTION 1777 "This object is a count of the number of times 1778 that the associated instance of the 1779 vgRptrPortHighPriorityOctets counter has rolled 1780 over. 1782 This two-counter mechanism is provided for those 1783 network management protocols that do not support 1784 64-bit counters (e.g. SNMPv1). Note that 1785 retrieval of these two counters in the same PDU 1786 is NOT guaranteed to be atomic. 1788 This counter may experience a discontinuity when 1789 the value of the corresponding instance of 1790 vgRptrPortLastChange changes." 1791 REFERENCE 1792 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1793 aHighPriorityOctetsReceived." 1794 ::= { vgRptrMonPortEntry 10 } 1796 vgRptrPortHCHighPriorityOctets OBJECT-TYPE 1797 SYNTAX Counter64 1798 MAX-ACCESS read-only 1799 STATUS current 1800 DESCRIPTION 1801 "This object is a count of the number of octets 1802 contained in high priority frames that have been 1803 received on this port. This counter is 1804 incremented by OctetCount for each frame received 1805 on this port which is counted by 1806 vgRptrPortHighPriorityFrames. 1808 This counter is a 64 bit version of 1809 vgRptrPortHighPriorityOctets. It should be used 1810 by Network Management protocols which support 1811 64 bit counters (e.g. SNMPv2). 1813 This counter may experience a discontinuity when 1814 the value of the corresponding instance of 1815 vgRptrPortLastChange changes." 1816 REFERENCE 1817 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1818 aHighPriorityOctetsReceived." 1819 ::= { vgRptrMonPortEntry 11 } 1821 vgRptrPortNormPriorityFrames OBJECT-TYPE 1822 SYNTAX Counter32 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "This object is a count of normal priority frames 1827 that have been received on this port. This 1828 counter is incremented by one for each normal 1829 priority frame received on this port. This 1830 counter includes both good and bad normal 1831 priority frames, as well as normal priority 1832 training frames and normal priority frames which 1833 were priority promoted. 1835 This counter may experience a discontinuity when 1836 the value of the corresponding instance of 1837 vgRptrPortLastChange changes." 1838 REFERENCE 1839 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1840 aNormalPriorityFramesReceived." 1841 ::= { vgRptrMonPortEntry 12 } 1843 vgRptrPortNormPriorityOctets OBJECT-TYPE 1844 SYNTAX Counter32 1845 MAX-ACCESS read-only 1846 STATUS current 1847 DESCRIPTION 1848 "This object is a count of the number of octets 1849 contained in normal priority frames that have 1850 been received on this port. This counter is 1851 incremented by OctetCount for each frame received 1852 on this port which is counted by 1853 vgRptrPortNormPriorityFrames. 1855 Note that this counter can roll over very 1856 quickly. A management station is advised to 1857 also poll the vgRptrPortNormPriOctetRollovers 1858 object, or to use the 64-bit counter defined by 1859 vgRptrPortHCNormPriorityOctets instead of the two 1860 32-bit counters. 1862 This two-counter mechanism is provided for those 1863 network management protocols that do not support 1864 64-bit counters (e.g. SNMPv1). Note that 1865 retrieval of these two counters in the same PDU 1866 is NOT guaranteed to be atomic. 1868 This counter may experience a discontinuity when 1869 the value of the corresponding instance of 1870 vgRptrPortLastChange changes." 1871 REFERENCE 1872 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1873 aNormalPriorityOctetsReceived." 1874 ::= { vgRptrMonPortEntry 13 } 1876 vgRptrPortNormPriOctetRollovers OBJECT-TYPE 1877 SYNTAX Counter32 1878 MAX-ACCESS read-only 1879 STATUS current 1880 DESCRIPTION 1881 "This object is a count of the number of times 1882 that the associated instance of the 1883 vgRptrPortNormPriorityOctets counter has rolled 1884 over. 1886 This two-counter mechanism is provided for those 1887 network management protocols that do not support 1888 64-bit counters (e.g. SNMPv1). Note that 1889 retrieval of these two counters in the same PDU 1890 is NOT guaranteed to be atomic. 1892 This counter may experience a discontinuity when 1893 the value of the corresponding instance of 1894 vgRptrPortLastChange changes." 1895 REFERENCE 1896 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1897 aNormalPriorityOctetsReceived." 1899 ::= { vgRptrMonPortEntry 14 } 1901 vgRptrPortHCNormPriorityOctets OBJECT-TYPE 1902 SYNTAX Counter64 1903 MAX-ACCESS read-only 1904 STATUS current 1905 DESCRIPTION 1906 "This object is a count of the number of octets 1907 contained in normal priority frames that have 1908 been received on this port. This counter is 1909 incremented by OctetCount for each frame received 1910 on this port which is counted by 1911 vgRptrPortNormPriorityFrames. 1913 This counter is a 64 bit version of 1914 vgRptrPortNormPriorityOctets. It should be used 1915 by Network Management protocols which support 1916 64 bit counters (e.g. SNMPv2). 1918 This counter may experience a discontinuity when 1919 the value of the corresponding instance of 1920 vgRptrPortLastChange changes." 1921 REFERENCE 1922 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1923 aNormalPriorityOctetsReceived." 1924 ::= { vgRptrMonPortEntry 15 } 1926 vgRptrPortBroadcastFrames OBJECT-TYPE 1927 SYNTAX Counter32 1928 MAX-ACCESS read-only 1929 STATUS current 1930 DESCRIPTION 1931 "This object is a count of broadcast packets that 1932 have been received on this port. This counter is 1933 incremented by one for each readable frame 1934 received on this port whose destination MAC 1935 address is the broadcast address. Frames 1936 counted by this counter are also counted by 1937 vgRptrPortReadableFrames. 1939 This counter may experience a discontinuity when 1940 the value of the corresponding instance of 1941 vgRptrPortLastChange changes." 1942 REFERENCE 1943 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1944 aBroadcastFramesReceived." 1945 ::= { vgRptrMonPortEntry 16 } 1947 vgRptrPortMulticastFrames OBJECT-TYPE 1948 SYNTAX Counter32 1949 MAX-ACCESS read-only 1950 STATUS current 1951 DESCRIPTION 1952 "This object is a count of multicast packets that 1953 have been received on this port. This counter is 1954 incremented by one for each readable frame 1955 received on this port whose destination MAC 1956 address has the group address bit set, but is not 1957 the broadcast address. Frames counted by this 1958 counter are also counted by 1959 vgRptrPortReadableFrames, but not by 1960 vgRptrPortBroadcastFrames. Note that when the 1961 value of the instance vgRptrInfoCurrentFramingType 1962 for the repeater that this port is associated 1963 with is equal to 'frameType88025', this count 1964 includes packets addressed to functional 1965 addresses. 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 aMulticastFramesReceived." 1973 ::= { vgRptrMonPortEntry 17 } 1975 vgRptrPortNullAddressedFrames OBJECT-TYPE 1976 SYNTAX Counter32 1977 MAX-ACCESS read-only 1978 STATUS current 1979 DESCRIPTION 1980 "This object is a count of null addressed packets 1981 that have been received on this port. This 1982 counter is incremented by one for each frame 1983 received on this port with a destination MAC 1984 address consisting of all zero bits. Both void 1985 and training frames are included in this 1986 counter. 1988 This counter may experience a discontinuity when 1989 the value of the corresponding instance of 1990 vgRptrPortLastChange changes." 1991 REFERENCE 1992 "IEEE Standard 802.12-1995, 13.2.4.5.1, 1993 aNullAddressedFramesReceived." 1994 ::= { vgRptrMonPortEntry 18 } 1996 vgRptrPortIPMFrames OBJECT-TYPE 1997 SYNTAX Counter32 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "This object is a count of the number of frames 2002 that have been received on this port with an 2003 invalid packet marker and no PMI errors. A 2004 repeater will write an invalid packet marker to 2005 the end of a frame containing errors as it is 2006 forwarded through the repeater to the other 2007 ports. This counter is incremented by one for 2008 each frame received on this port which has had an 2009 invalid packet marker added to the end of the 2010 frame. 2012 This counter indicates problems occurring in the 2013 domain of other repeaters, as opposed to problems 2014 with cables or devices directly attached to this 2015 repeater. 2017 This counter may experience a discontinuity when 2018 the value of the corresponding instance of 2019 vgRptrPortLastChange changes." 2020 REFERENCE 2021 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2022 aIPMFramesReceived." 2023 ::= { vgRptrMonPortEntry 19 } 2025 vgRptrPortOversizeFrames OBJECT-TYPE 2026 SYNTAX Counter32 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "This object is a count of oversize frames 2031 received on this port. This counter is 2032 incremented by one for each frame received on 2033 this port whose OctetCount is larger than the 2034 maximum legal frame size. 2036 The frame size which causes this counter to 2037 increment is dependent on the current value of 2038 vgRptrInfoCurrentFramingType for the repeater that 2039 the port is associated with. When 2040 vgRptrInfoCurrentFramingType is equal to 2041 frameType88023 this counter will increment for 2042 frames that are 1519 octets or larger. When 2043 vgRptrInfoCurrentFramingType is equal to 2044 frameType88025 this counter will increment for 2045 frames that are 4521 octets or larger. 2047 This counter may experience a discontinuity when 2048 the value of the corresponding instance of 2049 vgRptrPortLastChange changes." 2050 REFERENCE 2051 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2052 aOversizeFramesReceived." 2053 ::= { vgRptrMonPortEntry 20 } 2055 vgRptrPortDataErrorFrames OBJECT-TYPE 2056 SYNTAX Counter32 2057 MAX-ACCESS read-only 2058 STATUS current 2059 DESCRIPTION 2060 "This object is a count of errored frames 2061 received on this port. This counter is 2062 incremented by one for each frame received on 2063 this port with any of the following errors: bad 2064 FCS (with no IPM), PMI errors (excluding frames 2065 with an IPM error as the only PMI error), or 2066 undersize (with no IPM). Does not include 2067 packets counted by vgRptrPortIPMFrames, 2068 vgRptrPortOversizeFrames, or 2069 vgRptrPortNullAddressedFrames. 2071 This counter indicates problems with cables or 2072 devices directly connected to this repeater, while 2073 vgRptrPortIPMFrames indicates problems occurring 2074 in the domain of other repeaters. 2076 This counter may experience a discontinuity when 2077 the value of the corresponding instance of 2078 vgRptrPortLastChange changes." 2079 REFERENCE 2080 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2081 aDataErrorFramesReceived." 2082 ::= { vgRptrMonPortEntry 21 } 2084 vgRptrPortPriorityPromotions OBJECT-TYPE 2085 SYNTAX Counter32 2086 MAX-ACCESS read-only 2087 STATUS current 2088 DESCRIPTION 2089 "This counter is incremented by one each time the 2090 priority promotion timer has expired on this port 2091 and a normal priority frame is priority 2092 promoted. 2094 This counter may experience a discontinuity when 2095 the value of the corresponding instance of 2096 vgRptrPortLastChange changes." 2097 REFERENCE 2098 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2099 aPriorityPromotions." 2100 ::= { vgRptrMonPortEntry 22 } 2102 vgRptrPortTransitionToTrainings OBJECT-TYPE 2103 SYNTAX Counter32 2104 MAX-ACCESS read-only 2105 STATUS current 2106 DESCRIPTION 2107 "This counter is incremented by one each time the 2108 vgRptrPortStatus object for this port transitions 2109 into the 'training' state. 2111 This counter may experience a discontinuity when 2112 the value of the corresponding instance of 2113 vgRptrPortLastChange changes." 2114 REFERENCE 2115 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2116 aTransitionsIntoTraining." 2117 ::= { vgRptrMonPortEntry 23 } 2119 vgRptrPortLastChange OBJECT-TYPE 2120 SYNTAX TimeStamp 2121 MAX-ACCESS read-only 2122 STATUS current 2123 DESCRIPTION 2124 "The value of sysUpTime when the last of the 2125 following occurred: 2126 1) the agent cold- or warm-started; 2127 2) the row for the port was created 2128 (such as when a device or module was 2129 added to the system); or 2130 3) any condition that would cause one of 2131 the counters for the row to experience 2132 a discontinuity." 2133 ::= { vgRptrMonPortEntry 24 } 2135 vgRptrAddrTrack OBJECT IDENTIFIER ::= { vgRptrObjects 3 } 2137 vgRptrAddrTrackRptr 2138 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 1 } 2140 -- Currently unused 2142 vgRptrAddrTrackGroup 2143 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 2 } 2144 -- Currently unused 2146 vgRptrAddrTrackPort 2147 OBJECT IDENTIFIER ::= { vgRptrAddrTrack 3 } 2149 vgRptrAddrTrackTable OBJECT-TYPE 2150 SYNTAX SEQUENCE OF VgRptrAddrTrackEntry 2151 MAX-ACCESS not-accessible 2152 STATUS current 2153 DESCRIPTION 2154 "Table of address mapping information about the 2155 ports." 2156 ::= { vgRptrAddrTrackPort 1 } 2158 vgRptrAddrTrackEntry OBJECT-TYPE 2159 SYNTAX VgRptrAddrTrackEntry 2160 MAX-ACCESS not-accessible 2161 STATUS current 2162 DESCRIPTION 2163 "An entry in the table, containing address mapping 2164 information about a single port." 2165 INDEX { vgRptrGroupIndex, vgRptrPortIndex } 2166 ::= { vgRptrAddrTrackTable 1 } 2168 VgRptrAddrTrackEntry ::= 2169 SEQUENCE { 2170 vgRptrAddrLastTrainedAddress OCTET STRING, 2171 vgRptrAddrTrainedAddrChanges Counter32, 2172 vgRptrRptrDetectedDupAddress TruthValue, 2173 vgRptrMgrDetectedDupAddress TruthValue 2174 } 2176 vgRptrAddrLastTrainedAddress OBJECT-TYPE 2177 SYNTAX OCTET STRING (SIZE(0 | 6)) 2178 MAX-ACCESS read-only 2179 STATUS current 2180 DESCRIPTION 2181 "This object is the MAC address of the last 2182 station which succeeded in training on this port. 2183 A cascaded repeater may train using the null 2184 address. If no stations have succeeded in 2185 training on this port since the agent began 2186 monitoring the port activity, the agent shall 2187 return a string of length zero." 2188 REFERENCE 2189 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2190 aLastTrainedAddress." 2191 ::= { vgRptrAddrTrackEntry 1 } 2193 vgRptrAddrTrainedAddrChanges OBJECT-TYPE 2194 SYNTAX Counter32 2195 MAX-ACCESS read-only 2196 STATUS current 2197 DESCRIPTION 2198 "This counter is incremented by one for each time 2199 that the vgRptrAddrLastTrainedAddress object for 2200 this port changes." 2201 REFERENCE 2202 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2203 aTrainedAddressChanges." 2204 ::= { vgRptrAddrTrackEntry 2 } 2206 vgRptrRptrDetectedDupAddress OBJECT-TYPE 2207 SYNTAX TruthValue 2208 MAX-ACCESS read-only 2209 STATUS current 2210 DESCRIPTION 2211 "This object is used to indicate that the 2212 repeater detected an error-free training frame on 2213 this port with a non-null source MAC address which 2214 matches the value of vgRptrAddrLastTrainedAddress 2215 of another active port in the same repeater. This 2216 is reset to 'false' when an error-free training 2217 frame is received with a non-null source MAC 2218 address which does not match 2219 vgRptrAddrLastTrainedAddress of another port which 2220 is active in the same repeater. 2222 For the cascade port, this object will be 'true' 2223 if the 'D' bit in the most recently received 2224 error-free training response frame was set, 2225 indicating the device at the other end of the link 2226 believes that this repeater's cascade port is 2227 using a duplicate address. This may be because 2228 the device at the other end of the link detected a 2229 duplicate address itself, or, if the other device 2230 is also a repeater, it could be because 2231 vgRptrMgrDetectedDupAddress was set to 'true' on 2232 the port that this repeater's cascade port is 2233 connected to." 2234 REFERENCE 2235 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2236 aLocalRptrDetectedDupAddr." 2237 ::= { vgRptrAddrTrackEntry 3 } 2239 vgRptrMgrDetectedDupAddress OBJECT-TYPE 2240 SYNTAX TruthValue 2241 MAX-ACCESS read-write 2242 STATUS current 2243 DESCRIPTION 2244 "This object can be set by a management station 2245 when it detects that there is a duplicate MAC 2246 address. This object is OR'd with 2247 vgRptrRptrDetectedDupAddress to form the value of 2248 the 'D' bit in training response frames on this 2249 port. 2251 The purpose of this object is to provide a means 2252 for network management software to inform an end 2253 station that it is using a duplicate station 2254 address. Setting this object does not affect the 2255 current state of the link; the end station will 2256 not be informed of the duplicate address until it 2257 retrains for some reason. Note that regardless 2258 of its station address, the end station will not 2259 be able to train successfully until the network 2260 management software has set this object back to 2261 'false'. Although this object exists on 2262 cascade ports, it does not perform any function 2263 since this repeater is the initiator of training 2264 on a cascade port." 2265 REFERENCE 2266 "IEEE Standard 802.12-1995, 13.2.4.5.1, 2267 aCentralMgmtDetectedDupAddr." 2268 ::= { vgRptrAddrTrackEntry 4 } 2270 vgRptrTraps OBJECT IDENTIFIER ::= { vgRptrMIB 2 } 2271 vgRptrTrapPrefix OBJECT IDENTIFIER ::= { vgRptrTraps 0 } 2273 vgRptrHealth NOTIFICATION-TYPE 2274 OBJECTS { vgRptrInfoOperStatus } 2275 STATUS current 2276 DESCRIPTION 2277 "A vgRptrHealth trap conveys information related 2278 to the operational state of a repeater. This trap 2279 is sent when the value of an instance of 2280 vgRptrInfoOperStatus changes. The vgRptrHealth 2281 trap is not sent as a result of powering up a 2282 repeater. 2284 The vgRptrHealth trap must contain the instance of 2285 the vgRptrInfoOperStatus object associated with 2286 the affected repeater. 2288 The agent must throttle the generation of 2289 consecutive vgRptrHealth traps so that there is at 2290 least a five-second gap between traps of this 2291 type. When traps are throttled, they are dropped, 2292 not queued for sending at a future time. (Note 2293 that 'generating' a trap means sending to all 2294 configured recipients.)" 2295 REFERENCE 2296 "IEEE 802.12, Layer Management, 13.2.4.2.3, 2297 nRepeaterHealth." 2298 ::= { vgRptrTrapPrefix 1 } 2300 vgRptrResetEvent NOTIFICATION-TYPE 2301 OBJECTS { vgRptrInfoOperStatus } 2302 STATUS current 2303 DESCRIPTION 2304 "A vgRptrResetEvent trap conveys information 2305 related to the operational state of a repeater. 2306 This trap is sent on completion of a repeater 2307 reset action. A repeater reset action is defined 2308 as a transition to its initial state as specified 2309 in clause 12 [IEEE Std 802.12] when triggered by 2310 a management command. 2312 The vgRptrResetEvent trap is not sent when the 2313 agent restarts and sends an SNMP coldStart or 2314 warmStart trap. 2316 The vgRptrResetEvent trap must contain the 2317 instance of the vgRptrInfoOperStatus object 2318 associated with the affected repeater. 2320 The agent must throttle the generation of 2321 consecutive vgRptrResetEvent traps so that there 2322 is at least a five-second gap between traps of 2323 this type. When traps are throttled, they are 2324 dropped, not queued for sending at a future time. 2325 (Note that 'generating' a trap means sending to 2326 all configured recipients.)" 2327 REFERENCE 2328 "IEEE 802.12, Layer Management, 13.2.4.2.3, 2329 nRepeaterReset." 2331 ::= { vgRptrTrapPrefix 2 } 2333 -- conformance information 2335 vgRptrConformance OBJECT IDENTIFIER ::= { vgRptrMIB 3 } 2337 vgRptrCompliances 2338 OBJECT IDENTIFIER ::= { vgRptrConformance 1 } 2340 vgRptrGroups OBJECT IDENTIFIER ::= { vgRptrConformance 2 } 2342 -- compliance statements 2344 vgRptrCompliance MODULE-COMPLIANCE 2345 STATUS current 2346 DESCRIPTION 2347 "The compliance statement for managed 802.12 2348 repeaters." 2350 MODULE -- this module 2351 MANDATORY-GROUPS { vgRptrConfigGroup, 2352 vgRptrStatsGroup, 2353 vgRptrAddrGroup, 2354 vgRptrNotificationsGroup } 2356 GROUP vgRptrStats64Group 2357 DESCRIPTION 2358 "Implementation of this group is recommended 2359 for systems which can support Counter64." 2361 OBJECT vgRptrInfoDesiredFramingType 2362 MIN-ACCESS read-only 2363 DESCRIPTION 2364 "Write access to this object is not required 2365 in a repeater system that does not support 2366 configuration of framing types." 2368 MODULE SNMP-REPEATER-MIB 2369 GROUP snmpRptrGrpRptrAddrSearch 2370 DESCRIPTION 2371 "Implementation of this group is recommended 2372 for systems which have the necessary 2373 instrumentation to search all incoming data 2374 streams for a particular source MAC address." 2375 ::= { vgRptrCompliances 1 } 2377 -- units of conformance 2378 vgRptrConfigGroup OBJECT-GROUP 2379 OBJECTS { 2380 vgRptrInfoMACAddress, 2381 vgRptrInfoCurrentFramingType, 2382 vgRptrInfoDesiredFramingType, 2383 vgRptrInfoFramingCapability, 2384 vgRptrInfoTrainingVersion, 2385 vgRptrInfoOperStatus, 2386 vgRptrInfoReset, 2387 vgRptrInfoLastChange, 2388 vgRptrGroupObjectID, 2389 vgRptrGroupOperStatus, 2390 vgRptrGroupPortCapacity, 2391 vgRptrGroupCablesBundled, 2392 vgRptrPortType, 2393 vgRptrPortAdminStatus, 2394 vgRptrPortOperStatus, 2395 vgRptrPortSupportedPromiscMode, 2396 vgRptrPortSupportedCascadeMode, 2397 vgRptrPortAllowedTrainType, 2398 vgRptrPortLastTrainConfig, 2399 vgRptrPortTrainingResult, 2400 vgRptrPortPriorityEnable, 2401 vgRptrPortRptrInfoIndex 2402 } 2403 STATUS current 2404 DESCRIPTION 2405 "A collection of objects for managing the status 2406 and configuration of IEEE 802.12 repeaters." 2407 ::= { vgRptrGroups 1 } 2409 vgRptrStatsGroup OBJECT-GROUP 2410 OBJECTS { 2411 vgRptrMonTotalReadableFrames, 2412 vgRptrMonTotalReadableOctets, 2413 vgRptrMonReadableOctetRollovers, 2414 vgRptrMonTotalErrors, 2415 vgRptrPortReadableFrames, 2416 vgRptrPortReadableOctets, 2417 vgRptrPortReadOctetRollovers, 2418 vgRptrPortUnreadableOctets, 2419 vgRptrPortUnreadOctetRollovers, 2420 vgRptrPortHighPriorityFrames, 2421 vgRptrPortHighPriorityOctets, 2422 vgRptrPortHighPriOctetRollovers, 2423 vgRptrPortNormPriorityFrames, 2424 vgRptrPortNormPriorityOctets, 2425 vgRptrPortNormPriOctetRollovers, 2426 vgRptrPortBroadcastFrames, 2427 vgRptrPortMulticastFrames, 2428 vgRptrPortNullAddressedFrames, 2429 vgRptrPortIPMFrames, 2430 vgRptrPortOversizeFrames, 2431 vgRptrPortDataErrorFrames, 2432 vgRptrPortPriorityPromotions, 2433 vgRptrPortTransitionToTrainings, 2434 vgRptrPortLastChange 2435 } 2436 STATUS current 2437 DESCRIPTION 2438 "A collection of objects for providing statistics 2439 for IEEE 802.12 repeaters. Systems which support 2440 Counter64 should also implement 2441 vgRptrStats64Group." 2442 ::= { vgRptrGroups 2 } 2444 vgRptrStats64Group OBJECT-GROUP 2445 OBJECTS { 2446 vgRptrMonHCTotalReadableOctets, 2447 vgRptrPortHCReadableOctets, 2448 vgRptrPortHCUnreadableOctets, 2449 vgRptrPortHCHighPriorityOctets, 2450 vgRptrPortHCNormPriorityOctets 2451 } 2452 STATUS current 2453 DESCRIPTION 2454 "A collection of objects for providing statistics 2455 for IEEE 802.12 repeaters in a system that 2456 supports Counter64." 2457 ::= { vgRptrGroups 3 } 2459 vgRptrAddrGroup OBJECT-GROUP 2460 OBJECTS { 2461 vgRptrAddrLastTrainedAddress, 2462 vgRptrAddrTrainedAddrChanges, 2463 vgRptrRptrDetectedDupAddress, 2464 vgRptrMgrDetectedDupAddress 2465 } 2466 STATUS current 2467 DESCRIPTION 2468 "A collection of objects for tracking addresses 2469 on IEEE 802.12 repeaters." 2470 ::= { vgRptrGroups 4 } 2472 vgRptrNotificationsGroup NOTIFICATION-GROUP 2473 NOTIFICATIONS { 2474 vgRptrHealth, 2475 vgRptrResetEvent 2476 } 2477 STATUS current 2478 DESCRIPTION 2479 "A collection of notifications used to indicate 2480 802.12 repeater general status changes." 2481 ::= { vgRptrGroups 5 } 2483 END 2485 4. Acknowledgements 2487 This document was produced by the IETF 100VG-AnyLAN Working Group, 2488 whose efforts were greatly advanced by the contributions of the 2489 following people: 2491 Paul Chefurka 2492 Bob Faulk 2493 Jeff Johnson 2494 Karen Kimball 2495 David Lapp 2496 Jason Spofford 2497 Kaj Tesink 2499 This document is based on the work of IEEE 802.12. 2501 5. References 2503 [1] Information processing systems - Open Systems Interconnection - 2504 Specification of Abstract Syntax Notation One (ASN.1), 2505 International Organization for Standardization. International 2506 Standard 8824 (December, 1987). 2508 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2509 S. Waldbusser, "Structure of Management Information for Version 2510 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2511 SNMP Research, Inc., Cisco Systems, Inc., Dover Beach 2512 Consulting, Inc., International Network Services, January 1996. 2514 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2515 S. Waldbusser, "Textual Conventions for Version 2 of the Simple 2516 Network Management Protocol (SNMPv2)", RFC 1903, SNMP Research, 2517 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2518 International Network Services, January 1996. 2520 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2521 S. Waldbusser, "Conformance Statements for Version 2 of the 2522 Simple Network Management Protocol (SNMPv2)", RFC 1904, SNMP 2523 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 2524 Inc., International Network Services, January 1996. 2526 [5] McCloghrie, K., and M. Rose, "Management Information Base for 2527 Network Management of TCP/IP-based internets - MIB-II", STD 17, 2528 RFC 1213, Hughes LAN Systems, Performance Systems International, 2529 March 1991. 2531 [6] IEEE, "Demand Priority Access Method, Physical Layer and 2532 Repeater Specifications for 100 Mb/s Operation", IEEE Standard 2533 802.12-1995" 2535 [7] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, 2536 "Definitions of Managed Objects for IEEE 802.3 Repeater 2537 Devices", RFC 2108, 3Com Corporation, Madge Networks (Israel) 2538 Ltd., Cisco Systems, Inc., February, 1997. 2540 [8] McAnally, G., Gilbert, D., and J. Flick, "Conditional Grant of 2541 Rights to Specific Hewlett-Packard Patents In Conjunction With 2542 the Internet Engineering Task Force's Internet-Standard 2543 Network Management Framework", RFC 1988, August 1996. 2545 [9] Hewlett-Packard Company, US Patents 5,293,635 and 5,421,024. 2547 6. Security Considerations 2549 Certain management information defined in this MIB may be considered 2550 sensitive in some network environments. Therefore, authentication of 2551 received SNMP requests and controlled access to management 2552 information should be employed in such environments. The method for 2553 this authentication is a function of the SNMP Administrative 2554 Framework, and has not been expanded by this MIB. 2556 Several objects in the vgRptrConfigGroup allow write access. Setting 2557 these objects can have a serious effect on the operation of the 2558 network, including modifying the framing type of the network, 2559 resetting the repeater, enabling and disabling individual ports, and 2560 modifying the allowed capabilities of end stations attached to each 2561 port. It is recommended that implementers seriously consider whether 2562 set operations should be allowed without providing, at a minimum, 2563 authentication of request origin. 2565 One particular object in this MIB, vgRptrPortAllowedTrainType, is 2566 considered significant for providing operational security in an 2567 802.12 network. It is recommended that network administrators 2568 configure this object to the 'allowEndNodesOnly' value on all ports 2569 except ports which the administrator knows are attached to cascaded 2570 repeaters or devices which require promiscuous receive capability 2571 (bridges, switches, RMON probes, etc.). This will prevent 2572 unauthorized users from extending the network (by attaching cascaded 2573 repeaters or bridges) without the administrator's knowledge, and will 2574 prevent unauthorized end nodes from listening promiscuously to 2575 network traffic. 2577 7. Author's Address 2578 John Flick 2579 Hewlett Packard Company 2580 8000 Foothills Blvd. M/S 5556 2581 Roseville, CA 95747-5556 2583 Phone: +1 916 785 4018 2584 Email: johnf@hprnd.rose.hp.com 2586 Table of Contents 2588 1. The SNMP Network Management Framework ...................... 2 2589 1.1. Object Definitions ....................................... 2 2590 2. Overview ................................................... 3 2591 2.1. Repeater Management Model ................................ 3 2592 2.2. MAC Addresses ............................................ 4 2593 2.3. Master Mode and Slave Mode ............................... 4 2594 2.4. IEEE 802.12 Training Frames .............................. 5 2595 2.5. Structure of the MIB ..................................... 8 2596 2.5.1. Basic Definitions ...................................... 8 2597 2.5.2. Monitor Definitions .................................... 8 2598 2.5.3. Address Tracking Definitions ........................... 8 2599 2.6. Relationship to other MIBs ............................... 8 2600 2.6.1. Relationship to MIB-II ................................. 8 2601 2.6.1.1. Relationship to the 'system' group ................... 9 2602 2.6.1.2. Relationship to the 'interfaces' group ............... 9 2603 2.6.2. Relationship to the 802.3 Repeater MIB ................. 9 2604 2.7. Mapping of IEEE 802.12 Managed Objects ................... 11 2605 3. Definitions ................................................ 15 2606 4. Acknowledgements ........................................... 57 2607 5. References ................................................. 57 2608 6. Security Considerations .................................... 58 2609 7. Author's Address ........................................... 58