On Jan 18, 2009, at 5:22 AM, Ram Mohan wrote: > Thank you Dave for pointing out that I had posted wrong error > message. The actual error message I get is > > bash-3.00# ldm add-vsw net-dev=nxge0 primary-vsw0 primary > bash-3.00# ldm add-vsw net-dev=nxge0 secsd-vsw0 secsd > bash-3.00# ldm add-vsw net-dev=nxge3 vid=20,30 primary-vsw3 primary > bash-3.00# ldm add-vsw net-dev=nxge3 vid=20,30 secsd-vsw3 secsd > The device path nxge3 for virtual switchsecsd-vsw3 > is already in use by virtual switch primary-vsw3
This error should only occur when attempting to set the same net-dev path on two vswitch devices in the same domain. Are you certain there isn't somehow a primary-vsw3 defined in the secsd domain? If you are certain, then somehow the LDom Manager is confused into thinking the primary-vsw3 vswitch is associated with secsd. What happens if you remove and then try to redefine primary-vsw3? Also, just as an experiment, what happens if you attempt to create secsd-vsw3 without the vlan IDs? Thanks. -Eric > > I would like to know if I am doing anything wrong???? or the is > thereanything else I should do to make the control domain recognize > same interface names are situated in different service domains. > -- > This message posted from opensolaris.org > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
