ProxySG SWG Gen2 Initial Configuration Guide
ProxySG SWG Gen2 Initial Configuration Guide
Virtual Appliance
Initial Configuration Guide
for High-Performance Models
Platform: VMware vSphere Hypervisor
Broadcom, the pulse logo, Connecting everything, and Symantec are among the trademarks of Broadcom. The term
“Broadcom” refers to Broadcom Inc. and/or its subsidiaries.
The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit
www.broadcom.com.
Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability,
function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does
not assume any liability arising out of the application or use of this information, nor the application or use of any product
or circuit described herein, neither does it convey any license under its patent rights nor the rights of others.
Document Revision: 02/2020
Additional Restrictions
ProxySG Appliances
Within sixty (60) days of the date from which the User powers up the ProxySG appliance (“Activation Period”), the Administrator must complete the
ProxySG licensing requirements as instructed by the ProxySG to continue to use all of the ProxySG features. Prior to the expiration of the Activation
Period, the ProxySG software will deliver notices to install the license each time the Administrator logs in to manage the product. Failure to install the
license prior to the expiration of the Activation Period may result in some ProxySG features becoming inoperable until the Administrator has completed
licensing.
Proxy Client:
The Administrator may install the Proxy Client only on the number of personal computers licensed to them. Each personal computer shall count as one
“user” or “seat.” The ProxyClient software may only be used with Blue Coat ProxySG appliances. The Administrator shall require each user of the Blue
Coat ProxyClient software to agree to a license agreement that is at least as protective of Blue Coat and the Blue Coat ProxyClient software as the Blue
Coat EULA.
The ProxySG Virtual Appliances (MACH5 or Secure Web Gateway edition) are licensed on either a perpetual or subscription basis for a maximum
number of concurrent users. Support for the Virtual Appliances will be subject to the separate support agreement entered into by the parties if the
Administrator licenses the Virtual Appliances on a perpetual basis. The Virtual Appliances will (a) not function upon expiration of the subscription if the
Administrator licenses the Virtual Appliances on a subscription basis; or (b) if the traffic exceeds the maximum number of concurrent
users/connections, features may not function beyond the maximum number of concurrent users/connections. This means that, in these cases, the
network traffic will only be affected by the default policy set by the Administrator (either pass or deny). Such cessation of functionality is by design, and
is not a defect in the Virtual Appliances. The Administrator may not install the same license key or serial number on more than one instance of the
Virtual Appliance. The Administrator may move the Virtual Appliance along with its license key and serial number to a different server, provided that
server is also owned by the Administrator and the Administrator permanently deletes the prior instance of the Virtual Appliance on the server on which
it was prior installed. The Virtual Appliances require a third party environment that includes software and/or hardware not provided by Blue Coat,
which the Administrator will purchase or license separately. Blue Coat has no liability for such third party products.
ii
Contents
Contents
Chapter 1: Overview
About This Guide .................................................................................................................................. 8
Conventions Used in This Guide........................................................................................................... 9
Terminology ........................................................................................................................................ 10
iii
Initial Configuration Guide for SWG VA High-Performance Models
iv
Chapter 1: Overview
The Secure Web Gateway Virtual Appliance (SWG VA) is a software solution that can
be installed and deployed on a server running VMware vSphere Hypervisor. SWG VA
facilitates server consolidation by co-existing with other virtual machines on a single
hardware platform, including Symantec Content Analysis and Blue Coat ProxySG
Virtual Appliance MACH5 Edition. With the SWG VA providing security, the other
virtual machines can provide branch office services (such as Domain Controller, print,
DNS, and DHCP), as well as any VMware-certified software applications.
Symantec is VMware Ready™, having worked closely with VMware to ensure that the
SWG VA runs efficiently in the virtual environment and meets all technical criteria and
specifications.
Note: VMware Ready is a validation program designed to provide the best possible
user experience among virtual appliances deployed in production. This status indicates
that Symantec has followed best practices and that the SWG VA is optimized for
VMware vSphere, helping to ensure “ready-to-run” reliability and security.
7
Initial Configuration Guide for SWG VA High-Performance Models
8
Overview
Convention Example
Terms that identify buttons, fields, menus, or options on 1. Select Maintenance > Licensing > Install.
the user are shown in bold Arial font. 2. Click Retrieve.
Text that you must type exactly is denoted using bold, Enter https://
Courier New font. <ProxySG_IP_address>:8082/mgmt
9
Initial Configuration Guide for SWG VA High-Performance Models
Section 3 Terminology
The following table lists the terms used in this guide.
Term Definition
Appliance Serial A string of numbers that uniquely identify a virtual appliance. On the first bootup,
Number you must enter the appliance serial number to begin initial configuration on the SWG
VA. High-performance model serial numbers have “59” as the middle digits.
Datastore Storage defined in VMware vSphere Hypervisor, made up of one or more physical
disks.
Director The Symantec Director is a centralized management platform for managing ProxySG
configurations and policies. It allows you to manage multiple ProxySG appliances in
your deployment.
Enable Mode A mode that allows administrative privileges on the command line interface (CLI) of
the ProxySG appliance. You can make changes to the configuration in this mode.
Enable Password A password used to enter enable mode so that you can modify settings and configure
an appliance. Enable mode is for administrators who are authorized to configure an
appliance.
VMware vSphere The physical computer (host server) on which VMware’s virtualization product is
Hypervisor installed. The vSphere Hypervisor provides CPU and memory resources, access to
storage, and network connectivity to multiple virtual machines.
Management Console The web interface for configuration of the SWG VA.
Enter the following URL in the web browser to directly access the Management
Console:
https://<ProxySG_IP_address>:8082
<ProxySG_IP_address> is the IP address of your SWG VA.
OVF Open Virtualization Format. A format for packaging and distributing virtual
machines. The OVF file in the Virtual Appliance Package (VAP) is an XML text file
that defines the attributes of a specific virtual machine package.
SWG VA A ProxySG with a Secure Web Gateway (SWG) license running as a virtual appliance
on VMware’s vSphere Hypervisor.
VAP The Virtual Appliance Package is the zip file that contains the OVF file and the
virtual disk file (.vmdk) required for creating the SWG VA. It also includes a PDF of
this guide, the Initial Configuration Guide for SWG VA High-Performance Models.
10
Overview
Term Definition
Virtual Machine An instance of an operating system and one or more applications that run in an
isolated partition of a VMware vSphere Hypervisor. SWG VA is a virtual machine.
VLAN Virtual Local Area Network. A local area network (LAN) that is created with
software. It maps clients (hosts) logically rather than physically, and extends across
LAN segments instead of remaining in one physical LAN.
11
Initial Configuration Guide for SWG VA High-Performance Models
12
Chapter 2: Before You Begin
This chapter assumes that you have configured your hardware platform as a VMware
vSphere Hypervisor, created datastores, and configured the vSphere Hypervisor for
network access. For information on setting up your vSphere Hypervisor, refer to
VMware documentation.
Before you proceed with creating the Secure Web Gateway Virtual Appliance (SWG
VA), perform the following tasks:
p "Verify Support for VMware Products" on page 14
p "Verify System Requirements" on page 15
p "Verify Resource Availability" on page 17
p "Retrieve Appliance Serial Numbers" on page 19
p "Create a Virtual Switch" on page 21
Note: The instructions in this document are for vSphere Client version 5.5.
13
Initial Configuration Guide for SWG VA High-Performance Models
6.7.x, 7.1.x, and 7.2.x ESXi 5.5, 6.0, 6.5, and 6.7
14
Before You Begin
Note: The following requirements reflect Symantec’s test environment. Using the same
or a similar configuration should achieve satisfactory performance of the SWG VA;
however, you should expect different performance results if your resources or virtual drive
configuration are different from the configuration described in Table 2–1 and Table 2–2.
Be aware that over-provisioning CPUs can cause license suspension, but under-
provisioning can cause sub-optimal VA performance and operation.
Resource Requirement
The following table lists requirements for each model, including recommended and
alternate virtual drive configurations. Symantec recommends creating 100GB virtual
drives, although models with higher storage requirements can have larger drives. Note that
each virtual drive must be the same size.
Note: After you have deployed your virtual appliance, you should have the number of
virtual disks that the model requires (listed in the following table) plus a boot disk. The
boot disk is automatically created during deployment.
15
Initial Configuration Guide for SWG VA High-Performance Models
Note: With fewer disks, more throughput is required per disk. See “Throughput
Requirements Per Virtual Disk” on page 55 for disk read and write throughput rates per
disk.
16
Before You Begin
17
Initial Configuration Guide for SWG VA High-Performance Models
2. To display the summary of the vSphere Hypervisor’s resources, select the ESX server
and click the Summary tab.
18
Before You Begin
Note: Be sure to use the correct serial number for your SWG VA. It helps ensure that
your license is valid.
b. Click Next.
The License Agreement page displays.
5. Read and accept the License Agreement.
a. Read the license agreement.
b. Select I accept at the bottom of the page.
c. Click Next.
A serial numbers page displays.
6. Record the appliance serial number(s). You will refer to the serial number when you
perform initial configuration on the SWG VA.
Perform one of the following tasks to note the appliance serial number:
• Write down the serial number(s) listed on the screen.
• Download a comma-separated values (CSV) file containing all of the serial
numbers. Click the link beside Download as CSV file and save the file to disk.
19
Initial Configuration Guide for SWG VA High-Performance Models
For future reference, record the location and name of the SWG VA with the serial
number.
Note: Each appliance serial number is unique. When performing initial configuration on
the SWG VA, make sure that you use a dedicated serial number for each instance of a
SWG VA. If you reuse a serial number, the SWG VA license could be suspended. See
“Serial Numbers and Licensing” on page 50 for more information.
Connection Limits
The SWG VA supports a maximum number of concurrent connections and enforces this
by limiting the number of unique clients. Connections will be queued after the connection
limit is reached.
Use the show license CLI command to verify the number of concurrent users (i.e.,
connections) your SWG VA is licensed for.
To upgrade the connection limit for your SWG VA, see "How do I upgrade the connection
limit for the SWG VA?" on page 51. Note that you will need to reboot after upgrading the
license to reset the connection limits.
20
Before You Begin
Note: If you use VLANs for segregating traffic within the vSphere Hypervisor or across
your network, you must enable VLAN trunking on all interconnecting devices such as
switches or routers. This guide does not include information on VLAN configurations.
Note: This guide assumes that you do not use VLANs. If you use VLANs, select All
(4095) to enable VLAN trunking. This value enables Virtual Guest Machine Tagging
mode on the switch, and allows the virtual switch to preserve VLAN tags between the
virtual machine and the external switch/router.
8. Click Next.
9. Verify the details and click Finish.
21
Initial Configuration Guide for SWG VA High-Performance Models
22
Chapter 3: Create the SWG VA
This chapter describes how to deploy a virtual appliance on the vSphere Hypervisor and
ensure that the SWG VA has the resources available for optimal performance.
To create the SWG VA, you must have administrator privileges on the vSphere
Hypervisor.
This chapter covers the following topics:
p "Download the Virtual Appliance Package" on page 24
p "Deploy a SWG VA" on page 26
p "Reserve Resources for the SWG VA" on page 29
p "Power on the SWG VA" on page 31
Note: The instructions in this chapter are for vSphere Client version 5.5.
23
Initial Configuration Guide for SWG VA High-Performance Models
Note: If the VM is running ESXi 6.x, use the OVF file with “ESXi6.x” in its name in
"Deploy a SWG VA" on page 26.
Note: If you have already downloaded the VAP, skip this procedure and proceed to
"Deploy a SWG VA" on page 26.
Note: The first time you download files, you are prompted to install the Download
Manager. Follow the onscreen prompts to download and run the installer. For more
information, refer to https://www.symantec.com/support-center/getting-started.
24
Create the SWG VA
Note: Because the .ovf file includes a pointer to the .vmdk file, you must extract and
store the contents of the .zip file within the same folder. Do not rename the files.
25
Initial Configuration Guide for SWG VA High-Performance Models
Note: The equivalent command in VI Client is File > Virtual Appliance > Import.
c. In the Deploy from a file or URL field, browse to the location of the OVF file.
Alternatively, copy and paste the URL of an OVF file.
Click Next.
d. Verify the OVF template details and click Next.
e. Enter a name for the SWG VA, such as SGVA_Sydney. (The default name is
ProxySG Model SWG). You should enter a name that is unique within your
vSphere Hypervisor host.
f. Select an Inventory Location. Click Next.
g. In the Configuration dialog, select the SWG VA model, for example, SG-VA-
C2S.
26
Create the SWG VA
Note: If you have purchased a SG-VA-C1XS model, choose SG-VA-C1S from the
Configuration list, since these two models have the same basic configuration.
h. In the Storage dialog, select a datastore with sufficient free space for your
SWG VA model. See Table 2–2, "Model-Specific Requirements" on page 16
for disk space requirements. Click Next.
i. In the Disk Format dialog, select one of the thick provisioning types for the
virtual disk format and click Next.
j. In the Network Mapping dialog, specify the networks for each interface.
k. Click Next.
l. Review the deployment settings and click Finish to begin creating the SWG
VA.
See the Recent Tasks panel for the progress bar indicating the percentage
complete.
2. (Required only if you plan to use the third and fourth interfaces) Enable the vSwitch
for the third and fourth interfaces.
a. Select the SWG VA on the vSphere Hypervisor Server.
b. Right click and select Edit Settings.
c. Select Hardware > Network Adapter 3.
d. In the Device Status panel, mark the Connect at power on check box.
If necessary, repeat these steps for the fourth interface.
e. Click OK.
Note: When the VA is first imported, it has one 100 GB data drive attached.
Depending on your SWG VA model, you may need to create additional virtual
disks. For example, the SG-VA-C16S requires 800 GB of storage space so you
must create additional drives, with each drive being the same size. See Table 2–2,
"Model-Specific Requirements" on page 16.
27
Initial Configuration Guide for SWG VA High-Performance Models
Note: For optimal performance, create each virtual disk on a different physical
disk.
Note: Virtual disks must be thick provisioned (either Lazy or Eager Zeroed).
i. Click Finish.
j. Repeat steps 3a–3i for each virtual disk that your SWG VA model requires.
4. Click OK to close the Virtual Machine Properties window.
28
Create the SWG VA
d. Specify the Reservation value for the CPU that you determined in Step 1e.
Ensure this value is larger than the minimum specified in "Verify System
Requirements" on page 15 ; for example, change the Reservation value to
5200 MHz.
Retain the default values for the other options.
3. Specify the memory reservation for the SWG VA.
29
Initial Configuration Guide for SWG VA High-Performance Models
b. Specify the Reservation value for memory allotted to the SWG VA.
Input the value for Virtual Memory recommended for your SWG VA model;
see Table 2–2, "Model-Specific Requirements" on page 16.
Retain the default values for the other options.
4. Recommended if the SWG VA’s datastore is shared by other virtual machines on the
vSphere Hypervisor Server:
Give the virtual disks on the SWG VA a higher priority access to the physical disks on
the vSphere Hypervisor Server.
a. On the Resources tab, select Disk.
b. For each virtual drive, change the value to High in the Shares field. Setting
this value to high ensures that the SWG VA gains higher priority access to
disk resources, as compared to other virtual machines that use the same
physical disks.
5. Click OK to save your settings.
For additional settings you may want to modify, see "Optional Settings for Optimal
Performance" on page 56.
30
Create the SWG VA
31
Initial Configuration Guide for SWG VA High-Performance Models
32
Chapter 4: Configure the SWG Virtual Appliance
This chapter describes how to perform the initial setup and configuration of the Secure
Web Gateway Virtual Appliance (SWG VA) for transparent redirection of traffic. The
following topics are covered in this chapter:
p "Prepare for Initial Configuration" on page 34
p "Complete Initial Configuration" on page 35
p "Verify Your Configuration" on page 39
p "Retrieve and Install the SWG VA License" on page 40
p "When to Power Off the SWG VA" on page 42
p "Monitor the SWG VA" on page 43
p "Additional References" on page 45
Note: The instructions in this chapter are for vSphere Client version 5.5.
33
Initial Configuration Guide for SWG VA High-Performance Models
Appliance Serial Refer to the appliance serial number that you recorded in
Number "Retrieve Appliance Serial Numbers" on page 19.
Interface configuration Identify the IP addresses and subnet masks for the
interfaces.
You also have an option to assign a VLAN ID to each
interface. If you use VLANs for segregating traffic within
the vSphere Hypervisor Server or across your network,
you must enable VLAN trunking on all interconnecting
devices such as switches or routers. This guide does not
include information on VLAN configurations.
Primary DNS server Provide the IP address for the primary DNS server.
Administrator The password you assign here will also be used for
username (ID) and accessing enable mode in the command line interface
password (CLI). Enable mode allows you to make configuration
changes.
The default enable username is admin.
34
Configure the SWG Virtual Appliance
2. Access the virtual console of the SWG VA on the vSphere Hypervisor Server.
a. Select the SWG VA on the vSphere Hypervisor Server.
b. Select the Console tab and click inside the console window to activate your
mouse.
3. The appliance serial number is unique for each appliance and must be used on only
one SWG VA. For more information, see "Retrieve Appliance Serial Numbers" on
page 19.
a. Enter the appliance serial number at the prompt.
Note: The leading zeros are significant for serial numbers. Enter all 10 digits at
the prompt.
b. Press Enter.
4. Follow the prompts and enter the details in the setup script.
a. Press Enter three times to activate the serial console.
Note: To release the mouse from the VMware client’s Co ns o le tab, press
Ctrl+Alt.
b. When asked How do you plan to configure this appliance? specify your
preference for either configuring the SWG VA manually or using Director.
If you are using Director, assign a registration password on Director and enter
the password in the setup console when prompted. For information on setting
up a registration password, refer to the Symantec Director Configuration and
Management Guide.
c. At the Enter interface number to configure prompt, specify an interface.
35
Initial Configuration Guide for SWG VA High-Performance Models
36
Configure the SWG Virtual Appliance
Note: If you have this type of deployment and do not perform these steps, the SWG VA
will be unable to connect to the server and the license may be suspended.
Note: If you do not want to forward all client HTTP requests to the hosts specified
in the sequence, do not enter the default-sequence add <host_alias> command
shown below. Instead, you will configure policy to use the forwarding host. For more
information on forwarding and proxy chaining, refer to the SGOS Administration
Guide.
#conf t
Enter configuration commands, one per line. End with CTRL-Z.
#(config)forwarding
#(config forwarding)create host <host_alias> <host_name> http proxy
ok
#(config forwarding)default-sequence add <host_alias>
ok
#(config forwarding)download-via-forwarding enable
37
Initial Configuration Guide for SWG VA High-Performance Models
ok
In the policy above, <host_alias> is the forwarding host you configured in the CLI.
38
Configure the SWG Virtual Appliance
Note: When you enter the URL for the Management Console, the browser may
display an error about an untrusted connection or security certificate. Depending on
the browser you use, you must proceed with the connection to access the Management
Console or add an exception to allow access to the web site. For specific instructions,
refer to the documentation for the browser.
2. In the prompt that appears, enter the user name and password that you created in
"Complete Initial Configuration" on page 35. The Management Console displays.
39
Initial Configuration Guide for SWG VA High-Performance Models
Note: If the SWG VA is a downstream proxy and cannot access these servers
directly, make sure you have performed the additional configuration steps in "Upgrade
and Downgrade Considerations" on page 53 before completing the procedure below.
The SWG VA license contains data that is used to uniquely identify the SWG VA as a Blue
Coat appliance.
Note: If a license is not installed, after you power on the appliance, users who open a
browser window will see an exception page indicating that the device is not licensed.
Note: If you have blocked the Symantec NTP servers, add a local server.
2. Click Retrieve.
3. In the dialog that opens:
a. Enter your MySymantec account login information.
40
Configure the SWG Virtual Appliance
Note: The Symantec WebFilter (formerly BCWF) license is not included with the high-
performance models of SWG VA and must be purchased separately.
41
Initial Configuration Guide for SWG VA High-Performance Models
Note: Symantec recommends that you use the shutdown command instead of
powering off the SWG VA using the vSphere client to avoid losing recent
configuration changes.
42
Configure the SWG Virtual Appliance
The health state displays at the top right corner of the Management Console and in the
State field on the health monitoring licensing page (Statistics > Health Monitoring >
Licensing).
The current state of a component is determined by the relationship between its current
value and its monitoring thresholds. The Warning and Critical states have thresholds
associated with them.
Each component’s health state begins at OK. If the value exceeds the Warning threshold
and remains there for the threshold’s specified interval, the component’s health transitions
to the Warning state and the SWG VA issues a warning alert.
When a component is in the Warning state and the Critical threshold is exceeded for the
specified interval, the component health transitions to the Critical state and an error alert is
issued.
If the problem is resolved, the value returns below the Warning threshold. If the value stays
below the Warning threshold longer than the specified interval, the state returns to OK.
To edit the thresholds, click Set Thresholds at the bottom of the Maintenance > Health
Monitoring tab. For more information on thresholds, see the SGOS Administration Guide.
43
Initial Configuration Guide for SWG VA High-Performance Models
44
Configure the SWG Virtual Appliance
45
Initial Configuration Guide for SWG VA High-Performance Models
46
Appendix A: Supplemental Information
This appendix answers some questions you may have about the following topics and
the SWG VA:
p "Features" on page 48
p "Serial Numbers and Licensing" on page 50
p "Upgrade and Downgrade Considerations" on page 53
p "Throughput Requirements Per Virtual Disk" on page 55
p "Optional Settings for Optimal Performance" on page 56
47
Initial Configuration Guide for SWG VA High-Performance Models
Section 1 Features
This section covers the following topics:
p "How do features vary between the various ProxySG editions and licenses?" on page
48
p "Can I manage SWG VA using Sky UI?" on page 49
48
Supplemental Information
Table A-1
49
Initial Configuration Guide for SWG VA High-Performance Models
Your license specifies the maximum number of CPUs for your SWG VA. If you have configured
more than the maximum, your license will be suspended. The SWG VA event log shows an error
and the health monitoring alert shows Critical. See "Monitor the SWG VA" on page 43.Why
is my license suspended?
First, verify that you do not have duplicate serial numbers (see "How can I prevent
duplicate serial numbers?" ) and that you have not exceeded the number of CPUs that your
license allows (see "Can I configure more CPUs than my license allows?" ). To determine
the number of CPUs that your license allows, issue the show license CLI command.
If the license validation status still has a warning, the SWG VA might be unable to connect
to the Internet.
If the SWG VA has not been able to contact the license validation server, the license will
not be reactivated until connectivity to the Internet is restored. To fix this problem,
troubleshoot network connection problems within your deployment.
50
Supplemental Information
If the SWG VA is a downstream proxy in a forward proxy deployment and cannot access
Symantec websites directly, make sure that you have created and configured an HTTP
forwarding host.
Note: You cannot request a user limit upgrade and renew a subscription on a single
order; the upgrade and renewal must be on separate orders.
51
Initial Configuration Guide for SWG VA High-Performance Models
9. To verify that the connection limit for the SWG VA has been upgraded, click the View
tab and confirm that the number of concurrent users has increased.
Note: You cannot request a connection limit upgrade and renew a subscription on a
single order; the upgrade and renewal must be on separate orders.
52
Supplemental Information
Note: Upgrading a MACH5 VA or SWG V100 to SGOS 6.7 will not convert the VA to a
high-performance model. You must purchase a new license to use a high-performance
model.
• You do not require a VAP to upgrade SGOS on the VA; VAPs are used for initial configuration
only. The upgrade process for a VA is the same as for a physical appliance. See the ProxySG
Upgrade/Downgrade WebGuide for details.
Upgrade SGOS
Upgrading the SGOS version consists of associating the activation code with the existing
serial number, and then rebooting the appliance to apply changes.
Use the procedure outlined in "Upgrade the VA Model" below, but skip steps 7 through 9
because they are needed only for VA model upgrades.
53
Initial Configuration Guide for SWG VA High-Performance Models
9. Follow the instructions in "Reserve Resources for the SWG VA" on page 29 to specify
additional CPU cores, memory, and disks as allowed by the upgraded model. Note that
over-provisioning CPUs can cause license suspension, but under-provisioning can
cause sub-optimal VA performance and operation.
See "Verify System Requirements" on page 15 for details.
10. Reboot the appliance.
11. Check the appliance health status. If you encounter health warnings or errors, see in
"Serial Numbers and Licensing" on page 50. Alternatively, search for Symantec
knowledge base articles:
https://support.symantec.com/en_US/proxysg.html
54
Supplemental Information
Model Number of Drive Size Disk Read Disk Write Read Request Write
Drives (GB) Throughput Throughput Rate (IOPS) Request Rate
(Mbps) (Mbps) (IOPS)
Model Number of Drive Size Disk Read Disk Write Read Request Write
Drives (GB) Throughput Throughput Rate (IOPS) Request Rate
(Mbps) (Mbps) (IOPS)
Model Number of Drive Size Disk Read Disk Write Read Request Write
Drives (GB) Throughput Throughput Rate Request Rate
(Mbps) (Mbps) (IOPS) (IOPS)
55
Initial Configuration Guide for SWG VA High-Performance Models
Note: The following settings could negatively impact other virtual machines on your
ESX server.
56
Supplemental Information
Set the CPU Scheduling Affinity to the logical processors on the same CPU. For example,
if the host has 24 processors per socket, the scheduling affinity is set to any of the 24
logical processors on CPU0.
The NUMA Memory Affinity should be set to use memory from Node 0.
57
Initial Configuration Guide for SWG VA High-Performance Models
58
Supplemental Information
59
Initial Configuration Guide for SWG VA High-Performance Models
60