A service provider needs to upgrade a gateway to a new software version. Which step in needed to complete the upgrade process?

Question

Options

• ARe-assign the Gateway to a new gateway Pool with the appropriate software version, and then run
• BCreate a new disk partition to save the new software image to, modify the boot order via the
• CFrom the Orchestrator, select the check-box next to the appropriate gateway, choose `'Assign
• DCopy the new image to/var/lib/velocloud/software_update.tar, and then run the upgrade the script

• A
  7% (2)
• B
  71% (20)
• C
  4% (1)
• D
  18% (5)

Explanation

Upgrading a gateway typically involves a dual-partition boot process: a new disk partition is created to store the incoming software image, the boot order is modified to point to that new partition, and the device reboots into the upgraded version - leaving the old partition intact as a fallback. This method is standard on many network appliances (Cisco IOS XE, Juniper Junos, etc.) because it enables safe rollback if the new image fails.

Why the distractors are wrong:

• A - Reassigning a gateway to a pool with a different software version is a configuration/policy operation, not the actual image installation process.
• C - While VeloCloud Orchestrator does let you select gateways and assign settings via checkboxes, that workflow handles configuration deployment, not the underlying OS/firmware upgrade steps.
• D - Manually copying a tarball to /var/lib/velocloud/ and running a script is an unofficial/unsupported workaround, not the documented upgrade procedure.

Memory tip: Think B = Boot partition. Any time you upgrade gateway firmware, you're touching the boot system - new partition, new boot order. The other options deal with management-plane tools (Orchestrator, pools, scripts), which sit above the boot-level upgrade.

No community discussion yet for this question.