ELH100-MIB: View SNMP OID List / Download MIB

Software major version

Software minor version

Hardware version of system board

Community table

Index in community table.

The status of this row entry. Before add a row into table, it should be created first. Set Valid(1) to a row will create this row. To delete a row from this table, set this object for the row to invalid(2). Row sets for new rows with a row status set to invalid(2) return a BAD VALUE error. This object will always read as valid(1). If no more rows can be added to the end of the table, then a row set to create a new row will return BAD VALUE. When rows are deleted from this table, the indexes of the other rows do not change. In other words, this table can be 'sparse' or have 'holes'. Deleted entries can be re-created using a row set with a row status of valid(1). Enumeration: 'valid': 1, 'invalid': 2.

The community string that is required for any requests coming from this host. The default value for this object is 'public'.

Access mode of the community. Enumeration: 'readWrite': 3, 'readOnly': 2, 'invalid': 1.

A list of IP trap destination entries.

A destination entry which defines the IP address to which traps are sent for a community.

A value that uniquely identifies this IPTrap Entry.

The status of this row entry. Before add a row into table, it should be created first. Set valid(1) to a row will create this row. To delete a row from this table, set this object for the row to invalid(2). Row sets for new rows with a row status set to invalid(2) return a BAD VALUE error. This object will always read as valid(1). If no more rows can be added to the end of the table, then a row set to create a new row will return BAD VALUE. When rows are deleted from this table, the indexes of the other rows do not change. In other words, this table can be 'sparse' or have 'holes'. Deleted entries can be re-created using a row set with a row status of valid(1). Enumeration: 'valid': 1, 'invalid': 2.

A community name to which this destination IP address belongs.

The IP address to send traps to on behalf of this entry.

The file server of the download file

The file name to download

Permanent upgrade stores download software into permanent storage of the agent device. Temporary upgrade just put download software in RAM, often for a test only. Enumeration: 'permanent': 1, 'temporary': 2.

elh100DownloadAction triggers the download operation. The run option starts new software execution after download is complete. The noRun option does not start new software execution. The new software will be effective after next restart. Note that noRun option is useful only when the download is permanent. Enumeration: 'run': 1, 'noRun': 2.

A write to restart the machine. Only three values are accepted: normal -- 0, coldstart -- 1, warmstart -- 2.

The IP address which is in used in the Dual-Speed Hub system.

The subnet mask which is in used in the Dual-Speed Hub system.

The prefered gateway used to send traps.

The IP address of the BOOTP server that last responded. If no BOOP server has responded, then this object will be '0.0.0.0'.

Used to change the IP address of the Dual-Speed Hub system.

Used to change the subnet mask of the Dual-Speed Hub system.

Used to change the prefered gateway to send traps.

This object allows the users to enable/disable generation of BOOTP requests. Enumeration: 'disable-bootp': 1, 'enable-bootp': 2.

Setting the stackIP, stackNetMask,stackGateway, and stackBootUpIP will not make these parameters take effect immediately. They will take effect when ipInformationReset is set to reset(2). Enumeration: 'reset': 2, 'noReset': 1.

