D1000 Storedge array connection

I am trying to connect D1000 storedge with my sun blade 1500 and i am getting the following error when booting the system.

Oct 13 22:21:56 brampton rpcbind: [ID 564983 daemon.error] rpcbind terminating on signal.
Oct 13 22:22:02 brampton syseventd[374]: [ID 617319 daemon.error] SIGHUP caught - reloading modules
Oct 13 22:22:02 brampton svc.startd[7]: [ID 636263 daemon.warning] svc:/system/sysevent:default: Method "/lib/svc/method/svc-syseventd stop 25" failed due to signal HUP.
Oct 13 22:22:02 brampton vxesd[620]: [ID 477869 daemon.notice] Event source daemon stopped
Oct 13 22:22:03 brampton syseventd[374]: [ID 661968 daemon.error] Daemon restarted
Oct 13 22:22:03 brampton genunix: [ID 723447 kern.warning] WARNING: vmem_destroy('devfsadm_event_channel'): leaked 1 identifiers
Oct 13 22:22:28 brampton genunix: [ID 672855 kern.notice] syncing file systems...
Oct 13 22:22:28 brampton genunix: [ID 904073 kern.notice]  done
Oct 13 22:56:10 brampton genunix: [ID 540533 kern.notice] ^MSunOS Release 5.10 Version Generic_142909-17 64-bit
Oct 13 22:56:10 brampton genunix: [ID 877030 kern.notice] Copyright (c) 1983, 2010, Oracle and/or its affiliates. All rights reserved.
Oct 13 22:56:10 brampton genunix: [ID 678236 kern.info] Ethernet address = 8:0:20:ad:44:36
Oct 13 22:56:10 brampton unix: [ID 673563 kern.info] NOTICE: Kernel Cage is ENABLED
Oct 13 22:56:10 brampton unix: [ID 389951 kern.info] mem = 1048576K (0x40000000)
Oct 13 22:56:10 brampton unix: [ID 930857 kern.info] avail mem = 1006714880
Oct 13 22:56:10 brampton rootnex: [ID 466748 kern.info] root nexus = Sun Ultra 60 UPA/PCI (2 X UltraSPARC-II 450MHz)
Oct 13 22:56:10 brampton rootnex: [ID 349649 kern.info] pseudo0 at root
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] pseudo0 is /pseudo
Oct 13 22:56:10 brampton rootnex: [ID 349649 kern.info] scsi_vhci0 at root
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] scsi_vhci0 is /scsi_vhci
Oct 13 22:56:10 brampton rootnex: [ID 349649 kern.info] pcipsy0 at root: UPA 0x1f 0x4000
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] pcipsy0 is /pci@1f,4000
Oct 13 22:56:10 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3 (glm0):
Oct 13 22:56:10 brampton     Rev. 5 Symbios 53c876 found.
Oct 13 22:56:10 brampton pcipsy: [ID 370704 kern.info] PCI-device: scsi@3, glm0
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] glm0 is /pci@1f,4000/scsi@3
Oct 13 22:56:10 brampton scsi: [ID 193665 kern.info] sd4 at glm0: target 0 lun 0
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] sd4 is /pci@1f,4000/scsi@3/sd@0,0
Oct 13 22:56:10 brampton swapgeneric: [ID 308332 kern.info] root on /pci@1f,4000/scsi@3/disk@0,0:a fstype ufs
Oct 13 22:56:10 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@3,1 (glm1):
Oct 13 22:56:10 brampton     Rev. 5 Symbios 53c876 found.
Oct 13 22:56:10 brampton pcipsy: [ID 370704 kern.info] PCI-device: scsi@3,1, glm1
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] glm1 is /pci@1f,4000/scsi@3,1
Oct 13 22:56:10 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:56:10 brampton     Rev. 5 Symbios 53c876 found.
Oct 13 22:56:10 brampton pcipsy: [ID 370704 kern.info] PCI-device: scsi@5, glm2
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] glm2 is /pci@1f,4000/scsi@5
Oct 13 22:56:10 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5,1 (glm3):
Oct 13 22:56:10 brampton     Rev. 5 Symbios 53c876 found.
Oct 13 22:56:10 brampton pcipsy: [ID 370704 kern.info] PCI-device: scsi@5,1, glm3
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] glm3 is /pci@1f,4000/scsi@5,1
Oct 13 22:56:10 brampton scsi: [ID 193665 kern.info] sd0 at glm0: target 1 lun 0
Oct 13 22:56:10 brampton genunix: [ID 936769 kern.info] sd0 is /pci@1f,4000/scsi@3/sd@1,0
Oct 13 22:56:11 brampton scsi: [ID 193665 kern.info] sd6 at glm0: target 6 lun 0
Oct 13 22:56:11 brampton genunix: [ID 936769 kern.info] sd6 is /pci@1f,4000/scsi@3/sd@6,0
Oct 13 22:56:14 brampton rootnex: [ID 349649 kern.info] iscsi0 at root
Oct 13 22:56:14 brampton genunix: [ID 936769 kern.info] iscsi0 is /iscsi
Oct 13 22:57:20 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:57:20 brampton     Cmd (0x30001107d48) dump for Target 0 Lun 0:
Oct 13 22:57:20 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:57:20 brampton         cdb=[ 0x12 0x0 0x0 0x0 0x30 0x0 ]
Oct 13 22:57:20 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:57:20 brampton     pkt_flags=0x808 pkt_statistics=0x60 pkt_state=0x7
Oct 13 22:57:20 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:57:20 brampton     pkt_scbp=0x0 cmd_flags=0x2860
Oct 13 22:57:20 brampton scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:57:20 brampton     Connected command timeout for Target 0.0
Oct 13 22:57:20 brampton genunix: [ID 408822 kern.info] NOTICE: glm2: fault detected in device; service still available
Oct 13 22:57:20 brampton genunix: [ID 611667 kern.info] NOTICE: glm2: Connected command timeout for Target 0.0
Oct 13 22:57:20 brampton glm: [ID 280919 kern.warning] WARNING: ID[SUNWpd.glm.cmd_timeout.6017]
Oct 13 22:57:20 brampton scsi: [ID 107833 kern.warning] WARNING: /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:57:20 brampton     got SCSI bus reset
Oct 13 22:57:20 brampton genunix: [ID 408822 kern.info] NOTICE: glm2: fault detected in device; service still available
Oct 13 22:57:20 brampton genunix: [ID 611667 kern.info] NOTICE: glm2: got SCSI bus reset
Oct 13 22:58:31 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:58:31 brampton     Cmd (0x30001107d48) dump for Target 0 Lun 0:
Oct 13 22:58:31 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):
Oct 13 22:58:31 brampton         cdb=[ 0x12 0x0 0x0 0x0 0x30 0x0 ]
Oct 13 22:58:31 brampton scsi: [ID 365881 kern.info] /pci@1f,4000/scsi@5 (glm2):

