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-2175454.1
Update Date:2016-09-02
Keywords:

Solution Type  Problem Resolution Sure

Solution  2175454.1 :   Oracle ZFS Storage Appliance: How To Recover From Cannot Reconnect ISCSI LUNs Due To Domain Name Change  


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




In this Document
Symptoms
Cause
Solution


Created from <SR 3-13220973161>

Applies to:

Oracle ZFS Storage ZS3-4 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-2 - Version All Versions to All Versions [Release All Releases]
Oracle ZFS Storage ZS3-BA - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7120 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

Some iSCSI LUNs cannot connect after fail over of the storage node - not all were affected.

However, everything was online in ZFS Storage with no errors reported what so ever.

 

Cause

The customer had reconfigured his network with some DNS domain name changes.

But, the issue did not manifest itself until the the nodes were rebooted for other testing reasons.

 

Solution

iSCSI configuration:

 

Initiators:

NAME ALIAS
initiator-000 <name>
|
+-> INITIATOR
iqn.1991-05.com.microsoft:xxxx.xxxxx.xxxxxxxxx.net

iqn.1991-05.com.microsoft:xxxx.xxxx.xxxxx.com                            <<<<<<<<<<< NEW DOMAIN!

lunguid = 600144F0C8AFDD660000565CDB9A000A

initiatorgroup = XXXXInitiatorGroup
targetgroup = ZStorage1

 

 

This issue can be resolved by simply re-mapping the initiators to the new domain name.

 

 


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