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-72-1932633.1
Update Date:2018-05-04
Keywords:

Solution Type  Problem Resolution Sure

Solution  1932633.1 :   Oracle ZFS Storage Appliance: iSCSI LUNs are not seen by client systems  


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




In this Document
Symptoms
Changes
Cause
Solution
References


Created from <SR 3-9632155381>

Applies to:

Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7110 Unified Storage System - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

New iSCSI LUNs are created on one node of a ZFS-SA cluster and some other iSCSI LUNs are created on the other cluster node.

There are 2 target IQNs.

One target IQN is for each pool - since this is an active-active cluster.

When discovering the new LUNs (new LUNs started at LUN 45) on the OVM clients, the new iSCSI LUNs are not seen.

The new iSCSI LUNs are configured with the same Host Group and Target Group as the other iSCSI LUNs.

 

In the OVM messages, there are messages like ...

kernel: sd 4:0:0:0: Unexpected response from lun 44 while scanning, scan aborted

 

Changes

 

Cause

The new LUNs were configured on 'this' cluster node .... LUN 44 was on the 'other' cluster node - but LUN 44 had the Target Group set to All

Views for 600144F094A3A90D0000540F52AD0019:

    Data File      : prop unavailable in standby

    Host group     : All

    Target Group   : All

    LUN            : 44

 

Solution

Having the incorrect Target Group caused the OVM client to discover everything up to LUN 43.

But since it was unable to discover LUN 44 down both IQNs, it aborted the discover and didn't discover any LUNs higher than LUN 43 (in this case).

 

The solution is to ensure all LUNs have the correct Host Group and Target Group set on the ZFS-SA.

 

References

<BUG:19690546> - ISCSI LUNS NOT BEING SEEN ON LINUX CLIENT

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