Search <book_title>...

Veritas Access Appliance Initial Configuration Guide

Last Published: 2020-02-21

Product(s): Appliances (7.4.2)

Platform: Access Appliance OS

About obtaining IP addresses for Veritas Access

The Veritas Access initial configuration process requires that you configure several IP addresses for the two appliance nodes.

Note:

Do not use IP addresses starting with 172.16.X.X either as physical IP addresses or virtual IP addresses since this range of IP addresses are used for the private network.

Note:

It is not supported to configure mixed IPv4/IPv6 addresses to any node within one cluster.

You need to obtain a contiguous range of physical IP addresses, a contiguous range of virtual IP addresses, and a netmask for the chosen public network from the network administrator in charge of the facility where the appliance is located. All IP addresses (both physical and virtual) must be part of the same subnet and use the same netmask as the node's access IP.

By design, the appliance does not support the use of the localhost (127.0.0.1) IP address during configuration.

Note:

Netmask is used for IPv4 addresses. Prefix is used for IPv6 addresses. Accepted ranges for prefixes are 0-128 (integers) for IPv6 addresses.

The information you obtain from the network administrator is used to configure the following:

Physical IP addresses
Virtual IP addresses
Console IP address
IP address for the default gateway
IP address for the Domain Name System (DNS) server
DNS domain name

IP address requirements

Table: Required IP addresses

Number of IPs	Item
4	Physical IP addresses for public network access over eth4 and eth5
4	Virtual IP addresses for public network access over eth4 and eth5
1	IP address for the management console
Total = 9	Note: You need four additional physical IP addresses for appliance management. See Initial configuration requirements.

To request and specify IP addresses

Request the public IP addresses that you need from your Network Administrator.
For example, if the Network Administrator provides you with IP addresses 10.209.105.120 through 10.209.105.123 and 10.209.105.127 through 10.209.105.131, you can allocate the resources in the following manner:
```
Start of Physical IP address: 10.209.105.120
Start of Virtual IP address: 10.209.105.127
Management Console IP:10.209.105.131
```
This entry gives you four physical IP addresses (10.209.105.120 to 10.209.105.123), four virtual IP addresses (10.209.105.127 to 10.209.105.130), and one IP address for the Operations Manager (10.209.105.131).
10.209.105.120 and 10.209.105.121 are assigned to pubeth0 and pubeth1 as physical IP addresses on the first node.
10.209.105.122 and 10.209.105.123 are assigned to pubeth0 and pubeth1 as physical IP addresses on the second node.
10.209.105.127 to 10.209.105.130 are assigned to pubeth0 and pubeth1 as virtual IP addresses on the two nodes.

For more details about Veritas Access network requirements, refer to the Veritas Access Installation Guide.

See Where to find the documentation.

IP address requirements for network bonding

You can configure network bonding to group multiple network interfaces into a single logical interface. The bonded network interface increases data throughput and provides redundancy.

When you configure network bonding for public network access, bond0 is created, which groups eth4 (pubeth0) and eth5 (pubeth1) into a single logical network interface.

Use the following guidelines when you assign an IP address for the bonded network interface:

Allocate either IPV4 public and virtual IP addresses or IPV6 public and virtual IP addresses, but not both.
Reserve a minimum of two continuous public IP addresses for public network access.
Reserve a minimum of two continuous virtual IP addresses for public network access.
Reserve one virtual IP address for the Remote Management Console.

More Information

Network and firewall requirements