Fore-E1-MIB: View SNMP OID List / Download MIB

This mib implements management tables for the E1 port module.

A table of E1 switch port configuration information.

A table entry containing E1 configuration information for each port. Not all RFC1406 configuration table variables are included, and some are modified.

The index of this port's switch board.

The network module of this port.

The number of this port.

This variable indicates the variety of E1 Line implementing this circuit. The type of circuit affects the number of bits per second that the circuit can reasonably carry, as well as the interpretation of the usage and error statistics. This variable is defined in the rfc1406 configuration table as dsx1LineType. According to rfc1406, the different values are: e1NoCRC CCITT recommendation G.704 (table a) e1CRC CCITT recommendation G.704 (table b) e1MF G.704(table a) with TS16 multifatming enabled e1MFCRC G.704(table b) with TS16 multifatming enabled. Enumeration: 'e1NoCRC': 2, 'e1MF': 4, 'e1CRC': 3, 'e1CRCMF': 5, 'e1Other': 1.

This variable describes the variety of Zero Code suppression used on this link, which in turn affects a number of its characteristics. e1AMI(3) refers to a mode wherein no zero code suppression is present and the line encoding does not solve the problem directly. In this application, the higher layer must provide data which meets or exceeds the pulse density re-quirements, such as inverting HDLC data. This variable is defined in the rfc1406 configuration table as dsx1LineCoding. Enumeration: 'e1AMI': 3, 'e1HDB3': 2, 'e1Other': 1.

This variable indicates what type of code is being sent across the E1 interface by the device. The values mean: e1SendNoCode sending looped or normal data e1SendLineCode sending request for a line loopback e1SendPayloadCode sending a request for a payload loopback e1SendResetCode sending a loopback termination request e1SendQRS sending a Quasi-Random Signal (QRS) test pattern e1Send511Pattern sending a 511 bit fixed test pattern e1Send3in24Pattern sending a fixed test pattern of 3 bits set in 24 e1SendOtherTestPattern sending a test pattern other than the above. Enumeration: 'e1SendPayloadCode': 3, 'e1SendResetCode': 4, 'e1SendQRS': 5, 'e1SendOtherTestPattern': 8, 'e1Send511Pattern': 6, 'e1Send3in24Pattern': 7, 'e1SendLineCode': 2, 'e1SendNoCode': 1.

This variable indicates the type of code that was received across the E1 interface. The values mean: e1ReceiveNoCode receiving looped or normal data e1ReceiveLineCode receiving request for a line loopback e1ReceivePayloadCode receiving a request for a payload loopback e1ReceiveResetCode receiving a loopback deactivation request e1ReceiveQRS receiving a Quasi-Random Signal (QRS) test pattern e1Receive511Pattern receiving a 511 bit fixed test pattern e1Receive3in24Pattern receiving a fixed test pattern of 3 bits set in 24 e1ReceiveOtherTestPattern receiving a test pattern other than the above. Enumeration: 'e1ReceiveResetCode': 4, 'e1ReceiveNoCode': 1, 'e1ReceiveLineCode': 2, 'e1ReceivePayloadCode': 3, 'e1SendQRS': 5, 'e1SendOtherTestPattern': 8, 'e1Send511Pattern': 6, 'e1Send3in24Pattern': 7.

