cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1327
Views
5
Helpful
3
Replies

Add NTP, DNS, etc. information

RonF
Level 1
Level 1

When creating my first collector I had to walk away from it for a while.  Later I came back and tried to enter in the NTP and DNS server IPs, the current time, etc. but it would not accept it.  I continued the installation.  Is there a way to add this information in now, either through the GUI or the CLI?  I tried logging into the server via SSH but it would not accept the administrator ID and password I created.

It occurs to me that this same process would be necessary if either of those changed - as has happened in my company before....

3 Replies 3

Justin Sprake
Cisco Employee
Cisco Employee
Hello,

Please find the below commands in order to configure NTP / DNS via the admin user (CLI):

admin# timesync
-----
[To add the dns nameserver IP]
admin# conf dns -a 192.168.1.1 192.168.2.1

[To delete the dns nameserver IP]
admin# conf dns -d 192.168.1.1 192.168.2.1

https://www.cisco.com/c/dam/en/us/support/docs/cloud-systems-management/common-services-platform-collector-cspc/CSPC-Quick-Start-Guide.pdf

Please note that between CLI and GUI there are 2 separate 'admin' accounts. The credentials for each would be unique and will not provide access to the other. Upon first configuring the CSPC via CLI you or your Server team may have been prompted to change/update the credentials.

I found out that there must be a difference between the CLI and the GUI admin ID/PW combination when I tried logging into the CLI using "admin" and the GUI password I created.  Having tried that a few times I'm now being told that "admin" is locked out (although it still works in the GUI).  Unfortunately the person who created the VM for me is out so I have no way of finding out what she used to create the CLI password, which if that message is correct will do me no good now anyway.  Unless there's some root ID/PW I can use to reset the admin ID/PW....

RonF
Level 1
Level 1

Given that I had hosed up the CLI admin ID I decided to short-circuit the issue and just had the VM blown away and a new one created.