Registering an ACS 5.2 instance to a primary

[bradh]

Hi folks,

Hoping someone can assist me with this. When attempting to register an ACS instance to a primary (via System Administration -> Operations -> Local Operations -> Deployment Operations), I receive the following error as a popup in my browser:

"This System Failure occurred:  /opt/CSCOacs/db/acs.crt (No such file or directory). Your changes have not been saved.Click OK to return to the list page."

I had 2 ACS 1120 appliances clustered, 1 suffered a hardware failure about a year ago so I replaced it with a VM. That one is now the primary. I'm now wanting to replace the secondary instance (the remaining 1120 appliance) with a VM as well. I removed the current appliance from the network, installed the VM using the same IP address, and attempted to register. It failed as per the above error. After trying this a number of times, I then decided to return the 1120 appliance to secondary status and attempted to register it with the same results as above.

Any assistance with this would be much appreciated

Thanks

[Jatin Katyal · Accepted solution]

I've seen this before. This can be resolved by reloading the primary server.

In case you still see this issue

1. Log into ACS CLI w/ CLI username/pass

2. issue 'acs-config'

3. log in w/ ACS GUI username/pass

4. show debug-log. This will tell you what the levels are set at now

5. debug-log mgmt level debug

6. Reproduce the problem

7. Get the support bundle with system logs and debug logs from both the ACS.

8. Restore the logging level of mgmt to warn (debug-log mgmt level warn)

You may also filter the managment logs from both the servers and paste the relevent logs of that time frame.

Jatin Katyal
- Do rate helpful posts -

[bradh]

Reloading the primary did indeed do the trick and my cluster is back up again.

Thank you, Jatin!

[Jatin Katyal]

Awesome

Jatin Katyal


- Do rate helpful posts -