On Jan 18, 2009, at 11:39 AM, Eric Sharakan wrote: > 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
Sigh, looking through the LDom Manager code, I now see that this is actually a bug. In fact, it's one we encountered before, but were never able to reproduce. Now that I know what the issue is, I'm going to re-open the CR. I'm trying to come up with a workaround scenario. Can you try swapping steps 2 & 3 in the list of add-vsw operations above and see whether that works? Unfortunately, even if we come up with a workaround that allows you to initially configure the vswitches the way you want, as soon as the LDom Manager restarts, the bug will get triggered again, and with a more serious consequence: the LDom Manager will detect what it thinks is an impossible config and abort. I see no workaround for that. The CR # for this issue is 6758934. Ram, we need to ask you to go through standard Sun support channels to get this bug escalated, so we can get a patch generated for LDoms 1.1 ASAP. -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 > > _______________________________________________ > ldoms-discuss mailing list > ldoms-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
