Nortel-MsCarrier-MscPassport-LogicalProcessorMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of mscLp components.

A single entry in the table represents a single mscLp component.

This variable is used as the basis for SNMP naming of mscLp components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLp tables.

This variable represents the index for the mscLp tables.

This entry controls the addition and deletion of mscLpDS3 components.

A single entry in the table represents a single mscLpDS3 component.

This variable is used as the basis for SNMP naming of mscLpDS3 components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3 tables.

This variable represents the index for the mscLpDS3 tables.

This entry controls the addition and deletion of mscLpDS3Test components.

A single entry in the table represents a single mscLpDS3Test component.

This variable is used as the basis for SNMP naming of mscLpDS3Test components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3Test tables.

This variable represents the index for the mscLpDS3Test tables.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS3TestStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains all of the operational data for a Test component.

An entry in the mscLpDS3TestSetupTable.

This attribute records the purpose of the test so that the test results can be associated and properly analyzed.

This attribute is the type of test to be run. The available test types include the following: card test sets up an internal loop on the board and runs a bit error rate test. manual test assumes the line is looped back externally and a bit error rate test is performed. localLoop test loops back the local modem and performs a bit error rate test. remoteLoop test loops back the remote modem (or CSU) and performs a bit error rate test. externalLoop test loops back the line to the far end. payloadLoop test only loops back the payload data received from the incoming line. remoteLoopThisTrib loops this particular tributary back at the far end, using services provided by the parent. v54RemoteLoop initiates a V.54 Remote Loopback test. pn127RemoteLoop initiates a PN127 Remote Loopback test. Note that not all test types are not supported by all function processors. Enumeration: 'externalLoop': 4, 'pn127RemoteLoop': 8, 'payloadLoop': 5, 'manual': 1, 'remoteLoop': 3, 'v54RemoteLoop': 7, 'remoteLoopThisTrib': 6, 'localLoop': 2, 'card': 0.

This attribute defines the size of the test data frames in number of bytes.

This attribute defines the type of data pattern generation to use. The following lists the available pattern types: ccitt32kBitPattern is a pseudo-random sequence of 32 kbit. ccitt8MBitPattern is a pseudo-random sequence of 8Mbit. customizedPattern is the pattern defined in the customizedPattern attribute. Enumeration: 'ccitt32kBitPattern': 0, 'customizedPattern': 2, 'ccitt8MBitPattern': 1.

This attribute allows a customized 32 bit pattern to be defined for use in the test data frames. This attribute is used when the attribute frmPatternType is set to CustomizedPattern. Note that a 55 hex pattern is an alternating 1 and 0 pattern.

This attribute specifies the time delay (in seconds) between when the test expects the loop to have been set up, to when the test data actually starts to be transmitted. This attribute is to accommodate some non-standard equipment that requires extra time for setting up a requested loop. This attribute is ignored when the test type is set to externalLoop.

This attribute defines the interval (in minutes) between which interim test results are to be displayed. Results are displayed at the operator console at which the test was started. When the test type is set to externalLoop, this attribute is ignored. There will be no display of results if displayInterval is set to 0. This attribute can be changed anytime.

This attribute is the duration (in minutes) that test data will be transmitted. In the case of an externalLoop, this is the time that the loop is in effect. Note that dataStartDelay does not apply to the externalLoop.

This group contains all the statistics related attributes of the Test component.

An entry in the mscLpDS3TestResultsTable.

This attribute is the number of minutes elapsed since the test started for an externalLoop test. For a data test, this is the time since test data was first transmitted.

This attribute is the number of minutes remaining before the test is to be stopped according to the duration attribute.

This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values. Enumeration: 'patternSyncFailed': 7, 'unknown': 2, 'neverStarted': 3, 'hardwareReconfigured': 5, 'loopCodeSyncFailed': 6, 'stoppedByOperator': 1, 'testTimeExpired': 0, 'testRunning': 4, 'patternSyncLost': 8.

This attribute is the total number of bits sent during the test period. As long as the line speed of the hardware interface is less than 70 Mbit/s, this counter is not expected to reach the maximum value.

This attribute is the total number of bytes sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of frames sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of bits received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach the maximum value.

This attribute is the total number of bytes received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is the total number of frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the total number of errored frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the calculated bit error rate on the link. Test data are generated and sent in frames of a preset size (frameSize). The Test component will try to estimate the number of bit errors in any errored frame which is identifiable. The statistics will be updated accordingly. A lost frame (may be due to an error on the flag sequence) will be discarded for the bit error rate calculation. The result is presented in the form of xEsyy, where x is the mantissa, syy is the exponent, for example 0E+00, 2E-09. Note that the bitErrorRate is an estimate only. For more reliable test results, the test should be done over a long period. Multiple tests would also improve the confidence level of the test results.

This entry controls the addition and deletion of mscLpDS3CBit components.

A single entry in the table represents a single mscLpDS3CBit component.

This variable is used as the basis for SNMP naming of mscLpDS3CBit components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3CBit tables.

This variable represents the index for the mscLpDS3CBit tables.

This group contains the DS3 C-Bit Parity operational data for the CBIT component.

An entry in the mscLpDS3CBitOperationalTable.

This attribute indicates the Far-End alarm signal that is currently received at the DS3 interface. This signal is carried over the Far- End Alarm and Control (FEAC) bits of DS3 frames. Five far-end alarm signals can be received: far-end equipment failure that is received when the far-end terminal has detected a local equipment failure; far-end Loss Of Signal (LOS) that is received when the far- end DS3 terminal has declared a LOS failure condition; far-end Loss of Frame (LOF) when the far-end DS3 terminal has declared a Loss Of Frame (LOF) failure condition; far-end Alarm Indication Signal (AIS) when the far-end has declared an AIS failure condition; far-end Idle when the far-end has declared an Idle signal condition. Enumeration: 'none': 5, 'sef': 2, 'ais': 3, 'los': 1, 'idle': 4, 'equipmentFailure': 0.

This indicates whether or not the DS3 component is currently looping back the incoming DS3 signal or one of its DS1 tributaries to the far-end DS3 terminal. This is activated when the far-end DS3 equipment has ordered the local terminal to do so. Description of bits: notused0(0) n1(1) n2(2) n3(3) n4(4) n5(5) n6(6) n7(7) n8(8) n9(9) n10(10) n11(11) n12(12) n13(13) n14(14) n15(15) n16(16) n17(17) n18(18) n19(19) n20(20) n21(21) n22(22) n23(23) n24(24) n25(25) n26(26) n27(27) n28(28) notused29(29) notused30(30) ds3Line(31)

This attribute indicates which DS1 tributaries are being looped back, or if the DS3 line is being looped back. Each value listed indicates a loopback request has been made. When a loopback deactivation command has been sent to the far end, the corresponding value will be removed from the list. Description of bits: notused0(0) n1(1) n2(2) n3(3) n4(4) n5(5) n6(6) n7(7) n8(8) n9(9) n10(10) n11(11) n12(12) n13(13) n14(14) n15(15) n16(16) n17(17) n18(18) n19(19) n20(20) n21(21) n22(22) n23(23) n24(24) n25(25) n26(26) n27(27) n28(28) notused29(29) notused30(30) ds3Line(31)

This group contains the DS3 C-Bit Parity statistical data for the CBIT component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpDS3CBitStatsTable.

This attribute indicates the number of seconds that the DS3 port has not suffered any C-Bit errors.

This attribute indicates the total count of C-Bit Parity Code Violations (CCV). A CCV is obtained when the parity calculated over the previous DS3 frame and the value of the CP-bits appearing in the current DS3 frame differ. The value of this attribute will wrap around to 0 if it does reach its maximum value. CCV counting is inhibited for second intervals where C-Bit Parity Severely Errored Seconds (CSES) are counted. It is also inhibited for second intervals where C-Bit Unavailable Seconds (CUAS) are counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of C-Bit Parity Errored Seconds (CES). A CES second is declared for second intervals containing one or more CCVs or when one or more SEF (Severely Errored Frame) or AIS (Alarm Indication Signal) defects. CES counting is inhibited for second intervals where C-Bit Unavailable Seconds (CUAS) are counted.

This attribute indicates the total number of C-Bit Parity Severely Errored Seconds (CSES). A CSES is declared for second intervals containing more than 44 CCVs or one or more SEF or AIS defects. The occurrence of CSES in a one second interval causes the inhibition of CCV counting during that second interval. CSES counting is also inhibited for second intervals where C-Bit Unavailable Seconds (CUAS) are counted.

This attribute indicates the total number of one second intervals for which the DS3 path is unavailable. The DS3 path becomes unavailable at the onset of 10 consecutive C-Bit Severely Errored Seconds (CSES). The 10 CSESs are included in the unavailable time. Once unavailable, the DS3 path becomes available at the onset of 10 contiguous seconds with no CSES. The 10 seconds with no CSES are excluded from the unavailable time. For second intervals where CUAS is counted, counting of C-Bit Coding Violations (CCV), C-Bit Errored Seconds (CES) and C-Bit Severely Errored Seconds (CSES) is inhibited.

This attribute indicates the number of seconds that the DS3 port has not suffered of any far-end errors.

This attribute indicates the total count of DS3 frames containing a Coding Violation on the Far-End (FECV), also known as a Far-End Block Error (FEBE). Each FEBE is reported over the FEBE bits each time the far-end DS3 terminal detects a C-BIT Parity error over a received DS3 frame. For second intervals where Far-End Unavailable Seconds (FEAUS) or Far-End Severely Errored Seconds (FESES) are counted, counting of FECVs is inhibited. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Far-End Errored Seconds (FEES). A FEES is declared for second intervals containing with one or more FECVs or one or more far-end SEF/ AIS defects. A far-end SEF/AIS defect occurs when the X-Bits of the DS3 frame are received as being set to zero. For second intervals where Far-End Unavailable Seconds (FEUAS) are counted, counting of FEESs is inhibited.

This attribute indicates the total number of Far-End Severely Errored Seconds (FESES). A FESES is declared for second intervals containing more than 44 FECVs or one or more far-end SEF/AIS defects. For second intervals where a FESES is counted, counting of FECVs is inhibited. For second intervals where Far-End Unavailable Seconds (FEUAS) are counted, counting of FESESs is inhibited.

This attribute indicates the total number of Far-End SEF/AIS Seconds (FESAS). A FESAS is declared for second intervals containing one or more far-end SEF/AIS defects.For second intervals where Far-End Unavailable Seconds (FEUAS) are counted, counting of FESASs is inhibited.

This attribute indicates the total number of one second intervals for which the DS3 far-end path is unavailable. The DS3 far-end path becomes unavailable at the onset of 10 consecutive Far-End Severely Errored Seconds (FESES). The 10 FESESs are included in the unavailable time. Once unavailable, the DS3 far-end path becomes available at the onset of 10 contiguous seconds with no FESES. The 10 seconds with no FESES are excluded from the unavailable time. For second intervals where FEUAS is counted, counting of Far-End Coding Violations (FECV), Far-End Errored Seconds (FEES), Far-End Severely Errored Seconds (FESES) and Far-End Sef/Ais Seconds (FESAS) is inhibited.

This attribute indicates the total number of times that a far-end path failure (i.e. a Far-End SEF/AIS defect) has been declared. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This entry controls the addition and deletion of mscLpDS3Plcp components.

A single entry in the table represents a single mscLpDS3Plcp component.

This variable is used as the basis for SNMP naming of mscLpDS3Plcp components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3Plcp tables.

This variable represents the index for the mscLpDS3Plcp tables.

This group contains the operational data for the PLCP component.

An entry in the mscLpDS3PlcpOperationalTable.

This attribute displays whether a PLCP Loss Of Frame (LOF) failure alarm state has been entered. An LOF failure is declared when a PLCP LOF defect persists for 2.5 s +/- 0.5 s. An LOF defect occurs when an OOF (Out of Frame) state persists for more than 1 ms. If the OOF events are intermittent, the LOF defect counter is decremented at a rate of 1/12 (for DS3 PLCP) or 1/9 (for G.751 E3 PLCP) of the incrementing rate, with all measurements based on a 200 ms polling cycle. An OOF event (also known as a PLCP SEF event) is declared when an error is detected in both the A1 and A2 octets, or when two consecutive POHIDs are found in error. OOF is removed when two valid sets of framing octets and two valid and sequential POHID octets have been found. The LOF defect is removed when the defect counter reaches zero, i.e. when OOF events are absent for more than 12 ms (DS3 PLCP) or 9 ms (G.751 E3 PLCP). LOF failure alarm is cleared when LOF defect is absent for 10.0 s +/- 0.5 s The DS3 or E3 component goes into an operational state of disabled until the LOF failure alarm is cleared. The terminal declaring the LOF failure alarm will transmit a PLCP RAI signal to the far-end for the duration of the alarm. The lofAlarm attribute is always set to off when the DS3 or E3 component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a PLCP Remote Alarm Indication (RAI) failure alarm state has been entered. An RAI failure alarm occurs when ten consecutive PLCP RAI bits (bit 5 in the G1 byte) are high on the incoming line. An RAI failure alarm is cleared when ten consecutive RAI bits are set to 0. Note: Some standards call this alarm RFI. The rxRaiAlarm attribute is always set to off when the DS3 or E3 component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This group contains the statistical data for the PLCP component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpDS3PlcpStatsTable.

This attribute indicates the number of seconds during which the near-end PLCP path layer had no errors.

This attribute indicates the total number of BIP-8 Errors, framing pattern octet errors, and path overhead identification errors detected in received PLCP frames. Counting of PLCP CV is inhibited for second intervals where PLCP Severely Errored Framing Seconds (SEFS) or PLCP Unavailable Seconds (UAS) are counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the number of seconds containing one or more PLCP Coding Violations (CV) or in which a PLCP Severely Errored Framing Second (SEFS) was counted. Counting of PLCP ES is inhibited during second intervals where PLCP Unavailable Seconds (UAS) are counted.

This attribute indicates the number of seconds containing 5 or more PLCPCVs or in which a PLCPSEFS was counted (i.e. a PLCP OOF event occurred). Counting of PLCP SES is inhibited during second intervals where PLCP Unavailable Seconds (UAS) are counted.

This attribute indicates the number of seconds containing one or more PLCP Severely Errored Frame (SEF) events. An SEF event is equivalent to a PLCP OOF (Out of Frame) event. Counting of PLCPP SEFSs is inhibited for second intervals where PLCP Unavailable Seconds (UAS) are counted.

