--- title: "Configuring the cluster virtual IP address using the CLI" slug: "configuring-the-cluster-virtual-ip-address-using-the-cli" tags: ["Central Management System", "Install and Get Started"] updated: 2026-10-01T15:00:45Z published: 2026-10-01T15:00:45Z canonical: "docs.trellix.com/configuring-the-cluster-virtual-ip-address-using-the-cli" --- > ## 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. # Configuring the cluster virtual IP address using the CLI Use the commands in this section to configure a virtual IP (VIP) address that provides access to the Web UI of the primary node. The VIP address must be in the same subnet as the two nodes in the LAN. ### Important You cannot use a VIP address in a WAN deployment. A VIP address is required in a LAN deployment if appliances are added to the primary node using a client-initiated connection. ### Note This is a global configuration. The configuration actions are performed from only one node, but are applied to the cluster. Stop the cluster engine on both nodes: 1. Log in to the secondary node. 2. Enable the CLI configuration mode: ```plaintext node-hostname > enable node-hostname # configure terminal ``` 3. Stop the cluster engine: ```plaintext node-hostname (config) # ha engine stop ``` 4. Repeat these steps on the primary node. Configure the VIP address: 1. Configure the VIP address: ```plaintext node-hostname (config) # ha address vip ``` where` ip address `is the VIP address. ### Important The VIP address must be in the same subnet as the two nodes. 2. (Optional) Enable the resource agent that manages the VIP address: ```plaintext node-hostname (config) # ha resource fe_address enable ``` ### Note The **fe_address** resource agent must be enabled before you can use the VIP address, but it can be enabled later. The VIP address remains in the configuration whether the resource agent is enabled or disabled. 3. Verify your change: ```plaintext node-hostname (config) # show ha configuration ``` 4. Save your changes: ```plaintext node-hostname (config) # write memory ``` Restart the cluster engine on both nodes: 1. Restart the cluster engine on the primary node: ```plaintext node-hostname (config) # ha engine restart ``` 2. Repeat the previous step to restart the cluster engine on the secondary node. ### Example The following example configures a VIP address and enables the resource agent from the primary node. ```plaintext node2 (config) # ha engine stop ``` ```plaintext node1 (config) # ha engine stop node1 (config) # ha address vip 10.11.121.19 node1 (config) # ha resource fe_address enable node1 (config) # show ha configuration CM HA Cluster Settings: ...    Virtual IP address:        10.11.121.19 ... Cluster Resources: ...    fe_address enabled:        yes ... node1 (config) # write memory node1 (config) # ha engine restart ``` ```plaintext node2 (config) # ha engine restart ``` :