Firmware Update Management by Switches

The RUCKUS One web interface supports RUCKUS ICX switch firmware updates at the switch level.

Feature Overview

The Firmware Update Management by Switches feature offers enhanced capabilities for managing update tasks at the switch level associated with one venue or across multiple venues.

  • Update Now: Immediately update one or more specifically selected switches
  • Change Update Schedule: Change the update schedule for one or more specifically selected switches
  • Skip Update: Cancel a scheduled update for one or more specifically selected switches

Requirements

Management of switch firmware updates, such as changing an update schedule, requires the RUCKUS ICX switch to be onboarded to RUCKUS One and associated with a venue.

Switch firmware update, whether scheduled or by Update Now, requires the RUCKUS ICX switch to be onboarded to RUCKUS One, associated with a venue, in the Operational state, and running a firmware version that is older than the latest released version.

Considerations

  • After selecting one or more venues and choosing the Update Now or the Schedule Updates option, you then have the choice of updating all switches in the selected venue(s) or selecting specific switches to be updated.
  • If a switch is offline during its scheduled update, it will, upon returning online, select the missed target version for updating, provided that the switch’s current firmware version is older than the target version.
  • Switches will be upgraded to match the respective generation of firmware version. For example, if you trigger an update to firmware versions 9.0.10xx_xxxx and 10.0.10x_xxxx. The switches that are 9.0.x releases will be updated to 9.0.10x_xxxx and the switches that are 10.0.x releases will be updated to 10.0.10x_xxxx.
  • If a switch has already been updated to the target version during a previous update cycle, it will not be updated again in the current cycle.
  • Switch-level scheduling takes precedence over venue-level scheduling while renewing a schedule for a switch update for an existing venue-level schedule, consider the following:
    • If you apply a new schedule on specific switches (for example, switch A and switch B) of a venue where the rest of the switches are following an existing venue-level schedule, then the new schedule will be effective only on those switches (switch A and switch B) and rest of the switches will use the existing venue-level schedule.
    • If you are applying a new schedule on all the switches of the venue, then the existing schedule on the switches will be canceled and all the switches of the venue will use the new schedule.
    • If you are applying a new schedule on a specified switch that is part of another existing schedule, then the specified switch will use the new schedule.
  • While skipping a scheduled switch upgrade, consider the following:
    • If you skip a switch update for a specific venue, then all scheduled updates on the venue are cancelled whether the switches follow the existing venue-level or switch-level schedules.
    • If you skip a switch update for a specific switch on a venue, then only the schedule related to that particular switch is cancelled. The other switch-level and venue-level schedules on the venue remain unaffected.

Best Practices

This feature has no special recommendations for feature enablement or usage.

Prerequisites

This feature has no prerequisites to feature enablement or usage.