Paul Eggleton wrote: > Hi, Hi Paul,
> After a succesful pilot with Logical Domains using 1.0.3 and Solaris 10 update 5 (127127-11) our company have moved to launch a new project based on this technology. All has been going well, apart from what appears to be a rather concerning issue. After a reboot of the control domain by our tools team, I have noticed the following, which I'm sure is "a bad thing"(tm). > > Please can anyone shed light on why I might have the same LDC for 2 separate logical domains? I have had a search through the release notes and bug list, but with no luck so far. > > Here is the output of "ldm list-bindings -e | grep vdisk | grep primary" > > ldom-01 ldom01-vol at primary-vds0 disk at 0 primary 4 > ldom-02 ldom02-vol at primary-vds0 disk at 0 primary 24 > ldom-03 ldom03-vol at primary-vds0 disk at 0 primary 12 > ldom-04 ldom04-vol at primary-vds0 disk at 0 primary 16 > ldom-05 ldom05-vol at primary-vds0 disk at 0 primary 20 > ldom-06 ldom06-vol at primary-vds0 disk at 0 primary 24 It looks like you are looking at the wrong part of the output. Those lines are from the section of the output for each client domain where each line shows which domain is acting as the vdisk server and what the LDC ID number is for the local endpoint--the endpoint on the client domain and not on the service domain. Take a look at the output of "ldm list-bindings -e primary" to confirm that each vdisk is getting a unique LDC ID number on the primary domain. If that doesn't look right, could you attach the full "ldm list-bindings -e" output? Oh and it looks like there's a copy-and-paste mistake in the email because the output shown wouldn't be generated by the above grep command because "vdisk" isn't anywhere in there. > Notice the LDC numbers on the right hand side. Surely 24 should not > be reused for 2 different LDOMs? As I understand it, the LDC > channels should be uniquely allocated, point-to-point connections. Yes, the same channel should not be used for more than one vdisk. At present, each channel may or may not be accessed via the same channel ID number at each endpoint. A channel connecting two domains will likely not have the same ID number at each endpoint. You could say the scope of a channel ID is a single domain only. As an example, in your configuration, it would not be a bug for say ldom-01 and ldom-02 to both locally refer to their boot vdisk channel by the same ID number because that does not imply they are referring to the same channel. Haik