This attribute indicates the number of seconds when the near-end PLCP layer is unavailable. The PLCP Path Layer becomes unavailable at the declaration of PLCP LOF (Loss of Frame) failure alarm state. The PLCP Path Layer becomes available again only after clearing this condition. For second intervals where PLCP UAS are counted, counting of PLCP Severely Errored Framing Seconds (SEFS), PLCP Coding Violations (CV), PLCP Errored Seconds (ES), PLCP Severely Errored Seconds (SES) and PLCP Far-End Severely Errored Seconds (FESES) is inhibited.

This attribute indicates the number of seconds during which the far- end PLCP path layer had no errors.

This attribute indicates the total number of PLCP Far-End Block Errors (FEBE) reported by the far-end terminal. Counting of FEBEs is inhibited for second intervals where PLCP Far-End Unavailable Seconds (FEUAS) are counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the number of seconds containing one or more PLCP Far-End Coding Violations (FECV). Counting of PLCP FEES is inhibited during second intervals where PLCP Far-End Unavailable Seconds (FEUAS) are counted.

This attribute indicates the number of seconds containing 5 or more PLCP Far-End Coding Violations (FECV). Counting of PLCP FESES is inhibited for second intervals where PLCP Far-End Unavailable Seconds (FEUAS) are counted.

This attribute indicates the number of seconds during which the PLCP far end is unavailable. The PLCP Path Layer becomes unavailable at the declaration of PLCP RAI (Remote Alarm Indication). Service becomes available again after this condition is cleared. For second intervals where PLCP FEUAS are counted, counting of PLCP Far-End Coding Violations (FECV), PLCP Far- End Errored Seconds (FEES), and PLCP Far-End Severely Errored Seconds (FESES) is inhibited.

This entry controls the addition and deletion of mscLpDS3Cell components.

A single entry in the table represents a single mscLpDS3Cell component.

This variable is used as the basis for SNMP naming of mscLpDS3Cell components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3Cell tables.

This variable represents the index for the mscLpDS3Cell tables.

This group contains the provisioning attributes for the AtmCell component.

An entry in the mscLpDS3CellProvTable.

This attribute defines the time during which a Loss of Cell Delineation (LCD) defect should be observed before declaring an LCD alarm (alarm 70115501). The time is specified in milliseconds.

Cell scrambling, as defined by ITU-T Recommendation I.432., can provide a solution to the problem of transmission equipment which is sensitive to certain bit patterns in the ATM cell payload. This attribute controls whether or not the cell payload is scrambled. It defaults to off for DS1 interfaces, and on for all other interfaces. Note that this setting must be the same at both ends of the link. Enumeration: 'on': 1, 'off': 0.

This attribute specifies whether the port corrects single bit errors detected in the headers of received cells. If single bit errors are corrected, the affected cells are passed up to the ATM layer according to normal operation. If single bit errors are not corrected, these errored cells are discarded by the physical layer. Note that cells containing multiple bit errors in their headers are always discarded. Single bit HEC error correction must remain off for the following card types: 3pDS1Atm, 8pDS1Atm, 3pE1Atm, 8pE1Atm, 2pJ6MAtm, 3pDS3Atm, and 3pE3Atm. Enumeration: 'on': 1, 'off': 0.

This group contains the common operational attributes for the AtmCell component.

An entry in the mscLpDS3CellOperTable.

This attribute displays whether the Loss of Cell Delineation (LCD) failure alarm state has been entered. This state is entered when LCD defects have been observed and accumulated for a period of time specified through the alarmActDelay attribute. In ATM cell direct mapping mode, an LCD defect occurs when Out of Cell Delineation (OCD) anomaly persists for x milliseconds, and disappears when the Out of Cell Delineation (OCD) is absent for x msec. An OCD anomaly occurs when 7 consecutive incorrect HECs have been detected. An OCD anomaly terminates when 6 consecutive correct HECs have been detected. For an AtmCell component located under a DS3 or E3 component with mapping = PLCP, the LCD defect is directly derived from the PLCP LOF defect. If LCD defects are intermittently occurring, the LCD defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle The component under which is located the AtmCell component goes into an operational state of disabled until the LCD alarm condition is cleared. The condition is cleared after the LCD defect has not been reported for a period of 10 seconds +/- 0.5 seconds. The lcdAlarm attribute is always set to off when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked. Enumeration: 'on': 0, 'off': 1.

This group contains the Statistics attribute for the AtmCell component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpDS3CellStatsTable.

This attribute indicates the number of uncorrectable ATM cell header errors that have been detected. Counting of uncorrectableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected.

This attribute indicates the total number of ATM Cell Severely Errored Seconds (SESs) that have been counted. In direct mapping mode, an ATM Cell SES is declared for second intervals containing one or more Out of Cell Delineation (OCD) defects. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected. In PLCP mapping mode, an ATM Cell SES is declared for second intervals containing one or more PLCP LOF defects. Counting of uncorrectableHeaderErrors (ucErr) and correctableHeaderErrors (cErr) is inhibited when the OCD defect is present.

This attribute is the ratio of the number of valid, assigned cells received on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute is the ratio of the number of valid, assigned cells transmitted on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute indicates the number of correctable ATM cell header errors that have been detected and corrected. Counting of correctableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected

This entry controls the addition and deletion of mscLpDS3DS1 components.

A single entry in the table represents a single mscLpDS3DS1 component.

This variable is used as the basis for SNMP naming of mscLpDS3DS1 components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3DS1 tables.

This variable represents the index for the mscLpDS3DS1 tables.

This entry controls the addition and deletion of mscLpDS3DS1Chan components.

A single entry in the table represents a single mscLpDS3DS1Chan component.

This variable is used as the basis for SNMP naming of mscLpDS3DS1Chan components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3DS1Chan tables.

This variable represents the index for the mscLpDS3DS1Chan tables.

This entry controls the addition and deletion of mscLpDS3DS1ChanTest components.

A single entry in the table represents a single mscLpDS3DS1ChanTest component.

This variable is used as the basis for SNMP naming of mscLpDS3DS1ChanTest components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3DS1ChanTest tables.

This variable represents the index for the mscLpDS3DS1ChanTest tables.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS3DS1ChanTestStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains all of the operational data for a Test component.

An entry in the mscLpDS3DS1ChanTestSetupTable.

This attribute records the purpose of the test so that the test results can be associated and properly analyzed.

This attribute is the type of test to be run. The available test types include the following: card test sets up an internal loop on the board and runs a bit error rate test. manual test assumes the line is looped back externally and a bit error rate test is performed. localLoop test loops back the local modem and performs a bit error rate test. remoteLoop test loops back the remote modem (or CSU) and performs a bit error rate test. externalLoop test loops back the line to the far end. payloadLoop test only loops back the payload data received from the incoming line. remoteLoopThisTrib loops this particular tributary back at the far end, using services provided by the parent. v54RemoteLoop initiates a V.54 Remote Loopback test. pn127RemoteLoop initiates a PN127 Remote Loopback test. Note that not all test types are not supported by all function processors. Enumeration: 'externalLoop': 4, 'pn127RemoteLoop': 8, 'payloadLoop': 5, 'manual': 1, 'remoteLoop': 3, 'v54RemoteLoop': 7, 'remoteLoopThisTrib': 6, 'localLoop': 2, 'card': 0.

This attribute defines the size of the test data frames in number of bytes.

This attribute defines the type of data pattern generation to use. The following lists the available pattern types: ccitt32kBitPattern is a pseudo-random sequence of 32 kbit. ccitt8MBitPattern is a pseudo-random sequence of 8Mbit. customizedPattern is the pattern defined in the customizedPattern attribute. Enumeration: 'ccitt32kBitPattern': 0, 'customizedPattern': 2, 'ccitt8MBitPattern': 1.

This attribute allows a customized 32 bit pattern to be defined for use in the test data frames. This attribute is used when the attribute frmPatternType is set to CustomizedPattern. Note that a 55 hex pattern is an alternating 1 and 0 pattern.

This attribute specifies the time delay (in seconds) between when the test expects the loop to have been set up, to when the test data actually starts to be transmitted. This attribute is to accommodate some non-standard equipment that requires extra time for setting up a requested loop. This attribute is ignored when the test type is set to externalLoop.

This attribute defines the interval (in minutes) between which interim test results are to be displayed. Results are displayed at the operator console at which the test was started. When the test type is set to externalLoop, this attribute is ignored. There will be no display of results if displayInterval is set to 0. This attribute can be changed anytime.

This attribute is the duration (in minutes) that test data will be transmitted. In the case of an externalLoop, this is the time that the loop is in effect. Note that dataStartDelay does not apply to the externalLoop.

This group contains all the statistics related attributes of the Test component.

An entry in the mscLpDS3DS1ChanTestResultsTable.

This attribute is the number of minutes elapsed since the test started for an externalLoop test. For a data test, this is the time since test data was first transmitted.

This attribute is the number of minutes remaining before the test is to be stopped according to the duration attribute.

This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values. Enumeration: 'patternSyncFailed': 7, 'unknown': 2, 'neverStarted': 3, 'hardwareReconfigured': 5, 'loopCodeSyncFailed': 6, 'stoppedByOperator': 1, 'testTimeExpired': 0, 'testRunning': 4, 'patternSyncLost': 8.

This attribute is the total number of bits sent during the test period. As long as the line speed of the hardware interface is less than 70 Mbit/s, this counter is not expected to reach the maximum value.

This attribute is the total number of bytes sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of frames sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of bits received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach the maximum value.

This attribute is the total number of bytes received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is the total number of frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the total number of errored frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the calculated bit error rate on the link. Test data are generated and sent in frames of a preset size (frameSize). The Test component will try to estimate the number of bit errors in any errored frame which is identifiable. The statistics will be updated accordingly. A lost frame (may be due to an error on the flag sequence) will be discarded for the bit error rate calculation. The result is presented in the form of xEsyy, where x is the mantissa, syy is the exponent, for example 0E+00, 2E-09. Note that the bitErrorRate is an estimate only. For more reliable test results, the test should be done over a long period. Multiple tests would also improve the confidence level of the test results.

This entry controls the addition and deletion of mscLpDS3DS1ChanCell components.

A single entry in the table represents a single mscLpDS3DS1ChanCell component.

This variable is used as the basis for SNMP naming of mscLpDS3DS1ChanCell components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3DS1ChanCell tables.

This variable represents the index for the mscLpDS3DS1ChanCell tables.

This group contains the provisioning attributes for the AtmCell component.

An entry in the mscLpDS3DS1ChanCellProvTable.

This attribute defines the time during which a Loss of Cell Delineation (LCD) defect should be observed before declaring an LCD alarm (alarm 70115501). The time is specified in milliseconds.

Cell scrambling, as defined by ITU-T Recommendation I.432., can provide a solution to the problem of transmission equipment which is sensitive to certain bit patterns in the ATM cell payload. This attribute controls whether or not the cell payload is scrambled. It defaults to off for DS1 interfaces, and on for all other interfaces. Note that this setting must be the same at both ends of the link. Enumeration: 'on': 1, 'off': 0.

This attribute specifies whether the port corrects single bit errors detected in the headers of received cells. If single bit errors are corrected, the affected cells are passed up to the ATM layer according to normal operation. If single bit errors are not corrected, these errored cells are discarded by the physical layer. Note that cells containing multiple bit errors in their headers are always discarded. Single bit HEC error correction must remain off for the following card types: 3pDS1Atm, 8pDS1Atm, 3pE1Atm, 8pE1Atm, 2pJ6MAtm, 3pDS3Atm, and 3pE3Atm. Enumeration: 'on': 1, 'off': 0.

This group contains the common operational attributes for the AtmCell component.

An entry in the mscLpDS3DS1ChanCellOperTable.

This attribute displays whether the Loss of Cell Delineation (LCD) failure alarm state has been entered. This state is entered when LCD defects have been observed and accumulated for a period of time specified through the alarmActDelay attribute. In ATM cell direct mapping mode, an LCD defect occurs when Out of Cell Delineation (OCD) anomaly persists for x milliseconds, and disappears when the Out of Cell Delineation (OCD) is absent for x msec. An OCD anomaly occurs when 7 consecutive incorrect HECs have been detected. An OCD anomaly terminates when 6 consecutive correct HECs have been detected. For an AtmCell component located under a DS3 or E3 component with mapping = PLCP, the LCD defect is directly derived from the PLCP LOF defect. If LCD defects are intermittently occurring, the LCD defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle The component under which is located the AtmCell component goes into an operational state of disabled until the LCD alarm condition is cleared. The condition is cleared after the LCD defect has not been reported for a period of 10 seconds +/- 0.5 seconds. The lcdAlarm attribute is always set to off when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked. Enumeration: 'on': 0, 'off': 1.

This group contains the Statistics attribute for the AtmCell component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpDS3DS1ChanCellStatsTable.

This attribute indicates the number of uncorrectable ATM cell header errors that have been detected. Counting of uncorrectableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected.

This attribute indicates the total number of ATM Cell Severely Errored Seconds (SESs) that have been counted. In direct mapping mode, an ATM Cell SES is declared for second intervals containing one or more Out of Cell Delineation (OCD) defects. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected. In PLCP mapping mode, an ATM Cell SES is declared for second intervals containing one or more PLCP LOF defects. Counting of uncorrectableHeaderErrors (ucErr) and correctableHeaderErrors (cErr) is inhibited when the OCD defect is present.

This attribute is the ratio of the number of valid, assigned cells received on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute is the ratio of the number of valid, assigned cells transmitted on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute indicates the number of correctable ATM cell header errors that have been detected and corrected. Counting of correctableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected

This entry controls the addition and deletion of mscLpDS3DS1ChanTc components.

A single entry in the table represents a single mscLpDS3DS1ChanTc component.

This variable is used as the basis for SNMP naming of mscLpDS3DS1ChanTc components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3DS1ChanTc tables.

This variable represents the index for the mscLpDS3DS1ChanTc tables.

This group contains all specific provisioning data for a Tc component.

An entry in the mscLpDS3DS1ChanTcProvTable.

This attribute specifies the trunk conditioning data byte to be substituted into the timeslots defined by the Chan component under fault conditions. replacementData can be set to any two digit hexadecimal number. The following are recommended values: DS1 MUX Out Of Service Code = 0x1A E1 MUX Out Of Service Code = 0xFF

This attribute specifies the time duration in seconds for which signalOne is substituted into the appropriate signaling bits, when a lineType that uses CAS has been defined. When signalOneDuration has expired signalTwo is substituted into the appropriate signaling bits. If signalOneDuration is set to zero then only signalTwo is substituted into the appropriate signaling bits during error conditions. signalOneDuration can be set to any integer value from 0 to 60 seconds.

This group contains all specific operational data for a Tc component.

