idnits 2.17.1 draft-ietf-agentx-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 16 instances of too long lines in the document, the longest one being 5 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 112 has weird spacing: '...ol used to...' == Line 113 has weird spacing: '...tribute the ...' == Line 114 has weird spacing: '...17] for detai...' == Line 131 has weird spacing: '...such as the ...' == Line 531 has weird spacing: '...session succe...' == (5 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (30 September 1999) is 8975 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) ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) == Outdated reference: A later version (-03) exists of draft-ietf-agentx-rfc-update-02 ** Downref: Normative reference to an Historic RFC: RFC 1227 (ref. '18') ** Obsolete normative reference: RFC 1907 (ref. '19') (Obsoleted by RFC 3418) Summary: 17 errors (**), 0 flaws (~~), 9 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT L. Heintz 2 Cerent Corporation 3 S. Gudur 4 Independent Consultant 5 M. Ellison, Ed. 6 Ellison Software Consulting, Inc. 7 30 September 1999 9 Definitions of Managed Objects for 10 Extensible SNMP Agents 11 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of Section 10 of RFC2026 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The Internet Society (1999). All Rights Reserved. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community. 42 In particular, it describes objects managing SNMP agents that use the 43 Agent Extensibility (AgentX) Protocol. 45 This memo specifies a MIB module in a manner that is both compliant 46 to the SMIv2, and semantically identical to the peer SMIv1 47 definitions. 49 Table of Contents 51 1. The SNMP Management Framework ............................... 3 52 2. Introduction ................................................ 3 53 3. AgentX MIB Overview ......................................... 4 54 4. Managed Object Definitions for AgentX ....................... 6 55 5. Intellectual Property ....................................... 18 56 6. Acknowledgements ............................................ 18 57 7. Security Considerations ..................................... 19 58 8. References .................................................. 20 59 9. Authors' and Editor's Addresses ............................. 23 60 10. Full Copyright Statement ................................... 23 62 1. The SNMP Management Framework 64 The SNMP Management Framework presently consists of five major 65 components: 67 - An overall architecture, described in RFC 2571 [1]. 69 - Mechanisms for describing and naming objects and events for the 70 purpose of management. The first version of this Structure of 71 Management Information (SMI) is called SMIv1 and described in 72 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second 73 version, called SMIv2, is described in RFC 2578 [5], RFC 2579 74 [6] and RFC 2580 [7]. 76 - Message protocols for transferring management information. The 77 first version of the SNMP message protocol is called SNMPv1 and 78 described in RFC 1157 [8]. A second version of the SNMP message 79 protocol, which is not an Internet standards track protocol, is 80 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 81 The third version of the message protocol is called SNMPv3 and 82 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 84 - Protocol operations for accessing management information. The 85 first set of protocol operations and associated PDU formats is 86 described in RFC 1157 [8]. A second set of protocol operations 87 and associated PDU formats is described in RFC 1905 [13]. 89 - A set of fundamental applications described in RFC 2573 [14] 90 and the view-based access control mechanism described in RFC 91 2575 [15]. 93 A more detailed introduction to the current SNMP Management Framework 94 can be found in RFC 2570 [16]. 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. Objects in the MIB are 98 defined using the mechanisms defined in the SMI. 100 This memo specifies a MIB module that is compliant to the SMIv2. A 101 MIB conforming to the SMIv1 can be produced through the appropriate 102 translations. The resulting translated MIB must be semantically 103 equivalent, except where objects or events are omitted because no 104 translation is possible (use of Counter64). Some machine readable 105 information in SMIv2 will be converted into textual descriptions in 106 SMIv1 during the translation process. However, this loss of machine 107 readable information is not considered to change the semantics of the 108 MIB. 110 2. Introduction 112 The SNMP Agent Extensibility Protocol (AgentX) is a protocol used to 113 distribute the implementation of an SNMP agent amongst a single 114 "master agent" and multiple "subagents". See [17] for details about 115 the AgentX protocol. 117 The goals of the AgentX MIB are: 119 - List the set of subagent connections that currently have 120 logical sessions open with the master agent. 122 - Identify each subagent connection transport address and type. 124 - Identify each subagent session vendor, AgentX protocol version, 125 and other characteristics. 127 - Identify the set of MIB objects each session implements, the 128 context in which the objects are registered, and the priority 129 of the registration. 131 - Determine protocol operational parameters such as the timeout 132 interval for responses from a session and the priority at which 133 a session registers a particular MIB region. 135 - Allow (but do not require) managers to explicitly close 136 subagent sessions with the master agent. 138 3. AgentX MIB Overview 140 This MIB is organized into four groups. The agentxGeneral group 141 provides information describing the master agent's AgentX support, 142 including the protocol version supported. The agentxConnection group 143 provides information describing the current set of connections 144 capable of carrying AgentX sessions. The agentxSession group 145 provides information describing the current set of AgentX sessions. 146 The agentxRegistration group provides information describing the 147 current set of registrations. 149 Three tables form the heart of this mib. These are the connection, 150 session, and registration tables. 152 Entries in the registration table exist in a many-to-one relationship 153 with entries in the session table. This relationship is expressed 154 through the two common indices, agentxSessionIndex and 155 agentxConnIndex. Entries in the registration table also exist in a 156 many-to-one relationship with entries in the connection table. This 157 relationship is expressed through the common index, agentxConnIndex. 159 Entries in the session table exist in a many-to-one relationship with 160 entries in the connection table. This relationship is expressed 161 through the common index, agentxConnIndex. 163 4. Managed Object Definitions for AgentX 165 AGENTX-MIB DEFINITIONS ::= BEGIN 167 IMPORTS 168 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, mib-2 169 FROM SNMPv2-SMI 170 SnmpAdminString 171 FROM SNMP-FRAMEWORK-MIB 172 MODULE-COMPLIANCE, OBJECT-GROUP 173 FROM SNMPv2-CONF 174 TEXTUAL-CONVENTION, TimeStamp, TruthValue, TDomain 175 FROM SNMPv2-TC; 176 agentxMIB MODULE-IDENTITY 177 LAST-UPDATED "9909300000Z" -- Midnight 30 September 1999 178 ORGANIZATION "AgentX Working Group" 179 CONTACT-INFO "WG-email: agentx@dorothy.bmc.com 180 Subscribe: agentx-request@dorothy.bmc.com 181 WG-email Archive: ftp://ftp.peer.com/pub/agentx/archives 182 FTP repository: ftp://ftp.peer.com/pub/agentx 183 http://www.ietf.org/html.charters/agentx-charter.html 185 Chair: Bob Natale 186 ACE*COMM Corporation 187 Email: bnatale@acecomm.com 189 WG editor: Mark Ellison 190 Ellison Software Consulting, Inc. 191 Email: ellison@world.std.com 193 Co-author: Lauren Heintz 194 Cerent Corporation, 195 EMail: lauren.heintz@cerent.com 197 Co-author: Smitha Gudur 198 Independent Consultant 199 Email: sgudur@hotmail.com 200 " 201 DESCRIPTION 202 "This is the MIB module for the SNMP Agent Extensibility 203 Protocol (AgentX). This MIB module will be implemented by 204 the master agent. 205 " 207 REVISION "9908230000Z" 208 DESCRIPTION 209 "Rev 1.0 -- 23 August 1999 00:00 ellison 210 initial version, published in RFC xxxx. -- To be assigned by IANA 212 " 214 REVISION "9909300000Z" 215 DESCRIPTION 216 "Rev 1.01 -- 30 September 1999 00:00 ellison 217 clarification on index objects per IESG last call. 218 " 220 ::= { mib-2 ? } -- To be assigned by IANA. 222 -- Textual Conventions 224 AgentxTAddress ::= TEXTUAL-CONVENTION 225 STATUS current 226 DESCRIPTION 227 "Denotes a transport service address. This is identical to 228 the TAddress textual convention (SNMPv2-SMI) except that 229 zero-length values are permitted. 230 " 231 SYNTAX OCTET STRING (SIZE (0..255)) 233 -- Administrative assignments 235 agentxObjects OBJECT IDENTIFIER ::= { agentxMIB 1 } 236 agentxGeneral OBJECT IDENTIFIER ::= { agentxObjects 1 } 237 agentxConnection OBJECT IDENTIFIER ::= { agentxObjects 2 } 238 agentxSession OBJECT IDENTIFIER ::= { agentxObjects 3 } 239 agentxRegistration OBJECT IDENTIFIER ::= { agentxObjects 4 } 241 agentxDefaultTimeout OBJECT-TYPE 242 SYNTAX INTEGER (0..255) 243 UNITS "seconds" 244 MAX-ACCESS read-only 245 STATUS current 246 DESCRIPTION 247 "The default length of time, in seconds, that the master 248 agent should allow to elapse after dispatching a message 249 to a session before it regards the subagent as not 250 responding. This is a system-wide value that may 251 override the timeout value associated with a particular 252 session (agentxSessionTimeout) or a particular registered 253 MIB region (agentxRegTimeout). If the associated value of 254 agentxSessionTimeout and agentxRegTimeout are zero, or 255 impractical in accordance with implementation-specific 256 procedure of the master agent, the value represented by 257 this object will be the effective timeout value for the 258 master agent to await a response to a dispatch from a 259 given subagent. 261 " 262 DEFVAL { 5 } 263 ::= { agentxGeneral 1 } 265 agentxMasterAgentXVer OBJECT-TYPE 266 SYNTAX INTEGER (1..255) 267 MAX-ACCESS read-only 268 STATUS current 269 DESCRIPTION 270 "The AgentX protocol version supported by this master agent. 271 The current protocol version is 1. Note that the master agent 272 must also allow interaction with earlier version subagents. 273 " 274 ::= { agentxGeneral 2 } 276 -- The AgentX Subagent Connection Group 278 agentxConnTableLastChange OBJECT-TYPE 279 SYNTAX TimeStamp 280 MAX-ACCESS read-only 281 STATUS current 282 DESCRIPTION 283 "The value of sysUpTime when the last row creation or deletion 284 occurred in the agentxConnectionTable. 285 " 286 ::= { agentxConnection 1 } 288 agentxConnectionTable OBJECT-TYPE 289 SYNTAX SEQUENCE OF AgentxConnectionEntry 290 MAX-ACCESS not-accessible 291 STATUS current 292 DESCRIPTION 293 "The agentxConnectionTable tracks all current AgentX transport 294 connections. There may be zero, one, or more AgentX sessions 295 carried on a given AgentX connection. 296 " 297 ::= { agentxConnection 2 } 299 agentxConnectionEntry OBJECT-TYPE 300 SYNTAX AgentxConnectionEntry 301 MAX-ACCESS not-accessible 302 STATUS current 303 DESCRIPTION 304 "An agentxConnectionEntry contains information describing a 305 single AgentX transport connection. A connection may be 306 used to support zero or more AgentX sessions. An entry is 307 created when a new transport connection is established, 308 and is destroyed when the transport connection is terminated. 310 " 311 INDEX { agentxConnIndex } 312 ::= { agentxConnectionTable 1 } 314 AgentxConnectionEntry ::= SEQUENCE { 315 agentxConnIndex Unsigned32, 316 agentxConnOpenTime TimeStamp, 317 agentxConnTransportDomain TDomain, 318 agentxConnTransportAddress AgentxTAddress } 320 agentxConnIndex OBJECT-TYPE 321 SYNTAX Unsigned32 (1..4294967295) 322 MAX-ACCESS not-accessible 323 STATUS current 324 DESCRIPTION 325 "agentxConnIndex contains the value that uniquely identifies 326 an open transport connection used by this master agent 327 to provide AgentX service. Values of this index should 328 not be re-used. The value assigned to a given transport 329 connection is constant for the lifetime of that connection. 330 " 331 ::= { agentxConnectionEntry 1 } 333 agentxConnOpenTime OBJECT-TYPE 334 SYNTAX TimeStamp 335 MAX-ACCESS read-only 336 STATUS current 337 DESCRIPTION 338 "The value of sysUpTime when this connection was established 339 and, therefore, its value when this entry was added to the table. 340 " 341 ::= { agentxConnectionEntry 2 } 343 agentxConnTransportDomain OBJECT-TYPE 344 SYNTAX TDomain 345 MAX-ACCESS read-only 346 STATUS current 347 DESCRIPTION 348 "The transport protocol in use for this connection to the 349 subagent. 350 " 351 ::= { agentxConnectionEntry 3 } 353 agentxConnTransportAddress OBJECT-TYPE 354 SYNTAX AgentxTAddress 355 MAX-ACCESS read-only 356 STATUS current 357 DESCRIPTION 358 "The transport address of the remote (subagent) end of this 359 connection to the master agent. This object may be zero-length 360 for unix-domain sockets (and possibly other types of transport 361 addresses) since the subagent need not bind a filename to its 362 local socket. 363 " 364 ::= { agentxConnectionEntry 4 } 366 -- The AgentX Subagent Session Group 368 agentxSessionTableLastChange OBJECT-TYPE 369 SYNTAX TimeStamp 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The value of sysUpTime when the last row creation or deletion 374 occurred in the agentxSessionTable. 375 " 376 ::= { agentxSession 1 } 378 agentxSessionTable OBJECT-TYPE 379 SYNTAX SEQUENCE OF AgentxSessionEntry 380 MAX-ACCESS not-accessible 381 STATUS current 382 DESCRIPTION 383 "A table of AgentX subagent sessions currently in effect. 384 " 385 ::= { agentxSession 2 } 387 agentxSessionEntry OBJECT-TYPE 388 SYNTAX AgentxSessionEntry 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "Information about a single open session between the AgentX 393 master agent and a subagent is contained in this entry. An 394 entry is created when a new session is successfully established 395 and is destroyed either when the subagent transport connection 396 has terminated or when the subagent session is closed. 397 " 398 INDEX { agentxConnIndex, agentxSessionIndex } 399 ::= { agentxSessionTable 1 } 401 AgentxSessionEntry ::= SEQUENCE { 402 agentxSessionIndex Unsigned32, 403 agentxSessionObjectID OBJECT IDENTIFIER, 404 agentxSessionDescr SnmpAdminString, 405 agentxSessionAdminStatus INTEGER, 406 agentxSessionOpenTime TimeStamp, 407 agentxSessionAgentXVer INTEGER, 408 agentxSessionTimeout INTEGER 409 } 411 agentxSessionIndex OBJECT-TYPE 412 SYNTAX Unsigned32 (0..4294967295) 413 MAX-ACCESS not-accessible 414 STATUS current 415 DESCRIPTION 416 "A unique index for the subagent session. It is the same as 417 h.sessionID defined in the agentx header. Note that if 418 a subagent's session with the master agent is closed for 419 any reason its index should not be re-used. 420 A value of zero(0) is specifically allowed in order 421 to be compatible with the definition of h.sessionId. 422 " 423 ::= { agentxSessionEntry 1 } 425 agentxSessionObjectID OBJECT-TYPE 426 SYNTAX OBJECT IDENTIFIER 427 MAX-ACCESS read-only 428 STATUS current 429 DESCRIPTION 430 "This is taken from the o.id field of the agentx-Open-PDU. 431 This attribute will report a value of '0.0' for subagents 432 not supporting the notion of an AgentX session object 433 identifier. 434 " 435 ::= { agentxSessionEntry 2 } 437 agentxSessionDescr OBJECT-TYPE 438 SYNTAX SnmpAdminString 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "A textual description of the session. This is analogous to 443 sysDescr defined in the SNMPv2-MIB in RFC 1907 [19] and is 444 taken from the o.descr field of the agentx-Open-PDU. 445 This attribute will report a zero-length string value for 446 subagents not supporting the notion of a session description. 447 " 448 ::= { agentxSessionEntry 3 } 450 agentxSessionAdminStatus OBJECT-TYPE 451 SYNTAX INTEGER { 452 up(1), 453 down(2) 454 } 455 MAX-ACCESS read-write 456 STATUS current 457 DESCRIPTION 458 "The administrative (desired) status of the session. Setting 459 the value to 'down(2)' closes the subagent session (with c.reason 460 set to 'reasonByManager'). 461 " 462 ::= { agentxSessionEntry 4 } 464 agentxSessionOpenTime OBJECT-TYPE 465 SYNTAX TimeStamp 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The value of sysUpTime when this session was opened and, 470 therefore, its value when this entry was added to the table. 471 " 472 ::= { agentxSessionEntry 5 } 474 agentxSessionAgentXVer OBJECT-TYPE 475 SYNTAX INTEGER (1..255) 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The version of the AgentX protocol supported by the 480 session. This must be less than or equal to the value of 481 agentxMasterAgentXVer. 482 " 483 ::= { agentxSessionEntry 6 } 485 agentxSessionTimeout OBJECT-TYPE 486 SYNTAX INTEGER (0..255) 487 UNITS "seconds" 488 MAX-ACCESS read-only 489 STATUS current 490 DESCRIPTION 491 "The length of time, in seconds, that a master agent should 492 allow to elapse after dispatching a message to this session 493 before it regards the subagent as not responding. This value 494 is taken from the o.timeout field of the agentx-Open-PDU. 496 This is a session-specific value that may be overridden by 497 values associated with the specific registered MIB regions 498 (see agentxRegTimeout). A value of zero(0) indicates that 499 the master agent's default timeout value should be used 500 (see agentxDefaultTimeout). 501 " 502 ::= { agentxSessionEntry 7 } 504 -- The AgentX Registration Group 506 agentxRegistrationTableLastChange OBJECT-TYPE 507 SYNTAX TimeStamp 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "The value of sysUpTime when the last row creation or deletion 512 occurred in the agentxRegistrationTable. 513 " 514 ::= { agentxRegistration 1 } 516 agentxRegistrationTable OBJECT-TYPE 517 SYNTAX SEQUENCE OF AgentxRegistrationEntry 518 MAX-ACCESS not-accessible 519 STATUS current 520 DESCRIPTION 521 "A table of registered regions. 522 " 523 ::= { agentxRegistration 2 } 525 agentxRegistrationEntry OBJECT-TYPE 526 SYNTAX AgentxRegistrationEntry 527 MAX-ACCESS not-accessible 528 STATUS current 529 DESCRIPTION 530 "Contains information for a single registered region. An 531 entry is created when a session successfully registers a 532 region and is destroyed for any of three reasons: this region 533 is unregistered by the session, the session is closed, 534 or the subagent connection is closed. 535 " 536 INDEX { agentxConnIndex, agentxSessionIndex, agentxRegIndex } 537 ::= { agentxRegistrationTable 1 } 539 AgentxRegistrationEntry ::= SEQUENCE { 540 agentxRegIndex Unsigned32, 541 agentxRegContext OCTET STRING, 542 agentxRegStart OBJECT IDENTIFIER, 543 agentxRegRangeSubId Unsigned32, 544 agentxRegUpperBound Unsigned32, 545 agentxRegPriority Unsigned32, 546 agentxRegTimeout INTEGER, 547 agentxRegInstance TruthValue } 549 agentxRegIndex OBJECT-TYPE 550 SYNTAX Unsigned32 (1..4294967295) 551 MAX-ACCESS not-accessible 552 STATUS current 553 DESCRIPTION 554 "agentxRegIndex uniquely identifies a registration entry. 555 This value is constant for the lifetime of an entry. 556 " 557 ::= { agentxRegistrationEntry 1 } 559 agentxRegContext OBJECT-TYPE 560 SYNTAX OCTET STRING 561 MAX-ACCESS read-only 562 STATUS current 563 DESCRIPTION 564 "The context in which the session supports the objects in this 565 region. A zero-length context indicates the default context. 566 " 567 ::= { agentxRegistrationEntry 2 } 569 agentxRegStart OBJECT-TYPE 570 SYNTAX OBJECT IDENTIFIER 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "The starting OBJECT IDENTIFIER of this registration entry. The 575 session identified by agentxSessionIndex implements objects 576 starting at this value (inclusive). Note that this value could 577 identify an object type, an object instance, or a partial object 578 instance. 579 " 580 ::= { agentxRegistrationEntry 3 } 582 agentxRegRangeSubId OBJECT-TYPE 583 SYNTAX Unsigned32 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "agentxRegRangeSubId is used to specify the range. This is 588 taken from r.region_subid in the registration PDU. If the value 589 of this object is zero, no range is specified. If it is non-zero, 590 it identifies the `nth' sub-identifier in r.region for which 591 this entry's agentxRegUpperBound value is substituted in the 592 OID for purposes of defining the region's upper bound. 593 " 594 ::= { agentxRegistrationEntry 4 } 596 agentxRegUpperBound OBJECT-TYPE 597 SYNTAX Unsigned32 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION 601 "agentxRegUpperBound represents the upper-bound sub-identifier in 602 a registration. This is taken from the r.upper_bound in the 603 registration PDU. If agentxRegRangeSubid (r.region_subid) is 604 zero, this value is also zero and is not used to define an upper 605 bound for this registration. 606 " 607 ::= { agentxRegistrationEntry 5 } 609 agentxRegPriority OBJECT-TYPE 610 SYNTAX Unsigned32 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The registration priority. Lower values have higher priority. 615 This value is taken from r.priority in the register PDU. 616 Sessions should use the value of 127 for r.priority if a 617 default value is desired. 618 " 619 ::= { agentxRegistrationEntry 6 } 621 agentxRegTimeout OBJECT-TYPE 622 SYNTAX INTEGER (0..255) 623 UNITS "seconds" 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The timeout value, in seconds, for responses to 628 requests associated with this registered MIB region. 629 A value of zero(0) indicates the default value (indicated 630 by by agentxSessionTimeout or agentxDefaultTimeout) is to 631 be used. This value is taken from the r.timeout field of 632 the agentx-Register-PDU. 633 " 634 ::= { agentxRegistrationEntry 7 } 636 agentxRegInstance OBJECT-TYPE 637 SYNTAX TruthValue 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The value of agentxRegInstance is `true' for 642 registrations for which the INSTANCE_REGISTRATION 643 was set, and is `false' for all other registrations. 644 " 645 ::= { agentxRegistrationEntry 8 } 647 -- Conformance Statements for AgentX 649 agentxConformance OBJECT IDENTIFIER ::= { agentxMIB 2 } 650 agentxMIBGroups OBJECT IDENTIFIER ::= { agentxConformance 1 } 651 agentxMIBCompliances OBJECT IDENTIFIER ::= { agentxConformance 2 } 653 -- Compliance Statements for AgentX 655 agentxMIBCompliance MODULE-COMPLIANCE 656 STATUS current 657 DESCRIPTION 658 "The compliance statement for SNMP entities that implement the 659 AgentX protocol. Note that a compliant agent can implement all 660 objects in this MIB module as read-only. 661 " 662 MODULE -- this module 663 MANDATORY-GROUPS { agentxMIBGroup } 665 OBJECT agentxSessionAdminStatus 666 MIN-ACCESS read-only 667 DESCRIPTION 668 "Write access is not required. 669 " 670 ::= { agentxMIBCompliances 1 } 672 agentxMIBGroup OBJECT-GROUP 673 OBJECTS { 674 agentxDefaultTimeout, 675 agentxMasterAgentXVer, 676 agentxConnTableLastChange, 677 agentxConnOpenTime, 678 agentxConnTransportDomain, 679 agentxConnTransportAddress, 680 agentxSessionTableLastChange, 681 agentxSessionTimeout, 682 agentxSessionObjectID, 683 agentxSessionDescr, 684 agentxSessionAdminStatus, 685 agentxSessionOpenTime, 686 agentxSessionAgentXVer, 687 agentxRegistrationTableLastChange, 688 agentxRegContext, 689 agentxRegStart, 690 agentxRegRangeSubId, 691 agentxRegUpperBound, 692 agentxRegPriority, 693 agentxRegTimeout, 694 agentxRegInstance 695 } 696 STATUS current 697 DESCRIPTION 698 "All accessible objects in the AgentX MIB. 699 " 700 ::= { agentxMIBGroups 1 } 702 END 704 5. Intellectual Property 706 The IETF takes no position regarding the validity or scope of any 707 intellectual property or other rights that might be claimed to 708 pertain to the implementation or use of the technology described in 709 this document or the extent to which any license under such rights 710 might or might not be available; neither does it represent that it 711 has made any effort to identify any such rights. Information on the 712 IETF's procedures with respect to rights in standards-track and 713 standards-related documentation can be found in BCP-11. Copies of 714 claims of rights made available for publication and any assurances of 715 licenses to be made available, or the result of an attempt made to 716 obtain a general license or permission for the use of such 717 proprietary rights by implementors or users of this specification can 718 be obtained from the IETF Secretariat. 720 The IETF invites any interested party to bring to its attention any 721 copyrights, patents or patent applications, or other proprietary 722 rights which may cover technology that may be required to practice 723 this standard. Please address the information to the IETF Executive 724 Director. 726 6. Acknowledgements 728 This document is the result of the efforts of the IETF AgentX Working 729 Group (WG). 731 This MIB is an evolution of the Subagent MIB by Bert Wijnen 732 (wijnen@vnet.ibm.com) which in turn was derived from the SMUX-MIB by 733 Marshall Rose [18]. 735 Thanks are in order to the following AgentX WG members: 737 Mike Daniele (Compaq Computer Corporation) 738 Dale Francisco (Cisco Systems) 739 Bob Natale (ACE*COMM Corporation) 740 Randy Presuhn (BMC Software, Inc.) 741 Shawn Routhier (Epilogue) 742 Mike Thatcher (Independent Consultant) 744 Special acknowledgement is made to: 746 Maria Greene (Xedia) 748 Special acknowledgement is also made to the following individuals for 749 participating in the 1998 AgentX testing summit (bakeoff) held in 750 Sunnyvale, California: 752 Jeff Case (SNMP Research, Inc.) 753 Mike Daniele (Compaq Computer Corporation) 754 Mark Ellison (Ellison Software Consulting, Inc.) 755 Lauren Heintz (BMC Software, Inc.) 756 Verne Hyde (Independent Consultant) 757 Bob Natale (ACE*COMM Corporation) 758 Shawn Routhier (Epilogue) 759 Mike Thatcher (Independent Consultant) 760 Bert Wijnen (IBM T. J. Watson Research Center) 762 7. Security Considerations 764 There is a single management object defined in this MIB that has a 765 MAX-ACCESS clause of read-write. This object may be considered 766 sensitive or vulnerable in some network environments. The support 767 for SET operations in a non-secure environment without proper 768 protection can have a negative effect on network operations. 770 There is a single managed object in this MIB that may contain 771 sensitive information. This object is agentxSessionAdminStatus. 772 Setting agentxSessionAdminStatus to an inappropriate value can 773 effectively prevent access to management information, or provide 774 access to inappropriate information. 776 It is thus important to control even GET access to these objects and 777 possibly to even encrypt the values of these objects when sending 778 them over the network via SNMP. Not all versions of SNMP provide 779 features for such a secure environment. 781 SNMPv1 by itself is not a secure environment. Even if the network 782 itself is secure (for example by using IPSec), even then, there is no 783 control as to who on the secure network is allowed to access and 784 GET/SET (read/change/create/delete) the objects in this MIB. 786 It is recommended that the implementers consider the security 787 features as provided by the SNMPv3 framework. Specifically, the use 788 of the User-based Security Model RFC 2574 [12] and the View-based 789 Access Control Model RFC 2575 [15] is recommended. 791 It is then a customer/user responsibility to ensure that the SNMP 792 entity giving access to an instance of this MIB, is properly 793 configured to give access to the objects only to those principals 794 (users) that have legitimate rights to indeed GET or SET 795 (change/delete) them. 797 8. References 799 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 800 Describing SNMP Management Frameworks", RFC 2571, Cabletron 801 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 802 April 1999 804 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 805 Management Information for TCP/IP-based Internets", RFC 1155, STD 806 16, Performance Systems International, Hughes LAN Systems, May 807 1990 809 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 810 STD 16, Performance Systems International, Hughes LAN Systems, 811 March 1991 813 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 814 RFC 1215, Performance Systems International, March 1991 816 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 817 M., and S. Waldbusser, "Structure of Management Information 818 Version 2 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 819 Braunschweig, SNMP Research, First Virtual Holdings, International 820 Network Services, April 1999 822 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 823 M., and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, 824 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 825 First Virtual Holdings, International Network Services, April 1999 827 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 828 M., and S. Waldbusser, "Conformance Statements for SMIv2", RFC 829 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP 830 Research, First Virtual Holdings, International Network Services, 831 April 1999 833 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 834 Network Management Protocol", RFC 1157, STD 15, SNMP Research, 835 Performance Systems International, Performance Systems 836 International, MIT Laboratory for Computer Science, May 1990. 838 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 839 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 840 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 841 International Network Services, January 1996. 843 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 844 "Transport Mappings for Version 2 of the Simple Network Management 845 Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, 846 Inc., Dover Beach Consulting, Inc., International Network 847 Services, January 1996. 849 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 850 Processing and Dispatching for the Simple Network Management 851 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron 852 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 853 April 1999 855 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 856 for version 3 of the Simple Network Management Protocol (SNMPv3)", 857 RFC 2574, IBM T. J. Watson Research, April 1999 859 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 860 Operations for Version 2 of the Simple Network Management Protocol 861 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 862 Dover Beach Consulting, Inc., International Network Services, 863 January 1996. 865 [14] Levi, D., Meyer, P., and B. Stewart, "SNMP Applications", RFC 866 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 867 Systems, April 1999 869 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 870 Control Model (VACM) for the Simple Network Management Protocol 871 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 872 Cisco Systems, Inc., April 1999 874 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction 875 to Version 3 of the Internet-standard Network Management 876 Framework", RFC 2570, SNMP Research, Inc., TIS Labs at Network 877 Associates, Inc., Ericsson, Cisco Systems, April 1999 879 [17] Daniele, M., Wijnen, B., Ellison, M. and D. Francisco, "Agent 880 Extensibility (AgentX) Protocol, Version 1", 881 draft-ietf-agentx-rfc-update-02.txt Compaq Computer Corporation, 882 T.J. Watson Research Center, IBM Corp., Ellison Software 883 Consulting, Inc., Cisco Systems, September, 1999 885 [18] Rose, M., "SNMP MUX Protocol and MIB", RFC1227, Performance 886 Systems International, May 1991. 888 [19] The SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M. and 889 S. Waldbusser, "Management Information Base for Version 2 of the 890 Simple Network Management Protocol (SNMPv2)", RFC 1907, January 891 1996. 893 9. Authors' and Editor's Addresses 895 Lauren Heintz 896 Cerent Corporation 897 1450 North McDowell Blvd. 898 Petaluma, CA 94954-6515 899 USA 900 Phone: +1 707-793-1714 901 EMail: lauren.heintz@cerent.com 903 Smitha Gudur 904 Independent Consultant 905 EMail: sgudur@hotmail.com 907 Mark Ellison (WG editor) 908 Ellison SOftware Consulting, Inc. 909 33 Eastview Drive, Suite #10 910 Wilton, NH 03086 911 USA 912 Phone: +1 603-654-2703 913 Email: ellison@world.std.com 915 10. Full Copyright Statement 917 Copyright (C) The Internet Society (1999). All Rights Reserved. 919 This document and translations of it may be copied and furnished to 920 others, and derivative works that comment on or otherwise explain it 921 or assist in its implementation may be prepared, copied, published 922 and distributed, in whole or in part, without restriction of any 923 kind, provided that the above copyright notice and this paragraph are 924 included on all such copies and derivative works. However, this 925 document itself may not be modified in any way, such as by removing 926 the copyright notice or references to the Internet Society or other 927 Internet organizations, except as needed for the purpose of 928 developing Internet standards in which case the procedures for 929 copyrights defined in the Internet Standards process must be 930 followed, or as required to translate it into languages other than 931 English. 933 The limited permissions granted above are perpetual and will not be 934 revoked by the Internet Society or its successors or assigns. 936 This document and the information contained herein is provided on an 937 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 938 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 939 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 940 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 941 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.