LX-10-MIB: View SNMP OID List / Download MIB

Name of the managed node.

Name of the organization that uses the managed node.

Phone number of the organization that uses the managed node.

Maintenance contact of the managed node.

Location of the managed node.

The time a TELNET or VT-100 terminal user can maintain a session with the managed node without any keyboard action. Unit: minute

Password required to access the managed node using VT-100 terminal or TELNET. A get request always returns a NULL string.

LX-10 unit identification number required to identify and set up the device's role (primary/secondary). This number should be unique among interconnected devices.

Time and date maintained in the managed node.

Table of available host IP interfaces.

Each entry contains the IP address and subnet mask of the specified interface and a flag which enables/disables the managed node to broadcast its (RIP) routing table through the interface.

Enumeration: 'ethernet': 1, 'nxt1': 3, 'slip': 2.

Host's IP address.

Host's IP subnet mask.

This object controls whether the managed node should broadcast its (RIP) routing table through the interface. Enumeration: 'disabled': 1, 'enabled': 2.

Default gateway's IP address.

Default gateway's IP subnet mask.

Trap client table has 4 entries

Each entry contains IP address and port number of an SNMP manager which receives traps from the managed node.

Trap client's IP address.

Trap client's IP subnet mask.

Trap client's port number.

Community name of the managed node. A get request for an instance of this object always returns a NULL string.

MAC-layer address of the management Ethernet port.

This table contains 2 rows. The first row shows the physical configuration of the port connected to a VT100 termianl. The second row is used to configure the port which supports SLIP. Access to the first row is read-only and access to the second row is read-write.

Each entry contains the attributes of a serial port.

The managed node has 2 serial ports: port 1 and port 2. Enumeration: 'port-1': 1, 'port-2': 2.

Baud rate. The instance of this object in port-1 is read-only. Enumeration: 'br-300': 1, 'br-2400': 3, 'br-19200': 6, 'br-4800': 4, 'br-1200': 2, 'br-38400': 7, 'br-9600': 5.

Parity. The instance of this object in port-1 is read-only. Enumeration: 'even': 2, 'none': 1, 'odd': 3.

Number of data bits. The instance of this object in port-1 is read-only. Enumeration: 'db-8': 2, 'db-7': 1.

Number of stop bits. The instance of this object in port-1 is read-only. Enumeration: 'sb-1': 1, 'sb-2': 2.

Firmware revision of the management CPU.

Firmware revision of the Ethernet (DATA) card.

DS1 configuration table.

Each entry contains the configuration attributes for a DS1 port.

DS1 port number.

DS1 administrative status. Enumeration: 'disabled': 1, 'enabled': 2.

DS1 operational status. Enumeration: 'down': 1, 'up': 2.

LBO. This object is not accessible if the managed node is the E1 version of LX10. Enumeration: 'dB-0': 1, 'dB-7-5': 2, 'dB-15': 3.

Encoding. This object is not accessible if the managed node is the E1 version of LX10. Enumeration: 'ami': 2, 'b8zs': 1.

Framing format. This object is not accessible if the managed node is the E1 version of LX10. Enumeration: 'esf': 1, 'd4': 2.

Enable/disable transmit AIS. Enumeration: 'disabled': 1, 'enabled': 2.

DS1 clock Source. Enumeration: 'looped': 1, 'internal': 2.

AFA activation rate is used by the managed node to decide when it will disable the operational status of a T1 interface if the interface's BER rate is above the selected activation rate for a period specified by configAfaActivationTime (see below). Enumeration: 'a-10-4': 1, 'a-10-5': 2, 'a-10-6': 3, 'a-10-7': 4, 'a-10-8': 5.

See above description. Unit - minute

AFA deactivation rate is used by the managed node to decide when it will enable the operational status of a T1 interface if the interface's BER rate is below the selected activation rate for a period specified by configAfaDectivationTime (see below). Enumeration: 'd-10-9': 4, 'd-10-8': 3, 'd-10-7': 2, 'd-10-6': 1.

See above description. Unit - minute

Enable/disable AFA function. Enumeration: 'disabled': 1, 'enabled': 2.

This object controls whether AFA will be activated when a near end LX-10 detects network loopback in the far end LX-10. If it's disabled, no AFA will be activated because of a far end network loopback. Enumeration: 'disabled': 1, 'enabled': 2.

There are 3 kinds of cards/port supported by the managed node: HSDP, Ethernet, or Token-Ring. Only one of them can be installed in the managed node. Hsdp is a high speed data port with v.35, rs-422, and HSSI interfaces. Enumeration: 'ethernet': 2, 'hsdp': 1, 'token-ring': 3.

