<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ONTAP_API invocation failed : Unexpected HTTP response: 400 Bad Request in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139106#M2621</link>
    <description>&lt;P&gt;There are 2 things. First off if you haven't updated to the 9.3 SDK then you need to do that due to some format changes in connect header. Secondly 9.3 applies a security patch that will cause any SVM connect attempt that resolves to a name with underscores to fail with "&lt;/P&gt;
&lt;P&gt;&amp;lt;results status="failed" reason="Server returned HTTP Error: 400 Bad" errno="13001"&amp;gt;&amp;lt;/results&amp;gt;"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are running into reason #1 upgrade, if you are running into #2, make sure the hostname/IP you are connecting to doesn't resolve/reverse resolve to a name with an underscore in it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Paul Winkel&lt;/P&gt;</description>
    <pubDate>Sat, 24 Mar 2018 13:06:42 GMT</pubDate>
    <dc:creator>winkel</dc:creator>
    <dc:date>2018-03-24T13:06:42Z</dc:date>
    <item>
      <title>ONTAP_API invocation failed : Unexpected HTTP response: 400 Bad Request</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139094#M2620</link>
      <description>&lt;P&gt;Hi everyone.&amp;nbsp; After updating to ONTAP version 9.3, the ONCommand API Service server can no longer gain access to our Clustered Ontap Storage System.&amp;nbsp; Any ideas on this one?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 13:53:06 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139094#M2620</guid>
      <dc:creator>CSiegle</dc:creator>
      <dc:date>2025-06-04T13:53:06Z</dc:date>
    </item>
    <item>
      <title>Re: ONTAP_API invocation failed : Unexpected HTTP response: 400 Bad Request</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139106#M2621</link>
      <description>&lt;P&gt;There are 2 things. First off if you haven't updated to the 9.3 SDK then you need to do that due to some format changes in connect header. Secondly 9.3 applies a security patch that will cause any SVM connect attempt that resolves to a name with underscores to fail with "&lt;/P&gt;
&lt;P&gt;&amp;lt;results status="failed" reason="Server returned HTTP Error: 400 Bad" errno="13001"&amp;gt;&amp;lt;/results&amp;gt;"&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you are running into reason #1 upgrade, if you are running into #2, make sure the hostname/IP you are connecting to doesn't resolve/reverse resolve to a name with an underscore in it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Cheers,&lt;/P&gt;
&lt;P&gt;Paul Winkel&lt;/P&gt;</description>
      <pubDate>Sat, 24 Mar 2018 13:06:42 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139106#M2621</guid>
      <dc:creator>winkel</dc:creator>
      <dc:date>2018-03-24T13:06:42Z</dc:date>
    </item>
    <item>
      <title>Re: ONTAP_API invocation failed : Unexpected HTTP response: 400 Bad Request</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139108#M2622</link>
      <description>&lt;P&gt;check system-get-version is working with hostname of cluster_mgmt_lif.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;if cluster_mgmt ip resolved into hostname with underscope, user can't talk to ontap 9.3. . To overcome this issue, user need to do below things:&lt;/P&gt;
&lt;P&gt;1. change cluster_mgmt hostname name without underscore&lt;/P&gt;
&lt;P&gt;2. remove and add cluster to API services&lt;/P&gt;
&lt;P&gt;3, check once again system-get-version&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 24 Mar 2018 13:42:42 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139108#M2622</guid>
      <dc:creator>pukale</dc:creator>
      <dc:date>2018-03-24T13:42:42Z</dc:date>
    </item>
    <item>
      <title>Re: ONTAP_API invocation failed : Unexpected HTTP response: 400 Bad Request</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139974#M2664</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Any reason why underscores are not allowed from 9.3 onwards ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;-Prasad&lt;/P&gt;</description>
      <pubDate>Tue, 01 May 2018 19:59:25 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139974#M2664</guid>
      <dc:creator>prasadm</dc:creator>
      <dc:date>2018-05-01T19:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: ONTAP_API invocation failed : Unexpected HTTP response: 400 Bad Request</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139975#M2665</link>
      <description>&lt;P&gt;Nevermind. I found this -&amp;nbsp;&lt;A href="https://community.netapp.com/t5/Data-ONTAP-Discussions/Problems-with-an-in-the-DNS-name-with-OnTap-9-3/m-p/138712#M30598" target="_blank"&gt;https://community.netapp.com/t5/Data-ONTAP-Discussions/Problems-with-an-in-the-DNS-name-with-OnTap-9-3/m-p/138712#M30598&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 01 May 2018 20:12:11 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/139975#M2665</guid>
      <dc:creator>prasadm</dc:creator>
      <dc:date>2018-05-01T20:12:11Z</dc:date>
    </item>
    <item>
      <title>Re: ONTAP_API invocation failed : Unexpected HTTP response: 400 Bad Request</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/144890#M2773</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;I'm facing the same problem after upgrading to 9.3P3. (from 9.1x)&lt;/P&gt;
&lt;P&gt;What do you mean with:&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/9580"&gt;@pukale&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;2. remove and add cluster to API services&amp;nbsp;&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 26 Nov 2018 16:49:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/ONTAP-API-invocation-failed-Unexpected-HTTP-response-400-Bad-Request/m-p/144890#M2773</guid>
      <dc:creator>skydriver</dc:creator>
      <dc:date>2018-11-26T16:49:44Z</dc:date>
    </item>
  </channel>
</rss>

