lcsSNMPv3UserConfEngineID – LCOS-SX-MIB

Object

column r/w SNMPv2-TCDisplayString

An octet string identifying the engine ID that this entry should belong to.
The string must contain an even number(in hexadecimal format) with
number of digits between 10 and 64, but all-zeros and all-'F's are not allowed.
The SNMPv3 architecture uses the User-based Security Model (USM)
for message security and the View-based Access Control Model (VACM) for access control.
For the USM entry, the usmUserEngineID and usmUserName are the entry's keys.
In a simple agent, usmUserEngineID is always that agent's own snmpEngineID value.
The value can also take the value of the snmpEngineID of a remote SNMP engine with
which this user can communicate. In other words, if user engine ID equal system engine ID
then it is local user; otherwise it's remote user.

Context

MIB: LCOS-SX-MIB
OID: .1.3.6.1.4.1.2356.14.1.6.6.1.2
Type: column
Access: readwrite
Status: current
Parent: lcsSNMPv3UserConfEntry

Net-SNMP examples

How SNMP and these commands work

Walk 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 'LCOS-SX-MIB' -M '/opt/observium/mibs/lancom:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LCOS-SX-MIB::lcsSNMPv3UserConfEngineID'

More examples

Read one indexed 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::lcsSNMPv3UserConfEngineID.<index>'

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::lcsSNMPv3UserConfEngineID'

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