How to Decommission SCP from an HCI 6.11.1 R1 Cluster Without Losing vCenter Access
  

George Fady Lv2Posted 2026-Jun-18 05:01

I recently worked on a support case involving Sangfor SCP 6.11.1 R1 integrated with an HCI 6.11.1 R1 cluster, and wanted to share the troubleshooting journey in case it helps others facing the same scenario.
The Scenario
A customer had integrated SCP to manage an HCI cluster (2 aSAN nodes + 2 floating nodes, also managing VMware vCenter). Later, it was decided SCP wasn't needed for this environment. The SCP integration was removed from the HCI Manager side first — before properly releasing the resource pool on the SCP side. This caused two problems:

  • HCI Manager started blocking all vCenter operations with: "This platform is being managed by Sangfor Technologies Cloud Platform. Please go to Sangfor Technologies Cloud Platform to perform operation."

  • SCP showed the resource pool stuck in Error status, since it could no longer reach the HCI cluster.

Key Lesson #1 — Order of Operations Matters
In SCP 6.11.1, there is no Unbind/Disassociate option. The only supported way to release an HCI cluster from SCP management is:

  • Delete all tenants and tenant users under the resource pool

  • Delete the resource pool in SCP

  • Delete the cluster entry in SCP

If you remove the SCP link from the HCI side before completing these steps in SCP, you can end up in a "split state" where neither platform agrees on who owns the cluster — which is exactly what happened here.
Key Lesson #2 — Deleting the Resource Pool Is Safe for VMs
The deletion warning in SCP looks alarming (mentions VMs, networks, aDR data being cleared). In reality, this only clears SCP's management records of those resources — it does not touch the actual VMs, data, or configuration running on the HCI cluster itself. The HCI platform and its VMs continue running independently throughout this process.
Key Lesson #3 — Watch for a "Cluster Credential" Error During Deletion
Even after entering the correct SCP admin password, we hit a secondary error:
"Cluster username or password is incorrect. Please check whether cluster configurations are correct."
This wasn't about the SCP login password — it was SCP trying to live-validate its connection to the HCI cluster as part of the delete process, which was failing because the HCI-side link was already cut. Editing the resource pool's stored cluster credentials didn't resolve it either. What worked was refreshing the SCP admin session (logging out/in) and re-attempting the deletion — this cleared the stale state and allowed the deletion to complete successfully.
Final Steps to Restore vCenter Access
Once the resource pool and cluster were removed from SCP:

  • Logged into HCI Manager directly

  • Went to Nodes → VMware vCenter → Add vCenter

  • Re-added vCenter using its IP, admin credentials, and port 443

vCenter nodes were visible again immediately, and the environment returned to normal operation.

Like this topic? Like it or reward the author.

Creating a topic earns you 5 coins. A featured or excellent topic earns you more coins. What is Coin?

Enter your mobile phone number and company name for better service. Go

Prosi Lv3Posted 2026-Jun-20 09:42
  
Thank you for the information
AR Lv3Posted 2026-Jun-18 17:12
  
Thanks to share
Humayun Ahmed Lv4Posted 2026-Jun-18 12:32
  
Thanks to share!