Configure Precryption in UCT-C
GigaVUE-FM allows you to enable or disable the Precryption feature.
Rules and Notes
The following are the memory limits to be applied to UCT-C:
| The memory limit changes depending on the numbers of vCPUs in the worker node. For example, if the worker node has 16 vCPUs, then the Precryption feature consumes around 1GB of memory (16 * 64 MB). |
| When you deploy secure tunnels, it requires additional (16 *64 MB) memory. Hence, the total memory that you must allocate for the TAP is 1 GB. |
| Protocol version IPv4 and IPv6 are supported. |
| If you wish to use IPv6 tunnels, your GigaVUE‑FM and the fabric components version must be 6.6.00 or above. |
The YAML configuration option allows you to choose the amount of buffer size.
To configure the Precryption feature in UCT-C, follow the steps listed below:
1. Go to Traffic > CONTAINER > Universal Cloud Tap - Container.
2. On the Policies page that appears, click Create.
3. In the General tab, enter or select the required information as described in the following table:
| Fields | Description |
|---|---|
|
Policy Name |
Enter a name for the Traffic Policy. The name must be unique. |
|
Monitoring Domain |
Select an existing Monitoring Domain. To create a new monitoring domain, refer to Create Monitoring Domain section in the UCT configuration guide. Only one Precryption Policy is allowed per Monitoring Domain |
|
Connections |
Select one or more connections for the policy. Once traffic policy is created for a Monitoring Domain, you cannot add or delete connections in the Monitoring Domain. |
|
Precryption Policy |
Click the radio button Yes, to enable the Precryption Policy, |
After enabling the Precryption, configure the Source Selectors, and the Rules. In this release, for Rules, Pass All option is supported.
