OID reference

ifClearStats

1.3.6.1.4.1.1978.2.18.2.2.1.29

Description

Full description and source information

Identification

Identifier and names

Parent: 1.3.6.1.4.1.1978.2.18.2.2.1 (ifEntry)
Node code: 29
Node name: ifClearStats
Category: SNMP management object
Numeric OID: 1.3.6.1.4.1.1978.2.18.2.2.1.29
URN notation: urn:oid:1.3.6.1.4.1.1978.2.18.2.2.1.29
Type: OBJECT-TYPE

ASN.1, OID-IRI and named path variants

ASN.1 notation

{1 3 6 1 4 1 1978 2 18 2 2 1 29}

{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}
{iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) interfaces(2) ifTable(2) ifEntry(1) ifClearStats(29)}

OID-IRI notation

/1/3/6/1/4/1/1978/2/18/2/2/1/29
/ISO/Identified-Organization/6/1/4/1/1978/2/18/2/2/1/29
/ISO/3/6/1/4/1/1978/2/18/2/2/1/29

Named path variants

/iso/identified-organization/dod/internet/private/enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/identified-organization/dod/internet/private/enterprises/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/identified-organization/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/identified-organization/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/org/dod/internet/private/enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/org/dod/internet/private/enterprises/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/org/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/org/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-identified-organization/dod/internet/private/enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-identified-organization/dod/internet/private/enterprises/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-identified-organization/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-identified-organization/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-organization/dod/internet/private/enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-organization/dod/internet/private/enterprises/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-organization/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats
/iso/iso-organization/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/interfaces/ifTable/ifEntry/ifClearStats

SNMP properties

Value type: INTEGER
Maximum access defined by MIB: read-write
Status in MIB: mandatory
Default value: cleared

Enumerated values

Value	Name
1	clear
2	cleared
3	cleared-confirmed

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In SYS-MIB, the row index ifIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1978.2.18.2.2.1.29.<ifIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

Published row index: ifIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1978.2.18.2.2.1.29

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Published definition

The displayed source records contain one distinct definition. Compare its source records.

ifClearStats OBJECT-TYPE
SYNTAX INTEGER {
clear (1),
cleared (2),
cleared-confirmed (3)
}
ACCESS read-write
STATUS mandatory
DESCRIPTION
"When set to 'clear' all of the interface statistics are cleared to zero.
It will also force a clearing of all protocol, and 'user' statistics that
are related to this interface.

Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8)

When read, this object should always return 'cleared' indicating that
the clear operation took place. Should the operation be defered, the
value will remain as 'clear' until such time as:

1/ all of the statistics have actually been zeroed, and
2/ ifClearStatsTime has been updated with the correct time.

Should an NMS read the object and receive a 'cleared' indication, the SNMP agent
will set this object to 'cleared-confirmed'. This aids the NMS in determining
whether or not the agent successfully received subsequent clear request.

Normal operation would be:

NMS Agent

set 'clear' --> set to 'clear,' perform clearing
.
read --> .
'clear' <-- .
clearing complete, set to 'cleared'
.
read --> .
'cleared' <-- set to 'cleared-confirmed'
.
read --> .
'cleared-confirmed' <-- .

Rules:
1/ NMS must read 'cleared-confirmed' BEFORE attempting
to set 'clear'.
2/ After setting 'clear' the NMS must read 'cleared'.
then the NMS must read 'cleared-confirmed'.
In this manner, if a 'clear' command was missed by the agent,
the variable will still be set to either 'cleared' or 'cleared-confirmed'."
DEFVAL { cleared }
::= { ifEntry 29 }

Meaning

Descriptions

2 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Description 1

When set to 'clear' all of the interface statistics are cleared to zero.
It will also force a clearing of all protocol, and 'user' statistics that
are related to this interface.

Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8)

When read, this object should always return 'cleared' indicating that
the clear operation took place. Should the operation be defered, the
value will remain as 'clear' until such time as:

1/ all of the statistics have actually been zeroed, and
2/ ifClearStatsTime has been updated with the correct time.

Should an NMS read the object and receive a 'cleared' indication, the SNMP agent
will set this object to 'cleared-confirmed'. This aids the NMS in determining
whether or not the agent successfully received subsequent clear request.

Normal operation would be:

NMS Agent

set 'clear'
.
read
'clear' <
clearing complete, set to 'cleared'
.
read
'cleared' <
.
read
'cleared-confirmed' <

Rules:
1/ NMS must read 'cleared-confirmed' BEFORE attempting
to set 'clear'.
2/ After setting 'clear' the NMS must read 'cleared'.
then the NMS must read 'cleared-confirmed'.
In this manner, if a 'clear' command was missed by the agent,
the variable will still be set to either 'cleared' or 'cleared-confirmed'.

Sources for this description

Circitor

Parsed from SYS-MIB.mib · SYS-MIB

MIBdepot

Description 2

When set to 'clear' all of the interface statistics are cleared to zero. It will also force a clearing of all protocol, and 'user' statistics that are related to this interface. Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8) When read, this object should always return 'cleared' indicating that the clear operation took place. Should the operation be defered, the value will remain as 'clear' until such time as: 1/ all of the statistics have actually been zeroed, and 2/ ifClearStatsTime has been updated with the correct time. Should an NMS read the object and receive a 'cleared' indication, the SNMP agent will set this object to 'cleared-confirmed'. This aids the NMS in determining whether or not the agent successfully received subsequent clear request. Normal operation would be: NMS Agent set 'clear' --> set to 'clear,' perform clearing . read --> . 'clear' <-- . clearing complete, set to 'cleared' . read --> . 'cleared' <-- set to 'cleared-confirmed' . read --> . 'cleared-confirmed' <-- . Rules: 1/ NMS must read 'cleared-confirmed' BEFORE attempting to set 'clear'. 2/ After setting 'clear' the NMS must read 'cleared'. then the NMS must read 'cleared-confirmed'. In this manner, if a 'clear' command was missed by the agent, the variable will still be set to either 'cleared' or 'cleared-confirmed'.

Sources for this description

CircitorMIBdepot

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 2Circitor, MIBdepot1 record · 2 sources

Description 2

ifClearStats · mandatoryCircitor, MIBdepot2 sources

Status in source: mandatory.

Names: ifClearStats

Technical details

{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ifClearStats",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "clear",
    "(",
    "1",
    ")",
    ",",
    "cleared",
    "(",
    "2",
    ")",
    ",",
    "cleared-confirmed",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"When set to 'clear' all of the interface statistics are cleared to zero. It will also force a clearing of all protocol, and 'user' statistics that are related to this interface. Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8) When read, this object should always return 'cleared' indicating that the clear operation took place. Should the operation be defered, the value will remain as 'clear' until such time as: 1/ all of the statistics have actually been zeroed, and 2/ ifClearStatsTime has been updated with the correct time. Should an NMS read the object and receive a 'cleared' indication, the SNMP agent will set this object to 'cleared-confirmed'. This aids the NMS in determining whether or not the agent successfully received subsequent clear request. Normal operation would be: NMS Agent set 'clear' --> set to 'clear,' perform clearing . read --> . 'clear' <-- . clearing complete, set to 'cleared' . read --> . 'cleared' <-- set to 'cleared-confirmed' . read --> . 'cleared-confirmed' <-- . Rules: 1/ NMS must read 'cleared-confirmed' BEFORE attempting to set 'clear'. 2/ After setting 'clear' the NMS must read 'cleared'. then the NMS must read 'cleared-confirmed'. In this manner, if a 'clear' command was missed by the agent, the variable will still be set to either 'cleared' or 'cleared-confirmed'.\"",
    "DEFVAL",
    "{",
    "cleared",
    "}",
    "::=",
    "{",
    "ifEntry",
    "29",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "clear",
            1
          ],
          [
            "cleared",
            2
          ],
          [
            "cleared-confirmed",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "When set to 'clear' all of the interface statistics are cleared to zero. It will also force a clearing of all protocol, and 'user' statistics that are related to this interface. Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8) When read, this object should always return 'cleared' indicating that the clear operation took place. Should the operation be defered, the value will remain as 'clear' until such time as: 1/ all of the statistics have actually been zeroed, and 2/ ifClearStatsTime has been updated with the correct time. Should an NMS read the object and receive a 'cleared' indication, the SNMP agent will set this object to 'cleared-confirmed'. This aids the NMS in determining whether or not the agent successfully received subsequent clear request. Normal operation would be: NMS Agent set 'clear' --> set to 'clear,' perform clearing . read --> . 'clear' <-- . clearing complete, set to 'cleared' . read --> . 'cleared' <-- set to 'cleared-confirmed' . read --> . 'cleared-confirmed' <-- . Rules: 1/ NMS must read 'cleared-confirmed' BEFORE attempting to set 'clear'. 2/ After setting 'clear' the NMS must read 'cleared'. then the NMS must read 'cleared-confirmed'. In this manner, if a 'clear' command was missed by the agent, the variable will still be set to either 'cleared' or 'cleared-confirmed'."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "cleared"
    ]
  ]
}

Preserved mibdepot archive

Module: SYS-MIB

See published definition above

Module imports

{'PORT-MIB': ['rs232PortIndex'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'SNMPv2-TC': ['TruthValue'], 'RFC1155-SMI': ['Gauge', 'IpAddress', 'TimeTicks', 'Counter', 'enterprises'], 'RFC1213-MIB': ['DisplayString']}

· Download mibII.mib.txt

Preserved circitor archive

Module: SYS-MIB

Same published definition

Module imports

{'RFC-1212': ['OBJECT-TYPE'], 'RFC-1215': ['TRAP-TYPE'], 'RS232-MIB': ['rs232PortIndex'], 'SNMPv2-TC': ['TruthValue'], 'SNMPv2-SMI': ['Gauge32'], 'RFC1155-SMI': ['Gauge', 'IpAddress', 'TimeTicks', 'Counter', 'enterprises'], 'RFC1213-MIB': ['DisplayString']}

· Download SYS-MIB.mib

Historical records

Additional source information

Information from OID Repository

Vendor: SITA ADS
Module: SYS-MIB

[Automatically extracted from oidview.com]

Information from MIBdepot

Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8)

When read, this object should always return 'cleared' indicating that
the clear operation took place. Should the operation be defered, the
value will remain as 'clear' until such time as:

1/ all of the statistics have actually been zeroed, and
2/ ifClearStatsTime has been updated with the correct time.

Normal operation would be:

NMS Agent

set 'clear'
.
read
'clear' <
clearing complete, set to 'cleared'
.
read
'cleared' <
.
read
'cleared-confirmed' <

Information from Circitor

Normally, this object will be adjusted if it is associated with physical ports (i.e. 1 - 8)

When read, this object should always return 'cleared' indicating that
the clear operation took place. Should the operation be defered, the
value will remain as 'clear' until such time as:

1/ all of the statistics have actually been zeroed, and
2/ ifClearStatsTime has been updated with the correct time.

Normal operation would be:

NMS Agent

set 'clear'
.
read
'clear' <
clearing complete, set to 'cleared'
.
read
'cleared' <
.
read
'cleared-confirmed' <

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1978)

Hew Fulko

Siblings (36)

