DAVID-MIB: View SNMP OID List / Download MIB

The chassis type (option). Enumeration: 'reserved': 8, 'm6318st': 6, 'm6310tel': 4, 'other': 1, 'm6103': 3, 'm6102': 2, 'm6318sma': 7, 'm6310rj': 5.

The chassis backplane type (option). Enumeration: 'other': 1, 'reserved': 3, 'expressNet': 2.

The chassis backplane revision.

The chassis power supply type. This refers to the chassis transformer. Each module (including the Supervisor Module) has its own switching power supply. Enumeration: 'other': 1, 'standardXfmr': 2.

The chassis power supply status. This refers t othe chassis transformer. Each module (including the Supervisor Module) has its own switching power supply. The status of the individual modules' power supplies is a module attribute. Enumeration: 'failed': 2, 'ok': 1.

The chassis slot configuration table.

Descriptions of the modules (or boards) in each slot.

The DAVID ExpressNet chassis slot number. Valid entries are 1 to exNetChassisCapacity. On the physical Concentrator boxes, the Supervisor Modules are not numbered and the plug-in modules are numbered from 1 to n-1, where n is the number of slots in the Concentrator. For the purposes of the DAVID ExpressNet SNMP MIB, the Supervisor Module is numbered one past the highest-numbered plug-in module. For example, in a 12-Slot Concentrator, the plug-in modules are numbered 1-11 and the Supervisor Module is numbered 12.

The unique hardware ID for the module.

The type of the module. Enumeration: 'm6312': 6, 'm6311': 5, 'm6313st': 7, 'm6201': 4, 'm6203': 3, 'other': 2, 'm6313sma': 8, 'm6006': 9, 'reserved': 10, 'empty': 1.

Textual description of the module type.

The number of ports supported by the plug-in module. For a 10BASE-T Module the value is 12; for an FOIRL Module, 6; for a Supervisor Module, 1.

The number of slots in the chassis for plug-in modules. This number will be either five or twelve for a Concentrator and two for a Hub.

Indicates whether this repeater has retiming turned on. All DAVID ExpressNet repeaters implement retiming, so the value on(2) is always returned for this variable. Enumeration: 'on': 2, 'off': 1.

A count of frames that are successfully received by the Concentrator. This counter does not include frames received with frame-too-long, runt, FCS, or alignment errors. This counter includes broadcast and multicast frames that are received.

A count of data and padding octets in frames that are successfully received by the concentrator. This counter does not include frames received with frame-too-long, runt, FCS, or alignment errors. This counter includes octets in broadcast and multicast frames that are received.

A count of frames that are successfully received by the concentrator and are directed to an active non-broadcast group address. This counter does not include frames received with frame-too-long, runt, FCS, or alignment errors. Only frames that are for a multicast address that this interface is receiving are counted. Broadcast packets are not included.

A count of frames that are successfully received by the concentrator and are directed to the broadcast group address. This counter does not include frames received with frame-too- long, runt, FCS, or alignment errors. Multicast packets are not included.

Total collisions involving an incoming packet on any port (link or Network Interface port) in the Concentrator. This counter increments once for each collision involving an incoming packet on any port, no matter how many ports are involved.

A count of frames that are received by the Concentrator and exceed the maximum permitted frame size.

Number of frames received by the Concentrator that have a correct preamble (including double 1), but are shorter than the minimum legal frame size of 64 bytes (512 bits). Runts are commonly collision fragments, and as such do not necessarily indicate a problem in the network. Runts are also known as 'short frames.'

Fragments of packets, shorter than the minimum legal transmission size of 96 bits, that are received on the Concentrator. Fragments indicate an external noise hit (a problem on the network). Fragments are also known as 'pygmies.'

Number of frames received on the Concentrator that are byte-misaligned, such that the number of bits is not a multiple of 8. (These frames do not pass the frame check sequence check, but are not counted as FCS errors.)

