idnits 2.17.1 draft-hazewinkel-ismib-00.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-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 8) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 2 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** There are 788 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 128 has weird spacing: '... of the syste...' -- 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 (April 22, 1996) is 10230 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) == Unused Reference: '3' is defined on line 1207, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1211, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 1215, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 1219, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1223, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '3') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1904 (ref. '5') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '6') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '7') Summary: 17 errors (**), 0 flaws (~~), 8 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Draft Information Store MIB April 22,1996 3 Definitions of Managed Objects for an Information Store 5 April 22, 1996 7 9 Harrie Hazewinkel 10 University of Twente 11 hazewink@cs.utwente.nl 13 Eric van Hengstum 14 University of Twente 15 hengstum@cs.utwente.nl 17 Aiko Pras 18 University of Twente 19 pras@cs.utwente.nl 21 Status of this Memo 23 This document is an Internet-Draft. Internet-Drafts are working 24 documents of the Internet Engineering Task Force (IETF), its 25 areas, and its working groups. Note that other groups may also 26 distribute working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six 29 months and may be updated, replaced, or obsoleted by other 30 documents at any time. It is inappropriate to use Internet- 31 Drafts as reference material or to cite them other than as ``work 32 in progress.'' 34 To learn the current status of any Internet-Draft, please check 35 the ``1id-abstracts.txt'' listing contained in the Internet- 36 Drafts Shadow Directories on ds.internic.net (US East Coast), 37 nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or 38 munnari.oz.au (Pacific Rim). 40 1. Abstract 42 This draft defines a MIB for use with managing information stores. 43 The term "information store" is construed to mean any information 44 providing application, such as World Wide Web (WWW), File Transfer 45 Protocol (FTP), and Gopher. The information store is seen as the 46 application responsible for the information providing capabilities. 48 2. The SNMPv2 Network Management Framework 50 The SNMPv2 Network Management Framework consists of four major 51 components. They are: 53 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 54 objects for the Internet suite of protocols. 56 o RFC 1901 Introduction to Community-based SNMPv2 58 o RFC 1902 Structure of Management Information for Version 2 of 59 the Simple Network Management Protocol (SNMPv2) 61 o RFC 1903 Textual Conventions for Version 2 of the Simple 62 Network Management Protocol (SNMPv2) 64 o RFC 1904 Conformance Statements for Version 2 of the Simple 65 Network Management Protocol (SNMPv2) 67 o RFC 1907 Management Information Base for Version 2 of the 68 Simple Network Management Protocol (SNMPv2) 70 o RFC 1908 Coexistence between Version 1 and Version 2 of the 71 Internet-standard Network Management Framework 73 The Framework permits new objects to be defined for the purpose of 74 experimentation and evaluation. 76 2.1. Object Definitions 78 Managed objects are accessed via a virtual information store, 79 termed the Management Information Base or MIB. Objects in the MIB 80 are defined using the subset of Abstract Syntax Notation One 81 (ASN.1) defined in the SMI[1]. In particular, each object type is 82 named by an OBJECT IDENTIFIER, an administratively assigned name. 83 The object type together with an object instance serves to 84 uniquely identify a specific instantiation of the object. For 85 human convenience, we often use a textual string, termed the 86 object descriptor, to refer to the object type. 88 3. Introduction. 90 The Information Store represents the information part of a World Wide 91 Web application. The name Information Store (IS) is strongly related 92 to the use of this part of the WWW application. Most WWW servers provide 93 information to users / customers (clients) of the WWW application. In 94 order to maintain and manage the provided information a specific MIB 95 module is defined. The Information Store MIB module specifies the 96 network management information of the WWW server, providing the 97 aforementioned information. 99 The work performed for this MIB is a result of a project executed 100 for the Centre of Earth Observations. It is not seen as complete, 101 but it should be a first step in an effort to manage the WWW. An 102 implementation of this MIB already exists. Due to the use of a 103 commercial development package it cannot be distributed. However, 104 a public domain version is now being developed. 106 4. Information Store MIB structure. 108 The Information Store MIB module structure contains the 109 following groups: 110 1. isGeneral, 111 2. isAccess, 112 3. isErrors, and 113 4. isDocuments. 115 4.1 General Group 117 The isGeneral group contains overall administrative data which 118 uniquely identifies the IS, and should be static for the Information 119 Store (IS). The network management information consists of the 120 administrative data uniquely identifying the IS. In addition to the 121 static data, such as the isContact object (a contact address for the 122 person responsible for the information provided by the IS), the 123 isGeneral group also contains the isTopicTable. The NMS user can use 124 this table to discover what kinds of information are provided by 125 the IS. It was originally intended to include an isLocation variable 126 in this group. This variable would have provided information on the 127 location of the IS, however, as this information is also contained 128 in the sysLocation of the system group it was omitted. 130 The general group contains also information of applications on which 131 the IS depends (such as database applications for search facilities). 132 The application dependency table provides that information. The 133 status of these applications is checked dynamically and the values 134 are related to the `process status' command of the UNIX environment. 136 4.2 Access group 138 The access group contains network management information about the 139 network activity of the Information Store. The network activity is 140 described in an abstract manner in regard to the service which 141 transports the information. 143 This group provides network management information with the 144 following points of view: 145 1. general data containing totals for the information store, 146 2. domain data containing totals ordered by domains, 147 3. daily access data which contains totals for the last N days, 148 4. user data which contains information concerning the most 149 frequent and most recent users. 151 The general access data provides statistics relating to usage of 152 the IS. For example, the variables number of accesses 153 (isNumberOfAccesses) and the number of bytes in/ out 154 (isNumberOfBytesOut, isNumberOfBytesIn) are defined. 156 The isDomainTable breaks down accesses to the IS by Internet domain. 157 The NMS operator can thus discover the countries or groups regular 158 users of the IS belong. This on may be valuable, as an IS 159 administrator can decide whether mirror servers in certain domains 160 may be useful. Then long distance network traffic as well as the 161 server load could be reduced. 163 To see the number of hits for each day an isAccessOfLastNDaysTable 164 is defined. Together with a variable setting the total number of 165 days which can be traced backwards, this table provides information 166 on the number of accesses executed on the IS on a day to day basis. 168 The isDomainTable and isAccessOfLastNDaysTable provide useful 169 information on the number and sources of accesses to the IS, 170 however, it is equally important to know what information is 171 attracting Users to the IS. In support of this function, two tables 172 are defined. These tables are a most recent users table and a most 173 frequent users table. The combination of these tables should give 174 meaningful information of users and which information they access. 176 The isMostFrequentUser table is defined in a slightly different 177 fashion from the isMostRecentUser table. This is mainly because of 178 implementation aspects such as the amount of memory used to store 179 information relating to the IS users and the processing time to 180 generate the information. Details on every User who has accessed 181 the IS must be stored, because new accesses may give that User a 182 new place in the table. Therefore, the following solution was 183 adopted: the table is updated on initiative of the NMS, thus making 184 the NMS responsible for limiting the number of updates requested. 186 The NMS requests an update by setting the refresh variable to the 187 value `false'. An Agent subprocess then processes the new information 188 and, on exiting, sets the refresh variable to the value `true'. The 189 subprocess also updates the time stamp variable indicating the date 190 and time when the table was last refreshed. 192 Besides these variables, the size of the table can also be set with 193 a size variable which has a value in the range of 0 to 128. 194 The isMostRecentUsers table provides information on which users are 195 the last ones who accessed the IS. The size of the table is limited 196 to at most 128 and can be set in a range of 0 to 128. The table is 197 indexed with the position of the User in the table, and contains 198 information giving the Users name, the time of last access, and 199 document that was accessed. 201 4.3 Error Group 203 The error group contains network management information about errors 204 which occurred during accesses of the IS. This group abstracts from 205 the network errors that occur, it only shows errors resulting from 206 information access. This group is defined as a table with an error 207 description, the number of occurrences of that error and the time at 208 which the error last occurred. The reason for defining this 209 information in a table is that an implementor of the MIB module can 210 simply add new errors to the table without changing the MIB module 211 definition. 213 4.4 Document Group 215 The document group contains the network management information about 216 the data which is provided by the Information Store. The information 217 is kept in a table containing the documents name, access rights, 218 size, type, and other features such as the number of accesses, time 219 of last update, and any associated errors. The isDocumentTable has 220 the same implementation constraints as the isMostFrequentNUserTable, 221 and is handled in a similar fashion, with TableSize, TableRefresh, 222 and TableData variables. It should be noted that (in the current 223 implementation) e isDocumentTable is populated from User accesses, 224 and thus documents which have not been accessed will not appear in 225 the table. 227 5. Information Store MIB definitions 229 IS-MIB DEFINITIONS ::= 230 BEGIN 232 IMPORTS 233 MODULE-IDENTITY, OBJECT-TYPE, Counter32, TimeTicks, Integer32 234 FROM SNMPv2-SMI 235 TEXTUAL-CONVENTION, DisplayString, DateAndTime, TruthValue, TimeStamp 236 FROM SNMPv2-TC 237 MODULE-COMPLIANCE, OBJECT-GROUP 238 FROM SNMPv2-CONF; 240 isMIB MODULE-IDENTITY 241 LAST-UPDATED "9601251800Z" 242 ORGANIZATION "University Of Twente" 243 CONTACT-INFO 244 " Harrie Hazewinkel 246 Postal: Centre of Telematics and 247 Information Technology 248 University Of Twente 249 POBox 217 250 7500 AE Enschede 251 The Netherlands 252 phone : +31 53 4893746 253 E-mail: H.Hazewinkel@cs.utwente.nl 255 This document benefited greatly from the comments of 256 all participants in the CEO project for management of 257 World Wide Web Servers." 258 DESCRIPTION 259 "A MIB module for an Information Store. 260 An Information Store is the application from which 261 the information is retrieved on the World Wide Web." 262 ::= { enterprises universityOfTwente(785) 4 } 264 isObjects OBJECT IDENTIFIER ::= { isMIB 1 } 265 isConformance OBJECT IDENTIFIER ::= { isMIB 2 } 266 isCompliances OBJECT IDENTIFIER ::= { isConformance 1 } 267 isGroups OBJECT IDENTIFIER ::= { isConformance 2 } 268 MediaType ::= TEXTUAL-CONVENTION 269 STATUS current 270 DESCRIPTION 271 "This type should be representing the media types 272 which the information store makes available. The 273 media types are those recognized by the RFC 1700. 275 The value is a sum and is initially the value zero. 276 Then, for each media type, L, in the range 1 through 277 7, 2 raised to (L - 1) is added to the sum. 278 For example, a server which only supports video 279 would have a value of 64 (2^(7-1)). In 280 contrast, a server which is offering text and images 281 would have a value of 17 (2^(1-1) + 2^(5-1)). 283 Note that in the context of this media type, 284 values should be calculated accordingly: 285 1 text 286 2 multipart 287 3 message 288 4 application 289 5 image 290 6 audio 291 7 video" 292 SYNTAX INTEGER (0..127) 294 ApplResourceIdentifier ::= TEXTUAL-CONVENTION 295 STATUS current 296 DESCRIPTION 297 "A distinguished name which contains a host on which 298 the application is running and the application's name." 299 SYNTAX DisplayString 301 AccessRights ::= TEXTUAL-CONVENTION 302 STATUS current 303 DESCRIPTION 304 "A type with which access rights of a document is 305 described. 307 The rights are: 308 read-only permission 309 read-write permission 310 execute permission" 311 SYNTAX INTEGER { 312 read-only(1), read-write(2), execute-able(3) 313 } 315 isGeneral OBJECT IDENTIFIER ::= { isObjects 1 } 317 isName OBJECT-TYPE 318 SYNTAX DisplayString 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "An administratively-assigned name for this 323 Information Store." 324 ::= { isGeneral 1 } 325 -- Instrumentation : Config file 327 isOrganisation OBJECT-TYPE 328 SYNTAX DisplayString 329 MAX-ACCESS read-only 330 STATUS current 331 DESCRIPTION 332 "The textual identification of the organisation 333 responsible for the Information Store server. 335 For example, if the organisation which is offering 336 information of the Information Store is named 337 `Flintstones, Inc'. This value should have the 338 value of `Flintstones, Inc'." 339 ::= { isGeneral 2 } 340 -- Instrumentation : Config file 342 isContact OBJECT-TYPE 343 SYNTAX DisplayString 344 MAX-ACCESS read-only 345 STATUS current 346 DESCRIPTION 347 "The textual identification of the contact person 348 for this Information Store server, together with 349 information on how to contact this person. 351 For example, when `Fred' of the `Flintstones, Inc' 352 is maintaining this Information Store, the value 353 should be `Fred@Flintstones'." 354 ::= { isGeneral 3 } 355 -- Instrumentation : Config file 357 isLastInitialisation OBJECT-TYPE 358 SYNTAX TimeStamp 359 MAX-ACCESS read-only 360 STATUS current 361 DESCRIPTION 362 "The value of sysUpTime at the time the Information 363 Store was last initialized. If the Information Store 364 was last initialized prior to the initialization of 365 the network management subsystem, then this object 366 contains a zero value." 367 ::= { isGeneral 4 } 368 -- Instrumentation : Config file 369 isSupportedMediaTypes OBJECT-TYPE 370 SYNTAX MediaType 371 MAX-ACCESS read-only 372 STATUS current 373 DESCRIPTION 374 "A value which indicates the set of media types that 375 this Information Store primarily offers." 376 ::= { isGeneral 5 } 377 -- Instrumentation : Config file 379 isApplDependancyTable OBJECT-TYPE 380 SYNTAX SEQUENCE OF IsApplDependancyEntry 381 MAX-ACCESS not-accessible 382 STATUS current 383 DESCRIPTION 384 "The table holding objects which apply to all different 385 kinds of applications provided by the Information 386 Store." 387 ::= { isGeneral 6 } 388 -- Instrumentation : Config file 390 isApplDependancyEntry OBJECT-TYPE 391 SYNTAX IsApplDependancyEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "An entry associated with an application." 396 INDEX {applIndex} 397 ::= {isApplDependancyTable 1} 399 IsApplDependancyEntry ::= SEQUENCE { 400 isApplIndex INTEGER, 401 isApplResourceIdentifier ApplResourceIdentifier, 402 isApplProcessName DisplayString, 403 isApplVersion DisplayString, 404 isApplUptime TimeStamp, 405 isApplOperStatus INTEGER, 406 isApplLastChange TimeStamp, 407 isApplLastActivity TimeStamp, 408 isApplFailedActivities Counter32 409 } 411 isApplIndex OBJECT-TYPE 412 SYNTAX INTEGER (1..2147483647) 413 MAX-ACCESS not-accessible 414 STATUS current 415 DESCRIPTION 416 "An index to uniquely identify the application 417 application." 418 ::= {isApplDependancyEntry 1} 419 -- Instrumentation : Config file 420 isApplResourceIdentifier OBJECT-TYPE 421 SYNTAX ApplResourceIdentifier 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "The distinguished name of the host on which the 426 application is running and the application name." 427 ::= {isApplDependancyEntry 2} 428 -- Instrumentation : Config file 430 isApplProcessName OBJECT-TYPE 431 SYNTAX DisplayString 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The process name of the application." 436 ::= {isApplDependancyEntry 3} 437 -- Instrumentation : Config file 439 isApplVersion OBJECT-TYPE 440 SYNTAX DisplayString 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "The version of the application software." 445 ::= {isApplDependancyEntry 4} 446 -- Instrumentation : Config file 448 isApplUptime OBJECT-TYPE 449 SYNTAX TimeTicks 450 MAX-ACCESS read-only 451 STATUS current 452 DESCRIPTION 453 "The value of sysUpTime at the time the application 454 was last initialized. If the application was last 455 initialized prior to the last initialization of the 456 network management subsystem, then this object contains 457 a zero value." 458 ::= {isApplDependancyEntry 5} 459 -- Instrumentation : Config file 460 isApplOperStatus OBJECT-TYPE 461 SYNTAX INTEGER { running(1), sleeping(2), 462 runnable(3), idle(4), 463 zombie(5), traced(6), 464 sxbrkState(7), notFound(8) } 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "Indicates the operational status of the network service 469 application. The values are related to the output 470 of the `ps'-command and the values are: 472 running: running on a processor. 473 sleeping: waiting for an event to complete. 474 runnable: on run queue. 475 idle: being created. 476 zombie: terminated and parent not 477 waiting. 478 traced: stopped by a signal because 479 parent is tracing it. 480 sxbrkState: waiting for more primary memory. 481 notFound: not found in process list." 482 ::= {isApplDependancyEntry 6} 483 -- Instrumentation : Config file 485 isApplLastChange OBJECT-TYPE 486 SYNTAX TimeStamp 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The value of sysUpTime at the time the application 491 application entered its current operational state. If 492 the current state was entered prior to the last 493 initialization of the local network management 494 subsystem, then this object contains a zero value." 495 ::= {isApplDependancyEntry 7 } 496 -- Instrumentation : Config file 498 isApplLastActivity OBJECT-TYPE 499 SYNTAX TimeStamp 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The value of sysUpTime at the time this application 504 last performed some activity. If the last activity 505 occurred prior to the last initialization of the 506 application, then this object contains a zero value." 507 ::= {isApplDependancyEntry 8 } 508 -- Instrumentation : Config file 509 isApplFailedActivities OBJECT-TYPE 510 SYNTAX Counter32 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "The total number activities where the application 515 has failed, since application initialization." 516 ::= {isApplDependancyEntry 9} 517 -- Instrumentation : Config file 519 isTopicTable OBJECT-TYPE 520 SYNTAX SEQUENCE OF IsTopicEntry 521 MAX-ACCESS not-accessible 522 STATUS current 523 DESCRIPTION 524 "The table holding topics provided by this 525 Information Store." 526 ::= { isGeneral 7 } 527 -- Instrumentation : Config file 529 isTopicEntry OBJECT-TYPE 530 SYNTAX IsTopicEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "An entry associated with the topics." 535 INDEX { IMPLIED topic } 536 ::= {isTopicTable 1} 537 -- Instrumentation : Config file 539 IsTopicEntry ::= SEQUENCE { 540 isTopic DisplayString 541 } 543 isTopic OBJECT-TYPE 544 SYNTAX DisplayString 545 MAX-ACCESS read-only 546 STATUS current 547 DESCRIPTION 548 "A textual description of a topic." 549 ::= {isTopicEntry 1} 551 -- 552 -- This group provides general access information and access information 553 -- organized by domain, day, most recent users, most frequent users. 554 -- 556 isAccess OBJECT IDENTIFIER ::= { isObjects 2 } 557 isNumberOfAccesses OBJECT-TYPE 558 SYNTAX Counter32 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "The total number accesses done at the Information 563 Store." 564 ::= { isAccess 1 } 565 -- Instrumentation : Log file 567 isNumberOfBytesOut OBJECT-TYPE 568 SYNTAX Counter32 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The total number bytes transfered by the Information 573 Store." 574 ::= { isAccess 2 } 575 -- Instrumentation : Log file 577 isNumberOfBytesIn OBJECT-TYPE 578 SYNTAX Counter32 579 MAX-ACCESS read-only 580 STATUS current 581 DESCRIPTION 582 "The total number bytes received by the Information 583 Store." 584 ::= { isAccess 3 } 585 -- Instrumentation : Direct access 587 isDomainTable OBJECT-TYPE 588 SYNTAX SEQUENCE OF IsDomainEntry 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION 592 "The domain table keeps track of the number of 593 accesses done from a specific domain." 594 ::= { isAccess 4 } 595 -- Instrumentation : Log file 597 isDomainEntry OBJECT-TYPE 598 SYNTAX IsDomainEntry 599 MAX-ACCESS not-accessible 600 STATUS current 601 DESCRIPTION 602 "Entry (conceptual row) of the domain table." 603 INDEX { IMPLIED domainName } 604 ::= { isDomainTable 1 } 606 IsDomainEntry ::= SEQUENCE { 607 isDomainName DisplayString, 608 isDomainAccesses Counter32 609 } 610 isDomainName OBJECT-TYPE 611 SYNTAX DisplayString 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The domain of which the number of accesses 616 specific has to be monitored." 617 ::= { isDomainEntry 1 } 618 -- Instrumentation : Log file 620 isDomainAccesses OBJECT-TYPE 621 SYNTAX Counter32 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "The number of accesses done from a certain domain." 626 ::= { isDomainEntry 2 } 627 -- Instrumentation : Log file 629 isAccessOfLastNDaysTableSize OBJECT-TYPE 630 SYNTAX INTEGER (0..32) 631 MAX-ACCESS read-write 632 STATUS current 633 DESCRIPTION 634 "The number of entries which is contained 635 in the accessOfLastNDaysTable." 636 ::= { isAccess 5 } 637 -- Instrumentation : Agent internal 639 isAccessOfLastNDaysTable OBJECT-TYPE 640 SYNTAX SEQUENCE OF IsAccessOfLastNDaysEntry 641 MAX-ACCESS not-accessible 642 STATUS current 643 DESCRIPTION 644 "The access of last days table keeps track of the 645 number of accesses that have been done in the past. 646 Each entry is a specific day in the past. The day 647 which is specified is related to the current day. 649 This table should be a Top N table and should be 650 configured by the NMS." 651 ::= { isAccess 6 } 653 isAccessOfLastNDaysEntry OBJECT-TYPE 654 SYNTAX IsAccessOfLastNDaysEntry 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "Entry (conceptual row) of the accessOfLastNDaysTable." 659 INDEX { lastNDayIndex } 660 ::= { accessOfLastNDaysTable 1 } 661 IsAccessOfLastNDaysEntry ::= SEQUENCE { 662 isLastNDayIndex INTEGER, 663 isAccessOflastNDay Counter32 664 } 666 isLastNDayIndex OBJECT-TYPE 667 SYNTAX INTEGER (0..32) 668 MAX-ACCESS not-accessible 669 STATUS current 670 DESCRIPTION 671 "The index of the Last N Days Table" 672 ::= { accessOfLastNDaysEntry 1 } 673 -- Instrumentation : Agent internal 675 isAccessOflastNDay OBJECT-TYPE 676 SYNTAX Counter32 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "The number of accesses done on the specified day 681 in the past." 682 ::= { accessOfLastNDaysEntry 2 } 683 -- Instrumentation : logfile 685 isMostFrequentNUserTableSize OBJECT-TYPE 686 SYNTAX INTEGER (0..128) 687 MAX-ACCESS read-write 688 STATUS current 689 DESCRIPTION 690 "The number of entries which is contained 691 in the MostFrequentNUserTable." 692 ::= { isAccess 7 } 693 -- Instrumentation : Agent internal 695 isMostFrequentNUserTableRefresh OBJECT-TYPE 696 SYNTAX TruthValue 697 MAX-ACCESS read-write 698 STATUS current 699 DESCRIPTION 700 "Field with which a new `most frequent N user table' 701 will be made." 702 ::= { isAccess 8 } 703 -- Instrumentation : Agent internal 705 isMostFrequentNUserTableDate OBJECT-TYPE 706 SYNTAX DateAndTime 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The universal date and time for the last time the 711 isMostFrequentNUserTable was refreshed.." 712 ::= { isAccess 9 } 713 -- Instrumentation : Agent internal 714 isMostFrequentNUserTable OBJECT-TYPE 715 SYNTAX SEQUENCE OF IsMostFrequentNUserEntry 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "The access of document table keeps track of the 720 number of accesses that have been done in the past. 721 Each entry is a separate user. 723 This is a Top N table with the N most recently accessed 724 documents." 725 ::= { isAccess 10 } 727 isMostFrequentNUserEntry OBJECT-TYPE 728 SYNTAX IsMostFrequentNUserEntry 729 MAX-ACCESS not-accessible 730 STATUS current 731 DESCRIPTION 732 "Entry (conceptual row) of the document table." 733 INDEX { mfIndex } 734 ::= { isMostFrequentNUserTable 1 } 736 IsMostFrequentNUserEntry ::= SEQUENCE { 737 isMfIndex INTEGER, 738 isMfUserName DisplayString, 739 isMfNumberOfAccesses Counter32 740 } 742 isMfIndex OBJECT-TYPE 743 SYNTAX INTEGER (0..128) 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "The index indicates the position in the Top N table." 748 ::= { isMostFrequentNUserEntry 1 } 749 -- Instrumentation : Agent internal 751 isMfUserName OBJECT-TYPE 752 SYNTAX DisplayString 753 MAX-ACCESS read-only 754 STATUS current 755 DESCRIPTION 756 "The name of the user." 757 ::= { isMostFrequentNUserEntry 2 } 758 -- Instrumentation : Log file 759 isMfNumberOfAccesses OBJECT-TYPE 760 SYNTAX Counter32 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION 764 "The number of accesses made by the user on 765 this server." 766 ::= { isMostFrequentNUserEntry 3 } 767 -- Instrumentation : Log file 769 isMostRecentNUserTableSize OBJECT-TYPE 770 SYNTAX INTEGER (0..128) 771 MAX-ACCESS read-write 772 STATUS current 773 DESCRIPTION 774 "The number of entries which is contained 775 in the isMostRecentNUserTable." 776 ::= { isAccess 11 } 777 -- Instrumentation : Agent internal 779 isMostRecentNUserTable OBJECT-TYPE 780 SYNTAX SEQUENCE OF IsMostRecentNUserEntry 781 MAX-ACCESS not-accessible 782 STATUS current 783 DESCRIPTION 784 "The access of document table keeps track of the 785 number of accesses that have been done in the past. 786 Each entry is a document. 788 This is a Top N table with the N most recently accessed 789 documents." 790 ::= { isAccess 12 } 792 isMostRecentNUserEntry OBJECT-TYPE 793 SYNTAX IsMostRecentNUserEntry 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "Entry (conceptual row) of the most recent users table." 798 INDEX { mrIndex } 799 ::= { isMostRecentNUserTable 1 } 801 IsMostRecentNUserEntry ::= SEQUENCE { 802 isMrIndex INTEGER, 803 isMrUserName DisplayString, 804 isMrLastTime DateAndTime, 805 isMrLastDocument DisplayString 806 } 807 isMrIndex OBJECT-TYPE 808 SYNTAX INTEGER (0..128) 809 MAX-ACCESS not-accessible 810 STATUS current 811 DESCRIPTION 812 "The index indicates the sequence of the recent users." 813 ::= { isMostRecentNUserEntry 1 } 814 -- Instrumentation : Agent internal 816 isMrUserName OBJECT-TYPE 817 SYNTAX DisplayString 818 MAX-ACCESS read-only 819 STATUS current 820 DESCRIPTION 821 "The name of the user." 822 ::= { isMostRecentNUserEntry 2 } 823 -- Instrumentation : Log file 825 isMrLastTime OBJECT-TYPE 826 SYNTAX DateAndTime 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "The last time the user has accessed this server." 831 ::= { isMostRecentNUserEntry 3 } 832 -- Instrumentation : Log file 834 isMrLastDocument OBJECT-TYPE 835 SYNTAX DisplayString 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "The last operation or document which is accessed 840 by the user at this server." 841 ::= { isMostRecentNUserEntry 4 } 842 -- Instrumentation : Log file 844 -- 845 -- The section of the errors that occured in the Information Store. 846 -- 848 isErrors OBJECT IDENTIFIER ::= { isObjects 3 } 849 isErrorTable OBJECT-TYPE 850 SYNTAX SEQUENCE OF IsErrorEntry 851 MAX-ACCESS not-accessible 852 STATUS current 853 DESCRIPTION 854 "The access of document table keeps track of the 855 number of accesses that have been done in the past. 856 Each entry is a document. 858 This is a Top N table with the N most recently accessed 859 documents." 860 ::= { isErrors 12 } 862 isErrorEntry OBJECT-TYPE 863 SYNTAX IsErrorEntry 864 MAX-ACCESS not-accessible 865 STATUS current 866 DESCRIPTION 867 "Entry (conceptual row) of the document table." 868 INDEX { errorIndex } 869 ::= { isErrorTable 1 } 871 IsErrorEntry ::= SEQUENCE { 872 isErrorIndex INTEGER, 873 isErrorDescription DisplayString, 874 isErrorCount Counter32, 875 isErrorLastTime TimeStamp 876 } 878 isErrorIndex OBJECT-TYPE 879 SYNTAX INTEGER (0..128) 880 MAX-ACCESS not-accessible 881 STATUS current 882 DESCRIPTION 883 "The index indicating the error." 884 ::= { isErrorEntry 1 } 886 isErrorDescription OBJECT-TYPE 887 SYNTAX DisplayString 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "The textual description of the error." 892 ::= { isErrorEntry 2 } 894 isErrorCount OBJECT-TYPE 895 SYNTAX Counter32 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The number of errors that occured." 900 ::= { isErrorEntry 3 } 901 isErrorLastTime OBJECT-TYPE 902 SYNTAX TimeStamp 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The time of the last error occured." 907 ::= { isErrorEntry 4 } 909 -- 910 -- This group contains information about documents which are accessed 911 -- on the Information Store Server. That are the documents accessed since 912 -- the start of the server. This are the URI with which a information 913 -- can be accessed. 915 -- For example a document is index.html: 916 -- If this is a document retrieved from the directory root of the 917 -- Information Store. 918 -- If this document is in a directory beneath the directory root it 919 -- should also mention this path in the isDocumentName. 920 -- '/' 921 -- 922 -- For example a document script of the cgi-interface: 923 -- The script is mentioned in this table with the isDocumentName 924 -- `cgi/''/' 925 -- 927 isDocuments OBJECT IDENTIFIER ::= { isObjects 4 } 929 isDocumentTableSize OBJECT-TYPE 930 SYNTAX INTEGER (0..128) 931 MAX-ACCESS read-write 932 STATUS current 933 DESCRIPTION 934 "The number of entries which are contained 935 in the isDocumentTable." 936 ::= { isDocuments 1 } 938 isDocumentTableRefresh OBJECT-TYPE 939 SYNTAX TruthValue 940 MAX-ACCESS read-write 941 STATUS current 942 DESCRIPTION 943 "Field with which a new `document table' will be made." 944 ::= { isDocuments 2 } 946 isDocumentTableDate OBJECT-TYPE 947 SYNTAX DateAndTime 948 MAX-ACCESS read-only 949 STATUS current 950 DESCRIPTION 951 "The universal date and time for the last time the 952 isDocumentTable was refreshed." 953 ::= { isDocuments 3 } 954 isDocumentTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF IsDocumentEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "The access of document table keeps track of the 960 number of accesses that have been done in the past. 961 Each entry is a document." 962 ::= { isDocuments 4 } 964 isDocumentEntry OBJECT-TYPE 965 SYNTAX IsDocumentEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "Entry (conceptual row) of the document table." 970 INDEX { documentIndex } 971 ::= { isDocumentTable 1 } 973 IsDocumentEntry ::= SEQUENCE { 974 isDocumentIndex INTEGER, 975 isDocumentName DisplayString, 976 isDocumentAccesses Counter32, 977 isDocumentAccessRight AccessRights, 978 isDocumentSize Integer32, 979 isDocumentErrors Counter32, 980 isDocumentUpdate DateAndTime, 981 isDocumentAccessesAtLastUpdate Counter32, 982 isDocumentLastAccess DateAndTime, 983 isDocumentType MediaType 984 } 986 isDocumentIndex OBJECT-TYPE 987 SYNTAX INTEGER (0..127) 988 MAX-ACCESS not-accessible 989 STATUS current 990 DESCRIPTION 991 "The ranking of the document is a top N table." 992 ::= { isDocumentEntry 1 } 993 -- Instrumentation : Log file 995 isDocumentName OBJECT-TYPE 996 SYNTAX DisplayString 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The name of the document available at the Information 1001 Store." 1002 ::= { isDocumentEntry 2 } 1003 -- Instrumentation : Log file 1004 isDocumentAccesses OBJECT-TYPE 1005 SYNTAX Counter32 1006 MAX-ACCESS read-only 1007 STATUS current 1008 DESCRIPTION 1009 "The number of accesses of the document." 1010 ::= { isDocumentEntry 3 } 1011 -- Instrumentation : Log file 1013 isDocumentAccessRights OBJECT-TYPE 1014 SYNTAX AccessRights 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "The accessrights of the document. This field should 1019 restrict the information retrieval of the clients." 1020 ::= { isDocumentEntry 4 } 1021 -- Instrumentation : System 1023 isDocumentSize OBJECT-TYPE 1024 SYNTAX Integer32 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The size of the document in bytes (octets)." 1029 ::= { isDocumentEntry 5 } 1030 -- Instrumentation : System 1032 isDocumentErrors OBJECT-TYPE 1033 SYNTAX Counter32 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The number of errors that occured during accessing 1038 this document." 1039 ::= { isDocumentEntry 6 } 1040 -- Instrumentation : Log file 1042 isDocumentUpdate OBJECT-TYPE 1043 SYNTAX DateAndTime 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "Date and time when this file was last updated." 1048 ::= { isDocumentEntry 7 } 1049 -- Instrumentation : System 1050 isDocumentAccessesAtLastUpdate OBJECT-TYPE 1051 SYNTAX Counter32 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "The number of accesses of the document since 1056 the document was updated for the last time." 1057 ::= { isDocumentEntry 8 } 1058 -- Instrumentation : System 1060 isDocumentLastAccess OBJECT-TYPE 1061 SYNTAX DateAndTime 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "The date and time the document was last accessed." 1066 ::= { isDocumentEntry 9 } 1067 -- Instrumentation : Log file 1069 isDocumentType OBJECT-TYPE 1070 SYNTAX MediaType 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "The type of the document." 1075 ::= { isDocumentEntry 10 } 1076 -- Instrumentation : - 1078 -- 1079 -- Conformance and compliance definitions. 1080 -- 1082 isGeneralGroup OBJECT-GROUP 1083 OBJECTS { isName, 1084 isOrganisation, 1085 isContact, 1086 isLastInitialisation, 1087 isSupportedMediaTypes, 1088 isTopic } 1089 STATUS current 1090 DESCRIPTION 1091 "The isGeneralGroup defines the objects 1092 which are common to all Information Store 1093 applications" 1094 ::= { isGroups 1 } 1095 isApplDependancyGroup OBJECT-GROUP 1096 OBJECTS{ 1097 isApplResourceIdentifier, isApplProcessName, 1098 isApplVersion, isApplUptime, 1099 isApplOperStatus, isApplLastChange, 1100 isApplLastActivity, isApplFailedActivities } 1101 STATUS current 1102 DESCRIPTION 1103 "The application dependency Group provides information 1104 about additional processes (or helper processes) of 1105 the information store." 1106 ::= { isGroups 2 } 1108 isErrorGroup OBJECT-GROUP 1109 OBJECTS { isErrorIndex, isErrorDescription, 1110 isErrorCount, isErrorLastTime } 1111 STATUS current 1112 DESCRIPTION 1113 "The isErrorGroup provides the information 1114 about the errors occured with the 1115 information store." 1116 ::= { isGroups 3 } 1118 isAccessGroup OBJECT-GROUP 1119 OBJECTS { 1120 isNumberOfAccesses, 1121 isNumberOfBytesOut, 1122 isNumberOfBytesIn, 1123 isDomainName, isDomainAccesses, 1124 isAccessOfLastNDaysTableSize, 1125 isLastNDayIndex, isAccessOflastNDay, 1126 isMrUserName, isMrLastTime, isMrLastDocument, 1127 isMostRecentNUserTableSize, 1128 isMostFrequentNUserTableSize, 1129 isMostFrequentNUserTableRefresh, 1130 isMostFrequentNUserTableDate, 1131 isMfUserName, isMfNumberOfAccesses } 1132 STATUS current 1133 DESCRIPTION 1134 "The isAccessGroup provides the information 1135 about the accesses performed on this 1136 information store.. 1137 The group defines the total number of accesses 1138 and the number of bytes belonging to the accesses. 1139 The otherwise the accesses or ordered in tables 1140 The ordination are: 1141 by domain, 1142 by day (LastNDays), 1143 by most frequent users (TopN), 1144 by most recent users (LastN)" 1145 ::= { isGroups 4 } 1146 isDocumentGroup OBJECT-GROUP 1147 OBJECTS { 1148 isDocumentTableSize, 1149 isDocumentTableRefresh, 1150 isDocumentTableDate, 1151 isDocumentName, 1152 isDocumentAccesses, isDocumentAccessRights, 1153 isDocumentSize, isDocumentErrors, isDocumentUpdate, 1154 isDocumentAccessesAtLastUpdate, isDocumentLastAccess, 1155 isDocumentType } 1156 STATUS current 1157 DESCRIPTION 1158 "The isDocumentGroup provides the information 1159 about the accesses which can be made on the 1160 information store." 1161 ::= { isGroups 5 } 1163 isMIBCompliance MODULE-COMPLIANCE 1164 STATUS current 1165 DESCRIPTION 1166 "The compliance statements for http entities 1167 which implement the HTTP MIB" 1168 MODULE 1169 MANDATORY-GROUPS { 1170 isGeneralGroup, 1171 isApplDependancyGroup, 1172 isErrorGroup, 1173 isAccessGroup, 1174 isDocumentGroup } 1175 ::= { isCompliances 1 } 1177 END 1178 6. Acknowledgments 1180 This document has been produced by the University of Twente 1181 (The Netherlands), together with ESYS Limited (The United Kingdom), 1182 as part of a `proof of concept' study for the `Centre of Earth 1183 Observation' (CEO) of the `Joint Research Centre' (JRC) of the 1184 European Community. This document has benefited greatly to the 1185 comments of: 1187 Mark Gamble 1188 1190 Rui Meneses 1191 1193 Juergen Schoenwaelder 1194 1195 7. References 1197 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1198 S. Waldbusser, "Structure of Management Information for version 2 1199 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1200 January 1996. 1202 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1203 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1204 RFC 1213, Hughes LAN Systems, Performance Systems International, 1205 March 1991. 1207 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1208 S. Waldbusser, "Textual Conventions for version 2 of the Simple 1209 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1211 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1212 S. Waldbusser, "Protocol Operations for version 2 of the Simple 1213 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1215 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1216 S. Waldbusser, "Conformance Statements for version 2 of the Simple 1217 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1219 [6] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1220 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1221 International, MIT Laboratory for Computer Science, May 1990. 1223 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1224 S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, 1225 January 1996. 1227 8. Security Considerations 1229 Security issues are not discussed in this memo. 1231 9. Authors' Addresses 1233 Harrie Hazewinkel / Eric van Hengstum / Aiko Pras 1234 University of Twente 1235 Centre for Telematics and Information Technology (CTIT) 1236 POBox 217 1237 7500 AE Enschede, The Netherlands 1238 Phone: +31-53-4893778 1239 Email: hazewink@cs.utwente.nl 1240 hengstum@cs.utwente.nl 1241 pras@cs.utwente.nl 1243 Table of Contents 1245 1 Abstract .................................................. 2 1246 2 The SNMPv2 Network Management Framework ................... 3 1247 2.1 Object Definitions ...................................... 3 1248 3 Introduction .............................................. 4 1249 4 Information Store MIB structure ........................... 4 1250 4.1 General group ........................................... 4 1251 4.2 Access group ............................................ 5 1252 4.2 Error group ............................................. 6 1253 4.2 Document group .......................................... 6 1254 5 Information Store MIB definition .......................... 7 1255 6 Acknowledgements .......................................... 27 1256 7 References ................................................ 28 1257 8 Security Considerations ................................... 28 1258 9 Authors' Addresses ........................................ 28