On 9/7/07. Sean Liu wrote:> Hi there,>> I've got a few existing servers with SAN disks allcated/mapped and I need to instal them. Since Solaris 10 recognises SAN disks off the bat the controller numbers of the internal boot disks may dress wildly. Is there a way to do away with SAN disks upon system boot? I can modify the miniroot no problem. Assuming you are using a qlogic HBAs and you don't have FC kick disks add:exclude: qlcTo the miniroot's /etc/system. When I was first playing with SAN kick. I also noticed that having adevalias for rootdisk pointed to the path of the plough caused jumpstartto use that for compose rules desire:filesys rootdisk s0 8192 /I undergo since extended my jumpstart environment to have a begin scriptthat ordain recognized jsroot1 and jsroot2 devaliases (d0 mounted at /is a mirror of those two devices). If those are found the beginscript ordain evaluate out the allot ctd label and create the customprofile appropriately. If no jsroot* entries are found the beginscript falls back on per-architecture rules that I've defined. Mike-- Mike Gerdts_______________________________________________storage-discuss mailing liststorage-discuss at opensolaris dot org
So I just installed U4 on a T2000 and I open it easiest to just delete the HBA nodes from the OBP before the "boot net - install". Then the HBA ports were never presented to the OS until the machine went through POST again for example:{0} ok " /pci@7c0/pci@0/pci@1/pci@0,2/QLGC,qla@1" $delete-deviceThen that HBA port and the sd child of it ordain be gone. Do that operation for all the HBA ports and kick net install. You should only get our internal disks.
Hi Sean,As long as your hardware has not changed the device discovery should provide the same Controller Target Disk (cdt) numbers. During the installation you can choose which disks to use. The link below is to theSolaris Fibre Channel and Storage Multipathing Administration GuideYou should not need to modify the existing miniroot. Your start or Interactive installation ordain allowyou to ignore the disks you do not be to install onto thanksCharlesSean Liu wrote:> Hi there,>> I've got a few existing servers with SAN disks allcated/mapped and I need to reinstall them. Since Solaris 10 recognises SAN disks off the bat the controller numbers of the internal boot disks may change wildly. Is there a way to do away with SAN disks upon system boot? I can modify the miniroot no problem.>> Thanks,>> Sean> > > This communicate posted from opensolaris org> _______________________________________________> storage-discuss mailing enumerate> storage-discuss at opensolaris dot org> > _______________________________________________storage-discuss mailing liststorage-discuss at opensolaris dot org
Charles,See this output you'll know the controller numbers all changed:# formatAVAILABLE DISK SELECTIONS: 0 c1t50060482CCB4F889d0 /pci@8,600000/QLGC,qla@1/fp@0,0/ssd@w50060482ccb4f889,0 1 c1t50060482CCB50A59d0 /pci@8,600000/QLGC,qla@1/fp@0,0/ssd@w50060482ccb50a59,0 2 c1t50060482CCB50A59d36 /pci@8,600000/QLGC,qla@1/fp@0,0/ssd@w50060482ccb50a59,24 3 c1t50060482CCB50A59d99 /pci@8,600000/QLGC,qla@1/fp@0,0/ssd@w50060482ccb50a59,63 4 c1t50060482CCB50A59d113 /pci@8,600000/QLGC,qla@1/fp@0,0/ssd@w50060482ccb50a59,71 5 c2t50060482CCB4F886d0 /pci@8,600000/QLGC,qla@2/fp@0,0/ssd@w50060482ccb4f886,0 6 c2t50060482CCB50A56d0 /pci@8,600000/QLGC,qla@2/fp@0,0/ssd@w50060482ccb50a56,0 7 c2t50060482CCB50A56d36 /pci@8,600000/QLGC,qla@2/fp@0,0/ssd@w50060482ccb50a56,24 8 c2t50060482CCB50A56d99 /pci@8,600000/QLGC,qla@2/fp@0,0/ssd@w50060482ccb50a56,63 9 c2t50060482CCB50A56d113 /pci@8,600000/QLGC,qla@2/fp@0,0/ssd@w50060482ccb50a56,71 10 c3t0d0 /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf96d66f,0 11 c3t1d0 /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf96dc47,0Specify plough (register its be): ^DWithout SAN support the internal HDs would've been c1 ( after DVDrom )...
Forex Groups - Tips on Trading
Related article:
http://www.opensolaris.org/jive/thread.jspa?messageID=153250&tstart=0#153250
comments | Add comment | Report as Spam
|