< FOR cabletronELH100 Dual-Speed Hub DEFINITION : > There are two kinds of hub : 12 ports need (1+ 12 + 1 + 1 + 1 + 1 +1 +1 +1) 20 bytes and 24 ports need (1+ 24 + 1 + 1 + 1 + 1 +1 +1 +1) 32 bytes The maximun size : 256 bytes (total for 8 hubs)=8 hub * (1+ 24 + 1 + 1 + 1 +1 +1 +1 +1) byte | byte256 byte255......................byte2 byte1 | bit7 bit6 ... bit1 bit0 Use the first byte of each hub to indicate whether 20 or 32 bytes is used. BYTE 1: total number ports of a hub 00001100 : 12 ports | | bit7... bit0 00011000 : 24 ports | | bit7... bit0 For 12 ports hub BYTE 2 - 13 : port status for port 1 - 12 port *BYTE 2 : port status for port 1 bit 0-4 : LED status bit 0 : link status 0 - no link; 1 - link bit 1 : partition status 0 - no part.; 1 - part. bit 2 : port operation status 0 - disabled; 1 - enabled bit 3-4 : port type status 00 - not present 01 - tenMb 10 - onehundredMb 11 - reserved bit 5-7 : reserved BYTE 14-25 :reserved BYTE 26 : Expansion Port (EP) status1 bit 0-3: EP Type 0000 - not present 0010 - Internal Switch 0011 - External 100Base-TX 0100 - External 100Base-FX(ST) 0101 - External 100Base-FX(SC) 0110 - Internal + External 100Base-TX 0111 - Internal + External 100Base-FX(ST) 1000 - Internal + External 100Base-FX(SC) 1001 - Unknown switch module 1010 - Undertermined bit 4-7: reserved BYTE 27 : Expansion Port (EP) status2 bit 0-3 : LED status bit 0 : 10M port status 0 - disable; 1 - enable bit 1 : 100M port status 0 - disable; 1 - enable bit 2 : uplink port status 0 - disable; 1 - enable bit 3 : Uplink port half/full duplex status 1 - full duplex; 0 - half duplex bit 4 : EP collision led status 0 - off; 1 - on bit 5-6 : bit 3 : tx LED status 0 - off; 1 - tx on bit 4 : rx LED status 0 - off; 1 - rx on bit 7-8 : reserved BYTE 28 : tenMb segment traffic/collision bit 0-1 : tenMb traffic LED status 00 - no traffic 01 - low traffic 10 - middle traffic 11 - high traffic bit 2-5 : tenMb collision LED status 0000 - none 0001 - 1 % 0010 - 3 % 0011 - 5 % 0100 - 10 % 0101 - >= 15 % bit 6-7 : reserved BYTE 29 : onehundredMb segment traffic/collision /Power/Switch LED status bit 0-1 : onehundredMb traffic LED status 00 - no traffic 01 - low traffic 10 - middle traffic 11 - high traffic bit 2-5 : onehundredMb collision LED status 0000 - none 0001 - 1 % 0010 - 3 % 0011 - 5 % 0100 - 10 % 0101 - >= 15 % bit 6 : Power LED 0 - OFF; 1 - ON bit 7 : Switch LED 0 - OFF; 1 - ON BYTE 30 :SNMP agent & switch status bit 0: internal switch bit 0 - not exist; 1 - exist bit 1: internal switch status 0 - inactive; 1 - active bit 2: expension switch bit 0 - bad; 1 - good bit 3: expension switch status 0 - inactive; 1 - active bit 4: agent bit 0 - not exist; 1 - exist bit 5 : master status 0 - Slave; 1 - Master bit 6 - 7 : reserved BYTE 31 : Rmon status bit 0 : rmon bit 0 - not exist; 1 - exist bit 1 - 2 :rmon segment 00 - all stack 01 - segment tenMb 10 - segment onehundredMb 11 - reserved bit 3 - 5 : RMON group Status 000 - not-present 001 - disabled 010 - Rmon-4Group 011 - Rmon-7Group 100 - Rmon-all 101 to 111 - reserved bit 6 -7 : reserved BYTE 32 : Hub Position(Hub ID)/Bus Termination bit 0 - 3 : hub position 0000 - invalid 0001 - 1 0010 - 2 0011 - 3 0100 - 4 0101 - 5 0110 - 6 0111 - 7 1000 - 8 1001 to 1111 - reserved bit 4 : termination status 0 - not end hub 1 - end hub in the stack bit 5 - 7 : reserved For 24 ports hub BYTE 2 - 25 : port status for port 1 - 24 port *BYTE 2 : port status for port 1 bit 0-4 : LED status bit 0 : link status 0 - no link; 1 - link bit 1 : partition status 0 - no part.; 1 - part. bit 2 : port operation status 0 - disabled; 1 - enabled bit 3-4 : port type status 00 - not present 01 - tenMb 10 - onehundredMb 11 - reserved bit 5-7 : reserved BYTE 26 : Expansion Port (EP) status1 bit 0-3: EP Type 0000 - not present 0010 - Internal Switch 0011 - External 100Base-TX 0100 - External 100Base-FX(ST) 0101 - External 100Base-FX(SC) 0110 - Internal + External 100Base-TX 0111 - Internal + External 100Base-FX(ST) 1000 - Internal + External 100Base-FX(SC) 1001 - Unknown switch module 1010 - Undertermined bit 4-7: reserved BYTE 27 : Expansion Port (EP) status2 bit 0-3 : LED status bit 0 : 10M port status 0 - disable; 1 - enable bit 1 : 100M port status 0 - disable; 1 - enable bit 2 : uplink port status 0 - disable; 1 - enable bit 3 : Uplink port half/full duplex status 1 - full duplex; 0 - half duplex bit 4 : EP collision led status 0 - off; 1 - on bit 5-6 : bit 3 : tx LED status 0 - off; 1 - tx on bit 4 : rx LED status 0 - off; 1 - rx on bit 7-8 : reserved BYTE 28 : tenMb segment traffic/collision bit 0-1 : tenMb traffic LED status 00 - no traffic 01 - low traffic 10 - middle traffic 11 - high traffic bit 2-5 : tenMb collision LED status 0000 - none 0001 - 1 % 0010 - 3 % 0011 - 5 % 0100 - 10 % 0101 - >= 15 % bit 6-7 : reserved BYTE 29 : onehundredMb segment traffic/collision /Power/Switch LED status bit 0-1 : onehundredMb traffic LED status 00 - no traffic 01 - low traffic 10 - middle traffic 11 - high traffic bit 2-5 : onehundredMb collision LED status 0000 - none 0001 - 1 % 0010 - 3 % 0011 - 5 % 0100 - 10 % 0101 - >= 15 % bit 6 : Power LED 0 - OFF; 1 - ON bit 7 : Switch LED 0 - OFF; 1 - ON BYTE 30 :SNMP agent & switch status bit 0: internal switch bit 0 - not exist; 1 - exist bit 1: internal switch status 0 - inactive; 1 - active bit 2: expension switch bit 0 - bad; 1 - good bit 3: expension switch status 0 - inactive; 1 - active bit 4: agent bit 0 - not exist; 1 - exist bit 5 : master status 0 - Slave; 1 - Master bit 6 - 7 : reserved BYTE 31 : Rmon status bit 0 : rmon bit 0 - not exist; 1 - exist bit 1 - 2 :rmon segment 00 - all stack 01 - segment tenMb 10 - segment onehundredMb 11 - reserved bit 3 - 5 : RMON group Status 000 - not-present 001 - disabled 010 - Rmon-4Group 011 - Rmon-7Group 100 - Rmon-all 101 to 111 - reserved bit 6 -7 : reserved BYTE 32 : Hub Position(Hub ID)/Bus Termination bit 0 - 3 : hub position 0000 - invalid 0001 - 1 0010 - 2 0011 - 3 0100 - 4 0101 - 5 0110 - 6 0111 - 7 1000 - 8 1001 to 1111 - reserved bit 4 : termination status 0 - not end hub 1 - end hub in the stack bit 5 - 7 : reserved

