fsPtpGblTraceOption – SUPERMICRO-PTP-MIB

Object

scalar r/w SNMPv2-TCDisplayString

This object stores the trace option string input given by the user.
Based on the input to this object, trace statements corresponding
to the given options are displayed.
To enable particular trace the user has to enter the corresponding
string(given below) assigned for that. For enabling more than one
traces the user has to enter the corresponding strings with SPACE
(delimiter) between each string.
      For example,
      To enable the below traces:
          - Start and Shutdown traces
          - Management traces
          - Sync traces and
          - Packet Dump traces
          
      The input should be fed as follows:
      enable init-shut mgmt ctrl pkt-dump
          
      To disable the below traces:
          - Start and Shutdown traces
          - Sync traces
          
      The input should be,
      disable init-shut sync
          
      The entered input string is parsed to get the trace options.
          
enable / disable trace-types1 trace-types2 ...
          
TRACE-TYPES - TRACE-DESCRIPTION 
          
init-shut - Start and Shutdown traces
mgmt      - Management Traces
datapath  - Data packet path
ctrl      - Control Plane path 
pkt-dump  - Packet Dump Traces
resource  - Resourece failure traces
all-fail  - All Failure traces
buffer    - Buffer Traces
critical  - PTP Critical Traces
          
This object is used in places where context is not visible.
Any change in this object affects fsPtpTraceOption in all
contexts i.e. if a trace is set for fsPtpGblTraceOption, then
the same trace will be set for fsPtpTraceOption in all context.
Similarly if a trace is reset for fsPtpGblTraceOption, then
the same trace will be reset for fsPtpTraceOption in all context.

Context

MIB: SUPERMICRO-PTP-MIB
OID: .1.3.6.1.4.1.10876.101.2.45.1.1.2
Type: scalar
Access: readwrite
Status: current
Parent: fsPtpGeneralGroup

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 'SUPERMICRO-PTP-MIB' -M '/opt/observium/mibs/supermicro:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SUPERMICRO-PTP-MIB::fsPtpGblTraceOption.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'SUPERMICRO-PTP-MIB' -M '/opt/observium/mibs/supermicro:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'SUPERMICRO-PTP-MIB::fsPtpGblTraceOption'

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