Resized disk1 not present after Proxy ISG resizing for more concurrent users

Products

• ISG Proxy
• ProxySG Software - SGOS

Issue/Introduction

ISG-PROXY-VA-200 was deployed with SGOS 6.7.5.14 version using ovf and vmdk file. The default ISG setup after deployment was resized to  ISG-PROXY-VA-200 - 75,000 connection count requirements (12 vCPU, 48GB vMemory, disk1 200GB, disk2 200GB)

ISG was resized as follows:

• 1vCPU => 12 vCPU
• 4GB vRAM => 48GB vRAM
• Disk1 8GB => 200GB 
• Disk2 200GB

After resizing, Disk1 200GB is not showing as present. Only Disk2 200GB is recognized.

Environment

• ISG-PROXY-VA-200
• SGOS : 6.7.5.14

Cause

Disk1 for the ISG VA should not be touched during ISG sizing:

“Do not remove or resize Hard Disk 1 as it is the boot disk and resizing is not supported. Removing this disk causes the system to become non-bootable and resizing it does not provide extra storage for the system."

KB: https://techdocs.broadcom.com/us/en/symantec-security-software/web-and-network-security/proxysg/6-7/Overview_ISG_SGW_VA/ISG_SWG_VA_create_the_swg_va/ISG_SWG_VA_resize_the_swg_va.html

Resolution

To achieve following configuration for ISG-PROXY-VA-200 - 75,000 connection count (12 vCPU, 48GB vMemory, disk1 200GB, disk2 200GB) please redeploy the ISG Proxy from scratch and resize the VA as follows:

• 1 vCPU to 12 vCPU
• 4GB vRAM to 48GB vRAM
• Disk1 8GB (do not touch the SGOS boot disk)
• Disk2 200 GB
• Create Disk3 200GB

Additional Information

• ProxySG ISG SWG VA System Requirements - https://techdocs.broadcom.com/us/en/symantec-security-software/web-and-network-security/proxysg/6-7/Overview_ISG_SGW_VA/ISG_SWG_VA_before_you_begin/ISG_SWG_VA_verify_system_requirements.html
• Resize the SWG VA - https://techdocs.broadcom.com/us/en/symantec-security-software/web-and-network-security/proxysg/6-7/Overview_ISG_SGW_VA/ISG_SWG_VA_create_the_swg_va/ISG_SWG_VA_resize_the_swg_va.html
• ProxySG VA Disk resize article - https://knowledge.broadcom.com/external/article?articleId=235572