CISCO-ICSUDSU-MIB

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

The CSU/DSU Static Configuration Table. Contains items that are statically configured and can not be changed by end user without physically changing the CSU/DSU.

OBJECT-TYPE

An entry in the static configuration table for each integrated CSU/DSU.

OBJECT-TYPE

Specifies the type of line interface or CSU/DSU.

OBJECT-TYPE

The CSU/DSU hardware revision.

OBJECT-TYPE

The CSU/DSU software revision.

OBJECT-TYPE

The Protocol Revision of the CSU/DSU.

OBJECT-TYPE

The CSU/DSU test report Table. Contains the results of user initiated tests, including selftest, reset, and loopback.

OBJECT-TYPE

An entry in the test report table for each integrated CSU/DSU.

OBJECT-TYPE

The result of the last self test. Represented as a sum of a bit map. The variable bit positions are: 1 - Flash Checksum bad. Catastrophic error. 2 - EPROM Checksum bad. Catastrophic error. 4 - RAM Tests failed. Catastrophic error. 8 - ROM Checksum bad. Catastrophic error. 16 - DteLoss. Could not put DTE into loopback. NonCatastrophic error. 32 - patternLossDuringTest. Put DTE into loopback but found BERT errors. NonCatastrophic error.

OBJECT-TYPE

SysUpTime of LastSelfTest execution.

OBJECT-TYPE

Number of times CSU/DSU has been reset.

OBJECT-TYPE

SysUpTime of last CSU/DSU reset.

OBJECT-TYPE

Current Status of Loopback. Remaining Loopback results are valid only if status is 'completed' or 'failed' or 'noSyncWithTestPattern'.

OBJECT-TYPE

Number of Bit errors that occurred in last successful loopback test. Valid only if remote loopback with pattern was performed and a sync was achieved on the test pattern.

OBJECT-TYPE

Duration of last successful loopback test in hundredths of seconds. Note that it is possible for the CSU/DSU to lose framing during the test. If so, the duration represents the time between reframing and end of test. This simply means that the start time of last loopback cannot be calculated by subtracting this duration from the end time of last loopback.

OBJECT-TYPE

Point in network where last loopback was performed. Meaning for t1 CSU/DSU: dtePayload - local DSU loopback. The configured 'fractions' of the DS1 signal is looped back as the receive signal. Used to verify operation of DSU portion of local CSU/DSU. dteFull - local CSU loopback. DS1 transmit signal is looped back as the receive signal. Runs at full bandwidth irrespective of fractions configured. Used to verify operation of local CSU/DSU. lineFull - DS1 signal received from the network is transmitted back to the network. Signal is regenerated but not reframed. Loopback performed at the CSU. Used to verify operation of T1 network. linePayload - DS1 signal received from the network is transmitted back to the network. Data is regenerated and reframed with any LCV or CRC errors corrected. Loopback performed at the DSU. Used to verify operation of local CSU/DSU and T1 network. remoteSmartJack - the remote smart jack (telco installed wall socket device used to delineate network between CPE and telco equipment) is used to loopback the DS1 signal. Similar to remoteFull loopback except that the signal is looped at the smart jack before reaching remote CSU/DSU. Used to verify operation of local CSU/DSU and T1 network. remoteFull - remote unit placed in lineFull loopback. Used to verify operation of local CSU/DSU and T1 network. remotePayload - remote unit placed in linePayload loopback Used to verify operation of local CSU/DSU, T1 network, and remote CSU/DSU. Meaning for switched 56k CSU/DSU: dteFull - local CSU loopback. Transmit signal is looped back as the receive signal at a point close to the physical network interface. Used to verify operation of local CSU/DSU. lineFull - CSU/DSU is split into separate DTE and loop interface sections. Signal received from the network is transmitted back to the network. Data received from DTE is transmitted back to DTE. Used to verify operation of local CSU/DSU and network from remote site. linePayload - Signal received from the network is looped back at the DTE interface and transmitted back to the network. Data received from DTE is ignored. Used to verify operation of local CSU/DSU and network from remote site. remotePayload - Similar to linePayload except that the remote unit is placed into loopback. Used to verify operation of local CSU/DSU, T1 network, and remote CSU/DSU.

OBJECT-TYPE