This variable represents the loopback configuration of the E1 interface. This variable is defined in the rfc1406 configuration table as dsx1LoopbackConfig, with slightly different values. e1NoLoop (1) means that the interface is not in a loopback state. e1LineLoop (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. e1PayloadLoop (3) means that the receive signal is looped back for retransmission after it has passed through the port's reframing function. e1DiagLoop (4) means that the transmit data stream is looped back to the receiver. e1OtherLoop (5) means that the interface is in a loopback that is not defined here. Enumeration: 'e1LineLoop': 2, 'e1OtherLoop': 5, 'e1DiagLoop': 4, 'e1NoLoop': 1, 'e1PayloadLoop': 3.

The source of the transmit clock. rxTiming(1) indicated that the recovered receive clock is used as the transmit clock. localTiming(2) indicates that a local source clock is used as the transmit clock. To determine which local source clock is used advise the ntGlobalClock in the netmodTimingTable for this netmod (refer to the Fore-Switch-MIB for more information). Enumeration: 'localTiming': 2, 'rxTiming': 1.

This variable indicates the Line Status of the interface. A similar object is defined in the rfc1406 configuration table as dsx1LineStatus. The variable contains loopback state information and failure state information. It is a bit map represented as a sum. The e1NoAlarm should be set if and only if no other flag is set. The various bit positions are: 1 e1NoAlarm 2 e1RxFarEndLOF Far end LOF (Receiving Yellow Alarm Indication) 4 e1TxFarEndLOF Near end sending LOF Indication (Yellow Alarm) 8 e1RxAIS Far end sending AIS 16 e1TxAIS Near end sending AIS (Not used) 32 e1LOF Near end Loss Of Frame (Red Alarm) 64 e1LOS Near end Loss Of Signal 128 e1LoopbackState Near end is in loopback mode 256 e1RxPLCPYel Receving PLCP Yellow 512 e1TxPLCPYel Transmitting PLCP Yellow 1024 e1RxPLCPLOF Receiving PLCP LOF 2048 e1RcvTestCode Receiving a test pattern 4096 e1OtherFailure any line status not defined here 32768 e1RxLCD Receiving LCD failure indication.

This 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. Enumeration: 'idle': 2, 'unassigned': 1.

This variable represents the length of the physical cable connected to the e1 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: e1LineLt110 (1) means the line is shorter than 110 ft, e1Line110-220 (2) means the line is between 110 and 220 ft, e1Line220-330 (3) means the line is between 220 and 330 ft, e1Line330-440 (4) means the line is between 330 and 440 ft, e1Line440-550 (5) means the line is between 440 and 550 ft, e1Line550-660 (6) means the line is between 550 and 660 ft, e1LineG703-75 (7) G703 standard (75 ohm coaxial line), e1LineG703-120 (8) G703 standard (120 ohm symmetrical line). Enumeration: 'e1Line220-330Alt': 11, 'e1Line220-330': 3, 'e1LineLt110': 1, 'e1Line550-660Alt': 14, 'e1LineG703-75Alt': 15, 'e1Line110-220': 2, 'e1Line330-440Alt': 12, 'e1LineG703-120': 8, 'e1Line330-440': 4, 'e1Line440-550Alt': 13, 'e1Line440-550': 5, 'e1Line110-220Alt': 10, 'e1LineG703-75': 7, 'e1Line550-660': 6, 'e1LineG703-120Alt': 16, 'e1LineLt110Alt': 9.

This variable indicates the way ATM cells are constructed from the E1 stream. e1Hcs(2) indicates that the ATM cells are constructed upon the Header Check Sequence (HCS) inside the ATM cell header. e1Plcp(3) indicates that the ATM cells are constructed from the E1 PLCP (Physical Layer Convergence Protocol) bits. Enumeration: 'e1Hcs': 2, 'other': 1, 'e1Plcp': 3.

This variable indicates whether the information is being descrambled on receiving. It should be set the same as the transmitting side. Enumeration: 'descrambling': 1, 'noDescrambling': 2.

This variable indicates whether the information (48 octet payload) is being scrambled before transmitting. It should be set the same as the receiving side. Enumeration: 'scrambling': 1, 'noScrambling': 2.

A table of E1 framing statistics information.

A table entry containing E1 framing statistics information.

The index of this port's switch board.

The network module of this port.

The number of this port.

The number of Line Code Violations (LCV) that were detected by the E1 Receive Framer block.

Number of E1 framing error (FERR) events.

Number of E1 far end block errors.

The number cyclic redundancy errors.

Number of seconds when OOF (loss of basic frame alignment) errors were detected.

Number of seconds when LOS (loss of signal) error events were experienced.

Number of seconds when AIS (alarm indication signal) error events were experienced.

Number of seconds when AISD (unframed pattern of all ones) error events were experienced.

Number of seconds when Red Alarm events were experienced.

Number of seconds when Yellow Alarm events were experienced.

A table of E1 Physical Layer Convergence Protocol (Procedure) statistics information.

A table entry containing E1 PLCP statistics information.

The index of this port's switch board.

The network module of this port.

The number of this port.

Number 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.

Number of Physical Layer Convergence Protocol (PLCP) octet error events.

Number of ATM Far End Block Error (FEBE) events.

The 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.

The 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.

A table of E1 ATM statistics information.

A table entry containing E1 ATM statistics information.

The index of this port's switch board.

The network module of this port.

The number of this port.

Number of header check sequence (HCS) error events. The HCS is a CRC-8 calculation over the first 4 octets of the ATM cell header.

Number of ATM cells that were received.

Number of non-null ATM cells that were transmitted.

Number of uncorrectable header check sequence (HCS) error events. The HCS is a CRC-8 calculation over the first 4 octets of the ATM cell header.

Number of correctable header check sequence (HCS) error events. The HCS is a CRC-8 calculation over the first 4 octets of the ATM cell header.

The 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.