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