After onboarding three new AOS-10 gateways using the full-setup method into the same HPE Aruba Networking Central group, a customer cannot log in to one of the gateways using the HPE Aruba…

Question

Options

• AThe admin password created during the full-setup process is not configured to allow the remote
• BThe admin password created at the HPE Aruba Networking Central group level has expired
• CThe admin password created using full-setup does not match the global HPE Aruba Networking
• DThe admin password created during the full-setup process does not match the HPE Aruba

• A
  5% (2)
• B
  3% (1)
• C
  8% (3)
• D
  84% (32)

Explanation

Option D is correct because the full-setup method requires an administrator to manually configure a local admin password directly on the gateway during the setup wizard. When HPE Aruba Networking Central attempts to authenticate via the remote console, it uses the credentials it expects - if the password entered during full-setup on that one gateway was set differently from what Central has on record, authentication fails. Since only one of three gateways is affected, the other two were likely configured with a matching password, confirming this is a per-device misconfiguration rather than a systemic issue.

Why the distractors are wrong:

• A is incorrect because remote console access is a built-in Central feature - the password type doesn't restrict it; a mismatch is what blocks it.
• B is incorrect because password expiration would affect all gateways in the group equally, not just one.
• C is a near-miss but is incorrect because it implies a mismatch with a global Aruba setting, whereas the actual mismatch is specifically between the gateway's local full-setup password and what Central holds for that device.

Memory tip: Think of full-setup as "manual = mismatch risk." Unlike zero-touch provisioning, full-setup lets you type whatever password you want locally - if it doesn't match what Central expects, you're locked out of the remote console for that specific device. Always verify that the password entered during full-setup aligns with your Central configuration.

No community discussion yet for this question.