On 09/08/2010 05:03, Ken Woolard wrote:
Thanks for that Terence - I now have a better understanding and also a better
idea on what I want to do with regards to splitting the buses on my T5240.
However I'm not sure if it would benefit me to do this. Let me explain and let
me know what you think, your feedback what be most appreciated:-
In a previous LDOM config on a T5240 there was only a primary (control) domain
doing all the IO , servicing etc. points to note:-
--> T5240 installed via jumpstart onto local disks.
--> Primary domain set up with one virtual switch and 2 virtual disk services.
One disk service for the LUN's allocated for the Guest domains OS
One disk service for the LUN's for Guest domains application data
The PCI express HBA cards were put in PCI slots 4 and 5 ( p...@500) so that
they were not on the same bus as the internal disks ( p...@400). However the
internal quad network card is on p...@500
--> Guest domains were all jumpstarted onto the LUN's from vds 1 and then
application data LUN's allocated via vds 2.
Now I now have another T5240 that I have just installed the OS on and have been
exploring the possibility of creating a seperate IO domain hence all the
questions I have been asking
The way I see it on a T5240 is that the internal disks and the network devices
are on seperate buses. Ideally I would like them on the same bus freeing up the
other bus for an IO domain connected to the SAN storage.
The only way I see this happening is to get an PCI express 1GB NIC and install
it in slot 2 for example so that network and internal disks are on the same bus.
However the company does not want to spend money so I was thinking about still
splitting the buses having the internal disk on one bus and the network and SAN
storage on another bus ( IO domain ). To the IO domain I can add a virtual
switch for the guest domains to connect to.
I'm still not sure exactly what I'm trying to do here and maybe my prose is a
bit confusing but I would appreciate any feedback you may have to offer.
Ken
I am not sure you are going to gain anything from doing the above (
apart from making your configuration more complex).
Ususally the scond I/O domain would be used to make the configuration
more resilient, but this is not what you are proposing. As I already
said you will be using the primary domain to supply the boot device for
the second I/O domain, so if that fails then the second I/O domain will
hang as well. Thus gaining you nothing.
Are you worried about performance or resilience or are you just
experimenting?
T
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
