1/2
SCP 6.11.3 stuck at 33% after rebooting

Rushdi Lv1Posted 2026-Aug-26 19:41

Has anyone come across the issue where, SCP 6.11.3 is stuck at 33% after reboot? This is a fresh installation of SCP.

Muhammad Abid has solved this question and earned 10 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

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

Yes — if you mean Sangfor Cloud Platform (SCP) 6.11.3, a boot/install process hanging around 33% after a reboot is something I’d troubleshoot as a SCP VM/resource or service initialization issue, rather than immediately assuming the installation is corrupted.

I checked the current Sangfor documentation, and 6.11.3 is an active SCP release. There is also a current Sangfor support article specifically showing that SCP 6.11.3 should be matched with HCI 6.11.3.

A few things I'd check first:

Confirm the HCI version

If SCP is deployed on HCI, verify the underlying HCI is also 6.11.3.
Sangfor's current guidance explicitly pairs HCI 6.11.3 with SCP 6.11.3.
Check SCP VM resources
CPU and RAM allocation.
Disk capacity and whether the SCP virtual disk is healthy.
Make sure the SCP VM isn't being constrained by HCI resource contention.
Open the SCP VM console
Don't rely only on the web interface.
Check whether the console is actually progressing, showing a service failure, or completely frozen at the same stage.

Check networking
Verify the management NIC/VLAN.
Confirm the SCP IP is still reachable after reboot.
If possible, test both ping and HTTPS access.
Consider the image/package

If this is a fresh installation, I'd strongly consider re-importing/reinstalling from the official 6.11.3 VMA rather than spending too long troubleshooting a potentially bad image.

There are also newer 6.11.3 patches in circulation. For example, Sangfor's current documentation for Veeam integration references SCP 6.11.3 + col01, with a SP_SCP_fix_col01_6113 package.

One important distinction: if it reaches 33% only after the first reboot, rather than during the initial deployment, I'd want to see exactly what the 33% screen says. That can point to a very different problem.

If you can send me a screenshot of the SCP console stuck at 33%, plus your HCI version, SCP VM CPU/RAM, and whether SCP is installed as a VM on HCI, I can narrow it down considerably.
Is this answer helpful?
Muhammad Abid Lv3Posted 2026-Aug-27 12:24
  
Yes — if you mean Sangfor Cloud Platform (SCP) 6.11.3, a boot/install process hanging around 33% after a reboot is something I’d troubleshoot as a SCP VM/resource or service initialization issue, rather than immediately assuming the installation is corrupted.

I checked the current Sangfor documentation, and 6.11.3 is an active SCP release. There is also a current Sangfor support article specifically showing that SCP 6.11.3 should be matched with HCI 6.11.3.

A few things I'd check first:

Confirm the HCI version

If SCP is deployed on HCI, verify the underlying HCI is also 6.11.3.
Sangfor's current guidance explicitly pairs HCI 6.11.3 with SCP 6.11.3.
Check SCP VM resources
CPU and RAM allocation.
Disk capacity and whether the SCP virtual disk is healthy.
Make sure the SCP VM isn't being constrained by HCI resource contention.
Open the SCP VM console
Don't rely only on the web interface.
Check whether the console is actually progressing, showing a service failure, or completely frozen at the same stage.

Check networking
Verify the management NIC/VLAN.
Confirm the SCP IP is still reachable after reboot.
If possible, test both ping and HTTPS access.
Consider the image/package

If this is a fresh installation, I'd strongly consider re-importing/reinstalling from the official 6.11.3 VMA rather than spending too long troubleshooting a potentially bad image.

There are also newer 6.11.3 patches in circulation. For example, Sangfor's current documentation for Veeam integration references SCP 6.11.3 + col01, with a SP_SCP_fix_col01_6113 package.

One important distinction: if it reaches 33% only after the first reboot, rather than during the initial deployment, I'd want to see exactly what the 33% screen says. That can point to a very different problem.

If you can send me a screenshot of the SCP console stuck at 33%, plus your HCI version, SCP VM CPU/RAM, and whether SCP is installed as a VM on HCI, I can narrow it down considerably.
EduardoOliveira Lv1Posted 2026-Aug-28 20:18
  
Check if the option Use CPU from host is flagged.

We had an issue recently where we faced this situation and the cause was the bad io perfomance.. also worth to check.

AR Lv3Posted 2026-Aug-29 19:16
  
Yes, if you're referring about Sangfor Cloud Platform (SCP) 6.11.3, I would troubleshoot a boot/install process that hangs around 33% after a reboot as a SCP VM/resource or service initialisation issue rather than presuming the installation is corrupted right away.

6.11.3 is an active SCP release, according to the Sangfor documentation I looked at. Additionally, a recent Sangfor support post explicitly states that HCI 6.11.3 and SCP 6.11.3 should be compatible.

I would start by checking a few things:

Verify the HCI version.

Make sure the underlying HCI is 6.11.3 if SCP is installed on HCI.
HCI 6.11.3 and SCP 6.11.3 are specifically paired in Sangfor's current guidelines.
Examine the SCP virtual machine resources
RAM and CPU distribution.
disc capacity and the health of the SCP virtual disc.
Verify that HCI resource contention isn't limiting the SCP virtual machine.
Launch the SCP virtual machine terminal.
Don't depend solely on the online interface.
Verify if the console is indeed moving forward, displaying a service failure, or remaining motionless at the same point.
Examine networking
Check the management VLAN and NIC.
Verify that the SCP IP is still accessible following a reboot.
Ping and HTTPS access should be tested if at all possible.
Think about the picture or package

Instead of spending too much time investigating a potentially problematic image, I would strongly advise re-importing/reinstalling from the official 6.11.3 VMA if this is a new installation.

Additionally, there are more recent 6.11.3 fixes available. For instance, SCP 6.11.3 + col01 and an SP_SCP_fix_col01_6113 package are mentioned in Sangfor's current Veeam integration documentation.

One crucial distinction is that I would like to see exactly what the 33% screen indicates if it only hits 33% on the first reboot instead of during the initial deployment. That may indicate a very different issue.

I can narrow it down significantly if you send me a screenshot of the SCP console stuck at 33%, along with your HCI version, SCP VM CPU/RAM, and whether SCP is installed as a VM on HCI.
Sangfor Jojo Lv5Posted 2026-Sep-10 16:47
  
For future inquiries about troubleshooting, product capabilities and configuration settings, feel free to use our Solvia Chatbot in the community. Available 24/7 with zero waiting time, it provides instant responses with an 88.6% accuracy rate.

I Can Help:

Change

Board Leaders

George ...

Weekly Sharers

George ...

Weekly Questioners