verify

Allows the verification of boot images based on hash codes and the generation of hash codes where needed.
Syntax
verify { md5 | sha1 | crc32 } { primary | secondary } [ string ]
Parameters
md5
Verifies the file content using an MD5 checksum and generates a 16-byte hash code.
sha1
Verifies the file content using SHA-1 and generates a 20-byte hash code.
crc32
Verifies the file content using CRC32 and generates a 4-byte hash code.
primary
Verifies the primary boot image.
secondary
Verifies the secondary boot image.
string
A valid image file name or a generated hash code value.
Modes

Privileged EXEC mode

Usage Guidelines

This feature lets you select from three data integrity verification algorithms:

  • MD5: Message-digest algorithm (RFC 1321)
  • SHA1: US Secure Hash Algorithm (RFC 3174)
  • CRC: Cyclic redundancy check algorithm

Examples

The following example shows how the verify command can be used to generate an MD5 hash value for the secondary image. 

device# verify md5 secondary
device#.........................Done
Size = 2044830, MD5 01c410d6d153189a4a5d36c955653862

The following example shows how the verify command can be used to generate a SHA-1 hash value for the secondary image. 

device# verify sha1 secondary
device#.........................Done
Size = 2044830, SHA1 49d12d26552072337f7f5fcaef4cf4b742a9f525

The following example shows how the verify command can be used to generate a CRC32 hash value for the secondary image. 

device# verify crc32 secondary
device#.........................Done
Size = 2044830, CRC32 b31fcbc0

The following example shows how the verify command can be used to verify the hash value of a secondary image with a known value. 

device# verify md5 secondary 01c410d6d153189a4a5d36c955653861
device#.........................Done
Size = 2044830, MD5 01c410d6d153189a4a5d36c955653861
Verification SUCEEDED.

The following example shows how the verify command can be used to verify the SHA-1 hash value of a secondary image with a known value. 

device# verify sha1 secondary 49d12d26552072337f7f5fcaef4cf4b742a9f525
device#.........................Done
Size = 2044830, sha 49d12d26552072337f7f5fcaef4cf4b742a9f525
Verification SUCCEEDED.

The following example shows how the verify command can be used to verify the CRC32 hash value of a secondary image with a known value. 

device# verify crc32 secondary b31fcbc0
device#.........................Done
Size = 2044830, CRC32 b31fcbc0
Verification SUCCEEDED
Parent topic: Commands Si - Z