File checksum stored in the file header. This
checksum is computed and stored when the file is
written into Flash. It serves to validate the data
written into Flash.
Whereas the system will generate and store the checksum
internally in hexadecimal form, this object will
provide the checksum in a string form.
The checksum will be available for all valid and
invalid-checksum files.
Parsed from file CISCO-FLASH-MIB.mib
Module: CISCO-FLASH-MIB
File checksum stored in the file header. This
checksum is computed and stored when the file is
written into Flash. It serves to validate the data
written into Flash.
Whereas the system will generate and store the checksum
internally in hexadecimal form, this object will
provide the checksum in a string form.
The checksum will be available for all valid and
invalid-checksum files.
ciscoFlashFileChecksum OBJECT-TYPE
SYNTAX ChecksumString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"File checksum stored in the file header. This
checksum is computed and stored when the file is
written into Flash. It serves to validate the data
written into Flash.
Whereas the system will generate and store the checksum
internally in hexadecimal form, this object will
provide the checksum in a string form.
The checksum will be available for all valid and
invalid-checksum files.
"
View at oid-info.com
File checksum stored in the file header. This
checksum is computed and stored when the file is
written into Flash. It serves to validate the data
written into Flash.
Whereas the system will generate and store the checksum
internally in hexadecimal form, this object will
provide the checksum in a string form.
The checksum will be available for all valid and
invalid-checksum files.
Parsed from file cisco-flash.mib.txt
Company: None
Module: CISCO-FLASH-MIB
File checksum stored in the file header. This
checksum is computed and stored when the file is
written into Flash. It serves to validate the data
written into Flash.
Whereas the system will generate and store the checksum
internally in hexadecimal form, this object will
provide the checksum in a string form.
The checksum will be available for all valid and
invalid-checksum files.
ciscoFlashFileChecksum OBJECT-TYPE SYNTAX ChecksumString MAX-ACCESS read-only STATUS current DESCRIPTION "File checksum stored in the file header. This checksum is computed and stored when the file is written into Flash. It serves to validate the data written into Flash. Whereas the system will generate and store the checksum internally in hexadecimal form, this object will provide the checksum in a string form. The checksum will be available for all valid and invalid-checksum files." ::= { ciscoFlashFileEntry 3 }
ciscoFlashFileChecksum OBJECT-TYPE SYNTAX ChecksumString ACCESS read-only STATUS mandatory DESCRIPTION "File checksum stored in the file header. This checksum is computed and stored when the file is written into Flash. It serves to validate the data written into Flash. Whereas the system will generate and store the checksum internally in hexadecimal form, this object will provide the checksum in a string form. The checksum will be available for all valid and invalid-checksum files." ::= { ciscoFlashFileEntry 3 }
Automatically extracted from Cisco "SNMP v2 MIBs".
ciscoFlashFileChecksum OBJECT-TYPE SYNTAX ChecksumString MAX-ACCESS read-only STATUS current DESCRIPTION "File checksum stored in the file header. This checksum is computed and stored when the file is written into Flash. It serves to validate the data written into Flash. Whereas the system will generate and store the checksum internally in hexadecimal form, this object will provide the checksum in a string form. The checksum will be available for all valid and invalid-checksum files. " ::= { ciscoFlashFileEntry 3 }
ciscoFlashFileChecksum OBJECT-TYPE SYNTAX ChecksumString MAX-ACCESS read-only STATUS current DESCRIPTION "File checksum stored in the file header. This checksum is computed and stored when the file is written into Flash. It serves to validate the data written into Flash. Whereas the system will generate and store the checksum internally in hexadecimal form, this object will provide the checksum in a string form. The checksum will be available for all valid and invalid-checksum files." ::= { ciscoFlashFileEntry 3 }
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
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.4 | ciscoFlashFileStatus | 0 | 0 | Status of a file. A file could be explicitly deleted if the file system supports such a user command facility. Alternately, an exi… |
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. |