Skip to main content
NetApp Knowledge Base

Frequent ‘security.invalid.login’ Errors Due to Stale BlueXP connection

  1. Last updated
  2. Save as PDF
Views:
4
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • BlueXP (NetApp Console)
  • On-premises environments using BlueXP to manage ONTAP clusters

Issue

  • The ONTAP cluster event logs are repeatedly filled with security.invalid.login errors for the ‘admin’ user. These failed login attempts originate from specific IP addresses associated with BlueXP and other management systems, causing the ‘admin’ account to be locked out after repeated failures.
  • Example EMS log output:

security.invalid.login: error - User 'admin' from IP 192.168.1.100 attempted to log in via REST API - Authentication failed.security.invalid.login: error - User 'admin' from IP 192.168.1.101 attempted to log in via CLI - Authentication failed.

  • The errors persisted even after removing and re-adding the cluster to BlueXP with a different user.
  • The retries originated from the BlueXP agent VM IP.
  • The system event log filled up and the ‘admin’ account was repeatedly locked.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.