transportTlsVersion – MX-SIPEP-MIB – Observium MIB Browser

Object

scalar r/w Enumeration

TLS Version
          
Defines the allowed TLS versions when using TLS persistent
connections.
          
  * SSLv3: Allow SSL version 3 and all TLS versions.
  * TLSv1: Allow TLS versions 1 and up.
  * TLSv1_1: Allow TLS versions 1.1 and up.
  * TLSv1_2: Allow TLS versions 1.2 and up.
          
The device will always send its highest supported TLS version
in the ClientHello message. The server will select the highest
supported TLS version it supports from the ClientHello
message. The device will then validate that the selected
version is allowed. If the version is not allowed the device
will close the connection.

Context

MIB: MX-SIPEP-MIB
OID: .0.1400.1.900.95
Type: scalar
Access: readwrite
Status: current
Parent: transportGroup

Net-SNMP examples

How SNMP and these commands work

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

Read the scalar instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'MX-SIPEP-MIB' -M '/opt/observium/mibs/media5:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MX-SIPEP-MIB::transportTlsVersion.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'MX-SIPEP-MIB' -M '/opt/observium/mibs/media5:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MX-SIPEP-MIB::transportTlsVersion'

Syntax

Enumeration

Values & Constraints

Enumerated Values

`100`	sSLv3
`200`	tLSv1
`300`	tLSv1-1
`400`	tLSv1-2