clientIfJ1TxTrailTrace
LUM-CLIENT-MIB ·
.1.3.6.1.4.1.8708.2.27.2.2.1.1.70
Object
The J1 trail trace identifier(s) to be
transmitted for the VC4s/VC3s related to this
interface, in the line signal (STM16/OC48).
This parameter can be used in two different
modes, see j1TxTrailTraceInsertionMode.
The insertionMode therefore decides what
the transmitted string actually will look
like.
Set to empty string for default value:
<IP address><space><subrack><slot><interface>
xx.xx y w z
=> 'xx.xx ywz'
where:
<IP address>: xx.xx
The last 2 octets coded in hex.
5 bytes.
<space>: 1 byte.
<subrack>: y
The subrack number coded in hex.
1 byte.
<slot>: w
The slot position coded n hex.
Slot 16 and 17 will be coded as 0
and 1 respectively.
1 byte.
<interface>: z
The logical numbering of the client interface
coded in hex.
Interface 1 <=> ports 1-2
2 <=> 3-4
10 <=> 19-20
1 byte
Context
- MIB
- LUM-CLIENT-MIB
- OID
.1.3.6.1.4.1.8708.2.27.2.2.1.1.70- Type
- column
- Access
- readwrite
- Status
- current
- Default
""- Parent
- clientIfEntry
- Groups
- 28
Net-SNMP examples
How SNMP and these commands workWalk the column to discover its indexed instances, or supply every index to read one instance.
Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LUM-CLIENT-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LUM-CLIENT-MIB::clientIfJ1TxTrailTrace'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'LUM-CLIENT-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LUM-CLIENT-MIB::clientIfJ1TxTrailTrace.<clientIfIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'LUM-CLIENT-MIB' -M '/opt/observium/mibs/infinera:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'LUM-CLIENT-MIB::clientIfJ1TxTrailTrace'
Syntax
- 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
Object Constraints
range: 0-15
Type Constraints
range: 0..255
Conformance
Member of
clientIfGroupV10
clientIfGroupV11
clientIfGroupV12
clientIfGroupV13
clientIfGroupV14
clientIfGroupV15
clientIfGroupV16
clientIfGroupV17
clientIfGroupV18
clientIfGroupV19
clientIfGroupV20
clientIfGroupV21
clientIfGroupV22
clientIfGroupV23
clientIfGroupV24
clientIfGroupV25
clientIfGroupV26
clientIfGroupV27
clientIfGroupV28
clientIfGroupV29
clientIfGroupV30
clientIfGroupV31
clientIfGroupV32
clientIfGroupV33
clientIfGroupV6
clientIfGroupV7
clientIfGroupV8
clientIfGroupV9