Client Management Suite

In attempting to update the agents for SLES 10 & 11 64-bit OSes.  The system is reporting that all the 64-bit versions for valid SLES clients are unsupported.   I was lead to believe that the agent install would poll the environment and then install the proper agent is the version of the OS was correct.

Not sure what I may be missing but I am certainly not finding any information in the documentation as to how to resolve this issue.

Thank you for your assistance and make it a great day.

Hi,

How you try to upgrade clients? Using policy based upgrade or push/pull upgrade? Can you post uname -a and /etc/SuSE-release output. If you use push based upgrade can you attach client log(click status report on push install page and press View link for  this client) or if it is policy based upgrade then /opt/altiris/notification/nsagent/aex-nsclt-install.log. Can you also specify product version - is it 7.1 (SP1,SP2)?.

Thanks,

Andrei

I am upgrading the client doing the push method and it is for 7.1 SP1.

The output for uname -a the the SuSE-release -

plmtdb01:/etc # cat SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 1
plmtdb01:/etc # uname -a
Linux plmtdb01 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux
plmtdb01:/etc #

Log for SLES 10 X64 -

Unable to use key file "" (unable to open file)
Using username "root".
Last login: Tue Sep  4 13:33:13 2012 from mcaltcsmtdc02.mclane.mclaneco.com

fp01:~ # stty kill ^U
fp01:~ # stty cols 253
fp01:~ # stty rows 25
fp01:~ # export LC_ALL="C"
fp01:~ # export LANG="C"
fp01:~ # echo ACTIVE SHELL IS $SHELL END
ACTIVE SHELL IS /bin/bash END
fp01:~ # uname -s; echo ERROR=$?
Linux
ERROR=0
fp01:~ #
fp01:~ # uname -s; echo ERROR=$?
Linux
ERROR=0
fp01:~ # cat /etc/redhat-release; echo ERROR=$?
cat: /etc/redhat-release: No such file or directory
ERROR=1
fp01:~ # cat /etc/SuSE-release; echo ERROR=$?
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
ERROR=0
fp01:~ # test -f /usr/bin/vmware && /usr/bin/vmware -v; echo ERROR=$?
ERROR=1
fp01:~ # uname -p; echo ERROR=$?
x86_64
ERROR=0
fp01:~ # ps -ef | grep -v grep | grep aex-bootstrap-linux; echo ERROR=$?
ERROR=1
fp01:~ # ps -ef | grep -v grep | grep AltirisAgentInstaller.bin; echo ERROR=$?
ERROR=1
fp01:~ # rpm -q aex-nsclt; echo ERROR=$?
package aex-nsclt is not installed
ERROR=1
fp01:~ # rpm -qi aex-nsclt; echo ERROR=$?
package aex-nsclt is not installed
ERROR=1
fp01:~ # mkdir -p /opt/altiris/notification/nsagent; echo ERROR=$?
ERROR=0
fp01:~ # cd /opt/altiris/notification/nsagent; echo ERROR=$?
ERROR=0
fp01:/opt/altiris/notification/nsagent # rm -f aex-bootstrap-linux; echo ERROR=$?
ERROR=0
fp01:/opt/altiris/notification/nsagent #
["uploading file using 'scp' source=C:\Program Files\Altiris\Notification Server\NSCap\Bin\Unix\AgentInstall\Linux\x86\aex-bootstrap-linux target=/opt/altiris/notification/nsagent/aex-bootstrap-linux"]
find /opt/altiris/notification/nsagent/ -name aex-bootstrap-linux; echo ERROR=$?
/opt/altiris/notification/nsagent/aex-bootstrap-linux
ERROR=0
fp01:/opt/altiris/notification/nsagent # chmod 755 aex-bootstrap-linux; echo ERROR=$?
ERROR=0
fp01:/opt/altiris/notification/nsagent # ./aex-bootstrap-linux --check; echo ERROR=$?
Verifying archive integrity... MD5 checksums are OK. All good.
ERROR=0
fp01:/opt/altiris/notification/nsagent # rm -f .aex-agent-install-config.xml; echo ERROR=$?
ERROR=0
fp01:/opt/altiris/notification/nsagent # stty -echo; dd bs=1 count=1094 of=/opt/altiris/notification/nsagent/.aex-agent-install-config.xml
1094+0 records in
1094+0 records out
1094 bytes (1.1 kB) copied, 1.39809 seconds, 0.8 kB/s
fp01:/opt/altiris/notification/nsagent # fp01:/opt/altiris/notification/nsagent # Connection terminated because of inactivity for 60 seconds.Command './aex-bootstrap-linux -- -checkpackage' threw an exception Connection terminated because of inactivity for 60 seconds.

Apologies, below is the log related to SLES 11

Unable to use key file "" (unable to open file)
Using username "root".
Last login: Wed Aug 29 13:53:05 2012 from uptime.mclaneco.com

dpsmdb02:~ # stty kill ^U
dpsmdb02:~ # stty cols 253
dpsmdb02:~ # stty rows 25
dpsmdb02:~ # export LC_ALL="C"
dpsmdb02:~ # export LANG="C"
dpsmdb02:~ # echo ACTIVE SHELL IS $SHELL END
ACTIVE SHELL IS /bin/bash END
dpsmdb02:~ # uname -s; echo ERROR=$?
Linux
ERROR=0
dpsmdb02:~ #
dpsmdb02:~ # uname -s; echo ERROR=$?
Linux
ERROR=0
dpsmdb02:~ # cat /etc/redhat-release; echo ERROR=$?
cat: /etc/redhat-release: No such file or directory
ERROR=1
dpsmdb02:~ # cat /etc/SuSE-release; echo ERROR=$?
SUSE Linux Enterprise Server 11 (s390x)
VERSION = 11
PATCHLEVEL = 1
ERROR=0
dpsmdb02:~ # test -f /usr/bin/vmware && /usr/bin/vmware -v; echo ERROR=$?
ERROR=1
dpsmdb02:~ # Unsupported Platform

For SuSe 11 (based on log you provided) these steps should help:

On Push install page select this machine, go to installation settings  and under Platform Detection section choose "manually select OS type" and choose appropriate(SuSe Linux Enterprise Server 11 SP1 x86_64)

This happens because you have probably installed SUSE Linux Enterprise Server 11 Service Pack 1 for IBM® System z, that is not regular SuSe Server x86_64. So this platform cannot be detected automatically. That is why you need to set OS type manually.

For SuSe 10 ( log you provided earlier) : can you run  ./aex-bootstrap-linux -- -checkpackage  manually on client and post here output.(bootstrap should be  there /opt/altiris/notification/nsagent/)

Thanks,

Andrei

Andrei,
 

I could not find ./aex-bootstrap-linux -- -checkpackage to execute the command.  However, I believe I have been able to resolve this by selecting the version 10 OS as I did for 11.

Thank you again for your assistance and make it a great day.

Steven