3510 FC array - disk target IDs keep changing during rebuild

3510 FC array - disk target IDs keep changing during rebuild

Post by andrew » Thu, 17 Nov 2005 01:52:46



Hi

Hopefully this is a faq, but if it is I can't faq'ing find it :PP
Google, you've let me down.

I have a 3510 array on a V440 (Solaris 9 9/05, current Recommended
patch level) and have been setting 7 machines up with Jumpstart. I've
noticed that the disk ID targets appear to be climbing each time I've
jumpstarted the system. Well, perhaps not every time, but I can't work
out why it has some times and not others.

Currently, these are the first disks in my system:

       4. c3t48d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

       5. c3t49d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

Starting at target 48 !

Anything I can do to bring these back to a more sensible number - and
preferably stop them wandering at all ? I don't want to obsess over it,
but I'm writing some system configuration scripts (and associated
documentation) and I'd rather not gamble that things will change should
someone have to do a rebuild in my absence.

Thanks in advance

Andrew

 
 
 

3510 FC array - disk target IDs keep changing during rebuild

Post by andrew » Thu, 17 Nov 2005 02:20:14



> Hi

> Hopefully this is a faq, but if it is I can't faq'ing find it :PP
> Google, you've let me down.

> I have a 3510 array on a V440 (Solaris 9 9/05, current Recommended
> patch level) and have been setting 7 machines up with Jumpstart. I've
> noticed that the disk ID targets appear to be climbing each time I've
> jumpstarted the system. Well, perhaps not every time, but I can't work
> out why it has some times and not others.

> Currently, these are the first disks in my system:

>        4. c3t48d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

>        5. c3t49d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107>

> Starting at target 48 !

> Anything I can do to bring these back to a more sensible number - and
> preferably stop them wandering at all ? I don't want to obsess over it,
> but I'm writing some system configuration scripts (and associated
> documentation) and I'd rather not gamble that things will change should
> someone have to do a rebuild in my absence.

> Thanks in advance

> Andrew

More information:

sccli> show enclosure-status
 Id Chassis Vendor/Product ID    Rev  PLD  WWNN             WWPN
----------------------------------------------------------------------------
 60 0984F2  SUN StorEdge 3510F D 1046 1000 205000C0FF0984F2
215000C0FF0984F2
                                      Topology: loop(a)  Status:
OK

Enclosure Component Status:
     Type Unit Status   FRU P/N   FRU S/N   Add'l Data
------------------------------------------------------------------
      Fan 0    OK       370-6776  GM21NJ     --
      Fan 1    OK       370-6776  GM21NJ     --
      Fan 2    OK       370-6776  GM21NH     --
      Fan 3    OK       370-6776  GM21NH     --
       PS 0    OK       370-6776  GM21NJ     --
       PS 1    OK       370-6776  GM21NH     --
     Temp 0    OK       370-5535  0984F2     temp=30
     Temp 1    OK       370-5535  0984F2     temp=31
     Temp 2    OK       370-5535  0984F2     temp=30
     Temp 3    OK       370-5535  0984F2     temp=31
     Temp 4    OK       370-5535  0984F2     temp=30
     Temp 5    OK       370-5535  0984F2     temp=30
     Temp 6    OK       370-5538  HG109W     temp=35
     Temp 7    OK       370-5538  HG109W     temp=35
     Temp 8    OK       370-5538  HG109W     temp=33
     Temp 9    OK       370-5538  HG109W     temp=33
     Temp 10   OK       370-6776  GM21NJ     temp=33
     Temp 11   OK       370-6776  GM21NH     temp=32
 DiskSlot 0    OK       370-5535  0984F2     addr=48,led=off
 DiskSlot 1    OK       370-5535  0984F2     addr=49,led=off
 DiskSlot 2    OK       370-5535  0984F2     addr=50,led=off
 DiskSlot 3    OK       370-5535  0984F2     addr=51,led=off
 DiskSlot 4    OK       370-5535  0984F2     addr=52,led=off
 DiskSlot 5    OK       370-5535  0984F2     addr=53,led=off
 DiskSlot 6    OK       370-5535  0984F2     addr=54,led=off
 DiskSlot 7    OK       370-5535  0984F2     addr=55,led=off
 DiskSlot 8    OK       370-5535  0984F2     addr=56,led=off
 DiskSlot 9    OK       370-5535  0984F2     addr=57,led=off
 DiskSlot 10   OK       370-5535  0984F2     addr=58,led=off
 DiskSlot 11   OK       370-5535  0984F2     addr=59,led=off

So how come it started at 48 all of a sudden?

 
 
 

3510 FC array - disk target IDs keep changing during rebuild

