Issues with entering CCO details in CSPC 2.11

[david]

Hi team,

We have jsut deployed a CSPC 2.11 VM on ESXi 7.0.3.  Having issues when entering CCO credentials to allow for checks of software updates.  Error message advises vailidation of the credentials failed.  Have attempted to setup the same via CLI and get the same error.

Have had someone else within the team logon and use their details and getting the same error displayed.  Happy to share the followign in a PM to Cisco Contact if required:

1. CCOID/Email Address
2. Company Name:
3. CR-Party ID:
4. Company Address:

Here is a screen grab of the error

[JENS PETER POULSEN]

I had the same problem, but cloud activte account from CLI with conf server enable

[david]

Hi @JENS PETER POULSEN

We have tried that also but it isn't working for us.

[juanfsan]

Hi David,

would you kindly let me know the following information of the user that has been running into the issue?

1. CCOID/Email Address
2. Company Name:
3. CR-Party ID:
4. Company Address:

[david]

Requested information has been provided via a PM

[juanfsan]

Hi David,

I reviewed the information in depth, this is not an API support issue it seems the issue is in the collector itself. I am looking into it.

[david]

I've been chasing the Cisco Engineer assigned to this issue for an update for the best part of 8 weeks now via DM, and I'm not getting any response.  I can see others have posted about the same issue affecting their 2.11 installs, and they also don't appear to have a resolution to the issue.

How can I escalate this issue further please?

[maareval]

Hello David,
For sure, let's work with you, I have some details about your account and collector. I would like to confirm some additional things to move forward. please ping me in an internal message.

[david]

Many thanks

[metinvestnet]

I found a workaround, enable server connection via CLI.

[david]

Thanks for the response.  You will see above that we have tried via the CLI and this didn't work for us.  Still working with TAC on this issue.  They have been provided with various logs and we are awaiting a response.

[maareval]

yes, Mr. David, we are validating the Logs, however, could you confirm what final purpose of enabling the server? the question is because the "server connection" is needed for upgrading CSPC to the latest version, and has no impact on CSPC's other functionality. currently, the options available to do upgrades are by CLI only (GUI upgrade is not available) // v2.11

[metinvestnet]

GUI upgrade not working (for me) from version 2.7. Also never been successfully upgrade via application shell (by admin).
I using CLI root access for upgrading:

• manual download update from software.cisco.com
• ./install.sh JeOS <jeos-update-file.zip>
• ./install.sh SP <sp-update-file.zip>

[david]

The upgrade to 2.11 from previous versions is to deploy a new CSPC server, take a backup of the old server data, restore this to the 2.11 server using the cspc210backupscript.zip script (or reconfigure the server discovery from scratch).  This is due to changes in the underlying OS for CSPC.

[david]

Hi Marie

Yes the reason to get this configured is to stop the popup message every time you access the CSPC Server via the GUI, and to ensure checks are undertaken for updates.  Previously we have undertaken upgrades via the GUI.  If this is not available and con only be completed via the CLI I was not aware of this.  I've not seen this in any documentation and it hasn't been mentioned as part of the activities undertaken so far on the case.