Topic
  • 2 replies
  • Latest Post - ‏2011-12-12T08:28:43Z by xf00657
xf00657
xf00657
25 Posts

Pinned topic RAL installation

‏2011-12-07T09:50:33Z |
Hello,
I want to install the Remote Agentless Adapter on the same nodes where SAAM is installed, too and using the "ANTICOLLOCATED to eezdmn" Relationship to start it on the backup node where eezdmn is not running on. But installation is not allowed on SAAM nodes. What is the reason for this restriction. Now we must look for other Lpars and it is not sure the we found some.
Regards
Ruediger Dahlke
Updated on 2011-12-12T08:28:43Z at 2011-12-12T08:28:43Z by xf00657
  • SystemAdmin
    SystemAdmin
    46 Posts

    Re: RAL installation

    ‏2011-12-09T09:10:12Z  
    Hi Ruediger,

    the remote agentless adapter cannot be installed on any system hosting also the SA Application Manager.
    Sorry to say this. On the other hand it don't see a good reason, why this would be required.

    The Remote Installable Agentless Adapter does provide exactly the same capabilities as the agentless adapter which is anyway already installed on any node, on which the SA Application Manager is already installed. So installing the code twice would not bring any benefit.

    By the way - if you look on the HA policy for the SA Application Manager, which gets created with cfgeezdmn you'll see that it does exactly this what you wanted to try. The (local) agentless adapter which comes installed with the SA AppMan will be started with anti-affinity to the SA AppMan. Only in the case just one node for the SA Application Manager is left over the Agentless Adapter will be started together on the system with the remaining SA Application Manager components.

    Greetings,

    Josi.
  • xf00657
    xf00657
    25 Posts

    Re: RAL installation

    ‏2011-12-12T08:28:43Z  
    Hi Ruediger,

    the remote agentless adapter cannot be installed on any system hosting also the SA Application Manager.
    Sorry to say this. On the other hand it don't see a good reason, why this would be required.

    The Remote Installable Agentless Adapter does provide exactly the same capabilities as the agentless adapter which is anyway already installed on any node, on which the SA Application Manager is already installed. So installing the code twice would not bring any benefit.

    By the way - if you look on the HA policy for the SA Application Manager, which gets created with cfgeezdmn you'll see that it does exactly this what you wanted to try. The (local) agentless adapter which comes installed with the SA AppMan will be started with anti-affinity to the SA AppMan. Only in the case just one node for the SA Application Manager is left over the Agentless Adapter will be started together on the system with the remaining SA Application Manager components.

    Greetings,

    Josi.
    Hi Bernd,

    it was because we were quit sure that AL doesn't work when running on another noder then eezdmn. But now I've tested it again and it does. So you are right and we can forget my question.
    Greeting

    Rüdiger