For training we provision HW so students can work in a predefined environment and perform their lab exercises. The provisioning happens automatically via expect scripting and jumpstart (for now).
Ever since we have to deal with LDOMS (on a T2000) our scripts break, however. It seems that configuring the system for LDOMS sets certain variables/properties in the OBP and/or the ALOM that change certain behavior of the system. We must know how to best completely reset a T2000 (or any sun4v) system to a defined condition, or even factory defaults, to be able to re-build the environment without manual intervention, blowing away any possible configuration that might have been on the platform. The faster the better. I have posted to this alias before regarding this, specifically the bootmode bootscript ALOM directive being ignored by some of my hosts. I then got the following advice [i]Can you change "reset" to "powercycle"? I think you are hitting a know issue which is documented at, http://docs.sun.com/source/820-3269-10/chapter1.html#i1072165 look for "bootmode" (Bug ID 6585340).[/i] unfortunately powecycle did not work at all, nor did a poweroff/poweron yield the desired result, ie the system would ignore the bootmode and simply boot from disk, even though bootmode was set to bootscript="boot net - install" I am aware that we are doing "things" to these environments they were not necessarily designed for ([very] frequent reseting and rebuilding), but in the name of training that is what we got to do. Any pointers welcome PS: which OBP versions and/or platforms support booting from iSCSI? -- This message was posted from opensolaris.org
