Step 4: Configuring the VMware Components
Before you start these procedures, install and configure the required VMware component. You can install more than one ESXi.
Adding the vCenter IP Address to the Runtime Settings
To use VMware, you must add the vCenter IP address to the tab on the vCenter Server Setting page.
To add the vCenter IP address:
- In the vSphere Web Client, click > and select the server.
- Click > > > .
- Click > > .
- In the field, enter the vCenter server IP address.
Preparing the ESXi Cluster for CloudGuard Service Deployment
The sections below describe how to configure an ESXi cluster.
Adding an ESXi to an ESXi Cluster
To add a new ESXi to a cluster:
- In the vSphere Web Client, right-click the ESXi cluster object and select .
- Configure the setting for the new host.
If there is CloudGuard Service deployed on the cluster, CloudGuard Gateway automatically installs on the new host.
- If you do not use an IP address pool or Automatic Provisioning, manually activate the CloudGuard Gateway and then configure it.
Configuring Agent VM Host Settings
To configure Agent VM settings for each ESXi server:
- In the vSphere Web Client, go to the ESXi server and select the tab for each ESXi server.
- Go to > .
- In the window, select the datastore to hold the files for the CloudGuard Gateway Service Virtual Machine.
Best Practice - Deploy the CloudGuard Gateway on ESXi server local storage and not on external storage.
- In the window, select the Port Group network that connects to the CloudGuard Gateway Service VM by default.
This Port Group is used for communication with the CloudGuard Controller.
- Install the NSX VIB on all hosts before you deploy it.
To install the NSX VIB on all ESXi:
- Log in to the vSphere Web Client.
- Select > > .
- Click for all clusters where you install NSX.
Removing an ESXi Server from an ESXi Cluster
To remove a host from a cluster:
- In the vSphere Web Client, go to .
- Select the ESXi server and click > > .
- Move the ESXi server from the cluster to a Data Center.
- Select the host and click > .
- Reboot the ESXi server.
If you did not enable Automatic Provisioning, remove the Cluster Member in SmartConsole.
NSX Grouping Objects
With the Grouping feature, you can create custom containers and assign resources, such as Virtual Machines and network adapters, for CloudGuard Service protection. After a group is defined, you can add the group as source or destination to a firewall rule.
Creating a Security Group
To create a Security Group:
- In the vSphere Web Client, go to > > .
- Click the icon.
The wizard opens.
- Enter a name and description for the new Security Group.
- Click .
- Define dynamic memberships and objects.
Select objects in the and pages.
Objects that you select are always included in the Security Group, even if these objects do not match the dynamic membership specifications.
Note - You can include other Security Groups in your new Security Group.
Creating a CloudGuard Gateway IP Address Pool
Best Practice - Create an IP address pool to automatically assign management interface IP addresses.
To create an IP address pool:
- Log in to the vSphere Web Client.
- Click > .
- In , click the
- Click .
- Click > .
- Click
- Enter a name for the IP pool and its default gateway.
- Enter the primary and secondary DNS, DNS suffix and prefix length.
- Enter the IP address ranges to include in the pool.
- Click .
Creating an IP Set
To create an IP Set:
- Log in to the vSphere Web Client.
- Click > .
- In , click the .
- Click > .
- Click .
- In the window, enter a name, description and IP address for the new Security Group.
This IP address is redirected to the CloudGuard Gateway.
- Add the new IP Set to the Security Group.
vMotion
vMotion lets you migrate active Virtual Machines between ESXi servers.
Configure network interfaces on source and target ESXi servers. Configure each ESXi server with at least one network interface for vMotion traffic. To secure data transfer, make sure only trusted parties access the vMotion network. Additional bandwidth significantly improves vMotion performance. When you migrate a Virtual Machine with vMotion without using shared storage, the virtual disk contents are also transferred over the network.
Configure the Virtual Networks on vMotion enabled ESXi server:
- On each ESXi server, configure a VMkernel port group for vMotion.
- Make sure the Virtual Machines can access the same subnets on source and destination ESXi server.
- If you use standard switches for networking, make sure the Virtual Machine port group network labels are consistent across ESXi servers. During a vMotion migration, the vCenter server assigns Virtual Machines to port groups based on matching network labels.
- If you use vSphere Distributed Switches for networking, make sure source and destination ESXi server are members of all vSphere Distributed Switches used by Virtual Machines.
For minimum impact on connectivity, applications, and security:
- The VMware distributed firewall on the target ESXi server handles existing connections until they are closed or reset.
- The CloudGuard service that runs on the target ESXi server secures new connections to and from the migrated Virtual Machine.
Important -
The HTTPS connection and the Control connection must be initialized again after vMotion. Initialize the sessions of existing connections that need a control channel, in addition to the data channel.