Flash image CLI commands
The following examples show how the verify command can be used in a variety of circumstances.
To generate an MD5 hash value for the secondary image, enter the following command.
device# verify md5 secondary device#.........................Done Size = 2044830, MD5 01c410d6d153189a4a5d36c955653862
To generate a SHA-1 hash value for the secondary image, enter the following command.
device# verify sha secondary device#.........................Done Size = 2044830, SHA1 49d12d26552072337f7f5fcaef4cf4b742a9f525
To generate a CRC32 hash value for the secondary image, enter the following command.
device# verify crc32 secondary device#.........................Done Size = 2044830, CRC32 b31fcbc0
To verify the hash value of a secondary image with a known value, enter the following commands.
device# verify md5 secondary 01c410d6d153189a4a5d36c955653861 device#.........................Done Size = 2044830, MD5 01c410d6d153189a4a5d36c955653862 Verification FAILED.
In the previous example, the codes did not match, and verification failed. If verification succeeds, the output will look like this.
device# verify md5 secondary 01c410d6d153189a4a5d36c955653861 device#.........................Done Size = 2044830, MD5 01c410d6d153189a4a5d36c955653861 Verification SUCEEDED.
The following examples show this process for SHA-1 and CRC32 algorithms.
device# verify sha secondary 49d12d26552072337f7f5fcaef4cf4b742a9f525 device#.........................Done Size = 2044830, sha 49d12d26552072337f7f5fcaef4cf4b742a9f525 Verification SUCCEEDED.
and
device# verify crc32 secondary b31fcbc0 device#.........................Done Size = 2044830, CRC32 b31fcbc0 Verification SUCCEEDED.