Something similar a long time ago, back when the product was Perfigo, before the Cisco purchase. It was explained to me that (At that time, unsure about now) that the HA was hardware only, it did no internal state checking. Our specific issue was we had some database corruption (the server had a power supply issue, and was power cycling ever 12 hours. Hard power cycling) and the database was crapping out. We ended up rebuilding our CAM from scratch, and the issue went away. (Both the database corruption, and the HA failure)
I'd engage TAC. Have you had any events recently that might have caused Database corruption? Mike On Mon, Apr 13, 2009 at 4:19 PM, Matt Grover <[email protected]> wrote: > We are running into an issue where the active CAM becomes unavailable and > HA > does not failover to the standby CAM. We get notice of the problem because > users are no longer able to login through their CAS server. They get the > login page but they are unable to get a successful login. Behind the > scenes > it is occurring because the active CAM is no longer processing the > authentication requests. Once we receive this problem report attempts to > open the web GUI on the service IP and direct IP of the active CAM fail. > For fail over to occur we have to manually cause the failover to happen, > usually by dropping the network connection on the active(but faulty) CAM. > A > service restart on the faulty CAM will restore it to normal operation. So > far logs have failed to show anything of merit regarding the failure. This > has occurred under 4.5.0 and 4.5.1. > > Has anyone seen this type of issue? >
