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?
Haha, I bet the customer's IT team is cursing the day they decided to go with Aruba. Replacing a failed node should be a simple process, not a trivia question!
Option C seems the most straightforward. Booting in recovery mode to upgrade the firmware and restore the config sounds like the quickest way to get the node back up and running.
Hyun
16 days agoAmber
4 days agoAnnmarie
19 days agoEthan
1 days agoLashawn
3 days agoKing
7 days agoHuey
26 days agoFelton
6 days agoSharmaine
10 days agoEllsworth
17 days agoCiara
1 months agoAlesia
24 hours agoChantell
2 days agoEmmett
7 days agoLai
2 months agoLindsey
2 months ago