The ifIndex of the segment to which the agent's Ethernet NIC (Network Interface Controller) is connected. ifIndex 1 is the 100Mbps NIC; ifIndex 2 is the 10Mbps NIC. The factory setting is ifIndex 1.

This table defines the unit serial numbers tracked by the agent. A maximum of 6 serial numbers are tracked.

The index of the serial number being referenced. Indexes are always sequential, starting with 1.

The serial number. Every ELH100 unit has a unique serial number.

The current unit ID of the unit with this serial number. If the unit with this serial number is not currently in the stack, this object's value is 255. If this object does not match sNIndex, it may mean that the unit has been moved. The configurations in the following tables may be affected: backplaneTable portTable switchPortTable backupPortTable intrusionTable rptrPortTable (RFC2108)

The maximum number of Telnet sessions that may be active at one time. The factory setting is 2.

Setting this object to enabled(1) causes the agent to automatically close Telnet sessions when no activity has occurred for telnetAutoLogoutTimeout minutes. Setting this object to disabled(2) disables automatic logout. The factory setting is enabled(1). Enumeration: 'disabled': 2, 'enabled': 1.

The number of minutes of inactivity after which the agent may automatically close a Telnet session. Telnet auto-logout is active only when telnetAutoLogoutEnable is set to enabled(1). The factory setting is 10 minutes.

