Node Reporting “splog.sp.not.accessible” due to network firewall configuration
Applies to
- ONTAP
- AFF/FAS platforms
- Clustered ONTAP environments with mixed node types
- Sites with network segmentation or firewall policies between management and SP/BMC interfaces
Issue
- Nodes in a cluster report the following error:
Message: splog.sp.not.accessible: The SP on the remote node (xxxxDestNodexxxx) is not accessible because the Service Processor on node "xxxxDestNodexxxx" is not reachable. Verify that the SP or BMC is online, verify that the 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.- The command system node power show returns error:
Error: Failed to initiate power control operation due to API error- Firewall logs and network tests reveal:
- SP and management IPs are on different networks/VLANs.
- Attempts to connect via port 50000 fail but port 443 traffic is observed instead.
system service-processor api-service showconfirms SP API is enabled and set to port 50000.- Network Firewall configuration has some services blocked
