VRRP Configuration (Optional)

The Universal Compute Platform relies on Virtual Router Redundancy Protocol (VRRP) to provide IP abstraction to key functionality. if you are using VRRP, the following settings must be defined per intended interface:

Note

VRRP IPs must be within the same segment as configured for the interface.
VRRP IP addresses must not overlap with any other address in use in the segment.

Priority— VRRP uses priority settings as a mechanism to arbitrate mastery of the state of exchanges across members of the cluster.
RouterID — This setting allows segmentation of a routing domain, and it is important to separate from any other VRRP uses on the same network segment. The assigned value is arbitrary, but the value must not overlap when another VRRP usage is visible in the attached network segments.
Note
In a stand-alone configuration, configure priority and router ID with a numeric value. However, in a stand-alone configuration, the specific value is not important. These attribute definitions are important in a multiple-node configuration.

Note
For some applications, access to their management interface, or user interface, is configured as a pass-through Universal Compute Platform data interface by leveraging VRRP to create an alias IP. Make sure that the VRRP IP addresses that you use are not in conflict with any other IP in the segment, including addresses that are assigned by the application.

Services VRRP Configuration

The VRRP configuration relates to the number of services you are exposing. Configure a VRRP IP address (VIP) for each service.

Table 1. Stand-Alone Configuration for Services VRRP Configuration
	Single Node (Port #)
Data Port (optional)	Node Port IP /CIDR
VLAN	VLAN Tagged/Untagged
Port type	Physical
VRRP (required)
VRRP IP address (VIP)	VIP address
Priority	Numeric Value
Router ID	ID (1)