Wireless Access

 View Only
last person joined: 23 hours ago 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Mobility Conductor Error: Maximum Authentication Attempts Exceeded

This thread has been viewed 3 times

  • 1.  Mobility Conductor Error: Maximum Authentication Attempts Exceeded

    Posted 28 days ago

    I tried logging into our mobility conductor this morning and started receiving this message:

    Mar 29 08:09:46 2024  aaa[6599]: <125022> <6599> <WARN> |aaa|  Authentication failed for User Adm123, Logged in from 10.1.1.3 port 22, Connecting to 10.1.18.18 port 58054 connection type SSH
    Mar 29 08:09:46 2024  sshd[15155]: <199801> <15155> <INFO> |sshd|  Failed password for Adm123 from 10.1.1.3 port 58054 ssh2
    Mar 29 08:09:48 2024  sshd[15155]: <199801> <15155> <INFO> |sshd|  Failed password for Adm123 from 10.1.1.3 port 58054 ssh2
    Mar 29 08:09:48 2024  sshd[15155]: <199801> <15155> <ERRS> |sshd|  error: maximum authentication attempts exceeded for Adm123 from 10.1.1.3 port 58054 ssh2
    Mar 29 08:09:48 2024  sshd[15155]: <199801> <15155> <INFO> |sshd|  Disconnecting authenticating user Adm123 10.1.1.3 port 58054: Too many authentication failures
    Mar 29 08:09:48 2024  sshd[15155]: <199801> <15155> <ERRS> |sshd|  error: maximum authentication attempts exceeded for Adm123 from 10.1.1.3 port 58054 ssh2

    Not sure how to clear this out, I verified my credentials are valid. I was testing some network automation yesterday with Ansible and wonder if I had too many failed attempts. 

    I could reboot the conductor, but other than that, not sure what I can do here?



  • 2.  RE: Mobility Conductor Error: Maximum Authentication Attempts Exceeded
    Best Answer

    Posted 28 days ago

    Resolved ... we just recently migrated to a new CPPM cluster and was not returning "root" as the Aruba-Admin-Role. 

    Thanks anyway!


    Original Message