Test pattern used for locally initiated remote loopback. Valid only if a remote loopback was last performed. Following patterns valid for T1 or Switched 56k CSU/DSU: noPattern - no specific pattern is used, data provided by the DTE. Used to loopback transmit data. Following patterns only valid for T1 CSU/DSU: patternQRW - Quasi-Random Word pattern. Specifically used to measure Bit Error Rates. pattern0In1 - repeated binary pattern of '0' or all zeros. Typically used for verification of B8ZS optioning of the T1 facility. pattern1In1 - repeated binary pattern of '1' or all ones. Typically used for signal power measurements. pattern1In2 - repeated binary pattern of '01'. Typically used in testing for bridge taps. pattern1In3 - repeated binary pattern of '001'. Typically used to terminate a remote loopback. pattern1In5 - repeated binary pattern of '00001'. Typically used to put the remote unit in loopback. pattern1In8 - repeated binary pattern of '00000001'. Typically used to stress the timing recovery circuits of repeaters and other intermediate equipment. pattern3In24 - repeated binary pattern of '000000000000000000000111' or hex '000007'. Typically used to test for one's density (consecutive zeros) tolerance on AMI lines. patternUser - user defined pattern. Following patterns only valid for Switched 56k CSU/DSU: pattern2047 - 2047 bit long pseudorandom pattern containing a maximum of 10 sequential zeros and 11 sequential ones. pattern511 - 511 bit long pseudorandom pattern containing a maximum of 8 sequential zeros and 9 sequential ones. patternStressDDS1 - DDS Stress test pattern #1. patternStressDDS2 - DDS Stress test pattern #2. patternStressDDS3 - DDS Stress test pattern #3. patternStressDDS4 - DDS Stress test pattern #4.

OBJECT-TYPE

User Defined Loopback Pattern. Valid only if ciscoICsuDsuLoopbackPattern is patternUser.

OBJECT-TYPE

LoopCode used to initiate last remote loopback. Valid only if a only if a remote loopback was last performed. standard - standard loopback code. Usually consists of the repeated binary pattern of '00001' alternate - alternate loopback code. Usually the inverse of the standard pattern or '11110'. v54 - V.54 pattern. Used for fractional loopback.

OBJECT-TYPE

SysUpTime of completion of last loopback test execution.

OBJECT-IDENTITY

OBJECT-TYPE

The T1 CSU/DSU Unit Configuration Table. Contains current T1 CSU/DSU configuration parameters not covered by RFC1406.

OBJECT-TYPE

An entry in the configuration table for each integrated T1 CSU/DSU.

OBJECT-TYPE

Line build out (LBO) is loss inserted by the CSU in order to meet the 15 to 22.5 dB loss requirement of the premises remote-end section. Selected so that (phone company loss) + (cable length loss) + (line build out) is greater that 15dB but less than 22.5 dB. buildOut0 means insert 0 dB. buildOut7p5 means insert 7.5 dB. buildOut15 means insert 15 dB.

OBJECT-TYPE

Indicates whether the DTE line code is inverted or not. When fractional timeslots are configured for 64kps and AMI linecode, a combination of inverting the DTE line code along with the proper line protocol (i.e. HDLC/SDLC) may be necessary to meet the ones density constraint.

OBJECT-TYPE

Determines if unit will generate or detect a remote alarm indication (RAI) signal which is also known as a yellow alarm. In D4 framing format, DTE equipment (including Frame Relay equipment) that is using the HDLC or SDLC protocol may generate patterns as part of its normal traffic. These patterns may be interpreted as yellow alarms and disrupt data traffic.

OBJECT-TYPE

LoopCode to be accepted from remote end to place unit in and out of full bandwidth loopback. standard - standard loopback code. Usually consists of the repeated binary pattern of '00001' alternate - alternate loopback code. Usually the inverse of the standard pattern or '11110'. disabled - No code is accepted, disabling an request for remote loopback.

OBJECT-TYPE

LoopCode to be accepted from remote end to place unit in and out of payload or fractional loopback. standard - standard loopback code. Usually consists of the repeated binary pattern of '00001' alternate - alternate loopback code. Usually the inverse of the standard pattern or '11110'. disabled - No code is accepted, disabling an request for remote loopback. v54 - V.54 pattern. Used for fractional loopback.

OBJECT-TYPE

The T1 CSU/DSU Unit Status Table. Contains information about the status of the CSU/DSU, including externally generated alarm conditions.

OBJECT-TYPE

An entry in the status table for each integrated T1 CSU/DSU.

OBJECT-TYPE

