tlpAgentConfigRemoteRegistration

TRIPPLITE-PRODUCTS · .1.3.6.1.4.1.850.1.2.2.1.1

Object

Registers an SNMP contact's IP address and the port on which 
the contact is listening for SNMP traps.  Setting this
value is used to CREATE a table entry in a non-standard way.
Getting this value will return a string INADDR_ANY and any
port number.
          
The port number should always be included. When unregistering
an SNMP contact, the requester's IP address should be provided
with a port number of 0.  When setting or unsetting this OID, 
the IP address string should never be 0 nor should it be empty.
          
The registration uses its default community string to register
each contact. To use a community other than the default, then
it must be appended to the end of the string delimited with a
comma.
          
The address should be of the format 0.0.0.0:00000 for IPv4. 
If IPv6 is supported, use the bracket-enclosed format given 
in IETF RFC 2732 Section 2, with the following examples:
          
[FEDC:BA98:7654:3210:FEDC:BA98:7654:3210]:80
[1080:0:0:0:8:800:200C:417A]:162
[3ffe:2a00:100:7031::1]:162
[1080::8:800:200C:417A]:162,myCommunity
[::192.9.5.5]:162,myCommunity
[::FFFF:129.144.52.38]:80
[2010:836B:4179::836B:4179]:162

Context

MIB
TRIPPLITE-PRODUCTS
OID
.1.3.6.1.4.1.850.1.2.2.1.1
Type
scalar
Access
readwrite
Status
current
Parent
tlpAgentConfig

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TRIPPLITE-PRODUCTS' -M '/opt/observium/mibs/tripplite:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TRIPPLITE-PRODUCTS::tlpAgentConfigRemoteRegistration.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TRIPPLITE-PRODUCTS' -M '/opt/observium/mibs/tripplite:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TRIPPLITE-PRODUCTS::tlpAgentConfigRemoteRegistration'

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

Type Constraints
range: 0..255