DLINKES-IF-COUNTER-MIB

Counter64 (0..18446744073709551615)

The number of interface link change events.

Unsigned32 · packets per second

This object indicates the current rate of received frames on the interface. This object is deprecated in favour of esIfCounterRateStatsRxPkts.

Unsigned32 · packets per second

This object indicates the current rate of transmitted frames on the interface. This object is deprecated in favour of esIfCounterRateStatsTxPkts.

Unsigned32 (0..100) · percentage

This object indicates the percentage of the utilization on the interface.

Counter64 (0..18446744073709551615)

The number of packets received on the interface. This object is a 64-bit version of etherStatsPkts. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets). This object is a 64-bit version of etherStatsPkts64Octets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

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). This object is a 64-bit version of etherStatsPkts65to127Octets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

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). This object is a 64-bit version of etherStatsPkts128to255Octets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

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). This object is a 64-bit version of etherStatsPkts256to511Octets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

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. This object is a 64-bit version of etherStatsPkts512to1023Octets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

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). This object is a 64-bit version of etherStatsPkts1024to1518Octets. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of good VLAN packets received that were between 1519 and 1522 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) received that were between 1519 and 2047 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) received that were between 2048 and 4095 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) received that were between 4096 and 9216 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets discarded while input buffer full.

Counter64 (0..18446744073709551615)

The total number of received packets denied by ACLs.

Counter64 (0..18446744073709551615)

The total number of received multicast packet that is discarded.

Counter64 (0..18446744073709551615)

The total number of packets discarded by VLAN ingress checking.

Counter64 (0..18446744073709551615)

The total number of IPv6 packets dropped by routing process.

Counter64 (0..18446744073709551615)

The total number of packets discarded when ingress port is not in forwarding state.

Counter64 (0..18446744073709551615)

The total number of packets discarded by receiving policy (e.g. the source or destination MAC is not allowed, rate limit, etc.)

Counter64 (0..18446744073709551615)

The total number of packets discarded by frames received, which exceeds Maximum Frame in length and contains a valid or invalid FCS.

Counter64 (0..18446744073709551615)

The total number of packets dropped due to no destination port can be forwarded to.

Counter64 (0..18446744073709551615)

The total number of packets discarded by port ingress bandwidth control.

Counter64 (0..18446744073709551615)

