After a recent firmware update, several Aruba switches in the network stopped responding. The administrator suspects a configuration corruption issue. What should be the first troubleshooting step?

Question

Options

• ARestore the last working configuration from backup
• BDisable spanning-tree on all switches
• CRestart the switches multiple times
• DReinstall the firmware update immediately

• A
  90% (35)
• B
  5% (2)
• C
  3% (1)
• D
  3% (1)

Explanation

Restoring from backup is the correct first step because it directly addresses the suspected root cause - configuration corruption - by reverting to a known-good state, following the standard troubleshooting principle of reversing the most recent change before exploring deeper fixes.

Why the distractors are wrong:

• B (Disable spanning-tree): This is unrelated to firmware-induced configuration corruption and would introduce network instability (loops), making the problem worse.
• C (Restart switches multiple times): Rebooting repeatedly doesn't fix corrupted configuration files and wastes time without addressing the actual cause.
• D (Reinstall the firmware immediately): Reinstalling the same update that caused the problem is likely to reproduce the issue; the configuration must be stabilized first before any firmware action.

Memory tip: Think "UNDO before REDO" - when a network change breaks things, your first move is always to revert (restore backup), not retry the change or apply unrelated fixes. In Aruba environments specifically, always maintain configuration backups before firmware updates precisely for this scenario.

No community discussion yet for this question.