Error: netapp_ontap_rest probe fails with 401 Unauthorized or 400 Bad Request due to ONTAP API
search cancel

Error: netapp_ontap_rest probe fails with 401 Unauthorized or 400 Bad Request due to ONTAP API

book

Article ID: 447274

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Issue/Introduction

When monitoring NetApp ONTAP clusters ranging from versions 9.6 to 9.17.1, the netapp_ontap_rest probe may encounter connection or data retrieval failures. This occurs because certain metric fields or counters have evolved, changed availability, or been deprecated in newer ONTAP API schemas, requiring more adaptive handling by the probe.

Symptoms

The netapp_ontap_rest probe fails to successfully collect data from the NetApp system. The following errors are observed in the probe logs:

  • Status code: 401 / Non-200 status code: 401
  • HTTP 400 Bad Request for URL: .../api/cluster/counter/tables/...
  • Error Message: The value "key" is invalid for field "fields"

Note: Connectivity via curl from the same robot using identical credentials and certificates completes successfully.

Environment

  • DX Unified Infrastructure Management (UIM) 23.4.*
  • netapp_ontap_rest probe version 1.0.3 or lower
  • NetApp ONTAP 9.16.1P8 or higher (and systems with varied API configurations)

Cause

NetApp ONTAP environments span a wide range of versions where API schemas, counter tables, and field availability can vary significantly or depend on specific cluster configurations.

An issue (tracked via DE675876) was identified where the probe requested specific legacy or default fields (such as "key") that are either unconfigured, restricted, or no longer recognized by the API of certain modern ONTAP versions. When encountering these unexpected schema differences, the NetApp system rejects the request, throwing a 400 Bad Request or 401 Unauthorized error.

Resolution

The attached patch fixes the issue netapp_ontap_rest-1.0.4-20260626.134247-2.zip

 

1. Download the package

2. Deploy on the natapp_ontap_rest robot

3. Verify if the issue still exists

 

Additional Information

If the issue persists after upgrading to version netapp_ontap_rest-1.0.4-20260626.134247-2.zip, verify:

  1. The user account has appropriate permissions on the NetApp ONTAP cluster.
  2. The SSL certificate is correctly imported into the probe's keystore.
  3. For assistance, Contact Broadcom support
Powered by Wolken Software