it is interesting, but in ha-ldom, one still be able to access the console from the new control domain on the new phy node?
Sent from my iPad Hung-Sheng Tsao ( LaoTsao) Ph.D On Sep 6, 2011, at 11:16, Liam Merwick <liam.merw...@oracle.com> wrote: > On 04/09/2011 18:09, Ian S. Cottington-Bray wrote: >> I agree that the T-Series is never going to be a high RAS system like the >> M-Series, for that reason it doesn't come at the (high) price of an M-Series. >> >> Clustering means downtime on guest domains - for the guest domain to be >> restarted on the alternate system. T3-1 and T3-2 systems are not capable >> of running independent IO domains (without expensive additional hardware) >> the T3-4 can. The advantage of the second IO domain is that the guest >> continue to run while the control domain is down - and you don't therefore >> need guest downtime. Also you don't have the cost of the clustering >> software or the complexity of maintaining and configuring the cluster. >> >> In any environment running T3's you potentially have more than a dozen guest >> domains - do you really want to co-ordinate downtime across many different >> groups simply to maintain the control domain ? In the real world it >> becomes impossible - thus you try to limit the impact by running a second IO >> domain. As I said previously this is only really practical on the T3-4, >> where due to it's size it becomes even more important (to have a second IO >> domain) because you're running possibly 40 or 50 guest domains. >> >> If they didn't want you to run vntsd on other domains why include it within >> a package which is installed on all domains in a sun4v system ? > > > You can run vntsd on other domains. However the vcc for a guest is decided at > bind time and is not dynamic (e.g. if ldg1 uses primary-vcc0 and primary goes > down you can't switch the guest to access the console from secondary-vcc0 > without unbinding the domain). The output of 'ldm ls -o console' for the > machine would help with any specific questions. > > Regards, > Liam > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss _______________________________________________ ldoms-discuss mailing list ldoms-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
