# VIPs (virtual IPs) A Region (Cluster) Network VIP (or Virtual IP) is an IP address servicing inbound traffic of a specific network application or function. It is virtual because it can reside on any physical node that also functions as a Control Node. In Region Networking, VIPs have a dedicated page at **Region Networking > VIPs**. This page gives MSP admins a focused view of VIP objects. It helps admins find service-facing IP entries without opening the full Networking Applications page. ## VIPs management ### Viewing VIPs To view VIPs: 1. Go to **Region Networking**. 2. Select **VIPs**. The VIPs list shows these columns: * **Name** The VIP object’s descriptive name. * **Switch Domain** The switch domain that contains the VIP context. * **Cluster Network** The cluster network linked to the VIP. * **Service** The service value shown for the VIP. * **Direction** The traffic direction shown for the VIP. * **Shared** The shared state shown for the VIP. #### Viewing a VIP’s details To view a VIP’s details: 1. Open **Region Networking > VIPs**. 2. Select the VIP name. The VIP details screen opens. The details page shows the selected VIP’s configuration, with the following sections: * **Info** section: Displays basic configuration properties for the application: * **Enabled/Disabled** status, indicating the VIP’s availability. * **ID** The unique identifier assigned to the VIP. This value is generated by the system when the application is created. Administrators typically use this identifier when referencing the application in system operations or when reviewing configuration data. * **Name** The descriptive name of the VIP. The name identifies the function associated with the VIP. * **Type** The type is `virtual_ip`, that indicates the role that a VIP performs within the cluster networking model. * **Cluster Network ID** The identifier of the cluster network associated with the VIP. * **Enabled** Indicates whether the VIP is currently enabled. An enabled VIP allows network behavior and firewall rules associated with the VIP to be applied. * **Direction** Indicates the traffic direction associated with the VIP. The direction defines whether the VIP accepts traffic from external systems or handles internal traffic within the cluster network. This property helps determine how the VIP participates in the networking flow and which services or clients are expected to connect to it. * **Service** Identifies the service associated with the VIP. The service value represents the networking function or platform service that is exposed through the VIP. Clients use the VIP address to reach the service instead of connecting directly to individual nodes. Associating a service with a VIP provides a stable endpoint that remains consistent even if the underlying service location changes. * **Shared** Indicates whether the VIP address can be shared by multiple services or applications. When enabled, the same VIP can be used by more than one service. This allows the platform to expose multiple services through a single logical address when required by the network design. When **Shared** is disabled, the VIP is dedicated to a single service. * **IP Address** Displays the VIP address assigned to the application. This address represents the network endpoint used by clients to access the associated service. The VIP remains stable even if the service moves between nodes or instances within the cluster. Administrators use this address when configuring clients, external systems, or network integrations that must reach the service. * **Firewall Rules** section: Lists the network protocols and ports allowed for the VIP. Firewall rules control which types of traffic can access services that use the VIP. Each rule defines the protocol and port used for communication. Displayed fields: * **Protocol** The network protocol allowed by the firewall rule. Examples: * **tcp** * **icmp** * **Port** The network port allowed for the protocol. These ports represent services that are reachable through the VIP. Example interpretation: * **22 (TCP)** commonly represents SSH access. * **80 (TCP)** commonly represents HTTP traffic. * **443 (TCP)** commonly represents HTTPS traffic. Firewall rules allow administrators to restrict network access so that only required protocols and ports are permitted. Use the details page to confirm the current state and network settings of the VIP. ### Modifying a VIP 1. Open **Region Networking > VIPs**. 2. Select the VIP name. The VIP details screen opens. 3. On the top toolbar, select **Modify**. 4. Review the fields in the **Modify VIP** dialog. The **Modify VIP** dialog opens. Update the required values: * **Name** The VIP name shown in the dialog. * **Cluster Network** The related cluster network. * **IP Address** The IP address value for the VIP. * **Enable** The enable/disable control toggle for the VIP enabled state. * **Direction** The direction value: * **Inbound** * **Outbound** * **Service** Identifies the service associated with the VIP. The service value represents the networking function or platform service that is exposed through the VIP. Clients use the VIP address to reach the service instead of connecting directly to individual nodes. * **Shared** The shared state control toggle indicating that the VIP address can be shared by multiple services or applications. 5. To save the changes, select **Finish**. ## Recommended best practices For any desired change, consult first with Zadara support. These VIPs are predefined, and tightly-coupled with specific functionality.