Hi Dan, Unfortunately, there are limitations with all products, especially when they are new. In the case of vsw's, you do have to go back into the "factory-default" mode for certain operations. Hopefully, this will be corrected in the future where it can be dynamic. Also, you can't do vlan tagging or link aggregation with LDom's at this point. N1 System Manager is a front-end to JET (Jumpstart Enterprise ToolKit), so you could do the make_template/make_client on your server and start the jumpstart process. N1 System Manager also has issues with automating the "boot net - install" on non ALOM/LOM servers (I'm sure everyone still has older servers), which is something that needs to be fixed. Hopefully, it'll support LDoms at some point. *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* Octave J. Orgeron Solaris Systems Engineer http://www.opensolaris.org/os/community/sysadmin/ http://unixconsole.blogspot.com unixconsole at yahoo.com *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
----- Original Message ---- From: Dan Gubber <[email protected]> To: ldoms-discuss at opensolaris.org Sent: Monday, October 29, 2007 11:05:10 AM Subject: [ldoms-discuss] LDOM Configurations I've recently been exploring the different configuration possibilities of SUN's newest virutalization layer, ie, LDOM's and seem to be encountering a number of contraints. Either that or the configuration capabilities are just not documented sufficiently. Here's some of the list. 1. It appears that the only way to reconfigure the control domain is to reboot back to the factory-default config, remove the "initial" configuration, then recreate it. Example is if you have a vswitch entry defined, you can not modify the entry, remove and re-add it, etc, from the control domain. 2. The only way you can install the OS on a guest domain, providing you get that far, is via a jumpstart server ! AND!! if you have the N1 System Manager Server software functional in your environment, you will not be able to use it's functionality to "provision" the OS to a guest domain as it requires the ability to discovery the ALOM of the physical server. 2. The use of "virtual NIC's" for a vswitch definition is not supported, ie ( again ) if you create an aggregate device or have a net port connection setup for tagging, you cannot define a vswitch as follows: ldm add-vswitch net-dev=e1000g10002 primary-vsw0 primary 4. There seems to be indication that tagged NIC's can be used as follows: ldm add-vswitch net-dev=e1000g2 primary-vsw0 primary ( where e1000g2 is connected to a tagged port ) Then on the guest domain ( of course providing you can get an install to occurr ) use vsw10000 for the NIC device. Those are a start - I'll reply to this and add more as I find them Regards, Dan -- This message was posted from opensolaris.org _______________________________________________ ldoms-discuss mailing list ldoms-discuss at opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
