idnits 2.17.1 draft-galimbe-kunze-g-698-2-snmp-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 101 instances of too long lines in the document, the longest one being 7 characters in excess of 72. ** The abstract seems to contain references ([ITU.G698.2]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 12 has weird spacing: '...optical inter...' == Line 954 has weird spacing: '...ded the optIf...' == Line 977 has weird spacing: '... config param...' == Line 1042 has weird spacing: '... config param...' == Line 1840 has weird spacing: '...t Entry at ei...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (March 6, 2012) is 4427 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) == Missing Reference: 'ITU-T G.7710' is mentioned on line 142, but not defined == Missing Reference: 'TEMPLATE TODO' is mentioned on line 3365, but not defined == Unused Reference: 'RFC2629' is defined on line 3570, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 3573, but no explicit reference was found in the text == Unused Reference: 'I-D.kunze-g-698-2-management-control-framework' is defined on line 3576, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G698.2' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G709' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G872' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G798' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G874' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G874.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G959.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G826' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G8201' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G694.1' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU.G7710' -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) == Outdated reference: A later version (-02) exists of draft-kunze-g-698-2-management-control-framework-00 Summary: 2 errors (**), 0 flaws (~~), 14 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force GMG. G.Galimberti, Ed. 3 Internet-Draft Cisco 4 Intended status: Standards Track RK. R.Kunze, Ed. 5 Expires: September 7, 2012 Deutsche Telekom 6 Kam. Lam, Ed. 7 Alcatel-Lucent 8 DH. Hiremagalur, Ed. 9 Juniper 10 March 6, 2012 12 A SNMP MIB to manage black-link optical interface parameters of DWDM 13 applications 14 draft-galimbe-kunze-g-698-2-snmp-mib-02 16 Abstract 18 This memo defines a portion of the Management Information Base (MIB) 19 used by Simple Network Management Protocol (SNMP) in TCP/IP- based 20 internets. In particular, it defines objects for managing Optical 21 parameters associated with Wavelength Division Multiplexing (WDM) 22 systems or characterized by the Optical Transport Network (OTN) in 23 accordance with the Black-Link approach defined in ITU-T 24 Recommendation G.698.2. [ITU.G698.2] 26 The MIB module defined in this memo can be used for Optical 27 Parameters monitoring and/or configuration of the endpoints of Black 28 Links. 30 Copyright Notice 32 Copyright (c) 2011 IETF Trust and the persons identified as the 33 document authors. All rights reserved. 35 Status of this Memo 37 This Internet-Draft is submitted in full conformance with the 38 provisions of BCP 78 and BCP 79. 40 Internet-Drafts are working documents of the Internet Engineering 41 Task Force (IETF). Note that other groups may also distribute 42 working documents as Internet-Drafts. The list of current Internet- 43 Drafts is at http://datatracker.ietf.org/drafts/current/. 45 Internet-Drafts are draft documents valid for a maximum of six months 46 and may be updated, replaced, or obsoleted by other documents at any 47 time. It is inappropriate to use Internet-Drafts as reference 48 material or to cite them other than as "work in progress." 49 This Internet-Draft will expire on September 7, 2012. 51 Copyright Notice 53 Copyright (c) 2012 IETF Trust and the persons identified as the 54 document authors. All rights reserved. 56 This document is subject to BCP 78 and the IETF Trust's Legal 57 Provisions Relating to IETF Documents 58 (http://trustee.ietf.org/license-info) in effect on the date of 59 publication of this document. Please review these documents 60 carefully, as they describe your rights and restrictions with respect 61 to this document. Code Components extracted from this document must 62 include Simplified BSD License text as described in Section 4.e of 63 the Trust Legal Provisions and are provided without warranty as 64 described in the Simplified BSD License. 66 Table of Contents 68 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 2. The Internet-Standard Management Framework . . . . . . . . . . 5 70 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 5 71 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 72 4.1. Optical Parameters Description . . . . . . . . . . . . . . 6 73 4.1.1. General . . . . . . . . . . . . . . . . . . . . . . . 7 74 4.1.2. Parameters at Ss . . . . . . . . . . . . . . . . . . . 8 75 4.1.3. Optical path from point Ss to Rs . . . . . . . . . . . 9 76 4.1.4. Interface at point Rs . . . . . . . . . . . . . . . . 11 77 4.1.5. Alarms and Threshold definition . . . . . . . . . . . 11 78 4.1.6. Performance Monitoring (PM) description . . . . . . . 12 79 4.1.7. Generic Parameter description . . . . . . . . . . . . 14 80 4.2. Use of ifTable . . . . . . . . . . . . . . . . . . . . . . 14 81 4.2.1. Use of ifTable for OPS Layer . . . . . . . . . . . . . 16 82 4.2.2. Use of ifTable for OCh Layer . . . . . . . . . . . . . 17 83 4.2.3. Use of ifTable . . . . . . . . . . . . . . . . . . . . 17 84 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 18 85 6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 18 86 7. Relationship to Other MIB Modules . . . . . . . . . . . . . . 73 87 7.1. Relationship to the [TEMPLATE TODO] MIB . . . . . . . . . 73 88 7.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 73 89 8. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 73 90 9. Security Considerations . . . . . . . . . . . . . . . . . . . 73 91 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 74 92 11. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 75 93 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 76 94 12.1. Normative References . . . . . . . . . . . . . . . . . . . 76 95 12.2. Informative References . . . . . . . . . . . . . . . . . . 77 96 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 78 97 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . . 78 98 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 78 100 1. Introduction 102 This memo defines a portion of the Management Information Base (MIB) 103 used by Simple Network Management Protocol (SNMP) in TCP/IP- based 104 internets. In particular, it defines objects for managing Optical 105 parameters associated with Wavelength Division Multiplexing (WDM) 106 systems or characterized by the Optical Transport Network (OTN) in 107 accordance with the Black-Link approach defined in G.698.2 108 [ITU.G698.2] 110 Black Link approach allows supporting an optical transmitter/receiver 111 pair of one vendor to inject a DWDM channel and run it over an 112 optical network composed of amplifiers, filters, add-drop 113 multiplexers from a different vendor. From architectural point of 114 view, the "Black Link" is a set of pre-configured/qualified network 115 connections between the G.698.2 reference points S and R. The black 116 links will be managed at the edges (i.e. the transmitters and 117 receivers attached to the S and R reference points respectively) for 118 the relevant parameters specified in G.698.2 [ITU.G698.2], G.798 119 [ITU.G798], G.874 [ITU.G874], and the performance parameters 120 specified G.7710/Y.1701 [ITU-T G.7710] and and G.874.1 [ITU.G874.1]. 122 The G.698.2 [ITU.G698.2] provides optical parameter values for 123 physical layer interfaces of Dense Wavelength Division Multiplexing 124 (DWDM) systems primarily intended for metro applications which 125 include optical amplifiers. Applications are defined in G.698.2 126 [ITU.G698.2] using optical interface parameters at the single-channel 127 connection points between optical transmitters and the optical 128 multiplexer, as well as between optical receivers and the optical 129 demultiplexer in the DWDM system. This Recommendation uses a 130 methodology which does not specify the details of the optical link, 131 e.g. the maximum fibre length, explicitly. The Recommendation 132 currently includes unidirectional DWDM applications at 2.5 and 10 133 Gbit/s (with 100 GHz and 50 GHz channel frequency spacing). Work is 134 still underway for 40 and 100 Gbit/s interfaces. There is 135 possibility for extensions to a lower channel frequency spacing. 137 This draft refers and supports also the 138 draft-kunze-g698-mgnt-ctrl-framework. 140 The building of a SNMP MIB describing the optical parameters defined 141 in G.698.2 [ITU.G698.2] G.798 [ITU.G798], G.874 [ITU.G874], 142 parameters specified G.7710/Y.1701 [ITU-T G.7710] allows the 143 different vendors and operator to retrieve, provision and exchange 144 information related to Optical blak links in a standardized way. 145 This facilitates interworking in case of using optical interfaces 146 from different vendors at the end of the link. 148 The MIB, reporting the Optical parameters and their values, 149 characterizes the features and the performances of the optical 150 components and allow a reliable black link design in case of 151 multivendor optical networks. 153 Although RFC 3591 [RFC3591] describes and defines the SNMP MIB of a 154 number of key optical parameters, alarms and Performance Monitoring, 155 a more complete description of optical parameters and processes can 156 be found in the ITU-T Recommendations. Appendix A of this document 157 provides an overview about the extensive ITU-T documentation in this 158 area. The same considerations can be applied to the RFC 4054 159 [RFC4054] 161 2. The Internet-Standard Management Framework 163 For a detailed overview of the documents that describe the current 164 Internet-Standard Management Framework, please refer to section 7 of 165 RFC 3410 [RFC3410]. 167 Managed objects are accessed via a virtual information store, termed 168 the Management Information Base or MIB. MIB objects are generally 169 accessed through the Simple Network Management Protocol (SNMP). 170 Objects in the MIB are defined using the mechanisms defined in the 171 Structure of Management Information (SMI). This memo specifies a MIB 172 module that is compliant to the SMIv2, which is described in STD 58, 173 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 174 [RFC2580]. 176 3. Conventions 178 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 179 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 180 document are to be interpreted as described in RFC 2119 [RFC2119] In 181 the description of OIDs the convention: Set (S) Get (G) and Trap (T) 182 conventions will describe the action allowed by the paramenter. 184 4. Overview 186 In this document, the term OTN (Optical Transport Network) system is 187 used to describe devices that are compliant with the requirements 188 specified in the ITU-T Recommendations G.872 [ITU.G872], G.709 189 [ITU.G709] , G.798 [ITU.G798], G.874 [ITU.G874], and G.874.1 190 [ITU.G874.1] while refers to G.698.2 [ITU.G698.2] for the Black Link 191 and DWDM parameter description. 193 Figure 1 shows a set of reference points, for the linear "black-link" 194 approach, for single-channel connection (Ss and Rs) between 195 transmitters (Tx) and receivers (Rx). Here the DWDM network elements 196 include an OM and an OD (which are used as a pair with the opposing 197 element), one or more optical amplifiers and may also include one or 198 more OADMs. 200 +-------------------------------------------------+ 201 Ss | DWDM Network Elements | Rs 202 +---+ | | | \ / | | | +---+ 203 Tx L1----|->| \ +------+ +------+ / |--|--->Rx L1 204 +---+ | | | | | +------+ | | | | | +---+ 205 +---+ | | | | | | | | | | | | +---+ 206 Tx L2----|->| OM |-->|------|->| OADM |--|------|->| OD |--|--->Rx L2 207 +---+ | | | | | | | | | | | | +---+ 208 +---+ | | | | | +------+ | | | | | +---+ 209 Tx L3----|->| / | DWDM | | ^ | DWDM | \ |--|--->Rx L3 210 +---+ | | / | Link +----|--|----+ Link | \ | | +---+ 211 +-----------+ | | +----------+ 212 +--+ +--+ 213 | | 214 v | 215 +-----+ +-----+ 216 |RxLx | |TxLx | 217 +-----+ +-----+ 218 Ss = reference point at the DWDM network element tributary output 219 Rs = reference point at the DWDM network element tributary input 220 Lx = Lambda x 221 OM = Optical Mux 222 OD = Optical Demux 223 OADM = Optical Add Drop Mux 225 from Fig. 5.1/G.698.2 227 Figure 1: Linear Black Link 229 G.698.2 [ITU.G698.2] defines also Ring Black Link configurations 230 [Fig. 5.2/G.698.2] and Bidiractional Black Link configurations [Fig. 231 5.3/G.698.2] 233 4.1. Optical Parameters Description 235 The black links are managed at the edges, i.e. at the transmitters 236 (Tx) and receivers (Rx) attached to the S and R reference points 237 respectively. The parameters that could be managed at the black link 238 edges are specified in G.698.2 [ITU.G698.2] for the optical 239 interface, in G.798 [ITU.G798] for the equipment aspect, and in 240 G.7710/Y.1701 [ITU.G7710] and G.874 [ITU.G874] for fault management 241 and performance monitoring. 243 The definitions of the optical parameters are provided below to 244 increase the readability of the document, where the definition is 245 ended by (G) the parameter can be retrieve with a GET, when (S) it 246 can be provisioned by a SET, (G,S) can be either GET and SET. 248 To support the management of these parameters, the SNMP MIB in RFC 249 3591 [RFC3591] is extended with a new MIB module defined in section 6 250 of this document. This new MIB module includes the definition of new 251 configuratoin table of the OCh Level for the parameters at Tx (S) and 252 Rx (R). 254 4.1.1. General 256 The following general parameters from G.698.2 [ITU.G698.2] and 257 G.694.1 [ITU.G694.1] provide general information at the optical 258 interface reference points. 260 Minimum channel spacing: 261 This is the minimum nominal difference in frequency (in GHz) 262 between two adjacent channels (G). 264 Bit rate/line coding of optical tributary signals: 265 Optical tributary signal class NRZ 2.5G (from nominally 622 Mbit/s 266 to nominally 2.67 Gbit/s) or NRZ 10G nominally 2.4 Gbit/s to 267 nominally 10.71 Gbit/s. (nominally 2.4 Gbit/s to nominally 10.71 268 Gbit/s). 40Gbit/s and 100Gbit/s are under study (G, S). 270 FEC Coding: 271 This parameter indicate what Forward Error Correction (FEC) code 272 is used at Ss and Rs (G, S) (not mentioned in G.698). EDITOR 273 NOTE: Need to check whether this parameter is to be put in "vendor 274 specific" parameter or can be a standard paramenter as defined in 275 G.698.2. Is this the various adaptations (FEC encoding types) 276 specified in G.798 clauses 12.3.1.1 (with FEC), 12.3.1.2 (without 277 FEC), and 12.3.1.5 (vendor-specific FEC) . 279 Maximum bit error ratio (BER): 280 This parameter indicate the maximum Bit error rate can be 281 supported by the application at the Receiver. In case of FEC 282 applications it is intended after the FEC correction (G) . 284 Fiber type: 285 Fiber type as per fibre types are chosen from those defined in 286 ITU-T Recs G.652, G.653, G.654 and G.655 (G,S) . 288 Wavelength Range (see G.694.1): [ITU.G694.1] 289 This parameter indicate minimum and maximum wavelength spectrum 290 (G) in a definite wavelength Band (L, C and S). 292 Wavelength Value (see G.694.1): 293 This parameter indicates the wavelength value that Ss and Rs will 294 be set to work (G, S). 296 Vendor Transceiver Class: 297 Other than specifying all the Transceiver parameter, it might be 298 convenient for the vendors to summarize a set of parameters in a 299 single proprietary parameter: the Class of transceiver. The 300 Transceiver classification will be based on the Vendor Name and 301 the main TX and RX parameters (i.e. Trunk Mode, Framing, Bit 302 rate, Trunk Type, Channel Band, Channel Grid, Modulation Format, 303 Channel Modulation Format, FEC Coding, Electrical Signal Framing 304 at Tx, Minimum maximum Chromatic Disperion (CD) at Rx, Maximum 305 Polarization Mode Dispersion (PMD) at Rx, Maximum differential 306 group delay at Rx, Loopbacks, TDC, Pre-FEC BER, Q-factor, 307 Q-margin,etc.). If this parameter is used, the MIB parameters 308 specifying the Transceiver characteristics may not be significant 309 and the vendor will be responsible to specify the Class contents 310 and values. The Vendor can publish the parameters of its Classes 311 or declare to be compatible with published Classes.(G) Optional 312 for compliance. (not mentioned in G.698) 314 single-channel application codes (see G.698.2): 315 This parameter indicates the transceiver application code at Ss 316 and Rs as defined in [ITU.G698.2] Chapter 5.3 - this parameter can 317 be called Optical Interface Identifier OII as per 318 [draft-martinelli-wson-interface-class] (G, S). 320 4.1.2. Parameters at Ss 322 The following parameters for the interface at point S are defined in 323 G.698.2 [ITU.G698.2]. 325 Maximum and minimum mean channel output power: 326 The mean launched power at Ss is the average power (in dBm) of a 327 pseudo-random data sequence coupled into the DWDM link. It is 328 defined as the rhange (Max and Min ) of the parameter (G, S) 330 Minimum and maximum central frequency: 331 The central frequency is the nominal single-channel frequency (in 332 THz) on which the digital coded information of the particular 333 optical channel is modulated by use of the NRZ line code. The 334 central frequencies of all channels within an application lie on 335 the frequency grid for the minimum channel spacing of the 336 application given in ITU-T Rec. G.694.1. This parameter give the 337 Maximum and minimum frequency interval the channel must be 338 modulated (G) 340 Maximum spectral excursion: 341 This is the maximum acceptable difference between the nominal 342 central frequency (in GHz) of the channel and the minus 15 dB 343 points of the transmitter spectrum furthest from the nominal 344 central frequency measured at point Ss. (G) 346 Maximum transmitter (residual) dispersion OSNR penalty (B.3/G.959.1) 347 [ITU.G959.1] 348 Defines a reference receiver that this penalty is measured with. 349 Lowest OSNR at Ss with worst case (residual) dispersion minus the 350 Lowest OSNR at Ss with no dispersion. Lowest OSNR at Ss with no 351 dispersion (G) 353 Minimum side mode suppression ratio, Minimum channel extinction 354 ratio, Eye mask: 355 Although are defined in G.698.2 are not supported by this draft 356 (G). 358 Current Laser Output power: 359 This parameter report the current Transceiver Output power, it can 360 be either a setting and measured value (G, S) NEED TO DISCUSS ON 361 THIS. 363 4.1.3. Optical path from point Ss to Rs 365 The following parameters for the optical path from point S and R are 366 defined in G.698.2 [ITU.G698.2]. 368 Maximum and minimum (residual) chromatic dispersion: 369 These parameters define the maximum and minimum value of the 370 optical path "end to end chromatic dispersion" (in ps/nm) that the 371 system shall be able to tolerate. (G) 373 Minimum optical return loss at Ss: 374 These parameter defines minimum optical return loss (in dB) of the 375 cable plant at the source reference point (Ss), including any 376 connectors (G) 378 Maximum discrete reflectance between SS and RS: 379 Optical reflectance is defined to be the ratio of the reflected 380 optical power present at a point, to the optical power incident to 381 that point. Control of reflections is discussed extensively in 382 ITU-T Rec. G.957 (G) 384 Maximum differential group delay: 385 Differential group delay (DGD) is the time difference between the 386 fractions of a pulse that are transmitted in the two principal 387 states of polarization of an optical signal. For distances 388 greater than several kilometres, and assuming random (strong) 389 polarization mode coupling, DGD in a fibre can be statistically 390 modelled as having a Maxwellian distribution. (G) 392 Maximum polarisation dependent loss: 393 The polarisation dependent loss (PDL) is the difference (in dB) 394 between the maximum and minimum values of the channel insertion 395 loss (or gain) of the black-link from point SS to RS due to a 396 variation of the state of polarization (SOP) over all SOPs. (G) 398 Maximum inter-channel crosstalk: 399 Inter-channel crosstalk is defined as the ratio of total power in 400 all of the disturbing channels to that in the wanted channel, 401 where the wanted and disturbing channels are at different 402 wavelengths. The parameter specify the isolation of a link 403 conforming to the "black-link" approach such that under the worst- 404 case operating conditions the inter-channel crosstalk at any 405 reference point RS is less than the maximum inter-channel 406 crosstalk value (G) 408 Maximum interferometric crosstalk: 409 This parameter places a requirement on the isolation of a link 410 conforming to the "black-link" approach such that under the worst 411 case operating conditions the interferometric crosstalk at any 412 reference point RS is less than the maximum interferometric 413 crosstalk value. (G) 415 Maximum optical path OSNR penalty: 416 The optical path OSNR penalty is defined as the difference between 417 the Lowest OSNR at Rs and Lowest OSNR at Ss that meets the BER 418 requirement (G) 420 Maximum ripple: 421 Although is defined in G.698.2, this parameter is not supported by 422 this draft. 424 4.1.4. Interface at point Rs 426 The following parameters for the interface at point R are defined in 427 G.698.2. 429 4.1.4.1. Mandatory parameters 431 Maximum and minimum mean input power: 432 The maximum and minimum values of the average received power (in 433 dBm) at point Rs. (G) 435 Minimum optical signal-to-noise ratio (OSNR): 436 The minimum optical signal-to-noise ratio (OSNR) is the minimum 437 value of the ratio of the signal power in the wanted channel to 438 the highest noise power density in the range of the central 439 frequency plus and minus the maximum spectral excursion (G) 441 Receiver OSNR tolerance: 442 The receiver OSNR tolerance is defined as the minimum value of 443 OSNR at point Rs that can be tolerated while maintaining the 444 maximum BER of the application. (G) 446 Maximum reflectance at receiver: 447 Although is defined in G.698.2, this parameter is not supported by 448 this draft (G). 450 4.1.4.2. Optional parameters 452 Current Chromatic Dispersion (CD): 453 Residual Chromatic Dispersion measuread at Rx Transceiver port 454 (G). 456 Current Optical Signal to Noise Ratio (OSNR): 457 Current Optical Signal to Noise Ratio (OSNR) estimated at Rx 458 Transceiver port (G). 460 Current Quality factor (Q): 461 "Q" factor estimated at Rx Transceiver port (G). 463 4.1.5. Alarms and Threshold definition 465 This section describes the Alarms and the Thresholds at Ss and Rs 466 points according to ITU-T Recommendations G.798 [ITU.G798], G.874 467 [ITU.G874], and G.874.1 [ITU.G874.1]. 469 OTN alarms defined in RFC3591: 471 Threshold Crossing Alert (TCA Alarm) 473 LOW-TXPOWER 475 HIGH-TXPOWER 477 LOW-RXPOWER 479 HIGH-RXPOWER 481 Loss of Signal (LOS) 483 Loss of Frame (LOF) 485 Server Signal Failure-P (SSF-P) 487 Loss of Multiframe (LOM) 489 OTN Thresholds (for TCA) defined in RFC3591 491 LOW-TXPOWER 493 HIGH-TXPOWER 495 LOW-RXPOWER 497 HIGH-RXPOWER 499 As the above parameters/alarms are already defined in RFC3591, they 500 are out of scope of this document and the RFC3591 will continue to be 501 the only reference for them 503 The list below reports the new Alarms and Thresholds not managed in 504 RFC3591 506 4.1.6. Performance Monitoring (PM) description 508 This section describes the Performance Monitoring parameters and 509 their thresholds at Ss and Rs points (Near -End and Far-End)according 510 to ITU-T Recommendations G.826 [ITU.G826], G.8201 [ITU.G8201], G.709 511 [ITU.G709], G.798 [ITU.G798], G.874 [ITU.G874], and G.874.1 512 [ITU.G874.1]. 514 Failure Counts (fc) : 515 Number of Failures occurred in an observation period (G) 517 Errored Seconds (es) : 518 It is a one-second period in which one or more bits are in error 519 or during which Loss of Signal (LOS) or Alarm Indication Signal 520 (AIS) is detected (G) 522 Severely Errored Seconds (ses) : 523 It is a one-second period which has a bit-error ratio = 524 1x10Eminus3 or during which Loss of Signal (LOS) or Alarm 525 Indication Signal (AIS) is detected (G) 527 Unavailable Seconds (uas) : 528 A period of unavailable time begins at the onset of ten 529 consecutive SES events. These ten seconds are considered to be 530 part of unavailable time. A new period of available time begins 531 at the onset of ten consecutive non-SES events. These ten seconds 532 are considered to be part of available time (G) 534 Background Block Errors (bbe) : 535 An errored block not occurring as part of an SES(G) 537 Error Seconds Ratio (esr) : 538 The ratio of ES in available time to total seconds in available 539 time during a fixed measurement interval(G) 541 Severely Errored Seconds Ratio (sesr) : 542 The ratio of SES in available time to total seconds in available 543 time during a fixed measurement interval(G) 545 Background Block Errored Seconds Ratio (bber) : 546 The ratio of Background Block Errors (BBE) to total blocks in 547 available time during a fixed measurement interval. The count of 548 total blocks excludes all blocks during SESs.(G) 550 FEC corrected Bit Error (FECcorrErr): 551 The number of bits corrected by the FEC are counted over one 552 second (G) 554 FEC un-corrected Words Error : 555 The number of Words un-corrected by the FEC are counted over one 556 second (G) 558 Pre-FEC Bit Error : 559 The number of Errored bits at receiving side before the FEC 560 function counted over one second (G) 562 OTN Valid Intervals : 563 The number of contiguous 15 minute intervals for which valid OTN 564 performance monitoring data is available for the particular 565 interface (G) 567 FEC Valid Intervals : 568 The number of contiguous 15 minute intervals for which valid FEC 569 PM data is available for the particular interface.(G) 571 4.1.7. Generic Parameter description 573 This section describes the Generic Parameters at Ss and Rs points 574 according to ITU-T Recommendations G.872 [ITU.G872], G.709 575 [ITU.G709], G.798 [ITU.G798], G.874 [ITU.G874], and G.874.1 576 [ITU.G874.1]. 578 Interface Admin Status : 579 The Administrative Status of an Interface: Up/Down - In Service/ 580 Out of Service (can be Automatic in Service) (G/S) 582 Interface Operational Status : 583 The Operational Status of an Interface: Up/Down - In Service/Out 584 of Service (G) 586 4.2. Use of ifTable 588 This section specifies how the MIB II interfaces group, as defined in 589 RFC 2863 [RFC2863], is used for the link ends of a black link. Only 590 the ifGeneralInformationGroup will be supported for the ifTable and 591 the ifStackTable to maintain the relationship between the OCh and OPS 592 layers. The OCh and OPS layers are managed in the ifTable using 593 IfEntries that correlate to the layers depicted in Figure 1. 595 For example, a device with TX and/or RX will have an Optical Physical 596 Section (OPS) layer, and an Optical Channel (OCh) layer. There is a 597 one to n relationship between the OPS and OCh layers. 599 EDITOR NOTE: Reason for changing from OChr to OCh: Work on revised 600 G.872 in the SG15 December 2011 meeting agreed to remove OChr from 601 the architecture and to update G.709 to account for this 602 architectural change. The meeting also agreed to consent the revised 603 text of G.872 and G.709 at the September 2012 SG15 meeting. 605 Figure 2 In the following figures, opticalChannel and 606 opticalPhysicalSection are abbreviated as och and ops respectively. 608 _____________________ 609 \ 610 Path Data Unit |\ 611 (ODUk) | \ 612 _____________________| \ ______________________ 613 | | | > 614 Tandem Data Unit | | | | 615 (ODUkT) | | OCh Layer | > n och IfEntries 616 _____________________| | | | 617 | |______________________| > 618 Optical | /| | > 619 Transport Unit | / | | | 620 (OTUk) |/ | OPSn Layer | > m ops IfEntries 621 _____________________/ | | | 622 |______________________| > 623 Sub-layers in 624 the OCh Layer 626 Figure 2: OTN Layers for OPS and OCh 628 Each opticalChannel IfEntry may be mapped to m opticalPhyscalSection 629 IfEntries, where m is greater than or equal to 1. Conversely, each 630 opticalTransPhyscalSection port entry may be mapped to n 631 opticalChannel IfEntries, where n is greater than or equal to 1. 633 The design of the Optical Interface MIB provides the option to model 634 an interface either as a single bidirectional object containing both 635 sink and source functions or as a pair of unidirectional objects, one 636 containing sink functions and the other containing source functions. 638 If the sink and source for a given protocol layer are to be modelled 639 as separate objects, then there need to be two ifTable entries, one 640 that corresponds to the sink and one that corresponds to the source, 641 where the directionality information is provided in the configuration 642 tables for that layer via the xxxDirectionality objects. The agent 643 is expected to maintain consistent directionality values between 644 ifStackTable layers (e.g., a sink must not be stacked in a 1:1 manner 645 on top of a source, or vice-versa), and all protocol layers that are 646 represented by a given ifTable entry are expected to have the same 647 directionality. 649 When separate ifTable entries are used for the source and sink 650 functions of a given physical interface, association between the two 651 uni-directional ifTable entries (one for the source function and the 652 other for the sink functions) should be provided. It is recommended 653 that identical ifName values are used for the two ifTable entries to 654 indicate such association. An implementation shall explicitly state 655 what mechanism is used to indicate the association, if ifName is not 656 used. 658 4.2.1. Use of ifTable for OPS Layer 660 Only the ifGeneralInformationGroup needs to be supported. 662 ifTable Object Use for OTN OPS Layer 663 ======================================================================== 665 ifIndex The interface index. 667 ifDescr Optical Transport Network (OTN) Optical 668 Physical Section (OPS) 670 ifType opticalPhysicalSection (xxx) 672 <<>> 674 ifSpeed Actual bandwidth of the interface in bits per 675 second. If the bandwidth of the interface is 676 greater than the maximum value of 4,294,967,295, 677 then the maximum value is reported and 678 ifHighSpeed must be used to report the 679 interface's speed. 681 ifPhysAddress An octet string with zero length. (There is 682 no specific address associated with the 683 interface.) 685 ifAdminStatus The desired administrative state of the 686 interface. Supports read-only access. 688 ifOperStatus The operational state of the interface. The 689 value lowerLayerDown(7) is not used, since 690 there is no lower layer interface. This object 691 is set to notPresent(6) if a component is 692 missing, otherwise it is set to down(2) if 693 either of the objects optIfOPSnCurrentStatus 694 indicates that any defect is present. 696 ifLastChange The value of sysUpTime at the last change in 697 ifOperStatus. 699 ifName Enterprise-specific convention (e.g., TL-1 AID) 700 to identify the physical or data entity 701 associated with this interface or an 702 OCTET STRING of zero length. The 703 enterprise-specific convention is intended to 704 provide the means to reference one or more 705 enterprise-specific tables. 707 ifLinkUpDownTrapEnable Default value is enabled(1). Supports 708 read-only access. 710 ifHighSpeed Actual bandwidth of the interface in Mega-bits 711 per second. A value of n represents a range of 712 'n-0.5' to 'n+0.499999'. 714 ifConnectorPresent Set to true(1). 716 ifAlias The (non-volatile) alias name for this interface 717 as assigned by the network manager. 719 4.2.2. Use of ifTable for OCh Layer 721 Use of ifTable for OCh Layer See RFC 3591 [RFC3591] section 2.4 723 4.2.3. Use of ifTable 725 Use of ifStackTable 727 EDITOR NOTE: more to be provided (similar to RFC 3591 Section 2.5) 728 Use of the ifStackTable and ifInvStackTable to associate the 729 opticalPhysicalSection and opticalChannel interface entries is best 730 illustrated by the example shown in Figure 3. The example assumes an 731 ops interface with ifIndex i that carries two multiplexed och 732 interfaces with ifIndex values of j and k, respectively. The example 733 shows that j and k are stacked above (i.e., multiplexed into) i. 734 Furthermore, it shows that there is no layer lower than i and no 735 layer higher than j and/or k. 737 Figure 3 739 HigherLayer LowerLayer 740 -------------------------- 741 0 j 742 0 k 743 j i 744 k i 745 i 0 747 Figure 3: Use of ifStackTable for an OTN port 749 For the inverse stack table, it provides the same information as the 750 interface stack table, with the order of the Higher and Lower layer 751 interfaces reversed. 753 5. Structure of the MIB Module 755 EDITOR NOTE:text will be provided based on the MIB module in Section 756 6 758 6. Object Definitions 760 EDITOR NOTE: Once the scope in Section 1 and the parameters in 761 Section 4 are finalized, a MIB module will be defined. It could be 762 an extension to the OPT-IF-MIB module of RFC 3591. >>> 764 OPT-IF-MIB DEFINITIONS ::= BEGIN 766 IMPORTS 767 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, Integer32, 768 Unsigned32, transmission, NOTIFICATION-TYPE 769 FROM SNMPv2-SMI 770 TEXTUAL-CONVENTION, RowPointer, RowStatus, TruthValue, DateAndTime 771 FROM SNMPv2-TC 772 SnmpAdminString 773 FROM SNMP-FRAMEWORK-MIB 774 MODULE-COMPLIANCE, OBJECT-GROUP 775 FROM SNMPv2-CONF 776 ifIndex 777 FROM IF-MIB; 779 -- This is the MIB module for the optical parameters associated with the 780 black link end points. 782 OptIfChannelSpacing ::= TEXTUAL-CONVENTION 783 STATUS current 784 DESCRIPTION 785 "Channel spacing 786 1 - 6.25GHz 787 2 - 12.5GHz 788 3 - 25GHz 789 4 - 50GHz 790 5 - 100 Ghz 791 " 792 SYNTAX INTEGER { 793 spacing6-25Ghz(1), 794 spacing12-5Ghz(2), 795 spacing25Ghz(3), 796 spacing50Ghz(4), 797 spacing100Ghz(5) 798 } 800 OptIfBitRateLineCoding ::= TEXTUAL-CONVENTION 801 STATUS current 802 DESCRIPTION 803 "Optical tributary signal class 804 1 - NRZ 2.5G ( from nominally 622 Mbit/s to nominally 2.67 Gbit/s) 805 2 - NRZ 10G nominally 2.4 Gbit/s to nominally 10.71 Gbit/s. 806 3 - 40Gbits/s 807 4 - 100Gbits/s 808 5 - 400Gbits/s 809 40Gbits/s and above are under study. " 810 SYNTAX INTEGER { 811 rate2-5G(1), 812 rate10G(2), 813 rate40G(3), 814 rate100G(4), 815 rate400G(5) 816 } 818 OptIfFiberTypeRecommendation ::= TEXTUAL-CONVENTION 819 STATUS current 820 DESCRIPTION 821 " Fiber Types - ITU-T Recs G.652, G.653, G.654 and G.655 822 One for recommendation and one for category. 823 G.652 A, B, C, D 824 G.653 A, B 825 G.654 A, B, C 826 G.655 C, D, E 827 G.656 828 G.657 A, B 829 " 830 SYNTAX INTEGER { 831 g652(1), 832 g653(2), 833 g654(3), 834 g655(4), 835 g656(5), 836 g657(6), 837 } 839 OptIfFiberTypeCategory ::= TEXTUAL-CONVENTION 840 STATUS current 841 DESCRIPTION 842 " Fiber Types - ITU-T Recs G.652, G.653, G.654 and G.655 843 G.652 A, B, C, D 844 G.653 A, B 845 G.654 A, B, C 846 G.655 C, D, E 847 G.656 848 G.657 A, B 849 Categories - A, B, C, D and E 850 " 851 SYNTAX INTEGER { 852 categoryA(1), 853 categoryB(2), 854 categoryC(3), 855 categoryD(4), 856 categoryE(5) 857 } 859 OptIfOTNType ::= TEXTUAL-CONVENTION 860 STATUS current 861 DESCRIPTION 862 " 863 This parameter indicates the parameters for the table are for 864 the Near End or Far End performance data. 865 1 - Near End 866 2 - Far End 867 " 868 SYNTAX INTEGER { 869 nearEnd(1), 870 farEnd(2) 871 } 873 OptIfOTNLayer ::= TEXTUAL-CONVENTION 874 STATUS current 875 DESCRIPTION 876 " 877 This parameter indicates the parameters for the table are for OTUk, 878 ODUk, TCM performance data. 879 1 - OTUk 880 2 - ODUk 881 3 - TCM 882 The ODUk layer and TCM sublayer PM is not related to the black link PM 883 management, but since this could be a common PM model for the ODUk 884 layer and TCM layers, we include it here so it may be used for simple 885 scenarios where only lower order ODUk or higher order ODUk is present. 886 For scenarios where both lower order ODUk and higher order ODUk are 887 present, further extension to the MIB model is required, in particular 888 for the indexing for these layers. 889 " 890 SYNTAX INTEGER { 891 OTUkLayer(1), 892 ODUkLayer(2), 893 TCMSubLayer(3) 894 } 896 -- 897 -- Alarm for the OCh and OTUk sublayer 898 -- 899 OptIfOTNOChAlarms ::= TEXTUAL-CONVENTION 900 STATUS current 901 DESCRIPTION 902 " This is the possible alarms from the OCh and OTUk layer." 903 SYNTAX INTEGER { 904 optIfOtnLosAlarm(1), -- OTN Loss of signal alarm 905 optIfOtnLofAlarm(2), -- OTN Loss of frame alarm 906 optIfOtnLomAlarm(3), -- OTN Loss of multi frame 907 alarm 908 optIfOtnOtuSsfAlarm(4), -- OTN SSF alarm 909 optIfOtnOtuBdiAlarm(5), -- OTN OTU BDI alarm 910 optIfOtnOtuTtimAlarm(6), -- OTN OTU Trail termination 911 mismatch alarm 912 optIfOtnOtuIaeAlarm(7), -- OTN OTU IAE alarm 913 optIfOtnOtuDegAlarm(8), -- OTN OTU signal degrade 914 alarm 915 optIfOptIfOtnOtuFecExcessiveErrsAlarm(9), 916 -- OTN OTU Fec Excessive 917 Errors alarm 918 optIf15MinThreshBBETCA(10), -- OTN OTU BBE Threshold alarm 919 optIf15MinThreshESTCA(11), -- OTN OTU ES Threshold alarm 920 optIf15MinThreshSESTCA(12), -- OTN OTU SES Threshold alarm 921 optIf15MinThreshUASTCA(13), -- OTN OTU UAS Threshold alarm 922 optIf15MinThreshFcsTCA(14), -- OTN OTU Fcs Threshold alarm 923 optIf15MinThreshFECUnCorrectedWordsTCA(15), 924 -- OTN FEC uncorrected words 925 -- TCA 926 optIf15MinThreshPreFECBERTCA(16) -- OTN Pre FEC BER TCA 927 } 928 OptIfOTNODUkTcmAlarms ::= TEXTUAL-CONVENTION 929 STATUS current 930 DESCRIPTION 931 " This is the alarms from the ODUk and TCM layer." 932 SYNTAX INTEGER { 933 optIfOTNOdukTcmOciAlarm(1), -- OTN ODU/TCM OCI alarm 934 optIfOTNOdukTcmLckAlarm(2), -- OTN ODU/TCM LCK alarm 935 optIfOTNOdukTcmBdiAlarm(3), -- OTN ODU/TCM BDI alarm 936 optIfOTNOdukTcmTtimAlarm(4), -- OTN ODU/TCM TTIM alarm 937 optIfOTNOdukTcmDegAlarm(5), -- OTN ODU/TCM Signal 938 -- degrade alarm, 939 optIfOTNOdukTcmSSfAlarm(6), -- OTN ODU/TCM SSF alarm, 940 optIfOTNOdukTcm15MinThreshBBETCA(7), -- OTN OTU BBE Threshold alarm 941 optIfOTNOdukTcm15MinThreshESTCA(8), -- OTN OTU ES Threshold alarm 942 optIfOTNOdukTcm15MinThreshSESTCA(9), -- OTN OTU SES Threshold alarm 943 optIfOTNOdukTcm15MinThreshUASTCA(10), -- OTN OTU UAS Threshold alarm 944 optIfOTNOdukTcm15MinThreshFcsTCA(11), -- OTN OTU Fcs Threshold alarm 945 } 947 -- Addition to the RFC 3591 objects 948 optIfOPSmConfigTable OBJECT IDENTIFIER ::= { optIfObjects 10 } 949 optIfOTNPMObjects OBJECT-TYPE ::= { optIfObjects 11 } 950 optIfOTNAlarm OBJECT IDENTIFIER ::= { optIfObjects 12 } 951 optIfOTNNotifications OBJECT IDENTIFIER ::= { optIfObjects 13 } 953 optIfOChConfigTable OBJECT IDENTIFIER ::= { optIfOCh 1 } 954 // Extended the optIfOChConfigTable 955 optIfOChSinkCurrentTable OBJECT IDENTIFIER ::= { optIfOCh 1 } 956 // Extended this table to add OSNR/CD/Q 957 optIfOChSrcConfigTable OBJECT IDENTIFIER ::= { optIfOCh 10 } 958 optIfOChSrcSinkConfigTable OBJECT IDENTIFIER ::= { optIfOCh 11 } 959 optIfOChSinkConfigTable OBJECT IDENTIFIER ::= { optIfOCh 12 } 960 optIfOTNPMConfigTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 1 } 961 optIfOTNPMCurrentTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 2 } 962 optIfOTNPMIntervalTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 3 } 963 optIfOTNPMCurrentDayTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 4 } 964 optIfOTNPMPrevDayTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 5 } 965 optIfOTNPMFECConfigTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 6 } 966 optIfOTNPMFECCurrentTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 7 } 967 optIfOTNPMFECIntervalTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 8 } 968 optIfOTNPMFECCurrentDayTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 9 } 969 optIfOTNPMFECPrevDayTable OBJECT IDENTIFIER ::= { optIfOTNPMObjects 10} 971 -- OPS - Optical Phyical Section 972 optIfOPSmConfigTable OBJECT-TYPE 973 SYNTAX SEQUENCE OF optIfOPSmConfigEntry 974 MAX-ACCESS not-accessible 975 STATUS current 976 DESCRIPTION 977 "A table of OPS General config parameters." 978 ::= { optIfObjects 10 } 980 optIfOPSmConfigEntry OBJECT-TYPE 981 SYNTAX OptIfOPSmConfigEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "An conceptual row of OPS General config parameters." 986 INDEX { ifIndex } 987 ::= { optIfOPSmConfigTable 1 } 989 OptIfOPSmConfigEntry ::= 990 SEQUENCE { 991 optIfOPSmDirectionality OptIfDirectionality, 992 optIfOPSmFiberTypeRecommendation OptIfFiberTypeRecommendation, 993 optIfOPSmFiberTypeCategory OptIfFiberTypeCategory, 994 optIfOPSmWavelengthsUsed Unsigned32 995 } 997 optIfOPSmDirectionality OBJECT-TYPE 998 SYNTAX OptIfDirectionality 999 MAX-ACCESS read-only 1000 STATUS current 1001 DESCRIPTION 1002 "Indicates the directionality of the entity." 1003 ::= { optIfOPSmConfigEntry 1 } 1005 optIfOPSmFiberTypeRecommendation OBJECT-TYPE 1006 SYNTAX OptIfFiberTypeRecommendation 1007 MAX-ACCESS read-write 1008 STATUS current 1009 DESCRIPTION 1010 "Fiber type as per fibre types are chosen from those defined in 1011 ITU-T Recs G.652, G.653, G.654, G.655, G.656 and G.657." 1012 ::= { optIfOPSmConfigEntry 2 } 1014 optIfOPSmFiberTypeCategory OBJECT-TYPE 1015 SYNTAX OptIfFiberTypeCategory 1016 MAX-ACCESS read-write 1017 STATUS current 1018 DESCRIPTION 1019 "Fiber type as per fibre types are chosen from those defined in 1020 ITU-T Recs G.652, G.653, and G.655. 1021 The categories are A, B, C, D and E." 1022 ::= { optIfOPSmConfigEntry 3 } 1024 optIfOPSmWavelengthsUsed OBJECT-TYPE 1025 SYNTAX Unsigned32 1026 MAX-ACCESS read-write 1027 STATUS current 1028 DESCRIPTION 1029 "Number of wavelengths used currently." 1030 ::= { optIfOPSmConfigEntry 4 } 1032 -- OCh config table 1033 -- modified the OCh Table group 1034 -- General parameters for the Black Link Ss-Rs will be added to 1035 -- the OchConfigTable 1037 optIfOChConfigTable OBJECT-TYPE 1038 SYNTAX SEQUENCE OF OptIfOChConfigEntry 1039 MAX-ACCESS not-accessible 1040 STATUS current 1041 DESCRIPTION 1042 "A table of Och General config parameters" 1043 ::= { optIfOCh 1 } 1045 optIfOChConfigEntry OBJECT-TYPE 1046 SYNTAX OptIfOChConfigEntry 1047 MAX-ACCESS not-accessible 1048 STATUS current 1049 DESCRIPTION 1050 " A conceptual row that contains OCh configuration information 1051 of an interface. " 1052 INDEX { ifIndex } 1053 ::= { optIfOChConfigTable 1 } 1055 OptIfOChConfigEntry ::= 1056 SEQUENCE { 1057 optIfOChMiminumChannelSpacing OptIfChannelSpacing, 1058 optIfOChBitRateLineCoding OptIfBitRateLineCoding, 1059 optIfOChFEC Integer32, 1060 optIfOChSinkMaximumBERMantisa Integer32, 1061 optIfOChSinkMaximumBERExponent Integer32, 1062 optIfOChMinWavelength Integer32, 1063 optIfOChMaxWavelength Integer32, 1064 optIfOChWavelength Integer32, 1065 optIfOChVendorTransceiverClass OCTET STRING, 1066 optIfOChOpticalInterfaceApplicationCode OCTET STRING, 1067 optIfOChLaserAdminState Integer, 1068 optIfOChLaserOperationalState TruthValue, 1069 optIfOChAdminState Integer, 1070 optIfOChOperationalState Integer 1071 } 1073 optIfOChMiminumChannelSpacing OBJECT-TYPE 1074 SYNTAX OptIfChannelSpacing 1075 UNITS "Gigahertz" 1076 MAX-ACCESS read-only 1077 STATUS current 1078 DESCRIPTION 1079 "A minimum nominal difference in frequency (GHz) between two adjacent 1080 channels." 1081 ::= { optIfOChConfigEntry 3 } 1083 optIfOChBitRateLineCoding OBJECT-TYPE 1084 SYNTAX OptIfBitRateLineCoding 1085 MAX-ACCESS read-write 1086 STATUS current 1087 DESCRIPTION 1088 " Optical tributary signal class 1089 NRZ 2.5G (from nominally 622 Mbit/s to nominally 2.67 Gbit/s) 1090 NRZ 10G (nominally 2.4 Gbit/s to nominally 10.71 Gbit/s) 1091 " 1092 ::= { optIfOChConfigEntry 4 } 1094 optIfOChFEC OBJECT-TYPE 1095 SYNTAX Integer32 1096 MAX-ACCESS read-write 1097 STATUS current 1098 DESCRIPTION 1099 " This parameter indicates what Forward Error Correction (FEC) code 1100 is used at Source and Sink. 1101 GFEC (from G709) and the I.x EFEC's 1102 (G.975 - Table I.1 super FEC). 1104 1 - No FEC 1105 2 - GFEC 1106 3 - I.2 EFEC 1107 4 - I.3 EFEC 1108 5 - I.4 EFEC 1109 6 - I.5 EFEC 1110 7 - I.6 EFEC 1111 8 - I.7 EFEC 1112 9 - I.8 EFEC 1113 10 - I.9 EFEC 1114 11 - 40G FEC (for new applications under study) 1115 12 - 40G EFEC (for new applications under study) 1116 13 - 100G FEC (for new applications under study) 1117 14 - 100G EFEC (for new applications under study) 1118 99 - Vendor Specific 1119 " 1120 ::= { optIfOChConfigEntry 5 } 1122 optIfOChSinkMaximumBERMantisa OBJECT-TYPE 1123 SYNTAX Integer32 1124 MAX-ACCESS read-only 1125 STATUS current 1126 DESCRIPTION 1127 " This parameter indicate the maximum Bit(mantisa) error rate can be 1128 supported by the application at the Receiver. In case of FEC 1129 applications it is intended after the FEC correction . 1130 " 1131 ::= { optIfOChConfigEntry 6} 1133 optIfOChSinkMaximumBERExponent OBJECT-TYPE 1134 SYNTAX Integer32 1135 MAX-ACCESS read-only 1136 STATUS current 1137 DESCRIPTION 1138 " This parameter indicate the maximum Bit(exponent) error rate can be 1139 supported by the application at the Receiver. In case of FEC 1140 applications it is intended after the FEC correction . 1141 " 1142 ::= { optIfOChConfigEntry 7} 1144 optIfOChMinWavelength OBJECT-TYPE 1145 SYNTAX Integer32 1146 UNITS "hertz" 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 " 1151 This parameter indicate minimum wavelength spectrum in a 1152 definite wavelength Band (L, C and S) 1153 " 1154 ::= { optIfOChConfigEntry 8} 1156 optIfOChMaxWavelength OBJECT-TYPE 1157 SYNTAX Integer32 1158 UNITS "hertz" 1159 MAX-ACCESS read-only 1160 STATUS current 1161 DESCRIPTION 1162 " 1163 This parameter indicate maximum wavelength spectrum in a 1164 definite wavelength Band (L, C and S) 1165 " 1166 ::= { optIfOChConfigEntry 9} 1168 optIfOChWavelength OBJECT-TYPE 1169 SYNTAX Integer32 1170 UNITS "hertz" 1171 MAX-ACCESS read-write 1172 STATUS current 1173 DESCRIPTION 1174 " This parameter indicates the wavelength value. 1175 " 1176 ::= { optIfOChConfigEntry 10} 1178 optIfOChVendorTransceiverClass OBJECT-TYPE 1179 SYNTAX OCTET STRING 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 " As defined in G.698 1184 Vendors can summarize a set of parameters in a 1185 single proprietary parameter: the Class of transceiver. The 1186 Transceiver classification will be based on the Vendor Name and 1187 the main TX and RX parameters (i.e. Trunk Mode, Framing, Bit 1188 rate, Trunk Type etc). 1189 If this parameter is used, the MIB parameters 1190 specifying the Transceiver characteristics may not be significant 1191 and the vendor will be responsible to specify the Class contents 1192 and values. The Vendor can publish the parameters of its Classes 1193 or declare to be compatible with published Classes.(G) Optional 1194 for compliance. (not mentioned in G.698) 1195 " 1196 ::= { optIfOChConfigEntry 11} 1198 optIfOChOpticalInterfaceApplicationCode OBJECT-TYPE 1199 SYNTAX OCTET STRING 1200 MAX-ACCESS read-write 1201 STATUS current 1202 DESCRIPTION 1203 " This parameter indicates the transceiver application code at Ss 1204 and Rs as defined in [ITU.G698.2] Chapter 5.3 1205 " 1206 ::= { optIfOChConfigEntry 12} 1208 optIfOChLaserAdminState OBJECT-TYPE 1209 SYNTAX INTEGER { 1210 off(0), 1211 on(1), 1212 autoInService(2) 1213 } 1214 MAX-ACCESS read-write 1215 STATUS current 1216 DESCRIPTION 1217 " 1218 The configured State of the laser: 0 - Off 1219 1 - On 1220 2 - Automatic - Inservice 1221 " 1222 ::= { optIfOChConfigEntry 13} 1224 optIfOChLaserOperationalState OBJECT-TYPE 1225 SYNTAX INTEGER { 1226 off(0), 1227 on(1) 1228 } 1229 MAX-ACCESS read-only 1230 STATUS current 1231 DESCRIPTION 1232 " 1233 The Operational Status of Laser : 0 - Off 1234 1 - On 1235 " 1236 ::= { optIfOChConfigEntry 14} 1238 optIfOChAdminState OBJECT-TYPE 1239 SYNTAX INTEGER { 1240 off(0), 1241 on(1), 1242 autoInService(2) 1243 } 1244 MAX-ACCESS read-write 1245 STATUS current 1246 DESCRIPTION 1247 " 1248 The Administrative Status of an Interface: 1249 0 - Out of Service 1250 1 - In Service 1251 2 - Automatic in Service. 1252 " 1253 ::= { optIfOChConfigEntry 15} 1255 optIfOChOperationalState OBJECT-TYPE 1256 SYNTAX INTEGER { 1257 off(0), 1258 on(1) 1259 } 1260 MAX-ACCESS read-only 1261 STATUS current 1262 DESCRIPTION 1263 " 1264 The Operational Status of an Interface: 1265 0 - Off 1266 1 - On 1267 " 1268 ::= { optIfOChConfigEntry 16} 1270 -- Parameters at OCh Src (Ss) 1271 -- OptIfOChSrcConfigEntry 1273 optIfOChSrcConfigTable OBJECT-TYPE 1274 SYNTAX SEQUENCE OF OptIfOChSrcConfigEntry 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "A configuration table of OCh Src (Ss) parameters." 1279 ::= { optIfOCh 10 } 1281 optIfOChSrcConfigEntry OBJECT-TYPE 1282 SYNTAX OptIfOChSrcConfigEntry 1283 MAX-ACCESS not-accessible 1284 STATUS current 1285 DESCRIPTION 1286 " A conceptual row that contains the Src (Ss) configuration 1287 parameters for a given interface." 1288 INDEX { ifIndex } 1289 ::= { optIfOChSrcConfigTable 1 } 1291 OptIfOChSrcConfigEntry ::= 1292 SEQUENCE { 1293 optIfOChMinimumMeanChannelOutputPower Integer32, 1294 optIfOChMaximumMeanChannelOutputPower Integer32, 1295 optIfOChMinimumCentralFrequency Integer32, 1296 optIfOChMaximumCentralFrequency Integer32, 1297 optIfOChMaximumSpectralExcursion Integer32, 1298 optIfOChMaximumTxDispersionOSNRPenalty Integer32 1299 } 1301 optIfOChMinimumMeanChannelOutputPower OBJECT-TYPE 1302 SYNTAX Integer32 1303 UNITS "0.1 dbm" 1304 MAX-ACCESS read-write 1305 STATUS current 1306 DESCRIPTION 1307 " 1308 The minimum mean launched power at Ss is the average power (in dBm) 1309 of a pseudo-random data sequence coupled into the DWDM link. 1310 " 1311 ::= { optIfOChSrcConfigEntry 1} 1313 optIfOChMaximumMeanChannelOutputPower OBJECT-TYPE 1314 SYNTAX Integer32 1315 UNITS "0.1 dbm" 1316 MAX-ACCESS read-write 1317 STATUS current 1318 DESCRIPTION 1319 " 1320 The maximum mean launched power at Ss is the average power (in dBm) 1321 of a pseudo-random data sequence coupled into the DWDM link. 1322 " 1323 ::= { optIfOChSrcConfigEntry 2} 1325 optIfOChMinimumCentralFrequency OBJECT-TYPE 1326 SYNTAX Integer32 1327 UNITS "0.01 THz" 1328 MAX-ACCESS read-only 1329 STATUS current 1330 DESCRIPTION 1331 " 1332 The minimum central frequency is the nominal single-channel frequency 1333 (in THz) on which the digital coded information of the particular 1334 optical channel is modulated by use of the NRZ line code. 1335 Eg 191.5THz will be represented as 19150 1336 " 1337 ::= { optIfOChSrcConfigEntry 3} 1339 optIfOChMaximumCentralFrequency OBJECT-TYPE 1340 SYNTAX Integer32 1341 UNITS "0.01 THz" 1342 MAX-ACCESS read-only 1343 STATUS current 1344 DESCRIPTION 1345 " 1346 The maximum central frequency is the nominal single-channel frequency 1347 (in THz) on which the digital coded information of the particular 1348 optical channel is modulated by use of the NRZ line code. 1349 Eg 191.5THz will be represented as 19150 1350 " 1351 ::= { optIfOChSrcConfigEntry 4} 1353 optIfOChMaximumSpectralExcursion OBJECT-TYPE 1354 SYNTAX Integer32 1355 UNITS "0.1 GHz" 1356 MAX-ACCESS read-only 1357 STATUS current 1358 DESCRIPTION 1359 " 1360 This is the maximum acceptable difference between the nominal 1361 central frequency (in GHz) of the channel and the minus 15 dB 1362 points of the transmitter spectrum furthest from the nominal 1363 central frequency measured at point Ss. 1364 " 1365 ::= { optIfOChSrcConfigEntry 5} 1367 optIfOChMaximumTxDispersionOSNRPenalty OBJECT-TYPE 1368 SYNTAX Integer32 1369 UNITS "0.1 dB" 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 " 1374 Defines a reference receiver that this penalty is measured with. 1375 Lowest OSNR at Ss with worst case (residual) dispersion minus the 1376 Lowest OSNR at Ss with no dispersion. Lowest OSNR at Ss with no 1377 dispersion 1378 " 1379 ::= { optIfOChSrcConfigEntry 6} 1381 -- Optical Path from Point Src (Ss) to Sink (Rs) 1382 -- Alternatively this can be optIfOChSsRsTable 1384 optIfOChSrcSinkConfigTable OBJECT-TYPE 1385 SYNTAX SEQUENCE OF OptIfOChSrcSinkConfigEntry 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "A table of paramters for the optical path from Src to Sink 1390 (Ss to Rs)." 1391 ::= { optIfOCh 11 } 1393 optIfOChSrcSinkConfigEntry OBJECT-TYPE 1394 SYNTAX OptIfOChSrcSinkConfigEntry 1395 MAX-ACCESS not-accessible 1396 STATUS current 1397 DESCRIPTION 1398 "A conceptual row that contains the optical path Src-Sink (Ss-Rs) 1399 configuration parameters for a given interface." 1400 INDEX { ifIndex } 1401 ::= { optIfOChSrcSinkConfigTable 1 } 1403 OptIfOChSrcSinkConfigEntry ::= 1404 SEQUENCE { 1405 optIfOChSrcSinkMinimumChromaticDispersion Integer32, 1406 optIfOChSrcSinkMaximumChromaticDispersion Integer32, 1407 optIfOChSrcSinkMinimumSrcOpticalReturnLoss Integer32, 1408 optIfOChSrcSinkMaximumDiscreteReflectanceSrcToSink Integer32, 1409 optIfOChSrcSinkMaximumDifferentialGroupDelay Integer32, 1410 optIfOChSrcSinkMaximumPolarisationDependentLoss Integer32, 1411 optIfOChSrcSinkMaximumInterChannelCrosstalk Integer32, 1412 optIfOChSrcSinkInterFerometricCrosstalk Integer32, 1413 optIfOChSrcSinkOpticalPathOSNRPenalty Integer32 1414 } 1416 optIfOChSrcSinkMinimumChromaticDispersion OBJECT-TYPE 1417 SYNTAX Integer32 1418 UNITS "ps/nm" 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 " 1423 These parameters define the minimum value of the 1424 optical path 'end to end chromatic dispersion' (in ps/nm) that the 1425 system shall be able to tolerate." 1426 ::= { optIfOChSrcSinkConfigEntry 1} 1428 optIfOChSrcSinkMaximumChromaticDispersion OBJECT-TYPE 1429 SYNTAX Integer32 1430 UNITS "ps/nm" 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 " These parameters define the maximum value of the 1435 optical path 'end to end chromatic dispersion' (in ps/nm) that the 1436 system shall be able to tolerate." 1437 ::= { optIfOChSrcSinkConfigEntry 2 } 1439 optIfOChSrcSinkMinimumSsOpticalReturnLoss OBJECT-TYPE 1440 SYNTAX Integer32 1441 UNITS ".1 db" 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 " 1446 These parameter defines minimum optical return loss (in dB) of the 1447 cable plant at the source reference point (Src/Ss), including any 1448 connectors." 1449 ::= { optIfOChSrcSinkConfigEntry 3 } 1451 optIfOChSrcSinkMaximumDiscreteReflectanceSrcToSink OBJECT-TYPE 1452 SYNTAX Integer32 1453 UNITS ".1 db" 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 " 1458 Optical reflectance is defined to be the ratio of the reflected 1459 optical power pre.sent at a point, to the optical power incident to 1460 that point. Control of reflections is discussed extensively in 1461 ITU-T Rec. G.957." 1462 ::= { optIfOChSrcSinkConfigEntry 4} 1464 optIfOChSrcSinkMaximumDifferentialGroupDelay OBJECT-TYPE 1465 SYNTAX Integer32 1466 UNITS "ps" 1467 MAX-ACCESS read-only 1468 STATUS current 1469 DESCRIPTION 1470 " 1471 Differential group delay (DGD) is the time difference between th 1472 fractions of a pulse that are transmitted in the two principal 1473 states of polarization of an optical signal. For distances 1474 greater than several kilometres, and assuming random (strong) 1475 polarization mode coupling, DGD in a fibre can be statistically 1476 modelled as having a Maxwellian distribution." 1477 ::= { optIfOChSrcSinkConfigEntry 5} 1479 optIfOChSrcSinkMaximumPolarisationDependentLoss OBJECT-TYPE 1480 SYNTAX Integer32 1481 UNITS "0.1 db" 1482 MAX-ACCESS read-only 1483 STATUS current 1484 DESCRIPTION 1485 " 1486 The polarisation dependent loss (PDL) is the difference (in dB) 1487 between the maximum and minimum values of the channel insertion 1488 loss (or gain) of the black-link from point SS to RS due to a 1489 variation of the state of polarization (SOP) over all SOPs." 1490 ::= { optIfOChSrcSinkConfigEntry 6} 1492 optIfOChSrcSinkMaximumInterChannelCrosstalk OBJECT-TYPE 1493 SYNTAX Integer32 1494 UNITS "0.1 db" 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 " 1499 Inter-channel crosstalk is defined as the ratio of total power in 1500 all of the disturbing channels to that in the wanted channel, 1501 where the wanted and disturbing channels are at different 1502 wavelengths. The parameter specify the isolation of a link 1503 conforming to the 'black-link' approach such that under the worst- 1504 case operating conditions the inter-channel crosstalk at any 1505 reference point RS is less than the maximum inter-channel 1506 crosstalk value." 1507 ::= { optIfOChSrcSinkConfigEntry 7} 1509 optIfOChSrcSinkInterFerometricCrosstalk OBJECT-TYPE 1510 SYNTAX Integer32 1511 UNITS "0.1 db" 1512 MAX-ACCESS read-only 1513 STATUS current 1514 DESCRIPTION 1515 " 1516 This parameter places a requirement on the isolation of a link 1517 conforming to the 'black-link' approach such that under the worst 1518 case operating conditions the interferometric crosstalk at any 1519 reference point RS is less than the maximum interferometric 1520 crosstalk value.." 1521 ::= { optIfOChSrcSinkConfigEntry 8} 1523 optIfOChSrcSinkOpticalPathOSNRPenalty OBJECT-TYPE 1524 SYNTAX Integer32 1525 UNITS "0.1 db" 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 " 1530 The optical path OSNR penalty is defined as the difference between 1531 the Lowest OSNR at Rs and Lowest OSNR at Ss that meets the BER 1532 requirement." 1533 ::= { optIfOChSrcSinkConfigEntry 9} 1535 -- Parameters at Sink (Rs) 1536 -- optIfOChSinkConfigTable 1537 optIfOChSinkConfigTable OBJECT-TYPE 1538 SYNTAX SEQUENCE OF OptIfOChSinkConfigEntry 1539 MAX-ACCESS not-accessible 1540 STATUS current 1541 DESCRIPTION 1542 "A table of OCh Sink (Rs) configuration parameters." 1543 ::= { optIfOCh 12 } 1545 optIfOChSinkConfigEntry OBJECT-TYPE 1546 SYNTAX OptIfOChSinkConfigEntry 1547 MAX-ACCESS not-accessible 1548 STATUS current 1549 DESCRIPTION 1550 "A conceptual row that contains the Sink (Rs) configuration 1551 parameters for a given interface." 1552 INDEX { ifIndex } 1553 ::= { optIfOChSinkConfigTable 1 } 1555 OptIfOChSinkConfigEntry ::= 1556 SEQUENCE { 1557 optIfOChSinkMinimumMeanIntputPower Integer32, 1558 optIfOChSinkMaximumMeanIntputPower Integer32, 1559 optIfOChSinkMinimumOSNR Integer32, 1560 optIfOChSinkOSNRTolerance Integer32 1561 } 1563 optIfOChSinkMinimumMeanIntputPower OBJECT-TYPE 1564 SYNTAX Integer32 1565 UNITS "0.1 dBm" 1566 MAX-ACCESS read-only 1567 STATUS current 1568 DESCRIPTION 1569 " The minimum values of the average received power (in dBm 1570 at point the Sink (Rs)." 1571 ::= { optIfOChSinkConfigEntry 1} 1573 optIfOChSinkMaximumMeanIntputPower OBJECT-TYPE 1574 SYNTAX Integer32 1575 UNITS "0.1 dBm" 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 " The maximum values of the average received power (in dBm) 1580 at point the Sink (Rs)." 1581 ::= { optIfOChSinkConfigEntry 2} 1583 optIfOChSinkMinimumOSNR OBJECT-TYPE 1584 SYNTAX Integer32 1585 UNITS "0.1 dB" 1586 MAX-ACCESS read-only 1587 STATUS current 1588 DESCRIPTION 1589 " The minimum optical signal-to-noise ratio (OSNR) is the minimum 1590 value of the ratio of the signal power in the wanted channel to 1591 the highest noise power density in the range of the central 1592 frequency plus and minus the maximum spectral excursion." 1593 ::= { optIfOChSinkConfigEntry 3} 1595 optIfOChSinkMinimumOSNRTolerance OBJECT-TYPE 1596 SYNTAX Integer32 1597 UNITS "0.1 dB" 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 " The receiver OSNR tolerance is defined as the minimum value of 1602 OSNR at point Sink (Rs) that can be tolerated while maintaining the 1603 maximum BER of the application. Sink (Rs)." 1604 ::= { optIfOChSinkConfigEntry 4} 1606 -- The OptIfOChSinkCurrentEntry table has been enhanced to add the 1607 -- following optional parameters 1608 -- For current status 1609 -- OptIfOChSinkCurrentEntry 1611 optIfOChSinkCurrentTable OBJECT-TYPE 1612 SYNTAX SEQUENCE OF OptIfOChSinkCurrentEntry 1613 MAX-ACCESS not-accessible 1614 STATUS current 1615 DESCRIPTION 1616 "A table of OCh sink performance monitoring information for 1617 the current 15-minute interval." 1618 ::= { optIfOCh 2 } 1620 optIfOChSinkCurrentEntry OBJECT-TYPE 1621 SYNTAX OptIfOChSinkCurrentEntry 1622 MAX-ACCESS not-accessible 1623 STATUS current 1624 DESCRIPTION 1625 "A conceptual row that contains OCh sink performance 1626 monitoring information for an interface for the current 1627 15-minute interval." 1628 INDEX { ifIndex } 1629 ::= { optIfOChSinkCurrentTable 1 } 1631 OptIfOChSinkCurrentEntry ::= 1632 SEQUENCE { 1633 optIfOChSinkCurrentChromaticDispersion Integer32, 1634 optIfOChSinkCurrentOSNR Integer32, 1635 optIfOChSinkCurrentQ Integer32 1636 } 1638 optIfOChSinkCurrentChromaticDispersion OBJECT-TYPE 1639 SYNTAX Integer32 1640 UNITS "ps/nm" 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 " Residual Chromatic Dispersion measured at Rx Transceiver port." 1645 ::= { optIfOChSinkCurrentEntry 7} 1647 optIfOChSinkCurrentOSNR OBJECT-TYPE 1648 SYNTAX Integer32 1649 UNITS "0.1 db" 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 " Current Optical Signal to Noise Ratio (OSNR) estimated at Rx 1654 Transceiver port ." 1655 ::= { optIfOChSinkCurrentEntry 8} 1657 optIfOChSinkCurrentQ OBJECT-TYPE 1658 SYNTAX Integer32 1659 MAX-ACCESS read-only 1660 STATUS current 1661 DESCRIPTION 1662 " 'Q' factor estimated at Rx Transceiver port." 1663 ::= { optIfOChSinkCurrentEntry 9} 1665 -- Performance Monitoring 1666 -- OTN PM Config Table 1667 -- 1668 optIfOTNPMConfigTable OBJECT-TYPE 1669 SYNTAX SEQUENCE OF OptIfOTNPMConfigEntry 1670 MAX-ACCESS not-accessible 1671 STATUS current 1672 DESCRIPTION 1673 "A table of performance monitoring configuration for the type 1674 'optIfOTNPMConfigSublayer' layer." 1675 ::= { optIfOTNPMObjects 1 } 1677 optIfOTNPMConfigEntry OBJECT-TYPE 1678 SYNTAX optIfOTNPMConfigEntry 1679 MAX-ACCESS not-accessible 1680 STATUS current 1681 DESCRIPTION 1682 " A conceptual entry in the performance monitoring configuration 1683 for the type 1684 'optIfOTNPMConfigSublayer' layer. 1685 " 1686 INDEX { ifIndex, optIfOTNPMConfigType, optIfOTNPMConfigSublayer, 1687 optIfOTNPMConfigTCMLevel } 1688 ::= { optIfOTNPMConfigTable 1 } 1690 OptIfOTNPMConfigEntry ::= 1691 SEQUENCE { 1692 optIfOTNPMConfigType OptIfOTNType, 1693 optIfOTNPMConfigLayer OptIfOTNLayer, 1694 optIfOTNPMConfigTCMLevel Unsigned32, 1695 optIfOTNPMESRInterval Integer32, 1696 optIfOTNPMSESRInterval Integer32, 1697 optIfOTNPMOTNValidIntervals Integer32, 1698 optIfOTNPMOTNThresh15MinFcs Integer32, 1699 optIfOTNPMOTNThresh15MinESs Integer32, 1700 optIfOTNPMOTNThresh15MinSESs Integer32, 1701 optIfOTNPMOTNThresh15MinUASs Integer32, 1702 optIfOTNPMOTNThresh15MinBBEs Integer32, 1703 } 1705 optIfOTNPMConfigType OBJECT-TYPE 1706 SYNTAX OptIfOTNType 1707 MAX-ACCESS read-only 1708 STATUS current 1709 DESCRIPTION 1710 " 1711 This parameter indicates the parameters for the table are for the 1712 Near End or Far End performance data. 1713 1 - Near End 1714 2 - Far End 1716 " 1717 ::= { optIfOTNPMConfigEntry 1} 1719 optIfOTNPMConfigSublayer OBJECT-TYPE 1720 SYNTAX OptIfOTNLayer 1721 MAX-ACCESS read-only 1722 STATUS current 1723 DESCRIPTION 1724 " 1725 This parameter indicates the parameters for the table are for OTUk, 1726 ODUk, TCMn performance data. 1727 1 - OTUk 1728 2 - ODUk 1729 3 - TCM 1730 The ODUk/TCM sublayer PM is not related to the black link PM 1731 management, but since this is a common PM model for the ODU/TCM layer, 1732 we may include it here. 1733 " 1734 ::= { optIfOTNPMConfigEntry 2} 1736 optIfOTNPMConfigTCMLevel OBJECT-TYPE 1737 SYNTAX Unsigned32 1738 MAX-ACCESS read-only 1739 STATUS current 1740 DESCRIPTION 1741 " 1742 This parameter indicates the TCM level (1-6) 1743 if the PM is of the type TCM. This will be 0 for OTUK/ODUK. 1744 " 1745 ::= { optIfOTNPMConfigEntry 3} 1747 optIOTNPMESRInterval OBJECT-TYPE 1748 SYNTAX Integer32 1749 UNITS "seconds" 1750 MAX-ACCESS read-write 1751 STATUS current 1752 DESCRIPTION 1753 " This parameter indicates the measurement interval 1754 for error seconds ratio. 1755 " 1756 ::= {optIfOTNPMConfigEntry 4} 1758 optIOTNPMSESRInterval OBJECT-TYPE 1759 SYNTAX Integer32 1760 UNITS "seconds" 1761 MAX-ACCESS read-write 1762 STATUS current 1763 DESCRIPTION 1764 " This parameter indicates the measurement interval 1765 for severely error seconds ratio. 1766 " 1767 ::= {optIfOTNPMConfigEntry 5} 1769 optIfOTNPM15MinThreshFcs OBJECT-TYPE 1770 SYNTAX Integer32 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION 1774 " 1775 The number of Fcs encountered by the interface within any 1776 given 15 minutes performance data collection period, which causes the 1777 SNMP agent to send optIf15MinThreshFcsTCA. One notification will be 1778 sent per interval per interface. A value of `0' will disable the 1779 notification. 1780 " 1781 ::= {optIfOTNPMConfigEntry 6} 1783 optIfOTNPM15MinThreshES OBJECT-TYPE 1784 SYNTAX Integer32 1785 MAX-ACCESS read-only 1786 STATUS current 1787 DESCRIPTION 1788 " 1789 The number of ES encountered by the interface within any 1790 given 15 minutes performance data collection period, which causes the 1791 SNMP agent to send optIf15MinThreshEsTCA. One notification will be 1792 sent per interval per interface. A value of `0' will disable the 1793 notification. 1794 " 1795 ::= {optIfOTNPMConfigEntry 7} 1797 optIfOTNPM15MinThreshSES OBJECT-TYPE 1798 SYNTAX Integer32 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 " 1803 The number of SES encountered by the interface within any 1804 given 15 minutes performance data collection period, which causes the 1805 SNMP agent to send optIf15MinThreshSESTCA. One notification will be 1806 sent per interval per interface. A value of `0' will disable the 1807 notification. 1808 " 1809 ::= {optIfOTNPMConfigEntry 8} 1811 optIfOTNPM15MinThreshUAS OBJECT-TYPE 1812 SYNTAX Integer32 1813 MAX-ACCESS read-only 1814 STATUS current 1815 DESCRIPTION 1816 " 1817 The number of UAS encountered by the interface within any 1818 given 15 minutes performance data collection period, which causes the 1819 SNMP agent to send optIf15MinThreshUASTCA. One notification will be 1820 sent per interval per interface. A value of `0' will disable the 1821 notification. 1822 " 1823 ::= {optIfOTNPMConfigEntry 9} 1825 optIfOTNPM15MinThreshBBE OBJECT-TYPE 1826 SYNTAX Integer32 1827 MAX-ACCESS read-only 1828 STATUS current 1829 DESCRIPTION 1830 " 1831 The number of UAS encountered by the interface within any 1832 given 15 minutes performance data collection period, which causes the 1833 SNMP agent to send optIf15MinThreshBBETCA. One notification will be 1834 sent per interval per interface. A value of `0' will disable the 1835 notification. 1836 " 1837 ::= {optIfOTNPMConfigEntry 10} 1839 -- 1840 -- PM Current Entry at either the OTU/ODUk/TCM 1841 -- 1842 optIfOTNPMCurrentTable OBJECT-TYPE 1843 SYNTAX SEQUENCE OF OptIfOTNPMCurrentEntry 1844 MAX-ACCESS not-accessible 1845 STATUS current 1846 DESCRIPTION 1847 "A table for the Performance monitoring Current Table. 1848 " 1849 ::= {optIfOTNPMObjects 2} 1851 optIfOTNPMCurrentEntry OBJECT-TYPE 1852 SYNTAX OptIfOTNPMCurrentEntry 1853 MAX-ACCESS not-accessible 1854 STATUS current 1855 DESCRIPTION 1856 "A conceptual entry in the Near end or Far End performance monitoring 1857 Current table for the type 'optIfOTNPMCurrentSublayer' layer. 1858 " 1859 INDEX { ifIndex, optIfOTNPMCurrentType , 1860 optIfOTNPMCurrentSublayer, optIfOTNPMCurrentTCMLevel } 1861 ::= { optIfOTNPMCurrentTable 1 } 1863 OptIfOTNPMCurrentEntry ::= 1864 SEQUENCE { 1865 optIfOTNPMCurrentType OptIfOTNType, 1866 optIfOTNPMCurrentLayer OptIfOTNLayer, 1867 optIfOTNPMCurrentTCMLevel Unsigned32, 1868 optIfOTNPMCurrentSuspectedFlag TruthValue, 1869 optIfOTNPMCurrentFcs Integer32, 1870 optIfOTNPMCurrentESs Integer32, 1871 optIfOTNPMCurrentSESs Integer32, 1872 optIfOTNPMCurrentUASs Integer32, 1873 optIfOTNPMCurrentBBEs Integer32, 1874 optIfOTNPMCurrentESR Integer32, 1875 optIfOTNPMCurrentSESR Integer32, 1876 optIfOTNPMCurrentBBER Integer32, 1877 } 1879 optIfOTNPMCurrentType OBJECT-TYPE 1880 SYNTAX OptIfOTNType 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 " 1885 This parameter indicates the parameters for the table are for the Near 1886 End or Far End performance data. 1887 1 - Near End 1888 2 - Far End 1889 " 1890 ::= { optIfOTNPMCurrentEntry 1} 1892 optIfOTNPMCurrentSublayer OBJECT-TYPE 1893 SYNTAX OptIfOTNLayer 1894 MAX-ACCESS read-only 1895 STATUS current 1896 DESCRIPTION 1897 " 1898 This parameter indicates the parameters for the table are for OTUk, 1899 ODUk, TCMn performance data. 1900 1 - OTUk (OCh which is used for the black link) 1901 2 - ODUk 1902 3 - TCM 1903 The ODUk/TCM sublayer PM is not related to the black link PM 1904 management, but since this is a common PM model for the ODU/TCM layer, 1905 we may include it here. 1906 " 1907 ::= { optIfOTNPMCurrentEntry 2} 1909 optIfOTNPMCurrentTCMLevel OBJECT-TYPE 1910 SYNTAX Unsigned32 1911 MAX-ACCESS read-only 1912 STATUS current 1913 DESCRIPTION 1914 " 1915 This parameter indicates the TCM level (1-6) 1916 if the PM is of the type TCM. This will be 0 for OTUK/ODUK. 1917 " 1918 ::= { optIfOTNPMCurrentEntry 3} 1920 optIfOTNPMCurrentSuspectedFlag OBJECT-TYPE 1921 SYNTAX TruthValue 1922 MAX-ACCESS read-only 1923 STATUS current 1924 DESCRIPTION 1925 " 1926 If true, the data in this entry may be unreliable. 1927 " 1928 ::= { optIfOTNPMCurrentEntry 4} 1930 optIfOTNPMCurrentFcs OBJECT-TYPE 1931 SYNTAX Integer32 1932 MAX-ACCESS read-only 1933 STATUS current 1934 DESCRIPTION 1935 " 1936 Number of Failures occurred in an observation period. 1937 " 1938 ::= { optIfOTNPMCurrentEntry 5} 1940 optIfOTNPMCurrentESs OBJECT-TYPE 1941 SYNTAX Integer32 1942 MAX-ACCESS read-only 1943 STATUS current 1944 DESCRIPTION 1945 " 1946 This is the number of seconds in which one or more bits are in 1947 error or during which Loss of Signal (LOS) or Alarm Indication 1948 Signal (AIS) is detected. 1949 " 1950 ::= { optIfOTNPMCurrentEntry 6} 1952 optIfOTNPMCurrentSESs OBJECT-TYPE 1953 SYNTAX Integer32 1954 MAX-ACCESS read-only 1955 STATUS current 1956 DESCRIPTION 1957 " The number of seconds which have a severe error. 1958 This is the number of seconds in which the bit-error ratio = 1959 1x10Eminus3 or during which Loss of Signal (LOS) or Alarm 1960 Indication Signal (AIS) is detected. 1961 " 1962 ::= { optIfOTNPMCurrentEntry 7} 1964 optIfOTNPMCurrentUASs OBJECT-TYPE 1965 SYNTAX Integer32 1966 MAX-ACCESS read-only 1967 STATUS current 1968 DESCRIPTION 1969 " It is the number of unavailable seconds. 1970 A period of unavailable time begins at the onset of ten 1971 consecutive SES events. These ten seconds are considered to be 1972 part of unavailable time. A new period of available time begins 1973 at the onset of ten consecutive non-SES events. These ten seconds 1974 are considered to be part of available time. 1975 " 1976 ::= { optIfOTNPMCurrentEntry 8} 1978 optIfOTNPMCurrentBBEs OBJECT-TYPE 1979 SYNTAX Integer32 1980 MAX-ACCESS read-only 1981 STATUS current 1982 DESCRIPTION 1983 " 1984 An errored block not occurring as part of an SES. 1985 " 1986 ::= { optIfOTNPMCurrentEntry 9} 1988 optIfOTNPMCurrentESR OBJECT-TYPE 1989 SYNTAX Integer32 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 " 1994 The ratio of ES in available time to total seconds in available 1995 time during a fixed measurement interval. 1996 " 1997 ::= { optIfOTNPMCurrentEntry 10} 1999 optIfOTNPMCurrentSESR OBJECT-TYPE 2000 SYNTAX Integer32 2001 UNIT ".001" 2002 MAX-ACCESS read-only 2003 STATUS current 2004 DESCRIPTION 2005 " 2006 The ratio of SES in available time to total seconds in available 2007 time during a fixed measurement interval. 2008 " 2009 ::= { optIfOTNPMCurrentEntry 11} 2011 -- 2012 -- OTN PM Interval Table 2013 -- Upto 96 15-minute intervals 2014 -- 2015 optIfOTNPMIntervalTable OBJECT-TYPE 2016 SYNTAX SEQUENCE OF OptIfOTNPMIntervalEntry 2017 MAX-ACCESS not-accessible 2018 STATUS Current 2019 DESCRIPTION 2020 "A Performance monitoring Interval Table. 2021 " 2022 ::= {optIfOTNPMObjects 3} 2024 optIfOTNPMIntervalEntry OBJECT-TYPE 2025 SYNTAX OptIfOTNPMIntervalEntry 2026 MAX-ACCESS not-accessible 2027 STATUS current 2028 DESCRIPTION 2029 "A conceptual entry in the Near end or Far End performance monitoring 2030 Interval table for the type 'optIfOTNPMIntervalSublayer' layer. 2031 " 2032 INDEX { ifIndex, optIfOTNPMIntervalType, optIfOTNPMIntervalSublayer, 2033 optIfOTNPMIntervalTCMLevel, optIfOTNPMIntervalNumber } 2034 ::= { optIfOTNPMIntervalTable 1 } 2036 OptIfOTNPMIntervalEntry ::= 2037 SEQUENCE { 2038 optIfOTNPMIntervalType OptIfOTNType, 2039 optIfOTNPMIntervalLayer OptIfOTNLayer, 2040 optIfOTNPMTIntervalTCMLevel Unsigned32, 2041 optIfOTNPMIntervalNumber OptIfIntervalNumber, 2042 optIfOTNPMIntervalSuspectedFlag TruthValue, 2043 optIfOTNPMIntervalFcs Integer32, 2044 optIfOTNPMIntervalESs Integer32, 2045 optIfOTNPMIntervalSESs Integer32, 2046 optIfOTNPMIntervalUASs Integer32, 2047 optIfOTNPMIntervalBBEs Integer32, 2048 optIfOTNPMIntervalESR Integer32, 2049 optIfOTNPMIntervalSESR Integer32, 2050 optIfOTNPMIntervalBBER Integer32, 2052 } 2054 optIfOTNPMIntervalType OBJECT-TYPE 2055 SYNTAX OptIfOTNType 2056 MAX-ACCESS read-only 2057 STATUS current 2058 DESCRIPTION 2059 " 2060 This parameter indicates the parameters for the table are for the 2061 Near End or Far End performance data. 2062 1 - Near End 2063 2 - Far End 2064 " 2065 ::= { optIfOTNPMIntervalEntry 1} 2067 optIfOTNPMIntervalSublayer OBJECT-TYPE 2068 SYNTAX OptIfOTNLayer 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 " 2073 This parameter indicates the parameters for the table are for OTUk, 2074 ODUk, TCMn performance data. 2075 1 - OTUk 2076 2 - ODUk 2077 3 - TCM 2078 The ODUk/TCM sublayer PM is not related to the black link PM 2079 management, but since this is a common PM model for the ODU/TCM 2080 layer, we may include it here." 2081 ::= { optIfOTNPMIntervalEntry 2} 2083 optIfOTNPMIntervalTCMLevel OBJECT-TYPE 2084 SYNTAX Unsigned32 2085 MAX-ACCESS read-only 2086 STATUS current 2087 DESCRIPTION 2088 " 2089 This parameter indicates the TCM level (1-6) 2090 if the PM is of the type TCM. This will be 0 for OTUK/ODUK. 2091 " 2092 ::= { optIfOTNPMIntervalEntry 3} 2094 optIfOTNPMIntervalNumber OBJECT-TYPE 2095 SYNTAX OptIfIntervalNumber 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 " 2100 A number between 1 and 96, where 1 is the most 2101 recently completed 15 minute interval and 96 is 2102 the 15 minutes interval completed 23 hours and 45 2103 minutes prior to interval 1. 2104 " 2105 ::= { optIfOTNPMIntervalEntry 4} 2107 optIfOTNPMIntervalSuspectedFlag OBJECT-TYPE 2108 SYNTAX TruthValue 2109 MAX-ACCESS read-only 2110 STATUS current 2111 DESCRIPTION 2112 " 2113 If true, the data in this entry may be unreliable. 2114 " 2115 ::= { optIfOTNPMIntervalEntry 5} 2117 optIfOTNPMIntervalFcs OBJECT-TYPE 2118 SYNTAX Integer32 2119 MAX-ACCESS read-only 2120 STATUS current 2121 DESCRIPTION 2122 " 2123 Number of Failures occurred in an observation period. 2124 " 2125 ::= { optIfOTNPMIntervalEntry 6} 2127 optIfOTNPMIntervalESs OBJECT-TYPE 2128 SYNTAX Integer32 2129 MAX-ACCESS read-only 2130 STATUS current 2131 DESCRIPTION 2132 " 2133 It is a one-second period in which one or more bits are in error 2134 or during which Loss of Signal (LOS) or Alarm Indication Signal 2135 (AIS) is detected. 2136 " 2137 ::= { optIfOTNPMIntervalEntry 7} 2139 optIfOTNPMIntervalSESs OBJECT-TYPE 2140 SYNTAX Integer32 2141 MAX-ACCESS read-only 2142 STATUS current 2143 DESCRIPTION 2144 " The number of seconds which have a severe error. 2145 It is a one-second period which has a bit-error ratio = 2146 1x10Eminus3 or during which Loss of Signal (LOS) or Alarm 2147 Indication Signal (AIS) is detected. 2148 " 2149 ::= { optIfOTNPMIntervalEntry 8} 2151 optIfOTNPMIntervalUASs OBJECT-TYPE 2152 SYNTAX Integer32 2153 MAX-ACCESS read-only 2154 STATUS current 2155 DESCRIPTION 2156 " It is the number of unavailable seconds in this 15 minute interval. 2157 A period of unavailable time begins at the onset of ten 2158 consecutive SES events. These ten seconds are considered to be 2159 part of unavailable time. A new period of available time begins 2160 at the onset of ten consecutive non-SES events. These ten seconds 2161 are considered to be part of available time. 2162 " 2163 ::= { optIfOTNPMIntervalEntry 9} 2165 optIfOTNPMIntervalBBEs OBJECT-TYPE 2166 SYNTAX Integer32 2167 MAX-ACCESS read-only 2168 STATUS current 2169 DESCRIPTION 2170 " 2171 An errored block not occurring as part of an SES. 2172 " 2173 ::= { optIfOTNPMIntervalEntry 10} 2175 optIfOTNPMIntervalESR OBJECT-TYPE 2176 SYNTAX Integer32 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 " 2181 The ratio of ES in available time to total seconds in available 2182 time during a fixed measurement interval. 2183 " 2184 ::= { optIfOTNPMIntervalEntry 11} 2186 optIfOTNPMIntervalSESR OBJECT-TYPE 2187 SYNTAX Integer32 2188 MAX-ACCESS read-only 2189 STATUS current 2190 DESCRIPTION 2191 " 2192 The ratio of SES in available time to total seconds in available 2193 time during a fixed measurement interval. 2194 " 2196 ::= { optIfOTNPMIntervalEntry 12} 2198 optIfOTNPMIntervalBBER OBJECT-TYPE 2199 SYNTAX Integer32 2200 MAX-ACCESS read-only 2201 STATUS current 2202 DESCRIPTION 2203 " 2204 The ratio of BBE in available time to total seconds in available 2205 time during a fixed measurement interval. 2206 " 2207 ::= { optIfOTNPMIntervalEntry 13} 2209 -- 2210 -- PM Current Day Entry 2211 -- 2212 optIfOTNPMCurrentDayTable OBJECT-TYPE 2213 SYNTAX SEQUENCE OF OptIfOTNPMCurrentDayEntry 2214 MAX-ACCESS not-accessible 2215 STATUS current 2216 DESCRIPTION 2217 " A Performance monitoring Current Day Table. 2218 " 2219 ::= {optIfOTNPMObjects 4} 2221 optIfOTNPMCurrentDayEntry OBJECT-TYPE 2222 SYNTAX OptIfOTNPMCurrentDayEntry 2223 MAX-ACCESS not-accessible 2224 STATUS current 2225 DESCRIPTION 2226 "A conceptual entry in the Near end or Far End performance 2227 monitoring Current day table for the type 2228 'optIfOTNPMCurrentDaySublayer' layer. 2229 " 2230 INDEX { ifIndex, optIfOTNPMCurrentDayType, optIfOTNPMCurrentDaySublayer, 2231 optIfOTNPMCurrentDayTCMLevel } 2232 ::= { optIfOTNPMCurrentDayTable 1 } 2234 OptIfOTNPMCurrentDayEntry ::= 2235 SEQUENCE { 2236 optIfOTNPMCurrentDayType OptIfOTNType, 2237 optIfOTNPMCurrentDayLayer OptIfOTNLayer, 2238 optIfOTNPMCurrentDayTCMLevel Unsigned32, 2239 optIfOTNPMNECurrentDaySuspectedFlag TruthValue, 2240 optIfOTNPMNECurrentDayFcs Integer32, 2241 optIfOTNPMNECurrentDayESs Integer32, 2242 optIfOTNPMNECurrentDaySESs Integer32, 2243 optIfOTNPMNECurrentDayUASs Integer32, 2244 optIfOTNPMNECurrentDayBBEs Integer32, 2245 optIfOTNPMNECurrentDayESR Integer32, 2246 optIfOTNPMNECurrentDaySESR Integer32, 2247 optIfOTNPMNECurrentDayBBER Integer32, 2248 } 2250 optIfOTNPMCurrentDayType OBJECT-TYPE 2251 SYNTAX OptIfOTNType 2252 MAX-ACCESS read-only 2253 STATUS current 2254 DESCRIPTION 2255 " 2256 This parameter indicates the parameters for the table are for 2257 the Near End or Far End performance data. 2258 1 - Near End 2259 2 - Far End 2260 " 2261 ::= { optIfOTNPMCurrentDayEntry 1} 2263 optIfOTNPMCurrentDaySublayer OBJECT-TYPE 2264 SYNTAX OptIfOTNLayer 2265 MAX-ACCESS read-only 2266 STATUS current 2267 DESCRIPTION 2268 " 2269 This parameter indicates the parameters for the table are for OTUk, 2270 ODUk, TCMn performance data. 2271 1 - OTUk 2272 2 - ODUk 2273 3 - TCM 2274 The ODUk/TCM sublayer PM is not related to the black link PM 2275 management, but since this is a common PM model for the ODU/TCM layer, 2276 we may include it here." 2277 ::= { optIfOTNPMCurrentDayEntry 2} 2279 optIfOTNPMCurrentDayTCMLevel OBJECT-TYPE 2280 SYNTAX Unsigned32 2281 MAX-ACCESS read-only 2282 STATUS current 2283 DESCRIPTION 2284 " 2285 This parameter indicates the TCM level (1-6) 2286 if the PM is of the type TCM. This will be 0 for OTUK/ODUK. 2287 " 2288 ::= { optIfOTNPMCurrentDayEntry 3} 2290 optIfOTNPMCurrentDaySuspectedFlag OBJECT-TYPE 2291 SYNTAX TruthValue 2292 MAX-ACCESS read-only 2293 STATUS current 2294 DESCRIPTION 2295 " 2296 If true, the data in this entry may be unreliable. 2297 " 2298 ::= { optIfOTNPMCurrentDayEntry 4} 2300 optIfOTNPMCurrentDayFcs OBJECT-TYPE 2301 SYNTAX Integer32 2302 MAX-ACCESS read-only 2303 STATUS current 2304 DESCRIPTION 2305 " 2306 Number of Failures occurred in an observation period. 2307 " 2308 ::= { optIfOTNPMCurrentDayEntry 5} 2310 optIfOTNPMCurrentDayESs OBJECT-TYPE 2311 SYNTAX Integer32 2312 MAX-ACCESS read-only 2313 STATUS current 2314 DESCRIPTION 2315 " The number of seconds which have an error. 2316 It is a one-second period in which one or more bits are in error 2317 or during which Loss of Signal (LOS) or Alarm Indication Signal 2318 (AIS) is detected. 2319 " 2320 ::= { optIfOTNPMCurrentDayEntry 6} 2322 optIfOTNPMCurrentDaySESs OBJECT-TYPE 2323 SYNTAX Integer32 2324 MAX-ACCESS read-only 2325 STATUS current 2326 DESCRIPTION 2327 " The number of seconds which have a severe error. 2328 It is a one-second period which has a bit-error ratio = 2329 1x10Eminus3 or during which Loss of Signal (LOS) or Alarm 2330 Indication Signal (AIS) is detected. 2331 " 2332 ::= { optIfOTNPMCurrentDayEntry 7} 2334 optIfOTNPMCurrentDayUASs OBJECT-TYPE 2335 SYNTAX Integer32 2336 MAX-ACCESS read-only 2337 STATUS current 2338 DESCRIPTION 2339 " It is the number of unavailable seconds in the cunrrent day. 2340 A period of unavailable time begins at the onset of ten 2341 consecutive SES events. These ten seconds are considered to be 2342 part of unavailable time. A new period of available time begins 2343 at the onset of ten consecutive non-SES events. These ten seconds 2344 are considered to be part of available time. 2345 " 2346 ::= { optIfOTNPMCurrentDayEntry 8} 2348 optIfOTNPMCurrentDayBBEs OBJECT-TYPE 2349 SYNTAX Integer32 2350 MAX-ACCESS read-only 2351 STATUS current 2352 DESCRIPTION 2353 " 2354 An errored block not occurring as part of an SES. 2355 " 2356 ::= { optIfOTNPMCurrentDayEntry 9} 2358 optIfOTNPMCurrentDayESR OBJECT-TYPE 2359 SYNTAX Integer32 2360 UNIT ".001" 2361 MAX-ACCESS read-only 2362 STATUS current 2363 DESCRIPTION 2364 " 2365 The ratio of ES in available time to total seconds in available 2366 time during a fixed measurement interval. 2367 " 2368 ::= { optIfOTNPMCurrentDayEntry 10} 2370 optIfOTNPMCurrentDaySESR OBJECT-TYPE 2371 SYNTAX Integer32 2372 MAX-ACCESS read-only 2373 STATUS current 2374 DESCRIPTION 2375 " 2376 The ratio of SES in available time to total seconds in available 2377 time during a fixed measurement interval. 2378 " 2379 ::= { optIfOTNPMCurrentDayEntry 11} 2381 optIfOTNPMCurrentDayBBER OBJECT-TYPE 2382 SYNTAX Integer32 2383 MAX-ACCESS read-only 2384 STATUS current 2385 DESCRIPTION 2386 " 2387 The ratio of BBE in available time to total seconds in available 2388 time during a fixed measurement interval. 2389 " 2390 ::= { optIfOTNPMCurrentDayEntry 12} 2392 -- 2393 -- PM Prev Day Entry 2394 -- 2395 optIfOTNPMPrevDayTable OBJECT-TYPE 2396 SYNTAX SEQUENCE OF OptIfOTNPMPrevDayEntry 2397 MAX-ACCESS not-accessible 2398 STATUS current 2399 DESCRIPTION 2400 "A Performance monitoring Previous Day Table. 2401 " 2402 ::= {optIfOTNPMObjects 5} 2404 optIfOTNPMPrevDayEntry OBJECT-TYPE 2405 SYNTAX OptIfOTNPMPrevDayEntry 2406 MAX-ACCESS not-accessible 2407 STATUS current 2408 DESCRIPTION 2409 "A conceptual entry in the Near end or Far End performance 2410 monitoring previous day table for the type 2411 'optIfOTNPMPrevDaySublayer' layer. 2412 " 2413 INDEX { ifIndex, optIfOTNPMPrevDayType , 2414 optIfOTNPMPrevDaySublayer, optIfOTNPMPrevDayTCMLevel } 2415 ::= { optIfOTNPMPrevDayTable 1 } 2417 OptIfOTNPMPrevDayEntry ::= 2418 SEQUENCE { 2419 optIfOTNPMPrevDayType OptIfOTNType, 2420 optIfOTNPMPrevDayLayer OptIfOTNLayer, 2421 optIfOTNPMPrevDayTCMLevel Unsigned32, 2422 optIfOTNPMNEPrevDaySuspectedFlag TruthValue, 2423 optIfOTNPMNEPrevDayFcs Integer32, 2424 optIfOTNPMNEPrevDayESs Integer32, 2425 optIfOTNPMNEPrevDaySESs Integer32, 2426 optIfOTNPMNEPrevDayUASs Integer32, 2427 optIfOTNPMNEPrevDayBBEs Integer32, 2428 optIfOTNPMNEPrevDayESR Integer32, 2429 optIfOTNPMNEPrevDaySESR Integer32, 2430 optIfOTNPMNEPrevDayBBER Integer32, 2431 } 2433 optIfOTNPMPrevDayType OBJECT-TYPE 2434 SYNTAX OptIfOTNType 2435 MAX-ACCESS read-only 2436 STATUS current 2437 DESCRIPTION 2438 " 2439 This parameter indicates the parameters for the table are for the 2440 Near End or Far End performance data. 2441 1 - Near End 2442 2 - Far End 2443 " 2444 ::= { optIfOTNPMPrevDayEntry 1} 2446 optIfOTNPMPrevDaySublayer OBJECT-TYPE 2447 SYNTAX OptIfOTNLayer 2448 MAX-ACCESS read-only 2449 STATUS current 2450 DESCRIPTION 2451 " 2452 This parameter indicates the parameters for the table are for OTUk, 2453 ODUk, TCMn performance data. 2454 1 - OTUk 2455 2 - ODUk 2456 3 - TCM 2457 The ODUk/TCM sublayer PM is not related to the black link PM 2458 management, but since this is a common PM model for the ODU/TCM 2459 layer, we may include it here." 2460 ::= { optIfOTNPMPrevDayEntry 2} 2462 optIfOTNPMPrevDayTCMLevel OBJECT-TYPE 2463 SYNTAX Unsigned32 2464 MAX-ACCESS read-only 2465 STATUS current 2466 DESCRIPTION 2467 " 2468 This parameter indicates the TCM level (1-6) 2469 if the PM is of the type TCM. 2470 " 2471 ::= { optIfOTNPMPrevDayEntry 3} 2473 optIfOTNPMPrevDaySuspectedFlag OBJECT-TYPE 2474 SYNTAX TruthValue 2475 MAX-ACCESS read-only 2476 STATUS current 2477 DESCRIPTION 2478 " 2479 If true, the data in this entry may be unreliable. 2481 " 2482 ::= { optIfOTNPMPrevDayEntry 4} 2484 optIfOTNPMPrevDayFcs OBJECT-TYPE 2485 SYNTAX Integer32 2486 MAX-ACCESS read-only 2487 STATUS current 2488 DESCRIPTION 2489 " 2490 Number of failures occurred in an observation period. 2491 " 2492 ::= { optIfOTNPMPrevDayEntry 5} 2494 optIfOTNPMPrevDayESs OBJECT-TYPE 2495 SYNTAX Integer32 2496 MAX-ACCESS read-only 2497 STATUS current 2498 DESCRIPTION 2499 " 2500 The number of seconds which have an error. 2501 It is a one-second period in which one or more bits are in error 2502 or during which Loss of Signal (LOS) or Alarm Indication Signal 2503 (AIS) is detected. 2504 " 2505 ::= { optIfOTNPMPrevDayEntry 6} 2507 optIfOTNPMPrevDaySESs OBJECT-TYPE 2508 SYNTAX Integer32 2509 MAX-ACCESS read-only 2510 STATUS current 2511 DESCRIPTION 2512 " The number of seconds which have a severe error. 2513 A severely errored second, is a one-second period which has 2514 a bit-error ratio = 1x10Eminus3 or during which Loss of Signal (LOS) 2515 or Alarm Indication Signal (AIS) is detected. 2516 " 2517 ::= { optIfOTNPMPrevDayEntry 7} 2519 optIfOTNPMPrevDayUASs OBJECT-TYPE 2520 SYNTAX Integer32 2521 MAX-ACCESS read-only 2522 STATUS current 2523 DESCRIPTION 2524 " It is the number of unavailable seconds in the previous day. 2525 A period of unavailable time begins at the onset of ten 2526 consecutive SES events. These ten seconds are considered to be 2527 part of unavailable time. A new period of available time begins 2528 at the onset of ten consecutive non-SES events. These ten seconds 2529 are considered to be part of available time. 2530 " 2531 ::= { optIfOTNPMPrevDayEntry 8} 2533 optIfOTNPMPrevDayBBEs OBJECT-TYPE 2534 SYNTAX Integer32 2535 MAX-ACCESS read-only 2536 STATUS current 2537 DESCRIPTION 2538 " 2539 An errored block not occurring as part of an SES. 2540 " 2541 ::= { optIfOTNPMPrevDayEntry 9} 2543 optIfOTNPMPrevDayESR OBJECT-TYPE 2544 SYNTAX Integer32 2545 MAX-ACCESS read-only 2546 STATUS current 2547 DESCRIPTION 2548 " 2549 The ratio of ES in available time to total seconds in available 2550 time during a fixed measurement interval. 2551 " 2552 ::= { optIfOTNPMPrevDayEntry 10} 2554 optIfOTNPMPrevDaySESR OBJECT-TYPE 2555 SYNTAX Integer32 2556 MAX-ACCESS read-only 2557 STATUS current 2558 DESCRIPTION 2559 " 2560 The ratio of SES in available time to total seconds in available 2561 time during a fixed measurement interval. 2562 " 2563 ::= { optIfOTNPMPrevDayEntry 11} 2565 optIfOTNPMPrevDayBBER OBJECT-TYPE 2566 SYNTAX Integer32 2567 MAX-ACCESS read-only 2568 STATUS current 2569 DESCRIPTION 2570 " 2571 The ratio of BBE in available time to total seconds in available 2572 time during a fixed measurement interval. 2573 " 2574 ::= { optIfOTNPMPrevDayEntry 12} 2576 -- 2577 -- OTN FEC PM Config Table 2578 -- 2579 optIfOTNPMFECConfigTable OBJECT-TYPE 2580 SYNTAX SEQUENCE OF OptIfOTNPMFECConfigEntry 2581 MAX-ACCESS not-accessible 2582 STATUS current 2583 DESCRIPTION 2584 "A table of performance monitoring FEC configuration. " 2585 ::= { optIfOTNPMObjects 6 } 2587 optIfOTNPMFECConfigEntry OBJECT-TYPE 2588 SYNTAX optIfOTNPMFECConfigEntry 2589 MAX-ACCESS not-accessible 2590 STATUS current 2591 DESCRIPTION 2592 " A conceptual entry in the performance monitoring FEC configuration 2593 layer." 2594 INDEX { ifIndex, optIfOTNPMFECConfigType } 2595 ::= { optIfOTNPMFECConfigTable 1 } 2597 OptIfOTNPMFECConfigEntry ::= 2598 SEQUENCE { 2599 optIfOTNPMFECConfigType OptIfOTNType, 2600 optIfOTNPMFECValidIntervals Integer32, 2601 optIfOTNPMOTNThresh15MinFECUnCorrectedWords Integer32, 2602 optIfOTNPMOTNThreshPreFECBERMantissa Integer32, 2603 optIfOTNPMOTNThreshPreFECBERExponent Integer32, 2604 } 2606 optIfOTNPMFECConfigType OBJECT-TYPE 2607 SYNTAX OptIfOTNType 2608 MAX-ACCESS read-only 2609 STATUS current 2610 DESCRIPTION 2611 " 2612 This parameter indicates the parameters for the table are for the 2613 Near End or Far End performance data. 2614 1 - Near End 2615 2 - Far End 2616 " 2617 ::= { optIfOTNPMFECConfigEntry 1} 2619 optIfOTNPMFECValidInterval OBJECT-TYPE 2620 SYNTAX Integer32 2621 MAX-ACCESS read-only 2622 STATUS current 2623 DESCRIPTION 2624 " 2625 The number of contiguous 15 minute intervals for which valid FEC 2626 PM data is available for the particular interface. 2627 " 2628 ::= {optIfOTNPMFECConfigEntry 2} 2630 optIfOTNPM15MinThreshFECUnCorrectedWords OBJECT-TYPE 2631 SYNTAX Integer32 2632 MAX-ACCESS read-only 2633 STATUS current 2634 DESCRIPTION 2635 " 2636 The number of Uncorrected words encountered by the interface within 2637 any given 15 minutes performance data collection period, which causes 2638 the SNMP agent to send optIf15MinThreshFECUnCorrectedWordsTCA. One 2639 notification will be sent per interval per interface. A value of `0' 2640 will disable the notification. 2641 " 2642 ::= {optIfOTNPMFECConfigEntry 3} 2644 optIfOTNPM15MinThreshPreFECBERMantissa OBJECT-TYPE 2645 SYNTAX Integer32 2646 MAX-ACCESS read-only 2647 STATUS current 2648 DESCRIPTION 2649 " 2650 The Pre FEC BER (mantissa) by the interface within any 2651 given 15 minutes performance data collection period, which causes the 2652 SNMP agent to send optIf15MinThreshPreFECBERTCA. One notification 2653 will be sent per interval per interface. A value of `0' will disable 2654 the notification. 2655 " 2656 ::= {optIfOTNPMFECConfigEntry 4} 2658 optIfOTNPM15MinThreshPreFECBERExponent OBJECT-TYPE 2659 SYNTAX Integer32 2660 MAX-ACCESS read-only 2661 STATUS current 2662 DESCRIPTION 2663 " 2664 The Pre FEC BER (exponent) by the interface within any 2665 given 15 minutes performance data collection period, which causes the 2666 SNMP agent to send optIf15MinThreshPreFECBERTCA. One notification 2667 will be sent per interval per interface. A value of `0' will disable 2668 the notification. 2669 " 2670 ::= {optIfOTNPMFECConfigEntry 5} 2672 -- 2673 -- FEC PM Table 2674 -- 2675 optIfOTNPMFECCurrentTable OBJECT-TYPE 2676 SYNTAX SEQUENCE OF OptIfOTNPMFECCurrentEntry 2677 MAX-ACCESS not-accessible 2678 STATUS current 2679 DESCRIPTION 2680 "A Performance monitoring FEC Current Table. 2681 " 2682 ::= {optIfOTNPMObjects 7} 2684 optIfOTNPMFECCurrentEntry OBJECT-TYPE 2685 SYNTAX OptIfOTNPMFECCurrentEntry 2686 MAX-ACCESS not-accessible 2687 STATUS current 2688 DESCRIPTION 2689 " A conceptual entry in the Near end or Far End performance 2690 monitoring FEC current table. 2691 " 2692 INDEX { ifIndex, optIfOTNPMFECCurrentType} 2693 ::= { optIfOTNPMFECCurrentTable 1 } 2695 OptIfOTNPMFECCurrentEntry ::= 2696 SEQUENCE { 2697 optIfOTNPMFECCurrentType OptIfOTNType, 2698 optIfOTNPMFECCurrentSuspectedFlag TruthValue, 2699 optIfOTNPMCurrentFECCorrectedErr Integer32, 2700 optIfOTNPMCurrentFECUncorrectedWords Integer32, 2701 optIfOTNPMCurrentFECBERMantissa Integer32, 2702 optIfOTNPMCurrentFECBERExponent Integer32, 2703 } 2705 optIfOTNPMFECCurrentType OBJECT-TYPE 2706 SYNTAX OptIfOTNType 2707 MAX-ACCESS read-only 2708 STATUS current 2709 DESCRIPTION 2710 " 2711 This parameter indicates the parameters for the table are for the 2712 Near End or Far End performance data. 2713 1 - Near End 2714 2 - Far End 2715 " 2716 ::= { optIfOTNPMFECCurrentEntry 1} 2718 optIfOTNPMFECCurrentSuspectedFlag OBJECT-TYPE 2719 SYNTAX TruthValue 2720 MAX-ACCESS read-only 2721 STATUS current 2722 DESCRIPTION 2723 " 2724 If true, the data in this entry may be unreliable. 2725 " 2726 ::= { optIfOTNPMFECCurrentEntry 2} 2728 optIfOTNPMCurrentFECCorrectedErr OBJECT-TYPE 2729 SYNTAX Integer32 2730 MAX-ACCESS read-only 2731 STATUS current 2732 DESCRIPTION 2733 " 2734 The number of bits corrected by the FEC are counted in the 2735 interval. 2736 " 2737 ::= { optIfOTNPMFECCurrentEntry 3} 2739 optIfOTNPMCurrentFECUncorrectedWords OBJECT-TYPE 2740 SYNTAX Integer32 2741 MAX-ACCESS read-only 2742 STATUS current 2743 DESCRIPTION 2744 " 2745 The number of un-corrected words by the FEC are counted over the 2746 interval. 2747 " 2748 ::= { optIfOTNPMFECCurrentEntry 4} 2750 optIfOTNPMCurrentFECBERMantissa OBJECT-TYPE 2751 SYNTAX Integer32 2752 MAX-ACCESS read-only 2753 STATUS current 2754 DESCRIPTION 2755 " 2756 The number of Errored bits at receiving side before the FEC 2757 function counted over one second .. mantisa. 2758 " 2759 ::= { optIfOTNPMFECCurrentEntry 5} 2761 optIfOTNPMCurrentFECBERExponent OBJECT-TYPE 2762 SYNTAX Integer32 2763 MAX-ACCESS read-only 2764 STATUS current 2765 DESCRIPTION 2766 " 2767 The number of Errored bits at receiving side before the FEC 2768 function counted over one second .. exponent (eg -1). 2769 " 2770 ::= { optIfOTNPMFECCurrentEntry 6} 2772 -- 2773 -- FEC PM Interval Table 2774 -- 2775 optIfOTNPMFECIntervalTable OBJECT-TYPE 2776 SYNTAX SEQUENCE OF OptIfOTNPMFECIntervalEntry 2777 MAX-ACCESS not-accessible 2778 STATUS current 2779 DESCRIPTION 2780 "A Performance monitoring FEC Interval Table. 2781 " 2782 ::= {optIfOTNPMObjects 8} 2784 optIfOTNPMFECIntervalEntry OBJECT-TYPE 2785 SYNTAX OptIfOTNPMFECIntervalEntry 2786 MAX-ACCESS not-accessible 2787 STATUS current 2788 DESCRIPTION 2789 "A conceptual entry in the Near end or Far End performance 2790 monitoring FEC interval table. 2791 " 2792 INDEX { ifIndex, optIfOTNPMIntervalType, optIfOTNPMFECIntervalNumber } 2793 ::= { optIfOTNPMFECIntervalTable 1 } 2795 OptIfOTNPMFECIntervalEntry ::= 2796 SEQUENCE { 2797 optIfOTNPMFECIntervalType OptIfOTNType, 2798 optIfOTNPMFECIntervalNumber OptIfIntervalNumber, 2799 optIfOTNPMFECIntervalSuspectedFlag TruthValue, 2800 optIfOTNPMIntervalFECCorrectedErr Integer32, 2801 optIfOTNPMIntervalFECUncorrectedErr Integer32, 2802 optIfOTNPMIntervalMinFECBERMantissa Integer32, 2803 optIfOTNPMIntervalMinFECBERExponent Integer32, 2804 optIfOTNPMIntervalMaxFECBERMantissa Integer32, 2805 optIfOTNPMIntervalMaxFECBERExponent Integer32, 2806 optIfOTNPMIntervalAvgFECBERMantissa Integer32, 2807 optIfOTNPMIntervalAvgFECBERExponent Integer32, 2808 } 2810 optIfOTNPMFECIntervalType OBJECT-TYPE 2811 SYNTAX OptIfOTNType 2812 MAX-ACCESS read-only 2813 STATUS current 2814 DESCRIPTION 2815 " 2816 This parameter indicates the parameters for the table are for the 2817 Near End or Far End performance data. 2818 1 - Near End 2819 2 - Far End 2820 " 2821 ::= { optIfOTNPMFECIntervalEntry 1} 2823 optIfOTNPMFECIntervalNumber OBJECT-TYPE 2824 SYNTAX OptIfIntervalNumber 2825 MAX-ACCESS read-only 2826 STATUS current 2827 DESCRIPTION 2828 " 2829 A number between 1 and 96, where 1 is the most 2830 recently completed 15 minute interval and 96 is 2831 the 15 minutes interval completed 23 hours and 45 2832 minutes prior to interval 1. 2833 " 2834 ::= { optIfOTNPMFECIntervalEntry 2} 2836 optIfOTNPMFECIntervalSuspectedFlag OBJECT-TYPE 2837 SYNTAX TruthValue 2838 MAX-ACCESS read-only 2839 STATUS current 2840 DESCRIPTION 2841 " 2842 If true, the data in this entry may be unreliable. 2843 " 2844 ::= { optIfOTNPMFECIntervalEntry 3} 2846 optIfOTNPMIntervalFECCorrectedErr OBJECT-TYPE 2847 SYNTAX Integer32 2848 MAX-ACCESS read-only 2849 STATUS current 2850 DESCRIPTION 2851 " 2852 The number of bits corrected by the FEC are counted in the 2853 interval. 2854 " 2855 ::= { optIfOTNPMFECIntervalEntry 4} 2857 optIfOTNPMIntervalFECUncorrectedWords OBJECT-TYPE 2858 SYNTAX Integer32 2859 MAX-ACCESS read-only 2860 STATUS current 2861 DESCRIPTION 2862 " 2863 The number of words un-corrected words by the FEC are counted over 2864 the interval. 2865 " 2866 ::= { optIfOTNPMFECIntervalEntry 5} 2868 optIfOTNPMIntervalMinFECBERMantissa OBJECT-TYPE 2869 SYNTAX Integer32 2870 MAX-ACCESS read-only 2871 STATUS current 2872 DESCRIPTION 2873 " 2874 The minimun bit error rate at receiving side before the FEC 2875 function counted over one second .. mantissa. This is the minimum Pre 2876 FEC BER in the current 24hour period. 2877 " 2878 ::= { optIfOTNPMFECIntervalEntry 6} 2880 optIfOTNPMIntervalMinFECBERExponent OBJECT-TYPE 2881 SYNTAX Integer32 2882 MAX-ACCESS read-only 2883 STATUS current 2884 DESCRIPTION 2885 " 2886 The minimun bit error rate at receiving side before the FEC 2887 function counted over one second .. exponent. This is the minimum Pre 2888 FEC BER in the current 24hour period. 2889 " 2890 ::= { optIfOTNPMFECIntervalEntry 7} 2892 optIfOTNPMIntervalMaxFECBERMantissa OBJECT-TYPE 2893 SYNTAX Integer32 2894 MAX-ACCESS read-only 2895 STATUS current 2896 DESCRIPTION 2897 " 2898 The maximun bit error rate at receiving side before the FEC 2899 function counted over one second .. mantissa. This is the maximum Pre 2900 FEC BER in the current 24hour period. 2901 " 2902 ::= { optIfOTNPMFECIntervalEntry 8} 2904 optIfOTNPMCurrentMaxFECBERExponent OBJECT-TYPE 2905 SYNTAX Integer32 2906 MAX-ACCESS read-only 2907 STATUS current 2908 DESCRIPTION 2909 " 2910 The maximun bit error rate at receiving side before the FEC 2911 function counted over one second .. exponent. This is the maximum Pre 2912 FEC BER in the current 24hour period. 2913 " 2914 ::= { optIfOTNPMFECIntervalEntry 9} 2916 optIfOTNPMIntervalAvgFECBERMantissa OBJECT-TYPE 2917 SYNTAX Integer32 2918 MAX-ACCESS read-only 2919 STATUS current 2920 DESCRIPTION 2921 " 2922 The average bit error rate at receiving side before the FEC 2923 function counted over one second .. mantissa. This is the average Pre 2924 FEC BER in the current 24hour period. 2925 " 2926 ::= { optIfOTNPMFECIntervalEntry 10} 2928 optIfOTNPMIntervalAvgFECBERExponent OBJECT-TYPE 2929 SYNTAX Integer32 2930 MAX-ACCESS read-only 2931 STATUS current 2932 DESCRIPTION 2933 " 2934 The average bit error rate at receiving side before the FEC 2935 function counted over one second .. exponent. This is the average Pre 2936 FEC BER in the current 24hour period. 2937 " 2938 ::= { optIfOTNPMFECIntervalEntry 11} 2939 -- 2940 -- FEC PM Current Day day Table 2941 -- 2942 optIfOTNPMFECCurrentDayTable OBJECT-TYPE 2943 SYNTAX SEQUENCE OF OptIfOTNPMFECCurrentDayEntry 2944 MAX-ACCESS not-accessible 2945 STATUS current 2946 DESCRIPTION 2947 "A Performance monitoring FEC current day table. 2948 " 2949 ::= {optIfOTNPMObjects 9} 2951 optIfOTNPMFECCurrentDayEntry OBJECT-TYPE 2952 SYNTAX OptIfOTNPMFECCurrentDayEntry 2953 MAX-ACCESS not-accessible 2954 STATUS current 2955 DESCRIPTION 2956 "A conceptual entry in the Near end or Far End performance 2957 monitoring FEC current day table. 2958 " 2960 INDEX { ifIndex, optIfOTNPMFECCurrentDayType } 2961 ::= { optIfOTNPMFECCurrentDayTable 1 } 2963 OptIfOTNPMFECCurrentDayEntry ::= 2964 SEQUENCE { 2965 optIfOTNPMFECCurrentDayType OptIfOTNType, 2966 optIfOTNPMFECCurrentDaySuspectedFlag TruthValue, 2967 optIfOTNPMCurrentDayFECCorrectedErr Integer32, 2968 optIfOTNPMCurrentDayFECUncorrectedWords Integer32, 2969 optIfOTNPMCurrentDayMinFECBERMantissa Integer32, 2970 optIfOTNPMCurrentDayMinFECBERExponent Integer32, 2971 optIfOTNPMCurrentDayMaxFECBERMantissa Integer32, 2972 optIfOTNPMCurrentDayMaxFECBERExponent Integer32, 2973 optIfOTNPMCurrentDayAvgFECBERMantissa Integer32, 2974 optIfOTNPMCurrentDayAvgFECBERExponent Integer32, 2975 } 2977 optIfOTNPMFECCurrentDayType OBJECT-TYPE 2978 SYNTAX OptIfOTNType 2979 MAX-ACCESS read-only 2980 STATUS current 2981 DESCRIPTION 2982 " 2983 This parameter indicates the parameters for the table are for the 2984 Near End or Far End performance data. 2985 1 - Near End 2986 2 - Far End 2987 " 2988 ::= { optIfOTNPMFECCurrentDayEntry 1} 2990 optIfOTNPMFECCurrentDaySuspectedFlag OBJECT-TYPE 2991 SYNTAX TruthValue 2992 MAX-ACCESS read-only 2993 STATUS current 2994 DESCRIPTION 2995 " 2996 If true, the data in this entry may be unreliable. 2997 " 2998 ::= { optIfOTNPMFECCurrentDayEntry 2} 3000 optIfOTNPMCurrentDayFECCorrectedErr OBJECT-TYPE 3001 SYNTAX Integer32 3002 MAX-ACCESS read-only 3003 STATUS current 3004 DESCRIPTION 3005 " 3006 The number of bits corrected by the FEC are counted in the 3007 interval. 3008 " 3009 ::= { optIfOTNPMFECCurrentDayEntry 3} 3011 optIfOTNPMCurrentDayFECUncorrectedWords OBJECT-TYPE 3012 SYNTAX Integer32 3013 MAX-ACCESS read-only 3014 STATUS current 3015 DESCRIPTION 3016 " 3017 The number of words un-corrected by the FEC are counted over the 3018 Day. 3019 " 3020 ::= { optIfOTNPMFECCurrentDayEntry 4} 3022 optIfOTNPMCurrentDayMinFECBERMantissa OBJECT-TYPE 3023 SYNTAX Integer32 3024 MAX-ACCESS read-only 3025 STATUS current 3026 DESCRIPTION 3027 " 3028 The minimun bit error rate at receiving side before the FEC 3029 function counted over one second .. mantissa. This is the minimum 3030 PreFEC BER in the current 24hour period. 3031 " 3032 ::= { optIfOTNPMFECCurrentDayEntry 5} 3034 optIfOTNPMCurrentDayMinFECBERExponent OBJECT-TYPE 3035 SYNTAX Integer32 3036 MAX-ACCESS read-only 3037 STATUS current 3038 DESCRIPTION 3039 " 3040 The minimun bit error rate at receiving side before the FEC 3041 function counted over one second .. exponent. This is the minimum 3042 PreFEC BER in the current 24hour period. 3043 " 3044 ::= { optIfOTNPMFECCurrentDayEntry 6} 3046 optIfOTNPMCurrentDayMaxFECBERMantissa OBJECT-TYPE 3047 SYNTAX Integer32 3048 MAX-ACCESS read-only 3049 STATUS current 3050 DESCRIPTION 3051 " 3052 The maximun bit error rate at receiving side before the FEC 3053 function counted over one second .. mantissa. This is the maximum 3054 PreFEC BER in the current 24hour period. 3056 " 3057 ::= { optIfOTNPMFECCurrentDayEntry 7} 3059 optIfOTNPMCurrentDayMaxFECBERExponent OBJECT-TYPE 3060 SYNTAX Integer32 3061 MAX-ACCESS read-only 3062 STATUS current 3063 DESCRIPTION 3064 " 3065 The maximun bit error rate at receiving side before the FEC 3066 function counted over one second .. exponent. This is the maximum 3067 PreFEC BER in the current 24hour period.. 3068 " 3069 ::= { optIfOTNPMFECCurrentDayEntry 8} 3071 optIfOTNPMCurrentDayAvgFECBERMantissa OBJECT-TYPE 3072 SYNTAX Integer32 3073 MAX-ACCESS read-only 3074 STATUS current 3075 DESCRIPTION 3076 " 3077 The average bit error rate at receiving side before the FEC 3078 function counted over one second .. mantissa. This is the average 3079 PreFEC BER in the current 24hour period. . 3080 " 3081 ::= { optIfOTNPMFECCurrentDayEntry 9} 3083 optIfOTNPMCurrentdayAvgFECBERExponent OBJECT-TYPE 3084 SYNTAX Integer32 3085 MAX-ACCESS read-only 3086 STATUS current 3087 DESCRIPTION 3088 " 3089 The average bit error rate at receiving side before the FEC 3090 function counted over one second .. exponent. This is the average 3091 PreFEC BER in the current 24hour period. 3092 " 3093 ::= { optIfOTNPMFECCurrentDayEntry 10} 3094 -- 3095 -- FEC PM Prev day Table 3096 -- 3097 optIfOTNPMFECPrevDayTable OBJECT-TYPE 3098 SYNTAX SEQUENCE OF OptIfOTNPMFECPrevDayEntry 3099 MAX-ACCESS not-accessible 3100 STATUS current 3101 DESCRIPTION 3102 "A Performance monitoring FEC previous day table. 3103 " 3105 ::= {optIfOTNPMObjects 10} 3107 optIfOTNPMFECPrevDayEntry OBJECT-TYPE 3108 SYNTAX OptIfOTNPMFECPrevDayEntry 3109 MAX-ACCESS not-accessible 3110 STATUS current 3111 DESCRIPTION 3112 "A conceptual entry in the Near end or Far End performance 3113 monitoring FEC previous day table 3114 " 3115 INDEX { ifIndex, optIfOTNPMFECPrevDayType } 3116 ::= { optIfOTNPMFECPrevDayTable 1 } 3118 OptIfOTNPMFECPrevDayEntry ::= 3119 SEQUENCE { 3120 optIfOTNPMFECPrevDayType OptIfOTNType, 3121 optIfOTNPMFECPrevDaySuspectedFlag TruthValue, 3122 optIfOTNPMPrevDayFECCorrectedErr Integer32, 3123 optIfOTNPMPrevDayFECUncorrectedWords Integer32, 3124 optIfOTNPMPrevDayMinFECBERMantissa Integer32, 3125 optIfOTNPMPrevDayMinFECBERExponent Integer32, 3126 optIfOTNPMPrevDayMaxFECBERMantissa Integer32, 3127 optIfOTNPMPrevDayMaxFECBERExponent Integer32, 3128 optIfOTNPMPrevDayAvgFECBERMantissa Integer32, 3129 optIfOTNPMPrevDayAvgFECBERExponent Integer32, 3130 } 3132 optIfOTNPMFECPrevDayType OBJECT-TYPE 3133 SYNTAX OptIfOTNType 3134 MAX-ACCESS read-only 3135 STATUS current 3136 DESCRIPTION 3137 " 3138 This parameter indicates the parameters for the table are for the 3139 Near End or Far End performance data. 3140 1 - Near End 3141 2 - Far End 3142 " 3143 ::= { optIfOTNPMFECPrevDayEntry 1} 3145 optIfOTNPMFECPrevDaySuspectedFlag OBJECT-TYPE 3146 SYNTAX TruthValue 3147 MAX-ACCESS read-only 3148 STATUS current 3149 DESCRIPTION 3150 " 3151 If true, the data in this entry may be unreliable. 3153 " 3154 ::= { optIfOTNPMFECPrevDayEntry 2} 3156 optIfOTNPMPrevDayFECCorrectedErr OBJECT-TYPE 3157 SYNTAX Integer32 3158 MAX-ACCESS read-only 3159 STATUS current 3160 DESCRIPTION 3161 " 3162 The number of bits corrected by the FEC are counted in the 3163 previous day. 3164 " 3165 ::= { optIfOTNPMFECPrevDayEntry 3} 3167 optIfOTNPMPrevDayFECUncorrectedWords OBJECT-TYPE 3168 SYNTAX Integer32 3169 MAX-ACCESS read-only 3170 STATUS current 3171 DESCRIPTION 3172 " 3173 The number of un-corrected words by the FEC are counted over the 3174 previous Day. 3175 " 3176 ::= { optIfOTNPMFECPrevDayEntry 4} 3178 optIfOTNPMPrevDayMinFECBERMantissa OBJECT-TYPE 3179 SYNTAX Integer32 3180 MAX-ACCESS read-only 3181 STATUS current 3182 DESCRIPTION 3183 " 3184 The maximun bit error rate at receiving side before the FEC 3185 function counted over one second .. mantissa. This is the maximum Pre 3186 FEC BER in the previous 24hour period. 3187 " 3188 ::= { optIfOTNPMFECPrevDayEntry 5} 3190 optIfOTNPMPrevDayMinFECBERExponent OBJECT-TYPE 3191 SYNTAX Integer32 3192 MAX-ACCESS read-only 3193 STATUS current 3194 DESCRIPTION 3195 " 3196 The minimun bit error rate at receiving side before the FEC 3197 function counted over one second .. exponent. This is the maximum Pre 3198 FEC BER in the previous 24hour period 3199 " 3200 ::= { optIfOTNPMFECPrevDayEntry 6} 3202 optIfOTNPMPrevDayMaxFECBERMantissa OBJECT-TYPE 3203 SYNTAX Integer32 3204 MAX-ACCESS read-only 3205 STATUS current 3206 DESCRIPTION 3207 " 3208 The maximun bit error rate at receiving side before the FEC 3209 function counted over one second .. mantissa. This is the maximum Pre 3210 FEC BER in the previous 24hour period (mantissa). 3211 " 3212 ::= { optIfOTNPMFECPrevDayEntry 7} 3214 optIfOTNPMPrevDayMaxFECBERExponent OBJECT-TYPE 3215 SYNTAX Integer32 3216 MAX-ACCESS read-only 3217 STATUS current 3218 DESCRIPTION 3219 " 3220 The maximun bit error rate at receiving side before the FEC 3221 function counted over one second .. exponent (eg -3). 3222 This is the maximum Pre FEC BER in the previous 24hour period. 3223 " 3224 ::= { optIfOTNPMFECPrevDayEntry 8} 3226 optIfOTNPMPrevDayAvgFECBERMantissa OBJECT-TYPE 3227 SYNTAX Integer32 3228 MAX-ACCESS read-only 3229 STATUS current 3230 DESCRIPTION 3231 " 3232 The average bit error rate at receiving side before the FEC 3233 function counted over one second .. mantissa. This is the average Pre 3234 FEC BER during the previous 24hour period (mantissa). 3235 " 3236 ::= { optIfOTNPMFECPrevDayEntry 9} 3238 optIfOTNPMPrevdayAvgFECBERExponent OBJECT-TYPE 3239 SYNTAX Integer32 3240 MAX-ACCESS read-only 3241 STATUS current 3242 DESCRIPTION 3243 " 3244 The average bit error rate at receiving side before the FEC 3245 function counted over one second .. exponent (eg -3). 3246 This is the average Pre FEC BER during the previous 24hour period. 3247 " 3248 ::= { optIfOTNPMFECPrevDayEntry 10} 3250 -- 3251 -- OTN Alarm Table 3252 -- 3253 optIfOTNAlarmTable OBJECT-TYPE 3254 SYNTAX SEQUENCE OF OptIfOTNAlarmEntry 3255 MAX-ACCESS not-accessible 3256 STATUS current 3257 DESCRIPTION 3258 "A table of alarm entries." 3260 ::= { optIfOTNAlarm 1 } 3262 optIfOTNAlarmEntry OBJECT-TYPE 3263 SYNTAX OptIfOTNAlarmEntry 3264 MAX-ACCESS not-accessible 3265 STATUS current 3266 DESCRIPTION 3267 "A conceptual entry in the alarm table." 3268 INDEX { ifIndex, optIfOTNAlarmIndex } 3269 ::= { optIfOTNAlarmTable 1 } 3271 OptIfOTNAlarmEntry ::= SEQUENCE { 3272 optIfOTNAlarmIndex Unsigned32, 3273 optIfOTNAlarmSublayer OptIfOTNSublayer, 3274 optIfOTNAlarmTCMLevel, Unsigned32, 3275 optIfOTNAlarmType Unsigned32, 3276 optIfOTNAlarmDate DateAndTime, 3277 optIfOTNAlarmStatus TruthValue, 3278 } 3280 optIfOTNAlarmIndex OBJECT-TYPE 3281 SYNTAX Unsigned32 3282 MAX-ACCESS read-only 3283 STATUS current 3284 DESCRIPTION 3285 "An index that uniquely identifies an entry in the 3286 alarm table." 3287 ::= { optIfOTNAlarmEntry 1 } 3289 optIfOTNAlarmSublayer OBJECT-TYPE 3290 SYNTAX OptIfOTNSublayer 3291 MAX-ACCESS read-only 3292 STATUS current 3293 DESCRIPTION 3294 "This specifies which sublayer this alarm is for." 3295 ::= { optIfOTNAlarmEntry 2 } 3297 optIfOTNAlarmTCMLevel OBJECT-TYPE 3298 SYNTAX Unsigned32 3299 MAX-ACCESS read-only 3300 STATUS current 3301 DESCRIPTION 3302 "TCM level 1-6 of the alarm. It will be 0 if alarm sublayer is 3303 OCh, OTUk or ODUk." 3304 ::= { optIfOTNAlarmEntry 3 } 3306 optIfOTNAlarmType OBJECT-TYPE 3307 SYNTAX Unsigned32 3308 MAX-ACCESS read-only 3309 STATUS current 3310 DESCRIPTION 3311 "This specifies the type of alarm of the sublayer 3312 'optIfOTNAlarmSublayer' ." 3313 ::= { optIfOTNAlarmEntry 4 } 3315 optIfOTNAlarmDate OBJECT-TYPE 3316 SYNTAX DateAndTime 3317 MAX-ACCESS read-only 3318 STATUS current 3319 DESCRIPTION 3320 "This specifies the date and time when this alarm occurred." 3321 ::= { optIfOTNAlarmEntry 5 } 3323 optIfOTNAlarmStatus OBJECT-TYPE 3324 SYNTAX TruthValue 3325 MAX-ACCESS read-only 3326 STATUS current 3327 DESCRIPTION 3328 "This specifies the state of the alarm -- cleared(0) or set(1) ." 3329 ::= { optIfOTNAlarmEntry 6 } 3331 -- 3332 -- OTN Notifications 3333 -- 3335 optIfOTNAlarmSet NOTIFICATION-TYPE 3336 OBJECTS { optIfOTNAlarmSublayer, 3337 optIfOTNAlarmTCMLevel, 3338 optIfOTNAlarmType, 3339 optIfOTNAlarmDate } 3340 STATUS current 3341 DESCRIPTION 3342 "Notification of a recently set OTN alarm of Sublayer 3343 and Type." 3344 ::= { optIfOTNNotifications 1 } 3346 optIfOTNAlarmClear NOTIFICATION-TYPE 3347 OBJECTS { optIfOTNAlarmSublayer, 3348 optIfOTNAlarmTCMLevel, 3349 optIfOTNAlarmType, 3350 optIfOTNAlarmDate } 3351 STATUS current 3352 DESCRIPTION 3353 "Notification of a recently clear OTN alarm of Sublayer 3354 and Type." 3355 ::= { optIfOTNNotifications 2 } 3357 7. Relationship to Other MIB Modules 3359 7.1. Relationship to the [TEMPLATE TODO] MIB 3361 7.2. MIB modules required for IMPORTS 3363 8. Definitions 3365 [TEMPLATE TODO]: put your valid MIB module here. 3366 A list of tools that can help automate the process of 3367 checking MIB definitions can be found at 3368 http://www.ops.ietf.org/mib-review-tools.html 3370 9. Security Considerations 3372 There are a number of management objects defined in this MIB module 3373 with a MAX-ACCESS clause of read-write and/or read-create. Such 3374 objects may be considered sensitive or vulnerable in some network 3375 environments. The support for SET operations in a non-secure 3376 environment without proper protection can have a negative effect on 3377 network operations. These are the tables and objects and their 3378 sensitivity/vulnerability: 3380 o 3382 Some of the readable objects in this MIB module (i.e., objects with a 3383 MAX-ACCESS other than not-accessible) may be considered sensitive or 3384 vulnerable in some network environments. It is thus important to 3385 control even GET and/or NOTIFY access to these objects and possibly 3386 to even encrypt the values of these objects when sending them over 3387 the network via SNMP. 3389 SNMP versions prior to SNMPv3 did not include adequate security. 3390 Even if the network itself is secure (for example by using IPsec), 3391 even then, there is no control as to who on the secure network is 3392 allowed to access and GET/SET (read/change/create/delete) the objects 3393 in this MIB module. 3395 It is RECOMMENDED that implementers consider the security features as 3396 provided by the SNMPv3 framework (see [RFC3410], section 8), 3397 including full support for the SNMPv3 cryptographic mechanisms (for 3398 authentication and privacy). 3400 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3401 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3402 enable cryptographic security. It is then a customer/operator 3403 responsibility to ensure that the SNMP entity giving access to an 3404 instance of this MIB module is properly configured to give access to 3405 the objects only to those principals (users) that have legitimate 3406 rights to indeed GET or SET (change/create/delete) them. 3408 10. IANA Considerations 3410 Option #1: 3412 The MIB module in this document uses the following IANA-assigned 3413 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 3415 Descriptor OBJECT IDENTIFIER value 3416 ---------- ----------------------- 3418 sampleMIB { mib-2 XXX } 3420 Option #2: 3422 Editor's Note (to be removed prior to publication): the IANA is 3423 requested to assign a value for "XXX" under the 'mib-2' subtree and 3424 to record the assignment in the SMI Numbers registry. When the 3425 assignment has been made, the RFC Editor is asked to replace "XXX" 3426 (here and in the MIB module) with the assigned value and to remove 3427 this note. 3429 Note well: prior to official assignment by the IANA, an internet 3430 draft MUST use placeholders (such as "XXX" above) rather than actual 3431 numbers. See RFC4181 Section 4.5 for an example of how this is done 3432 in an internet draft MIB module. 3434 Option #3: 3436 This memo includes no request to IANA. 3438 11. Contributors 3440 Arnold Mattheus 3441 Deutsche Telekom 3442 Darmstadt 3443 Germany 3444 email a.mattheus@telekom.de 3446 Manuel Paul 3447 Deutsche Telekom 3448 Berlin 3449 Germany 3450 email Manuel.Paul@telekom.de 3452 Frank Luennemann 3453 Deutsche Telekom 3454 Munster 3455 Germany 3456 email Frank.Luennemann@telekom.de 3458 Najam Saquib 3459 Cisco 3460 Ludwig-Erhard-Strasse 3 3461 ESCHBORN, HESSEN 65760 3462 GERMANY 3463 email nasaquib@cisco.com 3465 Walid Wakim 3466 Cisco 3467 9501 Technology Blvd 3468 ROSEMONT, ILLINOIS 60018 3469 UNITED STATES 3470 email wwakim@cisco.com 3472 Ori Gerstel 3473 Cisco 3474 32 HaMelacha St., (HaSharon Bldg) 3475 SOUTH NETANYA, HAMERKAZ 42504 3476 ISRAEL 3477 email ogerstel@cisco.com 3479 12. References 3480 12.1. Normative References 3482 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3483 MIB", RFC 2863, June 2000. 3485 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3486 Requirement Levels", BCP 14, RFC 2119, March 1997. 3488 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3489 Schoenwaelder, Ed., "Structure of Management Information 3490 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3492 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3493 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3494 STD 58, RFC 2579, April 1999. 3496 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3497 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3498 April 1999. 3500 [RFC3591] Lam, H-K., Stewart, M., and A. Huynh, "Definitions of 3501 Managed Objects for the Optical Interface Type", RFC 3591, 3502 September 2003. 3504 [ITU.G698.2] 3505 International Telecommunications Union, "Amplified 3506 multichannel dense wavelength division multiplexing 3507 applications with single channel optical interfaces", ITU- 3508 T Recommendation G.698.2, November 2009. 3510 [ITU.G709] 3511 International Telecommunications Union, "Interface for the 3512 Optical Transport Network (OTN)", ITU-T Recommendation 3513 G.709, March 2003. 3515 [ITU.G872] 3516 International Telecommunications Union, "Architecture of 3517 optical transport networks", ITU-T Recommendation G.872, 3518 November 2001. 3520 [ITU.G798] 3521 International Telecommunications Union, "Characteristics 3522 of optical transport network hierarchy equipment 3523 functional blocks", ITU-T Recommendation G.798, 3524 October 2010. 3526 [ITU.G874] 3527 International Telecommunications Union, "Management 3528 aspects of optical transport network elements", ITU- 3529 T Recommendation G.874, July 2010. 3531 [ITU.G874.1] 3532 International Telecommunications Union, "Optical transport 3533 network (OTN): Protocol-neutral management information 3534 model for the network element view", ITU-T Recommendation 3535 G.874.1, January 2002. 3537 [ITU.G959.1] 3538 International Telecommunications Union, "Optical transport 3539 network physical layer interfaces", ITU-T Recommendation 3540 G.959.1, November 2009. 3542 [ITU.G826] 3543 International Telecommunications Union, "End-to-end error 3544 performance parameters and objectives for international, 3545 constant bit-rate digital paths and connections", ITU- 3546 T Recommendation G.826, November 2009. 3548 [ITU.G8201] 3549 International Telecommunications Union, "Error performance 3550 parameters and objectives for multi-operator international 3551 paths within the Optical Transport Network (OTN)", ITU- 3552 T Recommendation G.8201, September 2003. 3554 [ITU.G694.1] 3555 International Telecommunications Union, "Spectral grids 3556 for WDM applications: DWDM frequency grid", ITU- 3557 T Recommendation G.694.1, June 2002. 3559 [ITU.G7710] 3560 International Telecommunications Union, "Common equipment 3561 management function requirements", ITU-T Recommendation 3562 G.7710, May 2008. 3564 12.2. Informative References 3566 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3567 "Introduction and Applicability Statements for Internet- 3568 Standard Management Framework", RFC 3410, December 2002. 3570 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 3571 June 1999. 3573 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB 3574 Documents", BCP 111, RFC 4181, September 2005. 3576 [I-D.kunze-g-698-2-management-control-framework] 3577 Kunze, R., "A framework for Management and Control of 3578 optical interfaces supporting G.698.2", 3579 draft-kunze-g-698-2-management-control-framework-00 (work 3580 in progress), July 2011. 3582 [RFC4054] Strand, J. and A. Chiu, "Impairments and Other Constraints 3583 on Optical Layer Routing", RFC 4054, May 2005. 3585 Appendix A. Change Log 3587 This optional section should be removed before the internet draft is 3588 submitted to the IESG for publication as an RFC. 3590 Note to RFC Editor: please remove this appendix before publication as 3591 an RFC. 3593 Appendix B. Open Issues 3595 Note to RFC Editor: please remove this appendix before publication as 3596 an RFC. 3598 Authors' Addresses 3600 Gabriele Galimberti (editor) 3601 Cisco 3602 Via Philips,12 3603 20052 - Monza 3604 Italy 3606 Phone: +390392091462 3607 Email: ggalimbe@cisco.com 3609 Ruediger Kunze (editor) 3610 Deutsche Telekom 3611 Dddd, xx 3612 Berlin 3613 Germany 3615 Phone: +49xxxxxxxxxx 3616 Email: RKunze@telekom.de 3617 Hing-Kam Lam (editor) 3618 Alcatel-Lucent 3619 600-700 Mountain Avenue, Murray Hill 3620 New Jersey, 07974 3621 USA 3623 Phone: +19085820672 3624 Email: kam.lam@alcatel-lucent.com 3626 Dharini Hiremagalur (editor) 3627 Juniper 3628 1194 N Mathilda Avenue 3629 Sunnyvale - 94089 California 3630 USA 3632 Phone: +1408 3633 Email: dharinih@juniper.net