The interval for automatic statistics refresh for VT100 screens. The factory setting is seconds30(30). Enumeration: 'seconds30': 30, 'seconds300': 300, 'seconds60': 60, 'seconds5': 5, 'seconds120': 120, 'seconds180': 180.

This table defines basic configuration information for each unit in the stack.

The group ID of the group being referenced. Groups are numbered in top-down order, with the top group being group 1. Attempts to reference nonexistent groups are rejected with an error-status of noSuchName(2).

The type of group. Enumeration: 'elh100-24tx': 4, 'unknown': 2, 'notPresent': 1, 'elh100-12tx': 3.

Setting this object to reset(2) causes the agent to reset all RFC1757 and RFC2108 counters for all ports on this group. This object always returns noReset(1) when read. Attempts to set this object to noReset(1) are rejected with an error-status of badValue(3). Enumeration: 'reset': 2, 'noReset': 1.

The status of this group's management module. Only one management module in a stack is allowed to act as the active agent. A value of notPresent(1) indicates that there is no management module in this group. A value of active(2) means that this group's management module is acting as the stack's active agent. A value of standby(3) means that this group contains a management module, but it is not the active agent. Enumeration: 'active': 2, 'standby': 3, 'notPresent': 1.

The configuration database version number of this managing agent. If a management module is not present, this object's value is a zero-length string. Each management agent contains a database version that is determined by the version of the agent's firmware. Different firmware versions MAY or MAY NOT have the same database version number. Usually a database version number changes only when new features are added. Database version numbers are used to determine which components of non-volatile configuration may be synchronized between active and standby management modules. A component belonging to a higher (newer) database version may not be present in a lower (older) database version; in this case, the component will not be updated in the older database.

The type of the switch module. Enumeration: 'internalSwitch10-100': 3, 'switchMediaTX-10-100': 7, 'unknown': 2, 'switchMediaFX-ST': 9, 'mediaFX-SC': 5, 'mediaTX-10-100': 4, 'notPresent': 1, 'mediaFX-ST': 6, 'switchMediaFX-SC': 8.

Indicates whether or not a switch module is active. In order to avoid network loops, the switch hardware allows only one switch to bridge the stack's common 10Mbps and 100Mbps backplanes. Redundant switches are automatically disabled. Note that this restriction does not apply to switches that bridge one or more micro-isolated segments. Individual switch ports may be administratively enabled/disabled using the object switchPortAdminStatus. If the switch is hardware-disabled, the switch is disabled no matter what its administrative status. Enumeration: 'active': 1, 'notActive': 2, 'notApplicable': 3.

This table provides backplane isolation/connection status for each unit's 100Mbps and 10Mbps segments.

The group ID of the segment being referenced. Groups are numbered in top-down order, with the top group being group 1. Attempts to reference nonexistent groups are rejected with an error-status of noSuchName(2).

The segment ID of the segment being referenced. Enumeration: 'tenMbps': 10, 'oneHundredMbps': 100.

The status of the segment's connection to the backplane bus. The factory setting is attached(2). Enumeration: 'attached': 2, 'isolated': 1.

This table defines basic configuration information for each repeater port in the stack.

The group ID of the repeater port being referenced. Groups are numbered in top-down order, with the top group being group 1. Attempts to reference nonexistent groups are rejected with an error-status of noSuchName(2).

The port ID of the repeater port being referenced.

The speed at which the port is currently operating. If there is no link on the port, this object returns noLink(1). Enumeration: 'tenMbps': 10, 'oneHundredMbps': 100, 'noLink': 1.

Selects the speed at which the port operates. The factory setting is autoNegotiate(1). Enumeration: 'tenMbps': 10, 'oneHundredMbps': 100, 'autoNegotiate': 1.

The number of valid-length packets with CRC errors received on the agent's MAC port.

The number of valid-length packets with alignment errors received on the agent's MAC port.

The number of collisions detected on the agent's MAC port.

The number of times the agent's MAC port became isolated. Port isolation occurs only during 100Mbps operation.

The number of packets with symbol errors received on the agent's MAC port. Symbol errors occur only during 100Mbps operation.

This table provides configuration information about each port on each switch module in the stack.

The group ID of the switch module port being referenced. Groups are numbered in top-down order, with the top group being group 1. If a switch module is not installed on the group, then a GetNextRequest skips the entry. Attempts to reference nonexistent groups are rejected with an error-status of noSuchName(2).

The port ID of the switch module port being referenced. Port 1 is always the internal 100Mbps port. Port 2 is always the internal 10Mbps port; note that this port is inactive on media modules. Port 3 is always the external port; note that this port is inactive on internal switch modules.

The administrative status of the port. Setting this object to enabled(1) enables the port. Setting this object to disabled(2) disables the port. On media modules, port 2 (the internal 10Mbps port) cannot be managed. The external port cannot be managed on any module. In these cases, attempts to set this object are rejected with an error-status of badValue(3). The factory setting for manageable ports is enabled(1). Note that if switchModuleActive is notActive(2), then the switch is disabled no matter what its administrative status. Enumeration: 'disabled': 2, 'notApplicable': 3, 'enabled': 1.

The speed at which the switch port is currently operating. If the port is inactive (port 2 on media modules and port 3 on internal switch modules), noLink(1) is returned. Enumeration: 'tenMbps': 10, 'oneHundredMbps': 100, 'noLink': 1.

The duplex mode in which the switch port is currently operating. If the port is inactive (port 2 on media modules and port 3 on internal switch modules), notApplicable(3) is returned. Enumeration: 'notApplicable': 3, 'fullDuplex': 2, 'halfDuplex': 1.

Indicates if link is detected on the port. If the port is inactive (port 2 on media modules and port 3 on internal switch modules), noLink(2) is returned. Enumeration: 'link': 1, 'noLink': 2.

This table provides statistics on each port on each switch module in the stack. Note that statistics for the external port on media and switch/media modules are unavailable to the agent and are reported as 0. Statistics for port 2 (the internal 10Mbps port) on media modules are also reported as 0.

The group ID of the switch module port being referenced. If the group is not present, or if there is no switch module installed in the group, GetRequests and SetRequests are rejected with an error-status of noSuchName(2). GetNextRequests skip entries for nonexistent modules.

The port ID of the switch module port being referenced. Port 1 is always the internal 100Mbps port. Port 2 is always the internal 10Mbps port. Port 3 is always the external port. Note that port 2 is inactive on media modules and port 3 is inactive on internal switch modules. Note: Statistics for the external port are unavailable to the agent and are reported as 0.

The number of valid frames received by the port.

The number of octets (bytes) in all valid frames received by the port.

The number of valid-length frames received by the port that had FCS (frame check sequence) errors.

The number of valid-length frames received by the port that had alignment errors.

The number of frames received by the port that were longer than 1518 bytes.

The number of frames received by the port that were shorter than 82 bits.

The number of frames received by the port that were longer than 82 bits but shorter than 512 bits (64 bytes).

The number of collisions detected on the port.

The number of collisions detected on the port that occurred later than 512 bit-times into the transmission of a packet.

The number of times any activity continued for more than 4 to 7.5 milliseconds.

The number of times the incoming data rate mismatched the local clock source enough to cause a FIFO overflow or underflow.

The number of times this port was auto-partitioned by the hardware. In 100Mbps mode, a port auto-partitions when it detects more than 60 consecutive collisions. In 10Mbps mode, a port auto-partitions after 32 consecutive collisions.

