Scope
|
||||||||||
|
||||||||||
Release
|
||||||||||
|
·
8.0.0 |
||||||||||
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 Galaxy. |
||||||||||
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 that Galaxy will display 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 + after the interface name. If the address does not match, CVIPinfo displays a - 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 Galaxy will use the second address listed. Galaxy will only
correctly use addresses that displayed a +. 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 Galaxy
for Multiple Network Interfaces In order for Galaxy to
utilize secondary network interfaces, the secondary interfaces must be
configured correctly. Galaxy requires that each interface be given a unique
name. This name will need to 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. (See the NOTE regarding Windows 2000.) 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, Galaxy
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 Galaxy will alternate between them. NOTE ·
Windows
2000 has introduced some problems in resolving addresses back to names. In
Windows 2000 and Windows 2000 SP1 addresses, lookups would skip the Host file
and DNS and simply return the local node name. This causes all pipeline pair
entries to return the machine name. This issue was fixed with hot fix Q265017.
Windows 2000 SP2 has re-introduced part of this problem, in that DNS is
ignored when resolving addresses — requiring all interface names to be
registered in the local hosts file. Sample Output Sample 1: Looking up
Local Host info for mystery Host Name: mystery.commvault.com In this
sample both addresses are correctly configured and Galaxy will not have any
problems using either address. Sample 2: Looking up
Local Host info for GLADIATOR Host Name:
GLADIATOR.commvault.com WARNING: 3
Interface Names did not resolve back to the correct address In this sample none of
the secondary addresses are registered in DNS, or the host file Galaxy will
list GLADIATOR.commvault.com four times and they will all use
172.19.63.139 to communicate. Sample 3: Looking up
Local Host info for mystery Host Name:
mystery.commvault.com 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. |
||||||||||
History
|
||||||||||
|
||||||||||
Disclaimer of
Warranties
|
||||||||||
|
CommVault provides software tools and
utilities on an "as is" basis, as a courtesy and convenience to its
users, and they may be changed from time to time without notice. These tools
and utilities are provided without express, implied, or statutory warranties
of any kind. You assume full risk and responsibility for the selection,
possession, performance and proper installation and use of the software tools
and utilities, and for verifying the results obtained there from. Your use of
CommVault software tools and utilities indicates
your unconditional acceptance of the above disclaimer. |
||||||||||