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.
You can configure a pure IPv4 or an IPv6 network, or a mixed mode network with both IPv4 and IPv6 addresses.
Table:
eth1 | eth2 and eth3 | eth4 and eth5 | Console IP |
|---|---|---|---|
IPv4 | IPv4 | IPv4 | IPv4 |
IPv4 | IPv4 | IPv6 | IPv4 |
IPv6 | IPv4 | IPv6 | IPv6 |
IPv6 | IPv4 | IPv4 | IPv6 |
You need to obtain a range of physical IP addresses, a 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. The range of IP addresses need not be contiguous as long as the IP addresses are in the same data network. 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
Netmask for the data network
Details for the private network, such as starting IP address and the netmask for the private IP address
(Optional) IP address for the Domain Name System (DNS) server
DNS domain name
NTP server
Table: Required IP addresses
Number of IPs | Item |
|---|---|
4 | Physical IP addresses for public network access over eth4 and eth5 |
0 to 8 (Optional) | Virtual IP addresses for public network access over eth4 and eth5 |
1 | IP address for the management console |
Total =5 (excluding virtual IPs) | Note: You need four additional physical IP addresses for appliance management. |
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.
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 public IP addresses for public network access. The IP addresses need not be contiguous.
Reserve a minimum of two virtual IP addresses for public network access. The IP addresses need not be contiguous.
Reserve one virtual IP address for the Remote Management Console.
More Information