The number of packets transmitted on the interface. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were 64 octets in length (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of good VLAN packets transmitted that were between 1519 and 1522 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 1519 and 2047 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 2048 and 4095 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets (including bad packets) transmitted that were between 4096 and 9216 octets in length inclusive (excluding framing bits but including FCS octets). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

Counter64 (0..18446744073709551615)

The total number of packets to be transmitted that are not pass the FCS check.

Counter64 (0..18446744073709551615)

Incremented for packets dropped when egress port is not in forwarding state.

Counter64 (0..18446744073709551615)

Incremented for each packet dropped due to Head Of Line blocking.

Counter64 (0..18446744073709551615)

Incremented for each packet dropped due to Head of Line blocking on the egress CoS queue 0.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 1.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 2.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 3.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 4.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 5.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 6.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 7.

INTEGER1 = rx2 = tx3 = both · Integer32

This object indicates the VLAN counter is counting for received and/or transmitted traffic.

InterfaceIndexOrZeroThis textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced. (0..2147483647) · Integer32 · hint d

This object indicates the counting entry is VLAN-based or port-based. A value of physical interface's index for this object means the counting entry port-based on the specified physical port interface. A value of zero for this object means that the counting entry is VLAN-based.

INTEGER1 = broadcast2 = multicast3 = unicast4 = any · Integer32

This object indicates the type of packet.

Counter64 (0..18446744073709551615)

This object indicates the statistics by packets.

Counter64 (0..18446744073709551615)

This object indicates the statistics by bytes.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

This object indicates the status of this entry.

Counter64 (0..18446744073709551615) · packets per second

This object indicates packets receiving rate.

Counter64 (0..18446744073709551615) · bits per second

This object indicates bits receiving rate.

Counter64 (0..18446744073709551615) · packets per second

This object indicates packets transmitting rate.

Counter64 (0..18446744073709551615) · bits per second

This object indicates bits transmitting rate.

INTEGER1 = fifteen-minute2 = one-day · Integer32

This object indicates the time slot for counters.

INTEGER (1..10) · Integer32

This object indicates the type of time slot for counters. e.g. when swHistoryCntTime is equal to fifteen-minute(1): 1: indicates slot 1(relate to the previous 0 ~ 15 minutes) 2: indicates slot 2(relate to the previous 15 ~ 30 minutes) 3: indicates slot 3(relate to the previous 30 ~ 45 minutes) ... n: indicates slot n(relate to the previous (n-1)*15 ~ n*15 minutes) when swHistoryCntTime is equal to one-day(2): 1: indicates slot 1(relate to the previous 0 ~ 24 hours) 2: indicates slot 2(relate to the previous 24 ~ 48 hours) 3: indicates slot 3(relate to the previous 48 ~ 72 hours) ... m: indicates slot m(relate to the previous (m-1)*24 ~ m*24 hours) For each case, one or more historical statistic entries can be supported, the maximum slot number is project depended.

Counter64 (0..18446744073709551615)

The historical number of packets received on the interface during a special time range. This object is a 64-bit version of etherStatsPkts.

Counter64 (0..18446744073709551615)

The historical number of Bytes received on the interface during a special time range. This object is a 64-bit version of etherStatsPkts.

Counter64 (0..18446744073709551615)

The historical number of unicast packets received on the interface during a special time range. This object is a 64-bit version of etherStatsPkts.

Counter64 (0..18446744073709551615)

The historical number of Multicast packets received on the interface during a special time range. This object is a 64-bit version of etherStatsPkts.

Counter64 (0..18446744073709551615)

The historical number of Broadcast packets received on the interface during a special time range. This object is a 64-bit version of etherStatsPkts.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including FCS octets) during a special time range. This object is a 64-bit version of etherStatsPkts64Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range. This object is a 64-bit version of etherStatsPkts65to127Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range. This object is a 64-bit version of etherStatsPkts128to255Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range. This object is a 64-bit version of etherStatsPkts256to511Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range. This object is a 64-bit version of etherStatsPkts512to1023Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range. This object is a 64-bit version of etherStatsPkts1024to1518Octets.

Counter64 (0..18446744073709551615)

The total historical number of good VLAN packets received that were between 1519 and 1522 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 1519 and 2047 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 2048 and 4095 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) received that were between 4096 and 9216 octets in length inclusive (excluding framing bits but including FCS octets) during a special time range.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the start time of the specified slot.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the end time of the specified slot.

Counter64 (0..18446744073709551615)

This object indicates receiving total historical number of CRC(FCS)Error packets during a specified historical time range. The CRC Error packets that are an integral number of octets in length but do not pass the FCS check.This count does not include frames received with frame-too-long or frame-too-short error.

Counter64 (0..18446744073709551615)

The receiving total historical number of Undersize packets during a specified historical time range.The Undersize packets were less than 64 octets long (excluding framing bits but including FCS octets) and were otherwise well formed.

Counter64 (0..18446744073709551615)

The receiving total historical number of Oversize packets during a specified historical time range.The Oversize packets were longer than 1518 octets (excluding framing bits but including FCS octets) but were otherwise well formed.

Counter64 (0..18446744073709551615)

The receiving total historical number of Fragment packets during a specified historical time range.The Fragment packets 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)

Counter64 (0..18446744073709551615)

The receiving total historical number of Jabber packets during a specified historical time range.The Jabber packets 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).

Counter64 (0..18446744073709551615)

The receiving total historical number of times where there was an invalid data symbol when a valid carrier was present during a specified historical time range.

Counter64 (0..18446744073709551615)

The receiving total historical number of times where the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface during a specified historical time range.

Counter64 (0..18446744073709551615)

The receiving total historical number of Alignment Errors packets during a specified historical time range.The Alignment Errors packets that are not an integral number of octets in length and do not pass the FCS check.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the start time of the specified slot.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the end time of the specified slot.