An entry in the mscLpDS3DS1ChanTcOpTable.

This attribute indicates the status of locally generated trunk conditioning towards the ATM network. When trunk conditioning is being locally generated towards the ATM network, ingressConditioning is set to on. When trunk conditioning is not being locally generated towards the ATM network, ingressConditioning is set to off. Trunk conditioning is transmitted towards the ATM network under the following conditions: lossOfSignal (LOS) lossOfFrame (LOF) remoteAlarmIndication (RAI) alarmIndicationSignal (AIS) bufferUnderflow (BU) and in addition for E1: lossOfMultiframe (LOMF) receiveMultiframeRemoteAlarmIndication (RMRAI) Enumeration: 'on': 1, 'off': 0.

This attribute indicates the status of locally generated trunk conditioning towards the PDH line. When trunk conditioning is being locally generated towards the PDH line, egressConditioning is set to on. When trunk conditioning is not being locally generated towards the PDH line, egressConditioning is set to off. Trunk conditioning is transmitted towards the PDH line under the following conditions: bufferUnderflow (BU) AAL1 protocol errors. Enumeration: 'on': 1, 'off': 0.

This attribute specifies the value to be substituted into the ABCD signaling bits for the timeslots defined by the Chan component under fault conditions. The value will be substituted for the duration provisioned in signalOneDuration when a lineType that uses CAS has been defined. For a lineType of d4Cas (Super Frame), signaling bits C and D are required to equal bits A and B respectively.

An entry in the mscLpDS3DS1ChanTcSigOneTable.

This variable represents the mscLpDS3DS1ChanTcSigOneTable specific index for the mscLpDS3DS1ChanTcSigOneTable. Enumeration: 'a': 3, 'c': 1, 'b': 2, 'd': 0.

This variable represents an individual value for the mscLpDS3DS1ChanTcSigOneTable.

This attribute specifies the value to be substituted into the ABCD signaling bits for the timeslots defined by the Chan component under fault conditions. The value will be substituted after the duration provisioned in signalOneDuration has expired and when a lineType that uses CAS has been defined. For a lineType of d4Cas (Super Frame), signaling bits C and D are required to equal bits A and B respectively.

An entry in the mscLpDS3DS1ChanTcSigTwoTable.

This variable represents the mscLpDS3DS1ChanTcSigTwoTable specific index for the mscLpDS3DS1ChanTcSigTwoTable. Enumeration: 'a': 3, 'c': 1, 'b': 2, 'd': 0.

This variable represents an individual value for the mscLpDS3DS1ChanTcSigTwoTable.

This group contains all of the provisional data for a Channel component.

An entry in the mscLpDS3DS1ChanProvTable.

This attribute contains the list of timeslots that are used by the Channel component. Valid numbers are 1-24 for a Channel used by a DS1 component, and 1-31 for a Channel used by an E1 component. Description of bits: notused0(0) n1(1) n2(2) n3(3) n4(4) n5(5) n6(6) n7(7) n8(8) n9(9) n10(10) n11(11) n12(12) n13(13) n14(14) n15(15) n16(16) n17(17) n18(18) n19(19) n20(20) n21(21) n22(22) n23(23) n24(24) n25(25) n26(26) n27(27) n28(28) n29(29) n30(30) n31(31)

This attribute selects the data rate of the timeslots in a channel of a DS1 component. For E1, the data rate of the timeslots will always be 64kbit/s regardless of this attribute. When doNotOverride is selected for a channel on a DS1, the data rate of the channel's timeslots are dependant on the zeroCoding selection of the DS1 component. If the zeroCoding is B8ZS (where supported on the FP) or none, the timeslot's data rate will be 64kbit/ s. If the zeroCoding option is bit7Stuffing, the data rate of a timeslot will be 56kbit/s. When 56k is selected for a channel on a DS1, the least significant bit of each timeslot of this Channel will always be set to 1 and not used for data. The data rate for the timeslots of this channel is therefore restricted to 56kbit/s. One application of this attribute is to allow a DS1 line to support mixing channels that originate from lines that use different zeroCoding schemes. Enumeration: 'n56k': 0, 'doNotOverride': 1.

This attribute defines the link to the software stack. It defines which application is running on top of this hardware component.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscLpDS3DS1ChanCidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains the provisionable attributes for the ifEntry.

An entry in the mscLpDS3DS1ChanIfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the mscLpDS3DS1ChanOperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS3DS1ChanStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains all of the operational data for a Channel component.

An entry in the mscLpDS3DS1ChanOperTable.

This attribute displays the measured link speed of the Channel component.

This group contains the attributes pertaining to the vendor of the equipment.

An entry in the mscLpDS3DS1ChanAdminInfoTable.

This is the name of the vendor supplying the facility.

Any miscellaneous text about the facility.

This entry controls the addition and deletion of mscLpDS3DS1Test components.

A single entry in the table represents a single mscLpDS3DS1Test component.

This variable is used as the basis for SNMP naming of mscLpDS3DS1Test components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS3DS1Test tables.

This variable represents the index for the mscLpDS3DS1Test tables.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS3DS1TestStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains all of the operational data for a Test component.

An entry in the mscLpDS3DS1TestSetupTable.

This attribute records the purpose of the test so that the test results can be associated and properly analyzed.

This attribute is the type of test to be run. The available test types include the following: card test sets up an internal loop on the board and runs a bit error rate test. manual test assumes the line is looped back externally and a bit error rate test is performed. localLoop test loops back the local modem and performs a bit error rate test. remoteLoop test loops back the remote modem (or CSU) and performs a bit error rate test. externalLoop test loops back the line to the far end. payloadLoop test only loops back the payload data received from the incoming line. remoteLoopThisTrib loops this particular tributary back at the far end, using services provided by the parent. v54RemoteLoop initiates a V.54 Remote Loopback test. pn127RemoteLoop initiates a PN127 Remote Loopback test. Note that not all test types are not supported by all function processors. Enumeration: 'externalLoop': 4, 'pn127RemoteLoop': 8, 'payloadLoop': 5, 'manual': 1, 'remoteLoop': 3, 'v54RemoteLoop': 7, 'remoteLoopThisTrib': 6, 'localLoop': 2, 'card': 0.

This attribute defines the size of the test data frames in number of bytes.

This attribute defines the type of data pattern generation to use. The following lists the available pattern types: ccitt32kBitPattern is a pseudo-random sequence of 32 kbit. ccitt8MBitPattern is a pseudo-random sequence of 8Mbit. customizedPattern is the pattern defined in the customizedPattern attribute. Enumeration: 'ccitt32kBitPattern': 0, 'customizedPattern': 2, 'ccitt8MBitPattern': 1.

This attribute allows a customized 32 bit pattern to be defined for use in the test data frames. This attribute is used when the attribute frmPatternType is set to CustomizedPattern. Note that a 55 hex pattern is an alternating 1 and 0 pattern.

This attribute specifies the time delay (in seconds) between when the test expects the loop to have been set up, to when the test data actually starts to be transmitted. This attribute is to accommodate some non-standard equipment that requires extra time for setting up a requested loop. This attribute is ignored when the test type is set to externalLoop.

This attribute defines the interval (in minutes) between which interim test results are to be displayed. Results are displayed at the operator console at which the test was started. When the test type is set to externalLoop, this attribute is ignored. There will be no display of results if displayInterval is set to 0. This attribute can be changed anytime.

This attribute is the duration (in minutes) that test data will be transmitted. In the case of an externalLoop, this is the time that the loop is in effect. Note that dataStartDelay does not apply to the externalLoop.

This group contains all the statistics related attributes of the Test component.

An entry in the mscLpDS3DS1TestResultsTable.

This attribute is the number of minutes elapsed since the test started for an externalLoop test. For a data test, this is the time since test data was first transmitted.

This attribute is the number of minutes remaining before the test is to be stopped according to the duration attribute.

This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values. Enumeration: 'patternSyncFailed': 7, 'unknown': 2, 'neverStarted': 3, 'hardwareReconfigured': 5, 'loopCodeSyncFailed': 6, 'stoppedByOperator': 1, 'testTimeExpired': 0, 'testRunning': 4, 'patternSyncLost': 8.

This attribute is the total number of bits sent during the test period. As long as the line speed of the hardware interface is less than 70 Mbit/s, this counter is not expected to reach the maximum value.

This attribute is the total number of bytes sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of frames sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of bits received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach the maximum value.

This attribute is the total number of bytes received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is the total number of frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the total number of errored frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the calculated bit error rate on the link. Test data are generated and sent in frames of a preset size (frameSize). The Test component will try to estimate the number of bit errors in any errored frame which is identifiable. The statistics will be updated accordingly. A lost frame (may be due to an error on the flag sequence) will be discarded for the bit error rate calculation. The result is presented in the form of xEsyy, where x is the mantissa, syy is the exponent, for example 0E+00, 2E-09. Note that the bitErrorRate is an estimate only. For more reliable test results, the test should be done over a long period. Multiple tests would also improve the confidence level of the test results.

This group contains all of the provisioning data for a DS1 component.

An entry in the mscLpDS3DS1ProvTable.

This attribute defines the framing of the DS1 tributary. d4 defines a framing pattern of 12 frames per multiframe. esf defines a framing pattern of 24 frames per multiframe. d4Cas defines a framing pattern of 12 frames per multiframe with channel associated signalling. esfCas defines a framing pattern of 24 frames per multiframe with channel associated signalling. For the 4pDS3ChAtm card, only d4 and esf framing patterns are permitted. Enumeration: 'esf': 1, 'd4': 0, 'd4Cas': 4, 'esfCas': 5.

This attribute defines the zero encoding on the DS1 tributary. bit7Stuffing sets bit 7 of every timeslot to a one to guarantee ones's density. This reduces the available bandwidth of the channel by 1/8. none does no zero encoding. Enumeration: 'bit7Stuffing': 0, 'none': 3.

This attribute defines the source of the transmit clock for the DS1 tributary. When the clocking source is selected from local, the crystal on the port generates the clocking for the DS1 tributary. When the clocking source is selected from line, the port synchronizes to the clock from the DS1 tributary. When the clocking source is selected from module, the ports clock synchronizes to the clock provided by the oscillator on the active CP. On a 1pDS3C card, if the NetworkSynchronization (NS) component is present the default value of this attribute will be module otherwise it will be line. On a 2pDS3cAal or 4pDS3ChAtm card, the only valid values are local and module. If the NS component is present the default value of this attribute will be module otherwise it will be local. On a 4pDS3ChAtm card the clocking source for all DS1 and all DS3 components on card must be the same, except when a DS1 is using line as a clocking source. Enumeration: 'line': 1, 'local': 0, 'module': 2.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscLpDS3DS1CidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains the attributes pertaining to the vendor of the equipment.

An entry in the mscLpDS3DS1AdminInfoTable.

This is the name of the vendor supplying the facility.

Any miscellaneous text about the facility.

This group contains the provisionable attributes for the ifEntry.

An entry in the mscLpDS3DS1IfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the mscLpDS3DS1OperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS3DS1StateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains the common operational data for a component in a digital hierarchy interface.

An entry in the mscLpDS3DS1OperTable.

This attribute indicates whether an AIS (Alarm Indication Signal) alarm state has been entered. The AIS Alarm state is entered when AIS defects have been observed and accumulated for 2.5 seconds +/- 0.5 seconds. An AIS defect is detected after having received less than 3 zeros in a 2048 bit period. If the AIS defects are intermittently occurring, the AIS defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. This tributary goes into an operationalState of disabled for the duration of an AIS alarm state. The AIS alarm state is cleared when AIS defects are absent for 10 seconds +/- 0.5 seconds. Enumeration: 'on': 0, 'off': 1.

This attribute indicates whether a LOF (Loss of Frame) alarm state has been entered. The LOF alarm state is entered when LOF defects (2 out of 5 framing bits in error ) have been detected for 3 seconds +/- 0.5 seconds. If the LOF defects are intermittently occurring, the LOF defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. This tributary goes into an operationalState of disabled until the LOF alarm state is cleared. Also, an RAI alarm is transmitted to the far end for the duration of the LOF alarm state The condition is cleared when framing has been achieved for 10 seconds +/- 0.5 seconds. Enumeration: 'on': 0, 'off': 1.

This attribute indicates whether an RAI (Remote Alarm Indication) alarm state has been entered. An RAI alarm state is entered when the RAI defect indicator has been observed and accumulated for 3.5 seconds +/- 0.5 seconds. If the RAI defects are intermittently occurring, the RAI defect accumulator is decremented at a rate of 1/ 10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The RAI alarm state is cleared when the RAI defect indicator has been absent for 10 seconds +/- 0.5 seconds. The RAI alarm is usually an indication that the far end facility is unable to gain synchronization. Enumeration: 'on': 0, 'off': 1.

This attribute indicates whether an AIS (Alarm Indication Signal) alarm is being transmitted on the line. An AIS alarm is transmitted when the tributary is in a locked state. Enumeration: 'on': 0, 'off': 1.

This attribute indicates whether a RAI signal is being sent on the outgoing line. The RAI signal is transmitted when the tributary detects a LOF alarm condition. Enumeration: 'on': 0, 'off': 1.

This group contains the common statistical data for a component in a digital hierarchy interface.

An entry in the mscLpDS3DS1StatsTable.

This attribute counts the number of seconds since the tributary was activated.

This attribute counts the number of seconds that the tributary has been in an error free state.

This attribute counts the number of errored seconds the tributary has counted since it was activated. An errored second is declared when a second with one or more Code Violation Error events, or one or more Out Of Frame events occurs. A code violation error may be a CRC error or a BPV error. An Out Of Frame event occurs when 2 out of 5 framing bits are in error.

This attribute counts the number of severely errored seconds the tributary has counted since it was activated. A severely errored second occurs when a second with 320 or more Code Violation Error events or one or more Out Of Frame events occurs.

This attribute counts the number of severely errored framing seconds the tributary has counted since it was activated A severely errored framing second occurs when a second with one or more Out Of Frame events occurs.

This attribute counts the total number of seconds that the tributary has been in an unavailable signal state. An unavailable signal state occurs at the onset of 10 consecutive Severely Errored Seconds. The state is cleared at the onset of 10 seconds with no Severely Errored Seconds.

This attribute counts the total number of CRC-6 errors. These will only be counted when the lineType is esf.

This attribute counts the total number of frame errors. A frame error is an error in the framing bits.

The total number of times that the line experienced a controlled frame slip.

This group contains all of the provisioning data for a DS3 component.

An entry in the mscLpDS3ProvTable.

