ZAPI timeout since ONTAP upgrade
Applies to
- ONTAP 9
- NetApp ONTAPI (ZAPI)
- Service Processor (SP)
- Baseboard Management Controller (BMC)
Issue
- ZAPI call <environment-sensors-get-iter>returns no values and timeout after 50+ seconds
time curl --connect-timeout 30 --user username --insecure --data-ascii '<?xml version="1.0" encoding="UTF-8"?> <netapp xmlns=http://www.netapp.com/filer/admin version="1.130">  <environment-sensors-get-iter/></netapp>' -H "Content-Type: text/xml" 'https://10.11.12.13/servlets/netapp....Lrequest_filer'  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                 Dload  Upload   Total   Spent    Left  Speed100  3078    0  2929  100   149     34      1  0:02:29  0:01:23  0:01:06   156real    1m 29.31suser    0m 0.02ssys     0m 0.00s- cluster01::*> system node environment sensors show -node node01
Node Sensor                 State Value/Units Crit-Low Warn-Low Warn-Hi Crit-Hi---- --------------------- ------ ----------- -------- -------- ------- -------ramfas11PSU2                  normalGOODPSU1                  normalGOODFan3                  normalGOODFan2                  normalGOODFan1                  normalGOODSP Status             normalIPMI_HB_OKmSATA Status          normalOKmSATA Pres            normalPRESENTWarning: Unable to list entries on node node01. The Service Processor on node "node01" is not reachable. Verify that the SP or BMC is online, verify that api-service is enabled on theSP or BMC, verify that the partner node is running, check if pings from SP or BMC to partner node work, check if hw-assist keep-alives are normal, check that network ports areconfigured correctly and are functional (up). Then, try the command again.Error: show failed on node "node01": The Service Processor on node "node01" is not reachable. Verify that the SP or BMC is online, verify that api-service is enabled on the SP or BMC,verify that the partner node is running, check if pings from SP or BMC to partner node work, check if hw-assist keep-alives are normal, check that network ports are configuredcorrectly and are functional (up). Then, try the command again.8 entries were displayed.- SSL Error in SP-MGMT-MLOG-TXT.GZASUP section
00000026.021819cb 0448d1c2 Thu Aug 31 2023 18:19:02 +02:00 [kern_servprocd:info:6028] 0x80944b000: 8503e8000083abee: ERR: Servprocd::CLI: sp_get_sensor_info_worker : TTX ERROR: 7 (SSL_connect: certificate verify failed (SSL_error_code = 1))00000026.021819cc 0448d1c2 Thu Aug 31 2023 18:19:02 +02:00 [kern_servprocd:info:6028] 0x80944b000: 8503e8000083abee: ERR: Servprocd::CLI: sp_get_sensor_info_worker : EXCEPTION Occured in closing the spcc transport- Issue continue after restarting api-service
cluster01::*> system service-processor api-service modify -is-enabled falsecluster01::*> system service-processor api-service modify -is-enabled truecluster01::*> system service-processor api-service check -node node01- Issue continue after rebooting SP/BMC
cluster01::*> system service-processor reboot-sp -node node01
- Issue continue after restarting servprocd process
