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.
B) 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
A) Replace the failed unit, boot up the new node without connecting cables, upgrade firmware and configure as secondary vsx node connect iSl and wart for VSX to synchronize After successful recovery, reconnect the remaining cables.
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.
B) 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
A) Replace the failed unit, boot up the new node without connecting cables, upgrade firmware and configure as secondary vsx node connect iSl and wart for VSX to synchronize After successful recovery, reconnect the remaining cables.
Hmm, option A sounds like it involves a lot of unnecessary steps. Why bother waiting for the VSX to sync after upgrading the firmware? Just do it all in one go.
Leah
5 months agoAdelina
3 months agoIvan
3 months agoRueben
3 months agoShonda
3 months agoWinfred
3 months agoDorinda
4 months agoSylvie
5 months agoFreeman
5 months agoDong
4 months agoAlfred
4 months agoGerman
5 months agoDenae
5 months agoParis
5 months agoBulah
5 months agoKatina
5 months agoAmie
5 months agoDell
4 months agoJennifer
5 months agoTonette
5 months agoNoah
5 months ago