idnits 2.17.1 draft-ietf-dlswmib-mib-09.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-26) 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. ** 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 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 is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. ** The abstract seems to contain references ([2], [3], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 903 has weird spacing: '... octets cont...' == Line 2337 has weird spacing: '...figured loc...' == Line 2340 has weird spacing: '...figured rem...' == Line 2343 has weird spacing: '...apExMsg remo...' == Line 2514 has weird spacing: '...figured loc...' == (2 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (4 June 1996) is 10188 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 4371, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 1795 (ref. '1') ** Obsolete normative reference: RFC 1902 (ref. '2') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '5') ** Obsolete normative reference: RFC 1905 (ref. '6') (Obsoleted by RFC 3416) -- Possible downref: Non-RFC (?) normative reference: ref. '7' ** Obsolete normative reference: RFC 1573 (ref. '8') (Obsoleted by RFC 2233) ** Downref: Normative reference to an Historic RFC: RFC 1747 (ref. '9') Summary: 18 errors (**), 0 flaws (~~), 8 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Definitions of Managed Objects for Data Link Switching 2 using SNMPv2 4 4 June 1996 6 David D. Chen (editor) 7 IBM Corp. 9 Peter W. Gayek 10 IBM Corp. 12 Shannon Nix (chair) 13 Metaplex, Inc. 15 17 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 valid for a maximum of six months and may be 25 updated, replaced, or obsoleted by other documents at any time. It is 26 inappropriate to use Internet Drafts as reference material or to cite 27 them other than as a "work in progress". 29 Abstract 31 This specification defines an extension to the Management Information 32 Base (MIB) for use with SNMP-based network management. In particular, 33 it defines objects for configuring, monitoring, and controlling Data 34 Link Switches (DLSw) [1]. 36 This memo specifies a MIB module in a manner that is both compliant to 37 the SNMPv2 SMI [2], and semantically identical to the SNMPv1 definitions 38 [3]. 40 1.0 Change Log 42 This section tracks changes made during revisions of this document. It 43 will be deleted when the document is published as a RFC. 45 06/04/96 (version 9.0) 47 1. Changed the OID of dlswTraps from dlswMIB.7 to dlswMIB.0 (complying 48 with Section 8.5 of RFC1902). 50 04/19/96 (version 8.0 - changes after IETF NM Directorate review) 52 1. Changed the "The SNMP Network Management Framework" to reference 53 SNMPv2 RFC's. 54 2. Changed IfIndex to ifIndex. 55 3. Removed text related to LLC MIB working group. 56 4. Changed the terms of network management station to manager, and 57 implementations to agent. 58 5. Rewrote multiple places in text for clarification. 59 6. Eliminated the DlswTimeStamp textual convention, instead TimeTicks 60 is used. 61 7. Added the trap control objects in the descriptions of the traps. 62 8. Changed InstancePointer to RowPointer 63 9. Added NOTIFICATION-GROUP 65 10/18/95 (version 7.0 - text editing changes only) 67 1. Added or significantly changed text in the following header 68 sections: Relation to Interface Group, Relation to 802.2 MIB, 69 Relation to SDLC MIB, DLSw MIB Structure, Compliance (formerly 70 conformance), and DLSw MIB Usage (formerly DLSw MIB special 71 features). The new text includes some recommendations and policy 72 statements that grew out of working group discussions and should be 73 reviewed. 74 2. Removed old reference to dlswTConnConfigRemoteTaddrMask from the 75 description of dlswTConnConfigRemoteTAddr. 76 3. Made minor description and comment changes to the compliance 77 statements and conformance groups. 79 10/09/95 (version 6.0 - changes just preceding and at AIW8) 81 1. Eliminated enumerated values of zero for dlswCircuitPriority and 82 dlswCircuitDiscReasonRemote. 83 2. Added objects dlswDirMacCacheNextIndex and dlswDirNBCacheNextIndex, 84 to make it possible for a management station to add configured cache 85 entries. Note that putting these objects in a logical place 86 required changes to the object id's of several other objects. 87 3. Modified the description of dlswTConnConfigLastModifyTime to exclude 88 dlswTConnConfigOpens from being considered as a change requiring an 89 update to ...LastModifyTime. 90 4. Changed the description of dlswTConnConfigAdvertiseMacNB to clarify 91 which control vectors should be sent for each object value. 92 5. Created textual convention for non-canonical format MAC addresses, 93 including making a consistent rule that a zero length should be 94 returned for unavailable MAC addresses. 95 6. Corrected DEFVALs of null instance pointers so they would compile 96 (they had been commented out). 97 7. Made the following object name changes: 98 o dlswSdlcLsLocalBlockNum -> dlswSdlcLsLocalIdBlock (also 99 clarified this is in fact configurable) 100 o Objects in node group -> dlswNode...... 101 o Circuit statistics objects -> dlswCircuitStat..... 102 8. Changed the MIB basing to the IETF-assigned experimental tree 103 location. 104 9. Corrected the conformance statements to match the current object 105 names and groups. 107 06/30/95 (version 5.0) 109 1. Changes adopted by the AIW DLSw MIB RIGLET / IETF DLSw MIB Working 110 Group during AIW 7 (May 1-3, 1995) in San Jose. Major changes 111 include: 112 o Added QLLC as a DLC type. 113 o Fixed up DEFVALs for LF size objects and SAP list objects. 114 Expanded range for all pacing objects. 115 o Moved all pacing objects (global and TC-level) to the circuit 116 table. 117 o Introduced TCP-specific TConnConfig and TConnOper tables, moved 118 some objects there from existing tables. 119 o Removed mask concept from TConnConfig, added ability to exclude 120 specified partners. 121 o Changed rule about backward reference from TConnOper to 122 TConnConfig. 123 o Reworked disconnect reason codes for TCs and Circuits. 124 o For MAC address and NB name cache, allowed local configured 125 entries not to be advertised in capabilities exchange. 126 o Added object for remote circuit disconnect reason 127 2. Numerous editorial improvements and clarifications to descriptions. 128 Some are marked with to-be-deleted comments to make sure everyone is 129 ok with the change. 131 3. Added group reference to TConnConfig as an escape for those who 132 would like to do masks or some other vendor-specific grouping 133 scheme. This adds no complexity for those who do not want a group 134 concept. 135 4. Deleted Initial window objects from the circuit table, and added 136 only the send window back to TConnOper as saved from capabilities 137 exchange. Also added TCP connections from capability exchange. 138 5. Removed the directory search function. We can add it back if 139 someone feels it should be in the standard MIB. 140 6. Assigned numbers and corrected dozens of small errors to get it to 141 compile successfully (I left 1 warning) using smicng. 143 04/24/95 (version 4.0) 145 1. The changes adopted by the AIW DLSw MIB RIGLET and IETF DLSw MIB 146 Working Group. 148 01/20/95 (version 3.0) 150 1. Changes are based on the review during IETF San Jose Meeting on 151 12/06/94. Most part of Node group and Circuit group were reviewed. 152 Major changes include: 153 o dlswName and dlswDescr were removed. 154 o dlswSnaSupport and dlswNBSupport were removed. 155 o dlswFlowCntlSupport was replaced with dlswXBusySupport and 156 dlswPacingSupport which specify the product's code capabilities 157 of supporting ENTER_BUSY/EXIT_BUSY messages and supporting 158 Fixed/Adaptive flow control scheme, respectively. In each 159 object, the capabilities of send and receive modes are 160 separately enumerated. 161 o dlswAdminFlowCntlMode and dlswOperFlowCntlMode were removed. 162 o New enumeration, xBusy, was added to dlswTConnFlowCntlMode. 163 o Text of dlswAdminVirtualSegment which describing when the value 164 takes effect was removed. 165 o The name of dlswAdminVirtualSegmentMTU was changed to 166 dlswAdminVirtualSegmentLFSize. Eight enumeration values were 167 defined which are based on the Largest Frame (LF) Base Values 168 specified in ANSI/IEEE Std 802.1D Annexes 1993 edition. 169 o The description of dlswAdminStatus was written to define the 170 meaning of active and inactive operations. 171 o The range of the size of pacing window related object was set to 172 (0..65). 173 o A trap-enable object for each type of notification was added to 174 control its emission. Those are: dlswTConnEnableStatusTraps, 175 dlswTConnEnableRejectionTraps, dlswTConnEnableProtVltnTraps, and 176 dlswEnableOutOfResourceTraps. 177 o DLSw partner configuration section was modified. Now SAP list 178 and initial window size are the only information that are 179 configurable on per DLSw partner basis. 180 o dlswTransportTcpReadPortNumber was added. 182 o dlswTConnTcpOperConnTable was added to identify each TCP 183 connection with local and remote port numbers. 184 o The state that causes an instance in the dlswCircuitTable being 185 substantiated was clarified. 186 o Now End Station 1 (S1) of the dlswCircuitTable is always 187 representing an end station that is locally attached. Thus, 188 dlswCircuitS1Location, dlswCircuitS1TDomain and 189 dlswCircuitS1TAddress were removed. 190 o All flow control statistics related objects in the 191 dlswCircuitTable were removed. 8 flow control objects were 192 added to dlswTConnTable. 193 o dlswCircuitStateDownTime, dlswCircuitS1SenseCode, and 194 dlswCircuitS2SenseCode were removed. dlswCircuitSenseCode was 195 added with an enumerated list. 196 o Now the index to dlswSdlcLsTable is dlswSdlcLsLocalMac and 197 dlswSdlcLsLocalSap. 198 2. Other changes: 200 11/29/94 (version 2.0) 202 1. Changes are based on the conference call review on 11/8/94. 203 Directory group (administrative, statistics, reachability cache, and 204 directory search initiation) was reviewed. Circuit group was only 205 briefly discussed. Major changes include: 206 o Explorer message counters, and outstanding exploring message 207 information were removed. 208 o Technique for NMS to initiate directory search and retrieve the 209 result was clarified. 210 o Indices of reachability cache tables were changed. 211 o A number of types and states of cache entries were added. 212 o Circuit event log table was removed. Last sense codes from the 213 origin and target DLSw partners were moved to dlswCiruitTable. 214 2. Other changes: 215 o dlswCirEstabTable was renamed to dlswCircuitTable. 216 o The index of dlswCirEstabTable was changed to end station 1 (S1) 217 and end station 2 (S2) MAC-SAP pairs. 219 11/01/94 (version 1.0) - Initial Draft 221 1. The initial draft was based on the proposal of David Chen and Peter 222 Gayek. 223 2. The following ideas in the Wellfleet DLSw MIB were identified and 224 incorporated: 225 o a table to show/control what interface DLSw is active on 226 o virtual ring MTU size 227 o TCP maximum segment size (MSS) 228 3. The structure and objects of dlswNode and dlswTConn were agreed in 229 AIW6 (10/12-10/13/94). 230 4. Other contributions: 231 o Object and operations of how to apply changes in CapEx control 232 vectors to runtime CapEx messages. (Alan Sciacca) 234 o Script about the correct usage of counters for accounting 235 purposes. (Alan Sciacca) 236 o TCP transport specific objects. (Peter Gayek) 237 o Definition of data and control traffic statistics. (Peter 238 Gayek) 240 2.0 The SNMPv2 Network Management Framework 242 The SNMP Network Management Framework presently consists of three major 243 components. They are: 245 o RFC 1902 [2] which defines the SMI, the mechanisms used for 246 describing and naming objects for the purpose of management. 248 o STD 17, RFC 1213 [4] defines MIB-II, the core set of managed objects 249 for the Internet suite of protocols. 251 o STD 15, RFC 1157 [5] and RFC 1905 [6] which define two versions of 252 the protocol used for network access to managed objects. 254 The Framework permits new objects to be defined for the purpose of 255 experimentation and evaluation. 257 2.1 Object Definitions 259 Managed objects are accessed via a virtual information store, termed the 260 Management Information Base or MIB. Objects in the MIB are defined 261 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 262 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 263 an administratively assigned name. The object type together with an 264 object instance serves to uniquely identify a specific instantiation of 265 the object. For human convenience, we often use a textual string, 266 termed the descriptor, to refer to the object type. 268 3.0 Overview 270 This memo identifies the set of objects for configuring, monitoring, and 271 controlling Data Link Switches. 273 3.1 Relation to Interface Group (RFC 1573) [8] 275 o ifIndex is used as the index into dlswIfTable, which shows and 276 controls the interfaces that DLSw is active on. 278 o Local entries in the MAC address and NetBIOS (NB) name caches can 279 point to an ifEntry to indicate the interface through which DLSw can 280 reach that MAC address or NB name. See the objects 281 dlswDirMacLocation and dlswDirNBLocation. 283 o Local entries in the circuit table use ifIndex to indicate the 284 interface through which DLSw is connected to the local end station. 285 See the object dlswCircuitS1Index. 287 o ifIndex is the primary index into dlswSdlcLsTable, which lists the 288 SDLC stations DLSw is serving. 290 3.2 Relation to Underlying DLC Layer 292 The DLSw MIB does not duplicate the information in the MIBs for the DLC 293 layer underneath it. Instead, each circuit table entry contains a 294 pointer to a conceptual row in an underlying enterprise-specific or 295 standard DLC MIB. 297 Using the 802.2 LLC management as an example, the following rules should 298 be considered when developing new DLSw related DLC MIBs, and when 299 implementing the interactions between DLSw MIB and DLC MIBs: 301 o The referenced row should represent the local LLC-2 (and/or LLC-1, 302 if supported) link station that DLSw is using. In the current 802.2 303 LLC MIB draft, this might be a row of one of the tables 304 llcCcAdminTable, llcCcOperTable, or llcCcStatsTable. 306 A circuit using local LLC services will therefore have 307 dlswCircuitS1DlcType = llc, and dlswCircuitS1Dlc = pointer to an LLC 308 MIB table row. 310 o Because DLSw is the user of LLC services, it is generally preferable 311 to initiate administrative actions using the DLSw MIB and allow DLSw 312 to control LLC directly, rather than starting with LLC MIB 313 administrative actions. For example, a hung circuit should be 314 disconnected by setting dlswCircuitState, as opposed to setting 315 llcCcAdminStatus to disable the LLC part of the circuit. Similarly, 316 setting bits in dlswIfSapList will cause row creation in 317 llcSapOperTable as well as set the necessary DLSw-LLC relationship. 319 3.3 Relation to SDLC MIB (RFC 1747) 321 The general comments stated in 3.2, "Relation to Underlying DLC Layer" 322 apply to the SDLC MIB. The following apply if the DLSw MIB is 323 implemented in a product that also implements RFC 1747 [9]: 325 o The row referenced from dlswCircuitS1Dlc should represent the local 326 SDLC link station that DLSw is using. This might be a row of one of 327 the tables sdlcLSAdminTable, sdlcLSOperTable, or sdlcLSStatsTable. 329 A circuit using local SDLC services will therefore have 330 dlswCircuitS1DlcType = sdlc, and dlswCircuitS1Dlc = OID of one of 331 these table rows. 333 o dlswSdlcLsTable uses the same indices that are used to index link 334 station information in RFC 1747. This table provides a mapping 335 between this native SDLC addressing (interface, link station 336 address) and the addressing used in the DLSw domain (local MAC and 337 SAP). 339 3.4 DLSw MIB Structure 341 See 4.0, "Definitions" on page 14 for a diagram outlining the DLSw MIB 342 structure. The following groups of objects are included: 344 dlswNode Objects related to this DLSw node's configuration, 345 monitoring and control. 347 dlswTConn Objects relating to transport connections to this DLSw's 348 partner nodes. 350 dlswInterface Objects configured for this DLSw relating to its local 351 interfaces. 353 dlswDirectory Objects reflecting this DLSw's view of where end-station 354 resources (MAC addresses and NetBIOS names) are located. 356 dlswCircuit Objects showing the end-station connections that DLSw 357 currently has established, or that are coming up or have 358 gone down. 360 dlswSDLC Objects configured for this DLSw's SDLC-attached end 361 stations. 363 3.4.1 Compliance 365 The MIB provides the following compliance statements: 367 dlswCoreCompliance Defines the minimum support required of all 368 implementations. Note that for this and the 369 other compliance statements, NetBIOS-related 370 objects are grouped separately because the DLSw 371 Version 1 Standard [1] does not require NetBIOS 372 support. 374 dlswTConnTCPCompliance Defines the minimum support required of 375 implementations that use TCP as a transport 376 protocol. 378 dlswDirCompliance Defines the minimum support required of 379 implementations that support some sort of 380 directory function. 382 dlswDirLocateCompliance Defines the minimum support required of 383 implementations that support a directory 384 function and also support the ordered retrieval 385 of the entries that match a given resource. 387 dlswSdlcCompliance Defines the minimum support required of 388 implementations that support SDLC-attached end 389 stations. 391 3.5 DLSw MIB Usage 393 3.5.1 Cooperative DLSw nodes 395 To reduce the size of the MIB, thus the amount of data that each agent 396 needs to keep, the information that usually could be made available in 397 two partner nodes (e.g., information exchanged between them) is only 398 defined in the MIB as the info received. That is, there are no objects 399 defined for the info sent. In order to form the complete picture of the 400 state of a resource, the manager needs to retrieve info from multiple 401 DLSw nodes. An example is that the SAP list, NETBIOS list and MAC list 402 are kept at the receiving end of a DLSw capabilities exchange (the 403 sender does not save what it sent to each partner). 405 Note well: The DLSw protocol does not specify a technique for a manager 406 to correlate the transport address of the partner managed DLSw node and 407 the transport address that the management protocol uses. 409 3.5.2 Setting capabilities exchange-related objects 411 This MIB supports changes to DLSw variables whose change should be 412 reported to DLSw partner nodes in a "run-time" capabilities exchange. 413 Since a DLSw node normally unicasts these capabilities messages to all 414 its active partners, frequent changes to these variables can result in 415 excessive network traffic. To avoid this problem, developers of network 416 management applications using this MIB should try to group all such 417 changes in a few SNMP SET requests, and should send them in bulk. Agent 418 developers should implement a technique to group a number of changes 419 into a single capabilities exchange message. One possible approach is 420 to send a run-time capabilities message only if no capabilities-related 421 changes have been received for a pre-defined period of time. 423 3.5.3 Examples of Tasks Using This MIB 425 3.5.3.1 Configuring DLSw to actively connect to a specific TCP/IP 426 partner 428 Create a conceptual row in dlswTConnConfigTable with: Index = the 429 highest the managed station has used so far + 1; TDomain = 430 dlswTCPDomain; LocalTAddr = this node's DLSw IP address; RemoteTAddr = 431 the partner's DLSw IP address; EntryType = individual; SetupType = 432 activePersistent. Note that determining the index to use may require 433 dumping the TConnConfigTable, but this will not typically be a large 434 table. If the DLSw node rejects the row creation due to index 435 collision, the management station should increment its index value and 436 try again. 438 3.5.3.2 Configuring DLSw to passively accept any partner 440 Create a conceptual row in dlswTConnConfigTable as above but with: 441 RemoteTAddr = 0; EntryType = global; SetUpType = passive. Every 442 individual transport connection accepted as a result of this global row 443 will inherit the configuration values from this row. 445 To prevent a specific remote node from being passively accepted as a 446 partner, create another row with: RemoteTAddr = that node's IP address; 447 EntryType = individual; SetupType = excluded. 449 3.5.3.3 Configuring DLSw to allow or connect to a group of partners 451 Define a conceptual row in dlswTConnConfigTable as above but with: 452 EntryType = group; GroupDefinition = pointer to an enterprise-specific 453 representation of a group. For example, a group definition might 454 consist of an IP address value and mask, or a multicast IP address. 455 Every individual transport connection accepted as a result of this group 456 row will inherit the configuration values from this row. 458 When a group is created that has some overlap with entries where 459 EntryType = individual (there will always be this overlap when a global 460 row exists), the DLSw node must use the configured rows using a "most 461 specific match wins" rule. That is, the entry in TConnConfigTable with 462 the remote address most nearly matching an incoming connection should be 463 used to provide the values for the new connection. For equal matches, 464 the choice of TConnConfigTable entry is up to the DLSw node 465 implementation. Note that the management station should never create 466 two TConnConfig rows with duplicate remote addressing values. 468 3.5.3.4 Identifying the protocol level of a partner DLSw 470 If the partner DLSw has implemented at least the AIW Version 1 DLSw 471 Standard [1], the AIW version and release number for the DLSw protocol 472 is accessible from dlswTConnOperPartnerVersion. If 473 TConnOperPartnerVersion is a string of zero length but the 474 TConnOperState = `connected' state (i.e., is not still performing 475 capabilities exchange), the partner DLSw can be assumed to be an RFC 476 1434+ node. 478 3.5.3.5 Recycling a transport connection 480 Quiesce or forcibly disconnect the transport connection by setting 481 TConnOperState to `quiescing' or `disconnecting', and monitor until it 482 moves to the `disconnected' state or the TConnOper row disappears. The 483 row may disappear because implementations are not required to maintain 484 transport connection information after a transport connection has gone 485 down. 487 The action required to re-activate the transport connection depends on 488 the value of TConnConfigSetupType for the relevant TConnConfig row. 489 ActivePersistent connections will attempt to come back automatically. 490 Passive connections must be re-established from the remote partner. 491 ActiveOnDemand connections will be re-established by this node, but only 492 after some end-station operation triggers a circuit setup attempt. 494 3.5.3.6 Investigating why a transport connection went down 496 TConnOperDiscTime and TConnOperDiscReason provide the vital information 497 of the time and the cause of the disconnection of a transport connection 498 and TConnOperDiscActiveCir indicates whether end users may have been 499 affected. This MIB does not specify the duration that an agent must 500 make this information available after the disconnection of a transport 501 connection occurs. Manager should try the agent of the partner DLSw, if 502 such information is not available in one DLSw node. Additional 503 information might come from the MIB for the transport protocol (e.g., 504 TCP or LLC). dlswTConnStat* and dlswTConnConfigOpens give a more 505 general picture of transport connection activity, but can't give 506 specific reasons for problems. 508 3.5.3.7 Changing the configuration of an active transport connection 510 Follow this sequence of managment protocol set operations: 512 1. Use TConnOperConfigIndex to locate the TConnConfig entry that 513 governs the configuration of the transport connection. 514 2. Change the rowStatus of that conceptual row to notInService. This 515 prevents the transport connection from being connected automatically 516 if TConnConfigSetupType = activePersistent. 517 3. Quiesce or forcibly disconnect the transport connection by setting 518 TConnOperState to `quiescing' or `disconnecting', and monitor until 519 it moves to the `disconnected' state or the TConnOper row 520 disappears. 521 4. Change the values of TConnConfig variables as desired. 522 5. Change the rowStatus of the TConnConfig conceptual row to active. 523 TConnConfigSetupType will subsequently control whether this node 524 will actively seek to re-establish the transport connection, or will 525 wait. 527 3.5.3.8 Checking configuration validity for an active transport 528 connection 530 Use TConnOperConfigIndex to identify the row of TConnConfig for the 531 transport connection. If TConnConfigLastModifyTime is greater than 532 TConnOperConnectTime, then one or more of the variables in the 533 TConnConfig row may not be valid for the current state of the active 534 transport connection. This is an exception condition and will not 535 normally be the case. 537 3.5.3.9 Configuring the interfaces and SAPs DLSw will use 539 To add DLSw end-station support (not transport connection support) to an 540 interface, create a conceptual row for that ifIndex in the dlswIfTable. 541 For many products, you will specify the same single virtual segment 542 number for all interfaces. Indicate the list of SAPs to be supported by 543 that interface - this could be all 0xFFs if the product has some 544 automatic SAP opening function. 546 To open or close a SAP to DLSw on an existing interface, simply set or 547 reset the appropriate bit in dlswIfSapList in the table row for that 548 interface. 550 3.5.3.10 Configuring static MAC address (or NetBIOS name) cache entries 552 It is common to configure a few static directory entries to preload in 553 the caches of the DLSw nodes and reduce the need for broadcast searches. 554 The following example adds entries to the MAC cache to indicate that a 555 specific MAC address is reachable through two different remote partners: 557 1. The manager retrieves dlswDirMacCacheNextIndex to get an index 558 assignment from the DLSw node. The DLSw node ensures that the 559 retrieved index will not be reused. 560 2. The manager creates a conceptual row in dlswDirMacTable with: Index 561 = the retrieved index; Mac = the MAC address; Mask = all 0xFF's; 562 EntryType = userConfiguredPublic; LocationType = remote; Location = 563 OID for dlswTConnConfigEntry of the 1st partner; Status = unknown 564 (recommended for new entries). 565 3. The manager repeats the preceding 2 steps and creates a second row 566 using Index = second index retrieved; Location = OID for 567 dlswTConnConfigEntry of the 2nd partner. 569 Note that the DLSw node is not obligated to use newly created directory 570 entries in the order in which they were created. It is recommended that 571 entries be used in most-specific match first order, i.e., an entry with 572 a Mask of all 0xFFs should take precedence over one with a "partial 573 wildcard". The relative order of static versus dynamic entries and of 574 "equal length" matches is up to the DLSw implementation. 576 The dlswDirStat objects can be used to get an idea of the success rate 577 for a particular static caching scheme. 579 3.5.3.11 Seeing where the directory indicates a given resource is 581 To retrieve all directory information related to a given resource (in 582 this example, a NetBIOS name), the management station should: 584 1. Retrieve dlswDirLocateNBLocation in the dlswDirLocateNBTable entry 585 where NBName = the fully-specified NetBIOS name without wildcards; 586 NBMatch = 1. 587 2. Use the returned value (i.e., OID) to retrieve the contents of the 588 dlswDirNBEntry itself. 589 3. Repeat the previous two steps with NBMatch = 2, 3, ..., until the 590 end of dlswDirLocateNBTable is reached. 592 The DLSw node conveys the precedence relationship of the different 593 matching directory entries by the order in which it returns their OIDs. 595 3.5.3.12 Investigating circuit bringup failure 597 Circuit bringup takes place in two stages: explorer flows to locate the 598 target resource (MAC address or NetBIOS name); and establishing the 599 circuit itself. To determine the success of explorer flows, have the 600 origin end station initiate a link establishment to the target, and look 601 later for cache entries for the target MAC address or NetBIOS name. The 602 dlswTConn*ex* counters also give some visibility to which transport 603 connections are being used to look for resources. Once circuit 604 establishment is started, an entry of dlswCircuitTable for the two 605 MAC/SAP addresses involved is created. dlswCircuitEntryTime, StateTime, 606 and State may provide useful information about intermediate states the 607 circuit is reaching before becoming disconnected again. 609 3.5.3.13 Investigating the failure of an established circuit 611 The variables dlswCircuitDiscReason* in the dlswCircuitTable provide the 612 key information of the cause of the disconnection of circuits. In 613 addition, the underlying DLC MIBs may provide information at the link 614 station level, and some clues (e.g., DISC or FRMR counters) at the SAP 615 or interface level. 617 3.5.3.14 Seeing circuit-level traffic statistics 619 Locate the relevant dlswCircuitEntry and follow dlswCircuitS1Dlc to a 620 link station-level table entry in the underlying DLC MIB. Move to the 621 corresponding link station's statistics table in the DLC MIB to get 622 counters of frames, bytes, etc. for this circuit. 624 3.5.3.15 Cutting down the flow of DLSw-related traps 626 Set some or all of the dlswTrapCntl* objects to the value of `disabled' 627 or `partial'. 629 4.0 Definitions 631 -- ******************************************************************* 632 -- 633 -- The structure of the DLSw MIB (t: indicates table): 634 -- DLSw MIB 635 -- |-- Node Group 636 -- | |-- Node Identity 637 -- | |-- Node Operational Related 638 -- | |-- Node Resource 639 -- | 640 -- |-- Transport Connection Group 641 -- | |-- Statistics 642 -- | |t- Transport Connection Configuration 643 -- | |t- Transport Connection Operation 644 -- | | |-- capabilities 645 -- | | |-- Supported SAP List 646 -- | | |-- statistics 647 -- | | |-- transport connection itself 648 -- | | |-- traffic over the transport connection 649 -- | | |-- directory search activities 650 -- | | |-- search filtered statistics 651 -- | | |-- circuits over the transport connection 652 -- | |-- Transport Specific 653 -- | |-- Tcp 654 -- | |t- Transport Connection Config (Tcp Specific) 655 -- | |t- Transport Connection Operation (Tcp Specific) 656 -- | 657 -- |-- Interface Group 658 -- | |t- interfaces that DLSw is active on. 659 -- | 660 -- |-- Directory Group 661 -- | |-- Statistics 662 -- | |-- Directory Cache 663 -- | | |t- Directory of MAC addresses 664 -- | | |t- Directory of NETBIOS names 665 -- | |-- Locate 666 -- | |t- Directory of Locate MAC 667 -- | |t- Directory of Locate NETBIOS 668 -- | 669 -- |-- Circuit Group 670 -- | |-- Statistics 671 -- | |t- Circuits 672 -- | 673 -- |-- Virtual and non-LAN end stations 674 -- | |t- SDLC end station 675 -- | 676 -- ******************************************************************* 678 -- ******************************************************************* 679 -- This MIB module contains objects necessary for management of Data 680 -- Link Switches. 681 -- 682 -- Terminology: 683 -- (1) DLSw: 684 -- A device which provides data link switching function. 685 -- Sometimes it is referred as a DLSw or DLSw node. 686 -- Local DLSw: The DLSw that the DLSw SNMP Agent is running on. 687 -- Partner DLSw (or DLSw partner): A DLSw node that is "transport 688 -- connected" with the local DLSw. Sometimes the term "DLSw 689 -- partners" is used to indicate the two ends of a transport 690 -- connection. 691 -- 692 -- (2) TCP Connection: 693 -- Full-duplex (-capable) association defined by a pair of 694 -- (IP address, port) pairs, running the TCP protocol. The port 695 -- addresses in RFC 1795 define two TCP connections between 696 -- a pair of DLSw nodes, each being used to send data in a 697 -- single direction. 698 -- Local: This end of TCP connection 699 -- Foreign: Remote end of TCP connection 700 -- 701 -- (3) Transport Connection: 702 -- It is a generic term for a full-duplex reliable connection 703 -- between DLSw nodes. This term is used to refer to the 704 -- association between DLSw nodes without being concerned 705 -- about whether TCP is the protocol or whether there are 706 -- one or two TCP connection. 707 -- (Note: for two TCP connections, the transport connection is 708 -- opened if and only if both TCP connections are operational. 709 -- Also note: sometimes race conditions will occur, but the 710 -- condition should only be temporary.) 711 -- 712 -- (4) Data Link: 713 -- An instance of OSI layer-2 procedures for exchanging information 714 -- using either connection-oriented (e.g., LLC-2) or connectionless 715 -- (e.g., LLC-1) services. A DLSw node or pair of partner nodes 716 -- switches data traffic from stations of one data link to 717 -- stations of another data link. Data link switching is 718 -- transparent to end stations. 719 -- Source: the end station which sends a message. 720 -- Destination: the end station which receives a message. 721 -- (This DLSw role is with respect to a give message) 722 -- 723 -- (5) Circuit: 724 -- End-to-end association of two DLC entities through one or 725 -- two DLSw nodes. A circuit is the concatenation of two 726 -- "data links", optionally with an intervening transport 727 -- connection. 728 -- Origin: the end station which initiates the circuit. 729 -- Target: the end station which receives the initiation. 730 -- 731 -- (6) Link Station: 732 -- It is one end of an LLC-2 connection. It performs error 733 -- recovery procedure, retries, and various timers. 734 -- DLSw terminates LLC-2 connection at each end of DLSw nodes, 735 -- thus, keepAlive and error recovery on LLC-2 connections are 736 -- kept to each side of LAN and do not flow through the WAN. 737 -- A link station is substantiated when SABME is sent/received. 738 -- All link stations have circuits, but not all circuits 739 -- have link stations. 740 -- 741 -- Key assumptions are: 742 -- (1) The MIB is designed to manage a single DLSw entity. 743 -- 744 -- (2) A DLSw may support various types of transport connections. 745 -- - This DLSw MIB module does not restrict the possibility to 746 -- have, at any given moment, more than one "transport 747 -- connection" defined or active between two DLSw's. 748 -- - However, current DLSw architecture does not provide a mechanism, 749 -- e.g., DLSw host name, to prevent two transport connections of 750 -- different types between the same two DLSw's. 751 -- 752 -- (3) This MIB assumes that interface MIB is implemented. ifIndex 753 -- is used in this MIB module. 754 -- 755 -- (4) This MIB assumes that the SDLC MIB (or an equivalent enterprise 756 -- specific MIB) is implemented, since SDLC-specific objects 757 -- are not duplicated here. 758 -- 759 -- (5) This MIB assumes that the LLC-2 MIB (or an equivalent enterprise 760 -- specific MIB) is implemented, since LLC-related objects are not 761 -- duplicated here. 762 -- 763 -- (6) All MACs, SAPs, Ring numbers, ... are in non-canonical form. 764 -- That is, the most significant bit will be transmitted first. 765 -- 766 -- ******************************************************************* 768 DLSW-MIB DEFINITIONS ::= BEGIN 770 IMPORTS 771 DisplayString, RowStatus, 772 RowPointer, TruthValue, 773 TEXTUAL-CONVENTION FROM SNMPv2-TC 774 Counter32, Gauge32, TimeTicks, 775 OBJECT-TYPE, MODULE-IDENTITY, 776 experimental, -- to be removed later 777 NOTIFICATION-TYPE FROM SNMPv2-SMI 778 MODULE-COMPLIANCE, OBJECT-GROUP, 779 NOTIFICATION-GROUP FROM SNMPv2-CONF 780 ifIndex FROM IF-MIB 781 sdlcLSAddress FROM SNA-SDLC-MIB; 783 dlsw MODULE-IDENTITY 784 LAST-UPDATED "9606040900Z" 785 ORGANIZATION "AIW DLSw MIB RIGLET and IETF DLSw MIB Working Group" 786 CONTACT-INFO 787 "David D. Chen 788 IBM Corporation 789 800 Park, Highway 54 790 Research Triangle Park, NC 27709-9990 791 Tel: 1 919 254 6182 792 E-mail: dchen@vnet.ibm.com" 793 DESCRIPTION 794 "This MIB module contains objects to manage Data Link 795 Switches." 796 ::= { experimental 68 } 798 dlswMIB OBJECT IDENTIFIER ::= { dlsw 1 } 799 dlswDomains OBJECT IDENTIFIER ::= { dlsw 2 } 801 -- ******************************************************************* 802 -- Textual convention definitions 803 -- ******************************************************************* 805 NBName ::= TEXTUAL-CONVENTION 806 STATUS current 807 DESCRIPTION 808 "Represents a single qualified NetBIOS name, which can include 809 `don't care' and `wildcard' characters to represent a number 810 of real NetBIOS names. If an individual character position in 811 the qualified name contains a `?', the corresponding character 812 position in a real NetBIOS name is a `don't care'. If the 813 qualified name ends in `*', the remainder of a real NetBIOS 814 name is a `don't care'. `*' is only considered a wildcard if it 815 appears at the end of a name." 816 SYNTAX OCTET STRING (SIZE (0..16)) 818 MacAddressNC ::= TEXTUAL-CONVENTION 819 DISPLAY-HINT "1x:" 820 STATUS current 821 DESCRIPTION 822 "Represents an 802 MAC address represented in 823 non-canonical format. That is, the most significant 824 bit will be transmitted first. If this information 825 is not available, the value is a zero length string." 826 SYNTAX OCTET STRING (SIZE (0 | 6)) 828 TAddress ::= TEXTUAL-CONVENTION 829 STATUS current 830 DESCRIPTION 831 "Denotes a transport service address. 833 For dlswTCPDomain, a TAddress is 4 octets long, 834 containing the IP-address in network-byte order." 835 SYNTAX OCTET STRING (SIZE (0..255)) 837 EndStationLocation ::= TEXTUAL-CONVENTION 838 STATUS current 839 DESCRIPTION 840 "Representing the location of an end station related 841 to the managed DLSw node." 842 SYNTAX INTEGER { 843 other (1), 844 internal (2), -- local virtual MAC address 845 remote (3), -- via DLSw partner 846 local (4) -- locally attached 847 } 849 DlcType ::= TEXTUAL-CONVENTION 850 STATUS current 851 DESCRIPTION 852 "Representing the type of DLC of an end station, if 853 applicable." 854 SYNTAX INTEGER { 855 other (1), -- not assigned yet 856 na (2), -- not applicable 857 llc (3), -- 802.2 Logical Link Control 858 sdlc (4), -- SDLC 859 qllc (5) -- QLLC 860 } 862 LFSize ::= TEXTUAL-CONVENTION 863 STATUS current 864 DESCRIPTION 865 "The largest size of the INFO field (including DLC header, 866 not including any MAC-level or framing octets). 867 64 valid values as defined by the IEEE 802.1D 868 Addendum are acceptable." 869 SYNTAX INTEGER { 870 lfs516(516), lfs635(635), lfs754(754), lfs873(873), 871 lfs993(993), lfs1112(1112), lfs1231(1231), 872 lfs1350(1350), lfs1470(1470), lfs1542(1542), 873 lfs1615(1615), lfs1688(1688), lfs1761(1761), 874 lfs1833(1833), lfs1906(1906), lfs1979(1979), 875 lfs2052(2052), lfs2345(2345), lfs2638(2638), 876 lfs2932(2932), lfs3225(3225), lfs3518(3518), 877 lfs3812(3812), lfs4105(4105), lfs4399(4399), 878 lfs4865(4865), lfs5331(5331), lfs5798(5798), 879 lfs6264(6264), lfs6730(6730), lfs7197(7197), 880 lfs7663(7663), lfs8130(8130), lfs8539(8539), 881 lfs8949(8949), lfs9358(9358), lfs9768(9768), 882 lfs10178(10178), lfs10587(10587), lfs10997(10997), 883 lfs11407(11407), lfs12199(12199), lfs12992(12992), 884 lfs13785(13785), lfs14578(14578), lfs15370(15370), 885 lfs16163(16163), lfs16956(16956), lfs17749(17749), 886 lfs20730(20730), lfs23711(23711), lfs26693(26693), 887 lfs29674(29674), lfs32655(32655), lfs38618(38618), 888 lfs41600(41600), lfs44591(44591), lfs47583(47583), 889 lfs50575(50575), lfs53567(53567), lfs56559(56559), 890 lfs59551(59551), lfs65535(65535) 891 } 893 null OBJECT IDENTIFIER ::= { 0 0 } 895 -- ******************************************************************* 896 -- DLSw Transport Domain definitions 897 -- ******************************************************************* 899 -- DLSw over TCP 900 dlswTCPDomain OBJECT IDENTIFIER ::= { dlswDomains 1 } 901 -- for an IP address of length 4: 902 -- 903 -- octets contents encoding 904 -- 1-4 IP-address network-byte order 905 -- 906 DlswTCPAddress ::= TEXTUAL-CONVENTION 907 DISPLAY-HINT "1d.1d.1d.1d" 908 STATUS current 909 DESCRIPTION 910 "Represents the IP address of a DLSw which uses 911 TCP as a transport protocol." 912 SYNTAX OCTET STRING (SIZE (4)) 914 -- ******************************************************************* 915 -- DLSw MIB Definition 916 -- ******************************************************************* 918 -- The DLSw MIB module contains an object part and a conformance part. 919 -- Object part is organized in the following groups: 920 -- (1) dlswNode -- information about this DLSw 921 -- (2) dlswTConn -- about adjacent DLSw partners 922 -- (3) dlswInterface -- about which interfaces DLSw is active on 923 -- (4) dlswDirectory -- about any directory of local/remote resources 924 -- (5) dlswCircuit -- about established circuits. 925 -- (6) dlswSdlc -- about SDLC data link switched devices 927 dlswNode OBJECT IDENTIFIER ::= { dlswMIB 1 } 928 dlswTConn OBJECT IDENTIFIER ::= { dlswMIB 2 } 929 dlswInterface OBJECT IDENTIFIER ::= { dlswMIB 3 } 930 dlswDirectory OBJECT IDENTIFIER ::= { dlswMIB 4 } 931 dlswCircuit OBJECT IDENTIFIER ::= { dlswMIB 5 } 932 dlswSdlc OBJECT IDENTIFIER ::= { dlswMIB 6 } -- SDLC 933 -- ******************************************************************* 934 -- THE NODE GROUP 935 -- ******************************************************************* 937 -- ------------------------------------------------------------------- 938 -- DLSw Node Identity 939 -- ------------------------------------------------------------------- 940 dlswNodeVersion OBJECT-TYPE 941 SYNTAX OCTET STRING (SIZE (2)) 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 "This value identifies the particular version of the DLSw 946 standard supported by this DLSw. The first octet is a 947 hexadecimal value representing the DLSw standard Version 948 number of this DLSw, and the second is a hexadecimal value 949 representing the DLSw standard Release number. This 950 information is reported in DLSw Capabilities Exchange." 951 REFERENCE 952 "DLSW: Switch-to-Switch Protocol RFC 1795" 953 ::= { dlswNode 1 } 955 dlswNodeVendorID OBJECT-TYPE 956 SYNTAX OCTET STRING (SIZE (3)) 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "The value identifies the manufacturer's IEEE-assigned 961 organizationally Unique Identifier (OUI) of this DLSw. 962 This information is reported in DLSw Capabilities 963 Exchange." 964 REFERENCE 965 "DLSW: Switch-to-Switch Protocol RFC 1795" 966 ::= { dlswNode 2 } 968 dlswNodeVersionString OBJECT-TYPE 969 SYNTAX DisplayString 970 MAX-ACCESS read-only 971 STATUS current 972 DESCRIPTION 973 "This string gives product-specific information about 974 this DLSw (e.g., product name, code release and fix level). 975 This flows in Capabilities Exchange messages." 976 REFERENCE 977 "DLSW: Switch-to-Switch Protocol RFC 1795" 978 ::= { dlswNode 3 } 980 -- ------------------------------------------------------------------- 981 -- DLSw Code Capability 982 -- ------------------------------------------------------------------- 983 dlswNodeStdPacingSupport OBJECT-TYPE 984 SYNTAX INTEGER { 985 none (1), -- does not support DLSw 986 -- Standard pacing scheme 987 adaptiveRcvWindow (2), -- the receive window size 988 -- varies 989 fixedRcvWindow (3) -- the receive window size 990 -- remains constant 991 } 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "Circuit pacing, as defined in the DLSw Standard, allows each 996 of the two DLSw nodes on a circuit to control the amount 997 of data the other is permitted to send to them. This object 998 reflects the level of support the DLSw node has for this 999 protocol. (1) means the node has no support for the standard 1000 circuit pacing flows; it may use RFC 1434+ methods only, or 1001 a proprietary flow control scheme. (2) means the node supports 1002 the standard scheme and can vary the window sizes it grants as 1003 a data receiver. (3) means the node supports the standard 1004 scheme but never varies its receive window size." 1005 ::= { dlswNode 4 } 1007 -- ------------------------------------------------------------------- 1008 -- DLSw Node Operational Objects 1009 -- ------------------------------------------------------------------- 1010 dlswNodeStatus OBJECT-TYPE 1011 SYNTAX INTEGER { 1012 active (1), 1013 inactive (2) 1014 } 1015 MAX-ACCESS read-write 1016 STATUS current 1017 DESCRIPTION 1018 "The status of the DLSw part of the system. Changing the 1019 value from active to inactive causes DLSw to take 1020 the following actions - (1) it disconnects all circuits 1021 through all DLSw partners, (2) it disconnects all 1022 transport connections to all DLSw partners, (3) it 1023 disconnects all local DLC connections, and (4) it stops 1024 processing all DLC connection set-up traffic. 1025 Since these are destructive actions, the user should 1026 query the circuit and transport connection tables in 1027 advance to understand the effect this action will have. 1028 Changing the value from inactive to active causes DLSw 1029 to come up in its initial state, i.e., transport 1030 connections established and ready to bring up circuits." 1031 ::= { dlswNode 5 } 1033 dlswNodeUpTime OBJECT-TYPE 1034 SYNTAX TimeTicks 1035 UNITS "hundredths of a second" 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "The amount of time (in hundredths of a second) since 1040 the DLSw portion of the system was last re-initialized. 1041 That is, if dlswState is in the active state, 1042 the time the dlswState entered the active state. 1043 It will remain zero if dlswState is in the 1044 inactive state." 1045 ::= { dlswNode 6 } 1047 dlswNodeVirtualSegmentLFSize OBJECT-TYPE 1048 SYNTAX LFSize 1049 MAX-ACCESS read-write 1050 STATUS current 1051 DESCRIPTION 1052 "The largest frame size (including DLC header and info field 1053 but not any MAC-level or framing octets) this DLSw can forward 1054 on any path through itself. This object can represent any box- 1055 level frame size forwarding restriction (e.g., from the use 1056 of fixed-size buffers). Some DLSw implementations will have 1057 no such restriction. 1059 This value will affect the LF size of circuits during circuit 1060 creation. The LF size of an existing circuit can be found in 1061 the RIF (Routing Information Field)." 1062 DEFVAL { lfs65535 } 1063 ::= { dlswNode 7 } 1065 -- ................................................................... 1066 -- NETBIOS Resources 1067 -- ................................................................... 1069 dlswNodeResourceNBExclusivity OBJECT-TYPE 1070 SYNTAX TruthValue 1071 MAX-ACCESS read-write 1072 STATUS current 1073 DESCRIPTION 1074 "The value of true indicates that the NetBIOS Names 1075 configured in dlswDirNBTable are the only ones accessible 1076 via this DLSw. 1078 If a node supports sending run-time capabilities exchange 1079 messages, changes to this object should cause that action. 1080 It is up to the implementation exactly when to start the 1081 run-time capabilities exchange." 1082 ::= { dlswNode 8 } 1084 -- ................................................................... 1085 -- MAC Address List 1086 -- ................................................................... 1088 dlswNodeResourceMacExclusivity OBJECT-TYPE 1089 SYNTAX TruthValue 1090 MAX-ACCESS read-write 1091 STATUS current 1092 DESCRIPTION 1093 "The value of true indicates that the MAC addresses 1094 configured in the dlswDirMacTable are the only ones 1095 accessible via this DLSw. 1097 If a node supports sending run-time capabilities exchange 1098 messages, changes to this object should cause that action. 1099 It is up to the implementation exactly when to start the 1100 run-time capabilities exchange." 1101 ::= { dlswNode 9 } 1103 -- ******************************************************************* 1104 -- TRANSPORT CONNECTION (aka: PARTNER DLSW) 1105 -- ******************************************************************* 1107 -- ------------------------------------------------------------------- 1108 -- Transport Connection Statistics Objects 1109 -- ------------------------------------------------------------------- 1110 dlswTConnStat OBJECT IDENTIFIER ::= { dlswTConn 1 } 1112 dlswTConnStatActiveConnections OBJECT-TYPE 1113 SYNTAX Gauge32 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION 1117 "The number of transport connections that are not in 1118 `disconnected' state." 1119 ::= { dlswTConnStat 1 } 1121 dlswTConnStatCloseIdles OBJECT-TYPE 1122 SYNTAX Counter32 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "The number of times transport connections in this node 1127 exited the connected state with zero active circuits on 1128 the transport connection." 1129 ::= { dlswTConnStat 2 } 1131 dlswTConnStatCloseBusys OBJECT-TYPE 1132 SYNTAX Counter32 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The number of times transport connections in this node 1137 exited the connected state with some non-zero number 1138 of active circuits on the transport connection. Normally 1139 this means the transport connection failed unexpectedly." 1140 ::= { dlswTConnStat 3 } 1142 -- ------------------------------------------------------------------- 1143 -- Transport Connection Configuration Table 1144 -- ------------------------------------------------------------------- 1145 dlswTConnConfigTable OBJECT-TYPE 1146 SYNTAX SEQUENCE OF DlswTConnConfigEntry 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "This table defines the transport connections 1151 that will be initiated or accepted by this 1152 DLSw. Structure of masks allows wildcard 1153 definition for a collection of transport 1154 connections by a conceptual row. For a 1155 specific transport connection, there may 1156 be multiple of conceptual rows match the 1157 transport address. The `best' match will 1158 the one to determine the characteristics 1159 of the transport connection." 1160 ::= { dlswTConn 2 } 1162 dlswTConnConfigEntry OBJECT-TYPE 1163 SYNTAX DlswTConnConfigEntry 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION 1167 "Each conceptual row defines a collection of 1168 transport connections." 1169 INDEX { dlswTConnConfigIndex } 1170 ::= { dlswTConnConfigTable 1 } 1172 DlswTConnConfigEntry ::= SEQUENCE { 1173 dlswTConnConfigIndex INTEGER, 1174 dlswTConnConfigTDomain OBJECT IDENTIFIER, 1175 dlswTConnConfigLocalTAddr TAddress, 1176 dlswTConnConfigRemoteTAddr TAddress, 1177 dlswTConnConfigLastModifyTime TimeTicks, 1178 dlswTConnConfigEntryType INTEGER, 1179 dlswTConnConfigGroupDefinition RowPointer, 1180 dlswTConnConfigSetupType INTEGER, 1181 dlswTConnConfigSapList OCTET STRING, 1182 dlswTConnConfigAdvertiseMacNB TruthValue, 1183 dlswTConnConfigInitCirRecvWndw INTEGER, 1184 dlswTConnConfigOpens Counter32, 1185 dlswTConnConfigRowStatus RowStatus 1186 } 1188 dlswTConnConfigIndex OBJECT-TYPE 1189 SYNTAX INTEGER (0..2147483647) 1190 MAX-ACCESS not-accessible 1191 STATUS current 1192 DESCRIPTION 1193 "The index to the conceptual row of the table. 1194 Negative numbers are not allowed. There 1195 are objects defined that point to conceptual 1196 rows of this table with this index value. 1197 Zero is used to denote that no corresponding 1198 row exists. 1200 Index values are assigned by the agent, and 1201 should not be reused but should continue to 1202 increase in value." 1203 ::= { dlswTConnConfigEntry 1 } 1205 dlswTConnConfigTDomain OBJECT-TYPE 1206 SYNTAX OBJECT IDENTIFIER 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "The object identifier which indicates the transport 1211 domain of this conceptual row." 1212 ::= { dlswTConnConfigEntry 2 } 1214 dlswTConnConfigLocalTAddr OBJECT-TYPE 1215 SYNTAX TAddress 1216 MAX-ACCESS read-create 1217 STATUS current 1218 DESCRIPTION 1219 "The local transport address for this conceptual row 1220 of the transport connection definition." 1221 ::= { dlswTConnConfigEntry 3 } 1223 dlswTConnConfigRemoteTAddr OBJECT-TYPE 1224 SYNTAX TAddress 1225 MAX-ACCESS read-create 1226 STATUS current 1227 DESCRIPTION 1228 "The remote transport address. Together with 1229 dlswTConnConfigEntryType and dlswTConnConfigGroupDefinition, 1230 the object instance of this conceptual row identifies a 1231 collection of the transport connections that will be 1232 either initiated by this DLSw or initiated by a partner 1233 DLSw and accepted by this DLSw." 1234 ::= { dlswTConnConfigEntry 4 } 1236 dlswTConnConfigLastModifyTime OBJECT-TYPE 1237 SYNTAX TimeTicks 1238 UNITS "hundredths of a second" 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "The time (in hundredths of a second) since the value of 1243 any object in this conceptual row except for 1244 dlswTConnConfigOpens was last changed. This value 1245 may be compared to dlswTConnOperConnectTime to 1246 determine whether values in this row are completely 1247 valid for a transport connection created using 1248 this row definition." 1249 ::= { dlswTConnConfigEntry 5 } 1251 dlswTConnConfigEntryType OBJECT-TYPE 1252 SYNTAX INTEGER { 1253 individual (1), 1254 global (2), 1255 group (3) 1256 } 1257 MAX-ACCESS read-create 1258 STATUS current 1259 DESCRIPTION 1260 "The object instance signifies the type of entry in the 1261 associated conceptual row. The value of `individual' 1262 means that the entry applies to a specific partner DLSw 1263 node as identified by dlswTConnConfigRemoteTAddr and 1264 dlswTConnConfigTDomain. The value of `global' 1265 means that the entry applies to all partner DLSw nodes 1266 of the TDomain. The value of 'group' means that the entry 1267 applies to a specific set of DLSw nodes in the TDomain. 1268 Any group definitions are enterprise-specific and are pointed 1269 to by dlswTConnConfigGroupDefinition. In the cases of 1270 `global' and `group', the value in dlswTConnConfigRemoteTAddr 1271 may not have any significance." 1272 ::= { dlswTConnConfigEntry 6 } 1274 dlswTConnConfigGroupDefinition OBJECT-TYPE 1275 SYNTAX RowPointer 1276 MAX-ACCESS read-create 1277 STATUS current 1278 DESCRIPTION 1279 "For conceptual rows of `individual' and `global' as 1280 specified in dlswTConnConfigEntryType, the instance 1281 of this object is `0.0'. For conceptual rows of 1282 `group', the instance points to the specific 1283 group definition." 1284 ::= { dlswTConnConfigEntry 7 } 1286 dlswTConnConfigSetupType OBJECT-TYPE 1287 SYNTAX INTEGER { 1288 other (1), 1289 activePersistent (2), 1290 activeOnDemand (3), 1291 passive (4), 1292 excluded (5) 1293 } 1294 MAX-ACCESS read-create 1295 STATUS current 1296 DESCRIPTION 1297 "This value of the instance of a conceptual row 1298 identifies the behavior of the collection of 1299 transport connections that this conceptual row 1300 defines. The value of activePersistent, activeOnDemand 1301 and passive means this DLSw will accept any transport 1302 connections, initiated by partner DLSw nodes, which 1303 are defined by this conceptual row. The value of 1304 activePersistent means this DLSw will also initiate 1305 the transport connections of this conceptual row and 1306 retry periodically if necessary. The value of 1307 activeOnDemand means this DLSw will initiate a 1308 transport connection of this conceptual row, if 1309 there is a directory cache hits. The value of 1310 other is implementation specific. The value of exclude 1311 means that the specified node is not allowed to be 1312 a partner to this DLSw node. To take a certain 1313 conceptual row definition out of service, a value of 1314 notInService for dlswTConnConfigRowStatus should be 1315 used." 1316 DEFVAL { passive } 1317 ::= { dlswTConnConfigEntry 8 } 1319 dlswTConnConfigSapList OBJECT-TYPE 1320 SYNTAX OCTET STRING (SIZE(16)) 1321 MAX-ACCESS read-create 1322 STATUS current 1323 DESCRIPTION 1324 "The SAP list indicates which SAPs are advertised to 1325 the transport connection defined by this conceptual 1326 row. Only SAPs with even numbers are represented, 1327 in the form of the most significant bit of the first 1328 octet representing the SAP 0, the next most significant 1329 bit representing the SAP 2, to the least significant 1330 bit of the last octet representing the SAP 254. Data 1331 link switching is allowed for those SAPs which have 1332 one in its corresponding bit, not allowed otherwise. 1333 The whole SAP list has to be changed together. Changing 1334 the SAP list affects only new circuit establishments 1335 and has no effect on established circuits. 1337 This list can be used to restrict specific partners 1338 from knowing about all the SAPs used by DLSw on all its 1339 interfaces (these are represented in dlswIfSapList for 1340 each interface). For instance, one may want to run NetBIOS 1341 with some partners but not others. 1343 If a node supports sending run-time capabilities exchange 1344 messages, changes to this object should cause that action. 1345 When to start the run-time capabilities exchange is 1346 implementation-specific. 1348 The DEFVAL below indicates support for SAPs 0, 4, 8, and C." 1349 DEFVAL { 'AA000000000000000000000000000000'H } 1350 ::= { dlswTConnConfigEntry 9 } 1352 dlswTConnConfigAdvertiseMacNB OBJECT-TYPE 1353 SYNTAX TruthValue 1354 MAX-ACCESS read-create 1355 STATUS current 1356 DESCRIPTION 1357 "The value of true indicates that any defined local MAC 1358 addresses and NetBIOS names will be advertised to a 1359 partner node via initial and (if supported) run-time 1360 capabilities exchange messages. The DLSw node should send 1361 the appropriate exclusivity control vector to accompany 1362 each list it sends, or to represent that the node is 1363 explicitly configured to have a null list. 1365 The value of false indicates that the DLSw node should not 1366 send a MAC address list or NetBIOS name list, and should 1367 also not send their corresponding exclusivity control 1368 vectors." 1369 DEFVAL { true } 1370 ::= { dlswTConnConfigEntry 10 } 1372 dlswTConnConfigInitCirRecvWndw OBJECT-TYPE 1373 SYNTAX INTEGER (0..65535) 1374 UNITS "SSP messages" 1375 MAX-ACCESS read-create 1376 STATUS current 1377 DESCRIPTION 1378 "The initial circuit receive pacing window size, in the unit 1379 of SSP messages, to be used for future transport connections 1380 activated using this table row. The managed node sends this 1381 value as its initial receive pacing window in its initial 1382 capabilities exchange message. Changing this value does not 1383 affect the initial circuit receive pacing window size of 1384 currently active transport connections. If the standard window 1385 pacing scheme is not supported, the value is zero. 1387 A larger receive window value may be appropriate for partners 1388 that are reachable only via physical paths that have longer 1389 network delays." 1390 DEFVAL { 1 } 1391 ::= { dlswTConnConfigEntry 11 } 1393 dlswTConnConfigOpens OBJECT-TYPE 1394 SYNTAX Counter32 1395 MAX-ACCESS read-only 1396 STATUS current 1397 DESCRIPTION 1398 "Number of times transport connections entered 1399 connected state according to the definition of 1400 this conceptual row." 1401 ::= { dlswTConnConfigEntry 12 } 1403 dlswTConnConfigRowStatus OBJECT-TYPE 1404 SYNTAX RowStatus 1405 MAX-ACCESS read-create 1406 STATUS current 1407 DESCRIPTION 1408 "This object is used by the manager to create 1409 or delete the row entry in the dlswTConnConfigTable 1410 following the RowStatus textual convention. The value 1411 of notInService will be used to take a conceptual 1412 row definition out of use." 1413 ::= { dlswTConnConfigEntry 13 } 1415 -- ------------------------------------------------------------------- 1416 -- Transport Connection Operation Table 1417 -- ------------------------------------------------------------------- 1418 -- (1) At most one transport connection can be connected between 1419 -- this DLSw and one of its DLSw partners at a given time. 1420 -- (2) Multiple transport types are supported. 1421 -- (3) Since the entries may be reused, dlswTConnOperEntryTime 1422 -- needs to be consulted for the possibility of counter reset. 1423 -- ------------------------------------------------------------------- 1425 dlswTConnOperTable OBJECT-TYPE 1426 SYNTAX SEQUENCE OF DlswTConnOperEntry 1427 MAX-ACCESS not-accessible 1428 STATUS current 1429 DESCRIPTION 1430 "A list of transport connections. It is optional but 1431 desirable for the agent to keep an entry for some 1432 period of time after the transport connection is 1433 disconnected. This allows the manager to capture 1434 additional useful information about the connection, in 1435 particular, statistical information and the cause of the 1436 disconnection." 1437 ::= { dlswTConn 3 } 1439 dlswTConnOperEntry OBJECT-TYPE 1440 SYNTAX DlswTConnOperEntry 1441 MAX-ACCESS not-accessible 1442 STATUS current 1443 DESCRIPTION 1444 "" 1445 INDEX { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr } 1446 ::= { dlswTConnOperTable 1 } 1448 DlswTConnOperEntry ::= SEQUENCE { 1449 dlswTConnOperTDomain OBJECT IDENTIFIER, 1450 dlswTConnOperLocalTAddr TAddress, 1451 dlswTConnOperRemoteTAddr TAddress, 1453 dlswTConnOperEntryTime TimeTicks, 1454 dlswTConnOperConnectTime TimeTicks, 1455 dlswTConnOperState INTEGER, 1456 dlswTConnOperConfigIndex INTEGER, 1457 dlswTConnOperFlowCntlMode INTEGER, 1459 dlswTConnOperPartnerVersion OCTET STRING, 1460 dlswTConnOperPartnerVendorID OCTET STRING, 1461 dlswTConnOperPartnerVersionStr DisplayString, 1462 dlswTConnOperPartnerInitPacingWndw INTEGER, 1464 dlswTConnOperPartnerSapList OCTET STRING, 1465 dlswTConnOperPartnerNBExcl TruthValue, 1466 dlswTConnOperPartnerMacExcl TruthValue, 1467 dlswTConnOperPartnerNBInfo INTEGER, 1468 dlswTConnOperPartnerMacInfo INTEGER, 1470 dlswTConnOperDiscTime TimeTicks, 1471 dlswTConnOperDiscReason INTEGER, 1472 dlswTConnOperDiscActiveCir INTEGER, 1474 dlswTConnOperInDataPkts Counter32, 1475 dlswTConnOperOutDataPkts Counter32, 1476 dlswTConnOperInDataOctets Counter32, 1477 dlswTConnOperOutDataOctets Counter32, 1479 dlswTConnOperInCntlPkts Counter32, 1480 dlswTConnOperOutCntlPkts Counter32, 1482 dlswTConnOperCURexSents Counter32, 1483 dlswTConnOperICRexRcvds Counter32, 1484 dlswTConnOperCURexRcvds Counter32, 1485 dlswTConnOperICRexSents Counter32, 1487 dlswTConnOperNQexSents Counter32, 1488 dlswTConnOperNRexRcvds Counter32, 1489 dlswTConnOperNQexRcvds Counter32, 1490 dlswTConnOperNRexSents Counter32, 1491 dlswTConnOperCirCreates Counter32, 1492 dlswTConnOperCircuits Gauge32 1493 } 1495 dlswTConnOperTDomain OBJECT-TYPE 1496 SYNTAX OBJECT IDENTIFIER 1497 MAX-ACCESS not-accessible 1498 STATUS current 1499 DESCRIPTION 1500 "The object identifier indicates the transport domain 1501 of this transport connection." 1502 ::= { dlswTConnOperEntry 1 } 1504 dlswTConnOperLocalTAddr OBJECT-TYPE 1505 SYNTAX TAddress 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "The local transport address for this transport connection. 1510 This value could be different from dlswTConnConfigLocalAddr, 1511 if the value of the latter were changed after this transport 1512 connection was established." 1513 ::= { dlswTConnOperEntry 2 } 1515 dlswTConnOperRemoteTAddr OBJECT-TYPE 1516 SYNTAX TAddress 1517 MAX-ACCESS not-accessible 1518 STATUS current 1519 DESCRIPTION 1520 "The remote transport address of this transport connection." 1521 ::= { dlswTConnOperEntry 3 } 1523 dlswTConnOperEntryTime OBJECT-TYPE 1524 SYNTAX TimeTicks 1525 UNITS "hundredths of a second" 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "The amount of time (in hundredths of a second) since this 1530 transport connection conceptual row was created." 1531 ::= { dlswTConnOperEntry 4 } 1533 -- ................................................................... 1534 -- DLSw Transport Connection Operational Objects 1535 -- ................................................................... 1537 dlswTConnOperConnectTime OBJECT-TYPE 1538 SYNTAX TimeTicks 1539 UNITS "hundredths of a second" 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "The amount of time (in hundredths of a second) since this 1544 transport connection last entered the 'connected' state. 1545 A value of zero means this transport connection has never 1546 been established." 1547 ::= { dlswTConnOperEntry 5 } 1549 dlswTConnOperState OBJECT-TYPE 1550 SYNTAX INTEGER { 1551 connecting (1), 1552 initCapExchange (2), 1553 connected (3), 1554 quiescing (4), 1555 disconnecting (5), 1556 disconnected (6) 1557 } 1558 MAX-ACCESS read-write 1559 STATUS current 1560 DESCRIPTION 1561 "The state of this transport connection. The transport 1562 connection enters `connecting' state when DLSw makes 1563 a connection request to the transport layer. Once initial 1564 Capabilities Exchange is sent, the transport connection 1565 enters enters `initCapExchange' state. When partner 1566 capabilities have been determined and the transport 1567 connection is ready for sending CanUReach (CUR) messages, 1568 it moves to the `connected' state. When DLSw is in the 1569 process of bringing down the connection, it is in the 1570 `disconnecting' state. When the transport layer 1571 indicates one of its connections is disconnected, the 1572 transport connection moves to the `disconnected' state. 1574 Whereas all of the values will be returned in response 1575 to a management protocol retrieval operation, only two 1576 values may be specified in a management protocol set 1577 operation: `quiescing' and `disconnecting'. Changing 1578 the value to `quiescing' prevents new circuits from being 1579 established, and will cause a transport disconnect when 1580 the last circuit on the connection goes away. Changing 1581 the value to `disconnecting' will force off all circuits 1582 immediately and bring the connection to `disconnected' 1583 state." 1584 ::= { dlswTConnOperEntry 6 } 1586 dlswTConnOperConfigIndex OBJECT-TYPE 1587 SYNTAX INTEGER (0..2147483647) 1588 MAX-ACCESS read-only 1589 STATUS current 1590 DESCRIPTION 1591 "The value of dlswTConnConfigIndex of the dlswTConnConfigEntry 1592 that governs the configuration information used by this 1593 dlswTConnOperEntry. The manager can therefore normally 1594 examine both configured and operational information 1595 for this transport connection. 1597 This value is zero if the corresponding dlswTConnConfigEntry 1598 was deleted after the creation of this dlswTConnOperEntry. 1599 If some fields in the former were changed but the conceptual 1600 row was not deleted, some configuration information may not 1601 be valid for this operational transport connection. The 1602 manager can compare dlswTConnOperConnectTime and 1603 dlswTConnConfigLastModifyTime to determine if this condition 1604 exists." 1605 ::= { dlswTConnOperEntry 7 } 1607 -- ................................................................... 1608 -- Transport Connection Characteristics 1609 -- ................................................................... 1611 dlswTConnOperFlowCntlMode OBJECT-TYPE 1612 SYNTAX INTEGER { 1613 undetermined (1), 1614 pacing (2), -- DLSw standard flow control 1615 other (3) -- non-DLSw standard flow control 1616 } 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "The flow control mechanism in use on this transport connection. 1621 This value is undetermined (1) before the mode of flow control 1622 can be established on a new transport connection (i.e., after 1623 CapEx is sent but before Capex or other SSP control messages 1624 have been received). Pacing (2) indicates that the standard 1625 RFC 1795 pacing mechanism is in use. Other (3) may be either 1626 the RFC 1434+ xBusy mechanism operating to a back-level DLSw, 1627 or a vendor-specific flow control method. Whether it is xBusy 1628 or not can be inferred from dlswTConnOperPartnerVersion." 1629 ::= { dlswTConnOperEntry 8 } 1631 -- ................................................................... 1633 dlswTConnOperPartnerVersion OBJECT-TYPE 1634 SYNTAX OCTET STRING (SIZE (0 | 2)) 1635 MAX-ACCESS read-only 1636 STATUS current 1637 DESCRIPTION 1638 "This value identifies which version (first octet) and release 1639 (second octet) of the DLSw standard is supported by this 1640 partner DLSw. This information is obtained from a DLSw 1641 capabilities exchange message received from the partner DLSw. 1642 A string of zero length is returned before a Capabilities 1643 Exchange message is received, or if one is never received. 1644 A conceptual row with a dlswTConnOperState of `connected' but 1645 a zero length partner version indicates that the partner is 1646 a non-standard DLSw partner. 1648 If an implementation chooses to keep dlswTConnOperEntrys in 1649 the `disconnected' state, this value should remain unchanged." 1650 REFERENCE 1651 "DLSW: Switch-to-Switch Protocol RFC 1795" 1652 ::= { dlswTConnOperEntry 9 } 1654 dlswTConnOperPartnerVendorID OBJECT-TYPE 1655 SYNTAX OCTET STRING (SIZE (0 | 3)) 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "This value identifies the IEEE-assigned organizationally 1660 Unique Identifier (OUI) of the maker of this partner 1661 DLSw. This information is obtained from a DLSw 1662 capabilities exchange message received from the partner DLSw. 1663 A string of zero length is returned before a Capabilities 1664 Exchange message is received, or if one is never received. 1666 If an implementation chooses to keep dlswTConnOperEntrys in 1667 the `disconnected' state, this value should remain unchanged." 1668 ::= { dlswTConnOperEntry 10 } 1670 dlswTConnOperPartnerVersionStr OBJECT-TYPE 1671 SYNTAX DisplayString (SIZE (0..253)) 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "This value identifies the particular product version (e.g., 1676 product name, code level, fix level) of this partner DLSw. 1677 The format of the actual version string is vendor-specific. 1678 This information is obtained from a DLSw capabilities exchange 1679 message received from the partner DLSw. 1680 A string of zero length is returned before a Capabilities 1681 Exchange message is received, if one is never received, or 1682 if one is received but it does not contain a version string. 1684 If an implementation chooses to keep dlswTConnOperEntrys in 1685 the `disconnected' state, this value should remain unchanged." 1686 REFERENCE 1687 "DLSW: Switch-to-Switch Protocol RFC 1795" 1688 ::= { dlswTConnOperEntry 11 } 1690 dlswTConnOperPartnerInitPacingWndw OBJECT-TYPE 1691 SYNTAX INTEGER (0..65535) 1692 MAX-ACCESS read-only 1693 STATUS current 1694 DESCRIPTION 1695 "The value of the partner initial receive pacing window. This 1696 is our initial send pacing window for all new circuits on this 1697 transport connection, as modified and granted by the first flow 1698 control indication the partner sends on each circuit. 1699 This information is obtained from a DLSw capabilities exchange 1700 message received from the partner DLSw. 1701 A value of zero is returned before a Capabilities 1702 Exchange message is received, or if one is never received. 1704 If an implementation chooses to keep dlswTConnOperEntrys in 1705 the `disconnected' state, this value should remain unchanged." 1706 REFERENCE 1707 "DLSW: Switch-to-Switch Protocol RFC 1795" 1708 ::= { dlswTConnOperEntry 12 } 1710 -- ................................................................... 1712 dlswTConnOperPartnerSapList OBJECT-TYPE 1713 SYNTAX OCTET STRING (SIZE (0 | 16)) 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "The Supported SAP List received in the capabilities 1718 exchange message from the partner DLSw. This list has 1719 the same format described for dlswTConnConfigSapList. 1720 A string of zero length is returned before a Capabilities 1721 Exchange message is received, or if one is never received. 1723 If an implementation chooses to keep dlswTConnOperEntrys in 1724 the `disconnected' state, this value should remain unchanged." 1725 ::= { dlswTConnOperEntry 13 } 1727 dlswTConnOperPartnerNBExcl OBJECT-TYPE 1728 SYNTAX TruthValue 1729 MAX-ACCESS read-only 1730 STATUS current 1731 DESCRIPTION 1732 "The value of true signifies that the NetBIOS names received 1733 from this partner in the NetBIOS name list in its capabilities 1734 exchange message are the only NetBIOS names reachable by 1735 that partner. `False' indicates that other NetBIOS names may 1736 be reachable. `False' should be returned before a Capabilities 1737 Exchange message is received, if one is never received, or if 1738 one is received without a NB Name Exclusivity CV. 1740 If an implementation chooses to keep dlswTConnOperEntrys in 1741 the `disconnected' state, this value should remain unchanged." 1742 ::= { dlswTConnOperEntry 14 } 1744 dlswTConnOperPartnerMacExcl OBJECT-TYPE 1745 SYNTAX TruthValue 1746 MAX-ACCESS read-only 1747 STATUS current 1748 DESCRIPTION 1749 "The value of true signifies that the MAC addresses received 1750 from this partner in the MAC address list in its capabilities 1751 exchange message are the only MAC addresses reachable by 1752 that partner. `False' indicates that other MAC addresses may 1753 be reachable. `False' should be returned before a Capabilities 1754 Exchange message is received, if one is never received, or if 1755 one is received without a MAC Address Exclusivity CV. 1757 If an implementation chooses to keep dlswTConnOperEntrys in 1758 the `disconnected' state, this value should remain unchanged." 1759 ::= { dlswTConnOperEntry 15 } 1761 dlswTConnOperPartnerNBInfo OBJECT-TYPE 1762 SYNTAX INTEGER { 1763 none (1), -- none is kept 1764 partial (2), -- partial list is kept 1765 complete (3), -- complete list is kept 1766 notApplicable (4) 1767 } 1768 MAX-ACCESS read-only 1769 STATUS current 1770 DESCRIPTION 1771 "It is up to this DSLw whether to keep either none, some, 1772 or all of the NetBIOS name list that was received in 1773 the capabilities exchange message sent by this partner DLSw. 1774 This object identifies how much information was kept by 1775 this DLSw. These names are stored as userConfigured 1776 remote entries in dlswDirNBTable. 1777 A value of (4), notApplicable, should be returned before 1778 a Capabilities Exchange message is received, or if one is 1779 never received. 1781 If an implementation chooses to keep dlswTConnOperEntrys in 1782 the `disconnected' state, this value should remain unchanged." 1783 ::= { dlswTConnOperEntry 16 } 1785 dlswTConnOperPartnerMacInfo OBJECT-TYPE 1786 SYNTAX INTEGER { 1787 none (1), -- none is kept 1788 partial (2), -- partial list is kept 1789 complete (3), -- complete list is kept 1790 notApplicable (4) 1791 } 1792 MAX-ACCESS read-only 1793 STATUS current 1794 DESCRIPTION 1795 "It is up to this DLSw whether to keep either none, some, 1796 or all of the MAC address list that was received in the 1797 capabilities exchange message sent by this partner DLSw. 1798 This object identifies how much information was kept by 1799 this DLSw. These names are stored as userConfigured 1800 remote entries in dlswDirMACTable. 1801 A value of (4), notApplicable, should be returned before 1802 a Capabilities Exchange message is received, or if one is 1803 never received. 1805 If an implementation chooses to keep dlswTConnOperEntrys in 1806 the `disconnected' state, this value should remain unchanged." 1807 ::= { dlswTConnOperEntry 17 } 1809 -- ................................................................... 1810 -- Information about the last disconnect of this transport connection. 1811 -- These objects make sense only for implementations that keep 1812 -- transport connection information around after disconnection. 1813 -- ................................................................... 1814 dlswTConnOperDiscTime OBJECT-TYPE 1815 SYNTAX TimeTicks 1816 UNITS "hundredths of a second" 1817 MAX-ACCESS read-only 1818 STATUS current 1819 DESCRIPTION 1820 "The amount of time (in hundredths of a second) since the 1821 dlswTConnOperState last entered `disconnected' state." 1822 ::= { dlswTConnOperEntry 18 } 1824 dlswTConnOperDiscReason OBJECT-TYPE 1825 SYNTAX INTEGER { 1826 other (1), 1827 capExFailed (2), 1828 transportLayerDisc (3), 1829 operatorCommand (4), 1830 lastCircuitDiscd (5), 1831 protocolError (6) 1832 } 1833 MAX-ACCESS read-only 1834 STATUS current 1835 DESCRIPTION 1836 "This object signifies the reason that either prevented the 1837 transport connection from entering the connected state, or 1838 caused the transport connection to enter the disconnected 1839 state." 1840 ::= { dlswTConnOperEntry 19 } 1842 dlswTConnOperDiscActiveCir OBJECT-TYPE 1843 SYNTAX INTEGER (0..2147483647) 1844 MAX-ACCESS read-only 1845 STATUS current 1846 DESCRIPTION 1847 "The number of circuits active (not in DISCONNECTED state) 1848 at the time the transport connection was last disconnected. 1849 This value is zero if the transport connection has never 1850 been connected." 1851 ::= { dlswTConnOperEntry 20 } 1853 -- ................................................................... 1854 -- Transport Connection Statistics 1855 -- (1) Traffic counts 1856 -- ................................................................... 1857 dlswTConnOperInDataPkts OBJECT-TYPE 1858 SYNTAX Counter32 1859 UNITS "SSP messages" 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "The number of Switch-to-Switch Protocol (SSP) messages of 1864 type DGRMFRAME, DATAFRAME, or INFOFRAME received on this 1865 transport connection." 1866 ::= { dlswTConnOperEntry 21 } 1868 dlswTConnOperOutDataPkts OBJECT-TYPE 1869 SYNTAX Counter32 1870 UNITS "SSP messages" 1871 MAX-ACCESS read-only 1872 STATUS current 1873 DESCRIPTION 1874 "The number of Switch-to-Switch Protocol (SSP) messages of 1875 type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this 1876 transport connection." 1877 ::= { dlswTConnOperEntry 22 } 1879 dlswTConnOperInDataOctets OBJECT-TYPE 1880 SYNTAX Counter32 1881 UNITS "octets" 1882 MAX-ACCESS read-only 1883 STATUS current 1884 DESCRIPTION 1885 "The number octets in Switch-to-Switch Protocol (SSP) messages 1886 of type DGRMFRAME, DATAFRAME, or INFOFRAME received on this 1887 transport connection. Each message is counted starting with 1888 the first octet following the SSP message header." 1889 ::= { dlswTConnOperEntry 23 } 1891 dlswTConnOperOutDataOctets OBJECT-TYPE 1892 SYNTAX Counter32 1893 UNITS "octets" 1894 MAX-ACCESS read-only 1895 STATUS current 1896 DESCRIPTION 1897 "The number octets in Switch-to-Switch Protocol (SSP) messages 1898 of type DGRMFRAME, DATAFRAME, or INFOFRAME transmitted on this 1899 transport connection. Each message is counted starting with 1900 the first octet following the SSP message header." 1901 ::= { dlswTConnOperEntry 24 } 1903 dlswTConnOperInCntlPkts OBJECT-TYPE 1904 SYNTAX Counter32 1905 UNITS "SSP messages" 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "The number of Switch-to-Switch Protocol (SSP) messages 1910 received on this transport connection which were not of 1911 type DGRMFRAME, DATAFRAME, or INFOFRAME." 1912 ::= { dlswTConnOperEntry 25 } 1914 dlswTConnOperOutCntlPkts OBJECT-TYPE 1915 SYNTAX Counter32 1916 UNITS "SSP messages" 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "The number of Switch-to-Switch Protocol (SSP) messages of 1921 transmitted on this transport connection which were not of 1922 type DGRMFRAME, DATAFRAME, or INFOFRAME." 1923 ::= { dlswTConnOperEntry 26 } 1925 -- ................................................................... 1926 -- (2) Directory activities (Explorer messages) 1927 -- ................................................................... 1929 dlswTConnOperCURexSents OBJECT-TYPE 1930 SYNTAX Counter32 1931 MAX-ACCESS read-only 1932 STATUS current 1933 DESCRIPTION 1934 "The number of CanUReach_ex messages sent on this transport 1935 connection." 1936 ::= { dlswTConnOperEntry 27 } 1938 dlswTConnOperICRexRcvds OBJECT-TYPE 1939 SYNTAX Counter32 1940 MAX-ACCESS read-only 1941 STATUS current 1942 DESCRIPTION 1943 "The number of ICanReach_ex messages received on this transport 1944 connection." 1945 ::= { dlswTConnOperEntry 28 } 1947 dlswTConnOperCURexRcvds OBJECT-TYPE 1948 SYNTAX Counter32 1949 MAX-ACCESS read-only 1950 STATUS current 1951 DESCRIPTION 1952 "The number of CanUReach_ex messages received on this transport 1953 connection." 1954 ::= { dlswTConnOperEntry 29 } 1956 dlswTConnOperICRexSents OBJECT-TYPE 1957 SYNTAX Counter32 1958 MAX-ACCESS read-only 1959 STATUS current 1960 DESCRIPTION 1961 "The number of ICanReach_ex messages sent on this transport 1962 connection." 1963 ::= { dlswTConnOperEntry 30 } 1965 -- ................................................................... 1967 dlswTConnOperNQexSents OBJECT-TYPE 1968 SYNTAX Counter32 1969 MAX-ACCESS read-only 1970 STATUS current 1971 DESCRIPTION 1972 "The number of NetBIOS_NQ_ex (NetBIOS Name Query-explorer) 1973 messages sent on this transport connection." 1974 ::= { dlswTConnOperEntry 31 } 1976 dlswTConnOperNRexRcvds OBJECT-TYPE 1977 SYNTAX Counter32 1978 MAX-ACCESS read-only 1979 STATUS current 1980 DESCRIPTION 1981 "The number of NETBIOS_NR_ex (NetBIOS Name Recognized-explorer) 1982 messages received on this transport connection." 1983 ::= { dlswTConnOperEntry 32 } 1985 dlswTConnOperNQexRcvds OBJECT-TYPE 1986 SYNTAX Counter32 1987 MAX-ACCESS read-only 1988 STATUS current 1989 DESCRIPTION 1990 "The number of NETBIOS_NQ_ex messages received on this 1991 transport connection." 1992 ::= { dlswTConnOperEntry 33 } 1994 dlswTConnOperNRexSents OBJECT-TYPE 1995 SYNTAX Counter32 1996 MAX-ACCESS read-only 1997 STATUS current 1998 DESCRIPTION 1999 "The number of NETBIOS_NR_ex messages sent on this transport 2000 connection." 2001 ::= { dlswTConnOperEntry 34 } 2003 -- ................................................................... 2004 -- (3) Circuit activities on each transport connection 2005 -- ................................................................... 2006 dlswTConnOperCirCreates OBJECT-TYPE 2007 SYNTAX Counter32 2008 MAX-ACCESS read-only 2009 STATUS current 2010 DESCRIPTION 2011 "The number of times that circuits entered `circuit_established' 2012 state (not counting transitions from `circuit_restart')." 2013 ::= { dlswTConnOperEntry 35 } 2015 dlswTConnOperCircuits OBJECT-TYPE 2016 SYNTAX Gauge32 2017 MAX-ACCESS read-only 2018 STATUS current 2019 DESCRIPTION 2020 "The number of currently active circuits on this transport 2021 connection, where `active' means not in `disconnected' state." 2022 ::= { dlswTConnOperEntry 36 } 2024 -- ------------------------------------------------------------------- 2025 -- Transport Connection Specific 2026 -- ------------------------------------------------------------------- 2027 dlswTConnSpecific OBJECT IDENTIFIER ::= { dlswTConn 4 } 2028 dlswTConnTcp OBJECT IDENTIFIER ::= { dlswTConnSpecific 1 } 2030 -- ................................................................... 2031 -- TCP Transport Connection Specific -- Configuration 2032 -- ................................................................... 2033 dlswTConnTcpConfigTable OBJECT-TYPE 2034 SYNTAX SEQUENCE OF DlswTConnTcpConfigEntry 2035 MAX-ACCESS not-accessible 2036 STATUS current 2037 DESCRIPTION 2038 "This table defines the TCP transport connections that 2039 will be either initiated by or accepted by this DSLw. 2040 It augments the entries in dlswTConnConfigTable whose domain 2041 is dlswTCPDomain." 2042 ::= { dlswTConnTcp 1 } 2044 dlswTConnTcpConfigEntry OBJECT-TYPE 2045 SYNTAX DlswTConnTcpConfigEntry 2046 MAX-ACCESS not-accessible 2047 STATUS current 2048 DESCRIPTION 2049 "Each conceptual row defines parameters that are 2050 specific to dlswTCPDomain transport connections." 2051 INDEX { dlswTConnConfigIndex } 2052 ::= { dlswTConnTcpConfigTable 1 } 2054 DlswTConnTcpConfigEntry ::= SEQUENCE { 2055 dlswTConnTcpConfigKeepAliveInt INTEGER, 2056 dlswTConnTcpConfigTcpConnections INTEGER, 2057 dlswTConnTcpConfigMaxSegmentSize INTEGER 2058 } 2060 dlswTConnTcpConfigKeepAliveInt OBJECT-TYPE 2061 SYNTAX INTEGER (0..1800) 2062 UNITS "seconds" 2063 MAX-ACCESS read-create 2064 STATUS current 2065 DESCRIPTION 2066 "The time in seconds between TCP keepAlive messages when 2067 no traffic is flowing. Zero signifies no keepAlive protocol. 2068 Changes take effect only for new TCP connections." 2069 DEFVAL { 0 } 2070 ::= { dlswTConnTcpConfigEntry 1 } 2072 dlswTConnTcpConfigTcpConnections OBJECT-TYPE 2073 SYNTAX INTEGER (1..16) 2074 MAX-ACCESS read-create 2075 STATUS current 2076 DESCRIPTION 2077 "This is our preferred number of TCP connections within a 2078 TCP transport connection. The actual number used is negotiated 2079 at capabilities exchange time. Changes take effect only 2080 for new transport connections." 2081 DEFVAL { 2 } 2082 ::= { dlswTConnTcpConfigEntry 2 } 2084 dlswTConnTcpConfigMaxSegmentSize OBJECT-TYPE 2085 SYNTAX INTEGER (0..65535) 2086 UNITS "packets" 2087 MAX-ACCESS read-create 2088 STATUS current 2089 DESCRIPTION 2090 "This is the number of bytes that this node is 2091 willing to receive over the read TCP connection(s). 2092 Changes take effect for new transport connections." 2093 DEFVAL { 4096 } 2094 ::= { dlswTConnTcpConfigEntry 3 } 2096 -- ................................................................... 2097 -- TCP Transport Connection Specific -- Operation 2098 -- ................................................................... 2099 dlswTConnTcpOperTable OBJECT-TYPE 2100 SYNTAX SEQUENCE OF DlswTConnTcpOperEntry 2101 MAX-ACCESS not-accessible 2102 STATUS current 2103 DESCRIPTION 2104 "A list of TCP transport connections. It is optional 2105 but desirable for the agent to keep an entry for some 2106 period of time after the transport connection is 2107 disconnected. This allows the manager to capture 2108 additional useful information about the connection, in 2109 particular, statistical information and the cause of the 2110 disconnection." 2111 ::= { dlswTConnTcp 2 } 2113 dlswTConnTcpOperEntry OBJECT-TYPE 2114 SYNTAX DlswTConnTcpOperEntry 2115 MAX-ACCESS not-accessible 2116 STATUS current 2117 DESCRIPTION 2118 "" 2119 INDEX { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr } 2120 ::= { dlswTConnTcpOperTable 1 } 2122 DlswTConnTcpOperEntry ::= SEQUENCE { 2123 dlswTConnTcpOperKeepAliveInt INTEGER, 2124 dlswTConnTcpOperPrefTcpConnections INTEGER, 2125 dlswTConnTcpOperTcpConnections INTEGER 2126 } 2128 dlswTConnTcpOperKeepAliveInt OBJECT-TYPE 2129 SYNTAX INTEGER (0..1800) 2130 UNITS "seconds" 2131 MAX-ACCESS read-only 2132 STATUS current 2133 DESCRIPTION 2134 "The time in seconds between TCP keepAlive messages when 2135 no traffic is flowing. Zero signifies no keepAlive protocol is 2136 operating." 2137 ::= { dlswTConnTcpOperEntry 1 } 2139 dlswTConnTcpOperPrefTcpConnections OBJECT-TYPE 2140 SYNTAX INTEGER (1..16) 2141 MAX-ACCESS read-only 2142 STATUS current 2143 DESCRIPTION 2144 "This is the number of TCP connections preferred by this DLSw 2145 partner, as received in its capabilities exchange message." 2146 ::= { dlswTConnTcpOperEntry 2 } 2148 dlswTConnTcpOperTcpConnections OBJECT-TYPE 2149 SYNTAX INTEGER (1..16) 2150 MAX-ACCESS read-only 2151 STATUS current 2152 DESCRIPTION 2153 "This is the actual current number of TCP connections within 2154 this transport connection." 2155 ::= { dlswTConnTcpOperEntry 3 } 2157 -- ******************************************************************* 2158 -- DLSW INTERFACE GROUP 2159 -- ******************************************************************* 2161 dlswIfTable OBJECT-TYPE 2162 SYNTAX SEQUENCE OF DlswIfEntry 2163 MAX-ACCESS not-accessible 2164 STATUS current 2165 DESCRIPTION 2166 "The list of interfaces on which DLSw is active." 2167 ::= { dlswInterface 1 } 2169 dlswIfEntry OBJECT-TYPE 2170 SYNTAX DlswIfEntry 2171 MAX-ACCESS not-accessible 2172 STATUS current 2173 DESCRIPTION 2174 "" 2175 INDEX { ifIndex } 2176 ::= { dlswIfTable 1 } 2178 DlswIfEntry ::= SEQUENCE { 2179 dlswIfRowStatus RowStatus, 2180 dlswIfVirtualSegment INTEGER, 2181 dlswIfSapList OCTET STRING 2182 } 2184 dlswIfRowStatus OBJECT-TYPE 2185 SYNTAX RowStatus 2186 MAX-ACCESS read-create 2187 STATUS current 2188 DESCRIPTION 2189 "This object is used by the manager to create 2190 or delete the row entry in the dlswIfTable 2191 following the RowStatus textual convention." 2192 ::= { dlswIfEntry 1 } 2194 dlswIfVirtualSegment OBJECT-TYPE 2195 SYNTAX INTEGER (0..4095 | 65535) 2196 MAX-ACCESS read-create 2197 STATUS current 2198 DESCRIPTION 2199 "The segment number that uniquely identifies the virtual 2200 segment to which this DLSw interface is connected. 2202 Current source routing protocols limit this value to 2203 the range 0 - 4095. (The value 0 is used by some 2204 management applications for special test cases.) 2205 A value of 65535 signifies that no virtual segment 2206 is assigned to this interface. For instance, 2207 in a non-source routing environment, segment number 2208 assignment is not required." 2209 DEFVAL { 65535 } 2210 ::= { dlswIfEntry 2 } 2212 dlswIfSapList OBJECT-TYPE 2213 SYNTAX OCTET STRING (SIZE(16)) 2214 MAX-ACCESS read-create 2215 STATUS current 2216 DESCRIPTION 2217 "The SAP list indicates which SAPs are allowed to be 2218 data link switched through this interface. This list 2219 has the same format described for dlswTConnConfigSapList. 2221 When changes to this object take effect is implementation- 2222 specific. Turning off a particular SAP can destroy 2223 active circuits that are using that SAP. An agent 2224 implementation may reject such changes until there are no 2225 active circuits if it so chooses. In this case, it is up 2226 to the manager to close the circuits first, using 2227 dlswCircuitState. 2229 The DEFVAL below indicates support for SAPs 0, 4, 8, and C." 2230 DEFVAL { 'AA000000000000000000000000000000'H } 2231 ::= { dlswIfEntry 3 } 2233 -- ******************************************************************* 2234 -- DIRECTORY 2235 -- Directory services caches the locations of MAC addresses 2236 -- and NetBIOS names. For resources which are attached via 2237 -- local interfaces, the ifIndex may be cached, and for 2238 -- resources which are reachable via a DLSw partner, the 2239 -- transport address of the DLSw partner is cached. 2240 -- ******************************************************************* 2242 -- ------------------------------------------------------------------- 2243 -- Directory Related Statistical Objects 2244 -- ------------------------------------------------------------------- 2245 dlswDirStat OBJECT IDENTIFIER ::= { dlswDirectory 1 } 2247 dlswDirMacEntries OBJECT-TYPE 2248 SYNTAX Gauge32 2249 MAX-ACCESS read-only 2250 STATUS current 2251 DESCRIPTION 2252 "The current total number of entries in the dlswDirMacTable." 2253 ::= { dlswDirStat 1 } 2255 dlswDirMacCacheHits OBJECT-TYPE 2256 SYNTAX Counter32 2257 MAX-ACCESS read-only 2258 STATUS current 2259 DESCRIPTION 2260 "The number of times a cache search for a particular MAC address 2261 resulted in success." 2262 ::= { dlswDirStat 2 } 2264 dlswDirMacCacheMisses OBJECT-TYPE 2265 SYNTAX Counter32 2266 MAX-ACCESS read-only 2267 STATUS current 2268 DESCRIPTION 2269 "The number of times a cache search for a particular MAC address 2270 resulted in failure." 2271 ::= { dlswDirStat 3 } 2273 dlswDirMacCacheNextIndex OBJECT-TYPE 2274 SYNTAX INTEGER (0..2147483647) 2275 MAX-ACCESS read-only 2276 STATUS current 2277 DESCRIPTION 2278 "The next value of dlswDirMacIndex to be assigned by 2279 the agent. A retrieval of this object atomically reserves 2280 the returned value for use by the manager to create a row 2281 in dlswDirMacTable. This makes it possible for the agent 2282 to control the index space of the MAC address cache, yet 2283 allows the manager to administratively create new rows." 2284 ::= { dlswDirStat 4 } 2286 dlswDirNBEntries OBJECT-TYPE 2287 SYNTAX Gauge32 2288 MAX-ACCESS read-only 2289 STATUS current 2290 DESCRIPTION 2291 "The current total number of entries in the dlswDirNBTable." 2292 ::= { dlswDirStat 5 } 2294 dlswDirNBCacheHits OBJECT-TYPE 2295 SYNTAX Counter32 2296 MAX-ACCESS read-only 2297 STATUS current 2298 DESCRIPTION 2299 "The number of times a cache search for a particular NetBIOS 2300 name resulted in success." 2301 ::= { dlswDirStat 6 } 2303 dlswDirNBCacheMisses OBJECT-TYPE 2304 SYNTAX Counter32 2305 MAX-ACCESS read-only 2306 STATUS current 2307 DESCRIPTION 2308 "The number of times a cache search for a particular NetBIOS 2309 name resulted in failure." 2310 ::= { dlswDirStat 7 } 2312 dlswDirNBCacheNextIndex OBJECT-TYPE 2313 SYNTAX INTEGER (0..2147483647) 2314 MAX-ACCESS read-only 2315 STATUS current 2316 DESCRIPTION 2317 "The next value of dlswDirNBIndex to be assigned by the 2318 agent. A retrieval of this object atomically reserves 2319 the returned value for use by the manager to create 2320 a row in dlswDirNBTable. This makes it possible for the 2321 agent to control the index space for the NetBIOS name 2322 cache, yet allows the manager to administratively 2323 create new rows." 2324 ::= { dlswDirStat 8 } 2326 -- ------------------------------------------------------------------- 2327 -- Directory Cache 2328 -- ------------------------------------------------------------------- 2329 dlswDirCache OBJECT IDENTIFIER ::= { dlswDirectory 2 } 2331 -- ................................................................... 2332 -- Directory for MAC Addresses. 2333 -- All Possible combinations of values of these objects. 2334 -- 2335 -- EntryType LocationType Location Status 2336 -- -------------- ------------ ------------------ -------------- 2337 -- userConfigured local ifEntry or 0.0 reachable, or 2338 -- notReachable, or 2339 -- unknown 2340 -- userConfigured remote TConnConfigEntry reachable, or 2341 -- notReachable, or 2342 -- unknown 2343 -- partnerCapExMsg remote TConnOperEntry unknown 2344 -- dynamic local ifEntry or 0.0 reachable 2345 -- dynamic remote TConnOperEntry reachable 2346 -- 2347 -- ................................................................... 2348 dlswDirMacTable OBJECT-TYPE 2349 SYNTAX SEQUENCE OF DlswDirMacEntry 2350 MAX-ACCESS not-accessible 2351 STATUS current 2352 DESCRIPTION 2353 "This table contains locations of MAC addresses. 2355 They could be either verified or not verified, 2356 local or remote, and configured locally or learned 2357 from either Capabilities Exchange messages or 2358 directory searches." 2359 ::= { dlswDirCache 1 } 2361 dlswDirMacEntry OBJECT-TYPE 2362 SYNTAX DlswDirMacEntry 2363 MAX-ACCESS not-accessible 2364 STATUS current 2365 DESCRIPTION 2366 "Indexed by dlswDirMacIndex." 2367 INDEX { dlswDirMacIndex } 2368 ::= { dlswDirMacTable 1 } 2370 DlswDirMacEntry ::= SEQUENCE { 2371 dlswDirMacIndex INTEGER, 2372 dlswDirMacMac MacAddressNC, 2373 dlswDirMacMask MacAddressNC, 2374 dlswDirMacEntryType INTEGER, 2375 dlswDirMacLocationType INTEGER, 2376 dlswDirMacLocation RowPointer, 2377 dlswDirMacStatus INTEGER, 2378 dlswDirMacLFSize LFSize, 2379 dlswDirMacRowStatus RowStatus 2380 } 2382 dlswDirMacIndex OBJECT-TYPE 2383 SYNTAX INTEGER (0..2147483647) 2384 MAX-ACCESS not-accessible 2385 STATUS current 2386 DESCRIPTION 2387 "Uniquely identifies a conceptual row of this table." 2388 ::= { dlswDirMacEntry 1 } 2390 dlswDirMacMac OBJECT-TYPE 2391 SYNTAX MacAddressNC 2392 MAX-ACCESS read-create 2393 STATUS current 2394 DESCRIPTION 2395 "The MAC address, together with the dlswDirMacMask, 2396 specifies a set of MAC addresses that are defined or 2397 discovered through an interface or partner DLSw nodes." 2398 ::= { dlswDirMacEntry 2 } 2400 dlswDirMacMask OBJECT-TYPE 2401 SYNTAX MacAddressNC 2402 MAX-ACCESS read-create 2403 STATUS current 2404 DESCRIPTION 2405 "The MAC address mask, together with the dlswDirMacMac, 2406 specifies a set of MAC addresses that are defined or 2407 discovered through an interface or partner DLSw nodes." 2408 DEFVAL { 'FFFFFFFFFFFF'H } 2409 ::= { dlswDirMacEntry 3 } 2411 dlswDirMacEntryType OBJECT-TYPE 2412 SYNTAX INTEGER { 2413 other (1), 2414 userConfiguredPublic (2), 2415 userConfiguredPrivate (3), 2416 partnerCapExMsg (4), 2417 dynamic (5) 2418 } 2419 MAX-ACCESS read-create 2420 STATUS current 2421 DESCRIPTION 2422 "The cause of the creation of this conceptual row. 2423 It could be one of the three methods: (1) user 2424 configured, including via management protocol 2425 set operations, configuration file, command line 2426 or equivalent methods; (2) learned from the 2427 partner DLSw Capabilities Exchange messages; 2428 and (3) dynamic, e.g., learned from ICanReach 2429 messages, or LAN explorer frames. Since only 2430 individual MAC addresses can be dynamically learned, 2431 dynamic entries will all have a mask of all FFs. 2433 The public versus private distinction for user- 2434 configured resources applies only to local resources 2435 (UC remote resources are private), and indicates 2436 whether that resource should be advertised in 2437 capabilities exchange messages sent by this node." 2438 DEFVAL { userConfiguredPublic } 2439 ::= { dlswDirMacEntry 4 } 2441 dlswDirMacLocationType OBJECT-TYPE 2442 SYNTAX INTEGER { 2443 other (1), 2444 local (2), 2445 remote (3) 2446 } 2447 MAX-ACCESS read-create 2448 STATUS current 2449 DESCRIPTION 2450 "The location of the resource (or a collection of 2451 resources using a mask) of this conceptual row 2452 is either (1) local - the resource is reachable 2453 via an interface, or (2) remote - the resource 2454 is reachable via a partner DLSw node (or a set 2455 of partner DLSw nodes)." 2456 DEFVAL { local } 2457 ::= { dlswDirMacEntry 5 } 2459 dlswDirMacLocation OBJECT-TYPE 2460 SYNTAX RowPointer 2461 MAX-ACCESS read-create 2462 STATUS current 2463 DESCRIPTION 2464 "Points to either the ifEntry, dlswTConnConfigEntry, 2465 dlswTConnOperEntry, 0.0, or something that is implementation 2466 specific. It identifies the location of the MAC address 2467 (or the collection of MAC addresses.)" 2468 DEFVAL { null } 2469 ::= { dlswDirMacEntry 6 } 2471 dlswDirMacStatus OBJECT-TYPE 2472 SYNTAX INTEGER { 2473 unknown (1), 2474 reachable (2), 2475 notReachable (3) 2476 } 2477 MAX-ACCESS read-create 2478 STATUS current 2479 DESCRIPTION 2480 "This object specifies whether DLSw currently believes 2481 the MAC address to be accessible at the specified location. 2482 The value `notReachable' allows a configured resource 2483 definition to be taken out of service when a search to 2484 that resource fails (avoiding a repeat of the search)." 2485 DEFVAL { unknown } 2486 ::= { dlswDirMacEntry 7 } 2488 dlswDirMacLFSize OBJECT-TYPE 2489 SYNTAX LFSize 2490 MAX-ACCESS read-create 2491 STATUS current 2492 DESCRIPTION 2493 "The largest size of the MAC INFO field (LLC header and data) 2494 that a circuit to the MAC address can carry through this path." 2495 DEFVAL { lfs65535 } 2496 ::= { dlswDirMacEntry 8 } 2498 dlswDirMacRowStatus OBJECT-TYPE 2499 SYNTAX RowStatus 2500 MAX-ACCESS read-create 2501 STATUS current 2502 DESCRIPTION 2503 "This object is used by the manager to create 2504 or delete the row entry in the dlswDirMacTable 2505 following the RowStatus textual convention." 2506 ::= { dlswDirMacEntry 9 } 2508 -- ................................................................... 2509 -- Directory for NetBIOS Names 2510 -- All Possible combinations of values of these objects. 2511 -- 2512 -- EntryType LocationType Location Status 2513 -- -------------- ------------ ------------------ -------------- 2514 -- userConfigured local ifEntry or 0.0 reachable, or 2515 -- notReachable, or 2516 -- unknown 2517 -- userConfigured remote TConnConfigEntry reachable, or 2518 -- notReachable, or 2519 -- unknown 2520 -- partnerCapExMsg remote TConnOperEntry unknown 2521 -- dynamic local ifEntry or 0.0 reachable 2522 -- dynamic remote TConnOperEntry reachable 2523 -- 2524 -- ................................................................... 2525 dlswDirNBTable OBJECT-TYPE 2526 SYNTAX SEQUENCE OF DlswDirNBEntry 2527 MAX-ACCESS not-accessible 2528 STATUS current 2529 DESCRIPTION 2530 "This table contains locations of NetBIOS names. 2531 They could be either verified or not verified, 2532 local or remote, and configured locally or learned 2533 from either Capabilities Exchange messages or 2534 directory searches." 2535 ::= { dlswDirCache 2 } 2537 dlswDirNBEntry OBJECT-TYPE 2538 SYNTAX DlswDirNBEntry 2539 MAX-ACCESS not-accessible 2540 STATUS current 2541 DESCRIPTION 2542 "Indexed by dlswDirNBIndex." 2543 INDEX { dlswDirNBIndex } 2544 ::= { dlswDirNBTable 1 } 2546 DlswDirNBEntry ::= SEQUENCE { 2547 dlswDirNBIndex INTEGER, 2548 dlswDirNBName NBName, 2549 dlswDirNBNameType INTEGER, 2550 dlswDirNBEntryType INTEGER, 2551 dlswDirNBLocationType INTEGER, 2552 dlswDirNBLocation RowPointer, 2553 dlswDirNBStatus INTEGER, 2554 dlswDirNBLFSize LFSize, 2555 dlswDirNBRowStatus RowStatus 2556 } 2558 dlswDirNBIndex OBJECT-TYPE 2559 SYNTAX INTEGER (0..2147483647) 2560 MAX-ACCESS not-accessible 2561 STATUS current 2562 DESCRIPTION 2563 "Uniquely identifies a conceptual row of this table." 2564 ::= { dlswDirNBEntry 1 } 2566 dlswDirNBName OBJECT-TYPE 2567 SYNTAX NBName 2568 MAX-ACCESS read-create 2569 STATUS current 2570 DESCRIPTION 2571 "The NetBIOS name (including `any char' and `wildcard' 2572 characters) specifies a set of NetBIOS names that are 2573 defined or discovered through an interface or partner 2574 DLSw nodes." 2575 ::= { dlswDirNBEntry 2 } 2577 dlswDirNBNameType OBJECT-TYPE 2578 SYNTAX INTEGER { 2579 unknown (1), 2580 individual (2), 2581 group (3) 2582 } 2583 MAX-ACCESS read-create 2584 STATUS current 2585 DESCRIPTION 2586 "Whether dlswDirNBName represents an (or a set of) individual 2587 or group NetBIOS name(s)." 2588 DEFVAL { unknown } 2589 ::= { dlswDirNBEntry 3 } 2591 dlswDirNBEntryType OBJECT-TYPE 2592 SYNTAX INTEGER { 2593 other (1), 2594 userConfiguredPublic (2), 2595 userConfiguredPrivate (3), 2596 partnerCapExMsg (4), 2597 dynamic (5) 2598 } 2599 MAX-ACCESS read-create 2600 STATUS current 2601 DESCRIPTION 2602 "The cause of the creation of this conceptual row. 2603 It could be one of the three methods: (1) user 2604 configured, including via management protocol 2605 set operations, configuration file, command line, 2606 or equivalent methods; (2) learned from the 2607 partner DLSw Capabilities Exchange messages; 2608 and (3) dynamic, e.g., learned from ICanReach 2609 messages, or test frames. Since only actual 2610 NetBIOS names can be dynamically learned, dynamic 2611 entries will not contain any char or wildcard 2612 characters. 2614 The public versus private distinction for user- 2615 configured resources applies only to local resources 2616 (UC remote resources are private), and indicates 2617 whether that resource should be advertised in 2618 capabilities exchange messages sent by this node." 2619 DEFVAL { userConfiguredPublic } 2620 ::= { dlswDirNBEntry 4 } 2622 dlswDirNBLocationType OBJECT-TYPE 2623 SYNTAX INTEGER { 2624 other (1), 2625 local (2), 2626 remote (3) 2627 } 2628 MAX-ACCESS read-create 2629 STATUS current 2630 DESCRIPTION 2631 "The location of the resource (or a collection of resources 2632 using any char/wildcard characters) of this conceptual row 2633 is either (1) local - the resource is reachable via an 2634 interface, or (2) remote - the resource is reachable via a 2635 a partner DLSw node (or a set of partner DLSw nodes)." 2636 DEFVAL { local } 2637 ::= { dlswDirNBEntry 5 } 2639 dlswDirNBLocation OBJECT-TYPE 2640 SYNTAX RowPointer 2641 MAX-ACCESS read-create 2642 STATUS current 2643 DESCRIPTION 2644 "Points to either the ifEntry, dlswTConnConfigEntry, 2645 dlswTConnOperEntry, 0.0, or something that is implementation 2646 specific. It identifies the location of the NetBIOS name 2647 or the set of NetBIOS names." 2648 DEFVAL { null } 2649 ::= { dlswDirNBEntry 6 } 2651 dlswDirNBStatus OBJECT-TYPE 2652 SYNTAX INTEGER { 2653 unknown (1), 2654 reachable (2), 2655 notReachable (3) 2656 } 2657 MAX-ACCESS read-create 2658 STATUS current 2659 DESCRIPTION 2660 "This object specifies whether DLSw currently believes 2661 the NetBIOS name to be accessible at the specified location. 2662 The value `notReachable' allows a configured resource 2663 definition to be taken out of service when a search to 2664 that resource fails (avoiding a repeat of the search)." 2665 DEFVAL { unknown } 2666 ::= { dlswDirNBEntry 7 } 2668 dlswDirNBLFSize OBJECT-TYPE 2669 SYNTAX LFSize 2670 MAX-ACCESS read-create 2671 STATUS current 2672 DESCRIPTION 2673 "The largest size of the MAC INFO field (LLC header and data) 2674 that a circuit to the NB name can carry through this path." 2675 DEFVAL { lfs65535 } 2676 ::= { dlswDirNBEntry 8 } 2678 dlswDirNBRowStatus OBJECT-TYPE 2679 SYNTAX RowStatus 2680 MAX-ACCESS read-create 2681 STATUS current 2682 DESCRIPTION 2683 "This object is used by manager to create 2684 or delete the row entry in the dlswDirNBTable 2685 following the RowStatus textual convention." 2686 ::= { dlswDirNBEntry 9 } 2688 -- ------------------------------------------------------------------- 2689 -- Resource Locations 2690 -- ------------------------------------------------------------------- 2691 dlswDirLocate OBJECT IDENTIFIER ::= { dlswDirectory 3 } 2693 -- ................................................................... 2694 -- Locate Entries in the dlswDirMacTable for a given MAC address 2695 -- ................................................................... 2696 dlswDirLocateMacTable OBJECT-TYPE 2697 SYNTAX SEQUENCE OF DlswDirLocateMacEntry 2698 MAX-ACCESS not-accessible 2699 STATUS current 2700 DESCRIPTION 2701 "This table is used to retrieve all entries in the 2702 dlswDirMacTable that match a given MAC address, 2703 in the order of the best matched first, the 2704 second best matched second, and so on, till 2705 no more entries match the given MAC address." 2706 ::= { dlswDirLocate 1 } 2708 dlswDirLocateMacEntry OBJECT-TYPE 2709 SYNTAX DlswDirLocateMacEntry 2710 MAX-ACCESS not-accessible 2711 STATUS current 2712 DESCRIPTION 2713 "Indexed by dlswDirLocateMacMac and dlswDirLocateMacMatch. 2714 The first object is the MAC address of interest, and 2715 the second object is the order in the list of all 2716 entries that match the MAC address." 2717 INDEX { dlswDirLocateMacMac, dlswDirLocateMacMatch } 2718 ::= { dlswDirLocateMacTable 1 } 2720 DlswDirLocateMacEntry ::= SEQUENCE { 2721 dlswDirLocateMacMac MacAddressNC, 2722 dlswDirLocateMacMatch INTEGER, 2723 dlswDirLocateMacLocation RowPointer 2724 } 2726 dlswDirLocateMacMac OBJECT-TYPE 2727 SYNTAX MacAddressNC 2728 MAX-ACCESS not-accessible 2729 STATUS current 2730 DESCRIPTION 2731 "The MAC address to be located." 2732 ::= { dlswDirLocateMacEntry 1 } 2734 dlswDirLocateMacMatch OBJECT-TYPE 2735 SYNTAX INTEGER (1..255) 2736 MAX-ACCESS not-accessible 2737 STATUS current 2738 DESCRIPTION 2739 "The order of the entries of dlswDirMacTable 2740 that match dlswDirLocateMacMac. A value of 2741 one represents the entry that best matches the 2742 MAC address. A value of two represents the second 2743 best matched entry, and so on." 2744 ::= { dlswDirLocateMacEntry 2 } 2746 dlswDirLocateMacLocation OBJECT-TYPE 2747 SYNTAX RowPointer 2748 MAX-ACCESS read-only 2749 STATUS current 2750 DESCRIPTION 2751 "Points to the dlswDirMacEntry." 2752 ::= { dlswDirLocateMacEntry 3 } 2754 -- ................................................................... 2755 -- Locate Entries in the dlswDirNBTable for a given NetBIOS name 2756 -- ................................................................... 2757 dlswDirLocateNBTable OBJECT-TYPE 2758 SYNTAX SEQUENCE OF DlswDirLocateNBEntry 2759 MAX-ACCESS not-accessible 2760 STATUS current 2761 DESCRIPTION 2762 "This table is used to retrieve all entries in the 2763 dlswDirNBTable that match a given NetBIOS name, 2764 in the order of the best matched first, the 2765 second best matched second, and so on, till 2766 no more entries match the given NetBIOS name." 2767 ::= { dlswDirLocate 2 } 2769 dlswDirLocateNBEntry OBJECT-TYPE 2770 SYNTAX DlswDirLocateNBEntry 2771 MAX-ACCESS not-accessible 2772 STATUS current 2773 DESCRIPTION 2774 "Indexed by dlswDirLocateNBName and dlswDirLocateNBMatch. 2775 The first object is the NetBIOS name of interest, and 2776 the second object is the order in the list of all 2777 entries that match the NetBIOS name." 2778 INDEX { dlswDirLocateNBName, dlswDirLocateNBMatch } 2779 ::= { dlswDirLocateNBTable 1 } 2781 DlswDirLocateNBEntry ::= SEQUENCE { 2782 dlswDirLocateNBName NBName, 2783 dlswDirLocateNBMatch INTEGER, 2784 dlswDirLocateNBLocation RowPointer 2785 } 2787 dlswDirLocateNBName OBJECT-TYPE 2788 SYNTAX NBName 2789 MAX-ACCESS not-accessible 2790 STATUS current 2791 DESCRIPTION 2792 "The NetBIOS name to be located (no any char or wildcards)." 2793 ::= { dlswDirLocateNBEntry 1 } 2795 dlswDirLocateNBMatch OBJECT-TYPE 2796 SYNTAX INTEGER (1..255) 2797 MAX-ACCESS not-accessible 2798 STATUS current 2799 DESCRIPTION 2800 "The order of the entries of dlswDirNBTable 2801 that match dlswDirLocateNBName. A value of 2802 one represents the entry that best matches the 2803 NetBIOS name. A value of two represents the second 2804 best matched entry, and so on." 2805 ::= { dlswDirLocateNBEntry 2 } 2807 dlswDirLocateNBLocation OBJECT-TYPE 2808 SYNTAX RowPointer 2809 MAX-ACCESS read-only 2810 STATUS current 2811 DESCRIPTION 2812 "Points to the dlswDirNBEntry." 2814 ::= { dlswDirLocateNBEntry 3 } 2816 -- ******************************************************************* 2817 -- CIRCUIT 2818 -- A circuit is the end-to-end association of two DLSw entities 2819 -- through one or two DLSw nodes. It is the concatenation of 2820 -- two "data links", optionally with an intervening transport 2821 -- connection. The origin of the circuit is the end station that 2822 -- initiates the circuit. The target of the circuit is the end 2823 -- station that receives the initiation. 2824 -- ******************************************************************* 2826 -- ------------------------------------------------------------------- 2827 -- Statistics Related to Circuits 2828 -- ------------------------------------------------------------------- 2829 dlswCircuitStat OBJECT IDENTIFIER ::= { dlswCircuit 1 } 2831 dlswCircuitStatActives OBJECT-TYPE 2832 SYNTAX Gauge32 2833 MAX-ACCESS read-only 2834 STATUS current 2835 DESCRIPTION 2836 "The current number of circuits in dlswCircuitTable that are 2837 not in the disconnected state." 2838 ::= { dlswCircuitStat 1 } 2840 dlswCircuitStatCreates OBJECT-TYPE 2841 SYNTAX Counter32 2842 MAX-ACCESS read-only 2843 STATUS current 2844 DESCRIPTION 2845 "The total number of entries ever added to dlswCircuitTable, 2846 or reactivated upon exiting `disconnected' state." 2847 ::= { dlswCircuitStat 2 } 2849 -- ------------------------------------------------------------------- 2850 -- Circuit Table 2851 -- 2852 -- This table is the DLSw entity's view of circuits. There will be 2853 -- a conceptual row in the table associated with each data link. 2854 -- 2855 -- The chart below lists the various possible combinations of 2856 -- origin and target MAC locations and the number of entries in 2857 -- this Circuit Table: 2858 -- 2859 -- number of | Origin End Station Location 2860 -- entries in the |-------------------------------------- 2861 -- Circuit Table | internal local remote 2862 -- -----------------------|-------------------------------------- 2863 -- Target | internal | NA 2 1 2864 -- End | local | 2 2 1 2865 -- Station | remote | 1 1 NA 2866 -- Location | | 2867 -- 2868 -- NA: Not applicable 2869 -- 2870 -- Note: 2871 -- (a) IfIndex and RouteInfo are applied only if location is local. 2872 -- (b) TDomain and TAddr are applied only if location is remote. 2873 -- 2874 -- Most of statistics related to circuits can be collected 2875 -- from LLC-2 Link Station Table. 2876 -- ------------------------------------------------------------------- 2877 dlswCircuitTable OBJECT-TYPE 2878 SYNTAX SEQUENCE OF DlswCircuitEntry 2879 MAX-ACCESS not-accessible 2880 STATUS current 2881 DESCRIPTION 2882 "This table is the circuit representation in the DLSw 2883 entity. Virtual data links are used to represent any internal 2884 end stations. There is a conceptual row associated with 2885 each data link. Thus, for circuits without an intervening 2886 transport connection, there are two conceptual rows 2887 for each circuit. 2889 The table consists of the circuits being established, 2890 established, and as an implementation option, circuits that 2891 have been disconnected. For circuits carried over 2892 transport connections, an entry is created after 2893 the CUR_cs was sent or received. For circuits between 2894 two locally attached devices, or internal virtual MAC 2895 addresses, an entry is created when the equivalent of 2896 CUR_cs sent/received status is reached. 2898 End station 1 (S1) and End station 2 (S2) are used to 2899 represent the two end stations of the circuit. 2900 S1 is always an end station which is locally attached. 2901 S2 may be locally attached or remote. If it is locally 2902 attached, the circuit will be represented by two rows indexed 2903 by (A, B) and (B, A) where A & B are the relevant MACs/SAPs. 2905 The table may be used to store the causes of disconnection of 2906 circuits. It is recommended that the oldest disconnected 2907 circuit entry be removed from this table when the memory 2908 space of disconnected circuits is needed." 2909 ::= { dlswCircuit 2 } 2911 dlswCircuitEntry OBJECT-TYPE 2912 SYNTAX DlswCircuitEntry 2913 MAX-ACCESS not-accessible 2914 STATUS current 2915 DESCRIPTION 2916 "" 2917 INDEX { dlswCircuitS1Mac, 2918 dlswCircuitS1Sap, 2919 dlswCircuitS2Mac, 2920 dlswCircuitS2Sap } 2921 ::= { dlswCircuitTable 1 } 2923 DlswCircuitEntry ::= SEQUENCE { 2924 dlswCircuitS1Mac MacAddressNC, 2925 dlswCircuitS1Sap OCTET STRING, 2926 dlswCircuitS1IfIndex INTEGER, 2927 dlswCircuitS1DlcType DlcType, 2928 dlswCircuitS1RouteInfo OCTET STRING, 2929 dlswCircuitS1CircuitId OCTET STRING, 2930 dlswCircuitS1Dlc RowPointer, 2932 dlswCircuitS2Mac MacAddressNC, 2933 dlswCircuitS2Sap OCTET STRING, 2934 dlswCircuitS2Location EndStationLocation, 2935 dlswCircuitS2TDomain OBJECT IDENTIFIER, 2936 dlswCircuitS2TAddress TAddress, 2937 dlswCircuitS2CircuitId OCTET STRING, 2939 dlswCircuitOrigin INTEGER, 2941 dlswCircuitEntryTime TimeTicks, 2942 dlswCircuitStateTime TimeTicks, 2943 dlswCircuitState INTEGER, 2945 dlswCircuitPriority INTEGER, 2947 dlswCircuitFCSendGrantedUnits INTEGER, 2948 dlswCircuitFCSendCurrentWndw INTEGER, 2949 dlswCircuitFCRecvGrantedUnits INTEGER, 2950 dlswCircuitFCRecvCurrentWndw INTEGER, 2951 dlswCircuitFCLargestRecvGranted Gauge32, 2952 dlswCircuitFCLargestSendGranted Gauge32, 2953 dlswCircuitFCHalveWndwSents Counter32, 2954 dlswCircuitFCResetOpSents Counter32, 2955 dlswCircuitFCHalveWndwRcvds Counter32, 2956 dlswCircuitFCResetOpRcvds Counter32, 2957 dlswCircuitDiscReasonLocal INTEGER, 2958 dlswCircuitDiscReasonRemote INTEGER, 2959 dlswCircuitDiscReasonRemoteData OCTET STRING 2960 } 2962 -- ................................................................... 2963 -- Information related to the End Station 1 (S1). 2965 -- ................................................................... 2966 dlswCircuitS1Mac OBJECT-TYPE 2967 SYNTAX MacAddressNC 2968 MAX-ACCESS not-accessible 2969 STATUS current 2970 DESCRIPTION 2971 "The MAC Address of End Station 1 (S1) used for this circuit." 2972 ::= { dlswCircuitEntry 1 } 2974 dlswCircuitS1Sap OBJECT-TYPE 2975 SYNTAX OCTET STRING (SIZE(1)) 2976 MAX-ACCESS not-accessible 2977 STATUS current 2978 DESCRIPTION 2979 "The SAP at End Station 1 (S1) used for this circuit." 2980 ::= { dlswCircuitEntry 2 } 2982 dlswCircuitS1IfIndex OBJECT-TYPE 2983 SYNTAX INTEGER (0..2147483647) 2984 MAX-ACCESS read-only 2985 STATUS current 2986 DESCRIPTION 2987 "The ifEntry index of the local interface through which S1 2988 can be reached." 2989 ::= { dlswCircuitEntry 3 } 2991 dlswCircuitS1DlcType OBJECT-TYPE 2992 SYNTAX DlcType 2993 MAX-ACCESS read-only 2994 STATUS current 2995 DESCRIPTION 2996 "The DLC protocol in use between the DLSw node and S1." 2997 ::= { dlswCircuitEntry 4 } 2999 dlswCircuitS1RouteInfo OBJECT-TYPE 3000 SYNTAX OCTET STRING (SIZE (0..30)) 3001 MAX-ACCESS read-only 3002 STATUS current 3003 DESCRIPTION 3004 "If source-route bridging is in use between the DLSw 3005 node and S1, this is the routing information field 3006 describing the path between the two devices. 3007 Otherwise the value will be an OCTET STRING of 3008 zero length." 3009 ::= { dlswCircuitEntry 5 } 3011 dlswCircuitS1CircuitId OBJECT-TYPE 3012 SYNTAX OCTET STRING (SIZE (0 | 8)) 3013 MAX-ACCESS read-only 3014 STATUS current 3015 DESCRIPTION 3016 "The Circuit ID assigned by this DLSw node to this circuit. 3017 The first four octets are the DLC port Id, and 3018 the second four octets are the Data Link Correlator. 3019 If the DLSw SSP was not used to establish this circuit, 3020 the value will be a string of zero length." 3021 ::= { dlswCircuitEntry 6 } 3023 dlswCircuitS1Dlc OBJECT-TYPE 3024 SYNTAX RowPointer 3025 MAX-ACCESS read-only 3026 STATUS current 3027 DESCRIPTION 3028 "Points to a conceptual row of the underlying DLC MIB, 3029 which could either be the standard MIBs (e.g., the SDLC), 3030 or an enterprise-specific DLC MIB." 3031 ::= { dlswCircuitEntry 7 } 3033 -- ................................................................... 3034 -- Information related to the End Station 2 (S2). 3035 -- ................................................................... 3036 dlswCircuitS2Mac OBJECT-TYPE 3037 SYNTAX MacAddressNC 3038 MAX-ACCESS not-accessible 3039 STATUS current 3040 DESCRIPTION 3041 "The MAC Address of End Station 2 (S2) used for this circuit." 3042 ::= { dlswCircuitEntry 8 } 3044 dlswCircuitS2Sap OBJECT-TYPE 3045 SYNTAX OCTET STRING (SIZE(1)) 3046 MAX-ACCESS not-accessible 3047 STATUS current 3048 DESCRIPTION 3049 "The SAP at End Station 2 (S2) used for this circuit." 3050 ::= { dlswCircuitEntry 9 } 3052 dlswCircuitS2Location OBJECT-TYPE 3053 SYNTAX EndStationLocation 3054 MAX-ACCESS read-only 3055 STATUS current 3056 DESCRIPTION 3057 "The location of End Station 2 (S2). 3058 If the location of End Station 2 is local, the 3059 interface information will be available in the 3060 conceptual row whose S1 and S2 are the S2 and 3061 the S1 of this conceptual row, respectively." 3062 ::= { dlswCircuitEntry 10 } 3064 dlswCircuitS2TDomain OBJECT-TYPE 3065 SYNTAX OBJECT IDENTIFIER 3066 MAX-ACCESS read-only 3067 STATUS current 3068 DESCRIPTION 3069 "If the location of End Station 2 is remote, 3070 this value is the transport domain of the 3071 transport protocol the circuit is running 3072 over. Otherwise, the value is 0.0." 3073 ::= { dlswCircuitEntry 11 } 3075 dlswCircuitS2TAddress OBJECT-TYPE 3076 SYNTAX TAddress 3077 MAX-ACCESS read-only 3078 STATUS current 3079 DESCRIPTION 3080 "If the location of End Station 2 is remote, 3081 this object contains the address of the partner 3082 DLSw, else it will be an OCTET STRING of zero length." 3083 ::= { dlswCircuitEntry 12 } 3085 dlswCircuitS2CircuitId OBJECT-TYPE 3086 SYNTAX OCTET STRING (SIZE (0 | 8)) 3087 MAX-ACCESS read-only 3088 STATUS current 3089 DESCRIPTION 3090 "The Circuit ID assigned to this circuit by the partner 3091 DLSw node. The first four octets are the DLC port Id, and 3092 the second four octets are the Data Link Correlator. 3093 If the DLSw SSP was not used to establish this circuit, 3094 the value will be a string of zero length." 3095 ::= { dlswCircuitEntry 13 } 3097 -- ................................................................... 3098 dlswCircuitOrigin OBJECT-TYPE 3099 SYNTAX INTEGER { 3100 s1 (1), 3101 s2 (2) 3102 } 3103 MAX-ACCESS read-only 3104 STATUS current 3105 DESCRIPTION 3106 "This object specifies which of the two end stations 3107 initiated the establishment of this circuit." 3108 ::= { dlswCircuitEntry 14 } 3110 -- ................................................................... 3111 -- Operational information related to this circuit. 3112 -- ................................................................... 3113 dlswCircuitEntryTime OBJECT-TYPE 3114 SYNTAX TimeTicks 3115 UNITS "hundredths of a second" 3116 MAX-ACCESS read-only 3117 STATUS current 3118 DESCRIPTION 3119 "The amount of time (in hundredths of a second) since this 3120 circuit table conceptual row was created." 3121 ::= { dlswCircuitEntry 15 } 3123 dlswCircuitStateTime OBJECT-TYPE 3124 SYNTAX TimeTicks 3125 UNITS "hundredths of a second" 3126 MAX-ACCESS read-only 3127 STATUS current 3128 DESCRIPTION 3129 "The amount of time (in hundredths of a second) since this 3130 circuit entered the current state." 3131 ::= { dlswCircuitEntry 16 } 3133 dlswCircuitState OBJECT-TYPE 3134 SYNTAX INTEGER { 3135 disconnected (1), 3136 circuitStart (2), 3137 resolvePending (3), 3138 circuitPending (4), 3139 circuitEstablished (5), 3140 connectPending (6), 3141 contactPending (7), 3142 connected (8), 3143 disconnectPending (9), 3144 haltPending (10), 3145 haltPendingNoack (11), 3146 circuitRestart (12), 3147 restartPending (13) 3148 } 3149 MAX-ACCESS read-write 3150 STATUS current 3151 DESCRIPTION 3152 "The current state of this circuit. The agent, implementation 3153 specific, may choose to keep entries for some period of time 3154 after circuit disconnect, so the manager can gather the time 3155 and cause of disconnection. 3157 While all of the specified values may be returned from a GET 3158 operation, the only SETable value is `disconnectPending'. 3159 When this value is set, DLSw should perform the appropriate 3160 action given its previous state (e.g., send HALT_DL if the 3161 state was `connected') to bring the circuit down to the 3162 `disconnected' state. Both the partner DLSw and local end 3163 station(s) should be notified as appropriate. 3165 This MIB provides no facility to re-establish a disconnected 3166 circuit, because in DLSw this should be an end station-driven 3167 function." 3168 ::= { dlswCircuitEntry 17 } 3170 dlswCircuitPriority OBJECT-TYPE 3171 SYNTAX INTEGER { 3172 unsupported (1), 3173 low (2), 3174 medium (3), 3175 high (4), 3176 highest (5) 3177 } 3178 MAX-ACCESS read-only 3179 STATUS current 3180 DESCRIPTION 3181 "The transmission priority of this circuit as understood by 3182 this DLSw node. This value is determined by the two DLSw 3183 nodes at circuit startup time. If this DLSw node does not 3184 support DLSw circuit priority, the value `unsupported' should 3185 be returned." 3186 ::= { dlswCircuitEntry 18 } 3188 -- ................................................................... 3189 -- Pacing Objects: 3190 -- These objects are applicable if DLSw is using the SSP circuit 3191 -- pacing protocol to control the flow between the two data links 3192 -- in this circuit. 3193 -- ................................................................... 3194 dlswCircuitFCSendGrantedUnits OBJECT-TYPE 3195 SYNTAX INTEGER (0..65535) 3196 MAX-ACCESS read-only 3197 STATUS current 3198 DESCRIPTION 3199 "The number of paced SSP messages that this DLSw is currently 3200 authorized to send on this circuit before it must stop and 3201 wait for an additional flow control indication from the 3202 partner DLSw. 3204 The value zero should be returned if this circuit is not 3205 running the DLSw pacing protocol." 3206 ::= { dlswCircuitEntry 19 } 3208 dlswCircuitFCSendCurrentWndw OBJECT-TYPE 3209 SYNTAX INTEGER (0..65535) 3210 MAX-ACCESS read-only 3211 STATUS current 3212 DESCRIPTION 3213 "The current window size that this DLSw is using in its role 3214 as a data sender. This is the value by which this DLSw would 3215 increase the number of messages it is authorized to send, if 3216 it were to receive a flow control indication with the bits 3217 specifying `repeat window'. 3219 The value zero should be returned if this circuit is not 3220 running the DLSw pacing protocol." 3221 ::= { dlswCircuitEntry 20 } 3223 dlswCircuitFCRecvGrantedUnits OBJECT-TYPE 3224 SYNTAX INTEGER (0..65535) 3225 MAX-ACCESS read-only 3226 STATUS current 3227 DESCRIPTION 3228 "The current number of paced SSP messages that this DLSw has 3229 authorized the partner DLSw to send on this circuit before 3230 the partner DLSw must stop and wait for an additional flow 3231 control indication from this DLSw. 3233 The value zero should be returned if this circuit is not 3234 running the DLSw pacing protocol." 3235 ::= { dlswCircuitEntry 21 } 3237 dlswCircuitFCRecvCurrentWndw OBJECT-TYPE 3238 SYNTAX INTEGER (0..65535) 3239 MAX-ACCESS read-only 3240 STATUS current 3241 DESCRIPTION 3242 "The current window size that this DLSw is using in its role 3243 as a data receiver. This is the number of additional paced 3244 SSP messages that this DLSw would be authorizing its DLSw 3245 partner to send, if this DLSw were to send a flow control 3246 indication with the bits specifying `repeat window'. 3248 The value zero should be returned if this circuit is not 3249 running the DLSw pacing protocol." 3250 ::= { dlswCircuitEntry 22 } 3252 dlswCircuitFCLargestRecvGranted OBJECT-TYPE 3253 SYNTAX Gauge32 3254 MAX-ACCESS read-only 3255 STATUS current 3256 DESCRIPTION 3257 "The largest receive window size granted by this DLSw during 3258 the current activation of this circuit. This is not the 3259 largest number of messages granted at any time, but the 3260 largest window size as represented by FCIND operator bits. 3262 The value zero should be returned if this circuit is not 3263 running the DLSw pacing protocol." 3264 ::= { dlswCircuitEntry 23 } 3266 dlswCircuitFCLargestSendGranted OBJECT-TYPE 3267 SYNTAX Gauge32 3268 MAX-ACCESS read-only 3269 STATUS current 3270 DESCRIPTION 3271 "The largest send (with respect to this DLSw) window size 3272 granted by the partner DLSw during the current activation of 3273 this circuit. 3275 The value zero should be returned if this circuit is not 3276 running the DLSw pacing protocol." 3277 ::= { dlswCircuitEntry 24 } 3279 dlswCircuitFCHalveWndwSents OBJECT-TYPE 3280 SYNTAX Counter32 3281 MAX-ACCESS read-only 3282 STATUS current 3283 DESCRIPTION 3284 "The number of Halve Window operations this DLSw has sent on 3285 this circuit, in its role as a data receiver. 3287 The value zero should be returned if this circuit is not 3288 running the DLSw pacing protocol." 3289 ::= { dlswCircuitEntry 25 } 3291 dlswCircuitFCResetOpSents OBJECT-TYPE 3292 SYNTAX Counter32 3293 MAX-ACCESS read-only 3294 STATUS current 3295 DESCRIPTION 3296 "The number of Reset Window operations this DLSw has sent on 3297 this circuit, in its role as a data receiver. 3299 The value zero should be returned if this circuit is not 3300 running the DLSw pacing protocol." 3301 ::= { dlswCircuitEntry 26 } 3303 dlswCircuitFCHalveWndwRcvds OBJECT-TYPE 3304 SYNTAX Counter32 3305 MAX-ACCESS read-only 3306 STATUS current 3307 DESCRIPTION 3308 "The number of Halve Window operations this DLSw has received on 3309 this circuit, in its role as a data sender. 3311 The value zero should be returned if this circuit is not 3312 running the DLSw pacing protocol." 3313 ::= { dlswCircuitEntry 27 } 3315 dlswCircuitFCResetOpRcvds OBJECT-TYPE 3316 SYNTAX Counter32 3317 MAX-ACCESS read-only 3318 STATUS current 3319 DESCRIPTION 3320 "The number of Reset Window operations this DLSw has received on 3321 this circuit, in its role as a data sender. 3323 The value zero should be returned if this circuit is not 3324 running the DLSw pacing protocol." 3325 ::= { dlswCircuitEntry 28 } 3327 -- ................................................................... 3328 -- Information about the circuit disconnection 3329 -- ................................................................... 3330 dlswCircuitDiscReasonLocal OBJECT-TYPE 3331 SYNTAX INTEGER { 3332 endStationDiscRcvd (1), 3333 endStationDlcError (2), 3334 protocolError (3), 3335 operatorCommand (4), 3336 haltDlRcvd (5), 3337 haltDlNoAckRcvd (6), 3338 transportConnClosed (7) 3339 } 3340 MAX-ACCESS read-only 3341 STATUS current 3342 DESCRIPTION 3343 "The reason why this circuit was last disconnected, as seen 3344 by this DLSw node. 3346 This object is present only if the agent keeps circuit 3347 table entries around for some period after circuit disconnect." 3348 ::= { dlswCircuitEntry 29 } 3350 dlswCircuitDiscReasonRemote OBJECT-TYPE 3351 SYNTAX INTEGER { 3352 unknown (1), 3353 endStationDiscRcvd (2), 3354 endStationDlcError (3), 3355 protocolError (4), 3356 operatorCommand (5) 3357 } 3358 MAX-ACCESS read-only 3359 STATUS current 3360 DESCRIPTION 3361 "The generic reason code why this circuit was last 3362 disconnected, as reported by the DLSw partner in a HALT_DL 3363 or HALT_DL_NOACK. If the partner does not send a reason 3364 code in these messages, or the DLSw implementation does 3365 not report receiving one, the value `unknown' is returned. 3367 This object is present only if the agent keeps circuit table 3368 entries around for some period after circuit disconnect." 3369 ::= { dlswCircuitEntry 30 } 3371 dlswCircuitDiscReasonRemoteData OBJECT-TYPE 3372 SYNTAX OCTET STRING (SIZE (0 | 4)) 3373 MAX-ACCESS read-only 3374 STATUS current 3375 DESCRIPTION 3376 "Implementation-specific data reported by the DLSw partner in 3377 a HALT_DL or HALT_DL_NOACK, to help specify how and why this 3378 circuit was last disconnected. If the partner does not send 3379 this data in these messages, or the DLSw implementation does 3380 not report receiving it, a string of zero length is returned. 3382 This object is present only if the agent keeps circuit table 3383 entries around for some period after circuit disconnect." 3384 ::= { dlswCircuitEntry 31 } 3386 -- ................................................................... 3387 -- Statistics related to this circuit. 3388 -- All statistics are in LLC-2 Link Station Statistical Table. 3389 -- All SDLC statistics are in SDLC MIB 3390 -- ................................................................... 3392 -- ******************************************************************* 3393 -- DLSW SDLC EXTENSION 3394 -- ******************************************************************* 3395 dlswSdlcLsEntries OBJECT-TYPE 3396 SYNTAX Gauge32 3397 MAX-ACCESS read-only 3398 STATUS current 3399 DESCRIPTION 3400 "The number of entries in dlswSdlcLsTable." 3401 ::= { dlswSdlc 1 } 3403 -- ................................................................... 3404 dlswSdlcLsTable OBJECT-TYPE 3405 SYNTAX SEQUENCE OF DlswSdlcLsEntry 3406 MAX-ACCESS not-accessible 3407 STATUS current 3408 DESCRIPTION 3409 "The table defines the virtual MAC addresses for those 3410 SDLC link stations that participate in data link switching." 3411 ::= { dlswSdlc 2 } 3413 dlswSdlcLsEntry OBJECT-TYPE 3414 SYNTAX DlswSdlcLsEntry 3415 MAX-ACCESS not-accessible 3416 STATUS current 3417 DESCRIPTION 3418 "The index of this table is the ifIndex value for the 3419 SDLC port which owns this link station and the poll 3420 address of the particular SDLC link station." 3422 INDEX { ifIndex, sdlcLSAddress } 3423 ::= { dlswSdlcLsTable 1 } 3425 DlswSdlcLsEntry ::= SEQUENCE { 3426 dlswSdlcLsLocalMac MacAddressNC, 3427 dlswSdlcLsLocalSap OCTET STRING, 3428 dlswSdlcLsLocalIdBlock DisplayString, 3429 dlswSdlcLsLocalIdNum DisplayString, 3430 dlswSdlcLsRemoteMac MacAddressNC, 3431 dlswSdlcLsRemoteSap OCTET STRING, 3432 dlswSdlcLsRowStatus RowStatus 3433 } 3435 dlswSdlcLsLocalMac OBJECT-TYPE 3436 SYNTAX MacAddressNC 3437 MAX-ACCESS read-create 3438 STATUS current 3439 DESCRIPTION 3440 "The virtual MAC address used to represent the SDLC-attached 3441 link station to the rest of the DLSw network." 3442 ::= { dlswSdlcLsEntry 1 } 3444 dlswSdlcLsLocalSap OBJECT-TYPE 3445 SYNTAX OCTET STRING (SIZE(1)) 3446 MAX-ACCESS read-create 3447 STATUS current 3448 DESCRIPTION 3449 "The SAP used to represent this link station." 3450 ::= { dlswSdlcLsEntry 2 } 3452 dlswSdlcLsLocalIdBlock OBJECT-TYPE 3453 SYNTAX DisplayString (SIZE (0 | 3)) 3454 MAX-ACCESS read-create 3455 STATUS current 3456 DESCRIPTION 3457 "The block number is the first three digits of the node_id, 3458 if available. These 3 hexadecimal digits identify the 3459 product." 3460 DEFVAL { ''H } 3461 ::= { dlswSdlcLsEntry 3 } 3463 dlswSdlcLsLocalIdNum OBJECT-TYPE 3464 SYNTAX DisplayString (SIZE (0 | 5)) 3465 MAX-ACCESS read-create 3466 STATUS current 3467 DESCRIPTION 3468 "The ID number is the last 5 digits of the node_id, if 3469 available. These 5 hexadecimal digits are 3470 administratively defined and combined with the 3 digit 3471 block number form the node_id. This node_id is used to 3472 identify the local node and is included in SNA XIDs." 3474 DEFVAL { ''H } 3475 ::= { dlswSdlcLsEntry 4 } 3477 dlswSdlcLsRemoteMac OBJECT-TYPE 3478 SYNTAX MacAddressNC 3479 MAX-ACCESS read-create 3480 STATUS current 3481 DESCRIPTION 3482 "The MAC address to which DLSw should attempt to connect 3483 this link station. If this information is not available, 3484 a length of zero for this object should be returned." 3485 DEFVAL { ''H } 3486 ::= { dlswSdlcLsEntry 5 } 3488 dlswSdlcLsRemoteSap OBJECT-TYPE 3489 SYNTAX OCTET STRING (SIZE (0 | 1)) 3490 MAX-ACCESS read-create 3491 STATUS current 3492 DESCRIPTION 3493 "The SAP of the remote station to which this link 3494 station should be connected. If this information 3495 is not available, a length of zero for this object 3496 should be returned." 3497 DEFVAL { ''H } 3498 ::= { dlswSdlcLsEntry 6 } 3500 dlswSdlcLsRowStatus OBJECT-TYPE 3501 SYNTAX RowStatus 3502 MAX-ACCESS read-create 3503 STATUS current 3504 DESCRIPTION 3505 "This object is used by the manager to create 3506 or delete the row entry in the dlswSdlcLsTable 3507 following the RowStatus textual convention." 3508 ::= { dlswSdlcLsEntry 7 } 3510 -- ******************************************************************* 3511 -- TRAP GENERATION CONTROL 3512 -- ******************************************************************* 3513 dlswTrapControl OBJECT IDENTIFIER ::= { dlswNode 10} 3515 dlswTrapCntlTConnPartnerReject OBJECT-TYPE 3516 SYNTAX INTEGER { 3517 enabled (1), 3518 disabled (2), 3519 partial (3) 3520 } 3521 MAX-ACCESS read-write 3522 STATUS current 3523 DESCRIPTION 3524 "Indicates whether the DLSw is permitted to emit partner 3525 reject related traps. With the value of `enabled' 3526 the DLSw will emit all partner reject related traps. 3527 With the value of `disabled' the DLSw will not emit 3528 any partner reject related traps. With the value 3529 of `partial' the DLSw will only emits partner reject 3530 traps for CapEx reject. The changes take effect 3531 immediately." 3532 ::= { dlswTrapControl 1 } 3534 dlswTrapCntlTConnProtViolation OBJECT-TYPE 3535 SYNTAX TruthValue 3536 MAX-ACCESS read-write 3537 STATUS current 3538 DESCRIPTION 3539 "Indicates whether the DLSw is permitted to generate 3540 protocol-violation traps on the events such as 3541 window size violation. The changes take effect 3542 immediately." 3543 ::= { dlswTrapControl 2 } 3545 dlswTrapCntlTConn OBJECT-TYPE 3546 SYNTAX INTEGER { 3547 enabled (1), 3548 disabled (2), 3549 partial (3) 3550 } 3551 MAX-ACCESS read-write 3552 STATUS current 3553 DESCRIPTION 3554 "Indicates whether the DLSw is permitted to emit transport 3555 connection up and down traps. With the value of `enabled' 3556 the DLSw will emit traps when connections enter `connected' 3557 and `disconnected' states. With the value of `disabled' 3558 the DLSw will not emit traps when connections enter of 3559 `connected' and `disconnected' states. With the value 3560 of `partial' the DLSw will only emits transport connection 3561 down traps when the connection is closed with busy. 3562 The changes take effect immediately." 3563 ::= { dlswTrapControl 3 } 3565 dlswTrapCntlCircuit OBJECT-TYPE 3566 SYNTAX INTEGER { 3567 enabled (1), 3568 disabled (2), 3569 partial (3) 3570 } 3571 MAX-ACCESS read-write 3572 STATUS current 3573 DESCRIPTION 3574 "Indicates whether the DLSw is permitted to generate 3575 circuit up and down traps. With the value of `enabled' 3576 the DLSw will emit traps when circuits enter `connected' 3577 and `disconnected' states. With the value of `disabled' 3578 the DLSw will not emit traps when circuits enter of 3579 `connected' and `disconnected' states. With the value 3580 of `partial' the DLSw will emit traps only for those 3581 circuits that are initiated by this DLSw, e.g., 3582 originating the CUR_CS message. The changes take effect 3583 immediately." 3584 ::= { dlswTrapControl 4 } 3586 -- ******************************************************************* 3587 -- NOTIFICATIONS, i.e., TRAP DEFINITIONS 3588 -- ******************************************************************* 3589 dlswTraps OBJECT IDENTIFIER ::= { dlswMIB 0 } 3591 -- ------------------------------------------------------------------- 3592 -- This section defines the well-known notifications sent by 3593 -- DLSW agents. 3594 -- Care must be taken to insure that no particular notification 3595 -- is sent to a single receiving entity more often than once 3596 -- every five seconds. 3597 -- 3598 -- Traps includes: 3599 -- (1) Partner rejected (capEx rejection, not in partner list, etc.) 3600 -- (2) DLSw protocol violation (e.g., window size violation, etc.) 3601 -- (3) Transport connection up/down 3602 -- (4) Circuit up/down 3603 -- ------------------------------------------------------------------- 3604 -- 3606 dlswTrapTConnPartnerReject NOTIFICATION-TYPE 3607 OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr 3608 } 3609 STATUS current 3610 DESCRIPTION 3611 "This trap is sent each time a transport connection 3612 is rejected by a partner DLSw during Capabilities 3613 Exchanges. The emission of this trap is controlled 3614 by dlswTrapCntlTConnPartnerReject." 3615 ::= { dlswTraps 1 } 3617 dlswTrapTConnProtViolation NOTIFICATION-TYPE 3618 OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr 3619 } 3620 STATUS current 3621 DESCRIPTION 3622 "This trap is sent each time a protocol violation is 3623 detected for a transport connection. The emission of this 3624 trap is controlled by dlswTrapCntlTConnProtViolation." 3625 ::= { dlswTraps 2 } 3627 dlswTrapTConnUp NOTIFICATION-TYPE 3628 OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr 3629 } 3630 STATUS current 3631 DESCRIPTION 3632 "This trap is sent each time a transport connection 3633 enters `connected' state. The emission of this trap 3634 is controlled by dlswTrapCntlTConn." 3635 ::= { dlswTraps 3 } 3637 dlswTrapTConnDown NOTIFICATION-TYPE 3638 OBJECTS { dlswTConnOperTDomain, dlswTConnOperRemoteTAddr 3639 } 3640 STATUS current 3641 DESCRIPTION 3642 "This trap is sent each time a transport connection 3643 enters `disconnected' state. The emission of this trap 3644 is controlled by dlswTrapCntlTConn." 3645 ::= { dlswTraps 4 } 3647 dlswTrapCircuitUp NOTIFICATION-TYPE 3648 OBJECTS { dlswCircuitS1Mac, dlswCircuitS1Sap, 3649 dlswCircuitS2Mac, dlswCircuitS2Sap 3650 } 3651 STATUS current 3652 DESCRIPTION 3653 "This trap is sent each time a circuit enters `connected' 3654 state. The emission of this trap is controlled by 3655 dlswTrapCntlCircuit." 3656 ::= { dlswTraps 5 } 3658 dlswTrapCircuitDown NOTIFICATION-TYPE 3659 OBJECTS { dlswCircuitS1Mac, dlswCircuitS1Sap, 3660 dlswCircuitS2Mac, dlswCircuitS2Sap 3661 } 3662 STATUS current 3663 DESCRIPTION 3664 "This trap is sent each time a circuit enters `disconnected' 3665 state. The emission of this trap is controlled by 3666 dlswTrapCntlCircuit." 3667 ::= { dlswTraps 6 } 3669 -- ******************************************************************* 3670 -- CONFORMANCE INFORMATION 3671 -- ******************************************************************* 3672 dlswConformance OBJECT IDENTIFIER ::= { dlsw 3 } 3674 dlswCompliances OBJECT IDENTIFIER ::= { dlswConformance 1 } 3675 dlswGroups OBJECT IDENTIFIER ::= { dlswConformance 2 } 3676 -- ------------------------------------------------------------------- 3677 -- COMPLIANCE STATEMENTS 3678 -- ------------------------------------------------------------------- 3680 -- ................................................................... 3681 -- Core compliance for all DLSw entities 3682 -- ................................................................... 3683 dlswCoreCompliance MODULE-COMPLIANCE 3684 STATUS current 3685 DESCRIPTION 3686 "The core compliance statement for all DLSw nodes." 3687 MODULE 3688 MANDATORY-GROUPS { 3689 dlswNodeGroup, 3690 dlswTConnStatGroup, 3691 dlswTConnConfigGroup, 3692 dlswTConnOperGroup, 3693 dlswInterfaceGroup, 3694 dlswCircuitGroup, 3695 dlswCircuitStatGroup, 3696 dlswNotificationGroup } 3698 GROUP dlswNodeNBGroup 3699 DESCRIPTION 3700 "The DLSw NetBIOS Node group is mandatory only for 3701 those DLSw entities that implement NetBIOS." 3703 GROUP dlswTConnNBGroup 3704 DESCRIPTION 3705 "The DLSw NetBIOS Transport Connection group is 3706 mandatory only for those DLSw entities that 3707 implement NetBIOS." 3709 OBJECT dlswNodeStatus 3710 MIN-ACCESS read-only 3711 DESCRIPTION 3712 "Write access is not required." 3714 OBJECT dlswNodeVirtualSegmentLFSize 3715 MIN-ACCESS read-only 3716 DESCRIPTION 3717 "Write access is not required." 3719 OBJECT dlswNodeResourceNBExclusivity 3720 MIN-ACCESS read-only 3721 DESCRIPTION 3722 "Write access is not required." 3724 OBJECT dlswNodeResourceMacExclusivity 3725 MIN-ACCESS read-only 3726 DESCRIPTION 3727 "Write access is not required." 3729 OBJECT dlswTrapCntlTConnPartnerReject 3730 MIN-ACCESS read-only 3731 DESCRIPTION 3732 "Write access is not required." 3734 OBJECT dlswTrapCntlTConnProtViolation 3735 MIN-ACCESS read-only 3736 DESCRIPTION 3737 "Write access is not required." 3739 OBJECT dlswTrapCntlTConn 3740 MIN-ACCESS read-only 3741 DESCRIPTION 3742 "Write access is not required." 3744 OBJECT dlswTrapCntlCircuit 3745 MIN-ACCESS read-only 3746 DESCRIPTION 3747 "Write access is not required." 3749 OBJECT dlswTConnConfigTDomain 3750 MIN-ACCESS read-only 3751 DESCRIPTION 3752 "Write access is not required." 3754 OBJECT dlswTConnConfigLocalTAddr 3755 MIN-ACCESS read-only 3756 DESCRIPTION 3757 "Write access is not required." 3759 OBJECT dlswTConnConfigRemoteTAddr 3760 MIN-ACCESS read-only 3761 DESCRIPTION 3762 "Write access is not required." 3764 OBJECT dlswTConnConfigEntryType 3765 MIN-ACCESS read-only 3766 DESCRIPTION 3767 "Write access is not required." 3769 OBJECT dlswTConnConfigGroupDefinition 3770 MIN-ACCESS read-only 3771 DESCRIPTION 3772 "Write access is not required." 3774 OBJECT dlswTConnConfigSetupType 3775 MIN-ACCESS read-only 3776 DESCRIPTION 3777 "Write access is not required." 3779 OBJECT dlswTConnConfigSapList 3780 MIN-ACCESS read-only 3781 DESCRIPTION 3782 "Write access is not required." 3784 OBJECT dlswTConnConfigAdvertiseMacNB 3785 MIN-ACCESS read-only 3786 DESCRIPTION 3787 "Write access is not required." 3789 OBJECT dlswTConnConfigInitCirRecvWndw 3790 MIN-ACCESS read-only 3791 DESCRIPTION 3792 "Write access is not required." 3794 OBJECT dlswTConnConfigRowStatus 3795 MIN-ACCESS read-only 3796 DESCRIPTION 3797 "Write access is not required." 3799 OBJECT dlswTConnOperState 3800 MIN-ACCESS read-only 3801 DESCRIPTION 3802 "Write access is not required." 3804 OBJECT dlswIfRowStatus 3805 MIN-ACCESS read-only 3806 DESCRIPTION 3807 "Write access is not required." 3809 OBJECT dlswIfVirtualSegment 3810 MIN-ACCESS read-only 3811 DESCRIPTION 3812 "Write access is not required." 3814 OBJECT dlswIfSapList 3815 MIN-ACCESS read-only 3816 DESCRIPTION 3817 "Write access is not required." 3819 OBJECT dlswCircuitState 3820 MIN-ACCESS read-only 3821 DESCRIPTION 3822 "Write access is not required." 3824 ::= { dlswCompliances 1 } 3826 -- ................................................................... 3827 -- Compliance for all DLSw entities that provide TCP transport. 3829 -- ................................................................... 3830 dlswTConnTcpCompliance MODULE-COMPLIANCE 3831 STATUS current 3832 DESCRIPTION 3833 "Compliance for DLSw nodes that use TCP as a 3834 transport connection protocol." 3835 MODULE 3836 MANDATORY-GROUPS { 3837 dlswTConnTcpConfigGroup, 3838 dlswTConnTcpOperGroup } 3840 OBJECT dlswTConnTcpConfigKeepAliveInt 3841 MIN-ACCESS read-only 3842 DESCRIPTION 3843 "Write access is not required." 3845 OBJECT dlswTConnTcpConfigTcpConnections 3846 MIN-ACCESS read-only 3847 DESCRIPTION 3848 "Write access is not required." 3850 OBJECT dlswTConnTcpConfigMaxSegmentSize 3851 MIN-ACCESS read-only 3852 DESCRIPTION 3853 "Write access is not required." 3855 ::= { dlswCompliances 2 } 3857 -- ................................................................... 3858 -- Compliance for all DLSw Entities that implement a directory 3859 -- ................................................................... 3860 dlswDirCompliance MODULE-COMPLIANCE 3861 STATUS current 3862 DESCRIPTION 3863 "Compliance for DLSw nodes that provide a directory 3864 function." 3865 MODULE 3866 MANDATORY-GROUPS { 3867 dlswDirGroup } 3869 GROUP dlswDirNBGroup 3870 DESCRIPTION 3871 "The DLSw NetBIOS group is mandatory only for 3872 those DLSw entities that implement NetBIOS." 3874 OBJECT dlswDirMacMac 3875 MIN-ACCESS read-only 3876 DESCRIPTION 3877 "Write access is not required." 3879 OBJECT dlswDirMacMask 3880 MIN-ACCESS read-only 3881 DESCRIPTION 3882 "Write access is not required." 3884 OBJECT dlswDirMacEntryType 3885 MIN-ACCESS read-only 3886 DESCRIPTION 3887 "Write access is not required." 3889 OBJECT dlswDirMacLocationType 3890 MIN-ACCESS read-only 3891 DESCRIPTION 3892 "Write access is not required." 3894 OBJECT dlswDirMacLocation 3895 MIN-ACCESS read-only 3896 DESCRIPTION 3897 "Write access is not required." 3899 OBJECT dlswDirMacStatus 3900 MIN-ACCESS read-only 3901 DESCRIPTION 3902 "Write access is not required." 3904 OBJECT dlswDirMacLFSize 3905 MIN-ACCESS read-only 3906 DESCRIPTION 3907 "Write access is not required." 3909 OBJECT dlswDirMacRowStatus 3910 MIN-ACCESS read-only 3911 DESCRIPTION 3912 "Write access is not required." 3914 OBJECT dlswDirNBName 3915 MIN-ACCESS read-only 3916 DESCRIPTION 3917 "Write access is not required." 3919 OBJECT dlswDirNBNameType 3920 MIN-ACCESS read-only 3921 DESCRIPTION 3922 "Write access is not required." 3924 OBJECT dlswDirNBEntryType 3925 MIN-ACCESS read-only 3926 DESCRIPTION 3927 "Write access is not required." 3929 OBJECT dlswDirNBLocationType 3930 MIN-ACCESS read-only 3931 DESCRIPTION 3932 "Write access is not required." 3934 OBJECT dlswDirNBLocation 3935 MIN-ACCESS read-only 3936 DESCRIPTION 3937 "Write access is not required." 3939 OBJECT dlswDirNBStatus 3940 MIN-ACCESS read-only 3941 DESCRIPTION 3942 "Write access is not required." 3944 OBJECT dlswDirNBLFSize 3945 MIN-ACCESS read-only 3946 DESCRIPTION 3947 "Write access is not required." 3949 OBJECT dlswDirNBRowStatus 3950 MIN-ACCESS read-only 3951 DESCRIPTION 3952 "Write access is not required." 3954 ::= { dlswCompliances 3 } 3956 -- ................................................................... 3957 -- Compliance for all DLSw entities that provide an ordered 3958 -- list of directory entries that match a resource 3959 -- ................................................................... 3960 dlswDirLocateCompliance MODULE-COMPLIANCE 3961 STATUS current 3962 DESCRIPTION 3963 "Compliance for DLSw nodes that provide an ordered 3964 list of directory entries for a given resource." 3965 MODULE 3966 MANDATORY-GROUPS { 3967 dlswDirLocateGroup } 3969 GROUP dlswDirLocateNBGroup 3970 DESCRIPTION 3971 "The DLSw NetBIOS group is mandatory only for 3972 those DLSw entities that implement NetBIOS." 3974 ::= { dlswCompliances 4 } 3976 -- ................................................................... 3977 -- Compliance for all DLSw entities that support SDLC end stations 3978 -- ................................................................... 3979 dlswSdlcCompliance MODULE-COMPLIANCE 3980 STATUS current 3981 DESCRIPTION 3982 "Compliance for DLSw nodes that support SDLC." 3983 MODULE 3984 MANDATORY-GROUPS { 3985 dlswSdlcGroup } 3987 OBJECT dlswSdlcLsLocalMac 3988 MIN-ACCESS read-only 3989 DESCRIPTION 3990 "Write access is not required." 3992 OBJECT dlswSdlcLsLocalSap 3993 MIN-ACCESS read-only 3994 DESCRIPTION 3995 "Write access is not required." 3997 OBJECT dlswSdlcLsLocalIdBlock 3998 MIN-ACCESS read-only 3999 DESCRIPTION 4000 "Write access is not required." 4002 OBJECT dlswSdlcLsLocalIdNum 4003 MIN-ACCESS read-only 4004 DESCRIPTION 4005 "Write access is not required." 4007 OBJECT dlswSdlcLsRemoteMac 4008 MIN-ACCESS read-only 4009 DESCRIPTION 4010 "Write access is not required." 4012 OBJECT dlswSdlcLsRemoteSap 4013 MIN-ACCESS read-only 4014 DESCRIPTION 4015 "Write access is not required." 4017 OBJECT dlswSdlcLsRowStatus 4018 MIN-ACCESS read-only 4019 DESCRIPTION 4020 "Write access is not required." 4022 ::= { dlswCompliances 5 } 4024 -- ------------------------------------------------------------------- 4025 -- CONFORMANCE GROUPS 4026 -- ------------------------------------------------------------------- 4028 -- ................................................................... 4029 -- Node Conformance Group 4030 -- ................................................................... 4031 dlswNodeGroup OBJECT-GROUP 4032 OBJECTS { 4033 dlswNodeVersion, 4034 dlswNodeVendorID, 4035 dlswNodeVersionString, 4036 dlswNodeStdPacingSupport, 4037 dlswNodeStatus, 4038 dlswNodeUpTime, 4039 dlswNodeVirtualSegmentLFSize, 4040 dlswNodeResourceMacExclusivity, 4041 dlswTrapCntlTConnPartnerReject, 4042 dlswTrapCntlTConnProtViolation, 4043 dlswTrapCntlTConn, 4044 dlswTrapCntlCircuit 4045 } 4046 STATUS current 4047 DESCRIPTION 4048 "Conformance group for DLSw node general information." 4049 ::= { dlswGroups 1 } 4051 -- ................................................................... 4052 dlswNodeNBGroup OBJECT-GROUP 4053 OBJECTS { 4054 dlswNodeResourceNBExclusivity 4055 } 4056 STATUS current 4057 DESCRIPTION 4058 "Conformance group for DLSw node general information 4059 specifically for nodes that support NetBIOS." 4060 ::= { dlswGroups 2 } 4062 -- ................................................................... 4063 dlswTConnStatGroup OBJECT-GROUP 4064 OBJECTS { 4065 dlswTConnStatActiveConnections, 4066 dlswTConnStatCloseIdles, 4067 dlswTConnStatCloseBusys 4068 } 4069 STATUS current 4070 DESCRIPTION 4071 "Conformance group for statistics for transport 4072 connections." 4073 ::= { dlswGroups 3 } 4075 -- ................................................................... 4076 dlswTConnConfigGroup OBJECT-GROUP 4077 OBJECTS { 4078 dlswTConnConfigTDomain, 4079 dlswTConnConfigLocalTAddr, 4080 dlswTConnConfigRemoteTAddr, 4081 dlswTConnConfigLastModifyTime, 4082 dlswTConnConfigEntryType, 4083 dlswTConnConfigGroupDefinition, 4084 dlswTConnConfigSetupType, 4085 dlswTConnConfigSapList, 4086 dlswTConnConfigAdvertiseMacNB, 4087 dlswTConnConfigInitCirRecvWndw, 4088 dlswTConnConfigOpens, 4089 dlswTConnConfigRowStatus 4090 } 4091 STATUS current 4092 DESCRIPTION 4093 "Conformance group for the configuration of 4094 transport connections." 4095 ::= { dlswGroups 4 } 4097 -- ................................................................... 4098 dlswTConnOperGroup OBJECT-GROUP 4099 OBJECTS { 4100 dlswTConnOperLocalTAddr, 4101 dlswTConnOperEntryTime, 4102 dlswTConnOperConnectTime, 4103 dlswTConnOperState, 4104 dlswTConnOperConfigIndex, 4105 dlswTConnOperFlowCntlMode, 4106 dlswTConnOperPartnerVersion, 4107 dlswTConnOperPartnerVendorID, 4108 dlswTConnOperPartnerVersionStr, 4109 dlswTConnOperPartnerInitPacingWndw, 4110 dlswTConnOperPartnerSapList, 4111 dlswTConnOperPartnerMacExcl, 4112 dlswTConnOperPartnerMacInfo, 4113 dlswTConnOperDiscTime, 4114 dlswTConnOperDiscReason, 4115 dlswTConnOperDiscActiveCir, 4116 dlswTConnOperInDataPkts, 4117 dlswTConnOperOutDataPkts, 4118 dlswTConnOperInDataOctets, 4119 dlswTConnOperOutDataOctets, 4120 dlswTConnOperInCntlPkts, 4121 dlswTConnOperOutCntlPkts, 4122 dlswTConnOperCURexSents, 4123 dlswTConnOperICRexRcvds, 4124 dlswTConnOperCURexRcvds, 4125 dlswTConnOperICRexSents, 4126 dlswTConnOperCirCreates, 4127 dlswTConnOperCircuits 4128 } 4129 STATUS current 4130 DESCRIPTION 4131 "Conformance group for operation information for 4132 transport connections." 4133 ::= { dlswGroups 5 } 4135 -- ................................................................... 4136 dlswTConnNBGroup OBJECT-GROUP 4137 OBJECTS { 4138 dlswTConnOperPartnerNBExcl, 4139 dlswTConnOperPartnerNBInfo, 4140 dlswTConnOperNQexSents, 4141 dlswTConnOperNRexRcvds, 4142 dlswTConnOperNQexRcvds, 4143 dlswTConnOperNRexSents 4144 } 4145 STATUS current 4146 DESCRIPTION 4147 "Conformance group for operation information for 4148 transport connections, specifically for nodes 4149 that support NetBIOS." 4150 ::= { dlswGroups 6 } 4152 -- ................................................................... 4153 dlswTConnTcpConfigGroup OBJECT-GROUP 4154 OBJECTS { 4155 dlswTConnTcpConfigKeepAliveInt, 4156 dlswTConnTcpConfigTcpConnections, 4157 dlswTConnTcpConfigMaxSegmentSize 4158 } 4159 STATUS current 4160 DESCRIPTION 4161 "Conformance group for configuration information for 4162 transport connections using TCP." 4163 ::= { dlswGroups 7 } 4165 -- ................................................................... 4166 dlswTConnTcpOperGroup OBJECT-GROUP 4167 OBJECTS { 4168 dlswTConnTcpOperKeepAliveInt, 4169 dlswTConnTcpOperPrefTcpConnections, 4170 dlswTConnTcpOperTcpConnections 4171 } 4172 STATUS current 4173 DESCRIPTION 4174 "Conformance group for operation information for 4175 transport connections using TCP." 4176 ::= { dlswGroups 8 } 4178 -- ................................................................... 4179 dlswInterfaceGroup OBJECT-GROUP 4180 OBJECTS { 4181 dlswIfRowStatus, 4182 dlswIfVirtualSegment, 4183 dlswIfSapList 4184 } 4185 STATUS current 4186 DESCRIPTION 4187 "Conformance group for DLSw interfaces." 4188 ::= { dlswGroups 9 } 4190 -- ................................................................... 4191 dlswDirGroup OBJECT-GROUP 4192 OBJECTS { 4193 dlswDirMacEntries, 4194 dlswDirMacCacheHits, 4195 dlswDirMacCacheMisses, 4196 dlswDirMacCacheNextIndex, 4197 dlswDirMacMac, 4198 dlswDirMacMask, 4199 dlswDirMacEntryType, 4200 dlswDirMacLocationType, 4201 dlswDirMacLocation, 4202 dlswDirMacStatus, 4203 dlswDirMacLFSize, 4204 dlswDirMacRowStatus 4205 } 4206 STATUS current 4207 DESCRIPTION 4208 "Conformance group for DLSw directory using MAC 4209 addresses." 4210 ::= { dlswGroups 10 } 4212 -- ................................................................... 4213 dlswDirNBGroup OBJECT-GROUP 4214 OBJECTS { 4215 dlswDirNBEntries, 4216 dlswDirNBCacheHits, 4217 dlswDirNBCacheMisses, 4218 dlswDirNBCacheNextIndex, 4219 dlswDirNBName, 4220 dlswDirNBNameType, 4221 dlswDirNBEntryType, 4222 dlswDirNBLocationType, 4223 dlswDirNBLocation, 4224 dlswDirNBStatus, 4225 dlswDirNBLFSize, 4226 dlswDirNBRowStatus 4227 } 4228 STATUS current 4229 DESCRIPTION 4230 "Conformance group for DLSw directory using NetBIOS 4231 names." 4232 ::= { dlswGroups 11 } 4234 -- ................................................................... 4235 dlswDirLocateGroup OBJECT-GROUP 4236 OBJECTS { 4237 dlswDirLocateMacLocation 4238 } 4239 STATUS current 4240 DESCRIPTION 4241 "Conformance group for a node that can return directory 4242 entry order for a given MAC address." 4243 ::= { dlswGroups 12 } 4245 -- ................................................................... 4246 dlswDirLocateNBGroup OBJECT-GROUP 4247 OBJECTS { 4248 dlswDirLocateNBLocation 4249 } 4250 STATUS current 4251 DESCRIPTION 4252 "Conformance group for a node that can return directory 4253 entry order for a given NetBIOS name." 4254 ::= { dlswGroups 13 } 4256 -- ................................................................... 4257 dlswCircuitStatGroup OBJECT-GROUP 4258 OBJECTS { 4259 dlswCircuitStatActives, 4260 dlswCircuitStatCreates 4261 } 4262 STATUS current 4263 DESCRIPTION 4264 "Conformance group for statistics about circuits." 4265 ::= { dlswGroups 14 } 4267 -- ................................................................... 4268 dlswCircuitGroup OBJECT-GROUP 4269 OBJECTS { 4270 dlswCircuitS1IfIndex, 4271 dlswCircuitS1DlcType, 4272 dlswCircuitS1RouteInfo, 4273 dlswCircuitS1CircuitId, 4274 dlswCircuitS1Dlc, 4275 dlswCircuitS2Location, 4276 dlswCircuitS2TDomain, 4277 dlswCircuitS2TAddress, 4278 dlswCircuitS2CircuitId, 4279 dlswCircuitOrigin, 4280 dlswCircuitEntryTime, 4281 dlswCircuitStateTime, 4282 dlswCircuitState, 4283 dlswCircuitPriority, 4284 dlswCircuitFCSendGrantedUnits, 4285 dlswCircuitFCSendCurrentWndw, 4286 dlswCircuitFCRecvGrantedUnits, 4287 dlswCircuitFCRecvCurrentWndw, 4288 dlswCircuitFCLargestRecvGranted, 4289 dlswCircuitFCLargestSendGranted, 4290 dlswCircuitFCHalveWndwSents, 4291 dlswCircuitFCResetOpSents, 4292 dlswCircuitFCHalveWndwRcvds, 4293 dlswCircuitFCResetOpRcvds, 4294 dlswCircuitDiscReasonLocal, 4295 dlswCircuitDiscReasonRemote, 4296 dlswCircuitDiscReasonRemoteData 4297 } 4298 STATUS current 4299 DESCRIPTION 4300 "Conformance group for DLSw circuits." 4301 ::= { dlswGroups 15 } 4303 -- ................................................................... 4304 dlswSdlcGroup OBJECT-GROUP 4305 OBJECTS { 4306 dlswSdlcLsEntries, 4307 dlswSdlcLsLocalMac, 4308 dlswSdlcLsLocalSap, 4309 dlswSdlcLsLocalIdBlock, 4310 dlswSdlcLsLocalIdNum, 4311 dlswSdlcLsRemoteMac, 4312 dlswSdlcLsRemoteSap, 4313 dlswSdlcLsRowStatus 4314 } 4315 STATUS current 4316 DESCRIPTION 4317 "Conformance group for DLSw SDLC support." 4318 ::= { dlswGroups 16 } 4320 -- ................................................................... 4321 dlswNotificationGroup NOTIFICATION-GROUP 4322 NOTIFICATIONS { 4323 dlswTrapTConnPartnerReject, 4324 dlswTrapTConnProtViolation, 4325 dlswTrapTConnUp, 4326 dlswTrapTConnDown, 4327 dlswTrapCircuitUp, 4328 dlswTrapCircuitDown 4329 } 4330 STATUS current 4331 DESCRIPTION 4332 "Conformance group for DLSw notifications." 4333 ::= { dlswGroups 17 } 4335 END 4336 5.0 Acknowledgements 4338 This memo has been produced by the AIW DLSw MIB RIGlet, which is also 4339 recognized as the IETF DLSw MIB Working Group. 4341 6.0 References 4343 [1] A. Bartky, "Data Link Switching: Switch-to-Switch Protocol; AIW DLSw 4344 RIG: DLSw Closed Pages, DLSw Standard Version 1", RFC 1795, Sync 4345 Research Inc., April 1995. 4347 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 4348 Waldbusser, "Structure of Management Information for version 2 of 4349 the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 4350 1996. 4352 [3] Rose, M., and K. McCloghrie, "Structure and Identification of 4353 Management Information for TCP/IP-based Internets", STD 16, RFC 4354 1155, Performance Systems International, Hughes LAN Systems, May 4355 1990. 4357 [4] McCloghrie, K., and M. Rose, "Management Information Base for 4358 Network Management of TCP/IP-based internets - MIB-II", STD 17, RFC 4359 1213, Hughes LAN Systems, Performance Systems International, March 4360 1991. 4362 [5] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 4363 Management Protocol", STD 15, RFC 1157, SNMP Research, Performance 4364 Systems International, Performance Systems International, MIT 4365 Laboratory for Computer Science, May 1990. 4367 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 4368 Waldbusser, "Protocol Operations for version 2 of the Simple Network 4369 Management Protocol (SNMPv2)", RFC 1905, January 1996. 4371 [7] IEEE Project, "ANSI/IEEE P802.1D", 1993 4373 [8] McCloghrie, K., and F. Kastenholz, "Evolution of the Interfaces 4374 Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, 4375 January 1994. 4377 [9] Hilgeman, J., S. Nix, A. Bartky, and W. Clark, "Definitions of 4378 Managed Objects for SNA Data Link Control (SDLC) using SMIv2", RFC 4379 1747, Apertus Technologies, Inc., Metaplex, Inc., Sync Research, 4380 Inc., cisco Systems, Inc., January 1995 4382 7.0 Security Considerations 4384 Security issues are not discussed in this memo. 4386 8.0 Authors' Addresses 4388 David D. Chen 4389 IBM Networking Systems 4390 P. O. Box 12195 4391 Research Triangle Park, NC 27709 4392 US 4394 Phone: +1 919 254 6182 4395 Email: dchen@vnet.ibm.com 4397 Peter W. Gayek 4398 IBM Networking Systems 4399 P. O. Box 12195 4400 Research Triangle Park, NC 27709 4401 US 4403 Phone: +1 919 254 1808 4404 Email: gayek@vnet.ibm.com 4406 Shannon Nix 4407 Metaplex, Inc. 4409 7025 Kit Creek Road 4410 P. O. Box 14987 4411 Research Triangle Park, NC 27709 4412 US 4414 Phone: +1 919 472 2388 4415 Email: snix@metaplex.com 4417 9.0 Contents 4419 Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4421 1.0 Change Log . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4423 2.0 The SNMPv2 Network Management Framework . . . . . . . . . . . 6 4424 2.1 Object Definitions . . . . . . . . . . . . . . . . . . . . . . 6 4426 3.0 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 4427 3.1 Relation to Interface Group (RFC 1573) [8] . . . . . . . . . . 6 4428 3.2 Relation to Underlying DLC Layer . . . . . . . . . . . . . . . 7 4429 3.3 Relation to SDLC MIB (RFC 1747) . . . . . . . . . . . . . . . 7 4430 3.4 DLSw MIB Structure . . . . . . . . . . . . . . . . . . . . . . 8 4431 3.4.1 Compliance . . . . . . . . . . . . . . . . . . . . . . . . 8 4432 3.5 DLSw MIB Usage . . . . . . . . . . . . . . . . . . . . . . . . 9 4433 3.5.1 Cooperative DLSw nodes . . . . . . . . . . . . . . . . . . 9 4434 3.5.2 Setting capabilities exchange-related objects . . . . . . 9 4435 3.5.3 Examples of Tasks Using This MIB . . . . . . . . . . . . . 9 4437 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 14 4439 5.0 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 87 4441 6.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 87 4443 7.0 Security Considerations . . . . . . . . . . . . . . . . . . . 88 4445 8.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 88