I'm running Solaris 8 / Sun StorEdge Enterprise Backup 7.4.3 on a Sun Fire 
V440.  The library I'm having problems with is a FC attached STK L180 with 
10xLTO2 drives.

We had three drives fail on our L180 a few days ago, so the tech came out to 
replace them.  While he was there, he turned on the WWN Feature in the L180 
which would create static WWNs for the library and drives.  This done so we 
wouldn't have to re-configure every time a drive failed.

After the WWNs were changed, we did a reconfiguration boot and was able to see 
everything via cfgadm.   

The drives all showed up in /dev/rmt/ and we can access them just fine. 

cfgadm -al -o show_FCP_dev|egrep 'med|tape'
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
c6::500104f000595f97,0        
 med-changer  connected    configured   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

Added the entries to /usr/kernel/drv/lus.conf, and ran inquire.   We were able 
to see all the drives and the library just fine.


#inquire
...
[email protected]:STK     L180        
    0317|Autochanger (Jukebox)
                      
                    
 S/N: MPC51001930
                      
                    
 WWNN=500104F000595F96
                      
                    
 WWPN=500104F000595F97
                      
                    
 PORT=00000001
...


However, when I run jbconfig or jbconfig -l, it seems to hang forever, and 
eventually fails with this message in the syslog:


lus: NOTICE: lus_intr(10.100.0): transport failure 
(timeout)
Failed to create nodes for pwwn=500104f000595f97; error=5
scsi: [ID 799468 kern.info] lus33 at fp3: name 
w500104f000595f97,0, bus address 6d0108
genunix: [ID 936769 kern.info] lus33 is 
/pci@1d,700000/SUNW,qlc@1,1/fp@0,0/lus@w500104f000595f97,0


The wwn in the error messages happens to be the robotics.  I tried to do a 
configure on the port, and it fails.


#cfgadm -c configure c6
cfgadm: Library error: failed to create device node: 
500104f000595f97: I/O error
Operation partially successful. Some failures seen


I'm also getting the I/O error using sji commands.

#sjiinq [email protected]
SJIINQ: Device busy
1640&#58;&#40;pid 8154&#41;&#58; Code&#58;0x29, Str=<I/O error>
#


#luxadm -e dump_map /devices/pci@1d,700000/SUNW,qlc@1,1/fp@0,0&#58;devctl
Pos&nbsp; Port_ID Hard_Addr Port WWN&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Node 
WWN&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Type
0&nbsp; &nbsp; 6d0108&nbsp; 0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;500104f000595f97 
500104f000595f96 0x8&nbsp; &#40;Medium changer device&#41;
1&nbsp; &nbsp; 6d0255&nbsp; 6d0055&nbsp; &nbsp; 500104f000595fb5 
500104f000595fb4 0x1&nbsp; &#40;Tape device&#41;
2&nbsp; &nbsp; 6d0355&nbsp; 6d0055&nbsp; &nbsp; 500104f000595faf 
500104f000595fae 0x1&nbsp; &#40;Tape device&#41;
3&nbsp; &nbsp; 6d0455&nbsp; 6d0055&nbsp; &nbsp; 500104f000595fa9 
500104f000595fa8 0x1&nbsp; &#40;Tape device&#41;
4&nbsp; &nbsp; 6d0555&nbsp; 6d0055&nbsp; &nbsp; 500104f000595fa3 
500104f000595fa2 0x1&nbsp; &#40;Tape device&#41;
5&nbsp; &nbsp; 6d0755&nbsp; 6d0055&nbsp; &nbsp; 500104f000595f9d 
500104f000595f9c 0x1&nbsp; &#40;Tape device&#41;
6&nbsp; &nbsp; 6d0000&nbsp; 0&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;210100e08b31106c 
200100e08b31106c 0x1f &#40;Unknown Type,Host Bus Adapter&#41;
#


This was working before we turned on the WWN Feature on the L180.  It's almost 
like cfgadm is having problems recognizing the library.

The tech is coming out tomorrow to rule out hardware issues, and I may ask him 
to turn off the WWN Feature so we can see if that is causing us grief. 

We're also going to look at swapping out the MCB board on the library and 
possibly the HBA in the server. 

I've power cycled the library, the server, reconfiguration boots,  
unconfiguring, configuring the HBA, re-installed Networker, etc, etc...

Has anyone ran across this before?  Any ideas?

Thanks in advance.

+----------------------------------------------------------------------
|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