Skip to main content
NetApp Knowledge Base

CONTAP-355735: "Failed to discover SNMPv3 engine ID of remote SNMP agent" in one side of a MCC IP

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

Issue

  • Cluster Switch Health Alert. Example:

Monitor ethernet-switch
Alert ID SwitchSNMPCommunication_Alert
Subsystem Switch-Health
Probable Cause Configuration_error
Description Physical SNMP communication from the node to the ethernet switch has failed repeatedly. Invalid SNMP settings are configured with ONTAP Switch Health Monitoring or on the Ethernet switch.
Corrective Actions 1) Check the SNMPv2c community or SNMPv3 username on the Ethernet switch to verify
that the expected community string or username is configured.
To view the expected community string or username, run the "system switch ethernet show -snmp-config" command.
2) (SNMPv3) Verify that the SNMPv3 credentials are present within ONTAP.
To view the established SNMP logins, run the "security login show -application snmp" command.
If a custom engine-id was provided for the SNMPv3 user, ensure it is same as that of the remote switch.
Possible Effect Ethernet switch communication problems and accessibility issues.
  • Error creating the SNMPv3 user. Example:

::*> security login create -user-or-group-name <SNMPv3_name> -application snmp -authentication-method usm -vserver <svm_name> -remote-switch-ipaddress <switch_management_IP>
Error: command failed: Failed to discover SNMPv3 engine ID of remote SNMP agent with IP address 123.123.123.123.

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.