Failed to install agent on AIX 5.3

Usage and Config Platform
1

(imported topic written by SystemAdmin)

Hi All,

Has anyone encountered problem in installation agent on AIX 5.3?

Can not Install: For AIX we require at least Technology level 8

instal: Failed while executing the BESClient.pre_i script

0503-464 installp: The installation has failed for the “usr” part

of the following fileset

BESClient8.2.1310.0

Thanks,

Braian

2

(imported comment written by SystemAdmin)

So what oslevel do you have?

oslevel -r

We require Technology Level 8 at minimum (ie: 5300-08) to install the agent.

3

(imported comment written by SystemAdmin)

Hi AlanM,

os level 5300-07, any solution to remediate it? during POC installation is successful but we did not use the latest version release.

Thanks,

Brai

4

(imported comment written by SystemAdmin)

You would have to use an 8.1 released AIX agent on this unsupported in 8.2 platform

The agent could then help bring the AIX machine up to the right technology level and then you can upgrade.

5

(imported comment written by SystemAdmin)

Thanks Alan,

I will just need the masthead for the installation of lower version right?

6

(imported comment written by dmccalla)

If you need to download a TEM client package that is older than the current release you can access them here:

http://support.bigfix.com/bes/install/besnonwindowsarchive.html

So for 8.1 versions you can start here:

http://support.bigfix.com/bes/install/besnonwindowsarchive.html#8.1.617.0

7

(imported comment written by SystemAdmin)

Hi AlanM,

Ive tried installing version 8.1.617.0 and encountered the ff. error:

November 8, 2012

At 10:50:59 +0800 -

Starting client version 8.1.617.0

Unhandled error: NotASignedMessage

Client shutdown (Unexpected error)

At 11:11:32 +0800 -

Starting client version 8.1.617.0

Unhandled error: NotASignedMessage

Client shutdown (Unexpected error)

Thanks in advance,

Braian

8

(imported comment written by SystemAdmin)

Did you get your masthead into /etc/opt/BESClient ? It must also be named actionsite.afxm

And if you are transferring it there, make sure its in binary, it can’t be altered as its signed.

9

(imported comment written by SystemAdmin)

Thanks AlanM, I copied the wrong one, it already works when i copied actionsite from server.