Customer is having issues with VM SNTC collector

[carrkell]

Team,

Our customer is having issues with their VM SNTC collector.  Can the team advise?

'Brent Forrest' <Brent.Forrest@enlink.com>  CCO user Brent.Forrest@enlink.com

Cisco CSP Collector 2.3

SNTC1XSN00000000376 (Serial number, and I think I put in enough zero’s)

Appliance ID – CSP0009010150

Per customer:

Carrie,

Can you assist on this?  We need to open a TAC ticket for the SNTC VM we put in a couple of years ago.  Might needs to be patched, because if we are in the web gui for an extended amount of time and making changes the appliance will freeze up and require a reboot.

Thanks,

Carrie

[Lynden Price]

Hi carrkell,

I would recommend deploying a new 2.5 OVA and transferring over their information.

Log into your 2.3 collector:

1. Reports > Managed Devices, select the blue export arrow. Export the managed device list in CSV format.
2. Settings > Device Credentials, select the export button. Choose pari xml format.
3. If you’ve set up local users or remote authentication, then make a note of those settings from Administration > Manage Users and Administration > Manage Remote Authentication Servers

Follow the instructions for deploying the 2.5 OVA:

https://supportforums.cisco.com/blog/12696871/self-service-onboarding-setting-cspc-25-collector

Log into your 2.5 collector:

1. Settings > Device Credentials, select “Import”. From the drop down, choose pari xml format. Browse to the exported credentials and select them. Give the job a name and click “OK”.
2. Open the csv of your managed devices in Excel. Copy the column of IP addresses. In the collector, go to Management > Discover and Manage Devices. Select “Discover by known IP address”. Click “Next”. Paste the column of IP addresses into the entry box and then click the “Add” button. Click “Next”. Select the correct version of SNMP, and finish.
3. Add any user accounts or remote authentication servers by going to Administration > Manage Users and Administration > Manage Remote Authentication Servers

Thanks,

Lynden