The number of ICMP Echo (request) messages sent from this port.
Sources for this description
Retix RX7000 MIB in the historical IETF archive
OID reference
1.3.6.1.4.1.72.14.3.31.1.31
The number of ICMP Echo (request) messages sent from this port.
Identification
{1 3 6 1 4 1 72 14 3 31 1 31}
A counter is cumulative. To estimate a rate, subtract two readings and divide by the elapsed time; use the units stated in the MIB.
Counter values can wrap or reset. A decrease alone does not distinguish a wrap from a reset, and multiple wraps between readings cannot be recovered reliably. Check the device's discontinuity indicators when available.
Published counter width: 32 bits. SMIv2: Counter32 · Counter64
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 RETIX-RX7000-MIB, the row index ipPortStatsIndex 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.72.14.3.31.1.31.<ipPortStatsIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
Published row index: ipPortStatsIndex.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.72.14.3.31.1.31
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.
ipPortICMPOutEchos OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
DESCRIPTION
"The number of ICMP Echo (request) messages sent
from this port."
::= { ipPortStatsEntry 31 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The number of ICMP Echo (request) messages sent from this port.
Retix RX7000 MIB in the historical IETF archive
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: mandatory.
Names: ipPortICMPOutEchos
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ipPortICMPOutEchos",
"OBJECT-TYPE",
"SYNTAX",
"Counter",
"ACCESS",
"read-only",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"The number of ICMP Echo (request) messages sent from this port.\"",
"::=",
"{",
"ipPortStatsEntry",
"31",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Counter"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"The number of ICMP Echo (request) messages sent from this port."
],
null,
null,
null,
null
]
}Module: RETIX-RX7000-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['mgmt', 'experimental', 'NetworkAddress', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Source data warning: This is a historical Retix version 3.2 MIB dated 26 July 1995, preserved in a mirror of the IETF private MIB archive. It covers the product and software releases named in the file; the archive does not make it an IETF standard. The author states that the file includes draft MIBs. Its enterprises symbol is used without an IMPORTS declaration; its standard value is supplied from RFC 1155 for this exact reviewed file only.
· Download Retix RX7000 MIB version 3.2 — historical IETF archiveRelated source files and packages:
Registration