Skip to content
TheChatArchiveThe Chat Archive
gpt-4.1-mini-2025-04-14· OpenAIHugging Face LMArena Human Preference 140K

how to change password in Aruba access point AOS CLI

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Qwenqwen3-30b-a3b’s answer.
  1. User

    how to change password in Aruba access point AOS CLI

  2. Assistant

    To change the password on an Aruba Access Point running AOS (ArubaOS) via the CLI, you generally need to change the password for the user account you use to log in. Here’s how you can do it:

    Steps to Change Password in ArubaOS CLI

    1. Access the Aruba AP CLI:

      • Connect to the Aruba AP via SSH or console.
      • Log in with your current username and password.
    2. Enter Configuration Mode:

      enable
      configure terminal
      
    3. Change the Password for a User: If you want to change the password for a specific user (e.g., admin), use the following command:

      username admin password plaintext NEW_PASSWORD
      

      Replace admin with your username and NEW_PASSWORD with the new password you want to set.

    4. Save the Configuration:

      write memory
      

      or

      save
      
    5. Exit:

      exit
      exit
      

    Example

    Aruba# enable
    Aruba# configure terminal
    Aruba(config)# username admin password plaintext MyNewPass123
    Aruba(config)# exit
    Aruba# write memory
    

    Notes:

    • The plaintext keyword means the password is entered in clear text. ArubaOS may also support encrypted passwords.
    • If your AP is managed by a controller, the password might be managed centrally, and changing it on the AP directly might not be persistent or recommended.
    • Always ensure you have proper authorization before changing passwords.

    If you want to change the password for the admin user on a standalone Aruba Instant AP or controller, the above method applies.


    If you need help with a specific ArubaOS version or model, please provide that info!

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.