The acceptance test for a Data Domain with a bonded management pair is to pull the active NIC's cable at the switch. What result makes that failover configuration acceptable?
Select an answer to reveal the explanation.
Short Explanation
Failover you have never watched is just a setting you like. Pull the cable for real, keep a ping running, and watch the second path carry management while the first one is dark. That log entry is a souvenir, not proof.
Full Explanation
Bonded failover only earns acceptance when it demonstrably happens on the live path. During a cable-pull, continuous reachability plus observation that the standby slave is now carrying traffic proves the whole chain at once: the standby cable is genuinely connected, its switch port is enabled, and both members sit on the same VLAN and subnet so addresses stay live across the transition. A configured-and-enabled standby in the settings view is half an answer - the most common real faults are switch-side (a disabled port, a wrong VLAN), and none of them show up in appliance configuration. Recovery confirmed only by a browser reloading later is weak evidence: minutes is an eternity in a failover test, it never shows which path carried the return, and it masks how long the transition actually took. A link-down log entry proves detection, not recovery - the event fires whether or not anything took over. Exam caveat: run the inverse test too - pull the now-active member and watch the original path resume - so the return behavior and any LACP policy are exercised rather than assumed. Operational check: a ping or live management session that survives the pull with a measured interruption, and the observed active-path change recorded on the acceptance sheet.