cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4643
Views
0
Helpful
18
Replies

Unable to upload to backend

Mark Best
Level 1
Level 1

After upgraded from CSPC 2.5 to 2.6 I can no longer upload my files to concsoweb-prd.cisco.com.

There are no blocks in the firewall, and I can use NetCat to verify connectivity on 443/80/5222 etc. But using the web interface I get an error 'Unable to upload to backend'. (See Attached Screenshot)

************

Netcat

************

([root@h1867 ~]# nc -v 72.163.7.138 5222
Connection to 72.163.7.138 5222 port [tcp/xmpp-client] succeeded!
[root@h1867 ~]# nc -v 72.163.7.138 5222443 443
Connection to concsoweb-prd.cisco.com 443 port [tcp/https] succeeded!
([root@h1867 ~]# nc -v concsoweb-prd.cisco.com 80
Connection to concsoweb-prd.cisco.com 80 port [tcp/http] succeeded!
[root@h1867 ~]# nc -v concsoweb-prd.cisco.com 80www
Connection to www.cisco.com 80 port [tcp/http] succeeded!
[root@h1867 ~]# nc -v www.cisco.com 80
Connection to dl.cisco.com 80 port [tcp/http] succeeded!
[root@h1867 ~]# nc -v dl.cisco.com 80
Connection to dl1.cisco.com 80 port [tcp/http] succeeded!
[root@h1867 ~]# nc -v dl1.cisco.com 80
Connection to dl2.cisco.com 80 port [tcp/http] succeeded!
[root@h1867 ~]# nc -v dl2.cisco.com 80
Connection to sso.cisco.com 80 port [tcp/http] succeeded!

[root@h1867 ~]# nc -v 198.133.219.53 21
Connection to 198.133.219.53 21 port [tcp/ftp] succeeded!
220 (vsFTPd 2.2.2)

[root@h1867 ~]# nc -v 72.163.7.113 443
Connection to 72.163.7.113 443 port [tcp/https] succeeded!


************
I copied the ZIP file to my Workstation and unzipped it successfully.

*************

[root@h1867 326_1]# ls
transport-inventory-CSP0009026923-1484001684285.zip
[root@h1867 326_1]# pwd
/opt/cisco/ss/adminshell/applications/CSPC/uploaddata/_CORP_2016/326_1

************
/etc/hosts

*************
72.163.9.100 nettools-upload.cisco.com
192.135.250.12 nettools-upload.cisco.com
64.103.36.134 nettools-upload.cisco.com
72.163.7.113 concsoweb-prd.cisco.com
173.37.186.17 concsoweb-prd.cisco.com
72.163.4.161 www.cisco.com
72.163.7.60 dl.cisco.com
72.163.7.60 dl1.cisco.com
173.37.146.12 dl2.cisco.com
173.37.144.208 sso.cisco.com

::1     localhost.localdom localhost localhost ip6-localhost ip6-loopback
127.0.0.1    localhost    h1867 h1867.corp.com


*************
nohup.out

*************
I'm not sure if there is a legitimate error from this file. I suspect its a CCO login problem? (I don't want to FTP the files so I'm not worried about creating a directory. )

Can someone point me in the right direction?

18 Replies 18

Please see attached picture.  I need to make a report to the management as to the status of this issue.  Again, nothing inside this solution is working at the moment and so the product is at this moment completely useless. 

Thank you for the screenshot.

Looking at the transport file name, it looks like the collector ID (CSP***) might belong to a deleted license file.

Can you please confirm that the license file on the collector is active on your account?

Regards,

Cesar

Cesar,

  Back on 1/9/17 I re-entitled the CSPC but as you noticed it didn't stick for some reason.  Perhaps I forgot to reboot.  I have now confirmed (as per the attached screen shots) that the CSPC and SNTC entitlements match, however I am still receiving the Upload Processing error. Manual uploading is again working as expected.  Thanks. 

I have begrudgingly exported the CSPC upload data and manually imported to the SNTC portal.  I don't like this, how long until a fix?  Is Prime going to start playing a bigger role in the Collection/Upload process?