DECHUB900-HUBMGR-MIB-V3-0: View SNMP OID List / Download MIB

VENDOR: DEC


 Home MIB: DECHUB900-HUBMGR-MIB-V3-0
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 dec 1.3.6.1.4.1.36
       ema 1.3.6.1.4.1.36.2
           decMIBextension 1.3.6.1.4.1.36.2.18
                 decHub900 1.3.6.1.4.1.36.2.18.11
                       mgmtAgent 1.3.6.1.4.1.36.2.18.11.1
                           mgmtAgentVersion2 1.3.6.1.4.1.36.2.18.11.1.2
                               mamPrivate 1.3.6.1.4.1.36.2.18.11.1.2.1
                                   eventLogger 1.3.6.1.4.1.36.2.18.11.1.2.1.1
                                       eventLogTotalEvents 1.3.6.1.4.1.36.2.18.11.1.2.1.1.1 counter read-only
The total number of events in the eventLogTable.
                                       eventLogTable 1.3.6.1.4.1.36.2.18.11.1.2.1.1.2 no-access
A list of eventLogEntry.
                                           eventLogEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1 no-access
A list of information describing 'interesting events' which have occurred in the hub or stack.
                                               eventLogIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.1 integer read-only
An index into the eventLogTable. This index begins at one and increments by one each time an event is logged. Older entries may be deleted to make room to newer entries. An eventLogTable of size 7 might look like this: ._____.____.___________.____________________________. |Index|Slot| TimeStamp | Description | |_____|____|___________|____________________________| | 12 | 2 | 2357890 | Port 3 auto-partitioned. | |_____|____|___________|____________________________| | 13 | 4 | 2358900 | Broadcast storm on port 4. | |_____|____|___________|____________________________| | 14 | 2 | 2364220 | Port 3 auto-partitioned. | |_____|____|___________|____________________________| | 15 | 5 | 2369030 | FDDI ring trace received. | |_____|____|___________|____________________________| | 16 | 9 | 2484560 | Stack configuration change.| |_____|____|___________|____________________________| | 17 | 4 | 2504560 | Broadcast storm on port 1. | |_____|____|___________|____________________________| | 18 | 9 | 2600060 | Slot 5 firmware upgraded. | ._____.____.___________.____________________________.
                                               eventLogSlot 1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.2 integer read-only
The slot number of the module reporting the event.
                                               eventLogTimeStamp 1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.3 timeticks read-only
The time at which the event was logged. This is the Hub Manager's notion of sysUpTime, not the module's.
                                               eventLogDescription 1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.4 octet string read-only
A textual description of the event.
                                   rmonHub 1.3.6.1.4.1.36.2.18.11.1.2.1.2
                                       hubAlarm 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1
                                           hubAlarmTable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1 no-access
A list of alarm entries.
                                               hubAlarmEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1 no-access
A list of parameters that set up periodic checking of alarm conditions. For example, an instance of the hubAlarmValue object might be named hubAlarmValue.4.8 for the eighth alarm table entry for hubAlarmValue pertaining to the module occupying slot 4.
                                                   hubAlarmSlotNumber 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.1 integer read-only
The number of the slot in which the module to be monitored occupies in the hub chassis or the module's position in a stack.
                                                   hubAlarmIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.2 integer read-only
An index that uniquely identifies an entry in the alarm table for a given slot.
                                                   hubAlarmInterval 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.3 integer read-write
The interval, in seconds, over which the data is sampled and compared with the rising and falling thresholds. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1).
                                                   hubAlarmVariable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.4 object identifier read-write
The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (INTEGER, Counter, Gauge, or TimeTicks) may be sampled. During a set operation, any legally formed Object Identifier is accepted. Once the entry is marked valid, a sample will be taken after the first poll period. If the device (specified by hubAlarmSlotNumber) responds correctly to the first poll, the hubAlarmState for the entry is set to 'active(1)'. Otherwise it is set to 'inactive(2)'. hubAlarmVariables must be unique among slots. For example, you can monitor object X on slot 3 and 5, but you can't monitor object X using two alarmTableEntries on slot 3. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1).
                                                   hubAlarmSampleType 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.5 integer read-write
The method of sampling the selected variable and calculating the value to be compared against the thresholds. If the value of this object is absoluteValue(1), the value of the selected variable is compared directly with the thresholds at the end of the sampling interval. If the value of this object is deltaValue(2), the value of the selected variable at the last sample will be subtracted from the current value, and the difference compared with the thresholds. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1). Enumeration: 'absoluteValue': 1, 'deltaValue': 2.
                                                   hubAlarmValue 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.6 integer read-only
The value of the statistic during the last sampling period. For example, if the sample type is deltaValue, this value is the difference between the samples at the beginning and end of the period. If the sample type is absoluteValue, this value is the sampled value at the end of the period. This is the value that is compared with the rising and falling thresholds. The value during the current sampling period is not made available until the period is completed and will remain available until the next period completes.
                                                   hubAlarmStartupAlarm 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.7 integer read-write
The alarm that may be sent when this entry is first set to valid. If the first sample after this entry becomes valid is greater than or equal to the risingThreshold and hubAlarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3), then a single rising alarm will be generated. If the first sample after this entry becomes valid is less than or equal to the fallingThreshold and hubAlarmStartupAlarm is equal to fallingAlarm(2) or risingOrFalling Alarm(3), then a single falling alarm will be generated. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1). Enumeration: 'fallingAlarm': 2, 'risingAlarm': 1, 'risingOrFallingAlarm': 3.
                                                   hubAlarmRisingThreshold 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.8 integer read-write
A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is greater than or equal to this threshold and the associated hubAlarmStartupAlarm is equal to risingAlarm(1) or risingOrFallingAlarm(3). After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the hubAlarmFallingThreshold. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1).
                                                   hubAlarmFallingThreshold 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.9 integer read-write
A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes valid is less than or equal to this threshold and the associated hubAlarmStartupAlarm is equal to fallingAlarm(2) or risingOrFallingAlarm(3). After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the hubAlarmRisingThreshold. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1).
                                                   hubAlarmRisingEventIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.10 integer read-write
The index of the eventEntry that is used when a rising threshold is crossed. The hubEventEntry identified by a particular value of this index is the same as identified by the same value of the hubEvent Index object. If there is no corresponding entry in the hubEvent Table, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1).
                                                   hubAlarmFallingEventIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.11 integer read-write
The index of the hubEventEntry that is used when a falling threshold is crossed. The hubEventEntry identified by a particular value of this index is the same as identified by the same value of the hub EventIndex object. If there is no corresponding entry in the hub EventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid event index. This object may not be modified if the associated hubAlarmStatus object is equal to valid(1).
                                                   hubAlarmOwner 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.12 displaystring read-write
The entity that configured this entry and is therefore using the resources assigned to it.
                                                   hubAlarmState 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.13 integer read-only
The state of this alarm entry. Entries in the Alarm Table are marked as 'inactive' when the module to which they refer: - is removed or becomes 'asleep', - returns an error in response to a poll request, or - ignores a request message. Inactive entries are still polled and are reactivated when: - the module becomes 'awake', and - whenever the module correctly returns a polled value. Entries in the Alarm and Event Tables are deleted either by a network manager, or whenever a stack or hub reconfiguration occurs such that a module of a different type now occupies the slot being polled. (Modules are determined to be 'of a different type' when their sysObjectIDs differ.) Enumeration: 'active': 1, 'inactive': 2.
                                                   hubAlarmStatus 1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.14 integer read-write
The status of this alarm entry. (Refer to the RFC 1757 definition of 'EntryStatus.) Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.
                                       hubEvent 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2
                                           hubEventTable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1 no-access
A list of events to be generated.
                                               hubEventEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1 no-access
A set of parameters that describe an event to be generated when certain conditions are met. As an example, an instance of the hubEventLastTimeSent object might be named hubEventLastTimeSent.6
                                                   hubEventIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.1 integer read-only
An index that uniquely identifies an entry in the event table. Each such entry defines one event that is to be generated when the appropriate conditions occur.
                                                   hubEventDescription 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.2 displaystring read-write
A comment describing this hubEvent entry.
                                                   hubEventType 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.3 integer read-write
The type of notification that the probe will make about this event. In the case of log, an entry is made in the log table for each event. In the case of snmp-trap, an SNMP trap is sent to one or more management stations. Enumeration: 'snmp-trap': 3, 'none': 1, 'log': 2, 'log-and-trap': 4.
                                                   hubEventCommunity 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.4 octet string read-write
If an SNMP trap is to be sent, it will be sent to the SNMP community specified by this octet string.
                                                   hubEventLastTimeSent 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.5 timeticks read-only
The value of sysUpTime at the time this event entry last generated an event. If this entry has not generated any events, this value is zero.
                                                   hubEventOwner 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.6 displaystring read-write
The entity that configured this entry and is therefore using the resources assigned to it.
                                                   hubEventStatus 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.7 integer read-write
The status of this event entry. If this object is not equal to valid(1), all associated log entries shall be deleted by the agent. (Refer to the RFC 1757 definition of 'EntryStatus.) Enumeration: 'underCreation': 3, 'createRequest': 2, 'valid': 1, 'invalid': 4.
                                           hubLogTable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2 no-access
A list of events that have been logged.
                                               hubLogEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1 no-access
A set of data describing an event that has been logged. For example, an instance of the hubLogDescription object might be named hubLogDescription.6.47
                                                   hubLogSlotNumber 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.1 integer read-only
                                                   hubLogEventIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.2 integer read-only
The event entry that generated this log entry. The log identified by a particular value of this index is associated with the same eventEntry as identified by the same value of eventIndex.
                                                   hubLogIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.3 integer read-only
An index that uniquely identifies an entry in the log table amongst those generated by the same eventEntries. These indexes are assigned beginning with 1 and increase by one with each new log entry. The association between values of hubLogIndex and hubLog Entries is fixed for the lifetime of each hubLogEntry. The agent may choose to delete the oldest instances of hubLogEntry as required because of lack of memory. It is an implementation-specific matter as to when this deletion may occur.
                                                   hubLogTime 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.4 timeticks read-only
The value of sysUpTime when this log entry was created.
                                                   hubLogDescription 1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.5 displaystring read-only
An implementation dependent description of the event that activated this log entry.
                                       hubEtherCapabilities 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3
                                           hubEtherCapabilitiesTable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1 no-access
A list of Ethernet statistic capability entries.
                                               hubEtherCapabilitiesEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1 no-access
An entry which describes the Ethernet monitoring capabilities or an interface or internal LAN.
                                                   hubEtherCapabilitiesSlotNumber 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.1 integer read-only
The number of the slot in which the device resides.
                                                   hubEtherCapabilitiesIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.2 integer read-only
The number of the interface, port, or LAN described by this entry. Where possible, this index should match front bezel numbering. (And front-bezel numbering should match the MIB-II ifIndex of interface types. Where possible, this index should match pcomConTable indices for internal LAN types.
                                                   hubEtherCapabilitiesLanType 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.3 integer read-only
This enumeration describes interface, port, or LAN. The interface type is for any interface which can be described in the MIB-II interface table. Examples of interfaces include switch ports, SLIP/PPP ports, and repeater MACs. The portGroup type is for a group of ports which can be described in the IETF repeater MIB (rfc1368). The portGoup type is for LANs configured to connect the front- bezel ports of repeaters. These internal LANs should be described in the pcomConTable. Indices should match the indices in the pcomConTable. The port type is for a single port which can be described by the IETF repeater MIB. Enumeration: 'interface': 1, 'port': 3, 'portGroup': 2.
                                                   hubEtherCapabilitiesLanSpeed 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.4 integer read-only
The speed at which the Ethernet operates, in mega-bits per second.
                                                   hubEtherCapabilitiesTrueCollisions 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.5 integer read-only
The value of this object indicates if the etherStatsCollisions counter is accurately reported. The etherStatsCollisions counter is problematic in that it is defined as the total number of collisions on the segment, while many implementations can only detect the number of collisions involved with transmissions from the interface or port. Enumeration: 'false': 2, 'true': 1.
                                                   hubEtherCapabilitiesState 1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.6 integer read-write
Setting hubEtherCapabilitiesState to 'active' has the side-effect of: o creating an entry in the hubEtherStatsTable, and o creating two entries in the hubHistoryControlTable. Conversely, setting this object to inactive causes entries in the hubEtherStatsTable and hubHistoryControlTable to be deleted. Enumeration: 'active': 1, 'inactive': 2.
                                       hubStatistics 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4
                                           hubEtherStatsTable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1 no-access
A list of Ethernet statistics entries.
                                               hubEtherStatsEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1 no-access
A collection of statistics kept for a particular Ethernet interface. As an example, an instance of the hubEtherStatsPkts object might be named hubEtherStatsPkts.1
                                                   hubEtherStatsSlotNumber 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.1 integer read-only
The number of the slot in which the device whose statistics are being gathered resides. This index corresponds to hubEtherCapabilitiesSlotNumber.
                                                   hubEtherStatsIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.2 integer read-only
An index into the hubEtherStatsTable. This index corresponds to hubEtherCapabilitiesIndex.
                                                   hubEtherStatsDropEvents 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.3 counter read-only
The total number of events in which packets were dropped by the device due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected.
                                                   hubEtherStatsOctets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.4 counter read-only
The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).
                                                   hubEtherStatsPkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.5 counter read-only
The total number of packets (including bad packets, broadcast packets, and multicast packets) received.
                                                   hubEtherStatsBroadcastPkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.6 counter read-only
The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast packets.
                                                   hubEtherStatsMulticastPkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.7 counter read-only
The total number of good packets received that were directed to a multicast address. Note that this number does not include packets directed to the broadcast address.
                                                   hubEtherStatsCRCAlignErrors 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.8 counter read-only
The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 octets, inclusive, but but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
                                                   hubEtherStatsUndersizePkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.9 counter read-only
The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and were otherwise well formed.
                                                   hubEtherStatsOversizePkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.10 counter read-only
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed.
                                                   hubEtherStatsFragments 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.11 counter read-only
The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that it is entirely normal for hubEtherStatsFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.
                                                   hubEtherStatsJabbers 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.12 counter read-only
The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
                                                   hubEtherStatsCollisions 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.13 counter read-only
The best estimate of the total number of collisions on this Ethernet segment.
                                                   hubEtherStatsPkts64Octets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.14 counter read-only
The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets).
                                                   hubEtherStatsPkts65to127Octets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.15 counter read-only
The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets).
                                                   hubEtherStatsPkts128to255Octets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.16 counter read-only
The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets).
                                                   hubEtherStatsPkts256to511Octets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.17 counter read-only
The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets).
                                                   hubEtherStatsPkts512to1023Octets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.18 counter read-only
The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets).
                                                   hubEtherStatsPkts1024to1518Octets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.19 counter read-only
The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets).
                                       hubHistory 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5
                                           hubHistoryControlFastPollInterval 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.1 integer read-write
When hubEtherCapabilitiesState is set to active, two hubHistoryControlEntry are created; a fast poll entry with a default rate of 30 seconds, and a slot poll entry with a default rate of 1800 seconds (30 minutes). This object controls the amount of time, in seconds, between polls of the fast poll entry in the hubHistoryControlTable.
                                           hubHistoryControlSlowPollInterval 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.2 integer read-write
When hubEtherCapabilitiesState is set to active, two hubHistoryControlEntry are created; a fast poll entry with a default rate of 30 seconds, and a slot poll entry with a default rate of 1800 seconds (30 minutes). This object controls the amount of time, in seconds, between polls of the slow poll entry in the hubHistoryControlTable.
                                           hubHistoryControlTable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3 no-access
A list of history control entries.
                                               hubHistoryControlEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1 no-access
A list of parameters that set up a periodic sampling of statistics. As an example, an instance of the hubHistoryControlInterval object might be named hubHistoryControlInterval.2
                                                   hubHistoryControlSlotNumber 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.1 integer read-only
The number of the slot in which the device's whose Ethernet history is being gathered resides.
                                                   hubHistoryControlIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.2 integer read-only
                                                   hubHistoryControlHistoryIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.3 integer read-only
An index which uniquely identifies instances of both this table and the hubHistoryTable.
                                                   hubHistoryControlBuckets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.4 integer read-only
The number of sampling intervals over which data shall be saved in hubEtherHistoryTable.
                                                   hubHistoryControlInterval 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.5 integer read-only
The interval in seconds over which the data is sampled for each bucket in the part of the media-specific table associated with this hubHistoryControlEntry.
                                           hubEtherHistoryTable 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4 no-access
A list of Ethernet history entries.
                                               hubEtherHistoryEntry 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1 no-access
An historical sample of Ethernet statistics on a particular Ethernet interface. This sample is associated with the hubHistoryControlEntry which set up the parameters for a regular collection of these samples. As an example, an instance of the hubEtherHistoryPkts object might be named hubEtherHistoryPkts.2.89
                                                   hubEtherHistoryIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.1 integer read-only
                                                   hubEtherHistorySampleIndex 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.2 integer read-only
An index that uniquely identifies the particular sample this entry represents among all samples associated with the same hubHistoryControlEntry. This index starts at 1 and increases by one as each new sample is taken.
                                                   hubEtherHistoryIntervalStart 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.3 timeticks read-only
The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
                                                   hubEtherHistoryDropEvents 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.4 counter read-only
The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
                                                   hubEtherHistoryOctets 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.5 counter read-only
The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including FCS octets).
                                                   hubEtherHistoryPkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.6 counter read-only
The number of packets (including bad packets) received during this sampling interval.
                                                   hubEtherHistoryBroadcastPkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.7 counter read-only
The number of good packets received during this sampling interval that were directed to the broadcast address.
                                                   hubEtherHistoryMulticastPkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.8 counter read-only
The number of good packets received during this sampling interval that were directed to a multicast address. Note that this number does not include packets addressed to the broadcast address.
                                                   hubEtherHistoryCRCAlignErrors 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.9 counter read-only
The number of packets received during this sampling interval that had a length (excluding framing bits but including FCS octets) between 64 and 1518 octets, inclusive, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
                                                   hubEtherHistoryUndersizePkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.10 counter read-only
The number of packets received during this sampling interval that were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed.
                                                   hubEtherHistoryOversizePkts 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.11 counter read-only
The number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets) but were otherwise well formed.
                                                   hubEtherHistoryFragments 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.12 counter read-only
The total number of packets received during this sampling interval that were less than 64 octets in length (excluding framing bits but including FCS octets) had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Note that it is entirely normal for hubEtherHistoryFragments to increment. This is because it counts both runts (which are normal occurrences due to collisions) and noise hits.
                                                   hubEtherHistoryJabbers 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.13 counter read-only
The number of packets received during this sampling interval that were longer than 1518 octets (excluding framing bits but including FCS octets), and had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non- integral number of octets (Alignment Error). Note that this definition of jabber is different than the definition in IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150 ms.
                                                   hubEtherHistoryCollisions 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.14 counter read-only
The best estimate of the total number of collisions on this Ethernet segment during this sampling interval.
                                                   hubEtherHistoryUtilization 1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.15 integer read-only
The best estimate of the mean physical layer network utilization on this interface during this sampling interval, in hundredths of a percent.
                                     hubRisingAlarm 1.3.6.1.4.1.36.2.18.11.1.2.10.1
The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps. The enterprise Object Identifier for this trap is: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1). dec(36).ema(2).decMIBextension(18).decHub900(11). mgmtAgent(1).mgmtAgentVersion2(2).mamPrivate(2)
                                     hubFallingAlarm 1.3.6.1.4.1.36.2.18.11.1.2.10.2
The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps. The enterprise Object Identifier for this trap is: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1). dec(36).ema(2).decMIBextension(18).decHub900(11). mgmtAgent(1).mgmtAgentVersion2(2).mamPrivate(2)