ONTAP Discussions

ontap api not working with veeam backup and PRTG after updating to ontap9.6P9

JWHatAVO
6,395 Views

Updated to ontap 9.6P9 from ontap 9.5  directly after I notice my PRTG (https based) sensors  going down for this cluster

short time after i found out that storage based snapshot backup with veeam backup also stopped working

also seems to use the https api.  Can't find what's stopping this , when i use either program i get a " The remote server returned an error: (408) Request Timeout. "  but from both servers I can connect to the https of the ontap system and I can run a curl command to query the api with successful output:

C:\curl\bin>curl -X GET -u admin:*** https://10.1.0.100/api/cluster?fields=version -v -k
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying 10.1.0.100:443...
* Connected to 10.1.0.100 (10.1.0.100) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: CN=SAN; C=US
* start date: Jul 25 19:39:11 2020 GMT
* expire date: Jul 23 19:39:11 2030 GMT
* issuer: CN=SAN; C=US
* SSL certificate verify result: self signed certificate (18), continuing anyway.
* Server auth using Basic with user 'admin'
> GET /api/cluster?fields=version HTTP/1.1
> Host: 10.1.0.100
> Authorization: Basic YWRtaW46KlN5c3RlbTAxKg==
> User-Agent: curl/7.71.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Date: Wed, 29 Jul 2020 11:33:35 GMT
< Server: libzapid-httpd
< X-Content-Type-Options: nosniff
< Cache-Control: no-cache,no-store,must-revalidate
< Content-Length: 208
< Content-Type: application/hal+json
<
{
"version": {
"full": "NetApp Release 9.6P9: Wed Jul 08 09:07:16 UTC 2020",
"generation": 9,
"major": 6,
"minor": 0
},
"_links": {
"self": {
"href": "/api/cluster"
}
}
}* Connection #0 to host 10.1.0.100 left intact

 

any one else have seen this or have some suggestions ? have cases running with netapp support , prtg support and veeam support , but the process is going very slow and I need to get my backup back running again.

 

All help appreciated.

 

JWH

 

1 ACCEPTED SOLUTION

JWHatAVO
5,798 Views

Thank you ,

 

I have a case indeed and  I was called today by netapp , the bug is indeed identified:

https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/1342292

downgrade is normally not advised by netapp but they did today as I can not go to 9.7 because of other netapp system that is connected. so the advise is to go back to 9.6P8

 

JWH

 

Thanks to all

View solution in original post

6 REPLIES 6

Becca1701
6,246 Views

We also have this issue affecting Veeam and SnapCentre.  We have a case raised with NetApp, however through our own internal testing in a lab environment we have confirmed that the issue is only affecting OnTAP9.6P9.

--

ONTAP 9.5P9 works fine

ONTAP 9.6P8 works fine

ONTAP 9.6P9 doesn’t work for Veeam or SnapCenter

JWHatAVO
6,219 Views

Great to hear that I'm not the only one.

so snapcenter also use the same api and has the same communication problem as veeam does ?

how far are you with your case with netapp ?  for me there is not really an option to go to 9.7 so or netapp should come with a patch or we should consider downgrade to 9.6p8 , but not really looking forward to do a downgrade to a live system with many vm's on it.

 

Thank you for sharing what you know with me.

 

JWH

parisi
6,042 Views

I browsed the bug fixes introduced in 9.6P9 and the only API fix is this one:

 

https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/1312566

 

Could be related. 

 

You can see the bug fixes in the release here:

https://mysupport.netapp.com/site/products/all/details/ontap9/downloads-tab/download/62286/9.6P9

JWHatAVO
6,019 Views

Hi ,

 

Thanks for the suggestion ,  yes this bug is api related although the bug description is very specific on a certain api request in a specific situation.  ofcource I don't know there resolution to the fix , but what seems for now is that not any program who talks to the api can get a connection at all ,  not just a specific one.

 

JWH

parisi
5,818 Views

Ok, this is a confirmed bug in P9.

 

When you open a case (if you haven't already), have the TSE add it to bug 1342292. We'll have a public report soon.

 

There doesn't seem to be a workaround for this other than reverting to the previous P release or moving to the latest 9.7 release.

JWHatAVO
5,799 Views

Thank you ,

 

I have a case indeed and  I was called today by netapp , the bug is indeed identified:

https://mysupport.netapp.com/site/bugs-online/product/ONTAP/BURT/1342292

downgrade is normally not advised by netapp but they did today as I can not go to 9.7 because of other netapp system that is connected. so the advise is to go back to 9.6P8

 

JWH

 

Thanks to all

Public