A count of frames received by the Concentrator that are an integral number of octets in length and do not pass the frame check sequence (FCS) check. FCS errors are sometimes called CRC errors.

A total Concentrator count of the late collisions. The late collision counter for a port is incremented whenever a collision is detected on the port later than 512 bit times into the transmitted packet. Late collisions are not included in the collision count.

A descriptive string that can be used by a network administrator to name the Concentrator.

A count of the number of times that the jabber function had to be invoked because a frame received from one of this Concentrator's ports exceeded 5 msec in duration.

Amount of activity from this Concentrator's ports where a double-zero is seen before the start-frame delimiter (double-1). (This could indicate a polarity problem.)

Indicates how often ports on this Concentrator have been automatically partitioned by the Concentrator repeater function.

Number of times that frames have been received on the Concentrator with the transmission frequency (data rate) badly out of spec. This counter is incremented when the frequency of a received frame is so far out of spec that the packet has been corrupted within the relay. The spec allows deviations of +/- 100 parts per million (ppm). The DAVID ExpressNet Intelligent Concentrators can handle greater deviations than this, depending on frame length.

This composite counter includes jabbers, auto-partitions, and start-frame delimiter errors.

This composite counter includes frame check sequence errors, fragments, short frames, long frames, and alignment errors.

A series of ten bytes, each indicating the percentage of bandwidth utilization for a 100-millisecond interval. Together they give the bandwidth utilization for the previous second.

The value of sysUpTime at the point that the Concentrator repeater state machine was last reset.

The reset state of the Concentrator's repeater state machine. Writing a 2 will reset the Concentrator's control logic, without changing the current configuration. Writing a 3 will reset the Concentrator to the initial factory default configuration. Enumeration: 'reset': 2, 'resetToDefault': 3, 'noReset': 1.

A list of module entries. The number of entries is given by the number of modules that are obtained by the Concentrator Slot Configuration Table.

A module entry containing objects at the module level for a particular module.

A unique value for each module. Its value ranges between 1 and exNetChassisCapacity. The value for each module must remain constant at least from one reinitialization of the entity's network management system to the next reinitialization. This value is tied to the hardware chassis slot number.

The type of the module. Enumeration: 'm6312': 6, 'm6311': 5, 'm6313st': 7, 'm6201': 4, 'm6203': 3, 'other': 2, 'm6313sma': 8, 'm6006': 9, 'reserved': 10, 'empty': 1.

The hardware configuration of the module or hub. For model 6311, 6312, and 6313 board types, the type of Network Interface provided with the board is indicated by the following values (0-3 apply to ExpressNet Hubs; 7 is returned for Concentrator modules): 0 = AUI 1 = 10BASE2 2 = 10BASE-T 3 = FOIRL 7 = no interface

The operational status of the module. If the status is selfTestFail(3), the exNetModuleSelfTestResult will give more detailed information about the module's condition. Enumeration: 'selfTestFail': 3, 'ok': 1, 'noComms': 2.

The reset state of the module. Writing a 2 will reset the module's control logic, without changing the current configuration. Writing a 3 will reset the module to the initial factory default configuration. Enumeration: 'reset': 2, 'resetToDefault': 3, 'noReset': 1.

Tells whether the module is partitioned or enabled. Writing a 2 will partition the module and 1 will enable the module. Enumeration: 'partition': 2, 'enabled': 1.

Tells whether the module is under network management control. DAVID ExpressNet Concentrators always return nmControl(2), since all modules are always under network management control. Enumeration: 'notNmControl': 1, 'nmControl': 2.

The status of the module's power supply. Enumeration: 'fail': 2, 'ok': 1.

A count of frames that are successfully received by the module. This counter does not include frames received with frame-too-long, runt, FCS, or alignment errors. This counter includes broadcast and multicast frames that are received.

A count of data and padding octets in frames that are successfully received by the module. This counter does not include frames received with frame-too-long, runt, FCS, or alignment errors. This counter includes octets in broadcast and multicast frames that are received.

