Hopefully someone can shed some light on what I am doing wrong as this is getting %^$R&$ frustrating
I have both a Cisco 4230 and 4210 sensor which I have upgraded to 4.1 (1) S47 from version 3 using the Cisco provided Recovery/Upgrade CD. The 4210 has the additional 256Mb of RAM for a total of 512Mb.
Once upgraded to 4.1 (1) S47 I then attempted to apply 4.1 (3) S61 with no luck - the file would appear to download, the sensor would restart but the version always appeared as 4.1 (1) S47
Thinking that an earlier SP may be required I downloaded 4.1 (2) S58 and tried to upgrade both sensors via CLI and Web interface - downloads the file from FTP, reboots but still 4.1 (1) S47
FTP server is SERV-U V5 - logs show sensor downloading file correctly
Look at the output of show tech support (even easier to read is the diagnostics run from with in IDM since it will be html formatted and contain the same information).
If I remember correctly there will be an area that pulls information from logs that are made during the update. You could check these logs for any possible errors.
From your posting there is one thing that does pop out. In the command: upgrade ftp://firstname.lastname@example.org//updates/ids-k9-sp-4.1-
All of the letters are lower case. This will cause problems. The sensor is a Linux OS and does treat capital letters differently than lower case letters (unlike Windows).
The sensor is probably detecting that the file has been renamed, and is unable to properly execute it.
What to do: Be sure the filename on your FTP has the exact name (including capitalization) for the file as it is listed on CCO. Be sure to use this exact name (including capitalization) when executing the upgrade command.
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 :