idnits 2.17.1 draft-ietf-snanau-ebnmib-01.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. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 21 longer pages, the longest (page 2) 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 60 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 93 has weird spacing: '...defines trans...' == Line 242 has weird spacing: '...BN1 is the R...' == Line 243 has weird spacing: '...uteInfo objec...' == Line 244 has weird spacing: '...2 also conta...' == Line 259 has weird spacing: '...ing the route...' == (9 more instances...) == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (February 1998) is 9567 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) ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (ref. '5') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 1907 (ref. '6') (Obsoleted by RFC 3418) ** Obsolete normative reference: RFC 1908 (ref. '7') (Obsoleted by RFC 2576) ** Obsolete normative reference: RFC 2155 (ref. '9') (Obsoleted by RFC 2455) -- Possible downref: Non-RFC (?) normative reference: ref. '10' -- Possible downref: Non-RFC (?) normative reference: ref. '11' Summary: 17 errors (**), 0 flaws (~~), 10 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 SNANAU Working Group Bob Clouston 2 INTERNET DRAFT: Cisco Systems 3 Expiration Date: August 1998 Bob Moore 4 IBM Corporation 5 February 1998 7 Definitions of Managed Objects 8 for Extended Border Node 9 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, and 15 its Working Groups. Note that other groups may also distribute working 16 documents as Internet Drafts. 18 Internet Drafts are draft documents valid for a maximum of six months. 19 Internet Drafts may be updated, replaced, or obsoleted by other 20 documents at any time. It is not appropriate to use Internet Drafts as 21 reference material or to cite them other than as a "working draft" or 22 "work in progress." 24 Please check the I-D abstract listing contained in each Internet Draft 25 directory to learn the current status of this or any Internet Draft. 26 Distribution of this document is unlimited. 28 Copyright Notice 30 Copyright (C) The Internet Society (1998). All Rights Reserved. 32 Abstract 34 This memo defines a portion of the Management Information Base (MIB) for 35 use with network management protocols in the Internet community. In 36 particular, it defines objects for monitoring and controlling network 37 devices with APPN (Advanced Peer-to-Peer Network) EBN (Extended Border 38 Node) capabilities. This memo identifies managed objects for the EBN 39 architecture. 41 This memo does not specify a standard for the Internet community. 43 Table of Contents 45 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 47 2.0 The SNMPv2 Network Management Framework . . . . . . . . . . . 2 48 3.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 3.1 EBN MIB Structure . . . . . . . . . . . . . . . . . . . . . . 4 50 3.1.1 enbDir group . . . . . . . . . . . . . . . . . . . . . . . 4 51 3.1.2 ebnIsRscv group . . . . . . . . . . . . . . . . . . . . . 5 52 3.1.3 ebnDirConfig group . . . . . . . . . . . . . . . . . . . . 7 53 3.1.4 ebnCos group . . . . . . . . . . . . . . . . . . . . . . . 7 54 3.1.5 ebnSubnetRoutingList group . . . . . . . . . . . . . . . . 7 55 3.1.6 hbn group . . . . . . . . . . . . . . . . . . . . . . . . 7 57 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 59 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 20 61 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 20 63 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 20 65 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 21 67 9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 21 69 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 22 71 1.0 Introduction 73 This document is a product of the SNA NAU Services MIB Working Group. 74 It defines a MIB module for managing devices with Advanced Peer-to-Peer 75 Networking (APPN) Extended Border Node (EBN) capabilities. 77 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 78 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 79 document are to be interpreted as described in RFC 2119, reference [8]. 81 2.0 The SNMPv2 Network Management Framework 83 The SNMPv2 Network Management Framework consists of seven major 84 components. They are: 86 o RFC 1902 [1] which defines the SMI, the mechanisms used for 87 describing and naming objects for the purpose of management. 89 o RFC 1903 [2] defines textual conventions for SNMPv2. 91 o RFC 1904 [3] defines conformance statements for SNMPv2. 93 o RFC 1905 [4] defines transport mappings for SNMPv2. 95 o RFC 1906 [5] defines the protocol operations used for network access 96 to managed objects. 98 o RFC 1907 [6] defines the Management Information Base for SNMPv2. 100 o RFC 1908 [7] specifies coexistence between SNMP and SNMPv2. 102 The Framework permits new objects to be defined for the purpose of 103 experimentation and evaluation. 105 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. A 106 semantically identical MIB conforming to the SNMPv1 SMI can be produced 107 through the appropriate translation. 109 3.0 Overview 111 This document identifies the proposed set of objects for monitoring the 112 configuration and active characteristics of devices with EBN 113 capabilities. The Extended Border Node function is an APPN enhancement 114 for an APPN network node (NN). It supports topology isolation, subnet 115 interconnection, and session establishment between subnets. 117 In a single APPN network, all network topology information is propagated 118 to all network nodes. Directory searches can also be forwarded to all 119 network nodes. As the network grows, this network traffic could become 120 prohibitive. Also, in networks where different enterprises are 121 connected via APPN, it may be desirable to shield an enterprise from the 122 network traffic of another enterprise. EBN allows customers to 123 partition a network into subnets to reduce or shield such network 124 traffic. 126 An EBN provides this function by blocking topology information exchange 127 between subnets, and controlling where directory searches are forwarded. 128 A subnetwork is a cluster of APPN NNs which share the same network 129 topology. Subnetwork boundaries, or partitions, occur where an EBN and 130 an NN adjacent to it have different network identifiers (NETIDs). They 131 may also occur where an EBN and adjacent NN have the same NETID but are 132 configured to have a subnetwork boundary. 134 The connection between two APPN nodes is an APPN transmission group 135 (TG). A TG at a subnet boundary is called an Intersubnetwork 136 Transmission Group (ISTG). 138 The subnet that the EBN resides in is called its native subnetwork. The 139 subnet across the subnet boundary is called the non-native subnetwork, 140 with respect to the EBN. 142 A cost of the EBN function is that customers may have difficulty 143 determining the end-to-end route of sessions that cross subnet 144 boundaries, and understanding how the EBN will control directory 145 searches between subnets. This MIB addresses these issues. 147 Another challenge facing customers is to identify subnet boundaries 148 formed by EBNs. The SNANAU APPN MIB [9] identifies subnet boundaries in 149 the appnNnTopology group. The SNANAU APPN MIB provides management of 150 APPN objects, and contains some tables which are extended by this MIB. 152 In this document, we describe EBN managed objects. 154 The EBN terms and overall architecture are available from the 155 networking.raleigh.ibm.com ftp site [10]. 157 Highlights of the management functions supported by the EBN MIB module 158 include the following: 160 o Identifying the subnet affiliation of LUs (logical units) 162 o Identifying session routes in non-native subnets, with correlation 163 to the route in the native subnet provided in the SNANAU APPN MIB. 165 o Identifying the COS (Class of Service) mappings between subnets. 167 o Identifying the subnet routing lists 169 This MIB module does not support: 171 o Configuration of EBN nodes. 173 o Historical information about session initiation failures. 175 o Peripheral Border Node (PBN) support. PBN is an APPN function that 176 only supports communication to adjacent subnetworks, and is not 177 expected to be widely implemented. 179 o Traps. The APPN MIB contains a trap for Alert conditions that may 180 affect EBN resources. Although no APPN/EBN Alerts are defined today 181 in [11], they could exist in the future. The value for the 182 affectedObject object contained in the alertTrap is determined by 183 the implementation. It may contain a VariablePointer from the EBN 184 MIB. 186 3.1 EBN MIB Structure 188 The EBN MIB module contains the following groups of objects: 190 o ebnDir - subnet information about LUs. 192 o ebnIsRscv - provides the RSCV (Route Selection Control Vector) and 193 COS for the subnetwork on the BIND destination side of the EBN. 195 o ebnDirConfig - objects related to the EBN directory. 197 o ebnCos - COS mapping between subnetworks, 199 o ebnSubnetRoutingList - the customer-supplied list of where to 200 forward search requests. 202 o hbn - HPR (High Performance Routing) EBN intermediate session 203 information. 205 These groups are described below in more detail. 207 3.1.1 enbDir group 208 The ebnDir group contains the ebnDirTable, which is an extension to the 209 appnDirTable. It specifies the subnet affiliation of LUs in the EBNs 210 directory. 212 3.1.2 ebnIsRscv group 214 The ebnIsRscv group contains the ebnIsRscvTable, which is an extension 215 to the appnIsInTable. The appnIsInTable only allows for the RSCV and 216 COS name for one subnetwork involved in the session. This extension 217 contains the RSCV and COS name for the other subnetwork. 219 When an EBN changes RSCVs before forwarding a BIND, appnIsInRouteInfo 220 contains the incoming RSCV, and ebnIsRscvDestinationRoute contains the 221 outgoing RSCV. 223 The following three cases illustrate the contents of appnIsInRouteInfo 224 and ebnIsRscvDestinationRoute at Extended Border Nodes. 226 1. EBN connected to another EBN 228 **subnet 1**|----ISTG -------|**subnet 2** 229 EBN1 EBN2 230 PLU SLU 231 ---------------------------->| 232 (1) |------------>| 233 (2) |-----------> 234 (3) 236 PLU = Primary Logical Unit (session initiator) 237 SLU = Secondary Logical Unit (session destination) 239 The value of appnIsInRouteInfo object at EBN1 is the RSCV 240 containing the route, represented by (1), from the PLU (or the entry 241 EBN in its subnet) to EBN2. The value of ebnIsRscvDestinationRoute 242 object at EBN1 is the RSCV, represented by (2), containing 243 the one-hop route from EBN1 to EBN2. The appnIsInRouteInfo object 244 at EBN2 also contains the RSCV represented by (2). The value 245 of ebnIsRscvDestinationRoute in EBN2 is the RSVC containing the 246 route to the SLU (or to the next subnet's entry EBN), represented 247 by (3). 249 2. EBN connected to a NN or PBN 251 **subnet 1**|----ISTG ------|**subnet 2** 252 EBN1 NN/PBN 253 PLU 254 --------------------------->| SLU 255 (1) |-----------------------------> 256 (2) 258 The value of the appnIsInRouteInfo object at EBN1 is the RSCV 259 containing the route from the PLU (or the entry EBN in its 260 subnet) to the NN or PBN, represented by (1). The value of the 261 ebnIsRscvDestinationRoute object at EBN1 is the RSCV containing 262 the route from EBN1 to the SLU, represented by (2). Note that the 263 SLU must be in subnet 2, because the entry node is an NN or PBN 264 rather than an EBN. The appnIsInRouteInfo object at NN/PBN contains 265 the same RSCV, as represented by (2). 267 3. NN or PBN connected to EBN 269 **subnet 1**|----ISTG -------|**subnet 2** 270 NN/PBN EBN1 271 PLU 272 -----------------------------| SLU 273 (1) |-----------> 274 (2) 276 The value of the appnIsInRouteInfo object at the NN/PBN is the 277 RSCV containing the route from the PLU to EBN1, represented by 278 (1). Note that the PLU must be in subnet 1, because the exit node 279 is an NN/PBN rather than an EBN. The appnIsInRouteInfo object 280 at EBN1 contains the same RSCV. The value of the 281 ebnIsRscvDestinationRoute object at EBN1 is the RSCV containing the 282 route from EBN1 to the SLU (or the next subnet's entry border node), 283 as represented by (2). 285 The following three cases illustrate the contents of 286 ebnIsRscvDestinationCos at Extended Border Nodes. 288 1. EBN connected to another EBN 290 **subnet 1**|----ISTG -------|**subnet 2** 291 EBN1 EBN2 292 PLU SLU 293 COS A 294 ----------------------------->| 295 COS B 296 |--------------> 298 PLU = Primary Logical Unit (session initiator) 299 SLU = Secondary Logical Unit (session destination) 301 The value of ebnIsRscvDestinationCos object at EBN1 is COS A. The 302 value of ebnIsRscvDestinationCos object at EBN2 is COS B. 304 2. EBN connected to a NN or PBN 306 **subnet 1**|----ISTG ------|**subnet 2** 307 EBN1 NN/PBN 308 PLU SLU 309 COS A 310 ------------>| 311 COS B 312 |---------------------------------> 314 The value of the ebvIsRscvDestinationCos object at EBN1 is COS B. 316 3. NN or PBN connected to EBN 317 **subnet 1**|----ISTG -------|**subnet 2** 318 NN/PBN EBN1 319 PLU SLU 320 COS A 321 ---------------------------->| 322 COS B 323 |-----------> 325 The value of the ebnIsRscvDestinationCos object at the EBN2 is COSB. 327 3.1.3 ebnDirConfig group 329 The ebnDirConfig group consists of simple objects that provide 330 EBN-specific information about directory caching and the local default 331 value for the maximum number of subnetworks a LOCATE search procedure 332 may traverse. 334 3.1.4 ebnCos group 336 The ebnCos group contains the ebnCosMapTable, which specifies how COS 337 values are mapped between the non-native subnetwork and the native 338 subnetwork. 340 3.1.5 ebnSubnetRoutingList group 342 The ebnSubnetRoutingList group contains information about the 343 customer-supplied EBN subnetwork routing list, which indicates to which 344 adjacent nodes an EBN will forward LOCATE search requests. It consists 345 of the following tables: 347 1. ebnSubnetSearchTable 349 This table has an entry for each LU name that has a defined subnet 350 routing list. The LU name may identify a single LU, or it may 351 contain a wildcard character that could identify a group of LUs 352 (partial wildcard) or all LUs (full wildcard). The objects in the 353 table indicate whether the EBN may add dynamic entries to the subnet 354 routing list, and whether the subnet routing list entries may be 355 reordered for better search performance. 357 2. ebnSearchTable 359 This table has an entry for each control point name which is 360 included in a multi-subnet search for a particular LU name. The 361 index to the table is the LU name to be searched for, and an index 362 which lists the order in which the CP names are to be searched. 363 Both the CP name and the LU name entries in the table allow for 364 partial and full wildcards. The CP name also allows for special 365 entries that indicate that the EBN will search itself and its own 366 native subnetwork at this point in the search, or will search all 367 native EBNs. 369 3.1.6 hbn group 370 The hbn group contains information about HBN (HPR EBN) intermediate 371 sessions. The hbnIsInTable is an extension to the appnIsInTable. This 372 table is present for intermediate sessions when there are back-to-back 373 RTP (Rapid Transport Protocol) connections in an HBN. It provides the 374 NCE ID (network connection endpoint identifier) and TCID (transport 375 connection identifier) for the second RTP connection. 377 4.0 Definitions 379 EBN-MIB DEFINITIONS ::= BEGIN 381 IMPORTS 382 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32 383 FROM SNMPv2-SMI 384 MODULE-COMPLIANCE, OBJECT-GROUP 385 FROM SNMPv2-CONF 386 DisplayString, TEXTUAL-CONVENTION 387 FROM SNMPv2-TC 388 SnaControlPointName 389 -- Because the characters allowed in an SNA control 390 -- point name come from a restricted character set, 391 -- these names are not subject to internationalization. 392 FROM APPN-MIB 393 snanauMIB 394 FROM SNA-NAU-MIB; 396 ebnMIB MODULE-IDENTITY 397 LAST-UPDATED "9709011200Z" 398 ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN MIBs SIG" 399 CONTACT-INFO 400 " 401 Bob Clouston 402 Cisco Systems 403 7025 Kit Creek Road 404 P.O. Box 14987 405 Research Triangle Park, NC 27709, USA 406 Tel: 1 919 472 2333 407 E-mail: clouston@cisco.com 409 Bob Moore 410 IBM Corporation 411 BRQA/501 412 P.O. Box 12195 413 Research Triangle Park, NC 27709, USA 414 Tel: 1 919 254 4436 415 E-mail: remoore@us.ibm.com 417 Katie D. Lee 418 IBM Corporation 419 RHJA/501 420 P.O. Box 12195 421 Research Triangle Park, NC 27709, USA 422 Tel: 1 919 254 7507 423 E-mail: kdlee@vnet.ibm.com 425 " 427 DESCRIPTION 428 " The MIB Module for Extended Border Node" 430 ::= { snanauMIB 7 } 431 -- snanauMIB ::= { mib-2 34 } 433 -- ******************************************************************* 434 -- Textual Conventions 435 -- --------------------------------------------------------------------- 436 SnaNAUWildcardName ::= TEXTUAL-CONVENTION 437 STATUS current 438 DESCRIPTION 439 "Fully-qualified network NAU name. Entries take one of three 440 forms: 441 - Explicit entries do not contain the character '*'. 442 - Partial Wildcard entries have the form 'ccc*', where 443 'ccc' represents one to sixteen characters in a legal 444 SNA NAU Name. 445 - A full wildcard consists of a single character '*'. 447 Because the characters allowed in an SNA NAU name come from 448 a restricted character set, these names are not subject to 449 internationalization." 451 SYNTAX DisplayString(SIZE(1..17)) 453 -- ******************************************************************* 454 ebnObjects OBJECT IDENTIFIER ::= { ebnMIB 1 } 455 -- ******************************************************************* 457 -- ******************************************************************* 458 -- EBN Directory Group 459 -- The ebnDirTable is an extension to the appnDirTable. It specifies 460 -- the subnet information about LUs in the EBN's directory. 461 -- ******************************************************************* 463 ebnDir OBJECT IDENTIFIER ::= { ebnObjects 1 } 465 ebnDirTable OBJECT-TYPE 466 SYNTAX SEQUENCE OF EbnDirEntry 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "The EBN Directory Table." 471 ::= { ebnDir 1} 473 ebnDirEntry OBJECT-TYPE 474 SYNTAX EbnDirEntry 475 MAX-ACCESS not-accessible 476 STATUS current 477 DESCRIPTION 478 "Entry in the EBN Directory Table." 480 INDEX { ebnDirLuName } 482 ::= { ebnDirTable 1 } 484 EbnDirEntry ::= SEQUENCE { 485 ebnDirLuName SnaNAUWildcardName, 486 ebnDirSubnetAffiliation INTEGER } 488 ebnDirLuName OBJECT-TYPE 489 SYNTAX SnaNAUWildcardName 490 MAX-ACCESS not-accessible 491 STATUS current 492 DESCRIPTION 493 "Fully qualified network LU name in the domain of the serving 494 network node." 496 ::= { ebnDirEntry 1 } 498 ebnDirSubnetAffiliation OBJECT-TYPE 499 SYNTAX INTEGER { native (1), 500 nonNative (2), 501 subarea (3) } 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "Specifies the subnetwork affiliation of the LU: 506 - native(1) : The LU is in the native APPN subnetwork. 507 - nonNative(2) : The LU is in a non-native APPN subnetwork. 508 - subarea(3) : The LU is in a subarea network." 510 ::= { ebnDirEntry 2 } 512 -- ******************************************************************* 513 -- EBN Intermediate Session RSCV Group 514 -- This table is an extension to the appnIsInTable. It contains the 515 -- RSCV and COS used in the direction of the BIND destination. 516 -- ******************************************************************* 518 ebnIsRscv OBJECT IDENTIFIER ::= { ebnObjects 2 } 520 ebnIsRscvTable OBJECT-TYPE 521 SYNTAX SEQUENCE OF EbnIsRscvEntry 522 MAX-ACCESS not-accessible 523 STATUS current 524 DESCRIPTION 525 "The EBN Intermediate Session RSCV table" 527 ::= { ebnIsRscv 1} 529 ebnIsRscvEntry OBJECT-TYPE 530 SYNTAX EbnIsRscvEntry 531 MAX-ACCESS not-accessible 532 STATUS current 533 DESCRIPTION 534 "Entry in ebnIsRscvTable." 536 INDEX { ebnIsRscvCpName, 537 ebnIsRscvPcid } 539 ::= { ebnIsRscvTable 1 } 541 EbnIsRscvEntry ::= SEQUENCE { 542 ebnIsRscvCpName SnaControlPointName, 543 ebnIsRscvPcid OCTET STRING, 544 ebnIsRscvDestinationRoute OCTET STRING, 545 ebnIsRscvDestinationCos DisplayString } 547 ebnIsRscvCpName OBJECT-TYPE 548 SYNTAX SnaControlPointName 549 MAX-ACCESS not-accessible 550 STATUS current 551 DESCRIPTION 552 "The network-qualified control point name of the node at which 553 the session and PCID originated. For APPN and LEN nodes, this 554 is either CP name of the APPN node at which the origin LU is 555 located or the CP name of the NN serving the LEN node at which 556 the origin LU is located. For DLUR resources it is the name of 557 the owning SSCP. " 559 ::= { ebnIsRscvEntry 1 } 561 ebnIsRscvPcid OBJECT-TYPE 562 SYNTAX OCTET STRING (SIZE (8)) 563 MAX-ACCESS not-accessible 564 STATUS current 565 DESCRIPTION 566 "The procedure correlation identifier (PCID) of a session. It 567 is an 8-octet value." 569 ::= { ebnIsRscvEntry 2 } 571 ebnIsRscvDestinationRoute OBJECT-TYPE 572 SYNTAX OCTET STRING(SIZE (0..255)) 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The route selection control vector (RSCV x'2B') used in the 577 direction towards the SLU." 579 ::= { ebnIsRscvEntry 3 } 581 ebnIsRscvDestinationCos OBJECT-TYPE 582 SYNTAX DisplayString (SIZE (1..8)) 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "The Class of Service (COS) name used in the direction towards 587 the SLU." 589 ::= { ebnIsRscvEntry 4 } 591 -- ******************************************************************* 592 -- EBN Directory Config Group 593 -- The following simple objects provide information about EBN directory. 594 -- ******************************************************************* 596 ebnDirConfig OBJECT IDENTIFIER ::= { ebnObjects 3 } 598 ebnSearchCacheTime OBJECT-TYPE 599 SYNTAX Unsigned32 600 UNITS "minutes" 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "The amount of time in minutes an extended border node will 605 retain information about a multi-subnetwork search, once that 606 that search terminates. A value 0 indicates that the EBN has 607 no defined limit, and the number of entries is bounded only by 608 memory." 610 ::= { ebnDirConfig 1 } 612 ebnMaxSearchCache OBJECT-TYPE 613 SYNTAX Unsigned32 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION 617 "The maximum number of multi-subnet entries to be cached. The 618 value 0 indicates that the local node has no defined limit, and 619 the number of entries is bounded only by memory." 621 ::= { ebnDirConfig 2 } 623 ebnDefaultSubnetVisitCount OBJECT-TYPE 624 SYNTAX Unsigned32 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "The default maximum number of subnetworks a LOCATE search 629 procedure may traverse." 631 ::= { ebnDirConfig 3 } 633 -- ******************************************************************* 634 -- EBN COS Mapping Group 635 -- The ebnCosMap Table specifies how non-native COS values are mapped 636 -- to a COS value which is defined in the native subnetwork. This 637 -- table defines the mappings that actually take place, as opposed to 638 -- the user-defined mappings. 639 -- ******************************************************************* 641 ebnCOS OBJECT IDENTIFIER ::= { ebnObjects 4 } 643 ebnCosMapTable OBJECT-TYPE 644 SYNTAX SEQUENCE OF EbnCosMapEntry 645 MAX-ACCESS not-accessible 646 STATUS current 647 DESCRIPTION 648 "The EBN COS Mapping Table." 650 ::= { ebnCOS 1} 652 ebnCosMapEntry OBJECT-TYPE 653 SYNTAX EbnCosMapEntry 654 MAX-ACCESS not-accessible 655 STATUS current 656 DESCRIPTION 657 "An entry in the EBN COS Mapping table." 659 INDEX { ebnCosMapCpName, 660 ebnCosMapNonNativeCos } 662 ::= { ebnCosMapTable 1 } 664 EbnCosMapEntry ::= SEQUENCE { 665 ebnCosMapCpName SnaNAUWildcardName, 666 ebnCosMapNonNativeCos DisplayString, 667 ebnCosMapNativeCos DisplayString } 669 ebnCosMapCpName OBJECT-TYPE 670 SYNTAX SnaNAUWildcardName 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "Fully qualified network CP name for which the COS mapping 675 applies." 677 ::= { ebnCosMapEntry 1 } 679 ebnCosMapNonNativeCos OBJECT-TYPE 680 SYNTAX DisplayString (SIZE(1..8)) 681 MAX-ACCESS not-accessible 682 STATUS current 683 DESCRIPTION 684 "An 8-byte name for the class-of-service, as known in the non- 685 native subnetwork. This variable may contain one '*' 686 character, indicating a default class-of-service mapping, 687 rather than a COS name. If the non-native COS name to be 688 mapped cannot be found in the cos mapping tablee, then the '*' 689 is used to resolve the native/non-native COS. Only one non- 690 native COS name per CP name can have a '*'. " 692 ::= { ebnCosMapEntry 2 } 694 ebnCosMapNativeCos OBJECT-TYPE 695 SYNTAX DisplayString (SIZE(1..8)) 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "An 8-byte name for the class-of-service, as known in the native 700 subnetwork." 702 ::= { ebnCosMapEntry 3 } 704 -- ******************************************************************* 705 -- EBN Subnet Routing List Group 706 -- The EBN Subnet Routing List indicates to which nodes an EBN forwards 707 -- search request. This group contains information pertaining to the 708 -- customer-supplied Subnet Routing List. 709 -- ******************************************************************* 711 ebnSubnetRoutingList OBJECT IDENTIFIER ::= { ebnObjects 5 } 713 ebnSubnetSearchTable OBJECT-TYPE 714 SYNTAX SEQUENCE OF EbnSubnetSearchEntry 715 MAX-ACCESS not-accessible 716 STATUS current 717 DESCRIPTION 718 "This table contains one entry for each fully qualified LU name 719 defined to have an associated subnet routing list. Each entry 720 contains general characteristics of the subnet search routing 721 list for each LU name." 723 ::= { ebnSubnetRoutingList 1} 725 ebnSubnetSearchEntry OBJECT-TYPE 726 SYNTAX EbnSubnetSearchEntry 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "An entry for the ebnSubnetSearchTable." 732 INDEX { ebnSubnetSearchLuName } 734 ::= { ebnSubnetSearchTable 1 } 736 EbnSubnetSearchEntry ::= SEQUENCE { 737 ebnSubnetSearchLuName SnaNAUWildcardName, 738 ebnSubnetSearchDynamics INTEGER, 739 ebnSubnetSearchOrdering INTEGER } 741 ebnSubnetSearchLuName OBJECT-TYPE 742 SYNTAX SnaNAUWildcardName 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "Fully qualified network LU name." 748 ::= { ebnSubnetSearchEntry 1 } 750 ebnSubnetSearchDynamics OBJECT-TYPE 751 SYNTAX INTEGER { none(1), 752 limited (2), 753 full (3) } 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "Indicates whether an EBN may add dynamic entries to a 758 subnetwork routing list. none(1) means no entries may be added 759 to the subnetwork routing list. limited(2) means only likely 760 entries may be added to the subnetwork routing list. full(3) 761 means all native extended border nodes and adjacent, non-native 762 EBNs and NNs will be added to the subnetwork routing list." 764 ::= { ebnSubnetSearchEntry 2 } 766 ebnSubnetSearchOrdering OBJECT-TYPE 767 SYNTAX INTEGER{ priority(1), 768 defined(2) } 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "Indicates whether an EBN may reorder a subnetwork routing list 773 so that entries which are more likely to be successful are at 774 the top of the subnetwork routing list and entries which are 775 more likely to be unsuccessful are at the bottom of the list." 777 ::= { ebnSubnetSearchEntry 3 } 779 -- Border node search table 781 ebnSearchTable OBJECT-TYPE 782 SYNTAX SEQUENCE OF EbnSearchEntry 783 MAX-ACCESS not-accessible 784 STATUS current 785 DESCRIPTION 786 "This table indicates where an EBN sends Locate searches for a 787 given fully qualified LU name. Each entry in the table 788 indicates one control point that should be included in a multi- 789 subnet search for a particular LU name. " 791 ::= { ebnSubnetRoutingList 2} 793 ebnSearchEntry OBJECT-TYPE 794 SYNTAX EbnSearchEntry 795 MAX-ACCESS not-accessible 796 STATUS current 797 DESCRIPTION 798 "An entry in the ebnSearchTable." 800 INDEX { ebnSearchLuName, 801 ebnSearchIndex } 803 ::= { ebnSearchTable 1 } 805 EbnSearchEntry ::= SEQUENCE { 806 ebnSearchLuName SnaNAUWildcardName, 807 ebnSearchIndex Unsigned32, 808 ebnSearchCpName DisplayString, 809 ebnSearchSNVC Unsigned32 } 811 ebnSearchLuName OBJECT-TYPE 812 SYNTAX SnaNAUWildcardName 813 MAX-ACCESS not-accessible 814 STATUS current 815 DESCRIPTION 816 "Fully qualified network LU name." 818 ::= { ebnSearchEntry 1 } 820 ebnSearchIndex OBJECT-TYPE 821 SYNTAX Unsigned32 822 MAX-ACCESS not-accessible 823 STATUS current 824 DESCRIPTION 825 "Secondary index which enumerates the order in which a search 826 is forwarded to CPs for a particular LU name." 828 ::= { ebnSearchEntry 2 } 830 ebnSearchCpName OBJECT-TYPE 831 SYNTAX DisplayString(SIZE(1..17)) 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "This object specifies the CP(s) to which a search should be 836 forwarded. It either follows the SnaNAUWildcardName textual 837 convention or takes one of the following special formats: 839 '*' indicates that all native EBNs and all adjacent non- 840 native EBNs and NNs may be added to the routing list 841 dynamically, 843 '*SELF' indicates that the EBN should search itself and its 844 native subnetwork at this time during the cross-subnet 845 search, 847 '*EBNS' indicates all native EBNs." 849 ::= { ebnSearchEntry 3 } 851 ebnSearchSNVC OBJECT-TYPE 852 SYNTAX Unsigned32 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION 856 "The maximum number of subnets a Locate search procedure may 857 traverse. " 859 ::= { ebnSearchEntry 4 } 861 -- ******************************************************************* 862 -- HPR Extended Border Node Intermediate Session Group 863 -- The hbnIsInTable is an extension to the appnIsInTable. 864 -- In the case where there are back-to-back RTP connections 865 -- in an HBN, this table is necessary to provide the NceId 866 -- and Tcid for the second RTP connection. 867 -- ******************************************************************* 869 hbn OBJECT IDENTIFIER ::= { ebnObjects 6 } 871 hbnIsInTable OBJECT-TYPE 872 SYNTAX SEQUENCE OF HbnIsInEntry 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION 876 "The HBN Intermediate Session table." 878 ::= { hbn 1} 880 hbnIsInEntry OBJECT-TYPE 881 SYNTAX HbnIsInEntry 882 MAX-ACCESS not-accessible 883 STATUS current 884 DESCRIPTION 885 "Entry of the HBN Intermediate Session Table." 887 INDEX { hbnIsInFqCpName, 888 hbnIsInPcid } 890 ::= { hbnIsInTable 1 } 892 HbnIsInEntry ::= SEQUENCE { 893 hbnIsInFqCpName SnaControlPointName, 894 hbnIsInPcid OCTET STRING, 895 hbnIsInRtpNceId OCTET STRING, 896 hbnIsInRtpTcid OCTET STRING } 898 hbnIsInFqCpName OBJECT-TYPE 899 SYNTAX SnaControlPointName 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION 903 "The network-qualified control point name of the node at which 904 the session and PCID originated. For APPN and LEN nodes, this 905 is either the CP name of the APPN node at which the origin LU 906 is located or the CP name of the NN serving the LEN node at 907 which the origin LU is located. " 909 ::= { hbnIsInEntry 1 } 911 hbnIsInPcid OBJECT-TYPE 912 SYNTAX OCTET STRING (SIZE(8)) 913 MAX-ACCESS not-accessible 914 STATUS current 915 DESCRIPTION 916 "The procedure correlation identifier (PCID) of a session. It 917 is an 8-octet value." 919 ::= { hbnIsInEntry 2 } 921 hbnIsInRtpNceId OBJECT-TYPE 922 SYNTAX OCTET STRING (SIZE(1..8)) 923 MAX-ACCESS read-only 924 STATUS current 925 DESCRIPTION 926 "The HPR local Network Connection Endpoint of the session in 927 the direction of the SLU. When this object exists, the 928 appnIsInRtpNceId object contains the HPR local Network 929 Connection Endpoint of the session in the direction of the 930 PLU." 932 ::= { hbnIsInEntry 3 } 934 hbnIsInRtpTcid OBJECT-TYPE 935 SYNTAX OCTET STRING (SIZE(8)) 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "The RTP connection local TCID of the session in the direction 940 of the SLU. When this object exists, the appnIsInRtpTcid 941 object contains the RTP connection local TCID of the session in 942 the direction of the PLU." 944 ::= { hbnIsInEntry 4 } 946 -- ******************************************************************* 947 -- Conformance Statement 948 -- ******************************************************************* 949 ebnConformance OBJECT IDENTIFIER ::= { ebnMIB 2 } 951 ebnCompliances OBJECT IDENTIFIER ::= { ebnConformance 1 } 952 ebnGroups OBJECT IDENTIFIER ::= { ebnConformance 2 } 954 -- Compliance statements 955 ebnCompliance MODULE-COMPLIANCE 956 STATUS current 957 DESCRIPTION 958 "The compliance statement for the SNMPv2 entites which implement 959 the ebnMIB." 961 MODULE -- this module 963 -- Unconditionally mandatory groups 964 MANDATORY-GROUPS { 965 ebnDirectoryGroup, 966 ebnIsRscvGroup, 967 ebnDirectoryConfigGroup, 968 ebnCosMappingGroup, 969 ebnSubnetRoutingListGroup } 971 -- Conditionally mandatory groups 972 GROUP hbnIsInGroup 973 DESCRIPTION 974 "The hbnIsInGroup is mandatory only for HPR extended border 975 nodes." 977 ::= {ebnCompliances 1} 979 -- Group definitions 980 ebnDirectoryGroup OBJECT-GROUP 981 OBJECTS { ebnDirSubnetAffiliation } 982 STATUS current 983 DESCRIPTION 984 "The EBN-related directory objects." 986 ::= { ebnGroups 1 } 988 ebnIsRscvGroup OBJECT-GROUP 989 OBJECTS { ebnIsRscvDestinationRoute, 990 ebnIsRscvDestinationCos } 991 STATUS current 992 DESCRIPTION 993 "Two objects representing RSCV and class of service information 994 saved by an EBN." 996 ::= { ebnGroups 2 } 998 ebnDirectoryConfigGroup OBJECT-GROUP 999 OBJECTS { ebnSearchCacheTime, 1000 ebnMaxSearchCache, 1001 ebnDefaultSubnetVisitCount } 1002 STATUS current 1003 DESCRIPTION 1004 "The EBN Directory Configuration Group." 1006 ::= { ebnGroups 3 } 1008 ebnCosMappingGroup OBJECT-GROUP 1009 OBJECTS { ebnCosMapNativeCos } 1010 STATUS current 1011 DESCRIPTION 1012 "The EBN COS Mapping Group." 1014 ::= { ebnGroups 4 } 1016 ebnSubnetRoutingListGroup OBJECT-GROUP 1017 OBJECTS { ebnSubnetSearchDynamics, 1018 ebnSubnetSearchOrdering, 1019 ebnSearchCpName, 1020 ebnSearchSNVC } 1021 STATUS current 1022 DESCRIPTION 1023 "The Subnet Routing List Group." 1025 ::= { ebnGroups 5 } 1027 hbnIsInGroup OBJECT-GROUP 1028 OBJECTS { hbnIsInRtpNceId, hbnIsInRtpTcid } 1029 STATUS current 1030 DESCRIPTION 1031 "The HBN-related Intermediate Session Objects." 1033 ::= { ebnGroups 6 } 1035 END 1037 5.0 Security Considerations 1039 Certain management information defined in this MIB may be considered 1040 sensitive in some network environments. Therefore, authentication of 1041 received SNMP requests and controlled access to management information 1042 SHOULD be employed in such environments. The method for this 1043 authentication is a function of the SNMP Administrative Framework, and 1044 has not been expanded by this MIB. 1046 None of the read-only objects in the EBN MIB reports a password, user 1047 data, or anything else that is particularly sensitive. Some enterprises 1048 view their network configuration itself, as well as information about 1049 network usage and performance, as corporate assets; such enterprises may 1050 wish to restrict SNMP access to most of the objects in the MIB. 1052 There are no read-write objects in the EBN MIB. 1054 6.0 Intellectual Property 1056 The IETF takes no position regarding the validity or scope of any 1057 intellectual property or other rights that might be claimed to pertain 1058 to the implementation or use of the technology described in this 1059 document or the extent to which any license under such rights might or 1060 might not be available; neither does it represent that it has made any 1061 effort to identify any such rights. Information on the IETF's 1062 procedures with respect to rights in standards-track and 1063 standards-related documentation can be found in BCP-11. Copies of 1064 claims of rights made available for publication and any assurances of 1065 licenses to be made available, or the result of an attempt made to 1066 obtain a general license or permission for the use of such proprietary 1067 rights by implementers or users of this specification can be obtained 1068 from the IETF Secretariat. 1070 The IETF invites any interested party to bring to its attention any 1071 copyrights, patents or patent applications, or other proprietary rights 1072 which may cover technology that may be required to practice this 1073 standard. Please address the information to the IETF Executive 1074 Director. 1076 7.0 Acknowledgments 1078 This MIB module is the product of the IETF SNA NAU MIB WG and the AIW 1079 APPN/HPR MIBs SIG. Thanks to Dave Billing, Cisco Systems; Katie Lee, 1080 IBM Corporation; and Marcia Peters, IBM Corporation, for their 1081 contributions and review. 1083 8.0 References 1085 [1] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 1086 of Management Information for Version 2 of the Simple Network 1087 Management Protocol (SNMPv2)", RFC 1902, January 1996. 1089 [2] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 1090 Conventions for Version 2 of the Simple Network Management Protocol 1091 (SNMPv2)", RFC 1903, January 1996. 1093 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 1094 "Conformance Statements for Version 2 of the Simple Network 1095 Management Protocol (SNMPv2)", RFC 1904, January 1996. 1097 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 1098 Operations for Version 2 of the Simple Network Management Protocol 1099 (SNMPv2)", RFC 1905, January 1996. 1101 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport 1102 Mappings for Version 2 of the Simple Network Management Protocol 1103 (SNMPv2)", RFC 1906, January 1996. 1105 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management 1106 Information Base for Version 2 of the Simple Network Management 1107 Protocol (SNMPv2)", RFC 1907, January 1996. 1109 [7] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 1110 "Coexistence between Version 1 and Version 2 of the 1111 Internet-standard Network Management Framework", RFC 1908, January 1112 1996. 1114 [8] Bradner, S., "Key words for use in RFCs to Indicate Requirement 1115 Levels", BCP 14, RFC 2119, March 1997. 1117 [9] Clouston, B., and B. Moore, "Definition of Managed Objects for APPN 1118 using SMIv2", RFC 2155, June 1997. 1120 [10] IBM, APPN Extended Border Node Architecture Reference Version 1.0, 1121 available only via anonymous FTP at networking.raleigh.ibm.com, as 1122 /pub/standards/aiw/appn/bordernode/ebn4.psbin. 1124 [11] IBM, SNA/MS Formats, GC31-8302-00 1126 9.0 Authors' Addresses 1127 Bob Clouston 1128 Cisco Systems 1129 7025 Kit Creek Road 1130 P.O. Box 14987 1131 Research Triangle Park, NC 27709, USA 1133 Phone: +1-919-472-2333 1134 E-mail: clouston@cisco.com 1136 Robert Moore 1137 Dept. BRQA/Bldg. 501/G114 1138 IBM Corporation 1139 P.O.Box 12195 1140 3039 Cornwallis 1141 Research Triangle Park, NC 27709, USA 1142 Phone: +1-919-254-7507 1143 E-mail: remoore@us.ibm.com 1145 10.0 Full Copyright Statement 1147 Copyright (C) The Internet Society (1997). All Rights Reserved. 1149 This document and translations of it may be copied and furnished to 1150 others, and derivative works that comment on or otherwise explain it or 1151 assist in its implementation may be prepared, copied, published and 1152 distributed, in whole or in part, without restriction of any kind, 1153 provided that the above copyright notice and this paragraph are included 1154 on all such copies and derivative works. However, this document itself 1155 may not be modified in any way, such as by removing the copyright notice 1156 or references to the Internet Society or other Internet organizations, 1157 except as needed for the purpose of developing Internet standards in 1158 which case the procedures for copyrights defined in the Internet 1159 Standards process must be followed, or as required to translate it into 1160 languages other than English. 1162 The limited permissions granted above are perpetual and will not be 1163 revoked by the Internet Society or its successors or assigns. 1165 This document and the information contained herein is provided on an "AS 1166 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1167 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1168 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1169 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1170 FITNESS FOR A PARTICULAR PURPOSE.