Reference record for OID 1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.4



parent
1.3.6.1.4.1.9.9.10.1.1.4.2.1.1 (ciscoFlashFileEntry)
node code
4
node name
ciscoFlashFileStatus
dot oid
1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.4
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoFlashMIB(10) ciscoFlashMIBObjects(1) ciscoFlashDevice(1) ciscoFlashPartitions(4) ciscoFlashFiles(2) ciscoFlashFileTable(1) ciscoFlashFileEntry(1) ciscoFlashFileStatus(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoFlashMIB(10) ciscoFlashMIBObjects(1) ciscoFlashDevice(1) ciscoFlashPartitions(4) ciscoFlashFiles(2) ciscoFlashFileTable(1) ciscoFlashFileEntry(1) ciscoFlashFileStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoFlashMIB(10) ciscoFlashMIBObjects(1) ciscoFlashDevice(1) ciscoFlashPartitions(4) ciscoFlashFiles(2) ciscoFlashFileTable(1) ciscoFlashFileEntry(1) ciscoFlashFileStatus(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoFlashMIB(10) ciscoFlashMIBObjects(1) ciscoFlashDevice(1) ciscoFlashPartitions(4) ciscoFlashFiles(2) ciscoFlashFileTable(1) ciscoFlashFileEntry(1) ciscoFlashFileStatus(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cisco(9) ciscoMgmt(9) ciscoFlashMIB(10) ciscoFlashMIBObjects(1) ciscoFlashDevice(1) ciscoFlashPartitions(4) ciscoFlashFiles(2) ciscoFlashFileTable(1) ciscoFlashFileEntry(1) ciscoFlashFileStatus(4)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cisco(9) ciscoMgmt(9) ciscoFlashMIB(10) ciscoFlashMIBObjects(1) ciscoFlashDevice(1) ciscoFlashPartitions(4) ciscoFlashFiles(2) ciscoFlashFileTable(1) ciscoFlashFileEntry(1) ciscoFlashFileStatus(4)}
    • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoFlashMIB/ciscoFlashMIBObjects/ciscoFlashDevice/ciscoFlashPartitions/ciscoFlashFiles/ciscoFlashFileTable/ciscoFlashFileEntry/ciscoFlashFileStatus
  • /iso/identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoFlashMIB/ciscoFlashMIBObjects/ciscoFlashDevice/ciscoFlashPartitions/ciscoFlashFiles/ciscoFlashFileTable/ciscoFlashFileEntry/ciscoFlashFileStatus
  • /iso/org/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoFlashMIB/ciscoFlashMIBObjects/ciscoFlashDevice/ciscoFlashPartitions/ciscoFlashFiles/ciscoFlashFileTable/ciscoFlashFileEntry/ciscoFlashFileStatus
  • /iso/org/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoFlashMIB/ciscoFlashMIBObjects/ciscoFlashDevice/ciscoFlashPartitions/ciscoFlashFiles/ciscoFlashFileTable/ciscoFlashFileEntry/ciscoFlashFileStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprise/cisco/ciscoMgmt/ciscoFlashMIB/ciscoFlashMIBObjects/ciscoFlashDevice/ciscoFlashPartitions/ciscoFlashFiles/ciscoFlashFileTable/ciscoFlashFileEntry/ciscoFlashFileStatus
  • /iso/iso-identified-organization/dod/internet/private/enterprises/cisco/ciscoMgmt/ciscoFlashMIB/ciscoFlashMIBObjects/ciscoFlashDevice/ciscoFlashPartitions/ciscoFlashFiles/ciscoFlashFileTable/ciscoFlashFileEntry/ciscoFlashFileStatus
    • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/9/9/10/1/1/4/2/1/1/4

    Description by circitor

    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.

    Parsed from file CISCO-FLASH-MIB.mib
    Module: CISCO-FLASH-MIB

    Description by cisco_v1

    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.

    Description by oid_info

    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.
    "
    View at oid-info.com

    Description by mibdepot

    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.

    Parsed from file cisco-flash.mib.txt
    Company: None
    Module: CISCO-FLASH-MIB

    Description by cisco

    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.

    Information by circitor

    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."
    ::= { ciscoFlashFileEntry 4 }

    Information by cisco_v1

    ciscoFlashFileStatus OBJECT-TYPE
    SYNTAX INTEGER {
        deleted(1),
        invalidChecksum(2),
        valid(3)
        }
    ACCESS read-only
    STATUS mandatory
    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."
    ::= { ciscoFlashFileEntry 4 }

    Information by oid_info

    Automatically extracted from Cisco "SNMP v2 MIBs".

    Information by mibdepot

    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.
                "
        ::= { ciscoFlashFileEntry 4 }

    Information by cisco

    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." 
    ::= { ciscoFlashFileEntry 4 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Greg Satz

    Current Registration Authority (recovered by parent 1.3.6.1.4.1.9)

    Cisco Systems, Inc.

    Brothers (6)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.1 ciscoFlashFileIndex 0 0 Flash file sequence number used to index within
    a Flash partition directory table.
    1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.2 ciscoFlashFileSize 0 0 Size of the file in bytes. Note that this size does
    not include the size of the filesystem file header.
    File size will always be …
    1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.3 ciscoFlashFileChecksum 0 0 File checksum stored in the file header. This
    checksum is computed and stored when the file is
    written into Flash. It serves to v…
    1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.5 ciscoFlashFileName 0 0 Flash file name as specified by the user copying in
    the file. The name should not include the colon (:)
    character as it is a spec…
    1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.6 ciscoFlashFileType 0 0 Type of the file.
    1.3.6.1.4.1.9.9.10.1.1.4.2.1.1.7 ciscoFlashFileDate 0 0 The time at which this file was created.