10-18-2013 07:39 AM
I created a 4.3.2 tarball to upgrade a series of ASR9001 and 9006's running 4.3.0.
This file worked fine upgrading 2x ASR9001 routers, I ran the install with the activate keyword, it unpacked, installed and activated on both routers without issue.
But on the ASR9006, with the same tarball some of the packages would not unpack. I had to tftp the individual packages from another router, and install individually.
The obvious thing to check was for tarball corruption during TFTP, I checked the MD5 checksums and they match on for the original tarball for the file on my PC and on different routers, so I am sure of the files integrity.
Anyone else seen this?
10-18-2013 08:11 AM
Hi,
Can you provide some more details?
Thanks,
Sam
11-01-2013 02:41 AM
Hi, it turned out to be a corrupt file, dont know how it slipped through the MD5 checksum verification, but its fixed now.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide