Fore-DS3-MIB
This MIB module supports the FORE DS3 port module.
Main OID:
foreDs3.1.3.6.1.4.1.326.2.2.1.1.3
62
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
62 total| Object Name |
|---|
foreDs3This MIB module supports the FORE DS3 port module. MODULE-IDENTITY .1.3.6.1.4.1.326.2.2.1.1.3 |
ds3ConfGroup OBJECT IDENTIFIER .1.3.6.1.4.1.326.2.2.1.1.3.1 |
ds3ConfTableA table of DS3 switch port configuration information. SEQUENCE OF Ds3ConfEntry .1.3.6.1.4.1.326.2.2.1.1.3.1.1 |
ds3ConfEntryA table entry containing DS3 configuration information for each port. Not all RFC1407 configuration table variables are included, and some are modified. Ds3ConfEntry .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1 |
ds3ConfBoardThe index of this port's switch board.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.1 |
ds3ConfModuleThe network module of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.2 |
ds3ConfPortThe number of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.3 |
ds3LineTypeThis variable indicates the variety of DS3 C-bit application implementing this interface. The type of interface affects the interpretation of the usage and error statistics. This variable is defined in the rfc1407 configuration table as dsx3LineType. According to rfc1407, the different values are: ds3M23 specification: ANSI T1.107-1988 ds3SYNTRAN specification: ANSI T1.107-1988 ds3CbitParity specification: ANSI T1.107a-1989 ds3CleatChannel specification: ANSI T1.102-1987.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.4 |
ds3LineCodingThis variable describes the variety of Zero Code suppression used on this interface, which in turn affects a number of its characteristics. ds3B3ZS (2) refers to the use of specified pattern of normal bits and bipolar violations which are used to replaced sequences of zero bits of specified length. This variable is defined in the rfc1407 configuration table as dsx3LineCoding.ro Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.5 |
ds3SendCodeThis variable indicates what type of code is being sent across the DS3/E3 interface by the device. The values mean: ds3SendNoCode sending looped or normal data ds3SendLineCode sending request for a line loopback ds3SendPayloadCode sending a request for a payload loopback (i.e. all DS1/E1 in a DS3/E3 frame) ds3SendResetCode sending a loopback deactivation request ds3SendDS1LoopCode requesting to loopback a particular DS1/E1 within a DS3/E3 frame ds3SendTestPattern sending a test pattern.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.6 |
ds3ReceiveCodeThis variable indicates the type of code that was received across the DS3/E3 interface. The values mean: ds3ReceiveNoCode receiving looped or normal data ds3ReceiveLineCode receiving request for a line loopback ds3ReceivePayloadCode receiving a request for a payload loopback (i.e. all DS1/E1 in a DS3/E3 frame) ds3ReceiveResetCode receiving a loopback deactivation request ds3ReceiveDS1LoopCode receiving a request to loopback a particular DS1/E1 within a DS3/E3 frame ds3ReceiveTestPattern receiving a test pattern.ro Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.7 |
ds3LoopbackConfigThis variable represents the loopback configuration of the DS3 interface. This variable is defined in the rfc1407 configuration table as dsx3LoopbackConfig, with slightly different values. ds3NoLoop (1) means that the interface is not in a loopback state. ds3CellLoop (2) means that cells that are processed by the receiving component are not written into the receive FIFO, but into the transmit FIFO for retransmission. ds3PayloadLoop (3) means that the receive signal is looped back for retransmission after it has passed through the port's reframing function. ds3DiagLoop (4) means that the transmit data stream is looped back to the receiver. ds3LineLoop (5) is only supported on series B and later netmods. ds3OtherLoop (6) means that the interface is in a loopback that is not defined here.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.8 |
ds3TxClockSourceThe source of the transmit clock.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.9 |
ds3RxScramblingThis variable indicates whether the information is being descrambled on receiving. It should be set the same as the transmitting side.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.10 |
ds3TxScramblingThis variable indicates whether the information (48 octet payload) is being scrambled before transmitting. It should be set the same as the receiving side.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.11 |
ds3LineStatusThis variable indicates the Line Status of the interface. A similar object is defined in the rfc1407 configuration table as dsx3LineStatus (the ds3RxFERF bit is not defined in rfc1407) . The variable contains loopback state information and failure state information. It is a bit map represented as a sum. The ds3NoAlarm should be set if and only if no other flag is set. The various bit positions are: 1 No Alarm. 2 Receiving PLCP Yellow Alarm Indication. 4 Transmitting PLCP Yellow alarm indication. 8 Receiving PLCP LOF. 16 Receiving FERF. 32 Transmiting FERF. 64 Receiving AIS failure indication. 128 Receiving LOF failure indication. 256 Receiving LOS failure indication. 512 Loopback State. 1024 Receiving a test pattern. 2048 Other failures. 16384 Receiving IDLE failure indication. 32768 Receiving LCD failure indication.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.12 |
ds3IdleUnassignedCellsThis variable indicates the types of cells that should be sent in case there is no real data to send. According to the ATM Forum, Unassigned cells should be sent (octet 1-3 are 0's, octet 4 is 0000xxx0, where x is 'don't care'). According to the CCITT specifications, Idle cells should be sent (everything is '0' except for the CLP bit which is '1'). By default, unassigned cells are transmitted is case there is no data to send.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.13 |
ds3LineTypeFramingThis variable indicates the way ATM cells are constructed from the DS3 stream. ds3Hcs(1) indicates that the ATM cells are constructed upon the Header Check Sequence (HCS) inside the ATM cell header. ds3Plcp(2) indicates that the ATM cells are constructed from the DS3 PLCP (Physical Layer Convergence Protocol) bits.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.14 |
ds3LineLengthThis variable represents the length of the physical cable connected to the ds3 port. The user has to set this object to match the physical cable in order to get the netmod to receive the signal on the cable. The different values are: ds3LineLt225 (1) means the line is shorter than 225 ft, ds1LineGt225 (2) means the line length is greater than 220 ft. This value is not settable for Series A netmods and the value for these netmods is Gt225rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.15 |
ds3PbitPErrThrSecondsThis variable represents the consecutive number of BAD/GOOD seconds to detect/clear an Excessive P-bit Parity Error Defect. The range of values it can take is between 2 and 10 inclusive.rw Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.16 |
ds3PbitPErrThrErrorsThis variable is a threshold for the number of P-bit Parity Errors per second and is used as a parameter to the Excessive P-bit Parity Error Defect. If the number of errors exceeds the threshold, the particular second is declared BAD, otherwise it is declared GOOD.rw Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.17 |
ds3PbitPErrFailEnableThis variable controls whether declaration of an Excessive P-bit Parity Error Defect forces the port's operState to Down.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.18 |
ds3SigFailBerThis is the exponent of 10 for the current signal fail bit error rate (BER) threshold for this port. The value -4, for example, represents a BER of 1E-4. This variable is only applicable when ds3BerErrorModel is set to errorModelRandom.rw Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.19 |
ds3SigDegradeBerThis is the exponent of 10 for the current signal degrade bit error rate (BER) threshold for this port. The value -8, for example, represents a BER of 1E-8. This variable is only applicable when ds3BerErrorModel is set to errorModelRandom.rw Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.20 |
ds3BerErrorModelThis is the error distribution model to be used to identify signal degrade and signal fail conditions. errorModelRandom selects a random error distribution and declares signal conditions based on the thresholds set in ds3SigDegradeBer and ds3SigFailBer. errorModelBurst selects a burst error model and declares signal degrade conditions based on the thresholds set in ds3PErrThrSeconds and ds1PErrThrErrors. errorModelNone disables detection of signal conditions.rw Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.21 |
ds3BerStateThis value describes the current state of the port as determined through bit error rate analysis.ro Enumeration .1.3.6.1.4.1.326.2.2.1.1.3.1.1.1.22 |
ds3StatsGroup OBJECT IDENTIFIER .1.3.6.1.4.1.326.2.2.1.1.3.2 |
ds3FramingTableA table of DS3 framing statistics information. SEQUENCE OF Ds3FramingEntry .1.3.6.1.4.1.326.2.2.1.1.3.2.1 |
ds3FramingEntryA table entry containing DS3 framing statistics information. Ds3FramingEntry .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1 |
ds3FramingBoardThe index of this port's switch board.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.1 |
ds3FramingModuleThe network module of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.2 |
ds3FramingPortThe number of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.3 |
ds3FramingLOSsThe number of seconds in which Loss Of Signal (LOS) errors were detected by the DS3 Receive Framer block.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.4 |
ds3FramingLCVsThe number of Line Code Violations (LCV) that were detected by the DS3 Receive Framer block.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.5 |
ds3FramingSumLCVsThe number of DS3 information blocks (85 bits) which contain one or more Line Code Violations (LCV).ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.6 |
ds3FramingFERRsNumber of DS3 framing error (FERR) events.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.7 |
ds3FramingOOFsNumber of seconds DS3 Out Of Frame (OOF) error events were experienced.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.8 |
ds3FramingFERFsThe number of seconds in which Far End Receive Failure (FERF) state has been detected by the DS3 Receive Framer block. FERF signal alerts the upstream terminal that a failure has been detected along the downstream line.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.9 |
ds3FramingAISsThe number of seconds in which Alarm Indication Signals (AIS) were detected by the DS3 Receive Framer block. AIS indicates that an upstream failure has been detected by the far end.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.10 |
ds3FramingPbitPERRsNumber of P-bit parity error (PERR) events.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.11 |
ds3FramingCbitPERRsNumber of C-bit parity error (PERR) events.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.12 |
ds3FramingFEBEsNumber of DS3 far end block error (FEBE) events.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.13 |
ds3FramingIDLEsThe number of seconds in which IDLE signal was detected by the DS3 Receive Framer block.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.1.1.14 |
ds3PlcpTableA table of DS3 Physical Layer Convergence Protocol (Procedure) statistics information. SEQUENCE OF Ds3PlcpEntry .1.3.6.1.4.1.326.2.2.1.1.3.2.2 |
ds3PlcpEntryA table entry containing DS3 PLCP statistics information. Ds3PlcpEntry .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1 |
ds3PlcpBoardThe index of this port's switch board.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.1 |
ds3PlcpModuleThe network module of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.2 |
ds3PlcpPortThe number of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.3 |
ds3PlcpFERRsNumber of Physical Layer Convergence Protocol (PLCP) octet error events.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.4 |
ds3PlcpLOFsThe number of seconds in which Loss Of Frame (LOF) errors were detected by the PLCP (Physical Layer Convergence Protocol) receiver. LOF is declared when an Out-Of-Frame state persists for more than 1ms. LOF is removed when in-frame state persists for more than 12ms.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.5 |
ds3PlcpBIP8sNumber of BIP-8 (Bit Interleaved Parity - 8) error events. The BIP-8 is calculated over the Path Overhead field and the associated ATM cell of the previous frame. A BIP-N is a method of error monitoring. An N bit code is generated by the transmitting equipment in such a manner that the first bit of the code provides even parity over the first bit of all N-bit sequences in the previous VT SPE, the second bit provides even parity over the second bits of all N-bit sequences within the specified portion, etc.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.6 |
ds3PlcpFEBEsNumber of ATM Far End Block Error (FEBE) events.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.7 |
ds3PlcpYellowsThe number of seconds in which Yellow alarm errors were detected by the PLCP (Physical Layer Convergence Protocol) receiver. Yellow alarm is asserted when 10 consecutive yellow signal bits are set to logical 1. Yellow signals are used to alert upstream terminals of a downstream failure in order to initiate trunk conditioning on the failure circuit.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.2.1.8 |
ds3AtmTableA table of DS3 ATM statistics information. SEQUENCE OF Ds3AtmEntry .1.3.6.1.4.1.326.2.2.1.1.3.2.3 |
ds3AtmEntryA table entry containing DS3 ATM statistics information. Ds3AtmEntry .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1 |
ds3AtmBoardThe index of this port's switch board.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1.1 |
ds3AtmModuleThe network module of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1.2 |
ds3AtmPortThe number of this port.ro Integer32 .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1.3 |
ds3AtmHCSsNumber of header check sequence (HCS) error events. The HCS is a CRC-8 calculation over the first 4 octets of the ATM cell header.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1.4 |
ds3AtmRxCellsNumber of ATM cells that were received.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1.5 |
ds3AtmTxCellsNumber of non-null ATM cells that were transmitted.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1.6 |
ds3AtmLCDsThe number of seconds in which Loss of Cell Delineation (LCD) has occurred. An LCD defect is detected when an out of cell delination state has persisted for 4ms. An LCD defect is cleared when the sync state has been maintained for 4ms.ro Counter32 .1.3.6.1.4.1.326.2.2.1.1.3.2.3.1.7 |