Interface type used by HSDP. Enumeration: 'rs-422': 2, 'v-35': 1, 'hssi': 3.

CTS line control in HSDP. If the value of an instance of this object is set, the CTS line will always be set. If the value of an instance of this object is no-bandwidth, the CTS line will go low when no bandwidth is available after a hold-off time. If the value of an instance of this object is frequency- change, the CTS line will go low for a hold-off time when there is a frequency change. Enumeration: 'frequency-change': 3, 'no-bandwidth': 2, 'set': 1.

Status of CTS line in HSDP. Enumeration: 'clear': 1, 'set': 2.

Terminal timing source in HSDP. It applies only when the value of the instance of configHsdpMode is v-35 or rs-422. Enumeration: 'internal': 2, 'external': 1.

Status of terminal timing in HSDP. It applies only when the value of the instance of configHsdpMode is v-35 or rs-422. Enumeration: 'inverted': 2, 'normal': 1.

Status of receive timing in HSDP. It applies only when the value of the instance of configHsdpMode is v-35 or rs-422. Enumeration: 'inverted': 2, 'normal': 1.

Hold-off time for CA lead. If the hold-off is set at 5 seconds, and if the CTS control is sensitive to no-bandwidth, the CTS line will go low after 5 seconds when no bandwidth is available. If the CTS control is sensitive to frequency-change, the CTS line will stay low for 5 seconds when there is a frequency change, and then back to high. Enumeration: 'sec1': 1, 'sec3': 3, 'sec2': 2, 'sec5': 5, 'sec4': 4.

Select the way in which HDLC port will be assigned. If mode is manual, the HDLC port is selectable by the NMS. If mode is auto, the 2 LX-10's in the 2 sides will match their HDLC ports automatically. Enumeration: 'auto': 1, 'manual': 2.

Assign one of the DS1 ports as the HDLC port. If its value is 0, no port is asssigned as the HDLC port.

The DS1 port currently being used as the HDLC port in the far end LX-10.

Master/slave relationship of the 2 LX-10E's in the point to point connection. Enumeration: 'primary': 2, 'secondary': 1.

DS1 loopback table for 7 DS1 ports.

Each entry in the table contains the loopback status of a DS1 port.

The port number of one of the 7 DS1 ports

DS1 loopback is used to control the loopback state of one of the 7 DS1 interfaces in the managed node. Enumeration: 'none': 1, 'line': 3, 'card': 2.

This loopback status is controlled by the LA/LB leads in the remote node. Enumeration: 'active': 2, 'inactive': 1.

The state of the LA loopbak lead. Enumeration: 'clear': 1, 'set': 2.

The state of the LB loopbak lead. Enumeration: 'clear': 1, 'set': 2.

The managed node uses the states of the LA and LB leads to decide what kind of loopback to perform if faultLaLbLoopbackEnable (see below) is ENABLED. The meaning of LA and LB leads is as follows: loopback LA-Lead LB-Lead ------------------------------------------------ none clear clear local-line set clear remote-line clear set dte set set Enumeration: 'none': 1, 'local-line': 2, 'dte': 4, 'remote-line': 3.

Enable/disable the managed node to use the LA and LB lead states to perform loopbaks. Enumeration: 'disabled': 1, 'enabled': 2.

Enable/disable the customer equipment (DTE) to perform loopback toward the managed node. Enumeration: 'disabled': 1, 'enabled': 2.

Enable/disable the managed node to perform loopback toward the customer equipment (DTE). Enumeration: 'disabled': 1, 'enabled': 2.

A set request clears all entries in the current alarm table. A get/get-next request returns 0.

A set request clears all entries in the history alarm table. A get/get-next request returns 0.

Current alarm table.

Each entry in the table contains the information of a currently active alarm.

The tag of the alarm in the current alarm table.