This attribute indicates if C-Bit parity has been turned ON or OFF. The CBIT component will appear under the DS3 component when the cbitParity attribute is set to on. Enumeration: 'on': 1, 'off': 0.

This attribute defines the line length for equalization calculations for the DS3 line. The range is between 0 and 450 feet (1 metre = 3.28 feet). Note: There are currently only two ranges as far as the equalization calculation performed on the FP is concerned: 0 to 224ft and 225 to 450ft.

This attribute defines the type of clocking source used for synchronizing the DS3 transmit clock: local means direct use of the local clock oscillator at its centre frequency; line means use of a signal phase-locked to the incoming DS3 line rate; module means the use of a signal phase-locked to the CP reference clock. Note that the multiport cell-based cards have one common clock source for all ports. For this reason, the following rules apply for the value of clockingSource across the board's three ports: All three clockingSource values must be 'local' OR All three clockingSource values must be 'module' OR One clockingSource value must be 'line' and the other two must be 'otherPort'. If there is no NS component provisioned, the default value for this attribute will be local. If the NS component has been provisioned, the default value is module, except for the 1pDS3C cards. For the 1pDS3C cards, the default and only valid value for this attribute is local. The clockingSource of the DS1 sub-component becomes the effective clocking source for this attribute. All the DS1 sub-components have the same clocking source. Enumeration: 'line': 1, 'local': 0, 'otherPort': 4, 'module': 2.

This attribute defines the link to the software stack. It defines which application is running on top of the DS3 component.

This attribute indicates if ATM cells will be mapped directly into the DS3 payload, or whether PLCP mapping will be used. The PLCP component will appear under the DS3 component when this attribute is set to plcp. This attribute will be ignored when set on frame-based cards. Enumeration: 'plcp': 1, 'direct': 0.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscLpDS3CidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains the attributes pertaining to the vendor of the equipment.

An entry in the mscLpDS3AdminInfoTable.

This is the name of the vendor supplying the facility.

Any miscellaneous text about the facility.

This group contains the provisionable attributes for the ifEntry.

An entry in the mscLpDS3IfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the mscLpDS3OperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS3StateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains the common operational data for DS3 component.

An entry in the mscLpDS3OperTable.

This attribute displays whether a Loss Of Signal (LOS) alarm state has been entered. An LOS alarm state is entered when LOS defects have been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds. An LOS defect is detected at the DS3 line interface upon observing 175 +/- 75 continuous pulse positions with no pulses of either positive or negative polarity. If the LOS defects are intermittently occurring, the LOS defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The DS3 component goes into an operational state of disabled until the LOS alarm condition is cleared. The LOS alarm state is cleared after LOS defects have been absent for a period of 10 seconds +/- 0.5 seconds. The losAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a Loss Of Frame (LOF) alarm state has been entered. An LOF alarm state is entered when Severely Errored Frame (SEF) defects have been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds. A SEF defect is detected when 3 (or more) out of 16 (or fewer) F-bits are in error, or one (or more) M-bits in two (or more) out of four (or fewer) consecutive M-frames are in error. If the LOF defects are intermittently occurring, the LOF defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The DS3 component goes into an operational state of disabled until the LOF alarm condition is cleared. The condition is cleared when framing has been achieved for a period of 10 seconds +/- 0.5 seconds. As long as SEF defects are detected, the node also transmits the far-end SEF/AIS defect indicator over the outgoing line. When not running in C-Bit Parity mode, the txRai attribute is also set to on when transmitting the far-end SEF/AIS defect indicator on the outgoing line. The lofAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an Alarm Indication Signal (AIS) alarm state has been entered. An AIS alarm state is entered when AIS defects have been observed and accumulated for 2.5 seconds +/ - 0.5 seconds. An AIS defect is the occurrence of AIS (valid DS3 frame with payload containing the 1010...sequence and with C-Bits set to zero) in contiguous M-frames for a time greater than 100 milliseconds. If the AIS defects are intermittently occurring, the AIS defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The DS3 component goes into an operational state of disabled until the AIS alarm condition is cleared (after AIS has been no longer detected for a period of 10 seconds +/- 0.5 seconds). As long as AIS is detected, the node also transmits the far-end SEF/AIS defect indicator over the outgoing line. When not running in C-Bit Parity mode, the txRai attribute is also set to on when transmitting the far- end SEF/AIS defect indicator on the outgoing line. The rxAisAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a Remote Alarm Indication (RAI) alarm state has been entered. When not running the C-Bit Parity mode, the RAI alarm state is entered when the far-end SEF/AIS defect indicator has been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds on the incoming DS3 line. If the RAI defects are intermittently occurring, the RAI defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The DS3 component goes into an operational state of disabled until the RAI alarm condition is cleared. The condition is cleared when the far-end SEF/AIS defect indicator has not been detected for 10 seconds +/- 0.5 seconds. When running the C-Bit Parity mode, the RAI alarm state is entered upon detection of a far-end alarm over the Far-End Alarm and Control (FEAC) channel. The RAI alarm state is exited as soon as no more far-end alarm is detected on the FEAC channel. The far- end alarms that can be detected on the FEAC channel and that cause the RAI alarm state to be entered are: equipment failure alarm (service affecting), LOS alarm, LOF alarm, idle and AIS alarm. The rxRaiAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an Idle failure condition has been reported on the DS3 port. An Idle condition is reported when DS3 Idle defects have been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds. The DS3 Idle defect is the occurrence of a valid DS3 frame with the information bits set to a 11001100.. sequence. If the DS3 Idle defects are intermittently occurring, the DS3 Idle defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The DS3 component goes into an operational state of disabled until the Idle failure condition is cleared. The failure condition is cleared when the DS3 idle pattern has not been detected for at least 10 seconds +/- 0.5 seconds. The rxIdle attribute is always set to off when the component has been locked and left offline. The idle pattern indicates that the far-end is physically connected but not put in service. For instance, DS3 idle is transmitted on the outgoing line when the DS3 component is locked and not used for operational testing. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an Alarm Indication Signal (AIS) alarm is being transmitted on the DS3 line. Currently, AIS is never transmitted by a Passport DS3 node. Enumeration: 'on': 0, 'off': 1.

When not running C-Bit Parity mode, this attribute displays whether the far-end SEF/AIS defect indicator is transmitted over the outgoing line when the DS3 component has been unlocked or used in operational testing. When running in C-Bit Parity mode, this attribute displays whether a far-end alarm is sent over the Far-End Alarm and Control (FEAC) channel when the DS3 component has been unlocked or used in operational testing. When the DS3 component is locked and not used in operational testing, this attribute is always set to off. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether the DS3 Idle signal is transmitted over the outgoing line. DS3 Idle is sent when the DS3 component has been locked and not used in operational testing. Enumeration: 'on': 0, 'off': 1.

This group contains the specific DS3 common operational data for a DS3 component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpDS3StatsTable.

This attribute indicates the total number of seconds since the DS3 component has been activated and been in unlocked state or used for operational testing. All the other error counts that follow as well as each DS3 subcomponent's error counts can be updated when this count is active.

This attribute indicates the number of seconds that the DS3 port has been in an error free state.

This attribute indicates the total number of Line Code Violations (LCV) detected. A DS3 Line Code Violation is a B3Zs error. LCV counting is inhibited for second intervals where Line Severely Errored Second (LSES) is counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Line Errored Seconds (LES) that have been counted. A LES is declared for second intervals containing one or more LCV or one or more Loss Of Signal (LOS) defects.

This attribute indicates the total number of Line Severely Errored Seconds (LSES) that have been counted. A LSES is declared for second intervals containing more than 44 LCVs or one or more LOS defects.

This attribute indicates the total number of Line LOS Seconds (LOSS) that have been counted. A LOSS is declared for second intervals containing one or more LOS defects.

This attribute indicates the total number of times that a line failure (LOS failure) has been declared. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Path Code Violations (PCVs) detected. Each PCV corresponds to a P-bit parity error, or possibly a frame error or a disagreement between P-bits or X-bits. PCV counting is inhibited over second intervals where a Path Severely Errored Second (PSES) is counted. Counting of PCVs is also inhibited over second intervals where a Path Unavailable Second (PUAS) is counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Path Errored Seconds (PESs) that have been counted. A PES is declared for second intervals containing one or more Path Code Violations (PCV) or one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects. Counting of Path Errored Seconds is inhibited when Path Unavailable Seconds (PUAS) is counted over the monitored second.

This attribute indicates the total number of Path Severely Errored Seconds (PSESs) that have been counted. A PSES is declared for second intervals containing more than 44 PCVs or one or more SEF or AIS defects. Counting of PSESs is inhibited when Path Unavailable Seconds (PUAS) is counted over the monitored second.

This attribute indicates the total number of SEF/AIS Seconds (PSASs). A PSAS is declared for second intervals containing one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects. Counting of PSAS is inhibited when Path Unavailable Seconds (PUAS) is counted over the monitored second.

This attribute indicates the total number of one second intervals for which the DS3 path is unavailable. The DS3 path becomes unavailable at the onset of 10 consecutive Path Severely Errored Seconds (PSES). The 10 PSESs are included in the unavailable time. Once unavailable, the DS3 path becomes available at the onset of 10 contiguous seconds with no PSES. The 10 seconds with no PSES are excluded from the unavailable time. For second intervals where PUAS is counted, counting of Path Coding Violations (PCV), Path Errored Seconds (PES), Path Severely Errored Seconds (PSES) and Path Sef/Ais Seconds (PSAS) is inhibited.

This attribute indicates the total number of times that a path failure (LOF/AIS failure) has been declared. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This entry controls the addition and deletion of mscLpE3 components.

A single entry in the table represents a single mscLpE3 component.

This variable is used as the basis for SNMP naming of mscLpE3 components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpE3 tables.

This variable represents the index for the mscLpE3 tables.

This entry controls the addition and deletion of mscLpE3Test components.

A single entry in the table represents a single mscLpE3Test component.

This variable is used as the basis for SNMP naming of mscLpE3Test components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpE3Test tables.

This variable represents the index for the mscLpE3Test tables.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpE3TestStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains all of the operational data for a Test component.

An entry in the mscLpE3TestSetupTable.

This attribute records the purpose of the test so that the test results can be associated and properly analyzed.

This attribute is the type of test to be run. The available test types include the following: card test sets up an internal loop on the board and runs a bit error rate test. manual test assumes the line is looped back externally and a bit error rate test is performed. localLoop test loops back the local modem and performs a bit error rate test. remoteLoop test loops back the remote modem (or CSU) and performs a bit error rate test. externalLoop test loops back the line to the far end. payloadLoop test only loops back the payload data received from the incoming line. remoteLoopThisTrib loops this particular tributary back at the far end, using services provided by the parent. v54RemoteLoop initiates a V.54 Remote Loopback test. pn127RemoteLoop initiates a PN127 Remote Loopback test. Note that not all test types are not supported by all function processors. Enumeration: 'externalLoop': 4, 'pn127RemoteLoop': 8, 'payloadLoop': 5, 'manual': 1, 'remoteLoop': 3, 'v54RemoteLoop': 7, 'remoteLoopThisTrib': 6, 'localLoop': 2, 'card': 0.

This attribute defines the size of the test data frames in number of bytes.

This attribute defines the type of data pattern generation to use. The following lists the available pattern types: ccitt32kBitPattern is a pseudo-random sequence of 32 kbit. ccitt8MBitPattern is a pseudo-random sequence of 8Mbit. customizedPattern is the pattern defined in the customizedPattern attribute. Enumeration: 'ccitt32kBitPattern': 0, 'customizedPattern': 2, 'ccitt8MBitPattern': 1.

This attribute allows a customized 32 bit pattern to be defined for use in the test data frames. This attribute is used when the attribute frmPatternType is set to CustomizedPattern. Note that a 55 hex pattern is an alternating 1 and 0 pattern.

This attribute specifies the time delay (in seconds) between when the test expects the loop to have been set up, to when the test data actually starts to be transmitted. This attribute is to accommodate some non-standard equipment that requires extra time for setting up a requested loop. This attribute is ignored when the test type is set to externalLoop.

This attribute defines the interval (in minutes) between which interim test results are to be displayed. Results are displayed at the operator console at which the test was started. When the test type is set to externalLoop, this attribute is ignored. There will be no display of results if displayInterval is set to 0. This attribute can be changed anytime.

This attribute is the duration (in minutes) that test data will be transmitted. In the case of an externalLoop, this is the time that the loop is in effect. Note that dataStartDelay does not apply to the externalLoop.

This group contains all the statistics related attributes of the Test component.

An entry in the mscLpE3TestResultsTable.

This attribute is the number of minutes elapsed since the test started for an externalLoop test. For a data test, this is the time since test data was first transmitted.

This attribute is the number of minutes remaining before the test is to be stopped according to the duration attribute.

This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values. Enumeration: 'patternSyncFailed': 7, 'unknown': 2, 'neverStarted': 3, 'hardwareReconfigured': 5, 'loopCodeSyncFailed': 6, 'stoppedByOperator': 1, 'testTimeExpired': 0, 'testRunning': 4, 'patternSyncLost': 8.

This attribute is the total number of bits sent during the test period. As long as the line speed of the hardware interface is less than 70 Mbit/s, this counter is not expected to reach the maximum value.

This attribute is the total number of bytes sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of frames sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of bits received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach the maximum value.

This attribute is the total number of bytes received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is the total number of frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the total number of errored frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the calculated bit error rate on the link. Test data are generated and sent in frames of a preset size (frameSize). The Test component will try to estimate the number of bit errors in any errored frame which is identifiable. The statistics will be updated accordingly. A lost frame (may be due to an error on the flag sequence) will be discarded for the bit error rate calculation. The result is presented in the form of xEsyy, where x is the mantissa, syy is the exponent, for example 0E+00, 2E-09. Note that the bitErrorRate is an estimate only. For more reliable test results, the test should be done over a long period. Multiple tests would also improve the confidence level of the test results.

This entry controls the addition and deletion of mscLpE3G832 components.

A single entry in the table represents a single mscLpE3G832 component.

This variable is used as the basis for SNMP naming of mscLpE3G832 components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpE3G832 tables.

This variable represents the index for the mscLpE3G832 tables.

This group contains the provisionable data for the G832 component.

An entry in the mscLpE3G832ProvisionedTable.

This attribute indicates the E.164 address which is to be encoded in the trail access point identifier, which is transmitted using the Trail Trace (TR) field of the transmitted E3 Frame. Both the expected trail access point identifier and the transmitted trail access point identifier are provisionable attributes of the G832 component. The 16 byte Trail Trace frame is composed of one byte containing a frame start marker and a CRC-7 calculation over the previous frame, and 15 bytes for transporting an E.164 address. If less than the full 15 bytes are used, the address is padded with NULL characters.

