Drew, This seems to be what I'm looking for, but right now I'm just checking email and won't get to testing this for ... maybe tomorrow morning or later tonight.
Thank you, Peter On Feb 12, 2012, at 6:11 AM, Drew Fisher wrote: > Peter, > > The DTD specifies that only one <iscsi> element can exist as a child of the > <disk> element. Your manifest has a <disk> element with an <iscsi> child > which itself has an <iscsi> child. The DTD won't let that happen. What you > have in your manifest has some conflicts, so I need to ask you some questions. > > Are you pulling iSCSI information from the DHCP server? If you are trying to > do that, the existing codebase has a bug in it which will prevent you from > setting the iSCSI parameters correctly. (This is being fixed with > PSARC/2012/023 which is almost ready to go to code review - I'm currently > targeting build 11 or 12 for putback) > > If you're not requesting information from the DHCP server (and you shouldn't > since it won't work ;) ), and you want to specify the iSCSI parameters > manually, you need to have something that looks like this: > > <disk whole_disk="true"> > <iscsi target_name="iqn.2002-03.com.pillardata:axiom.ssn.a002880bjb" > target_lun="0" target_ip="10.129.158.87"/> > </disk> > > This will set up static iSCSI target discovery and map the resulting CTD for > use by the installers. There's no need to specify the <disk_name> element. > > Please let me know if you run into issues. If you DO need to specify DHCP > parameters, let me know and I get you some project bits or an ISO for usage. > > -Drew > > On 2/10/12 3:06 PM, Peter Mccormick wrote: >> >> >> Team, (oh, I'm not on this alias so... include me in your reply) >> >> I am working in System test and running tests for S11u1 latest build. I >> have been trying to create >> a manifest that will allow me to recognize the device during installation, >> no luck. The commented >> items are variations of things I've tried but did not work. >> >> <target> >> <!-- Any disk here will be added to root pool, since no root pool is >> specified --> >> <!-- <disk whole_disk="true"> --> >> <disk> >> <disk_name name="c0t000B080027002880d0" name_type="ctd"/> >> <!-- <disk_name name="/scsi_vhci/ssd@g000b080027002880" >> name_type="devpath"/> --> >> <iscsi source="dhcp"/> >> <iscsi target_name="iqn.2002-03.com.pillardata:axiom.ssn.a002880bjb" >> target_lun="0" target_ip="10.129.158.87"/> >> <!-- dendron internal boot disk --> >> <!-- <disk_name name="/pci@0,600000/pci@0/pci@0/scsi@0/sd@0,0" >> name_type="devpath"/> --> >> <!-- <iscsi name="c0t600A0B80003487FA00009ADF4DAF6F6Ad0s0"> >> <ip>10.129.158.87</ip> --> >> <!-- Adding hook for s11 boot paths --> >> <!-- disk_name name="S11_DPATH" name_type="devpath"/> --> >> </iscsi> >> </disk> >> </target> >> >> When I run against the above I get: (But I'm following the ai_manifest.xml, >> examples, well .. :-\ O:-) ...) >> >> [] (56357)> pfexec installadm add-manifest -n sca05-1010-ai1-s11u1-09-sparc >> -f ssqa.dendron.manifest-s11u1b9.xml -C >> ssqa.dendron.criteria-sun4u-latest.xml >> Error: There was a syntax error parsing the manifest >> ssqa.dendron.manifest-s11u1b9.xml: >> Opening and ending tag mismatch: disk line 8 and iscsi, line 18, column 18 >> >> Does anyone know what's wrong in my manifest, the entire manifest is >> attached. >> >> >> >> _______________________________________________ >> caiman-discuss mailing list >> [email protected] >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
