Skip to main content

Coming soon...New Support-Specific categorization of Knowledge Articles in the NetApp Knowledge Base site to improve navigation, searchability and your self-service journey.

NetApp Knowledge Base

Service processor raises Ping error on some Ping Monitor Tools and auto-recover in a few seconds

Views:
480
Visibility:
Public
Votes:
0
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

AFF-A300

Issue

  • Some Ping Monitor Tools raise the following SP error and recover automatically in a few seconds.

Example:

Time:2020.06.10 10:23:37
System Name: NetApp service processor 2
Host name: NetApp host
IP address: 10.10.0.3
Monitor option: ping check(packet loss rate)

  • In SP events log, the SP service "servprocd" updated itself around at that time like the following.

Example:

Wed Jun 10 2020 10:24:17 [kern_servprocd:info:5329] 0x80a1d8b00: 0: NOTICE: Servprocd::SpUpdate: SpUpdateStateHandleEvent: e_sp_startup event received in SP_UPDATE_NOT_IN_PROGRESS state.
Wed Jun 10 2020 10:24:17 [kern_servprocd:info:5329] 0x80a1d8b00: 0: NOTICE: Servprocd::SpUpdate: sp_startup_notify_servprocd: SP startup handler has been called.
Wed Jun 10 2020 10:25:07 [kern_servprocd:info:5329] 0x80a1d9500: 0: NOTICE: Servprocd::SpUpdate: SpUpdateStateHandleEvent: e_sp_online event received in SP_UPDATE_NOT_IN_PROGRESS state.
Wed Jun 10 2020 10:25:07 [kern_servprocd:info:5329] 0x80a1d9500: 0: NOTICE: Servprocd::SpUpdate: sp_bootup_notify_servprocd: SP online handler has been called

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

Scan to view the article on your device

 

  • Was this article helpful?