Current Loop status of T1 CSU/DSU. Represented as a sum of a bit map. The variable bit positions are: 1 - lossofSignal (LOS); unable to detect the DS1 signal. 2 - lossofFrame (LOF); unable to synchronize on the DS1 signal. 4 - detectedRemoteAlarmIndication (RAI); indicates that the transmitting equipment has lost its incoming signal. RAI is commonly called yellow alarm. 8 - detectedAlarmIndicationSignal (AIS); indicates that there is a transmission interruption located either at the equipment originating the AIS signal or upstream of that equipment. Indicated by an unframed, all-'ones' signal. Also known as blue alarm. 16 - placedInLoopback; Line placed in loopback from remote.

OBJECT-TYPE

Number of times lossofSignal event detected.

OBJECT-TYPE

Number of times lossofFrame event detected.

OBJECT-TYPE

Number of times RemoteAlarmIndication signal or yellow alarm received.

OBJECT-TYPE

Number of times Alarm Indication Signal or blue alarm received.

OBJECT-IDENTITY

OBJECT-TYPE

The Switched 56k CSU/DSU Configuration Table. Contains current Sw56k CSU/DSU configuration parameters.

OBJECT-TYPE

An entry in the sw56k configuration table for each integrated switched 56 kbps CSU/DSU.

OBJECT-TYPE

Configures the DSU Module for the specific type of network being used. dds - AT&T's Dataphone Digital Service, generically known as Digital Data System. Requires 4-Wire interface. att - AT&T's Switched 56 Network. Operates over 2-Wire or or 4-Wire interface. sprint - Sprint Switched 56 Network. Operates over 2-Wire or 4-Wire interface. otherCarrier - Other carrier being used.

OBJECT-TYPE

Specifies the timing source for the DSU. 'internal' indicates timing provided by DSU. 'line' indicates timing provided by network receive signal.

OBJECT-TYPE

The Loop Rate option selects the network loop operating speed. Only 'ciscoICsuDsuSw56kNetworkType' of 'dds' supports all listed loop rates. 'att' and 'sprint' network types only support 'bps56k' or 56 kilobits per second.

OBJECT-TYPE

Indicates if line code scrambling is enabled. Scrambling is used to prevent DTE data sequences that minic network loop maintenance functions from activating loopback. Only supported when operating in DDS mode at 64kbps (also known as clear channel mode).

OBJECT-TYPE

Indicates if a request for Remote Digital Loopback is will be accepted.

OBJECT-TYPE

The Sw56k CSU/DSU Status Table. Contains information about the status of the CSU/DSU, including externally generated alarm conditions.

OBJECT-TYPE

An entry in the sw56k status table for each integrated switched 56 kbps CSU/DSU.

OBJECT-TYPE

This variable indicates the dialing status of units using switched connections. idle - on-hook and no call in progress. dialing - dialing a number. onLine - Online passing data. noWinkFromSwitch - No wink from switch (cleared after 5 seconds). Wink is a DC signalling method in which the polarity of the line is temporarily reversed and then returned to its original polarity as an acknowledgement. numberBusy - Number is busy (cleared after 5 seconds). noAnswer - No answer. (cleared after 5 seconds).

OBJECT-TYPE

Current loop status or alarm condition. Represented as a sum of a bit map. The variable bit positions are: 1 oosOofFromNetwork - The DSU is receiving Out of Service/ Out of Frame code from network indicating network trouble. This can be a problem with a device at the remote DSU. The most common cause of the this error is either the remote DSU is powered off or the remote telco connection is open. 2 noReceiveSignal - The DSU has detected sealing current from the central office but the receive level is below -45db. 4 noSealingCurrent - the DSU does not detect sealing current on the loop interface. This is normal for a private network. 8 noFrameSync - At 64k data rate the local loop operates at 72k with a framing pattern added to maintain byte alignment with the network. This condition is reported if the DSU cannot find the framing pattern. 16 attemptingToRateAdap - Set in 'autorate' mode when the DSU is searching for the loop rate. 32 rtTestFromTelco - Set when the DSU in telco initiated RT test. 64 llTestFromTelco - Set when the DSU in telco initiated LL test or when the transmit and receive pairs are reversed. 128 rdlFromRemoteDSU - Set when remote digital loopback initiated from remote DSU.

OBJECT-TYPE

Number of times OOS/OOF (Out Of Sync / Out Of Frame) code received.

OBJECT-TYPE

Number of times Lost Sealing Current.

OBJECT-TYPE

Number of times lost receive signal.

OBJECT-TYPE

Number of times lost frame synchronization.

OBJECT-TYPE

Number of times attempted Loop Rate Search.

OBJECT-IDENTITY

OBJECT-TYPE

Indicates whether or not a T1 Alarm Notification will be generated by this system.

OBJECT-TYPE

Indicates whether or not a Sw56k Alarm Notification will be generated by this system.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY