DECHUB900-HUBMGR-MIB-V3-0
Detailed view of the defined objects, syntax rules, and hierarchical paths.
111
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
111 total| Object Name |
|---|
dec OBJECT IDENTIFIER .1.3.6.1.4.1.36 |
RFC1155-SMI Unknown .1.3.6.1.4.1.36 |
ema OBJECT IDENTIFIER .1.3.6.1.4.1.36.2 |
decMIBextension OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18 |
decHub900 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11 |
mgmtAgent OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1 |
mgmtAgentVersion2 OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2 |
mamPrivate OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1 |
hubRisingAlarmThe 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) TRAP-TYPE .1.3.6.1.4.1.36.2.18.11.1.2.1.0.1 |
hubFallingAlarmThe 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) TRAP-TYPE .1.3.6.1.4.1.36.2.18.11.1.2.1.0.2 |
eventLogger OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.1 |
eventLogTotalEventsThe total number of events in the eventLogTable.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.1.1 |
eventLogTableA list of eventLogEntry. SEQUENCE OF EventLogEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.1.2 |
eventLogEntryA list of information describing 'interesting events' which
have occurred in the hub or stack. EventLogEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1 |
eventLogIndexAn 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. |
._____.____.___________.____________________________.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.1 |
eventLogSlotThe slot number of the module reporting the event.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.2 |
eventLogTimeStampThe time at which the event was logged. This is the
Hub Manager's notion of sysUpTime, not the module's.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.3 |
eventLogDescriptionA textual description of the event.ro OCTET STRING .1.3.6.1.4.1.36.2.18.11.1.2.1.1.2.1.4 |
rmonHub OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.2 |
hubAlarm OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1 |
hubAlarmTableA list of alarm entries. SEQUENCE OF HubAlarmEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1 |
hubAlarmEntryA 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. HubAlarmEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1 |
hubAlarmSlotNumberThe number of the slot in which the module to be monitored
occupies in the hub chassis or the module's position in
a stack.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.1 |
hubAlarmIndexAn index that uniquely identifies an entry in the alarm table
for a given slot.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.2 |
hubAlarmIntervalThe 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).rw INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.3 |
hubAlarmVariableThe 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).rw OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.4 |
hubAlarmSampleTypeThe 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).rw Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.5 |
hubAlarmValueThe 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.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.6 |
hubAlarmStartupAlarmThe 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).rw Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.7 |
hubAlarmRisingThresholdA 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).rw INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.8 |
hubAlarmFallingThresholdA 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).rw INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.9 |
hubAlarmRisingEventIndexThe 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).rw INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.10 |
hubAlarmFallingEventIndexThe 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).rw INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.11 |
hubAlarmOwnerThe entity that configured this entry and is therefore using the
resources assigned to it.rw DisplayString .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.12 |
hubAlarmStateThe 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.)ro Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.13 |
hubAlarmStatusThe status of this alarm entry. (Refer to the RFC 1757 definition
of 'EntryStatus.)rw Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.1.1.1.14 |
hubEvent OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2 |
hubEventTableA list of events to be generated. SEQUENCE OF HubEventEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1 |
hubEventEntryA 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 HubEventEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1 |
hubEventIndexAn 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.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.1 |
hubEventDescriptionA comment describing this hubEvent entry.rw DisplayString .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.2 |
hubEventTypeThe 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.rw Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.3 |
hubEventCommunityIf an SNMP trap is to be sent, it will be sent to the SNMP community
specified by this octet string.rw OCTET STRING .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.4 |
hubEventLastTimeSentThe 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.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.5 |
hubEventOwnerThe entity that configured this entry and is therefore using the
resources assigned to it.rw DisplayString .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.6 |
hubEventStatusThe 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.)rw Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.1.1.7 |
hubLogTableA list of events that have been logged. SEQUENCE OF HubLogEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2 |
hubLogEntryA set of data describing an event that has been logged. For
example, an instance of the hubLogDescription object might be named
hubLogDescription.6.47 HubLogEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1 |
hubLogSlotNumberro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.1 |
hubLogEventIndexThe 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.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.2 |
hubLogIndexAn 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.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.3 |
hubLogTimeThe value of sysUpTime when this log entry was created.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.4 |
hubLogDescriptionAn implementation dependent description of the event that activated
this log entry.ro DisplayString .1.3.6.1.4.1.36.2.18.11.1.2.1.2.2.2.1.5 |
hubEtherCapabilities OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3 |
hubEtherCapabilitiesTableA list of Ethernet statistic capability entries. SEQUENCE OF HubEtherCapabilitiesEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1 |
hubEtherCapabilitiesEntryAn entry which describes the Ethernet monitoring capabilities
or an interface or internal LAN. HubEtherCapabilitiesEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1 |
hubEtherCapabilitiesSlotNumberThe number of the slot in which the device resides.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.1 |
hubEtherCapabilitiesIndexThe 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.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.2 |
hubEtherCapabilitiesLanTypeThis 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.ro Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.3 |
hubEtherCapabilitiesLanSpeedThe speed at which the Ethernet operates, in mega-bits per second.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.4 |
hubEtherCapabilitiesTrueCollisionsThe 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.ro Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.5 |
hubEtherCapabilitiesStateSetting 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.rw Enumeration .1.3.6.1.4.1.36.2.18.11.1.2.1.2.3.1.1.6 |
hubStatistics OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4 |
hubEtherStatsTableA list of Ethernet statistics entries. SEQUENCE OF HubEtherStatsEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1 |
hubEtherStatsEntryA collection of statistics kept for a particular Ethernet interface.
As an example, an instance of the hubEtherStatsPkts object might be
named hubEtherStatsPkts.1 HubEtherStatsEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1 |
hubEtherStatsSlotNumberThe number of the slot in which the device whose statistics
are being gathered resides. This index corresponds to
hubEtherCapabilitiesSlotNumber.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.1 |
hubEtherStatsIndexAn index into the hubEtherStatsTable. This index corresponds to
hubEtherCapabilitiesIndex.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.2 |
hubEtherStatsDropEventsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.3 |
hubEtherStatsOctetsThe total number of octets of data (including those in bad packets)
received on the network (excluding framing bits but including FCS
octets).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.4 |
hubEtherStatsPktsThe total number of packets (including bad packets, broadcast
packets, and multicast packets) received.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.5 |
hubEtherStatsBroadcastPktsThe total number of good packets received that were directed to
the broadcast address. Note that this does not include multicast
packets.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.6 |
hubEtherStatsMulticastPktsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.7 |
hubEtherStatsCRCAlignErrorsThe 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).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.8 |
hubEtherStatsUndersizePktsThe total number of packets received that were less than 64 octets
long (excluding framing bits, but including FCS octets) and were
otherwise well formed.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.9 |
hubEtherStatsOversizePktsThe total number of packets received that were longer than 1518
octets (excluding framing bits, but including FCS octets) and were
otherwise well formed.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.10 |
hubEtherStatsFragmentsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.11 |
hubEtherStatsJabbersThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.12 |
hubEtherStatsCollisionsThe best estimate of the total number of collisions on this
Ethernet segment.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.13 |
hubEtherStatsPkts64OctetsThe total number of packets (including bad packets) received that
were 64 octets in length (excluding framing bits but including FCS
octets).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.14 |
hubEtherStatsPkts65to127OctetsThe 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).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.15 |
hubEtherStatsPkts128to255OctetsThe 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).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.16 |
hubEtherStatsPkts256to511OctetsThe 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).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.17 |
hubEtherStatsPkts512to1023OctetsThe 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).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.18 |
hubEtherStatsPkts1024to1518OctetsThe 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).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.4.1.1.19 |
hubHistory OBJECT IDENTIFIER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5 |
hubHistoryControlFastPollIntervalWhen 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.rw INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.1 |
hubHistoryControlSlowPollIntervalWhen 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.rw INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.2 |
hubHistoryControlTableA list of history control entries. SEQUENCE OF HubHistoryControlEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3 |
hubHistoryControlEntryA 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 HubHistoryControlEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1 |
hubHistoryControlSlotNumberThe number of the slot in which the device's whose Ethernet history
is being gathered resides.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.1 |
hubHistoryControlIndexro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.2 |
hubHistoryControlHistoryIndexAn index which uniquely identifies instances of both this
table and the hubHistoryTable.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.3 |
hubHistoryControlBucketsThe number of sampling intervals over which data shall be saved in
hubEtherHistoryTable.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.4 |
hubHistoryControlIntervalThe interval in seconds over which the data is sampled for each
bucket in the part of the media-specific table associated with this
hubHistoryControlEntry.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.3.1.5 |
hubEtherHistoryTableA list of Ethernet history entries. SEQUENCE OF HubEtherHistoryEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4 |
hubEtherHistoryEntryAn 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 HubEtherHistoryEntry .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1 |
hubEtherHistoryIndexro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.1 |
hubEtherHistorySampleIndexAn 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.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.2 |
hubEtherHistoryIntervalStartThe 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.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.3 |
hubEtherHistoryDropEventsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.4 |
hubEtherHistoryOctetsThe total number of octets of data (including those in bad packets)
received on the network (excluding framing bits but including FCS
octets).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.5 |
hubEtherHistoryPktsThe number of packets (including bad packets) received during this
sampling interval.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.6 |
hubEtherHistoryBroadcastPktsThe number of good packets received during this sampling interval
that were directed to the broadcast address.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.7 |
hubEtherHistoryMulticastPktsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.8 |
hubEtherHistoryCRCAlignErrorsThe 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).ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.9 |
hubEtherHistoryUndersizePktsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.10 |
hubEtherHistoryOversizePktsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.11 |
hubEtherHistoryFragmentsThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.12 |
hubEtherHistoryJabbersThe 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.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.13 |
hubEtherHistoryCollisionsThe best estimate of the total number of collisions on this Ethernet
segment during this sampling interval.ro Counter .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.14 |
hubEtherHistoryUtilizationThe best estimate of the mean physical layer network utilization
on this interface during this sampling interval, in hundredths of
a percent.ro INTEGER .1.3.6.1.4.1.36.2.18.11.1.2.1.2.5.4.1.15 |