Issue Description

When creating or expanding Virtual Storage, or replacing a cache disk, the SSD cannot be used as a cache disk and displays the error "Incompatible disk".

Handling Process

1. Check the SSD model.
2. Verify the SSD model against the compatibility list. If it is listed, proceed to the solution. If not, proceed to the next step.
3. Take a photo of the SSD for documentation.
4. （MUST DO) Verify with CTI or R&D for confirmation if the SSD is compatible or can be bypassed.

Root Cause

Not all SSDs have been test or compatible.
Thus, it is needed to verify the performance before bypassing the compatibility check.

Solution

1. Confirm with CTI or R&D whether the SSD is allowed to be bypassed.
2. Once verified, SSH to the HCI backend and apply the following commands based on your HCI version:
   • For version 5.8.8R1 and below: touch /sf/cfg/vs/.notcheckDC
   • For version 6.0.0/VS3.0.2 and above: vs_cluster_cmd.sh e 'sed -i "s|\"disk_dump\": 13|\"disk_dump\": 0|g" /sf/cfg/vs/disk/*'
   • For version 6.3.0R1 and above: vs_cluster_cmd.sh e 'for file in $(ls /sf/cfg/vs/disk ); do diskfile=/sf/cfg/vs/disk/${file}; /sf/vs/bin/vs_json_rw.py -f $diskfile -w -k disk_dump -v [0] -t json;done'
   • For version 6.8.0:
     Enter the vs container first using command: ssh -p 25022 localhost OR container_exec -n vs-cpThen execute the bypass command: vs_cluster_cmd.sh e 'for file in $(ls /sf/cfg/vs/disk ); do diskfile=/sf/cfg/vs/disk/${file}; /sf/vs/bin/vs_json_rw.py -f $diskfile -w -k disk_dump -v [0] -t json;done'
3. Proceed with the VS creation, expansion or replacement.

Sangfor HCI Compatibility List: https://community.sangfor.com/forum.php?mod=attachment&aid=MTA4MDAzfDRjYTRlNTYxfDE3MzIxNTA4MDN8NDI3MTR8Nzk0OQ%3D%3D