cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1578
Views
0
Helpful
13
Replies

upgrade from 2.7.2 to 2.7.3.2 gets stuck " Apply-in progress"

Cisco Service
Level 1
Level 1

Hi,

 

Trying to upgrade from 2.7.2 to 2.7.3.2, but gets stuck in "Apply-in-progress"

Tried to restart CSCP and upgrade from CLI, but same problem.

 

Any ideas ?

13 Replies 13

Hello,

We'll have an expert reply shortly.

Cheers,

Cheri

Supriya Patel
Cisco Employee
Cisco Employee

Hi User,

 

Please check Here under section 'Enable Upgrades using LCM Software Updates' and let me know if you have any question.

 

Thanks,

Supriya

Hi,

 

I have tried upgrading both using GUI and CLI, but same result.

Upgrade dosen't work

Below upgrade info :


admin# upgrade

Version Description
-------------------------------------------------------
sp-30.0.3-2-0-lnx64 Collector patch to upgrade to CSPC 2.7.3.2

Download and apply of a package can take a while.
It is recommended to schedule the upgrade.

Do you want to continue [y|n] ?y
Please enter the version to upgrade :sp-30.0.3-2-0-lnx64

Do you want to continue with download and apply [y|n] ?y
Connection to Software Download Server will use User Id 'xxxx@xxxx.dk'.

In order to download software, please indicate that you have read and agree
to be bound by the Cisco End User License Agreement which can be viewed at
http://www.cisco.com/en/US/docs/general/warranty/English/EU1KEN_.html

Accept License Agreement (y|n)? y

Attempting to download the requested package.....sp-30.0.3-2-0-lnx64
Download of package has been initated.
admin# Connection to 10.0.6.43 closed by remote host.

 

 

After a while server responds again and I can login.

But when i check update info, no upgrade has been applied :

 

admin# show update history

Package Applied Date
----------------------------------------------------------

sp-30.0.2-0-0-lnx64 Sep/11/2017 13:42:08
sp-30.0.1-0-0-lnx64 Jun/19/2017 12:29:50
sp-30.0.0-0-0-lnx64 Jun/13/2017 11:23:54

 

 

HI user,

 

Could you please send me 'show version -d' and 'show download'

 

Thanks,

Supriya


admin# show version -d
Build-name : Collection Platform Software 2.7.2

Package-type : ServicePack
Version : sp-30.0.2-0-0-lnx64
Component : CSPC Base
Version : 2.7.2
Package-type : JeOS
Version : jeos-30.0.3-2-lnx64
Component : ConcsoTgw
Version : 1.7.0
Component : AdminShell
Version : 1.6
Component : Hardened CentOS
Version : 6.8 patch#0
Component : LCM
Version : 1.6
Component : CASP
Version : 2.7.3.2
admin#
admin#
admin# show download
Version : sp-30.0.0-0-0-lnx64
Download Location : /opt/LCM/tmp/sp-30.0.0-0-0-lnx64-package.zip
Status : Downloaded
Start Time : Jun/13/2017 10:01:36
End Time : Jun/13/2017 10:45:12
Reason For Failure : -

Version : sp-30.0.1-0-0-lnx64
Download Location : /opt/LCM/tmp/sp-30.0.1-0-0-lnx64-package.zip
Status : Downloaded
Start Time : Jun/19/2017 11:21:06
End Time : Jun/19/2017 11:52:11
Reason For Failure : -

Version : sp-30.0.2-0-0-lnx64
Download Location : /opt/LCM/tmp/sp-30.0.2-0-0-lnx64-package.zip
Status : Downloaded
Start Time : Sep/11/2017 12:24:09
End Time : Sep/11/2017 12:57:11
Reason For Failure : -

Version : sp-30.0.2-5-0-lnx64
Download Location : /opt/LCM/tmp/sp-30.0.2-5-0-lnx64-package.zip
Status : Downloaded
Start Time : Nov/16/2017 09:41:54
End Time : Nov/16/2017 09:46:59
Reason For Failure : -

Version : sp-30.0.3-0-0-lnx64
Download Location : /opt/LCM/tmp/sp-30.0.3-0-0-lnx64-package.zip
Status : Downloaded
Start Time : Jan/19/2018 07:33:41
End Time : Jan/19/2018 08:20:24
Reason For Failure : -

Version : sp-30.0.3-2-0-lnx64
Download Location : /opt/LCM/tmp/sp-30.0.3-2-0-lnx64-package.zip
Status : Downloaded
Start Time : Nov/29/50163 04:27:57
End Time : Mar/12/2018 12:43:22
Reason For Failure : -

HI User,

 

Please make sure if you have followed ''Enable Upgrades using LCM Software Updates' from the guide that I have provided earlier (it is good idea to enable collectorlogin and root user ahead of time as mentioned in guide).

 

Now, please follow below:

 

# apply sp-30.0.3-2-0-lnx64

# show apply

 

The download might take several hrs depending on several factors. I would recommend to check back after couple of hr using command 'show apply'.  System may reboot during this process. Please get back to me if you have any further question.

 

Thanks,
Supriya

Hi Supriya,

 

As you can see the job is still in apply process.

Also other jobs has the same status.

 

admin# show apply
Version Number : sp-30.0.0-0-0-lnx64
Status : Applied
Start Time : Jun/13/2017 10:46:49
End Time : Jun/13/2017 11:23:54

Version Number : sp-30.0.1-0-0-lnx64
Status : Applied
Start Time : Jun/19/2017 11:52:13
End Time : Jun/19/2017 12:29:50

Version Number : sp-30.0.2-0-0-lnx64
Status : Applied
Start Time : Sep/11/2017 12:57:14
End Time : Sep/11/2017 13:42:08

Version Number : sp-30.0.2-5-0-lnx64
Status : Apply-in-progress
Start Time : Nov/16/2017 09:47:12
End Time : -

Version Number : sp-30.0.3-0-0-lnx64
Status : Apply-in-progress
Start Time : Jan/19/2018 08:21:54
End Time : -

Version Number : sp-30.0.3-2-0-lnx64
Status : Apply-in-progress
Start Time : Mar/20/2018 21:12:46
End Time : -

Hi User,

 

could you please run 'show version' or 'show version -d'?

 

Thanks,

Supriya

admin# show version -d
Build-name : Collection Platform Software 2.7.2

Package-type : ServicePack
Version : sp-30.0.2-0-0-lnx64
Component : CSPC Base
Version : 2.7.2
Package-type : JeOS
Version : jeos-30.0.3-2-lnx64
Component : ConcsoTgw
Version : 1.7.0
Component : AdminShell
Version : 1.6
Component : Hardened CentOS
Version : 6.8 patch#0
Component : LCM
Version : 1.6
Component : CASP
Version : 2.7.3.2

 

Regards Kim

Hi user,

 

I just private message you, please follow the steps and update me.


Thanks,
Supriya

Hi User,

 

Thanks for updating me that TAC case is opened on this one.


Thanks,

Supriya

Customer is a service  Partner for  service SMART CARE and has a service contract for that collector and portal support. There is differences in collector from SNTC built and SMARTCARE it seems the problem at this time on his collector does refer to some networking binding issues, we we will post here if a solution is found to the problem