OID reference

pingProbeHistoryLastRC

1.3.6.1.2.1.80.1.4.1.4

Description

The last implementation method specific reply code received. If the ICMP Echo capability is being used then a successful probe ends when an ICMP response is received that contains the code ICMP_ECHOREPLY(0). The ICMP responses are defined normally in the ip_icmp include file.

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.2.1.80.1.4.1 (pingProbeHistoryEntry)
Node code
4
Node name
pingProbeHistoryLastRC
Category
SNMP management object
Numeric OID
1.3.6.1.2.1.80.1.4.1.4
URN notation
urn:oid:1.3.6.1.2.1.80.1.4.1.4
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 2 1 80 1 4 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) mib(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
  • {iso(1) iso-organization(3) dod(6) internet(1) mgmt(2) stdmib-2(1) pingMIB(80) pingObjects(1) pingProbeHistoryTable(4) pingProbeHistoryEntry(1) pingProbeHistoryLastRC(4)}
OID-IRI notation
  • /1/3/6/1/2/1/80/1/4/1/4
  • /ISO/Identified-Organization/6/1/2/1/80/1/4/1/4
  • /ISO/3/6/1/2/1/80/1/4/1/4
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/identified-organization/dod/internet/mgmt/mib/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/identified-organization/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/org/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/org/dod/internet/mgmt/mib/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/org/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/org/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-identified-organization/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-identified-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-identified-organization/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-organization/dod/internet/mgmt/mib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-organization/dod/internet/mgmt/mib/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-organization/dod/internet/mgmt/RFC1066-MIB-INTERPRETATION/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC
  • /iso/iso-organization/dod/internet/mgmt/stdmib-2/pingMIB/pingObjects/pingProbeHistoryTable/pingProbeHistoryEntry/pingProbeHistoryLastRC

SNMP properties

Value type
Integer32, INTEGER
Maximum access defined by MIB
read-only
Status in MIB
current, mandatory

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — RFC Editor, MIBdepot, and others

Value type
Integer32
Maximum access defined by MIB
read-only
Status in MIB
current

Variant 2 — Cisco SMIv1

Value type
INTEGER
Maximum access defined by MIB
read-only
Status in MIB
mandatory

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. The index encoding is not inferred here.

Published row index: pingCtlOwnerIndex, pingCtlTestName, pingProbeHistoryIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.2.1.80.1.4.1.4

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.

Product context

Documented MIB packages

The FS.COM catalogue lists MIB packages containing this definition for these models:

IES3220-8T4F, IES3220-8T4F-U, IES5120-28TF, IES5120-28TS, IES5120-28TS-P, IES5120-48T4S, IES5220-30TS-3ES, IES5220-6S-3ES, N5580-32C, N5580-48Y8C, N5850-48S6Q, N5860-48SC.

Show 24 more models

N8560-32C, N8560-48BC, N8560-64C, NC8200-16Q, NC8200-24BC, NC8200-4TD, NC8200-8C, NC8400-16CD, NC8400-32C, NC8400-4TH, S3100-16TF, S3410-24TS-P, S3910-24TS, S3910-48TS, S5810-28FS, S5810-28TS, S5810-48FS, S5810-48TS, S5810-48TS-P, S5860-20SQ, S5860-24XB-U, S5860-48SC, TSN3220-10S, TSN3220-10S-U.

A definition in a model's MIB package does not establish that the device implements it or permits access.

The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:

These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.

Available source records contain 4 distinct definitions; some records may not include a definition.

Show 4 published definitions

pingProbeHistoryLastRC · current

pingProbeHistoryLastRC        OBJECT-TYPE
       SYNTAX      Integer32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The last implementation-method-specific reply code received.
           If the ICMP Echo capability is being used, then a successful
           probe ends when an ICMP response is received that contains
           the code ICMP_ECHOREPLY(0).  The ICMP codes are maintained
           by IANA.  Standardized ICMP codes are listed at
           http://www.iana.org/assignments/icmp-parameters.
           The ICMPv6 codes are listed at
           http://www.iana.org/assignments/icmpv6-parameters."
       ::= { pingProbeHistoryEntry 4 }

pingProbeHistoryLastRC · current

pingProbeHistoryLastRC        OBJECT-TYPE
       SYNTAX      Integer32
       MAX-ACCESS  read-only
       STATUS      current
       DESCRIPTION
           "The last implementation-method-specific reply code received.
           If the ICMP Echo capability is being used, then a successful
           probe ends when an ICMP response is received that contains
           the code ICMP_ECHOREPLY(0).  The ICMP codes are maintained
           by IANA.  Standardized ICMP codes are listed at
           http://www.iana.org/assignments/icmp-parameters.
           The ICMPv6 codes are listed at
           http://www.iana.org/assignments/icmpv6-parameters."
       ::= { pingProbeHistoryEntry 4 }

pingProbeHistoryLastRC · current

pingProbeHistoryLastRC        OBJECT-TYPE
   SYNTAX      Integer32
   MAX-ACCESS  read-only
   STATUS      current
   DESCRIPTION
       "The last implementation-method-specific reply code received.
       If the ICMP Echo capability is being used, then a successful
       probe ends when an ICMP response is received that contains
       the code ICMP_ECHOREPLY(0).  The ICMP codes are maintained
       by IANA.  Standardized ICMP codes are listed at
       http://www.iana.org/assignments/icmp-parameters.
       The ICMPv6 codes are listed at
       http://www.iana.org/assignments/icmpv6-parameters."
   ::= { pingProbeHistoryEntry 4 }

pingProbeHistoryLastRC · current

pingProbeHistoryLastRC        OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The last implementation-method-specific reply code received.
        If the ICMP Echo capability is being used, then a successful
        probe ends when an ICMP response is received that contains
        the code ICMP_ECHOREPLY(0).  The ICMP codes are maintained
        by IANA.  Standardized ICMP codes are listed at
        http://www.iana.org/assignments/icmp-parameters.
        The ICMPv6 codes are listed at
        http://www.iana.org/assignments/icmpv6-parameters."
    ::= { pingProbeHistoryEntry 4 }

Meaning

Descriptions

3 unique

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

Description 1

The last implementation method specific reply code received. If the ICMP Echo capability is being used then a successful probe ends when an ICMP response is received that contains the code ICMP_ECHOREPLY(0). The ICMP responses are defined normally in the ip_icmp include file.
Original text from OID Repository
pingProbeHistoryLastRC OBJECT-TYPE SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The last implementation method specific reply code received.
If the ICMP Echo capability is being used then a successful
probe ends when an ICMP response is received that contains
the code ICMP_ECHOREPLY(0). The ICMP responses are defined
normally in the ip_icmp include file."
Sources for this description

OID Repository

View at oid-base.com
Automatically extracted from RFC2925

Circitor

Parsed from DISMAN-PING-MIB.mib · DISMAN-PING-MIB

Source file: Download DISMAN-PING-MIB.mib

Browse all files from Circitor

Cisco

Source file: Download rfc2925-disman-ping.mib · Publisher's file

Other official packages with the same file

tsn3220-10s-u-switch-snmp-mib-files.zip

tsn3220-10s-switch-snmp-mib-files.zip

ies5220-6s-3es-switch-snmp-mib-files.zip

ies5220-30ts-3es-switch-snmp-mib-files.zip

Source file: Download rfc2925.mib · Publisher's file

Other official packages with the same file

MIB-6.5.1.22.zip

XS728T_XS748T_mib_files.zip

XS728T_XS748T_MIB_V6.5.1.59.zip

XS728T_XS748T_MIB_V6.5.1.42.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

M4250H-v13.0.4.14-mibs.zip

M4250H-v13.0.4.13-mibs.zip

M4250L-v13.0.4.14-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

XS508TM_XS516TM-v7.8.11.13-Mibs.zip

M4350-v14.0.9.10-mibs.zip

M4350-v14.0.6.9-mibs.zip

M4350-v14.0.6.19-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

mibs-m4500-48xf8c-7.0.5.6.tar.bz2

mibs-m4500-48xf8c-7.0.4.30.tar.bz2

mibs-m4500-48xf8c-7.0.4.23.tar.bz2

mibs-m4500-48xf8c-7.0.4.18.tar.bz2

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

xsm72xxs-v9.0.1.46-mibs.zip

gs7xxts_tps-v5.3.0.31-mibs.zip

gs7xxts_tps-v5.3.0.29-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

xs7xxt_6.6.3.2-mibs.zip

xs712t-v6.1.0.36-mibs.zip

xs712t-v6.1.0.34-mibs.zip

xs7xxt6.6.3.3-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

xs7xxtv7.0.0.24-mibs.zip

xs7xxtv7.0.0.20-mibs.zip

s3300v6.6.4.26-mibs.zip

s3300v6.6.4.25-mibs.zip

Source file: Download rfc2925_ping.my · Publisher's file

Other official packages with the same file

GSM72xxP-mibs-fwv9.0.2.2.zip

gs7xxts_tps-v5.3.0.36-mibs.zip

gs7xxts_tps-v5.3.0.35-mibs.zip

fs728tp_5.0.2.50-mibs.zip

Source file: Download rfc2925_ping.mib · Publisher's file

Other official packages with the same file

LC-YS-7154CF-5.30.0363-RU2-MIB.zip

LC-XS-6128QF-5.20.0534-RU12-MIB.zip

LC-XS-5116QF-5.20.0534-RU12-MIB.zip

LC-XS-5110F-5.20.0534-RU12-MIB.zip

Browse all files from Cisco

Description 2

The last implementation method specific reply code received.

Sources for this description

H3C official MIB documentation and object descriptions

See 1 matching source record

Description 3

The last implementation-method-specific reply code received. If the ICMP Echo capability is being used, then a successful probe ends when an ICMP response is received that contains the code ICMP_ECHOREPLY(0). The ICMP codes are maintained by IANA. Standardized ICMP codes are listed at http://www.iana.org/assignments/icmp-parameters. The ICMPv6 codes are listed at http://www.iana.org/assignments/icmpv6-parameters.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBsD-Link official switch MIBsFS.COM official Documentation Hub native MIB packagesHuawei official enterprise MIB Query and object descriptionsMIBdepotCommon and standard MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copiesRFC Editor

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 2H3C official MIB documentation and object descriptions1 record · 36 sources

Description 2

pingProbeHistoryLastRC · unspecifiedH3C official MIB documentation and object descriptions36 sources

Status in source: unspecified.

Names: pingProbeHistoryLastRC

Technical details
{}

Browse all 36 supporting sources

Records for description 3Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs, and others1 record · 11 sources

Description 3

pingProbeHistoryLastRC · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Belden, GarrettCom and Hirschmann IT official standalone MIBs, and others11 sources

Status in source: current.

Names: pingProbeHistoryLastRC

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "pingProbeHistoryLastRC",
    "OBJECT-TYPE",
    "SYNTAX",
    "Integer32",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The last implementation-method-specific reply code received. If the ICMP Echo capability is being used, then a successful probe ends when an ICMP response is received that contains the code ICMP_ECHOREPLY(0). The ICMP codes are maintained by IANA. Standardized ICMP codes are listed at http://www.iana.org/assignments/icmp-parameters. The ICMPv6 codes are listed at http://www.iana.org/assignments/icmpv6-parameters.\"",
    "::=",
    "{",
    "pingProbeHistoryEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "Integer32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The last implementation-method-specific reply code received. If the ICMP Echo capability is being used, then a successful probe ends when an ICMP response is received that contains the code ICMP_ECHOREPLY(0). The ICMP codes are maintained by IANA. Standardized ICMP codes are listed at http://www.iana.org/assignments/icmp-parameters. The ICMPv6 codes are listed at http://www.iana.org/assignments/icmpv6-parameters."
    ],
    null,
    null,
    null,
    null
  ]
}

