As per v5.0 & v5.1 upgrade info, to upgrade from 4.x to the latest 5.1(1), you must first install the 5.0(1) Major Update file, followed by the 5.1(1) Minor Upgrade file. V5.0(1a) is a minor upgrade for v5.0(1) if you already load v5.0(1).
Problems were found in the upgrade file and were fixed and we were going to release the new upgrade file as 5.0(1a):
BUT the IPS software was unable to handle the letter "a" after the one when validating the filename.
So the 5.0(1a) file in order to work properly actually wound up being named exactly the same as the original 5.0(1) upgrade file:
So the IPS-K9-maj-5.0-1-S149.rpm.pkg file on CCO is actually the 5.0(1a).
The only place you see 5.0(1a) is in the name of the corresponding readme file.
So when upgrading to 5.0(1)/5.0(1a) you will just need to ensure you are using the latest IPS-K9-maj-5.0-1-S149.rpm.pkg upgrade file available on CCO.
Now when we built the 5.1(1) Minor Upgrade file we also found installation issues. So we built 5.1(1a), 5.1(1b), 5.1(1c), and 5.1(1d) upgrade files. And because we had corrected the problem whic previously prevented us from using the letters we are now able to put the letters into the filename.
So you will see on CCO that the latest 5.1(1) upgrade file is actually 5.1(1d) and that is what should be used when going from 5.0(1) to 5.1(1):
Be aware that the letter change is only in the package name. The changes made were only in the installation script of the package and not in the actual files being installed. So 5.1(1d) still installs the same files as the original 5.1(1) and so after installation a "show version" output will report 5.1(1) and not 5.1(1d).
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :