Interesting development. I swapped HBAs, and did a reconfig boot. When the
system came back up, the library controller is being reported as a disk instead
of a med_changer.
#cfgadm -al -o show_FCP_dev
....
c6
fc-fabric connected
configured unknown
c6::500104f000595f97 disk
connected unconfigured unknown
c6::500104f000595f9d,0 tape
connected configured unknown
c6::500104f000595fa3,0 tape
connected configured unknown
c6::500104f000595fa9,0 tape
connected configured unknown
c6::500104f000595faf,0 tape
connected configured unknown
c6::500104f000595fb5,0 tape
connected configured unknown
....
c4
fc-fabric connected
configured unknown
c4::500104f000595f9a,0 tape
connected configured unknown
c4::500104f000595fa0,0 tape
connected configured unknown
c4::500104f000595fa6,0 tape
connected configured unknown
c4::500104f000595fac,0 tape
connected configured unknown
c4::500104f000595fb2,0 tape
connected configured unknown
Same I/O error when configuring it.
#cfgadm -c configure c6::500104f000595f97
cfgadm: Library error: failed to create device node:
500104f000595f97: I/O error
/var/adm/messages:
Apr 15 09:27:04 backupsrv Failed to
create nodes for pwwn=500104f000595f97 ; error=5
Apr 15 09:38:33 backupsrv FCP: WWN
0x500104f000595f97 reset successfully
Apr 15 09:46:38 backupsrv scsi: [ID 799468 kern.info] lus33
at fp3: name w500104f0 00595f97,0, bus address 6d0108
Apr 15 09:46:38 backupsrv genunix: [ID 936769 kern.info]
lus33 is /pci@1d,700000/S UNW,qlc@1,1/fp@0,0/lus@w500104f000595f97,0
Apr 15 09:53:18 backupsrv Failed to
create nodes for pwwn=500104f000595f97 ; error=5
Apr 15 09:56:10 backupsrv Failed to
create nodes for pwwn=500104f000595f97 ; error=5
+----------------------------------------------------------------------
|This was sent by dustin.gregory AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|