Veritas NetBackup™ Flex Scale Administrator's Guide
- Product overview
- Viewing information about the NetBackup Flex Scale cluster environment
- NetBackup Flex Scale infrastructure management
- User management
- About Universal Shares
- Node and disk management
- Adding a node to the cluster using the NetBackup Flex Scale web interface
- License management
- Managing the Fibre Channel ports
- Requirements
- Managing hardware vendor packages
- User management
- NetBackup Flex Scale network management
- Bonding operations
- Data network configurations
- Network configuration on plain device (eth5)
- Network configuration on bonded interfaces (bond0 on eth5 and eth7)
- NetBackup Flex Scale infrastructure monitoring
- Resiliency in NetBackup Flex Scale
- EMS server configuration
- Site-based disaster recovery in NetBackup Flex Scale
- Performing disaster recovery using RESTful APIs
- NetBackup Flex Scale security
- STIG overview for NetBackup Flex Scale
- FIPS overview for NetBackup Flex Scale
- Support for immutability in NetBackup Flex Scale
- Deploying external certificates on NetBackup Flex Scale
- Configuring multifactor authentication
- Single Sign-On (SSO)
- Appendix A. Maintenance procedures for HPE servers
- Appendix B. Configuring NetBackup optimized duplication
- Appendix C. Disaster recovery terminologies
- Appendix D. Configuring Auto Image Replication
Choosing the correct input method for data network configuration
You can provide inputs for IP/FQDN either using the Automatic tab or Custom tab from the GUI for operations such as initial configuration, add data network and add node.
Automatic tab:
The Automatic tab accepts only IP address. You can specify a single IP range, multiple IP ranges separated by a comma, comma-separated individual IP addresses, a combination of individual IP addresses and IP ranges separated by a comma, or IP addresses in CIDR format. The FQDN is retrieved using nslookup depending on the DNS server and search domain entry provided for that network. For nslookup to work correctly, the DNS server provided should be valid. In case only the short host name is specified as the FQDN, the correct search domain strings should be specified for nslookup to work correctly. The IP/FQDN validation check fails in case there is no information about the IP address in the DNS server provided.
Custom tab:
The Custom tab accepts both IP address and FQDN and does validation using forward and reverse lookup of the IP address. When Custom tab is used for providing input, the IP/FQDN validation check only fails when there is a conflict between the IP address and FQDN. There can be a conflict:
If the forward lookup of an FQDN returns an IP address which is different than the input IP provided.
If the reverse lookup of an IP address returns an FQDN which is different than the input FQDN provided.
In a non-DNS environment, if the Custom tab is used, the IP/FQDN validation check is skipped.
Consideration while choosing Automatic or Custom tab for providing input for IP/FQDN.
During initial configuration, if the IP/FQDN entries exist in the DNS, use the Automatic tab for providing input IP.
During initial configuration, if the DNS server is not specified or if the IP/FQDN entries do not exist in the DNS, then Custom tab should be used to provide the inputs for both IP address and FQDN.
During data network addition, if DNS server in configured for that network, then Automatic tab is enabled by default. Automatic tab can be used if the IP/FQDN entries are already added in DNS.
During data network addition, if DNS server is not configured or if the IP/FQDN entries do not exist in the DNS server, then the Custom tab should be used for providing input for both IP/FQDN.
During node addition operation, if DNS is configured for the data network, the Automatic tab should be used for providing input for data network IPs.
During node addition operation, if DNS is not configured or if the IP/FQDN entries do not exist in the DNS server then the Custom tab should be used for providing input for both IP/FQDN.
During node addition operation, when a secondary data network exists on the management interface (eth1 or eth1.<VLANID>), the Custom tab should be used for providing input for both IP/FQDN for the secondary data network IPs.