--- title: "Create a vIPS Cluster for Azure" slug: "create-a-vips-cluster-for-azure-3" tags: ["Product Usage"] updated: 2026-11-19T12:27:13Z published: 2026-11-19T12:27:13Z canonical: "docs.trellix.com/create-a-vips-cluster-for-azure-3" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Create a vIPS Cluster for Azure A Cluster is a collection of Virtual IPS Sensors that protect a group of instances. The **Clusters** tab allows you to configure Clusters and the corresponding protected groups. **Steps:** 1. In the Manager, go to **Devices** → **** → **Global** → **Device Manager**. The **Device Manager** page is displayed. 2. Select the **vIPS Clusters** tab. The page displays Clusters. When you select any Cluster, details for the specific groups protected by it are displayed. ![GUID-0B2CE98B-14EB-457B-9CCC-1ED93E7E6544-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-29effef1-d595-56ab-f4db-30e4c4d500b1(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) | Option | Definition | | --- | --- | | **Cluster Name** | Name of the Cluster | | **Description** | Description of the Cluster | | **Capacity** | Displays the total capacity of license required for all member Sensors in the cluster. | | **Member Sensors** | Number of Member Sensors in the selected Cluster > [!NOTE] > Note > > Clicking on this number redirects you to **Devices** → **** → **Devices** → **Summary**. Here, the summary of the Member Sensors is displayed. | | **License** | Displays the license(s) status of the cluster. **Auto-assignment of license(s) to the device:** If sufficient licenses(s) are available in the pool, the license(s) will be auto-assigned to the device. However, if enough license(s) are unavailable in the pool, the partial assignment of license(s) will not be permitted. - When a standalone Sensor or a member Sensor is registered successfully, and enough license(s) are available in the pool, the license(s) will be auto-assigned to the standalone Sensor or a member Sensor. - When you upgrade the Manager, and enough license(s) are available in the pool, the license(s) will be auto-assigned to the Sensor. - When the license(s) assigned to the device expires and sufficient unassigned license(s) are available in the pool, license(s) will be auto-assigned to the device. **Manual assignment of license(s) to the device:** You can assign a license by clicking the ![GUID-AD58F10B-F37A-45AA-A55D-0DD7A02B2AA1-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-0fc8b103-cf8e-aaf6-51c2-e2f460c69236(4).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) icon. However, you cannot perform the license assignment if the cluster is empty. In such scenarios, the ![GUID-AD58F10B-F37A-45AA-A55D-0DD7A02B2AA1-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-0fc8b103-cf8e-aaf6-51c2-e2f460c69236(4).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) icon will be hidden. The license(s) status can be one of the following options: - ![GUID-89BC390A-3C39-40F9-BCC2-CF115261968D-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-6172e8f6-b39d-1f7f-337c-29971e8ca5e4(12).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D)**Required**: The reason can be one of the following: - The license(s) has not been assigned. - The license(s) are assigned, but their capacity is less than the cluster's configured capacity. > [!NOTE] > Note > > If a combination of expired and insufficient licenses exists, the insufficient license takes a higher priority. - ![GUID-C395F07B-D0CD-480A-BCC2-FB886010F5DD-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-5f3ecb5f-3b80-d67f-3d11-265ebca482f0(15).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D)**Present**: The sufficient license(s) are present and valid. - ![GUID-7B2E01C8-BD1B-4E8F-8F61-6FC4E27E8413-low.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-4044a27a-e611-308e-e3a6-ca90ad25002e(12).jpg?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D)**Expired**: The license(s) are assigned, but one or more license(s) are expired. - ![GUID-D70B49BB-3DC3-44A9-98BE-B347D2898838-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-04629069-d5b7-1b38-94f0-0d92c8d7b006(14).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D)**Grace Period**: The assigned license(s) have expired and are now running on a grace period. > [!NOTE] > Note > > A grace period of **30 days** is provided to subscription-based system licenses after they expire. | | **Last Updated** | **Time** — Date in format, and time when the Cluster was last updated **By** — User who modified the Cluster | | ![GUID-0E47A2C8-D361-4090-B96C-F756BAC98E17-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-36cfcf5c-cac8-98ad-f4ac-c99e49a78932(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) | Refresh the status of all the Clusters. | | *Search* | Enter the keyword to search the required Clusters. | | ![GUID-B9B906D7-0A24-439D-9CCA-7E3B57735B45-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b18eb240-17a1-974e-62ee-051dbdfb422d(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) | Create a new Cluster. | | ![GUID-DDEB30D1-8F15-44F5-A05F-3D3C59BD2E8F-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-082bb84f-15a8-3052-bc92-5010ec755a83(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) | Deletes a Cluster Perform the following steps to delete a Cluster: 1. Select the Cluster and click ![GUID-DDEB30D1-8F15-44F5-A05F-3D3C59BD2E8F-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-082bb84f-15a8-3052-bc92-5010ec755a83(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D). 2. Click **OK** to delete the selected Cluster, or click **Cancel** to return to the **Clusters** page. \| ![GUID-23A0B162-5ADA-4EF1-8E18-756B64BDC0B7-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-89559d5b-7c67-658b-086d-343c5cb38530(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) \| \| --- \| | | ![GUID-23A0B162-5ADA-4EF1-8E18-756B64BDC0B7-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-89559d5b-7c67-658b-086d-343c5cb38530(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) | | **Save as CSV** | Creates a .csv list of the list of Clusters | | **View VMs** | To view the VMs protected by the Clusters | 3. To add a new Cluster, click ![GUID-B9B906D7-0A24-439D-9CCA-7E3B57735B45-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-b18eb240-17a1-974e-62ee-051dbdfb422d(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D). 4. The **Add Cluster** panel appears where you can update the Controller configuration, and enter the shared secret key for the Cluster to establish communication with your Manager. 5. Enter the following details: **Option definitions** | Option | Definitions | | --- | --- | | **Cluster Name** | Enter a unique name for the cluster. > [!NOTE] > Note > > The minimum length for a name is 1 character. The name can contain up to 50 alphanumeric (upper or lower case letters) characters, including hyphens and underscores. The name must begin with a letter. | | **Description** | Enter a description for the Cluster. > [!NOTE] > Note > > The minimum length for description is 1 character. The maximum allowed character length is 255 characters. | | **Shared Key** | Enter the shared key used by the Sensor to establish communication with the Manager. > [!NOTE] > Note > > The minimum length for shared secret size is 8 characters. The maximum allowed character length is 25 characters. | | **Confirm Shared Key** | Re-enter the shared key for confirmation. | | **Last Updated** | Displays the time and user who last modified the Cluster. The field is blank when you are creating the Cluster for the first time. | | **vIPS Protected Groups** | Displays the list of Protected Groups whose instances are assigned to the Cluster | ![GUID-704F6EA1-6F20-4A23-B7F8-8CD8CDD6BBFA-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-672cd40d-2eb3-25c6-f5a2-2710118d9d00(2).png?sv=2026-02-06&spr=https&st=2026-11-20T15%3A24%3A44Z&se=2026-11-20T16%3A24%3A44Z&sr=c&sp=r&sig=RZ5mMweqdEafjXlNO2uC3X%2FcHit6wulAYmDMV6EC7O8%3D) 6. Click **Save** to save the details to the Manager database. The **Cluster** tab displays the details of the new Cluster. > [!NOTE] > Note > > After you install and start the Sensor instance, the Sensor establishes trust with the Manager. The Manager then adds the Sensor to the relevant cluster. 7. To view the instances being protected by a Cluster, click **View VMs**.