Please help.

I am not sure how the configuration option and box id works.

how do you connect the box to your blade? please discribe in detail... which scsi card do you use and so on...

I have two nodes connected to this array via SCSI cables.
SCSI initiator id is set 6 on one node and 7 on other node. its dual scsi connection.

Don't know whether if it is your prob,but maybe check: disks ID should be within the range of what is specified in the drivers.

again, what kind of SCSI HBA do you use?

what is the box id on the back of the array ?

what is used for?

Sun StorEdge A1000 and D1000 Installation, Operations, and Service Manual - Sun Microsystems

I checked this manual but I can't find it

---------- Post updated at 07:06 PM ---------- Previous update was at 07:04 PM ----------

I am using Dual SCSI card.

Is it you asking.

---------- Post updated at 07:09 PM ---------- Previous update was at 07:06 PM ----------

i am using dual scsi card.

are you aware that there are different SCSI standards? if i remember right, you need a HVD SCSI adapter to use the D1000 box. so not EVERY other adapter works! page 25 of the admin guide gives some clues... also page 29 should answer your "id" question...

I checked with three SCSI cables and i don't see any problem with the connection.

I did turn on the D1000 first and started Blade 1500 and went to OK prompt.

From ok prompt.

OK> probe-scsi-all
Nothing came.

If I disconnect the scsi connection and start the Sun box first and turn on the array I will able to see 8 disks when I run format command.

devfsadm takes longer than ever.

What could be the issue.

If I restart the system I will get the following message repeatedly

got SCSI bus reset

---------- Post updated at 09:41 PM ---------- Previous update was at 09:39 PM ----------

on the back of the D1000 there is something called box id. is box related to scsi-initiator-id?