Iniciar sesión
 
InicioBibliotecaAprendizajeDescargaSoporteComunidadForos
Recursos para Profesionales de TI >
> 
> 
SCOM 2007 R2 CU3 AIX 6.1 Cross Platform Agent installation error

Answered SCOM 2007 R2 CU3 AIX 6.1 Cross Platform Agent installation error

  • miércoles, 12 de enero de 2011 20:47
     
     
    Inicie sesión para votar
    0

    I am attempting to install the Cross Platform agent on an AIX 6.1 server, the agent install file is scx-1.0.4-265.aix.6.ppc.lpp.gz, I have applied SCOM 2007 R2 Cummulative Update 3 (KB2222955).  When I attempt to discover and install the agent it fails.  According to the log file the prerequisites (scx.rte 1.0.4.265) is looking for xlC.aix50.rte 9.0.0.2.  I am running AIX 6 with xlC.aix61.rte 10.1.0.0 and xlC.aix50.rte 8.0.0.4 installed.

    I am wondering if it is possible to install the agent without upgrading the xlC.aix50.rte to version 9.0.0.2?

    • Cambiado Robert_Hearn martes, 19 de julio de 2011 23:06 moving forum (From:Cross Platform Solutions for System Center)
    •  
     

Todas las respuestas

  • jueves, 13 de enero de 2011 2:26
    Moderador
     
     Respuesta propuesta Tiene código
    Inicie sesión para votar
    0

    Hmm.  In looking at our dependencies:

      specfile.write('*prereq openssl.base 0.9.8.4\n')
  specfile.write('*prereq xlC.rte 9.0.0.2\n')
  specfile.write('*prereq xlC.aix50.rte 9.0.0.2\n')
  specfile.write('*prereq bos.rte.libc 5.3.0.65\n')
  specfile.write('%\n')

    These are the relevant lines we write to the LPP file when generating the package.

    For AIX 6.1, I'm not sure it makes sense to be checking for an AIX 5.3 (or 5.0) package.  We did this to be certain that the appropriate files were actually updated, but on AIX 6.1, this probably doesn't make sense.

    I've entered a new bug in our database, bug 30581 in the DEV database (not support database).  I'm not sure when the bug will be scheduled to be fixed; you should probably go through technical support if you need to persue this and get a fix.  Otherwise, see if you can actually update the package to allow installation.

    Another option might be to try and install the package manually, but specify installp qualifiers to force the installation even failing the prereq check.  -Q *might* fit the bill - not certain (the online help isn't terribly descriptive - it may just quiet the error, not quiet the test for the prereq).

    Hope this helps.

     
  • viernes, 14 de enero de 2011 14:26
     
     
    Inicie sesión para votar
    0

    Jeff,

    Thank you for the response, we attempted to manually install the agent, but we are still not able to get passed the prerequisite check.  I've got my AIX administrator checking into any switches that might help us get passed this.

    Does anyone know what installp switch, if any, will allow us to install the package even if the prerequisite check fails?

     
  • viernes, 14 de enero de 2011 17:03
     
     
    Inicie sesión para votar
    0

    I should add that we attempted to use the -Q and -F switches and neither of these worked, we looked through the installp documentation and didn't see another option.

     
  • viernes, 14 de enero de 2011 17:07
    Moderador
     
     
    Inicie sesión para votar
    0

    I don't believe there is another option.  If -Q didn't cut it and -F didn't cut it, then I don't see any qualifiers or options to ignore the prereq in the installp documentation.

    Any possibility that you can actually update the requested package?  If not, then I think you'll need to follow up with technical support to persue further.  Sorry.

    /Jeff

     
  • viernes, 14 de enero de 2011 20:50
     
     
    Inicie sesión para votar
    0
    Hi, I am having the same issue.  Were you able to get any help with this?  I am just before calling techical support to resolve, just checking to see if you have done this.  Thanks for any help..
     
  • martes, 18 de enero de 2011 14:42
     
     
    Inicie sesión para votar
    0
    I have opened an incident with Microsoft Support and they are looking to see if there is any kind of workaround for the issue.  I will post back when I know more informaton.
     
  • miércoles, 26 de enero de 2011 1:02
    Moderador
     
     
    Inicie sesión para votar
    0

    Hi folks,

    Gark15141: You contacted support. Thanks for that! We may need to get back to you with regards to resolving this issue.

    Candicesking: You said you have the same problem. Can you contact support as well please?

    Basically, I want support to have a list of people affected by this so that, if needed, we can get back to you.

    Finally, for both of you: For testing purposes (to make sure my fix actually resolves the problem), I need to be able to get an AIX 6.1 machine in this state. We've never seen this before. I recognize the problem, but for testing purposes, I need to be able to get a machine in this state so I can verify the fix.

    Can you please clearly describe your installation process? What specific version of AIX 6.1 did you install? Any relevant patches?  What TL (Technology Level) have you upgraded to? Essentially, if I can get a list of what to do to get a machine in a failing state (either from a fresh install perspective, or from a modification perspective), that would be wonderful. If I had a fixed kit (that worked on this test system) where the existing kit failed, that would allow us to validate our fix.

    Thanks so much for your help!

    /Jeff

     
  • miércoles, 26 de enero de 2011 15:38
     
     
    Inicie sesión para votar
    0

    Jeff,

    I spoke with our AIX Administrator and he stated that we had been running AIX 5.3 with xlC.aix50.rte version 8 and we performed an in place upgrade of our AIX base OS to AIX 6.1 and at that point xlC.aix61.rte vesion 10 was installed.

    Unfortunately, the details are a little vague because we had a vendor come in and perform the upgrade, if you need more detail than that please let me know, and I will try to contact the vendor to see if they can provide more detail.

    Greg

     
  • miércoles, 26 de enero de 2011 21:19
     
     
    Inicie sesión para votar
    0

    Jeff,

    One more thing - our AIX admin noticed that our production AIX server does not have the xlC.aix50.rte library installed, so we removed it from our test server and still the installation failed, below is some additional information from my AIX admin:

    No good news.

     

    MISSING REQUISITES:  The following filesets are required by one or more

      of the selected filesets listed above.  They are not currently installed

      and could not be found on the installation media.

     

        xlC.aix50.rte 9.0.0.2                     # Fileset Update

     

    Currently Installed libraries:

     

    si005:root:/space/aix_media/scom>lslpp -l | grep -i xlc

      xlC.aix61.rte             10.1.0.0  COMMITTED  XL C/C++ Runtime for AIX 6.1

      xlC.cpp                    9.0.0.0  COMMITTED  C for AIX Preprocessor

      xlC.msg.en_US.cpp          9.0.0.0  COMMITTED  C for AIX Preprocessor

      xlC.msg.en_US.rte         10.1.0.0  COMMITTED  XL C/C++ Runtime

      xlC.rte                   10.1.0.0  COMMITTED  XL C/C++ Runtime

     

    Apparantly it REALLY wants this library.

    Greg 

     
  • jueves, 27 de enero de 2011 0:31
    Moderador
     
     Respuesta propuesta
    Inicie sesión para votar
    0

    Hi Greg,

    Yeah, xlC.aix50.rte 9.0.0.2 or later a hard requirement. The fix in our source code is super simple, but I need a way to test to be 100% certain that the fix is "good". Your prior message was pretty dang good, I think: I've given those instructions to our Infra team to ask them to set up a system for us using your instructions.

    The fundamental problem: At the point that you had 5.3 installed, our agent wouldn't have installed because you had an old version of xlC.rte. Had you fixed that prior to upgrade, then after upgrading to AIX 6.1, the agent would have worked. But, unfortunately, that wasn't the sequence of steps you followed. Also, if you installed AIX 6.1 "fresh", you wouldn't have experienced the problem either. It was the particular sequence of steps you followed prior to installing our agent.

    But none the less, it is a problem in our installer: We list xlC.aix50.rte as a hard requirement, and it's not.

    As soon as our Infrastructure team can set up a test system to replicate this, I should be able to check a fix in. That's step one for getting the fix into customer hands.

    Thanks for your help and assistance in helping us track this down,

    /Jeff

     
  • martes, 01 de febrero de 2011 19:26
     
     
    Inicie sesión para votar
    0
    Would you still like for me to call this error into support?  I too am getting the same error.  I was trying to do a manual install of the SCOM agent .265 on an AIX 6.1.03.01.0921 server.  This is a new install of SCOM agent on this server.
     
  • jueves, 03 de febrero de 2011 17:10
    Moderador
     
     
    Inicie sesión para votar
    0

    Hi candicesking,

    Did you get your system into this state in much the same way as Gark15141?  That is, did you have a 5.3 install (with no agent), and then did you do a 6.1 in-place upgrade on your 5.3 system?

    If so, you probably don't need to call support.  But if the history of the system was different in some material way, I'd like to know that history, and I may have you call support.  So please let me know - thanks!

    /Jeff

     
  • viernes, 04 de febrero de 2011 17:24
    Moderador
     
      Tiene código
    Inicie sesión para votar
    0

    Hi Greg (gark15141),

    Our Infrastructure Team has been diligently trying to replicate your issue. Our steps so far:

    Install AIX 5.3 on a system.  Do NOT upgrade xlC.  At this point, we had an old version of xlC (that came with the system):

    root@scxaix4-1.scx.com # lslpp -l | grep -i xlc
 xlC.aix50.rte       6.0.0.13 COMMITTED C Set ++ Runtime for AIX 5.0 
 xlC.cpp          6.0.0.0 COMMITTED C for AIX Preprocessor
 xlC.msg.en_US.cpp     6.0.0.0 COMMITTED C for AIX Preprocessor
 xlC.msg.en_US.rte     6.0.0.0 COMMITTED C Set ++ Runtime
 xlC.rte          6.0.0.0 COMMITTED C Set ++ Runtime

     

    si005:root:/space/aix_media/scom>lslpp -l | grep -i xlc

      xlC.aix61.rte             10.1.0.0  COMMITTED  XL C/C++ Runtime for AIX 6.1

      xlC.cpp                    9.0.0.0  COMMITTED  C for AIX Preprocessor

      xlC.msg.en_US.cpp          9.0.0.0  COMMITTED  C for AIX Preprocessor

      xlC.msg.en_US.rte         10.1.0.0  COMMITTED  XL C/C++ Runtime

      xlC.rte                   10.1.0.0  COMMITTED  XL C/C++ Runtime

    Can you verify that this is the case, please?

    My system is still at the AIX 5.3 level - I'll have Infra upgrade it to 6.1 with no other changes and then see where we stand.  Thanks for your help.

    /Jeff

    I noted, that under AIX 6.1, you didn't have xlC.aix50.rte at all.  Is that correct?  Somehow, my recollection is that this package wasn't removed when you upgraded.  You said you had:
     
  • viernes, 04 de febrero de 2011 19:04
     
     
    Inicie sesión para votar
    0

    Hi Jeff,

    You are correct, the snippit you have above is after we attempted to remove the xlC.aix50.rte from our test server, we had noticed that one of our production servers did not have the library installed.  So in an attempt to fix our issue we removed the xlC.aix50.rte and attempted the manual install again, however the installer still recognized some form of the old library and failed. 

    Here is a screen shot of our original configuration when I opened the ticket.

    si005:root:/space/aix_media/scom>lslpp -l | grep -i xlc

      xlC.aix50.rte              8.0.0.4  COMMITTED  C Set ++ Runtime for AIX 5.0

      xlC.aix61.rte             10.1.0.0  COMMITTED  XL C/C++ Runtime for AIX 6.1

      xlC.cpp                    9.0.0.0  COMMITTED  C for AIX Preprocessor

      xlC.msg.en_US.cpp          9.0.0.0  COMMITTED  C for AIX Preprocessor

      xlC.msg.en_US.rte         10.1.0.0  COMMITTED  XL C/C++ Runtime

      xlC.rte                   10.1.0.0  COMMITTED  XL C/C++ Runtime

    Greg

     
  • martes, 08 de febrero de 2011 18:07
    Moderador
     
      Tiene código
    Inicie sesión para votar
    0

    Hi Greg,

    I heard back from our Infrastructure team.  They're having a boatload of grief trying to replicate your problem.  They installed AIX 5.3 with no other changes, and got something that should have caused problems:

    root@scxaix4-1.scx.com # lslpp -l | grep -i xlc
 xlC.aix50.rte       6.0.0.13 COMMITTED C Set ++ Runtime for AIX 5.0 
 xlC.cpp          6.0.0.0 COMMITTED C for AIX Preprocessor
 xlC.msg.en_US.cpp     6.0.0.0 COMMITTED C for AIX Preprocessor
 xlC.msg.en_US.rte     6.0.0.0 COMMITTED C Set ++ Runtime
 xlC.rte          6.0.0.0 COMMITTED C Set ++ Runtime
 
root@scxaix4-1.scx.com # uname -a
AIX scxaix4-1 3 5 000374EAD300

     

     

    That's all good.  Then I had them update the system, in place, to AIX 6.1 with no other changes at all.  Results now:

     

     root@scxaix4-1.scx.com # lslpp -l | grep -i xlc
 xlC.aix61.rte       9.0.0.5 COMMITTED XL C/C++ Runtime for AIX 6.1 
 xlC.cpp          9.0.0.0 COMMITTED C for AIX Preprocessor
 xlC.msg.en_US.cpp     9.0.0.0 COMMITTED C for AIX Preprocessor
 xlC.msg.en_US.rte     6.0.0.0 COMMITTED C Set ++ Runtime
 xlC.rte          9.0.0.5 COMMITTED XL C/C++ Runtime 
 xlC.sup.aix50.rte     9.0.0.1 COMMITTED XL C/C++ Runtime for AIX 5.2
 /
 root@scxaix4-1.scx.com # uname -a
AIX scxaix4-1 1 6 000374EAD300

    So just doing the update alone, at least in our environment, got us to a state where our agent would likely install, at least as far as this requirement.

    Can you please contact your vendor?  I need very explicit instructions, if possible, on how to replicate your state so that I can resolve the issue at hand.  It appears to be something more than a vanilla "in-place upgrade", since we did that but have different results than you.

    Thanks so much,

    /Jeff

     
  • miércoles, 16 de febrero de 2011 14:43
     
     
    Inicie sesión para votar
    0

    Hi Jeff,

    Sorry for delay in getting back to you, we have been working with IBM on the issue and have successfully been able to install the package.

    The IBM technician basically 'reverse engineered' the fileset and tried to fix it so there is NO reference to the xlC at all.  According to the IBM Tech -

    'I don't think it's an OS problem. The .toc file is built from a file within the builld of a fileset called the "lpp_name" file. The lpp_name file basically looks like the .toc file inutoc creates. I unpacked the fileset, edited the lpp_name file, then simply repackaged the fileset.   I made no changes to your ODM or anything from your mksysb other than repackaging the fileset.'

    This allowed us to manually install the agent and perform the discovery successfully.  I don't think this answers the original question - the install doesn't work with the presence of xlC.aix50.rte ver 8, but by removing the prereq check we were able to install agent without issue.

    Greg

     
  • miércoles, 23 de marzo de 2011 19:50
     
     
    Inicie sesión para votar
    0

    I am experiencing this issue in a slightly different way. I have AIX 5.3 ML8 systems that we cannot upgrade at this time. When I try to install the agent either manually or through SCOM, it errors out because of xlC file pre-req. If this is not a hard pre-req, then I would really like to get my hands on the manual install files to get around this. Or if there is something I can install on the SCOM server to have it ignore the version conflict. We have xlC installed under 5.3 ML8, it is just a slightly older version. If none of that is available, can I get a step by step on how you modified the inutoc/lpp_name file and maybe I can tweak it myself?

     

    Thanks,

    Kelly

     
  • jueves, 24 de marzo de 2011 16:02
    Moderador
     
     
    Inicie sesión para votar
    0

    Hi Kelly,

    In the case of AIX 5.3, our xlC requirement is quite real.  If you try to jury-rig things to bypass our xlC requirement, I can guarantee that you'll have problems.  We hit problems in testing that was fixed in xlC 9.0.0.2.

    You don't need to upgrade from ML8 to upgrade xlC.  Upgrading xlC is orthogonal to your AIX technology level.

    The reason this came up is because we have an error - we test for a requirement on AIX 5.3 and we (in error) test for the same requirement on AIX 6.1.  The problem is that it's tricky to have an AIX 5.3 package installed on an AIX 6.1 system (thus the problem).

    Your situation is quite different, and we really do need a newer version of xlC to run properly.  Our code is correct, but the runtime does the wrong thing and makes our code misbehave.  That's why we require a newer xlC version.

    /Jeff

     
  • lunes, 28 de marzo de 2011 19:01
     
     
    Inicie sesión para votar
    0

    Ahh OK. That would also be why I could not find any other references to this work around on 5.3. :)

    Thanks. I will try to get my hands on the xlc update then.

    I am guessing it is just for these two as they are the only alerts SCOM gives me during package install.

    xlC.aix50.rte 9.0.0.2                     # Fileset Update
    xlC.rte 9.0.0.2                           # Fileset Update

     
  • lunes, 04 de abril de 2011 17:34
     
     
    Inicie sesión para votar
    0

    Is there any update on this issue?  Re: installing scx-1.0.4-265.aix.6.ppc.lpp on an AIX 6.1 system and it requires xlC.aix50.rte 9.0.0.2 (although 6.1 now has xlC.aix61.rte...etc. 

    Candice S King
     
  • lunes, 11 de abril de 2011 17:44
    Moderador
     
     
    Inicie sesión para votar
    0

    There's no real update on this issue (sorry).

    Assuming things go well, we'll add support for AIX 7.1 in CU6 (which is after CU5 - it's a ways out).  This issue will likely be fixed there as well, since we'll be dealing with AIX installation dependencies at that time.  I'm still not sure how this will be tested since, to date, I've been unable to replicate the situation on my test systems.  I still don't fully understand how the systems got into that state to begin with.  In our testing, when AIX 6.1 is installed, xlC is upgraded as well.

    In any case, that's the hope.  Of course, I can't make a promise that things will go as anticipated.  If, for example, AIX 7.1 gets pushed out, then this fix may be be pushed out too.

    If you need something sooner than that, then the best approach to follow is to open a service request with our technical support folks.  If appropriate, they can request a hot fix, which has the potential of speeding up the timetable.

    /Jeff

     
  • lunes, 16 de mayo de 2011 13:19
     
     
    Inicie sesión para votar
    0
    I have reported this as an issue with Microsoft support.  I still have not heard anything from them.  Just curious if anyone else has had any luck with resolving this issue.
    Candice S King
     
  • martes, 24 de mayo de 2011 16:15
    Moderador
     
     
    Inicie sesión para votar
    0

    I believe that our support organization will have more information very shortly (if they don't already).  They determined how to break apart our kit, change the dependency, and create a kit again.  This will work until we release a new version of the agent (through engineering) that fixes this issue.

    That will likely happen in CU6.

    /Jeff

     
  • viernes, 24 de junio de 2011 16:44
     
     
    Inicie sesión para votar
    0

    My organisation is about to deploy SCOM to manage a host of Windows servers and AIX and Linux as well.

    My speciality is AIX so I've been keen to understand the installation process for the SCOM agents so I've got hold of the agaents (1.0.4-258) to examine the prerequisites (the documentation is confusing as is references openssl.base and xlC.rte only but the example check is also listing levels of bos.rte.security and libxml2).

    I was horrified to see the pre-req for xlC.aix50.rte in the agent package for AIX 6.  This fileset will only be installed if the server to be monitored has been migrated from AIX5 to AIX6, it will never be installed on a clean AIX6 install - there's your method to verify your changes to the packing.  xlC.aix61.rte will never satisfy the requirement for a version of xlC.aix50.rte as they are different packages completely.  If the AIX version specific code needs to be at a specific level for AIX6 then that will need a pre-req definition in the packaging for the xlC.aix61.rte fileset.

    If there is no patch out for this I'll have to modify the packaged agent for AIX6, as we'll be installing the agent manually it's under my (AIX Admin) control rather than the SCOM admin.

    If a server is upgraded from AIX5 to AIX6 (or AIX6 to AIX7) will the agents cease to function correctly?

    For anyone wanting to repackage the fileset themselves to get around the problem the following steps should be followed (Note that I haven't installed this yet as our SCOM server isn't built yet):

    create a new directory to hold the contents of the package:

    $ mkdir /var/tmp/scxnew

    Unpack the current package into directory:

    $ cd /var/tmp/scxnew

    $ restore -xvqf <scx package file>

    Edit the lpp_name file and change the pre-req list to match the published pre-reqs:

    *prereq openssl.base 0.9.8.4

    *prereq xlC.rte 9.0.0.5

    *prereq xlC.aix61.rte 9.0.0.5

    Remove the *prereq line for bos.rte.libc as that references TL6 for AIX 5.3 and any level of AIX 6 is supported

    Repackage the file:

    $ find . | backup -iqvf <new package filename outside current directory>

    The package can now be installed from the new package file.

    ...Mark Rowlinson

     
  • lunes, 11 de julio de 2011 20:43
    Moderador
     
     Respondida
    Inicie sesión para votar
    0

    In the past, the Infrastructure team (who sets up the system) has provided systems to us (development) to use.  Since then, we've changed our processes so that the development team is involved much more closely with this process, so the likelihood of this sort of problem coming up again is considerably reduced.

    This was a bug.  The engineer who added this requirement at the time didn't fully understand the ramifications of this requirement, and it wasn't caught by test since our Infrastructure team upgraded older (5.3) systems to AIX 6.1.

    This problem has already been fixed in source code, and will be released as part of CU6.  The problem is also fixed in the next major release of Operations Manager.

    Additionally, our support organization, upon request, will provide the exact sequence of steps to fix a kit to not require this 5.3 xlC package.

    /Jeff

     

     
  • jueves, 26 de abril de 2012 9:31
     
     
    Inicie sesión para votar
    0

    Hey Jeff!

    Is there any timeline for CU6? Last CU was in august last year...

    Would need the Update for monitoring AIX 7.1...

    Best regards,
    Peter

     
  • jueves, 26 de abril de 2012 14:42
    Moderador
     
     
    Inicie sesión para votar
    0

    Peter,

    CU6 just finished up testing and should be out within the next month but I don't have an exact date. Look for it soon.

    Regards,

    -Steve

     
  • lunes, 30 de abril de 2012 11:32
     
     
    Inicie sesión para votar
    0

    Hey Steve!

    Thanxs for your fast answer!

    Best Regards,
    Peter