That seems unusual, the uname -a version still gives 11.0 does it?.
Do you have the current version of agent 3.2.00, only three days old (dated
Did you use the Distribution server to install there is a known issue that
might affect you, try installing direct.
If all OK I'd log a bug.
thanks for your reply!
>> That seems unusual, the uname -a version still gives 11.0 does it?.
that's not uname output !!
>> Do you have the current version of agent 3.2.00, only three days old (dated
sorry, i do not have it.
>> Did you use the Distribution server to install there is a known issue that
might affect you, try installing direct
Nope. I had direct installation.
From some discussions I have had with BMC I do not believe that SLES 11 SP2 is supported by the Patrol agent at the moment. The kernel has been changed in SP2, which means that a more extensive re-write of Patrol is needed.
A new version of Patrol was released on the 20th April which may contain the necessary support - if not, an RFE will be needed for this to be included.
The new 3.2.00 release notes still state support up to and including SP1, so SP2 is still not officially supported.
See Table 5, page 8 of:
I have the same problem,
This system contains an unsupported operating system by PATROL.
Now the BMC has support to platform SuSE E 11 SP2 - Pag 2
I applied patch 900002.
patrol@linux-sp5l:~/Patrol3-10> uname -a
Linux linux-sp5l 3.0.13-0.27-default #1 SMP Wed Feb 15 13:33:49 UTC 2012 (d73692b) x86_64 x86_64 x86_64 GNU/Linux
patrol@linux-sp5l:~/Patrol3-10> cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 2
You can I help me?
I have been able to install the latest v9.0.00 agent on SLES 11 SP2 without a problem, alongside the v9.0.00.02 patch. DCM does not run (PSL only collection at the moment) but the monitoring does work.
One thing to note is that the 7.5.62 installer does not work correctly with SLES 11 SP2 - you have to download a patch containing new bcf.dat and untested.dat files from the EPD site. It could be that the installer fault is affecting the files laid down for the agent, so it does not recognise the OS it has been applied to.