CVIPInfo

Description

CVIPInfo is a diagnostic tool for getting information about the IP configuration of a machine. It is typically used to verify the configuration of multiple network cards to be used with SnapProtect.

Usage

When CVIPInfo is run without arguments, it lists all the addresses that are bound to the local machine. It then takes each address and attempts to do a reverse lookup to find the name for that address. This list of names is the list of interfaces displayed as possible selections for pipeline pairs. CVIPInfo will then try to find the primary address for each interface name. This address should match the address that was resolved back to the interface name; if so CVIPInfo displays a plus (+) after the interface name. If the address does not match, CVIPinfo displays a minus (-) after the interface name and prints the address that was returned. If an interface name is used that did not resolve back to the correct address, then the second address listed is used. Only addresses that display a plus (+) are used.

When CVIPInfo has checked all the addresses, it will print a warning report about any problems it encountered. This will include any address that did not have a name entry, names that didn't have address entries, and names that had mismatched addresses.

CVIPInfo can also look up remote names. This is done by specifying the name to look up as the first parameter on the command line. This can be useful to ensure that two machines know a name as the same address.

Configuring Multiple Network Interfaces

In order to utilize secondary network interfaces, the secondary interfaces must be configured correctly. Each interface must be given a unique name. This name must be the primary name for that address. If using host files, this would be the first name after the IP address; if using DNS it would be the Fully Qualified Domain Name (FQDN) that causes the DNS server to reply. It is possible to allow one IP address to resolve directly to the machine name; however, this address must be bound first so that it is the primary address for the machine.

Once the machine's network cards and name/address resolution are correctly configured, SnapProtect must be instructed to use the secondary interfaces. This is done by setting pipeline pairs. A pipeline pair is configured at the subclient level; it is an advanced property on the Storage Device Pane. When adding a pipeline pair it is important to make sure that the interfaces are capable of communicating with each other. Although Pipeline pairs are configured at the subclient level, they affect all backups and restores that are done between that Client and the MediaAgent. Configuration of one pipeline pair will automatically update all other subclients on that Client that point to the same MediaAgent (not just the storage policy). If multiple pipeline pairs are configured for a Client/MediaAgent, then SnapProtect will alternate between them.

Sample Output

Sample 1: Looking up Local Host info for mystery

In this sample both addresses are correctly configured and SnapProtect will not have any problems using either address.

Host Name: mystery.commvault.com
Address Type: 2
Address Length: 4
Aliases:
Addresses:
172.19.60.203 mystery.commvault.com +
172.19.177.12 mystery.henry.commvault.com +

Sample 2: Looking up Local Host info for GLADIATOR

In this sample none of the secondary addresses are registered in DNS, or the host file SnapProtect will list GLADIATOR.commvault.com four times and they will all use 172.19.63.139 to communicate.

Host Name: GLADIATOR.commvault.com
Address Type: 2
Address Length: 4
Aliases:
Addresses:
172.19.63.139 GLADIATOR.commvault.com +
192.168.0.1 GLADIATOR.commvault.com - 172.19.63.139
192.168.0.11 GLADIATOR.commvault.com - 172.19.63.139
192.168.0.111 GLADIATOR.commvault.com - 172.19.63.139
WARNING: 3 Interface Names did not resolve back to the correct address

Sample 3: Looking up Local Host info for mystery

In this sample, the second address, which has the name of the primary address, points back to the primary address. This is due to an incorrect binding order. The address that has the machine name as its own name should be bound before secondary cards.

Host Name: mystery.commvault.com
Address Type: 2
Address Length: 4
Aliases:
Addresses:
172.19.177.12 mystery.henry.commvault.com +
172.19.60.203 mystery.commvault.com - 172.19.177.12
WARNING: 1 Interface Names did not resolve back to the correct address