OID	Name	Description
1.3.6.1.4.1.1978.2.18.2.2.1.1	ifIndex	A unique value for each interface. Its value ranges between 1 and the value of ifNumber. The value for each interface must rema…
1.3.6.1.4.1.1978.2.18.2.2.1.2	ifDescr	A textual string containing information about the interface. This string should include the name of the manufacturer, the produc…
1.3.6.1.4.1.1978.2.18.2.2.1.3	ifType	iftype
1.3.6.1.4.1.1978.2.18.2.2.1.4	ifMtu	The size of the largest datagram which can be sent/received on the interface, specified in octets. For interfaces that are used…
1.3.6.1.4.1.1978.2.18.2.2.1.5	ifSpeed	An estimate of the interface's current bandwidth in bits per second. For interfaces which do not vary in bandwidth or for those …
1.3.6.1.4.1.1978.2.18.2.2.1.6	ifPhysAddress	This information is required for configuration only when BOOTP support is enabled in the TIGER configuration tool in order to pr…
1.3.6.1.4.1.1978.2.18.2.2.1.7	ifAdminStatus	The desired state of the interface. The testing(3) state indicates that no operational packets can be passed.
1.3.6.1.4.1.1978.2.18.2.2.1.8	ifOperStatus	The current operational state of the interface. testing - indicates that no operational packets can be passed. up - normal…
1.3.6.1.4.1.1978.2.18.2.2.1.9	ifLastChange	The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior …
1.3.6.1.4.1.1978.2.18.2.2.1.10	ifInOctets	The total number of octets received on the interface, including framing characters.
1.3.6.1.4.1.1978.2.18.2.2.1.11	ifInUcastPkts	The number of subnetwork-unicast packets delivered to a higher-layer protocol.
1.3.6.1.4.1.1978.2.18.2.2.1.12	ifInNUcastPkts	The number of non-unicast (i.e., subnetwork-broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol.
1.3.6.1.4.1.1978.2.18.2.2.1.13	ifInDiscards	The number of inbound packets which were chosen to be discarded even though no errors had been detected to prevent their being d…
1.3.6.1.4.1.1978.2.18.2.2.1.14	ifInErrors	The number of inbound packets that contained errors preventing them from being deliverable to a higher-layer protocol.
1.3.6.1.4.1.1978.2.18.2.2.1.15	ifInUnknownProtos	The number of packets received via the interface which were discarded because of an unknown or unsupported protocol.
1.3.6.1.4.1.1978.2.18.2.2.1.16	ifOutOctets	The total number of octets transmitted out of the interface, including framing characters.
1.3.6.1.4.1.1978.2.18.2.2.1.17	ifOutUcastPkts	The total number of packets that higher-level protocols requested be transmitted to a subnetwork-unicast address, including thos…
1.3.6.1.4.1.1978.2.18.2.2.1.18	ifOutNUcastPkts	The total number of packets that higher-level protocols requested be transmitted to a non-unicast (i.e., a subnetwork-broadcast …
1.3.6.1.4.1.1978.2.18.2.2.1.19	ifOutDiscards	The number of outbound packets which were chosen to be discarded even though no errors had been detected to prevent their being …
1.3.6.1.4.1.1978.2.18.2.2.1.20	ifOutErrors	The number of outbound packets that could not be transmitted because of errors.
1.3.6.1.4.1.1978.2.18.2.2.1.21	ifOutQLen	The length of the output packet queue (in packets).
1.3.6.1.4.1.1978.2.18.2.2.1.22	ifSpecific	A reference to MIB definitions specific to the particular media being used to realize the interface. For example, if the interf…
1.3.6.1.4.1.1978.2.18.2.2.1.23	ifInMulticastPkts	The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a multicast address at this …
1.3.6.1.4.1.1978.2.18.2.2.1.24	ifInBroadcastPkts	The number of packets, delivered by this sub-layer to a higher (sub-)layer, which were addressed to a broadcast address at this …
1.3.6.1.4.1.1978.2.18.2.2.1.25	ifOutMulticastPkts	The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a multicast addres…
1.3.6.1.4.1.1978.2.18.2.2.1.26	ifOutBroadcastPkts	The total number of packets that higher-level protocols requested be transmitted, and which were addressed to a broadcast addres…
1.3.6.1.4.1.1978.2.18.2.2.1.27	ifStateChangeTrapEnable	Indicates whether ifStateChange traps should be generated for this interface. By default, this object should have the value enab…
1.3.6.1.4.1.1978.2.18.2.2.1.28	ifConnectorPresent	This object has the value 'true(1)' if the interface sublayer has a physical connector and the value 'false(2)' otherwise.
1.3.6.1.4.1.1978.2.18.2.2.1.30	ifClearStatsTime	The number of ticks when the Tiger last received a ifClearStats command.
1.3.6.1.4.1.1978.2.18.2.2.1.31	ifErrorRateTrapEnable	Indicates whether ifErrorRate traps should be generated for this interface. In addition to enabling the trap via this object, th…
1.3.6.1.4.1.1978.2.18.2.2.1.32	ifErrorRateInterval	The amount of time over which any error rate is calculated.
1.3.6.1.4.1.1978.2.18.2.2.1.33	ifErrorInLowThreshold	If the number of input errors drops below the low water mark (threshold) over the interval defined by 'ifErrorRateInterval' then…
1.3.6.1.4.1.1978.2.18.2.2.1.34	ifErrorInHighThreshold	ifErrorInHighthreshold
1.3.6.1.4.1.1978.2.18.2.2.1.35	ifErrorOutLowThreshold	If the number of output errors drops below the low water mark (threshold) over the interval defined by 'ifErrorRateInterval' the…
1.3.6.1.4.1.1978.2.18.2.2.1.36	ifErrorOutHighThreshold	ifErrorOutHighthreshold
1.3.6.1.4.1.1978.2.18.2.2.1.37	ifErrType	Informs the NMS of the reason for the ifErrorRate trap that was received. When read asynchronously, it also indicates the last k…