option82FormatVerboseNodeIdentifier
GBNL3If-MIB ·
.1.3.6.1.4.1.13464.1.2.5.1.5.4
Object
when format is verbose,can set value of node-identifier.Except special string listing below, others string means user-define string. default is 0 length of value, means use switch mac
Context
- MIB
- GBNL3If-MIB
- OID
.1.3.6.1.4.1.13464.1.2.5.1.5.4- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- gbnL3DHCP
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'GBNL3If-MIB' -M '/opt/observium/mibs/gbn:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'GBNL3If-MIB::option82FormatVerboseNodeIdentifier.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'GBNL3If-MIB' -M '/opt/observium/mibs/gbn:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'GBNL3If-MIB::option82FormatVerboseNodeIdentifier'
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-50
Type Constraints
range: 0..255