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-2067653.1
Update Date:2015-11-26
Keywords:

Solution Type  Problem Resolution Sure

Solution  2067653.1 :   Oracle ZFS Storage Appliance : Cluster setup failed - 'cabling is not correct or peer is faulty'  


Related Items
  • Sun ZFS Storage 7320
  •  
  • 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
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: ZS
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-11451490021>

Applies to:

Sun Storage 7310 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - 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-4 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

NOTE: To confirm that the cluster 'links' cabling is correctly configured - See Document ID 2081179.1

 

The cluster will not join as both nodes have the same ASN in the root disks

On trying to join the the joining cluster will state:

 'cabling is not correct or peer is faulty'

 

Both heads can be configured to work with dummy values and each will work fine as singletons

Cause

It has been noted from the shipping information that the root disks have been moved between the two heads
 
This meant that both heads having the same ASN & CSN
 

Solution

A factory reset or altering the CSN  did not cure this.

The only option was to reinstall the head using a fishstick on the head that had a different CSN than the one on the SP/ILOM
 

The clue came about when each head was dummy configured, they both had the same serial number in the support bundle.

 

NOTE: Do not move system/boot disks between NAS heads as once the OS is on the CSN and ASN are populated throughout the configuration files.

 

References

<BUG:21945338> - CLUSTER SETUP FAILED - 'CABLING IS NOT CORRECT OR PEER IS FAULTY'

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