This attribute indicates the E.164 address which is expected in the trail access point identifier, which is transmitted using the Trail Trace (TR) field of the transmitted E3 Frame. Both the expected trail access point identifier and the transmitted trail access point identifier are provisionable attributes of the G832 component. The 16 byte Trail Trace frame is composed of one byte containing a frame start marker and a CRC-7 calculation over the previous frame, and 15 bytes for transporting an E.164 address. If less than the full 15 bytes are used, the address is padded with NULL characters.

This group contains the operational data for the G832 component.

An entry in the mscLpE3G832OperationalTable.

This attribute displays whether the Unexpected Payload Type (UPT) alarm state has been entered. The UPT alarm state is entered when UPT defects have been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds. The UPT defect is reported when a received frame fails to agree with the expected Payload Type. If the UPT defects are intermittently occurring, the UPT defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle.. The UPT alarm is cleared when the Payload Type in the received frame agrees with the expected Payload Type for a period of 10 seconds +/- 0.5 seconds. The unexpectedPayloadType attribute is always set to off when the E3 component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether the Trail Trace Mismatch (TTM) alarm state has been entered. The TTM alarm state is entered when TTM defects have been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds. The TTM defect is reported when the trail access point identifier contained in the Trail Trace (TR) field in the received frame fails to agree with the expected identifier. If the TTM defects are intermittently occurring, the TTM defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The TTM alarm is cleared when the trail access point identifier in the received frame agrees with the expected identifier for a period of 10 seconds +/- 0.5 seconds. The trailTraceMismatch attribute is always set to off when the E3 component has been locked and left offline. Both the expected trail access identifier and the transmitted trail access identifier are provisionable attributes of the G832 component. Enumeration: 'on': 0, 'off': 1.

Indicates whether or not the timing source at the far-end node is traceable to a Primary Reference Clock. The timingMarker indication is controlled by the timing marker bit in the G832 MA byte. If the received timing marker bit is 1 for five consecutive frames, and five consecutive 0s are not received for two seconds, the timingMarker indication will be set to not traceable. If the received timing marker bit is 0 for five consecutive frames and five consecutive 1s are not received for two seconds, the timingMarker indication will be set to traceable. Enumeration: 'traceable': 1, 'notTraceable': 0.

This attribute indicates the 15 byte E.164 address which is currently being received in the trail trace (TR) field of the E3 G832 frame. If this attribute differs from the provisioned trailTraceTransmitted string a trail trace mismatch (TTM) defect is reported, possibly resulting in a TTM alarm, as described for operational attribute trailTraceMismatch.

This group contains the statistical data for the G832 component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpE3G832StatsTable.

This attribute indicates the number of seconds that the E3 line has not suffered any G832 errors.

A count of E3 frames containing a Far-End Block Error (FEBE). A FEBE is reported over the FEBE bit each time the far-end terminal detects a BIP-8 error in a received E3 frame. For second intervals where Far End Unavailable Seconds (FEUAS) or Far End Severely Errored Seconds (FESES) are counted, counting of FECVs is inhibited. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Far-End Errored Seconds (FEES). A FEES is declared for second intervals containing with one or more Far-End Coding Violations (FECV) or one or more Far-End Receive Failure (FERF) defects. A FERF defect occurs when the FERF bit in the received frame is set to one. For second intervals where Far End Unavailable Seconds (FEUAS) are counted, counting of FEESs is inhibited.

This attribute indicates the total number of Far-End Severely Errored Seconds (FESESs). A FESES is declared for second intervals containing more than 34 Far-End Coding Violations (FECV) or one or more Far-End Receive Failure (FERF) defects. For second intervals where a Far-End Severely Errored Seconds (FESES) is counted, counting of FECVs is inhibited. For second intervals where Far End Unavailable Seconds (FEUAS) are counted, counting of FESESs is inhibited.

This attribute indicates the total number of Far-End SEF/AIS Seconds (FESAS). A FESAS is declared for second intervals containing one or more Far-End Receive Failure (FERF) defects. For second intervals where Far End Unavailable Seconds (FEUAS) are counted, counting of FESAS is inhibited.

This attribute indicates the total number of one second intervals for which the E3 far-end path is unavailable. The E3 far-end path becomes unavailable at the onset of 10 consecutive Far End Severely Errored Seconds (FESES). It comes available at the onset of 10 contiguous seconds with no FESES. The unavailable time includes the initial 10 seconds to enter the unavailable state but not the 10 seconds to exit the state For second intervals where FEUAS is counted, counting of Far End Coding Violations (FECV), Far- End Errored Seconds (FEES), Far-End Severely Errored Seconds (FESES) and Far-End SefAis Seconds (FESAS) are inhibited.

This entry controls the addition and deletion of mscLpE3Plcp components.

A single entry in the table represents a single mscLpE3Plcp component.

This variable is used as the basis for SNMP naming of mscLpE3Plcp components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpE3Plcp tables.

This variable represents the index for the mscLpE3Plcp tables.

This group contains the operational data for the PLCP component.

An entry in the mscLpE3PlcpOperationalTable.

This attribute displays whether a PLCP Loss Of Frame (LOF) failure alarm state has been entered. An LOF failure is declared when a PLCP LOF defect persists for 2.5 s +/- 0.5 s. An LOF defect occurs when an OOF (Out of Frame) state persists for more than 1 ms. If the OOF events are intermittent, the LOF defect counter is decremented at a rate of 1/12 (for DS3 PLCP) or 1/9 (for G.751 E3 PLCP) of the incrementing rate, with all measurements based on a 200 ms polling cycle. An OOF event (also known as a PLCP SEF event) is declared when an error is detected in both the A1 and A2 octets, or when two consecutive POHIDs are found in error. OOF is removed when two valid sets of framing octets and two valid and sequential POHID octets have been found. The LOF defect is removed when the defect counter reaches zero, i.e. when OOF events are absent for more than 12 ms (DS3 PLCP) or 9 ms (G.751 E3 PLCP). LOF failure alarm is cleared when LOF defect is absent for 10.0 s +/- 0.5 s The DS3 or E3 component goes into an operational state of disabled until the LOF failure alarm is cleared. The terminal declaring the LOF failure alarm will transmit a PLCP RAI signal to the far-end for the duration of the alarm. The lofAlarm attribute is always set to off when the DS3 or E3 component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a PLCP Remote Alarm Indication (RAI) failure alarm state has been entered. An RAI failure alarm occurs when ten consecutive PLCP RAI bits (bit 5 in the G1 byte) are high on the incoming line. An RAI failure alarm is cleared when ten consecutive RAI bits are set to 0. Note: Some standards call this alarm RFI. The rxRaiAlarm attribute is always set to off when the DS3 or E3 component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This group contains the statistical data for the PLCP component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpE3PlcpStatsTable.

This attribute indicates the number of seconds during which the near-end PLCP path layer had no errors.

This attribute indicates the total number of BIP-8 Errors, framing pattern octet errors, and path overhead identification errors detected in received PLCP frames. Counting of PLCP CV is inhibited for second intervals where PLCP Severely Errored Framing Seconds (SEFS) or PLCP Unavailable Seconds (UAS) are counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the number of seconds containing one or more PLCP Coding Violations (CV) or in which a PLCP Severely Errored Framing Second (SEFS) was counted. Counting of PLCP ES is inhibited during second intervals where PLCP Unavailable Seconds (UAS) are counted.

This attribute indicates the number of seconds containing 5 or more PLCPCVs or in which a PLCPSEFS was counted (i.e. a PLCP OOF event occurred). Counting of PLCP SES is inhibited during second intervals where PLCP Unavailable Seconds (UAS) are counted.

This attribute indicates the number of seconds containing one or more PLCP Severely Errored Frame (SEF) events. An SEF event is equivalent to a PLCP OOF (Out of Frame) event. Counting of PLCPP SEFSs is inhibited for second intervals where PLCP Unavailable Seconds (UAS) are counted.

This attribute indicates the number of seconds when the near-end PLCP layer is unavailable. The PLCP Path Layer becomes unavailable at the declaration of PLCP LOF (Loss of Frame) failure alarm state. The PLCP Path Layer becomes available again only after clearing this condition. For second intervals where PLCP UAS are counted, counting of PLCP Severely Errored Framing Seconds (SEFS), PLCP Coding Violations (CV), PLCP Errored Seconds (ES), PLCP Severely Errored Seconds (SES) and PLCP Far-End Severely Errored Seconds (FESES) is inhibited.

This attribute indicates the number of seconds during which the far- end PLCP path layer had no errors.

This attribute indicates the total number of PLCP Far-End Block Errors (FEBE) reported by the far-end terminal. Counting of FEBEs is inhibited for second intervals where PLCP Far-End Unavailable Seconds (FEUAS) are counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the number of seconds containing one or more PLCP Far-End Coding Violations (FECV). Counting of PLCP FEES is inhibited during second intervals where PLCP Far-End Unavailable Seconds (FEUAS) are counted.

This attribute indicates the number of seconds containing 5 or more PLCP Far-End Coding Violations (FECV). Counting of PLCP FESES is inhibited for second intervals where PLCP Far-End Unavailable Seconds (FEUAS) are counted.

This attribute indicates the number of seconds during which the PLCP far end is unavailable. The PLCP Path Layer becomes unavailable at the declaration of PLCP RAI (Remote Alarm Indication). Service becomes available again after this condition is cleared. For second intervals where PLCP FEUAS are counted, counting of PLCP Far-End Coding Violations (FECV), PLCP Far- End Errored Seconds (FEES), and PLCP Far-End Severely Errored Seconds (FESES) is inhibited.

This entry controls the addition and deletion of mscLpE3Cell components.

A single entry in the table represents a single mscLpE3Cell component.

This variable is used as the basis for SNMP naming of mscLpE3Cell components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpE3Cell tables.

This variable represents the index for the mscLpE3Cell tables.

This group contains the provisioning attributes for the AtmCell component.

An entry in the mscLpE3CellProvTable.

This attribute defines the time during which a Loss of Cell Delineation (LCD) defect should be observed before declaring an LCD alarm (alarm 70115501). The time is specified in milliseconds.

Cell scrambling, as defined by ITU-T Recommendation I.432., can provide a solution to the problem of transmission equipment which is sensitive to certain bit patterns in the ATM cell payload. This attribute controls whether or not the cell payload is scrambled. It defaults to off for DS1 interfaces, and on for all other interfaces. Note that this setting must be the same at both ends of the link. Enumeration: 'on': 1, 'off': 0.

This attribute specifies whether the port corrects single bit errors detected in the headers of received cells. If single bit errors are corrected, the affected cells are passed up to the ATM layer according to normal operation. If single bit errors are not corrected, these errored cells are discarded by the physical layer. Note that cells containing multiple bit errors in their headers are always discarded. Single bit HEC error correction must remain off for the following card types: 3pDS1Atm, 8pDS1Atm, 3pE1Atm, 8pE1Atm, 2pJ6MAtm, 3pDS3Atm, and 3pE3Atm. Enumeration: 'on': 1, 'off': 0.

This group contains the common operational attributes for the AtmCell component.

An entry in the mscLpE3CellOperTable.

This attribute displays whether the Loss of Cell Delineation (LCD) failure alarm state has been entered. This state is entered when LCD defects have been observed and accumulated for a period of time specified through the alarmActDelay attribute. In ATM cell direct mapping mode, an LCD defect occurs when Out of Cell Delineation (OCD) anomaly persists for x milliseconds, and disappears when the Out of Cell Delineation (OCD) is absent for x msec. An OCD anomaly occurs when 7 consecutive incorrect HECs have been detected. An OCD anomaly terminates when 6 consecutive correct HECs have been detected. For an AtmCell component located under a DS3 or E3 component with mapping = PLCP, the LCD defect is directly derived from the PLCP LOF defect. If LCD defects are intermittently occurring, the LCD defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle The component under which is located the AtmCell component goes into an operational state of disabled until the LCD alarm condition is cleared. The condition is cleared after the LCD defect has not been reported for a period of 10 seconds +/- 0.5 seconds. The lcdAlarm attribute is always set to off when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked. Enumeration: 'on': 0, 'off': 1.

This group contains the Statistics attribute for the AtmCell component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpE3CellStatsTable.

This attribute indicates the number of uncorrectable ATM cell header errors that have been detected. Counting of uncorrectableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected.

This attribute indicates the total number of ATM Cell Severely Errored Seconds (SESs) that have been counted. In direct mapping mode, an ATM Cell SES is declared for second intervals containing one or more Out of Cell Delineation (OCD) defects. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected. In PLCP mapping mode, an ATM Cell SES is declared for second intervals containing one or more PLCP LOF defects. Counting of uncorrectableHeaderErrors (ucErr) and correctableHeaderErrors (cErr) is inhibited when the OCD defect is present.

This attribute is the ratio of the number of valid, assigned cells received on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute is the ratio of the number of valid, assigned cells transmitted on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute indicates the number of correctable ATM cell header errors that have been detected and corrected. Counting of correctableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected

This group contains all of the provisioning data for a E3 component.

An entry in the mscLpE3ProvTable.

This attribute defines the line length for equalization calculations for the E3 line. The line length range is between 0 and 300 metres (1 metres = 3.28 feet).

This attribute defines the type of clocking source used for synchronizing the E3 transmit clock: local means direct use of the local clock oscillator at its centre frequency; line means use of a signal phase-locked to the incoming E3 line rate; module means the use of a signal phase-locked to the CP reference clock. Note that the multiport cell-based cards have one common clock source for each of the three ports. For this reason, the following rules apply for the value of clockingSource across the board's three ports: All three clockingSource values must be 'local' OR All three clockingSource values must be 'module' OR One clockingSource value must be 'line' and the other two must be 'otherPort'. The default value for this attribute will be module if a CP clock is available, and local otherwise. Enumeration: 'line': 1, 'local': 0, 'otherPort': 4, 'module': 2.

This attribute defines the link to the software stack. It defines which application is running on top of the E3 component.

This attribute indicates if ATM cells will be mapped directly into the E3 payload, or whether PLCP mapping will be used. The PLCP component will appear under the E3 component when this attribute is set to plcp. This attribute will be ignored when set on frame- based cards. Enumeration: 'plcp': 1, 'direct': 0.

This attribute indicates if the framing mode will be in accordance with the CCITT G.751 or G.832 specification. The G832 component will appear under the E3 component when this attribute is set to g832. This attribute may only be set on cell-based card types. Note also that this attribute may only be set to g751 if the mapping attribute is set to plcp. The default value of this attribute will be g751 for frame-based cards, and g832 for cell-based cards. Note: when E3 framing is changed from g832 to g751, the G832 component must be deleted. Enumeration: 'g832': 1, 'g751': 0.

