Use this information to solve performance problems related
to common agent services (CAS) in the IBM® Flex
System Manager management software.
Table 1. Common Agent problems and corrective actionsProblem description |
Corrective action |
You experience either of the following problems:
|
The reason for the problem might be that the
Domain Name Server (DNS) that is configured to provide hostname resolution
to VIOS is offline. The name resolution order in VIOS is set to bind
the hosts by default, which causes CAS to timeout when trying to resolve
the hostname from DNS before it gets the hostname from the local hosts
file. To change the DNS hostname resolution and fix the problem,
complete the following steps on the managed endpoint that has the
error or poor performance: - If CAS is running, stop CAS. See
the first step in Restarting Common Agent for more information about
how to stop CAS.
- Add the local host to the \etc\hosts directory
on the managed compute node.
- Open the local hosts file on the compute node operating system.
- Add an entry in the hosts file for the local hostname and IP address.
The entry might be similar to the following:
172.16.254.1 localhost
where 172.16.254.1 and localhost are
the IP address and hostname of the local host.
- Save and close the hosts file.
- Change the host order in the /etc/netsvc.conf configuration
file to local,bind:
- Open the /etc/netsvc.conf file on the compute
node operating system.
- Add the following entry:
hosts=local,bind
- Save and close the configuration file.
- Start CAS. See Restarting Common Agent for more information about
starting CAS.
|