zxAnSysClockSourcePriority – ZTE-AN-SYS-MIB

Object

scalar r/w SNMPv2-TCDisplayString

Clock source priority. For example, the string '3,4,2,5,6,1' means there are 6 priorities.
And priority 1 is clock source 3(est2m),priority 2 is clock source 4(ttl2m),etc.
The clock source values refer to zxAnSysConfigClockSource.

Context

MIB: ZTE-AN-SYS-MIB
OID: .1.3.6.1.4.1.3902.1015.1.1.104.5
Type: scalar
Access: readwrite
Status: current
Parent: zxAnSysClockMgmt

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 'ZTE-AN-SYS-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ZTE-AN-SYS-MIB::zxAnSysClockSourcePriority.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'ZTE-AN-SYS-MIB' -M '/opt/observium/mibs/zte:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ZTE-AN-SYS-MIB::zxAnSysClockSourcePriority'

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