Service Processor is not reachable due to sp.dup.ip:error SP IP address in use by another system

• ONTAP 9
• Service Processor
  • Service Processor (SP)
  • Baseboard Management Controller (BMC)

• When executing system node power show on the cluster, one of the nodes returns an error stating the Service Processor is not reachable.

Cluster::> system node power show

Node             Status
---------------- -----------
node1   on

Error: The Service Processor on node "node2" 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.
node2   -
2 entries were displayed.

EMS report a duplicate IP

Node1: spnr_main: sp.dup.ip:error]: SP IP address xx.xx.xxx.xxx in use by another system.

SP-LATEST-SYSTEM-EVENT-LOG (AutoSupport Log)

Record 1316: Fri Feb 20 07:29:27.688416 2026 [BMC.notice]: eth0 ipv4 address is duplicated.

• SP status is online from cluster shell.
• The SP IP is inaccessible via SSH but can be pinged. 

user@XX.XX.XXX.XX's password:
Permission denied, please try again.

• Same credentials works on cluster mgmt, node mgmt and other node SP IPs. 

Following steps doesn't resolve the issue:

• Rebooted SP using the command ::*> system service-processor reboot-sp -node <>
• Restarted the Service Processor API service:
  

  cluster::*> system service-processor api-service modify -is-enabled false
cluster::*> system service-processor api-service modify -is-enabled true

• Renewed internal certificates using the command ::> system service-processor api-service renew-internal-certificate