It’s always a good idea to calculate an MD5 or SHA1 file checksum to validate file integrity after download or transfer, especially when dealing with firmware binaries. While most modern systems are smart enough to validate images before attempting an installation, not all are so wise, and I’m sure I’m not the only one to have seen a device bricked (or stuck in ROMMON or a similar bootloader or equivalent) after a bad image was uploaded.

Here’s a quick reference guide to creating file checksums on Macos (OSX), Windows and Linux.
There are various ways to check md5/sha1 checksums depending on your preferred platform. Vendors tend to publish the MD5 or SHA1 checksums (or both) for downloadable files, so it’s silly not to do checksum validation and confirm that the file has downloaded completely and uncorrupted. I try to validate after each time I transfer a file so that I don’t waste time sending a corrupted file on to the next hop. For example:
Delta's recent IT failures put spotlight on the faulty nature of enterprise disaster recovery planning.
The post Worth Reading: Quantum safe glossary appeared first on 'net work.
As many as 1 million tech workers hold H-1B visas.
Microsoft Azure appears to be gaining steam.
A weak Q3 is now a distant memory.
Some ISR routers and Nexus 9000 switches impacted by faulty component from Cisco supplier.
My two LiveLessons are currently on sale at Pearson sites. Use the code RW60 to receive the discount. The sale price, $79 for each one, is available until the 15th of March.
The post LiveLessons on Sale appeared first on 'net work.