Use this window to add, change, or resume VM managers by
specifying or changing connection parameters.
Tip: The time it takes for the server to connect to
a VM manager depends on the settings of the vmManagerPollingInterval parameter
of the setserverconf command. The default is 30 minutes.
Use the
Test Connection button to test the
connection with the VM manager in order to verify that you have specified
the correct Web address and credentials.
- Host name, IP address, or full Web address
- You can specify either the full URL, or only the host name or
IP address. In the second case, the full VM manager address will be
built on the server side basing on the selected type of the VM manager.
Each VM manager in the table must have different Web address, that
is, only one entry is allowed for a given URL.
Important: When
providing the full Web address, you have to specify the protocol,
for example https://virtualcenter/sdk. Refer to the VM manager
documentation in case of any problems.
- Type
- WebSphere CloudBurst
- Microsoft Hyper-V (With Microsoft Hyper-V, you can select the
check box below the Select Type list to use
the same credentials with other hosts in the same cluster.)
- VMware ESX, ESXi, or vCenter
- KVM - RHEV-M
- Communication interface
- When you specify the VM manager type as Microsoft Hyper-V, you
can specify the communication interface.
- PowerShell is a framework for managing the automation and configuration
of tasks and can use the RPC protocol. In order to use PowerShell
for retrieving the information from VM managers, the server or the
VM manager data collector must be installed on a Windows computer. The computer must also
meet the following requirements:
- Microsoft RPC communication
with Microsoft Hyper-V
cannot be blocked by a firewall
- Microsoft PowerShell
2.0 or higher must be installed
- Microsoft.NET Framework
3.5 or higher must be installed
- NTLM is a suite of protocols that are used for user authentication,
integrity, and confidentiality, and uses the WS-MAN protocol. It is
a legacy method that is planned to be withdrawn. In order to use NTLM
for retrieving the information from VM managers:
- NTLM must be in version 1 or 2
- You must configure Windows Remote
Management Service (WinRM) for all members of the Microsoft Hyper-V cluster.
- The default URL that is to be used is https://<HYPER-V_IP_address>:<port>/wsman,
where <port> is the port of
the listener that was created for the WinRM service. The default value
for the HTTP listeners is 80 and for HTTPS listeners is 443. The default
URL might vary in your environment if the administrator of the Microsoft Hyper-V hypervisor
changed the configuration of the API, for example, if the HTTP protocol
is used instead of the HTTPS protocol.
- User name
- User login specified for a given VM manager.
Note: Different
definitions of users are used for Microsoft Hyper-V
and VMware:
- For Microsoft Hyper-V,
the user name must contain the domain name and be defined as domain\username or username@domain.
For example: cluster.com\test or test@cluster.com.
If the target server is not in a domain, specify its host name as
the domain. For example: hostname\test or test@hostname.
- For VMware, the user is defined as domain\username.
For example: cluster.com\test.
- Password
- Password specified for a given VM manager.
Note: For
the server to see the agent hierarchy on virtual machines managed
by a given VM manager, the user has to have sufficient authority to
see those virtual machines.
After adding a new VM manger, you should check the number of servers
that is displayed in the Partition Assignment History window
for the chosen agent because after adding a VM manger, both the agent
and the VM manager collect information about your infrastructure on
a given day.