On 10/18/09 10:52, Lars Tunkrans wrote: > I am going to build a couple of T5240's with LDOM 1.2 s/w in an as > redundant config as possible. > > I Have two Emulex LP11000s cards with Sun Microcode and an > additional QuadGIG eth card in the systems. > > I have Split the PCI bus and created the secondary I/O domain. > I have given the Scondary I/O domain a SAN card and the additional quad > gig card. > I have connected both FC cards to the SAN and both set of quad Gig cards > to the Cisco backbone. > I have tried booting the secondary I/O Domain directly from the SAN > using its local FC card. > THis doesnt work and I belive the Documentation also says that its not > supported.
This does work, and this is supported. Just ensure that you have an FC card from which you can boot; check the documentation of your FC card that it does support booting Solaris on Sparc. > I Can boot the secondary I/O domain off the primary domains FC card > via its VDS switch of course. > I plan to set up Virtual disk Multipathing using the mpgroup feature of > the VDS. > > Now to the question: > > IF I boot the Secondary I/O domain of the Control domains FC-Card and > at some later > point in time the Control domains SAN connection fails ! > > Will that crash the secondary domain as its boot disk will disappear > ? An I/O error will probably be reported up to the filesystem of the virtual disk on the secondary disk. A filesystem error on the boot disk is usually fatal, the system might panic or be partially hang because it is unable to access critical filesystems. > WIll this as an additional effect break the secondary I/O domains VDS > to the Guest > domains , so that the guest domains will loose both the disk paths > configured > in the vds mpgroup ? In this situation, any virtual disk exported from vds from the secondary domain might have problems because the system running the secondary domain will be unstable (or down). > Would it be a better solution to boot the secondary I/O domain from the > same > T5240 Local SAS disks as the the primary domain uses ? You would have the same problem if there's any error with the SAS disk. The only viable solution is to directly boot the secondary domain from SAN. alex.
