Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1616246.1
Update Date:2018-01-08
Keywords:

Solution Type  Technical Instruction Sure

Solution  1616246.1 :   Sun Storage 7000 Unified Storage System: How to verify FC attached Tape Library is correctly configured into the ZFSSA  


Related Items
  • Sun ZFS Storage 7420
  •  
  • Oracle ZFS Storage ZS3-2
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Oracle ZFS Storage ZS4-4
  •  
  • Sun Storage 7410 Unified Storage System
  •  
  • Sun Storage 7310 Unified Storage System
  •  
  • Sun ZFS Storage 7120
  •  
  • Oracle ZFS Storage ZS3-4
  •  
  • Sun ZFS Storage 7320
  •  
  • Oracle ZFS Storage Appliance Racked System ZS4-4
  •  
  • Oracle ZFS Storage ZS3-BA
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
  •  


Service Request was opened for the issue "SL150 library not seen by the ZFSSA".
Investigating the issue showed that one drive was seen correctly while the other wasn't.  Also the changer wasn't seen.
This document shows some techniques which help to find the cause of the issue.

In this Document
Goal
Solution
References


Created from <SR 3-8362309091>

Applies to:

Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
Sun ZFS Storage 7120 - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
7000 Appliance OS (Fishworks)
The configuration consists of a 7420 ZFSSA with two FC-HBAs, two FC-switches and an SL150 library with two drives.
The drives are connected to port 9 of each switch.
The SL150-changer connects also via port 9 on switch1.
The FC-HBAs of the ZFSSA are (supposed to be) connected to port 8 of each switch.
The switches have zoning implemented...

Goal

How to verify an FC tape library is configured correctly into a ZFSSA
 

Solution

Additional information of note:

The FC HBA's must be configured in INITIATOR mode in order to work in combination with FC tape drives/libraries.
This was the default, but in the latest Appliance Firmware Release 2013.x, the default mode for an FC port is target.

Changing the setting from TARGET to INITIATOR requires a reboot.

 

With the use of a few commands, one can check the availability of both drives and changer in Solaris.

Checking the configuration in the (un-packed) support bundle we see:

% more <bundle_directory>/ndmp/devices.out
Tape drive(s):
        Name      : /dev/rmt/0bn
        LUN #     : 0
        SCSI ID # : 0
        Vendor    : HP
        Product   : Ultrium 6-SCSI
        Revision  : 22GS
        Serial    : HU1320VTJ6
        WWN       : 0x500104F000CD7649

Tape drive(s):
        Name      : /dev/rmt/0dbn
        LUN #     : 0
        SCSI ID # : 0
        Vendor    : HP
        Product   : Ultrium 6-SCSI
        Revision  : 22GS
        Serial    : HU1320VTJ6

        WWN       : 0x500104F000CD7649

NOTE: We only see one drive here (/dev/rmt/0 in two densities).

 

% more <bundle_directory>/hw/cfgadm-alv.txt

Ap_Id                          Receptacle   Occupant     Condition  Information
When         Type         Busy     Phys_Id
c5::500104f000cd764a           connected    configured   unknown    HP Ultrium 6-SCSI
unavailable  tape         n        /devices/pci@75,0/pci8086,3408@1/pci1077,171@0,1/fp@0,0:fc::500104f000cd764a

(some output snipped for brevity )

NOTE: Here again we only find one drive.

 

The customer also provided some information from the 2 Fibre Channel switches involved in this configuration:

switchshow for switch1 shows:

Index Port Address Media Speed State     Proto\
==============================================\
  0   0   010000   id    N8   Online      FC  F-Port  21:00:00:24:ff:4d:f7:80 \
  1   1   010100   id    N8   Online      FC  F-Port  21:00:00:24:ff:47:82:b0 \
  2   2   010200   id    N8   Online      FC  F-Port  21:00:00:24:ff:4e:20:42 \
  3   3   010300   id    N8   Online      FC  F-Port  21:00:00:24:ff:47:82:64 \
  4   4   010400   id    N8   Online      FC  F-Port  21:00:00:24:ff:4d:fb:ac \
  5   5   010500   id    N8   Online      FC  F-Port  21:00:00:24:ff:4d:fa:74 \
  6   6   010600   id    N8   Online      FC  F-Port  21:00:00:24:ff:4e:20:fc \
  7   7   010700   id    N8   Online      FC  F-Port  21:00:00:24:ff:4c:f8:a8 \
  8   8   010800   id    N8   Online      FC  F-Port  21:00:00:24:ff:4c:f8:e6 \
  9   9   010900   id    N8   Online      FC  F-Port  50:01:04:f0:00:cd:76:47 \

 

