---
oid: "1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.4"
short-description: "ciscoFlashFileStatus OBJECT-TYPE"
last-modified: "2020-03-30"
parent-oid: "1.3.6.1.4.1.9.9.10.1.1.4.2.1.1"
---

## OID: `1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.4`

```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) ciscoFlashFiles(2) ciscoFlashFileTable(1) ciscoFlashFileEntry(1) ciscoFlashFileStatus(4)}
```

### Description

```asn1
ciscoFlashFileStatus OBJECT-TYPE
SYNTAX INTEGER {
deleted(1),
invalidChecksum(2),
valid(3)}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Status of a file.
A file could be explicitly deleted if the file system
supports such a user command facility. Alternately,
an existing good file would be automatically deleted
if another good file with the same name were copied in.
Note that deleted files continue to occupy prime
Flash real estate.
A file is marked as having an invalid checksum if any
checksum mismatch was detected while writing or reading
the file. Incomplete files (files truncated either
because of lack of free space, or a network download
failure) are also written with a bad checksum and
marked as invalid."
```

**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.