This attribute specifies the time interval between the detection of a sustained link failure and the activation of an alarm. It is provisionable for E3 cards.

This attribute specifies the alarm scan timer polling interval. It determines how frequently the status of the link is monitored after a first link error interrupt. It is provisionable for E3 cards.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscLpE3CidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains the attributes pertaining to the vendor of the equipment.

An entry in the mscLpE3AdminInfoTable.

This is the name of the vendor supplying the facility.

Any miscellaneous text about the facility.

This group contains the provisionable attributes for the ifEntry.

An entry in the mscLpE3IfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the mscLpE3OperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpE3StateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains the common operational data for E3 component.

An entry in the mscLpE3OperTable.

This attribute displays whether a Loss Of Signal (LOS) alarm state has been entered. An LOS alarm state is entered when LOS defects has been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds. An LOS defect is detected at the E3 line interface upon observing N continuous pulse positions with no pulses of either positive or negative polarity, where N is between 10 and 255. If the LOS defects are intermittently occurring, the LOS defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The E3 component goes into an operational state of disabled until the LOS alarm condition is cleared. The LOS alarm state is cleared when the LOS defects are absent for a period of 10 seconds +/- 0.5 seconds. The losAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a Loss Of Frame (LOF) alarm state has been entered. An LOF alarm state is entered when Severely Errored Frame (SEF) defects have been detected and accumulated for a period of 2.5 seconds +/- 0.5 seconds. An E3 SEF defect is reported after detecting Frame Alignment Signal (FAS) errors on 4 consecutive E3 frames received on the incoming line. If the LOF defects are intermittently occurring, the LOF defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The E3 component goes into an operational state of disabled until the LOF alarm condition is cleared. The condition is cleared when E3 framing has been achieved for a period of 10 seconds +/- 0.5 seconds. As long as SEF defects are detected, the node also transmits the far-end SEF/AIS (in G.751 E3) or FERF (in G.832) defect indicator over the outgoing line. The txRai attribute is set to on when transmitting the far-end SEF/AIS defect indicator on the outgoing line. The lofAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an Alarm Indication Signal (AIS) alarm when state has been entered. An AIS alarm state is entered when AIS defects have been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds on the incoming E3 line. An AIS defect is the occurrence of the AIS (unframed signal with a density of zeros below a certain threshold such as defined by ITU Recommendation G.775). If the AIS defects are intermittently occurring, the AIS defect accumulator is decremented at a rate of 1/ 10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The E3 component goes into an operational state of disabled until the AIS alarm condition is cleared (after AIS has been no longer detected for a period of 10 seconds +/- 0.5 seconds). As long as AIS is detected on the incoming line, the node also transmits the far-end SEF/AIS (in G.751 E3) or FERF (in G.832) defect indicator over the outgoing line. The txRai attribute is set to on when transmitting the far-end SEF/AIS defect indicator on the outgoing line. The rxAisAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a Remote Alarm Indication (RAI) alarm state has been entered. A RAI alarm state is entered when far- end SEF/AIS defects (or Far-End Receive Failure (FERF) defects in G.832 E3 Framing mode) have been observed and accumulated for a period of 2.5 seconds +/- 0.5 seconds on the E3 incoming line. If the RAI defects are intermittently occurring, the RAI defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The E3 component goes into an operational state of disabled until the RAI alarm condition is cleared. The condition is cleared when the far-end defect indicator has not been detected for 10 seconds +/- 0.5 seconds. The declaration of a RAI Alarm is usually a signal that the far end facility is unable to gain synchronization. The rxRaiAlarm attribute is always set to off when the component has been locked and left offline. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an AIS alarm is being transmitted on the E3 line. AIS is transmitted on the outgoing line when the E3 component is locked and not used for operational testing. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether the far-end SEF/AIS defect indicator is transmitted over the outgoing line when the E3 component has been unlocked or used in operational testing. When the E3 component is locked and not used in operational testing, this attribute is always set to off. The far-end SEF/AIS defect indicator is transmitted over the outgoing line when SEF/AIS defects are detected on the incoming line. In G.832 E3 Framing mode, the FERF bit is set to '1' to transmit the SEF/AIS defect indicator. Enumeration: 'on': 0, 'off': 1.

This group contains the common operational data for E3 component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpE3StatsTable.

This attribute indicates the total number of seconds since the E3 component has been activated and been in unlocked state or used for operational testing. All the other error counts that follow as well as each E3 subcomponent's error counts can be updated when this count is active.

This attribute indicates the number of seconds that the E3 port has been in an error free state.

This attribute indicates the total number of Line Code Violations (LCV) detected. An E3 Line Code Violation is an HDB3 coded signal error. LCV counting is inhibited for second intervals where a Line Severely Errored Second (LSES) is counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Line Errored Seconds (LES) that have been counted. A LES is declared for interval seconds containing one or more Line Code Violations (LCV) or one or more Loss Of Signal (LOS) defects.

This attribute indicates the total number of Line Severely Errored Seconds (LSES) that have been counted. A LSES is declared for second intervals containing more than 34 Line Code Violations (LCV) or one or more Loss of Signal (LOS) defects.

This attribute indicates the total number of Line LOS Seconds (LOSS) that have been counted. A LOSS is declared for second intervals containing one or more Loss of Signal (LOS) defects.

This attribute indicates the total number of times that a line failure (LOS failure) has been declared. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Path Code Violations (PCV) detected. An E3 PCV is an error in the Frame Alignment (FA) signal, or, in G.832 Framing Mode, an error in the Frame Alignment signal or a BIP-8 error. PCV counting is inhibited over second intervals where a Path Severely Errored Second (PSES) is counted. Counting of PCVs is also inhibited over second intervals where a Path Unavailable Second (PUAS) is counted. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This attribute indicates the total number of Path Errored Seconds (PES) that have been counted. A PES is declared for second intervals containing one or more Path Code Violations (PCV) or one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects. Counting of Path Errored Seconds is inhibited when a Path Unavailable Second (PUAS) is counted over the monitored second.

This attribute indicates the total number of Path Severely Errored Seconds (PSES) that have been counted. A PSES is declared for second intervals containing more than 22 (G.751 E3) or 34 (G.832 E3) Path Code Violations (PCV) or one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects. Counting of PSESs is inhibited when a Path Unavailable Second (PUAS) is counted over the monitored second.

This attribute indicates the total number of Path SEF/AIS Seconds (PSAS). A PSAS is declared for second intervals containing one or more Severely Errored Frame (SEF) or Alarm Indication Signal (AIS) defects. Counting of PSAS is inhibited when Path Unavailable Seconds (PUAS) is counted over the monitored second.

This attribute indicates the total number of one second intervals for which the E3 path is unavailable. The E3 path becomes unavailable at the onset of 10 consecutive Path Severely Errored Seconds (PSES). The 10 PSESs are included in the unavailable time. Once unavailable, the E3 path becomes available at the onset of 10 contiguous seconds with no PSES. The 10 seconds with no PSES are excluded from the unavailable time. For second intervals where PUAS is counted, counting of Path Code Violations (PCV), Path Errored Seconds (PES), Path Severely Errored Seconds (PSES) and Path SefAis Seconds (PSAS) is inhibited.

This attribute indicates the total number of times that a path failure (LOF/AIS failure) has been declared. This attribute is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

This entry controls the addition and deletion of mscLpDS1 components.

A single entry in the table represents a single mscLpDS1 component.

This variable is used as the basis for SNMP naming of mscLpDS1 components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1 tables.

This variable represents the index for the mscLpDS1 tables.

This entry controls the addition and deletion of mscLpDS1Chan components.

A single entry in the table represents a single mscLpDS1Chan component.

This variable is used as the basis for SNMP naming of mscLpDS1Chan components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1Chan tables.

This variable represents the index for the mscLpDS1Chan tables.

This entry controls the addition and deletion of mscLpDS1ChanTest components.

A single entry in the table represents a single mscLpDS1ChanTest component.

This variable is used as the basis for SNMP naming of mscLpDS1ChanTest components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1ChanTest tables.

This variable represents the index for the mscLpDS1ChanTest tables.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS1ChanTestStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains all of the operational data for a Test component.

An entry in the mscLpDS1ChanTestSetupTable.

This attribute records the purpose of the test so that the test results can be associated and properly analyzed.

This attribute is the type of test to be run. The available test types include the following: card test sets up an internal loop on the board and runs a bit error rate test. manual test assumes the line is looped back externally and a bit error rate test is performed. localLoop test loops back the local modem and performs a bit error rate test. remoteLoop test loops back the remote modem (or CSU) and performs a bit error rate test. externalLoop test loops back the line to the far end. payloadLoop test only loops back the payload data received from the incoming line. remoteLoopThisTrib loops this particular tributary back at the far end, using services provided by the parent. v54RemoteLoop initiates a V.54 Remote Loopback test. pn127RemoteLoop initiates a PN127 Remote Loopback test. Note that not all test types are not supported by all function processors. Enumeration: 'externalLoop': 4, 'pn127RemoteLoop': 8, 'payloadLoop': 5, 'manual': 1, 'remoteLoop': 3, 'v54RemoteLoop': 7, 'remoteLoopThisTrib': 6, 'localLoop': 2, 'card': 0.

This attribute defines the size of the test data frames in number of bytes.

This attribute defines the type of data pattern generation to use. The following lists the available pattern types: ccitt32kBitPattern is a pseudo-random sequence of 32 kbit. ccitt8MBitPattern is a pseudo-random sequence of 8Mbit. customizedPattern is the pattern defined in the customizedPattern attribute. Enumeration: 'ccitt32kBitPattern': 0, 'customizedPattern': 2, 'ccitt8MBitPattern': 1.

This attribute allows a customized 32 bit pattern to be defined for use in the test data frames. This attribute is used when the attribute frmPatternType is set to CustomizedPattern. Note that a 55 hex pattern is an alternating 1 and 0 pattern.

This attribute specifies the time delay (in seconds) between when the test expects the loop to have been set up, to when the test data actually starts to be transmitted. This attribute is to accommodate some non-standard equipment that requires extra time for setting up a requested loop. This attribute is ignored when the test type is set to externalLoop.

This attribute defines the interval (in minutes) between which interim test results are to be displayed. Results are displayed at the operator console at which the test was started. When the test type is set to externalLoop, this attribute is ignored. There will be no display of results if displayInterval is set to 0. This attribute can be changed anytime.

This attribute is the duration (in minutes) that test data will be transmitted. In the case of an externalLoop, this is the time that the loop is in effect. Note that dataStartDelay does not apply to the externalLoop.

This group contains all the statistics related attributes of the Test component.

An entry in the mscLpDS1ChanTestResultsTable.

This attribute is the number of minutes elapsed since the test started for an externalLoop test. For a data test, this is the time since test data was first transmitted.

This attribute is the number of minutes remaining before the test is to be stopped according to the duration attribute.

This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values. Enumeration: 'patternSyncFailed': 7, 'unknown': 2, 'neverStarted': 3, 'hardwareReconfigured': 5, 'loopCodeSyncFailed': 6, 'stoppedByOperator': 1, 'testTimeExpired': 0, 'testRunning': 4, 'patternSyncLost': 8.

This attribute is the total number of bits sent during the test period. As long as the line speed of the hardware interface is less than 70 Mbit/s, this counter is not expected to reach the maximum value.

This attribute is the total number of bytes sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of frames sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of bits received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach the maximum value.

This attribute is the total number of bytes received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is the total number of frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the total number of errored frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the calculated bit error rate on the link. Test data are generated and sent in frames of a preset size (frameSize). The Test component will try to estimate the number of bit errors in any errored frame which is identifiable. The statistics will be updated accordingly. A lost frame (may be due to an error on the flag sequence) will be discarded for the bit error rate calculation. The result is presented in the form of xEsyy, where x is the mantissa, syy is the exponent, for example 0E+00, 2E-09. Note that the bitErrorRate is an estimate only. For more reliable test results, the test should be done over a long period. Multiple tests would also improve the confidence level of the test results.

This entry controls the addition and deletion of mscLpDS1ChanCell components.

A single entry in the table represents a single mscLpDS1ChanCell component.

This variable is used as the basis for SNMP naming of mscLpDS1ChanCell components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1ChanCell tables.

This variable represents the index for the mscLpDS1ChanCell tables.

This group contains the provisioning attributes for the AtmCell component.

An entry in the mscLpDS1ChanCellProvTable.

This attribute defines the time during which a Loss of Cell Delineation (LCD) defect should be observed before declaring an LCD alarm (alarm 70115501). The time is specified in milliseconds.

Cell scrambling, as defined by ITU-T Recommendation I.432., can provide a solution to the problem of transmission equipment which is sensitive to certain bit patterns in the ATM cell payload. This attribute controls whether or not the cell payload is scrambled. It defaults to off for DS1 interfaces, and on for all other interfaces. Note that this setting must be the same at both ends of the link. Enumeration: 'on': 1, 'off': 0.

This attribute specifies whether the port corrects single bit errors detected in the headers of received cells. If single bit errors are corrected, the affected cells are passed up to the ATM layer according to normal operation. If single bit errors are not corrected, these errored cells are discarded by the physical layer. Note that cells containing multiple bit errors in their headers are always discarded. Single bit HEC error correction must remain off for the following card types: 3pDS1Atm, 8pDS1Atm, 3pE1Atm, 8pE1Atm, 2pJ6MAtm, 3pDS3Atm, and 3pE3Atm. Enumeration: 'on': 1, 'off': 0.

This group contains the common operational attributes for the AtmCell component.

An entry in the mscLpDS1ChanCellOperTable.

This attribute displays whether the Loss of Cell Delineation (LCD) failure alarm state has been entered. This state is entered when LCD defects have been observed and accumulated for a period of time specified through the alarmActDelay attribute. In ATM cell direct mapping mode, an LCD defect occurs when Out of Cell Delineation (OCD) anomaly persists for x milliseconds, and disappears when the Out of Cell Delineation (OCD) is absent for x msec. An OCD anomaly occurs when 7 consecutive incorrect HECs have been detected. An OCD anomaly terminates when 6 consecutive correct HECs have been detected. For an AtmCell component located under a DS3 or E3 component with mapping = PLCP, the LCD defect is directly derived from the PLCP LOF defect. If LCD defects are intermittently occurring, the LCD defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle The component under which is located the AtmCell component goes into an operational state of disabled until the LCD alarm condition is cleared. The condition is cleared after the LCD defect has not been reported for a period of 10 seconds +/- 0.5 seconds. The lcdAlarm attribute is always set to off when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked. Enumeration: 'on': 0, 'off': 1.

