idnits 2.17.1 draft-ietf-trunkmib-ds3-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. Expected boilerplate is as follows today (2024-04-27) 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. ** There are 6 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** The abstract seems to contain references ([6], [7], [14]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- The abstract seems to indicate that this document obsoletes RFC1407, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 303 has weird spacing: '...ifIndex dsx1D...' == Line 318 has weird spacing: '...ifIndex dsx0...' == Line 338 has weird spacing: '...ifIndex dsx1D...' == Line 355 has weird spacing: '...ifIndex dsx1...' == Line 1005 has weird spacing: '...Failure any...' == (13 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 (February 1998) is 9568 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1905 (ref. '4') (Obsoleted by RFC 3416) == Outdated reference: A later version (-05) exists of draft-ietf-ifmib-mib-03 == Outdated reference: A later version (-09) exists of draft-ietf-trunkmib-ds1-mib-03 ** Obsolete normative reference: RFC 1595 (ref. '7') (Obsoleted by RFC 2558) -- Possible downref: Non-RFC (?) normative reference: ref. '8' -- Possible downref: Non-RFC (?) normative reference: ref. '9' -- Possible downref: Non-RFC (?) normative reference: ref. '9a' -- Possible downref: Non-RFC (?) normative reference: ref. '10' -- Possible downref: Non-RFC (?) normative reference: ref. '11' -- Possible downref: Non-RFC (?) normative reference: ref. '12' -- Possible downref: Non-RFC (?) normative reference: ref. '13' == Outdated reference: A later version (-08) exists of draft-ietf-trunkmib-ds0-mib-02 Summary: 15 errors (**), 0 flaws (~~), 11 warnings (==), 10 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT DS3/E3 MIB February 1998 3 Definitions of Managed Objects 4 for the DS3/E3 Interface Type 6 Tue Feb 24 09:53:17 EST 1998 8 draft-ietf-trunkmib-ds3-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 learn the current status of any Internet-Draft, please check the 27 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 28 Directories on ds.internic.net (US East Coast), nic.nordu.net 29 (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific 30 Rim). 32 Abstract 34 This memo defines an experimental portion of the Management 35 Information Base (MIB) for use with network management protocols in 36 the Internet community. In particular, it describes objects used for 37 managing DS3 and E3 interfaces. This document is a companion 38 document with Definitions of Managed Objects for the DS0, 39 DS1/E1/DS2/E2 and SONET/SDH Interface Types, rfcTBD [14], rfcTBD [6] 40 and rfcTBD [7]. 42 This memo specifies a MIB module in a manner that is both compliant 43 to the SNMPv2 SMI, and semantically identical to the peer SNMPv1 44 definitions. 46 This memo does not specify a standard for the Internet community. 48 This document entirely replaces RFC 1407. 50 1. The SNMPv2 Network Management Framework 52 The SNMP Network Management Framework presently consists of three 53 major components. They are: 55 o the SMI, described in RFC 1902 [1] - the mechanisms used for 56 describing and naming objects for the purpose of management. 58 o the MIB-II, STD 17, RFC 1213 [2] - the core set of managed 59 objects for the Internet suite of protocols. 61 o the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol 62 for accessing managed objects. 64 The Framework permits new objects to be defined for the purpose of 65 experimentation and evaluation. 67 2. Object Definitions 69 Managed objects are accessed via a virtual information store, termed 70 the Management Information Base or MIB. Objects in the MIB are 71 defined using the subset of Abstract Syntax Notation One (ASN.1) 72 defined in the SMI. In particular, each object type is named by an 73 OBJECT IDENTIFIER, an administratively assigned name. The object 74 type together with an object instance serves to uniquely identify a 75 specific instantiation of the object. For human convenience, we 76 often use a textual string, termed the descriptor, to also refer to 77 the object type. 79 2.1. Changes from RFC1407 81 This MIB obsoletes RFC1407. The changes from RFC1407 are the 82 following: 84 (1) The Fractional Table has been deprecated 86 (2) This document uses SMIv2 88 (3) Values are given for ifTable and ifXTable 90 (4) Example usage of ifStackTable is included 92 (5) dsx3IfIndex has been deprecated 94 (6) The definition of valid intervals has been clarified 95 for the case where the agent proxied for other 96 devices. In particular, the treatment of missing 97 intervals has been clarified. 99 (7) An inward loopback has been added. 101 (8) Additional lineStatus bits have been added for Near End 102 in Unavailable Signal State, Carrier Equipment Out of 103 Service, DS@ Payload AIS, and DS@ Performance Threshold 105 (9) A read-write line Length object has been added. 107 (10) Added a lineStatus last change, trap and enabler. 109 (11) Textual Conventions for statistics objects have 110 been used. 112 (12) A new object, dsx3LoopbackStatus, has been introduced 113 to reflect the loopbacks established on a DS3/E3 interface 114 and the source to the requests. dsx3LoopbackConfig 115 continues to be the desired loopback state while 116 dsx3LoopbackStatus reflects the actual state. 118 (13) A dual loopback has been added to allow the setting of 119 an inward loopback and a line loopback at the same time. 121 (14) An object has been added to indicated whether or not this 122 is a channelized DS3/E3. 124 (15) A new object has been added to indicate which DS1 is to 125 set for remote loopback. 127 3. Overview 129 These objects are used when the particular media being used to 130 realize an interface is a DS3/E3 interface. At present, this applies 131 to these values of the ifType variable in the Internet-standard MIB: 133 ds3 (30) 135 The DS3 definitions contained herein are based on the DS3 136 specifications in ANSI T1.102-1987, ANSI T1.107-1988, ANSI T1.107a- 137 1990, and ANSI T1.404-1989 [8,9,9a,10]. The E3 definitions contained 138 herein are based on the E3 specifications in CCITT G.751 [12]. 140 3.1. Use of ifTable for DS3 Layer 142 Only the ifGeneralGroup needs to be supported. 144 ifTable Object Use for DS3 Layer 145 ====================================================================== 146 ifIndex Interface index. 148 ifDescr See interfaces MIB [5] 150 ifType ds3(30) 152 ifSpeed Speed of line rate 153 DS3 - 44736000 154 E3 - 34368000 156 ifPhysAddress The value of the Circuit Identifier. 157 If no Circuit Identifier has been assigned 158 this object should have an octet string 159 with zero length. 161 ifAdminStatus See interfaces MIB [5] 163 ifOperStatus See interfaces MIB [5] 165 ifLastChange See interfaces MIB [5] 167 ifName See interfaces MIB [5] 169 ifLinkUpDownTrapEnable Set to enabled(1). 171 ifHighSpeed Speed of line in Mega-bits per second 172 (either 45 or 34) 174 ifConnectorPresent Set to true(1) normally, except for 175 cases such as DS3/E3 over AAL1/ATM where 176 false(2) is appropriate 178 3.2. Usage Guidelines 180 3.2.1. Usage of ifStackTable 182 The objects dsx3IfIndex and dsx3LineIndex have been deprecated. 183 These objects previously allowed a very special proxy situation to 184 exist for Routers and CSUs. This section now describes how to use 185 ifStackTable to represent this relationship. 187 The paragraphs discussing dsx3IfIndex and dsx3LineIndex have been 188 preserved in Appendix A for informational purposes. 190 The ifStackTable is used in the proxy case to represent the 191 assoication between pairs of interfaces, e.g. this DS3 is attached to 192 that DS3. This use is consistent with the use of the ifStackTable to 193 show the assoication between various sub-layers of an interface. In 194 both cases entire PDUs are exchanged between the interface pairs - in 195 the case of a DS3, entire DS3 frames are exchanged; in the case of 196 PPP and HDLC, entire HDLC frames are exchanged. This usage is not 197 meant to suggest the use of the ifStackTable to represent Time 198 Division Multiplexing (TDM) connections in general. 200 External&Internal interface scenario: the SNMP Agent resides on a 201 host external from the device supporting DS3/E3 interfaces (e.g., a 202 router). The Agent represents both the host and the DS3/E3 device. 204 Example: 206 A shelf full of CSUs connected to a Router. An SNMP Agent residing on 207 the router proxies for itself and the CSU. The router has also an 208 Ethernet interface: 210 +-----+ 211 | | | 212 | | | +---------------------+ 213 |E | | 44.736 MBPS | ds3 M13 Line#A | ds3 C-bit Parity 214 |t | R |---------------+ - - - - - - - - - +------> 215 |h | | | | 216 |e | O | 44.736 MBPS | ds3 M13 Line#B | ds3 C-bit Parity 217 |r | |---------------+ - - - - - - - - - - +------> 218 |n | U | | | 219 |e | | 44.736 MBPS | ds3 M13 Line#C | ds3 C-bit Parity 220 |t | T |---------------+ - - - -- -- - - - - +------> 221 | | | | | 222 |-----| E | 44.736 MBPS | ds3 M13 Line#D | ds3 C-bit Parity 223 | | |---------------+ - - - - -- - - - - +------> 224 | | R | |_____________________| 225 | | | 226 | +-----+ 228 The assignment of the index values could for example be: 230 ifIndex Description 231 1 Ethernet 232 2 Line#A Router 233 3 Line#B Router 234 4 Line#C Router 235 5 Line#D Router 236 6 Line#A CSU Router 237 7 Line#B CSU Router 238 8 Line#C CSU Router 239 9 Line#D CSU Router 240 10 Line#A CSU Network 241 11 Line#B CSU Network 242 12 Line#C CSU Network 243 13 Line#D CSU Network 245 The ifStackTable is then used to show the relationships between the 246 various DS3 interfaces. 248 ifStackTable Entries 250 HigherLayer LowerLayer 251 2 6 252 3 7 253 4 8 254 5 9 255 6 10 256 7 11 257 8 12 258 9 13 260 If the CSU shelf is managed by itself by a local SNMP Agent, the 261 situation would be identical, except the Ethernet and the 4 router 262 interfaces are deleted. Interfaces would also be numbered from 1 to 263 8. 265 ifIndex Description 266 1 Line#A CSU Router 267 2 Line#B CSU Router 268 3 Line#C CSU Router 269 4 Line#D CSU Router 270 5 Line#A CSU Network 271 6 Line#B CSU Network 272 7 Line#C CSU Network 273 8 Line#D CSU Network 275 ifStackTable Entries 277 HigherLayer LowerLayer 278 1 5 279 2 6 280 3 7 281 4 8 283 3.2.2. Usage of Channelization for DS3, DS1, DS0 285 An example is given here to explain the channelization objects in the 286 DS3, DS1, and DS0 MIBs to help the implementor use the objects 287 correctly. Treatment of E3 and E1 would be similar, with the number of 288 DS0s being different depending on the framing of the E1. 290 Assume that a DS3 (with ifIndex 1) is Channelized into DS1s (without 291 DS2s). The object dsx3Channelization is set to enabledDs1. When this 292 object is set to enabledDS1, 28 ifEntries of type DS1 will be created by 293 the agent. If dsx3Channelization is set to disabled, then the DS1s are 294 destroyed. 296 Assume the entries in the ifTable for the DS1s are created in channel 297 order and the ifIndex values are 2 through 29. In the DS1 MIB, there 298 will be an entry in the dsx1ChanMappingTable for each ds1. The entries 299 will be as follows: 301 dsx1ChanMappingTable Entries 303 ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 304 1 1 2 305 1 2 3 306 ...... 307 1 28 29 309 In addition, the DS1s are channelized into DS0s. The object 310 dsx1Channelization is set to enabledDS0 for each DS1. There will be 24 311 DS0s in the ifTable for each DS1. Assume the entries in the ifTable are 312 created in channel order and the ifIndex values for the DS0s in the 313 first DS1 are 30 through 53. In the DS0 MIB, there will be an entry in 314 the dsx0ChanMappingTable for each DS0. The entries will be as follows: 316 dsx0ChanMappingTable Entries 318 ifIndex dsx0Ds0ChannelNumber dsx0ChanMappedIfIndex 319 2 1 30 320 2 2 31 321 ...... 322 2 24 53 324 3.2.3. Usage of Channelization for DS3, DS2, DS1 326 An example is given here to explain the channelization objects in the 327 DS3 and DS1 MIBs to help the implementor use the objects correctly. 329 Assume that a DS3 (with ifIndex 1) is Channelized into DS2s. The object 330 dsx3Channelization is set to enabledDs2. There will be 7 DS2s (ifType 331 of DS1) in the ifTable. Assume the entries in the ifTable for the DS2s 332 are created in channel order and the ifIndex values are 2 through 8. In 333 the DS1 MIB, there will be an entry in the dsx1ChanMappingTable for each 334 DS2. The entries will be as follows: 336 dsx1ChanMappingTable Entries 338 ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 339 1 1 2 340 1 2 3 341 ...... 342 1 7 8 344 In addition, the DS2s are channelized into DS1s. The object 345 dsx1Channelization is set to enabledDS1 for each DS2. There will be 346 4 DS1s in the ifTable for each DS2. Assume the entries in the ifTable 347 are created in channel order and the ifIndex values for the DS1s in 348 the first DS2 are 9 through 12, then 13 through 16 for the second DS2, 349 and so on. In the DS1 MIB, there will be an 350 entry in the dsx1ChanMappingTable for each DS1. The entries will 351 be as follows: 353 dsx1ChanMappingTable Entries 355 ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 356 2 1 9 357 2 2 10 358 2 3 11 359 2 4 12 360 3 1 13 361 3 2 14 362 ... 363 8 4 36 365 3.2.4. Usage of Loopbacks 367 This section discusses the behaviour of objects related to loopbacks. 369 The object dsx3LoopbackConfig represents the desired state of loopbacks 370 on this interface. Using this object a Manager can request: 371 LineLoopback 372 PayloadLoopback (if ESF framing) 373 InwardLoopback 374 DualLoopback (Line + Inward) 375 NoLoopback 377 The remote end can also request lookbacks either through the FDL channel 378 if ESF or inband if D4. The loopbacks that can be request this way are: 379 LineLoopback 380 PayloadLoopback (if ESF framing) 381 NoLoopback 383 To model the current state of loopbacks on a DS3 interface, the object 384 dsx3LoopbackStatus defines which loopback is currently applies to an 385 interface. This objects, which is a bitmap, will have bits turned on 386 which reflect the currently active loopbacks on the interface as well as 387 the source of those loopbacks. 389 The following restrictions/rules apply to loopbacks: 391 The far end cannot undo loopbacks set by a manager. 393 A manager can undo loopbacks set by the far end. 395 Both a line loopback and an inward loopback can be set at the same time. 396 Only these two loopbacks can co-exist and either one may be set by the 397 manager or the far end. A LineLoopback request from the far end is 398 incremental to an existing Inward loopback established by a manager. 399 When a NoLoopback is received from the far end in this case, the 400 InwardLoopback remains in place. 402 3.3. Objectives of this MIB Module 404 There are numerous things that could be included in a MIB for DS3/E3 405 signals: the management of multiplexors, CSUs, DSUs, and the like. 406 The intent of this document is to facilitate the common management of 407 all devices with DS3/E3 interfaces. As such, a design decision was 408 made up front to very closely align the MIB with the set of objects 409 that can generally be read from DS3/E3 devices that are currently 410 deployed. 412 3.4. DS3/E3 Terminology 414 The terminology used in this document to describe error conditions on 415 a DS3 interface as monitored by a DS3 device are based on the late 416 but not final draft of what became the ANSI T1.231 standard [11]. If 417 the definition in this document does not match the definition in the 418 ANSI T1.231 document, the implementer should follow the definition 419 described in this document. 421 3.4.1. Error Events 423 Bipolar Violation (BPV) Error Event 424 A bipolar violation error event, for B3ZS(HDB3)-coded signals, 425 is the occurrence of a pulse of the same polarity as the 426 previous pulse without being part of the zero substitution 427 code, B3ZS(HDB3). For B3ZS(HDB3)-coded signals, a bipolar 428 violation error event may also include other error patterns 429 such as: three(four) or more consecutive zeros and incorrect 430 polarity. (See T1.231 section 7.1.1.1.1) 432 Excessive Zeros (EXZ) Error Event 433 An EXZ is the occurrence of any zero string length equal to or 434 greater than 3 for B3ZS, or greater than 4 for HDB3. (See 435 T1.231 section 7.1.1.1.2) 437 Line Coding Violation (LCV) Error Event 438 This parameter is a count of both BPVs and EXZs occurring over 439 the accumulation period. An EXZ increments the LCV by one 440 regardless of the length of the zero string. (Also known as 441 CV-L. See T1.231 section 7.4.1.1) 443 P-bit Coding Violation (PCV) Error Event 444 For all DS3 applications, a coding violation error event is a 445 P-bit Parity Error event. A P-bit Parity Error event is the 446 occurrence of a received P-bit code on the DS3 M-frame that is 447 not identical to the corresponding locally- calculated code. 448 (See T1.231 section 7.1.1.2.1) 450 C-bit Coding Violation (CCV) Error Event 451 For C-bit Parity and SYNTRAN DS3 applications, this is the 452 count of coding violations reported via the C-bits. For C-bit 453 Parity, it is a count of CP-bit parity errors occurring in the 454 accumulation interval. For SYNTRAN, it is a count of CRC-9 455 errors occurring in the accumulation interval. (See T1.231 456 section 7.1.1.2.2) 458 3.4.2. Performance Parameters 460 All performance parameters are accumulated in fifteen minute 461 intervals and up to 96 intervals (24 hours worth) are kept by an 462 agent. Fewer than 96 intervals of data will be available if the 463 agent has been restarted within the last 24 hours. In addition, 464 there is a rolling 24-hour total of each performance parameter. 466 There is no requirement for an agent to ensure fixed relationship 467 between the start of a fifteen minute interval and any wall clock; 468 however some agents may align the fifteen minute intervals with 469 quarter hours. 471 Performance parameters are of types PerfCurrentCount, 472 PerfIntervalCount and PerfTotalCount. These textual conventions are 473 all Gauge32, and they are used because it is possible for these 474 objects to decrease. Objects may decrease when Unavailable Seconds 475 occurs across a fifteen minutes interval boundary. See Unavailable 476 Seconds discussion later in this section. 478 Line Errored Seconds (LES) 479 A Line Errored Second is a second in which one or more CV 480 occurred OR one or more LOS defects. (Also known as ES-L. See 481 T1.231 section 7.4.1.2) 483 P-bit Errored Seconds (PES) 484 An PES is a second with one or more PCVs OR one or more Out of 485 Frame defects OR a detected incoming AIS. This gauge is not 486 incremented when UASs are counted. (Also known as ESP-P. See 487 T1.231 section 7.4.2.2) 489 P-bit Severely Errored Seconds (PSES) 490 A PSES is a second with 44 or more PCVs OR one or more Out of 491 Frame defects OR a detected incoming AIS. This gauge is not 492 incremented when UASs are counted. (Also known as SESP-P. See 493 T1.231 section 7.4.2.5) 495 C-bit Errored Seconds (CES) 496 An CES is a second with one or more CCVs OR one or more Out of 497 Frame defects OR a detected incoming AIS. This count is only 498 for the SYNTRAN and C-bit Parity DS3 applications. This gauge 499 is not incremented when UASs are counted. (Also known as 500 ESCP-P. See T1.231 section 7.4.2.2) 502 C-bit Severely Errored Seconds (CSES) 503 A CSES is a second with 44 or more CCVs OR one or more Out of 504 Frame defects OR a detected incoming AIS. This count is only 505 for the SYNTRAN and C-bit Parity DS3 applications. This gauge 506 is not incremented when UASs are counted. (Also known as 507 SESCP-P. See T1.231 section 7.4.2.5) 509 Severely Errored Framing Seconds (SEFS) 510 A SEFS is a second with one or more Out of Frame defects OR a 511 detected incoming AIS. This item is not incremented during 512 unavailable seconds. (Also known as SAS-P. See T1.231 section 513 7.4.2.6) 515 Unavailable Seconds (UAS) 516 UAS are calculated by counting the number of seconds that the 517 interface is unavailable. The DS3 interface is said to be 518 unavailable from the onset of 10 contiguous PSESs, or the 519 onset of the condition leading to a failure (see Failure 520 States). If the condition leading to the failure was 521 immediately preceded by one or more contiguous PSESs, then the 522 DS3 interface unavailability starts from the onset of these 523 PSESs. Once unavailable, and if no failure is present, the 524 DS3 interface becomes available at the onset of 10 contiguous 525 seconds with no PSESs. Once unavailable, and if a failure is 526 present, the DS3 interface becomes available at the onset of 527 10 contiguous seconds with no PSESs, if the failure clearing 528 time is less than or equal to 10 seconds. If the failure 529 clearing time is more than 10 seconds, the DS3 interface 530 becomes available at the onset of 10 contiguous seconds with 531 no PSESs, or the onset period leading to the successful 532 clearing condition, whichever occurs later. With respect to 533 the DS3 error counts, all counters are incremented while the 534 DS3 interface is deemed available. While the interface is 535 deemed unavailable, the only count that is incremented is 536 UASs. 538 Note that this definition implies that the agent cannot 539 determine until after a ten second interval has passed whether 540 a given one-second interval belongs to available or 541 unavailable time. If the agent chooses to update the various 542 performance statistics in real time then it must be prepared 543 to retroactively reduce the PES, PSES, CES, and CSES counts by 544 10 and increase the UAS count by 10 when it determines that 545 available time has been entered. It must also be prepared to 546 adjust the PCV, CCV, and SEFS count as necessary since these 547 parameters are not accumulated during unavailable time. It 548 must be similarly prepared to retroactively decrease the UAS 549 count by 10 and increase the PES, CES, PCV, and CCV counts as 550 necessary upon entering available time. A special case exists 551 when the 10 second period leading to available or unavailable 552 time crosses a 900 second statistics window boundary, as the 553 foregoing description implies that the PCV, CCV, PES, CES, 554 PSES, CSEC, SEFS, and UAS counts for the PREVIOUS interval 555 must be adjusted. In this case successive GETs of the 556 affected dsx3IntervalPSESs and dsx3IntervalUASs objects will 557 return differing values if the first GET occurs during the 558 first few seconds of the window. 560 The agent may instead choose to delay updates to the various 561 statistics by 10 seconds in order to avoid retroactive 562 adjustments to the counters. A way to do this is sketched in 563 Appendix B. 565 In any case, a linkDown trap shall be sent only after the 566 agent has determined for certain that the unavailable state 567 has been entered, but the time on the trap will be that of the 568 first UAS (i.e., 10 seconds earlier). A linkUp trap shall be 569 handled similarly. 571 According to ANSI T1.231 unavailable time begins at the 572 _onset_ of 10 contiguous severely errored seconds -- that is, 573 unavailable time starts with the _first_ of the 10 contiguous 574 SESs. Also, while an interface is deemed unavailable all 575 counters for that interface are frozen except for the UAS 576 count. It follows that an implementation which strictly 577 complies with this standard must _not_ increment any counters 578 other than the UAS count -- even temporarily -- as a result of 579 anything that happens during those 10 seconds. Since changes 580 in the signal state lag the data to which they apply by 10 581 seconds, an ANSI-compliant implementation must pass the the 582 one-second statistics through a 10-second delay line prior to 583 updating any counters. That can be done by performing the 584 following steps at the end of each one second interval. 586 i) Read near/far end CV counter and alarm status flags from the 587 hardware. 589 ii) Accumulate the CV counts for the preceding second and 590 compare them to the ES and SES threshold for the layer 591 in question. Update the signal state and shift the 592 one-second CV counts and ES/SES flags into the 10-element 593 delay line. Note that far-end one-second statistics are 594 to be flagged as "absent" during any second in which there 595 is an incoming defect at the layer in question or at any 596 lower layer. 598 iii) Update the current interval statistics using the signal 599 state from the _previous_ update cycle and the one-second 600 CV counts and ES/SES flags shifted out of the 10-element 601 delay line. 603 This approach is further described in Appendix B. 605 3.4.3. Performance Defects 607 Failure States: 608 The Remote Alarm Indication (RAI) failure, in SYNTRAN 609 applications, is declared after detecting the Yellow Alarm 610 Signal on the alarm channel. See ANSI T1.107a-1990 [9a]. The 611 Remote Alarm Indication failure, in C-bit Parity DS3 612 applications, is declared as soon as the presence of either 613 one or two alarm signals are detected on the Far End Alarm 614 Channel. See [9]. The Remote Alarm Indication failure may 615 also be declared after detecting the far-end SEF/AIS defect 616 (aka yellow). The Remote Alarm Indication failure is cleared 617 as soon as the presence of the any of the above alarms are 618 removed. 620 Also, the incoming failure state is declared when a defect 621 persists for at least 2-10 seconds. The defects are the 622 following: Loss of Signal (LOS), an Out of Frame (OOF) or an 623 incoming Alarm Indication Signal (AIS). The Failure State is 624 cleared when the defect is absent for less than or equal to 20 625 seconds. 627 Far End SEF/AIS defect (aka yellow) 628 A Far End SEF/AIS defect is the occurrence of the two X-bits 629 in a M-frame set to zero. The Far End SEF/AIS defect is 630 terminated when the two X-bits in a M-frame are set to one. 631 (Also known as SASCP-PFE. See T1.231 section 7.4.4.2.6) 633 Out of Frame (OOF) defect 634 A DS3 OOF defect is detected when any three or more errors in 635 sixteen or fewer consecutive F-bits occur within a DS3 M- 636 frame. An OOF defect may also be called a Severely Errored 637 Frame (SEF) defect. An OOF defect is cleared when reframe 638 occurs. A DS3 Loss of Frame (LOF) failure is declared when 639 the DS3 OOF defect is consistent for 2 to 10 seconds. The DS3 640 OOF defect ends when reframe occurs. The DS3 LOF failure is 641 cleared when the DS3 OOF defect is absent for 10 to 20 642 seconds. (See T1.231 section 7.1.2.2.1) 644 An E3 OOF defect is detected when four consecutive frame 645 alignment signals have been incorrectly received in there 646 predicted positions in an E3 signal. E3 frame alignment occurs 647 when the presence of three consecutive frame alignment signals 648 have been detected. 650 Loss of Signal (LOS) 651 defect 652 The DS3 LOS defect is declared upon observing 175 +/- 75 653 contiguous pulse positions with no pulses of either positive 654 or negative polarity. The DS3 LOS defect is terminated upon 655 observing an average pulse density of at least 33% over a 656 period of 175 +/- 75 contiguous pulse positions starting with 657 the receipt of a pulse. (See T1.231 section 7.1.2.1.1) 659 Alarm Indication Signal (AIS) defect 660 The DS3 AIS is framed with "stuck stuffing." This implies 661 that it has a valid M-subframe alignments bits, M-frame 662 alignment bits, and P bits. The information bits are set to a 663 1010... sequence, starting with a one (1) after each M- 664 subframe alignment bit, M-frame alignment bit, X bit, P bit, 665 and C bit. The C bits are all set to zero giving what is 666 called "stuck stuffing." The X bits are set to one. The DS3 667 AIS defect is declared after DS3 AIS is present in contiguous 668 M-frames for a time equal to or greater than T, where 0.2 ms 669 <= T <= 100 ms. The DS3 AIS defect is terminated after AIS is 670 absent in contiguous M-frames for a time equal to or greater 671 than T. (See T1.231 section 7.1.2.2.3) 673 The E3 binary content of the AIS is nominally a continuous 674 stream of ones. AIS detection and the application of 675 consequent actions, should be completed within a time limit of 676 1 ms. 678 3.4.4. Other Terms 679 Circuit Identifier 680 This is a character string specified by the circuit 681 vendor, and is useful when communicating with the vendor 682 during the troubleshooting process. 684 4. Object Definitions 686 DS3-MIB DEFINITIONS ::= BEGIN 688 IMPORTS 689 MODULE-IDENTITY, OBJECT-TYPE, 690 NOTIFICATION-TYPE, transmission FROM SNMPv2-SMI 691 DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC 692 MODULE-COMPLIANCE, OBJECT-GROUP, 693 NOTIFICATION-GROUP FROM SNMPv2-CONF 694 InterfaceIndex FROM IF-MIB 695 PerfCurrentCount, PerfIntervalCount, 696 PerfTotalCount FROM PerfHist-TC-MIB; 698 ds3 MODULE-IDENTITY 699 LAST-UPDATED "9802112330Z" 700 ORGANIZATION "IETF Trunk MIB Working Group" 701 CONTACT-INFO 702 " David Fowler 704 Postal: Newbridge Networks Corporation 705 600 March Road 706 Kanata, Ontario, Canada K2K 2E6 708 Tel: +1 613 591 3600 709 Fax: +1 613 599 3667 711 E-mail: davef@newbridge.com" 712 DESCRIPTION 713 "The is the MIB module that describes 714 DS3 and E3 interfaces objects." 716 ::= { transmission 30 } 718 -- The DS3/E3 Near End Group 720 -- The DS3/E3 Near End Group consists of four tables: 721 -- DS3/E3 Configuration 722 -- DS3/E3 Current 723 -- DS3/E3 Interval 724 -- DS3/E3 Total 726 -- the DS3/E3 Configuration Table 728 dsx3ConfigTable OBJECT-TYPE 729 SYNTAX SEQUENCE OF Dsx3ConfigEntry 730 MAX-ACCESS not-accessible 731 STATUS current 732 DESCRIPTION 733 "The DS3/E3 Configuration table." 734 ::= { ds3 5 } 736 dsx3ConfigEntry OBJECT-TYPE 737 SYNTAX Dsx3ConfigEntry 738 MAX-ACCESS not-accessible 739 STATUS current 740 DESCRIPTION 741 "An entry in the DS3/E3 Configuration table." 742 INDEX { dsx3LineIndex } 743 ::= { dsx3ConfigTable 1 } 745 Dsx3ConfigEntry ::= 746 SEQUENCE { 747 dsx3LineIndex InterfaceIndex, 748 dsx3IfIndex InterfaceIndex, 749 dsx3TimeElapsed INTEGER, 750 dsx3ValidIntervals INTEGER, 751 dsx3LineType INTEGER, 752 dsx3LineCoding INTEGER, 753 dsx3SendCode INTEGER, 754 dsx3CircuitIdentifier DisplayString, 755 dsx3LoopbackConfig INTEGER, 756 dsx3LineStatus INTEGER, 757 dsx3TransmitClockSource INTEGER, 758 dsx3InvalidIntervals INTEGER, 759 dsx3LineLength INTEGER, 760 dsx3LineStatusLastChange TimeStamp, 761 dsx3LineStatusChangeTrapEnable INTEGER, 762 dsx3LoopbackStatus INTEGER, 763 dsx3Channelization INTEGER, 764 dsx3Ds1ForRemoteLoop INTEGER 765 } 767 dsx3LineIndex OBJECT-TYPE 768 SYNTAX InterfaceIndex 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "This object should be made equal to ifIndex. The 773 next paragraph describes its previous usage. 774 Making the object equal to ifIndex allows propoer 775 use of ifStackTable. 777 Previously, this object was the identifier of a 778 DS3/E3 Interface on a managed device. If there is 779 an ifEntry that is directly associated with this 780 and only this DS3/E3 interface, it should have the 781 same value as ifIndex. Otherwise, number the 782 dsx3LineIndices with an unique identifier 783 following the rules of choosing a number that is 784 greater than ifNumber and numbering the inside 785 interfaces (e.g., equipment side) with even 786 numbers and outside interfaces (e.g, network side) 787 with odd numbers." 788 ::= { dsx3ConfigEntry 1 } 790 dsx3IfIndex OBJECT-TYPE 791 SYNTAX InterfaceIndex 792 MAX-ACCESS read-only 793 STATUS deprecated 794 DESCRIPTION 795 "This value for this object is equal to the value 796 of ifIndex from the Interfaces table of MIB II 797 (RFC 1213)." 798 ::= { dsx3ConfigEntry 2 } 800 dsx3TimeElapsed OBJECT-TYPE 801 SYNTAX INTEGER (0..899) 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The number of seconds that have elapsed since the 806 beginning of the near end current error- 807 measurement period." 809 ::= { dsx3ConfigEntry 3 } 811 dsx3ValidIntervals OBJECT-TYPE 812 SYNTAX INTEGER (0..96) 813 MAX-ACCESS read-only 814 STATUS current 815 DESCRIPTION 816 "The number of previous near end intervals for 817 which valid data was collected. The value will be 818 96 unless the interface was brought online within 819 the last 24 hours, in which case the value will be 820 the number of complete 15 minute near end 821 intervals since the interface has been online. In 822 the case where the agent is a proxy, it is 823 possible that some intervals are unavailable. In 824 this case, this interval is the maximum interval 825 number for which valid data is available." 826 ::= { dsx3ConfigEntry 4 } 828 dsx3LineType OBJECT-TYPE 829 SYNTAX INTEGER { 830 dsx3other(1), 831 dsx3M23(2), 832 dsx3SYNTRAN(3), 833 dsx3CbitParity(4), 834 dsx3ClearChannel(5), 835 e3other(6), 836 e3Framed(7), 837 e3Plcp(8) 838 } 839 MAX-ACCESS read-write 840 STATUS current 841 DESCRIPTION 842 "This variable indicates the variety of DS3 C-bit 843 or E3 application implementing this interface. The 844 type of interface affects the interpretation of 845 the usage and error statistics. The rate of DS3 846 is 44.736 Mbps and E3 is 34.368 Mbps. The 847 dsx3ClearChannel value means that the C-bits are 848 not used except for sending/receiving AIS. 849 The values, in sequence, describe: 851 TITLE: SPECIFICATION: 852 dsx3M23 ANSI T1.107-1988 [9] 853 dsx3SYNTRAN ANSI T1.107-1988 [9] 854 dsx3CbitParity ANSI T1.107a-1990 [9a] 855 dsx3ClearChannel ANSI T1.102-1987 [8] 856 e3Framed CCITT G.751 [12] 857 e3Plcp ETSI T/NA(91)18 [13]." 858 ::= { dsx3ConfigEntry 5 } 860 dsx3LineCoding OBJECT-TYPE 861 SYNTAX INTEGER { 862 dsx3Other(1), 863 dsx3B3ZS(2), 864 e3HDB3(3) 865 } 866 MAX-ACCESS read-write 867 STATUS current 868 DESCRIPTION 869 "This variable describes the variety of Zero Code 870 Suppression used on this interface, which in turn 871 affects a number of its characteristics. 873 dsx3B3ZS and e3HDB3 refer to the use of specified 874 patterns of normal bits and bipolar violations 875 which are used to replace sequences of zero bits 876 of a specified length." 877 ::= { dsx3ConfigEntry 6 } 879 dsx3SendCode OBJECT-TYPE 880 SYNTAX INTEGER { 881 dsx3SendNoCode(1), 882 dsx3SendLineCode(2), 883 dsx3SendPayloadCode(3), 884 dsx3SendResetCode(4), 885 dsx3SendDS1LoopCode(5), 886 dsx3SendTestPattern(6) 887 } 888 MAX-ACCESS read-write 889 STATUS current 890 DESCRIPTION 891 "This variable indicates what type of code is 892 being sent across the DS3/E3 interface by the 893 device. (These are optional for E3 interfaces.) 894 Setting this variable causes the interface to 895 begin sending the code requested. 896 The values mean: 898 dsx3SendNoCode 899 sending looped or normal data 901 dsx3SendLineCode 902 sending a request for a line loopback 904 dsx3SendPayloadCode 905 sending a request for a payload loopback 906 (i.e., all DS1/E1s in a DS3/E3 frame) 908 dsx3SendResetCode 909 sending a loopback deactivation request 911 dsx3SendDS1LoopCode 912 requesting to loopback a particular DS1/E1 913 within a DS3/E3 frame. The DS1/E1 is 914 indicated in dsx3Ds1ForRemoteLoop. 916 dsx3SendTestPattern 917 sending a test pattern." 918 ::= { dsx3ConfigEntry 7 } 920 dsx3CircuitIdentifier OBJECT-TYPE 921 SYNTAX DisplayString (SIZE (0..255)) 922 MAX-ACCESS read-write 923 STATUS current 924 DESCRIPTION 925 "This variable contains the transmission vendor's 926 circuit identifier, for the purpose of 927 facilitating troubleshooting." 928 ::= { dsx3ConfigEntry 8 } 930 dsx3LoopbackConfig OBJECT-TYPE 931 SYNTAX INTEGER { 932 dsx3NoLoop(1), 933 dsx3PayloadLoop(2), 934 dsx3LineLoop(3), 935 dsx3OtherLoop(4), 936 dsx3InwardLoop(5), 937 dsx3DualLoop(6) 938 } 939 MAX-ACCESS read-write 940 STATUS current 941 DESCRIPTION 942 "This variable represents the desired loopback 943 configuration of the DS3/E3 interface. 945 The values mean: 947 dsx3NoLoop 948 Not in the loopback state. A device that is 949 not capable of performing a loopback on 950 the interface shall always return this as 951 its value. 953 dsx3PayloadLoop 954 The received signal at this interface is looped 955 through the device. Typically the received signal 956 is looped back for retransmission after it has 957 passed through the device's framing function. 959 dsx3LineLoop 960 The received signal at this interface does not 961 go through the device (minimum penetration) but 962 is looped back out. 964 dsx3OtherLoop 965 Loopbacks that are not defined here. 967 dsx3InwardLoop 968 The sent signal at this interface is looped back 969 through the device. 971 dsx3DualLoop 972 Both dsx1LineLoop and dsx1InwardLoop will be 973 active simultaneously." 974 ::= { dsx3ConfigEntry 9 } 976 dsx3LineStatus OBJECT-TYPE 977 SYNTAX INTEGER (1..4095) 978 MAX-ACCESS read-only 979 STATUS current 980 DESCRIPTION 981 "This variable indicates the Line Status of the 982 interface. It contains loopback state information 983 and failure state information. The dsx3LineStatus 984 is a bit map represented as a sum, therefore, it 985 can represent multiple failures and a loopback 986 (see dsx3LoopbackConfig object for the type of 987 loopback) simultaneously. The dsx3NoAlarm must be 988 set if and only if no other flag is set. 990 If the dsx3loopbackState bit is set, the loopback 991 in effect can be determined from the 992 dsx3loopbackConfig object. 993 The various bit positions are: 994 1 dsx3NoAlarm No alarm present 995 2 dsx3RcvRAIFailure Receiving Yellow/Remote 996 Alarm Indication 997 4 dsx3XmitRAIAlarm Transmitting Yellow/Remote 998 Alarm Indication 999 8 dsx3RcvAIS Receiving AIS failure state 1000 16 dsx3XmitAIS Transmitting AIS 1001 32 dsx3LOF Receiving LOF failure state 1002 64 dsx3LOS Receiving LOS failure state 1003 128 dsx3LoopbackState Looping the received signal 1004 256 dsx3RcvTestCode Receiving a Test Pattern 1005 512 dsx3OtherFailure any line status not defined 1006 here 1007 1024 dsx3UnavailSigState Near End in Unavailable Signal 1008 State 1009 2048 dsx3NetEquipOOS Carrier Equipment Out of Service" 1010 ::= { dsx3ConfigEntry 10 } 1012 dsx3TransmitClockSource OBJECT-TYPE 1013 SYNTAX INTEGER { 1014 loopTiming(1), 1015 localTiming(2), 1016 throughTiming(3) 1017 } 1018 MAX-ACCESS read-write 1019 STATUS current 1020 DESCRIPTION 1021 "The source of Transmit Clock. 1023 loopTiming indicates that the recovered receive clock 1024 is used as the transmit clock. 1026 localTiming indicates that a local clock source is used 1027 or that an external clock is attached to the box 1028 containing the interface. 1030 throughTiming indicates that transmit clock is derived 1031 from the recovered receive clock of another DS3 1032 interface." 1033 ::= { dsx3ConfigEntry 11 } 1035 dsx3InvalidIntervals OBJECT-TYPE 1036 SYNTAX INTEGER (0..96) 1037 MAX-ACCESS read-only 1038 STATUS current 1039 DESCRIPTION 1040 "The number of intervals for which no valid data 1041 is available." 1042 ::= { dsx3ConfigEntry 12 } 1044 dsx3LineLength OBJECT-TYPE 1045 SYNTAX INTEGER (0..64000) 1046 UNITS "meters" 1047 MAX-ACCESS read-write 1048 STATUS current 1049 DESCRIPTION 1050 "The length of the ds3 line in meters. This 1051 object provides information for line build out 1052 circuitry if it exists and can use this object to 1053 adjust the line build out." 1054 ::= { dsx3ConfigEntry 13 } 1056 dsx3LineStatusLastChange OBJECT-TYPE 1057 SYNTAX TimeStamp 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "The value of MIB II's sysUpTime object at the 1062 time this DS3/E3 entered its current line status 1063 state. If the current state was entered prior to 1064 the last re-initialization of the proxy-agent, 1065 then this object contains a zero value." 1066 ::= { dsx3ConfigEntry 14 } 1068 dsx3LineStatusChangeTrapEnable OBJECT-TYPE 1069 SYNTAX INTEGER { 1070 enabled(1), 1071 disabled(2) 1072 } 1073 MAX-ACCESS read-write 1074 STATUS current 1075 DESCRIPTION 1076 "Indicates whether dsx3LineStatusChange traps 1077 should be generated for this interface." 1078 DEFVAL { disabled } 1079 ::= { dsx3ConfigEntry 15 } 1081 dsx3LoopbackStatus OBJECT-TYPE 1082 SYNTAX INTEGER (1..127) 1083 MAX-ACCESS read-only 1084 STATUS current 1085 DESCRIPTION 1086 "This variable represents the current state of the 1087 loopback on the DS3 interface. It contains 1088 information about loopbacks established by a 1089 manager and remotely from the far end. 1091 The dsx3LoopbackStatus is a bit map represented as 1092 a sum, therefore is can represent multiple 1093 loopbacks simultaneously. 1095 The various bit positions are: 1096 1 dsx3NoLoopback 1097 2 dsx3NearEndPayloadLoopback 1098 4 dsx3NearEndLineLoopback 1099 8 dsx3NearEndOtherLoopback 1100 16 dsx3NearEndInwardLoopback 1101 32 dsx3FarEndPayloadLoopback 1102 64 dsx3FarEndLineLoopback" 1104 ::= { dsx3ConfigEntry 16 } 1106 dsx3Channelization OBJECT-TYPE 1107 SYNTAX INTEGER { 1108 disabled(1), 1109 enabledDs1(2), 1110 enabledDs2(3) 1111 } 1112 MAX-ACCESS read-write 1113 STATUS current 1114 DESCRIPTION 1115 "Indicates whether this ds3/e3 is channelized or 1116 unchannelized. The value of enabledDs1 indicates 1117 that this is a DS3 channelized into DS1s. The 1118 value of enabledDs3 indicated that this is a DS3 1119 channelized into DS2s. Setting this object will 1120 cause the creation or deletion of DS2 or DS1 1121 entries in the ifTable. " 1122 ::= { dsx3ConfigEntry 17 } 1124 dsx3Ds1ForRemoteLoop OBJECT-TYPE 1125 SYNTAX INTEGER (0..29) 1126 MAX-ACCESS read-write 1127 STATUS current 1128 DESCRIPTION 1129 "Indicates which ds1/e1 on this ds3/e3 will be 1130 indicated in the remote ds1 loopback request. A 1131 value of 0 means no DS1 will be looped. A value 1132 of 29 means all ds1s/e1s will be looped." 1133 ::= { dsx3ConfigEntry 18 } 1134 -- the DS3/E3 Current Table 1136 dsx3CurrentTable OBJECT-TYPE 1137 SYNTAX SEQUENCE OF Dsx3CurrentEntry 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "The DS3/E3 current table contains various 1142 statistics being collected for the current 15 1143 minute interval." 1144 ::= { ds3 6 } 1146 dsx3CurrentEntry OBJECT-TYPE 1147 SYNTAX Dsx3CurrentEntry 1148 MAX-ACCESS not-accessible 1149 STATUS current 1150 DESCRIPTION 1151 "An entry in the DS3/E3 Current table." 1152 INDEX { dsx3CurrentIndex } 1153 ::= { dsx3CurrentTable 1 } 1155 Dsx3CurrentEntry ::= 1156 SEQUENCE { 1157 dsx3CurrentIndex InterfaceIndex, 1158 dsx3CurrentPESs PerfCurrentCount, 1159 dsx3CurrentPSESs PerfCurrentCount, 1160 dsx3CurrentSEFSs PerfCurrentCount, 1161 dsx3CurrentUASs PerfCurrentCount, 1162 dsx3CurrentLCVs PerfCurrentCount, 1163 dsx3CurrentPCVs PerfCurrentCount, 1164 dsx3CurrentLESs PerfCurrentCount, 1165 dsx3CurrentCCVs PerfCurrentCount, 1166 dsx3CurrentCESs PerfCurrentCount, 1167 dsx3CurrentCSESs PerfCurrentCount 1168 } 1170 dsx3CurrentIndex OBJECT-TYPE 1171 SYNTAX InterfaceIndex 1172 MAX-ACCESS read-only 1173 STATUS current 1174 DESCRIPTION 1175 "The index value which uniquely identifies the 1176 DS3/E3 interface to which this entry is 1177 applicable. The interface identified by a 1178 particular value of this index is the same 1179 interface as identified by the same value an 1180 dsx3LineIndex object instance." 1181 ::= { dsx3CurrentEntry 1 } 1183 dsx3CurrentPESs OBJECT-TYPE 1184 SYNTAX PerfCurrentCount 1185 MAX-ACCESS read-only 1186 STATUS current 1187 DESCRIPTION 1188 "The counter associated with the number of P-bit 1189 Errored Seconds, encountered by a DS3 interface in 1190 the current 15 minute interval. noSuchInstance 1191 will be returned if no data is available." 1192 ::= { dsx3CurrentEntry 2 } 1194 dsx3CurrentPSESs OBJECT-TYPE 1195 SYNTAX PerfCurrentCount 1196 MAX-ACCESS read-only 1197 STATUS current 1198 DESCRIPTION 1199 "The counter associated with the number of P-bit 1200 Severely Errored Seconds, encountered by a DS3 1201 interface in the current 15 minute interval. 1202 noSuchInstance will be returned if no data is 1203 available." 1204 ::= { dsx3CurrentEntry 3 } 1206 dsx3CurrentSEFSs OBJECT-TYPE 1207 SYNTAX PerfCurrentCount 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "The counter associated with the number of 1212 Severely Errored Framing Seconds, encountered by a 1213 DS3/E3 interface in the current 15 minute 1214 interval. noSuchInstance will be returned if no 1215 data is available." 1216 ::= { dsx3CurrentEntry 4 } 1218 dsx3CurrentUASs OBJECT-TYPE 1219 SYNTAX PerfCurrentCount 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION 1223 "The counter associated with the number of 1224 Unavailable Seconds, encountered by a DS3 1225 interface in the current 15 minute interval. 1226 noSuchInstance will be returned if no data is 1227 available." 1228 ::= { dsx3CurrentEntry 5 } 1230 dsx3CurrentLCVs OBJECT-TYPE 1231 SYNTAX PerfCurrentCount 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "The counter associated with the number of Line 1236 Coding Violations encountered by a DS3/E3 1237 interface in the current 15 minute interval. 1238 noSuchInstance will be returned if no data is 1239 available." 1240 ::= { dsx3CurrentEntry 6 } 1242 dsx3CurrentPCVs OBJECT-TYPE 1243 SYNTAX PerfCurrentCount 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "The counter associated with the number of P-bit 1248 Coding Violations, encountered by a DS3 interface 1249 in the current 15 minute interval. noSuchInstance 1250 will be returned if no data is available." 1251 ::= { dsx3CurrentEntry 7 } 1253 dsx3CurrentLESs OBJECT-TYPE 1254 SYNTAX PerfCurrentCount 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The number of Line Errored Seconds encountered by 1259 a DS3/E3 interface in the current 15 minute 1260 interval. noSuchInstance will be returned if no 1261 data is available." 1262 ::= { dsx3CurrentEntry 8 } 1264 dsx3CurrentCCVs OBJECT-TYPE 1265 SYNTAX PerfCurrentCount 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "The number of C-bit Coding Violations encountered 1270 by a DS3 interface in the current 15 minute 1271 interval. noSuchInstance will be returned if no 1272 data is available." 1273 ::= { dsx3CurrentEntry 9 } 1275 dsx3CurrentCESs OBJECT-TYPE 1276 SYNTAX PerfCurrentCount 1277 MAX-ACCESS read-only 1278 STATUS current 1279 DESCRIPTION 1280 "The number of C-bit Errored Seconds encountered 1281 by a DS3 interface in the current 15 minute 1282 interval. noSuchInstance will be returned if no 1283 data is available." 1284 ::= { dsx3CurrentEntry 10 } 1286 dsx3CurrentCSESs OBJECT-TYPE 1287 SYNTAX PerfCurrentCount 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The number of C-bit Severely Errored Seconds 1292 encountered by a DS3 interface in the current 15 1293 minute interval. noSuchInstance will be returned 1294 if no data is available." 1295 ::= { dsx3CurrentEntry 11 } 1297 -- the DS3/E3 Interval Table 1299 dsx3IntervalTable OBJECT-TYPE 1300 SYNTAX SEQUENCE OF Dsx3IntervalEntry 1301 MAX-ACCESS not-accessible 1302 STATUS current 1303 DESCRIPTION 1304 "The DS3/E3 Interval Table contains various 1305 statistics collected by each DS3/E3 Interface over 1306 the previous 24 hours of operation. The past 24 1307 hours are broken into 96 completed 15 minute 1308 intervals." 1310 ::= { ds3 7 } 1312 dsx3IntervalEntry OBJECT-TYPE 1313 SYNTAX Dsx3IntervalEntry 1314 MAX-ACCESS not-accessible 1315 STATUS current 1316 DESCRIPTION 1317 "An entry in the DS3/E3 Interval table." 1318 INDEX { dsx3IntervalIndex, dsx3IntervalNumber } 1319 ::= { dsx3IntervalTable 1 } 1321 Dsx3IntervalEntry ::= 1322 SEQUENCE { 1323 dsx3IntervalIndex InterfaceIndex, 1324 dsx3IntervalNumber INTEGER, 1325 dsx3IntervalPESs PerfIntervalCount, 1326 dsx3IntervalPSESs PerfIntervalCount, 1327 dsx3IntervalSEFSs PerfIntervalCount, 1328 dsx3IntervalUASs PerfIntervalCount, 1329 dsx3IntervalLCVs PerfIntervalCount, 1330 dsx3IntervalPCVs PerfIntervalCount, 1331 dsx3IntervalLESs PerfIntervalCount, 1332 dsx3IntervalCCVs PerfIntervalCount, 1333 dsx3IntervalCESs PerfIntervalCount, 1334 dsx3IntervalCSESs PerfIntervalCount, 1335 dsx3IntervalValidData TruthValue 1336 } 1338 dsx3IntervalIndex OBJECT-TYPE 1339 SYNTAX InterfaceIndex 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "The index value which uniquely identifies the 1344 DS3/E3 interface to which this entry is 1345 applicable. The interface identified by a 1346 particular value of this index is the same 1347 interface as identified by the same value an 1348 dsx3LineIndex object instance." 1349 ::= { dsx3IntervalEntry 1 } 1351 dsx3IntervalNumber OBJECT-TYPE 1352 SYNTAX INTEGER (1..96) 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "A number between 1 and 96, where 1 is the most 1357 recently completed 15 minute interval and 96 is 1358 the 15 minutes interval completed 23 hours and 45 1359 minutes prior to interval 1." 1360 ::= { dsx3IntervalEntry 2 } 1362 dsx3IntervalPESs OBJECT-TYPE 1363 SYNTAX PerfIntervalCount 1364 MAX-ACCESS read-only 1365 STATUS current 1366 DESCRIPTION 1367 "The counter associated with the number of P-bit 1368 Errored Seconds, encountered by a DS3 interface in 1369 one of the previous 96, individual 15 minute, 1370 intervals. In the case where the agent is a proxy 1371 and valid data is not available, return 1372 noSuchInstance." 1373 ::= { dsx3IntervalEntry 3 } 1375 dsx3IntervalPSESs OBJECT-TYPE 1376 SYNTAX PerfIntervalCount 1377 MAX-ACCESS read-only 1378 STATUS current 1379 DESCRIPTION 1380 "The counter associated with the number of P-bit 1381 Severely Errored Seconds, encountered by a DS3 1382 interface in one of the previous 96, individual 15 1383 minute, intervals. In the case where the agent is 1384 a proxy and valid data is not available, return 1385 noSuchInstance." 1386 ::= { dsx3IntervalEntry 4 } 1388 dsx3IntervalSEFSs OBJECT-TYPE 1389 SYNTAX PerfIntervalCount 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "The counter associated with the number of 1394 Severely Errored Framing Seconds, encountered by a 1395 DS3/E3 interface in one of the previous 96, 1396 individual 15 minute, intervals. In the case where 1397 the agent is a proxy and valid data is not 1398 available, return noSuchInstance." 1399 ::= { dsx3IntervalEntry 5 } 1401 dsx3IntervalUASs OBJECT-TYPE 1402 SYNTAX PerfIntervalCount 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "The counter associated with the number of 1407 Unavailable Seconds, encountered by a DS3 1408 interface in one of the previous 96, individual 15 1409 minute, intervals. In the case where the agent is 1410 a proxy and valid data is not available, return 1411 noSuchInstance. This object may decrease if the 1412 occurance of unavailable seconds occurs across an 1413 inteval boundary." 1414 ::= { dsx3IntervalEntry 6 } 1416 dsx3IntervalLCVs OBJECT-TYPE 1417 SYNTAX PerfIntervalCount 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "The counter associated with the number of Line 1422 Coding Violations encountered by a DS3/E3 1423 interface in one of the previous 96, individual 15 1424 minute, intervals. In the case where the agent is 1425 a proxy and valid data is not available, return 1426 noSuchInstance." 1427 ::= { dsx3IntervalEntry 7 } 1429 dsx3IntervalPCVs OBJECT-TYPE 1430 SYNTAX PerfIntervalCount 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "The counter associated with the number of P-bit 1435 Coding Violations, encountered by a DS3 interface 1436 in one of the previous 96, individual 15 minute, 1437 intervals. In the case where the agent is a proxy 1438 and valid data is not available, return 1439 noSuchInstance." 1440 ::= { dsx3IntervalEntry 8 } 1442 dsx3IntervalLESs OBJECT-TYPE 1443 SYNTAX PerfIntervalCount 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "The number of Line Errored Seconds (BPVs or 1448 illegal zero sequences) encountered by a DS3/E3 1449 interface in one of the previous 96, individual 15 1450 minute, intervals. In the case where the agent is 1451 a proxy and valid data is not available, return 1452 noSuchInstance." 1453 ::= { dsx3IntervalEntry 9 } 1455 dsx3IntervalCCVs OBJECT-TYPE 1456 SYNTAX PerfIntervalCount 1457 MAX-ACCESS read-only 1458 STATUS current 1459 DESCRIPTION 1460 "The number of C-bit Coding Violations encountered 1461 by a DS3 interface in one of the previous 96, 1462 individual 15 minute, intervals. In the case where 1463 the agent is a proxy and valid data is not 1464 available, return noSuchInstance." 1465 ::= { dsx3IntervalEntry 10 } 1467 dsx3IntervalCESs OBJECT-TYPE 1468 SYNTAX PerfIntervalCount 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "The number of C-bit Errored Seconds encountered 1473 by a DS3 interface in one of the previous 96, 1474 individual 15 minute, intervals. In the case where 1475 the agent is a proxy and valid data is not 1476 available, return noSuchInstance." 1477 ::= { dsx3IntervalEntry 11 } 1479 dsx3IntervalCSESs OBJECT-TYPE 1480 SYNTAX PerfIntervalCount 1481 MAX-ACCESS read-only 1482 STATUS current 1483 DESCRIPTION 1484 "The number of C-bit Severely Errored Seconds 1485 encountered by a DS3 interface in one of the 1486 previous 96, individual 15 minute, intervals. In 1487 the case where the agent is a proxy and valid data 1488 is not available, return noSuchInstance." 1489 ::= { dsx3IntervalEntry 12 } 1491 dsx3IntervalValidData OBJECT-TYPE 1492 SYNTAX TruthValue 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "This variable indicates if there is valid data 1497 for this interval." 1498 ::= { dsx3IntervalEntry 13 } 1500 -- the DS3/E3 Total 1502 dsx3TotalTable OBJECT-TYPE 1503 SYNTAX SEQUENCE OF Dsx3TotalEntry 1504 MAX-ACCESS not-accessible 1505 STATUS current 1506 DESCRIPTION 1507 "The DS3/E3 Total Table contains the cumulative 1508 sum of the various statistics for the 24 hour 1509 period preceding the current interval." 1510 ::= { ds3 8 } 1512 dsx3TotalEntry OBJECT-TYPE 1513 SYNTAX Dsx3TotalEntry 1514 MAX-ACCESS not-accessible 1515 STATUS current 1516 DESCRIPTION 1517 "An entry in the DS3/E3 Total table." 1518 INDEX { dsx3TotalIndex } 1519 ::= { dsx3TotalTable 1 } 1521 Dsx3TotalEntry ::= 1522 SEQUENCE { 1523 dsx3TotalIndex InterfaceIndex, 1524 dsx3TotalPESs PerfTotalCount, 1525 dsx3TotalPSESs PerfTotalCount, 1526 dsx3TotalSEFSs PerfTotalCount, 1527 dsx3TotalUASs PerfTotalCount, 1528 dsx3TotalLCVs PerfTotalCount, 1529 dsx3TotalPCVs PerfTotalCount, 1530 dsx3TotalLESs PerfTotalCount, 1531 dsx3TotalCCVs PerfTotalCount, 1532 dsx3TotalCESs PerfTotalCount, 1533 dsx3TotalCSESs PerfTotalCount 1534 } 1536 dsx3TotalIndex OBJECT-TYPE 1537 SYNTAX InterfaceIndex 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "The index value which uniquely identifies the 1542 DS3/E3 interface to which this entry is 1543 applicable. The interface identified by a 1544 particular value of this index is the same 1545 interface as identified by the same value an 1546 dsx3LineIndex object instance." 1547 ::= { dsx3TotalEntry 1 } 1549 dsx3TotalPESs OBJECT-TYPE 1550 SYNTAX PerfTotalCount 1551 MAX-ACCESS read-only 1552 STATUS current 1553 DESCRIPTION 1554 "The counter associated with the number of P-bit 1555 Errored Seconds, encountered by a DS3 interface in 1556 the previous 24 hour interval. Invalid 15 minute 1557 intervals count as 0." 1558 ::= { dsx3TotalEntry 2 } 1560 dsx3TotalPSESs OBJECT-TYPE 1561 SYNTAX PerfTotalCount 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "The counter associated with the number of P-bit 1566 Severely Errored Seconds, encountered by a DS3 1567 interface in the previous 24 hour interval. 1568 Invalid 15 minute intervals count as 0." 1569 ::= { dsx3TotalEntry 3 } 1571 dsx3TotalSEFSs OBJECT-TYPE 1572 SYNTAX PerfTotalCount 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "The counter associated with the number of 1577 Severely Errored Framing Seconds, encountered by a 1578 DS3/E3 interface in the previous 24 hour interval. 1579 Invalid 15 minute intervals count as 0." 1580 ::= { dsx3TotalEntry 4 } 1582 dsx3TotalUASs OBJECT-TYPE 1583 SYNTAX PerfTotalCount 1584 MAX-ACCESS read-only 1585 STATUS current 1586 DESCRIPTION 1587 "The counter associated with the number of 1588 Unavailable Seconds, encountered by a DS3 1589 interface in the previous 24 hour interval. 1591 Invalid 15 minute intervals count as 0." 1592 ::= { dsx3TotalEntry 5 } 1594 dsx3TotalLCVs OBJECT-TYPE 1595 SYNTAX PerfTotalCount 1596 MAX-ACCESS read-only 1597 STATUS current 1598 DESCRIPTION 1599 "The counter associated with the number of Line 1600 Coding Violations encountered by a DS3/E3 1601 interface in the previous 24 hour interval. 1602 Invalid 15 minute intervals count as 0." 1603 ::= { dsx3TotalEntry 6 } 1605 dsx3TotalPCVs OBJECT-TYPE 1606 SYNTAX PerfTotalCount 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "The counter associated with the number of P-bit 1611 Coding Violations, encountered by a DS3 interface 1612 in the previous 24 hour interval. Invalid 15 1613 minute intervals count as 0." 1614 ::= { dsx3TotalEntry 7 } 1616 dsx3TotalLESs OBJECT-TYPE 1617 SYNTAX PerfTotalCount 1618 MAX-ACCESS read-only 1619 STATUS current 1620 DESCRIPTION 1621 "The number of Line Errored Seconds (BPVs or 1622 illegal zero sequences) encountered by a DS3/E3 1623 interface in the previous 24 hour interval. 1624 Invalid 15 minute intervals count as 0." 1625 ::= { dsx3TotalEntry 8 } 1627 dsx3TotalCCVs OBJECT-TYPE 1628 SYNTAX PerfTotalCount 1629 MAX-ACCESS read-only 1630 STATUS current 1631 DESCRIPTION 1632 "The number of C-bit Coding Violations encountered 1633 by a DS3 interface in the previous 24 hour 1634 interval. Invalid 15 minute intervals count as 0." 1635 ::= { dsx3TotalEntry 9 } 1637 dsx3TotalCESs OBJECT-TYPE 1638 SYNTAX PerfTotalCount 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "The number of C-bit Errored Seconds encountered 1643 by a DS3 interface in the previous 24 hour 1644 interval. Invalid 15 minute intervals count as 0." 1645 ::= { dsx3TotalEntry 10 } 1647 dsx3TotalCSESs OBJECT-TYPE 1648 SYNTAX PerfTotalCount 1649 MAX-ACCESS read-only 1650 STATUS current 1651 DESCRIPTION 1652 "The number of C-bit Severely Errored Seconds 1653 encountered by a DS3 interface in the previous 24 1654 hour interval. Invalid 15 minute intervals count 1655 as 0." 1656 ::= { dsx3TotalEntry 11 } 1658 -- The DS3 Far End Group 1660 -- The DS3 Far End Group consists of four tables : 1661 -- DS3 Far End Configuration 1662 -- DS3 Far End Current 1663 -- DS3 Far End Interval 1664 -- DS3 Far End Total 1666 -- The DS3 Far End Configuration Table 1668 dsx3FarEndConfigTable OBJECT-TYPE 1669 SYNTAX SEQUENCE OF Dsx3FarEndConfigEntry 1670 MAX-ACCESS not-accessible 1671 STATUS current 1672 DESCRIPTION 1673 "The DS3 Far End Configuration Table contains 1674 configuration information reported in the C-bits 1675 from the remote end." 1676 ::= { ds3 9 } 1678 dsx3FarEndConfigEntry OBJECT-TYPE 1679 SYNTAX Dsx3FarEndConfigEntry 1680 MAX-ACCESS not-accessible 1681 STATUS current 1682 DESCRIPTION 1683 "An entry in the DS3 Far End Configuration table." 1684 INDEX { dsx3FarEndLineIndex } 1685 ::= { dsx3FarEndConfigTable 1 } 1687 Dsx3FarEndConfigEntry ::= 1688 SEQUENCE { 1689 dsx3FarEndLineIndex InterfaceIndex, 1690 dsx3FarEndEquipCode DisplayString, 1691 dsx3FarEndLocationIDCode DisplayString, 1692 dsx3FarEndFrameIDCode DisplayString, 1693 dsx3FarEndUnitCode DisplayString, 1694 dsx3FarEndFacilityIDCode DisplayString 1695 } 1697 dsx3FarEndLineIndex OBJECT-TYPE 1698 SYNTAX InterfaceIndex 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "The index value which uniquely identifies the DS3 1703 interface to which this entry is applicable. The 1704 interface identified by a particular value of this 1705 index is the same interface as identified by the 1706 same value an dsx3LineIndex object instance." 1707 ::= { dsx3FarEndConfigEntry 1 } 1709 dsx3FarEndEquipCode OBJECT-TYPE 1710 SYNTAX DisplayString (SIZE (0..10)) 1711 MAX-ACCESS read-write 1712 STATUS current 1713 DESCRIPTION 1714 "This is the Far End Equipment Identification code 1715 that describes the specific piece of equipment. 1716 It is sent within the Path Identification 1717 Message." 1718 ::= { dsx3FarEndConfigEntry 2 } 1720 dsx3FarEndLocationIDCode OBJECT-TYPE 1721 SYNTAX DisplayString (SIZE (0..11)) 1722 MAX-ACCESS read-write 1723 STATUS current 1724 DESCRIPTION 1725 "This is the Far End Location Identification code 1726 that describes the specific location of the 1727 equipment. It is sent within the Path 1728 Identification Message." 1729 ::= { dsx3FarEndConfigEntry 3 } 1731 dsx3FarEndFrameIDCode OBJECT-TYPE 1732 SYNTAX DisplayString (SIZE (0..10)) 1733 MAX-ACCESS read-write 1734 STATUS current 1735 DESCRIPTION 1736 "This is the Far End Frame Identification code 1737 that identifies where the equipment is located 1738 within a building at a given location. It is sent 1739 within the Path Identification Message." 1740 ::= { dsx3FarEndConfigEntry 4 } 1742 dsx3FarEndUnitCode OBJECT-TYPE 1743 SYNTAX DisplayString (SIZE (0..6)) 1744 MAX-ACCESS read-write 1745 STATUS current 1746 DESCRIPTION 1747 "This is the Far End code that identifies the 1748 equipment location within a bay. It is sent 1749 within the Path Identification Message." 1750 ::= { dsx3FarEndConfigEntry 5 } 1752 dsx3FarEndFacilityIDCode OBJECT-TYPE 1753 SYNTAX DisplayString (SIZE (0..38)) 1754 MAX-ACCESS read-write 1755 STATUS current 1756 DESCRIPTION 1757 "This code identifies a specific Far End DS3 path. 1758 It is sent within the Path Identification 1759 Message." 1760 ::= { dsx3FarEndConfigEntry 6 } 1762 -- The DS3 Far End Current 1764 dsx3FarEndCurrentTable OBJECT-TYPE 1765 SYNTAX SEQUENCE OF Dsx3FarEndCurrentEntry 1766 MAX-ACCESS not-accessible 1767 STATUS current 1768 DESCRIPTION 1769 "The DS3 Far End Current table contains various 1770 statistics being collected for the current 15 1771 minute interval. The statistics are collected 1772 from the far end block error code within the C- 1773 bits." 1774 ::= { ds3 10 } 1776 dsx3FarEndCurrentEntry OBJECT-TYPE 1777 SYNTAX Dsx3FarEndCurrentEntry 1778 MAX-ACCESS not-accessible 1779 STATUS current 1780 DESCRIPTION 1781 "An entry in the DS3 Far End Current table." 1782 INDEX { dsx3FarEndCurrentIndex } 1783 ::= { dsx3FarEndCurrentTable 1 } 1785 Dsx3FarEndCurrentEntry ::= 1786 SEQUENCE { 1787 dsx3FarEndCurrentIndex InterfaceIndex, 1788 dsx3FarEndTimeElapsed INTEGER, 1789 dsx3FarEndValidIntervals INTEGER, 1790 dsx3FarEndCurrentCESs PerfCurrentCount, 1791 dsx3FarEndCurrentCSESs PerfCurrentCount, 1792 dsx3FarEndCurrentCCVs PerfCurrentCount, 1793 dsx3FarEndCurrentUASs PerfCurrentCount, 1794 dsx3FarEndInvalidIntervals INTEGER 1795 } 1797 dsx3FarEndCurrentIndex OBJECT-TYPE 1798 SYNTAX InterfaceIndex 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 "The index value which uniquely identifies the DS3 1803 interface to which this entry is applicable. The 1804 interface identified by a particular value of this 1805 index is identical to the interface identified by 1806 the same value of dsx3LineIndex." 1807 ::= { dsx3FarEndCurrentEntry 1 } 1809 dsx3FarEndTimeElapsed OBJECT-TYPE 1810 SYNTAX INTEGER (0..899) 1811 MAX-ACCESS read-only 1812 STATUS current 1813 DESCRIPTION 1814 "The number of seconds that have elapsed since the 1815 beginning of the far end current error-measurement 1816 period." 1817 ::= { dsx3FarEndCurrentEntry 2 } 1819 dsx3FarEndValidIntervals OBJECT-TYPE 1820 SYNTAX INTEGER (0..96) 1821 MAX-ACCESS read-only 1822 STATUS current 1823 DESCRIPTION 1824 "The number of previous far end intervals for 1825 which valid data was collected. The value will be 1826 96 unless the interface was brought online within 1827 the last 24 hours, in which case the value will be 1828 the number of complete 15 minute far end intervals 1829 since the interface has been online." 1830 ::= { dsx3FarEndCurrentEntry 3 } 1832 dsx3FarEndCurrentCESs OBJECT-TYPE 1833 SYNTAX PerfCurrentCount 1834 MAX-ACCESS read-only 1835 STATUS current 1836 DESCRIPTION 1837 "The counter associated with the number of Far Far 1838 End C-bit Errored Seconds encountered by a DS3 1839 interface in the current 15 minute interval. 1840 noSuchInstance will be returned if no data is 1841 available." 1842 ::= { dsx3FarEndCurrentEntry 4 } 1844 dsx3FarEndCurrentCSESs OBJECT-TYPE 1845 SYNTAX PerfCurrentCount 1846 MAX-ACCESS read-only 1847 STATUS current 1848 DESCRIPTION 1849 "The counter associated with the number of Far End 1850 C-bit Severely Errored Seconds encountered by a 1851 DS3 interface in the current 15 minute interval. 1852 noSuchInstance will be returned if no data is 1853 available." 1854 ::= { dsx3FarEndCurrentEntry 5 } 1856 dsx3FarEndCurrentCCVs OBJECT-TYPE 1857 SYNTAX PerfCurrentCount 1858 MAX-ACCESS read-only 1859 STATUS current 1860 DESCRIPTION 1861 "The counter associated with the number of Far End 1862 C-bit Coding Violations reported via the far end 1863 block error count encountered by a DS3 interface 1864 in the current 15 minute interval. noSuchInstance 1865 will be returned if no data is available." 1866 ::= { dsx3FarEndCurrentEntry 6 } 1868 dsx3FarEndCurrentUASs OBJECT-TYPE 1869 SYNTAX PerfCurrentCount 1870 MAX-ACCESS read-only 1871 STATUS current 1872 DESCRIPTION 1873 "The counter associated with the number of Far End 1874 unavailable seconds encountered by a DS3 interface 1875 in the current 15 minute interval. noSuchInstance 1876 will be returned if no data is available." 1877 ::= { dsx3FarEndCurrentEntry 7 } 1879 dsx3FarEndInvalidIntervals OBJECT-TYPE 1880 SYNTAX INTEGER (0..96) 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 "The number of intervals for which no valid data 1885 is available." 1886 ::= { dsx3FarEndCurrentEntry 8 } 1888 -- The DS3 Far End Interval Table 1890 dsx3FarEndIntervalTable OBJECT-TYPE 1891 SYNTAX SEQUENCE OF Dsx3FarEndIntervalEntry 1892 MAX-ACCESS not-accessible 1893 STATUS current 1894 DESCRIPTION 1895 "The DS3 Far End Interval Table contains various 1896 statistics collected by each DS3 interface over 1897 the previous 24 hours of operation. The past 24 1898 hours are broken into 96 completed 15 minute 1899 intervals." 1900 ::= { ds3 11 } 1902 dsx3FarEndIntervalEntry OBJECT-TYPE 1903 SYNTAX Dsx3FarEndIntervalEntry 1904 MAX-ACCESS not-accessible 1905 STATUS current 1906 DESCRIPTION 1907 "An entry in the DS3 Far End Interval table." 1908 INDEX { dsx3FarEndIntervalIndex, 1909 dsx3FarEndIntervalNumber } 1910 ::= { dsx3FarEndIntervalTable 1 } 1912 Dsx3FarEndIntervalEntry ::= 1913 SEQUENCE { 1914 dsx3FarEndIntervalIndex InterfaceIndex, 1915 dsx3FarEndIntervalNumber INTEGER, 1916 dsx3FarEndIntervalCESs PerfIntervalCount, 1917 dsx3FarEndIntervalCSESs PerfIntervalCount, 1918 dsx3FarEndIntervalCCVs PerfIntervalCount, 1919 dsx3FarEndIntervalUASs PerfIntervalCount, 1920 dsx3FarEndIntervalValidData TruthValue 1921 } 1923 dsx3FarEndIntervalIndex OBJECT-TYPE 1924 SYNTAX InterfaceIndex 1925 MAX-ACCESS read-only 1926 STATUS current 1927 DESCRIPTION 1928 "The index value which uniquely identifies the DS3 1929 interface to which this entry is applicable. The 1930 interface identified by a particular value of this 1931 index is identical to the interface identified by 1932 the same value of dsx3LineIndex." 1933 ::= { dsx3FarEndIntervalEntry 1 } 1935 dsx3FarEndIntervalNumber OBJECT-TYPE 1936 SYNTAX INTEGER (1..96) 1937 MAX-ACCESS read-only 1938 STATUS current 1939 DESCRIPTION 1940 "A number between 1 and 96, where 1 is the most 1941 recently completed 15 minute interval and 96 is 1942 the 15 minutes interval completed 23 hours and 45 1943 minutes prior to interval 1." 1944 ::= { dsx3FarEndIntervalEntry 2 } 1946 dsx3FarEndIntervalCESs OBJECT-TYPE 1947 SYNTAX PerfIntervalCount 1948 MAX-ACCESS read-only 1949 STATUS current 1950 DESCRIPTION 1951 "The counter associated with the number of Far End 1952 C-bit Errored Seconds encountered by a DS3 1953 interface in one of the previous 96, individual 15 1954 minute, intervals. In the case where the agent is 1955 a proxy and valid data is not available, return 1956 noSuchInstance." 1957 ::= { dsx3FarEndIntervalEntry 3 } 1959 dsx3FarEndIntervalCSESs OBJECT-TYPE 1960 SYNTAX PerfIntervalCount 1961 MAX-ACCESS read-only 1962 STATUS current 1963 DESCRIPTION 1964 "The counter associated with the number of Far End 1965 C-bit Severely Errored Seconds encountered by a 1966 DS3 interface in one of the previous 96, 1967 individual 15 minute, intervals. In the case where 1968 the agent is a proxy and valid data is not 1969 available, return noSuchInstance." 1970 ::= { dsx3FarEndIntervalEntry 4 } 1972 dsx3FarEndIntervalCCVs OBJECT-TYPE 1973 SYNTAX PerfIntervalCount 1974 MAX-ACCESS read-only 1975 STATUS current 1976 DESCRIPTION 1977 "The counter associated with the number of Far End 1978 C-bit Coding Violations reported via the far end 1979 block error count encountered by a DS3 interface 1980 in one of the previous 96, individual 15 minute, 1981 intervals. In the case where the agent is a proxy 1982 and valid data is not available, return 1983 noSuchInstance." 1984 ::= { dsx3FarEndIntervalEntry 5 } 1986 dsx3FarEndIntervalUASs OBJECT-TYPE 1987 SYNTAX PerfIntervalCount 1988 MAX-ACCESS read-only 1989 STATUS current 1990 DESCRIPTION 1991 "The counter associated with the number of Far End 1992 unavailable seconds encountered by a DS3 interface 1993 in one of the previous 96, individual 15 minute, 1994 intervals. In the case where the agent is a proxy 1995 and valid data is not available, return 1996 noSuchInstance." 1997 ::= { dsx3FarEndIntervalEntry 6 } 1999 dsx3FarEndIntervalValidData OBJECT-TYPE 2000 SYNTAX TruthValue 2001 MAX-ACCESS read-only 2002 STATUS current 2003 DESCRIPTION 2004 "This variable indicates if there is valid data 2005 for this interval." 2006 ::= { dsx3FarEndIntervalEntry 7 } 2008 -- The DS3 Far End Total 2010 dsx3FarEndTotalTable OBJECT-TYPE 2011 SYNTAX SEQUENCE OF Dsx3FarEndTotalEntry 2012 MAX-ACCESS not-accessible 2013 STATUS current 2014 DESCRIPTION 2015 "The DS3 Far End Total Table contains the 2016 cumulative sum of the various statistics for the 2017 24 hour period preceding the current interval." 2018 ::= { ds3 12 } 2020 dsx3FarEndTotalEntry OBJECT-TYPE 2021 SYNTAX Dsx3FarEndTotalEntry 2022 MAX-ACCESS not-accessible 2023 STATUS current 2024 DESCRIPTION 2025 "An entry in the DS3 Far End Total table." 2026 INDEX { dsx3FarEndTotalIndex } 2027 ::= { dsx3FarEndTotalTable 1 } 2029 Dsx3FarEndTotalEntry ::= 2030 SEQUENCE { 2031 dsx3FarEndTotalIndex InterfaceIndex, 2032 dsx3FarEndTotalCESs PerfTotalCount, 2033 dsx3FarEndTotalCSESs PerfTotalCount, 2034 dsx3FarEndTotalCCVs PerfTotalCount, 2035 dsx3FarEndTotalUASs PerfTotalCount 2036 } 2038 dsx3FarEndTotalIndex OBJECT-TYPE 2039 SYNTAX InterfaceIndex 2040 MAX-ACCESS read-only 2041 STATUS current 2042 DESCRIPTION 2043 "The index value which uniquely identifies the DS3 2044 interface to which this entry is applicable. The 2045 interface identified by a particular value of this 2046 index is identical to the interface identified by 2047 the same value of dsx3LineIndex." 2048 ::= { dsx3FarEndTotalEntry 1 } 2050 dsx3FarEndTotalCESs OBJECT-TYPE 2051 SYNTAX PerfTotalCount 2052 MAX-ACCESS read-only 2053 STATUS current 2054 DESCRIPTION 2055 "The counter associated with the number of Far End 2056 C-bit Errored Seconds encountered by a DS3 2057 interface in the previous 24 hour interval. 2058 Invalid 15 minute intervals count as 0." 2059 ::= { dsx3FarEndTotalEntry 2 } 2061 dsx3FarEndTotalCSESs OBJECT-TYPE 2062 SYNTAX PerfTotalCount 2063 MAX-ACCESS read-only 2064 STATUS current 2065 DESCRIPTION 2066 "The counter associated with the number of Far End 2067 C-bit Severely Errored Seconds encountered by a 2068 DS3 interface in the previous 24 hour interval. 2069 Invalid 15 minute intervals count as 0." 2070 ::= { dsx3FarEndTotalEntry 3 } 2072 dsx3FarEndTotalCCVs OBJECT-TYPE 2073 SYNTAX PerfTotalCount 2074 MAX-ACCESS read-only 2075 STATUS current 2076 DESCRIPTION 2077 "The counter associated with the number of Far End 2078 C-bit Coding Violations reported via the far end 2079 block error count encountered by a DS3 interface 2080 in the previous 24 hour interval. Invalid 15 2081 minute intervals count as 0." 2082 ::= { dsx3FarEndTotalEntry 4 } 2084 dsx3FarEndTotalUASs OBJECT-TYPE 2085 SYNTAX PerfTotalCount 2086 MAX-ACCESS read-only 2087 STATUS current 2088 DESCRIPTION 2089 "The counter associated with the number of Far End 2090 unavailable seconds encountered by a DS3 interface 2091 in the previous 24 hour interval. Invalid 15 2092 minute intervals count as 0." 2093 ::= { dsx3FarEndTotalEntry 5 } 2095 -- the DS3/E3 Fractional Table 2097 -- This table is deprecated. 2099 dsx3FracTable OBJECT-TYPE 2100 SYNTAX SEQUENCE OF Dsx3FracEntry 2101 MAX-ACCESS not-accessible 2102 STATUS deprecated 2103 DESCRIPTION 2104 "This table is deprecated in favour of using 2105 ifStackTable. 2107 Implementation of this table was optional. It was 2108 designed for those systems dividing a DS3/E3 into 2109 channels containing different data streams that 2110 are of local interest. 2112 The DS3/E3 fractional table identifies which 2113 DS3/E3 channels associated with a CSU are being 2114 used to support a logical interface, i.e., an 2115 entry in the interfaces table from the Internet- 2116 standard MIB. 2118 For example, consider a DS3 device with 4 high 2119 speed links carrying router traffic, a feed for 2120 voice, a feed for video, and a synchronous channel 2121 for a non-routed protocol. We might describe the 2122 allocation of channels, in the dsx3FracTable, as 2123 follows: 2124 dsx3FracIfIndex.2. 1 = 3 dsx3FracIfIndex.2.15 = 4 2125 dsx3FracIfIndex.2. 2 = 3 dsx3FracIfIndex.2.16 = 6 2126 dsx3FracIfIndex.2. 3 = 3 dsx3FracIfIndex.2.17 = 6 2127 dsx3FracIfIndex.2. 4 = 3 dsx3FracIfIndex.2.18 = 6 2128 dsx3FracIfIndex.2. 5 = 3 dsx3FracIfIndex.2.19 = 6 2129 dsx3FracIfIndex.2. 6 = 3 dsx3FracIfIndex.2.20 = 6 2130 dsx3FracIfIndex.2. 7 = 4 dsx3FracIfIndex.2.21 = 6 2131 dsx3FracIfIndex.2. 8 = 4 dsx3FracIfIndex.2.22 = 6 2132 dsx3FracIfIndex.2. 9 = 4 dsx3FracIfIndex.2.23 = 6 2133 dsx3FracIfIndex.2.10 = 4 dsx3FracIfIndex.2.24 = 6 2134 dsx3FracIfIndex.2.11 = 4 dsx3FracIfIndex.2.25 = 6 2135 dsx3FracIfIndex.2.12 = 5 dsx3FracIfIndex.2.26 = 6 2136 dsx3FracIfIndex.2.13 = 5 dsx3FracIfIndex.2.27 = 6 2137 dsx3FracIfIndex.2.14 = 5 dsx3FracIfIndex.2.28 = 6 2138 For dsx3M23, dsx3 SYNTRAN, dsx3CbitParity, and 2139 dsx3ClearChannel there are 28 legal channels, 2140 numbered 1 throug h 28. 2142 For e3Framed there are 16 legal channels, numbered 2143 1 through 16. The channels (1..16) correspond 2144 directly to the equivalently numbered time-slots." 2145 ::= { ds3 13 } 2147 dsx3FracEntry OBJECT-TYPE 2148 SYNTAX Dsx3FracEntry 2149 MAX-ACCESS not-accessible 2150 STATUS deprecated 2151 DESCRIPTION 2152 "An entry in the DS3 Fractional table." 2153 INDEX { dsx3FracIndex, dsx3FracNumber } 2154 ::= { dsx3FracTable 1 } 2156 Dsx3FracEntry ::= 2157 SEQUENCE { 2158 dsx3FracIndex INTEGER, 2159 dsx3FracNumber INTEGER, 2160 dsx3FracIfIndex INTEGER 2161 } 2163 dsx3FracIndex OBJECT-TYPE 2164 SYNTAX INTEGER (1..'7fffffff'h) 2165 MAX-ACCESS read-only 2166 STATUS deprecated 2167 DESCRIPTION 2168 "The index value which uniquely identifies the 2169 DS3 interface to which this entry is applicable 2170 The interface identified by a particular value 2171 of this index is the same interface as 2172 identified by the same value an dsx3LineIndex 2173 object instance." 2174 ::= { dsx3FracEntry 1 } 2176 dsx3FracNumber OBJECT-TYPE 2177 SYNTAX INTEGER (1..31) 2178 MAX-ACCESS read-only 2179 STATUS deprecated 2180 DESCRIPTION 2181 "The channel number for this entry." 2182 ::= { dsx3FracEntry 2 } 2184 dsx3FracIfIndex OBJECT-TYPE 2185 SYNTAX INTEGER (1..'7fffffff'h) 2186 MAX-ACCESS read-write 2187 STATUS deprecated 2188 DESCRIPTION 2189 "An index value that uniquely identifies an 2190 interface. The interface identified by a 2191 particular value of this index is the same 2192 interface as identified by the same value an 2193 ifIndex object instance. If no interface is 2194 currently using a channel, the value should be 2195 zero. If a single interface occupies more than 2196 one time slot, that ifIndex value will be found 2197 in multiple time slots." 2198 ::= { dsx3FracEntry 3 } 2200 -- Ds3 TRAPS 2202 ds3Traps OBJECT IDENTIFIER ::= { ds3 15 } 2204 dsx3LineStatusChange NOTIFICATION-TYPE 2205 OBJECTS { dsx3LineStatus, 2206 dsx3LineStatusLastChange } 2207 STATUS current 2208 DESCRIPTION 2209 "A dsx3LineStatusChange trap is sent when the 2210 value of an instance of dsx3LineStatus changes. It 2211 can be utilized by an NMS to trigger polls. When 2212 the line status change results in a lower level 2213 line status change (i.e. ds1), then no traps for 2214 the lower level are sent." 2215 ::= { ds3Traps 0 1 } 2217 -- conformance information 2219 ds3Conformance OBJECT IDENTIFIER ::= { ds3 14 } 2221 ds3Groups OBJECT IDENTIFIER ::= { 2222 ds3Conformance 1 } ds3Compliances OBJECT 2223 IDENTIFIER ::= { ds3Conformance 2 } 2225 -- compliance statements 2227 ds3Compliance MODULE-COMPLIANCE 2228 STATUS current 2229 DESCRIPTION 2230 "The compliance statement for DS3/E3 2231 interfaces." 2232 MODULE -- this module 2233 MANDATORY-GROUPS { ds3NearEndConfigGroup, 2234 ds3NearEndStatisticsGroup } 2236 GROUP ds3FarEndGroup 2237 DESCRIPTION 2238 "Implementation of this group is optional for all 2239 systems that attach to a DS3 Interface. However, 2240 only C-bit Parity and SYNTRAN DS3 applications 2241 have the capability (option) of providing this 2242 information." 2243 GROUP ds3NearEndOptionalConfigGroup 2244 DESCRIPTION 2245 "Implementation of this group is optional for all 2246 systems that attach to a DS3 interface." 2248 OBJECT dsx3LineType 2249 MIN-ACCESS read-only 2250 DESCRIPTION 2251 "Write access for the line type is not required." 2253 OBJECT dsx3LineCoding 2254 MIN-ACCESS read-only 2255 DESCRIPTION 2256 "Write access for the line coding is not 2257 required." 2259 OBJECT dsx3SendCode 2260 MIN-ACCESS read-only 2261 DESCRIPTION 2262 "Write access for the send code is not required." 2264 OBJECT dsx3LoopbackConfig 2265 MIN-ACCESS read-only 2266 DESCRIPTION 2267 "Write access for loopbacks is not required." 2269 OBJECT dsx3TransmitClockSource 2270 MIN-ACCESS read-only 2271 DESCRIPTION 2272 "Write access for the transmit clock source is not 2273 required." 2275 OBJECT dsx3LineLength 2276 MIN-ACCESS read-only 2277 DESCRIPTION 2278 "Write access for the line length is not 2279 required." 2281 OBJECT dsx3Channelization 2282 MIN-ACCESS read-only 2283 DESCRIPTION 2284 "Write access for the channelization is not 2285 required." 2287 ::= { ds3Compliances 1 } 2289 -- units of conformance 2291 ds3NearEndConfigGroup OBJECT-GROUP 2292 OBJECTS { dsx3LineIndex, 2293 dsx3TimeElapsed, 2294 dsx3ValidIntervals, 2295 dsx3LineType, 2296 dsx3LineCoding, 2297 dsx3SendCode, 2298 dsx3CircuitIdentifier, 2299 dsx3LoopbackConfig, 2300 dsx3LineStatus, 2301 dsx3TransmitClockSource, 2302 dsx3InvalidIntervals, 2303 dsx3LineLength, 2304 dsx3LoopbackStatus, 2305 dsx3Channelization, 2306 dsx3Ds1ForRemoteLoop } 2307 STATUS current 2308 DESCRIPTION 2309 "A collection of objects providing configuration 2310 information applicable to all DS3/E3 interfaces." 2311 ::= { ds3Groups 1 } 2313 ds3NearEndStatisticsGroup OBJECT-GROUP 2314 OBJECTS { dsx3CurrentIndex, 2315 dsx3CurrentPESs, 2316 dsx3CurrentPSESs, 2317 dsx3CurrentSEFSs, 2318 dsx3CurrentUASs, 2319 dsx3CurrentLCVs, 2320 dsx3CurrentPCVs, 2321 dsx3CurrentLESs, 2322 dsx3CurrentCCVs, 2323 dsx3CurrentCESs, 2324 dsx3CurrentCSESs, 2325 dsx3IntervalIndex, 2326 dsx3IntervalNumber, 2327 dsx3IntervalPESs, 2328 dsx3IntervalPSESs, 2329 dsx3IntervalSEFSs, 2330 dsx3IntervalUASs, 2331 dsx3IntervalLCVs, 2332 dsx3IntervalPCVs, 2333 dsx3IntervalLESs, 2334 dsx3IntervalCCVs, 2335 dsx3IntervalCESs, 2336 dsx3IntervalCSESs, 2337 dsx3IntervalValidData, 2338 dsx3TotalIndex, 2339 dsx3TotalPESs, 2340 dsx3TotalPSESs, 2341 dsx3TotalSEFSs, 2342 dsx3TotalUASs, 2343 dsx3TotalLCVs, 2344 dsx3TotalPCVs, 2345 dsx3TotalLESs, 2346 dsx3TotalCCVs, 2347 dsx3TotalCESs, 2348 dsx3TotalCSESs } 2349 STATUS current 2350 DESCRIPTION 2351 "A collection of objects providing statistics 2352 information applicable to all DS3/E3 interfaces." 2353 ::= { ds3Groups 2 } 2355 ds3FarEndGroup OBJECT-GROUP 2356 OBJECTS { dsx3FarEndLineIndex, 2357 dsx3FarEndEquipCode, 2358 dsx3FarEndLocationIDCode, 2359 dsx3FarEndFrameIDCode, 2360 dsx3FarEndUnitCode, 2361 dsx3FarEndFacilityIDCode, 2362 dsx3FarEndCurrentIndex, 2363 dsx3FarEndTimeElapsed, 2364 dsx3FarEndValidIntervals, 2365 dsx3FarEndCurrentCESs, 2366 dsx3FarEndCurrentCSESs, 2367 dsx3FarEndCurrentCCVs, 2368 dsx3FarEndCurrentUASs, 2369 dsx3FarEndInvalidIntervals, 2370 dsx3FarEndIntervalIndex, 2371 dsx3FarEndIntervalNumber, 2372 dsx3FarEndIntervalCESs, 2373 dsx3FarEndIntervalCSESs, 2374 dsx3FarEndIntervalCCVs, 2375 dsx3FarEndIntervalUASs, 2376 dsx3FarEndIntervalValidData, 2377 dsx3FarEndTotalIndex, 2378 dsx3FarEndTotalCESs, 2379 dsx3FarEndTotalCSESs, 2380 dsx3FarEndTotalCCVs, 2381 dsx3FarEndTotalUASs } 2382 STATUS current 2383 DESCRIPTION 2384 "A collection of objects providing remote 2385 configuration and statistics information 2386 applicable to C-bit Parity and SYNTRAN DS3 2387 interfaces." 2388 ::= { ds3Groups 3 } 2390 ds3DeprecatedGroup OBJECT-GROUP 2391 OBJECTS { dsx3IfIndex, 2392 dsx3FracIndex, 2393 dsx3FracNumber, 2394 dsx3FracIfIndex } 2395 STATUS deprecated 2396 DESCRIPTION 2397 "A collection of obsolete objects that may be 2398 implemented for backwards compatibility." 2399 ::= { ds3Groups 4 } 2401 ds3NearEndOptionalConfigGroup OBJECT-GROUP 2402 OBJECTS { dsx3LineStatusLastChange, 2403 dsx3LineStatusChangeTrapEnable } 2405 STATUS current 2406 DESCRIPTION 2407 "A collection of objects that may be implemented 2408 on DS3/E3 interfaces." 2409 ::= { ds3Groups 5 } 2411 ds3NearEndOptionalTrapGroup NOTIFICATION-GROUP 2412 NOTIFICATIONS { dsx3LineStatusChange } 2413 STATUS current 2414 DESCRIPTION 2415 "A collection of notifications that may be 2416 implemented on DS3/E3 interfaces." 2417 ::= { ds3Groups 6 } 2419 END 2421 5. Appendix A - Use of dsx3IfIndex and dsx3LineIndex 2423 This Appendix exists to document the previous use if dsx3IfIndex and 2424 dsx3LineIndex and to clarify the relationship of dsx3LineIndex as 2425 defined in rfc1407 with the dsx3LineIndex as defined in this 2426 document. 2428 The following shows the old and new definitions and the relationship: 2430 [New Definition]: "This object should be made equal to ifIndex. The 2431 next paragraph describes its previous usage. Making the object equal 2432 to ifIndex allows proper use of ifStackTable. 2434 [Old Definition]: "this object is the identifier of a DS3/E3 2435 Interface on a managed device. If there is an ifEntry that is 2436 directly associated with this and only this DS3/E3 interface, it 2437 should have the same value as ifIndex. Otherwise, number the 2438 dsx3LineIndices with an unique identifier following the rules of 2439 choosing a number that is greater than ifNumber and numbering the 2440 inside interfaces (e.g., equipment side) with even numbers and 2441 outside interfaces (e.g, network side) with odd numbers." 2443 When the "Old Definition" was created, my understanding was that it 2444 was described this way to allow a manager to treat the value _as if_ 2445 it were and ifIndex, i.e. the value would either be: 1) an ifIndex 2446 value or 2) a value that was guaranteed to be different from all 2447 valid ifIndex values. 2449 The new definition is a subset of that definition, i.e. the value is 2450 always an ifIndex value. 2452 The following is Section 3.1 from rfc1407: 2454 Different physical configurations for the support of SNMP with DS3/E3 2455 equipment exist. To accommodate these scenarios, two different 2456 indices for DS3/E3 interfaces are introduced in this MIB. These 2457 indices are dsx3IfIndex and dsx3LineIndex. 2459 External interface scenario: the SNMP Agent represents all managed 2460 DS3/E3 lines as external interfaces (for example, an Agent residing 2461 on the device supporting DS3/E3 interfaces directly): 2463 For this scenario, all interfaces are assigned an integer value equal 2464 to ifIndex, and the following applies: 2466 ifIndex=dsx3IfIndex=dsx3LineIndex for all interfaces. 2468 The dsx3IfIndex column of the DS3/E3 Configuration table relates each 2469 DS3/E3 interface to its corresponding interface (ifIndex) in the 2470 Internet-standard MIB (MIB-II STD 17, RFC1213). 2472 External&Internal interface scenario: the SNMP Agents resides on an 2473 host external from the device supporting DS3/E3 interfaces (e.g., a 2474 router). The Agent represents both the host and the DS3/E3 device. 2475 The index dsx3LineIndex is used to not only represent the DS3/E3 2476 interfaces external from the host/DS3/E3-device combination, but also 2477 the DS3/E3 interfaces connecting the host and the DS3/E3 device. The 2478 index dsx3IfIndex is always equal to ifIndex. 2480 Example: 2482 A shelf full of CSUs connected to a Router. An SNMP Agent residing on 2483 the router proxies for itself and the CSU. The router has also an 2484 Ethernet interface: 2486 +-----+ 2487 | | | 2488 | | | +---------------------+ 2489 |E | | 44.736 MBPS | ds3 M13 Line#A | ds3 C-bit Parity 2490 |t | R |---------------+ - - - - - - - - - +------> 2491 |h | | | | 2492 |e | O | 44.736 MBPS | ds3 M13 Line#B | ds3 C-bit Parity 2493 |r | |---------------+ - - - - - - - - - - +------> 2494 |n | U | | | 2495 |e | | 44.736 MBPS | ds3 M13 Line#C | ds3 C-bit Parity 2496 |t | T |---------------+ - - - -- -- - - - - +------> 2497 | | | | | 2498 |-----| E | 44.736 MBPS | ds3 M13 Line#D | ds3 C-bit Parity 2499 | | |---------------+ - - - - -- - - - - +------> 2500 | | R | |_____________________| 2501 | | | 2502 | +-----+ 2504 The assignment of the index values could for example be: 2506 ifIndex (= dsx3IfIndex) dsx3LineIndex 2508 1 NA NA (Ethernet) 2509 2 Line#A Router Side 6 2510 2 Line#A Network Side 7 2511 3 Line#B Router Side 8 2512 3 Line#B Network Side 9 2513 4 Line#C Router Side 10 2514 4 Line#C Network Side 11 2515 5 Line#D Router Side 12 2516 5 Line#D Network Side 13 2518 For this example, ifNumber is equal to 5. Note the 2519 following description of dsx3LineIndex: 2520 the dsx3LineIndex identifies a DS3/E3 Interface on a managed 2521 device. If there is an ifEntry that is directly associated with 2522 this and only this DS3/E3 interface, it should have the same value 2523 as ifIndex. Otherwise, number the dsx3LineIndices with an unique 2524 identifier following the rules of choosing a number greater 2525 than ifNumber and numbering inside interfaces (e.g., equipment 2526 side) with even numbers and outside interfaces 2527 (e.g, network side) with odd numbers. 2529 If the CSU shelf is managed by itself by a local SNMP Agent, 2530 the situation would be: 2532 ifIndex (= dsx3IfIndex) dsx3LineIndex 2534 1 Line#A Network Side 1 2535 2 Line#A RouterSide 2 2536 3 Line#B Network Side 3 2537 4 Line#B RouterSide 4 2538 5 Line#C Network Side 5 2539 6 Line#C Router Side 6 2540 7 Line#D Network Side 7 2541 8 Line#D Router Side 8 2543 6. Appendix B - The delay approach to Unavialable Seconds. 2544 This procedure is illustrated below for a DS3 C-Bit parity application. 2545 Similar rules would apply for other interfaces covered by this MIB. The 2546 procedure guarantees that the statistical counters are correctly updated 2547 at all times, although they lag real time by 10 seconds. At the end of 2548 each 15 minutes interval the current interval counts are transferred to 2549 the most recent interval entry and each interval is shifted up by one 2550 position, with the oldest being discarded if necessary in order to make 2551 room. The current interval counts then start over from zero. Note, 2552 however, that the signal state calculation does not start afresh at each 2553 interval boundary; rather, signal state information is retained across 2554 interval boundaries. 2555 +----------------------------------------------------------------+ 2556 | READ COUNTERS & STATUS INFO FROM HARDWARE | 2557 | | 2558 |BPV EXZ LOS PCV CCV AIS SEF OOF LOF FEBE RAI | 2559 +----------------------------------------------------------------+ 2560 | | | | | | | | | | | 2561 | | | | | | | | | | | 2562 V V V V V V V V V V V 2563 +----------------------------------------------------------------+ 2564 | ACCUM ONE-SEC STATS, CHK ERR THRESHOLDS, & UPDT SIGNAL STATE | 2565 | | 2566 |<------------- NEAR END ---------------->| |<---- FAR END ----->| 2567 | | 2568 |LCV LES PCV CCV PES CES PSES CSES SEFS A/U CCV CES CSES SEFS A/U| 2569 +----------------------------------------------------------------+ 2570 | | | | | | | | | | | | | | | 2571 | | | | | | | | | | | | | | | 2572 V V V V V V V V V | V V V V | 2573 +--------------------------------------+ | +-----------------+ | 2574 | ONE-SEC DELAY | | | ONE-SEC DELAY | | 2575 | (1 OF 10) | | | (1 OF 10) | | 2576 +--------------------------------------+ | +-----------------+ | 2577 | | | | | | | | | | | | | | | 2578 / / / / / / / / / / / / / / / 2579 | | | | | | | | | | | | | | | 2580 V V V V V V V V V | V V V V | 2581 +--------------------------------------+ | +-----------------+ | 2582 | ONE-SEC DELAY | | | ONE-SEC DELAY | | 2583 | (10 OF 10) | | | (10 OF 10) | | 2584 +--------------------------------------+ | +-----------------+ | 2585 | | | | | | | | | | | | | | | 2586 | | | | | | | | | | | | | | | 2587 V V V V V V V V V V V V V V V 2588 +----------------------------------------------------------------+ 2589 | UPDATE STATISTICS COUNTERS | 2590 | | 2591 |<------------- NEAR END ---------------->| |<---- FAR END ----->| 2592 | | 2593 |LCV LES PCV CCV PES CES PSES CSES SEFS UAS CCV CES CSES SEFS UAS| 2594 +----------------------------------------------------------------+ 2595 Note that if such a procedure is adopted there is no current interval 2596 data for the first ten seconds after a system comes up. noSuchInstance 2597 must be returned if a management station attempts to access the current 2598 interval counters during this time. 2600 It is an implementation-specific matter whether an agent assumes that 2601 the initial state of the interface is available or unavailable. 2603 7. Acknowledgments 2605 This document was produced by the Trunk MIB Working Group 2607 8. References 2609 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2610 S. Waldbusser, "Structure of Management Information for Version 2 2611 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2612 January 1996. 2614 [2] McCloghrie, K., and M. Rose, Editors, "Management 2615 Information Base for Network Management of TCP/IP-based 2616 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 2617 Performance Systems International, March 1991. 2619 [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin. " A Simple 2620 Network Management Protocol (SNMP)", STD 15, RFC 1157, SNMP 2621 Research, Performance Systems International, MIT Lab for 2622 Computer Science, May 1990. 2624 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2625 S. Waldbusser, "Protocol Operations for Version 2 of the Simple 2626 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2628 [5] McCloghrie, K. and F. Kastenholz, "Evolution of the 2629 Interfaces Group of MIB-II", draft-ietf-ifmib-mib-03.txt, 2630 Cisco, FTP Software, January 1994. 2632 [6] Fowler D., "Definitions of Managed Objects for the DS1 and 2633 E1 Interface Types", draft-ietf-trunkmib-ds1-mib-03.txt, 2634 Newbridge Networks Corporation, January 1993. 2636 [7] Brown, T., and Tesink, K., "Definitions of Managed Objects 2637 for the SONET/SDH Interface Type", RFC1595, Bell Communications 2638 Research, March 1994. 2640 [8] American National Standard for telecommunications - digital 2641 hierarchy - electrical interfaces, ANSI T1.102- 1987. 2643 [9] American National Standard for telecommunications - digital 2644 hierarchy - formats specification, ANSI T1.107- 1988. 2646 [9a] ANSI T1.107a-1990. 2648 [10] American National Standard for telecommunications - Carrier-to- 2649 Customer Installation - DS3 Metallic Interface, 2650 ANSI T1.404-1989. 2652 [11] American National Standard for Telecommunications -- 2653 Layer 1 In-Service Digital Transmission Performance Monitoring 2654 T1.231, Sept 1993. 2656 [12] CCITT - Digital Multiplex Equipment Operating at the Third 2657 Order Bit Rate of 34 368 Kbit/s and the Forth Order Bit Rate 2658 of 139 264 Kbit/s and Using Positive Justification, G.751 2660 [13] European Telecommunications Standards Institute -- 2661 ETS "34M" -- Metropolitan Area Network Physical Convergence 2662 Layer Procedure for 34.368 Megabits per Second, 2663 T/NA(91)18, May 1991. 2665 [14] Fowler, D., "Definitions of Managed Objects for the Ds0 and 2666 DS0Bundle Interface Types", draft-ietf-trunkmib-ds0-mib-02.txt, 2667 Newbridge Networks, March 1996. 2669 9. Security Considerations 2671 This MIB adds no security issues that are not raised by SNMP itself. 2672 As a Network Management Protocol, SNMP is capable of changing the 2673 configuration of a system, of denial of service attacks through 2674 requiring the agent to respond to its messages, and displaying values 2675 of system counters and configuration settings in the clear where an 2676 adversary might read them. This, however, is not in itself a threat: 2677 this is the function of the protocol, but could be misused. Such 2678 misuse can be avoided or minimized through SNMP Security. 2680 Setting any of the following objects to an inappropriate value can 2681 cause loss of traffic. The definition of inappropriate varies for 2682 each object. In the case of dsx3LineType, for example, both ends of 2683 a ds3/e3 must have the same value in order for traffic to flow. In 2684 the case of dsx3SendCode and dsx3LoopbackConfig, for another example, 2685 traffic may stop transmitting when particular loopbacks are applied. 2686 dsx3LineType 2687 dsx3LineCoding 2688 dsx3SendCode 2689 dsx3LoopbackConfig 2690 dsx3TransmitClockSource 2691 dsx3LineLength 2692 dsx3Channelization 2694 Setting the following object is mischevious, but not harmful to 2695 traffic 2696 dsx3CircuitIdentifier 2698 Setting the following object can cause an increase in the number of 2699 traps received by the network management station. 2700 dsx3LineStatusChangeTrabEnable 2702 10. Author's Address 2704 David Fowler 2705 Newbridge Networks 2706 600 March Road 2707 Kanata, Ontario, Canada K2K 2E6 2709 Phone: (613) 599-3600, ext 6559 2711 EMail: davef@newbridge.com 2713 Table of Contents 2715 1 The SNMPv2 Network Management Framework ...................... 2 2716 2 Object Definitions ........................................... 3 2717 2.1 Changes from RFC1407 ....................................... 3 2718 3 Overview ..................................................... 5 2719 3.1 Use of ifTable for DS3 Layer ............................... 5 2720 3.2 Usage Guidelines ........................................... 6 2721 3.2.1 Usage of ifStackTable .................................... 6 2722 3.2.2 Usage of Channelization for DS3, DS1, DS0 ................ 8 2723 3.2.3 Usage of Channelization for DS3, DS2, DS1 ................ 9 2724 3.2.4 Usage of Loopbacks ....................................... 10 2725 3.3 Objectives of this MIB Module .............................. 11 2726 3.4 DS3/E3 Terminology ......................................... 11 2727 3.4.1 Error Events ............................................. 11 2728 3.4.2 Performance Parameters ................................... 12 2729 3.4.3 Performance Defects ...................................... 15 2730 3.4.4 Other Terms .............................................. 17 2731 4 Object Definitions ........................................... 18 2732 4.1 The DS3/E3 Near End Group .................................. 19 2733 4.1.1 The DS3/E3 Configuration Table ........................... 19 2734 4.1.2 The DS3/E3 Current Table ................................. 29 2735 4.1.3 The DS3/E3 Interval Table ................................ 33 2736 4.1.4 The DS3/E3 Total ......................................... 38 2737 4.2 The DS3 Far End Group ...................................... 42 2738 4.2.1 The DS3 Far End Configuration ............................ 42 2739 4.2.2 The DS3 Far End Current .................................. 44 2740 4.2.3 The DS3 Far End Interval Table ........................... 47 2741 4.2.4 The DS3 Far End Total .................................... 49 2742 4.3 The DS3/E3 Fractional Table ................................ 52 2743 4.4 The DS3 Trap Group ......................................... 55 2744 4.5 Conformance Groups ......................................... 55 2745 5 Appendix A - Use of dsx3IfIndex and dsx3LineIndex ............ 60 2746 6 Appendix B - The delay approach to Unavialable Seconds. ..... 62 2747 7 Acknowledgments .............................................. 64 2748 8 References ................................................... 65 2749 9 Security Considerations ...................................... 67 2750 10 Author's Address ............................................ 67