Post by andrew » Thu, 17 Nov 2005 02:36:21


Well, I found the answer, and sadly it was that that it didn't start at
48 "all of a sudden". Where I would have bet money it was in the 20's
earlier, I just found the bit in the guide that sets the range of IDs
by the ID switch on the front of the array. The two arrays were set to
ID 2 and 3, and sure enough that started them at 32 and 48.

So how come I didn't spot that sooner? I blame tiredness and stress.

AW (wearing the dunces cap)

 
 
 

3510 FC array - disk target IDs keep changing during rebuild

Post by Charlie Giannet » Fri, 18 Nov 2005 00:46:35




>Well, I found the answer, and sadly it was that that it didn't start at
>48 "all of a sudden". Where I would have bet money it was in the 20's
>earlier, I just found the bit in the guide that sets the range of IDs
>by the ID switch on the front of the array. The two arrays were set to
>ID 2 and 3, and sure enough that started them at 32 and 48.

>So how come I didn't spot that sooner? I blame tiredness and stress.

>AW (wearing the dunces cap)

  I'm not so sure that's the reason.  Take a look at:

sccli> show channels
Ch  Type    Media   Speed   Width  PID / SID
--------------------------------------------
 0  Host    FC(L)   2G      Serial  40 / 41
 1  Host    FC(L)   2G      Serial  43 / 42
 2  Drive   FC(L)   2G      Serial  14 / 15
 3  Drive   FC(L)   2G      Serial  14 / 15
 4  Host    FC(L)   2G      Serial  44 / 45
 5  Host    FC(L)   2G      Serial  47 / 46
 6  Host    LAN     N/A     Serial  N/A / N/A

  I'm pretty sure the numbers you're seeing are the channel definitions
above.  My example does not have channels 32 and 48 defined but
your's almost certainly does.  The ID switch on the front of the arrays
is for connecting JBOD disk trays to a controller (or dual controller)
array.  

- Charlie

 
 
 

3510 FC array - disk target IDs keep changing during rebuild

Post by Hans » Sat, 19 Nov 2005 17:08:35


I'm currently scratching my head over this too.
I have been monitoring a couple of systems with several 3510-units for some
time now and I find that these numbers aren't even constant for the same
system. I'm not sure exactly when the IDs change because this hasn't been
24/7 monitoring. I'm sitting with an example before me whith 2 large
HA-clusters and four 3510 units. Every single ID on all units has changed
since I probed the systems in August.


Quote:> Well, I found the answer, and sadly it was that that it didn't start at
> 48 "all of a sudden". Where I would have bet money it was in the 20's
> earlier, I just found the bit in the guide that sets the range of IDs
> by the ID switch on the front of the array. The two arrays were set to
> ID 2 and 3, and sure enough that started them at 32 and 48.

> So how come I didn't spot that sooner? I blame tiredness and stress.

> AW (wearing the dunces cap)

 
 
 

1. V20z opteron, Red Hat, Sun StorEdge 3510 FC Array?

Hello,

I'm trying to connect a 3510 fibre channel storage array to a V20z
(AMD opteron) box running
64-bit Red Hat Enterprise Linux 3.

Both the 3510 and the V20z are sun products:

http://www.sun.com/storage/workgroup/3000/3500/3510/
http://www.sun.com/servers/entry/v20z/

I tested the 3510 by connecting it to a sparc box running Solaris 9
(with the SAN packages installed).
The sparc box and the 3510 worked well together.

Next, I put a fibre channel card in the V20z:
http://sunsolve.sun.com/handbook_private/Devices/Fibre_Channel/FIBRE_...

I ran a cable from the 3510 to the fibre channel card in the V20z.

I booted the V20z.

Result:
-no link light on the 3510
-both amber and green light on the fibre channel

So, I'm curious:

- Have you ever successfully setup a V20z-3510 fibre channel
connection?
- Do you know of anyone who has successfully setup a V20z-3510 fibre
channel connection?
- Is there anything I should be aware of when attempting to set this
up?
- How would you trouble shoot my no-link-light problem?

-Thanks,

-moi

2. Problem with Plextor CD (not boot, not block size)

3. StorEdge 3510 FC - any good for Sun Cluster 3.0?

4. help!!! 14.4 modem dial-in / out setup

5. Storedge 3510 FC questions

6. Reading writing pipes: Bad Adress

7. Which FCAL to buy for 3510 array?

8. Screen switching in Solaris

9. Did anybody here use the equivalent Seagate FC disks in a Sun T3 disk array?

10. owner id and group id change after mount the new disk

11. Solaris seeing target ID on boot but no disk devices being created

12. Moving Linux install disk SCSI target ID

13. Value of Target Id when Lun spans disks