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?
C) Replace the failed unit, connect the correct cables, boot up the new node in recovery mode, upgrade firmware and restore, and save config Then, reboot and wait for VSX to synchronize.
A) Replace the failed unit, boot up the new node without connecting cables, upgrade firmware, and restore and save config Shutdown all ports, reconnect the correct cables, and enable all ports
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
1 months agoCeola
3 days agoYuette
13 days agoHillary
1 months agoAlisha
2 months agoLillian
24 days agoMitzie
28 days agoBronwyn
1 months agoLawanda
1 months agoMarisha
2 months agoLeonardo
2 months agoLeah
1 months agoValentin
1 months agoSang
1 months agoBuddy
2 months agoPaulina
2 months agoGabriele
2 months agoHerman
1 months agoArlette
1 months agoFlorinda
2 months agoHelene
2 months ago