OID reference

ipClearStats

1.3.6.1.4.1.1978.2.18.3.24

Description

When set to 'clear' all of the ip/icmp/tcp/udp/ppp/snmp statistics are cleared to zero. 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…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1978.2.18.3 (ip)
Node code
24
Node name
ipClearStats
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1978.2.18.3.24
URN notation
urn:oid:1.3.6.1.4.1.1978.2.18.3.24
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ngcan(1978) tiger(2) sysMIB(18) ip(3) ipClearStats(24)}
OID-IRI notation
  • /1/3/6/1/4/1/1978/2/18/3/24
  • /ISO/Identified-Organization/6/1/4/1/1978/2/18/3/24
  • /ISO/3/6/1/4/1/1978/2/18/3/24
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/identified-organization/dod/internet/private/enterprises/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/identified-organization/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/org/dod/internet/private/enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/org/dod/internet/private/enterprises/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/org/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/org/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-identified-organization/dod/internet/private/enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-identified-organization/dod/internet/private/enterprises/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-organization/dod/internet/private/enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-organization/dod/internet/private/enterprises/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/ngcan/tiger/sysMIB/ip/ipClearStats
  • /iso/iso-organization/dod/internet/private/vendor-objects/ngcan/tiger/sysMIB/ip/ipClearStats

SNMP properties

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

Enumerated values

ValueName
1clear
2cleared
3cleared-confirmed

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.1978.2.18.3.24.0

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.

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

ipClearStats OBJECT-TYPE
		SYNTAX		INTEGER {
			clear				(1),
			cleared				(2),
			cleared-confirmed	(3)
			}
		ACCESS		read-write
		STATUS		mandatory
		DESCRIPTION
			"When set to 'clear' all of the ip/icmp/tcp/udp/ppp/snmp statistics
			are cleared to zero.
			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/ ipClearStatsTime 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 }
		::= { ip 24 }

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 ip/icmp/tcp/udp/ppp/snmp statistics
are cleared to zero.
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/ ipClearStatsTime 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 ip/icmp/tcp/udp/ppp/snmp statistics are cleared to zero. 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/ ipClearStatsTime 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

ipClearStats · mandatoryCircitor, MIBdepot2 sources

Status in source: mandatory.

Names: ipClearStats

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "ipClearStats",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "clear",
    "(",
    "1",
    ")",
    ",",
    "cleared",
    "(",
    "2",
    ")",
    ",",
    "cleared-confirmed",
    "(",
    "3",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"When set to 'clear' all of the ip/icmp/tcp/udp/ppp/snmp statistics are cleared to zero. 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/ ipClearStatsTime 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",
    "}",
    "::=",
    "{",
    "ip",
    "24",
    "}"
  ],
  "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 ip/icmp/tcp/udp/ppp/snmp statistics are cleared to zero. 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/ ipClearStatsTime 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
ipClearStats OBJECT-TYPE
		SYNTAX		INTEGER {
			clear				(1),
			cleared				(2),
			cleared-confirmed	(3)
			}
		ACCESS		read-write
		STATUS		mandatory
		DESCRIPTION
			"When set to 'clear' all of the ip/icmp/tcp/udp/ppp/snmp statistics
			are cleared to zero.
			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/ ipClearStatsTime 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'."
		DEFVAL	{ cleared }
		::= { ip 24 }
Information from Circitor
ipClearStats OBJECT-TYPE
		SYNTAX		INTEGER {
			clear				(1),
			cleared				(2),
			cleared-confirmed	(3)
			}
		ACCESS		read-write
		STATUS		mandatory
		DESCRIPTION
			"When set to 'clear' all of the ip/icmp/tcp/udp/ppp/snmp statistics
			are cleared to zero.
			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/ ipClearStatsTime 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'."
		DEFVAL	{ cleared }
		::= { ip 24 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1978)

Hew Fulko

