idnits 2.17.1 draft-ietf-rmonmib-rmon2-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-18) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- 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 Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' Rationale:' ) ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 3746 has weird spacing: '...ticular probe...' == Line 4200 has weird spacing: '... field octet...' == Line 4474 has weird spacing: '...se code bps...' == Line 4725 has weird spacing: '... octets cont...' == Line 4734 has weird spacing: '... octets cont...' == (1 more instance...) -- 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 (October 17, 1995) is 10411 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) -- Missing reference section? '1' on line 5675 looks like a reference -- Missing reference section? '2' on line 5681 looks like a reference -- Missing reference section? '3' on line 5686 looks like a reference -- Missing reference section? '4' on line 5692 looks like a reference -- Missing reference section? '5' on line 5698 looks like a reference -- Missing reference section? '6' on line 5704 looks like a reference -- Missing reference section? '9' on line 5721 looks like a reference -- Missing reference section? 'RFC1516' on line 1444 looks like a reference -- Missing reference section? 'RFC1449' on line 4731 looks like a reference -- Missing reference section? '7' on line 5709 looks like a reference -- Missing reference section? '8' on line 5715 looks like a reference -- Missing reference section? '10' on line 5726 looks like a reference Summary: 12 errors (**), 0 flaws (~~), 7 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Remote Network Monitoring Management Information Base 3 5 October 17, 1995 7 Editor: 9 Steven Waldbusser 11 waldbusser@ins.com 13 1. Status of this Memo 15 This document is an Internet-Draft. Internet-Drafts are 16 working documents of the Internet Engineering Task Force 17 (IETF), its areas, and its working groups. Note that other 18 groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months. Internet-Drafts may be updated, replaced, or 23 obsoleted by other documents at any time. It is not 24 appropriate to use Internet-Drafts as reference material or to 25 cite them other than as a ``working draft'' or ``work in 26 progress.'' 28 To learn the current status of any Internet-Draft, please 29 check the 1id-abstracts.txt listing contained in the Internet- 30 Drafts Shadow Directories on ds.internic.net, nic.nordu.net, 31 venera.isi.edu, or munnari.oz.au. 33 2. Abstract 35 This memo defines an experimental portion of the Management 36 Information Base (MIB) for use with network management 37 protocols in TCP/IP-based internets. In particular, it 38 defines objects for managing remote network monitoring 39 devices. 41 This memo does not specify a standard for the Internet 42 community. 44 3. The Network Management Framework 46 The Internet-standard Network Management Framework consists of 47 three components. They are: 49 RFC 1155[1] which defines the SMI, the mechanisms used for 50 describing and naming objects for the purpose of management. 51 RFC 1212[2] defines a more concise description mechanism, 52 which is wholly consistent with the SMI. 54 RFC 1213[3] which defines MIB-II, the core set of managed 55 objects for the Internet suite of protocols. 57 RFC 1157[4] which defines the SNMP, the protocol used for 58 network access to managed objects. 60 The Framework permits new objects to be defined for the 61 purpose of experimentation and evaluation. 63 Managed objects are accessed via a virtual information store, 64 termed the Management Information Base or MIB. Within a given 65 MIB module, objects are defined using RFC 1212's OBJECT-TYPE 66 macro. At a minimum, each object has a name, a syntax, an 67 access-level, and an implementation-status. 69 The name is an object identifier, an administratively assigned 70 name, which specifies an object type. The object type 71 together with an object instance serves to uniquely identify a 72 specific instantiation of the object. For human convenience, 73 we often use a textual string, termed the object descriptor, 74 to also refer to the object type. 76 The syntax of an object type defines the abstract data 77 structure corresponding to that object type. The ASN.1[5] 78 language is used for this purpose. However, RFC 1155 79 purposely restricts the ASN.1 constructs which may be used. 80 These restrictions are explicitly made for simplicity. 82 The access-level of an object type defines whether it makes 83 "protocol sense" to read and/or write the value of an instance 84 of the object type. (This access-level is independent of any 85 administrative authorization policy.) 87 The implementation-status of an object type indicates whether 88 the object is mandatory, optional, obsolete, or deprecated. 90 4. Overview 92 Remote network monitoring devices, often called monitors or 93 probes, are instruments that exist for the purpose of managing 94 a network. Often these remote probes are stand-alone devices 95 and devote significant internal resources for the sole purpose 96 of managing a network. An organization may employ many of 97 these devices, one per network segment, to manage its 98 internet. In addition, these devices may be used for a 99 network management service provider to access a client 100 network, often geographically remote. 102 The objects defined in this document are intended as an 103 interface between an RMON agent and an RMON management 104 application and are not intended for direct manipulation by 105 humans. While some users may tolerate the direct display of 106 some of these objects, few will tolerate the complexity of 107 manually manipulating objects to accomplish row creation. 108 These functions should be handled by the management 109 application. 111 4.1. Remote Network Management Goals 113 o Offline Operation 114 There are sometimes conditions when a management 115 station will not be in constant contact with its 116 remote monitoring devices. This is sometimes by 117 design in an attempt to lower communications costs 118 (especially when communicating over a WAN or 119 dialup link), or by accident as network failures 120 affect the communications between the management 121 station and the probe. 123 For this reason, this MIB allows a probe to be 124 configured to perform diagnostics and to collect 125 statistics continuously, even when communication with 126 the management station may not be possible or 127 efficient. The probe may then attempt to notify 128 the management station when an exceptional condition 129 occurs. Thus, even in circumstances where 130 communication between management station and probe is 131 not continuous, fault, performance, and configuration 132 information may be continuously accumulated and 133 communicated to the management station conveniently 134 and efficiently. 136 o Proactive Monitoring 137 Given the resources available on the monitor, it 138 is potentially helpful for it continuously to run 139 diagnostics and to log network performance. The 140 monitor is always available at the onset of any 141 failure. It can notify the management station of the 142 failure and can store historical statistical 143 information about the failure. This historical 144 information can be played back by the management 145 station in an attempt to perform further diagnosis 146 into the cause of the problem. 148 o Problem Detection and Reporting 149 The monitor can be configured to recognize 150 conditions, most notably error conditions, and 151 continuously to check for them. When one of these 152 conditions occurs, the event may be logged, and 153 management stations may be notified in a number of 154 ways. 156 o Value Added Data 157 Because a remote monitoring device represents a 158 network resource dedicated exclusively to network 159 management functions, and because it is located 160 directly on the monitored portion of the network, the 161 remote network monitoring device has the opportunity 162 to add significant value to the data it collects. 163 For instance, by highlighting those hosts on the 164 network that generate the most traffic or errors, the 165 probe can give the management station precisely the 166 information it needs to solve a class of problems. 168 o Multiple Managers 169 An organization may have multiple management stations 170 for different units of the organization, for different 171 functions (e.g. engineering and operations), and in an 172 attempt to provide disaster recovery. Because 173 environments with multiple management stations are 174 common, the remote network monitoring device has to 175 deal with more than own management station, 176 potentially using its resources concurrently. 178 4.2. Structure of MIB 180 The objects are arranged into the following groups: 182 - protocol directory 184 - protocol distribution 186 - address mapping 188 - network layer host 190 - network layer matrix 192 - application layer host 194 - application layer matrix 196 - user history 198 - probe configuration 200 These groups are the basic units of conformance. If a remote 201 monitoring device implements a group, then it must implement 202 all objects in that group. For example, a managed agent that 203 implements the network layer matrix group must implement the 204 nlMatrixSDTable and the nlMatrixDSTable. 206 Implementations of this MIB must also implement the system and 207 interfaces group of MIB-II [6]. MIB-II may also mandate the 208 implementation of additional groups. 210 These groups are defined to provide a means of assigning 211 object identifiers, and to provide a method for managed agents 212 to know which objects they must implement. 214 5. Control of Remote Network Monitoring Devices 216 Due to the complex nature of the available functions in these 217 devices, the functions often need user configuration. In many 218 cases, the function requires parameters to be set up for a 219 data collection operation. The operation can proceed only 220 after these parameters are fully set up. 222 Many functional groups in this MIB have one or more tables in 223 which to set up control parameters, and one or more data 224 tables in which to place the results of the operation. The 225 control tables are typically read-write in nature, while the 226 data tables are typically read-only. Because the parameters 227 in the control table often describe resulting data in the data 228 table, many of the parameters can be modified only when the 229 control entry is invalid. Thus, the method for modifying 230 these parameters is to invalidate the control entry, causing 231 its deletion and the deletion of any associated data entries, 232 and then create a new control entry with the proper 233 parameters. Deleting the control entry also gives a 234 convenient method for reclaiming the resources used by the 235 associated data. 237 Some objects in this MIB provide a mechanism to execute an 238 action on the remote monitoring device. These objects may 239 execute an action as a result of a change in the state of the 240 object. For those objects in this MIB, a request to set an 241 object to the same value as it currently holds would thus 242 cause no action to occur. 244 To facilitate control by multiple managers, resources have to 245 be shared among the managers. These resources are typically 246 the memory and computation resources that a function requires. 248 5.1. Resource Sharing Among Multiple Management Stations 250 When multiple management stations wish to use functions that 251 compete for a finite amount of resources on a device, a method 252 to facilitate this sharing of resources is required. 253 Potential conflicts include: 255 o Two management stations wish to simultaneously use 256 resources that together would exceed the capability of 257 the device. 259 o A management station uses a significant amount of 260 resources for a long period of time. 261 o A management station uses resources and then crashes, 262 forgetting to free the resources so others may 263 use them. 265 A mechanism is provided for each management station initiated 266 function in this MIB to avoid these conflicts and to help 267 resolve them when they occur. Each function has a label 268 identifying the initiator (owner) of the function. This label 269 is set by the initiator to provide for the following 270 possibilities: 272 o A management station may recognize resources it owns 273 and no longer needs. 274 o A network operator can find the management station that 275 owns the resource and negotiate for it to be freed. 276 o A network operator may decide to unilaterally free 277 resources another network operator has reserved. 278 o Upon initialization, a management station may recognize 279 resources it had reserved in the past. With this 280 information it may free the resources if it no longer 281 needs them. 283 Management stations and probes should support any format of 284 the owner string dictated by the local policy of the 285 organization. It is suggested that this name contain one or 286 more of the following: IP address, management station name, 287 network manager's name, location, or phone number. This 288 information will help users to share the resources more 289 effectively. 291 There is often default functionality that the device or the 292 administrator of the probe (often the network administrator) 293 wishes to set up. The resources associated with this 294 functionality are then owned by the device itself or by the 295 network administrator, and are intended to be long-lived. In 296 this case, the device or the administrator will set the 297 relevant owner object to a string starting with 'monitor'. 298 Indiscriminate modification of the monitor-owned configuration 299 by network management stations is discouraged. In fact, a 300 network management station should only modify these objects 301 under the direction of the administrator of the probe. 303 Resources on a probe are scarce and are typically allocated 304 when control rows are created by an application. Since many 305 applications may be using a probe simultaneously, 306 indiscriminate allocation of resources to particular 307 applications is very likely to cause resource shortages in the 308 probe. 310 When a network management station wishes to utilize a function 311 in a monitor, it is encouraged to first scan the control table 312 of that function to find an instance with similar parameters 313 to share. This is especially true for those instances owned 314 by the monitor, which can be assumed to change infrequently. 315 If a management station decides to share an instance owned by 316 another management station, it should understand that the 317 management station that owns the instance may indiscriminately 318 modify or delete it. 320 It should be noted that a management application should have 321 the most trust in a monitor-owned row because it should be 322 changed very infrequently. A row owned by the management 323 application is less long-lived because a network administrator 324 is more likely to re-assign resources from a row that is in 325 use by one user than from a monitor-owned row that is 326 potentially in use by many users. A row owned by another 327 application would be even less long-lived because the other 328 application may delete or modify that row completely at its 329 discretion. 331 5.2. Row Addition Among Multiple Management Stations 333 The addition of new rows is achieved using the method 334 described in RFC 1212 [9]. In this MIB, rows are often added 335 to a table in order to configure a function. This 336 configuration usually involves parameters that control the 337 operation of the function. The agent must check these 338 parameters to make sure they are appropriate given 339 restrictions defined in this MIB as well as any implementation 340 specific restrictions such as lack of resources. The agent 341 implementor may be confused as to when to check these 342 parameters and when to signal to the management station that 343 the parameters are invalid. There are two opportunities: 345 o When the management station sets each parameter object. 347 o When the management station sets the entry status object 348 to valid. 350 If the latter is chosen, it would be unclear to the management 351 station which of the several parameters was invalid and caused 352 the badValue error to be emitted. Thus, wherever possible, 353 the implementor should choose the former as it will provide 354 more information to the management station. 356 A problem can arise when multiple management stations attempt 357 to set configuration information simultaneously using SNMP. 358 When this involves the addition of a new conceptual row in the 359 same control table, the managers may collide, attempting to 360 create the same entry. To guard against these collisions, 361 each such control entry contains a status object with special 362 semantics that help to arbitrate among the managers. If an 363 attempt is made with the row addition mechanism to create such 364 a status object and that object already exists, an error is 365 returned. When more than one manager simultaneously attempts 366 to create the same conceptual row, only the first will 367 succeed. The others will receive an error. 369 When a manager wishes to create a new control entry, it needs 370 to choose an index for that row. It may choose this index in 371 a variety of ways, hopefully minimizing the chances that the 372 index is in use by another manager. If the index is in use, 373 the mechanism mentioned previously will guard against 374 collisions. Examples of schemes to choose index values 375 include random selection or scanning the control table looking 376 for the first unused index. Because index values may be any 377 valid value in the range and they are chosen by the manager, 378 the agent must allow a row to be created with any unused index 379 value if it has the resources to create a new row. 381 Some tables in this MIB reference other tables within this 382 MIB. When creating or deleting entries in these tables, it is 383 generally allowable for dangling references to exist. There 384 is no defined order for creating or deleting entries in these 385 tables. 387 6. Conventions 389 The following conventions are used throughout the RMON MIB and 390 its companion documents. 392 Good Packets 394 Good packets are error-free packets that have a valid frame 395 length. For example, on Ethernet, good packets are error-free 396 packets that are between 64 octets long and 1518 octets long. 397 They follow the form defined in IEEE 802.3 section 3.2.all. 399 Bad Packets 401 Bad packets are packets that have proper framing and are 402 therefore recognized as packets, but contain errors within the 403 packet or have an invalid length. For example, on Ethernet, 404 bad packets have a valid preamble and SFD, but have a bad CRC, 405 or are either shorter than 64 octets or longer than 1518 406 octets. 408 7. RMON 2 Conventions 410 The following practices and conventions are introduced in the 411 RMON 2 MIB. 413 7.1. Usage of the term Application Level 415 There are many cases in this MIB where the term Application 416 Level is used to describe a class of protocols or a 417 capability. This does not typically mean a protocol that is 418 an OSI Layer 7 protocol. Rather, it is used to identify a 419 class of protocols that is not limited to MAC-layer and 420 network-layer protocols, but can also include transport, 421 session, presentation, and application-layer protocols. 423 7.2. Protocol Directory and Limited Extensibility 425 Every RMON 2 implementation will have the capability to parse 426 certain types of packets and identify their protocol type at 427 multiple levels, The protocol directory presents an inventory 428 of those protocol types the probe is capable of monitoring, 429 and allows the addition, deletion, and configuration of 430 protocol types in this list. 432 One concept deserves special attention: the "limited 433 extensibility" of the protocol directory table. The RMON 2 434 model is that protocols are detected by static software that 435 has been written at implementation time. Therefore, as a 436 matter of configuration, an implementation does not have the 437 ability to suddenly learn how to parse new packet types. 438 However, an implementation may be written such that the 439 software knows where the demultiplexing field is for a 440 particular protocol, and can be written in such a way that the 441 decoding of the next layer up is table-driven. This works 442 when the code has been written to accomodate it and can be 443 extended no more than one level higher. This extensibility is 444 called "limited extensibility" to highlight these limitations. 445 However, this can be a very useful tool. 447 For example, suppose that an implementation has C code that 448 understands how to decode IP packets on any of several 449 ethernet encapsulations, and also knows how to interpret the 450 IP protocol field to recognize UDP packets and how to decode 451 the UDP port number fields. That implementation may be table- 452 driven so that among the many different UDP port numbers 453 possible, it is configured to recognize 161 as SNMP, port 53 454 as DNS, and port 69 as TFTP. The limited extensibility of the 455 protocol directory table would allow an SNMP operation to 456 create an entry that would create an additional table mapping 457 for UDP that would recognize UDP port 123 as NTP and begin 458 counting such packets. 460 This limited extensibility is an option that an implementation 461 can choose to allow or disallow for any protocol that has 462 child protocols. 464 7.3. Errors in packets 466 Packets with link-level errors are not counted anywhere in 467 this MIB. 469 Packets in which protocol errors are detected are counted for 470 all protocols below the layer in which the error was 471 encountered. The implication of this is that packets in which 472 errors are detected at the network-layer are not counted 473 anywhere in this MIB, while packets with errors detected at 474 the transport layer may have network-layer statistics counted. 476 8. Definitions 478 RMON2-MIB DEFINITIONS ::= BEGIN 479 IMPORTS 480 MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32, 481 Gauge32, IpAddress, TimeTicks FROM SNMPv2-SMI 482 TEXTUAL-CONVENTION, RowStatus, DisplayString 483 FROM SNMPv2-TC 484 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 485 mib-2 FROM RFC1213-MIB 486 OwnerString, statistics, history, hosts, 487 matrix, filter, etherStatsEntry, historyControlEntry, 488 hostControlEntry, matrixControlEntry, filterEntry, 489 channelEntry FROM RFC1757-MIB 490 tokenRing, tokenRingMLStatsEntry, tokenRingPStatsEntry, 491 ringStationControlEntry, sourceRoutingStatsEntry 492 FROM TOKEN-RING-RMON-MIB; 493 -- Remote Network Monitoring MIB 494 rmon MODULE-IDENTITY 495 LAST-UPDATED "9510150000Z" 496 ORGANIZATION "IETF RMON MIB Working Group" 497 CONTACT-INFO 498 "Andy Bierman (WG Chair) 499 Postal: Cisco Systems, Inc. 500 170 West Tasman Drive 501 San Jose, CA 95134-1706 502 USA 503 Phone: +1 408 526 8951 504 Email: abierman@cisco.com 506 Steve Waldbusser (WG Editor) 507 Postal: International Network Services 508 650 Castro Street, Suite 260 509 Mountain View, CA 94041 511 Phone: +1 415 254 4251 512 Email: waldbusser@ins.com" 513 DESCRIPTION 514 "The MIB module for managing remote monitoring 515 device implementations. This MIB module 516 augments the original RMON MIB as specified in 517 RFC 1757." 518 ::= { mib-2 16 } 520 protocolDir OBJECT IDENTIFIER ::= { rmon 11 } 521 protocolDist OBJECT IDENTIFIER ::= { rmon 12 } 522 addressMap OBJECT IDENTIFIER ::= { rmon 13 } 523 nlHost OBJECT IDENTIFIER ::= { rmon 14 } 524 nlMatrix OBJECT IDENTIFIER ::= { rmon 15 } 525 alHost OBJECT IDENTIFIER ::= { rmon 16 } 526 alMatrix OBJECT IDENTIFIER ::= { rmon 17 } 527 usrHistory OBJECT IDENTIFIER ::= { rmon 18 } 528 probeConfig OBJECT IDENTIFIER ::= { rmon 19 } 529 rmonConformance OBJECT IDENTIFIER ::= { rmon 20 } 531 -- Textual Conventions 533 ZeroBasedCounter ::= TEXTUAL-CONVENTION 534 STATUS current 535 DESCRIPTION 536 "This TC describes an object which counts events with the 537 following semantics: objects of this type will be set to 538 zero(0) on creation and will thereafter count appropriate 539 events, wrapping back to zero(0) when the value 2^32 is 540 reached. 542 Provided that an application discovers the new object within 543 the minimum time to wrap it can use the initial value as a 544 delta since it last polled the table of which this object is 545 part. It is important for a management station to be aware of 546 this minimum time and the actual time between polls, and to 547 discard data if the actual time is too long or there is no 548 defined minimum time. 550 Typically this TC is used in tables where the INDEX space is 551 constantly changing and/or the TimeFilter mechanism is in use." 552 SYNTAX Integer32 554 LastCreateTime ::= TEXTUAL-CONVENTION 555 STATUS current 556 DESCRIPTION 557 "This TC describes an object that stores the last time its 558 entry was created. 560 This can be used for polling applications to determine that an 561 entry has been deleted and re-created between polls, causing 562 an otherwise undetectable discontinuity in the data." 563 SYNTAX TimeTicks 565 TimeFilter ::= TEXTUAL-CONVENTION 566 STATUS current 567 DESCRIPTION 568 "To be used for the index to a table. Allows an application 569 to download only those rows changed since a particular time. 571 When sysUpTime is equal to zero, this table shall be empty. 573 One entry exists for each past value of sysUpTime, except that 574 the whole table is purged should sysUpTime wrap. 576 As this basic row is updated new conceptual rows are created 577 (which still share the now updated object values with all 578 other instances). The number of instances which are created 579 is determined by the value of sysUpTime at which the basic row 580 was last updated. One instance will exist for each value of 581 sysUpTime at the last update time for the row. A new 582 timeMark instance is created for each new sysUpTime value. 583 Each new conceptual row will be associated with the timeMark 584 instance which was created at the value of sysUpTime with 585 which the conceptual row is to be associated. 587 By definition all conceptual rows were updated at or after 588 time zero and so at least one conceptual row (associated with 589 timeMark.0) must exist for each underlying (basic) row. 591 Consider the following fooTable: 593 fooTable ... 594 INDEX { fooTimeMark, fooIndex } 596 FooEntry { 597 fooTimeMark TimeFilter 598 fooIndex INTEGER, 599 fooCounts Counter 600 } 602 Should there be two basic rows in this table (fooIndex == 1, 603 fooIndex == 2) and row 1 was updated most recently at time 6, 604 while row 2 was updated most recently at time 8, and both rows 605 had been updated on several earlier occasions such that the 606 current values were 5 and 9 respectively then the following 607 fooCounts instances would exist. 609 fooCounts.0.1 5 610 fooCounts.0.2 9 611 fooCounts.1.1 5 612 fooCounts.1.2 9 613 fooCounts.2.1 5 614 fooCounts.2.2 9 615 fooCounts.3.1 5 616 fooCounts.3.2 9 617 fooCounts.4.1 5 618 fooCounts.4.2 9 619 fooCounts.5.1 5 620 fooCounts.5.2 9 621 fooCounts.6.1 5 622 fooCounts.6.2 9 623 fooCounts.7.2 9 -- note that row 1 doesn't exist for 624 fooCounts.8.2 9 -- times 7 and 8" 625 SYNTAX TimeTicks 627 DataSource ::= TEXTUAL-CONVENTION 628 STATUS current 629 DESCRIPTION 630 "Identifies the source of the data that the associated 631 function is configured to analyze. This source can be any 632 interface on this device. 634 In order to identify a particular interface, this 635 object shall identify the instance of the ifIndex 636 object, defined in [4,6], for the desired interface. 638 For example, if an entry were to receive data from 639 interface #1, this object would be set to ifIndex.1." 640 SYNTAX OBJECT IDENTIFIER 642 -- 643 -- Protocol Directory Group 644 -- 645 -- Lists the inventory of protocols the probe has the capability of 646 -- monitoring and allows the addition, deletion, and configuration of 647 -- entries in this list. 649 protocolDirTable OBJECT-TYPE 650 SYNTAX SEQUENCE OF ProtocolDirEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "This table lists the protocols that this agent has the 655 capability to decode and count. There is one entry in this 656 table for each such protocol. These protocols represent 657 different network layer, transport layer, and higher-layer 658 protocols. The agent should boot up with this table 659 preconfigured with those protocols that it knows about and 660 wishes to monitor. Implementations are strongly encouraged to 661 support protocols higher than the network layer (at least for 662 the protocol distribution group), even for implementations 663 that don't support the application layer groups." 664 ::= { protocolDir 1 } 666 protocolDirEntry OBJECT-TYPE 667 SYNTAX ProtocolDirEntry 668 MAX-ACCESS not-accessible 669 STATUS current 670 DESCRIPTION 671 "A conceptual row in the protocolDirTable. 673 An example of the indexing of this entry is 674 protocolDirLocalIndex.8.0.0.0.1.0.0.8.0.0.0, which is the 675 encoding of a length of 8, followed by 8 subids encoding the 676 protocolDirID of 1.2048, followed by 2 subids encoding 677 zero-valued parameters." 678 INDEX { protocolDirID, protocolDirParameters } 679 ::= { protocolDirTable 1 } 681 ProtocolDirEntry ::= SEQUENCE { 682 protocolDirID OCTET STRING, 683 protocolDirParameters OCTET STRING, 684 protocolDirLocalIndex Integer32, 685 protocolDirDescr DisplayString, 686 protocolDirType BITS, 687 protocolDirAddressMapConfig INTEGER, 688 protocolDirHostConfig INTEGER, 689 protocolDirMatrixConfig INTEGER, 690 protocolDirOwner OwnerString, 691 protocolDirStatus RowStatus 692 } 694 protocolDirID OBJECT-TYPE 695 SYNTAX OCTET STRING 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "A unique identifier for a particular protocol. Standard 700 identifiers will be defined in a manner such that they 701 can often be used as specifications for new protocols - i.e. 702 a tree-structured assignment mechanism that matches the 703 protocol encapsulation `tree' and which has algorithmic 704 assignment mechanisms for certain subtrees. See RFC XXX for 705 more details. 706 For example: 707 XXX check these examples against the proto document. 708 protocolDir.assignments.ethernet 709 -- children of ethernet will have values representing the 710 -- two byte ethertype value of an ethernet protocol. Some 711 -- well-known ones are defined below. 713 protocolDir.assignments.ethernet.ip 714 -- children of ip will have values representing the 715 -- one byte value of an ip protocol. Some 716 -- well-known ones are defined below. 718 ... 720 protocolDir.assignments.ethernet.ip.udp.dns 722 Despite the algorithmic mechanism, the probe will only place 723 entries in here for those protocols it chooses to collect. In 724 other words, it need not populate this table with all of the 725 possible ethernet protocol types, nor need it create them on 726 the fly when it sees them. Whether or not it does these 727 things is a matter of product definition (cost/benefit, 728 usability), and is up to the designer of the product. 730 If an entry is written to this table with a protocolDirID that 731 the agent doesn't understand, either directly or 732 algorithmically, the SET request will be rejected with an 733 inconsistentName or badValue (for SNMPv1) error." 734 ::= { protocolDirEntry 1 } 736 protocolDirParameters OBJECT-TYPE 737 SYNTAX OCTET STRING 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "A set of parameters for the associated protocolDirID. There 742 will be one octet in this string for each sub-identifier in 743 the protocolDirID, and the parameters will appear here in the 744 same order as the associated sub-identifiers appear in the 745 protocolDirID. 747 Every node in the protocolDirID tree has a different, optional 748 set of parameters defined (that is, the definition of 749 parameters for a node is optional). The proper parameter 750 value for each node is included in this string. Note that the 751 inclusion of a parameter value in this string for each node is 752 not optional - what is optional is that a node may have no 753 parameters defined, in which case the parameter field for that 754 node will be zero." 755 ::= { protocolDirEntry 2 } 757 protocolDirLocalIndex OBJECT-TYPE 758 SYNTAX Integer32 (1..2147483647) 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The locally arbitrary, but unique identifier associated 763 with this protocolDir entry. 765 The value for each supported protocol must remain constant at 766 least from one re-initialization of the entity's network 767 management system to the next re-initialization, except that 768 if a protocol is deleted and re-created, it may be re-created 769 with a new value that has not been used since the last 770 re-initialization. 772 The specific value is meaningful only within a given SNMP 773 entity. A protocolDirLocalIndex may not be re-used until the 774 next agent-restart in the event the protocol directory entry 775 is deleted." 776 ::= { protocolDirEntry 3 } 778 protocolDirDescr OBJECT-TYPE 779 SYNTAX DisplayString (SIZE (1..64)) 780 MAX-ACCESS read-create 781 STATUS current 782 DESCRIPTION 783 "A textual description of the protocol encapsulation. 784 A probe may choose to describe only a subset of the 785 entire encapsulation (e.g. only the highest layer). 787 This object is intended for human consumption only. 789 This object may not be modified if the associated 790 protocolDirStatus object is equal to active(1)." 791 ::= { protocolDirEntry 4 } 793 protocolDirType OBJECT-TYPE 794 SYNTAX BITS { 795 extensible(0), 796 addressRecognitionCapable(1) 797 } 798 MAX-ACCESS read-only 799 STATUS current 800 DESCRIPTION 801 "This object describes 2 attributes of this protocol 802 directory entry. 804 The presence or absence of the `extensible' bit describes 805 whether or not this protocol directory entry can be extended 806 by the user by creating protocol directory entries which are 807 children of this protocol. 809 An example of an entry that will often allow extensibility is 810 `ip.udp'. The probe may automatically populate some children 811 of this node such as `ip.udp.snmp' and `ip.udp.dns'. 812 A probe administrator or user may also populate additional 813 children via remote SNMP requests that create entries in this 814 table. When a child node is added for a protocol for which the 815 probe has no built in support, extending a parent node (for 816 which the probe does have built in support), 817 that child node is not extendible. This is termed `limited 818 extensibility'. 820 When a child node is added through this extensibility 821 mechanism, the values of protocolDirLocalIndex and 822 protocolDirType shall be assigned by the agent. 824 The other objects in the entry will be assigned by the 825 manager who is creating the new entry. 827 This object also describes whether or not this agent can 828 recognize addresses for this protocol, should it be a network 829 level protocol. That is, while a probe may be able to 830 recognize packets of a particular network layer protocol and 831 count them, it takes additional logic to be able to recognize 832 the addresses in this protocol and to populate network layer 833 or application layer tables with the addresses in this 834 protocol. 836 Note that when an entry is created, the agent will supply 837 values for the bits that match the capabilities of the agent 838 with respect to this protocol. Note that since row creations 839 usually exercise the limited extensibility feature, these 840 bits will usually be set to zero." 841 ::= { protocolDirEntry 5 } 843 protocolDirAddressMapConfig OBJECT-TYPE 844 SYNTAX INTEGER { 845 notSupported(1), 846 supportedOff(2), 847 supportedOn(3) 848 } 849 MAX-ACCESS read-create 850 STATUS current 851 DESCRIPTION 852 "This object describes and configures the probe's support for 853 address mapping for this protocol. When the probe creates 854 entries in this table for all protocols that it understands, 855 it will set the entry to notSupported(1) if it doesn't have 856 the capability to perform address mapping for the protocol or 857 if this protocol is not a network-layer protocol. When 858 an entry is created in this table by a management operation as 859 part of the limited extensibility feature, the probe must set 860 this value to notSupported(1), because limited extensibility 861 of the protocolDirTable does not extend to interpreting 862 addresses of the extended protocols. 864 If the value of this object is notSupported(1), the probe 865 will not perform address mapping for this protocol and 866 shall not allow this object to be changed to any other value. 867 If the value of this object is supportedOn(3), the probe 868 supports address mapping for this protocol and is configured 869 to perform address mapping for this protocol for all 870 addressMappingControlEntries and all interfaces. 871 If the value of this object is supportedOff(2), the probe 872 supports address mapping for this protocol but is configured 873 to not perform address mapping for this protocol for any 874 addressMappingControlEntries and all interfaces. 875 Whenever this value changes from supportedOn(3) to 876 supportedOff(2), the probe shall delete all related entries in 877 the addressMappingTable." 878 ::= { protocolDirEntry 6 } 880 protocolDirHostConfig OBJECT-TYPE 881 SYNTAX INTEGER { 882 notSupported(1), 883 supportedOff(2), 884 supportedOn(3) 885 } 886 MAX-ACCESS read-create 887 STATUS current 888 DESCRIPTION 889 "This object describes and configures the probe's support for 890 the network layer and application layer host tables for this 891 protocol. When the probe creates entries in this table for 892 all protocols that it understands, it will set the entry to 893 notSupported(1) if it doesn't have the capability to track the 894 nlHostTable for this protocol or if the alHostTable is 895 implemented but doesn't have the capability to track this 896 protocol. Note that if the alHostTable is implemented, the 897 probe may only support a protocol if it is supported in both 898 the nlHostTable and the alHostTable. 900 If the associated protocolDirType object has the 901 addressRecognitionCapable bit set, then this is a network 902 layer protocol for which the probe recognizes addresses, and 903 thus the probe will populate the nlHostTable and alHostTable 904 with addresses it discovers for this protocol. 906 If the value of this object is notSupported(1), the probe 907 will not track the nlHostTable or alHostTable for this 908 protocol and shall not allow this object to be changed to any 909 other value. If the value of this object is supportedOn(3), 910 the probe supports tracking of the nlHostTable and alHostTable 911 for this protocol and is configured to track both tables 912 for this protocol for all control entries and all interfaces. 913 If the value of this object is supportedOff(2), the probe 914 supports tracking of the nlHostTable and alHostTable for this 915 protocol but is configured to not track these tables 916 for any control entries or interfaces. 917 Whenever this value changes from supportedOn(3) to 918 supportedOff(2), the probe shall delete all related entries in 919 the nlHostTable and alHostTable. 921 Note that since each alHostEntry references 2 protocol 922 directory entries, one for the network address and one for the 923 type of the highest protocol recognized, that an entry will 924 only be created in that table if this value is supportedOn(3) 925 for both protocols." 926 ::= { protocolDirEntry 7 } 928 protocolDirMatrixConfig OBJECT-TYPE 929 SYNTAX INTEGER { 930 notSupported(1), 931 supportedOff(2), 932 supportedOn(3) 933 } 934 MAX-ACCESS read-create 935 STATUS current 936 DESCRIPTION 937 "This object describes and configures the probe's support for 938 the network layer and application layer matrix tables for this 939 protocol. When the probe creates entries in this table for 940 all protocols that it understands, it will set the entry to 941 notSupported(1) if it doesn't have the capability to track the 942 nlMatrixTables for this protocol or if the alMatrixTables are 943 implemented but don't have the capability to track this 944 protocol. Note that if the alMatrix tables are implemented, 945 the probe may only support a protocol if it is supported in 946 the the both of the nlMatrixTables and both of the 947 alMatrixTables. 949 If the associated protocolDirType object has the 950 addressRecognitionCapable bit set, then this is a network 951 layer protocol for which the probe recognizes addresses, and 952 thus the probe will populate both of the nlMatrixTables and 953 both of the alMatrixTables with addresses it discovers for 954 this protocol. 956 If the value of this object is notSupported(1), the probe 957 will not track either of the nlMatrixTables or either of the 958 alMatrixTables for this protocol and shall not allow this 959 object to be changed to any other value. If the value of this 960 object is supportedOn(3), the probe supports tracking of both 961 of the nlMatrixTables and (if implemented) both of the 962 alMatrixTables for this protocol and is configured to track 963 these tables for this protocol for all control entries and all 964 interfaces. If the value of this object is supportedOff(2), 965 the probe supports tracking of both of the nlMatrixTables and 966 (if implemented) both of the alMatrixTables for this protocol 967 but is configured to not track these tables for this 968 protocol for any control entries or interfaces. 969 Whenever this value changes from supportedOn(3) to 970 supportedOff(2), the probe shall delete all related entries in 971 the nlMatrixTables and the alMatrixTables. 973 Note that since each alMatrixEntry references 2 protocol 974 directory entries, one for the network address and one for the 975 type of the highest protocol recognized, that an entry will 976 only be created in that table if this value is supportedOn(3) 977 for both protocols." 978 ::= { protocolDirEntry 8 } 980 protocolDirOwner OBJECT-TYPE 981 SYNTAX OwnerString 982 MAX-ACCESS read-create 983 STATUS current 984 DESCRIPTION 985 "The entity that configured this entry and is 986 therefore using the resources assigned to it." 987 ::= { protocolDirEntry 9 } 989 protocolDirStatus OBJECT-TYPE 990 SYNTAX RowStatus 991 MAX-ACCESS read-create 992 STATUS current 993 DESCRIPTION 994 "The status of this protocol directory entry. 996 An entry may not exist in the active state unless all 997 objects in the entry have an appropriate value. 999 If this object is not equal to active(1), all associated 1000 entries in the nlHostTable, nlMatrixSDTable, nlMatrixDSTable, 1001 alHostTable, alMatrixSDTable, and alMatrixDSTable shall be 1002 deleted." 1003 ::= { protocolDirEntry 10 } 1005 -- 1006 -- Protocol Distribution Group (protocolDist) 1007 -- 1008 -- Collects the relative amounts of octets and packets for the 1009 -- different protocols detected on a network segment. 1010 -- protocolDistControlTable, 1011 -- protocolDistStatsTable 1013 protocolDistControlTable OBJECT-TYPE 1014 SYNTAX SEQUENCE OF ProtocolDistControlEntry 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "Controls the setup of protocol type distribution statistics 1019 tables. 1021 Implementations are encouraged to add an entry per monitored 1022 interface upon initialization so that a default collection 1023 of protocol statistics is available. 1025 Rationale: 1026 This table controls collection of very basic statistics 1027 for any or all of the protocols detected on a given interface. 1028 An NMS can use this table to quickly determine bandwidth 1029 allocation utilized by different protocols. 1031 A media-specific statistics collection could also 1032 be configured (e.g. etherStats, trPStats) to easily obtain 1033 total frame, octet, and droppedEvents for the same 1034 interface." 1035 ::= { protocolDist 1 } 1037 protocolDistControlEntry OBJECT-TYPE 1038 SYNTAX ProtocolDistControlEntry 1039 MAX-ACCESS not-accessible 1040 STATUS current 1041 DESCRIPTION 1042 "A conceptual row in the protocolDistControlTable. 1044 An example of the indexing of this entry is 1045 protocolDistControlDroppedFrames.7" 1046 INDEX { protocolDistControlIndex } 1047 ::= { protocolDistControlTable 1 } 1049 ProtocolDistControlEntry ::= SEQUENCE { 1050 protocolDistControlIndex Integer32, 1051 protocolDistControlDataSource DataSource, 1052 protocolDistControlDroppedFrames Counter32, 1053 protocolDistControlCreateTime LastCreateTime, 1054 protocolDistControlOwner OwnerString, 1055 protocolDistControlStatus RowStatus 1056 } 1058 protocolDistControlIndex OBJECT-TYPE 1059 SYNTAX Integer32 (1..65535) 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "A unique index for this protocolDistControlEntry." 1064 ::= { protocolDistControlEntry 1 } 1066 protocolDistControlDataSource OBJECT-TYPE 1067 SYNTAX DataSource 1068 MAX-ACCESS read-create 1069 STATUS current 1070 DESCRIPTION 1071 "The source of data for the this protocol distribution. 1073 The statistics in this group reflect all packets 1074 on the local network segment attached to the 1075 identified interface. 1077 This object may not be modified if the associated 1078 protocolDistControlStatus object is equal to active(1)." 1079 ::= { protocolDistControlEntry 2 } 1081 protocolDistControlDroppedFrames OBJECT-TYPE 1082 SYNTAX Counter32 1083 MAX-ACCESS read-only 1084 STATUS current 1085 DESCRIPTION 1086 "The total number of frames which were received by the probe 1087 and therefore not accounted for in the *StatsDropEvents, but 1088 for which the probe chose not to count for this entry for 1089 whatever reason. Most often, this event occurs when the probe 1090 is out of some resources and decides to shed load from this 1091 collection. 1093 This count does not include packets that were not counted 1094 because they had MAC-layer errors. 1096 Note that, unlike the dropEvents counter, this number is the 1097 exact number of frames dropped." 1098 ::= { protocolDistControlEntry 3 } 1100 protocolDistControlCreateTime OBJECT-TYPE 1101 SYNTAX LastCreateTime 1102 MAX-ACCESS read-only 1103 STATUS current 1104 DESCRIPTION 1105 "The value of sysUpTime when this control entry was activated. 1106 This can be used by the management station to ensure that the 1107 table has not been deleted and recreated between polls." 1108 ::= { protocolDistControlEntry 4 } 1110 protocolDistControlOwner OBJECT-TYPE 1111 SYNTAX OwnerString 1112 MAX-ACCESS read-create 1113 STATUS current 1114 DESCRIPTION 1115 "The entity that configured this entry and is 1116 therefore using the resources assigned to it." 1117 ::= { protocolDistControlEntry 5 } 1119 protocolDistControlStatus OBJECT-TYPE 1120 SYNTAX RowStatus 1121 MAX-ACCESS read-create 1122 STATUS current 1123 DESCRIPTION 1124 "The status of this row. 1126 An entry may not exist in the active state unless all 1127 objects in the entry have an appropriate value. 1129 If this object is not equal to active(1), all associated 1130 entries in the protocolDistStatsTable shall be deleted." 1131 ::= { protocolDistControlEntry 6 } 1133 -- per interface protocol distribution statistics table 1134 protocolDistStatsTable OBJECT-TYPE 1135 SYNTAX SEQUENCE OF ProtocolDistStatsEntry 1136 MAX-ACCESS not-accessible 1137 STATUS current 1138 DESCRIPTION 1139 "An entry is made in this table for every protocol in the 1140 protocolDirTable which has been seen in at least one packet. 1142 Counters are updated in this table for every protocol type 1143 that is encountered when parsing a packet, but no counters are 1144 updated for packets with MAC-layer errors. 1146 Note that there is a protocol OTHER in the protocol document 1147 that is defined to count all packets that had no recognizable 1148 network layer protocol. This protocol will also get 1149 instantiated here as an entry with an octet and a packet 1150 counter. 1152 Note that if a protocolDirEntry is deleted, all associated 1153 entries in this table are removed." 1154 ::= { protocolDist 2 } 1156 protocolDistStatsEntry OBJECT-TYPE 1157 SYNTAX ProtocolDistStatsEntry 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "A conceptual row in the protocolDistStatsTable. 1163 The index is composed of the protocolDistControlIndex of the 1164 associated protocolDistControlEntry followed by the 1165 protocolDirLocalIndex of the associated protocol that this 1166 entry represents. In other words, the index identifies the 1167 protocol distribution an entry is a part of as well as the 1168 particular protocol that it represents. 1170 An example of the indexing of this entry is 1171 protocolDistStatsPkts.1.18" 1172 INDEX { protocolDistControlIndex, protocolDirLocalIndex } 1173 ::= { protocolDistStatsTable 1 } 1175 ProtocolDistStatsEntry ::= SEQUENCE { 1176 protocolDistStatsPkts ZeroBasedCounter, 1177 protocolDistStatsOctets ZeroBasedCounter 1178 } 1180 protocolDistStatsPkts OBJECT-TYPE 1181 SYNTAX ZeroBasedCounter 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "The number of packets without errors received of this 1186 protocol type. Note that this is the number of link-layer 1187 packets, so if a single network-layer packet is fragmented 1188 into several link-layer frames, this counter is incremented 1189 several times." 1190 ::= { protocolDistStatsEntry 1 } 1192 protocolDistStatsOctets OBJECT-TYPE 1193 SYNTAX ZeroBasedCounter 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION 1197 "The number of octets in packets received of this protocol 1198 type since it was added to the nlHostTable (excluding 1199 framing bits but including FCS octets), except for 1200 those octets in packets that contained errors. 1202 Note this doesn't count just those octets in the particular 1203 protocol frames, but includes the entire packet that contained 1204 the protocol." 1205 ::= { protocolDistStatsEntry 2 } 1207 -- 1208 -- Address Map Group (addressMap) 1209 -- 1210 -- Lists MAC address to network address bindings discovered by the 1211 -- probe and what interface they were last seen on. 1212 -- addressMapControlTable 1213 -- addressMapTable 1215 addressMapInserts OBJECT-TYPE 1216 SYNTAX Counter32 1217 MAX-ACCESS read-only 1218 STATUS current 1219 DESCRIPTION 1220 "The number of times an address mapping entry has been 1221 inserted into the addressMapTable. If an entry is inserted, 1222 then deleted, and then inserted, this counter will be 1223 incremented by 2. 1225 Note that the table size can be determined by subtracting 1226 addressMapDeletes from addressMapInserts." 1227 ::= { addressMap 1 } 1229 addressMapDeletes OBJECT-TYPE 1230 SYNTAX Counter32 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "The number of times an address mapping entry has been 1235 deleted from the addressMapTable (for any reason). If 1236 an entry is deleted, then inserted, and then deleted, this 1237 counter will be incremented by 2. 1239 Note that the table size can be determined by subtracting 1240 addressMapDeletes from addressMapInserts." 1241 ::= { addressMap 2 } 1243 addressMapMaxDesiredEntries OBJECT-TYPE 1244 SYNTAX Integer32 1245 MAX-ACCESS read-write 1246 STATUS current 1247 DESCRIPTION 1248 "The maximum number of entries that are desired in the 1249 addressMapTable. The probe will not create more than 1250 this number of entries in the table, but may choose to create 1251 fewer entries in this table for any reason including the lack 1252 of resources. 1254 If this value is set to -1, the probe may create any number 1255 of entries in this table. 1257 This object may be used to control how resources are allocated 1258 on the probe for the various RMON functions." 1259 ::= { addressMap 3 } 1261 addressMapControlTable OBJECT-TYPE 1262 SYNTAX SEQUENCE OF AddressMapControlEntry 1263 MAX-ACCESS not-accessible 1264 STATUS current 1265 DESCRIPTION 1266 "A table to control the collection of network layer address to 1267 physical address to interface mappings. 1269 Note that this is not like the typical RMON 1270 controlTable and dataTable in which each entry creates 1271 its own data table. Each entry in this table enables the 1272 discovery of addresses on a new interface and the placement 1273 of address mappings into the central addressMapTable. 1275 Implementations are encouraged to add an entry per monitored 1276 interface upon initialization so that a default collection 1277 of address mappings is available." 1278 ::= { addressMap 4 } 1280 addressMapControlEntry OBJECT-TYPE 1281 SYNTAX AddressMapControlEntry 1282 MAX-ACCESS not-accessible 1283 STATUS current 1284 DESCRIPTION 1285 "A conceptual row in the addressMapControlTable. 1287 An example of the indexing of this entry is 1288 addressMapControlDroppedFrames.1" 1289 INDEX { addressMapControlIndex } 1290 ::= { addressMapControlTable 1 } 1292 AddressMapControlEntry ::= SEQUENCE { 1293 addressMapControlIndex Integer32, 1294 addressMapControlDataSource DataSource, 1295 addressMapControlDroppedFrames Counter32, 1296 addressMapControlOwner OwnerString, 1297 addressMapControlStatus RowStatus 1298 } 1300 addressMapControlIndex OBJECT-TYPE 1301 SYNTAX Integer32 1302 MAX-ACCESS not-accessible 1303 STATUS current 1304 DESCRIPTION 1305 "A unique index for this entry in the addressMapControlTable." 1306 ::= { addressMapControlEntry 1 } 1308 addressMapControlDataSource OBJECT-TYPE 1309 SYNTAX DataSource 1310 MAX-ACCESS read-create 1311 STATUS current 1312 DESCRIPTION 1313 "The source of data for this addressMapControlEntry." 1314 ::= { addressMapControlEntry 2 } 1316 addressMapControlDroppedFrames OBJECT-TYPE 1317 SYNTAX Counter32 1318 MAX-ACCESS read-only 1319 STATUS current 1320 DESCRIPTION 1321 "The total number of frames which were received by the probe 1322 and therefore not accounted for in the *StatsDropEvents, but 1323 for which the probe chose not to count for this entry for 1324 whatever reason. Most often, this event occurs when the probe 1325 is out of some resources and decides to shed load from this 1326 collection. 1328 This count does not include packets that were not counted 1329 because they had MAC-layer errors. 1331 Note that, unlike the dropEvents counter, this number is the 1332 exact number of frames dropped." 1333 ::= { addressMapControlEntry 3 } 1335 addressMapControlOwner OBJECT-TYPE 1336 SYNTAX OwnerString 1337 MAX-ACCESS read-create 1338 STATUS current 1339 DESCRIPTION 1340 "The entity that configured this entry and is 1341 therefore using the resources assigned to it." 1343 ::= { addressMapControlEntry 4 } 1345 addressMapControlStatus OBJECT-TYPE 1346 SYNTAX RowStatus 1347 MAX-ACCESS read-create 1348 STATUS current 1349 DESCRIPTION 1350 "The status of this addressMap control entry. 1352 An entry may not exist in the active state unless all 1353 objects in the entry have an appropriate value. 1355 If this object is not equal to active(1), all associated 1356 entries in the addressMapTable shall be deleted." 1357 ::= { addressMapControlEntry 5 } 1359 addressMapTable OBJECT-TYPE 1360 SYNTAX SEQUENCE OF AddressMapEntry 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "A table of network layer address to physical address to 1365 interface mappings. 1367 The probe will add entries to this table based on the source 1368 MAC and network addresses seen in packets without MAC-level 1369 errors. The probe will populate this table for all protocols 1370 in the protocol directory table whose value of 1371 protocolDirAddressMapConfig is equal to supportedOn(3), and 1372 will delete any entries whose protocolDirEntry is deleted or 1373 has a protocolDirAddressMapConfig value of supportedOff(2)." 1374 ::= { addressMap 5 } 1376 addressMapEntry OBJECT-TYPE 1377 SYNTAX AddressMapEntry 1378 MAX-ACCESS not-accessible 1379 STATUS current 1380 DESCRIPTION 1381 "A conceptual row in the addressMapTable. 1383 The protocolDirLocalIndex in the index identifies the network 1384 layer protocol of the addressMapNetworkAddress. 1386 An example of the indexing of this entry is 1387 addressMapSource.783495.18.4.128.2.6.6.11.1.3.6.1.2.1.2.2.1.1.1" 1389 INDEX { addressMapTimeMark, protocolDirLocalIndex, 1390 addressMapNetworkAddress, addressMapSource } 1391 ::= { addressMapTable 1 } 1393 AddressMapEntry ::= SEQUENCE { 1394 addressMapTimeMark TimeFilter, 1395 addressMapNetworkAddress OCTET STRING, 1396 addressMapSource OBJECT IDENTIFIER, 1397 addressMapPhysicalAddress OCTET STRING, 1398 addressMapLastChange TimeTicks 1399 } 1401 addressMapTimeMark OBJECT-TYPE 1402 SYNTAX TimeFilter 1403 MAX-ACCESS not-accessible 1404 STATUS current 1405 DESCRIPTION 1406 "A TimeFilter for this entry. See the TimeFilter textual 1407 convention to see how this works." 1408 ::= { addressMapEntry 1 } 1410 addressMapNetworkAddress OBJECT-TYPE 1411 SYNTAX OCTET STRING 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "The network address for this relation. 1417 This is represented as an octet string with 1418 specific semantics and length as identified 1419 by the protocolDirLocalIndex component of the 1420 index. 1422 For example, if the protocolDirLocalIndex indicates an 1423 encapsulation of ip, this object is encoded as a length 1424 octet of 4, followed by the 4 octets of the ip address, 1425 in network byte order." 1426 ::= { addressMapEntry 2 } 1428 addressMapSource OBJECT-TYPE 1429 SYNTAX OBJECT IDENTIFIER 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "The interface or port on which the associated network 1434 address was most recently seen. 1436 If this address mapping was discovered on an interface, this 1437 object shall identify the instance of the ifIndex 1438 object, defined in [4,6], for the desired interface. 1439 For example, if an entry were to receive data from 1440 interface #1, this object would be set to ifIndex.1. 1442 If this address mapping was discovered on a port, this 1443 object shall identify the instance of the rptrGroupPortIndex 1444 object, defined in [RFC1516], for the desired port. 1445 For example, if an entry were to receive data from 1446 group #1, port #1, this object would be set to 1447 rptrGroupPortIndex.1.1." 1448 ::= { addressMapEntry 3 } 1450 addressMapPhysicalAddress OBJECT-TYPE 1451 SYNTAX OCTET STRING 1452 MAX-ACCESS read-only 1453 STATUS current 1454 DESCRIPTION 1455 "The last source physical address on which the associated 1456 network address was seen. If the protocol of the associated 1457 network address was encapsulated inside of a network-level or 1458 higher protocol, this will be the address of the next-lower 1459 protocol with the addressRecognitionCapable bit enabled and 1460 will be formatted as specified for that protocol." 1461 ::= { addressMapEntry 4 } 1463 addressMapLastChange OBJECT-TYPE 1464 SYNTAX TimeTicks 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "The value of sysUpTime at the time this entry was created or 1469 the values of the physical address or ifIndex changed. 1471 This can be used to help detect duplicate address problems, in 1472 which case this object will be updated frequently." 1473 ::= { addressMapEntry 5 } 1475 -- 1476 -- Network Layer Host Group 1477 -- 1478 -- Counts the amount of traffic sent from and to each network address 1479 -- discovered by the probe. 1480 -- Note that while the hlHostControlTable also has objects that 1481 -- control an optional alHostTable, implementation of the alHostTable is 1482 -- not required to fully implement this group. 1484 hlHostControlTable OBJECT-TYPE 1485 SYNTAX SEQUENCE OF HlHostControlEntry 1486 MAX-ACCESS not-accessible 1487 STATUS current 1488 DESCRIPTION 1489 "A list of higher layer (i.e. non-MAC) host table control entries. 1491 These entries will enable the collection of the network and 1492 application level host tables indexed by network addresses. 1493 Both the network and application level host tables are 1494 controlled by this table is so that they will both be created 1495 and deleted at the same time, further increasing the ease with 1496 which they can be implemented as a single datastore (note that 1497 if an implementation stores application layer host records in 1498 memory, it can derive network layer host records from them). 1500 Entries in the nlHostTable will be created on behalf of each 1501 entry in this table. Additionally, if this probe implements 1502 the alHostTable, entries in the alHostTable will be created on 1503 behalf of each entry in this table. 1505 Implementations are encouraged to add an entry per monitored 1506 interface upon initialization so that a default collection 1507 of host statistics is available." 1508 ::= { nlHost 1 } 1510 hlHostControlEntry OBJECT-TYPE 1511 SYNTAX HlHostControlEntry 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "A conceptual row in the hlHostControlTable. 1517 An example of the indexing of this entry is 1518 hlHostControlNlDroppedFrames.1" 1519 INDEX { hlHostControlIndex } 1520 ::= { hlHostControlTable 1 } 1522 HlHostControlEntry ::= SEQUENCE { 1523 hlHostControlIndex Integer32, 1524 hlHostControlDataSource DataSource, 1525 hlHostControlNlDroppedFrames Counter32, 1526 hlHostControlNlInserts Counter32, 1527 hlHostControlNlDeletes Counter32, 1528 hlHostControlNlMaxDesiredEntries Integer32, 1529 hlHostControlAlDroppedFrames Counter32, 1530 hlHostControlAlInserts Counter32, 1531 hlHostControlAlDeletes Counter32, 1532 hlHostControlAlMaxDesiredEntries Integer32, 1533 hlHostControlOwner OwnerString, 1534 hlHostControlStatus RowStatus 1535 } 1537 hlHostControlIndex OBJECT-TYPE 1538 SYNTAX Integer32 (1..65535) 1539 MAX-ACCESS not-accessible 1540 STATUS current 1541 DESCRIPTION 1542 "An index that uniquely identifies an entry in the 1543 hlHostControlTable. Each such entry defines 1544 a function that discovers hosts on a particular 1545 interface and places statistics about them in the 1546 nlHostTable, and optionally in the alHostTable, on 1547 behalf of this hlHostControlEntry." 1548 ::= { hlHostControlEntry 1 } 1550 hlHostControlDataSource OBJECT-TYPE 1551 SYNTAX DataSource 1552 MAX-ACCESS read-create 1553 STATUS current 1554 DESCRIPTION 1555 "The source of data for the associated host tables. 1557 The statistics in this group reflect all packets 1558 on the local network segment attached to the 1559 identified interface. 1561 This object may not be modified if the associated 1562 hlHostControlStatus object is equal to active(1)." 1563 ::= { hlHostControlEntry 2 } 1565 hlHostControlNlDroppedFrames OBJECT-TYPE 1566 SYNTAX Counter32 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 "The total number of frames which were received by the probe 1571 and therefore not accounted for in the *StatsDropEvents, but 1572 for which the probe chose not to count for the associated 1573 nlHost entries for whatever reason. Most often, this event 1574 occurs when the probe is out of some resources and decides to 1575 shed load from this collection. 1577 This count does not include packets that were not counted 1578 because they had MAC-layer errors. 1580 Note that if the nlHostTable is inactive because no protocols 1581 are enabled in the protocol directory, this value should be 0. 1583 Note that, unlike the dropEvents counter, this number is the 1584 exact number of frames dropped." 1585 ::= { hlHostControlEntry 3 } 1587 hlHostControlNlInserts OBJECT-TYPE 1588 SYNTAX Counter32 1589 MAX-ACCESS read-only 1590 STATUS current 1591 DESCRIPTION 1592 "The number of times an nlHost entry has been 1593 inserted into the nlHost table. If an entry is inserted, then 1594 deleted, and then inserted, this counter will be incremented 1595 by 2. 1597 Note that the table size can be determined by subtracting 1598 hlHostControlNlDeletes from hlHostControlNlInserts." 1599 ::= { hlHostControlEntry 4 } 1601 hlHostControlNlDeletes OBJECT-TYPE 1602 SYNTAX Counter32 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "The number of times an nlHost entry has been 1607 deleted from the nlHost table (for any reason). If an entry 1608 is deleted, then inserted, and then deleted, this counter will 1609 be incremented by 2. 1611 Note that the table size can be determined by subtracting 1612 hlHostControlNlDeletes from hlHostControlNlInserts." 1613 ::= { hlHostControlEntry 5 } 1615 hlHostControlNlMaxDesiredEntries OBJECT-TYPE 1616 SYNTAX Integer32 1617 MAX-ACCESS read-create 1618 STATUS current 1619 DESCRIPTION 1620 "The maximum number of entries that are desired in the 1621 nlHostTable on behalf of this control entry. The probe will 1622 not create more than this number of associated entries in the 1623 table, but may choose to create fewer entries in this table 1624 for any reason including the lack of resources. 1626 If this value is set to -1, the probe may create any number 1627 of entries in this table. If the associated 1628 hlHostControlStatus object is equal to `active', this 1629 object may not be modified. 1631 This object may be used to control how resources are allocated 1632 on the probe for the various RMON functions." 1633 ::= { hlHostControlEntry 6 } 1635 hlHostControlAlDroppedFrames OBJECT-TYPE 1636 SYNTAX Counter32 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "The total number of frames which were received by the probe 1641 and therefore not accounted for in the *StatsDropEvents, but 1642 for which the probe chose not to count for the associated 1643 alHost entries for whatever reason. Most often, this event 1644 occurs when the probe is out of some resources and decides to 1645 shed load from this collection. 1647 This count does not include packets that were not counted 1648 because they had MAC-layer errors. 1650 Note that if the alHostTable is not implemented or is inactive 1651 because no protocols are enabled in the protocol directory, 1652 this value should be 0. 1654 Note that, unlike the dropEvents counter, this number is the 1655 exact number of frames dropped." 1657 ::= { hlHostControlEntry 7 } 1659 hlHostControlAlInserts OBJECT-TYPE 1660 SYNTAX Counter32 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "The number of times an alHost entry has been 1665 inserted into the alHost table. If an entry is inserted, then 1666 deleted, and then inserted, this counter will be incremented 1667 by 2. 1669 Note that the table size can be determined by subtracting 1670 hlHostControlAlDeletes from hlHostControlAlInserts." 1671 ::= { hlHostControlEntry 8 } 1673 hlHostControlAlDeletes OBJECT-TYPE 1674 SYNTAX Counter32 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "The number of times an alHost entry has been 1679 deleted from the alHost table (for any reason). If an entry 1680 is deleted, then inserted, and then deleted, this counter will 1681 be incremented by 2. 1683 Note that the table size can be determined by subtracting 1684 hlHostControlAlDeletes from hlHostControlAlInserts." 1685 ::= { hlHostControlEntry 9 } 1687 hlHostControlAlMaxDesiredEntries OBJECT-TYPE 1688 SYNTAX Integer32 1689 MAX-ACCESS read-create 1690 STATUS current 1691 DESCRIPTION 1692 "The maximum number of entries that are desired in the alHost 1693 table on behalf of this control entry. The probe will not 1694 create more than this number of associated entries in the 1695 table, but may choose to create fewer entries in this table 1696 for any reason including the lack of resources. 1698 If this value is set to -1, the probe may create any number 1699 of entries in this table. If the associated 1700 hlHostControlStatus object is equal to `active', this 1701 object may not be modified. 1703 This object may be used to control how resources are allocated 1704 on the probe for the various RMON functions." 1705 ::= { hlHostControlEntry 11 } 1707 hlHostControlOwner OBJECT-TYPE 1708 SYNTAX OwnerString 1709 MAX-ACCESS read-create 1710 STATUS current 1711 DESCRIPTION 1712 "The entity that configured this entry and is 1713 therefore using the resources assigned to it." 1714 ::= { hlHostControlEntry 12 } 1716 hlHostControlStatus OBJECT-TYPE 1717 SYNTAX RowStatus 1718 MAX-ACCESS read-create 1719 STATUS current 1720 DESCRIPTION 1721 "The status of this hlHostControlEntry. 1723 An entry may not exist in the active state unless all 1724 objects in the entry have an appropriate value. 1726 If this object is not equal to active(1), all associated 1727 entries in the nlHostTable and alHostTable shall be deleted." 1728 ::= { hlHostControlEntry 13 } 1730 nlHostTable OBJECT-TYPE 1731 SYNTAX SEQUENCE OF NlHostEntry 1732 MAX-ACCESS not-accessible 1733 STATUS current 1734 DESCRIPTION 1735 "A collection of statistics for a particular network layer 1736 address that has been discovered on an interface of this 1737 device. 1739 The probe will populate this table for all network layer 1740 protocols in the protocol directory table whose value of 1741 protocolDirHostConfig is equal to supportedOn(3), and 1742 will delete any entries whose protocolDirEntry is deleted or 1743 has a protocolDirHostConfig value of supportedOff(2). 1745 The probe will add to this table all addresses seen 1746 as the source or destination address in all packets with no 1747 MAC errors, and will increment octet and packet counts in the 1748 table for all packets with no MAC errors." 1749 ::= { nlHost 2 } 1751 nlHostEntry OBJECT-TYPE 1752 SYNTAX NlHostEntry 1753 MAX-ACCESS not-accessible 1754 STATUS current 1755 DESCRIPTION 1756 "A conceptual row in the nlHostTable. 1758 The hlHostControlIndex value in the index identifies the 1759 hlHostControlEntry on whose behalf this entry was created. 1760 The protocolDirLocalIndex value in the index identifies the 1761 network layer protocol of the nlHostAddress. 1763 An example of the indexing of this entry is 1764 nlHostOutPkts.1.783495.18.4.128.2.6.6." 1765 INDEX { hlHostControlIndex, nlHostTimeMark, 1766 protocolDirLocalIndex, nlHostAddress } 1767 ::= { nlHostTable 1 } 1769 NlHostEntry ::= SEQUENCE { 1770 nlHostTimeMark TimeFilter, 1771 nlHostAddress OCTET STRING, 1772 nlHostInPkts ZeroBasedCounter, 1773 nlHostOutPkts ZeroBasedCounter, 1774 nlHostInOctets ZeroBasedCounter, 1775 nlHostOutOctets ZeroBasedCounter, 1776 nlHostOutMacNonUnicastPkts ZeroBasedCounter, 1777 nlHostCreateTime LastCreateTime 1778 } 1780 nlHostTimeMark OBJECT-TYPE 1781 SYNTAX TimeFilter 1782 MAX-ACCESS not-accessible 1783 STATUS current 1784 DESCRIPTION 1785 "A TimeFilter for this entry. See the TimeFilter textual 1786 convention to see how this works." 1787 ::= { nlHostEntry 1 } 1789 nlHostAddress OBJECT-TYPE 1790 SYNTAX OCTET STRING 1791 MAX-ACCESS not-accessible 1792 STATUS current 1793 DESCRIPTION 1794 "The network address for this nlHostEntry. 1796 This is represented as an octet string with 1797 specific semantics and length as identified 1798 by the protocolDirLocalIndex component of the index. 1800 For example, if the protocolDirLocalIndex indicates an 1801 encapsulation of ip, this object is encoded as a length 1802 octet of 4, followed by the 4 octets of the ip address, 1803 in network byte order." 1804 ::= { nlHostEntry 2 } 1806 nlHostInPkts OBJECT-TYPE 1807 SYNTAX ZeroBasedCounter 1808 MAX-ACCESS read-only 1809 STATUS current 1810 DESCRIPTION 1811 "The number of packets without errors transmitted to 1812 this address since it was added to the nlHostTable. Note that 1813 this is the number of link-layer packets, so if a single 1814 network-layer packet is fragmented into several link-layer 1815 frames, this counter is incremented several times." 1816 ::= { nlHostEntry 3 } 1818 nlHostOutPkts OBJECT-TYPE 1819 SYNTAX ZeroBasedCounter 1820 MAX-ACCESS read-only 1821 STATUS current 1822 DESCRIPTION 1823 "The number of packets without errors transmitted by 1824 this address since it was added to the nlHostTable. Note that 1825 this is the number of link-layer packets, so if a single 1826 network-layer packet is fragmented into several link-layer 1827 frames, this counter is incremented several times." 1828 ::= { nlHostEntry 4 } 1830 nlHostInOctets OBJECT-TYPE 1831 SYNTAX ZeroBasedCounter 1832 MAX-ACCESS read-only 1833 STATUS current 1834 DESCRIPTION 1835 "The number of octets transmitted to this address 1836 since it was added to the nlHostTable (excluding 1837 framing bits but including FCS octets), excluding 1838 those octets in packets that contained errors. 1840 Note this doesn't count just those octets in the particular 1841 protocol frames, but includes the entire packet that contained 1842 the protocol." 1843 ::= { nlHostEntry 5 } 1845 nlHostOutOctets OBJECT-TYPE 1846 SYNTAX ZeroBasedCounter 1847 MAX-ACCESS read-only 1848 STATUS current 1849 DESCRIPTION 1850 "The number of octets transmitted by this address 1851 since it was added to the nlHostTable (excluding 1852 framing bits but including FCS octets), excluding 1853 those octets in packets that contained errors. 1855 Note this doesn't count just those octets in the particular 1856 protocol frames, but includes the entire packet that contained 1857 the protocol." 1858 ::= { nlHostEntry 6 } 1860 nlHostOutMacNonUnicastPkts OBJECT-TYPE 1861 SYNTAX ZeroBasedCounter 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "The number of packets without errors transmitted by this 1866 address that were directed to any MAC broadcast addresses 1867 or to any MAC multicast addresses since this host was 1868 added to the nlHostTable. Note that this is the number of 1869 link-layer packets, so if a single network-layer packet is 1870 fragmented into several link-layer frames, this counter is 1871 incremented several times." 1872 ::= { nlHostEntry 7 } 1874 nlHostCreateTime OBJECT-TYPE 1875 SYNTAX LastCreateTime 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "The value of sysUpTime when this entry was activated. 1880 This can be used by the management station to ensure that the 1881 entry has not been deleted and recreated between polls." 1882 ::= { nlHostEntry 8 } 1884 -- 1885 -- Network Layer Matrix Group 1886 -- 1887 -- Counts the amount of traffic sent between each pair of network 1888 -- addresses discovered by the probe. 1889 -- Note that while the hlMatrixControlTable also has objects that 1890 -- control optional alMatrixTables, implementation of the 1891 -- alMatrixTables is not required to fully implement this group. 1893 hlMatrixControlTable OBJECT-TYPE 1894 SYNTAX SEQUENCE OF HlMatrixControlEntry 1895 MAX-ACCESS not-accessible 1896 STATUS current 1897 DESCRIPTION 1898 "A list of higher layer (i.e. non-MAC) matrix control entries. 1900 These entries will enable the collection of the network and 1901 application level matrix tables containing conversation 1902 statistics indexed by pairs of network addresses. 1903 Both the network and application level matrix tables are 1904 controlled by this table is so that they will both be created 1905 and deleted at the same time, further increasing the ease with 1906 which they can be implemented as a single datastore (note that 1907 if an implementation stores application layer matrix records 1908 in memory, it can derive network layer matrix records from 1909 them). 1911 Entries in the nlMatrixSDTable and nlMatrixDSTable will be 1912 created on behalf of each entry in this table. Additionally, 1913 if this probe implements the alMatrix tables, entries in the 1914 alMatrix tables will be created on behalf of each entry in 1915 this table." 1916 ::= { nlMatrix 1 } 1918 hlMatrixControlEntry OBJECT-TYPE 1919 SYNTAX HlMatrixControlEntry 1920 MAX-ACCESS not-accessible 1921 STATUS current 1922 DESCRIPTION 1923 "A conceptual row in the hlMatrixControlTable. 1925 An example of indexing of this entry is 1926 hlMatrixControlNlDroppedFrames.1" 1927 INDEX { hlMatrixControlIndex } 1928 ::= { hlMatrixControlTable 1 } 1930 HlMatrixControlEntry ::= SEQUENCE { 1931 hlMatrixControlIndex Integer32, 1932 hlMatrixControlDataSource DataSource, 1933 hlMatrixControlNlDroppedFrames Counter32, 1934 hlMatrixControlNlInserts Counter32, 1935 hlMatrixControlNlDeletes Counter32, 1936 hlMatrixControlNlMaxDesiredEntries Integer32, 1937 hlMatrixControlAlDroppedFrames Counter32, 1938 hlMatrixControlAlInserts Counter32, 1939 hlMatrixControlAlDeletes Counter32, 1940 hlMatrixControlAlMaxDesiredEntries Integer32, 1941 hlMatrixControlOwner OwnerString, 1942 hlMatrixControlStatus RowStatus 1943 } 1945 hlMatrixControlIndex OBJECT-TYPE 1946 SYNTAX Integer32 (1..65535) 1947 MAX-ACCESS not-accessible 1948 STATUS current 1949 DESCRIPTION 1950 "An index that uniquely identifies an entry in the 1951 hlMatrixControlTable. Each such entry defines 1952 a function that discovers conversations on a particular 1953 interface and places statistics about them in the 1954 nlMatrixSDTable and the nlMatrixDSTable, and optionally the 1955 alMatrixSDTable and alMatrixDSTable, on behalf of this 1956 hlMatrixControlEntry." 1957 ::= { hlMatrixControlEntry 1 } 1959 hlMatrixControlDataSource OBJECT-TYPE 1960 SYNTAX DataSource 1961 MAX-ACCESS read-create 1962 STATUS current 1963 DESCRIPTION 1964 "The source of the data for the associated matrix tables. 1966 The statistics in this group reflect all packets 1967 on the local network segment attached to the 1968 identified interface. 1970 This object may not be modified if the associated 1971 hlMatrixControlStatus object is equal to active(1)." 1972 ::= { hlMatrixControlEntry 2 } 1974 hlMatrixControlNlDroppedFrames OBJECT-TYPE 1975 SYNTAX Counter32 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "The total number of frames which were received by the probe 1980 and therefore not accounted for in the *StatsDropEvents, but 1981 for which the probe chose not to count for this entry for 1982 whatever reason. Most often, this event occurs when the probe 1983 is out of some resources and decides to shed load from this 1984 collection. 1986 This count does not include packets that were not counted 1987 because they had MAC-layer errors. 1989 Note that if the nlMatrixTables are inactive because no 1990 protocols are enabled in the protocol directory, this value 1991 should be 0. 1993 Note that, unlike the dropEvents counter, this number is the 1994 exact number of frames dropped." 1995 ::= { hlMatrixControlEntry 3 } 1997 hlMatrixControlNlInserts OBJECT-TYPE 1998 SYNTAX Counter32 1999 MAX-ACCESS read-only 2000 STATUS current 2001 DESCRIPTION 2002 "The number of times an nlMatrix entry has been 2003 inserted into the nlMatrix tables. If an entry is inserted, 2004 then deleted, and then inserted, this counter will be 2005 incremented by 2. The addition of a conversation into both 2006 the nlMatrixSDTable and nlMatrixDSTable shall be counted as 2007 two insertions (even though every addition into one table must 2008 be accompanied by an insertion into the other). 2010 Note that the table size can be determined by subtracting 2011 hlMatrixControlNlDeletes from hlMatrixControlNlInserts." 2012 ::= { hlMatrixControlEntry 4 } 2014 hlMatrixControlNlDeletes OBJECT-TYPE 2015 SYNTAX Counter32 2016 MAX-ACCESS read-only 2017 STATUS current 2018 DESCRIPTION 2019 "The number of times an nlMatrix entry has been 2020 deleted from the nlMatrix tables (for any reason). If an 2021 entry is deleted, then inserted, and then deleted, this 2022 counter will be incremented by 2. The deletion of a 2023 conversation from both the nlMatrixSDTable and nlMatrixDSTable 2024 shall be counted as two deletions (even though every deletion 2025 from one table must be accompanied by a deletion from the 2026 other). 2028 Note that the table size can be determined by subtracting 2029 hlMatrixControlNlDeletes from hlMatrixControlNlInserts." 2030 ::= { hlMatrixControlEntry 5 } 2032 hlMatrixControlNlMaxDesiredEntries OBJECT-TYPE 2033 SYNTAX Integer32 2034 MAX-ACCESS read-create 2035 STATUS current 2036 DESCRIPTION 2037 "The maximum number of entries that are desired in the 2038 nlMatrix tables on behalf of this control entry. The probe 2039 will not create more than this number of associated entries in 2040 the table, but may choose to create fewer entries in this 2041 table for any reason including the lack of resources. 2043 If this value is set to -1, the probe may create any number 2044 of entries in this table. If the associated 2045 hlMatrixControlStatus object is equal to `active', this 2046 object may not be modified. 2048 This object may be used to control how resources are allocated 2049 on the probe for the various RMON functions." 2050 ::= { hlMatrixControlEntry 6 } 2052 hlMatrixControlAlDroppedFrames OBJECT-TYPE 2053 SYNTAX Counter32 2054 MAX-ACCESS read-only 2055 STATUS current 2056 DESCRIPTION 2057 "The total number of frames which were received by the probe 2058 and therefore not accounted for in the *StatsDropEvents, but 2059 for which the probe chose not to count for this entry for 2060 whatever reason. Most often, this event occurs when the probe 2061 is out of some resources and decides to shed load from this 2062 collection. 2064 This count does not include packets that were not counted 2065 because they had MAC-layer errors. 2067 Note that if the alMatrixTables are not implemented or are 2068 inactive because no protocols are enabled in the protocol 2069 directory, this value should be 0. 2071 Note that, unlike the dropEvents counter, this number is the 2072 exact number of frames dropped." 2073 ::= { hlMatrixControlEntry 7 } 2075 hlMatrixControlAlInserts OBJECT-TYPE 2076 SYNTAX Counter32 2077 MAX-ACCESS read-only 2078 STATUS current 2079 DESCRIPTION 2080 "The number of times an alMatrix entry has been 2081 inserted into the alMatrix tables. If an entry is inserted, 2082 then deleted, and then inserted, this counter will be 2083 incremented by 2. The addition of a conversation into both 2084 the alMatrixSDTable and alMatrixDSTable shall be counted as 2085 two insertions (even though every addition into one table must 2086 be accompanied by an insertion into the other). 2088 Note that the table size can be determined by subtracting 2089 hlMatrixControlAlDeletes from hlMatrixControlAlInserts." 2090 ::= { hlMatrixControlEntry 8 } 2092 hlMatrixControlAlDeletes OBJECT-TYPE 2093 SYNTAX Counter32 2094 MAX-ACCESS read-only 2095 STATUS current 2096 DESCRIPTION 2097 "The number of times an alMatrix entry has been 2098 deleted from the alMatrix tables. If an entry is deleted, 2099 then inserted, and then deleted, this counter will be 2100 incremented by 2. The deletion of a conversation from both 2101 the alMatrixSDTable and alMatrixDSTable shall be counted as 2102 two deletions (even though every deletion from one table must 2103 be accompanied by a deletion from the other). 2105 Note that the table size can be determined by subtracting 2106 hlMatrixControlAlDeletes from hlMatrixControlAlInserts." 2107 ::= { hlMatrixControlEntry 9 } 2109 hlMatrixControlAlMaxDesiredEntries OBJECT-TYPE 2110 SYNTAX Integer32 2111 MAX-ACCESS read-create 2112 STATUS current 2113 DESCRIPTION 2114 "The maximum number of entries that are desired in the 2115 alMatrix tables on behalf of this control entry. The probe 2116 will not create more than this number of associated entries in 2117 the table, but may choose to create fewer entries in this 2118 table for any reason including the lack of resources. 2120 If this value is set to -1, the probe may create any number 2121 of entries in this table. If the associated 2122 hlMatrixControlStatus object is equal to `active', this 2123 object may not be modified. 2125 This object may be used to control how resources are allocated 2126 on the probe for the various RMON functions." 2127 ::= { hlMatrixControlEntry 10 } 2129 hlMatrixControlOwner OBJECT-TYPE 2130 SYNTAX OwnerString 2131 MAX-ACCESS read-create 2132 STATUS current 2133 DESCRIPTION 2134 "The entity that configured this entry and is 2135 therefore using the resources assigned to it." 2136 ::= { hlMatrixControlEntry 11 } 2138 hlMatrixControlStatus OBJECT-TYPE 2139 SYNTAX RowStatus 2140 MAX-ACCESS read-create 2141 STATUS current 2142 DESCRIPTION 2143 "The status of this hlMatrixControlEntry. 2145 An entry may not exist in the active state unless all 2146 objects in the entry have an appropriate value. 2148 If this object is not equal to active(1), all 2149 associated entries in the nlMatrixSDTable, 2150 nlMatrixDSTable, alMatrixSDTable, and the alMatrixDSTable 2151 shall be deleted by the agent." 2152 ::= { hlMatrixControlEntry 12 } 2154 nlMatrixSDTable OBJECT-TYPE 2155 SYNTAX SEQUENCE OF NlMatrixSDEntry 2156 MAX-ACCESS not-accessible 2157 STATUS current 2158 DESCRIPTION 2159 "A list of traffic matrix entries which collect statistics for 2160 conversations between two network-level addresses. This table 2161 is indexed first by the source address and then by the 2162 destination address to make it convenient to collect all 2163 conversations from a particular address. 2165 The probe will populate this table for all network layer 2166 protocols in the protocol directory table whose value of 2167 protocolDirMatrixConfig is equal to supportedOn(3), and 2168 will delete any entries whose protocolDirEntry is deleted or 2169 has a protocolDirMatrixConfig value of supportedOff(2). 2171 The probe will add to this table all pairs of addresses 2172 seen in all packets with no MAC errors, and will increment 2173 octet and packet counts in the table for all packets with no 2174 MAC errors. 2176 Further, this table will only contain entries that have a 2177 corresponding entry in the nlMatrixDSTable with the same 2178 source address and destination address." 2179 ::= { nlMatrix 2 } 2181 nlMatrixSDEntry OBJECT-TYPE 2182 SYNTAX NlMatrixSDEntry 2183 MAX-ACCESS not-accessible 2184 STATUS current 2185 DESCRIPTION 2186 "A conceptual row in the nlMatrixSDTable. 2188 The hlMatrixControlIndex value in the index identifies the 2189 hlMatrixControlEntry on whose behalf this entry was created. 2190 The protocolDirLocalIndex value in the index identifies the 2191 network layer protocol of the nlMatrixSDSourceAddress and 2192 nlMatrixSDDestAddress. 2194 An example of the indexing of this table is 2195 nlMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7" 2196 INDEX { hlMatrixControlIndex, nlMatrixSDTimeMark, 2197 protocolDirLocalIndex, 2198 nlMatrixSDSourceAddress, nlMatrixSDDestAddress } 2199 ::= { nlMatrixSDTable 1 } 2201 NlMatrixSDEntry ::= SEQUENCE { 2202 nlMatrixSDTimeMark TimeFilter, 2203 nlMatrixSDSourceAddress OCTET STRING, 2204 nlMatrixSDDestAddress OCTET STRING, 2205 nlMatrixSDPkts ZeroBasedCounter, 2206 nlMatrixSDOctets ZeroBasedCounter, 2207 nlMatrixSDCreateTime LastCreateTime 2208 } 2210 nlMatrixSDTimeMark OBJECT-TYPE 2211 SYNTAX TimeFilter 2212 MAX-ACCESS not-accessible 2213 STATUS current 2214 DESCRIPTION 2215 "A TimeFilter for this entry. See the TimeFilter textual 2216 convention to see how this works." 2217 ::= { nlMatrixSDEntry 1 } 2219 nlMatrixSDSourceAddress OBJECT-TYPE 2220 SYNTAX OCTET STRING 2221 MAX-ACCESS not-accessible 2222 STATUS current 2223 DESCRIPTION 2224 "The network source address for this nlMatrixSDEntry. 2226 This is represented as an octet string with 2227 specific semantics and length as identified 2228 by the protocolDirLocalIndex component of the index. 2230 For example, if the protocolDirLocalIndex indicates an 2231 encapsulation of ip, this object is encoded as a length 2232 octet of 4, followed by the 4 octets of the ip address, 2233 in network byte order." 2234 ::= { nlMatrixSDEntry 2 } 2236 nlMatrixSDDestAddress OBJECT-TYPE 2237 SYNTAX OCTET STRING 2238 MAX-ACCESS not-accessible 2239 STATUS current 2240 DESCRIPTION 2241 "The network destination address for this 2242 nlMatrixSDEntry. 2244 This is represented as an octet string with 2245 specific semantics and length as identified 2246 by the protocolDirLocalIndex component of the index. 2248 For example, if the protocolDirLocalIndex indicates an 2249 encapsulation of ip, this object is encoded as a length 2250 octet of 4, followed by the 4 octets of the ip address, 2251 in network byte order." 2252 ::= { nlMatrixSDEntry 3 } 2254 nlMatrixSDPkts OBJECT-TYPE 2255 SYNTAX ZeroBasedCounter 2256 MAX-ACCESS read-only 2257 STATUS current 2258 DESCRIPTION 2259 "The number of packets without errors transmitted from the 2260 source address to the destination address since this entry was 2261 added to the nlMatrixSDTable. Note that this is the number of 2262 link-layer packets, so if a single network-layer packet is 2263 fragmented into several link-layer frames, this counter is 2264 incremented several times." 2265 ::= { nlMatrixSDEntry 4 } 2267 nlMatrixSDOctets OBJECT-TYPE 2268 SYNTAX ZeroBasedCounter 2269 MAX-ACCESS read-only 2270 STATUS current 2271 DESCRIPTION 2272 "The number of octets transmitted from the source address to 2273 the destination address since this entry was added to the 2274 nlMatrixSDTable (excluding framing bits but 2275 including FCS octets), excluding those octets in packets that 2276 contained errors. 2278 Note this doesn't count just those octets in the particular 2279 protocol frames, but includes the entire packet that contained 2280 the protocol." 2281 ::= { nlMatrixSDEntry 5 } 2283 nlMatrixSDCreateTime OBJECT-TYPE 2284 SYNTAX LastCreateTime 2285 MAX-ACCESS read-only 2286 STATUS current 2287 DESCRIPTION 2288 "The value of sysUpTime when this entry was activated. 2289 This can be used by the management station to ensure that the 2290 entry has not been deleted and recreated between polls." 2292 ::= { nlMatrixSDEntry 6 } 2294 -- Traffic matrix tables from destination to source 2296 nlMatrixDSTable OBJECT-TYPE 2297 SYNTAX SEQUENCE OF NlMatrixDSEntry 2298 MAX-ACCESS not-accessible 2299 STATUS current 2300 DESCRIPTION 2301 "A list of traffic matrix entries which collect statistics for 2302 conversations between two network-level addresses. This table 2303 is indexed first by the destination address and then by the 2304 source address to make it convenient to collect all 2305 conversations to a particular address. 2307 The probe will populate this table for all network layer 2308 protocols in the protocol directory table whose value of 2309 protocolDirMatrixConfig is equal to supportedOn(3), and 2310 will delete any entries whose protocolDirEntry is deleted or 2311 has a protocolDirMatrixConfig value of supportedOff(2). 2313 The probe will add to this table all pairs of addresses 2314 seen in all packets with no MAC errors, and will increment 2315 octet and packet counts in the table for all packets with no 2316 MAC errors. 2318 Further, this table will only contain entries that have a 2319 corresponding entry in the nlMatrixSDTable with the same 2320 source address and destination address." 2321 ::= { nlMatrix 3 } 2323 nlMatrixDSEntry OBJECT-TYPE 2324 SYNTAX NlMatrixDSEntry 2325 MAX-ACCESS not-accessible 2326 STATUS current 2327 DESCRIPTION 2328 "A conceptual row in the nlMatrixDSTable. 2330 The hlMatrixControlIndex value in the index identifies the 2331 hlMatrixControlEntry on whose behalf this entry was created. 2332 The protocolDirLocalIndex value in the index identifies the 2333 network layer protocol of the nlMatrixDSSourceAddress and 2334 nlMatrixDSDestAddress. 2336 An example of the indexing of this table is 2337 nlMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6" 2338 INDEX { hlMatrixControlIndex, nlMatrixDSTimeMark, 2339 protocolDirLocalIndex, 2340 nlMatrixDSDestAddress, nlMatrixDSSourceAddress } 2341 ::= { nlMatrixDSTable 1 } 2343 NlMatrixDSEntry ::= SEQUENCE { 2344 nlMatrixDSTimeMark TimeFilter, 2345 nlMatrixDSSourceAddress OCTET STRING, 2346 nlMatrixDSDestAddress OCTET STRING, 2347 nlMatrixDSPkts ZeroBasedCounter, 2348 nlMatrixDSOctets ZeroBasedCounter, 2349 nlMatrixDSCreateTime LastCreateTime 2350 } 2352 nlMatrixDSTimeMark OBJECT-TYPE 2353 SYNTAX TimeFilter 2354 MAX-ACCESS not-accessible 2355 STATUS current 2356 DESCRIPTION 2357 "A TimeFilter for this entry. See the TimeFilter textual 2358 convention to see how this works." 2359 ::= { nlMatrixDSEntry 1 } 2361 nlMatrixDSSourceAddress OBJECT-TYPE 2362 SYNTAX OCTET STRING 2363 MAX-ACCESS not-accessible 2364 STATUS current 2365 DESCRIPTION 2366 "The network source address for this nlMatrixDSEntry. 2368 This is represented as an octet string with 2369 specific semantics and length as identified 2370 by the protocolDirLocalIndex component of the index. 2372 For example, if the protocolDirLocalIndex indicates an 2373 encapsulation of ip, this object is encoded as a length 2374 octet of 4, followed by the 4 octets of the ip address, 2375 in network byte order." 2376 ::= { nlMatrixDSEntry 2 } 2378 nlMatrixDSDestAddress OBJECT-TYPE 2379 SYNTAX OCTET STRING 2380 MAX-ACCESS not-accessible 2381 STATUS current 2382 DESCRIPTION 2383 "The network destination address for this 2384 nlMatrixDSEntry. 2386 This is represented as an octet string with 2387 specific semantics and length as identified 2388 by the protocolDirLocalIndex component of the index. 2390 For example, if the protocolDirLocalIndex indicates an 2391 encapsulation of ip, this object is encoded as a length 2392 octet of 4, followed by the 4 octets of the ip address, 2393 in network byte order." 2394 ::= { nlMatrixDSEntry 3 } 2396 nlMatrixDSPkts OBJECT-TYPE 2397 SYNTAX ZeroBasedCounter 2398 MAX-ACCESS read-only 2399 STATUS current 2400 DESCRIPTION 2401 "The number of packets without errors transmitted from the 2402 destination address to the source address since this entry was 2403 added to the nlMatrixDSTable. Note that this is the number of 2404 link-layer packets, so if a single network-layer packet is 2405 fragmented into several link-layer frames, this counter is 2406 incremented several times." 2407 ::= { nlMatrixDSEntry 4 } 2409 nlMatrixDSOctets OBJECT-TYPE 2410 SYNTAX ZeroBasedCounter 2411 MAX-ACCESS read-only 2412 STATUS current 2413 DESCRIPTION 2414 "The number of octets transmitted from the destination address 2415 to the source address since this entry was added to the 2416 nlMatrixDSTable (excluding framing bits but 2417 including FCS octets), excluding those octets in packets that 2418 contained errors. 2420 Note this doesn't count just those octets in the particular 2421 protocol frames, but includes the entire packet that contained 2422 the protocol." 2423 ::= { nlMatrixDSEntry 5 } 2425 nlMatrixDSCreateTime OBJECT-TYPE 2426 SYNTAX LastCreateTime 2427 MAX-ACCESS read-only 2428 STATUS current 2429 DESCRIPTION 2430 "The value of sysUpTime when this entry was activated. 2431 This can be used by the management station to ensure that the 2432 entry has not been deleted and recreated between polls." 2433 ::= { nlMatrixDSEntry 6 } 2435 nlMatrixTopNControlTable OBJECT-TYPE 2436 SYNTAX SEQUENCE OF NlMatrixTopNControlEntry 2437 MAX-ACCESS not-accessible 2438 STATUS current 2439 DESCRIPTION 2440 "A set of parameters that control the creation of a 2441 report of the top N matrix entries according to 2442 a selected metric." 2443 ::= { nlMatrix 4 } 2445 nlMatrixTopNControlEntry OBJECT-TYPE 2446 SYNTAX NlMatrixTopNControlEntry 2447 MAX-ACCESS not-accessible 2448 STATUS current 2449 DESCRIPTION 2450 "A conceptual row in the nlMatrixTopNControlTable. 2452 An example of the indexing of this table is 2453 nlMatrixTopNDuration.3" 2454 INDEX { nlMatrixTopNControlIndex } 2455 ::= { nlMatrixTopNControlTable 1 } 2457 NlMatrixTopNControlEntry ::= SEQUENCE { 2458 nlMatrixTopNControlIndex Integer32, 2459 nlMatrixTopNMatrixIndex Integer32, 2460 nlMatrixTopNRateBase INTEGER, 2461 nlMatrixTopNTimeRemaining Integer32, 2462 nlMatrixTopNGeneratedReports Counter32, 2463 nlMatrixTopNDuration Integer32, 2464 nlMatrixTopNRequestedSize Integer32, 2465 nlMatrixTopNGrantedSize Integer32, 2466 nlMatrixTopNStartTime TimeTicks, 2467 nlMatrixTopNOwner OwnerString, 2468 nlMatrixTopNStatus RowStatus 2469 } 2470 nlMatrixTopNControlIndex OBJECT-TYPE 2471 SYNTAX Integer32 (1..65535) 2472 MAX-ACCESS read-only 2473 STATUS current 2474 DESCRIPTION 2475 "An index that uniquely identifies an entry 2476 in the nlMatrixTopNControlTable. Each such 2477 entry defines one top N report prepared for 2478 one interface." 2479 ::= { nlMatrixTopNControlEntry 1 } 2481 nlMatrixTopNMatrixIndex OBJECT-TYPE 2482 SYNTAX Integer32 (1..65535) 2483 MAX-ACCESS read-create 2484 STATUS current 2485 DESCRIPTION 2486 "The nlMatrix[SD/DS] table for which a top N report will be 2487 prepared on behalf of this entry. The nlMatrix[SD/DS] table 2488 is identified by the value of the hlMatrixControlIndex 2489 for that table - that value is used here to identify the 2490 particular table. 2492 This object may not be modified if the associated 2493 nlMatrixTopNStatus object is equal to active(1)." 2494 ::= { nlMatrixTopNControlEntry 2 } 2496 nlMatrixTopNRateBase OBJECT-TYPE 2497 SYNTAX INTEGER { 2498 nlMatrixTopNPkts(1), 2499 nlMatrixTopNOctets(2) 2500 } 2501 MAX-ACCESS read-create 2502 STATUS current 2503 DESCRIPTION 2504 "The variable for each nlMatrix[SD/DS] entry that the 2505 nlMatrixTopNEntries are sorted by. 2507 This object may not be modified if the associated 2508 nlMatrixTopNStatus object is equal to active(1)." 2509 ::= { nlMatrixTopNControlEntry 3 } 2511 nlMatrixTopNTimeRemaining OBJECT-TYPE 2512 SYNTAX Integer32 2513 MAX-ACCESS read-create 2514 STATUS current 2515 DESCRIPTION 2516 "The number of seconds left in the report currently 2517 being collected. When this object is modified by 2518 the management station, a new collection is started, 2519 possibly aborting a currently running report. The 2520 new value is used as the requested duration of this 2521 report, and is immediately loaded into the associated 2522 nlMatrixTopNDuration object. 2523 When the report finishes, the probe will automatically 2524 start another collection with the same initial value 2525 of nlMatrixTopNTimeRemaining. Thus the management station may 2526 simply read the resulting reports repeatedly, checking the 2527 startTime and duration each time to ensure that a report was 2528 not missed or that the report parameters were not changed. 2530 While the value of this object is non-zero, it decrements 2531 by one per second until it reaches zero. At the time 2532 that this object decrements to zero, the report is made 2533 accessible in the nlMatrixTopNTable, overwriting any report 2534 that may be there. 2536 When this object is modified by the management station, any 2537 associated entries in the nlMatrixTopNTable shall be deleted. 2539 (Note that this is a different algorithm than in 2540 the hostTopNTable)." 2541 DEFVAL { 1800 } 2542 ::= { nlMatrixTopNControlEntry 4 } 2544 nlMatrixTopNGeneratedReports OBJECT-TYPE 2545 SYNTAX Counter32 2546 MAX-ACCESS read-only 2547 STATUS current 2548 DESCRIPTION 2549 "The number of reports that have been generated by this entry." 2550 ::= { nlMatrixTopNControlEntry 5 } 2552 nlMatrixTopNDuration OBJECT-TYPE 2553 SYNTAX Integer32 2554 MAX-ACCESS read-only 2555 STATUS current 2556 DESCRIPTION 2557 "The number of seconds that this report has collected 2558 during the last sampling interval. 2560 When the associated nlMatrixTopNTimeRemaining object is 2561 set, this object shall be set by the probe to the 2562 same value and shall not be modified until the next 2563 time the nlMatrixTopNTimeRemaining is set. 2565 This value shall be zero if no reports have been 2566 requested for this nlMatrixTopNControlEntry." 2567 ::= { nlMatrixTopNControlEntry 6 } 2569 nlMatrixTopNRequestedSize OBJECT-TYPE 2570 SYNTAX Integer32 2571 MAX-ACCESS read-create 2572 STATUS current 2573 DESCRIPTION 2574 "The maximum number of matrix entries requested for this report. 2576 When this object is created or modified, the probe 2577 should set nlMatrixTopNGrantedSize as closely to this 2578 object as is possible for the particular probe 2579 implementation and available resources." 2580 DEFVAL { 150 } 2581 ::= { nlMatrixTopNControlEntry 7 } 2583 nlMatrixTopNGrantedSize OBJECT-TYPE 2584 SYNTAX Integer32 2585 MAX-ACCESS read-only 2586 STATUS current 2587 DESCRIPTION 2588 "The maximum number of matrix entries in this report. 2590 When the associated nlMatrixTopNRequestedSize object is 2591 created or modified, the probe should set this 2592 object as closely to the requested value as is 2593 possible for the particular implementation and 2594 available resources. The probe must not lower this 2595 value except as a result of a set to the associated 2596 nlMatrixTopNRequestedSize object. 2598 If the value of nlMatrixTopNRateBase is equal to 2599 nlMatrixTopNPkts, when the next topN report is generated, 2600 matrix entries with the highest value of nlMatrixTopNPktRate 2601 shall be placed in this table in decreasing order of this rate 2602 until there is no more room or until there are no more 2603 matrix entries. 2605 If the value of nlMatrixTopNRateBase is equal to 2606 nlMatrixTopNOctets, when the next topN report is generated, 2607 matrix entries with the highest value of nlMatrixTopNOctetRate 2608 shall be placed in this table in decreasing order of this rate 2609 until there is no more room or until there are no more 2610 matrix entries. 2612 It is an implementation-specific matter how entries with the 2613 same value of nlMatrixTopNPktRate or nlMatrixTopNOctetRate are 2614 sorted. It is also an implementation-specific matter as to 2615 whether or not zero-valued entries are available." 2616 ::= { nlMatrixTopNControlEntry 8 } 2618 nlMatrixTopNStartTime OBJECT-TYPE 2619 SYNTAX TimeTicks 2620 MAX-ACCESS read-only 2621 STATUS current 2622 DESCRIPTION 2623 "The value of sysUpTime when this top N report was 2624 last started. In other words, this is the time that 2625 the associated nlMatrixTopNTimeRemaining object was 2626 modified to start the requested report or the time 2627 the report was last automatically (re)started. 2629 This object may be used by the management station to 2630 determine if a report was missed or not." 2631 ::= { nlMatrixTopNControlEntry 9 } 2633 nlMatrixTopNOwner OBJECT-TYPE 2634 SYNTAX OwnerString 2635 MAX-ACCESS read-create 2636 STATUS current 2637 DESCRIPTION 2638 "The entity that configured this entry and is 2639 therefore using the resources assigned to it." 2640 ::= { nlMatrixTopNControlEntry 10 } 2642 nlMatrixTopNStatus OBJECT-TYPE 2643 SYNTAX RowStatus 2644 MAX-ACCESS read-create 2645 STATUS current 2646 DESCRIPTION 2647 "The status of this nlMatrixTopNControlEntry. 2649 An entry may not exist in the active state unless all 2650 objects in the entry have an appropriate value. 2652 If this object is not equal to active(1), all 2653 associated entries in the nlMatrixTopNTable shall be deleted 2654 by the agent." 2655 ::= { nlMatrixTopNControlEntry 11 } 2657 nlMatrixTopNTable OBJECT-TYPE 2658 SYNTAX SEQUENCE OF NlMatrixTopNEntry 2659 MAX-ACCESS not-accessible 2660 STATUS current 2661 DESCRIPTION 2662 "A set of statistics for those network layer matrix entries 2663 that have counted the highest number of octets or packets." 2664 ::= { nlMatrix 5 } 2666 nlMatrixTopNEntry OBJECT-TYPE 2667 SYNTAX NlMatrixTopNEntry 2668 MAX-ACCESS not-accessible 2669 STATUS current 2670 DESCRIPTION 2671 "A conceptual row in the nlMatrixTopNTable. 2673 The nlMatrixTopNControlIndex value in the index identifies the 2674 nlMatrixTopNControlEntry on whose behalf this entry was 2675 created. 2677 An example of the indexing of this table is 2678 nlMatrixTopNPktRate.3.10" 2679 INDEX { nlMatrixTopNControlIndex, nlMatrixTopNIndex } 2680 ::= { nlMatrixTopNTable 1 } 2682 NlMatrixTopNEntry ::= SEQUENCE { 2683 nlMatrixTopNIndex Integer32, 2684 nlMatrixTopNProtocolDirLocalIndex Integer32, 2685 nlMatrixTopNSourceAddress OCTET STRING, 2686 nlMatrixTopNDestAddress OCTET STRING, 2687 nlMatrixTopNPktRate Integer32, 2688 nlMatrixTopNReversePktRate Integer32, 2689 nlMatrixTopNOctetRate Integer32, 2690 nlMatrixTopNReverseOctetRate Integer32 2691 } 2693 nlMatrixTopNIndex OBJECT-TYPE 2694 SYNTAX Integer32 (1..65535) 2695 MAX-ACCESS read-only 2696 STATUS current 2697 DESCRIPTION 2698 "An index that uniquely identifies an entry in 2699 the nlMatrixTopNTable among those in the same report. 2700 This index is between 1 and N, where N is the 2701 number of entries in this report. 2703 If the value of nlMatrixTopNRateBase is equal to 2704 nlMatrixTopNPkts, increasing values of nlMatrixTopNIndex shall 2705 be assigned to entries with decreasing values of 2706 nlMatrixTopNPktRate until index N is assigned to the entry 2707 with the lowest value of nlMatrixTopNPktRate or there are no 2708 more nlMatrixTopNEntries. 2710 If the value of nlMatrixTopNRateBase is equal to 2711 nlMatrixTopNOctets, increasing values of nlMatrixTopNIndex 2712 shall be assigned to entries with decreasing values of 2713 nlMatrixTopNOctetRate until index N is assigned to the entry 2714 with the lowest value of nlMatrixTopNOctetRate or there are no 2715 more nlMatrixTopNEntries." 2716 ::= { nlMatrixTopNEntry 1 } 2718 nlMatrixTopNProtocolDirLocalIndex OBJECT-TYPE 2719 SYNTAX Integer32 (1..2147483647) 2720 MAX-ACCESS read-only 2721 STATUS current 2722 DESCRIPTION 2723 "The protocolDirLocalIndex of the network layer protocol of 2724 this entry's network address." 2725 ::= { nlMatrixTopNEntry 2 } 2727 nlMatrixTopNSourceAddress OBJECT-TYPE 2728 SYNTAX OCTET STRING 2729 MAX-ACCESS read-only 2730 STATUS current 2731 DESCRIPTION 2732 "The network layer address of the source host in this 2733 conversation. 2735 This is represented as an octet string with 2736 specific semantics and length as identified 2737 by the associated nlMatrixTopNProtocolDirLocalIndex. 2739 For example, if the protocolDirLocalIndex indicates an 2740 encapsulation of ip, this object is encoded as a length 2741 octet of 4, followed by the 4 octets of the ip address, 2742 in network byte order." 2743 ::= { nlMatrixTopNEntry 3 } 2745 nlMatrixTopNDestAddress OBJECT-TYPE 2746 SYNTAX OCTET STRING 2747 MAX-ACCESS read-only 2748 STATUS current 2749 DESCRIPTION 2750 "The network layer address of the destination host in this 2751 conversation. 2753 This is represented as an octet string with 2754 specific semantics and length as identified 2755 by the associated nlMatrixTopNProtocolDirLocalIndex. 2757 For example, if the nlMatrixTopNProtocolDirLocalIndex 2758 indicates an encapsulation of ip, this object is encoded as a 2759 length octet of 4, followed by the 4 octets of the ip address, 2760 in network byte order." 2761 ::= { nlMatrixTopNEntry 4 } 2763 nlMatrixTopNPktRate OBJECT-TYPE 2764 SYNTAX Integer32 2765 MAX-ACCESS read-only 2766 STATUS current 2767 DESCRIPTION 2768 "The number of packets seen from the source host 2769 to the destination host during this sampling interval, counted 2770 using the rules for counting the nlMatrixSDPkts object. 2771 If the value of nlMatrixTopNRateBase is nlMatrixTopNPkts, this 2772 variable will be used to sort this report." 2773 ::= { nlMatrixTopNEntry 5 } 2775 nlMatrixTopNReversePktRate OBJECT-TYPE 2776 SYNTAX Integer32 2777 MAX-ACCESS read-only 2778 STATUS current 2779 DESCRIPTION 2780 "The number of packets seen from the destination host to the 2781 source host during this sampling interval, counted 2782 using the rules for counting the nlMatrixDSPkts object. 2784 Note that if the value of nlMatrixTopNRateBase is equal to 2785 nlMatrixTopNPkts, the sort of topN entries is based entirely on 2786 nlMatrixTopNPktRate, and not on the value of this object." 2787 ::= { nlMatrixTopNEntry 6 } 2789 nlMatrixTopNOctetRate OBJECT-TYPE 2790 SYNTAX Integer32 2791 MAX-ACCESS read-only 2792 STATUS current 2793 DESCRIPTION 2794 "The number of octets seen from the source host 2795 to the destination host during this sampling interval, counted 2796 using the rules for counting the nlMatrixSDOctets object. If 2797 the value of nlMatrixTopNRateBase is nlMatrixTopNOctets, this 2798 variable will be used to sort this report." 2799 ::= { nlMatrixTopNEntry 7 } 2801 nlMatrixTopNReverseOctetRate OBJECT-TYPE 2802 SYNTAX Integer32 2803 MAX-ACCESS read-only 2804 STATUS current 2805 DESCRIPTION 2806 "The number of octets seen from the destination host to the 2807 source host during this sampling interval, counted 2808 using the rules for counting the nlMatrixDSOctets object. 2810 Note that if the value of nlMatrixTopNRateBase is equal to 2811 nlMatrixTopNOctets, the sort of topN entries is based entirely 2812 on nlMatrixTopNOctetRate, and not on the value of this object." 2813 ::= { nlMatrixTopNEntry 8 } 2815 -- Application Layer Functions 2816 -- 2817 -- The application layer host, matrix, and matrixTopN functions report 2818 -- on protocol usage at the network layer or higher. Note that the 2819 -- use of the term application layer does not imply that only 2820 -- application-layer protocols are counted, rather it means that 2821 -- protocols up to and including the application layer are supported. 2823 -- 2824 -- Application Layer Host Group 2825 -- 2826 -- Counts the amount of traffic, by protocol, sent from and to each 2827 -- network address discovered by the probe. 2828 -- Implementation of this group requires implementation of the Network 2829 -- Layer Host Group. 2831 alHostTable OBJECT-TYPE 2832 SYNTAX SEQUENCE OF AlHostEntry 2833 MAX-ACCESS not-accessible 2834 STATUS current 2835 DESCRIPTION 2836 "A collection of statistics for a particular protocol from a 2837 particular network address that has been discovered on an 2838 interface of this device. 2840 The probe will populate this table for all protocols in the 2841 protocol directory table whose value of 2842 protocolDirHostConfig is equal to supportedOn(3), and 2843 will delete any entries whose protocolDirEntry is deleted or 2844 has a protocolDirHostConfig value of supportedOff(2). 2846 The probe will add to this table all addresses 2847 seen as the source or destination address in all packets with 2848 no MAC errors, and will increment octet and packet counts in 2849 the table for all packets with no MAC errors. Further, 2850 entries will only be added to this table if their address 2851 exists in the nlHostTable and will be deleted from this table 2852 if their address is deleted from the nlHostTable." 2853 ::= { alHost 1 } 2855 alHostEntry OBJECT-TYPE 2856 SYNTAX AlHostEntry 2857 MAX-ACCESS not-accessible 2858 STATUS current 2859 DESCRIPTION 2860 "A conceptual row in the alHostTable. 2862 The hlHostControlIndex value in the index identifies the 2863 hlHostControlEntry on whose behalf this entry was created. 2864 The first protocolDirLocalIndex value in the index identifies 2865 the network layer protocol of the address. 2866 The nlHostAddress value in the index identifies the network 2867 layer address of this entry. 2868 The second protocolDirLocalIndex value in the index identifies 2869 the protocol that is counted by this entry. 2871 An example of the indexing in this entry is 2872 alHostOutPkts.1.783495.18.4.128.2.6.6.34" 2873 INDEX { hlHostControlIndex, alHostTimeMark, 2874 protocolDirLocalIndex, nlHostAddress, 2875 protocolDirLocalIndex } 2876 ::= { alHostTable 1 } 2878 AlHostEntry ::= SEQUENCE { 2879 alHostTimeMark TimeFilter, 2880 alHostInPkts ZeroBasedCounter, 2881 alHostOutPkts ZeroBasedCounter, 2882 alHostInOctets ZeroBasedCounter, 2883 alHostOutOctets ZeroBasedCounter, 2884 alHostCreateTime LastCreateTime 2885 } 2887 alHostTimeMark OBJECT-TYPE 2888 SYNTAX TimeFilter 2889 MAX-ACCESS not-accessible 2890 STATUS current 2891 DESCRIPTION 2892 "A TimeFilter for this entry. See the TimeFilter textual 2893 convention to see how this works." 2894 ::= { alHostEntry 1 } 2896 alHostInPkts OBJECT-TYPE 2897 SYNTAX ZeroBasedCounter 2898 MAX-ACCESS read-only 2899 STATUS current 2900 DESCRIPTION 2901 "The number of packets of this protocol type without errors 2902 transmitted to this address since it was added to the 2903 alHostTable. Note that this is the number of link-layer 2904 packets, so if a single network-layer packet is fragmented 2905 into several link-layer frames, this counter is incremented 2906 several times." 2907 ::= { alHostEntry 2 } 2909 alHostOutPkts OBJECT-TYPE 2910 SYNTAX ZeroBasedCounter 2911 MAX-ACCESS read-only 2912 STATUS current 2913 DESCRIPTION 2914 "The number of packets of this protocol type without errors 2915 transmitted by this address since it was added to the 2916 alHostTable. Note that this is the number of link-layer 2917 packets, so if a single network-layer packet is fragmented 2918 into several link-layer frames, this counter is incremented 2919 several times." 2920 ::= { alHostEntry 3 } 2922 alHostInOctets OBJECT-TYPE 2923 SYNTAX ZeroBasedCounter 2924 MAX-ACCESS read-only 2925 STATUS current 2926 DESCRIPTION 2927 "The number of octets transmitted to this address 2928 of this protocol type since it was added to the 2929 alHostTable (excluding framing bits but including 2930 FCS octets), excluding those octets in packets that 2931 contained errors. 2933 Note this doesn't count just those octets in the particular 2934 protocol frames, but includes the entire packet that contained 2935 the protocol." 2936 ::= { alHostEntry 4 } 2938 alHostOutOctets OBJECT-TYPE 2939 SYNTAX ZeroBasedCounter 2940 MAX-ACCESS read-only 2941 STATUS current 2942 DESCRIPTION 2943 "The number of octets transmitted by this address 2944 of this protocol type since it was added to the 2945 alHostTable (excluding framing bits but including 2946 FCS octets), excluding those octets in packets that 2947 contained errors. 2949 Note this doesn't count just those octets in the particular 2950 protocol frames, but includes the entire packet that contained 2951 the protocol." 2952 ::= { alHostEntry 5 } 2954 alHostCreateTime OBJECT-TYPE 2955 SYNTAX LastCreateTime 2956 MAX-ACCESS read-only 2957 STATUS current 2958 DESCRIPTION 2959 "The value of sysUpTime when this entry was activated. 2960 This can be used by the management station to ensure that the 2961 entry has not been deleted and recreated between polls." 2962 ::= { alHostEntry 6 } 2964 -- 2965 -- Application Layer Matrix Group 2966 -- 2967 -- Counts the amount of traffic, by protocol, sent between each pair 2968 -- of network addresses discovered by the probe. 2969 -- Implementation of this group requires implementation of the Network 2970 -- Layer Matrix Group. 2972 alMatrixSDTable OBJECT-TYPE 2973 SYNTAX SEQUENCE OF AlMatrixSDEntry 2974 MAX-ACCESS not-accessible 2975 STATUS current 2976 DESCRIPTION 2977 "A list of application traffic matrix entries which collect 2978 statistics for conversations of a particular protocol between 2979 two network-level addresses. This table is indexed first by 2980 the source address and then by the destination address to make 2981 it convenient to collect all statistics from a particular 2982 address. 2984 The probe will populate this table for all protocols in the 2985 protocol directory table whose value of 2986 protocolDirMatrixConfig is equal to supportedOn(3), and 2987 will delete any entries whose protocolDirEntry is deleted or 2988 has a protocolDirMatrixConfig value of supportedOff(2). 2990 The probe will add to this table all pairs of addresses for 2991 all protocols seen in all packets with no MAC errors, and will 2992 increment octet and packet counts in the table for all packets 2993 with no MAC errors. Further, entries will only be added to 2994 this table if their address pair exists in the nlMatrixSDTable 2995 and will be deleted from this table if the address pair is 2996 deleted from the nlMatrixSDTable." 2997 ::= { alMatrix 1 } 2999 alMatrixSDEntry OBJECT-TYPE 3000 SYNTAX AlMatrixSDEntry 3001 MAX-ACCESS not-accessible 3002 STATUS current 3003 DESCRIPTION 3004 "A conceptual row in the alMatrixSDTable. 3006 The hlMatrixControlIndex value in the index identifies the 3007 hlMatrixControlEntry on whose behalf this entry was created. 3008 The first protocolDirLocalIndex value in the index identifies 3009 the network layer protocol of the nlMatrixSDSourceAddress and 3010 nlMatrixSDDestAddress. 3011 The nlMatrixSDSourceAddress value in the index identifies the 3012 network layer address of the source host in this conversation. 3013 The nlMatrixSDDestAddress value in the index identifies the 3014 network layer address of the destination host in this 3015 conversation. 3016 The second protocolDirLocalIndex value in the index identifies 3017 the protocol that is counted by this entry. 3019 An example of the indexing of this entry is 3020 alMatrixSDPkts.1.783495.18.4.128.2.6.6.4.128.2.6.7.34" 3021 INDEX { hlMatrixControlIndex, alMatrixSDTimeMark, 3022 protocolDirLocalIndex, 3023 nlMatrixSDSourceAddress, nlMatrixSDDestAddress, 3024 protocolDirLocalIndex } 3025 ::= { alMatrixSDTable 1 } 3027 AlMatrixSDEntry ::= SEQUENCE { 3028 alMatrixSDTimeMark TimeFilter, 3029 alMatrixSDPkts ZeroBasedCounter, 3030 alMatrixSDOctets ZeroBasedCounter, 3031 alMatrixSDCreateTime LastCreateTime 3032 } 3034 alMatrixSDTimeMark OBJECT-TYPE 3035 SYNTAX TimeFilter 3036 MAX-ACCESS not-accessible 3037 STATUS current 3038 DESCRIPTION 3039 "A TimeFilter for this entry. See the TimeFilter textual 3040 convention to see how this works." 3041 ::= { alMatrixSDEntry 1 } 3043 alMatrixSDPkts OBJECT-TYPE 3044 SYNTAX ZeroBasedCounter 3045 MAX-ACCESS read-only 3046 STATUS current 3047 DESCRIPTION 3048 "The number of packets of this protocol type without errors 3049 transmitted from the source address to the destination address 3050 since this entry was added to the alMatrixSDTable. Note that 3051 this is the number of link-layer packets, so if a single 3052 network-layer packet is fragmented into several link-layer 3053 frames, this counter is incremented several times." 3055 ::= { alMatrixSDEntry 2 } 3057 alMatrixSDOctets OBJECT-TYPE 3058 SYNTAX ZeroBasedCounter 3059 MAX-ACCESS read-only 3060 STATUS current 3061 DESCRIPTION 3062 "The number of octets in packets of this protocol type 3063 transmitted from the source address to the destination address 3064 since this entry was added to the alMatrixSDTable (excluding 3065 framing bits but including FCS octets), excluding those octets 3066 in packets that contained errors. 3068 Note this doesn't count just those octets in the particular 3069 protocol frames, but includes the entire packet that contained 3070 the protocol." 3071 ::= { alMatrixSDEntry 3 } 3073 alMatrixSDCreateTime OBJECT-TYPE 3074 SYNTAX LastCreateTime 3075 MAX-ACCESS read-only 3076 STATUS current 3077 DESCRIPTION 3078 "The value of sysUpTime when this entry was activated. 3079 This can be used by the management station to ensure that the 3080 entry has not been deleted and recreated between polls." 3081 ::= { alMatrixSDEntry 4 } 3083 -- Traffic matrix tables from destination to source 3085 alMatrixDSTable OBJECT-TYPE 3086 SYNTAX SEQUENCE OF AlMatrixDSEntry 3087 MAX-ACCESS not-accessible 3088 STATUS current 3089 DESCRIPTION 3090 "A list of application traffic matrix entries which collect 3091 statistics for conversations of a particular protocol between 3092 two network-level addresses. This table is indexed first by 3093 the destination address and then by the source address to make 3094 it convenient to collect all statistics to a particular 3095 address. 3097 The probe will populate this table for all protocols in the 3098 protocol directory table whose value of 3099 protocolDirMatrixConfig is equal to supportedOn(3), and 3100 will delete any entries whose protocolDirEntry is deleted or 3101 has a protocolDirMatrixConfig value of supportedOff(2). 3103 The probe will add to this table all pairs of addresses for 3104 all protocols seen in all packets with no MAC errors, and will 3105 increment octet and packet counts in the table for all packets 3106 with no MAC errors. Further, entries will only be added to 3107 this table if their address pair exists in the nlMatrixDSTable 3108 and will be deleted from this table if the address pair is 3109 deleted from the nlMatrixDSTable." 3110 ::= { alMatrix 2 } 3112 alMatrixDSEntry OBJECT-TYPE 3113 SYNTAX AlMatrixDSEntry 3114 MAX-ACCESS not-accessible 3115 STATUS current 3116 DESCRIPTION 3117 "A conceptual row in the alMatrixDSTable. 3119 The hlMatrixControlIndex value in the index identifies the 3120 hlMatrixControlEntry on whose behalf this entry was created. 3121 The first protocolDirLocalIndex value in the index identifies 3122 the network layer protocol of the alMatrixDSSourceAddress and 3123 alMatrixDSDestAddress. 3124 The nlMatrixDSDestAddress value in the index identifies the 3125 network layer address of the destination host in this 3126 conversation. 3127 The nlMatrixDSSourceAddress value in the index identifies the 3128 network layer address of the source host in this conversation. 3129 The second protocolDirLocalIndex value in the index identifies 3130 the protocol that is counted by this entry. 3132 An example of the indexing of this entry is 3133 alMatrixDSPkts.1.783495.18.4.128.2.6.7.4.128.2.6.6.34" 3134 INDEX { hlMatrixControlIndex, alMatrixDSTimeMark, 3135 protocolDirLocalIndex, 3136 nlMatrixDSDestAddress, nlMatrixDSSourceAddress, 3137 protocolDirLocalIndex } 3138 ::= { alMatrixDSTable 1 } 3140 AlMatrixDSEntry ::= SEQUENCE { 3141 alMatrixDSTimeMark TimeFilter, 3142 alMatrixDSPkts ZeroBasedCounter, 3143 alMatrixDSOctets ZeroBasedCounter, 3144 alMatrixDSCreateTime LastCreateTime 3146 } 3148 alMatrixDSTimeMark OBJECT-TYPE 3149 SYNTAX TimeFilter 3150 MAX-ACCESS not-accessible 3151 STATUS current 3152 DESCRIPTION 3153 "A TimeFilter for this entry. See the TimeFilter textual 3154 convention to see how this works." 3155 ::= { alMatrixDSEntry 1 } 3157 alMatrixDSPkts OBJECT-TYPE 3158 SYNTAX ZeroBasedCounter 3159 MAX-ACCESS read-only 3160 STATUS current 3161 DESCRIPTION 3162 "The number of packets of this protocol type without errors 3163 transmitted from the destination address to the source address 3164 since this entry was added to the alMatrixDSTable. Note that 3165 this is the number of link-layer packets, so if a single 3166 network-layer packet is fragmented into several link-layer 3167 frames, this counter is incremented several times." 3168 ::= { alMatrixDSEntry 2 } 3170 alMatrixDSOctets OBJECT-TYPE 3171 SYNTAX ZeroBasedCounter 3172 MAX-ACCESS read-only 3173 STATUS current 3174 DESCRIPTION 3175 "The number of octets in packets of this protocol type 3176 transmitted from the destination address to the source address 3177 since this entry was added to the alMatrixDSTable (excluding 3178 framing bits but including FCS octets), excluding those octets 3179 in packets that contained errors. 3181 Note this doesn't count just those octets in the particular 3182 protocol frames, but includes the entire packet that contained 3183 the protocol." 3184 ::= { alMatrixDSEntry 3 } 3186 alMatrixDSCreateTime OBJECT-TYPE 3187 SYNTAX LastCreateTime 3188 MAX-ACCESS read-only 3189 STATUS current 3190 DESCRIPTION 3191 "The value of sysUpTime when this entry was activated. 3192 This can be used by the management station to ensure that the 3193 entry has not been deleted and recreated between polls." 3194 ::= { alMatrixDSEntry 4 } 3196 alMatrixTopNControlTable OBJECT-TYPE 3197 SYNTAX SEQUENCE OF AlMatrixTopNControlEntry 3198 MAX-ACCESS not-accessible 3199 STATUS current 3200 DESCRIPTION 3201 "A set of parameters that control the creation of a 3202 report of the top N matrix entries according to 3203 a selected metric." 3204 ::= { alMatrix 4 } 3206 alMatrixTopNControlEntry OBJECT-TYPE 3207 SYNTAX AlMatrixTopNControlEntry 3208 MAX-ACCESS not-accessible 3209 STATUS current 3210 DESCRIPTION 3211 "A conceptual row in the alMatrixTopNControlTable. 3213 An example of the indexing of this table is 3214 alMatrixTopNDuration.3" 3215 INDEX { alMatrixTopNControlIndex } 3216 ::= { alMatrixTopNControlTable 1 } 3218 AlMatrixTopNControlEntry ::= SEQUENCE { 3219 alMatrixTopNControlIndex Integer32, 3220 alMatrixTopNMatrixIndex Integer32, 3221 alMatrixTopNRateBase INTEGER, 3222 alMatrixTopNTimeRemaining Integer32, 3223 alMatrixTopNGeneratedReports Counter32, 3224 alMatrixTopNDuration Integer32, 3225 alMatrixTopNRequestedSize Integer32, 3226 alMatrixTopNGrantedSize Integer32, 3227 alMatrixTopNStartTime TimeTicks, 3228 alMatrixTopNOwner OwnerString, 3229 alMatrixTopNStatus RowStatus 3230 } 3232 alMatrixTopNControlIndex OBJECT-TYPE 3233 SYNTAX Integer32 (1..65535) 3234 MAX-ACCESS read-only 3235 STATUS current 3236 DESCRIPTION 3237 "An index that uniquely identifies an entry 3238 in the alMatrixTopNControlTable. Each such 3239 entry defines one top N report prepared for 3240 one interface." 3241 ::= { alMatrixTopNControlEntry 1 } 3243 alMatrixTopNMatrixIndex OBJECT-TYPE 3244 SYNTAX Integer32 (1..65535) 3245 MAX-ACCESS read-create 3246 STATUS current 3247 DESCRIPTION 3248 "The alMatrix[SD/DS] table for which a top N report will be 3249 prepared on behalf of this entry. The alMatrix[SD/DS] table 3250 is identified by the value of the hlMatrixControlIndex 3251 for that table - that value is used here to identify the 3252 particular table. 3254 This object may not be modified if the associated 3255 alMatrixTopNStatus object is equal to active(1)." 3256 ::= { alMatrixTopNControlEntry 2 } 3258 alMatrixTopNRateBase OBJECT-TYPE 3259 SYNTAX INTEGER { 3260 alMatrixTopNTerminalsPkts(1), 3261 alMatrixTopNTerminalsOctets(2), 3262 alMatrixTopNAllPkts(3), 3263 alMatrixTopNAllOctets(4) 3264 } 3265 MAX-ACCESS read-create 3266 STATUS current 3267 DESCRIPTION 3268 "The variable for each alMatrix[SD/DS] entry that the 3269 alMatrixTopNEntries are sorted by, as well as the 3270 selector of the view of the matrix table that will be 3271 used. 3273 The values alMatrixTopNTerminalsPkts and 3274 alMatrixTopNTerminalsOctets cause collection only from 3275 protocols that have no child protocols that are counted as 3276 well as protocols with the `other' parameter set (i.e., the 3277 count of unknown protocols). The values alMatrixTopNAllPkts 3278 and alMatrixTopNAllOctets cause collection from all alMatrix 3279 entries. 3281 This object may not be modified if the associated 3282 alMatrixTopNStatus object is equal to active(1)." 3283 ::= { alMatrixTopNControlEntry 3 } 3285 alMatrixTopNTimeRemaining OBJECT-TYPE 3286 SYNTAX Integer32 3287 MAX-ACCESS read-create 3288 STATUS current 3289 DESCRIPTION 3290 "The number of seconds left in the report currently 3291 being collected. When this object is modified by 3292 the management station, a new collection is started, 3293 possibly aborting a currently running report. The 3294 new value is used as the requested duration of this 3295 report, and is immediately loaded into the associated 3296 alMatrixTopNDuration object. 3297 When the report finishes, the probe will automatically 3298 start another collection with the same initial value 3299 of alMatrixTopNTimeRemaining. Thus the management station may 3300 simply read the resulting reports repeatedly, checking the 3301 startTime and duration each time to ensure that a report was 3302 not missed or that the report parameters were not changed. 3304 While the value of this object is non-zero, it decrements 3305 by one per second until it reaches zero. At the time 3306 that this object decrements to zero, the report is made 3307 accessible in the alMatrixTopNTable, overwriting any report 3308 that may be there. 3310 When this object is modified by the management station, any 3311 associated entries in the alMatrixTopNTable shall be deleted. 3313 (Note that this is a different algorithm than in 3314 the hostTopNTable)." 3315 DEFVAL { 1800 } 3316 ::= { alMatrixTopNControlEntry 4 } 3318 alMatrixTopNGeneratedReports OBJECT-TYPE 3319 SYNTAX Counter32 3320 MAX-ACCESS read-only 3321 STATUS current 3322 DESCRIPTION 3323 "The number of reports that have been generated by this entry." 3324 ::= { alMatrixTopNControlEntry 5 } 3326 alMatrixTopNDuration OBJECT-TYPE 3327 SYNTAX Integer32 3328 MAX-ACCESS read-only 3329 STATUS current 3330 DESCRIPTION 3331 "The number of seconds that this report has collected 3332 during the last sampling interval. 3334 When the associated alMatrixTopNTimeRemaining object is 3335 set, this object shall be set by the probe to the 3336 same value and shall not be modified until the next 3337 time the alMatrixTopNTimeRemaining is set. 3339 This value shall be zero if no reports have been 3340 requested for this alMatrixTopNControlEntry." 3341 ::= { alMatrixTopNControlEntry 6 } 3343 alMatrixTopNRequestedSize OBJECT-TYPE 3344 SYNTAX Integer32 3345 MAX-ACCESS read-create 3346 STATUS current 3347 DESCRIPTION 3348 "The maximum number of matrix entries requested for this report. 3350 When this object is created or modified, the probe 3351 should set alMatrixTopNGrantedSize as closely to this 3352 object as is possible for the particular probe 3353 implementation and available resources." 3354 DEFVAL { 150 } 3355 ::= { alMatrixTopNControlEntry 7 } 3357 alMatrixTopNGrantedSize OBJECT-TYPE 3358 SYNTAX Integer32 3359 MAX-ACCESS read-only 3360 STATUS current 3361 DESCRIPTION 3362 "The maximum number of matrix entries in this report. 3364 When the associated alMatrixTopNRequestedSize object is 3365 created or modified, the probe should set this 3366 object as closely to the requested value as is 3367 possible for the particular implementation and 3368 available resources. The probe must not lower this 3369 value except as a result of a set to the associated 3370 alMatrixTopNRequestedSize object. 3372 If the value of alMatrixTopNRateBase is equal to 3373 alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, when the 3374 next topN report is generated, matrix entries with the highest 3375 value of alMatrixTopNPktRate shall be placed in this table in 3376 decreasing order of this rate until there is no more room or 3377 until there are no more matrix entries. 3379 If the value of alMatrixTopNRateBase is equal to 3380 alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, when the 3381 next topN report is generated, matrix entries with the highest 3382 value of alMatrixTopNOctetRate shall be placed in this table 3383 in decreasing order of this rate until there is no more room 3384 or until there are no more matrix entries. 3386 It is an implementation-specific matter how entries with the 3387 same value of alMatrixTopNPktRate or alMatrixTopNOctetRate are 3388 sorted. It is also an implementation-specific matter as to 3389 whether or not zero-valued entries are available." 3390 ::= { alMatrixTopNControlEntry 8 } 3392 alMatrixTopNStartTime OBJECT-TYPE 3393 SYNTAX TimeTicks 3394 MAX-ACCESS read-only 3395 STATUS current 3396 DESCRIPTION 3397 "The value of sysUpTime when this top N report was 3398 last started. In other words, this is the time that 3399 the associated alMatrixTopNTimeRemaining object was 3400 modified to start the requested report or the time 3401 the report was last automatically (re)started. 3403 This object may be used by the management station to 3404 determine if a report was missed or not." 3405 ::= { alMatrixTopNControlEntry 9 } 3407 alMatrixTopNOwner OBJECT-TYPE 3408 SYNTAX OwnerString 3409 MAX-ACCESS read-create 3410 STATUS current 3411 DESCRIPTION 3412 "The entity that configured this entry and is 3413 therefore using the resources assigned to it." 3414 ::= { alMatrixTopNControlEntry 10 } 3416 alMatrixTopNStatus OBJECT-TYPE 3417 SYNTAX RowStatus 3418 MAX-ACCESS read-create 3419 STATUS current 3420 DESCRIPTION 3421 "The status of this alMatrixTopNControlEntry. 3423 An entry may not exist in the active state unless all 3424 objects in the entry have an appropriate value. 3426 If this object is not equal to active(1), all 3427 associated entries in the alMatrixTopNTable shall be deleted 3428 by the agent." 3429 ::= { alMatrixTopNControlEntry 11 } 3431 alMatrixTopNTable OBJECT-TYPE 3432 SYNTAX SEQUENCE OF AlMatrixTopNEntry 3433 MAX-ACCESS not-accessible 3434 STATUS current 3435 DESCRIPTION 3436 "A set of statistics for those application layer matrix 3437 entries that have counted the highest number of octets or 3438 packets." 3439 ::= { alMatrix 5 } 3441 alMatrixTopNEntry OBJECT-TYPE 3442 SYNTAX AlMatrixTopNEntry 3443 MAX-ACCESS not-accessible 3444 STATUS current 3445 DESCRIPTION 3446 "A conceptual row in the alMatrixTopNTable. 3448 The alMatrixTopNControlIndex value in the index identifies the 3449 alMatrixTopNControlEntry on whose behalf this entry was 3450 created. 3452 An example of the indexing of this table is 3453 alMatrixTopNPktRate.3.10" 3454 INDEX { alMatrixTopNControlIndex, alMatrixTopNIndex } 3455 ::= { alMatrixTopNTable 1 } 3457 AlMatrixTopNEntry ::= SEQUENCE { 3458 alMatrixTopNIndex Integer32, 3459 alMatrixTopNProtocolDirLocalIndex Integer32, 3460 alMatrixTopNSourceAddress OCTET STRING, 3461 alMatrixTopNDestAddress OCTET STRING, 3462 alMatrixTopNAppProtocolDirLocalIndex Integer32, 3463 alMatrixTopNPktRate Integer32, 3464 alMatrixTopNReversePktRate Integer32, 3465 alMatrixTopNOctetRate Integer32, 3466 alMatrixTopNReverseOctetRate Integer32 3467 } 3469 alMatrixTopNIndex OBJECT-TYPE 3470 SYNTAX Integer32 (1..65535) 3471 MAX-ACCESS read-only 3472 STATUS current 3473 DESCRIPTION 3474 "An index that uniquely identifies an entry in 3475 the alMatrixTopNTable among those in the same report. 3476 This index is between 1 and N, where N is the 3477 number of entries in this report. 3479 If the value of alMatrixTopNRateBase is equal to 3480 alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, increasing 3481 values of alMatrixTopNIndex shall be assigned to entries with 3482 decreasing values of alMatrixTopNPktRate until index N is 3483 assigned to the entry with the lowest value of 3484 alMatrixTopNPktRate or there are no more alMatrixTopNEntries. 3486 If the value of alMatrixTopNRateBase is equal to 3487 alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, 3488 increasing values of alMatrixTopNIndex shall be assigned to 3489 entries with decreasing values of alMatrixTopNOctetRate until 3490 index N is assigned to the entry with the lowest value of 3491 alMatrixTopNOctetRate or there are no more alMatrixTopNEntries." 3492 ::= { alMatrixTopNEntry 1 } 3494 alMatrixTopNProtocolDirLocalIndex OBJECT-TYPE 3495 SYNTAX Integer32 (1..2147483647) 3496 MAX-ACCESS read-only 3497 STATUS current 3498 DESCRIPTION 3499 "The protocolDirLocalIndex of the network layer protocol of 3500 this entry's network address." 3501 ::= { alMatrixTopNEntry 2 } 3503 alMatrixTopNSourceAddress OBJECT-TYPE 3504 SYNTAX OCTET STRING 3505 MAX-ACCESS read-only 3506 STATUS current 3507 DESCRIPTION 3508 "The network layer address of the source host in this 3509 conversation. 3511 This is represented as an octet string with 3512 specific semantics and length as identified 3513 by the associated alMatrixTopNProtocolDirLocalIndex. 3515 For example, if the alMatrixTopNProtocolDirLocalIndex 3516 indicates an encapsulation of ip, this object is encoded as a 3517 length octet of 4, followed by the 4 octets of the ip address, 3518 in network byte order." 3519 ::= { alMatrixTopNEntry 3 } 3521 alMatrixTopNDestAddress OBJECT-TYPE 3522 SYNTAX OCTET STRING 3523 MAX-ACCESS read-only 3524 STATUS current 3525 DESCRIPTION 3526 "The network layer address of the destination host in this 3527 conversation. 3529 This is represented as an octet string with 3530 specific semantics and length as identified 3531 by the associated alMatrixTopNProtocolDirLocalIndex. 3533 For example, if the alMatrixTopNProtocolDirLocalIndex 3534 indicates an encapsulation of ip, this object is encoded as a 3535 length octet of 4, followed by the 4 octets of the ip address, 3536 in network byte order." 3537 ::= { alMatrixTopNEntry 4 } 3539 alMatrixTopNAppProtocolDirLocalIndex OBJECT-TYPE 3540 SYNTAX Integer32 (1..2147483647) 3541 MAX-ACCESS read-only 3542 STATUS current 3543 DESCRIPTION 3544 "The type of the protocol counted by this matrix entry." 3545 ::= { alMatrixTopNEntry 5 } 3547 alMatrixTopNPktRate OBJECT-TYPE 3548 SYNTAX Integer32 3549 MAX-ACCESS read-only 3550 STATUS current 3551 DESCRIPTION 3552 "The number of packets seen of this protocol from the source 3553 host to the destination host during this sampling interval, 3554 counted using the rules for counting the alMatrixSDPkts 3555 object. If the value of alMatrixTopNRateBase is 3556 alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, this 3557 variable will be used to sort this report." 3558 ::= { alMatrixTopNEntry 6 } 3560 alMatrixTopNReversePktRate OBJECT-TYPE 3561 SYNTAX Integer32 3562 MAX-ACCESS read-only 3563 STATUS current 3564 DESCRIPTION 3565 "The number of packets seen of this protocol from the 3566 destination host to the source host during this sampling 3567 interval, counted using the rules for counting the 3568 alMatrixDSPkts object. 3570 Note that if the value of alMatrixTopNRateBase is equal to 3571 alMatrixTopNTerminalsPkts or alMatrixTopNAllPkts, the sort of 3572 topN entries is based entirely on alMatrixTopNPktRate, and not 3573 on the value of this object." 3574 ::= { alMatrixTopNEntry 7 } 3576 alMatrixTopNOctetRate OBJECT-TYPE 3577 SYNTAX Integer32 3578 MAX-ACCESS read-only 3579 STATUS current 3580 DESCRIPTION 3581 "The number of octets seen of this protocol from the source 3582 host to the destination host during this sampling interval, 3583 counted using the rules for counting the alMatrixSDOctets 3584 object. If the value of alMatrixTopNRateBase is 3585 alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, this 3586 variable will be used to sort this report." 3587 ::= { alMatrixTopNEntry 8 } 3589 alMatrixTopNReverseOctetRate OBJECT-TYPE 3590 SYNTAX Integer32 3591 MAX-ACCESS read-only 3592 STATUS current 3593 DESCRIPTION 3594 "The number of octets seen of this protocol from the 3595 destination host to the source host during this sampling 3596 interval, counted using the rules for counting the 3597 alMatrixDSOctets object. 3599 Note that if the value of alMatrixTopNRateBase is equal to 3600 alMatrixTopNTerminalsOctets or alMatrixTopNAllOctets, the sort 3601 of topN entries is based entirely on alMatrixTopNOctetRate, 3602 and not on the value of this object." 3603 ::= { alMatrixTopNEntry 9 } 3605 -- 3606 -- User History Collection Group (usrHistory) 3607 -- 3608 -- The usrHistory group combines mechanisms seen in the alarm and 3609 -- history groups to provide user-specified history collection, 3610 -- utilizing two additional control tables and one additional data 3611 -- table. This function has traditionally been done by NMS 3612 -- applications, via periodic polling. The usrHistory group allows 3613 -- this task to be offloaded to an RMON probe. 3614 -- 3615 -- Data (an ASN.1 INTEGER based object) is collected in the same 3616 -- manner as any history data table (e.g. etherHistoryTable) except 3617 -- that the user specifies the MIB instances to be collected. Objects 3618 -- are collected in bucket-groups, with the intent that all MIB 3619 -- instances in the same bucket-group are collected as atomically as 3620 -- possible by the RMON probe. 3621 -- 3622 -- The usrHistoryControlTable is a one-dimensional read-create table. 3623 -- Each row configures a collection of user history buckets, much 3624 -- the same as a historyControlEntry, except that the creation of a 3625 -- row in this table will cause one or more associated instances in 3626 -- the usrHistoryObjectTable to be created. The user specifies the 3627 -- number of bucket elements (rows in the usrHistoryObjectTable) 3628 -- requested, as well as the number of buckets requested. 3629 -- 3630 -- The usrHistoryObjectTable is a 2-d read-write table. 3631 -- Each row configures a single MIB instance to be collected. 3632 -- All rows with the same major index constitute a bucket-group. 3633 -- 3634 -- The usrHistoryTable is a 3-d read-only table containing 3635 -- the data of associated usrHistoryControlEntries. Each 3636 -- entry represents the value of a single MIB instance 3637 -- during a specific sampling interval (or the rate of 3638 -- change during the interval). 3639 -- 3640 -- A sample value is stored in two objects - an absolute value and 3641 -- a status object. This allows numbers from -(2G-1) to +4G to be 3642 -- stored. The status object also indicates whether a sample is 3643 -- valid. This allows data collection to continue if periodic 3644 -- retrieval of a particular instance fails for any reason. 3645 -- 3646 -- Row Creation Order Relationships 3647 -- 3648 -- The static nature of the usrHistoryObjectTable creates 3649 -- some row creation/modification issues. The rows in this 3650 -- table need to be set before the associated 3651 -- usrHistoryControlEntry can be activated. 3652 -- 3653 -- Note that the usrHistoryObject entries associated with a 3654 -- particular usrHistoryControlEntry are not required to 3655 -- be active before the control entry is activated. However, 3656 -- the usrHistory data entries associated with an inactive 3657 -- usrHistoryObject entry will be inactive (i.e. 3658 -- usrHistoryValStatus == valueNotAvailable). 3659 -- 3661 usrHistoryControlTable OBJECT-TYPE 3662 SYNTAX SEQUENCE OF UsrHistoryControlEntry 3663 MAX-ACCESS not-accessible 3664 STATUS current 3665 DESCRIPTION 3666 "A list of data-collection configuration entries." 3667 ::= { usrHistory 1 } 3669 usrHistoryControlEntry OBJECT-TYPE 3670 SYNTAX UsrHistoryControlEntry 3671 MAX-ACCESS not-accessible 3672 STATUS current 3673 DESCRIPTION 3674 "A list of parameters that set up a group of user-defined 3675 MIB objects to be sampled periodically (called a 3676 bucket-group). 3678 For example, an instance of usrHistoryControlInterval 3679 might be named usrHistoryControlInterval.1" 3680 INDEX { usrHistoryControlIndex } 3681 ::= { usrHistoryControlTable 1 } 3683 UsrHistoryControlEntry ::= SEQUENCE { 3684 usrHistoryControlIndex Integer32, 3685 usrHistoryControlObjects Integer32, 3686 usrHistoryControlBucketsRequested Integer32, 3687 usrHistoryControlBucketsGranted Integer32, 3688 usrHistoryControlInterval Integer32, 3689 usrHistoryControlOwner OwnerString, 3690 usrHistoryControlStatus RowStatus 3691 } 3693 usrHistoryControlIndex OBJECT-TYPE 3694 SYNTAX Integer32 (1..65535) 3695 MAX-ACCESS not-accessible 3696 STATUS current 3697 DESCRIPTION 3698 "An index that uniquely identifies an entry in the 3699 usrHistoryControlTable. Each such entry defines a 3700 set of samples at a particular interval for a specified 3701 set of MIB instances available from the managed system." 3702 ::= { usrHistoryControlEntry 1 } 3704 usrHistoryControlObjects OBJECT-TYPE 3705 SYNTAX Integer32 (1..65535) 3706 MAX-ACCESS read-create 3707 STATUS current 3708 DESCRIPTION 3709 "The number of MIB objects to be collected 3710 in the portion of usrHistoryTable associated with this 3711 usrHistoryControlEntry. 3713 This object may not be modified if the associated instance 3714 of usrHistoryControlStatus is equal to active(1)." 3715 ::= { usrHistoryControlEntry 2 } 3717 usrHistoryControlBucketsRequested OBJECT-TYPE 3718 SYNTAX Integer32 (1..65535) 3719 MAX-ACCESS read-create 3720 STATUS current 3721 DESCRIPTION 3722 "The requested number of discrete time intervals 3723 over which data is to be saved in the part of the 3724 usrHistoryTable associated with this usrHistoryControlEntry. 3726 When this object is created or modified, the probe 3727 should set usrHistoryControlBucketsGranted as closely to 3728 this object as is possible for the particular probe 3729 implementation and available resources." 3730 DEFVAL { 50 } 3731 ::= { usrHistoryControlEntry 3 } 3733 usrHistoryControlBucketsGranted OBJECT-TYPE 3734 SYNTAX Integer32 (1..65535) 3735 MAX-ACCESS read-only 3736 STATUS current 3737 DESCRIPTION 3738 "The number of discrete sampling intervals 3739 over which data shall be saved in the part of 3740 the usrHistoryTable associated with this 3741 usrHistoryControlEntry. 3743 When the associated usrHistoryControlBucketsRequested 3744 object is created or modified, the probe should set 3745 this object as closely to the requested value as is 3746 possible for the particular probe implementation and 3747 available resources. The probe must not lower this 3748 value except as a result of a modification to the associated 3749 usrHistoryControlBucketsRequested object. 3751 The associated usrHistoryControlBucketsRequested object 3752 should be set before or at the same time as this object 3753 to allow the probe to accurately estimate the resources 3754 required for this usrHistoryControlEntry. 3756 There will be times when the actual number of buckets 3757 associated with this entry is less than the value of 3758 this object. In this case, at the end of each sampling 3759 interval, a new bucket will be added to the usrHistoryTable. 3761 When the number of buckets reaches the value of this object 3762 and a new bucket is to be added to the usrHistoryTable, 3763 the oldest bucket associated with this usrHistoryControlEntry 3764 shall be deleted by the agent so that the new bucket can be 3765 added. 3767 When the value of this object changes to a value less than 3768 the current value, entries are deleted from the 3769 usrHistoryTable associated with this usrHistoryControlEntry. 3770 Enough of the oldest of these entries shall be deleted by the 3771 agent so that their number remains less than or equal to the 3772 new value of this object. 3774 When the value of this object changes to a value greater 3775 than the current value, the number of associated usrHistory 3776 entries may be allowed to grow." 3777 ::= { usrHistoryControlEntry 4 } 3779 usrHistoryControlInterval OBJECT-TYPE 3780 SYNTAX Integer32 (1..2147483647) 3781 MAX-ACCESS read-create 3782 STATUS current 3783 DESCRIPTION 3784 "The interval in seconds over which the data is 3785 sampled for each bucket in the part of the usrHistory 3786 table associated with this usrHistoryControlEntry. 3788 Because the counters in a bucket may overflow at their 3789 maximum value with no indication, a prudent manager will 3790 take into account the possibility of overflow in any of 3791 the associated counters. It is important to consider the 3792 minimum time in which any counter could overflow on a 3793 particular media type and set the usrHistoryControlInterval 3794 object to a value less than this interval. 3796 This object may not be modified if the associated 3797 usrHistoryControlStatus object is equal to active(1)." 3798 DEFVAL { 1800 } 3799 ::= { usrHistoryControlEntry 5 } 3801 usrHistoryControlOwner OBJECT-TYPE 3802 SYNTAX OwnerString 3803 MAX-ACCESS read-create 3804 STATUS current 3805 DESCRIPTION 3806 "The entity that configured this entry and is 3807 therefore using the resources assigned to it." 3808 ::= { usrHistoryControlEntry 6 } 3810 usrHistoryControlStatus OBJECT-TYPE 3811 SYNTAX RowStatus 3812 MAX-ACCESS read-create 3813 STATUS current 3814 DESCRIPTION 3815 "The status of this variable history control entry. 3817 An entry may not exist in the active state unless all 3818 objects in the entry have an appropriate value. 3820 If this object is not equal to active(1), all associated 3821 entries in the usrHistoryObjectTable and the usrHistoryTable 3822 shall be deleted." 3823 ::= { usrHistoryControlEntry 7 } 3825 -- Object table 3827 usrHistoryObjectTable OBJECT-TYPE 3828 SYNTAX SEQUENCE OF UsrHistoryObjectEntry 3829 MAX-ACCESS not-accessible 3830 STATUS current 3831 DESCRIPTION 3832 "A list of data-collection configuration entries." 3833 ::= { usrHistory 2 } 3835 usrHistoryObjectEntry OBJECT-TYPE 3836 SYNTAX UsrHistoryObjectEntry 3837 MAX-ACCESS not-accessible 3838 STATUS current 3839 DESCRIPTION 3840 "A list of MIB instances to be sampled periodically. 3842 Entries in this table are created when an associated 3843 usrHistoryControlObjects object is created. 3845 The usrHistoryControlIndex value in the index is 3846 that of the associated usrHistoryControlEntry. 3848 For example, an instance of usrHistoryObjectVariable might be 3849 usrHistoryObjectVariable.1.3" 3850 INDEX { usrHistoryControlIndex, usrHistoryObjectIndex } 3851 ::= { usrHistoryObjectTable 1 } 3853 UsrHistoryObjectEntry ::= SEQUENCE { 3854 usrHistoryObjectIndex Integer32, 3855 usrHistoryObjectVariable OBJECT IDENTIFIER, 3856 usrHistoryObjectSampleType INTEGER 3857 } 3859 usrHistoryObjectIndex OBJECT-TYPE 3860 SYNTAX Integer32 (1..65535) 3861 MAX-ACCESS not-accessible 3862 STATUS current 3863 DESCRIPTION 3864 "An index used to uniquely identify an entry in the 3865 usrHistoryObject table. Each such entry defines a 3866 MIB instance to be collected periodically." 3867 ::= { usrHistoryObjectEntry 1 } 3869 usrHistoryObjectVariable OBJECT-TYPE 3870 SYNTAX OBJECT IDENTIFIER 3871 MAX-ACCESS read-create 3872 STATUS current 3873 DESCRIPTION 3874 "The object identifier of the particular variable to be 3875 sampled. 3877 Only variables that resolve to an ASN.1 primitive type of 3878 Integer32 (Integer32, Counter, Gauge, or TimeTicks) may be 3879 sampled. 3881 Because SNMP access control is articulated entirely in terms 3882 of the contents of MIB views, no access control mechanism 3883 exists that can restrict the value of this object to identify 3884 only those objects that exist in a particular MIB view. 3885 Because there is thus no acceptable means of restricting the 3886 read access that could be obtained through the user history 3887 mechanism, the probe must only grant write access to this 3888 object in those views that have read access to all objects on 3889 the probe. 3891 During a set operation, if the supplied variable name is not 3892 available in the selected MIB view, a badValue error must be 3893 returned. 3895 This object may not be modified if the associated 3896 usrHistoryControlStatus object is equal to active(1)." 3897 ::= { usrHistoryObjectEntry 2 } 3899 usrHistoryObjectSampleType OBJECT-TYPE 3900 SYNTAX INTEGER { 3901 absoluteValue(1), 3902 deltaValue(2) 3903 } 3904 MAX-ACCESS read-create 3905 STATUS current 3906 DESCRIPTION 3907 "The method of sampling the selected variable for storage in 3908 the usrHistoryTable. 3910 If the value of this object is absoluteValue(1), the value of 3911 the selected variable will be copied directly into the history 3912 bucket. 3914 If the value of this object is deltaValue(2), the value of the 3915 selected variable at the last sample will be subtracted from 3916 the current value, and the difference will be stored in the 3917 history bucket. If the associated usrHistoryObjectVariable 3918 instance could not be obtained at the previous sample 3919 interval, then a delta sample is not possible, and the value 3920 of the associated usrHistoryValStatus object for this interval 3921 will be valueNotAvailable(1). 3923 This object may not be modified if the associated 3924 usrHistoryControlStatus object is equal to active(1)." 3925 ::= { usrHistoryObjectEntry 3 } 3927 -- data table 3929 usrHistoryTable OBJECT-TYPE 3930 SYNTAX SEQUENCE OF UsrHistoryEntry 3931 MAX-ACCESS not-accessible 3932 STATUS current 3933 DESCRIPTION 3934 "A list of user defined history entries." 3935 ::= { usrHistory 3 } 3937 usrHistoryEntry OBJECT-TYPE 3938 SYNTAX UsrHistoryEntry 3939 MAX-ACCESS not-accessible 3940 STATUS current 3941 DESCRIPTION 3942 "An historical sample of user-defined variables. This sample 3943 is associated with the usrHistoryControlEntry which set up the 3944 parameters for a regular collection of these samples. 3946 The usrHistoryControlIndex value in the index identifies the 3947 usrHistoryControlEntry on whose behalf this entry was created. 3948 The usrHistoryObjectIndex value in the index identifies the 3949 usrHistoryObjectEntry on whose behalf this entry was created. 3951 For example, an instance of usrHistoryAbsValue, which represents 3952 the 14th sample of a variable collected as specified by 3953 usrHistoryControlEntry.1 and usrHistoryObjectEntry.1.5, 3954 would be named usrHistoryAbsValue.1.14.5" 3955 INDEX { usrHistoryControlIndex, usrHistorySampleIndex, 3956 usrHistoryObjectIndex } 3957 ::= { usrHistoryTable 1 } 3959 UsrHistoryEntry ::= SEQUENCE { 3960 usrHistorySampleIndex Integer32, 3961 usrHistoryIntervalStart TimeTicks, 3962 usrHistoryIntervalEnd TimeTicks, 3963 usrHistoryAbsValue Gauge32, 3964 usrHistoryValStatus INTEGER 3965 } 3967 usrHistorySampleIndex OBJECT-TYPE 3968 SYNTAX Integer32 (1..2147483647) 3969 MAX-ACCESS not-accessible 3970 STATUS current 3971 DESCRIPTION 3972 "An index that uniquely identifies the particular sample this 3973 entry represents among all samples associated with the same 3974 usrHistoryControlEntry. This index starts at 1 and increases 3975 by one as each new sample is taken." 3976 ::= { usrHistoryEntry 1 } 3978 usrHistoryIntervalStart OBJECT-TYPE 3979 SYNTAX TimeTicks 3980 MAX-ACCESS read-only 3981 STATUS current 3982 DESCRIPTION 3983 "The value of sysUpTime at the start of the interval over 3984 which this sample was measured. If the probe keeps track of 3985 the time of day, it should start the first sample of the 3986 history at a time such that when the next hour of the day 3987 begins, a sample is started at that instant. 3989 Note that following this rule may require the probe to delay 3990 collecting the first sample of the history, as each sample 3991 must be of the same interval. Also note that the sample which 3992 is currently being collected is not accessible in this table 3993 until the end of its interval." 3994 ::= { usrHistoryEntry 2 } 3996 usrHistoryIntervalEnd OBJECT-TYPE 3997 SYNTAX TimeTicks 3998 MAX-ACCESS read-only 3999 STATUS current 4000 DESCRIPTION 4001 "The value of sysUpTime at the end of the interval over which 4002 this sample was measured." 4003 ::= { usrHistoryEntry 3 } 4005 usrHistoryAbsValue OBJECT-TYPE 4006 SYNTAX Gauge32 4007 MAX-ACCESS read-only 4008 STATUS current 4009 DESCRIPTION 4010 "The absolute value (i.e. unsigned value) of the 4011 user-specified statistic during the last sampling period. The 4012 value during the current sampling period is not made available 4013 until the period is completed. 4015 To obtain the true value for this sampling interval, the 4016 associated instance of usrHistoryValStatus must be checked, 4017 and usrHistoryAbsValue adjusted as necessary. 4019 If the MIB instance could not be accessed during the sampling 4020 interval, then this object will have a value of zero and the 4021 associated instance of usrHistoryValStatus will be set to 4022 'valueNotAvailable(1)'." 4023 ::= { usrHistoryEntry 4 } 4025 usrHistoryValStatus OBJECT-TYPE 4026 SYNTAX INTEGER { 4027 valueNotAvailable(1), 4028 valuePositive(2), 4029 valueNegative(3) 4030 } 4031 MAX-ACCESS read-only 4032 STATUS current 4033 DESCRIPTION 4034 "This object indicates the validity and sign of the data in 4035 the associated instance of usrHistoryAbsValue. 4037 If the MIB instance could not be accessed during the sampling 4038 interval, then 'valueNotAvailable(1)' will be returned. 4040 If the sample is valid and actual value of the sample is 4041 greater than or equal to zero then 'valuePositive(2)' is 4042 returned. 4044 If the sample is valid and the actual value of the sample is 4045 less than zero, 'valueNegative(3)' will be returned. The 4046 associated instance of usrHistoryAbsValue should be multiplied 4047 by -1 to obtain the true sample value." 4048 ::= { usrHistoryEntry 5 } 4050 -- The Probe Configuration Group 4051 -- 4052 -- This group controls the configuration of various operating 4053 -- parameters of the probe. 4055 ControlString ::= DisplayString 4056 -- This data type is used to communicate with a modem or a serial 4057 -- data switch. A ControlString contains embedded commands to 4058 -- control how the device will interact with the remote device 4059 -- through the serial interface. Commands are represented as 4060 -- two character sequences beginning with the "^" character. 4061 -- The following commands are recognized by the device (note 4062 -- that command characters are case sensitive): 4063 -- 4064 -- ^s Send string that follows which is terminated by the next 4065 -- command or the end of string. 4066 -- ^c Delay for the number of seconds that follows. Toss out 4067 -- any data received rather than storing it in a buffer for 4068 -- parsing. 4069 -- ^t Set timeout to the value represented by the decimal 4070 -- digits that follow. The default timeout is 20 seconds. 4071 -- Note that this timeout may be overridden by a smaller 4072 -- serialTimeout configured for the associated serial 4073 -- interface (see serialConfigTable). 4074 -- ^w Wait for the reply string that follows which is terminated 4075 -- by the next command or the end of string. Partial and 4076 -- case insensitive matching is applied, ie. if the reply 4077 -- string (any case combination) is found anywhere in the 4078 -- received string, then the a match is found. If the 4079 -- current timeout elapses without a match, then the 4080 -- remaining control string is ignored. 4081 -- ^! The ^ character. 4082 -- ^d Delay the number of seconds specified by the decimal 4083 -- digits that follow. 4084 -- ^b Send break for the number of milliseconds specified by 4085 -- the decimal digits that follow. If no digits follow, 4086 -- break will be enforced for 250 milliseconds by default. 4087 -- 4088 -- The following ASCII control characters may be inserted into 4089 -- the "^s" send string or the "^w" reply string: 4090 -- 4091 -- ^@ 0x00 4092 -- ^A 0x01 4093 -- .. 4094 -- ^M 0x0D 4095 -- .. 4096 -- ^Z 0x1A 4097 -- ^[ 0x1B 4098 -- ^ 0x1C 4099 -- ^] 0x1D 4100 -- ^^ 0x1E 4101 -- ^_ 0x1F 4102 -- 4103 -- Binary data may also be inserted into the data stream. The 4104 -- control sequence for each byte of binary data is ^0x##, where 4105 -- ## is the hexadecimal representation of the data byte. Two 4106 -- ASCII characters (0-9, a-f, A-F) must follow the "^0x" control 4107 -- prefix. For example, "^0x0D^0x0A" is interpreted as a carriage 4108 -- return followed by a line feed. 4110 probeCapabilities OBJECT-TYPE 4111 SYNTAX Integer32 4112 MAX-ACCESS read-only 4113 STATUS current 4114 DESCRIPTION 4115 "An indication of the RMON MIB groups supported 4116 on at least one interface by this probe. 4117 The value of this mask is a sum. This sum 4118 initially takes the value zero. Then, for each 4119 MIB group G, that is supported by this probe, 4120 2 raised to a value representing G is added to the 4121 sum. 4123 Over time, additional MIB groups may be defined. A 4124 probe must set all unused bits to zero, and an NMS 4125 must ignore unknown bits. 4127 The RMON groups are defined as follows: 4129 G (bit#) Group name 4130 -------------------------------------- 4131 From RFC 1757: 4132 0 etherStats 4133 1 historyControl 4134 2 etherHistory 4135 3 alarm 4136 4 hosts 4137 5 hostTopN 4138 6 matrix 4139 7 filter 4140 8 capture 4141 9 event 4143 From RFC 1513: 4144 10 tokenRingMLStats 4145 11 tokenRingPStats 4146 12 tokenRingMLHistory 4147 13 tokenRingPHistory 4148 14 ringStation 4149 15 ringStationOrder 4150 16 ringStationConfig 4151 17 sourceRouting 4153 From RMON-2: 4154 18 protocolDirectory 4155 19 protocolDistribution 4156 20 addressMapping 4157 21 nlHost 4158 22 nlMatrix 4159 23 alHost 4160 24 alMatrix 4161 25 usrHistory 4162 26 probeConfig 4164 For example, an RMON probe supporting the etherStats, 4165 historyControl, and etherHistory groups would have 4166 a value of 7 (2^0 + 2^1 + 2^2)." 4167 ::= { probeConfig 1 } 4169 probeIdentification OBJECT-TYPE 4170 SYNTAX DisplayString (SIZE(0..127)) 4171 MAX-ACCESS read-write 4172 STATUS current 4173 DESCRIPTION 4174 "A string uniquely identifying this device." 4175 ::= { probeConfig 2 } 4177 probeSoftwareRev OBJECT-TYPE 4178 SYNTAX DisplayString (SIZE(0..15)) 4179 MAX-ACCESS read-only 4180 STATUS current 4181 DESCRIPTION 4182 "The software revision of this device." 4183 ::= { probeConfig 3 } 4185 probeHardwareRev OBJECT-TYPE 4186 SYNTAX DisplayString (SIZE(0..31)) 4187 MAX-ACCESS read-only 4188 STATUS current 4189 DESCRIPTION 4190 "The hardware revision of this device." 4191 ::= { probeConfig 4 } 4193 probeDateTime OBJECT-TYPE 4194 SYNTAX OCTET STRING (SIZE (0 | 8 | 11)) 4195 MAX-ACCESS read-write 4196 STATUS current 4197 DESCRIPTION 4198 "Probe's current date and time. 4200 field octets contents range 4201 ----- ------ -------- ----- 4202 1 1-2 year 0..65536 4203 2 3 month 1..12 4204 3 4 day 1..31 4205 4 5 hour 0..23 4206 5 6 minutes 0..59 4207 6 7 seconds 0..60 4208 (use 60 for leap-second) 4209 7 8 deci-seconds 0..9 4210 8 9 direction from UTC '+' / '-' 4211 9 10 hours from UTC 0..11 4212 10 11 minutes from UTC 0..59 4214 For example, Tuesday May 26, 1992 at 1:30:15 PM 4215 EDT would be displayed as: 4217 1992-5-26,13:30:15.0,-4:0 4219 Note that if only local time is known, then 4220 timezone information (fields 8-10) is not 4221 present, and if no time information is known, the null 4222 string is returned." 4223 ::= { probeConfig 5 } 4225 probeResetControl OBJECT-TYPE 4226 SYNTAX INTEGER { 4227 running(1), 4228 warmBoot(2), 4229 coldBoot(3) 4231 } 4232 MAX-ACCESS read-write 4233 STATUS current 4234 DESCRIPTION 4235 "Setting this object to warmBoot(2) causes the device to 4236 restart the application software with current configuration 4237 parameters saved in non-volatile memory. Setting this 4238 object to coldBoot(3) causes the device to reinitialize 4239 configuration parameters in non-volatile memory to default 4240 values and restart the application software. When the device 4241 is running normally, this variable has a value of 4242 running(1)." 4243 ::= { probeConfig 6 } 4245 probeDownloadFile OBJECT-TYPE 4246 SYNTAX DisplayString (SIZE(0..127)) 4247 MAX-ACCESS read-write 4248 STATUS current 4249 DESCRIPTION 4250 "The file name to be downloaded from the TFTP server." 4251 ::= { probeConfig 7 } 4253 probeDownloadTFTPServer OBJECT-TYPE 4254 SYNTAX IpAddress 4255 MAX-ACCESS read-write 4256 STATUS current 4257 DESCRIPTION 4258 "The IP address of the TFTP server that contains the boot 4259 image to load." 4260 ::= { probeConfig 8 } 4262 probeDownloadAction OBJECT-TYPE 4263 SYNTAX INTEGER { 4264 imageValid(1), 4265 downloadToPROM(2), 4266 downloadToRAM(3) 4267 } 4268 MAX-ACCESS read-write 4269 STATUS current 4270 DESCRIPTION 4271 "When this object is set to downloadToRAM(2) or 4272 downloadToPROM(3), the device will discontinue its 4273 normal operation and begin download of the image specified 4274 by probeDownloadFile from the server specified by 4275 probeDownloadTFTPServer using the TFTP protocol. If 4276 downloadToRAM(2) is specified, the new image is copied 4277 to RAM only (the old image remains unaltered in the flash 4278 EPROM). If downloadToPROM(3) is specified 4279 the new image is written to the flash EPROM 4280 memory after its checksum has been verified to be correct. 4281 When the download process is completed, the device will 4282 warm boot to restart the newly loaded application. 4283 When the device is not downloading, this object will have 4284 a value of imageValid(1)." 4285 ::= { probeConfig 9 } 4287 probeDownloadStatus OBJECT-TYPE 4288 SYNTAX INTEGER { 4289 downloadSuccess(1), 4290 downloadStatusUnknown(2), 4291 downloadGeneralError(3), 4292 downloadNoResponseFromServer(4), 4293 downloadChecksumError(5), 4294 downloadIncompatibleImage(6), 4295 tftpFileNotFound(7), 4296 tftpAccessViolation(8) 4297 } 4298 MAX-ACCESS read-only 4299 STATUS current 4300 DESCRIPTION 4301 "The status of the last download procedure, if any. This 4302 object will have a value of downloadStatusUnknown(2) if no 4303 download process has been performed." 4304 ::= { probeConfig 10 } 4306 serialConfigTable OBJECT-TYPE 4307 SYNTAX SEQUENCE OF SerialConfigEntry 4308 MAX-ACCESS not-accessible 4309 STATUS current 4310 DESCRIPTION 4311 "A table of serial interface configuration entries. This data 4312 will be stored in non-volatile memory and preserved across 4313 probe resets or power loss." 4314 ::= { probeConfig 11 } 4316 serialConfigEntry OBJECT-TYPE 4317 SYNTAX SerialConfigEntry 4318 MAX-ACCESS not-accessible 4319 STATUS current 4320 DESCRIPTION 4321 "A set of configuration parameters for a particular 4322 serial interface on this device." 4323 INDEX { serialIfIndex } 4324 ::= { serialConfigTable 1 } 4326 SerialConfigEntry ::= SEQUENCE { 4327 serialIfIndex Integer32, 4328 serialIpAddress IpAddress, 4329 serialSubnetMask IpAddress, 4330 serialMode INTEGER, 4331 serialProtocol INTEGER, 4332 serialSpeed INTEGER, 4333 serialTimeout Integer32 (1..65535), 4334 serialModemInitString ControlString (SIZE (0..255)), 4335 serialModemHangUpString ControlString (SIZE (0..255)), 4336 serialModemConnectResp DisplayString (SIZE (0..255)), 4337 serialModemNoConnectResp DisplayString (SIZE (0..255)), 4338 serialFlowControl INTEGER, 4339 serialDialoutTimeout Integer32 (1..65535), 4340 serialStatus RowStatus 4341 } 4343 serialIfIndex OBJECT-TYPE 4344 SYNTAX Integer32 (1..65535) 4345 MAX-ACCESS not-accessible 4346 STATUS current 4347 DESCRIPTION 4348 "The value of this object uniquely identifies the serial 4349 interface on this device for which this entry contains 4350 configuration parameters. The interface identified by a 4351 particular value of this object is the same interface as 4352 identified by the same value of the ifIndex object, defined 4353 in RFC 1213." 4354 ::= { serialConfigEntry 1 } 4356 serialIpAddress OBJECT-TYPE 4357 SYNTAX IpAddress 4358 MAX-ACCESS read-create 4359 STATUS current 4360 DESCRIPTION 4361 "The IP address of this serial interface." 4362 ::= { serialConfigEntry 2 } 4364 serialSubnetMask OBJECT-TYPE 4365 SYNTAX IpAddress 4366 MAX-ACCESS read-create 4367 STATUS current 4368 DESCRIPTION 4369 "The IP subnet mask of this serial interface." 4370 ::= { serialConfigEntry 3 } 4372 serialMode OBJECT-TYPE 4373 SYNTAX INTEGER { 4374 direct(1), 4375 modem(2) 4376 } 4377 MAX-ACCESS read-create 4378 STATUS current 4379 DESCRIPTION 4380 "The type of incoming connection to expect on this serial 4381 interface." 4382 DEFVAL { direct } 4383 ::= { serialConfigEntry 4 } 4385 serialProtocol OBJECT-TYPE 4386 SYNTAX INTEGER { 4387 other(1), 4388 slip(2), 4389 ppp(3) 4390 } 4391 MAX-ACCESS read-create 4392 STATUS current 4393 DESCRIPTION 4394 "The type of data link encapsulation to be used on this 4395 serial interface." 4396 DEFVAL { slip } 4397 ::= { serialConfigEntry 5 } 4399 serialSpeed OBJECT-TYPE 4400 SYNTAX INTEGER { 4401 speed300bps(1), 4402 speed1200bps(2), 4403 speed2400bps(3), 4404 speed4800bps(4), 4405 speed9600bps(5), 4406 speed14400bps(6), 4407 speed19200bps(7), 4408 speed38400bps(8), 4409 speed57600bps(9) 4410 } 4412 MAX-ACCESS read-create 4413 STATUS current 4414 DESCRIPTION 4415 "The data rate to configure this serial interface to on 4416 startup as well as after each serial connection." 4417 DEFVAL { speed9600bps } 4418 ::= { serialConfigEntry 6 } 4420 serialTimeout OBJECT-TYPE 4421 SYNTAX Integer32 (1..65535) 4422 MAX-ACCESS read-create 4423 STATUS current 4424 DESCRIPTION 4425 "This timeout value is used when the Management Station has 4426 initiated the conversation over the serial link. This variable 4427 represents the number of seconds of inactivity allowed before 4428 terminating the connection on this serial interface. Use the 4429 serialDialoutTimeout in the case where the probe has initiated 4430 the connection for the purpose of sending a trap." 4431 DEFVAL { 300 } 4432 ::= { serialConfigEntry 7 } 4434 serialModemInitString OBJECT-TYPE 4435 SYNTAX ControlString (SIZE (0..255)) 4436 MAX-ACCESS read-create 4437 STATUS current 4438 DESCRIPTION 4439 "A control string which controls how a modem attached to this 4440 serial interface should be initialized. The initialization 4441 is performed once during startup and again after each 4442 connection is terminated if the associated serialMode has the 4443 value of modem(2). 4445 A control string that is appropriate for a wide variety of 4446 modems is: '^s^MATE0Q0V1X4 S0=1 S2=43^M'." 4447 ::= { serialConfigEntry 8 } 4449 serialModemHangUpString OBJECT-TYPE 4450 SYNTAX ControlString (SIZE (0..255)) 4451 MAX-ACCESS read-create 4452 STATUS current 4453 DESCRIPTION 4454 "A control string which specifies how to disconnect a modem 4455 connection on this serial interface. This object is only 4456 meaningful if the associated serialMode has the value 4457 of modem(2). 4458 A control string that is appropriate for a wide variety of 4459 modems is: '^d2^s+++^d2^sATH0^M^d2'." 4460 ::= { serialConfigEntry 9 } 4462 serialModemConnectResp OBJECT-TYPE 4463 SYNTAX DisplayString (SIZE (0..255)) 4464 MAX-ACCESS read-create 4465 STATUS current 4466 DESCRIPTION 4467 "An ASCII string containing substrings that describe the 4468 expected modem connection response code and associated bps 4469 rate. The substrings are delimited by the first character 4470 in the string, for example: 4471 /CONNECT/300/CONNECT 1200/1200/CONNECT 2400/2400/ 4472 CONNECT 4800/4800/CONNECT 9600/9600 4473 will be interpreted as: 4474 response code bps rate 4475 CONNECT 300 4476 CONNECT 1200 1200 4477 CONNECT 2400 2400 4478 CONNECT 4800 4800 4479 CONNECT 9600 9600 4480 The agent will use the information in this string to adjust 4481 the bps rate of this serial interface once a modem connection 4482 is established. 4484 A value that is appropriate for a wide variety of modems is: 4485 '/CONNECT/300/CONNECT 1200/1200/CONNECT 2400/2400/ 4486 CONNECT 4800/4800/CONNECT 9600/9600/CONNECT 14400/14400/ 4487 CONNECT 19200/19200/CONNECT 38400/38400/'." 4488 ::= { serialConfigEntry 10 } 4490 serialModemNoConnectResp OBJECT-TYPE 4491 SYNTAX DisplayString (SIZE (0..255)) 4492 MAX-ACCESS read-create 4493 STATUS current 4494 DESCRIPTION 4495 "An ASCII string containing response codes that may be 4496 generated by a modem to report the reason why a connection 4497 attempt has failed. The response codes are delimited by 4498 the first character in the string, for example: 4499 /NO CARRIER/BUSY/NO DIALTONE/NO ANSWER/ERROR/ 4500 If one of these response codes is received via this serial 4501 interface while attempting to make a modem connection, 4502 the agent will issue the hang up command as specified by 4503 serialModemHangUpString. 4505 A value that is appropriate for a wide variety of modems is: 4506 '/NO CARRIER/BUSY/NO DIALTONE/NO ANSWER/ERROR/'." 4507 ::= { serialConfigEntry 11 } 4509 serialFlowControl OBJECT-TYPE 4510 SYNTAX INTEGER { 4511 noFlowControl(1), 4512 hardwareFlowControl(2) 4513 } 4514 MAX-ACCESS read-create 4515 STATUS current 4516 DESCRIPTION 4517 "The type of flow control to use on this serial 4518 interface." 4519 DEFVAL { hardwareFlowControl } 4520 ::= { serialConfigEntry 12 } 4522 serialDialoutTimeout OBJECT-TYPE 4523 SYNTAX Integer32 (1..65535) 4524 MAX-ACCESS read-create 4525 STATUS current 4526 DESCRIPTION 4527 "This timeout value is used when the probe initiates the 4528 serial connection with the intention of contacting a 4529 management station. This variable represents the number 4530 of seconds of inactivity allowed before terminating the 4531 connection on this serial interface." 4532 DEFVAL { 20 } 4533 ::= { serialConfigEntry 13 } 4535 serialStatus OBJECT-TYPE 4536 SYNTAX RowStatus 4537 MAX-ACCESS read-create 4538 STATUS current 4539 DESCRIPTION 4540 "The status of this serialConfigEntry. 4542 An entry may not exist in the active state unless all 4543 objects in the entry have an appropriate value." 4544 ::= { serialConfigEntry 14 } 4546 netConfigTable OBJECT-TYPE 4547 SYNTAX SEQUENCE OF NetConfigEntry 4548 MAX-ACCESS not-accessible 4549 STATUS current 4550 DESCRIPTION 4551 "A table of netConfigEntries." 4552 ::= { probeConfig 12 } 4554 netConfigEntry OBJECT-TYPE 4555 SYNTAX NetConfigEntry 4556 MAX-ACCESS not-accessible 4557 STATUS current 4558 DESCRIPTION 4559 "A set of configuration parameters for a particular 4560 network interface on this device." 4561 INDEX { netConfigIfIndex } 4562 ::= { netConfigTable 1 } 4564 NetConfigEntry ::= SEQUENCE { 4565 netConfigIfIndex Integer32, 4566 netConfigIPAddress IpAddress, 4567 netConfigSubnetMask IpAddress, 4568 netConfigStatus RowStatus 4569 } 4571 netConfigIfIndex OBJECT-TYPE 4572 SYNTAX Integer32 (1..65535) 4573 MAX-ACCESS not-accessible 4574 STATUS current 4575 DESCRIPTION 4576 "The value of this object uniquely identifies the physical 4577 interface on this device for which this entry contains 4578 configuration parameters. The interface identified by a 4579 particular value of this object is the same interface as 4580 identified by the same value of the ifIndex object, defined 4581 in RFC 1213." 4582 ::= { netConfigEntry 1 } 4584 netConfigIPAddress OBJECT-TYPE 4585 SYNTAX IpAddress 4586 MAX-ACCESS read-create 4587 STATUS current 4588 DESCRIPTION 4589 "The IP address of this Net interface. The default value 4590 for this object is 0.0.0.0. If either the netConfigIPAddress 4591 or netConfigSubnetMask are 0.0.0.0, then when the device 4592 boots, it may use BOOTP to try to figure out what these 4593 values should be. Otherwise, if BOOTP fails, before the device 4594 can talk on the network, this value must be configured through 4595 a terminal attached to the device. If BOOTP is used, care 4596 should be taken to not send BOOTP broadcasts too frequently 4597 and to eventually send very infrequently if no replies are 4598 received." 4599 ::= { netConfigEntry 2 } 4601 netConfigSubnetMask OBJECT-TYPE 4602 SYNTAX IpAddress 4603 MAX-ACCESS read-create 4604 STATUS current 4605 DESCRIPTION 4606 "The subnet mask of this Net interface. The default value 4607 for this object is 0.0.0.0. If either the netConfigIPAddress 4608 or netConfigSubnetMask are 0.0.0.0, then when the device 4609 boots, it may use BOOTP to try to figure out what these 4610 values should be. Otherwise, if BOOTP fails, before the device 4611 can talk on the network, this value must be configured through 4612 a terminal attached to the device.. If BOOTP is used, care 4613 should be taken to not send BOOTP broadcasts too frequently 4614 and to eventually send very infrequently if no replies are 4615 received." 4616 ::= { netConfigEntry 3 } 4618 netConfigStatus OBJECT-TYPE 4619 SYNTAX RowStatus 4620 MAX-ACCESS read-create 4621 STATUS current 4622 DESCRIPTION 4623 "The status of this netConfigEntry. 4625 An entry may not exist in the active state unless all 4626 objects in the entry have an appropriate value." 4627 ::= { netConfigEntry 4 } 4629 netDefaultGateway OBJECT-TYPE 4630 SYNTAX IpAddress 4631 MAX-ACCESS read-create 4632 STATUS current 4633 DESCRIPTION 4634 "The IP Address of the default gateway" 4635 ::= { probeConfig 13 } 4637 -- Trap Destination Table 4638 -- 4639 -- This table defines the destination addresses for traps generated 4640 -- from the device. This table maps a community to one or more trap 4641 -- destination entries. 4642 -- 4643 -- The same trap will be sent to all destinations specified in the 4644 -- entries that have the same trapDestCommunity as the eventCommunity 4645 -- (as defined by RMON MIB). Information in this table will be stored 4646 -- in non-volatile memory. If the device has gone through a hard 4647 -- restart, this information will be reset to its default state. 4649 trapDestTable OBJECT-TYPE 4650 SYNTAX SEQUENCE OF TrapDestEntry 4651 MAX-ACCESS not-accessible 4652 STATUS current 4653 DESCRIPTION 4654 "A list of trap destination entries." 4655 ::= { probeConfig 14 } 4657 trapDestEntry OBJECT-TYPE 4658 SYNTAX TrapDestEntry 4659 MAX-ACCESS not-accessible 4660 STATUS current 4661 DESCRIPTION 4662 "This entry includes a destination IP address to which to send 4663 traps for this community." 4664 INDEX { trapDestIndex } 4665 ::= { trapDestTable 1 } 4667 TrapDestEntry ::= SEQUENCE { 4668 trapDestIndex Integer32, 4669 trapDestCommunity OCTET STRING, 4670 trapDestProtocol INTEGER, 4671 trapDestAddress OCTET STRING, 4672 trapDestOwner OwnerString, 4673 trapDestStatus RowStatus 4674 } 4676 trapDestIndex OBJECT-TYPE 4677 SYNTAX Integer32 (1..65535) 4678 MAX-ACCESS not-accessible 4679 STATUS current 4680 DESCRIPTION 4681 "A value that uniquely identifies this trapDestEntry." 4683 ::= { trapDestEntry 1 } 4685 trapDestCommunity OBJECT-TYPE 4686 SYNTAX OCTET STRING (SIZE(0..127)) 4687 MAX-ACCESS read-create 4688 STATUS current 4689 DESCRIPTION 4690 "A community to which these destination IP addresses belong. 4691 This entry is associated with any eventEntries in the RMON 4692 MIB whose value of eventCommunity is equal to the value of 4693 this object. Every time an associated event entry sends a 4694 trap due to an event, that trap will be sent to each IP 4695 address in the trapDestTable with a trapDestCommunity equal to 4696 eventCommunity. 4698 This object may not be modified if the associated 4699 trapDestStatus object is equal to active(1)." 4700 ::= { trapDestEntry 2 } 4702 trapDestProtocol OBJECT-TYPE 4703 SYNTAX INTEGER { 4704 ip(1), 4705 ipx(2) 4706 } 4707 MAX-ACCESS read-create 4708 STATUS current 4709 DESCRIPTION 4710 "The protocol with which to send this trap." 4711 ::= { trapDestEntry 3 } 4713 trapDestAddress OBJECT-TYPE 4714 SYNTAX OCTET STRING 4715 MAX-ACCESS read-create 4716 STATUS current 4717 DESCRIPTION 4718 "The address to send traps on behalf of this entry. 4720 If the associated trapDestProtocol object is equal to ip(1), 4721 the encoding of this object is the same as the snmpUDPAddress 4722 textual convention in [RFC1449]: 4723 -- for a SnmpUDPAddress of length 6: 4724 -- 4725 -- octets contents encoding 4726 -- 1-4 IP-address network-byte order 4727 -- 5-6 UDP-port network-byte order 4729 If the associated trapDestProtocol object is equal to ipx(2), 4730 the encoding of this object is the same as the snmpIPXAddress 4731 textual convention in [RFC1449]: 4732 -- for a SnmpIPXAddress of length 12: 4733 -- 4734 -- octets contents encoding 4735 -- 1-4 network-number network-byte order 4736 -- 5-10 physical-address network-byte order 4737 -- 11-12 socket-number network-byte order 4739 This object may not be modified if the associated 4740 trapDestStatus object is equal to active(1)." 4741 ::= { trapDestEntry 4 } 4743 trapDestOwner OBJECT-TYPE 4744 SYNTAX OwnerString 4745 MAX-ACCESS read-create 4746 STATUS current 4747 DESCRIPTION 4748 "The entity that configured this entry and is 4749 therefore using the resources assigned to it." 4750 ::= { trapDestEntry 5 } 4752 trapDestStatus OBJECT-TYPE 4753 SYNTAX RowStatus 4754 MAX-ACCESS read-create 4755 STATUS current 4756 DESCRIPTION 4757 "The status of this trap destination entry. 4759 An entry may not exist in the active state unless all 4760 objects in the entry have an appropriate value." 4761 ::= { trapDestEntry 6 } 4763 -- Serial Connection Table 4764 -- 4765 -- The device may communicate with a management station using 4766 -- SLIP. In order for the device to send traps via SLIP, it must 4767 -- be able to initiate a connection over the serial interface. The 4768 -- serialConnectionTable stores the parameters for such connection 4769 -- initiation. 4771 serialConnectionTable OBJECT-TYPE 4772 SYNTAX SEQUENCE OF SerialConnectionEntry 4773 MAX-ACCESS not-accessible 4774 STATUS current 4775 DESCRIPTION 4776 "A list of serialConnectionEntries." 4777 ::= { probeConfig 15 } 4779 serialConnectionEntry OBJECT-TYPE 4780 SYNTAX SerialConnectionEntry 4781 MAX-ACCESS not-accessible 4782 STATUS current 4783 DESCRIPTION 4784 "Configuration for a SLIP link over a serial line." 4785 INDEX { serialConnectIndex } 4786 ::= { serialConnectionTable 1 } 4788 SerialConnectionEntry ::= SEQUENCE { 4789 serialConnectIndex Integer32, 4790 serialConnectDestIpAddress IpAddress, 4791 serialConnectType INTEGER, 4792 serialConnectDialString ControlString, 4793 serialConnectSwitchConnectSeq ControlString, 4794 serialConnectSwitchDisconnectSeq ControlString, 4795 serialConnectSwitchResetSeq ControlString, 4796 serialConnectOwner OwnerString, 4797 serialConnectStatus RowStatus 4798 } 4800 serialConnectIndex OBJECT-TYPE 4801 SYNTAX Integer32 (1..65535) 4802 MAX-ACCESS not-accessible 4803 STATUS current 4804 DESCRIPTION 4805 "A value that uniquely identifies this serialConnection 4806 entry." 4807 ::= { serialConnectionEntry 1 } 4809 serialConnectDestIpAddress OBJECT-TYPE 4810 SYNTAX IpAddress 4811 MAX-ACCESS read-create 4812 STATUS current 4813 DESCRIPTION 4814 "The IP Address that can be reached at the other end of this 4815 serial connection. 4816 This object may not be modified if the associated 4817 serialConnectStatus object is equal to active(1)." 4818 ::= { serialConnectionEntry 2 } 4820 serialConnectType OBJECT-TYPE 4821 SYNTAX INTEGER { 4822 direct(1), 4823 modem(2), 4824 switch(3), 4825 modemSwitch(4) 4826 } 4827 MAX-ACCESS read-create 4828 STATUS current 4829 DESCRIPTION 4830 "The type of outgoing connection to make. If this object 4831 has the value direct(1), then a direct serial connection 4832 is assumed. If this object has the value modem(2), 4833 then serialConnectDialString will be used to make a modem 4834 connection. If this object has the value switch(3), 4835 then serialConnectSwitchConnectSeq will be used to establish 4836 the connection over a serial data switch, and 4837 serialConnectSwitchDisconnectSeq will be used to terminate 4838 the connection. If this object has the value 4839 modem-switch(4), then a modem connection will be made first 4840 followed by the switch connection. 4842 This object may not be modified if the associated 4843 serialConnectStatus object is equal to active(1)." 4844 DEFVAL { direct } 4845 ::= { serialConnectionEntry 3 } 4847 serialConnectDialString OBJECT-TYPE 4848 SYNTAX ControlString (SIZE(0..255)) 4849 MAX-ACCESS read-create 4850 STATUS current 4851 DESCRIPTION 4852 "A control string which specifies how to dial the phone 4853 number in order to establish a modem connection. The 4854 string should include dialing prefix and suffix. For 4855 example: ``^s^MATD9,888-1234^M'' will instruct the Probe 4856 to send a carriage return followed by the dialing prefix 4857 ``ATD'', the phone number ``9,888-1234'', and a carriage 4858 return as the dialing suffix. 4859 This object may not be modified if the associated 4860 serialConnectStatus object is equal to active(1)." 4861 ::= { serialConnectionEntry 4 } 4863 serialConnectSwitchConnectSeq OBJECT-TYPE 4864 SYNTAX ControlString (SIZE(0..255)) 4865 MAX-ACCESS read-create 4866 STATUS current 4867 DESCRIPTION 4868 "A control string which specifies how to establish a 4869 data switch connection. 4870 This object may not be modified if the associated 4871 serialConnectStatus object is equal to active(1)." 4872 ::= { serialConnectionEntry 5 } 4874 serialConnectSwitchDisconnectSeq OBJECT-TYPE 4875 SYNTAX ControlString (SIZE(0..255)) 4876 MAX-ACCESS read-create 4877 STATUS current 4878 DESCRIPTION 4879 "A control string which specifies how to terminate a 4880 data switch connection. 4881 This object may not be modified if the associated 4882 serialConnectStatus object is equal to active(1)." 4883 ::= { serialConnectionEntry 6 } 4885 serialConnectSwitchResetSeq OBJECT-TYPE 4886 SYNTAX ControlString (SIZE(0..255)) 4887 MAX-ACCESS read-create 4888 STATUS current 4889 DESCRIPTION 4890 "A control string which specifies how to reset a data 4891 switch in the event of a timeout. 4892 This object may not be modified if the associated 4893 serialConnectStatus object is equal to active(1)." 4894 ::= { serialConnectionEntry 7 } 4896 serialConnectOwner OBJECT-TYPE 4897 SYNTAX OwnerString 4898 MAX-ACCESS read-create 4899 STATUS current 4900 DESCRIPTION 4901 "The entity that configured this entry and is 4902 therefore using the resources assigned to it." 4903 ::= { serialConnectionEntry 8 } 4905 serialConnectStatus OBJECT-TYPE 4906 SYNTAX RowStatus 4907 MAX-ACCESS read-create 4908 STATUS current 4909 DESCRIPTION 4910 "The status of this serialConnectionEntry. 4912 If the manager attempts to set this object to active(1) when 4913 the serialConnectType is set to modem(2) or modem-switch(4) 4914 and the serialConnectDialString is a zero-length string or 4915 cannot be correctly parsed as a ConnectString, the set 4916 request will be rejected with badValue(3). 4918 If the manager attempts to set this object to active(1) when 4919 the serialConnectType is set to switch(3) or modem-switch(4) 4920 and the serialConnectSwitchConnectSeq, 4921 the serialConnectSwitchDisconnectSeq, or 4922 the serialConnectSwitchResetSeq are zero-length strings 4923 or cannot be correctly parsed as ConnectStrings, the set 4924 request will be rejected with badValue(3). 4926 An entry may not exist in the active state unless all 4927 objects in the entry have an appropriate value." 4928 ::= { serialConnectionEntry 9 } 4930 -- 4931 -- Extensions to the RMON 1 MIB for RMON 2 devices 4932 -- 4933 -- These extensions include the standard LastCreateTime Textual 4934 -- Convention for all control tables, as well as an augmentation of 4935 -- the filter entry that provides variable-length offsets into 4936 -- packets. 4938 -- Each of the following, except for filterDroppedFrames, is a 4939 -- read-only object which, if implemented, automatically appears when 4940 -- the RMON1 row it is associated with is created. 4942 etherStats2Table OBJECT-TYPE 4943 SYNTAX SEQUENCE OF EtherStats2Entry 4944 MAX-ACCESS not-accessible 4945 STATUS current 4946 DESCRIPTION 4947 "Contains the RMON-2 augmentations to RMON-1." 4948 ::= { statistics 4 } 4950 etherStats2Entry OBJECT-TYPE 4951 SYNTAX EtherStats2Entry 4952 MAX-ACCESS not-accessible 4953 STATUS current 4954 DESCRIPTION 4955 "Contains the RMON-2 augmentations to RMON-1." 4956 AUGMENTS { etherStatsEntry } 4957 ::= { etherStats2Table 1 } 4959 EtherStats2Entry ::= SEQUENCE { 4960 etherStatsDroppedFrames Counter32, 4961 etherStatsCreateTime LastCreateTime 4962 } 4964 etherStatsDroppedFrames OBJECT-TYPE 4965 SYNTAX Counter32 4966 MAX-ACCESS read-only 4967 STATUS current 4968 DESCRIPTION 4969 "The total number of frames which were received by the probe 4970 and therefore not accounted for in the *StatsDropEvents, but 4971 for which the probe chose not to count for this entry for 4972 whatever reason. Most often, this event occurs when the probe 4973 is out of some resources and decides to shed load from this 4974 collection. 4976 This count does not include packets that were not counted 4977 because they had MAC-layer errors. 4979 Note that, unlike the dropEvents counter, this number is the 4980 exact number of frames dropped." 4981 ::= { etherStats2Entry 1 } 4983 etherStatsCreateTime OBJECT-TYPE 4984 SYNTAX LastCreateTime 4985 MAX-ACCESS read-only 4986 STATUS current 4987 DESCRIPTION 4988 "The value of sysUpTime when this control entry was activated. 4989 This can be used by the management station to ensure that the 4990 table has not been deleted and recreated between polls." 4991 ::= { etherStats2Entry 2 } 4993 historyControl2Table OBJECT-TYPE 4994 SYNTAX SEQUENCE OF HistoryControl2Entry 4995 MAX-ACCESS not-accessible 4996 STATUS current 4997 DESCRIPTION 4998 "Contains the RMON-2 augmentations to RMON-1." 5000 ::= { history 5 } 5002 historyControl2Entry OBJECT-TYPE 5003 SYNTAX HistoryControl2Entry 5004 MAX-ACCESS not-accessible 5005 STATUS current 5006 DESCRIPTION 5007 "Contains the RMON-2 augmentations to RMON-1." 5008 AUGMENTS { historyControlEntry } 5009 ::= { historyControl2Table 1 } 5011 HistoryControl2Entry ::= SEQUENCE { 5012 historyControlDroppedFrames Counter32 5013 } 5015 historyControlDroppedFrames OBJECT-TYPE 5016 SYNTAX Counter32 5017 MAX-ACCESS read-only 5018 STATUS current 5019 DESCRIPTION 5020 "The total number of frames which were received by the probe 5021 and therefore not accounted for in the *StatsDropEvents, but 5022 for which the probe chose not to count for this entry for 5023 whatever reason. Most often, this event occurs when the probe 5024 is out of some resources and decides to shed load from this 5025 collection. 5027 This count does not include packets that were not counted 5028 because they had MAC-layer errors. 5030 Note that, unlike the dropEvents counter, this number is the 5031 exact number of frames dropped." 5032 ::= { historyControl2Entry 1 } 5034 hostControl2Table OBJECT-TYPE 5035 SYNTAX SEQUENCE OF HostControl2Entry 5036 MAX-ACCESS not-accessible 5037 STATUS current 5038 DESCRIPTION 5039 "Contains the RMON-2 augmentations to RMON-1." 5040 ::= { hosts 4 } 5042 hostControl2Entry OBJECT-TYPE 5043 SYNTAX HostControl2Entry 5044 MAX-ACCESS not-accessible 5045 STATUS current 5046 DESCRIPTION 5047 "Contains the RMON-2 augmentations to RMON-1." 5048 AUGMENTS { hostControlEntry } 5049 ::= { hostControl2Table 1 } 5051 HostControl2Entry ::= SEQUENCE { 5052 hostControlDroppedFrames Counter32, 5053 hostControlCreateTime LastCreateTime 5054 } 5056 hostControlDroppedFrames OBJECT-TYPE 5057 SYNTAX Counter32 5058 MAX-ACCESS read-only 5059 STATUS current 5060 DESCRIPTION 5061 "The total number of frames which were received by the probe 5062 and therefore not accounted for in the *StatsDropEvents, but 5063 for which the probe chose not to count for this entry for 5064 whatever reason. Most often, this event occurs when the probe 5065 is out of some resources and decides to shed load from this 5066 collection. 5068 This count does not include packets that were not counted 5069 because they had MAC-layer errors. 5071 Note that, unlike the dropEvents counter, this number is the 5072 exact number of frames dropped." 5073 ::= { hostControl2Entry 1 } 5075 hostControlCreateTime OBJECT-TYPE 5076 SYNTAX LastCreateTime 5077 MAX-ACCESS read-only 5078 STATUS current 5079 DESCRIPTION 5080 "The value of sysUpTime when this control entry was activated. 5081 This can be used by the management station to ensure that the 5082 table has not been deleted and recreated between polls." 5083 ::= { hostControl2Entry 2 } 5085 matrixControl2Table OBJECT-TYPE 5086 SYNTAX SEQUENCE OF MatrixControl2Entry 5087 MAX-ACCESS not-accessible 5088 STATUS current 5089 DESCRIPTION 5090 "Contains the RMON-2 augmentations to RMON-1." 5091 ::= { matrix 4 } 5093 matrixControl2Entry OBJECT-TYPE 5094 SYNTAX MatrixControl2Entry 5095 MAX-ACCESS not-accessible 5096 STATUS current 5097 DESCRIPTION 5098 "Contains the RMON-2 augmentations to RMON-1." 5099 AUGMENTS { matrixControlEntry } 5100 ::= { matrixControl2Table 1 } 5102 MatrixControl2Entry ::= SEQUENCE { 5103 matrixControlDroppedFrames Counter32, 5104 matrixControlCreateTime LastCreateTime 5105 } 5107 matrixControlDroppedFrames OBJECT-TYPE 5108 SYNTAX Counter32 5109 MAX-ACCESS read-only 5110 STATUS current 5111 DESCRIPTION 5112 "The total number of frames which were received by the probe 5113 and therefore not accounted for in the *StatsDropEvents, but 5114 for which the probe chose not to count for this entry for 5115 whatever reason. Most often, this event occurs when the probe 5116 is out of some resources and decides to shed load from this 5117 collection. 5119 This count does not include packets that were not counted 5120 because they had MAC-layer errors. 5122 Note that, unlike the dropEvents counter, this number is the 5123 exact number of frames dropped." 5124 ::= { matrixControl2Entry 1 } 5126 matrixControlCreateTime OBJECT-TYPE 5127 SYNTAX LastCreateTime 5128 MAX-ACCESS read-only 5129 STATUS current 5130 DESCRIPTION 5131 "The value of sysUpTime when this control entry was activated. 5132 This can be used by the management station to ensure that the 5133 table has not been deleted and recreated between polls." 5134 ::= { matrixControl2Entry 2 } 5136 -- Associated with *all* filters 5137 filterDroppedFrames OBJECT-TYPE 5138 SYNTAX Counter32 5139 MAX-ACCESS read-only 5140 STATUS current 5141 DESCRIPTION 5142 "The total number of frames which were received by the probe 5143 and therefore not accounted for in the *StatsDropEvents, but 5144 for which the probe chose not to count for this function for 5145 whatever reason. Most often, this event occurs when the probe 5146 is out of some resources and decides to shed load from this 5147 collection. 5149 This count does not include packets that were not counted 5150 because they had MAC-layer errors. 5152 Note that, unlike the dropEvents counter, this number is the 5153 exact number of frames dropped." 5154 ::= { filter 3 } 5156 channel2Table OBJECT-TYPE 5157 SYNTAX SEQUENCE OF Channel2Entry 5158 MAX-ACCESS not-accessible 5159 STATUS current 5160 DESCRIPTION 5161 "Contains the RMON-2 augmentations to RMON-1." 5162 ::= { filter 4 } 5164 channel2Entry OBJECT-TYPE 5165 SYNTAX Channel2Entry 5166 MAX-ACCESS not-accessible 5167 STATUS current 5168 DESCRIPTION 5169 "Contains the RMON-2 augmentations to RMON-1." 5170 AUGMENTS { channelEntry } 5171 ::= { channel2Table 1 } 5173 Channel2Entry ::= SEQUENCE { 5174 channelCreateTime LastCreateTime 5175 } 5177 channelCreateTime OBJECT-TYPE 5178 SYNTAX LastCreateTime 5179 MAX-ACCESS read-only 5180 STATUS current 5181 DESCRIPTION 5182 "The value of sysUpTime when this control entry was activated. 5183 This can be used by the management station to ensure that the 5184 table has not been deleted and recreated between polls." 5185 ::= { channel2Entry 1 } 5187 tokenRingMLStats2Table OBJECT-TYPE 5188 SYNTAX SEQUENCE OF TokenRingMLStats2Entry 5189 MAX-ACCESS not-accessible 5190 STATUS current 5191 DESCRIPTION 5192 "Contains the RMON-2 augmentations to RMON-1." 5193 ::= { statistics 5 } 5195 tokenRingMLStats2Entry OBJECT-TYPE 5196 SYNTAX TokenRingMLStats2Entry 5197 MAX-ACCESS not-accessible 5198 STATUS current 5199 DESCRIPTION 5200 "Contains the RMON-2 augmentations to RMON-1." 5201 AUGMENTS { tokenRingMLStatsEntry } 5202 ::= { tokenRingMLStats2Table 1 } 5204 TokenRingMLStats2Entry ::= SEQUENCE { 5205 tokenRingMLStatsDroppedFrames Counter32, 5206 tokenRingMLStatsCreateTime LastCreateTime 5207 } 5209 tokenRingMLStatsDroppedFrames OBJECT-TYPE 5210 SYNTAX Counter32 5211 MAX-ACCESS read-only 5212 STATUS current 5213 DESCRIPTION 5214 "The total number of frames which were received by the probe 5215 and therefore not accounted for in the *StatsDropEvents, but 5216 for which the probe chose not to count for this entry for 5217 whatever reason. Most often, this event occurs when the probe 5218 is out of some resources and decides to shed load from this 5219 collection. 5221 This count does not include packets that were not counted 5222 because they had MAC-layer errors. 5224 Note that, unlike the dropEvents counter, this number is the 5225 exact number of frames dropped." 5227 ::= { tokenRingMLStats2Entry 1 } 5229 tokenRingMLStatsCreateTime OBJECT-TYPE 5230 SYNTAX LastCreateTime 5231 MAX-ACCESS read-only 5232 STATUS current 5233 DESCRIPTION 5234 "The value of sysUpTime when this control entry was activated. 5235 This can be used by the management station to ensure that the 5236 table has not been deleted and recreated between polls." 5237 ::= { tokenRingMLStats2Entry 2 } 5239 tokenRingPStats2Table OBJECT-TYPE 5240 SYNTAX SEQUENCE OF TokenRingPStats2Entry 5241 MAX-ACCESS not-accessible 5242 STATUS current 5243 DESCRIPTION 5244 "Contains the RMON-2 augmentations to RMON-1." 5245 ::= { statistics 6 } 5247 tokenRingPStats2Entry OBJECT-TYPE 5248 SYNTAX TokenRingPStats2Entry 5249 MAX-ACCESS not-accessible 5250 STATUS current 5251 DESCRIPTION 5252 "Contains the RMON-2 augmentations to RMON-1." 5253 AUGMENTS { tokenRingPStatsEntry } 5254 ::= { tokenRingPStats2Table 1 } 5256 TokenRingPStats2Entry ::= SEQUENCE { 5257 tokenRingPStatsDroppedFrames Counter32, 5258 tokenRingPStatsCreateTime LastCreateTime 5259 } 5261 tokenRingPStatsDroppedFrames OBJECT-TYPE 5262 SYNTAX Counter32 5263 MAX-ACCESS read-only 5264 STATUS current 5265 DESCRIPTION 5266 "The total number of frames which were received by the probe 5267 and therefore not accounted for in the *StatsDropEvents, but 5268 for which the probe chose not to count for this entry for 5269 whatever reason. Most often, this event occurs when the probe 5270 is out of some resources and decides to shed load from this 5271 collection. 5273 This count does not include packets that were not counted 5274 because they had MAC-layer errors. 5276 Note that, unlike the dropEvents counter, this number is the 5277 exact number of frames dropped." 5278 ::= { tokenRingPStats2Entry 1 } 5280 tokenRingPStatsCreateTime OBJECT-TYPE 5281 SYNTAX LastCreateTime 5282 MAX-ACCESS read-only 5283 STATUS current 5284 DESCRIPTION 5285 "The value of sysUpTime when this control entry was activated. 5286 This can be used by the management station to ensure that the 5287 table has not been deleted and recreated between polls." 5288 ::= { tokenRingPStats2Entry 2 } 5290 ringStationControl2Table OBJECT-TYPE 5291 SYNTAX SEQUENCE OF RingStationControl2Entry 5292 MAX-ACCESS not-accessible 5293 STATUS current 5294 DESCRIPTION 5295 "Contains the RMON-2 augmentations to RMON-1." 5296 ::= { tokenRing 7 } 5298 ringStationControl2Entry OBJECT-TYPE 5299 SYNTAX RingStationControl2Entry 5300 MAX-ACCESS not-accessible 5301 STATUS current 5302 DESCRIPTION 5303 "Contains the RMON-2 augmentations to RMON-1." 5304 AUGMENTS { ringStationControlEntry } 5305 ::= { ringStationControl2Table 1 } 5307 RingStationControl2Entry ::= SEQUENCE { 5308 ringStationControlDroppedFrames Counter32, 5309 ringStationControlCreateTime LastCreateTime 5310 } 5312 ringStationControlDroppedFrames OBJECT-TYPE 5313 SYNTAX Counter32 5314 MAX-ACCESS read-only 5315 STATUS current 5316 DESCRIPTION 5317 "The total number of frames which were received by the probe 5318 and therefore not accounted for in the *StatsDropEvents, but 5319 for which the probe chose not to count for this entry for 5320 whatever reason. Most often, this event occurs when the probe 5321 is out of some resources and decides to shed load from this 5322 collection. 5324 This count does not include packets that were not counted 5325 because they had MAC-layer errors. 5327 Note that, unlike the dropEvents counter, this number is the 5328 exact number of frames dropped." 5329 ::= { ringStationControl2Entry 1 } 5331 ringStationControlCreateTime OBJECT-TYPE 5332 SYNTAX LastCreateTime 5333 MAX-ACCESS read-only 5334 STATUS current 5335 DESCRIPTION 5336 "The value of sysUpTime when this control entry was activated. 5337 This can be used by the management station to ensure that the 5338 table has not been deleted and recreated between polls." 5339 ::= { ringStationControl2Entry 2 } 5341 sourceRoutingStats2Table OBJECT-TYPE 5342 SYNTAX SEQUENCE OF SourceRoutingStats2Entry 5343 MAX-ACCESS not-accessible 5344 STATUS current 5345 DESCRIPTION 5346 "Contains the RMON-2 augmentations to RMON-1." 5347 ::= { tokenRing 8 } 5349 sourceRoutingStats2Entry OBJECT-TYPE 5350 SYNTAX SourceRoutingStats2Entry 5351 MAX-ACCESS not-accessible 5352 STATUS current 5353 DESCRIPTION 5354 "Contains the RMON-2 augmentations to RMON-1." 5355 AUGMENTS { sourceRoutingStatsEntry } 5356 ::= { sourceRoutingStats2Table 1 } 5358 SourceRoutingStats2Entry ::= SEQUENCE { 5359 sourceRoutingStatsDroppedFrames Counter32, 5360 sourceRoutingStatsCreateTime LastCreateTime 5361 } 5362 sourceRoutingStatsDroppedFrames OBJECT-TYPE 5363 SYNTAX Counter32 5364 MAX-ACCESS read-only 5365 STATUS current 5366 DESCRIPTION 5367 "The total number of frames which were received by the probe 5368 and therefore not accounted for in the *StatsDropEvents, but 5369 for which the probe chose not to count for this entry for 5370 whatever reason. Most often, this event occurs when the probe 5371 is out of some resources and decides to shed load from this 5372 collection. 5374 This count does not include packets that were not counted 5375 because they had MAC-layer errors. 5377 Note that, unlike the dropEvents counter, this number is the 5378 exact number of frames dropped." 5379 ::= { sourceRoutingStats2Entry 1 } 5381 sourceRoutingStatsCreateTime OBJECT-TYPE 5382 SYNTAX LastCreateTime 5383 MAX-ACCESS read-only 5384 STATUS current 5385 DESCRIPTION 5386 "The value of sysUpTime when this control entry was activated. 5387 This can be used by the management station to ensure that the 5388 table has not been deleted and recreated between polls." 5389 ::= { sourceRoutingStats2Entry 2 } 5391 filter2Table OBJECT-TYPE 5392 SYNTAX SEQUENCE OF Filter2Entry 5393 MAX-ACCESS not-accessible 5394 STATUS current 5395 DESCRIPTION 5396 "Provides a variable-length packet filter feature to the 5397 RMON-1 filter table." 5398 ::= { filter 5 } 5400 filter2Entry OBJECT-TYPE 5401 SYNTAX Filter2Entry 5402 MAX-ACCESS not-accessible 5403 STATUS current 5404 DESCRIPTION 5405 "Provides a variable-length packet filter feature to the 5406 RMON-1 filter table." 5408 AUGMENTS { filterEntry } 5409 ::= { filter2Table 1 } 5411 Filter2Entry ::= SEQUENCE { 5412 filterProtocolDirLocalIndex Integer32 5413 } 5415 filterProtocolDirLocalIndex OBJECT-TYPE 5416 SYNTAX Integer32 (0..2147483647) 5417 MAX-ACCESS read-create 5418 STATUS current 5419 DESCRIPTION 5420 "When this object is set to a non-zero value, the filter that 5421 it is associated with performs the following operations on 5422 every packet: 5424 1) - If the packet doesn't match the protocol directory entry, 5425 discard and exit 5426 2) - If the packet matches, perform the regular filter 5427 algorithm as if the beginning of the named protocol is 5428 the beginning of the packet, potentially applying the 5429 filterOffset value to move further into the packet." 5430 DEFVAL { 0 } 5431 ::= { filter2Entry 1 } 5433 -- Conformance Macros 5435 rmon2MIBCompliances OBJECT IDENTIFIER ::= { rmonConformance 1 } 5436 rmon2MIBGroups OBJECT IDENTIFIER ::= { rmonConformance 2 } 5438 rmon2MIBCompliance MODULE-COMPLIANCE 5439 STATUS current 5440 DESCRIPTION 5441 "Describes the requirements for conformance to 5442 the RMON2 MIB" 5443 MODULE -- this module 5444 MANDATORY-GROUPS { protocolDirectoryGroup, 5445 protocolDistributionGroup, 5446 addressMapGroup, 5447 nlHostGroup, 5448 nlMatrixGroup, 5449 usrHistoryGroup, 5450 probeConfigurationGroup, 5451 rmon1EnhancementGroup } 5453 ::= { rmon2MIBCompliances 1 } 5455 rmon2MIBApplicationLayerCompliance MODULE-COMPLIANCE 5456 STATUS current 5457 DESCRIPTION 5458 "Describes the requirements for conformance to 5459 the RMON2 MIB with Application Layer Enhancements." 5460 MODULE -- this module 5461 MANDATORY-GROUPS { protocolDirectoryGroup, 5462 protocolDistributionGroup, 5463 addressMapGroup, 5464 nlHostGroup, 5465 nlMatrixGroup, 5466 alHostGroup, 5467 alMatrixGroup, 5468 usrHistoryGroup, 5469 probeConfigurationGroup, 5470 rmon1EnhancementGroup } 5471 ::= { rmon2MIBCompliances 2 } 5473 protocolDirectoryGroup OBJECT-GROUP 5474 OBJECTS { protocolDirLocalIndex, protocolDirDescr, 5475 protocolDirType, protocolDirAddressMapConfig, 5476 protocolDirHostConfig, protocolDirMatrixConfig, 5477 protocolDirOwner, protocolDirStatus } 5478 STATUS current 5479 DESCRIPTION 5480 "Lists the inventory of protocols the probe has the capability 5481 of monitoring and allows the addition, deletion, and 5482 configuration of entries in this list." 5483 ::= { rmon2MIBGroups 1 } 5485 protocolDistributionGroup OBJECT-GROUP 5486 OBJECTS { protocolDistControlDataSource, 5487 protocolDistControlDroppedFrames, 5488 protocolDistControlCreateTime, 5489 protocolDistControlOwner, protocolDistControlStatus, 5490 protocolDistStatsPkts, protocolDistStatsOctets } 5491 STATUS current 5492 DESCRIPTION 5493 "Collects the relative amounts of octets and packets for the 5494 different protocols detected on a network segment." 5495 ::= { rmon2MIBGroups 2 } 5497 addressMapGroup OBJECT-GROUP 5498 OBJECTS { addressMapInserts, addressMapDeletes, 5499 addressMapMaxDesiredEntries, 5500 addressMapControlDataSource, 5501 addressMapControlDroppedFrames, 5502 addressMapControlOwner, addressMapControlStatus, 5503 addressMapSource, addressMapPhysicalAddress, 5504 addressMapLastChange } 5505 STATUS current 5506 DESCRIPTION 5507 "Lists MAC address to network address bindings discovered by 5508 the probe and what interface they were last seen on." 5509 ::= { rmon2MIBGroups 3 } 5511 nlHostGroup OBJECT-GROUP 5512 OBJECTS { hlHostControlDataSource, 5513 hlHostControlNlDroppedFrames, hlHostControlNlInserts, 5514 hlHostControlNlDeletes, 5515 hlHostControlNlMaxDesiredEntries, 5516 hlHostControlAlDroppedFrames, hlHostControlAlInserts, 5517 hlHostControlAlDeletes, 5518 hlHostControlAlMaxDesiredEntries, hlHostControlOwner, 5519 hlHostControlStatus, nlHostInPkts, nlHostOutPkts, 5520 nlHostInOctets, nlHostOutOctets, 5521 nlHostOutMacNonUnicastPkts, nlHostCreateTime } 5522 STATUS current 5523 DESCRIPTION 5524 "Counts the amount of traffic sent from and to each network 5525 address discovered by the probe. Note that while the 5526 hlHostControlTable also has objects that control an optional 5527 alHostTable, implementation of the alHostTable is not required 5528 to fully implement this group." 5529 ::= { rmon2MIBGroups 4 } 5531 nlMatrixGroup OBJECT-GROUP 5532 OBJECTS { hlMatrixControlDataSource, 5533 hlMatrixControlNlDroppedFrames, 5534 hlMatrixControlNlInserts, hlMatrixControlNlDeletes, 5535 hlMatrixControlNlMaxDesiredEntries, 5536 hlMatrixControlAlDroppedFrames, 5537 hlMatrixControlAlInserts, hlMatrixControlAlDeletes, 5538 hlMatrixControlAlMaxDesiredEntries, 5539 hlMatrixControlOwner, hlMatrixControlStatus, 5540 nlMatrixSDPkts, nlMatrixSDOctets, nlMatrixSDCreateTime, 5541 nlMatrixDSPkts, nlMatrixDSOctets, nlMatrixDSCreateTime, 5542 nlMatrixTopNControlIndex, nlMatrixTopNMatrixIndex, 5543 nlMatrixTopNRateBase, nlMatrixTopNTimeRemaining, 5544 nlMatrixTopNGeneratedReports, nlMatrixTopNDuration, 5545 nlMatrixTopNRequestedSize, nlMatrixTopNGrantedSize, 5546 nlMatrixTopNStartTime, nlMatrixTopNOwner, 5547 nlMatrixTopNStatus, nlMatrixTopNIndex, 5548 nlMatrixTopNProtocolDirLocalIndex, 5549 nlMatrixTopNSourceAddress, nlMatrixTopNDestAddress, 5550 nlMatrixTopNPktRate, nlMatrixTopNReversePktRate, 5551 nlMatrixTopNOctetRate, nlMatrixTopNReverseOctetRate } 5552 STATUS current 5553 DESCRIPTION 5554 "Counts the amount of traffic sent between each pair of 5555 network addresses discovered by the probe. Note that while the 5556 hlMatrixControlTable also has objects that control optional 5557 alMatrixTables, implementation of the alMatrixTables is not 5558 required to fully implement this group." 5559 ::= { rmon2MIBGroups 5 } 5561 alHostGroup OBJECT-GROUP 5562 OBJECTS { alHostInPkts, alHostOutPkts, 5563 alHostInOctets, alHostOutOctets, alHostCreateTime } 5564 STATUS current 5565 DESCRIPTION 5566 "Counts the amount of traffic, by protocol, sent from and to 5567 each network address discovered by the probe. Implementation 5568 of this group requires implementation of the Network Layer 5569 Host Group." 5570 ::= { rmon2MIBGroups 6 } 5572 alMatrixGroup OBJECT-GROUP 5573 OBJECTS { alMatrixSDPkts, alMatrixSDOctets, alMatrixSDCreateTime, 5574 alMatrixDSPkts, alMatrixDSOctets, alMatrixDSCreateTime, 5575 alMatrixTopNControlIndex, alMatrixTopNMatrixIndex, 5576 alMatrixTopNRateBase, alMatrixTopNTimeRemaining, 5577 alMatrixTopNGeneratedReports, alMatrixTopNDuration, 5578 alMatrixTopNRequestedSize, alMatrixTopNGrantedSize, 5579 alMatrixTopNStartTime, alMatrixTopNOwner, 5580 alMatrixTopNStatus, alMatrixTopNIndex, 5581 alMatrixTopNProtocolDirLocalIndex, 5582 alMatrixTopNSourceAddress, alMatrixTopNDestAddress, 5583 alMatrixTopNAppProtocolDirLocalIndex, 5584 alMatrixTopNPktRate, alMatrixTopNReversePktRate, 5585 alMatrixTopNOctetRate, alMatrixTopNReverseOctetRate } 5586 STATUS current 5587 DESCRIPTION 5588 "Counts the amount of traffic, by protocol, sent between each 5589 pair of network addresses discovered by the 5590 probe. Implementation of this group requires implementation of 5591 the Network Layer Matrix Group." 5592 ::= { rmon2MIBGroups 7 } 5594 usrHistoryGroup OBJECT-GROUP 5595 OBJECTS { usrHistoryControlObjects, 5596 usrHistoryControlBucketsRequested, 5597 usrHistoryControlBucketsGranted, 5598 usrHistoryControlInterval, 5599 usrHistoryControlOwner, usrHistoryControlStatus, 5600 usrHistoryObjectVariable, usrHistoryObjectSampleType, 5601 usrHistoryIntervalStart, usrHistoryIntervalEnd, 5602 usrHistoryAbsValue, usrHistoryValStatus } 5603 STATUS current 5604 DESCRIPTION 5605 "The usrHistoryGroup provides user-defined collection of 5606 historical information from MIB objects on the probe." 5607 ::= { rmon2MIBGroups 8 } 5609 probeConfigurationGroup OBJECT-GROUP 5610 OBJECTS { probeCapabilities, probeIdentification, 5611 probeSoftwareRev, probeHardwareRev, probeDateTime, 5612 probeResetControl, probeDownloadFile, 5613 probeDownloadTFTPServer, probeDownloadAction, 5614 probeDownloadStatus, 5615 serialIpAddress, serialSubnetMask, serialMode, 5616 serialProtocol, serialSpeed, serialTimeout, 5617 serialModemInitString, serialModemHangUpString, 5618 serialModemConnectResp, serialModemNoConnectResp, 5619 serialFlowControl, serialDialoutTimeout, serialStatus, 5620 netConfigIPAddress, netConfigSubnetMask, 5621 netConfigStatus, netDefaultGateway, 5622 trapDestCommunity, trapDestProtocol, trapDestAddress, 5623 trapDestOwner, trapDestStatus, 5624 serialConnectDestIpAddress, serialConnectType, 5625 serialConnectDialString, serialConnectSwitchConnectSeq, 5626 serialConnectSwitchDisconnectSeq, 5627 serialConnectSwitchResetSeq, 5628 serialConnectOwner, serialConnectStatus } 5629 STATUS current 5630 DESCRIPTION 5631 "This group controls the configuration of various operating 5632 parameters of the probe." 5633 ::= { rmon2MIBGroups 9 } 5635 rmon1EnhancementGroup OBJECT-GROUP 5636 OBJECTS { historyControlDroppedFrames, hostControlDroppedFrames, 5637 hostControlCreateTime, matrixControlDroppedFrames, 5638 matrixControlCreateTime, filterDroppedFrames, 5639 channelCreateTime, filterProtocolDirLocalIndex } 5640 STATUS current 5641 DESCRIPTION 5642 "This group adds some enhancements to RMON-1 that help 5643 management stations." 5644 ::= { rmon2MIBGroups 10 } 5646 rmon1EnternetEnhancementGroup OBJECT-GROUP 5647 OBJECTS { etherStatsDroppedFrames, etherStatsCreateTime } 5648 STATUS current 5649 DESCRIPTION 5650 "This group adds some enhancements to RMON-1 that help 5651 management stations." 5652 ::= { rmon2MIBGroups 11 } 5654 rmon1TokenRingEnhancementGroup OBJECT-GROUP 5655 OBJECTS { tokenRingMLStatsDroppedFrames, 5656 tokenRingMLStatsCreateTime, 5657 tokenRingPStatsDroppedFrames, tokenRingPStatsCreateTime, 5658 ringStationControlDroppedFrames, 5659 ringStationControlCreateTime, 5660 sourceRoutingStatsDroppedFrames, 5661 sourceRoutingStatsCreateTime } 5662 STATUS current 5663 DESCRIPTION 5664 "This group adds some enhancements to RMON-1 that help 5665 management stations." 5666 ::= { rmon2MIBGroups 12 } 5667 END 5668 9. Acknowledgments 5670 This document was produced by the IETF Remote Network 5671 Monitoring Working Group. 5673 10. References 5675 [1] V. Cerf, IAB Recommendations for the Development of 5676 Internet Network Management Standards. Internet Working 5677 Group Request for Comments 1052. Network Information 5678 Center, SRI International, Menlo Park, California, 5679 (April, 1988). 5681 [2] V. Cerf, Report of the Second Ad Hoc Network Management 5682 Review Group, Internet Working Group Request for Comments 5683 1109. Network Information Center, SRI International, 5684 Menlo Park, California, (August, 1989). 5686 [3] M.T. Rose and K. McCloghrie, Structure and Identification 5687 of Management Information for TCP/IP-based internets, 5688 Internet Working Group Request for Comments 1155. 5689 Network Information Center, SRI International, Menlo 5690 Park, California, (May, 1990). 5692 [4] K. McCloghrie and M.T. Rose, Management Information Base 5693 for Network Management of TCP/IP-based internets: MIB-II, 5694 Internet Working Group Request for Comments 1213 Network 5695 Information Center, SRI International, Menlo Park, 5696 California, (March, 1991). 5698 [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, 5699 Simple Network Management Protocol, Internet Working 5700 Group Request for Comments 1157. Network Information 5701 Center, SRI International, Menlo Park, California, (May, 5702 1990). 5704 [6] K. McCloghrie and F. Kastenholz, Evolution of the 5705 Interfaces Group of MIB-II, Internet Working Group 5706 Request for Comments 1573. Network Information Center, 5707 SRI International, Menlo Park, California, (Jan, 1994). 5709 [7] Information processing systems -- Open Systems 5710 Interconnection -- Specification of Abstract Syntax 5711 Notation One (ASN.1), International Organization for 5712 Standardization. International Standard 8824, (December, 5713 1987). 5715 [8] Information processing systems -- Open Systems 5716 Interconnection -- Specification of Basic Encoding Rules 5717 for Abstract Notation One (ASN.1), International 5718 Organization for Standardization. International Standard 5719 8825, (December, 1987). 5721 [9] M.T. Rose, K. McCloghrie, Editors, Concise MIB 5722 Definitions, Internet Working Group Request for Comments 5723 1212. Network Information Center, SRI International, 5724 Menlo Park, California, (March, 1991). 5726 [10] M.T. Rose, Editor, A Convention for Defining Traps for 5727 use with the SNMP, Internet Working Group Request for 5728 Comments 1215. Network Information Center, SRI 5729 International, Menlo Park, California, (March, 1991). 5731 Table of Contents 5733 1 Status of this Memo ................................... 1 5734 2 Abstract .............................................. 1 5735 3 The Network Management Framework ...................... 3 5736 4 Overview .............................................. 4 5737 4.1 Remote Network Management Goals ..................... 4 5738 4.2 Structure of MIB .................................... 6 5739 5 Control of Remote Network Monitoring Devices .......... 7 5740 5.1 Resource Sharing Among Multiple Management Sta- 5741 tions .............................................. 7 5742 5.2 Row Addition Among Multiple Management Stations ..... 9 5743 6 Conventions ........................................... 11 5744 7 RMON 2 Conventions .................................... 12 5745 7.1 Usage of the term Application Level ................. 12 5746 7.2 Protocol Directory and Limited Extensibility ........ 12 5747 7.3 Errors in packets ................................... 13 5748 8 Definitions ........................................... 13 5749 9 Acknowledgments ....................................... 131 5750 10 References ........................................... 132