idnits 2.17.1 draft-ietf-agentx-mib-02.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: ---------------------------------------------------------------------------- ** 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. ** The document is more than 15 pages and seems to lack a Table of Contents. == 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 1) 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 3 instances of too long lines in the document, the longest one being 3 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 491 has weird spacing: '...ons for dupli...' -- 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 (14 April 1998) is 9510 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: '7' is defined on line 738, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) == Outdated reference: A later version (-03) exists of draft-ietf-agentx-ext-pro-02 ** Downref: Normative reference to an Historic RFC: RFC 1227 (ref. '6') ** Downref: Normative reference to an Experimental RFC: RFC 1592 (ref. '7') ** Obsolete normative reference: RFC 2044 (ref. '8') (Obsoleted by RFC 2279) Summary: 16 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT M. Greene 3 Xedia. 4 S. Gudur 5 BMC Software, Inc. 6 14 April 1998 8 Definitions of Managed Objects for 9 Extensible SNMP Agents 10 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its Areas, and 16 its Working Groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference material 22 or to cite them other than as a "work in progress". 24 To view the entire list of current Internet-Drafts, please check 25 the "1id-abstracts.txt" listing contained in the Internet-Drafts 26 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 27 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 28 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 29 (US West Coast). 31 Copyright Notice 33 Copyright (C) The Internet Society (1998). All Rights Reserved. 35 Abstract 37 This memo defines an experimental portion of the Management Information 38 Base (MIB) for use with network management protocols in the Internet 39 community. In particular, it describes objects managing SNMP agents 40 that use the Agent Extensibility (AgentX) Protocol. 42 This memo specifies a MIB module in a manner that is both compliant to 43 the SNMPv2 SMI, and semantically identical to the peer SNMPv1 44 definitions. 46 This memo does not specify a standard for the Internet community. 48 1. The SNMP Network Management Framework 50 The SNMP Network Management Framework presently consists of three major 51 components. They are: 53 - the SMI, described in RFC 1902 [1] - the mechanisms used for 54 describing and naming objects for the purpose of management. 56 - the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects 57 for the Internet suite of protocols. 59 - the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for 60 accessing managed objects. 62 The Framework permits new objects to be defined for the purpose of 63 experimentation and evaluation. 65 1.1. Object Definitions 67 Managed objects are accessed via a virtual information store, termed the 68 Management Information Base or MIB. Objects in the MIB are defined 69 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 70 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 71 an administratively assigned name. The object type together with an 72 object instance serves to uniquely identify a specific instantiation of 73 the object. For human convenience, we often use a textual string, 74 termed the descriptor, to also refer to the object type. 76 2. Introduction 78 The SNMP Agent Extensibility Protocol (AgentX) is a protocol used to 79 distribute the implementation of an SNMP agent amongst a single "master 80 agent" and multiple "subagents". See [5] for details about the AgentX 81 protocol. 83 The goals of the AgentX MIB are: 85 - List the set of subagents that currently have logical sessions open 86 with the master agent. 88 - Identify each subagent's type, vendor, transport address, AgentX 89 protocol version, and other characteristics. 91 - Identify the set of MIB objects each subagent implements, the context 92 in which the objects are registered, and the priority of the 93 registration. 95 - Provide statistics about the protocol operation such as the number of 96 packets to and from each subagent. 98 - Determine protocol operational parameters such as the timeout 99 interval for responses from a subagent and the priority at which a 100 subagent registers a particular MIB region. 102 - Allow (but do not require) managers to be able to modify AgentX 103 protocol operational parameters and to explicitly close subagent 104 sessions with the master agent. 106 3. Overview 108 This MIB is organized into four groups. The agentxGeneral group 109 provides information describing the master agent's Agentx support, 110 including the protocol version supported and the supported transport 111 mechanisms. The agentxConnection group provides information describing 112 the current set of connections capable of carrying Agentx sessions. The 113 agentxSession group provides information describing the current set of 114 AgentX sessions. The agentxRegistration group provides information 115 describing the current set of registrations. 117 Three tables form the heart of this mib. These are the connection, 118 session, and registration tables. 120 Entries in the registration table exist in a many-to-one relationship 121 with entries in the session table. This relationship is represented 122 through the agentxSessionIndex and agentxConnIndex. Registration entries 123 are indexed by agentxConnIndex and agentxSessionIndex, to determine 124 which registration(s), a subagent session is responsible for a given 125 connection. 127 Entries in the session table exist in a many-to-one relationship with 128 entries in the connection table. This relationship is represented 129 through the agentxConnIndex in a session table. Session entries are 130 indexed by agentxConnIndex to determine which sessions(s), are carried 131 by a given connection. 133 4. Definitions 135 AGENTX-MIB DEFINITIONS ::= BEGIN 137 IMPORTS 138 MODULE-IDENTITY, OBJECT-TYPE, experimental, Counter32, 139 Gauge32, Unsigned32, TDomain, TAddress 140 FROM SNMPv2-SMI 141 MODULE-COMPLIANCE, OBJECT-GROUP 142 FROM SNMPv2-CONF 143 TEXTUAL-CONVENTION, TimeStamp, TruthValue 144 FROM SNMPv2-TC; 146 agentxMIB MODULE-IDENTITY 147 LAST-UPDATED "9804141200Z" -- April 14, 1998 148 ORGANIZATION "IETF AgentX Working Group" 149 CONTACT-INFO 150 "WG-email: agentx@peer.com 151 Subscribe: agentx-request@peer.com 152 http://www.ietf.org/html.charters/agentx-charter.html 154 Chair: Bob Natale 155 ACE*COMM Corporation 156 Email: bnatale@acec.com 158 Editor: Smitha Gudur 159 BMC Software, Inc. 160 965 Stewart Drive 161 Sunnyvale, CA 94086 162 Phone: +1 408-616-3100 163 Email: sgudur@bmc.com 164 " 165 DESCRIPTION 166 "This is the MIB module for the SNMP Agent Extensibility 167 Protocol (AgentX). This MIB module will be implemented by 168 the master agent." 169 -- For testing purposes only. Need to get an experimental id 170 ::= { experimental 2001 } 172 agentxObjects OBJECT IDENTIFIER ::= { agentxMIB 1 } 174 -- 175 -- Define the four groups that serve to organize the 176 -- objects in this MIB 177 -- 178 agentxGeneral OBJECT IDENTIFIER ::= { agentxObjects 1 } 179 agentxConnection OBJECT IDENTIFIER ::= { agentxObjects 2 } 180 agentxSession OBJECT IDENTIFIER ::= { agentxObjects 3 } 181 agentxRegistration OBJECT IDENTIFIER ::= { agentxObjects 4 } 182 agentxTCPDomain OBJECT IDENTIFIER ::= {agentxObjects 5} 184 -- 185 -- Textual Conventions 186 -- 187 Utf8String ::= TEXTUAL-CONVENTION 188 DISPLAY-HINT "255a" 189 STATUS current 190 DESCRIPTION 191 "To facilitate internationalization, this TC represents 192 information taken from the ISO/IEC IS 10646-1 character set, 193 encoded as an octet string using the UTF-8 character encoding 194 scheme described in RFC 2044 [8]. For strings in 7-bit US-ASCII, 195 there is no impact since the UTF-8 representation is identical 196 to the US-ASCII encoding." 197 SYNTAX OCTET STRING (SIZE (0..255)) 199 AgentxTCPAddress ::= TEXTUAL-CONVENTION 200 DISPLAY-HINT "1d.1d.1d.1d/2d" 201 STATUS current 202 DESCRIPTION "Represents a TCP Address." 203 SYNTAX OCTET STRING (SIZE (6)) 205 agentxDefaultTimeout OBJECT-TYPE 206 SYNTAX INTEGER (0..255) 207 UNITS "seconds" 208 MAX-ACCESS read-write 209 STATUS current 210 DESCRIPTION 211 "The default length of time, in seconds, that the master agent 212 should allow to elapse after dispatching a message to a subagent 213 before it regards the subagent as not responding. This is a 214 system-wide value that may be overridden by the values 215 associated with a particular subagent (agentxSessionTimeout) or a 216 particular registered MIB region (agentxRegTimeout)." 217 DEFVAL { 5 } 218 ::= { agentxGeneral 1 } 220 agentxMasterAgentXVer OBJECT-TYPE 221 SYNTAX INTEGER (1..255) 222 MAX-ACCESS read-only 223 STATUS current 224 DESCRIPTION 225 "The AgentX protocol version supported by this master 226 agent. Current version is 1. Note that the master agent must 227 allow registration of earlier version subagents." 229 DEFVAL { 1 } 230 ::= { agentxGeneral 2 } 232 -- 233 -- The Agentx Subagent Connection Group 234 -- 235 agentxConnTableLastChange OBJECT-TYPE 236 SYNTAX TimeStamp 237 MAX-ACCESS read-only 238 STATUS current 239 DESCRIPTION 240 "The value of sysUpTime when the last row creation or deletion 241 occurred in the agentxConnectionTable." 242 ::= { agentxConnection 1 } 244 agentxConnNumber OBJECT-TYPE 245 SYNTAX Gauge32 246 MAX-ACCESS read-only 247 STATUS current 248 DESCRIPTION 249 "The current number of entries in the agentxConnectionTable. Note 250 that this may be smaller than the largest value of agentxConnIndex 251 since index values are not reused when entries come and go from 252 the agentxConnectionTable." 253 ::= { agentxConnection 2 } 255 agentxConnectionTable OBJECT-TYPE 256 SYNTAX SEQUENCE OF AgentxConnectionEntry 257 MAX-ACCESS not-accessible 258 STATUS current 259 DESCRIPTION 260 "The agentxConnectionTable tracks all current Agentx transport 261 connections. There may be zero, one, or more agentx sessions 262 on a given Agentx connection." 263 ::= { agentxConnection 3 } 265 AgentxConnectionEntry ::= SEQUENCE { 266 agentxConnIndex Unsigned32, 267 agentxConnOpenTime TimeStamp, 268 agentxConnTransportDomain TDomain, 269 agentxConnTransportAddress TAddress, 270 agentxConnSessions Gauge32 } 272 agentxConnectionEntry OBJECT-TYPE 273 SYNTAX AgentxConnectionEntry 274 MAX-ACCESS not-accessible 275 STATUS current 276 DESCRIPTION 277 "An agentxConnectionEntry contains information describing a 278 single Agentx transport connection. A connection may be 279 used to support zero or more Agentx sessions. Entries come 280 into being when the transport connection is established, 281 and are not deleted unless the transport connection has 282 been terminated." 283 INDEX { agentxConnIndex } 284 ::= { agentxConnectionTable 1 } 286 agentxConnIndex OBJECT-TYPE 287 SYNTAX Unsigned32 288 MAX-ACCESS not-accessible 289 STATUS current 290 DESCRIPTION 291 "The value of agentxConnIndex uniquely identifies each 292 open transport connection used by this master agent 293 to provide AgentX service. Values of this index should 294 not be re-used. The value assigned to a given transport 295 connection is constant for the lifetime of that connection." 296 ::= { agentxConnectionEntry 1 } 298 agentxConnOpenTime OBJECT-TYPE 299 SYNTAX TimeStamp 300 MAX-ACCESS read-only 301 STATUS current 302 DESCRIPTION 303 "The value of sysUpTime when this connection was established 304 and, therefore, its value when this entry was added to the table." 305 ::= { agentxConnectionEntry 2 } 307 agentxConnTransportDomain OBJECT-TYPE 308 SYNTAX TDomain 309 MAX-ACCESS read-only 310 STATUS current 311 DESCRIPTION 312 "The transport protocol in use for this connection to the 313 master agent." 314 ::= { agentxConnectionEntry 3 } 316 agentxConnTransportAddress OBJECT-TYPE 317 SYNTAX TAddress 318 MAX-ACCESS read-only 319 STATUS current 320 DESCRIPTION 321 "The transport address of the remote (subagent) end of this 322 connection to the master agent." 323 ::= { agentxConnectionEntry 4 } 325 agentxConnSessions OBJECT-TYPE 326 SYNTAX Gauge32 327 MAX-ACCESS read-only 328 STATUS current 329 DESCRIPTION 330 "The current number of AgentX sessions being carried by 331 this transport connection. For purposes of this MIB, 332 an AgentX session begins when a valid agentx-Open-PDU is 333 received, and ends when a corresponding agentx-Close-PDU 334 has been sent or received by the master agent." 335 ::= { agentxConnectionEntry 5 } 337 -- 338 -- The AgentX Subagent Session Group 339 -- 340 agentxSessionTableLastChange OBJECT-TYPE 341 SYNTAX TimeStamp 342 MAX-ACCESS read-only 343 STATUS current 344 DESCRIPTION 345 "The value of sysUpTime when the last row creation or deletion 346 occurred in the agentxSessionTable." 347 ::= { agentxSession 1 } 349 agentxSessionNumber OBJECT-TYPE 350 SYNTAX Gauge32 351 MAX-ACCESS read-only 352 STATUS current 353 DESCRIPTION 354 "The current number of entries in the 355 agentxSessionTable. Note that this may be smaller than 356 the largest value of agentxSessionIndex since index 357 values are not reused when entries come and go from the 358 agentxSessionTable." 359 ::= { agentxSession 2 } 361 -- 362 -- The AgentX Subagent Session Table 363 -- 364 agentxSessionTable OBJECT-TYPE 365 SYNTAX SEQUENCE OF AgentxSessionEntry 366 MAX-ACCESS not-accessible 367 STATUS current 368 DESCRIPTION 369 "A table of AgentX subagents that have open sessions with the 370 AgentX master agent." 371 ::= { agentxSession 3 } 373 agentxSessionEntry OBJECT-TYPE 374 SYNTAX AgentxSessionEntry 375 MAX-ACCESS not-accessible 376 STATUS current 377 DESCRIPTION 378 "Information about a single open session between the AgentX 379 master agent and a subagent." 380 INDEX { agentxConnIndex, agentxSessionIndex } 381 ::= { agentxSessionTable 1 } 383 AgentxSessionEntry ::= SEQUENCE { 384 agentxSessionIndex Unsigned32, 385 agentxSessionObjectID OBJECT IDENTIFIER, 386 agentxSessionDescr Utf8String, 387 agentxSessionAdminStatus INTEGER, 388 agentxSessionOpenTime TimeStamp, 389 agentxSessionAgentXVer INTEGER, 390 agentxSessionTimeout INTEGER 391 } 393 agentxSessionIndex OBJECT-TYPE 394 SYNTAX Unsigned32 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "A unique index for the subagent session. Note that if a 399 subagent's session with the master agent is closed for 400 any reason its index should not be re-used, therefore, 401 the values of agentxSessionIndex may not be contiguous and 402 will generally not be the same for the same subagent 403 across multiple sessions. Index values assigned for 404 a given registration are constant for the lifetime of 405 this table." 406 ::= { agentxSessionEntry 1 } 408 agentxSessionObjectID OBJECT-TYPE 409 SYNTAX OBJECT IDENTIFIER 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "This is analogous to sysObjectID defined in MIB-2 [2] and is taken 414 from the o.id field of the agentx-Open-PDU." 415 ::= { agentxSessionEntry 2 } 417 -- 418 -- Issue: should we describe this more in terms of AGENT-CAPABILITIES 419 -- or sysORTable? 420 -- 421 agentxSessionDescr OBJECT-TYPE 422 SYNTAX Utf8String 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "A textual description of the subagent. This is analogous to 427 sysDescr defined in MIB-2 [2] and is taken from the o.descr 428 field of the agentx-Open-PDU." 429 ::= { agentxSessionEntry 3 } 431 agentxSessionAdminStatus OBJECT-TYPE 432 SYNTAX INTEGER { 433 up(1), 434 down(2) 435 } 436 MAX-ACCESS read-write 437 STATUS current 438 DESCRIPTION 439 "The administrative (desired) status of the subagent. Setting 440 the value to 'down(2)' closes the subagent session (with c.reason 441 set to 'reasonByManager'). When read, the value returned is always 442 'up(1)'." 443 DEFVAL { up } 444 ::= { agentxSessionEntry 4 } 446 agentxSessionOpenTime OBJECT-TYPE 447 SYNTAX TimeStamp 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The value of sysUpTime when this session was opened and, 452 therefore, its value when this entry was added to the table." 453 ::= { agentxSessionEntry 5 } 455 agentxSessionAgentXVer OBJECT-TYPE 456 SYNTAX INTEGER (1..255) 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The version of the AgentX protocol supported by the 461 subagent. This will be less than or equal to the value of 462 agentxMasterAgentXVer." 463 DEFVAL { 1 } 464 ::= { agentxSessionEntry 6 } 466 agentxSessionTimeout OBJECT-TYPE 467 SYNTAX INTEGER (0..255) 468 UNITS "seconds" 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "The length of time, in seconds, that a master agent should 473 allow to elapse after dispatching a message to this subagent 474 before it regards the subagent as not responding. This value is 475 taken from the o.timeout field of the agentx-Open-PDU. 477 This is a subagent-specific value that may be overridden by 478 values associated with specific registered MIB regions (see 479 agentxRegTimeout). The default value of '0' indicates that the 480 master agent's default timeout value should be used (see 481 agentxDefaultTimeout)." 482 DEFVAL { 0 } 483 ::= { agentxSessionEntry 7 } 485 -- 486 -- The AgentX Registration Information group 487 -- 488 -- The statistics in this group are maintained by the Master Agent. 489 -- 490 -- Other stats have been removed. Support trap generation based 491 -- on certain situations for duplicate registration. 492 -- 493 agentxRegisterDuplicate OBJECT-TYPE 494 SYNTAX Counter32 495 MAX-ACCESS read-only 496 STATUS current 497 DESCRIPTION 498 "The number of agentx-Response-PDU messages sent by this master 499 agent where the res.error field was set to 'duplicateRegistration'." 500 ::= { agentxRegistration 1 } 502 -- 503 -- The AgentX Registration Table 504 -- 506 agentxRegistrationTable OBJECT-TYPE 507 SYNTAX SEQUENCE OF AgentxRegistrationEntry 508 MAX-ACCESS not-accessible 509 STATUS current 510 DESCRIPTION 511 "A table of registered OBJECT IDENTIFIER regions. This is the 512 table used to identify a registered region of a subagent. 513 Note that a subagent registration may be broken up into multiple 514 entries in this table, as described in the AgentX Protocol 515 specification [5]." 516 ::= { agentxRegistration 2 } 518 agentxRegistrationEntry OBJECT-TYPE 519 SYNTAX AgentxRegistrationEntry 520 MAX-ACCESS not-accessible 521 STATUS current 522 DESCRIPTION 523 "A single registered region. Regions are added by the master 524 agent when subagents register and are removed from the table 525 when the subagents unregister the region or their sessions are 526 closed. Note that the combination of agentxRegContext, 527 agentxRegStart and agentxRegDispatchOrder will be unique and 528 could have been used for indexing purposes, but would have 529 potentially resulted in excessively long OBJECT IDENTIFIERs." 530 INDEX { agentxConnIndex, agentxSessionIndex, agentxRegIndex } 531 ::= { agentxRegistrationTable 1 } 533 AgentxRegistrationEntry ::= SEQUENCE { 534 agentxRegIndex Unsigned32, 535 agentxRegContext OCTET STRING, 536 agentxRegStart OBJECT IDENTIFIER, 537 agentxRegEnd OBJECT IDENTIFIER, 538 agentxRegPriority Unsigned32, 539 agentxRegTimeout INTEGER, 540 agentxRegInstance TruthValue 541 } 543 agentxRegIndex OBJECT-TYPE 544 SYNTAX Unsigned32 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "AgentxRegIndex is an integer that uniquely identifies a 549 registration entry. Its value is constant for the lifetime 550 of an entry." 551 ::= { agentxRegistrationEntry 1 } 553 agentxRegContext OBJECT-TYPE 554 SYNTAX OCTET STRING 555 MAX-ACCESS read-only 556 STATUS current 557 DESCRIPTION 558 "The context in which the subagent supports the objects in this 559 region. A zero-length context indicates the default context." 560 ::= { agentxRegistrationEntry 2 } 562 agentxRegStart OBJECT-TYPE 563 SYNTAX OBJECT IDENTIFIER 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "The starting OBJECT IDENTIFIER of this registration entry. The 568 subagent identified by agentxSessionIndex implements objects 569 starting at this value (inclusive). Note that this value could 570 identify an object type, an object instance, or a partial object 571 instance." 572 ::= { agentxRegistrationEntry 3 } 574 agentxRegEnd OBJECT-TYPE 575 SYNTAX OBJECT IDENTIFIER 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 "The ending OBJECT IDENTIFIER of this registration entry. The 580 subagent identified by agentxSessionIndex implements 581 objects up to but not including this value. Note that this 582 value could identify an object type, an object instance, 583 or a partial object instance." 584 ::= { agentxRegistrationEntry 4 } 586 -- 587 -- To support other subagent types that can be visible 588 -- to the manager. 589 -- 590 agentxRegPriority OBJECT-TYPE 591 SYNTAX Unsigned32 592 MAX-ACCESS read-only 593 STATUS current 594 DESCRIPTION 595 "The subagent's priority when exporting this OID range. Lower 596 values have higher priority." 597 DEFVAL { 255 } 598 ::= { agentxRegistrationEntry 5 } 600 agentxRegTimeout OBJECT-TYPE 601 SYNTAX INTEGER (0..255) 602 UNITS "seconds" 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 606 "The timeout value, in seconds, for subagent responses to 607 requests associated with this OID range. The value '0' indicates 608 that the default value (indicated by agentxSessionTimeout or 609 agentxDefaultTimeout) is to be used. This value is taken from 610 the r.timeout field of the agentx-Register-PDU." 611 DEFVAL { 0 } 612 ::= { agentxRegistrationEntry 7 } 614 agentxRegInstance OBJECT-TYPE 615 SYNTAX TruthValue 616 MAX-ACCESS read-only 617 STATUS current 618 DESCRIPTION 619 "The value of agentxRegInstance is `true' for 620 registrations for which the INSTANCE_REGISTRATION 621 was set, and is `false' for all other registrations." 622 DEFVAL { false } 623 ::= { agentxRegistrationEntry 8 } 625 -- 626 -- Conformance Statements for the AgentX MIB 627 -- 629 agentxConformance OBJECT IDENTIFIER ::= { agentxMIB 2 } 630 agentxMIBGroups OBJECT IDENTIFIER ::= { agentxConformance 1 } 631 agentxMIBCompliances OBJECT IDENTIFIER ::= { agentxConformance 2 } 633 agentxMIBCompliance MODULE-COMPLIANCE 634 STATUS current 635 DESCRIPTION 636 "The compliance statement for SNMP entities that implement the 637 AgentX protocol. Note that a compliant agent can implement all 638 objects in this MIB module as read-only." 640 MODULE -- this module 641 MANDATORY-GROUPS { agentxMIBGroup } 643 OBJECT agentxDefaultTimeout 644 MIN-ACCESS read-only 645 DESCRIPTION 646 "Write access is not required." 648 OBJECT agentxSessionAdminStatus 649 MIN-ACCESS read-only 650 DESCRIPTION 651 "Write access is not required." 653 ::= { agentxMIBCompliances 1 } 655 agentxMIBGroup OBJECT-GROUP 656 OBJECTS { 657 agentxDefaultTimeout, 658 agentxMasterAgentXVer, 659 agentxConnTableLastChange, 660 agentxConnNumber, 661 agentxConnOpenTime, 662 agentxConnTransportDomain, 663 agentxConnTransportAddress, 664 agentxConnSessions, 665 agentxSessionTableLastChange, 666 agentxSessionNumber, 667 agentxSessionTimeout, 668 agentxSessionObjectID, 669 agentxSessionDescr, 670 agentxSessionAdminStatus, 671 agentxSessionOpenTime, 672 agentxSessionAgentXVer, 673 agentxRegisterDuplicate, 674 agentxRegContext, 675 agentxRegStart, 676 agentxRegEnd, 677 agentxRegPriority, 678 agentxRegTimeout, 679 agentxRegInstance 680 } 681 STATUS current 682 DESCRIPTION 683 "All accessible objects in the AgentX MIB." 684 ::= { agentxMIBGroups 1 } 686 END 688 5. Acknowledgments 690 This document is a product of the IETF's AgentX Working Group. 692 Special acknowledgement is made to: 694 Maria Greene 695 Xedia 696 119 Russell Street, Littleton MA 01460 697 USA 699 Phone: +1 978-952-6000 700 EMail: maria@xedia.com 702 This MIB is an evolution of the Subagent MIB by Bert Wijnen 703 (wijnen@vnet.ibm.com) which in turn was derived from the SMUX-MIB by 704 Marshall Rose [6]. 706 6. References 708 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 709 S. Waldbusser, "Structure of Management Information for Version 2 710 of the Simple Network Management Protocol (SNMPv2)", RFC1902, SNMP 711 Research,Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 712 International Network Services, January 1996. 714 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 715 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 716 RFC 1213, Hughes LAN Systems, Performance Systems International, 717 March 1991. 719 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 720 Management Protocol", RFC 1157, SNMP Research, Performance Systems 721 International, Performance Systems International, MIT Laboratory 722 for Computer Science, May 1990. 724 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 725 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 726 Network Management Protocol (SNMPv2)", RFC1905, SNMP Research,Inc., 727 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 728 Network Services, January 1996. 730 [5] Daniele, M., Wijnen, B., and D. Francisco, "Agent Extensibility 731 (AgentX) Protocol, Version 1", draft-ietf-agentx-ext-pro-02.txt, 732 Digital Equipment Corporation, T.J. Watson Research Center, IBM 733 Corp., Cisco Systems, November, 1996. 735 [6] Rose, M., "SNMP MUX Protocol and MIB", RFC1227, Performance Systems 736 International, Inc., May 1991. 738 [7] Wijnen, B., Carpenter, G., Curran, K., Sehgal, A., and G. Waters, 739 "Simple Network Management Protocol: Distributed Protocol 740 Interface, Version 2.0", RFC 1592, T.J. Watson Research Center, IBM 741 Corp., Bell Northern Research, Ltd., March 1994. 743 [8] F. Yergeau, "UTF-8, a transformation format of Unicode and ISO 744 10646,", RFC 2044, October 1996. 746 7. Security Considerations 747 In most cases, MIBs are not themselves security risks; if SNMP 748 security is operating as intended, the use of a MIB to view 749 information about a system, or to change some parameter at the 750 system, is a tool, not a threat. 752 None of the read-only objects in this MIB reports a password, user data, 753 or anything else that is particularly sensitive. If access to these 754 objects is not limited by an appropriate access control policy, these 755 objects can provide an attacker with information about a system's 756 configuration and the services that that system is providing. Some 757 enterprises view their network and system configurations themselves, as 758 well as information about usage and performance, as corporate assets; 759 such enterprises may wish to restrict SNMP access to most of the objects 760 in the MIB. 762 This MIB contains two read-write objects: agentxDefaultTimeout and 763 agentxSessionAdminStatus. Setting agentxDefaultTimeout to an 764 inappropriately small value can prevent new subagent sessions from being 765 usable. Setting agentxSessionAdminStatus to an inappropriate value can 766 effectively prevent access to management information, or provide access 767 to inappropriate information. Since changes to either of these objects 768 can adversely impact the manageability of a system, write access to 769 these objects should be subject to an appropriate access control policy. 770 Such a policy may be realized in an implementation by limiting support 771 for these objects to read-only access. 773 8. Editor's Address 775 Smitha Gudur 776 BMC Software, Inc. 777 965 Stewart Drive 778 Sunnyvale, CA 94086 779 USA 780 Phone: +1 408-616-3100 781 EMail: sgudur@bmc.com 783 9. Full Copyright Statement 785 Copyright (C) The Internet Society (1997). All Rights Reserved. 787 This document and translations of it may be copied and furnished to 788 others, and derivative works that comment on or otherwise explain it or 789 assist in its implmentation may be prepared, copied, published and 790 distributed, in whole or in part, without restriction of any kind, 791 provided that the above copyright notice and this paragraph are included 792 on all such copies and derivative works. However, this document itself 793 may not be modified in any way, such as by removing the copyright notice 794 or references to the Internet Society or other Internet organizations, 795 except as needed for the purpose of developing Internet standards in 796 which case the procedures for copyrights defined in the Internet 797 Standards process must be followed, or as required to translate it into 798 languages other than English. 800 The limited permissions granted above are perpetual and will not be 801 revoked by the Internet Society or its successors or assigns. 803 This document and the information contained herein is provided on an "AS 804 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 805 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 806 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 807 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 808 FITNESS FOR A PARTICULAR PURPOSE.