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-2293206.1
Update Date:2018-03-07
Keywords:

Solution Type  Problem Resolution Sure

Solution  2293206.1 :   Device Naming Conventions depemdences on FUJITSU ETERNUS DXL Storage Arrays  


Related Items
  • Netra SPARC T4-1 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>HBA>SN-DK: FC HBA
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-15406258501>

Applies to:

Netra SPARC T4-1 Server - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

Customer was using 2 identical FUJITSU ETERNUS DXL Storage Arrays, which showed different device naming , when connected to a solaris host.

Foe one array short  form cXtYd... for the other array the long form cXtWWNd....

Cause

.Checking the FUJITSU ETERNUS DXL Storage Arrays configurations we found different settings for 2 arrays.

 ( short device names ) < manual' Loop ID>  on one array and <Loop ID set to 0x0> on the other array. 

Loop ID set to 0x0
 
.
 

Solution

 a. Set the <Loop ID set to 0x0> when you need the ( wwn device names)on the FUJITSU ETERNUS DXL Storage Array (/dev/rdsk/c6t500000E0DA010220d0s2)
 b. Set the < manual' Loop ID> when you need the ( short device names ) on the FUJITSU ETERNUS DXL Storage Array (/dev/rdsk/c6t0d0s2)

 

References

<NOTE:2253395.1> - Solaris 10 - Reservation Conflict Panic On Replugging FC Cable To FUJITSU ETERNUS_DXL LUNs

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