IEM 9.1 - AIX client computer is not appearing in windows IEM 9.1 Console

Usage and Config Platform
1

I have successfully installed both client and server, IEM 9.1 on Windows Server 2012. I am also able to run the fixlet.

I installed the aix client and then it’s not appearing in IEM Console.

I have verified that IEM Machine is accesible over the port.
IEM client on Aix is running.

Can you please guide me further.

AIX Client Logs:

-----------------------------------------------------------------------------+
Pre-installation Verification…
±----------------------------------------------------------------------------+
Verifying selections…done
Verifying requisites…done
Results…

SUCCESSES

Filesets listed in this section passed pre-installation verification
and will be installed.

Selected Filesets

BESClient 9.1.1275.0 # IBM Endpoint Manager Agent

<< End of Success Section >>

±----------------------------------------------------------------------------+
BUILDDATE Verification …
±----------------------------------------------------------------------------+
Verifying build dates…done
FILESET STATISTICS

1  Selected to be installed, of which:
    1  Passed pre-installation verification

1  Total to be installed

±----------------------------------------------------------------------------+
Installing Software…
±----------------------------------------------------------------------------+

installp: APPLYING software for:
BESClient 9.1.1275.0

. . . . . << Copyright notice for BESClient >> . . . . . . .
Licensed Materials - Property of IBM Corp.

© Copyright IBM Corp. 2001-2016.

All rights reserved.
. . . . . << End of copyright notice for BESClient >>. . . .

Finished processing all filesets. (Total time: 2 secs).

±----------------------------------------------------------------------------+
Summaries:
±----------------------------------------------------------------------------+

Installation Summary

Name Level Part Event Result

BESClient 9.1.1275.0 USR APPLY SUCCESS
BESClient 9.1.1275.0 ROOT APPLY SUCCESS
dst36lp96:/home/waqas/IEM# ls
BESAgent-9.1.1275.0.ppc64_aix61.pkg*
LicenseAuthorization.BESLicenseAuthorization*
masthead.afxm*
dst36lp96:/home/waqas/IEM# /BESClient/actionsite.afxm <
dst36lp96:/home/waqas/IEM# /etc/rc.d/rc2.d/SBESClient start
ksh: /etc/rc.d/rc2.d/SBESClient: not found
dst36lp96:/home/waqas/IEM# /etc/rc.d/rc2.d/SBESClientd start
Starting IBM Endpoint Manager: BESClient
dst36lp96:/home/waqas/IEM# uname -u
IBM,021035EFP
dst36lp96:/home/waqas/IEM# ps -efa | grep BESClient
root 15007926 1 0 06:41:13 - 0:00 /opt/BESClient/bin/BESClien t
dst36lp96:/home/waqas/IEM# ps -efa | grep BESClient
root 15007926 1 0 06:41:13 - 0:00 /opt/BESClient/bin/BESClient

dst36lp96:/home/waqas/IEM# ps -efa | grep BESClient
root 15007926 1 0 06:41:13 - 0:00 /opt/BESClient/bin/BESClien t
dst36lp96:/home/waqas/IEM# /etc/rc.d/rc2.d/SBESClientd start
Starting IBM Endpoint Manager: BESClient
dst36lp96:/home/waqas/IEM# ps -efa | grep BESClient
root 15007926 1 0 06:41:13 - 0:00 /opt/BESClient/bin/BESClien

Looking forward to hear from you soon.

2

Have you reviewed the AIX Client installation steps described in the documentation?

http://www.ibm.com/support/knowledgecenter/SS63NW_9.1.0/com.ibm.tivoli.tem.doc_9.1/Platform/Adm/c_aix_installation_instructions.html

More specifically, have you ensured that the appropriate masthead exists in /etc/opt/BESClient/actionsite.afxm?

The Client’s log would be useful for subsequent troubleshooting (located in /var/opt/BESClient/__BESData/__Global/Logs). For reference to various file locations across platforms, please see:

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/Common%20File%20Locations

1 Like
3

Thank you, your guide helped me to identify the issue.

Yes, I have followed those instructions and it’s running on the AIX machine.

I looked into logs and found out that, my aix client is trying to connect to hostname of windows machine IEM, it’s not connecting to IP/name of the windows machine IEM Manager.

So I saw two files where hostname may be needed to be updated.

  1. actionsite.afxm

X-Fixlet-Site-Gather-URL: http://HOSTNAME:52311/cgi-bin/bfgather.exe/actionsite
X-Fixlet-Site-Report-URL: http://HOSTNAME:52311/cgi-bin/bfenterprise/PostResults.exe
X-Fixlet-Site-Registration-URL: http://HOSTNAME:52311/cgi-bin/bfenterprise/clientregister.exe
X-BES-Mirror-Gather-URL: http://HOSTNAME:52311/cgi-bin/bfenterprise/besgathermirror.exe
X-BES-Mirror-Download-URL: http://HOSTNAME:52311/bfmirror/downloads/

  1. /var/opt/besclient.config
    following values:

[Software\BigFix\EnterpriseClient\Settings\Client__Relay_Control_RootServer]
value = http://HOSTNAME:52311/cgi-bin/bfgather.exe/actionsite

  1. Should I do it manually, or there is a better way to do this thing.?
  2. What should I do so, that I avoid this on Linux installations?
4

You cannot edit the masthead directly, it must be generated by BESAdmin as it is a signed document. The other setting if its wrong will end up at the right thing over time but if the masthead points to the wrong server that is definitely the core of the problem

1 Like
5

During IEM Server Installation, It didn’t ask me about the IP Address or any thing like that, How can i make sure, that masterhead is pointing to that IP and not the hostname. Do you guide me on this point, so that all client installations directly point to the IP address rather then hostname.

I have checked above url, by giving IP, they are accessible and working.

6

During installation of the Root Server (and when the masthead is generated) rather than leveraging hostnames or IPs, we’d recommend DNS aliases which can be properly resolved by the various endpoints. Given that you cannot edit the gather URL in the masthead, I’d suggest there are a number of options (in no particular order):

  1. Generate a new masthead (requires essentially a new BigFix instance, and possibly migrating existing users/content/clients to the new instance)

  2. Have the Client point to a specific Relay or the Root Server at installation time (by name, IP, FQDN, alias, etc…) via the process outlined here: http://www-01.ibm.com/support/docview.wss?uid=swg21505838#unix

  3. Modify the endpoint’s HOSTS file (or leverage other similar approaches) to ensure that the hostname specified in the existing masthead is properly resolved for the given endpoint

7

thank you, it’s working now.