Browse all 11 supporting sources

Historical records

Additional source information

Information from Circitor
pingProbeHistoryLastRC        OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The last implementation method specific reply code received.
        If the ICMP Echo capability is being used then a successful
        probe ends when an ICMP response is received that contains
        the code ICMP_ECHOREPLY(0).  The ICMP responses are defined
        normally in the ip_icmp include file."
    ::= { pingProbeHistoryEntry 4 }
Information from Cisco SMIv1
pingProbeHistoryLastRC OBJECT-TYPE
    SYNTAX INTEGER
    ACCESS read-only
    STATUS mandatory
    DESCRIPTION
        "The last implementation method specific reply code received.
        If the ICMP Echo capability is being used then a successful
        probe ends when an ICMP response is received that contains
        the code ICMP_ECHOREPLY(0).  The ICMP responses are defined
        normally in the ip_icmp include file."
    ::= { pingProbeHistoryEntry 4 }
Information from MIBdepot
pingProbeHistoryLastRC        OBJECT-TYPE
    SYNTAX      Integer32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The last implementation method specific reply code received.
        If the ICMP Echo capability is being used then a successful
        probe ends when an ICMP response is received that contains
        the code ICMP_ECHOREPLY(0).  The ICMP responses are defined
        normally in the ip_icmp include file."
    ::= { pingProbeHistoryEntry 4 }
Information from Cisco
pingProbeHistoryLastRC OBJECT-TYPE
    SYNTAX          Integer32
    MAX-ACCESS      read-only
    STATUS          current
    DESCRIPTION
        "The last implementation method specific reply code received.
        If the ICMP Echo capability is being used then a successful
        probe ends when an ICMP response is received that contains
        the code ICMP_ECHOREPLY(0).  The ICMP responses are defined
        normally in the ip_icmp include file." 
    ::= { pingProbeHistoryEntry 4 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Siblings (4)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.80.1.4.1.1 pingProbeHistoryIndex, pingProeHistoryIndex00 An entry in this table is created when the result of
a ping probe is determined. The initial 2 instance
identifier index values …
1.3.6.1.2.1.80.1.4.1.2 pingProbeHistoryResponse00 The amount of time measured in milliseconds from when
a probe was sent to when its response was received or
when it timed out. T…
1.3.6.1.2.1.80.1.4.1.3 pingProbeHistoryStatus00 The result of a particular probe done by a remote host.
1.3.6.1.2.1.80.1.4.1.5 pingProbeHistoryTime00 Timestamp for when this probe result was determined.