ipIcmpTimestampReply
BINTEC-IPEXT-MIB ·
.0.32.10
Object
scalar r/w
Enumeration
enabled : each incoming ICMP 'Timestamp' message
addressed to local system is answered with
an RFC792-compliant ICMP 'Timestamp-Reply'
message.
This is the default behavior of the system.
disabled: incoming ICMP 'Timestamp' messages addressed
to local system are silently discarded.
extended: if an incoming ICMP 'Timestamp' message
contains data appended after the three
timestamp fields (which is a deviation of
RFC792), the system replies with a modified
'Timestamp-Reply' message which contains a
copy of the received data appended after
the three timestamp fields. This behaviour
is not RFC792-compliant and should be reserved
for testing purposes.
Context
- MIB
- BINTEC-IPEXT-MIB
- OID
.0.32.10- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- ipIcmp
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'BINTEC-IPEXT-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'BINTEC-IPEXT-MIB::ipIcmpTimestampReply.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'BINTEC-IPEXT-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'BINTEC-IPEXT-MIB::ipIcmpTimestampReply'
Syntax
Enumeration
Values & Constraints
No enumerated values or constraints recorded.