Could not power off target host...

Does anyone know what the below error might be? Is this because the ALOM password is incorrect, or configuration of the IP for the service processor network? I am using a different networks for provisioning and service processor.

pz

[{INFO} Tue Jan 02 14:39:26 GMT+05:00 2007]:Powering Off target host with new IP : 10.0.2.52

[{SEVERE} Tue Jan 02 14:39:26 GMT+05:00 2007]:Power Off failed for target host [ 10.0.2.52] with exception :Cannot instantiate service [com.sun.n1.isp.hal.PowerS ervice] without at least an ip or terminal server connection

[{SEVERE} Tue Jan 02 14:39:26 GMT+05:00 2007]:Jumpstart failed : Could not power off the target host

com.sun.n1.isp.osservice.provision.PowerOffFailedException: Power Off failed for target host [10.0.2.52] with exception :Cannot instantiate service [com.sun.n1. isp.hal.PowerService] without at least an ip or terminal server connection

[952 byte] By [peteziua] at [2007-11-26 13:56:39]
# 1
oops. wrong IP, sorry. Pete.
peteziua at 2007-7-8 1:36:15 > top of Java-index,Administration Tools,N1 Service Provisioning System...
# 2

Hmm. Now I am getting output from as though not all the params are there. I deleted my ALOM target and re-created it with the correct ALOM ip and now there are missing parameters?....

this is what ran last:

opt/SUNWn1sps/N1_Service_Provisioning_System/agent/data/systemcomps/com.sun .n1osp/n1osp_util/n1osp_deploy_sps_wrapper.sh

/opt/SUNWn1osp/sbin/n1osp_deploy /opt/SUNWn1osp/hosts/<hostname>-portal

/opt/SUNWn1osp/profiles/Solaris10_606_sparc.standard/osprovisioner-jet.< hostname>-portal

/opt/SUNWn1osp/subnets /var/run/n1osp log/<hostname>-portal-provision.log

console/<hostname>-portal-provision.console pid/<hostname>-portal-provision.pid

false

Making copies of files in /var/run/n1osp/13657

Clearing stale log and console files (if any)

Executing command in background /opt/SUNWn1osp/sbin/n1osp_deploy -f

/var/run/n1osp/13657 < /dev/null >

/var/run/n1osp/log/<hostname>-portal-provision.log 2>&1 &

bash-3.00# cat /var/run/n1osp/<hostname>-portal-provision.log

-

Usage: n1osp_deploy -h <hostfile1:hostfile2:...> -o <osprofilefile> -s <subnetdir> [-v]

orn1osp_deploy -f <provisioning files> [-v]

orn1osp_deploy -H

-h {h}ost description in xml

-o {o}s profile description in xml

-s directory containing {s}ubnet description(s) in xml

-f provisioning {f}iles (directory path)

-v {v}erbose console output

-H {H}elp and displays usage

At least last time I was getting an attempt to connect.

Pete.

peteziua at 2007-7-8 1:36:15 > top of Java-index,Administration Tools,N1 Service Provisioning System...
# 3
I can't seem to trap any more output other than the above. I verified that the tmp dir existed and had content, but beyond that, I am unsure where to go from here. Any suggestions are welcome.pz
peteziua at 2007-7-8 1:36:15 > top of Java-index,Administration Tools,N1 Service Provisioning System...
# 4

Hmm. Everything seems to work, but the host does not reboot. There are some exceptions logged by some GridOS classes (com.sun.n1.isp.core.sys.GridOS) within /var/adm/n1osp.debug. Also, I don't see any attempt to reboot in the logs. Do I need to do anything else other than run the provision-start plan? Are there any defaults that prevent the attempt of the booting of the box?

peteziua at 2007-7-8 1:36:15 > top of Java-index,Administration Tools,N1 Service Provisioning System...