Counter64 (0..18446744073709551615)

The total historical number of packets discarded while input buffer full during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of received packets denied by ACLs during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of received multicast packet that is discarded during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets discarded by VLAN ingress checking during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of IPv6 packets dropped by routing process during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets discarded when ingress port is not in forwarding state during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets discarded by receiving policy (e.g. the source or destination MAC is not allowed, rate limit, etc.) during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets discarded by frames received, which exceeds Maximum Frame in length and contains a valid or invalid FCS during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets dropped due to no destination port can be forwarded to during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets discarded by port ingress bandwidth control during a specified historical time range.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the start time of the specified slot.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the end time of the specified slot.

Counter64 (0..18446744073709551615)

The historical number of packets transmitted on the interface during a specified historical time range. This object is a 64-bit version of etherStatsPkts.

Counter64 (0..18446744073709551615)

The historical number of Bytes transmitted on the interface during a specified historical time range. This object is a 64-bit version of etherStatsPkts .

Counter64 (0..18446744073709551615)

The historical number of unicast packets transmitted on the interface during a specified historical time range. This object is a 64-bit version of etherStatsPkts .

Counter64 (0..18446744073709551615)

The historical number of Multicast packets transmitted on the interface during a specified historical time range. This object is a 64-bit version of etherStatsPkts .

Counter64 (0..18446744073709551615)

The historical number of Broadcast packets transmitted on the interface during a specified historical time range. This object is a 64-bit version of etherStatsPkts .

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were 64 octets in length (excluding framing bits but including FCS octets) during a specified historical time range. This object is a 64-bit version of etherStatsPkts64Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 65 and 127 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range. This object is a 64-bit version of etherStatsPkts65to127Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 128 and 255 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range. This object is a 64-bit version of etherStatsPkts128to255Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 256 and 511 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range. This object is a 64-bit version of etherStatsPkts256to511Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 512 and 1023 octets in length inclusive (excluding framing bits but including FCS octets during a specified historical time range. This object is a 64-bit version of etherStatsPkts512to1023Octets.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 1024 and 1518 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range. This object is a 64-bit version of etherStatsPkts1024to1518Octets.

Counter64 (0..18446744073709551615)

The total historical number of good VLAN packets transmitted that were between 1519 and 1522 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 1519 and 2047 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 2048 and 4095 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range.

Counter64 (0..18446744073709551615)

The total historical number of packets (including bad packets) transmitted that were between 4096 and 9216 octets in length inclusive (excluding framing bits but including FCS octets) during a specified historical time range.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the start time of the specified slot .

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the end time of the specified slot .

Counter64 (0..18446744073709551615)

The best estimate total number of total collision on this Ethernet segment during a specified historical time range.

Counter64 (0..18446744073709551615)

The transmitting total number of single deferral packets.

Counter64 (0..18446744073709551615)

The total number of times that a collision is detected on a particular interface later than one slotTime into the transmission of a packet during a specified historical time range.

Counter64 (0..18446744073709551615)

The total number of excessive collision for which transmission on a particular interface fails due to excessive collisions during a specified historical time range.

Counter64 (0..18446744073709551615)

The total number of frames that are successfully transmitted on a particular interface for which transmission is inhibited by exactly one collision during a specified historical time range.

Counter64 (0..18446744073709551615)

The total number of frames that are successfully transmitted on a particular interface for which transmission is inhibited by more than one collision during a specified historical time range.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the start time of the specified slot.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the end time of the specified slot.

Counter64 (0..18446744073709551615)

Incremented for packets dropped when egress port is not in forwarding state during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet dropped due to Head Of Line blocking during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet dropped due to Head of Line blocking on the egress CoS queue 0 during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 1 during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 2during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 3 during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 4 during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 5 during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 6 during a specified historical time range.

Counter64 (0..18446744073709551615)

Incremented for each packet drop due to Head of Line blocking on the egress CoS queue 7 during a specified historical time range.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the start time of the specified slot.

DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d

This object indicates the end time of the specified slot.