SSH public key authentication requires the user's public key to be stored and associated with their user account within ONTAP. The system uses this stored key to verify the signature provided by the user's private key during the login attempt. If a user can log in successfully with a password (local login) but fails with an SSH key, the most direct and probable cause is that their public key has not been correctly imported or associated with their ONTAP user account. The core login mechanism is working, but the specific key-based authentication method is not configured for that user.

Volume encryption key error: This relates to data-at-rest encryption (NVE/NAE) and has no impact on user authentication to the ONTAP management interfaces.

SVM offline: If the Storage Virtual Machine (SVM) were offline, no logins, including the successful local login, would be possible.

Role mapping disabled: Role mapping applies to external authentication sources (LDAP/AD) to assign ONTAP roles. It is not the primary cause for a specific SSH key failure.

1. NetApp, "ONTAP System Administration Basics," ONTAP 9 Documentation Center. (The section on managing user accounts details the process of creating users and adding public keys for SSH authentication using the security login publickey create command).

2. NetApp, "Authentication and RBAC," TR-4629, Section 3.2.1 SSH Public Key. (Explains that for SSH public key authentication, the public key must be configured for the specific user account in ONTAP).