We deployed a redundant CSS11501 with the Server's directly connected. There is no specific Master between the two.
When a server goes down (the box itself w/2 NIC), CSS-A detects a link failure and will fail-over to CSS-B. A minute after CSS-B becomes a master, it will also detect a link failure (secondary NIC of the Box). It will then switch back to CSS-A causing a loop until the Server is fixed. As a temporary work around, we shut the interfaces connecting to the Down Server on both CSS so it won't monitor the failed link.
This requires human intervention that our customer doesn't want.
We are using the 8.10 Standard Services on both CSS11501.
thanks and regards,