Aliases provide user-friendly management for backends and networking IP addresses in order to improve usability and easier operation. By creating aliases, it creates an abstraction layer for IP addresses of backends and network interfaces, so devops and developers don’t need to understand IP addresses or the network architecture in order to configure virtual services.
In this section, you will see two tables, one for the backend aliases and another one for the network interface aliases.
The Actions menu permits to perform aliases management.
ADD IP ALIAS. Open a form to create a new alias pair.
UNSET. Destroy one or more selected alias configuration.
This section permits the management of the backend aliases, by assigning just the IP address to the corresponding alias which could be used later in farms backends.
IP Address. Backend IP address (could be either IPv4 or IPv6).
Alias. Name or alias to identify the backend IP address.
This section permits the management of network interfaces by aliases.
Interface. Interface name as stored in the system.
Alias. Name or alias to identify the interface.
The column actions are the same for both, backend aliases and network interface aliases:
Actions. The allowed actions are:
For an already created alias:
- Edit. Open again the configuration form for the alias.
- Unset. This action destroys the alias information.