Preparing agentless managed systems

Prepare the agentless managed systems in your environment before you discover or manage them with IBM® Flex System Manager.

About this task

Note: A managed system might have more than one IP address (for example, when the system contains more than one network interface card). When a managed resource has multiple IP addresses, specify which IP address Flex System Manager uses to manage the resource. To specify the IP address to use, you specify that the management server ignore (or exclude) the other IP addresses associated with the resource. For more information, see "Excluding IP addresses."

Note: You must enable secure copy protocol (SCP) when you set up a Linux resource for agentless or Platform Agent managed systems.

Complete the following steps on each system to be managed.

Procedure

On all managed systems that use the ssh protocol to communicate with IBM Flex System Manager, ensure that the PasswordAuthentication value in /etc/ssh/sshd_config is set to yes. So, the corresponding line in the sshd_config file will appear as follows:
```
PasswordAuthentication yes
```
On all agentless managed systems that use the root user for request access for the ssh protocol, ensure that the PermitRootLogin value in /etc/ssh/sshd_config is set to yes.

What to do next

Notes:

You must restart the ssh server for any changes made to sshd_config to take effect.
IBM Flex System Manager does not support the ssh protocol on VMware ESXi hosts. If ssh is discovered on a VMware ESXi managed system, it might cause problems when attempting to collect inventory.