Buy or Renew
Buy or Renew
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
3423
Views
5
Helpful
1
Replies

Secondary ACS 5.1 fails to Deregister, after IP change on Primary

Go to solution
lorrainecamp
Level 1
Level 1

‎08-09-2011 12:14 PM - edited ‎03-10-2019 06:17 PM

IP address of Primary had to be changed, to respond to a hardware failure of TACACS server with IP in many device configs.

Now the Secondary fails to respond to repeated "Deregister from Primary" requests, even after reload  -

   apparently because it cannot reach the Primary at its old IP address. 

Requesting Deregister in GUI generates pop-up that says,  "This operation will deregister this ACS Instance from the Primary Instance.

     Management applications on this ACS instance will be restarted and you will be required to login again.  After performing this operation

     please wait five minutes for this restart to complete.

     Do you wish to contine?"      [ OK ]

But, checking back after 10 minutes -- or even the next day  --  finds the Secondary's status unchanged.

Also tried Local Mode, Deregister from Primary;  this also fails.

Does anyone have HOWTO URL on a total rebuild of ACS application?  

Both ACS are CACS-1121-K9   running 5.1.0.44.4.

Thanks in advance for any help...

***  UPDATE:  ***

Recommended command,  "application reset-config acs",    was _exactly_ what was needed. 

jrabinow  -   many thanks!    :-)

    also, thank you for mentioning that the license would be required, so that I could locate it in advance and have it ready.

      Since there were no local certs on the server, we did not need to re-install those.

Labels:
0 Helpful
1 Accepted Solution

Accepted Solutions

Go to solution
jrabinow
Level 7
Level 7

‎08-09-2011 01:14 PM

Since this is a secondary it should not have too much in terms of specific configuration

Therefore one possibility is to reset the configuration so it once again becomes just a standalone node and then regsiter back to the deployment as is done for any new node and as you previosuly registered it

reset configuration can be done using the following command at the CLI:

application reset-config acs

Note that after you reset the configuration you will need to reinstall the license so make sure you have this to hand

Also if you has installed a server certificate for the secondary server you would need that too

View solution in original post

1 Reply 1

Go to solution
jrabinow
Level 7
Level 7

‎08-09-2011 01:14 PM

Since this is a secondary it should not have too much in terms of specific configuration

Therefore one possibility is to reset the configuration so it once again becomes just a standalone node and then regsiter back to the deployment as is done for any new node and as you previosuly registered it

reset configuration can be done using the following command at the CLI:

application reset-config acs

Note that after you reset the configuration you will need to reinstall the license so make sure you have this to hand

Also if you has installed a server certificate for the secondary server you would need that too

Customers Also Viewed These Support Documents