Alex, that's what I am thinking that why we're talking about browser's here
Let me attempt to answer your question; in order to restore logging, as soon as primary is down, login to secondary device, de-register it from primary (THIS STEP WOULD RESTART THE SERVICES) and change the logging server to point to itself. Once a device becomes standalone, it'll be the log collector for itself unless you specify a syslog server.
All new authentications will start getting logged on to secondary ACS because currently it's a log collector. The old logs that were on dead master cannot be viewed from secondary.
After primary fails and before secondary is made standalone or new primary, you'll not be able to monitor logs. Since primary is configured as log server in your secondary servers, when you launch monitoring and reports page, it'll launch monitoring and reports from primary device and as primary is down, you'll not be able to view logs.
However, you can enable Log message recovery option in ACS so that the missing entries can be resent to log collector when it's up and running.
Yes, this answers my question on a technical level. From a user viewpoint, it's disappointing though. A well-established system should make logs available unrelated to any physical machine failure, in my opinion.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR
and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity
options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in
HA DocumentationCode download linksGoalRequirementLimitationsSupported
ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and
UCS-E Blades:Step by Step ConfigurationCo...
Question I am currently unable to specify "crypto keyring" command when
configuring VPN connection on my cisco 2901 router. The following
licenses have been activated on my router :