All MIBs › LANCITY-MCNS-MIB › lcFlashPersistenceSwitch
lcFlashPersistenceSwitch
Module: LANCITY-MCNS-MIB
OID (symbolic): LANCITY-MCNS-MIB::lcFlashPersistenceSwitch
OID (numeric): 1.3.6.1.4.1.482.60.7.12
Node type: OBJECT-TYPE
Type: Bits
Access: read-write
Description: Specifies the flash persistence behavior of the associated MIB objects.
lcFlashPersistenceSwitch MIB object is itself saved to flash. At modem startup, the value of lcFlashPersistenceSwitch is read from flash and used to determine how to initialize the associated MIB objects. At runtime, lcFlashPersistenceSwitch is used to determine whether or not modifications made to the enumerated MIB objects are saved to flash.
The factory default is no bits set; thus, none of the enumerated MIB objects are initialized from flash, and subsequent modifications to the enumerated MIB objects are not saved to flash.
If a bit value is set at startup, the associated MIB object will be initialized from flash memory, and subsequent modifications will be saved to flash. If a bit is set at runtime, the associated MIB object is immediately written to flash, and subsequent modifications will be saved to flash.
If a bit value is not set at startup, factory default values will be used to initialize the associated MIB object, and subsequent modifications will not be saved to flash memory. If a bit is cleared during runtime, subsequent modifications to the associated MIB object will not be saved to flash.
The nmAccess(0) bit effects the docsDevNmAccessTable. The llcIpFilters(1) bit effects docsDevFilterLLCDefault, docsDevFilterLLCTable, docsDevFilterIpDefault, and docsDevFilterIpTable.
What is lcFlashPersistenceSwitch?
Read-write bitmask -- nmAccess(0) and llcIpFilters(1) -- controlling whether the docsDevNmAccessTable and the LLC/IP filter tables (docsDevFilterLLCDefault/Table, docsDevFilterIpDefault/Table) are initialized from flash at startup and have their runtime changes saved back to flash. This switch object is itself saved to flash; with no bits set (the factory default) neither table is loaded from or saved to flash, so changes to those objects don't survive a reboot unless the relevant bit is turned on.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.482.60.7.12 snmpwalk -v2c -c public <target> LANCITY-MCNS-MIB::lcFlashPersistenceSwitch
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.482.60.7.12.1 snmpget -v2c -c public <target> LANCITY-MCNS-MIB::lcFlashPersistenceSwitch.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.482.60.7.12.1 s <value>
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> lcFlashPersistenceSwitch.1
Start monitoring LanCity/Bay Networks CMTS head-end or cable modem (MCNS/DOCSIS-style) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LANCITY-MCNS-MIB::lcFlashPersistenceSwitch OID value, configure state conditions and alerts, and monitor any LanCity/Bay Networks CMTS head-end or cable modem (MCNS/DOCSIS-style) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.482 | lancity | LANCITY-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.482.60 | lancityMcnsMib | LANCITY-MCNS-MIB |
| 1.3.6.1.4.1.482.60.7 | lcdevicecommon | LANCITY-MCNS-MIB |
| 1.3.6.1.4.1.482.60.7.12 | lcFlashPersistenceSwitch | LANCITY-MCNS-MIB |