The alarm type of the alarm. Enumeration: 'inband-loopback': 75, 'card-fail': 12, 'port-alarms-cleared': 22, 'ds1-yel': 16, 'p3-connected-to-p1': 38, 'p1-connected-to-p2': 26, 'p1-connected-to-p3': 27, 'p1-connected-to-p6': 30, 'customer-lpbk': 8, 'p1-connected-to-p4': 28, 'p1-connected-to-p5': 29, 'p7-connected-to-p4': 65, 'p7-connected-to-p5': 66, 'p7-connected-to-p6': 67, 'fan2-failed': 18, 'p7-connected-to-p1': 62, 'p7-connected-to-p2': 63, 'p7-connected-to-p3': 64, 'ds1-afa-alarm': 24, 'p5-connected-to-p6': 54, 'alarm1-in': 68, 'ds1-net-card-lpbk': 1, 'trunk-card-config-mismatch': 19, 'fan1-failed': 17, 'alarm3-in': 70, 'ds1-net-line-lpbk': 2, 'p6-connected-to-p5': 60, 'p6-connected-to-p4': 59, 'p6-connected-to-p7': 61, 'p6-connected-to-p1': 56, 'p6-connected-to-p3': 58, 'p6-connected-to-p2': 57, 'pll-fail': 11, 'la-lb-local-lpbk': 4, 'hdlc-unlocked': 71, 'p2-connected-to-p1': 32, 'p2-connected-to-p3': 33, 'p2-connected-to-p5': 35, 'p2-connected-to-p4': 34, 'p2-connected-to-p7': 37, 'p2-connected-to-p6': 36, 'ds1-ais': 15, 'cpu-restarted': 21, 'p3-connected-to-p2': 39, 'p3-connected-to-p4': 40, 'p3-connected-to-p5': 41, 'dte-clk-loss': 9, 'p3-connected-to-p7': 43, 'ds1-los': 13, 'ports-out-of-sequence': 77, 'all-alarms-cleared': 23, 'p4-connected-to-p7': 49, 'p4-connected-to-p6': 48, 'p4-connected-to-p5': 47, 'p4-connected-to-p3': 46, 'p4-connected-to-p2': 45, 'p4-connected-to-p1': 44, 'ds1-oof': 14, 'remote-afa': 73, 'la-lb-dte-lpbk': 3, 'remote-line-lpbk': 6, 'cim-card-config-mismatch': 20, 'hsdc-ga-oof': 10, 'att-fdl-loopback': 74, 'p5-connected-to-p2': 51, 'alarm2-in': 69, 'alarm-history-cleared': 25, 'dte-lpbk': 7, 'la-lb-remote-lpbk': 5, 't1-link-down': 76, 'p1-connected-to-p7': 31, 'p5-connected-to-p7': 55, 'p5-connected-to-p4': 53, 'far-end-loopback': 72, 'p3-connected-to-p6': 42, 'p5-connected-to-p3': 52, 'p5-connected-to-p1': 50.

The severity of the alarm. Enumeration: 'major': 3, 'minor': 2.

The type of the card which caused the alarm. Enumeration: 'ethernet': 2, 'hsdp': 1, 'token-ring': 3, 'ds1': 4.

The port number of the card which caused the alarm. Its value is between 1 and 7 for DS1 ports and 0 for others.

The time when the alarm was set.

A readable string which describes the alarm. Its format is as follows: 'Level' is the alarm severity. Its value can be 'Info', 'Major', or 'Minor'. 'Card' refers to where the alarm was generated. Its value can be 'HSDP', 'ENET', 'TRING', or 'DS1'. 'Port' refers to which port generated the alarm. Its value can be 1 to 7 for DS1 and 'empty' if no port number can be used for an alarm. 'Alarm Type' is an ASCII string of the alarm type. 'Time Occured' is the time when the alarm was generated.

History/Information alarm table.

Each entry in the history alarm table contains either a cleared alarm or an information alarm.

The tag of the alarm in the history alarm table.

