CSPC 2.11 update fails validation check current version detection

[kingtrw]

Hi, I am trying to update a bare metal install of CSPC 2.11

From a root CLI session, I did "install.sh JeOS jeos-30.4.0-3-lnx64.zip" -- this appeared to complete successfuly, and the system restarted.

The first odd thing was that I was then no longer able to log in via SSH using admin or collectorlogin. I was able to log in locally, only via collectorlogin.

I then tried "install.sh SP sp-30.4.0-3-0-lnx64.zip" and it said it had started, but then nothing happened. I checked the log file in /opt/LCM/logs/apply and I can see that it's failing the validation check to determine the current version:

Initializing SP Patch Installation .....
current CSPC version is :   and casp version is : 2.11.0.3
Current CSPC version
SP 2.11.0.3 can install on 2.11 and above only

I suspect I may have screwed up by not installing a pre-requsite patch version beforehand (I assumed there would be a validation check for that!)

I tried to see if I the 2.11.0.1 SP patch would go on but its validation check fails with the same issue.

The GUI still works fine though, so the system isn't *completely* hosed.

Is there a way I can get it to pass the validation check? As this is a bare metal install (we only have hyper-v so can't run a CSPC VM) having to reisntall from scratch will be a huge annoyance (though I do have a backup).

Hope someone can help!

[adias]

https://software.cisco.com/download/home/286312935/type/286312958/release/2.11?i=!pp

[kingtrw]

@adiasThat's very interesting! Just released today - so I feel justified in not knowing about it! Do you know if I will be able to import the backup I took of the old appliance into this one?

[kingtrw · Accepted solution]

I don't think I'll find a fix to this particular issue - I spun up a hyper-V vm, and then restored from backup.

I then applied the patched in order (.1, then .2, then .3) and they applied as expected.

.1 and .2 both did something to the admin and collectorlogin accounts that prevented logging in via SSH until I'd reset the passwords -- .3 did not have this issue.

[adias]

I have not tested but once it is a server the backup should at the same on any virtualization