On Tue, Nov 13, 2007 at 04:51:49AM -0800, Rainer Montag wrote:
> I'm working with SPARC Enterprise Server M4000 and the SAS HBA
> SG-XPCIE8SAS-E with an attached SAS-JBOD-Unit. After poweron the server, I
> changed within OBP to the HBAs Fcode.
>
> {0} ok show-devs
> ...........
> /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL
> PROTECTED]/LSILogic,[EMAIL PROTECTED]
> ...........
>
> {0} ok select /[EMAIL PROTECTED],600000/[EMAIL PROTECTED]/[EMAIL
> PROTECTED]/LSILogic,[EMAIL PROTECTED]
>
> On the SAS HBA the following command is available to show the
> relation of SAS-Address to Solaris Target Number.
>
> {0} ok show-persistent
> SAS-Address Target-Nr (used by Solaris)
> --------------------------------------------
> Entry 00 PhysId 5000c5000468eca9 Target 0
> Entry 01 PhysId 5000c500049f0a09 Target 1
> Entry 02 PhysId 5000c5000244e38d Target 2
> Entry 03 PhysId 5000c50005f40ff9 Target 3
> Entry 04 PhysId 5000c50005f409c5 Target 4
> Entry 05 PhysId 5000c50004768889 Target 5
> Entry 06 PhysId 5000c500017c8841 Target 6
> Entry 07 PhysId 5000c500017be6ad Target 7
> Entry 08 PhysId 5000c5000468edf9 Target 8
> Entry 09 PhysId 500c0ff00a61013e Target 9
> Entry 0a PhysId 5000c5000244d8f1 Target a
> Entry 0b PhysId 5000c500047651f1 Target b
> Entry 0c PhysId 500c0ff00a60c43e Target c
> {0} ok
>
> The problem is now if I want to change a Disk online, a new Target-ID was
> created because of the different SAS-Addr. from the new disk.
>
> It seems that this behavior is because of a fixed binding mode inside the HBA.
Yes, it's called persistent mapping mode, which associates a SAS
address with a target number and saves this mapping inside the HBA. I
agree with your negative assessment of this "feature".
> Q1: Is it possible to configure another binding, e.g. the PhyNum <-> Solaris
> Target
>
> Q2: Is it possible to configure the binding from Solaris
Not yet, as far as I know. I believe there are plans afoot to make
fixed or slot-based mapping (which is what you want) be the default
for future fresh installs, but I think that work is stalled trying to
figure out the upgrade and OBP issues. I've not heard of any project
to let you change the mapping mode, although it's possible that it
could be implemented as a property in mpt.conf, which you could then
change. It probably would not be documented (or supported), though.
One option you do have, and I REALLY hesitate to point this out
because it is NOT DISTRIBUTED OR SUPPORTED BY SUN and CAN SURELY BREAK
YOUR HARDWARE and can easily RENDER YOUR MACHINE UNBOOTABLE OR WORSE,
is lsituil. This is a program distributed by LSI, available to the
general public. It can be used to disable persistent mapping mode or
clear the mappings so that target numbers can be assigned anew. I
HAVE NEVER USED THIS ON SPARC. I DO NOT KNOW HOW IT INTEROPERATES
WITH OBP. YOU HAVE BEEN WARNED. See
http://www.lsi.com/cm/License.do?url=/support/downloads/hbas/fibre_channel/LsiUtil_10502.zip&prodName=LSI7404XP-LC&subType=Miscellaneous&locale=EN
Because the driver in question is not open source, it would not
surprise me if none of the people responsible for it read this list.
If you want more information, ping me privately and I'll see what I
can find out for you.
> Q3: Is there a description available for the Fcode commands
>
> Q4: What is the procedure to change a SAS-Disk online,
> cfgadm -c unconfigure <AP_ID> or cfgadm -x replace_device <AP_ID>.
> BTW, cfgadm -x replace_device returns
> cfgadm: Hardware-specific Error: Replacement failed: I/O-Error
I definitely don't know the answer to either of these.
--
Keith M Wesolowski "Sir, we're surrounded!"
FishWorks "Excellent; we can attack in any direction!"
_______________________________________________
opensolaris-help mailing list
[email protected]