Total collisions involving an incoming packet on any link or the backplane connector in the module. This counter increments once for each collision involving an incoming packet on any port, no matter how many ports are involved.

A count of frames that are received by the module and exceed the maximum permitted frame size.

Number of frames received by the module that have a correct preamble (including double 1), but are shorter than the minimum legal frame size of 64 bytes (512 bits). Runts are commonly collision fragments, and as such do not necessarily indicate a problem in the network. Runts are also called 'short frames.'

Number of frames received by the module that are byte-misaligned, such that the number of bits is not a multiple of 8. (These frames do not pass the frame check sequence check, but are not counted as FCS errors.)

A count of frames received by the module that are an integral number of octets in length and do not pass the frame check sequence (FCS) check. FCS errors are sometimes called CRC errors.

A module count of the late collisions on all of the module's ports. The late collision counter for a port is incremented whenever a collision is detected on the port later than 512 bit times into the transmitted packet. Late collisions are not included in the collision count.

A descriptive string that can be used by a network administrator to name the module.

A count of the number of times that the jabber function had to be invoked because a frame received from one of this module's ports exceeded 5 msec in duration.

Amount of activity from this module's ports where a double-zero is seen before the start-frame delimiter (double-1). (This could indicate a polarity problem.)

Indicates how often ports on this module have been automatically partitioned by the module repeater function.

Number of times that frames have been received from ports on this module with the transmission frequency (data rate) badly out of spec. This counter is incremented when the frequency of a received frame is so far out of spec that the packet has been corrupted within the relay. The spec allows deviations of +/- 100 parts per million (ppm). The DAVID ExpressNet Concentrators can handle greater deviations than this, depending on frame length.

This composite counter includes jabbers, auto-partitions, and start-frame delimiter errors.

This composite counter includes frame check sequence errors, fragments, short frames, long frames, and alignment errors.

Fragments of packets, shorter than the minimum legal transmission size of 96 bits, that are received on the module. Fragments indicate an external noise hit (a problem on the network). Fragments are also known as 'pygmies.'

Compresses the configuration of all of this module's ports into a two-byte integer value. Sums f(x) as x goes from 1 to number of ports, where f(x) = 0 for disabled port and f(x) = exp(2,x-1) for enabled port.

Compresses the link status configuration of all of this module's ports into a two-byte integer value. Sums f(x) as x goes from 1 to number of ports, where f(x) = 0 for port with link status disabled and f(x) = exp(2,x-1) for port with link status enabled.

The value of sysUpTime at the point that the module repeater state machine was last reset.

Compresses the link status of all of this module's ports into a two-byte integer value. Sums f(x) as x goes from 1 to number of ports, where f(x) = 0 for port with link status test passed (link active) and f(x) = exp(2,x-1) for port with link status test failed (link inactive). For ports with link status test disabled, zero is returned. For example, if link status is active on all ports, the value returned is zero. If link status for ports 3 and 7 is inactive and the rest of the ports have active link status, the value returned is (2^(3-1) + 2^(7-1)) = (4 + 64) = 68.

The firmware revision of the GAP processor on the module.

The feature package associated with the GAP processor on the module.

The self-test result value returned by the GAP processor on the module. Zero indicates that the module passed all tests. Bits set in the result indicate error conditions, as follows: Bit number Error encountered 0 ROM failure 1 CPU failure 2 RAM failure 3 repeater module failure 4 reserved 5 internal power (-5v) failure 6 NI power fuse (+12v) failure

A list of port entries. The number of entries is given by knowing the number of occupied slots in the exNetSlotConfigTable and the number of ports that are on an exNetModuleType.

A port entry containing objects at the port level for a particular port.

A unique value for each module. Its value ranges between 1 and exNetChassisCapacity.

A unique value for each port. Its value ranges between 1 and the value of exNetBoardNumOfPorts for this module.

