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?
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
1 months agoDorinda
4 days agoSylvie
1 months agoFreeman
1 months agoDong
16 days agoAlfred
17 days agoGerman
1 months agoDenae
1 months agoParis
2 months agoBulah
2 months agoKatina
2 months agoAmie
2 months agoDell
28 days agoJennifer
1 months agoTonette
1 months agoNoah
1 months ago