idnits 2.17.1 draft-ietf-snanau-dlurmib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 10 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (November 19, 1996) is 10013 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 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '3') (Obsoleted by RFC 2580) -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Non-RFC (?) normative reference: ref. '5' Summary: 14 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects 3 for DLUR 5 November 19, 1996 7 Bob Clouston (editor) 8 Cisco Systems 9 clouston@cisco.com 11 Bob Moore (editor) 12 IBM Corporation 13 remoore@ralvm6.vnet.ibm.com 15 17 1. Status of this Memo 19 This document is an Internet-Draft. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, and 21 its working groups. Note that other groups may also distribute working 22 documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months. 25 Internet-Drafts may be updated, replaced, or obsoleted by other 26 documents at any time. It is not appropriate to use Internet-Drafts as 27 reference material or to cite them other than as a working draft or work 28 in progress. 30 To learn the current status of any Internet-Draft, please check the 31 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 32 Directories on ds.internic.net, nic.nordu.net, ftp.isi.edu, or 33 munnari.oz.au. 35 2. Introduction 37 This memo defines a portion of the Management Information Base (MIB) for 38 use with network management protocols in the Internet community. In 39 particular, it defines objects for monitoring and controlling network 40 devices with DLUR (Dependent LU Requester) capabilities. This memo 41 identifies managed objects for the DLUR protocol. 43 This memo does not specify a standard for the Internet community. 45 3. The SNMP Network Management Framework 47 The SNMP Network Management Framework consists of several components. 48 For the purpose of this specification, the applicable components of the 49 Framework are the SMI and related documents [1, 2, 3], which define the 50 mechanisms used for describing and naming objects for the purpose of 51 management. 53 The Framework permits new objects to be defined for the purpose of 54 experimentation and evaluation. 56 4. Overview 58 This document identifies the proposed set of objects for monitoring the 59 configuration and active characteristics of devices with DLUR 60 capabilities. Dependent LU requester/server (DLUR/S) is an extension to 61 the Advanced Peer-to-Peer Networking (APPN) architecture that provides 62 dependent LU services in APPN networks. See the SNANAU APPN MIB [4] for 63 management of APPN networks. 65 The base APPN architecture only provided for transport of data between 66 independent logical units (LUs). However, customers have an enormous 67 investment in applications based on dependent LU types. DLUR/S provides 68 for support of dependent LU sessions in an APPN network. 70 A dependent LU server (DLUS) is an APPN node that provides System 71 Services Control Point (SSCP) services over an APPN network to remote 72 secondary dependent LUs by using SSCP-PU and SSCP-LU sessions whose 73 flows are encapsulated on LU 6.2 session flows between the DLUS node and 74 the appropriate dependent LU requester (DLUR) node. The secondary 75 dependent LUs may be local to the DLUR node, or in adjacent type 2.0 or 76 2.1 nodes. 78 The LU 6.2 control sessions between a DLUS node and a DLUR node are 79 referred to as a CPSVRMGR pipe. CPSVRMGR refers to the mode used for 80 the sessions. 82 In this document, we describe DLUR managed objects. 84 The DLUR terms and overall architecture are described in [5]. 86 Highlights of the management functions supported by the DLUR MIB module 87 include the following: 89 o Identifying the node's DLUR capabilities 91 o Displaying the physical units (PUs) this node is supporting 93 o Identification of Dependent LU Servers 95 o Displaying the state of control sessions to Dependent LU Servers. 97 This MIB module does not support: 99 o Management of dependent LU servers 101 o Configuration of DLUR nodes. 103 o Changing the state of control session to the DLUS 105 o Displaying the dependent LUs this node is supporting 107 o Traps. The APPN MIB contains a trap for Alert conditions that may 108 affect DLUR resources. 110 4.1. DLUR MIB Structure 112 The DLUR MIB module contains the following groups of objects: 114 o dlurNodeInfo--objects representing the capabilities and 115 architecture options supported by the DLUR implementation, as well 116 as default primary and backup DLUSs. 118 o dlurPuInfo--objects describing the PUs that this APPN node is 119 supporting with DLUR. 121 o dlurDlusInfo--objects describing the control sessions with DLUSs. 123 These groups are described below in more detail. 125 4.1.1. dlurNodeInfo group 127 The dlurNodeInfo group consists of the following objects and table: 129 1) dlurNodeCapabilities group 131 These objects represent the capabilities and options of the DLUR 132 implementation, such as the release level of the implementation 134 2) dlurDefaultDefBackupDlusTable 136 This group identifies the list of defined backup DLUSs for all PUs 137 served by this DLUR, if there is no specific DLUS backup list for the 138 PU. The list is in descending order of preference as a backup DLUS. 140 4.1.2. dlurPuInfo group 142 The dlurPuInfo group consists of the following table 144 1) dlurPuTable 146 This table has an entry for each PU this node is supporting via DLUR, 147 including the locally known name, the SSCP supplied name (if known), and 148 the PU status. 150 4.1.3. dlurDlusInfo group 152 This group consists of the following table: 154 1) dlurDlusTable 156 This table contains information about the control sessions (CPSVRMGR 157 pipes) with the DLUS, including the control point (CP) name of the DLUS 158 and the status of the control session. 160 5. Definitions 162 APPN-DLUR-MIB DEFINITIONS ::= BEGIN 164 IMPORTS 165 DisplayString, TruthValue, TEXTUAL-CONVENTION 166 FROM SNMPv2-TC 168 OBJECT-TYPE, MODULE-IDENTITY 169 FROM SNMPv2-SMI 171 MODULE-COMPLIANCE, OBJECT-GROUP 172 FROM SNMPv2-CONF 174 snanauMIB 175 FROM SNA-NAU-MIB 177 SnaControlPointName 178 FROM APPN-MIB; 180 dlurMIB MODULE-IDENTITY 181 LAST-UPDATED "9611190000Z" 182 ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN/HPR MIBs SIG" 183 CONTACT-INFO 185 " 186 Bob Clouston 187 Cisco Systems 188 7025 Kit Creek Road 189 P.O. Box 14987 190 Research Triangle Park, NC 27709, USA 191 Tel: 1 919 472 2333 192 E-mail: clouston@cisco.com 194 Bob Moore 195 IBM Corporation 196 800 Park Offices Drive 197 RHJA/664 198 P.O. Box 12195 199 Research Triangle Park, NC 27709, USA 200 Tel: 1 919 254 4436 201 E-mail: remoore@ralvm6.vnet.ibm.com 202 " 203 DESCRIPTION 204 "This is the MIB module for objects used to manage 205 network devices with DLUR capabilities. This MIB 206 contains information that is useful for managing an APPN 207 product that implements a DLUR (Dependent Logical Unit 208 Requester). The DLUR product has a client/server 209 relationship with an APPN product that implements a DLUS 210 (Dependent Logical Unit Server)." 212 ::= { snanauMIB 5 } 213 -- snanauMIB ::= { mib-2 34 } 215 -- ********************************************************************* 216 -- Textual Convention 217 -- --------------------------------------------------------------------- 218 -- SnaControlPointName is imported from the APPN MIB 220 -- ********************************************************************* 221 dlurObjects OBJECT IDENTIFIER ::= { dlurMIB 1 } 222 -- ********************************************************************* 224 dlurNodeInfo OBJECT IDENTIFIER ::= { dlurObjects 1 } 225 -- ********************************************************************* 226 -- DLUR Capabilities of the node 227 -- 228 -- This group represents the capabilities and options of the DLUR 229 -- implementation. 230 -- ********************************************************************* 231 dlurNodeCapabilities OBJECT IDENTIFIER ::= { dlurNodeInfo 1 } 233 dlurNodeCpName OBJECT-TYPE 234 SYNTAX SnaControlPointName 235 MAX-ACCESS read-only 236 STATUS current 237 DESCRIPTION 238 "Administratively assigned network name for the APPN node where 239 this DLUR implementation resides. This object corresponds to 240 the appnNodeCpName object in the APPN MIB." 242 ::= { dlurNodeCapabilities 1 } 244 dlurReleaseLevel OBJECT-TYPE 245 SYNTAX DisplayString (SIZE (2)) 246 MAX-ACCESS read-only 247 STATUS current 248 DESCRIPTION 249 "The DLUR release level of this implementation. This is the 250 value that is encoded in the DLUR/DLUS Capabilites (CV 51). 252 To insure consistent display, this one-byte value is encoded 253 here as two displayable characters that are equivalent to a 254 hexadecimal display. For example, if the one-byte value as 255 encoded in CV51 is X'01', this object will contain the 256 displayable string '01'." 258 ::= { dlurNodeCapabilities 2 } 260 dlurAnsSupport OBJECT-TYPE 261 SYNTAX INTEGER { 262 continueOrStop(1), 263 stopOnly(2) 264 } 265 MAX-ACCESS read-only 266 STATUS current 267 DESCRIPTION 268 "Automatic Network Shutdown capability of this node. 270 - 'continueOrStop' indicates that the DLUR implementation 271 supports either ANS value (continue or stop) as 272 specified by the DLUS on ACTPU for each PU. 274 - 'stopOnly' indicates that the DLUR implementation only 275 supports the ANS value of stop. 277 ANS = continue means that the DLUR node will keep LU-LU 278 sessions active even if SSCP-PU and SSCP-LU control sessions 279 are interrupted. 281 ANS = stop means that LU-LU sessions will be interrupted when 282 the SSCP-PU and SSCP-LU sessions are interrupted." 284 ::= { dlurNodeCapabilities 3 } 286 dlurMultiSubnetSupport OBJECT-TYPE 287 SYNTAX TruthValue 288 MAX-ACCESS read-only 289 STATUS current 290 DESCRIPTION 291 "Indication of whether this DLUR implementation can support 292 CPSVRMGR sessions that cross NetId boundaries." 294 ::= { dlurNodeCapabilities 4 } 296 dlurDefaultDefPrimDlusName OBJECT-TYPE 297 SYNTAX SnaControlPointName 298 MAX-ACCESS read-only 299 STATUS current 300 DESCRIPTION 301 "The SNA name of the defined default primary DLUS for all of 302 the PUs served by this DLUR. This can be overridden for a 303 particular PU by a defined primary DLUS for that PU, 304 represented by the dlurPuDefPrimDlusName object." 306 ::= { dlurNodeCapabilities 5 } 308 -- ********************************************************************* 309 -- DLUR default defined backup DLUS table 310 -- ********************************************************************* 312 dlurDefaultDefBackupDlusTable OBJECT-TYPE 313 SYNTAX SEQUENCE OF DlurDefaultDefBackupDlusEntry 314 MAX-ACCESS not-accessible 315 STATUS current 316 DESCRIPTION 317 "This table contains an ordered list of defined backup DLUSs 318 for all of the PUs served by this DLUR. These can be 319 overridden for a particular PU by a list of defined backup 320 DLUSs for that PU, represented by the 321 dlurPuDefBackupDlusNameTable. Entries in this table are 322 ordered from most preferred backup DLUS to least preferred." 324 ::= { dlurNodeInfo 2 } 326 dlurDefaultDefBackupDlusEntry OBJECT-TYPE 327 SYNTAX DlurDefaultDefBackupDlusEntry 328 MAX-ACCESS not-accessible 329 STATUS current 330 DESCRIPTION 331 "This table is indexed by an arbitrary integer-valued index." 333 INDEX { dlurDefaultDefBackupDlusIndex } 335 ::= { dlurDefaultDefBackupDlusTable 1 } 337 DlurDefaultDefBackupDlusEntry ::= SEQUENCE { 338 dlurDefaultDefBackupDlusIndex INTEGER, 339 dlurDefaultDefBackupDlusName SnaControlPointName 340 } 342 dlurDefaultDefBackupDlusIndex OBJECT-TYPE 343 SYNTAX INTEGER (1..255) 344 MAX-ACCESS not-accessible 345 STATUS current 346 DESCRIPTION 347 "Index for this table." 349 ::= { dlurDefaultDefBackupDlusEntry 1 } 351 dlurDefaultDefBackupDlusName OBJECT-TYPE 352 SYNTAX SnaControlPointName 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "Fully qualified name of a default backup DLUS for PUs served 357 by this DLUR." 359 ::= { dlurDefaultDefBackupDlusEntry 2 } 361 -- ********************************************************************* 362 -- DLUR-unique Information about PUs 363 -- 364 -- The following table carries DLUR-unique information about the PUs 365 -- that this APPN node is supporting via DLUR. 366 -- ********************************************************************* 367 dlurPuInfo OBJECT IDENTIFIER ::= { dlurObjects 2 } 369 dlurPuTable OBJECT-TYPE 370 SYNTAX SEQUENCE OF DlurPuEntry 371 MAX-ACCESS not-accessible 372 STATUS current 373 DESCRIPTION 374 "DLUR-unique information about PUs supported by this DLUR." 376 ::= { dlurPuInfo 1 } 378 dlurPuEntry OBJECT-TYPE 379 SYNTAX DlurPuEntry 380 MAX-ACCESS not-accessible 381 STATUS current 382 DESCRIPTION 383 "Entry in table of DLUR-unique information about PUs" 385 INDEX { dlurPuName } 387 ::= { dlurPuTable 1 } 389 DlurPuEntry ::= SEQUENCE { 390 dlurPuName DisplayString, 391 dlurPuSscpSuppliedName DisplayString, 392 dlurPuStatus INTEGER, 393 dlurPuAnsSupport INTEGER, 394 dlurPuLocation INTEGER, 395 dlurPuLsName DisplayString, 396 dlurPuDlusSessnStatus INTEGER, 397 dlurPuActiveDlusName DisplayString, 398 dlurPuDefPrimDlusName DisplayString 399 } 401 dlurPuName OBJECT-TYPE 402 SYNTAX DisplayString (SIZE (1..17)) 403 MAX-ACCESS not-accessible 404 STATUS current 405 DESCRIPTION 406 "Locally administered name of the PU. If this object has the 407 same value as the snaPu20Name object in the SNANAU MIB, then 408 the two are identifying the same PU." 410 ::= { dlurPuEntry 1 } 412 dlurPuSscpSuppliedName OBJECT-TYPE 413 SYNTAX DisplayString (SIZE (0..17)) 414 MAX-ACCESS read-only 415 STATUS current 416 DESCRIPTION 417 "The SNA name of the PU. This value is supplied to a PU by the 418 SSCP that activated it. If a value has not been supplied, a 419 zero-length string is returned. If this object has the same 420 value as the snaNodeSscpSuppliedName object in the SNANAU MIB, 421 then the two are identifying the same PU." 423 ::= { dlurPuEntry 2 } 425 dlurPuStatus OBJECT-TYPE 426 SYNTAX INTEGER { 427 reset(1), 428 pendReqActpuRsp(2), 429 pendActpu(3), 430 pendActpuRsp(4), 431 active(5), 432 pendLinkact(6), 433 pendDactpuRsp(7), 434 pendInop(8), 435 pendInopActpu(9) 436 } 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "Status of the DLUR-support PU." 442 ::= { dlurPuEntry 3 } 444 dlurPuAnsSupport OBJECT-TYPE 445 SYNTAX INTEGER { 446 continue(1), 447 stop(2) 448 } 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The Automatic Network Shutdown (ANS) support configured for 453 this PU. This value (as configured by the network 454 administrator) is sent by DLUS with ACTPU for each PU. 456 - 'continue' means that the DLUR node will attempt to keep 457 LU-LU sessions active even if SSCP-PU and SSCP-LU 458 control sessions are interrupted. 460 - 'stop' means that LU-LU sessions will be interrupted 461 when the SSCP-PU and SSCP-LU sessions are interrupted." 463 ::= { dlurPuEntry 4 } 465 dlurPuLocation OBJECT-TYPE 466 SYNTAX INTEGER { 467 internal(1), 468 downstream(2) } 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "Location of the DLUR-support PU: 473 internal(1) - internal to the APPN node itself (no link) 474 downstream(2) - downstream of the APPN node (connected via 475 a link)." 477 ::= { dlurPuEntry 5 } 479 dlurPuLsName OBJECT-TYPE 480 SYNTAX DisplayString (SIZE (0..10)) 481 MAX-ACCESS read-only 482 STATUS current 483 DESCRIPTION 484 "Administratively assigned name of the link station through 485 which a downstream PU is connected to this DLUR. A zero-length 486 string is returned for internal PUs. If this object has the 487 same value as the appnLsName object in the APPN MIB, then the 488 two are identifying the same link station." 490 ::= { dlurPuEntry 6 } 492 dlurPuDlusSessnStatus OBJECT-TYPE 493 SYNTAX INTEGER { 494 reset(1), 495 pendingActive(2), 496 active(3), 497 pendingInactive(4) 498 } 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "Status of the control session to the DLUS identified in 503 dlurPuActiveDlusName. This is a combination of the separate 504 states for the contention-winner and contention-loser sessions: 506 reset(1) - none of the cases below 507 pendingActive(2) - either contention-winner session or 508 contention-loser session is pending active 509 active(3) - contention-winner and contention-loser 510 sessions are both active 511 pendingInactive(4) - either contention-winner session or 512 contention-loser session is pending 513 inactive - this test is made AFTER the 514 'pendingActive' test." 516 ::= { dlurPuEntry 7 } 518 dlurPuActiveDlusName OBJECT-TYPE 519 SYNTAX DisplayString (SIZE (0..17)) 520 MAX-ACCESS read-only 521 STATUS current 522 DESCRIPTION 523 "The SNA name of the active DLUS for this PU. If present, this 524 name follows the SnaControlPointName textual convention. A 525 zero-length string indicates that the PU does not currently 526 have an active DLUS." 528 ::= { dlurPuEntry 8 } 530 dlurPuDefPrimDlusName OBJECT-TYPE 531 SYNTAX DisplayString (SIZE (0..17)) 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "The SNA name of the defined primary DLUS for this PU, if one 536 has been defined. If present, this name follows the 537 SnaControlPointName textual convention. A zero-length string 538 indicates that no primary DLUS has been defined for this PU, in 539 which case the global default represented by the 540 dlurDefaultDefPrimDlusName object is used." 542 ::= { dlurPuEntry 9 } 544 -- ***************************************** 545 -- Defined backup DLUS table for a PU 546 -- ***************************************** 548 dlurPuDefBackupDlusTable OBJECT-TYPE 549 SYNTAX SEQUENCE OF DlurPuDefBackupDlusEntry 550 MAX-ACCESS not-accessible 551 STATUS current 552 DESCRIPTION 553 "This table contains an ordered list of defined backup DLUSs 554 for those PUs served by this DLUR that have their own defined 555 backup DLUSs. PUs that have no entries in this table use the 556 global default backup DLUSs for the DLUR, represented by the 557 dlurDefaultDefBackupDlusNameTable. Entries in this table are 558 ordered from most preferred backup DLUS to least preferred for 559 each PU." 561 ::= { dlurPuInfo 2 } 563 dlurPuDefBackupDlusEntry OBJECT-TYPE 564 SYNTAX DlurPuDefBackupDlusEntry 565 MAX-ACCESS not-accessible 566 STATUS current 567 DESCRIPTION 568 "This table is indexed by PU name and by an arbitrary integer- 569 valued index." 571 INDEX { dlurPuDefBackupDlusPuName, 572 dlurPuDefBackupDlusIndex } 574 ::= { dlurPuDefBackupDlusTable 1 } 576 DlurPuDefBackupDlusEntry ::= SEQUENCE { 577 dlurPuDefBackupDlusPuName DisplayString, 578 dlurPuDefBackupDlusIndex INTEGER, 579 dlurPuDefBackupDlusName SnaControlPointName 580 } 582 dlurPuDefBackupDlusPuName OBJECT-TYPE 583 SYNTAX DisplayString (SIZE (1..17)) 584 MAX-ACCESS not-accessible 585 STATUS current 586 DESCRIPTION 587 "Locally administered name of the PU. If this object has the 588 same value as the dlurPuName object, then the two are 589 identifying the same PU." 591 ::= { dlurPuDefBackupDlusEntry 1 } 593 dlurPuDefBackupDlusIndex OBJECT-TYPE 594 SYNTAX INTEGER (1..255) 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "Secondary index for this table." 600 ::= { dlurPuDefBackupDlusEntry 2 } 602 dlurPuDefBackupDlusName OBJECT-TYPE 603 SYNTAX SnaControlPointName 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "Fully qualified name of a backup DLUS for this PU." 609 ::= { dlurPuDefBackupDlusEntry 3 } 611 -- ********************************************************************* 612 -- DLUS Control Sessions (CPSVRMGR Pipes) 613 -- 614 -- This table contains information about DLUS control sessions, also 615 -- known as CPSVRMGR pipes. Although DLUR uses a pair of CPSVRMGR 616 -- sessions for communication, for the purpose of status, information 617 -- about these two sessions is combined to yield a single status for the 618 -- requester/server connection. 619 -- ********************************************************************* 620 dlurDlusInfo OBJECT IDENTIFIER ::= { dlurObjects 3 } 622 dlurDlusTable OBJECT-TYPE 623 SYNTAX SEQUENCE OF DlurDlusEntry 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "Information about DLUS control sessions." 629 ::= { dlurDlusInfo 1} 631 dlurDlusEntry OBJECT-TYPE 632 SYNTAX DlurDlusEntry 633 MAX-ACCESS not-accessible 634 STATUS current 635 DESCRIPTION 636 "This entry is indexed by the name of the DLUS." 638 INDEX { dlurDlusName } 640 ::= { dlurDlusTable 1 } 642 DlurDlusEntry ::= SEQUENCE { 643 dlurDlusName SnaControlPointName, 644 dlurDlusSessnStatus INTEGER 645 } 647 dlurDlusName OBJECT-TYPE 648 SYNTAX SnaControlPointName 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "The SNA name of a DLUS with which this DLUR currently has a 653 CPSVRMGR pipe established." 655 ::= { dlurDlusEntry 1 } 657 dlurDlusSessnStatus OBJECT-TYPE 658 SYNTAX INTEGER { 659 reset(1), 660 pendingActive(2), 661 active(3), 662 pendingInactive(4) 663 } 664 MAX-ACCESS read-only 665 STATUS current 666 DESCRIPTION 667 "Status of the CPSVRMGR pipe between the DLUR and this DLUS. 668 This is a combination of the separate states for the 669 contention-winner and contention-loser sessions: 671 reset(1) - none of the cases below 672 pendingActive(2) - either contention-winner session or 673 contention-loser session is pending active 674 active(3) - contention-winner and contention-loser 675 sessions are both active 676 pendingInactive(4) - either contention-winner session or 677 contention-loser session is pending 678 inactive - this test is made AFTER the 679 'pendingActive' test." 681 ::= { dlurDlusEntry 2 } 683 -- *************************************************************** 684 -- Conformance information 685 -- *************************************************************** 687 dlurConformance OBJECT IDENTIFIER ::= { dlurMIB 2 } 689 dlurCompliances OBJECT IDENTIFIER ::= { dlurConformance 1 } 690 dlurGroups OBJECT IDENTIFIER ::= { dlurConformance 2 } 692 -- Compliance statements 694 dlurCompliance MODULE-COMPLIANCE 695 STATUS current 696 DESCRIPTION 697 "The compliance statement for the SNMPv2 entities which 698 implement the DLUR MIB." 700 MODULE -- this module 702 -- Unconditionally mandatory groups 703 MANDATORY-GROUPS { dlurConfGroup } 705 ::= { dlurCompliances 1 } 707 -- Units of conformance 708 dlurConfGroup OBJECT-GROUP 709 OBJECTS { 710 dlurNodeCpName, 711 dlurReleaseLevel, 712 dlurAnsSupport, 713 dlurMultiSubnetSupport, 714 dlurDefaultDefPrimDlusName, 715 dlurDefaultDefBackupDlusName, 716 dlurPuSscpSuppliedName, 717 dlurPuStatus, 718 dlurPuAnsSupport, 719 dlurPuLocation, 720 dlurPuLsName, 721 dlurPuDlusSessnStatus, 722 dlurPuActiveDlusName, 723 dlurPuDefPrimDlusName, 724 dlurPuDefBackupDlusName, 725 dlurDlusSessnStatus 726 } 727 STATUS current 728 DESCRIPTION 729 "A collection of objects providing information on an 730 implementation of APPN DLUR." 732 ::= { dlurGroups 1 } 734 -- end of conformance statement 736 END 737 6. Acknowledgments 739 This MIB module is the product of the IETF SNA NAU MIB WG and the AIW 740 APPN/HPR MIBs SIG. 742 7. References 744 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 745 Waldbusser, "Structure of Management Information for version 2 of 746 the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 747 1996. 749 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 750 Waldbusser, "Textual Conventions for Version 2 of the Simple 751 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 753 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 754 Waldbusser, "Conformance Statements for Version 2 of the Simple 755 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 757 [4] Clouston, B., and B. Moore, "Definition of Managed Objects for 758 APPN", Cisco Systems, IBM Corporation, November 1996. 760 [5] IBM, Systems Network Architecture Advanced Peer-to-Peer Networking 761 Dependent LU Requester Architecture Reference, Version 1.2, 762 December 1995. 764 8. Security Considerations 766 Security issues are not discussed in this memo. 768 9. Authors' Addresses 770 Bob Clouston 771 Cisco Systems 772 7025 Kit Creek Road 773 P.O. Box 14987 774 Research Triangle Park, NC 27709, USA 776 Tel: 1 919 472 2333 777 E-mail: clouston@cisco.com 779 Bob Moore 780 IBM Corporation 781 800 Park Offices Drive 782 CNMA/664 783 P.O. Box 12195 784 Research Triangle Park, NC 27709, USA 786 Tel: 1 919 254 4436 787 E-mail: remoore@ralvm6.vnet.ibm.com 788 10. Table of Contents 790 1. Status of this Memo .................................... 1 791 2. Introduction ........................................... 1 792 3. The SNMP Network Management Framework .................. 2 793 4. Overview ............................................... 2 794 4.1 DLUR MIB structure .................................... 3 795 5. Definitions ............................................ 5 796 6. Acknowledgments ........................................ 18 797 7. References ............................................. 18 798 8. Security Considerations ................................ 19 799 9. Author's Addresses ..................................... 19