---
oid: "1.3.6.1.4.1.9.9.10.1.1.4.1.1.8"
short-description: "ciscoFlashPartitionStatus OBJECT-TYPE"
last-modified: "2020-03-30"
parent-oid: "1.3.6.1.4.1.9.9.10.1.1.4.1.1"
---

## OID: `1.3.6.1.4.1.9.9.10.1.1.4.1.1.8`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 9 ciscoMgmt(9) ciscoFlashMIB(10) ciscoFlashMIBObjects(1) ciscoFlashDevice(1) ciscoFlashPartitions(4) ciscoFlashPartitionTable(1) ciscoFlashPartitionEntry(1) ciscoFlashPartitionStatus(8)}
```

### Description

```asn1
ciscoFlashPartitionStatus OBJECT-TYPE
SYNTAX INTEGER {
readOnly(1),
runFromFlash(2),
readWrite(3)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Flash partition status can be :
* readOnly if device is not programmable either because
chips could not be recognized or an erroneous mismatch
of chips was detected. Chip recognition may fail either
because the chips are not supported by the system,
or because the Vpp voltage required to identify chips
has been disabled via the programming jumper.
The ciscoFlashDeviceProgrammingJumper, ciscoFlashChipCode,
and ciscoFlashChipDescr objects can be examined to get
more details on the cause of this status
* runFromFlash (RFF) if current image is running from
this partition.
The ciscoFlashPartitionUpgradeMethod object will then
indicate whether the Flash Load Helper can be used
to write a file to this partition or not.
* readWrite if partition is programmable."
```

**Classification:** MIB object for network management

### Child OIDs

No child OID

### Terms of Use

[Terms of use](https://oid-base.com/disclaimer.htm.md)

**Note to implementers:**: The OID repository is constantly updated but does not necessarily store the latest (or most accurate) version of this formal description. For an implementation, it is recommended to search the web for a more recent description. If this is the case, please update the above description.