For 10BASE-T ports: this is the link integrity test defined by the 10BASE-T standard. If link status test is enabled, this flag indicates whether the link is active or inactive. There are several reasons for an inactive link: . PC or workstation connected to the MAU has been turned off . disrupted link (e.g., wiring problem) . TP-MAU on the end of the link is missing, dead, or powered off . transmit and receive polarities are swapped For FOIRL ports: the link status is constantly tested; thus, this variable is always meaningful. A value of off(1) indicates a low-light condition (poor signal quality). The value on(2) indicates that signal quality on the link is ok. For AUI ports: the value other(3) is always returned since link status test does not apply. Enumeration: 'on': 2, 'other': 3, 'off': 1.

Indicates whether the port is currently partitioned by the Concentrator's auto-partition protection. (The Concentrator automatically partitions a port if it is signalling continuous collision, or 32 consecutive collisions.) Writing a 1 will forcibly unpartition the port. Writing a 2 or a 3 is illegal. To enable or disable the port, use the exNetPortConfig variable. Enumeration: 'autoPartition': 3, 'partition': 2, 'enabled': 1.

Tells whether the DTE connected to the port is jabbering (receiving a frame longer than 5 msec in duration). Enumeration: 'ok': 1, 'jabbering': 2.

A count of frames that are successfully received by the port. This counter does not include frames received with frame-too- long, runt, FCS, or alignment errors. This counter includes broadcast and multicast frames that are received.

A count of data and padding octets in frames that are successfully received by the port. This counter does not include frames received with frame-too-long, runt, FCS, or alignment errors. This counter includes octets in broadcast and multicast frames that are received.

Number of times this port was involved in a collision with another port in the same Hub.

A count of frames that are received by the port and exceed the maximum permitted frame size.

Number of frames received by the port that have a correct preamble (including double 1), but are shorter than the minimum legal frame size of 64 bytes (512 bits). Runts are commonly collision fragments, and as such do not necessarily indicate a problem in the network. Runts are also called 'short frames.'

Number of frames received by the port that are byte-misaligned, such that the number of bits is not a multiple of 8. (These frames do not pass the frame check sequence check, but are not counted as FCS errors.)

A count of frames received by the port that are an integral number of octets in length and do not pass the frame check sequence (FCS) check. This counter is incremented when the frameCheckError status is detected. FCS errors are sometimes called CRC errors.

Number of times that a collision has been detected on this port later than 512 bit times into the transmitted packet. Late collisions are not included in the collision count.

A descriptive string that can be used by a network administrator to name the port.

A count of the number of times that the jabber function had to be invoked because a frame received from this port exceeded 5 msec in duration.

Amount of activity from this port where a double-zero is seen before the start-frame delimiter (double-1). (This could indicate a polarity problem.)

Indicates how often this port has been automatically partitioned by the module repeater function.

Number of times that frames have been received from this link with the transmission frequency (data rate) badly out of spec. This counter is incremented when the frequency of a received frame is so far out of spec that the packet has been corrupted within the relay. The spec allows deviations of +/- 100 parts per million (ppm). The DAVID ExpressNet Concentrators can handle greater deviations than this, depending on frame length.

This composite counter includes jabbers, auto-partitions, late collisions, start-frame delimiter errors, and out-of-spec bit rate errors.

This composite counter includes frame check sequence errors, fragments, short frames, long frames, and alignment errors.

Fragments of packets, shorter than the minimum legal transmission size of 96 bits, that are received on this port. Fragments indicate an external noise hit (a problem on the network).

The type of the port. Enumeration: 'tenBasefSync': 4, 'other': 1, 'repeater': 2, 'tenBasefAsync': 3.

The type of the MAU attached to the port. Enumeration: 'tenBase2': 5, 'tenBaseT': 3, 'tenBase5': 2, 'fOIRL': 4, 'other': 1, 'tenBaseFA': 6.

The administrative state of the port. If both transmit and receive are enabled, the port state is enabled. If both transmit and receive are disabled, the port state is disabled. Enumeration: 'disabled': 3, 'rxDisabled': 5, 'other': 1, 'enabled': 2, 'txDisabled': 4.

