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
4 months agoScarlet
3 months agoKirk
3 months agoAmber
4 months agoAnnmarie
4 months agoKeneth
3 months agoEthan
3 months agoLashawn
4 months agoKing
4 months agoHuey
4 months agoJeannetta
3 months agoFelton
4 months agoSharmaine
4 months agoEllsworth
4 months agoCiara
4 months agoAlesia
3 months agoChantell
4 months agoEmmett
4 months agoLai
5 months agoLindsey
5 months ago