This group contains the Statistics attribute for the AtmCell component. Each attribute type is a non-negative integer which monotonically increases until it reaches a maximum value, at which point it wraps around and starts increasing again from zero.

An entry in the mscLpDS1ChanCellStatsTable.

This attribute indicates the number of uncorrectable ATM cell header errors that have been detected. Counting of uncorrectableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected.

This attribute indicates the total number of ATM Cell Severely Errored Seconds (SESs) that have been counted. In direct mapping mode, an ATM Cell SES is declared for second intervals containing one or more Out of Cell Delineation (OCD) defects. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected. In PLCP mapping mode, an ATM Cell SES is declared for second intervals containing one or more PLCP LOF defects. Counting of uncorrectableHeaderErrors (ucErr) and correctableHeaderErrors (cErr) is inhibited when the OCD defect is present.

This attribute is the ratio of the number of valid, assigned cells received on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute is the ratio of the number of valid, assigned cells transmitted on the link to the nominal link capacity. The utilization is calculated over a period of one minute. This attribute is always set to 0 when the parent of the AtmCell component has been locked and left offline. This can also happen when the Path or Channel component has been suspended since its parent has been locked.

This attribute indicates the number of correctable ATM cell header errors that have been detected and corrected. Counting of correctableHeaderErrors is inhibited when an Out of Cell Delineation (OCD) defect is present. An OCD defect occurs when seven consecutive incorrect HECs have been detected. An OCD defect terminates when six consecutive correct HECs have been detected

This entry controls the addition and deletion of mscLpDS1ChanTc components.

A single entry in the table represents a single mscLpDS1ChanTc component.

This variable is used as the basis for SNMP naming of mscLpDS1ChanTc components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1ChanTc tables.

This variable represents the index for the mscLpDS1ChanTc tables.

This group contains all specific provisioning data for a Tc component.

An entry in the mscLpDS1ChanTcProvTable.

This attribute specifies the trunk conditioning data byte to be substituted into the timeslots defined by the Chan component under fault conditions. replacementData can be set to any two digit hexadecimal number. The following are recommended values: DS1 MUX Out Of Service Code = 0x1A E1 MUX Out Of Service Code = 0xFF

This attribute specifies the time duration in seconds for which signalOne is substituted into the appropriate signaling bits, when a lineType that uses CAS has been defined. When signalOneDuration has expired signalTwo is substituted into the appropriate signaling bits. If signalOneDuration is set to zero then only signalTwo is substituted into the appropriate signaling bits during error conditions. signalOneDuration can be set to any integer value from 0 to 60 seconds.

This group contains all specific operational data for a Tc component.

An entry in the mscLpDS1ChanTcOpTable.

This attribute indicates the status of locally generated trunk conditioning towards the ATM network. When trunk conditioning is being locally generated towards the ATM network, ingressConditioning is set to on. When trunk conditioning is not being locally generated towards the ATM network, ingressConditioning is set to off. Trunk conditioning is transmitted towards the ATM network under the following conditions: lossOfSignal (LOS) lossOfFrame (LOF) remoteAlarmIndication (RAI) alarmIndicationSignal (AIS) bufferUnderflow (BU) and in addition for E1: lossOfMultiframe (LOMF) receiveMultiframeRemoteAlarmIndication (RMRAI) Enumeration: 'on': 1, 'off': 0.

This attribute indicates the status of locally generated trunk conditioning towards the PDH line. When trunk conditioning is being locally generated towards the PDH line, egressConditioning is set to on. When trunk conditioning is not being locally generated towards the PDH line, egressConditioning is set to off. Trunk conditioning is transmitted towards the PDH line under the following conditions: bufferUnderflow (BU) AAL1 protocol errors. Enumeration: 'on': 1, 'off': 0.

This attribute specifies the value to be substituted into the ABCD signaling bits for the timeslots defined by the Chan component under fault conditions. The value will be substituted for the duration provisioned in signalOneDuration when a lineType that uses CAS has been defined. For a lineType of d4Cas (Super Frame), signaling bits C and D are required to equal bits A and B respectively.

An entry in the mscLpDS1ChanTcSigOneTable.

This variable represents the mscLpDS1ChanTcSigOneTable specific index for the mscLpDS1ChanTcSigOneTable. Enumeration: 'a': 3, 'c': 1, 'b': 2, 'd': 0.

This variable represents an individual value for the mscLpDS1ChanTcSigOneTable.

This attribute specifies the value to be substituted into the ABCD signaling bits for the timeslots defined by the Chan component under fault conditions. The value will be substituted after the duration provisioned in signalOneDuration has expired and when a lineType that uses CAS has been defined. For a lineType of d4Cas (Super Frame), signaling bits C and D are required to equal bits A and B respectively.

An entry in the mscLpDS1ChanTcSigTwoTable.

This variable represents the mscLpDS1ChanTcSigTwoTable specific index for the mscLpDS1ChanTcSigTwoTable. Enumeration: 'a': 3, 'c': 1, 'b': 2, 'd': 0.

This variable represents an individual value for the mscLpDS1ChanTcSigTwoTable.

This group contains all of the provisional data for a Channel component.

An entry in the mscLpDS1ChanProvTable.

This attribute contains the list of timeslots that are used by the Channel component. Valid numbers are 1-24 for a Channel used by a DS1 component, and 1-31 for a Channel used by an E1 component. Description of bits: notused0(0) n1(1) n2(2) n3(3) n4(4) n5(5) n6(6) n7(7) n8(8) n9(9) n10(10) n11(11) n12(12) n13(13) n14(14) n15(15) n16(16) n17(17) n18(18) n19(19) n20(20) n21(21) n22(22) n23(23) n24(24) n25(25) n26(26) n27(27) n28(28) n29(29) n30(30) n31(31)

This attribute selects the data rate of the timeslots in a channel of a DS1 component. For E1, the data rate of the timeslots will always be 64kbit/s regardless of this attribute. When doNotOverride is selected for a channel on a DS1, the data rate of the channel's timeslots are dependant on the zeroCoding selection of the DS1 component. If the zeroCoding is B8ZS (where supported on the FP) or none, the timeslot's data rate will be 64kbit/ s. If the zeroCoding option is bit7Stuffing, the data rate of a timeslot will be 56kbit/s. When 56k is selected for a channel on a DS1, the least significant bit of each timeslot of this Channel will always be set to 1 and not used for data. The data rate for the timeslots of this channel is therefore restricted to 56kbit/s. One application of this attribute is to allow a DS1 line to support mixing channels that originate from lines that use different zeroCoding schemes. Enumeration: 'n56k': 0, 'doNotOverride': 1.

This attribute defines the link to the software stack. It defines which application is running on top of this hardware component.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscLpDS1ChanCidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains the provisionable attributes for the ifEntry.

An entry in the mscLpDS1ChanIfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the mscLpDS1ChanOperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS1ChanStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains all of the operational data for a Channel component.

An entry in the mscLpDS1ChanOperTable.

This attribute displays the measured link speed of the Channel component.

This group contains the attributes pertaining to the vendor of the equipment.

An entry in the mscLpDS1ChanAdminInfoTable.

This is the name of the vendor supplying the facility.

Any miscellaneous text about the facility.

This entry controls the addition and deletion of mscLpDS1Test components.

A single entry in the table represents a single mscLpDS1Test component.

This variable is used as the basis for SNMP naming of mscLpDS1Test components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1Test tables.

This variable represents the index for the mscLpDS1Test tables.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS1TestStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains all of the operational data for a Test component.

An entry in the mscLpDS1TestSetupTable.

This attribute records the purpose of the test so that the test results can be associated and properly analyzed.

This attribute is the type of test to be run. The available test types include the following: card test sets up an internal loop on the board and runs a bit error rate test. manual test assumes the line is looped back externally and a bit error rate test is performed. localLoop test loops back the local modem and performs a bit error rate test. remoteLoop test loops back the remote modem (or CSU) and performs a bit error rate test. externalLoop test loops back the line to the far end. payloadLoop test only loops back the payload data received from the incoming line. remoteLoopThisTrib loops this particular tributary back at the far end, using services provided by the parent. v54RemoteLoop initiates a V.54 Remote Loopback test. pn127RemoteLoop initiates a PN127 Remote Loopback test. Note that not all test types are not supported by all function processors. Enumeration: 'externalLoop': 4, 'pn127RemoteLoop': 8, 'payloadLoop': 5, 'manual': 1, 'remoteLoop': 3, 'v54RemoteLoop': 7, 'remoteLoopThisTrib': 6, 'localLoop': 2, 'card': 0.

This attribute defines the size of the test data frames in number of bytes.

This attribute defines the type of data pattern generation to use. The following lists the available pattern types: ccitt32kBitPattern is a pseudo-random sequence of 32 kbit. ccitt8MBitPattern is a pseudo-random sequence of 8Mbit. customizedPattern is the pattern defined in the customizedPattern attribute. Enumeration: 'ccitt32kBitPattern': 0, 'customizedPattern': 2, 'ccitt8MBitPattern': 1.

This attribute allows a customized 32 bit pattern to be defined for use in the test data frames. This attribute is used when the attribute frmPatternType is set to CustomizedPattern. Note that a 55 hex pattern is an alternating 1 and 0 pattern.

This attribute specifies the time delay (in seconds) between when the test expects the loop to have been set up, to when the test data actually starts to be transmitted. This attribute is to accommodate some non-standard equipment that requires extra time for setting up a requested loop. This attribute is ignored when the test type is set to externalLoop.

This attribute defines the interval (in minutes) between which interim test results are to be displayed. Results are displayed at the operator console at which the test was started. When the test type is set to externalLoop, this attribute is ignored. There will be no display of results if displayInterval is set to 0. This attribute can be changed anytime.

This attribute is the duration (in minutes) that test data will be transmitted. In the case of an externalLoop, this is the time that the loop is in effect. Note that dataStartDelay does not apply to the externalLoop.

This group contains all the statistics related attributes of the Test component.

An entry in the mscLpDS1TestResultsTable.

This attribute is the number of minutes elapsed since the test started for an externalLoop test. For a data test, this is the time since test data was first transmitted.

This attribute is the number of minutes remaining before the test is to be stopped according to the duration attribute.

This attribute indicates either the status of the test or the cause of the test's termination: neverStarted indicates that the test has not yet been started. testRunning indicates that the test has been started. stoppedByOperator indicates that the operator issued a stop command on a test that was running. testTimeExpired indicates that the test ran for the time specified by the test's duration. loopCodeSyncFailed indicates that the local end failed to synchronize to the loopCode pattern. The local end transmits the loopCode pattern to cause the remote end to apply a loopback, after which the local end should receive the loopCode pattern. The exact pattern used to request loopCode depends on the test type. This failure indicates a high rate of transmission errors, or that the remote end has failed to apply the loopback. patternSyncFailed indicates that the local end failed to synchronize to the frmPatternType test pattern, that should have been looped back at the remote end. This failure indicates a high rate of transmission errors or the absence of a loopback. patternSyncLost indicates that the local end gained and then lost synchronization to the returned frmPatternType test pattern. This failure indicates a sudden increase in transmission errors, frame slippage, or the removal of an existing loopback. unknown is set when a reason to terminate other than those listed here is encountered. Note: Only MSA cards support recognition of the failures loopCodeSyncFailed, patternSyncFailed and patternSyncLost. Other cards will not terminate the test under the conditions described by these values. Enumeration: 'patternSyncFailed': 7, 'unknown': 2, 'neverStarted': 3, 'hardwareReconfigured': 5, 'loopCodeSyncFailed': 6, 'stoppedByOperator': 1, 'testTimeExpired': 0, 'testRunning': 4, 'patternSyncLost': 8.

This attribute is the total number of bits sent during the test period. As long as the line speed of the hardware interface is less than 70 Mbit/s, this counter is not expected to reach the maximum value.

This attribute is the total number of bytes sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of frames sent during the test period. This counter is not expected to reach its maximum value.

This attribute is the total number of bits received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach the maximum value.

This attribute is the total number of bytes received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is the total number of frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the total number of errored frames received during the test period. This counter is not expected to reach its maximum value. The counter will wrap around to 0 if it does reach its maximum value.

This attribute is not displayed for ATM cards because the physical layer drops all errored frames at the controller interface. For all other card types, this attribute is the calculated bit error rate on the link. Test data are generated and sent in frames of a preset size (frameSize). The Test component will try to estimate the number of bit errors in any errored frame which is identifiable. The statistics will be updated accordingly. A lost frame (may be due to an error on the flag sequence) will be discarded for the bit error rate calculation. The result is presented in the form of xEsyy, where x is the mantissa, syy is the exponent, for example 0E+00, 2E-09. Note that the bitErrorRate is an estimate only. For more reliable test results, the test should be done over a long period. Multiple tests would also improve the confidence level of the test results.

This entry controls the addition and deletion of mscLpDS1Dsp components.

A single entry in the table represents a single mscLpDS1Dsp component.

This variable is used as the basis for SNMP naming of mscLpDS1Dsp components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1Dsp tables.

This variable represents the index for the mscLpDS1Dsp tables.

This entry controls the addition and deletion of mscLpDS1Audio components.

A single entry in the table represents a single mscLpDS1Audio component.

This variable is used as the basis for SNMP naming of mscLpDS1Audio components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpDS1Audio tables.

This variable represents the index for the mscLpDS1Audio tables.

This group contains all of the provisioning data for a DS1 component.

An entry in the mscLpDS1ProvTable.

This attribute defines the framing of the DS1 line. d4 defines a framing pattern of 12 frames per multiframe. esf defines a framing pattern of 24 frames per multiframe. d4Cas defines a framing pattern of 12 frames per multiframe with channel associated signalling. esfCas defines a framing pattern of 24 frames per multiframe with channel associated signalling. unframed defines an unknown framing pattern for clear channels. For cell-based cards only the default option esf is permitted. Enumeration: 'esf': 1, 'd4': 0, 'unframed': 6, 'd4Cas': 4, 'esfCas': 5.

This attribute defines the zero encoding on the DS1 line. bit7Stuffing sets bit 7 of every timeslot to a one to guarantee ones's density. This reduces the available bandwidth of the channel by 1/8. b8zs substitutes a pattern of bipolar violations if more than 7 zeros in a row are to be transported. ami specifies Alternate Mark Inversion, in which successive marks (ones) alternate between positive and negative polarity voltage signals, and spaces (zeros) are sent as a zero amplitude signal. When zeroCoding is set to ami and lineType is set to d4, it is recommended that raiAlarmType be set to SBit in order to avoid possible mimic RAI alarm. For cell-based cards only the default value b8zs is permitted. Enumeration: 'ami': 2, 'bit7Stuffing': 0, 'b8zs': 1.