Siblings (24)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1978.2.18.3.1 ipForwarding00 The indication of whether this entity is acting
as an IP gateway in respect to the forwarding of
datagrams received by, but not a…
1.3.6.1.4.1.1978.2.18.3.2 ipDefaultTTL00 The default value inserted into the Time-To-Live
field of the IP header of datagrams originated at
this entity, whenever a TTL va…
1.3.6.1.4.1.1978.2.18.3.3 ipInReceives00 The total number of input datagrams received from
interfaces, including those received in error.
1.3.6.1.4.1.1978.2.18.3.4 ipInHdrErrors00 The number of input datagrams discarded due to
errors in their IP headers, including bad
checksums, version number mismatch, othe…
1.3.6.1.4.1.1978.2.18.3.5 ipInAddrErrors00 The number of input datagrams discarded because
the IP address in their IP header's destination
field was not a valid address to …
1.3.6.1.4.1.1978.2.18.3.6 ipForwDatagrams00 The number of input datagrams for which this
entity was not their final IP destination, as a
result of which an attempt was made …
1.3.6.1.4.1.1978.2.18.3.7 ipInUnknownProtos00 The number of locally-addressed datagrams
received successfully but discarded because of an
unknown or unsupported protocol.
1.3.6.1.4.1.1978.2.18.3.8 ipInDiscards00 The number of input IP datagrams for which no
problems were encountered to prevent their
continued processing, but which were dis…
1.3.6.1.4.1.1978.2.18.3.9 ipInDelivers00 The total number of input datagrams successfully
delivered to IP user-protocols (including ICMP).
1.3.6.1.4.1.1978.2.18.3.10 ipOutRequests00 The total number of IP datagrams which local IP
user-protocols (including ICMP) supplied to IP in
requests for transmission. Not…
1.3.6.1.4.1.1978.2.18.3.11 ipOutDiscards00 The number of output IP datagrams for which no
problem was encountered to prevent their
transmission to their destination, but wh…
1.3.6.1.4.1.1978.2.18.3.12 ipOutNoRoutes00 The number of IP datagrams discarded because no
route could be found to transmit them to their
destination. Note that this count…
1.3.6.1.4.1.1978.2.18.3.13 ipReasmTimeout00 The maximum number of seconds which received
fragments are held while they are awaiting
reassembly at this entity.
1.3.6.1.4.1.1978.2.18.3.14 ipReasmReqds00 The number of IP fragments received which needed
to be reassembled at this entity.
1.3.6.1.4.1.1978.2.18.3.15 ipReasmOKs00 The number of IP datagrams successfully re-assembled.
1.3.6.1.4.1.1978.2.18.3.16 ipReasmFails00 The number of failures detected by the IP re-
assembly algorithm (for whatever reason: timed
out, errors, etc). Note that this i…
1.3.6.1.4.1.1978.2.18.3.17 ipFragOKs00 The number of IP datagrams that have been
successfully fragmented at this entity.
1.3.6.1.4.1.1978.2.18.3.18 ipFragFails00 The number of IP datagrams that have been
discarded because they needed to be fragmented at
this entity but could not be, e.g., b…
1.3.6.1.4.1.1978.2.18.3.19 ipFragCreates00 The number of IP datagram fragments that have
been generated as a result of fragmentation at
this entity.
1.3.6.1.4.1.1978.2.18.3.20 ipAddrTable16 The table of addressing information relevant to
this entity's IP addresses.
1.3.6.1.4.1.1978.2.18.3.22 ipNetToMediaTable15 The IP Address Translation table used for mapping
from IP addresses to physical addresses.
1.3.6.1.4.1.1978.2.18.3.23 ipRoutingDiscards00 The number of routing entries which were chosen
to be discarded even though they are valid. One
possible reason for discarding s…
1.3.6.1.4.1.1978.2.18.3.25 ipClearStatsTime00 The number of ticks when the Tiger last received a ipClearStats command.
1.3.6.1.4.1.1978.2.18.3.26 ipForward414