switchshow for switch2 shows:

Index Port Address Media Speed State     Proto\
==============================================\
  0   0   010000   id    N8   Online      FC  F-Port  21:00:00:24:ff:4d:f7:81 \
  1   1   010100   id    N8   Online      FC  F-Port  21:00:00:24:ff:47:82:b1 \
  2   2   010200   id    N8   Online      FC  F-Port  21:00:00:24:ff:4e:20:43 \
  3   3   010300   id    N8   Online      FC  F-Port  21:00:00:24:ff:47:82:65 \
  4   4   010400   id    N8   Online      FC  F-Port  21:00:00:24:ff:4d:fb:ad \
  5   5   010500   id    N8   Online      FC  F-Port  21:00:00:24:ff:4d:fa:75 \
  6   6   010600   id    N8   Online      FC  F-Port  21:00:00:24:ff:4e:20:fd \
  7   7   010700   id    N8   Online      FC  F-Port  21:00:00:24:ff:4c:f8:a9 \
  8   8   010800   id    N8   Online      FC  F-Port  21:00:00:24:ff:4c:f8:e7 \
  9   9   010900   id    N8   Online      FC  F-Port  50:01:04:f0:00:cd:76:4a \

Looking at port 9 we see WWNs beginning with 50:01:04.

The last WWN 50:01:04:f0:00:cd:76:4a can be found back in the cfgadm-alv output above.  So the ZFSSA sees a tape drive connected via switch2.

 

The support bundle does not contain enough information, so we access the affected system remotely (via shared shell) to determine what ports are seen on the switch.

We use the 'luxadm' command for that:

First check which ports we have connections to:

CLI> confirm shell  luxadm -e port
/devices/pci@0,0/pci8086,3408@1/pci1077,171@0,1/fp@0,0:devctl      CONNECTED
/devices/pci@75,0/pci8086,3408@1/pci1077,171@0,1/fp@0,0:devctl     CONNECTED

Now we use the device tree of the above output to investigate what ports the ZFSSA sees on the switch and (more important here) what switch port the HBA's are connected to:

(For switch1)

CLI> confirm shell  luxadm -e dump_map /devices/pci@0,0/pci8086,3408@1/pci1077,171@0,1/fp@0,0 | sort +1                                      
1    10000   0        21000024ff4df781 20000024ff4df781 0x1f (Unknown Type)                                                         
7    10100   0        21000024ff4782b1 20000024ff4782b1 0x1f (Unknown Type)                                                         
5    10200   0        21000024ff4e2043 20000024ff4e2043 0x1f (Unknown Type)                                                         
4    10300   0        21000024ff478265 20000024ff478265 0x1f (Unknown Type)                                                         
6    10400   0        21000024ff4dfbad 20000024ff4dfbad 0x1f (Unknown Type)                                                         
0    10500   0        21000024ff4dfa75 20000024ff4dfa75 0x1f (Unknown Type)                                                         
2    10600   0        21000024ff4e20fd 20000024ff4e20fd 0x1f (Unknown Type)                                                         
8    10700   0        21000024ff4cf8a9 20000024ff4cf8a9 0x1f (Unknown Type,Host Bus Adapter)   << Port 7: FC-HBA in 7420
3    10800   0        21000024ff4cf8e7 20000024ff4cf8e7 0x1f (Unknown Type)                    
Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type

NOTE: The second and third character of the Port_ID tell us the port number.

From the above information we can see that the FC HBA of the 7420 is connected to port 7 of the switch.  It does not see any tape drives connected to the switch.