The administrative status of the link status test for this link. If both transmit and receive are enabled, the link status test is enabled. If both transmit and receive are disabled, the link status test is disabled. This variable applies only to ports with MauType = 10BASE-T. The value other(1) is returned for other MAU types. Enumeration: 'disabled': 3, 'rxDisabled': 5, 'other': 1, 'enabled': 2, 'txDisabled': 4.

The polarity of the port. Applies only to ports with MAU type 10BASE-T. The value other(1) is returned for other MAU types. Enumeration: 'positive': 2, 'txNegative': 4, 'other': 1, 'negative': 3, 'rxNegative': 5.

Whether or not transmit test is enabled on the link. Transmit test applies only to links of type 10BASE-T. The value other(1) is returned for other MAU types. THIS TEST CAN BE DISRUPTIVE TO THE NETWORK. Enumeration: 'disabled': 2, 'other': 1, 'enabled': 3.

The DAVID ExpressNet Ethernet network management type. Enumeration: 'other': 1, 'tbd': 2.

The network management ICM hardware version number: 1=Rev. A, 2=Rev. B, etc.

The network management ICP firmware version.

The network management major software version number, where the version number is of the form major.minor, e.g. 3.0. Refers to the ECP (External Communications Processor).

The network management minor software version number, where the version number is of the form major.minor, e.g. 3.0. Refers to the ECP.

Indicates that the network management is on line and operating. For the DAVID ExpressNet Concentrators, management status is always online(2). Enumeration: 'offline': 1, 'online': 2.

Indicates whether the network management is operating in primary or secondary mode. Presently, all DAVID ExpressNet Concentrators return primary(1). Enumeration: 'primary': 1, 'secondary': 2.

Network management reset status. Writing a 2 to this object will reset the network management (stop refreshing the watchdog timer) and restart. Enumeration: 'reset': 2, 'notReset': 1.

Network management restart status. Writing a 2 to this object will restart the network management. This initializes all the counters, rereads the EEPROM data structure, and starts executing from the beginning of the code. Enumeration: 'notRestart': 1, 'restart': 2.

The network management's administrative IP address. This parameter will take effect ONLY after a restart (exNetMgmtRestart) or reset (exNetMgmtReset) is issued. At that time it becomes the operational IP address. The value of the CURRENT operational IP address can be obtained from the ipAdEntAddr entry in the ipAddrTable.

The network management's administrative subnet mask. This parameter will take effect ONLY after a restart (exNetMgmtRestart) or reset (exNetMgmtReset) is issued. At that time it becomes the operational subnet mask. The value of the CURRENT operational subnet mask can be obtained from the ipAdEntNetMask entry in the ipAddrTable.

The network management's administrative default gateway IP address. This parameter will take effect ONLY after a restart (exNetMgmtRestart) or reset (exNetMgmtReset) is issued. At that time it becomes the operational default gateway IP address. The value of the CURRENT operational default gateway's IP address can be obtained from the ipRoutingTable.

Returns the baud rate in bits per second of the RS-232 port. Note: The Concentrators autobaud to match the device attached to the RS-232 port.

This is an informational string that could be used to show the physical location (i.e., area) of the network management or Concentrator. This parameter is saved in non-volatile memory and will survive a reset. Note: This variable is aliased to the sysLocation variable in the MIB-II system group. Changing one will change the other. It is suggested that the system group variable be used whenever possible.

This entity's Trap Receiver Table (10 entries).

A destination address and community string to a particular trap receiver.

Setting this object to the value invalid(2) invalidates the corresponding entry in the exNetTrapReceiverTable. That is, it effectively disassociates the address identified with the entry by removing the entry from the table. Enumeration: 'other': 1, 'invalid': 2.

IP address for trap receiver.

Community string used for traps.

Enable or disable the use of authentication error trap generation. Enumeration: 'enable': 2, 'disable': 1.