Specifications

Chapter 2: Installing SolarWinds Virtualization Manager
7. Enter the host name or IP address of the existing virtual appliance that you
are migrating from in the text field of Step 2.
8. Click Perform Migration. The migration tool moves your information to the
new virtual appliance.
Installing, updating and uninstalling a federated
collector
By using a federated collector, you can split the data collection tasks of
SolarWinds Virtualization Manager between one or more remote servers. The
federated collector has no database of its own. Its function is to serve as a proxy,
collecting configuration and performance data and relaying the collection back to
SolarWinds Virtualization Manager. To monitor 10,000 VMs or more, it is strongly
recommended that you use a federated collector.
Reasons for deploying a federated collector include scalability and geography. A
single SolarWinds Virtualization Manager data collector might not have sufficient
computing resources by itself to collect data from very large virtual environments
with thousands of VMs. If you experience slow performance due to collection,
consider deploying a federated collector.
Additionally, it is more efficient to collect data from distant vCenters by deploying
a federated collector in that distant location and having the collector periodically
phone home with a dense stream of data. If your organization uses WANs,
consider deploying a federated collector.
To use federated collectors, TCP port 61616 must be open on SolarWinds
Virtualization Manager. For more information, see Port requirements.
Note: Upgrading to the latest version of Virtualization Manager upgrades the
Virtualization Manager software on both the master virtual appliance and on
federated collectors. However, while the upgrade to Virtualization Manager also
raises the CentOS version on the master appliance, you must manually upgrade
CentOS on federated collectors using the .ISO file.
60