Hi, I am trying to figure out what to do next. I am trying to provision to bare metal via SPS OSP plugin via ALOM. I have installed SPS 5.2 MS and SPS 5.2 RA on different physical hosts. I have imported the OSP plug-in. I was able to setup a host record for the RA and prepare the host. Is there documentation on where to go from here?
Pete.
OK, I have found under "Common Tasks / OS Provisioning", I have found a section at the bottom titiled "Initial OSP Plug-in Installation Tasks". I did a pre-flight of a "Create" under "OSP Control Server". The preflight bombed though with the following:
Error verifying native procedure during preflight for the command "/opt/SUNWn1sps/N1_Service_Provisioning_System/agent/data/systemcomps/com.sun.n 1osp/pkgaddutil /opt/SUNWn1sps/N1_Service_Provisioning_System/agent/data/systemcomps/com.sun.n1 osp adminfile SUNWn1ospossvc". (026084)
User "root" does not have execute permissions for command "/opt/SUNWn1sps/N1_Service_Provisioning_System/agent/data/systemcomps/com.sun.n 1osp/pkgaddutil". (026079)
.... and lots more.
I think perhaps I need to set the JVM security properly within the agent.Anyone seen this?
Hmm
please read the docs here first:
http://docs.sun.com/app/docs/doc/819-4458
Setting up OSP in SPS is not a trivial task and lots of knowledge is involved.
It might be easier to use N1SM ( http://www.sun.com/software/products/system_manager/index.xml )for you, depends what your goal is ...
hth
L
Let me first describe some of the details about the OSP. It performs a lot of cr_cli in the background and this is done as root. So if you setup to run cr_cli with SSH then you need to allow to do SSH as the root account to run these commands.
Then the process is quite simple imo:
First if you follow the guide from docs.sun.com then it takes you through all the steps needed to install and configure this.
Using N1SM may be easier in one way but there are some limitations such as only allowing flash archives and not using JET for cusomized installs.
Here is a short recap on all the steps needed:
- Load the plugin
- Prep the hosts
- OSP Control Server
- OSP Subnets
(remeber to select IP network in the same space you intend to provisioning in)
- JET Solaris Image Servers
After this you create the target where you enter how to access the ALOM, LOM, IPMI or whatever console you have, including IP, Login and Password.
Then you create profile and select which JET modules to use, and after that you are all set to go and to click <b>Provision OS</b>
<P>
The docs can be found here:
http://docs.sun.com/app/docs/doc/819-6519
<P>
Rgds,<B>
Peter
Peter,
Thanks very much for the detailed brief overview and the link to the plugin docs that ships with 5.21. I guess I got lost in this paragraph in the n1sps install docs under "Onwnership of applications":
"If you want the Remote Agent to have root privileges on the machine where it is running, then you
must run the installation program as the root user. Even though you may specify a user other than
root to own the Remote Agent, if you want the Remote Agent to have root privileges on the machine
where it is running, start the installation program as the root user."
Also, I believe I failed to setup and test CLI. In anycase, I will do more reading first and revisit the sps install and config.
Pete.
Message was edited by:
peteziu
Message was edited by:
peteziu
I found under runtime issues in the OSP documentation the problem I am seeing, but I am not using 5.9, but 5.10 SPARC:
SPARC: Invalid Errors Displayed During Detailed
Preflight of Solaris OS Provisioning Server Create Plan
(6376733)
Description: If you create an OS Provisioning server on a SPARC based system that is running the
Solaris 9 release, 16 invalid warning messages are displayed if you select the Run Detailed Preflight
option for the plan.
The warning messages use the following format.
Error verifying native procedure during preflight for the command
"/opt/SUNWn1sps_en/N1_Service_Provisioning_System/agent/data/systemcomps/com.su n.n1osp/pkgaddutil
/opt/SUNWn1sps_en/N1_Service_Provisioning_System/agent/data/systemcomps/com.sun .n1osp
adminfile package_name". (026084)
User "root" does not have execute permissions for command
"/opt/SUNWn1sps_en/N1_Service_Provisioning_System/agent/data/systemcomps/com.su n.n1osp/pkgaddutil".
(026079)
In the previous example, package_name refers to a package that the warning indicates cannot be
added to the OS Provisioning server.
Workaround: Ignore the invalid error messages. The packages are added to the OS Provisioning
server, and the server is created successfully.
Pete.