The alarm type of the alarm. Enumeration: 'inband-loopback': 75, 'card-fail': 12, 'port-alarms-cleared': 22, 'ds1-yel': 16, 'p3-connected-to-p1': 38, 'p1-connected-to-p2': 26, 'p1-connected-to-p3': 27, 'p1-connected-to-p6': 30, 'customer-lpbk': 8, 'p1-connected-to-p4': 28, 'p1-connected-to-p5': 29, 'p7-connected-to-p4': 65, 'p7-connected-to-p5': 66, 'p7-connected-to-p6': 67, 'fan2-failed': 18, 'p7-connected-to-p1': 62, 'p7-connected-to-p2': 63, 'p7-connected-to-p3': 64, 'ds1-afa-alarm': 24, 'p5-connected-to-p6': 54, 'alarm1-in': 68, 'ds1-net-card-lpbk': 1, 'trunk-card-config-mismatch': 19, 'fan1-failed': 17, 'alarm3-in': 70, 'ds1-net-line-lpbk': 2, 'p6-connected-to-p5': 60, 'p6-connected-to-p4': 59, 'p6-connected-to-p7': 61, 'p6-connected-to-p1': 56, 'p6-connected-to-p3': 58, 'p6-connected-to-p2': 57, 'pll-fail': 11, 'la-lb-local-lpbk': 4, 'hdlc-unlocked': 71, 'p2-connected-to-p1': 32, 'p2-connected-to-p3': 33, 'p2-connected-to-p5': 35, 'p2-connected-to-p4': 34, 'p2-connected-to-p7': 37, 'p2-connected-to-p6': 36, 'ds1-ais': 15, 'cpu-restarted': 21, 'p3-connected-to-p2': 39, 'p3-connected-to-p4': 40, 'p3-connected-to-p5': 41, 'dte-clk-loss': 9, 'p3-connected-to-p7': 43, 'ds1-los': 13, 'ports-out-of-sequence': 77, 'all-alarms-cleared': 23, 'p4-connected-to-p7': 49, 'p4-connected-to-p6': 48, 'p4-connected-to-p5': 47, 'p4-connected-to-p3': 46, 'p4-connected-to-p2': 45, 'p4-connected-to-p1': 44, 'ds1-oof': 14, 'remote-afa': 73, 'la-lb-dte-lpbk': 3, 'remote-line-lpbk': 6, 'cim-card-config-mismatch': 20, 'hsdc-ga-oof': 10, 'att-fdl-loopback': 74, 'p5-connected-to-p2': 51, 'alarm2-in': 69, 'alarm-history-cleared': 25, 'dte-lpbk': 7, 'la-lb-remote-lpbk': 5, 't1-link-down': 76, 'p1-connected-to-p7': 31, 'p5-connected-to-p7': 55, 'p5-connected-to-p4': 53, 'far-end-loopback': 72, 'p3-connected-to-p6': 42, 'p5-connected-to-p3': 52, 'p5-connected-to-p1': 50.

The severity of the alarm. Its value can be either major or minor for DS1 ports and info for others. Enumeration: 'info': 1, 'major': 3, 'minor': 2.

The type of the card which caused the alarm. Enumeration: 'ethernet': 2, 'hsdp': 1, 'token-ring': 3, 'ds1': 4.

The port number of the card which caused the alarm. Its value is between 1 and 7 for DS1 ports and 0 for others.

The time when the alarm was set.

The time when the alarm was cleared.

A readable string which describes the alarm. Its format is as follows: 'Level' is the alarm severity. Its value can be 'Info', 'Major', or 'Minor'. 'Card' refers to where the alarm was generated. Its value can be 'HSDP', 'ENET', 'TRING', or 'DS1'. 'Port' refers to which port generated the alarm. Its value can be 1 to 7 for DS1 and 'empty' if no port number can be used for an alarm. 'Alarm Type' is an ASCII string of the alarm type. 'Time Occured' is the time when the alarm was generated. 'Time Cleared' is the time when the alarm was cleared.

A set request clears all DS1 performance monitoring data. A get/get-next request returns 0.

A set request clears all ethernet port card statistics. A get/get-next request returns 0.

A count of frames received by the ethernet port card.

A count of bytes received by the ethernet port card.

A count of frames transmitted on the ethernet port card.

A count of bytes transmitted on the ethernet port card.

A count of frames received that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.

A count of frames received that are an integral number of octets in length but do not pass the FCS check. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.

A count of successfully transmitted frames for which transmission is inhibited by exactly one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the enetPortCardStatsMultipleCollisionFrames object.

A count of successfully transmitted frames for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is not counted by the corresponding instance of the enetPortCardStatsSingleCollisionFrames object.

A count of frames for which the first transmission attempt is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions.

The number of times that a collision is detected on later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics.

A count of frames for which transmission fails due to excessive collisions.

A count of frames for which transmission fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the enetPortCardStatsLateCollisions object, the enetPortCardStatsExcessiveCollisions object, or the enetPortCardStatsCarrierSenseErrors object. The precise meaning of the count represented by an instance of this object is implementation- specific. In particular, an instance of this object may represent a count of transmission errors that are not otherwise counted.

The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame. The count represented by an instance of this object is incremented at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt.

A count of frames received that exceed the maximum permitted frame size. The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.

A set request clears all nxt1 port statistics. A get/get-next request returns 0.

A count of frames received by the NxT1 port.

A count of bytes received by the NxT1 port.

A count of frames transmitted on the NxT1 port.

A count of bytes transmitted on the NxT1 port.

A count of frames received by the NxT1 port that do not pass the CRC check.

LX-10-specific trap sent by the managed node when an alarm condition is set.

LX-10-specific trap sent by the managed node when an alarm condition is cleared.