This attribute defines the source of the transmit clock for the DS1 line. When local is selected, the crystal on the port generates the clocking for the line. When line is selected, the port synchronizes to the clock from the facility. When module is selected, the ports clock synchronizes to the clock provided by the oscillator on the active CP. When otherPort is selected, the port synchronizes to the port with a clocking source of line. When srtsMode is selected, the port transmit frequency depends on the SRTS (Synchronous Residual Time-Stamp) received over the ATM network. SRTS information is also generated sent over the ATM network. When adaptiveMode is selected, the port transmit frequency continually adapts to match the egress data received from the ATM network. A port with srtsMode or adaptiveMode must have a single Chan which may be linked only to an Aal1Ces.service with serviceType unstructured If the NetworkSynchronization component is present, the default value of this attribute is module, otherwise it defaults to line, except for the 3pDS1Atm card, which it defaults to local. On a 3pDS1Atm card all ports must have the same value, and be either local or module. otherPort is valid only on AAL1 cards. srtsMode is valid only on AAL1 and Multi-Service Access cards. adaptiveMode is valid only on Multi-Service Access cards. On 4DS1Aal1 cards either: all four ports' clockingSource values must be local OR all four ports' clockingSource values must be module OR one port's clockingSource value must be line and the other three must be otherPort. A port can only have srtsMode selected if the other ports are module or srtsMode. Enumeration: 'srtsMode': 4, 'module': 2, 'adaptiveMode': 5, 'otherPort': 3, 'line': 1, 'local': 0.

This attribute defines the method of sending a RAI (Remote Alarm Indication) alarm on a DS1 line. When SBit is selected, RAI alarm is sent by setting the S bit in frame 12. When Bit2 is selected, RAI alarm is sent by setting bit 2 in all timeslots to 0. When fdl is selected, RAI alarm is sent by a repeating pattern of 00 hex and FF hex on the FDL link. Note that for lineType of d4, only the SBit and the Bit2 methods are applicable. Whereas for lineType of esf, only the Bit2 and the fdl methods are applicable. SBit method is recommended if lineType is set to d4 and zeroCoding is set to ami. This will help to avoid potential mimic RAI alarm when 1's density is too low in the data transmitted. For cell-based cards only the default value fdl is permitted. Enumeration: 'sBit': 0, 'bit2': 1, 'fdl': 2.

This attribute defines the line length (in feet) for equalization calculations for the DS1 line. The value ranges between 0-655. For 8pDS1Atm cards the actual value used for equalization is rounded up to the nearest 110 feet; for all other card types the actual value used is rounded to the nearest 50 feet.

This group contains the attribute for a component's Customer Identifier (CID). Refer to the attribute description for a detailed explanation of CIDs.

An entry in the mscLpDS1CidDataTable.

This attribute holds the Customer Identifier (CID). Every component has a CID. If a component has a cid attribute, the component's CID is the provisioned value of that attribute; otherwise the component inherits the CID of its parent. The top- level component has a CID of 0. Every operator session also has a CID, which is the CID provisioned for the operator's user ID. An operator will see only the stream data for components having a matching CID. Also, the operator will be allowed to issue commands for only those components which have a matching CID. An operator CID of 0 is used to identify the Network Manager (referred to as 'NetMan' in DPN). This CID matches the CID of any component. Values 1 to 8191 inclusive (equivalent to 'basic CIDs' in DPN) may be assigned to specific customers.

This group contains the attributes pertaining to the vendor of the equipment.

An entry in the mscLpDS1AdminInfoTable.

This is the name of the vendor supplying the facility.

Any miscellaneous text about the facility.

This group contains the provisionable attributes for the ifEntry.

An entry in the mscLpDS1IfEntryTable.

The desired state of the interface. The up state indicates the interface is operational. The down state indicates the interface is not operational. The testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This is the index for the IfEntry. Its value is automatically initialized during the provisioning process.

This group includes the Operational Status attribute. This attribute defines the current operational state of this component.

An entry in the mscLpDS1OperStatusTable.

The current state of the interface. The up state indicates the interface is operational and capable of forwarding packets. The down state indicates the interface is not operational, thus unable to forward packets. testing state indicates that no operational packets can be passed. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

This group contains the three OSI State attributes and the six OSI Status attributes. The descriptions generically indicate what each attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241- 7001-150, Passport Operations and Maintenance Guide.

An entry in the mscLpDS1StateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. The OSI Status attributes, if supported by the component, may provide more details, qualifying the state of the component. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

If supported by the component, this attribute indicates the OSI Availability status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value inTest indicates that the resource is undergoing a test procedure. If adminState is locked or shuttingDown, the normal users are precluded from using the resource and controlStatus is reservedForTest. Tests that do not exclude additional users can be present in any operational or administrative state but the reservedForTest condition should not be present. The value failed indicates that the component has an internal fault that prevents it from operating. The operationalState is disabled. The value dependency indicates that the component cannot operate because some other resource on which it depends is unavailable. The operationalState is disabled. The value powerOff indicates the resource requires power to be applied and it is not powered on. The operationalState is disabled. The value offLine indicates the resource requires a routine operation (either manual, automatic, or both) to be performed to place it on-line and make it available for use. The operationalState is disabled. The value offDuty indicates the resource is inactive in accordance with a predetermined time schedule. In the absence of other disabling conditions, the operationalState is enabled or disabled. The value degraded indicates the service provided by the component is degraded in some way, such as in speed or operating capacity. However, the resource remains available for service. The operationalState is enabled. The value notInstalled indicates the resource is not present. The operationalState is disabled. The value logFull is not used. Description of bits: inTest(0) failed(1) powerOff(2) offLine(3) offDuty(4) dependency(5) degraded(6) notInstalled(7) logFull(8)

If supported by the component, this attribute indicates the OSI Procedural status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value initializationRequired indicates (for a resource which doesn't initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState is disabled. The value notInitialized indicates (for a resource which does initialize autonomously) that initialization is required before it can perform its normal functions, and this procedure has not been initiated. The operationalState may be enabled or disabled. The value initializing indicates that initialization has been initiated but is not yet complete. The operationalState may be enabled or disabled. The value reporting indicates the resource has completed some processing operation and is notifying the results. The operationalState is enabled. The value terminating indicates the component is in a termination phase. If the resource doesn't reinitialize autonomously, operationalState is disabled; otherwise it is enabled or disabled. Description of bits: initializationRequired(0) notInitialized(1) initializing(2) reporting(3) terminating(4)

If supported by the component, this attribute indicates the OSI Control status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value subjectToTest indicates the resource is available but tests may be conducted simultaneously at unpredictable times, which may cause it to exhibit unusual characteristics. The value partOfServicesLocked indicates that part of the service is restricted from users of a resource. The adminState is unlocked. The value reservedForTest indicates that the component is administratively unavailable because it is undergoing a test procedure. The adminState is locked. The value suspended indicates that the service has been administratively suspended. Description of bits: subjectToTest(0) partOfServicesLocked(1) reservedForTest(2) suspended(3)

If supported by the component, this attribute indicates the OSI Alarm status of the component. Note that, even though it is defined as a multi-valued set, at most one value is shown to the user. When no values are in the set, this indicates that either the attribute is not supported or that none of the status conditions described below are present. The value underRepair indicates the component is currently being repaired. The operationalState is enabled or disabled. The value critical indicates one or more critical alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value major indicates one or more major alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value minor indicates one or more minor alarms are outstanding against the component. Other, less severe, alarms may also be outstanding. The operationalState is enabled or disabled. The value alarmOutstanding generically indicates that an alarm of some severity is outstanding against the component. Description of bits: underRepair(0) critical(1) major(2) minor(3) alarmOutstanding(4)

If supported by the component, this attribute indicates the OSI Standby status of the component. The value notSet indicates that either the attribute is not supported or that none of the status conditions described below are present. Note that this is a non-standard value, used because the original specification indicated this attribute was set-valued and thus, did not provide a value to indicate that none of the other three are applicable. The value hotStandby indicates that the resource is not providing service but will be immediately able to take over the role of the resource to be backed up, without initialization activity, and containing the same information as the resource to be backed up. The value coldStandby indicates the resource is a backup for another resource but will not be immediately able to take over the role of the backed up resource and will require some initialization activity. The value providingService indicates that this component, as a backup resource, is currently backing up another resource. Enumeration: 'notSet': 15, 'coldStandby': 1, 'hotStandby': 0, 'providingService': 2.

This attribute indicates the OSI Unknown status of the component. The value false indicates that all of the other OSI State and Status attribute values can be considered accurate. The value true indicates that the actual state of the component is not known for sure. Enumeration: 'true': 1, 'false': 0.

This group contains the common operational data for a component in a digital hierarchy interface.

An entry in the mscLpDS1OperTable.

This attribute displays whether a LOS (Loss of Signal) alarm state has been entered. A LOS alarm is declared after LOS defects have been observed and accumulated for a period of 2 seconds +/- 0.5 seconds (for 3pDS1Atm, 3pE1Atm, 8pDS1Atm, and 8pE1Atm cards: 2.5 seconds +/- 0.5 seconds). A LOS defect is detected upon observing all zeros for 150 ms (for 3pDS1Atm, 3pE1Atm, 8pDS1Atm, and 8pE1Atm cards: upon observing 175 +/- 75 pulse positions with no pulses of either positive or negative polarity). If the LOS defects are intermittently occurring, the LOS defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The port goes into an operational state of disabled until the LOS alarm state is cleared. Also, an RAI alarm is transmitted to the far end for the duration of the LOS alarm state. The LOS alarm state is cleared when LOS defects are absent for 10 seconds +/- 0.5 seconds. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an AIS (Alarm Indication Signal) alarm state has been entered. The AIS Alarm state is entered when AIS defects have been observed and accumulated for 2.5 seconds +/ - 0.5 seconds. An AIS defect is detected after having received less than 3 zeros in a 2048 bit period (for 8pDS1Atm cards: when both an Out Of Frame condition exists and a 1's density of at least 99.9% is present for a time T, where 3 ms T 75 ms; for 8pE1Atm cards: when both an Out Of Frame condition exists and fewer than three 0's have been received in 512 bit periods). If the AIS defects are intermittently occurring, the AIS defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The port goes into an operational state of disabled for the duration of an AIS alarm state. The AIS alarm state is cleared when AIS defects are absent for 10 seconds +/- 0.5 seconds. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a LOF (Loss of Frame) alarm state has been entered. The LOF alarm state is entered when LOF defects (for DS1: 2 out of 5 framing bits in error; for E1: 3 consecutive frame alignment patterns in error) have been detected for 3 seconds +/- 0.5 seconds (for 3pDS1Atm, 3pE1Atm, 8pDS1Atm, and 8pE1Atm cards: 2.5 seconds +/- 0.5 seconds). If the LOF defects are intermittently occurring, the LOF defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The port goes into an operational state of disabled until the LOF alarm state is cleared. Also, an RAI alarm is transmitted to the far end for the duration of the LOF alarm state The condition is cleared when framing has been achieved for 10 seconds +/- 0.5 seconds. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an RAI (Remote Alarm Indication) alarm state has been entered. An RAI alarm state is entered when the RAI defect indicator has been observed and accumulated for 3.5 seconds +/- 0.5 seconds. For 3pDS1Atm, and 8pDS1Atm cards: alarm is declared immediately upon observing the defect is present, with no integration time. For 3pE1Atm, and 8pE1Atm cards: alarm state is entered when the RAI defect indicator has been observed and accumulated for 2.5 seconds +/- 0.5 seconds. If the RAI defects are intermittently occurring, the RAI defect accumulator is decremented at a rate of 1/10 of the incrementing rate (alarm integration ratio of 1/10), with all measurements based on a 200 ms polling cycle. The RAI alarm state is cleared when the RAI defect indicator has been absent for 10 seconds +/- 0.5 seconds (for 3pDS1Atm, and 8pDS1Atm cards: alarm is cleared immediately upon observing the defect is absent, with no integration time). The RAI alarm is usually an indication that the far end facility is unable to gain synchronization. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether an AIS (Alarm Indication Signal) alarm is being transmitted on the line. An AIS alarm is transmitted when the port is in a locked state. Enumeration: 'on': 0, 'off': 1.

This attribute displays whether a RAI signal is being sent on the outgoing line. The RAI signal is transmitted when the port detects a LOF alarm condition (for 3pDS1Atm, 3pE1Atm, 8pDS1Atm, and 8pE1Atm cards: RAI is transmitted when the port detects a LOS, LOF, or AIS condition). Enumeration: 'on': 0, 'off': 1.

This group contains the common statistical data for a component in a digital hierarchy interface.

An entry in the mscLpDS1StatsTable.

The number of seconds since the port component was activated.

The number of seconds that the port has been in an error free state.

An errored second is declared when a second with one or more Code Violation Error events, or one or more Out Of Frame events occurs. A code violation error may be a CRC error or a BPV error. An Out Of Frame event occurs when 2 out of 5 framing bits are in error.

A severely errored second occurs when a second with 320 or more Code Violation Error events or one or more Out Of Frame events occurs.

A severely errored framing second occurs when a second with one or more Out Of Frame events occurs.

The total number of seconds that the interface is in an unavailable signal state. An unavailable signal state occurs at the onset of 10 consecutive Severely Errored Seconds. The state is cleared at the onset of 10 seconds with no Severely Errored Seconds.

The current count of Bipolar Violations. A bipolar violation is an error in the alternate mark inversion pattern (AMI) on the line.

If the interface is a DS1 line, it is the current count of CRC-6 errors. These will only be counted when the lineType is ESF. If the interface is an E1 line, it is the total number of CRC-4 errors. These will only be counted when crc4Mode is on.

The current count of frame errors. A frame error is an error in the framing bits

The total number of times that the line lost signal.

The total number of times that the line experienced a controlled frame slip. This attribute is incremented for ports on the voice cards (for example the 1pDS1V and the 1pE1V function processors) only.

This entry controls the addition and deletion of mscLpE1 components.

A single entry in the table represents a single mscLpE1 component.

This variable is used as the basis for SNMP naming of mscLpE1 components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpE1 tables.

This variable represents the index for the mscLpE1 tables.

This entry controls the addition and deletion of mscLpE1Chan components.

A single entry in the table represents a single mscLpE1Chan component.

This variable is used as the basis for SNMP naming of mscLpE1Chan components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscLpE1Chan tables.