(For switch2)
CLI> confirm shell  luxadm -e dump_map /devices/pci@75,0/pci8086,3408@1/pci1077,171@0,1/fp@0,0 | sort +1                                                
1    10000   0        21000024ff4df781 20000024ff4df781 0x1f (Unknown Type)                                                         
8    10100   0        21000024ff4782b1 20000024ff4782b1 0x1f (Unknown Type)                                                         
6    10200   0        21000024ff4e2043 20000024ff4e2043 0x1f (Unknown Type)                                                         
4    10300   0        21000024ff478265 20000024ff478265 0x1f (Unknown Type)                                                         
7    10400   0        21000024ff4dfbad 20000024ff4dfbad 0x1f (Unknown Type)                                                         
0    10500   0        21000024ff4dfa75 20000024ff4dfa75 0x1f (Unknown Type)                                                         
2    10600   0        21000024ff4e20fd 20000024ff4e20fd 0x1f (Unknown Type)                                                         
3    10700   0        21000024ff4cf8a9 20000024ff4cf8a9 0x1f (Unknown Type)                                                         
9    10800   0        21000024ff4cf8e7 20000024ff4cf8e7 0x1f (Unknown Type,Host Bus Adapter)   << Port 8: FC-HBA in 7420
5    10900   0        500104f000cd764a 500104f000cd7649 0x1  (Tape device)                     << Port 9: Tape-drive
Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type    

On switch2, we see that the FC-HBA of the 7420 is connected to port 8.  It sees the tape drive correctly.

 

From this, we have a good indication on the cause of the issue.

The customer has zoning implemented and has a zone setup between ports 8 and 9 in order to have the ZFSSA FC-HBAs see the tape drives (and changer).

Unfortunately, during installation of the system someone swapped the cables and put the FC cable coming from the first FC HBA of the ZFSSA into port 7 on switch1 instead of port 8.

 

Customer had two options to correct this: change the cable to the correct position or change the zoning and adapt system documentation.

 

After modification the changer and both drives are seen:

$ more <bundle_directory>/hw/cfgadm-alv.txt:

c2::500104f000cd7647           connected    configured   unknown    HP Ultrium 6-SCSI
unavailable  tape         n        /devices/pci@0,0/pci8086,3408@1/pci1077,171@0/fp@0,0:fc::500104f000cd7647

c5::500104f000cd764a           connected    configured   unknown    HP Ultrium 6-SCSI
unavailable  tape         n        /devices/pci@75,0/pci8086,3408@1/pci1077,171@0,1/fp@0,0:fc::500104f000cd764a

 

$ more <bundle_directory>/ndmp/devices.out:

Robot (Changer):
        Name      : /dev/scsi/changer/c7t500104F000CD7646d0
        LUN #     : 0
        SCSI ID # : 0
        Vendor    : STK
        Product   : SL150
        Revision  : 0200
        Serial    : 464970G+1322SY09
        WWN       : 0x500104F000CD7646

Tape drive(s):
        Name      : /dev/rmt/0bn
        LUN #     : 0
        SCSI ID # : 0
        Vendor    : HP
        Product   : Ultrium 6-SCSI
        Revision  : 22GS
        Serial    : HU1320VTJ6
        WWN       : 0x500104F000CD7649

Tape drive(s):
        Name      : /dev/rmt/0dbn
        LUN #     : 0
        SCSI ID # : 0
        Vendor    : HP
        Product   : Ultrium 6-SCSI
        Revision  : 22GS
        Serial    : HU1320VTJ6
        WWN       : 0x500104F000CD7649

Tape drive(s):
        Name      : /dev/rmt/1bn
        LUN #     : 0
        SCSI ID # : 1
        Vendor    : HP
        Product   : Ultrium 6-SCSI
        Revision  : 22GS
        Serial    : HU1320VTJR
        WWN       : 0x500104F000CD7646

Tape drive(s):
        Name      : /dev/rmt/1dbn
        LUN #     : 0
        SCSI ID # : 1
        Vendor    : HP
        Product   : Ultrium 6-SCSI
        Revision  : 22GS
        Serial    : HU1320VTJR
        WWN       : 0x500104F000CD7646

 

 

 

References

<NOTE:1434004.1> - Sun Storage 7000 Unified Storage System: Verifying that the Unified Storage has been configured correctly for Fibre-Channel connectivity

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback