The HPE Aruba Networking CX 8320 VSX configuration is running the current software: How do you upgrade the VSX cluster with the least amount of downtime from a remote server 172.25.101.10 reachable…

Question

Exhibit

Options

• Avsx update-software scp://172.25.101.10/image vrf mgmt
• Bvsx update-software scp://172.25.101.10/image primary
• Cvsx update-software tftp://172.25.101.10/image vrf mgmt
• Dvsx update-software tftp://172.25.101.10/image primary

• A
  84% (54)
• B
  9% (6)
• C
  5% (3)
• D
  2% (1)

Explanation

Option A is correct because vsx update-software on HPE Aruba CX switches requires SCP as the file transfer protocol - it is the only supported protocol for this command, and vrf mgmt correctly identifies the management VRF routing instance used to reach the remote server (172.25.101.10) via the management interface (172.25.102.11).

Option B fails because primary is not a valid VRF keyword - it refers to VSX peer roles, not a routing instance. Without vrf mgmt, the switch cannot route traffic through the management plane to reach the remote server.

Options C and D are both wrong because TFTP is not a supported protocol for vsx update-software; the command only accepts SCP. Option D compounds this by also using primary incorrectly.

Memory tip: Think "SCP + VRF" - Secure Copy goes through the Virtual Routing for management. If you see TFTP in a vsx update-software command, eliminate it immediately; and if you see primary instead of vrf mgmt, that's a VSX peer role sneaking into the wrong place.

No community discussion yet for this question.