The number of good broadcast frames received by the port.

The number of good multicast (not broadcast) frames received by the port.

The number of times this port was auto-isolated by the hardware. This occurs only during 100Mbps operation. A port auto-isolates when it transmits more than 2 consecutive false carrier events.

This table allows configuration of backup port pairs.

The index of the Backup table entry being referenced. Indexes may be nonconsecutive.

Group ID of the primary port. Attempts to set this object to a nonexistent group are rejected with an error-status of badValue(3). If this object belongs to an empty entry, it returns a value of 255.

Port number of the primary port. Attempts to set this object to a nonexistent port are rejected with an error-status of badValue(3). If this object belongs to an empty entry, it returns a value of 255.

Group ID of the secondary port. The secondary port may be on any group in the stack. Attempts to set this object to a nonexistent unit are rejected with an error-status of badValue(3). If this object belongs to an empty entry, it returns a value of 255.

Port number of the secondary port. Attempts to set this object to a nonexistent port are rejected with an error-status of badValue(3). If this object belongs to an empty entry, it returns a value of 255.

The status of backup port monitoring for this port pair. Setting this object to active(2) enables the primary port, disables the secondary port, and activates backup port monitoring. Once backup port monitoring is activated, the value of this object is reported as standby(3) until a triggering event occurs. A triggering event may be loss of link after link was active, port auto-partition, or port auto-isolate (100Mbps ports only). After a triggering event occurs, the primary port is disabled, the secondary port is enabled, and the value of this object is reported as backup(4). A RFC2108 rptrHealthInfo trap is transmitted. To re-enable the primary port and re-activate backup port monitoring, set this object to active(2). To disable backup port monitoring for the port pair, set this object to inactive(1). To remove the port pair from the backup table, set this object to delete(6). The enable/disable statuses of the ports do not change when they are deactivated or deleted; use rptrPortAdminStatus (RFC2108) to set the ports to the desired state. A value of invalid(5) indicates that one or both of the units for which this entry was originally configured is not currently in the stack. Backup port monitoring is disabled. The agent makes this determination by tracking the serial numbers on the units in the stack. The values standby(3), backup(4), and invalid(5) are read-only. Attempts to set this object to either of these values are rejected with an error-status of badValue(3). Enumeration: 'standby': 3, 'invalid': 5, 'inactive': 1, 'active': 2, 'backup': 4, 'delete': 6.

This table allows configuration of port-level intrusion detection.

The group ID of the port being referenced. Groups are numbered in top-down order, with the top group being group 1. Attempts to reference nonexistent units are rejected with an error-status of noSuchName(2).

The port ID of the port being referenced. Attempts to reference nonexistent ports are rejected with an error-status of noSuchName(2).

The authorized MAC address for this port. This address may be configured through auto-learning if securityAutoLearnAction is set to active(2). Otherwise, the authorized MAC address may be configured by a SetRequest on this object. SNMP SetRequests are rejected unless securityAutoLearnAction is set to inactive(1).

Selects the auto-learning function for the port. Setting this object to inactive(1) disables auto-learning; the user must set securityAddr in order to specify the authorized MAC address. Setting this object to active(2) enables auto-learning of the port's authorized MAC address. The agent first sets the authorized MAC address to 0, then learns the source address of the first error-free frame received by the port. The newly-learned authorized address is reflected in securityAddr, and the status of this object changes to learned(3). The value learned(3) is read-only. Attempts to set this object to learned(3) are rejected with an error-status of badValue(3). Enumeration: 'active': 2, 'learned': 3, 'inactive': 1.

Setting this object to warningAndDisable(2) enables intrusion detection on the port. When an intruder is detected, a RFC2108 rptrInfoHealth trap is transmitted and the port is disabled. An intruder is detected only after it transmits a packet. A passive (non-transmitting) intruder cannot be detected. Setting this object to inactive(1) disables intrusion detection for the port. Enumeration: 'warningAndDisable': 2, 'inactive': 1.