A customer has implemented this ArubaOS-CX solution. NetEdit is not present. After a while, the secondary node of the VSX-cluster fails. What is the correct procedure to replace the failed node as quickly as possible?
Option C looks like the most straightforward way to get the secondary node back up and running quickly. Upgrading the firmware and restoring the config in recovery mode seems like the best approach.
Jutta
4 days agoHillary
9 days agoAlisha
15 days agoMarisha
24 days agoLeonardo
25 days agoBuddy
26 days agoPaulina
1 months agoGabriele
1 months agoHerman
8 days agoArlette
8 days agoFlorinda
14 days agoHelene
17 days ago