l2tpDomainConfigStorageType

Object

column r/w SNMPv2-TCStorageType

The storage type for this conceptual row.
              
Conceptual rows having the value 'permanent' must
allow write-access at a minimum to:
              
- l2tpDomainConfigAdminState and
              
  l2tpDomainConfigDrainTunnels at all times
- l2tpDomainConfigSecret if l2tpDomainConfigAuth
  has been configured as 'challenge'
              
It is an implementation issue to decide if a SET for
a readOnly or permanent row is accepted at all. In some
contexts this may make sense, in others it may not. If
a SET for a readOnly or permanent row is not accepted
at all, then a 'wrongValue' error must be returned.

Context

MIB: L2TP-MIB
OID: .1.3.6.1.2.1.10.95.1.2.1.15
Type: column
Access: readwrite
Status: current
Parent: l2tpDomainConfigEntry
Groups: 1

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 'L2TP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'L2TP-MIB::l2tpDomainConfigStorageType'

More examples

Read one indexed instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'L2TP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'L2TP-MIB::l2tpDomainConfigStorageType.<l2tpDomainConfigId>'

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'L2TP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'L2TP-MIB::l2tpDomainConfigStorageType'

Syntax

SNMPv2-TCStorageType

Source: SNMPv2-TCStorageType
Base type: Enumeration

Type Description

Describes the memory realization of a conceptual row.  A
row which is volatile(2) is lost upon reboot.  A row which
is either nonVolatile(3), permanent(4) or readOnly(5), is
backed up by stable storage.  A row which is permanent(4)
can be changed but not deleted.  A row which is readOnly(5)
cannot be changed nor deleted.
          
If the value of an object with this syntax is either
permanent(4) or readOnly(5), it cannot be written.
Conversely, if the value is either other(1), volatile(2) or
nonVolatile(3), it cannot be modified to be permanent(4) or
readOnly(5).  (All illegal modifications result in a
'wrongValue' error.)
          
Every usage of this textual convention is required to
specify the columnar objects which a permanent(4) row must
at a minimum allow to be writable.

Values & Constraints

Type Values

`1`	other
`2`	volatile
`3`	nonVolatile
`4`	permanent
`5`	readOnly

Object

Context

Net-SNMP examples

Syntax

Values & Constraints

Conformance