Hello,
After seeing SP error messages and ntpd messages , we have executed the below steps to get rid of these messages and to rule out the software issue on the node. But we could still see both the issues post SP and node reboot.
SP was rebooted before proceeding with node reboot. Post SP reboot, SP firmware was loaded from the secondary image instead of primary image.
We were able to login to the SP & SP IP is reachable over the network.
“Sp status” command is not giving the output from ONTAP prompt but getting the output from SP prompt. Same behavior is observed when SP is running on both the versions.
Service Processor Status: Online
Firmware Version: 1.3.2P1
Mgmt MAC Address: 00:A0:98:3D:E7:E4
Ethernet Link: up, 100Mb, full duplex, auto-neg complete
Using DHCP: no
IPv4 configuration:
IP Address:
Netmask:
Gateway
We have replaced the MB however the fault remains:
Line 285: Wed Mar 2 14:30:29 GMT [dldnc016pn1:auth.trace.mapNTToUnix:info]: AUTH: Mapping Windows user chinnasp to Unix user chinnasp.
Line 285: Wed Mar 2 14:30:29 GMT [dldnc016pn1:auth.trace.mapNTToUnix:info]: AUTH: Mapping Windows user chinnasp to Unix user chinnasp.
Line 286: Wed Mar 2 14:30:29 GMT [dldnc016pn1:auth.trace.authenticateUser.loginAccepted:info]: AUTH: Login by chinnasp from 10.60.58.245 accepted.
Line 287: Wed Mar 2 14:33:25 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 287: Wed Mar 2 14:33:25 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 287: Wed Mar 2 14:33:25 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 287: Wed Mar 2 14:33:25 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 289: Wed Mar 2 15:00:19 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 289: Wed Mar 2 15:00:19 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 289: Wed Mar 2 15:00:19 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 289: Wed Mar 2 15:00:19 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 290: Wed Mar 2 15:00:19 GMT [dldnc016pn1:spmgmt.driver.hourly.stats:warning]: The software driver for the Service Processor (SP) detected a problem: Configuration Error (1).
Line 290: Wed Mar 2 15:00:19 GMT [dldnc016pn1:spmgmt.driver.hourly.stats:warning]: The software driver for the Service Processor (SP) detected a problem: Configuration Error (1).
Line 292: Wed Mar 2 15:01:02 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 292: Wed Mar 2 15:01:02 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 292: Wed Mar 2 15:01:02 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 292: Wed Mar 2 15:01:02 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 293: Wed Mar 2 15:01:02 GMT [dldnc016pn1:cf.hwassist.notifyCfgFailed:CRITICAL]: Failed to notify hardware-assist configuration to hardware component (SP): SP is not online(3)
Line 293: Wed Mar 2 15:01:02 GMT [dldnc016pn1:cf.hwassist.notifyCfgFailed:CRITICAL]: Failed to notify hardware-assist configuration to hardware component (SP): SP is not online(3)
Line 294: Wed Mar 2 15:01:02 GMT [dldnc016pn1:spmgmt.driver.timeout:warning]: The software driver for the Service Processor (SP) detected a problem: SP is not online.
Line 294: Wed Mar 2 15:01:02 GMT [dldnc016pn1:spmgmt.driver.timeout:warning]: The software driver for the Service Processor (SP) detected a problem: SP is not online.
Line 294: Wed Mar 2 15:01:02 GMT [dldnc016pn1:spmgmt.driver.timeout:warning]: The software driver for the Service Processor (SP) detected a problem: SP is not online.
Line 295: Wed Mar 2 15:01:27 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 295: Wed Mar 2 15:01:27 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 295: Wed Mar 2 15:01:27 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
Line 295: Wed Mar 2 15:01:27 GMT [dldnc016pn1:sp.orftp.failed:warning]: SP communication error, receiver timeout waiting for SP response.
At this stage I am not sure what to do next. Syslog translator does not give us much info: https://mysupport.netapp.com/site/bugs-online/syslog-translator/details?eventId=5e85e1e197855c5d2edf965a