In order to determine if a particular Cache Server may be experience these types of issues, you can perform the following steps:
1. On the cache server console, select “Logs Menu”, then select “Display Current Cache Server Monitor Log”. Make note of the last few lines. Quit.
2. Make a change to at least one item on the cache server Details tab, perhaps the Retention or SMTP settings, click Save Changes. Allow 15 seconds for it to process.
3. Back on the cache server console, select the “Display Current Cache Server Monitor Log” again, and check the last few lines. If the requested change is logged, all is well. If the requested change is not logged, then this cache server is in a bad state and an in-place re-enrollment should be performed. Note that this in-place re-enrollment will reinitialize the cache server – the application server will be stopped, then started, and all data will be requested from the console appliance. Note that this can be done now, but should also be done after a hotfix is provided and installed to make sure no cache servers are lingering in this bad state.
4. Change the values on the cache server Details tab back to their original values. This can be done before or after the in-place re-enrollment if one is required.
1. Disable and re-enable the Cache Server
- Login to the /tpam interface on the Primary
- Navigate to the Management menu and select Manage Cache Servers.
- On the Listing tab, select the Cache Server in question and then click the Details tab.
- Uncheck the "Enabled" check box and then click Save Changes.
- Wait a few minutes for the change to process and then re-enable the Cache Server.
2. Re-enroll the Cache Server
- If the first option above does not resolve the issue, try re-enrolling the Cache Server.
- Full instructions for enrolling a Cache Server can be found in the "Application Password Virtual Cache" chapter of the TPAM Administrator Guide.