idnits 2.17.1 draft-ietf-atommib-rfc2496bis-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** 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 is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 72 pages 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.) ** There are 22 instances of too long lines in the document, the longest one being 10 characters in excess of 72. == 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 document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 2899: '... It is RECOMMENDED that implementers...' RFC 2119 keyword, line 2905: '... RECOMMENDED. Instead, it is RECOMME...' -- The abstract seems to indicate that this document obsoletes RFC2496, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 305 has weird spacing: '...ifIndex dsx1D...' == Line 321 has weird spacing: '...ifIndex dsx0...' == Line 341 has weird spacing: '...ifIndex dsx1D...' == Line 357 has weird spacing: '...ifIndex dsx1...' == Line 1134 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 (April 2004) is 7309 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC3593' is defined on line 2790, but no explicit reference was found in the text == Unused Reference: 'RFC1213' is defined on line 2800, but no explicit reference was found in the text == Unused Reference: 'RFC1407' is defined on line 2805, but no explicit reference was found in the text == Unused Reference: 'RFC3592' is defined on line 2821, but no explicit reference was found in the text == Unused Reference: 'RFC2494' is defined on line 2825, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-T-M.1400' -- Obsolete informational reference (is this intentional?): RFC 1406 (ref. 'RFC1407') (Obsoleted by RFC 2495) -- Obsolete informational reference (is this intentional?): RFC 2495 (Obsoleted by RFC 3895) Summary: 7 errors (**), 0 flaws (~~), 15 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT DS3/E3 MIB April 2004 4 Definitions of Managed Objects 5 for the DS3/E3 Interface Type 7 Sun April 4 11:52:50 EDT 2004 9 draft-ietf-atommib-rfc2496bis-06.txt 11 Orly Nicklass (editor) 12 RAD Data Communications, Ltd. 13 Orly_n@rad.com 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC2026. Internet-Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its areas, 20 and its working groups. Note that other groups may also distribute 21 working documents as Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The Internet Society (2004). All Rights Reserved. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community. 42 In particular, it describes objects used for managing DS3 and E3 43 interfaces. This document is a companion to the documents that 44 define Managed Objects for the DS0, DS1/E1/DS2/E2 and Synchronous 45 Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Interface 46 Types. 48 This document obsoletes RFC 2496. 50 1. The Internet Standard Management Framework 52 For a detailed overview of the documents that describe the current 53 Internet-Standard Management Framework, please refer to section 7 of 54 RFC 3410 [RFC3410]. 56 Managed objects are accessed via a virtual information store, termed 57 the Management Information Base or MIB. MIB objects are generally 58 accessed through the Simple Network Management Protocol (SNMP). 59 Objects in the MIB are defined using the mechanisms defined in the 60 Structure of Management Information (SMI). This memo specifies a MIB 61 module that is compliant to the SMIv2, which is described in STD 58, 62 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 63 [RFC2580]. 65 1.1. Changes from RFC2496 67 The changes from RFC2496 are the following: 69 (1) The dsx3FracIfIndex SYNTAX matches the description range. 71 (2) Reference was added to Circuit Identifier object. 73 (3) Usage of ifStackTable section was updated. 75 (4) Align the DESCRIPTION clauses of few statistic objects with 76 thenear end definition, the far end definition and with 77 RFC3593. 79 (5) Add new value, dsx3M13, to dsx3LineType. 81 1.2. Changes from RFC1407 83 The changes from RFC1407 are the following: 85 (1) The Fractional Table has been deprecated. 87 (2) This document uses SMIv2. 89 (3) Values are given for ifTable and ifXTable. 91 (4) Example usage of ifStackTable is included. 93 (5) dsx3IfIndex has been deprecated. 95 (6) The definition of valid intervals has been clarified 96 for the case where the agent proxied for other devices. In 97 particular, the treatment of missing intervals has been 98 clarified. 100 (7) An inward loopback has been added. 102 (8) Additional lineStatus bits have been added for Near End 103 in Unavailable Signal State, Carrier Equipment Out of 104 Service. 106 (9) A read-write line Length object has been added. 108 (10) Added a lineStatus last change, trap and enabler. 110 (11) Textual Conventions for statistics objects have 111 been used. 113 (12) A new object, dsx3LoopbackStatus, has been introduced to 114 reflect the loopbacks established on a DS3/E3 interface and 115 the source to the requests. dsx3LoopbackConfig continues 116 to be the desired loopback state while dsx3LoopbackStatus 117 reflects the actual state. 119 (13) A dual loopback has been added to allow the setting of an 120 inward loopback and a line loopback at the same time. 122 (14) An object has been added to indicated whether or not this 123 is a channelized DS3/E3. 125 (15) A new object has been added to indicate which DS1 is to set 126 for remote loopback. 128 2. Overview 130 These objects are used when the particular media being used to 131 realize an interface is a DS3/E3 interface. At present, this applies 132 to these values of the ifType variable in the Internet-standard MIB: 134 ds3 (30) 136 The DS3 definitions contained herein are based on the DS3 137 specifications in ANSI T1.102-1987 [ANSI-T1.102], ANSI T1.107-1988 138 [ANSI-T1.107], ANSI T1.107a-1990 [ANSI-T1.107a], and ANSI T1.404-1989 139 [ANSI-T1.404]. The E3 definitions contained herein are based on the 140 E3 specifications in CCITT G.751 [CCITT-G.751]. 142 2.1. Use of ifTable for DS3 Layer 144 Only the ifGeneralInformationGroup needs to be supported. 146 ifTable Object Use for DS3 Layer 147 ====================================================================== 148 ifIndex Interface index. 150 ifDescr See interfaces MIB [RFC2863] 152 ifType ds3(30) 154 ifSpeed Speed of line rate 155 DS3 - 44736000 156 E3 - 34368000 158 ifPhysAddress The value of the Circuit Identifier. 159 If no Circuit Identifier has been assigned 160 this object should have an octet string 161 with zero length. 163 ifAdminStatus See interfaces MIB [RFC2863] 165 ifOperStatus See interfaces MIB [RFC2863] 167 ifLastChange See interfaces MIB [RFC2863] 169 ifName See interfaces MIB [RFC2863] 171 ifLinkUpDownTrapEnable Set to enabled(1). 173 ifHighSpeed Speed of line in Mega-bits per second 174 (either 45 or 34) 176 ifConnectorPresent Set to true(1) normally, except for 177 cases such as DS3/E3 over AAL1/ATM where 178 false(2) is appropriate 180 2.2. Usage Guidelines 182 2.2.1. Usage of ifStackTable 184 The object dsx3IfIndex has been deprecated. This object previously 185 allowed a very special proxy situation to exist for Routers and CSUs. 186 This section now describes how to use ifStackTable to represent this 187 relationship. 189 The paragraphs discussing dsx3IfIndex and dsx3LineIndex have been 190 preserved in Appendix A for informational purposes. 192 The ifStackTable is used in the proxy case to represent the 193 association between pairs of interfaces, e.g. this DS3 is attached to 194 that DS3. This use is consistent with the use of the ifStackTable to 195 show the association between various sub-layers of an interface. In 196 both cases entire PDUs are exchanged between the interface pairs - in 197 the case of a DS3, entire DS3 frames are exchanged; in the case of 198 PPP and HDLC, entire HDLC frames are exchanged. This usage is not 199 meant to suggest the use of the ifStackTable to represent Time 200 Division Multiplexing (TDM) connections in general. 202 External&Internal interface scenario: the SNMP Agent resides on a 203 host external from the device supporting DS3/E3 interfaces (e.g., a 204 router). The Agent represents both the host and the DS3/E3 device. 206 Example: 208 A shelf full of CSUs connected to a Router. An SNMP Agent residing on 209 the router proxies for itself and the CSU. The router has also an 210 Ethernet interface: 212 +-----+ 213 | | | 214 | | | +---------------------+ 215 |E | | 44.736 MBPS | ds3 M13 Line#A | ds3 C-bit Parity 216 |t | R |---------------+ - - - - - - - - - +------> 217 |h | | | | 218 |e | O | 44.736 MBPS | ds3 M13 Line#B | ds3 C-bit Parity 219 |r | |---------------+ - - - - - - - - - - +------> 220 |n | U | | | 221 |e | | 44.736 MBPS | ds3 M13 Line#C | ds3 C-bit Parity 222 |t | T |---------------+ - - - -- -- - - - - +------> 223 | | | | | 224 |-----| E | 44.736 MBPS | ds3 M13 Line#D | ds3 C-bit Parity 225 | | |---------------+ - - - - -- - - - - +------> 226 | | R | |_____________________| 227 | | | 228 | +-----+ 230 The assignment of the index values could for example be: 232 ifIndex Description 233 1 Ethernet 234 2 Line#A Router 235 3 Line#B Router 236 4 Line#C Router 237 5 Line#D Router 238 6 Line#A CSU Router 239 7 Line#B CSU Router 240 8 Line#C CSU Router 241 9 Line#D CSU Router 242 10 Line#A CSU Network 243 11 Line#B CSU Network 244 12 Line#C CSU Network 245 13 Line#D CSU Network 247 The ifStackTable is then used to show the relationships between the 248 various DS3 interfaces. 250 ifStackTable Entries 252 HigherLayer LowerLayer 253 2 6 254 3 7 255 4 8 256 5 9 257 6 10 258 7 11 259 8 12 260 9 13 262 If the CSU shelf is managed by itself by a local SNMP Agent, the 263 situation would be identical, except the Ethernet and the 4 router 264 interfaces are deleted. Interfaces would also be numbered from 1 to 265 8. 267 ifIndex Description 268 1 Line#A CSU Router 269 2 Line#B CSU Router 270 3 Line#C CSU Router 271 4 Line#D CSU Router 272 5 Line#A CSU Network 273 6 Line#B CSU Network 274 7 Line#C CSU Network 275 8 Line#D CSU Network 277 ifStackTable Entries 279 HigherLayer LowerLayer 280 1 5 281 2 6 282 3 7 283 4 8 285 2.2.2. Usage of Channelization for DS3, DS1, DS0 287 An example is given here to explain the channelization objects in the 288 DS3, DS1, and DS0 MIBs to help the implementor use the objects 289 correctly. Treatment of E3 and E1 would be similar, with the number 290 of DS0s being different depending on the framing of the E1. 292 Assume that a DS3 (with ifIndex 1) is Channelized into DS1s (without 293 DS2s). The object dsx3Channelization is set to enabledDs1. When 294 this object is set to enabledDS1, 28 ifEntries of type DS1 will be 295 created by the agent. If dsx3Channelization is set to disabled, then 296 the DS1s are destroyed. 298 Assume the entries in the ifTable for the DS1s are created in channel 299 order and the ifIndex values are 2 through 29. In the DS1 MIB, there 300 will be an entry in the dsx1ChanMappingTable for each ds1. The 301 entries will be as follows: 303 dsx1ChanMappingTable Entries 305 ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 306 1 1 2 307 1 2 3 308 ...... 309 1 28 29 311 In addition, the DS1s are channelized into DS0s. The object 312 dsx1Channelization is set to enabledDS0 for each DS1. There will be 313 24 DS0s in the ifTable for each DS1. Assume the entries in the 314 ifTable are created in channel order and the ifIndex values for the 315 DS0s in the first DS1 are 30 through 53. In the DS0 MIB, there will 316 be an entry in the dsx0ChanMappingTable for each DS0. The entries 317 will be as follows: 319 dsx0ChanMappingTable Entries 321 ifIndex dsx0Ds0ChannelNumber dsx0ChanMappedIfIndex 322 2 1 30 323 2 2 31 324 ...... 325 2 24 53 327 2.2.3. Usage of Channelization for DS3, DS2, DS1 329 An example is given here to explain the channelization objects in the 330 DS3 and DS1 MIBs to help the implementor use the objects correctly. 332 Assume that a DS3 (with ifIndex 1) is Channelized into DS2s. The 333 object dsx3Channelization is set to enabledDs2. There will be 7 DS2s 334 (ifType of DS1) in the ifTable. Assume the entries in the ifTable 335 for the DS2s are created in channel order and the ifIndex values are 336 2 through 8. In the DS1 MIB, there will be an entry in the 337 dsx1ChanMappingTable for each DS2. The entries will be as follows: 339 dsx1ChanMappingTable Entries 341 ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 342 1 1 2 343 1 2 3 344 ...... 345 1 7 8 347 In addition, the DS2s are channelized into DS1s. The object 348 dsx1Channelization is set to enabledDS1 for each DS2. There will be 349 4 DS1s in the ifTable for each DS2. Assume the entries in the 350 ifTable are created in channel order and the ifIndex values for the 351 DS1s in the first DS2 are 9 through 12, then 13 through 16 for the 352 second DS2, and so on. In the DS1 MIB, there will be an entry in the 353 dsx1ChanMappingTable for each DS1. The entries will be as follows: 355 dsx1ChanMappingTable Entries 357 ifIndex dsx1Ds1ChannelNumber dsx1ChanMappedIfIndex 358 2 1 9 359 2 2 10 360 2 3 11 361 2 4 12 362 3 1 13 363 3 2 14 364 ... 365 8 4 36 367 2.2.4. Usage of Loopbacks 369 This section discusses the behaviour of objects related to loopbacks. 371 The object dsx3LoopbackConfig represents the desired state of 372 loopbacks on this interface. Using this object a Manager can 373 request: 374 LineLoopback 375 PayloadLoopback (if ESF framing) 376 InwardLoopback 377 DualLoopback (Line + Inward) 378 NoLoopback 380 The remote end can also request lookbacks either through the FDL 381 channel if ESF or inband if D4. The loopbacks that can be requested 382 this way are: 383 LineLoopback 384 PayloadLoopback (if ESF framing) 385 NoLoopback 387 To model the current state of loopbacks on a DS3 interface, the 388 object dsx3LoopbackStatus defines which loopback is currently applied 389 to an interface. This object, which is a bitmap, will have bits 390 turned on which reflect the currently active loopbacks on the 391 interface as well as the source of those loopbacks. 393 The following restrictions/rules apply to loopbacks: 395 The far end cannot undo loopbacks set by a manager. 397 A manager can undo loopbacks set by the far end. 399 Both a line loopback and an inward loopback can be set at the same 400 time. Only these two loopbacks can co-exist and either one may be 401 set by the manager or the far end. A LineLoopback request from the 402 far end is incremental to an existing Inward loopback established by 403 a manager. When a NoLoopback is received from the far end in this 404 case, the InwardLoopback remains in place. 406 2.3. Objectives of this MIB Module 408 There are numerous things that could be included in a MIB for DS3/E3 409 signals: the management of multiplexors, CSUs, DSUs, and the like. 410 The intent of this document is to facilitate the common management of 411 all devices with DS3/E3 interfaces. As such, a design decision was 412 made up front to very closely align the MIB with the set of objects 413 that can generally be read from DS3/E3 devices that are currently 414 deployed. 416 2.4. DS3/E3 Terminology 418 The terminology used in this document to describe error conditions on 419 a DS3 interface as monitored by a DS3 device are based on the late 420 but not final draft of what became the ANSI T1.231 standard [ANSI- 421 T1.231]. If the definition in this document does not match the 422 definition in the ANSI T1.231 document, the implementer should follow 423 the definition described in this document. 425 2.4.1. Error Events 427 Bipolar Violation (BPV) Error Event 428 A bipolar violation error event, for B3ZS(HDB3)-coded signals, 429 is the occurrence of a pulse of the same polarity as the 430 previous pulse without being part of the zero substitution 431 code, B3ZS(HDB3). For B3ZS(HDB3)-coded signals, a bipolar 432 violation error event may also include other error patterns 433 such as: three(four) or more consecutive zeros and incorrect 434 polarity (See T1.231 section 7.1.1.1.1). 436 Excessive Zeros (EXZ) Error Event 437 An EXZ is the occurrence of any zero string length equal to or 438 greater than 3 for B3ZS, or greater than 4 for HDB3 (See 439 T1.231 section 7.1.1.1.2). 441 Line Coding Violation (LCV) Error Event 442 This parameter is a count of both BPVs and EXZs occurring over 443 the accumulation period. An EXZ increments the LCV by one 444 regardless of the length of the zero string. (Also known as 445 CV-L. See T1.231 section 7.4.1.1.) 447 P-bit Coding Violation (PCV) Error Event 448 For all DS3 applications, a coding violation error event is a 449 P-bit Parity Error event. A P-bit Parity Error event is the 450 occurrence of a received P-bit code on the DS3 M-frame that is 451 not identical to the corresponding locally- calculated code 452 (See T1.231 section 7.1.1.2.1). 454 C-bit Coding Violation (CCV) Error Event 455 For C-bit Parity and SYNTRAN DS3 applications, this is the 456 count of coding violations reported via the C-bits. For C-bit 457 Parity, it is a count of CP-bit parity errors occurring in the 458 accumulation interval. For SYNTRAN, it is a count of CRC-9 459 errors occurring in the accumulation interval (See T1.231 460 section 7.1.1.2.2). 462 2.4.2. Performance Parameters 464 All performance parameters are accumulated in fifteen minute 465 intervals and up to 96 intervals (24 hours worth) are kept by an 466 agent. Fewer than 96 intervals of data will be available if the 467 agent has been restarted within the last 24 hours. In addition, 468 there is a rolling 24-hour total of each performance parameter. 470 There is no requirement for an agent to ensure fixed relationship 471 between the start of a fifteen minute interval and any wall clock; 472 however some agents may align the fifteen minute intervals with 473 quarter hours. 475 Performance parameters are of types PerfCurrentCount, 476 PerfIntervalCount and PerfTotalCount. These textual conventions are 477 all Gauge32, and they are used because it is possible for these 478 objects to decrease. Objects may decrease when Unavailable Seconds 479 occurs across a fifteen minutes interval boundary. See Unavailable 480 Seconds discussion later in this section. 482 Line Errored Seconds (LES) 483 A Line Errored Second is a second in which one or more CV 484 occurred OR one or more LOS defects. (Also known as ES-L. See 485 T1.231 section 7.4.1.2.) 487 P-bit Errored Seconds (PES) 488 An PES is a second with one or more PCVs OR one or more Out of 489 Frame defects OR a detected incoming AIS. This gauge is not 490 incremented when UASs are counted. (Also known as ESP-P. See 491 T1.231 section 7.4.2.2.) 493 P-bit Severely Errored Seconds (PSES) 494 A PSES is a second with 44 or more PCVs OR one or more Out of 495 Frame defects OR a detected incoming AIS. This gauge is not 496 incremented when UASs are counted. (Also known as SESP-P. See 497 T1.231 section 7.4.2.5.) 499 C-bit Errored Seconds (CES) 500 An CES is a second with one or more CCVs OR one or more Out of 501 Frame defects OR a detected incoming AIS. This count is only 502 for the SYNTRAN and C-bit Parity DS3 applications. This gauge 503 is not incremented when UASs are counted. (Also known as 504 ESCP-P. See T1.231 section 7.4.2.2.) 506 C-bit Severely Errored Seconds (CSES) 507 A CSES is a second with 44 or more CCVs OR one or more Out of 508 Frame defects OR a detected incoming AIS. This count is only 509 for the SYNTRAN and C-bit Parity DS3 applications. This gauge 510 is not incremented when UASs are counted. (Also known as 511 SESCP-P. See T1.231 section 7.4.2.5.) 513 Severely Errored Framing Seconds (SEFS) 514 A SEFS is a second with one or more Out of Frame defects OR a 515 detected incoming AIS. This item is not incremented during 516 unavailable seconds. (Also known as SAS-P. See T1.231 section 517 7.4.2.6.) 519 Unavailable Seconds (UAS) 520 UAS are calculated by counting the number of seconds that the 521 interface is unavailable. The DS3 interface is said to be 522 unavailable from the onset of 10 contiguous PSESs, or the 523 onset of the condition leading to a failure (see Failure 524 States). If the condition leading to the failure was 525 immediately preceded by one or more contiguous PSESs, then the 526 DS3 interface unavailability starts from the onset of these 527 PSESs. Once unavailable, and if no failure is present, the 528 DS3 interface becomes available at the onset of 10 contiguous 529 seconds with no PSESs. Once unavailable, and if a failure is 530 present, the DS3 interface becomes available at the onset of 531 10 contiguous seconds with no PSESs, if the failure clearing 532 time is less than or equal to 10 seconds. If the failure 533 clearing time is more than 10 seconds, the DS3 interface 534 becomes available at the onset of 10 contiguous seconds with 535 no PSESs, or the onset period leading to the successful 536 clearing condition, whichever occurs later. With respect to 537 the DS3 error counts, all counters are incremented while the 538 DS3 interface is deemed available. While the interface is 539 deemed unavailable, the only count that is incremented is 540 UASs. 542 Note that this definition implies that the agent cannot 543 determine until after a ten second interval has passed whether 544 a given one-second interval belongs to available or 545 unavailable time. If the agent chooses to update the various 546 performance statistics in real time then it must be prepared 547 to retroactively reduce the PES, PSES, CES, and CSES counts by 548 10 and increase the UAS count by 10 when it determines that 549 available time has been entered. It must also be prepared to 550 adjust the PCV, CCV, and SEFS count as necessary since these 551 parameters are not accumulated during unavailable time. It 552 must be similarly prepared to retroactively decrease the UAS 553 count by 10 and increase the PES, CES, PCV, and CCV counts as 554 necessary upon entering available time. A special case exists 555 when the 10 second period leading to available or unavailable 556 time crosses a 900 second statistics window boundary, as the 557 foregoing description implies that the PCV, CCV, PES, CES, 558 PSES, CSEC, SEFS, and UAS counts for the PREVIOUS interval 559 must be adjusted. In this case successive GETs of the 560 affected dsx3IntervalPSESs and dsx3IntervalUASs objects will 561 return differing values if the first GET occurs during the 562 first few seconds of the window. 564 The agent may instead choose to delay updates to the various 565 statistics by 10 seconds in order to avoid retroactive 566 adjustments to the counters. A way to do this is sketched in 567 Appendix B. 569 In any case, a linkDown trap shall be sent only after the agent has 570 determined for certain that the unavailable state has been entered, 571 but the time on the trap will be that of the first UAS (i.e., 10 572 seconds earlier). A linkUp trap shall be handled similarly. 574 According to ANSI T1.231 unavailable time begins at the _onset_ of 10 575 contiguous severely errored seconds -- that is, unavailable time 576 starts with the _first_ of the 10 contiguous SESs. Also, while an 577 interface is deemed unavailable all counters for that interface are 578 frozen except for the UAS count. It follows that an implementation 579 which strictly complies with this standard must _not_ increment any 580 counters other than the UAS count -- even temporarily -- as a result 581 of anything that happens during those 10 seconds. Since changes in 582 the signal state lag the data to which they apply by 10 seconds, an 583 ANSI-compliant implementation must pass the the one-second statistics 584 through a 10-second delay line prior to updating any counters. That 585 can be done by performing the following steps at the end of each one 586 second interval. 588 i) Read near/far end CV counter and alarm status flags from the 589 hardware. 591 ii) Accumulate the CV counts for the preceding second and 592 compare them to the ES and SES threshold for the layer 593 in question. Update the signal state and shift the 594 one-second CV counts and ES/SES flags into the 10-element 595 delay line. Note that far-end one-second statistics are 596 to be flagged as "absent" during any second in which there 597 is an incoming defect at the layer in question or at any 598 lower layer. 600 iii) Update the current interval statistics using the signal 601 state from the _previous_ update cycle and the one-second 602 CV counts and ES/SES flags shifted out of the 10-element 603 delay line. 605 This approach is further described in Appendix B. 607 2.4.3. Performance Defects 609 Failure States: 610 The Remote Alarm Indication (RAI) failure, in SYNTRAN 611 applications, is declared after detecting the Yellow Alarm 612 Signal on the alarm channel. See ANSI T1.107a-1990 [ANSI- 613 T1.107a]. The Remote Alarm Indication failure, in C-bit Parity 614 DS3 applications, is declared as soon as the presence of 615 either one or two alarm signals are detected on the Far End 616 Alarm Channel. See [ANSI-T1.107]. The Remote Alarm 617 Indication failure may also be declared after detecting the 618 far-end SEF/AIS defect (aka yellow). The Remote Alarm 619 Indication failure is cleared as soon as the presence of the 620 any of the above alarms are removed. 622 Also, the incoming failure state is declared when a defect 623 persists for at least 2-10 seconds. The defects are the 624 following: Loss of Signal (LOS), an Out of Frame (OOF) or an 625 incoming Alarm Indication Signal (AIS). The Failure State is 626 cleared when the defect is absent for less than or equal to 20 627 seconds. 629 Far End SEF/AIS defect (aka yellow) 630 A Far End SEF/AIS defect is the occurrence of the two X-bits 631 in a M-frame set to zero. The Far End SEF/AIS defect is 632 terminated when the two X-bits in a M-frame are set to one. 633 (Also known as SASCP-PFE. See T1.231 section 7.4.4.2.6) 635 Out of Frame (OOF) defect 636 A DS3 OOF defect is detected when any three or more errors in 637 sixteen or fewer consecutive F-bits occur within a DS3 M- 638 frame. An OOF defect may also be called a Severely Errored 639 Frame (SEF) defect. An OOF defect is cleared when reframe 640 occurs. A DS3 Loss of Frame (LOF) failure is declared when 641 the DS3 OOF defect is consistent for 2 to 10 seconds. The DS3 642 OOF defect ends when reframe occurs. The DS3 LOF failure is 643 cleared when the DS3 OOF defect is absent for 10 to 20 644 seconds. (See T1.231 section 7.1.2.2.1) 646 An E3 OOF defect is detected when four consecutive frame 647 alignment signals have been incorrectly received in there 648 predicted positions in an E3 signal. E3 frame alignment occurs 649 when the presence of three consecutive frame alignment signals 650 have been detected. 652 Loss of Signal (LOS) 653 defect 654 The DS3 LOS defect is declared upon observing 175 +/- 75 655 contiguous pulse positions with no pulses of either positive 656 or negative polarity. The DS3 LOS defect is terminated upon 657 observing an average pulse density of at least 33% over a 658 period of 175 +/- 75 contiguous pulse positions starting with 659 the receipt of a pulse. (See T1.231 section 7.1.2.1.1) 661 Alarm Indication Signal (AIS) defect 662 The DS3 AIS is framed with "stuck stuffing." This implies 663 that it has a valid M-subframe alignments bits, M-frame 664 alignment bits, and P bits. The information bits are set to a 665 1010... sequence, starting with a one (1) after each M- 666 subframe alignment bit, M-frame alignment bit, X bit, P bit, 667 and C bit. The C bits are all set to zero giving what is 668 called "stuck stuffing." The X bits are set to one. The DS3 669 AIS defect is declared after DS3 AIS is present in contiguous 670 M-frames for a time equal to or greater than T, where 0.2 ms 671 <= T <= 100 ms. The DS3 AIS defect is terminated after AIS is 672 absent in contiguous M-frames for a time equal to or greater 673 than T. (See T1.231 section 7.1.2.2.3) 675 The E3 binary content of the AIS is nominally a continuous 676 stream of ones. AIS detection and the application of 677 consequent actions, should be completed within a time limit of 678 1 ms. 680 2.4.4. Other Terms 682 Circuit Identifier 683 This is a character string specified by the circuit 684 vendor, and is useful when communicating with the vendor 685 during the troubleshooting process (see M.1400 [ITU-T-M.1400] for 686 additional information). 688 Proxy 689 In this document, the word proxy is meant to indicate an 690 application which receives SNMP messages and replies to them on 691 behalf of the devices which implement the actual DS3/E3 692 interfaces. The proxy may have already collected the information 693 about the DS3/E3 interfaces into its local database and may not 694 necessarily forward the requests to the actual DS3/E3 interface. 695 It is expected in such an application that there are periods of 696 time where the proxy is not communicating with the DS3/E3 697 interfaces. In these instances the proxy will not necessarily 698 have up-to-date configuration information and will most likely 699 have missed the collection of some statistics data. Missed 700 statistics data collection will result in invalid data in the 701 interval table. 703 3. Object Definitions 705 DS3-MIB DEFINITIONS ::= BEGIN 707 IMPORTS 708 MODULE-IDENTITY, OBJECT-TYPE, 709 NOTIFICATION-TYPE, transmission FROM SNMPv2-SMI 710 DisplayString, TimeStamp, TruthValue FROM SNMPv2-TC 711 MODULE-COMPLIANCE, OBJECT-GROUP, 712 NOTIFICATION-GROUP FROM SNMPv2-CONF 713 InterfaceIndex FROM IF-MIB 714 PerfCurrentCount, PerfIntervalCount, 715 PerfTotalCount FROM PerfHist-TC-MIB; 717 ds3 MODULE-IDENTITY 718 LAST-UPDATED "200404040000Z" 719 ORGANIZATION "IETF AToM MIB Working Group" 720 CONTACT-INFO 721 "WG charter: 722 http://www.ietf.org/html.charters/atommib-charter.html 724 Mailing Lists: 725 General Discussion: atommib@research.telcordia.com 726 To Subscribe: atommib-request@research.telcordia.com 728 Editor: Orly Nicklass 730 Postal: RAD Data Communications, Ltd. 731 Ziv Tower, 24 Roul Walenberg 732 Tel Aviv, Israel, 69719 734 Tel: +9723 765 9969 735 E-mail: orly_n@rad.com" 737 DESCRIPTION 738 "The is the MIB module that describes 739 DS3 and E3 interfaces objects. 741 Copyright (c) The Internet Society (2003). This 742 version of this MIB module is part of RFC yyyy; 743 see the RFC itself for full legal notices." 744 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 746 REVISION "200404040000Z" 747 DESCRIPTION 748 "The RFC yyyy version of this MIB module. 749 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 750 The key changes made to this MIB module 751 since its publication in RFC 2496 are as follows: 753 (1) The dsx3FracIfIndex SYNTAX matches the description range. 755 (2) Reference was added to Circuit Identifier object. 757 (3) Usage of ifStackTable section was updated. 759 (4) Align the DESCRIPTION clauses of few statistic objects with 760 thenear end definition, the far end definition and with 761 RFC3593. 763 (5) Add new value, dsx3M13, to dsx3LineType." 765 REVISION "199808012130Z" 766 DESCRIPTION 767 "The RFC 2496 version of this MIB module. 768 The key changes made to this MIB module 769 since its publication in RFC 1407 are as follows: 771 (1) The Fractional Table has been deprecated. 773 (2) This document uses SMIv2. 775 (3) Values are given for ifTable and ifXTable. 777 (4) Example usage of ifStackTable is included. 779 (5) dsx3IfIndex has been deprecated. 781 (6) The definition of valid intervals has been clarified 782 for the case where the agent proxied for other devices. In 783 particular, the treatment of missing intervals has been 784 clarified. 786 (7) An inward loopback has been added. 788 (8) Additional lineStatus bits have been added for Near End 789 in Unavailable Signal State, Carrier Equipment Out of 790 Service. 792 (9) A read-write line Length object has been added. 794 (10) Added a lineStatus last change, trap and enabler. 796 (11) Textual Conventions for statistics objects have 797 been used. 799 (12) A new object, dsx3LoopbackStatus, has been introduced to 800 reflect the loopbacks established on a DS3/E3 interface and 801 the source to the requests. dsx3LoopbackConfig continues 802 to be the desired loopback state while dsx3LoopbackStatus 803 reflects the actual state. 805 (13) A dual loopback has been added to allow the setting of an 806 inward loopback and a line loopback at the same time. 808 (14) An object has been added to indicated whether or not this 809 is a channelized DS3/E3. 811 (15) A new object has been added to indicate which DS1 is to set 812 for remote loopback." 814 REVISION "199301252028Z" 815 DESCRIPTION 816 "Initial version, published as RFC 1407." 818 ::= { transmission 30 } 820 -- The DS3/E3 Near End Group 822 -- The DS3/E3 Near End Group consists of four tables: 823 -- DS3/E3 Configuration 824 -- DS3/E3 Current 825 -- DS3/E3 Interval 826 -- DS3/E3 Total 828 -- the DS3/E3 Configuration Table 830 dsx3ConfigTable OBJECT-TYPE 831 SYNTAX SEQUENCE OF Dsx3ConfigEntry 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "The DS3/E3 Configuration table." 836 ::= { ds3 5 } 838 dsx3ConfigEntry OBJECT-TYPE 839 SYNTAX Dsx3ConfigEntry 840 MAX-ACCESS not-accessible 841 STATUS current 842 DESCRIPTION 843 "An entry in the DS3/E3 Configuration table." 844 INDEX { dsx3LineIndex } 845 ::= { dsx3ConfigTable 1 } 847 Dsx3ConfigEntry ::= 848 SEQUENCE { 849 dsx3LineIndex InterfaceIndex, 850 dsx3IfIndex InterfaceIndex, 851 dsx3TimeElapsed INTEGER, 852 dsx3ValidIntervals INTEGER, 853 dsx3LineType INTEGER, 854 dsx3LineCoding INTEGER, 855 dsx3SendCode INTEGER, 856 dsx3CircuitIdentifier DisplayString, 857 dsx3LoopbackConfig INTEGER, 858 dsx3LineStatus INTEGER, 859 dsx3TransmitClockSource INTEGER, 860 dsx3InvalidIntervals INTEGER, 861 dsx3LineLength INTEGER, 862 dsx3LineStatusLastChange TimeStamp, 863 dsx3LineStatusChangeTrapEnable INTEGER, 864 dsx3LoopbackStatus INTEGER, 865 dsx3Channelization INTEGER, 866 dsx3Ds1ForRemoteLoop INTEGER 868 } 870 dsx3LineIndex OBJECT-TYPE 871 SYNTAX InterfaceIndex 872 MAX-ACCESS read-only -- read-only since originally an 873 -- SMIv1 index 875 STATUS current 876 DESCRIPTION 877 "This object should be made equal to ifIndex. The 878 next paragraph describes its previous usage. 879 Making the object equal to ifIndex allows propoer 880 use of ifStackTable. 882 Previously, this object was the identifier of a 883 DS3/E3 Interface on a managed device. If there is 884 an ifEntry that is directly associated with this 885 and only this DS3/E3 interface, it should have the 886 same value as ifIndex. Otherwise, number the 887 dsx3LineIndices with an unique identifier 888 following the rules of choosing a number that is 889 greater than ifNumber and numbering the inside 890 interfaces (e.g., equipment side) with even 891 numbers and outside interfaces (e.g, network side) 892 with odd numbers." 893 ::= { dsx3ConfigEntry 1 } 895 dsx3IfIndex OBJECT-TYPE 896 SYNTAX InterfaceIndex 897 MAX-ACCESS read-only 898 STATUS deprecated 899 DESCRIPTION 900 "This value for this object is equal to the value 901 of ifIndex from the Interfaces table of MIB II 902 (RFC 1213)." 903 ::= { dsx3ConfigEntry 2 } 905 dsx3TimeElapsed OBJECT-TYPE 906 SYNTAX INTEGER (0..899) 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "The number of seconds that have elapsed since the 911 beginning of the near end current error- 912 measurement period. If, for some reason, such as 913 an adjustment in the system's time-of-day clock, 914 the current interval exceeds the maximum value, 915 the agent will return the maximum value." 916 ::= { dsx3ConfigEntry 3 } 918 dsx3ValidIntervals OBJECT-TYPE 919 SYNTAX INTEGER (0..96) 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "The number of previous near end intervals for 924 which data was collected. The value will be 96 925 unless the interface was brought online within the 926 last 24 hours, in which case the value will be the 927 number of complete 15 minute near end intervals 928 since the interface has been online. In the case 929 where the agent is a proxy, it is possible that 930 some intervals are unavailable. In this case, 931 this interval is the maximum interval number for 932 which data is available." 933 ::= { dsx3ConfigEntry 4 } 935 dsx3LineType OBJECT-TYPE 936 SYNTAX INTEGER { 937 dsx3other(1), 938 dsx3M23(2), 939 dsx3SYNTRAN(3), 940 dsx3CbitParity(4), 941 dsx3ClearChannel(5), 942 e3other(6), 943 e3Framed(7), 944 e3Plcp(8), 945 dsx3M13(9) 946 } 947 MAX-ACCESS read-write 948 STATUS current 949 DESCRIPTION 950 "This variable indicates the variety of DS3 C-bit 951 or E3 application implementing this interface. The 952 type of interface affects the interpretation of 953 the usage and error statistics. The rate of DS3 954 is 44.736 Mbps and E3 is 34.368 Mbps. The 955 dsx3ClearChannel value means that the C-bits are 956 not used except for sending/receiving AIS. The 957 values, in sequence, describe: 959 TITLE: SPECIFICATION: 960 dsx3M23 ANSI T1.107-1988 961 dsx3SYNTRAN ANSI T1.107-1988 962 dsx3CbitParity ANSI T1.107a-1990 963 dsx3ClearChannel ANSI T1.102-1987 964 e3Framed CCITT G.751 965 e3Plcp ETSI T/NA(91)18 966 dsx3M13 ANSI T1.107a-1990." 968 REFERENCE 969 "American National Standard for telecommunications 970 - digital hierarchy - 971 formats specification, ANSI T1.107- 1988. 972 ANSI T1.107a-1990. 973 American National Standard for telecommunications 974 - digital hierarchy - 975 electrical interfaces, ANSI T1.102- 1987. 976 CCITT - Digital Multiplex Equipment Operating at 977 the Third Order Bit Rate of 34 368 Kbit/s and 978 the Forth Order Bit Rate of 139 264 Kbit/s 979 and Using Positive Justification, G.751 980 European Telecommunications Standards Institute 981 -- ETS '34M' -- 982 Metropolitan Area Network Physical 983 Convergence Layer Procedure for 984 34.368 Megabits per Second, T/NA(91)18, 985 May 1991." 986 ::= { dsx3ConfigEntry 5 } 988 dsx3LineCoding OBJECT-TYPE 989 SYNTAX INTEGER { 990 dsx3Other(1), 991 dsx3B3ZS(2), 992 e3HDB3(3) 993 } 994 MAX-ACCESS read-write 995 STATUS current 996 DESCRIPTION 997 "This variable describes the variety of Zero Code 998 Suppression used on this interface, which in turn 999 affects a number of its characteristics. 1001 dsx3B3ZS and e3HDB3 refer to the use of specified 1002 patterns of normal bits and bipolar violations 1003 which are used to replace sequences of zero bits 1004 of a specified length." 1005 ::= { dsx3ConfigEntry 6 } 1007 dsx3SendCode OBJECT-TYPE 1008 SYNTAX INTEGER { 1009 dsx3SendNoCode(1), 1010 dsx3SendLineCode(2), 1011 dsx3SendPayloadCode(3), 1012 dsx3SendResetCode(4), 1013 dsx3SendDS1LoopCode(5), 1014 dsx3SendTestPattern(6) 1015 } 1016 MAX-ACCESS read-write 1017 STATUS current 1018 DESCRIPTION 1019 "This variable indicates what type of code is 1020 being sent across the DS3/E3 interface by the 1021 device. (These are optional for E3 interfaces.) 1022 Setting this variable causes the interface to 1023 begin sending the code requested. 1024 The values mean: 1026 dsx3SendNoCode 1027 sending looped or normal data 1029 dsx3SendLineCode 1030 sending a request for a line loopback 1032 dsx3SendPayloadCode 1033 sending a request for a payload loopback 1034 (i.e., all DS1/E1s in a DS3/E3 frame) 1036 dsx3SendResetCode 1037 sending a loopback deactivation request 1039 dsx3SendDS1LoopCode 1040 requesting to loopback a particular DS1/E1 1041 within a DS3/E3 frame. The DS1/E1 is 1042 indicated in dsx3Ds1ForRemoteLoop. 1044 dsx3SendTestPattern 1045 sending a test pattern." 1047 ::= { dsx3ConfigEntry 7 } 1049 dsx3CircuitIdentifier OBJECT-TYPE 1050 SYNTAX DisplayString (SIZE (0..255)) 1051 MAX-ACCESS read-write 1052 STATUS current 1053 DESCRIPTION 1054 "This variable contains the transmission vendor's 1055 circuit identifier, for the purpose of 1056 facilitating troubleshooting." 1057 REFERENCE "ITU-T M.1400" 1058 ::= { dsx3ConfigEntry 8 } 1060 dsx3LoopbackConfig OBJECT-TYPE 1061 SYNTAX INTEGER { 1062 dsx3NoLoop(1), 1063 dsx3PayloadLoop(2), 1064 dsx3LineLoop(3), 1065 dsx3OtherLoop(4), 1066 dsx3InwardLoop(5), 1067 dsx3DualLoop(6) 1068 } 1069 MAX-ACCESS read-write 1070 STATUS current 1071 DESCRIPTION 1072 "This variable represents the desired loopback 1073 configuration of the DS3/E3 interface. 1074 The values mean: 1076 dsx3NoLoop 1077 Not in the loopback state. A device that is 1078 not capable of performing a loopback on 1079 the interface shall always return this as 1080 its value. 1082 dsx3PayloadLoop 1083 The received signal at this interface is looped 1084 through the device. Typically the received signal 1085 is looped back for retransmission after it has 1086 passed through the device's framing function. 1088 dsx3LineLoop 1089 The received signal at this interface does not 1090 go through the device (minimum penetration) but 1091 is looped back out. 1093 dsx3OtherLoop 1094 Loopbacks that are not defined here. 1096 dsx3InwardLoop 1097 The sent signal at this interface is looped back 1098 through the device. 1100 dsx3DualLoop 1101 Both dsx1LineLoop and dsx1InwardLoop will be 1102 active simultaneously." 1103 ::= { dsx3ConfigEntry 9 } 1105 dsx3LineStatus OBJECT-TYPE 1106 SYNTAX INTEGER (1..4095) 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "This variable indicates the Line Status of the 1111 interface. It contains loopback state information 1112 and failure state information. The dsx3LineStatus 1113 is a bit map represented as a sum, therefore, it 1114 can represent multiple failures and a loopback 1115 (see dsx3LoopbackConfig object for the type of 1116 loopback) simultaneously. The dsx3NoAlarm must be 1117 set if and only if no other flag is set. 1119 If the dsx3loopbackState bit is set, the loopback 1120 in effect can be determined from the 1121 dsx3loopbackConfig object. 1122 The various bit positions are: 1123 1 dsx3NoAlarm No alarm present 1124 2 dsx3RcvRAIFailure Receiving Yellow/Remote 1125 Alarm Indication 1126 4 dsx3XmitRAIAlarm Transmitting Yellow/Remote 1127 Alarm Indication 1128 8 dsx3RcvAIS Receiving AIS failure state 1129 16 dsx3XmitAIS Transmitting AIS 1130 32 dsx3LOF Receiving LOF failure state 1131 64 dsx3LOS Receiving LOS failure state 1132 128 dsx3LoopbackState Looping the received signal 1133 256 dsx3RcvTestCode Receiving a Test Pattern 1134 512 dsx3OtherFailure any line status not defined 1135 here 1136 1024 dsx3UnavailSigState Near End in Unavailable Signal 1137 State 1139 2048 dsx3NetEquipOOS Carrier Equipment Out of Service" 1140 ::= { dsx3ConfigEntry 10 } 1142 dsx3TransmitClockSource OBJECT-TYPE 1143 SYNTAX INTEGER { 1144 loopTiming(1), 1145 localTiming(2), 1146 throughTiming(3) 1147 } 1148 MAX-ACCESS read-write 1149 STATUS current 1150 DESCRIPTION 1151 "The source of Transmit Clock. 1153 loopTiming indicates that the recovered receive 1154 clock is used as the transmit clock. 1156 localTiming indicates that a local clock source is 1157 used or that an external clock is attached to the 1158 box containing the interface. 1160 throughTiming indicates that transmit clock is 1161 derived from the recovered receive clock of 1162 another DS3 interface." 1163 ::= { dsx3ConfigEntry 11 } 1165 dsx3InvalidIntervals OBJECT-TYPE 1166 SYNTAX INTEGER (0..96) 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 " The number of intervals in the range from 0 to 1171 dsx3ValidIntervals for which no data is available. 1172 This object will typically be zero except in cases 1173 where the data for some intervals are not 1174 available (e.g., in proxy situations)." 1175 ::= { dsx3ConfigEntry 12 } 1177 dsx3LineLength OBJECT-TYPE 1178 SYNTAX INTEGER (0..64000) 1179 UNITS "meters" 1180 MAX-ACCESS read-write 1181 STATUS current 1182 DESCRIPTION 1183 "The length of the ds3 line in meters. This 1184 object provides information for line build out 1185 circuitry if it exists and can use this object to 1186 adjust the line build out." 1187 ::= { dsx3ConfigEntry 13 } 1189 dsx3LineStatusLastChange OBJECT-TYPE 1190 SYNTAX TimeStamp 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "The value of MIB II's sysUpTime object at the 1195 time this DS3/E3 entered its current line status 1196 state. If the current state was entered prior to 1197 the last re-initialization of the proxy-agent, 1198 then this object contains a zero value." 1199 ::= { dsx3ConfigEntry 14 } 1201 dsx3LineStatusChangeTrapEnable OBJECT-TYPE 1202 SYNTAX INTEGER { 1203 enabled(1), 1204 disabled(2) 1205 } 1206 MAX-ACCESS read-write 1207 STATUS current 1208 DESCRIPTION 1209 "Indicates whether dsx3LineStatusChange traps 1210 should be generated for this interface." 1211 DEFVAL { disabled } 1212 ::= { dsx3ConfigEntry 15 } 1214 dsx3LoopbackStatus OBJECT-TYPE 1215 SYNTAX INTEGER (1..127) 1216 MAX-ACCESS read-only 1217 STATUS current 1218 DESCRIPTION 1219 "This variable represents the current state of the 1220 loopback on the DS3 interface. It contains 1221 information about loopbacks established by a 1222 manager and remotely from the far end. 1224 The dsx3LoopbackStatus is a bit map represented as 1225 a sum, therefore is can represent multiple 1226 loopbacks simultaneously. 1228 The various bit positions are: 1230 1 dsx3NoLoopback 1231 2 dsx3NearEndPayloadLoopback 1232 4 dsx3NearEndLineLoopback 1233 8 dsx3NearEndOtherLoopback 1234 16 dsx3NearEndInwardLoopback 1235 32 dsx3FarEndPayloadLoopback 1236 64 dsx3FarEndLineLoopback" 1238 ::= { dsx3ConfigEntry 16 } 1240 dsx3Channelization OBJECT-TYPE 1241 SYNTAX INTEGER { 1242 disabled(1), 1243 enabledDs1(2), 1244 enabledDs2(3) 1245 } 1246 MAX-ACCESS read-write 1247 STATUS current 1248 DESCRIPTION 1249 "Indicates whether this ds3/e3 is channelized or 1250 unchannelized. The value of enabledDs1 indicates 1251 that this is a DS3 channelized into DS1s. The 1252 value of enabledDs3 indicated that this is a DS3 1253 channelized into DS2s. Setting this object will 1254 cause the creation or deletion of DS2 or DS1 1255 entries in the ifTable. " 1256 ::= { dsx3ConfigEntry 17 } 1258 dsx3Ds1ForRemoteLoop OBJECT-TYPE 1259 SYNTAX INTEGER (0..29) 1260 MAX-ACCESS read-write 1261 STATUS current 1262 DESCRIPTION 1263 "Indicates which DS1/E1 on this DS3/E3 will be 1264 indicated in the remote ds1 loopback request. A 1265 value of 0 means no DS1 will be looped. A value 1266 of 29 means all DS1s/E1s will be looped." 1267 ::= { dsx3ConfigEntry 18 } 1269 -- the DS3/E3 Current Table 1271 dsx3CurrentTable OBJECT-TYPE 1272 SYNTAX SEQUENCE OF Dsx3CurrentEntry 1273 MAX-ACCESS not-accessible 1274 STATUS current 1275 DESCRIPTION 1276 "The DS3/E3 current table contains various 1277 statistics being collected for the current 15 1278 minute interval." 1279 ::= { ds3 6 } 1281 dsx3CurrentEntry OBJECT-TYPE 1282 SYNTAX Dsx3CurrentEntry 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 "An entry in the DS3/E3 Current table." 1287 INDEX { dsx3CurrentIndex } 1288 ::= { dsx3CurrentTable 1 } 1290 Dsx3CurrentEntry ::= 1291 SEQUENCE { 1292 dsx3CurrentIndex InterfaceIndex, 1293 dsx3CurrentPESs PerfCurrentCount, 1294 dsx3CurrentPSESs PerfCurrentCount, 1295 dsx3CurrentSEFSs PerfCurrentCount, 1296 dsx3CurrentUASs PerfCurrentCount, 1297 dsx3CurrentLCVs PerfCurrentCount, 1298 dsx3CurrentPCVs PerfCurrentCount, 1299 dsx3CurrentLESs PerfCurrentCount, 1300 dsx3CurrentCCVs PerfCurrentCount, 1301 dsx3CurrentCESs PerfCurrentCount, 1302 dsx3CurrentCSESs PerfCurrentCount 1303 } 1305 dsx3CurrentIndex OBJECT-TYPE 1306 SYNTAX InterfaceIndex 1307 MAX-ACCESS read-only -- read-only since originally an 1308 -- SMIv1 index 1309 STATUS current 1310 DESCRIPTION 1311 "The index value which uniquely identifies the 1312 DS3/E3 interface to which this entry is 1313 applicable. The interface identified by a 1314 particular value of this index is the same 1315 interface as identified by the same value an 1316 dsx3LineIndex object instance." 1317 ::= { dsx3CurrentEntry 1 } 1319 dsx3CurrentPESs OBJECT-TYPE 1320 SYNTAX PerfCurrentCount 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "The counter associated with the number of P-bit 1325 Errored Seconds." 1326 ::= { dsx3CurrentEntry 2 } 1328 dsx3CurrentPSESs OBJECT-TYPE 1329 SYNTAX PerfCurrentCount 1330 MAX-ACCESS read-only 1331 STATUS current 1332 DESCRIPTION 1333 "The counter associated with the number of P-bit 1334 Severely Errored Seconds." 1335 ::= { dsx3CurrentEntry 3 } 1337 dsx3CurrentSEFSs OBJECT-TYPE 1338 SYNTAX PerfCurrentCount 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "The counter associated with the number of 1343 Severely Errored Framing Seconds." 1344 ::= { dsx3CurrentEntry 4 } 1346 dsx3CurrentUASs OBJECT-TYPE 1347 SYNTAX PerfCurrentCount 1348 MAX-ACCESS read-only 1349 STATUS current 1350 DESCRIPTION 1351 "The counter associated with the number of 1352 Unavailable Seconds." 1353 ::= { dsx3CurrentEntry 5 } 1355 dsx3CurrentLCVs OBJECT-TYPE 1356 SYNTAX PerfCurrentCount 1357 MAX-ACCESS read-only 1358 STATUS current 1359 DESCRIPTION 1360 "The counter associated with the number of Line 1361 Coding Violations." 1362 ::= { dsx3CurrentEntry 6 } 1364 dsx3CurrentPCVs OBJECT-TYPE 1365 SYNTAX PerfCurrentCount 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "The counter associated with the number of P-bit 1370 Coding Violations." 1371 ::= { dsx3CurrentEntry 7 } 1373 dsx3CurrentLESs OBJECT-TYPE 1374 SYNTAX PerfCurrentCount 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "The number of Line Errored Seconds." 1379 ::= { dsx3CurrentEntry 8 } 1381 dsx3CurrentCCVs OBJECT-TYPE 1382 SYNTAX PerfCurrentCount 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "The number of C-bit Coding Violations." 1387 ::= { dsx3CurrentEntry 9 } 1389 dsx3CurrentCESs OBJECT-TYPE 1390 SYNTAX PerfCurrentCount 1391 MAX-ACCESS read-only 1392 STATUS current 1393 DESCRIPTION 1394 "The number of C-bit Errored Seconds." 1395 ::= { dsx3CurrentEntry 10 } 1397 dsx3CurrentCSESs OBJECT-TYPE 1398 SYNTAX PerfCurrentCount 1399 MAX-ACCESS read-only 1400 STATUS current 1401 DESCRIPTION 1402 "The number of C-bit Severely Errored Seconds." 1404 ::= { dsx3CurrentEntry 11 } 1406 -- the DS3/E3 Interval Table 1408 dsx3IntervalTable OBJECT-TYPE 1409 SYNTAX SEQUENCE OF Dsx3IntervalEntry 1410 MAX-ACCESS not-accessible 1411 STATUS current 1412 DESCRIPTION 1413 "The DS3/E3 Interval Table contains various 1414 statistics collected by each DS3/E3 Interface over 1415 the previous 24 hours of operation. The past 24 1416 hours are broken into 96 completed 15 minute 1417 intervals. Each row in this table represents one 1418 such interval (identified by dsx3IntervalNumber) 1419 and for one specific interface (identifed by 1420 dsx3IntervalIndex)." 1422 ::= { ds3 7 } 1424 dsx3IntervalEntry OBJECT-TYPE 1425 SYNTAX Dsx3IntervalEntry 1426 MAX-ACCESS not-accessible 1427 STATUS current 1428 DESCRIPTION 1429 "An entry in the DS3/E3 Interval table." 1430 INDEX { dsx3IntervalIndex, dsx3IntervalNumber } 1431 ::= { dsx3IntervalTable 1 } 1433 Dsx3IntervalEntry ::= 1434 SEQUENCE { 1435 dsx3IntervalIndex InterfaceIndex, 1436 dsx3IntervalNumber INTEGER, 1437 dsx3IntervalPESs PerfIntervalCount, 1438 dsx3IntervalPSESs PerfIntervalCount, 1439 dsx3IntervalSEFSs PerfIntervalCount, 1440 dsx3IntervalUASs PerfIntervalCount, 1441 dsx3IntervalLCVs PerfIntervalCount, 1442 dsx3IntervalPCVs PerfIntervalCount, 1443 dsx3IntervalLESs PerfIntervalCount, 1444 dsx3IntervalCCVs PerfIntervalCount, 1445 dsx3IntervalCESs PerfIntervalCount, 1446 dsx3IntervalCSESs PerfIntervalCount, 1447 dsx3IntervalValidData TruthValue 1448 } 1450 dsx3IntervalIndex OBJECT-TYPE 1451 SYNTAX InterfaceIndex 1452 MAX-ACCESS read-only -- read-only since originally an 1453 -- SMIv1 index 1454 STATUS current 1455 DESCRIPTION 1456 "The index value which uniquely identifies the 1457 DS3/E3 interface to which this entry is 1458 applicable. The interface identified by a 1459 particular value of this index is the same 1460 interface as identified by the same value an 1461 dsx3LineIndex object instance." 1462 ::= { dsx3IntervalEntry 1 } 1464 dsx3IntervalNumber OBJECT-TYPE 1465 SYNTAX INTEGER (1..96) 1466 MAX-ACCESS read-only -- read-only since originally an 1467 -- SMIv1 index 1468 STATUS current 1469 DESCRIPTION 1470 "A number between 1 and 96, where 1 is the most 1471 recently completed 15 minute interval and 96 is 1472 the 15 minutes interval completed 23 hours and 45 1473 minutes prior to interval 1." 1474 ::= { dsx3IntervalEntry 2 } 1476 dsx3IntervalPESs OBJECT-TYPE 1477 SYNTAX PerfIntervalCount 1478 MAX-ACCESS read-only 1479 STATUS current 1480 DESCRIPTION 1481 "The counter associated with the number of P-bit 1482 Errored Seconds." 1483 ::= { dsx3IntervalEntry 3 } 1485 dsx3IntervalPSESs OBJECT-TYPE 1486 SYNTAX PerfIntervalCount 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "The counter associated with the number of P-bit 1491 Severely Errored Seconds." 1492 ::= { dsx3IntervalEntry 4 } 1494 dsx3IntervalSEFSs OBJECT-TYPE 1495 SYNTAX PerfIntervalCount 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "The counter associated with the number of 1500 Severely Errored Framing Seconds." 1501 ::= { dsx3IntervalEntry 5 } 1503 dsx3IntervalUASs OBJECT-TYPE 1504 SYNTAX PerfIntervalCount 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "The counter associated with the number of 1509 Unavailable Seconds. This object may decrease if 1510 the occurance of unavailable seconds occurs across 1511 an inteval boundary." 1512 ::= { dsx3IntervalEntry 6 } 1514 dsx3IntervalLCVs OBJECT-TYPE 1515 SYNTAX PerfIntervalCount 1516 MAX-ACCESS read-only 1517 STATUS current 1518 DESCRIPTION 1519 "The counter associated with the number of Line 1520 Coding Violations." 1521 ::= { dsx3IntervalEntry 7 } 1523 dsx3IntervalPCVs OBJECT-TYPE 1524 SYNTAX PerfIntervalCount 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "The counter associated with the number of P-bit 1529 Coding Violations." 1530 ::= { dsx3IntervalEntry 8 } 1532 dsx3IntervalLESs OBJECT-TYPE 1533 SYNTAX PerfIntervalCount 1534 MAX-ACCESS read-only 1535 STATUS current 1536 DESCRIPTION 1537 "The number of Line Errored Seconds (BPVs or 1538 illegal zero sequences)." 1539 ::= { dsx3IntervalEntry 9 } 1541 dsx3IntervalCCVs OBJECT-TYPE 1542 SYNTAX PerfIntervalCount 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "The number of C-bit Coding Violations." 1547 ::= { dsx3IntervalEntry 10 } 1549 dsx3IntervalCESs OBJECT-TYPE 1550 SYNTAX PerfIntervalCount 1551 MAX-ACCESS read-only 1552 STATUS current 1553 DESCRIPTION 1554 "The number of C-bit Errored Seconds." 1555 ::= { dsx3IntervalEntry 11 } 1557 dsx3IntervalCSESs OBJECT-TYPE 1558 SYNTAX PerfIntervalCount 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "The number of C-bit Severely Errored Seconds." 1563 ::= { dsx3IntervalEntry 12 } 1565 dsx3IntervalValidData OBJECT-TYPE 1566 SYNTAX TruthValue 1567 MAX-ACCESS read-only 1568 STATUS current 1569 DESCRIPTION 1570 " This variable indicates if the data for this 1571 interval is valid." 1572 ::= { dsx3IntervalEntry 13 } 1574 -- the DS3/E3 Total 1576 dsx3TotalTable OBJECT-TYPE 1577 SYNTAX SEQUENCE OF Dsx3TotalEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "The DS3/E3 Total Table contains the cumulative 1582 sum of the various statistics for the 24 hour 1583 period preceding the current interval." 1584 ::= { ds3 8 } 1586 dsx3TotalEntry OBJECT-TYPE 1587 SYNTAX Dsx3TotalEntry 1588 MAX-ACCESS not-accessible 1589 STATUS current 1590 DESCRIPTION 1591 "An entry in the DS3/E3 Total table." 1592 INDEX { dsx3TotalIndex } 1593 ::= { dsx3TotalTable 1 } 1595 Dsx3TotalEntry ::= 1596 SEQUENCE { 1597 dsx3TotalIndex InterfaceIndex, 1598 dsx3TotalPESs PerfTotalCount, 1599 dsx3TotalPSESs PerfTotalCount, 1600 dsx3TotalSEFSs PerfTotalCount, 1601 dsx3TotalUASs PerfTotalCount, 1602 dsx3TotalLCVs PerfTotalCount, 1603 dsx3TotalPCVs PerfTotalCount, 1604 dsx3TotalLESs PerfTotalCount, 1605 dsx3TotalCCVs PerfTotalCount, 1606 dsx3TotalCESs PerfTotalCount, 1607 dsx3TotalCSESs PerfTotalCount 1608 } 1610 dsx3TotalIndex OBJECT-TYPE 1611 SYNTAX InterfaceIndex 1612 MAX-ACCESS read-only -- read-only since originally an 1613 -- SMIv1 index 1614 STATUS current 1615 DESCRIPTION 1616 "The index value which uniquely identifies the 1617 DS3/E3 interface to which this entry is 1618 applicable. The interface identified by a 1619 particular value of this index is the same 1620 interface as identified by the same value an 1621 dsx3LineIndex object instance." 1622 ::= { dsx3TotalEntry 1 } 1624 dsx3TotalPESs OBJECT-TYPE 1625 SYNTAX PerfTotalCount 1626 MAX-ACCESS read-only 1627 STATUS current 1628 DESCRIPTION 1629 "The counter associated with the number of P-bit 1630 Errored Seconds, encountered by a DS3 interface in 1631 the previous 24 hour interval. Invalid 15 minute 1632 intervals count as 0." 1633 ::= { dsx3TotalEntry 2 } 1635 dsx3TotalPSESs OBJECT-TYPE 1636 SYNTAX PerfTotalCount 1637 MAX-ACCESS read-only 1638 STATUS current 1639 DESCRIPTION 1640 "The counter associated with the number of P-bit 1641 Severely Errored Seconds, encountered by a DS3 1642 interface in the previous 24 hour interval. 1643 Invalid 15 minute intervals count as 0." 1644 ::= { dsx3TotalEntry 3 } 1646 dsx3TotalSEFSs OBJECT-TYPE 1647 SYNTAX PerfTotalCount 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "The counter associated with the number of 1652 Severely Errored Framing Seconds, encountered by a 1653 DS3/E3 interface in the previous 24 hour interval. 1654 Invalid 15 minute intervals count as 0." 1655 ::= { dsx3TotalEntry 4 } 1657 dsx3TotalUASs OBJECT-TYPE 1658 SYNTAX PerfTotalCount 1659 MAX-ACCESS read-only 1660 STATUS current 1661 DESCRIPTION 1662 "The counter associated with the number of 1663 Unavailable Seconds, encountered by a DS3 1664 interface in the previous 24 hour interval. 1665 Invalid 15 minute intervals count as 0." 1666 ::= { dsx3TotalEntry 5 } 1668 dsx3TotalLCVs OBJECT-TYPE 1669 SYNTAX PerfTotalCount 1670 MAX-ACCESS read-only 1671 STATUS current 1672 DESCRIPTION 1673 "The counter associated with the number of Line 1674 Coding Violations encountered by a DS3/E3 1675 interface in the previous 24 hour interval. 1676 Invalid 15 minute intervals count as 0." 1677 ::= { dsx3TotalEntry 6 } 1679 dsx3TotalPCVs OBJECT-TYPE 1680 SYNTAX PerfTotalCount 1681 MAX-ACCESS read-only 1682 STATUS current 1683 DESCRIPTION 1684 "The counter associated with the number of P-bit 1685 Coding Violations, encountered by a DS3 interface 1686 in the previous 24 hour interval. Invalid 15 1687 minute intervals count as 0." 1688 ::= { dsx3TotalEntry 7 } 1690 dsx3TotalLESs OBJECT-TYPE 1691 SYNTAX PerfTotalCount 1692 MAX-ACCESS read-only 1693 STATUS current 1694 DESCRIPTION 1695 "The number of Line Errored Seconds (BPVs or 1696 illegal zero sequences) encountered by a DS3/E3 1697 interface in the previous 24 hour interval. 1698 Invalid 15 minute intervals count as 0." 1699 ::= { dsx3TotalEntry 8 } 1701 dsx3TotalCCVs OBJECT-TYPE 1702 SYNTAX PerfTotalCount 1703 MAX-ACCESS read-only 1704 STATUS current 1705 DESCRIPTION 1706 "The number of C-bit Coding Violations encountered 1707 by a DS3 interface in the previous 24 hour 1708 interval. Invalid 15 minute intervals count as 0." 1710 ::= { dsx3TotalEntry 9 } 1712 dsx3TotalCESs OBJECT-TYPE 1713 SYNTAX PerfTotalCount 1714 MAX-ACCESS read-only 1715 STATUS current 1716 DESCRIPTION 1717 "The number of C-bit Errored Seconds encountered 1718 by a DS3 interface in the previous 24 hour 1719 interval. Invalid 15 minute intervals count as 0." 1720 ::= { dsx3TotalEntry 10 } 1722 dsx3TotalCSESs OBJECT-TYPE 1723 SYNTAX PerfTotalCount 1724 MAX-ACCESS read-only 1725 STATUS current 1726 DESCRIPTION 1727 "The number of C-bit Severely Errored Seconds 1728 encountered by a DS3 interface in the previous 24 1729 hour interval. Invalid 15 minute intervals count 1730 as 0." 1731 ::= { dsx3TotalEntry 11 } 1733 -- The DS3 Far End Group 1735 -- The DS3 Far End Group consists of four tables : 1736 -- DS3 Far End Configuration 1737 -- DS3 Far End Current 1738 -- DS3 Far End Interval 1739 -- DS3 Far End Total 1741 -- The DS3 Far End Configuration Table 1743 dsx3FarEndConfigTable OBJECT-TYPE 1744 SYNTAX SEQUENCE OF Dsx3FarEndConfigEntry 1745 MAX-ACCESS not-accessible 1746 STATUS current 1747 DESCRIPTION 1748 "The DS3 Far End Configuration Table contains 1749 configuration information reported in the C-bits 1750 from the remote end." 1751 ::= { ds3 9 } 1753 dsx3FarEndConfigEntry OBJECT-TYPE 1754 SYNTAX Dsx3FarEndConfigEntry 1755 MAX-ACCESS not-accessible 1756 STATUS current 1757 DESCRIPTION 1758 "An entry in the DS3 Far End Configuration table." 1759 INDEX { dsx3FarEndLineIndex } 1760 ::= { dsx3FarEndConfigTable 1 } 1762 Dsx3FarEndConfigEntry ::= 1763 SEQUENCE { 1764 dsx3FarEndLineIndex InterfaceIndex, 1765 dsx3FarEndEquipCode DisplayString, 1766 dsx3FarEndLocationIDCode DisplayString, 1767 dsx3FarEndFrameIDCode DisplayString, 1768 dsx3FarEndUnitCode DisplayString, 1769 dsx3FarEndFacilityIDCode DisplayString 1770 } 1772 dsx3FarEndLineIndex OBJECT-TYPE 1773 SYNTAX InterfaceIndex 1774 MAX-ACCESS read-only -- read-only since originally an 1775 -- SMIv1 index 1776 STATUS current 1777 DESCRIPTION 1778 "The index value which uniquely identifies the DS3 1779 interface to which this entry is applicable. The 1780 interface identified by a particular value of this 1781 index is the same interface as identified by the 1782 same value an dsx3LineIndex object instance." 1783 ::= { dsx3FarEndConfigEntry 1 } 1785 dsx3FarEndEquipCode OBJECT-TYPE 1786 SYNTAX DisplayString (SIZE (0..10)) 1787 MAX-ACCESS read-write 1788 STATUS current 1789 DESCRIPTION 1790 "This is the Far End Equipment Identification code 1791 that describes the specific piece of equipment. 1792 It is sent within the Path Identification 1793 Message." 1794 ::= { dsx3FarEndConfigEntry 2 } 1796 dsx3FarEndLocationIDCode OBJECT-TYPE 1797 SYNTAX DisplayString (SIZE (0..11)) 1798 MAX-ACCESS read-write 1799 STATUS current 1800 DESCRIPTION 1801 "This is the Far End Location Identification code 1802 that describes the specific location of the 1803 equipment. It is sent within the Path 1804 Identification Message." 1805 ::= { dsx3FarEndConfigEntry 3 } 1807 dsx3FarEndFrameIDCode OBJECT-TYPE 1808 SYNTAX DisplayString (SIZE (0..10)) 1809 MAX-ACCESS read-write 1810 STATUS current 1811 DESCRIPTION 1812 "This is the Far End Frame Identification code 1813 that identifies where the equipment is located 1814 within a building at a given location. It is sent 1815 within the Path Identification Message." 1816 ::= { dsx3FarEndConfigEntry 4 } 1818 dsx3FarEndUnitCode OBJECT-TYPE 1819 SYNTAX DisplayString (SIZE (0..6)) 1820 MAX-ACCESS read-write 1821 STATUS current 1822 DESCRIPTION 1823 "This is the Far End code that identifies the 1824 equipment location within a bay. It is sent 1825 within the Path Identification Message." 1826 ::= { dsx3FarEndConfigEntry 5 } 1828 dsx3FarEndFacilityIDCode OBJECT-TYPE 1829 SYNTAX DisplayString (SIZE (0..38)) 1830 MAX-ACCESS read-write 1831 STATUS current 1832 DESCRIPTION 1833 "This code identifies a specific Far End DS3 path. 1834 It is sent within the Path Identification 1835 Message." 1836 ::= { dsx3FarEndConfigEntry 6 } 1838 -- The DS3 Far End Current 1840 dsx3FarEndCurrentTable OBJECT-TYPE 1841 SYNTAX SEQUENCE OF Dsx3FarEndCurrentEntry 1842 MAX-ACCESS not-accessible 1843 STATUS current 1844 DESCRIPTION 1845 "The DS3 Far End Current table contains various 1846 statistics being collected for the current 15 1847 minute interval. The statistics are collected 1848 from the far end block error code within the C- 1849 bits." 1850 ::= { ds3 10 } 1852 dsx3FarEndCurrentEntry OBJECT-TYPE 1853 SYNTAX Dsx3FarEndCurrentEntry 1854 MAX-ACCESS not-accessible 1855 STATUS current 1856 DESCRIPTION 1857 "An entry in the DS3 Far End Current table." 1858 INDEX { dsx3FarEndCurrentIndex } 1859 ::= { dsx3FarEndCurrentTable 1 } 1861 Dsx3FarEndCurrentEntry ::= 1862 SEQUENCE { 1863 dsx3FarEndCurrentIndex InterfaceIndex, 1864 dsx3FarEndTimeElapsed INTEGER, 1865 dsx3FarEndValidIntervals INTEGER, 1866 dsx3FarEndCurrentCESs PerfCurrentCount, 1867 dsx3FarEndCurrentCSESs PerfCurrentCount, 1868 dsx3FarEndCurrentCCVs PerfCurrentCount, 1869 dsx3FarEndCurrentUASs PerfCurrentCount, 1870 dsx3FarEndInvalidIntervals INTEGER 1871 } 1873 dsx3FarEndCurrentIndex OBJECT-TYPE 1874 SYNTAX InterfaceIndex 1875 MAX-ACCESS read-only -- read-only since originally an 1876 -- SMIv1 index 1877 STATUS current 1878 DESCRIPTION 1879 "The index value which uniquely identifies the DS3 1880 interface to which this entry is applicable. The 1881 interface identified by a particular value of this 1882 index is identical to the interface identified by 1883 the same value of dsx3LineIndex." 1884 ::= { dsx3FarEndCurrentEntry 1 } 1886 dsx3FarEndTimeElapsed OBJECT-TYPE 1887 SYNTAX INTEGER (0..899) 1888 MAX-ACCESS read-only 1889 STATUS current 1890 DESCRIPTION 1891 "The number of seconds that have elapsed since the 1892 beginning of the far end current error-measurement 1893 period. If, for some reason, such as an adjustment 1894 in the system's time-of-day clock, the current 1895 interval exceeds the maximum value, the agent will 1896 return the maximum value." 1897 ::= { dsx3FarEndCurrentEntry 2 } 1899 dsx3FarEndValidIntervals OBJECT-TYPE 1900 SYNTAX INTEGER (0..96) 1901 MAX-ACCESS read-only 1902 STATUS current 1903 DESCRIPTION 1904 "The number of previous far end intervals for 1905 which data was collected. The value will be 96 1906 unless the interface was brought online within the 1907 last 24 hours, in which case the value will be the 1908 number of complete 15 minute far end intervals 1909 since the interface has been online. In the case 1910 where the agent is a proxy, it is possible that 1911 some intervals are unavailable. In this case, 1912 this interval is the maximum interval number for 1913 which data is available." 1914 ::= { dsx3FarEndCurrentEntry 3 } 1916 dsx3FarEndCurrentCESs OBJECT-TYPE 1917 SYNTAX PerfCurrentCount 1918 MAX-ACCESS read-only 1919 STATUS current 1920 DESCRIPTION 1921 "The counter associated with the number of Far Far 1922 End C-bit Errored Seconds." 1923 ::= { dsx3FarEndCurrentEntry 4 } 1925 dsx3FarEndCurrentCSESs OBJECT-TYPE 1926 SYNTAX PerfCurrentCount 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "The counter associated with the number of Far End 1931 C-bit Severely Errored Seconds." 1932 ::= { dsx3FarEndCurrentEntry 5 } 1934 dsx3FarEndCurrentCCVs OBJECT-TYPE 1935 SYNTAX PerfCurrentCount 1936 MAX-ACCESS read-only 1937 STATUS current 1938 DESCRIPTION 1939 "The counter associated with the number of Far End 1940 C-bit Coding Violations reported via the far end 1941 block error count." 1942 ::= { dsx3FarEndCurrentEntry 6 } 1944 dsx3FarEndCurrentUASs OBJECT-TYPE 1945 SYNTAX PerfCurrentCount 1946 MAX-ACCESS read-only 1947 STATUS current 1948 DESCRIPTION 1949 "The counter associated with the number of Far End 1950 unavailable seconds." 1951 ::= { dsx3FarEndCurrentEntry 7 } 1953 dsx3FarEndInvalidIntervals OBJECT-TYPE 1954 SYNTAX INTEGER (0..96) 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 " The number of intervals in the range from 0 to 1959 dsx3FarEndValidIntervals for which no data is 1960 available. This object will typically be zero 1961 except in cases where the data for some intervals 1962 are not available (e.g., in proxy situations)." 1963 ::= { dsx3FarEndCurrentEntry 8 } 1965 -- The DS3 Far End Interval Table 1967 dsx3FarEndIntervalTable OBJECT-TYPE 1968 SYNTAX SEQUENCE OF Dsx3FarEndIntervalEntry 1969 MAX-ACCESS not-accessible 1970 STATUS current 1971 DESCRIPTION 1972 "The DS3 Far End Interval Table contains various 1973 statistics collected by each DS3 interface over 1974 the previous 24 hours of operation. The past 24 1975 hours are broken into 96 completed 15 minute 1976 intervals." 1977 ::= { ds3 11 } 1979 dsx3FarEndIntervalEntry OBJECT-TYPE 1980 SYNTAX Dsx3FarEndIntervalEntry 1981 MAX-ACCESS not-accessible 1982 STATUS current 1983 DESCRIPTION 1984 "An entry in the DS3 Far End Interval table." 1985 INDEX { dsx3FarEndIntervalIndex, 1986 dsx3FarEndIntervalNumber } 1987 ::= { dsx3FarEndIntervalTable 1 } 1989 Dsx3FarEndIntervalEntry ::= 1990 SEQUENCE { 1991 dsx3FarEndIntervalIndex InterfaceIndex, 1992 dsx3FarEndIntervalNumber INTEGER, 1993 dsx3FarEndIntervalCESs PerfIntervalCount, 1994 dsx3FarEndIntervalCSESs PerfIntervalCount, 1995 dsx3FarEndIntervalCCVs PerfIntervalCount, 1996 dsx3FarEndIntervalUASs PerfIntervalCount, 1997 dsx3FarEndIntervalValidData TruthValue 1998 } 2000 dsx3FarEndIntervalIndex OBJECT-TYPE 2001 SYNTAX InterfaceIndex 2002 MAX-ACCESS read-only -- read-only since originally an 2003 -- SMIv1 index 2004 STATUS current 2005 DESCRIPTION 2006 "The index value which uniquely identifies the DS3 2007 interface to which this entry is applicable. The 2008 interface identified by a particular value of this 2009 index is identical to the interface identified by 2010 the same value of dsx3LineIndex." 2011 ::= { dsx3FarEndIntervalEntry 1 } 2013 dsx3FarEndIntervalNumber OBJECT-TYPE 2014 SYNTAX INTEGER (1..96) 2015 MAX-ACCESS read-only -- read-only since originally an 2016 -- SMIv1 index 2017 STATUS current 2018 DESCRIPTION 2019 "A number between 1 and 96, where 1 is the most 2020 recently completed 15 minute interval and 96 is 2021 the 15 minutes interval completed 23 hours and 45 2022 minutes prior to interval 1." 2023 ::= { dsx3FarEndIntervalEntry 2 } 2025 dsx3FarEndIntervalCESs OBJECT-TYPE 2026 SYNTAX PerfIntervalCount 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "The counter associated with the number of Far End 2031 C-bit Errored Seconds encountered by a DS3 2032 interface in one of the previous 96, individual 15 2033 minute, intervals. In the case where the agent is 2034 a proxy and data is not available, return 2035 noSuchInstance." 2036 ::= { dsx3FarEndIntervalEntry 3 } 2038 dsx3FarEndIntervalCSESs OBJECT-TYPE 2039 SYNTAX PerfIntervalCount 2040 MAX-ACCESS read-only 2041 STATUS current 2042 DESCRIPTION 2043 "The counter associated with the number of Far End 2044 C-bit Severely Errored Seconds." 2045 ::= { dsx3FarEndIntervalEntry 4 } 2047 dsx3FarEndIntervalCCVs OBJECT-TYPE 2048 SYNTAX PerfIntervalCount 2049 MAX-ACCESS read-only 2050 STATUS current 2051 DESCRIPTION 2052 "The counter associated with the number of Far End 2053 C-bit Coding Violations reported via the far end 2054 block error count." 2055 ::= { dsx3FarEndIntervalEntry 5 } 2057 dsx3FarEndIntervalUASs OBJECT-TYPE 2058 SYNTAX PerfIntervalCount 2059 MAX-ACCESS read-only 2060 STATUS current 2061 DESCRIPTION 2062 "The counter associated with the number of Far End 2063 unavailable seconds." 2064 ::= { dsx3FarEndIntervalEntry 6 } 2066 dsx3FarEndIntervalValidData OBJECT-TYPE 2067 SYNTAX TruthValue 2068 MAX-ACCESS read-only 2069 STATUS current 2070 DESCRIPTION 2071 " This variable indicates if the data for this 2072 interval is valid." 2073 ::= { dsx3FarEndIntervalEntry 7 } 2075 -- The DS3 Far End Total 2077 dsx3FarEndTotalTable OBJECT-TYPE 2078 SYNTAX SEQUENCE OF Dsx3FarEndTotalEntry 2079 MAX-ACCESS not-accessible 2080 STATUS current 2081 DESCRIPTION 2082 "The DS3 Far End Total Table contains the 2083 cumulative sum of the various statistics for the 2084 24 hour period preceding the current interval." 2085 ::= { ds3 12 } 2087 dsx3FarEndTotalEntry OBJECT-TYPE 2088 SYNTAX Dsx3FarEndTotalEntry 2089 MAX-ACCESS not-accessible 2090 STATUS current 2091 DESCRIPTION 2092 "An entry in the DS3 Far End Total table." 2093 INDEX { dsx3FarEndTotalIndex } 2094 ::= { dsx3FarEndTotalTable 1 } 2096 Dsx3FarEndTotalEntry ::= 2097 SEQUENCE { 2098 dsx3FarEndTotalIndex InterfaceIndex, 2099 dsx3FarEndTotalCESs PerfTotalCount, 2100 dsx3FarEndTotalCSESs PerfTotalCount, 2101 dsx3FarEndTotalCCVs PerfTotalCount, 2102 dsx3FarEndTotalUASs PerfTotalCount 2103 } 2105 dsx3FarEndTotalIndex OBJECT-TYPE 2106 SYNTAX InterfaceIndex 2107 MAX-ACCESS read-only -- read-only since originally an 2108 -- SMIv1 index 2109 STATUS current 2110 DESCRIPTION 2111 "The index value which uniquely identifies the DS3 2112 interface to which this entry is applicable. The 2113 interface identified by a particular value of this 2114 index is identical to the interface identified by 2115 the same value of dsx3LineIndex." 2116 ::= { dsx3FarEndTotalEntry 1 } 2118 dsx3FarEndTotalCESs OBJECT-TYPE 2119 SYNTAX PerfTotalCount 2120 MAX-ACCESS read-only 2121 STATUS current 2122 DESCRIPTION 2123 "The counter associated with the number of Far End 2124 C-bit Errored Seconds encountered by a DS3 2125 interface in the previous 24 hour interval. 2126 Invalid 15 minute intervals count as 0." 2127 ::= { dsx3FarEndTotalEntry 2 } 2129 dsx3FarEndTotalCSESs OBJECT-TYPE 2130 SYNTAX PerfTotalCount 2131 MAX-ACCESS read-only 2132 STATUS current 2133 DESCRIPTION 2134 "The counter associated with the number of Far End 2135 C-bit Severely Errored Seconds encountered by a 2136 DS3 interface in the previous 24 hour interval. 2137 Invalid 15 minute intervals count as 0." 2138 ::= { dsx3FarEndTotalEntry 3 } 2140 dsx3FarEndTotalCCVs OBJECT-TYPE 2141 SYNTAX PerfTotalCount 2142 MAX-ACCESS read-only 2143 STATUS current 2144 DESCRIPTION 2145 "The counter associated with the number of Far End 2146 C-bit Coding Violations reported via the far end 2147 block error count encountered by a DS3 interface 2148 in the previous 24 hour interval. Invalid 15 2149 minute intervals count as 0." 2150 ::= { dsx3FarEndTotalEntry 4 } 2152 dsx3FarEndTotalUASs OBJECT-TYPE 2153 SYNTAX PerfTotalCount 2154 MAX-ACCESS read-only 2155 STATUS current 2156 DESCRIPTION 2157 "The counter associated with the number of Far End 2158 unavailable seconds encountered by a DS3 interface 2159 in the previous 24 hour interval. Invalid 15 2160 minute intervals count as 0." 2161 ::= { dsx3FarEndTotalEntry 5 } 2163 -- the DS3/E3 Fractional Table 2165 -- This table is deprecated. 2167 dsx3FracTable OBJECT-TYPE 2168 SYNTAX SEQUENCE OF Dsx3FracEntry 2169 MAX-ACCESS not-accessible 2170 STATUS deprecated 2171 DESCRIPTION 2172 "This table is deprecated in favour of using 2173 ifStackTable. 2175 Implementation of this table was optional. It was 2176 designed for those systems dividing a DS3/E3 into 2177 channels containing different data streams that 2178 are of local interest. 2180 The DS3/E3 fractional table identifies which 2181 DS3/E3 channels associated with a CSU are being 2182 used to support a logical interface, i.e., an 2183 entry in the interfaces table from the Internet- 2184 standard MIB. 2186 For example, consider a DS3 device with 4 high 2187 speed links carrying router traffic, a feed for 2188 voice, a feed for video, and a synchronous channel 2189 for a non-routed protocol. We might describe the 2190 allocation of channels, in the dsx3FracTable, as 2191 follows: 2192 dsx3FracIfIndex.2. 1 = 3 dsx3FracIfIndex.2.15 = 4 2193 dsx3FracIfIndex.2. 2 = 3 dsx3FracIfIndex.2.16 = 6 2194 dsx3FracIfIndex.2. 3 = 3 dsx3FracIfIndex.2.17 = 6 2195 dsx3FracIfIndex.2. 4 = 3 dsx3FracIfIndex.2.18 = 6 2196 dsx3FracIfIndex.2. 5 = 3 dsx3FracIfIndex.2.19 = 6 2197 dsx3FracIfIndex.2. 6 = 3 dsx3FracIfIndex.2.20 = 6 2198 dsx3FracIfIndex.2. 7 = 4 dsx3FracIfIndex.2.21 = 6 2199 dsx3FracIfIndex.2. 8 = 4 dsx3FracIfIndex.2.22 = 6 2200 dsx3FracIfIndex.2. 9 = 4 dsx3FracIfIndex.2.23 = 6 2201 dsx3FracIfIndex.2.10 = 4 dsx3FracIfIndex.2.24 = 6 2202 dsx3FracIfIndex.2.11 = 4 dsx3FracIfIndex.2.25 = 6 2203 dsx3FracIfIndex.2.12 = 5 dsx3FracIfIndex.2.26 = 6 2204 dsx3FracIfIndex.2.13 = 5 dsx3FracIfIndex.2.27 = 6 2205 dsx3FracIfIndex.2.14 = 5 dsx3FracIfIndex.2.28 = 6 2206 For dsx3M23, dsx3 SYNTRAN, dsx3CbitParity, and 2207 dsx3ClearChannel there are 28 legal channels, 2208 numbered 1 through 28. 2210 For e3Framed there are 16 legal channels, numbered 2211 1 through 16. The channels (1..16) correspond 2212 directly to the equivalently numbered time-slots." 2213 ::= { ds3 13 } 2215 dsx3FracEntry OBJECT-TYPE 2216 SYNTAX Dsx3FracEntry 2217 MAX-ACCESS not-accessible 2218 STATUS deprecated 2219 DESCRIPTION 2220 "An entry in the DS3 Fractional table." 2221 INDEX { dsx3FracIndex, dsx3FracNumber } 2222 ::= { dsx3FracTable 1 } 2224 Dsx3FracEntry ::= 2225 SEQUENCE { 2226 dsx3FracIndex INTEGER, 2227 dsx3FracNumber INTEGER, 2228 dsx3FracIfIndex INTEGER 2229 } 2231 dsx3FracIndex OBJECT-TYPE 2232 SYNTAX INTEGER (1..'7fffffff'h) 2233 MAX-ACCESS read-only -- read-only since originally an 2234 -- SMIv1 index 2235 STATUS deprecated 2236 DESCRIPTION 2237 "The index value which uniquely identifies the 2238 DS3 interface to which this entry is applicable 2239 The interface identified by a particular value 2240 of this index is the same interface as 2241 identified by the same value an dsx3LineIndex 2242 object instance." 2243 ::= { dsx3FracEntry 1 } 2245 dsx3FracNumber OBJECT-TYPE 2246 SYNTAX INTEGER (1..31) 2247 MAX-ACCESS read-only -- read-only since originally an 2248 -- SMIv1 index 2249 STATUS deprecated 2250 DESCRIPTION 2251 "The channel number for this entry." 2253 ::= { dsx3FracEntry 2 } 2255 dsx3FracIfIndex OBJECT-TYPE 2256 SYNTAX INTEGER (0..'7fffffff'h) 2257 MAX-ACCESS read-write 2258 STATUS deprecated 2259 DESCRIPTION 2260 "An index value that uniquely identifies an 2261 interface. The interface identified by a 2262 particular value of this index is the same 2263 interface as identified by the same value an 2264 ifIndex object instance. If no interface is 2265 currently using a channel, the value should be 2266 zero. If a single interface occupies more than 2267 one time slot, that ifIndex value will be found 2268 in multiple time slots." 2269 ::= { dsx3FracEntry 3 } 2271 -- DS3 TRAPS 2273 ds3Traps OBJECT IDENTIFIER ::= { ds3 15 } 2275 dsx3LineStatusChange NOTIFICATION-TYPE 2276 OBJECTS { dsx3LineStatus, 2277 dsx3LineStatusLastChange } 2278 STATUS current 2279 DESCRIPTION 2280 "A dsx3LineStatusChange trap is sent when the 2281 value of an instance of dsx3LineStatus changes. It 2282 can be utilized by an NMS to trigger polls. When 2283 the line status change results in a lower level 2284 line status change (i.e. ds1), then no traps for 2285 the lower level are sent." 2286 ::= { ds3Traps 0 1 } 2288 -- conformance information 2289 ds3Conformance OBJECT IDENTIFIER ::= { ds3 14 } 2291 ds3Groups OBJECT IDENTIFIER ::= { ds3Conformance 1 } 2292 ds3Compliances OBJECT IDENTIFIER ::= { ds3Conformance 2 } 2294 -- compliance statements 2296 ds3Compliance MODULE-COMPLIANCE 2297 STATUS current 2298 DESCRIPTION 2299 "The compliance statement for DS3/E3 interfaces." 2300 MODULE -- this module 2301 MANDATORY-GROUPS { ds3NearEndConfigGroup, 2302 ds3NearEndStatisticsGroup } 2304 GROUP ds3FarEndGroup 2305 DESCRIPTION 2306 "Implementation of this group is optional for all 2307 systems that attach to a DS3 Interface. However, 2308 only C-bit Parity and SYNTRAN DS3 applications 2309 have the capability (option) of providing this 2310 information." 2311 GROUP ds3NearEndOptionalTrapGroup 2312 DESCRIPTION 2313 "Implementation of this group is optional for all 2314 systems that attach to a DS3 Interface. If it is 2315 implemented then ds3NearEndOptionalConfigGroup 2316 should also be implemented." 2317 GROUP ds3NearEndOptionalConfigGroup 2318 DESCRIPTION 2319 "Implementation of this group is optional for all 2320 systems that attach to a DS3 interface." 2322 OBJECT dsx3LineType 2323 MIN-ACCESS read-only 2324 DESCRIPTION 2325 "Write access for the line type is not required." 2327 OBJECT dsx3LineCoding 2328 MIN-ACCESS read-only 2329 DESCRIPTION 2330 "Write access for the line coding is not 2331 required." 2333 OBJECT dsx3SendCode 2334 MIN-ACCESS read-only 2335 DESCRIPTION 2336 "Write access for the send code is not required." 2338 OBJECT dsx3LoopbackConfig 2339 MIN-ACCESS read-only 2340 DESCRIPTION 2341 "Write access for loopbacks is not required." 2343 OBJECT dsx3TransmitClockSource 2344 MIN-ACCESS read-only 2345 DESCRIPTION 2346 "Write access for the transmit clock source is not 2347 required." 2349 OBJECT dsx3LineLength 2350 MIN-ACCESS read-only 2351 DESCRIPTION 2352 "Write access for the line length is not 2353 required." 2355 OBJECT dsx3Channelization 2356 MIN-ACCESS read-only 2357 DESCRIPTION 2358 "Write access for the channelization is not 2359 required." 2361 ::= { ds3Compliances 1 } 2363 -- units of conformance 2365 ds3NearEndConfigGroup OBJECT-GROUP 2366 OBJECTS { dsx3LineIndex, 2367 dsx3TimeElapsed, 2368 dsx3ValidIntervals, 2369 dsx3LineType, 2370 dsx3LineCoding, 2371 dsx3SendCode, 2372 dsx3CircuitIdentifier, 2373 dsx3LoopbackConfig, 2374 dsx3LineStatus, 2375 dsx3TransmitClockSource, 2376 dsx3InvalidIntervals, 2377 dsx3LineLength, 2378 dsx3LoopbackStatus, 2379 dsx3Channelization, 2380 dsx3Ds1ForRemoteLoop} 2381 STATUS current 2382 DESCRIPTION 2383 "A collection of objects providing configuration 2384 information applicable to all DS3/E3 interfaces." 2385 ::= { ds3Groups 1 } 2387 ds3NearEndStatisticsGroup OBJECT-GROUP 2388 OBJECTS { dsx3CurrentIndex, 2389 dsx3CurrentPESs, 2390 dsx3CurrentPSESs, 2391 dsx3CurrentSEFSs, 2392 dsx3CurrentUASs, 2393 dsx3CurrentLCVs, 2394 dsx3CurrentPCVs, 2395 dsx3CurrentLESs, 2396 dsx3CurrentCCVs, 2397 dsx3CurrentCESs, 2398 dsx3CurrentCSESs, 2399 dsx3IntervalIndex, 2400 dsx3IntervalNumber, 2401 dsx3IntervalPESs, 2402 dsx3IntervalPSESs, 2403 dsx3IntervalSEFSs, 2404 dsx3IntervalUASs, 2405 dsx3IntervalLCVs, 2406 dsx3IntervalPCVs, 2407 dsx3IntervalLESs, 2408 dsx3IntervalCCVs, 2409 dsx3IntervalCESs, 2410 dsx3IntervalCSESs, 2411 dsx3IntervalValidData, 2412 dsx3TotalIndex, 2413 dsx3TotalPESs, 2414 dsx3TotalPSESs, 2415 dsx3TotalSEFSs, 2416 dsx3TotalUASs, 2417 dsx3TotalLCVs, 2418 dsx3TotalPCVs, 2419 dsx3TotalLESs, 2420 dsx3TotalCCVs, 2421 dsx3TotalCESs, 2422 dsx3TotalCSESs } 2423 STATUS current 2424 DESCRIPTION 2425 "A collection of objects providing statistics 2426 information applicable to all DS3/E3 interfaces." 2427 ::= { ds3Groups 2 } 2429 ds3FarEndGroup OBJECT-GROUP 2430 OBJECTS { dsx3FarEndLineIndex, 2431 dsx3FarEndEquipCode, 2432 dsx3FarEndLocationIDCode, 2433 dsx3FarEndFrameIDCode, 2434 dsx3FarEndUnitCode, 2435 dsx3FarEndFacilityIDCode, 2436 dsx3FarEndCurrentIndex, 2437 dsx3FarEndTimeElapsed, 2438 dsx3FarEndValidIntervals, 2439 dsx3FarEndCurrentCESs, 2440 dsx3FarEndCurrentCSESs, 2441 dsx3FarEndCurrentCCVs, 2442 dsx3FarEndCurrentUASs, 2443 dsx3FarEndInvalidIntervals, 2444 dsx3FarEndIntervalIndex, 2445 dsx3FarEndIntervalNumber, 2446 dsx3FarEndIntervalCESs, 2447 dsx3FarEndIntervalCSESs, 2448 dsx3FarEndIntervalCCVs, 2449 dsx3FarEndIntervalUASs, 2450 dsx3FarEndIntervalValidData, 2451 dsx3FarEndTotalIndex, 2452 dsx3FarEndTotalCESs, 2453 dsx3FarEndTotalCSESs, 2454 dsx3FarEndTotalCCVs, 2455 dsx3FarEndTotalUASs } 2456 STATUS current 2457 DESCRIPTION 2458 "A collection of objects providing remote 2459 configuration and statistics information 2460 applicable to C-bit Parity and SYNTRAN DS3 2461 interfaces." 2462 ::= { ds3Groups 3 } 2464 ds3DeprecatedGroup OBJECT-GROUP 2465 OBJECTS { dsx3IfIndex, 2466 dsx3FracIndex, 2467 dsx3FracNumber, 2468 dsx3FracIfIndex } 2469 STATUS deprecated 2470 DESCRIPTION 2471 "A collection of obsolete objects that may be 2472 implemented for backwards compatibility." 2473 ::= { ds3Groups 4 } 2475 ds3NearEndOptionalConfigGroup OBJECT-GROUP 2476 OBJECTS { dsx3LineStatusLastChange, 2477 dsx3LineStatusChangeTrapEnable } 2479 STATUS current 2480 DESCRIPTION 2481 "A collection of objects that may be implemented 2482 on DS3/E3 interfaces." 2483 ::= { ds3Groups 5 } 2485 ds3NearEndOptionalTrapGroup NOTIFICATION-GROUP 2486 NOTIFICATIONS { dsx3LineStatusChange } 2487 STATUS current 2488 DESCRIPTION 2489 "A collection of notifications that may be 2490 implemented on DS3/E3 interfaces." 2491 ::= { ds3Groups 6 } 2493 END 2495 4. Appendix A - Use of dsx3IfIndex and dsx3LineIndex 2497 This Appendix exists to document the previous use if dsx3IfIndex and 2498 dsx3LineIndex and to clarify the relationship of dsx3LineIndex as 2499 defined in rfc1407 with the dsx3LineIndex as defined in this 2500 document. 2502 The following shows the old and new definitions and the relationship: 2504 [New Definition]: "This object should be made equal to ifIndex. The 2505 next paragraph describes its previous usage. Making the object equal 2506 to ifIndex allows proper use of ifStackTable. 2508 [Old Definition]: "this object is the identifier of a DS3/E3 2509 Interface on a managed device. If there is an ifEntry that is 2510 directly associated with this and only this DS3/E3 interface, it 2511 should have the same value as ifIndex. Otherwise, number the 2512 dsx3LineIndices with an unique identifier following the rules of 2513 choosing a number that is greater than ifNumber and numbering the 2514 inside interfaces (e.g., equipment side) with even numbers and 2515 outside interfaces (e.g, network side) with odd numbers." 2517 When the "Old Definition" was created, it was described this way to 2518 allow a manager to treat the value _as if_ it were and ifIndex, i.e., 2519 the value would either be: 1) an ifIndex value or 2) a value that 2520 was guaranteed to be different from all valid ifIndex values. 2522 The new definition is a subset of that definition, i.e. the value is 2523 always an ifIndex value. 2525 The following is Section 3.1 from RFC1407: 2527 Different physical configurations for the support of SNMP with DS3/E3 2528 equipment exist. To accommodate these scenarios, two different 2529 indices for DS3/E3 interfaces are introduced in this MIB. These 2530 indices are dsx3IfIndex and dsx3LineIndex. 2532 External interface scenario: the SNMP Agent represents all managed 2533 DS3/E3 lines as external interfaces (for example, an Agent residing 2534 on the device supporting DS3/E3 interfaces directly): 2536 For this scenario, all interfaces are assigned an integer value equal 2537 to ifIndex, and the following applies: 2539 ifIndex=dsx3IfIndex=dsx3LineIndex for all interfaces. 2541 The dsx3IfIndex column of the DS3/E3 Configuration table relates each 2542 DS3/E3 interface to its corresponding interface (ifIndex) in the 2543 Internet-standard MIB (MIB-II STD 17, RFC1213). 2545 External&Internal interface scenario: the SNMP Agents resides on an 2546 host external from the device supporting DS3/E3 interfaces (e.g., a 2547 router). The Agent represents both the host and the DS3/E3 device. 2548 The index dsx3LineIndex is used to not only represent the DS3/E3 2549 interfaces external from the host/DS3/E3-device combination, but also 2550 the DS3/E3 interfaces connecting the host and the DS3/E3 device. The 2551 index dsx3IfIndex is always equal to ifIndex. 2553 Example: 2555 A shelf full of CSUs connected to a Router. An SNMP Agent residing on 2556 the router proxies for itself and the CSU. The router has also an 2557 Ethernet interface: 2559 +-----+ 2560 | | | 2561 | | | +---------------------+ 2562 |E | | 44.736 MBPS | ds3 M13 Line#A | ds3 C-bit Parity 2563 |t | R |---------------+ - - - - - - - - - +------> 2564 |h | | | | 2565 |e | O | 44.736 MBPS | ds3 M13 Line#B | ds3 C-bit Parity 2566 |r | |---------------+ - - - - - - - - - - +------> 2567 |n | U | | | 2568 |e | | 44.736 MBPS | ds3 M13 Line#C | ds3 C-bit Parity 2569 |t | T |---------------+ - - - -- -- - - - - +------> 2570 | | | | | 2571 |-----| E | 44.736 MBPS | ds3 M13 Line#D | ds3 C-bit Parity 2572 | | |---------------+ - - - - -- - - - - +------> 2573 | | R | |_____________________| 2574 | | | 2575 | +-----+ 2577 The assignment of the index values could for example be: 2579 ifIndex (= dsx3IfIndex) dsx3LineIndex 2581 1 NA NA (Ethernet) 2582 2 Line#A Router Side 6 2583 2 Line#A Network Side 7 2584 3 Line#B Router Side 8 2585 3 Line#B Network Side 9 2586 4 Line#C Router Side 10 2587 4 Line#C Network Side 11 2588 5 Line#D Router Side 12 2589 5 Line#D Network Side 13 2591 For this example, ifNumber is equal to 5. Note the 2592 following description of dsx3LineIndex: 2593 the dsx3LineIndex identifies a DS3/E3 Interface on a managed 2594 device. If there is an ifEntry that is directly associated with 2595 this and only this DS3/E3 interface, it should have the same value 2596 as ifIndex. Otherwise, number the dsx3LineIndices with an unique 2597 identifier following the rules of choosing a number greater 2598 than ifNumber and numbering inside interfaces (e.g., equipment 2599 side) with even numbers and outside interfaces 2600 (e.g, network side) with odd numbers. 2602 If the CSU shelf is managed by itself by a local SNMP Agent, 2603 the situation would be: 2605 ifIndex (= dsx3IfIndex) dsx3LineIndex 2607 1 Line#A Network Side 1 2608 2 Line#A RouterSide 2 2609 3 Line#B Network Side 3 2610 4 Line#B RouterSide 4 2611 5 Line#C Network Side 5 2612 6 Line#C Router Side 6 2613 7 Line#D Network Side 7 2614 8 Line#D Router Side 8 2616 5. Appendix B - The delay approach to Unavialable Seconds. 2618 This procedure is illustrated below for a DS3 C-Bit parity 2619 application. Similar rules would apply for other interfaces covered 2620 by this MIB. The procedure guarantees that the statistical counters 2621 are correctly updated at all times, although they lag real time by 10 2622 seconds. At the end of each 15 minutes interval the current interval 2623 counts are transferred to the most recent interval entry and each 2624 interval is shifted up by one position, with the oldest being 2625 discarded if necessary in order to make room. The current interval 2626 counts then start over from zero. Note, however, that the signal 2627 state calculation does not start afresh at each interval boundary; 2628 rather, signal state information is retained across interval 2629 boundaries. 2630 +----------------------------------------------------------------+ 2631 | READ COUNTERS & STATUS INFO FROM HARDWARE | 2632 | | 2633 |BPV EXZ LOS PCV CCV AIS SEF OOF LOF FEBE RAI | 2634 +----------------------------------------------------------------+ 2635 | | | | | | | | | | | 2636 | | | | | | | | | | | 2637 V V V V V V V V V V V 2638 +----------------------------------------------------------------+ 2639 | ACCUM ONE-SEC STATS, CHK ERR THRESHOLDS, & UPDT SIGNAL STATE | 2640 | | 2641 |<------------- NEAR END ---------------->| |<---- FAR END ----->| 2642 | | 2643 |LCV LES PCV CCV PES CES PSES CSES SEFS A/U CCV CES CSES SEFS A/U| 2644 +----------------------------------------------------------------+ 2645 | | | | | | | | | | | | | | | 2646 | | | | | | | | | | | | | | | 2647 V V V V V V V V V | V V V V | 2648 +--------------------------------------+ | +-----------------+ | 2649 | ONE-SEC DELAY | | | ONE-SEC DELAY | | 2650 | (1 OF 10) | | | (1 OF 10) | | 2651 +--------------------------------------+ | +-----------------+ | 2652 | | | | | | | | | | | | | | | 2653 / / / / / / / / / / / / / / / 2654 | | | | | | | | | | | | | | | 2655 V V V V V V V V V | V V V V | 2656 +--------------------------------------+ | +-----------------+ | 2657 | ONE-SEC DELAY | | | ONE-SEC DELAY | | 2658 | (10 OF 10) | | | (10 OF 10) | | 2659 +--------------------------------------+ | +-----------------+ | 2660 | | | | | | | | | | | | | | | 2661 | | | | | | | | | | | | | | | 2662 V V V V V V V V V V V V V V V 2663 +----------------------------------------------------------------+ 2664 | UPDATE STATISTICS COUNTERS | 2665 | | 2666 |<------------- NEAR END ---------------->| |<---- FAR END ----->| 2667 | | 2668 |LCV LES PCV CCV PES CES PSES CSES SEFS UAS CCV CES CSES SEFS UAS| 2669 +----------------------------------------------------------------+ 2671 Note that if such a procedure is adopted there is no current interval 2672 data for the first ten seconds after a system comes up. 2673 noSuchInstance must be returned if a management station attempts to 2674 access the current interval counters during this time. 2676 It is an implementation-specific matter whether an agent assumes that 2677 the initial state of the interface is available or unavailable. 2679 6. Intellectual Property 2681 The IETF takes no position regarding the validity or scope of any 2682 intellectual property or other rights that might be claimed to 2683 pertain to the implementation or use of the technology described in 2684 this document or the extent to which any license under such rights 2685 might or might not be available; neither does it represent that it 2686 has made any effort to identify any such rights. Information on the 2687 IETF's procedures with respect to rights in standards-track and 2688 standards-related documentation can be found in BCP-11. Copies of 2689 claims of rights made available for publication and any assurances of 2690 licenses to be made available, or the result of an attempt made to 2691 obtain a general license or permission for the use of such 2692 proprietary rights by implementors or users of this specification can 2693 be obtained from the IETF Secretariat. 2695 The IETF invites any interested party to bring to its attention any 2696 copyrights, patents or patent applications, or other proprietary 2697 rights which may cover technology that may be required to practice 2698 this standard. Please address the information to the IETF Executive 2699 Director. 2701 7. Full Copyright Statement 2703 Copyright (C) The Internet Society (2003). All Rights Reserved. 2705 This document and translations of it may be copied and furnished to 2706 others, and derivative works that comment on or otherwise explain it 2707 or assist in its implementation may be prepared, copied, published 2708 and distributed, in whole or in part, without restriction of any 2709 kind, provided that the above copyright notice and this paragraph are 2710 included on all such copies and derivative works. However, this 2711 document itself may not be modified in any way, such as by removing 2712 the copyright notice or references to the Internet Society or other 2713 Internet organizations, except as needed for the purpose of 2714 developing Internet standards in which case the procedures for 2715 copyrights defined in the Internet Standards process must be 2716 followed, or as required to translate it into languages other than 2717 English. 2719 The limited permissions granted above are perpetual and will not be 2720 revoked by the Internet Society or its successors or assigns. 2722 This document and the information contained herein is provided on an 2723 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2724 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2725 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2726 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2727 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2729 8. Acknowledgments 2731 This document was produced by the AToM MIB Working Group. The Editor 2732 would like to dedicate a special thanks to C. Mike Heard for 2733 providing a top notch doctor review and many helpful suggestions, and 2734 to acknowledge D. Fowler, Editor of RFC 2496, T. Cox and K. Tesink 2735 Editors of RFC 1407. 2737 9. References 2739 9.1. Normative References 2741 [RFC2578] 2742 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2743 and S. Waldbusser, "Structure of Management Information Version 2 2744 (SMIv2)", STD 58 RFC 2578, April 1999. 2746 [RFC2579] 2747 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2748 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58 RFC 2749 2579, April 1999. 2751 [RFC2580] 2752 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 2753 and S. Waldbusser,"Conformance Statements for SMIv2", STD 58 RFC 2754 2580, April 1999. 2756 [RFC2863] 2757 McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2758 2863, June 2000. 2760 [ANSI-T1.102] 2761 American National Standard for telecommunications - digital 2762 hierarchy - electrical interfaces, ANSI T1.102-1987. 2764 [ANSI-T1.107] 2765 American National Standard for telecommunications - digital 2766 hierarchy - formats specification, ANSI T1.107- 1988. 2768 [ANSI-T1.107a] 2769 ANSI T1.107a-1990. 2771 [ANSI-T1.404] 2772 American National Standard for telecommunications - Carrier-to- 2773 Customer Installation - DS3 Metallic Interface, ANSI T1.404-1989. 2775 [ANSI-T1.231] 2776 American National Standard for Telecommunications -- Layer 1 In- 2777 Service Digital Transmission Performance Monitoring T1.231, Sept 2778 1993. 2780 [CCITT-G.751] 2781 CCITT - Digital Multiplex Equipment Operating at the Third Order 2782 Bit Rate of 34 368 Kbit/s and the Forth Order Bit Rate of 139 264 2783 Kbit/s and Using Positive Justification, G.751 2785 [ETSI-T/NA(91)18] 2786 European Telecommunications Standards Institute -- ETS "34M" -- 2787 Metropolitan Area Network Physical Convergence Layer Procedure for 2788 34.368 Megabits per Second, T/NA(91)18, May 1991. 2790 [RFC3593] 2791 Tesink, K., "Textual Conventions for MIB Modules Using Performance 2792 History Based on 15 Minute Intervals", RFC3593, September 2003. 2794 [ITU-T-M.1400] 2795 ITU-T M.1400: Designation For Interconnections Among Network 2796 Operators, October 2001. 2798 9.2. Informative References 2800 [RFC1213] 2801 Rose M., Editor, "Management Information Base for Network 2802 Management of TCP/IP-based internets: MIB-II", RFC 1213, 2803 Performance Systems International, March 1991. 2805 [RFC1407] 2806 T. Cox, K. Tesink, "Definitions of Managed Objects for the DS3/E3 2807 Interface Types", RFC 1406, January 1993. 2809 [RFC2495] 2810 Fowler D., "Definitions of Managed Objects for the DS1, E1, DS2 and 2811 and E2 Interface Types", RFC 2495, january 1999. 2812 *********************************************************** 2813 * NOTE TO RFC Editor (to be removed prior to publication):* 2814 * If (or its * 2815 * successor) is to be published as an RFC concurrently * 2816 * with this document, please update this reference to * 2817 * point to that RFC, instead of RFC 2495, and change * 2818 * the reference tag [RFC2495] to match. * 2819 *********************************************************** 2821 [RFC3592] 2822 Brown, T., and Tesink, K., "Definitions of Managed Objects for the 2823 SONET/SDH Interface Type", RFC 3592, September 2003. 2825 [RFC2494] 2826 Fowler, D., "Definitions of Managed Objects for the Ds0 and 2827 DS0Bundle Interface Types", RFC 2494, January 1999. 2829 [RFC3410] 2830 Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 2831 Applicability Statements for Internet-Standard Management 2832 Framework", RFC 3410, December 2002. 2834 10. Security Considerations 2836 There are a number of management objects defined in this MIB module 2837 with a MAX-ACCESS clause of read-write. Such objects may be 2838 considered sensitive or vulnerable in some network environments. The 2839 support for SET operations in a non-secure environment without proper 2840 protection can have a negative effect on network operations. The 2841 specific the objects and their sensitivities/vulnerabilities are as 2842 follows. 2844 Setting the following objects to incorrect values may result in 2845 traffic interruptions: 2847 dsx3LineType 2848 dsx3LineCoding 2849 dsx3SendCode 2850 dsx3LoopbackConfig 2851 dsx3TransmitClockSource 2852 dsx3LineLength 2853 dsx3Channelization 2854 dsx3Ds1ForRemoteLoop 2856 In the case of dsx3LineType, for example, both ends of a DS3/E3 must 2857 have the same value in order for traffic to flow. In the case of 2858 dsx3SendCode and dsx3LoopbackConfig, for another example, traffic may 2859 stop transmitting when particular loopbacks are applied. 2861 Setting the following objects to an incorrect value will result in 2862 the remote end receiving an incorrect Path Identification message, 2863 which may result in a connectivity inconsistency: 2865 dsx3FarEndEquipCode 2866 dsx3FarEndLocationIDCode 2867 dsx3FarEndFrameIDCode 2868 dsx3FarEndUnitCode 2869 dsx3FarEndFacilityIDCode 2871 Setting the following object to an incorrect value will not harm the 2872 traffic, but it may cause a circuit to be mis-identified and thereby 2873 create difficulties for service personnel when attempting to 2874 troubleshoot a problem: 2876 dsx3CircuitIdentifier 2878 Setting the following object can cause an increase in the number of 2879 traps received by the network management station: 2881 dsx3LineStatusChangeTrapEnable 2883 The readable objects in this MIB module (i.e., the objects with a 2884 MAX-ACCESS other than not-accessible) may be considered sensitive 2885 in some environments since, collectively, they provide extensive 2886 information about the performance of interfaces in DS3/E3 2887 equipment or networks and can reveal some aspects of their 2888 configuration. In such environments it is important to control 2889 even GET and NOTIFY access to these objects and possibly to 2890 encrypt the values of these objects when sending them over the 2891 network via SNMP. 2893 SNMP versions prior to SNMPv3 did not include adequate security. 2894 Even if the network itself is secure (for example by using IPSec), 2895 even then, there is no control as to who on the secure network 2896 is allowed to access and GET/SET (read/change/create/delete) the 2897 objects in this MIB module. 2899 It is RECOMMENDED that implementers consider the security features 2900 as provided by the SNMPv3 framework (see [RFC3410], section 8), 2901 including full support for the SNMPv3 cryptographic mechanisms 2902 (for authentication and privacy). 2904 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2905 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2906 enable cryptographic security. It is then a customer/operator 2907 responsibility to ensure that the SNMP entity giving access to 2908 an instance of this MIB module is properly configured to give 2909 access to the objects only to those principals (users) that have 2910 legitimate rights to indeed GET or SET (change/create/delete) them. 2912 11. Author's Address 2914 Orly Nicklass (editor) 2915 RAD Data Communications, Ltd. 2916 Ziv Tower, 24 Roul Walenberg 2917 Tel Aviv, Israel, 69719 2919 Phone: 9723-765-9969 2921 e-Mail: orly_n@rad.com 2923 Table of Contents 2925 1 The Internet Standard Management Framework ................... 2 2926 1.1 Changes from RFC2496 ....................................... 2 2927 1.2 Changes from RFC1407 ....................................... 2 2928 2 Overview ..................................................... 4 2929 2.1 Use of ifTable for DS3 Layer ............................... 4 2930 2.2 Usage Guidelines ........................................... 5 2931 2.2.1 Usage of ifStackTable .................................... 5 2932 2.2.2 Usage of Channelization for DS3, DS1, DS0 ................ 7 2933 2.2.3 Usage of Channelization for DS3, DS2, DS1 ................ 8 2934 2.2.4 Usage of Loopbacks ....................................... 9 2935 2.3 Objectives of this MIB Module .............................. 10 2936 2.4 DS3/E3 Terminology ......................................... 10 2937 2.4.1 Error Events ............................................. 10 2938 2.4.2 Performance Parameters ................................... 11 2939 2.4.3 Performance Defects ...................................... 14 2940 2.4.4 Other Terms .............................................. 16 2941 3 Object Definitions ........................................... 17 2942 4.1 The DS3/E3 Near End Group .................................. 20 2943 4.1.1 The DS3/E3 Configuration Table ........................... 20 2944 4.1.2 The DS3/E3 Current Table ................................. 30 2945 4.1.3 The DS3/E3 Interval Table ................................ 34 2946 4.1.4 The DS3/E3 Total ......................................... 38 2947 4.2 The DS3 Far End Group ...................................... 42 2948 4.2.1 The DS3 Far End Configuration ............................ 42 2949 4.2.2 The DS3 Far End Current .................................. 44 2950 4.2.3 The DS3 Far End Interval Table ........................... 47 2951 4.2.4 The DS3 Far End Total .................................... 49 2952 4.3 The DS3/E3 Fractional Table ................................ 52 2953 4.4 The DS3 Trap Group ......................................... 55 2954 4.5 Conformance Groups ......................................... 56 2955 4 Appendix A - Use of dsx3IfIndex and dsx3LineIndex ............ 60 2956 5 Appendix B - The delay approach to Unavialable Seconds. ..... 63 2957 6 Intellectual Property ........................................ 64 2958 7 Full Copyright Statement ..................................... 65 2959 8 Acknowledgments .............................................. 66 2960 9 References ................................................... 67 2961 9.1 Normative References ....................................... 67 2962 9.2 Informative References ..................................... 68 2963 10 Security Considerations ..................................... 70 2964 11 Author's Address ............................................ 71