lcsPTPClockConfEntryClockDefaultDataSetClockQuality – LCOS-SX-MIB

Object

scalar SNMPv2-TCDisplayString

The clock quality is determined by the system, and holds 3 parts: Clock Class, Clock Accuracy and OffsetScaledLog Variance as defined in IEEE1588.
The Clock Accuracy values are defined in IEEE1588 table 6 (Currently the clock Accuracy is set to 'Unknown' as default).

Context

MIB: LCOS-SX-MIB
OID: .1.3.6.1.4.1.2356.14.2.28.7.30
Type: scalar
Access: readonly
Status: current
Parent: lcsPTPClockConfAndStatus

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LCOS-SX-MIB::lcsPTPClockConfEntryClockDefaultDataSetClockQuality.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LCOS-SX-MIB::lcsPTPClockConfEntryClockDefaultDataSetClockQuality'

Syntax

SNMPv2-TCDisplayString

Source: SNMPv2-TCDisplayString
Base type: OctetString
Display format: 255a

Type Description

Represents textual information taken from the NVT ASCII
          
character set, as defined in pages 4, 10-11 of RFC 854.
          
To summarize RFC 854, the NVT ASCII repertoire specifies:
          
  - the use of character codes 0-127 (decimal)
          
  - the graphics characters (32-126) are interpreted as
    US ASCII
          
  - NUL, LF, CR, BEL, BS, HT, VT and FF have the special
    meanings specified in RFC 854
          
  - the other 25 codes have no standard interpretation
          
  - the sequence 'CR LF' means newline
          
  - the sequence 'CR NUL' means carriage-return
          
  - an 'LF' not preceded by a 'CR' means moving to the
    same column on the next line.
          
  - the sequence 'CR x' for any x other than LF or NUL is
    illegal.  (Note that this also means that a string may
    end with either 'CR LF' or 'CR NUL', but not with CR.)
          
Any object defined using this syntax may not exceed 255
characters in length.

Values & Constraints

Type Constraints

range: 0..255