Hyper Converged Infrastructure (HCI/aSV)

Sangfor HCI and aSV provide a unified infrastructure combining compute, storage, networking, and built-in security to simplify deployment, operations, and services.
{{sendMatomoQuery("Hyper Converged Infrastructure (HCI/aSV)","Features")}}

Features

{{ $t('productDocDetail.updateTime') }}: 2025-12-29

1.     Isolation Framework + Slow Disk Handling:  A  software-based  isolation framework   is   implemented  to   isolate  fault   points   and   prevent   issue amplification.  This   effectively  resolves  issues  where   a  slow  disk,  RAID controller freeze,  physical  host  hang,  or  network  packet  loss/fluctuation could cause the entire cluster to hang and lead to business disruption.

2.     Storage Network Unhealthy Detection: Through  network  port  probing, the system detects packet loss and latency. Faulty ports in link aggregation are proactively isolated to enable rapid service recovery.

3.     Optimization   for   External  Storage  Cluster  Freezing:    Resolves   all currently known issues in external storage scenarios that could cause virtual machines  on  the   node  or  the  entire  cluster  to   become   sluggish   or unresponsive.

4.     Performance Testing:  Currently, newly created virtual machines or those migrated   from   VMware   to    HCI    may   perform    poorly   under    default configurations,  requiring  backend  tuning  by  R&D.  Default  configuration performance has been optimized to improve user experience.

5.     External Storage Support for Shared Disks: In external storage scenarios, shared virtual disks can now  be created and attached to multiple virtual machines, supporting clustered applications like Oracle RAC and MQ.

6.     Support for 64 Disks per Virtual Machine: Single virtual machine can now support up to 64 virtual disks, meeting the needs of customers requiring large-capacity VMs (e.g., for PACS applications).

1.1.1.1 Others

1.     If HCI has been managed by SCP (earlier than SCP6.7.30) before upgrading to HCI6.9.0, please upgrade SCP to SCP6.7.30 and above (including SCP6.9.0) before upgrading HCI.


2.    After   upgrading  SCP6.7.0  to   SCP6.7.30   and  above  (including   SCP6.9.0), please contact Sangfor Support for further inspection.

3.    Since  SCP6.8.0  has  been  containerized,  to  upgrade  an  earlier  version  to SCP6.8.0  or   SCP6.9.0,  please  add  a  disk  (400  GB)  to  the   platform  for container image storage so that databases will not be affected by disk IO from container images.

1. The offline licensing(virtual key) method is supported only when SCP6.8.0 is deployed on HCI6.8.0 or later.

2. When using a virtual key to upgrade to SCP6.8.0, the original license key file will become invalid, and required to renew the license key with the new device info. This licensing

method is supported only when SCP6.8.0 is deployed on HCI6.8.0 or later. Therefore, resource pools of earlier versions may cause SCP licensing to fail.

3. For HCI systems upgraded from versions earlier than 6.8.0 to version 6.8.0 or later using a virtual key, it is necessary to regenerate the license, as the device information file must now include details for two nodes.