idnits 2.17.1 draft-ietf-trunkmib-ds0-mib-08.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. Found some kind of copyright notice around line 34 but it does not match any copyright boilerplate known by this tool. Expected boilerplate is as follows today (2024-03-29) 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 expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard 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. ** The abstract seems to contain references ([17], [18], [19]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 254 has weird spacing: '...ifIndex dsx1D...' == Line 273 has weird spacing: '...ifIndex dsx0...' == Line 295 has weird spacing: '...leIndex dsx...' == Line 304 has weird spacing: '...ifIndex dsx0D...' -- 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 (August 1998) is 9358 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2233 (ref. '16') (Obsoleted by RFC 2863) -- Unexpected draft version: The latest known version of draft-ietf-trunkmib-ds3-mib is -08, but you're referring to -09. == Outdated reference: A later version (-05) exists of draft-ietf-atommib-sonetng-02 -- Possible downref: Non-RFC (?) normative reference: ref. '20' Summary: 24 errors (**), 0 flaws (~~), 7 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT DS0 MIB / DS0BUNDLE MIB August 1998 3 Definitions of Managed Objects 4 for the DS0 and DS0 Bundle Interface Type 6 Mon Aug 3 13:36:09 EDT 1998 8 draft-ietf-trunkmib-ds0-mib-08.txt 10 David Fowler (editor) 11 Newbridge Networks 12 davef@newbridge.com 14 Status of this Memo 16 This document is an Internet-Draft. Internet-Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its areas, 18 and its working groups. Note that other groups may also distribute 19 working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet- Drafts as reference 24 material or to cite them other than as "work in progress." 26 To view the entire list of current Internet-Drafts, please check the 27 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 28 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 29 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 30 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 32 Copyright Notice 34 Copyright (C) The Internet Society (1998). All Rights Reserved. 36 Abstract 38 This memo defines an experimental portion of the Management 39 Information Base (MIB) for use with network management protocols in 40 the Internet community. In particular, it describes objects used for 41 managing DS0 and DS0 Bundle interfaces. This document is a companion 42 document with Definitions of Managed Objects for the DS1/E1/DS2/E2, 43 DS3/E3 and SONET/SDH Interface Types, RFC XXXX [17], RFC XXXX [18] 44 and RFC XXXX [19]. 46 This memo specifies a MIB module in a manner that is both compliant 47 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 48 definitions. 50 This memo does not specify a standard for the Internet community. 52 1. The SNMP Management Framework 54 The SNMP Management Framework presently consists of five major 55 components: 57 o An overall architecture, described in RFC 2271 [1]. 59 o Mechanisms for describing and naming objects and events for the 60 purpose of management. The first version of this Structure of 61 Management Information (SMI) is called SMIv1 and described in 62 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 63 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 64 1904 [7]. 66 o Message protocols for transferring management information. The 67 first version of the SNMP message protocol is called SNMPv1 and 68 described in RFC 1157 [8]. A second version of the SNMP message 69 protocol, which is not an Internet standards track protocol, is 70 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 71 The third version of the message protocol is called SNMPv3 and 72 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 74 o Protocol operations for accessing management information. The 75 first set of protocol operations and associated PDU formats is 76 described in RFC 1157 [8]. A second set of protocol operations 77 and associated PDU formats is described in RFC 1905 [13]. 79 o A set of fundamental applications described in RFC 2273 [14] and 80 the view-based access control mechanism described in RFC 2275 81 [15]. Managed objects are accessed via a virtual information 82 store, termed the Management Information Base or MIB. Objects 83 in the MIB are defined using the mechanisms defined in the SMI. 84 This memo specifies a MIB module that is compliant to the SMIv2. 85 A MIB conforming to the SMIv1 can be produced through the 86 appropriate translations. The resulting translated MIB must be 87 semantically equivalent, except where objects or events are 88 omitted because no translation is possible (use of Counter64). 89 Some machine readable information in SMIv2 will be converted 90 into textual descriptions in SMIv1 during the translation 91 process. However, this loss of machine readable information is 92 not considered to change the semantics of the MIB. 94 2. Overview 96 These objects are used when the particular media being used to 97 realize an interface is a DS0 interface. At present, this applies to 98 these values of the ifType variable in the Internet-standard MIB: 100 ds0 (81) 101 ds0Bundle (82) 103 2.1. BONDing Terminology 105 Please reference The BONDing Spec [20] for definitions of terms used 106 to describe bonding modes. 108 2.2. Use of ifTable for DS0 Layer 110 The following items are defined in RFC 2233 [16]. 112 Only the ifGeneralInformationGroup and ifCounterDiscontinuityGroup 113 need to be supported. 115 ifTable Object Use for DS0 Layer 116 ====================================================================== 117 ifIndex Interface index. 119 ifDescr See interfaces MIB [16]. 121 ifType ds0(81) or ds0Bundle(82). 123 ifSpeed 64000 for ds0 (regardless of the 124 setting of robbed bit signalling) 125 or N*64000 for ds0Bundle. 127 ifPhysAddress The value of the Circuit 128 Identifier. If no Circuit 129 Identifier has been assigned 130 this object should have an octet 131 string with zero length. 133 ifAdminStatus See interfaces MIB [16]. 135 ifOperStatus See interfaces MIB [16]. 137 ifLastChange See interfaces MIB [16]. 139 ifName See interfaces MIB [16]. 141 ifLinkUpDownTrapEnable Set to disabled(2). 142 Supports read-only access. 144 ifHighSpeed Set to rounded ifSpeed/1000000. 146 ifConnectorPresent Set to false(2). 148 2.3. Using ifStackTable 150 This section describes by example how to use ifStackTable to 151 represent the relationship of ds0 and ds0Bundles with ds1 interfaces. 152 Implementors of the stack table for ds0 and ds0Bundle interfaces 153 should look at the appropriate RFC for the service being stacked on 154 ds0s and ds0Bundles. Examples given below are for illustration 155 purposes only. 157 Example: A Frame Relay Service is being carried on 4 ds0s of a ds1. 159 +---------------------+ 160 | Frame Relay Service | 161 +---------------------+ 162 | 163 +---------------------+ 164 | ds0Bundle | 165 +---------------------+ 166 | | | | 167 +---+ +---+ +---+ +---+ 168 |ds0| |ds0| |ds0| |ds0| 169 +---+ +---+ +---+ +---+ 170 | | | | 171 +---------------------+ 172 | ds1 | 173 +---------------------+ 175 The assignment of the index values could for example be: 177 ifIndex Description 178 1 FrameRelayService (type 44) 179 2 ds0Bundle (type 82) 180 3 ds0 #1 (type 81) 181 4 ds0 #2 (type 81) 182 5 ds0 #3 (type 81) 183 6 ds0 #4 (type 81) 184 7 ds1 (type 18) 186 The ifStackTable is then used to show the relationships between the 187 various interfaces. 189 ifStackTable Entries 191 HigherLayer LowerLayer 192 0 1 193 1 2 194 2 3 195 2 4 196 2 5 197 2 6 198 3 7 199 4 7 200 5 7 201 6 7 202 7 0 204 In the case where the frameRelayService is using a single ds0, then 205 the ds0Bundle is not required. 207 +---------------------+ 208 | Frame Relay Service | 209 +---------------------+ 210 | 211 +---+ 212 |ds0| 213 +---+ 214 | 215 +---------------------+ 216 | ds1 | 217 +---------------------+ 219 The assignment of the index values could for example be: 221 ifIndex Description 222 1 FrameRelayService (type 44) 223 2 ds0 (type 81) 224 3 ds1 (type 18) 226 The ifStackTable is then used to show the relationships between the 227 various interfaces. 229 ifStackTable Entries 231 HigherLayer LowerLayer 232 0 1 233 1 2 234 2 3 235 3 0 237 2.3.1. Usage of Channelization for DS3, DS1, DS0 239 An example is given here to explain the channelization objects in the 240 DS3, DS1, and DS0 MIBs to help the implementor use the objects 241 correctly. Treatment of E3 and E1 would be similar, with the number of 242 DS0s being different depending on the framing of the E1. Timeslot 16 is 243 not created for framing types that do not pass data over it. 245 Assume that a DS3 (with ifIndex 1) is channelized into DS1s (without 246 DS2s). The object dsx3Channelization is set to enabledDs1. There will 247 be 28 DS1s in the ifTable. Assume the entries in the ifTable for the 248 DS1s are created in channel order and the ifIndex values are 2 through 249 29. In the DS1 MIB, there will be an entry in the dsx1ChanMappingTable 250 for each ds1. The entries will be as follows: 252 dsx1ChanMappingTable Entries 254 ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 255 1 1 2 256 1 2 3 257 ...... 258 1 28 29 260 In addition, the DS1s are channelized into DS0s. The object 261 dsx1Channelization is set to enabledDs0 for each DS1. When this object 262 is set to this value, 24 DS0s are created by the agent. There will be 24 263 DS0s in the ifTable for each DS1. If the dsx1Channelization is set to 264 disabled, the 24 DS0s are destroyed. 266 Assume the entries in the ifTable are created in channel order and the 267 ifIndex values for the DS0s in the first DS1 are 30 through 53. In the 268 DS0 MIB, there will be an entry in the dsx0ChanMappingTable for each 269 DS0. The entries will be as follows: 271 dsx0ChanMappingTable Entries 273 ifIndex dsx0Ds0ChannelNumber dsx0ChanMappedIfIndex 274 2 1 30 275 2 2 31 276 ...... 277 2 24 53 279 2.3.2. Usage of ifIndex Mapping for DS0Bundle 281 An example is given here to explain the ifIndex mapping objects in the 282 DS0Bundle MIB to help the implementor use the objects correctly. 284 Assume that a DS1 (with ifIndex 1) is channelized into DS0s. There will 285 be 24 DS0s in the ifTable. Assume the entries in the ifTable for the 286 DS0s are created in channel order and the ifIndex values are 2 through 287 25. Now, assume that there are two bundles on the DS1. The first one 288 uses channels 1 and 2. The second uses channels 3 and 4. There will be 289 two ifTable entries for these bundles, with values of 26 and 27 for 290 ifIndex. There will be an entry in the dsx0BundleTable for each bundle. 291 The entries will be as follows: 293 dsx0BundleTable Entries 295 dsx0BundleIndex dsx0BundleIfIndex 296 1 26 297 2 27 299 There will be an entry in the dsx0ConfigTable for each DS0. The entries 300 will be as follows: 302 dsx0ConfigTable Entries 304 ifIndex dsx0Ds0ChannelNumber dsx0Ds0BundleMappedIfIndex 305 2 1 26 306 3 2 26 307 4 3 27 308 5 4 27 309 6 5 0 310 7 6 0 311 ...... 312 25 24 0 314 3. Overview of the MIB 316 This document contains 2 MIB modules, the DS0 MIB and the DS0Bundle 317 MIB. 319 3.1. DS0 MIB 321 The DS0 MIB is used to represent individual DS0s in a DS1 or E1. 322 Variables in this MIB would be created for each DS0 in the ifTable. 323 This MIB contains the following group: 325 The DS0 Config Group - This group contains configuration information 326 about a particular DS0. 328 3.2. DS0Bundle MIB 330 The DS0Bundle MIB is used to represent collections of DS0s that are 331 used together to carry data within a DS1/E1 at speeds greater than 332 that of a single DS0. DS0Bundles are created on top of DS0s and are 333 represented that way in the ifStackTable. This MIB contains the 334 following groups: 336 The DS0 Bundle Group - This group contains objects used for creating 337 new ds0Bundles. This group is mandatory. 339 The DS0 Bonding Group - This group contains information about bonding 340 for a ds0Bundle, if bonding is enabled. This group is optional. 342 4. Object Definitions for DS0 344 DS0-MIB DEFINITIONS ::= BEGIN 346 IMPORTS 347 MODULE-IDENTITY, OBJECT-TYPE, 348 transmission FROM SNMPv2-SMI 349 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 350 DisplayString, TruthValue FROM SNMPv2-TC 351 ifIndex, InterfaceIndex, 352 InterfaceIndexOrZero FROM IF-MIB; 354 -- This is the MIB module for the DS0 Interface objects. 356 ds0 MODULE-IDENTITY 357 LAST-UPDATED "9807161630Z" 358 ORGANIZATION "IETF Trunk MIB Working Group" 359 CONTACT-INFO 360 " David Fowler 362 Postal: Newbridge Networks Corporation 363 600 March Road 364 Kanata, Ontario, Canada K2K 2E6 366 Tel: +1 613 591 3600 367 Fax: +1 613 599 3619 369 E-mail: davef@newbridge.com" 370 DESCRIPTION 371 "The MIB module to describe 372 DS0 interfaces objects." 373 REVISION "9805242010Z" 374 DESCRIPTION 375 "Initial version of the DS0-MIB." 377 ::= { transmission 81 } 379 -- The DS0 Config Group 381 -- Implementation of this group is mandatory for all 382 -- systems that use a DS0 Interface. 384 -- The DS0 Config Group consists of two tables: 385 -- DS0 Configuration Table 386 -- DS0 Channel Mapping Table 388 -- The DS0 Configuration Table 390 dsx0ConfigTable OBJECT-TYPE 391 SYNTAX SEQUENCE OF Dsx0ConfigEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "The DS0 Configuration table." 396 ::= { ds0 1 } 398 dsx0ConfigEntry OBJECT-TYPE 399 SYNTAX Dsx0ConfigEntry 400 MAX-ACCESS not-accessible 401 STATUS current 402 DESCRIPTION 403 "An entry in the DS0 Configuration table. There 404 is an entry in this table for each DS0 interface." 405 INDEX { ifIndex } 406 ::= { dsx0ConfigTable 1 } 408 Dsx0ConfigEntry ::= 409 SEQUENCE { 410 dsx0Ds0ChannelNumber INTEGER, 411 dsx0RobbedBitSignalling TruthValue, 412 dsx0CircuitIdentifier DisplayString, 413 dsx0IdleCode INTEGER, 414 dsx0SeizedCode INTEGER, 415 dsx0ReceivedCode INTEGER, 416 dsx0TransmitCodesEnable TruthValue, 417 dsx0Ds0BundleMappedIfIndex InterfaceIndexOrZero 418 } 420 dsx0Ds0ChannelNumber OBJECT-TYPE 421 SYNTAX INTEGER(0..31) 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "This object indicates the channel number of the 426 ds0 on its DS1/E1." 427 ::= { dsx0ConfigEntry 1 } 429 dsx0RobbedBitSignalling OBJECT-TYPE 430 SYNTAX TruthValue 431 MAX-ACCESS read-write 432 STATUS current 433 DESCRIPTION 434 "This object indicates if Robbed Bit Signalling is 435 turned on or off for a given ds0. This only 436 applies to DS0s on a DS1 link. For E1 links the 437 value is always off (false)." 438 ::= { dsx0ConfigEntry 2 } 440 dsx0CircuitIdentifier OBJECT-TYPE 441 SYNTAX DisplayString (SIZE (0..255)) 442 MAX-ACCESS read-write 443 STATUS current 444 DESCRIPTION 445 "This object contains the transmission vendor's 446 circuit identifier, for the purpose of 447 facilitating troubleshooting." 448 ::= { dsx0ConfigEntry 3 } 450 dsx0IdleCode OBJECT-TYPE 451 SYNTAX INTEGER(0..15) 452 MAX-ACCESS read-write 453 STATUS current 454 DESCRIPTION 455 "This object contains the code transmitted in the 456 ABCD bits when the ds0 is not connected and 457 dsx0TransmitCodesEnable is enabled. The object is 458 a bitmap and the various bit positions are: 459 1 D bit 460 2 C bit 461 4 B bit 462 8 A bit" 463 ::= { dsx0ConfigEntry 4 } 465 dsx0SeizedCode OBJECT-TYPE 466 SYNTAX INTEGER(0..15) 467 MAX-ACCESS read-write 468 STATUS current 469 DESCRIPTION 470 "This object contains the code transmitted in the 471 ABCD bits when the ds0 is connected and 472 dsx0TransmitCodesEnable is enabled. The object is 473 a bitmap and the various bit positions are: 474 1 D bit 475 2 C bit 476 4 B bit 477 8 A bit" 478 ::= { dsx0ConfigEntry 5 } 480 dsx0ReceivedCode OBJECT-TYPE 481 SYNTAX INTEGER(0..15) 482 MAX-ACCESS read-only 483 STATUS current 484 DESCRIPTION 485 "This object contains the code being received in 486 the ABCD bits. The object is a bitmap and the 487 various bit positions are: 488 1 D bit 489 2 C bit 490 4 B bit 491 8 A bit" 492 ::= { dsx0ConfigEntry 6 } 494 dsx0TransmitCodesEnable OBJECT-TYPE 495 SYNTAX TruthValue 496 MAX-ACCESS read-write 497 STATUS current 498 DESCRIPTION 499 "This object determines if the idle and seized 500 codes are transmitted. If the value of this object 501 is true then the codes are transmitted." 502 ::= { dsx0ConfigEntry 7 } 504 dsx0Ds0BundleMappedIfIndex OBJECT-TYPE 505 SYNTAX InterfaceIndexOrZero 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "This object indicates the ifIndex value assigned 510 by the agent for the ds0Bundle(82) ifEntry to 511 which the given ds0(81) ifEntry may belong. 513 If the given ds0(81) ifEntry does not belong to 514 any ds0Bundle(82) ifEntry, then this object has a 515 value of zero. 517 While this object provides information that can 518 also be found in the ifStackTable, it provides 519 this same information with a single table lookup, 520 rather than by walking the ifStackTable to find 521 the possibly non-existent ds0Bundle(82) ifEntry 522 that may be stacked above the given ds0(81) 523 ifTable entry." 524 ::= { dsx0ConfigEntry 8 } 526 -- The DS0 Channel Mapping Table 528 dsx0ChanMappingTable OBJECT-TYPE 529 SYNTAX SEQUENCE OF Dsx0ChanMappingEntry 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 "The DS0 Channel Mapping table. This table maps a 534 DS0 channel number on a particular DS1/E1 into an 535 ifIndex." 536 ::= { ds0 3 } 538 dsx0ChanMappingEntry OBJECT-TYPE 539 SYNTAX Dsx0ChanMappingEntry 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION 543 "An entry in the DS0 Channel Mapping table. There 544 is an entry in this table corresponding to each 545 ds0 ifEntry within any interface that is 546 channelized to the individual ds0 ifEntry level. 548 This table is intended to facilitate mapping from 549 channelized interface / channel number to DS0 550 ifEntry. (e.g. mapping (DS1 ifIndex, DS0 Channel 551 Number) -> ifIndex) 553 While this table provides information that can 554 also be found in the ifStackTable and 555 dsx0ConfigTable, it provides this same information 556 with a single table lookup, rather than by walking 557 the ifStackTable to find the various constituent 558 ds0 ifTable entries, and testing various 559 dsx0ConfigTable entries to check for the entry 560 with the applicable DS0 channel number." 561 INDEX { ifIndex, dsx0Ds0ChannelNumber } 562 ::= { dsx0ChanMappingTable 1 } 564 Dsx0ChanMappingEntry ::= 565 SEQUENCE { 566 dsx0ChanMappedIfIndex InterfaceIndex 567 } 569 dsx0ChanMappedIfIndex OBJECT-TYPE 570 SYNTAX InterfaceIndex 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "This object indicates the ifIndex value assigned 575 by the agent for the individual ds0 ifEntry that 576 corresponds to the given DS0 channel number 577 (specified by the INDEX element 578 dsx0Ds0ChannelNumber) of the given channelized 579 interface (specified by INDEX element ifIndex)." 580 ::= { dsx0ChanMappingEntry 1 } 582 -- conformance information 584 ds0Conformance OBJECT IDENTIFIER ::= { ds0 2 } 586 ds0Groups OBJECT IDENTIFIER ::= { ds0Conformance 1 } 587 ds0Compliances OBJECT IDENTIFIER ::= { ds0Conformance 2 } 589 -- compliance statements 591 ds0Compliance MODULE-COMPLIANCE 592 STATUS current 593 DESCRIPTION 594 "The compliance statement for DS0 interfaces." 595 MODULE -- this module 596 MANDATORY-GROUPS { ds0ConfigGroup } 598 OBJECT dsx0RobbedBitSignalling 599 MIN-ACCESS read-only 600 DESCRIPTION 601 "The ability to set RBS is not required." 603 OBJECT dsx0CircuitIdentifier 604 MIN-ACCESS read-only 605 DESCRIPTION 606 "The ability to set the circuit identifier is not 607 required." 609 OBJECT dsx0IdleCode 610 MIN-ACCESS read-only 611 DESCRIPTION 612 "The ability to set the idle code is not 613 required." 615 OBJECT dsx0SeizedCode 616 MIN-ACCESS read-only 617 DESCRIPTION 618 "The ability to set the seized code is not 619 required." 621 OBJECT dsx0TransmitCodesEnable 622 MIN-ACCESS read-only 623 DESCRIPTION 624 "The ability to enable and disable the 625 transmitting of idle and seized codes is not 626 required." 628 ::= { ds0Compliances 1 } 630 -- units of conformance 632 ds0ConfigGroup OBJECT-GROUP 633 OBJECTS { dsx0Ds0ChannelNumber, 634 dsx0RobbedBitSignalling, 635 dsx0CircuitIdentifier, 636 dsx0IdleCode, 637 dsx0SeizedCode, 638 dsx0ReceivedCode, 639 dsx0TransmitCodesEnable, 640 dsx0Ds0BundleMappedIfIndex, 641 dsx0ChanMappedIfIndex } 642 STATUS current 643 DESCRIPTION 644 "A collection of objects providing configuration 645 information applicable to all DS0 interfaces." 646 ::= { ds0Groups 1 } 648 END 650 5. Object Definitions for DS0 Bundle 652 DS0BUNDLE-MIB DEFINITIONS ::= BEGIN 654 IMPORTS 655 MODULE-IDENTITY, OBJECT-TYPE, 656 transmission FROM SNMPv2-SMI 657 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 658 DisplayString, RowStatus, 659 TestAndIncr FROM SNMPv2-TC 660 ifIndex, InterfaceIndex FROM IF-MIB; 662 -- This is the MIB module for the DS0Bundle Interface 663 -- objects. 665 ds0Bundle MODULE-IDENTITY 666 LAST-UPDATED "9807161630Z" 667 ORGANIZATION "IETF Trunk MIB Working Group" 668 CONTACT-INFO 669 " David Fowler 671 Postal: Newbridge Networks Corporation 672 600 March Road 673 Kanata, Ontario, Canada K2K 2E6 675 Tel: +1 613 591 3600 676 Fax: +1 613 599 3619 678 E-mail: davef@newbridge.com" 679 DESCRIPTION 680 "The MIB module to describe 681 DS0 Bundle interfaces objects." 682 REVISION "9805242010Z" 683 DESCRIPTION 684 "Initial version of the DS0BUNDLE-MIB." 686 ::= { transmission 82 } 688 -- 689 -- The DS0 Bundle Config Group 690 -- 691 -- Implementation of this group is mandatory for all 692 -- systems that use a DS0Bundle Interface. 693 -- 694 -- The DS0 Bundle Config Group consists of one table: 695 -- DS0 Bundle Table 697 -- The DS0 Bundle Table 699 dsx0BundleNextIndex OBJECT-TYPE 700 SYNTAX TestAndIncr 701 MAX-ACCESS read-write 702 STATUS current 703 DESCRIPTION 704 "This object is used to assist the manager in 705 selecting a value for dsx0BundleIndex. Because 706 this object is of syntax TestAndIncr (see the 707 SNMPv2-TC document, RFC 1903) it can also be used 708 to avoid race conditions with multiple managers 709 trying to create rows in the table. 711 If the result of the SET for dsx0BundleNextIndex 712 is not success, this means the value has been 713 changed from index (i.e. another manager used the 714 value), so a new value is required. 716 The algorithm is: 717 done = false 718 while done == false 719 index = GET (dsx0BundleNextIndex.0) 720 SET (dsx0BundleNextIndex.0=index) 721 if (set failed) 722 done = false 723 else 724 SET(dsx0BundleRowStatus.index=createAndGo) 725 if (set failed) 726 done = false 727 else 728 done = true 729 other error handling" 730 ::= { ds0Bundle 2 } 732 dsx0BundleTable OBJECT-TYPE 733 SYNTAX SEQUENCE OF Dsx0BundleEntry 734 MAX-ACCESS not-accessible 735 STATUS current 736 DESCRIPTION 737 "There is an row in this table for each ds0Bundle 738 in the system. This table can be used to 739 (indirectly) create rows in the ifTable with 740 ifType = 'ds0Bundle(82)'." 741 ::= { ds0Bundle 3 } 743 dsx0BundleEntry OBJECT-TYPE 744 SYNTAX Dsx0BundleEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "There is a row in entry in this table for each 749 ds0Bundle interface." 750 INDEX { dsx0BundleIndex } 751 ::= { dsx0BundleTable 1 } 753 Dsx0BundleEntry ::= 754 SEQUENCE { 755 dsx0BundleIndex INTEGER, 756 dsx0BundleIfIndex InterfaceIndex, 757 dsx0BundleCircuitIdentifier DisplayString, 758 dsx0BundleRowStatus RowStatus 759 } 761 dsx0BundleIndex OBJECT-TYPE 762 SYNTAX INTEGER (0..2147483647) 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "A unique identifier for a ds0Bundle. This is not 767 the same value as ifIndex. This table is not 768 indexed by ifIndex because the manager has to 769 choose the index in a createable row and the agent 770 must be allowed to select ifIndex values." 771 ::= { dsx0BundleEntry 1 } 773 dsx0BundleIfIndex OBJECT-TYPE 774 SYNTAX InterfaceIndex 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The ifIndex value the agent selected for the 779 (new) ds0Bundle interface." 780 ::= { dsx0BundleEntry 2 } 782 dsx0BundleCircuitIdentifier OBJECT-TYPE 783 SYNTAX DisplayString (SIZE (0..255)) 784 MAX-ACCESS read-create 785 STATUS current 786 DESCRIPTION 787 "This variable contains the transmission vendor's 788 circuit identifier, for the purpose of 789 facilitating troubleshooting." 790 ::= { dsx0BundleEntry 3 } 792 dsx0BundleRowStatus OBJECT-TYPE 793 SYNTAX RowStatus 794 MAX-ACCESS read-create 795 STATUS current 796 DESCRIPTION 797 "This object is used to create and delete rows in 798 this table." 799 ::= { dsx0BundleEntry 4 } 801 -- The DS0 Bonding Group 803 -- Implementation of this group is optional for all 804 -- systems that use a DS0Bundle Interface. 806 -- The DS0 Bonding Group consists of one table: 807 -- DS0 Bonding Table 809 -- The DS0 Bonding Table 811 dsx0BondingTable OBJECT-TYPE 812 SYNTAX SEQUENCE OF Dsx0BondingEntry 813 MAX-ACCESS not-accessible 814 STATUS current 815 DESCRIPTION 816 "The DS0 Bonding table." 817 ::= { ds0Bundle 1 } 819 dsx0BondingEntry OBJECT-TYPE 820 SYNTAX Dsx0BondingEntry 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 "An entry in the DS0 Bonding table. There is a 825 row in this table for each DS0Bundle interface." 826 INDEX { ifIndex } 827 ::= { dsx0BondingTable 1 } 829 Dsx0BondingEntry ::= 830 SEQUENCE { 831 dsx0BondMode INTEGER, 832 dsx0BondStatus INTEGER, 833 dsx0BondRowStatus RowStatus 834 } 836 dsx0BondMode OBJECT-TYPE 837 SYNTAX INTEGER { 838 none(1), 839 other(2), 840 mode0(3), 841 mode1(4), 842 mode2(5), 843 mode3(6) 844 } 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "This object indicates which BONDing mode is used, 849 if any, for a ds0Bundle. Mode0 provides parameter 850 and number exchange with no synchronization. Mode 851 1 provides parameter and number exchange. Mode 1 852 also provides synchronization during 853 initialization but does not include inband 854 monitoring. Mode 2 provides all of the above plus 855 inband monitoring. Mode 2 also steals 1/64th of 856 the bandwidth of each channel (thus not supporting 857 n x 56/64 kbit/s data channels for most values of 858 n). Mode 3 provides all of the above, but also 859 provides n x 56/64 kbit/s data channels. Most 860 common implementations of Mode 3 add an extra 861 channel to support the inband monitoring overhead. 862 ModeNone should be used when the interface is not 863 performing bandwidth-on-demand." 864 ::= { dsx0BondingEntry 1 } 866 dsx0BondStatus OBJECT-TYPE 867 SYNTAX INTEGER { 868 idle(1), 869 callSetup(2), 870 dataTransfer(3) 871 } 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "This object indicates the current status of the 876 bonding call using this ds0Bundle. idle(1) should 877 be used when the bonding mode is set to none(1)." 878 ::= { dsx0BondingEntry 2 } 880 dsx0BondRowStatus OBJECT-TYPE 881 SYNTAX RowStatus 882 MAX-ACCESS read-create 883 STATUS current 884 DESCRIPTION 885 "This object is used to create new rows in this 886 table, modify existing rows, and to delete 887 existing rows." 888 ::= { dsx0BondingEntry 3 } 890 -- conformance information 892 ds0BundleConformance OBJECT IDENTIFIER ::= { ds0Bundle 4 } 894 ds0BundleGroups OBJECT IDENTIFIER 895 ::= { ds0BundleConformance 1 } 897 ds0BundleCompliances OBJECT IDENTIFIER 898 ::= { ds0BundleConformance 2 } 900 -- compliance statements 902 ds0BundleCompliance MODULE-COMPLIANCE 903 STATUS current 904 DESCRIPTION 905 "The compliance statement for DS0Bundle 906 interfaces." 907 MODULE -- this module 908 MANDATORY-GROUPS {ds0BundleConfigGroup } 910 GROUP ds0BondingGroup 911 DESCRIPTION 912 "Implementation of this group is optional for all 913 systems that attach to a DS0Bundle Interface." 915 OBJECT dsx0BundleRowStatus 916 SYNTAX INTEGER { 917 active(1), 918 createAndGo(4), 919 destroy(6) 920 } 921 MIN-ACCESS read-only 922 DESCRIPTION 923 "The agent is not required to support a SET 924 operation to this object, and only three of the 925 six enumerated values for the RowStatus textual 926 convention need be supported. Only supporting 927 createAndGo for a creation process prevents the 928 manager from creating an inactive row in the 929 ds0BundleTable. Inactive rows in the 930 ds0BundleTable do not make sense." 932 OBJECT dsx0BundleCircuitIdentifier 933 MIN-ACCESS read-only 934 DESCRIPTION 935 "The agent is not required to support a SET 936 operation to this object." 938 ::= { ds0BundleCompliances 1 } 940 -- units of conformance 942 ds0BondingGroup OBJECT-GROUP 943 OBJECTS { dsx0BondMode, 944 dsx0BondStatus, 945 dsx0BondRowStatus } 946 STATUS current 947 DESCRIPTION 948 "A collection of objects providing 949 configuration information applicable 950 to all DS0 interfaces." 951 ::= { ds0BundleGroups 1 } 953 ds0BundleConfigGroup OBJECT-GROUP 954 OBJECTS { dsx0BundleNextIndex, 955 dsx0BundleIfIndex, 956 dsx0BundleCircuitIdentifier, 957 dsx0BundleRowStatus } 958 STATUS current 959 DESCRIPTION 960 "A collection of objects providing the ability to 961 create a new ds0Bundle in the ifTable as well as 962 configuration information about the ds0Bundle." 963 ::= { ds0BundleGroups 2 } 964 END 966 6. Intellectual Property 968 The IETF takes no position regarding the validity or scope of any 969 intellectual property or other rights that might be claimed to 970 pertain to the implementation or use of the technology described in 971 this document or the extent to which any license under such rights 972 might or might not be available; neither does it represent that it 973 has made any effort to identify any such rights. Information on the 974 IETF's procedures with respect to rights in standards-track and 975 standards-related documentation can be found in BCP-11. Copies of 976 claims of rights made available for publication and any assurances of 977 licenses to be made available, or the result of an attempt made to 978 obtain a general license or permission for the use of such 979 proprietary rights by implementors or users of this specification can 980 be obtained from the IETF Secretariat. 982 The IETF invites any interested party to bring to its attention any 983 copyrights, patents or patent applications, or other proprietary 984 rights which may cover technology that may be required to practice 985 this standard. Please address the information to the IETF Executive 986 Director. 988 7. Acknowledgments 990 This document was produced by the Trunk MIB Working Group: 992 8. References 994 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 995 Describing SNMP Management Frameworks", RFC 2271, Cabletron 996 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 997 January 1998 999 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1000 Management Information for TCP/IP-based Internets", RFC 1155, 1001 Performance Systems International, Hughes LAN Systems, May 1990 1003 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1004 Performance Systems International, Hughes LAN Systems, March 1991 1006 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1007 RFC 1215, Performance Systems International, March 1991 1009 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 1010 of Management Information for Version 2 of the Simple Network 1011 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 1012 Systems, Inc., Dover Beach Consulting, Inc., International Network 1013 Services, January 1996. 1015 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1016 Conventions for Version 2 of the Simple Network Management Protocol 1017 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 1018 Dover Beach Consulting, Inc., International Network Services, 1019 January 1996. 1021 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 1022 Statements for Version 2 of the Simple Network Management Protocol 1023 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 1024 Dover Beach Consulting, Inc., International Network Services, 1025 January 1996. 1027 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1028 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1029 International, Performance Systems International, MIT Laboratory 1030 for Computer Science, May 1990. 1032 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1033 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1034 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1035 International Network Services, January 1996. 1037 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1038 Mappings for Version 2 of the Simple Network Management Protocol 1039 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1040 Dover Beach Consulting, Inc., International Network Services, 1041 January 1996. 1043 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1044 Processing and Dispatching for the Simple Network Management 1045 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 1046 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 1048 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1049 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1050 2274, IBM T. J. Watson Research, January 1998. 1052 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1053 Operations for Version 2 of the Simple Network Management Protocol 1054 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1055 Dover Beach Consulting, Inc., International Network Services, 1056 January 1996. 1058 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1059 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1060 Systems, January 1998. 1062 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1063 Control Model (VACM) for the Simple Network Management Protocol 1064 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1065 Cisco Systems, Inc., January 1998. 1067 [16] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB using 1068 SMIv2", RFC 2233, Cisco Systems, FTP Software, November 1997. 1070 [17] Fowler D., "Definitions of Managed Objects for the DS1 and E1 1071 Interface Types", draft-ietf-trunkmib-ds1-mib-09.txt, Newbridge 1072 Networks Corporation, August 1998. 1074 [18] Fowler, D., "Definitions of Managed Objects for the DS3/E3 1075 Interface Types", draft-ietf-trunkmib-ds3-mib-09.txt, Newbridge 1076 Networks, August 1998. 1078 [19] Brown, T., and Tesink, K., "Definitions of Managed Objects for the 1079 SONET/SDH Interface Type", draft-ietf-atommib-sonetng-02.txt, Bell 1080 Communications Research, August 1996. 1082 [20] Sharp, H. (Editor), "Interoperability Requirements for Nx56/64 1083 kbit/s Calls", BONDING Spec Version 1.0, BONDING Consortium, Sept 1084 1992. 1086 9. Security Considerations 1088 SNMPv1 by itself is such an insecure environment. Even if the 1089 network itself is secure (for example by using IPSec), even then, 1090 there is no control as to who on the secure network is allowed to 1091 access and GET (read) the objects in this MIB. 1093 It is recommended that the implementors consider the security 1094 features as provided by the SNMPv3 framework. Specifically, the use 1095 of the User-based Security Model RFC 2274 [12] and the View-based 1096 Access Control Model RFC 2275 [15] is recommended. 1098 It is then a customer/user responsibility to ensure that the SNMP 1099 entity giving access to an instance of this MIB, is properly 1100 configured to give access to those objects only to those principals 1101 (users) that have legitimate rights to access them. 1103 Setting the following objects to an inappropriate value can cause 1104 loss of traffic. In the case of dsx0RobbedBitSignalling, for 1105 example, the nature of the traffic flowing on the DS0 can be 1106 affected. 1107 dsx0RobbedBitSignalling 1108 dsx0IdleCode 1109 dsx0SeizedCode 1110 dsx0TransmitCodesEnable 1111 dsx0BundleRowStatus 1112 dsx0BondMode 1113 dsx0BondRowStatus 1115 Setting the following objects is mischievous, but not harmful to 1116 traffic. 1117 dsx0CircuitIdentifier 1118 dsx0BundleNextIndex 1120 10. Authors' Addresses 1122 David Fowler 1123 Newbridge Networks 1124 600 March Road 1125 Kanata, Ontario, Canada K2K 2E6 1127 Phone: (613) 599-3600, ext 6559 1128 EMail: davef@newbridge.com 1130 Table of Contents 1132 1 The SNMP Management Framework ................................ 2 1133 2 Overview ..................................................... 4 1134 2.1 BONDing Terminology ........................................ 4 1135 2.2 Use of ifTable for DS0 Layer ............................... 4 1136 2.3 Using ifStackTable ......................................... 5 1137 2.3.1 Usage of Channelization for DS3, DS1, DS0 ................ 8 1138 2.3.2 Usage of ifIndex Mapping for DS0Bundle ................... 9 1139 3 Overview of the MIB .......................................... 10 1140 3.1 DS0 MIB .................................................... 10 1141 3.2 DS0Bundle MIB .............................................. 10 1142 4 Object Definitions for DS0 ................................... 11 1143 5.1 The DS0 Config Group ....................................... 12 1144 5.1.1 The DS0 Configuration Table .............................. 12 1145 5.1.2 The DS0 Channel Mapping Table ............................ 15 1146 5 Object Definitions for DS0 Bundle ............................ 19 1147 6.1 The DS0 Bundle Config Group ................................ 20 1148 6.1.1 The DS0 Bundle Table ..................................... 20 1149 6.2 The DS0 Bonding Group ...................................... 22 1150 6.2.1 The DS0 Bonding Table .................................... 22 1151 6 Intellectual Property ........................................ 26 1152 7 Acknowledgments .............................................. 26 1153 8 References ................................................... 27 1154 9 Security Considerations ...................................... 30 1155 10 Authors' Addresses .......................................... 30