tIPsecClientDBClientIdIdiValue

TIMETRA-IPSEC-MIB · .1.3.6.1.4.1.6527.3.1.2.48.67.1.7

Object

The value of tIPsecClientDBClientIdIdiValue specifies the IDi value
within the client ID for this IPsec client entry.
              
A client ID may consist of more than one values (e.g., IDi (i.e.,
tIPsecClientDBClientIdIdiValue), peer IP prefix (i.e.,
tIPsecClientDBClientIdPeerPfx)). Which type of values a client ID
contains is configured by tIPsecClientDatabaseMatchType in the
associated entry of tIPsecClientDatabaseTable.
              
This value must be set in the same SNMP SET PDU as
tIPsecClientDBClientIdIdiType.
              
When the value of tIPsecClientDBClientIdIdiType is 'none (1)', 'any
(2)', 'ipv4PfxAny (4)' or 'ipv6PfxAny (6)', the value of
tIPsecClientDBClientIdIdiValue is ignored.

Context

MIB
TIMETRA-IPSEC-MIB
OID
.1.3.6.1.4.1.6527.3.1.2.48.67.1.7
Type
column
Access
readwrite
Status
current
Parent
tIPsecClientDBClientEntry
Groups
1

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 'TIMETRA-IPSEC-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-IPSEC-MIB::tIPsecClientDBClientIdIdiValue'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'TIMETRA-IPSEC-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-IPSEC-MIB::tIPsecClientDBClientIdIdiValue.<tIPsecClientDatabaseName>.<tIPsecClientDBClientIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-IPSEC-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-IPSEC-MIB::tIPsecClientDBClientIdIdiValue'

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

Conformance