Node reporting splog.sp.not.accessible, Firewall blocking port 50000 for SP API Service
Applies to
- Service Processor (SP)
- Baseboard Management Controller (BMC)
- SP API Service
- servprocd daemon
Issue
- One node reporting servprocd connectivity issues to the SP/BMC of other node(s) in the cluster. Example:
[node_name_03: servprocd: splog.sp.not.accessible:error]: The SP on the remote node (node_name_01) is not accessible because of The Service Processor on node "node_name_01" 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 configured correctly and are functional (up). Then, try the command again..
[node_name_03: servprocd: splog.sp.not.accessible:error]: The SP on the remote node (node_name_02) is not accessible because of The Service Processor on node "node_name_02" 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 configured correctly and are functional (up). Then, try the command again..
- These messages may begin appearing after an ONTAP or SP/BMC firmware update
- servprocd daemon and api-service restarted on the nodes
- HW-Assist a ping tests ok, between node magnamente LIFs and BMC IPs