ipsecPeerPeerIds – FEC-IPSEC-MIB – Observium MIB Browser

Object

column r/w SNMPv2-TCDisplayString

The IDs of the peer which are accepted for authentication.
Syntax:
  - X500 distinguished name:
    <obj-name=obj-value, obj-ID=obj-value, ...>
  - IPV4-Address:
    |123.456.789.012| with or without '|'
  - IPV4 Address Range (only IKEv1):
    |123.456.789.012-123.456.789.013| with or without '|'
  - IPV4 Address Subnet (only IKEv1):
    |123.456.789.012/255.255.255.0| with or without '|'
    or:
    |123.456.789.012/24| with or without '|'
  - Key-ID: arbitrary string:
    {anything}
  - Fully Qualified User Name (FQUN) (for IKEv1) or
    Fully-qualified RFC 822 email address string (for IKEv2):
    (anything) or user@domain with mandatory '@'
  - Fully Qualified Domain Name (FQDN):
    [anything] or any name without '@' not matching any other
    syntax

Context

MIB: FEC-IPSEC-MIB
OID: .0.5.1.5
Type: column
Access: readwrite
Status: current
Parent: ipsecPeerEntry

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 'FEC-IPSEC-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FEC-IPSEC-MIB::ipsecPeerPeerIds'

More examples

Read one indexed instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'FEC-IPSEC-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FEC-IPSEC-MIB::ipsecPeerPeerIds.<ipsecPeerTrafficList>'

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'FEC-IPSEC-MIB' -M '/opt/observium/mibs/bintec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FEC-IPSEC-MIB::ipsecPeerPeerIds'

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